Telecommunications (Mobile Equipment Air Interface) Technical Standard 2022

The instrument builds its legal and operational structure around a small set of interlocking concepts. These are the concepts you must map to product, supply-chain and compliance processes to determine regulatory effect.

• Item, customer equipment and addressable device (ss 5, 6, 13). The standard applies only to “a thing that is customer equipment” that is designed or intended for use with a public mobile telecommunications service or satellite service and is an addressable device (s 13). The term addressable device is defined in s 6 as a device that enables a carriage service provider to identify the device when used for two-way communications on a public mobile telecommunications service or a satellite service supplied by the carriage service provider. The instrument therefore targets devices that can be identified on the operator’s network, not every device with wireless capability.

• IMT, IMT items and technology subsets (s 6). IMT refers to the international mobile telecommunications family of technologies covering third, fourth and fifth generation systems (s 6). The standard distinguishes between IMT items using 3G/4G technologies (3G/4G technology defined), and those using 5G technology (5G technology defined). These distinctions determine which parts of the AS/CA S042 series are “applicable industry standards” (s 8).

• Applicable industry standard and incorporation by reference (ss 8, 15, 17-18). The instrument makes particular Communications Alliance standards applicable (AS/CA S042.1:2022 in all cases; S042.4:2022 for 3G/4G IMT items; S042.5:2022 for 5G IMT items), and prescribes that compliance is assessed against the version of the standard as it exists on the item’s “relevant date” or against replacement standards where the relevant date is on or after the publication date (s 15). The instrument expressly permits incorporation of standards “as in force from time to time” in other legislative instruments (s 7) and relies on publication dates for transition rules (ss 9, 15(1)(b)).

• Relevant date and modification (ss 11-12). The relevant date is the date the item is manufactured or imported (for an original item) or the date a modified item is made (s 12). The instrument treats post-manufacture modifications, including software updates, as modifications (s 6 definition of modified item and note), and the date of modification is the date the modification was made (s 11). Therefore, updates or modifications may alter the relevant compliance standard that applies.

• Classes of items and material modification (s 10, s 15(3)-(4)). The standard allows class-based compliance where items are identical and have the same manufacturer/importer, with the original item of the class used to determine compliance for the class (s 10, s 15(3)). It also permits an item to be taken as compliant if it would have been in a class but for a non-material modification, where materiality is defined in relation to whether the modification could reasonably affect the item’s compliance with the same version of the standard (s 15(4) and note).

• Transition periods for amended or replacement standards (s 9). If an applicable industry standard is amended or replaced by an instrument prepared by Communications Alliance Ltd, there is a default transition period of 12 months from the publication date of the amending instrument or replacement standard, unless that instrument specifies a longer period up to 24 months. This defines the window within which certain alternatives for compliance are available (s 9 and s 15(2)).

• Savings and phased treatment for pre-commencement items (Part 4). The instrument preserves compliance for items whose relevant date occurred prior to commencement by recognising compliance with the old technical standard or with specified earlier versions of the AS/CA documents (ss 17-19). There is a 12-month window post-commencement during which earlier versions remain available as compliance options (s 18).

These concepts create a compliance regime that is date-driven (manufacture/import/modification dates), standards-driven (specific AS/CA documents incorporated by reference), and class-aware (original items can supply compliance for identical items). They also bring Communications Alliance publication timing and the ACMA’s repeal of the prior instrument (s 4) into practical relevance when deciding which version of a standard applies to any given device.

This instrument distributes obligations and choices across a narrow set of market actors; the text identifies who is directly within remit and who bears compliance exposure.

• Manufacturers and importers. The term manufacturer explicitly includes a person who modifies an item (s 6). Modified items are defined to include changes made after manufacture or importation, including software updates made by or on behalf of the manufacturer or importer (s 6). Therefore, manufacturers and importers of addressable customer equipment intended for public mobile telecommunications or satellite services are the primary parties responsible for ensuring items comply with the applicable industry standard as determined by the item’s relevant date (ss 13, 15, 11-12). Those entities must track manufacture/import dates, modification dates, and keep evidence of compliance.

• Entities that modify equipment. Because the definition of manufacturer includes persons who modify the item (s 6), any third party that modifies devices on behalf of the original manufacturer or importer may incur responsibilities as manufacturer for the purposes of this standard. The definition of modified item is broad and includes software updates applied after manufacture or import (s 6). Consequently, software vendors, device management service providers, and original equipment manufacturers who push over-the-air updates must consider whether their actions trigger manufacturer obligations.

• Carriage service providers. The instrument targets devices that are “addressable” on a public mobile telecommunications service or a satellite service supplied by a carriage service provider (s 13 and definition of addressable device in s 6). While the instrument places compliance obligations on manufacturers/importers, carriage service providers will be affected operationally because the standard’s purposes include protecting the integrity of telecommunications networks and ensuring interoperability and emergency call access (s 5). Carriage service providers may therefore encounter operational impacts, device rejection or provisioning requirements from a network-integrity perspective, although the instrument itself does not set network operator obligations.

• Communications Alliance Ltd. The standard incorporates Communications Alliance standards and makes those publications central to compliance (s 8). Communications Alliance prepares amending instruments and replacement standards; the publication date of those documents triggers transition periods and dictates which versions are applicable to items (s 9). Thus, Communications Alliance’s publication schedule and the content of its standards effectively shape compliance obligations for industry participants.

• Consumers and businesses using addressable devices. Indirectly affected are purchasers, businesses and end users of devices that are addressable on public mobile or certain satellite services. The standard’s technical and compliance requirements may affect device availability, feature sets (if certain hardware or software functions are disallowed for network integrity or interoperability reasons), and costs. The instrument’s inclusion of software modifications within the definition of modified item could mean that post-sale updates alter regulatory status for a device (s 6, s 11).

• Importers, customs and supply-chain actors. The relevant date rules hinge on the date of import (s 12); importers therefore need to manage records showing dates and versions relevant to compliance. The instrument’s savings for items with relevant dates before commencement (Part 4, ss 17-19) is materially relevant to importers who moved stock into Australia before 22 December 2022.

Who pays and who decides. The obligations fall primarily on manufacturers, importers and any parties who modify devices (s 6). The decisions that determine compliance,whether an item is an IMT item using specified technologies, whether a modification is material, and which version of an AS/CA standard is applicable,are functions that industry actors must make based on the instrument’s definitions and Communications Alliance publication dates (ss 6, 8, 9, 10, 11, 15). ACMA made the instrument (s 3) and retains the policy authority to set standards under the Act.

The technical standard creates duties and configurational rights that are primarily compliance-oriented and hinge on the applicable industry standards and timing rules.

Primary duties

• Duty to ensure item compliance with applicable industry standards. An item must meet the requirements in subsection 15(1), (2), (3) or (4) in relation to each applicable industry standard (s 14(1)). Concretely this means meeting AS/CA S042.1:2022 in all cases, and where relevant AS/CA S042.4:2022 or S042.5:2022 depending on whether the IMT item uses 3G/4G or 5G technology (s 8). Subsection 15(1) ties the applicable version to the relevant date for the item; subsection 15(2) addresses items whose relevant date occurs during a transition period for an amending instrument or replacement standard.

• Duty to account for modified items. Modified items are treated as distinct items with a relevant date equal to the modification date (s 11). The manufacturer definition includes people who modify an item (s 6), so parties that perform modifications must ensure the resulting modified item is compliant with the applicable industry standards for the relevant date.

• Duty to manage class-of-items claims. Where an item belongs to a class, the class’ original item or original modified item can supply compliance for the class (s 10, s 15(3)). A duty arises to show that items are identical, have the same manufacturer/importer, and that any modifications are not material (s 10, s 15(4) and note).

Rights and structuring options for regulated parties

• Choice of which version to comply with within transition periods. If the applicable industry standard is amended or replaced, an item whose relevant date occurs during the transition period may comply with the pre-amendment standard, the amended standard as at publication date, or the replacement standard as at its publication date (s 15(2)). The transition period is governed by s 9, generally 12 months from publication unless the amending instrument specifies a longer period up to 24 months.

• Savings for pre-commencement items. Items with relevant dates before commencement are taken to comply if they complied with the old technical standard, or with specified earlier versions of the AS/CA S042 documents (Part 4, ss 17-19). This gives importers and manufacturers a certainty window for stock imported or manufactured before the changeover.

• Class-based compliance. Where items are identical and share the same manufacturer/importer, compliance can be established through the original item of the class (s 10, s 15(3)). This reduces repeated testing obligations if developers and suppliers can show class identity.

Operational duties implied by the standard

• Recordkeeping and traceability of manufacture/import dates and modification dates. The relevant date determines which version of a standard applies (s 12), and the instrument’s reliance on Communications Alliance publication dates for transition rules (s 9) makes accurate recordkeeping an operational necessity.

• Monitoring Communications Alliance publications. The applicable industry standards and their amending/replacement instruments are instruments of Communications Alliance Ltd; their publication dates trigger transition treatment and determine applicable standards (ss 8, 9, 15). Industry actors must monitor these publications to exercise the compliance choice permitted under transition periods.

Limitations and constraints

• Scope of the ACMA’s standard is purpose-limited. Section 5 recites the permitted purposes for requirements in this technical standard: protecting network integrity, health and safety, emergency call access, and interoperability for standard telephone service supply (s 5(2)). Requirements beyond these subjects are not within the stated scope of the instrument.

• Incorporation is time-specific. The instrument does not generally import the AS/CA standards in perpetuity as amended; s 15 prescribes how different versions apply depending on the item’s relevant date or the publication date of replacement standards. Parties cannot assume the latest standard applies retroactively to items with earlier relevant dates.

The technical standard itself does not specify offences, monetary penalties or enforcement mechanisms within its text. The document repeatedly links to, and is made under, the Telecommunications Act 1997, and contains notes that other expressions and definitions used are those found in the Act (s 3; notes to s 6 and s 7). The text therefore delegates the question of legal consequences for non-compliance to the Act and associated enforcement framework rather than setting penalties in the standard.

What the instrument does state about enforcement-relevant features

• ACMA as maker of the instrument. The standard is explicitly made by ACMA under s 376(1) of the Telecommunications Act 1997 (s 3). That legislative provenance is the relevant legal foundation for any enforcement actions related to the instrument.

• Incorporation of standards and effectivity tied to dates. The instrument sets out what constitutes compliance for different items by reference to the applicable industry standards and relevant dates (ss 8, 11-15). An enforcement process would therefore focus on whether an item meets the version of the standard applicable by those rules; the standard supplies the substantive compliance test.

• Transitional and savings arrangements. Part 4 (ss 16-19) preserves compliance positions for items manufactured/imported or modified before certain dates. Enforcement assessments would need to account for those savings rules.

What the standard does not do and how that affects enforcement

• Does not specify sanctions. There are no offence provisions or civil penalties set out in this technical standard. The instrument therefore does not itself create new penalties; it sets substantive obligations to which other statutory enforcement measures would attach if provided by the Act.

• Does not prescribe ACMA procedural approaches. The standard does not set out ACMA’s internal procedures for investigations, notices, or remedial steps. Any such enforcement mechanisms must be sourced in the Act or other legislative instruments.

Implication for regulated parties

• Enforcement outcomes depend on the Act and ACMA’s powers under the Act. The standard establishes what it means to comply, and therefore defines the substantive benchmark ACMA or other authorities will use if they act under powers in the Act. Regulated parties should therefore consult the Telecommunications Act 1997 for the statutory powers and sanctions that ACMA may invoke for non-compliance, and treat the standards-prescribed compliance tests as the substantive obligations ACMA will assess.

• Evidence and recordkeeping will matter. Because the instrument ties compliance to manufacture/import/modification dates and to versioned standards, proof of dates, versioning and conformity testing is likely to be primary evidence in any enforcement process. The instrument’s silence on sanctions increases the practical importance of being able to demonstrate compliance under its rules.

In short, the Mobile Equipment Standard 2022 sets out what compliance means and who must comply; enforcement, penalties and remedial procedures are matters to be found in the Telecommunications Act 1997 and instruments made under it rather than in this technical standard itself (s 3 and accompanying notes).

The standard is an instrument under the Telecommunications Act 1997 and explicitly references multiple provisions of that Act and other instruments. Its interaction with other legal instruments arises chiefly by incorporation of industry standards, by reliance on definitions and statutory concepts found in the Act, and by preserving prior compliance under the old technical standard.

Key statutory interactions and cross-references

• Made under s 376(1) of the Telecommunications Act 1997 (s 3). The legal authority for ACMA to make this standard derives from subsection 376(1). This ties the instrument’s legal force to the powers established in the Act.

• Incorporation references to the Act. Section 6 notes that many expressions used in this technical standard are defined in the Act, and enumerates specific sections for carriage service, carriage service provider, customer equipment, emergency call service, facility, import, manufacturer or importer of customer equipment or customer cabling, public mobile telecommunications service, satellite-based facility, standard telephone service, and telecommunications network (s 6 notes). That means resolving many terms used in this standard requires looking to the Act’s definitions.

• References to other legislative instruments. Section 7 states that, unless the contrary intention appears, references to any other legislative instrument are references to that instrument as in force from time to time (s 7). This treats dynamic amendments to referenced instruments in accordance with ordinary legislative interpretation rules and ties the technical standard to the wider legislative architecture.

• Incorporation of Communications Alliance documents and transition rules. The standard depends on Communications Alliance Ltd standards (AS/CA S042.*) and gives effect to amending instruments and replacement standards prepared by Communications Alliance via the transition period mechanism (s 9). Sections 15, 17 and 18 expressly state the versions of the industry standards that are applicable for items based on manufacture/import/modification dates.

• Savings for the old technical standard. Section 4 repeals the 2018 technical standard and Part 4 (ss 16-19) creates savings that preserve compliance for items compliant with the old standard or specified earlier versions of the AS/CA S042 series. This avoids retroactive invalidation of stock brought into market prior to commencement.

Other statutory concepts implicated

• Manufacturer and importer responsibilities cross-referenced to s 406A of the Act. The notes to s 6 reference the Act’s definition of manufacturer or importer of customer equipment or customer cabling (see s 406A), indicating that obligations flowing from other parts of the Act (for example labelling, reporting or notice duties) may interact with the compliance regime in this technical standard. Regulated parties should consult s 406A and related parts of the Act as available.

• Network integrity, emergency call access and interoperability. Section 5 limits the purposes of the standard to protecting network or facility integrity; protecting health and safety of persons operating, working on, or using services supplied by means of a telecommunications network or facility; ensuring access to emergency call services; and ensuring interoperability for the supply of a standard telephone service (s 5(2)). These are the substantive legal bases that justify ACMA’s imposition of technical requirements.

Consequences for statutory interpretation and administrative action

• The standard’s requirements must be interpreted and administered in light of the Act’s definitions and powers. Because the standard is an instrument made under the Act, its operation will interact with the Act’s enforcement and administrative mechanisms (see s 3 and notes). For example, whether a device is an “addressable device” for the carrier’s purposes will be determined by the text of this standard and by the Act’s definitions; any ACMA action will be taken under the Act’s powers.

• Communications Alliance standards operate as quasi-delegated technical content. The standard relies on Communications Alliance publications for technical substance. Those documents are not themselves legislative instruments made by ACMA, but the technical standard imports them by reference (s 8). This creates an interaction between industry-developed standards and statutory law: the content and timing of Communications Alliance publications, particularly publication dates and amending instruments, alter the legal compliance test through the transition rules (s 9).

Practical points on cross-law compliance

• Compliance obligations under this technical standard sit alongside any other obligations in the Act or other applicable laws (for example, import or product-safety regimes, which the text notes in its references to the Act). While this instrument addresses technical air-interface requirements for addressable devices, parties must also ensure they meet any adjoining statutory obligations that apply to manufacturers, importers or carriage service providers under other parts of the Act or other Commonwealth law.

• The instrument’s saving clauses and transition rules mean timing across multiple legal instruments matters. Devices manufactured or imported under prior regimes are treated differently; the effect is that actors must coordinate compliance strategies across the timelines of Communications Alliance publications, the repeal date of the old standard (s 4), and the commencement date of this standard (s 2).

In summary, this technical standard interacts with the Telecommunications Act and Communications Alliance standards in a tightly integrated way: the Act provides legal authority, definitions and enforcement context; Communications Alliance documents supply the technical substance; and the standard prescribes how both operate together in time to determine whether a specific device complies.

The document itself records a focused history consisting of replacement and incorporation events rather than multiple successive amendments. The instrument establishes the 2022 standard and records relationships to the earlier standards and dates.

Key historical steps recorded in the instrument

• Repeal of the 2018 standard. Section 4 expressly repeals the Telecommunications (Mobile Equipment Air Interface) Technical Standard 2018 (F2018L01727). That action is the immediate structural change effected by the 2022 instrument.

• Making and dating of the 2022 standard. The instrument is dated 8 December 2022 and states it was made by members of ACMA (cover page and s 3). It commences at the start of 22 December 2022 (s 2). Those are the operative enactment and commencement dates the instrument uses to define temporal application.

• Incorporation of AS/CA S042.1:2022, S042.4:2022 and S042.5:2022. The instrument names specific Communications Alliance standards as the applicable industry standards in relation to an item (s 8). It specifies publication dates for each standard in the definitions in s 6 and notes the publication dates used in the transitional provisions (for example, AS/CA S042.1:2022 was first published 8 March 2022; AS/CA S042.4:2022 first published 5 December 2022; AS/CA S042.5:2022 first published 8 March 2022 with an amendment reissued 4 May 2022).

• Recognition of earlier AS/CA versions for transitional treatment. Part 4 defines historical standards that are relevant for transitional treatment: AS/CA S042.1:2020 and AS/CA S042.4:2018 are identified for savings and transitional applications (s 16). Sections 17 and 18 set out the conditions under which items with relevant dates before or during a 12-month window are taken to comply by reference to those earlier versions.

• Transition regime for future amendments and replacements. Section 9 captures the approach for future amending instruments or replacement standards prepared by Communications Alliance Ltd: a default 12-month transition period starting on the publication date, or a longer period if the amending or replacement standard specifies one, capped at 24 months. This is the mechanism the standard sets for future amendments.

What the instrument does not record

• The standard does not record any subsequent amendments to itself; the text provided contains no schedule of later amendments or revocations beyond the repeal of the 2018 standard and the inclusion of particular AS/CA publications. Any further amendment history would be recorded in later legislative instruments or in the Federal Register of Legislation, but such subsequent entries are not contained in this instrument.

• There is no recorded list of modifications to the AS/CA standards beyond the specified publication dates; the standard instructs compliance with the applicable industry standard as it exists on the relevant date or with replacement standards as existing on their publication date (s 15). For future amendments to the AS/CA standards, the instrument’s s 9 sets the temporal mechanism for transition rather than recording amendments in the instrument itself.

Practical implications arising from the recorded history

• Time-limited reliance on earlier standards. Part 4’s identification of AS/CA S042.1:2020 and AS/CA S042.4:2018 as operative references for certain items provides a concrete transition path for devices whose relevant date occurred before commencement (s 17) or during the 12-month window following commencement (s 18). Those provisions function as a de facto amnesty for stock and deployed devices that complied with the previous requirements.

• The instrument’s link to Communications Alliance publication dates creates a tight coupling between industry standard publication history and legal compliance. The specified publication dates for the 2022 AS/CA parts are important milestones for interpreting the standard’s temporal application (s 6 definitions and notes; ss 17-18).

Overall, the amendment history contained in this instrument is narrowly focused: it replaces the 2018 technical standard, incorporates the 2022 AS/CA S042 series as the technical benchmarks, and provides saving and transition provisions for earlier standards and for future amendments through the transition-period mechanism in s 9.

The text of the Telecommunications (Mobile Equipment Air Interface) Technical Standard 2022 contains no references to litigation, court challenges, judicial interpretation or case law. The instrument itself does not record any litigation history, and it names no cases.

What can be stated from the instrument

• No litigation is recorded in the instrument. There are no statutory notes or footnotes that reference judicial proceedings about the instrument, its predecessors, or the incorporated Communications Alliance standards.

• Implementation or enforcement history would be external to the document. Any disputes, judicial review actions or enforcement proceedings concerning the 2022 standard, the 2018 standard it repealed, or the associated AS/CA standards would be matters recorded in court records, tribunal files or ACMA administrative records, none of which are included in this instrument.

Implications for legal research and risk assessment

• If you require litigation history, consult external sources. Because the instrument contains none, researchers or advisers who require information on legal challenges to ACMA standards, to Communications Alliance standards, or to related enforcement actions must consult case law databases, judicial registries, ACMA public determinations, or the Federal Register of Legislation for any subsequent judicial decisions or administrative appeals.

• Absence of litigation in the instrument does not imply absence of legal risk. The lack of recorded litigation in the standard simply reflects that the instrument does not document such matters; parties should still consider the legal framework in the Telecommunications Act and be alert to administrative or judicial processes that could arise from enforcement or industry disputes.

In short, the instrument itself contains no litigation history; any relevant litigation records will be external and should be located through dedicated legal and administrative registries.

The text contains several detailed drafting features that create practical compliance pitfalls and nuance that can trip up manufacturers, importers, device managers, carriers and advisers. These are not policy critiques but operationally important features, all grounded in the instrument’s text.

1. Manufacturer includes modifier; modified item definition is broad (s 6). The instrument states that “manufacturer, in relation to an item, includes (but is not limited to) a person who modifies the item” and that a modified item includes modifications made by or on behalf of the manufacturer or importer after manufacture or importation, with software updates given as an example. A small software patch pushed post-sale could change the relevant date (s 11) and thus change which version of the applicable industry standard applies. Parties that perform remote updates may become, or act as, manufacturers for the purposes of this standard.

2. Relevant date is the date of modification for modified items (s 11-12). Because the relevant date for a modified item is the date the modification is made (s 11), a software update or hardware retrofit may move an item into a different compliance regime. This affects spare-part strategies, firmware update policies and over-the-air management approaches.

3. Class-of-items rules require identity across the class and same manufacturer/importer (s 10, s 15(3)). To rely on the “original item” compliance route, the items must be identical and have the same manufacturer or importer (s 10), and modifications must not be material (s 15(4)). Proof of identity and chain of custody will therefore be critical. Slight variations in component sourcing, firmware configurations or variants intended for different markets could prevent class-based reliance.

4. Materiality test is fact-bound and defined in the text (s 15(4) note). The instrument defines a material modification as one that “would or could reasonably be expected to affect whether the relevant item would comply with the same version of the standard with which the original item… has complied”. This is a forward-looking, objective test and can be contested in enforcement contexts. Determining materiality may require technical testing or engineering assessment.

5. Timing and publication dates drive compliance options (s 15, s 9). The standard ties compliance to the item’s relevant date and to Communications Alliance publication dates. A compliance choice during a transition period can be made between multiple versions of a standard (s 15(2)), but only within the transition period defined in s 9, which is a default 12 months or a longer period specified by the amending/replacement instrument up to 24 months. Failure to track publication dates and amending instruments could leave a party incorrectly assuming it qualifies for a transitional option.

6. Optionality for 5G items during transitional treatment (ss 17-18 notes). The notes to ss 17-18 state that if an item is an IMT item that uses 5G technology, the item may, but is not required to, comply with AS/CA S042.5:2022 during transitional windows. This creates asymmetry compared to 3G/4G parts where the relevant S042.4 versions are treated as required in some transitional contexts (ss 17-18). Parties with 5G devices should not presume S042.5 compliance is mandatory in all transitional cases.

7. The instrument does not specify enforcement mechanics or penalties (Penalties and enforcement). Because penalties and enforcement are matters of the Act, regulated parties must consult the Telecommunications Act 1997 for sanctions and ACMA processes. This separation can obscure the immediate practical risk profile for non-compliance in the standard itself.

8. References to Act definitions require cross-referencing (s 6 notes). Many key terms used in the standard,carriage service, public mobile telecommunications service, emergency call service, facility, import, manufacturer/importer,are defined in the Act (s 6 notes). Interpreting the standard requires consulting those Act sections, which may create friction for non-legal personnel attempting to assess compliance.

9. Repeal of the 2018 standard and savings interplay (s 4, Part 4). The instrument repeals the prior standard and then specifies which earlier standards or versions are available for items with relevant dates before certain thresholds (Part 4). Mistaking the pre-commencement saving for a blanket grandfathering provision could be costly; the savings are specific and vary with the exact relevant date and the nature of the item (ss 17-19).

10. Communications Alliance publication control. The technical detail in the AS/CA documents is not contained in the instrument; compliance is therefore dependent on external standards prepared by Communications Alliance Ltd (s 8 and notes). This puts a significant regulatory control point in an industry body: publication content and timing determine legal compliance paths. Parties must obtain and understand the particular AS/CA documents and their amendments.

Mitigation focus areas

• Maintain tight records of manufacture/import dates and modification dates (ss 11-12). These determine which version of a standard applies.

• Map device populations to class definitions and document identity, manufacturer/importer commonality, and materiality assessments (ss 10, 15(3)-(4)).

• Treat software-update governance as a regulatory lever: if you push updates that could be material, understand that the update may reset the item’s relevant date and hence the applicable standard (s 6 definition of modified item; s 11).

• Monitor Communications Alliance publications and maintain a transition calendar to know when publication dates create or close transitional options (s 9).

These are practical, source-grounded “gotchas” that arise directly from the instrument’s drafting choices and the centrality of dates, class definitions, modification rules, and incorporation by reference of external technical standards.

A compliance plan should be structured around the instrument’s core mechanics: determining whether a device is in scope, identifying the applicable industry standard and version, mapping relevant dates, managing modifications and classes, and documenting evidence. Below are specific, grounded steps tied to the statutory text.

1. Determine whether the device is an “item” regulated by the standard (s 13)

   • Confirm the thing is customer equipment as defined in the Act (note to s 6).
   • Confirm the device is designed or intended for use with a public mobile telecommunications service or a satellite service (s 13(a)).
   • Confirm the device is an addressable device, meaning it enables a carriage service provider to identify the device when used for two-way communications on a public mobile telecommunications service or satellite service (s 6 definition of addressable device). If any of these elements is absent, the instrument does not apply.

2. Identify the applicable industry standards for the item (s 8)

   • In all cases, arrange to obtain and read AS/CA S042.1:2022 (Part 1: General) because it is applicable in all cases (s 8(a)).
   • If the item is an IMT item using 3G/4G technology (per s 6 definitions), obtain AS/CA S042.4:2022 (s 8(b)).
   • If the item is an IMT item using 5G technology, obtain AS/CA S042.5:2022 (s 8(c)). Note the transitional optionality explained in Part 4 (s 17 note, s 18 note).

3. Establish the relevant date for each item (ss 11-12)

   • For original items, the relevant date is the date the item was manufactured in Australia or imported (s 12(a)).
   • For modified items, the relevant date is the date the modified item is made (s 11; s 12(b)). Ensure change management and software update processes capture this date and the identity of the modifier.

4. Decide which version of the applicable standard applies (s 15)

   • If the relevant date is before a replacement standard’s publication date, comply with the applicable industry standard as it existed on the relevant date (s 15(1)).
   • If the applicable industry standard is amended or replaced and the relevant date falls during the transition period, you may comply with the standard as it existed immediately before publication, the amended standard as at publication, or the replacement standard as at publication (s 15(2)). Plan for this choice within transition-period timelines (s 9).
   • If the item is included in a class where the original item complies, rely on that original item to establish compliance for the class (s 15(3)). If modifications are non-material, you may still rely on class compliance (s 15(4)).

5. Manage modifications and software updates carefully (s 6, s 11, s 15(4))

   • Treat post-sale software updates as modifications for regulatory purposes. If you or a third party modifies devices, recognise that the modifier may be treated as a manufacturer (s 6).
   • Before issuing an update, perform a materiality assessment against the applicable standard. If the modification could reasonably affect compliance with the same version of the standard, it is material and will alter compliance reliance (s 15(4) note).

6. Use class-based pathways where possible (s 10, s 15(3))

   • Group identical devices produced or imported by the same manufacturer/importer as classes. Keep documentary evidence establishing identity, production/import sequence and that the original item of the class met the applicable standard.
   • For modified classes, ensure the original modified item is identifiable and that further modified items meet the non-material modification test where reliance is appropriate (s 10(2), s 15(4)).

7. Exploit transition and savings windows where applicable (s 9, Part 4)

   • If an applicable industry standard is amended or replaced, consult the amending instrument or replacement standard to determine the transition period (s 9). Default is 12 months; the amending instrument can specify a longer period up to 24 months.
   • For items with relevant dates before commencement (22 December 2022) or during the first 12 months from commencement, consult Part 4 (ss 17-18) to determine whether the item is taken to comply by reference to the old technical standard or earlier AS/CA versions.

8. Keep documentary evidence and traceability (ss 11-12, s 15)

   • Maintain records of manufacture/import dates, modification dates, firmware/software versions, conformity test reports, and chain-of-custody documentation showing that devices are identical when relying on class compliance.
   • Keep copies of the specific version of the AS/CA standard used for compliance and evidence of which version was in force on the relevant date or publication date relied upon (s 15).

9. Monitor Communications Alliance publications and ACMA notices (s 9, s 7)

   • Regularly review Communications Alliance Ltd’s website and subscribe to publication alerts to know publication dates and amending instruments that trigger transition periods (s 9).
   • Monitor ACMA communications for any administrative guidance, notices or further legislative instruments that may clarify applicability or interpretive issues (s 7 reference to legislative instruments “as in force from time to time”).

10. Coordinate with carriage service providers where necessary (s 5)

• Because the standard is aimed at protecting network integrity and ensuring emergency-call access and interoperability (s 5), engage carriage service providers where necessary to confirm network-plugging or provisioning requirements, and to confirm that a device’s technical profile is acceptable for enrolment on public mobile or satellite services.

11. Legal review and cross-reference to the Act

• Because many terms and the enforcement framework are located in the Telecommunications Act 1997, consult the Act for definitions (see s 6 notes referencing the Act) and for enforcement provisions that may apply to non-compliance. Legal advice can help map the standard’s substantive duties to any sanctions or reporting requirements in the Act.

12. Consider product-lifecycle controls

• Align product release schedules, software update windows, and import/manufacture timing with the transitional rules to prevent inadvertent exposure to stricter standard versions.
• For legacy stock, document reliance on Part 4 savings (ss 17-19) and maintain segregation of stock that is compliant only under prior standards.

Applying these steps will structure a compliance programme that mirrors the instrument’s date-driven, version-specific and class-aware architecture. The focus must be on date capture, publication monitoring, modification governance, class identity evidence and maintaining copies of the precise AS/CA versions relied upon.