3 Standards writing

3.1 Telecommunications environment

When developing a Standard or revising an existing Standard, consideration needs to be given to any potential impact from current or anticipated industry developments. Examples of areas that a Working Committee may need to take into account include:

  • addressing requirements for customer equipment that use analogue/TDM technologies (sometimes referred to as ‘legacy’) and those that use packet/cell technologies (either as discrete or hybrid equipment).
  • consideration of the impact of emerging services on the scope and relevance of the Standard.
  • recognition of the impact of carrier network transformations and the evolution of networks on customer equipment, for example the National Broadband Network (NBN).
  • consideration of specific characteristics of access technologies for wireless (e.g. cellular, BWA) and wireline (e.g. PSTN, DSL, fibre, BPL).
  • network intelligence moving out into the customer equipment.
  • evaluate requirements in a Standard that relate to network services provided by a C/CSP that may have or are to be withdrawn.

3.2 International

 

INTERNATIONAL ALIGNMENT

The World Trade Organisation’s Technical Barriers to Trade Agreement (TBT) contains a Code of Good Practice which includes a number of provisions on the standardising body, including that Standards ‘are not prepared, adopted or applied with a view to, or with the effect of, creating unnecessary obstacles to international trade’.

National variations are to be kept to a minimum recognising a country’s right to adopt Standards which are considered appropriate, for example, for the protection of the environment or to meet other consumer interests.

INTERNATIONAL ACTIVITIES

Communications Alliance recognises that Standards Australia is the Australian member of the International Organization for Standardisation (ISO) and the International Electrotechnical Commission (IEC). Participation in the standardisation activities of these two bodies shall be through Standards Australia.

Participation by Communications Alliance in other international standardisation activities is the responsibility of Communications Alliance. Where Communications Alliance participates in IEC or ISO activities, we comply with the appropriate Standards Development and Accreditation Committee (SDAC) procedures and any necessary directions from Standards Australia’s International Development Manager.


3.3 Telecommunications regimes in other countries

When considering Standards (international, regional or national) that have been developed by overseas standardisation organisations, the following factors need to be taken into account to determine the relevancy of the Standard to Australian conditions and regulatory framework:

  • the regulatory framework that the Standard has been developed to be applied under. See also Referencing Standards.
  • the reason for the development of the Standard. The history of the Standard may help explain the rationale of the existence of the Standard.
  • how the Standard is called up under regulations.
  • the compliance processes that would apply in Australia (including testing, certification, labelling) to equipment required to comply with the Standard.

3.4 Costs and benefits

Potential impacts to both the industry and to consumers (intentional and unintentional) arising from new or modified requirements need to be identified and examined. Examples include:

  • imposts or delays for manufacturers and importers.
  • additional compliance costs and testing.
  • delays or barriers to market entry.
  • risks to telecommunication networks (e.g. safety, quality of service (QoS), reliability, bushfires, earthquakes).
  • increased prices for consumers (it may be necessary to adopt requirements that provided increased benefits for consumers but may add to industry's burden and/or increase prices for consumers).

3.5 Future proofing Standards

Requirements in Standards are to be drafted in a manner to minimise technology-dependency without limiting innovation. Best practice in standards writing favour performance-based outcomes rather than design or descriptive characteristics of the device.


3.6 Mandatory versus voluntary provisions

When considering mandatory requirements for Standards to be called up under the Telecommunications Act 1997, Working Committees need to consider implications on suppliers (e.g. manufacturing imposts, restrictions of trade, international alignment), test laboratories (e.g. testability, costs of testing) and users (e.g. increase in costs of products).

Within the Terms of Reference, mandatory provisions in Standards, whether newly introduced requirements or existing requirements (in the case of a revision), are to be assessed against the relevant section of the Act.

NOTE:  Many of the current Standards have their origins in earlier documents that were developed for the PSTN and at a time when mandatory requirements were seen to be wider than the present ‘Heads of Power’ requirements. Existing requirements should also be examined as to their ongoing suitability against these Principles.

The relevant sections of the Act are referenced in Regulatory. Specifically for:

  • Customer Equipment Standards - assessed against the four ‘Heads of Power’ of section 376 (2) of the Act.
  • Disability Standards - assessed against section 380 (1) of the Act.
  • Standards for cabling work – which are legislated under the Telecommunications Cabling Provider Rules 2000 and Telecommunications (Types of Cabling Work) Declaration 1997 which are in turn legislated under section 421 and 419 of the Act.

In addition to the provisions of the Act, which always take precedence, the requirements in Standards (both mandatory and voluntary requirements) need to be assessed by the Working Committees and Working Groups against the features listed below.

Information that is non-mandatory (e.g. recommendations, guidelines or voluntary clauses) can be included in Standards. In providing this type of information in a Standard that is to be mandated, information along the following can be considered:

  • recommendations that are above the minimum requirements of the Standard.
  • guidance that is best practice.
  • design guidance.
  • providing context for existing mandatory requirements.

Consideration should also be given to developing a separate Guideline or a voluntary Standard instead of incorporating the text in the Standard itself.

Feature list

The following list of features provides guidance for Working Groups and Working Committees when considering the features or characteristics that may be included in a Standard.

This is not a definitive list, as there will be entries that are not applicable to all devices or all Standards and there may be additional items not listed which need to be considered.

a) Acoustic interface parameters

For pluggable devices such as headsets and earbuds, the distinction needs to be made whether the test is applied at the socket of the device where it is plugged in or incorporates the transducer(s).

  • Send Loudness Ratings (SLR)
  • Receive Loudness Ratings (RLR)
  • Maximum Sound Pressure Level (SPL)
  • acoustic shock
  • frequency response

b) Emergency call access parameters

  • key entry characteristics
  • dialling under lock conditions
  • a one-touch emergency call button
  • screen display messages, including when roaming (camp on)

c) Network interface parameters (network integrity)

When considering requirements for a network interface, the need to have a Customer Equipment Standard has to be determined, taking into account the current Australian regulatory framework, Australian telecommunications carriers/operators and overseas standardisation developments.

Current network interfaces include:

  • Public Switched Telephone Network (PSTN)
  • Integrated Services Digital Network (ISDN)
  • Large Megabit Bearer (LMB)
  • Public Mobile Telecommunications Network (PMTS) (e.g. GSM, CDMA, 3G, LTE)
  • Wireless (e.g. satellite, Broadband Wireless Access (BWA), WiFi)
  • National Broadband Network (NBN)

d) Safety Parameters

When considering how safety requirements are to be addressed, the most appropriate safety Standards need to be identified. Generally, the national equipment safety Standard AS/NZS 60950.1 contains all necessary requirements but it is also necessary to ensure that all the safety requirements are covered by this Standard. Additional safety requirements may need to be considered.

Safety requirements are to address personal safety. They do not intentionally address equipment protection.

AS/NZS 60950.1 addresses the following equipment hazards:

  • electric shock
  • energy related hazards
  • fire
  • heat related
  • mechanical
  • radiation (includes sonic (acoustic), RF, infra-red, ultraviolet, ionizing and high intensity visible and coherent light (lasers))
  • chemical (e.g. contact or inhalation of vapours/fumes)

AS/NZS 60950.1 does not currently address the follow hazard:

  • acoustic (i.e. safety in relation to the levels of audio signals delivered through an ear piece or headset)

e) Tactile interface parameters

Examples for consideration may include:

  • tactile indicators on keypads (also referred to as the ‘pip’)
  • button pressure
  • button size
  • colour
  • response (tactile or audible)

f) Visual interface parameters

Examples for consideration may include:

  • screen brightness
  • font type and size
  • resolution
  • flicker
  • colour

g) Cabling installation Standards

Examples for consideration may include:

  • separation of services (SELV, ELV, LV, LV telecommunications and HV).
  • earthing integrity (cable sizes, equipotential bonding, type of earthing system e.g. CES or TRC).
  • cable product appropriateness and integrity (e.g. indoor/outdoor use, conduits).
  • sectors of industry to which the standard applies (any cabling that is used, installed ready for use or intended for use on the customer side of the boundary of a telecommunications network) includes, for example, all ‘smart wiring’ in residential premises.
  • special provisions for some sectors of industry that may need to be included into the standard (e.g. LV telecommunications definition for public address systems, BMS, mining SWA cables).
  • explosive areas (e.g. such as paint manufacturing buildings).
  • Earth Potential Rise (EPR) zones (where there are HV transformers on or near the premises).
  • Low Frequency Induction (LFI) effects on customer cabling.
  • interference from other services sharing the same cable sheath with telecommunications circuits (e.g. such as nurse call, bells, buzzers, fire circuits, passive infra-red circuits).
  • sharing of infrastructure (e.g. power poles, ducts, cable trays)
  • co-locating with non-communications infrastructure (sub ducting or using electrical conduits).
  • carrier requirements (network boundary locations, clearances around network boundary devices, cabling interfaces).
  • prohibited locations of Main Distribution Frames or outlets (e.g. EPR zones, toilets, boiler rooms, fire escapes, damp areas).
  • Over-voltage protection of customer cabling and customer equipment (cabler installed SPDs and equipment SPDs).

3.7 Device configuration

In developing requirements for customer equipment that may be user-configured or user-installed (including software configuration), consideration needs to be given to ensure that the requirements address those features that the user can alter from the state when it was tested.

For example, are warning notices/labels required when users are downloading software updates or when users are modifying settings?


3.8 Referencing Standards

Introduction

The Interpretative Guidelines in Section 1 of Communications Alliance Standards provides guidance on how Standards are referenced within these Standards. All mandatory referenced Standards are listed in Section 3 References in each Standard. Mandatory referenced Standards are identified by version, typically by year of publication.

Voluntary referenced Standards and other voluntary documents (e.g. Guidelines) are generally listed in Section 3 References to provide a complete listing of all referenced documents in the Standard but it is optional for these voluntary documents to be listed. Voluntary references do not need to be identified by version but often are where a specific edition needs to be cited. Further guidance on dating references is provided in Dated or Undated References.

When considering how requirements are to be included in a Communications Alliance Standard and whether the Standard is to reference other publications, the following decision process is to be followed:

  1. Whether there is a need to reference a publication.
  2. What publications are to be referenced.
  3. How to reference a publication (including style, mandating and dating).

Deciding whether to reference a publication in a Communications Alliance Standard

Working Committees need to take into account the objectives of the World Trade Organisation’s Technical Barriers to Trade Agreement when considering whether to reference international (and internationally recognised) Standards or to develop nationally based requirements.

When referencing an international Standard (or other publication under consideration), consideration should be given as to whether or not there are sufficient resources and expertise available to the Working Committee in order to satisfactorily and accurately determine and identify that the requirements of the Standard are applicable and suitable for mandating under regulation in Australia.

At the end of the project, Working Committees are required to provide a report that includes a justification of any deviations from international/overseas Standards or Australian Standards (AS and AS/NZS) when a Standard is to be recommended for adoption under regulation by the ACMA.

Deciding on what publications to reference in a Communications Alliance Standard

In reviewing a publication for referencing in a Communications Alliance Standard, the following factors to be taken in account to determine the relevancy of the publication to Australian conditions and within our regulatory framework:

  • the nature of the regulatory framework the publication has been developed to be applied under and how the publication has been called up under those regulations.
  • the reason for the publication’s development. The history of the publication may help explain the rationale for its existence.
  • the compliance processes that would apply in Australia (including testing, certification and labelling) to equipment if the referenced publication has been mandated in the Communications Alliance Standard.
  • any impact to the industry and consumers (e.g. costs, delays, barriers to entry, risks to networks).
  • Differences in the nature of regulatory environments should be taken into account. For example, it should be noted that European regulation is ‘principles’ based whereas in Australia, the regulatory framework is ‘requirements’ based.

In many cases Standards developed for application under European regulations would be acceptable for application as mandated requirements via Australian regulations calling up Communications Alliance Standards. There will however be cases where the mandating in Australia of requirements of publications developed for application in the European ‘principles’ based regulatory environment would not be appropriate.

NOTE 1: The European ‘principles’ based regulations direct that an item must comply with the principles set out in the legislation (e.g. EU Directive), not necessarily with the specific or relevant requirements in applicable standards. Furthermore, in some cases the item may quite legitimately comply with the principles of the regulation when, in fact, the item may fail to comply with a specific section/clause of relevant standards.

NOTE 2: The Australian ‘requirements’ based regulations specify that the only way to comply with the regulations is to comply with the applicable standards, or other applicable arrangements, prescribed in the legislation.

How to reference Standards and other publications

a) Referencing style

When considering how to reference Standards and other publications in a Communications Alliance Standard, the following approach is to be adopted:

  • as the first option, reference the entire publication.
  • as the second option, reference a specific requirement (or requirements) of the publication.
  • as the last option, reproduce the relevant requirement (or requirements) in the Communications Alliance Standard.

Further guidance can be found in the Standards Australia Standardisation Guide SG-001 on ‘Preparing Standards’ and in the IEC/ISO Directives – 5th Edition, Part 2 Clause 6.6.7.5 on References to other Documents.

Referencing entire publications

When referencing another publication, it is recommended that the publication in its entirety be referenced. This is in recognition that the scope of the publication and often other parts of the publication need to be taken into account when considering a specific requirement or provision in that publication.

Care must be taken to avoid prescribing a mandatory reference to an entire publication that has voluntary or recommendatory clauses and thereby inadvertently mandating clauses that may be untestable.

Referencing specific requirements of publications

It is recognised that in certain situations referencing the entire publication (e.g. an ETSI Standard or ITU-T Recommendation) may not be the most appropriate method. For example where the referenced publication is large and the specific requirement of interest forms only a small part of the referenced publication.

In this case, the reference can be to a specific requirement of the publication, for example, a clause, a section, a table, a figure or an appendix. When referencing specific parts, the following needs to be taken into account:

  • to avoid taking the referenced requirement out of context where it may be dependent on other parts within the referenced publication.
  • to review the terminology used, specifically the defined terms, to avoid any confusion or ambiguity with unfamiliar or foreign terms.
  • to avoid referencing clause numbers as they may be subject to change in subsequent editions of referenced documents. Ideally the title of the referenced clause is to be cited.

Alternatively, referencing the ‘applicable requirements’ of a Standard places the onus of identifying the relevant applicable requirements on the user of the Standard and their professional judgment. Although this is a typical technique used to avoid undue referencing of multiple requirements, by reducing the specificity of the reference, the potential for the misapplication of requirements, either intentionally or unintentionally, increases. It is recommended that the technique of referencing ‘applicable requirements’ is to be only used in cases where the risk of introducing ambiguity in the requirements is not increased.

Reproducing requirements in publications

It is recognised that in certain situations referencing a publication or part of a publication may not be the most appropriate mechanism for including a specific requirement in a Communications Alliance Standard and that reproducing the requirement may have more utility.

Although reproducing parts of publications in Communications Alliance Standards is not recommended as the preferred approach, if the Working Committee is considering this approach, the following needs to be taken into account:

  • the trade-offs in reproducing the information from the source publication rather that referencing it (e.g. the benefits in readability and utility of the Standard versus increasing the length and the risk of introducing errors and inconsistencies in the Standard).
  • the likelihood that the information may change in the sourced publication. This may potentially lead to misalignment of requirements and add to Standards development costs down the track.
  • copyright considerations of the sourced publication.

b) Mandatory versus voluntary references

When prescribing mandatory requirements via a reference to another publication, typically a Standard, the requirements in that Standard need to be assessed against the regulatory and compliance framework where that Standard is applied.

Requirements specified via mandatory references must be prescriptive and testable. The requirements should not be ambiguous and should be enforceable. This is in recognition that the compliance of customer equipment under current legislation is based upon meeting all the mandatory requirements of the relevant Standards called up under the Telecommunications Labelling Notice.

The publication being considered to be referenced may not be appropriate to mandate in Australia because it may be that the publication was developed as a voluntary or guidance type publication without any intention for it to be mandated under regulation.

c) Dated or undated references

Standards Australia, the IEC and the ISO all allow the use of ‘undated’ and ‘dated’ references for both normative and informative references. It is recognised that because of the nature of Communications Alliance Standards and the fact that they are usually mandated by regulation it is most likely that ‘dated’ references will be the most appropriate however, it should also be recognised that in some instances it will be appropriate to use ‘undated’ references. Both ‘undated’ and ‘dated’ references can be to either the whole document or a specific requirement of that document.

Where the reference is to a Standard listed in the Telecommunications Labelling (Customer Equipment and Customer Cabling) Notice 2001 (the TLN) and the reference is not to a specific clause number in that Standard, then the reference should be undated. This approach takes into account that the version of the Standard listed in the TLN would take precedence. A statement in the ‘Interpretative Guidelines’ section at the front of the Standard is to be inserted to reflect this approach.

As this approach was introduced in 2011, future reviews of Standards should take into consideration these types of references, in particular references to the AS/NZS 60950 safety Standard.

The use of undated references needs to be assessed for the benefits (i.e. not having to update references as the referenced publications are revised) against the possible risks (future revisions of the referenced publication introducing unwanted changes). The Working Committee also needs to recognise that the applicability of subsequent editions or amendments of referenced Standards is a matter for determination by the users of the Standard, employing their professional judgement. Users of Communications Alliance Standards should be encouraged to investigate the possibility of applying the most recent editions of the undated reference document(s).

Consideration also needs to be given to the frequency that a referenced document is revised and any implications for references in the Communications Alliance Standard that would prematurely become out-of-date.

Finally, consideration needs to be given to referenced publications in the publications referenced by a Communications Alliance Standard, also referred to as ‘sub-referenced’ publications, to ensure that these sub-referenced publications are appropriate.

In summary, references are to be dated unless it is for:

  • informative references;
  • references to Standards listed in the TLN where the reference is not to a specific clause number; or
  • it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document.

d) Sourcing referenced publications

When referencing a Standard or other publication in a Communications Alliance Standard, consideration needs to be given to its access and availability. Publications from internationally recognised bodies such as the ITU, ETSI and the IEC/ISO are readily sourced and only the publication designation is required to be cited in a Communications Alliance Standard.

If the source of a referenced publication is likely to be not obvious to the user of the Communications Alliance Standard, then the Working Committee should consider providing further information in the References section of the Standard to assist in identifying the source of the referenced publication.


3.9 Network integrity

Introduction

The Telecommunications Act 1997 at s376 empowers the ACMA to make Technical Standards for Customer Equipment (CE) and Customer Cabling (CC) in relation to a restricted list of matters. In particular, it provides for Standards that contain ‘...such requirements as are necessary or convenient for ... protecting the integrity of a telecommunications network or facility’. There is no definition provided in the Act, however an interpretation of the expression is given in the Explanatory Memorandum where it is explained that the basic underlying intention is to protect the networks and facilities from harm from CE or CC.

That is, so the CE or CC does not adversely affect:

  • the switching, signalling, transmission, metering, charging and billing systems and equipment; or
  • the reliability of telecommunications networks or facilities.

While this sets a limit on the ACMA’s standards making powers, the ACMA is expected to also to consider matters that arise from the COAG Guidelines on regulatory Standards and the need to prepare regulatory impact statements which may lead it to decide to exercise its powers to a lesser extent. As a result, Working Committees should not consider technical requirements in isolation and must consider the costs and benefits arising from the requirements they propose.

Because the actual clauses in the Standards are so varied and have a range of impacts, examples of the matters that could be relevant are used. The examples provided may be relevant for a particular Standard and should be evaluated in the context of the Standard to assess whether related requirements are required to protect network integrity.

On this basis, network integrity should be considered in relation to any matter which has the potential to cause harm to a telecommunications network or facility operated by a Carrier or Carriage Service Provider (C/CSP), and in particular adversely affect the:

  • operation of the switches, softswitches, routers, gateways, firewalls, proxy servers and any other associated network equipment.
  • operation of the application servers and any other associated network equipment.
  • operation of the content servers and any other associated network equipment.
  • operation of the metering, charging and billing systems.
  • operation of the service activation, provisioning and assurance systems.
  • operation of any other IT systems and network equipment used in the telecommunications network or facility.
  • operation of the access and transmission network equipment including RF based elements, e.g. base stations, microwave links, satellites.
  • reliability of network cabling, equipment and systems.

From these principles the following examples may be relevant to a particular Standard.

Switching and Signalling Aspects

Switching and signalling aspects which relate to network integrity could include CE signals affecting call charging, network loading, support of complex protocols, such as ISDN, GSM MAP and IP, shared access networks and control of network equipment.

a) Call Charging

Incorrect answer/busy/no charge signals can be incorrectly sent by CE in some circumstances, resulting in incorrect C/CSP charging, directly compromising the C/CSP’s ability to collect revenue and meet standards for accurate call charging and billing.

b) Network Traffic Loading

Excessive bids by CE to establish connections or utilise other network resources have the potential to overload the IT systems and network equipment used in the telecommunications network or facility, resulting in delays for other callers or failure of the telecommunications network or facility affecting all customers connected to that telecommunications network or facility.

c) Keypad Signalling

The layout and alphanumeric designation of keys on a keypad dial may impact on the operation of the telecommunications network or facility. A uniform approach to alphanumeric keypad layout is desirable, however, the key designation for all keypads must be unambiguous.

d) Complex Protocols

Complex protocols such as GSM MAP, IP, ISDN and CCS7, if offered as a customer interface, have the potential to tie up or disrupt switch processor resources if incorrect messages or messages out of expected sequences are received by the telecommunications network or facility. Further, CE may be required to respond to network originated messages and failure to respond appropriately, or to respond within a set period, may also cause difficulties to occur.

e) Shared Access Networks

In mobile networks, hybrid fibre coaxial cable and DSL networks, the customer access network is based on a shared medium. Incorrect operation by CE could potentially adversely affect other users, for example, by disrupting channel allocation or tying up access network resources.

f) Control of Network Equipment

Remote control and monitoring of network equipment is an essential feature of Carrier operations, for example, for fault detection, configuration control and alarm collection. Uncontrolled loop backs of network equipment could disable common equipment and disrupt Carrier initiated loop backs and testing. CE therefore must not be able to send any such control signals into the Carrier's telecommunications network or facility automatically or under operator control.

Transmission Performance Aspects

Transmission aspects which relate to network integrity include cross talk, overload, electrical damage, interfering signals, impedance matching, interference with network systems and ability to perform to specifications.

a) Crosstalk

Signals of excessive magnitude can be coupled into both adjacent cables and also adjacent pairs within the same cable sheath and affect the services of other users. These signals can be speech, data or signalling tones either continuous or intermittent. Therefore signals must be constrained to be within a power level frequency spectrum mask.

b) Overload

Some analogue circuits are sensitive to the magnitude of customer signals. High level signal powers on one channel may cause excessive noise in other channels on the same bearer. Limits may be required until fully digital networks are established. Also, excessive acoustic or electrical coupling between transmit and receive paths may cause a circuit to oscillate. Therefore signals must be constrained to be within a power level frequency spectrum mask.

c) Electrical Damage

Excessive voltages could cause electrical damage to network equipment and must not be sent by CE.

d) Impedance Matching

Impedance mismatches cause reflections of transmitted signals. The reflected signal may cause errors or be detected as echo if the round trip delay on the call is significant. Impedance balance about earth may influence the noise performance of a connection and reduce the reliability of the call set up.

e) Interference with Network Systems

Active transmission systems require electrical or optical signals to be delivered in a defined manner, otherwise transmission failure occurs and alarms are raised and circuits may be automatically busied out, leading to congestion in the telecommunications network or facility and affecting other users.

Customer Cabling and Cabling Components

Impedance, impedance unbalance and crosstalk performance potentially affect network integrity. Characteristics of the cable should be suitable for the purpose of the circuit for example high speed digital signals may be coupled into other circuits in a cable with poor crosstalk performance. Cabling products should not be liable to water entry or corrosion which could affect other services or the reliability of network equipment, for example underground cable should be impervious to water entry and water migration along the core, while connectors, sockets, terminal strips, frames and battery supplies must be adequately plated or protected.

Installed cable and equipment should be suitably located or protected to avoid foreseeable damage that may affect network integrity, for example underground cabling should be installed at a suitable depth or clearly identified to prevent damage during minor excavation or digging such as for cultivation, gardening or laying paths.


3.10 Interoperability

Introduction

Section 376 of the Telecommunications Act 1997 empowers the ACMA to make Technical Standards for Customer Equipment (CE) and Customer Cabling (CC) in relation to a restricted list of matters. In particular, it provides for Standards that contain requirements necessary or convenient for:

  • ensuring that CE can be used to give access to an emergency call service; or
  • ensuring, for the supply of the Standard Telephone Service (STS), the interoperability of CE with a telecommunications network to which the CE is, or is proposed to be, connected.

Section 18 of the Telecommunications Act 1997 provides some guidance on access to emergency call service, in which a person should be able to establish and maintain a call to the emergency service number.

The ACMA is expected to also to consider matters that arise from the Council of Australian Governments (COAG) Guidelines on regulatory Standards and the need to prepare regulatory impact statements which may lead it to decide to exercise its powers to a lesser extent. As a result, Working Committees should not consider technical requirements in isolation and must consider the costs and benefits arising from the requirements they propose.

The following guidelines are intended to assist Communications Alliance Working Committees in determining what matters should be addressed in new or revised Standards the Communications Alliance is to propose to the ACMA.

This guidance should be read in conjunction with the guidance on assessing Network Integrity Items. Note that the guidance on network integrity and on interoperability is neither exhaustive nor exclusive and Working Committees are advised to use them as a reference guide in testing each clause for interoperability or access to emergency service numbers.

Because the actual clauses in the Standards are so varied and have a range of impacts, the use of examples of the matters that could be relevant is the best approach. The examples provided may be relevant for a particular Standard and should be evaluated in the context of the Standard to assess whether related requirements are required to ensure the interoperability of CE for the STS with a telecommunications network or facility operated by a C/CSP or to ensure access to an emergency call service.

A key point to consider is that a simplistic interpretation and application of the expression interoperability with the telecommunications network or facility could be that it only refers to the CE operating with the C/CSP’s network alone. That is, it does not recognise CE at the far end and the need to establish a connection between the two. From the practical viewpoint, it requires end users supplied with the same service being ordinarily able to communicate between each other whether or not the end users are connected to the same network.

Interoperability, for the purpose of the supply of a STS, can be considered to relate to the three phases of:

  • Call set-up;
  • Information transfer; and
  • Call clear-down.

The first and third are aligned with the signalling functions of the CE while the information transfer is primarily dependent on the transmission performance of the CE.

This Guideline also discusses issues concerning equivalent forms of communication for an end user with a disability. The Disability Matters: Access to Communication Technologies for People with Disabilities and Older Australians Industry Guideline (G586:2006) provides assistance for Communications Alliance Reference Panels and Working Committees to meet their responsibilities under the Disability Discrimination Act 1992 and the Telecommunications (Consumer Protection and Service Standards) Act 1999 and to assist Communications Alliance and its Reference Panels and Working Committees to provide equity in access to telecommunications for people with disabilities.

Signalling

a) Line Polarity

Where CE is required to recognise the polarity of the line to identify the condition of the line prior to initiating a call then the response to these conditions may need to be specified e.g. reversal on idle.

b) Looping the line (breaking dial tone)

CE resistance characteristics as a function of time determine the ability of the CE to loop the line. Therefore the network line port voltage-current characteristics may need to be specified for looping the line and throughout the duration of the connection.

c) Dialling

To establish a connection using the STS to a C/CSP’s telecommunications network or facility will require a destination number to be dialled after the line is looped. The characteristics of the dialling process affect the reliability and accuracy of the telecommunications network or facility in recognising the dialled digits and hence setting up the connection. Therefore the decadic, DTMF and MFC signalling characteristics would need to be specified. Similarly to ensure end-to-end interoperability it would seem that the correct reception of dialled digits on an indial circuit would also need to be considered. Possible misoperation by the end-user may also need to be considered, for example poor identification, layout or design of end-user accessible parts or end-user programmable software.

d) Incoming Call Recognition

To establish a connection using the STS to a C/CSP’s telecommunications network or facility, requires the destination CE to be able to recognise that an incoming call is being offered and is available to be answered. For indial circuits, the correct reception of dialled digits may need to be considered. Therefore the CE must be able to:

  • recognise the incoming call state (e.g. ringing on a ring-in loop-out service).
  • indicate to the called party that a call is being offered for answering.
  • apply the correct answering conditions to the line.

e) Clear Down

Although clear down directly relates to network integrity there is also a close link to interoperability as the CE should be able to clear down a connection and establish another connection as required. Therefore, requirements defining the clear down process signalling and the actual loop disconnect process (if used) would need to be considered.

Transmission

a) Send and Receive Loudness ratings

For the user to recognise network tones e.g. dial tone, the receive loudness rating would need to be adequate. To distinguish a specific tone within a range of network tones both the receive loudness rating and the distortion performance would need to be satisfactory. To enable the reliable transfer of information to the other party in a connection, e.g. an emergency service operator, the send loudness rating and the distortion performance of the sending CE must be specified to be within certain limits. To understand the emergency service operator, the receive performance must be satisfactory.

This then suggests that both the send and receive loudness ratings plus at least the send distortion performance should be considered.

b) Distortion

As noted above, distortion limits should apply to the send performance. Distortion limits could also apply to the receive performance however this is more difficult compared with the send performance and is probably not warranted in practice.

c) Noise

The overall information transfer on a connection will be dependent, inter alia, on the loudness loss between the two items of CE and the noise level on the circuit. Therefore consistent with specifying the loudness ratings and distortion, the noise performance on both send and receive would need to be considered.


3.11 Definition of the Standard Telephone Service

Introduction

The following guidance is to assist Working Committees in making decisions as to the application of the Standard Telephone Service (STS) definition to Customer Equipment (CE) Standards. It should be noted that there is an inherent difficulty in doing this:

  • the STS is defined in Section 6 of the Telecommunications (Consumer Protection and Service Standards) Act 1999 and is paraphrased in Clause 6.2; but
  • there is no corresponding definition of a Standard Telephone Instrument.

Many types of CE and interfaces may in fact deliver a voice carriage service. Therefore while this Guideline can point to key considerations it cannot stand in place of the need for the Working Committee to make some assessment or seek external guidance from the CECRP as to whether a given CE is a means of connecting to an STS.

Application of the STS definition to requirements in CE Standards

The STS may be defined as a carriage service for the purpose of voice telephony communication (or an equivalent form of communication for an end user with a disability) between end-users supplied with the same service, whether or not the end users are connected to the same telecommunications network.

NOTE 1: The common equivalent forms of communication are to use data to provide text communication via CE, e.g. TTY, Text Telephone, Modem, TeleBraille. These devices may interface to a carrier’s network using, for example, Baudot, V.21, V.18, EDT, V.23 and CTM. These CE are used by people who may be deaf, hearing impaired, speech impaired, deaf/blind and deaf/visually impaired and may have single or multiple disabilities.

NOTE 2: It is the purpose of the technology, not the technology itself, that is the key point of the application of the STS in providing equivalent service. For example, TTY is used to provide an equivalent service to the STS.

The above definition paraphrases the standard telephone service definition in Section 6 of the Telecommunications (Consumer Protection and Service Standards) Act 1999. Important points to note:

  • the definition covers carriage services which terminate at a Carrier’s network boundary and which are available for interfacing to CE. It does not cover CE interfaced to that service.
  • ‘voice telephony between end users’ implies call set-up and real-time two-way communication.
  • the definition of STS is independent of the technology used by the carrier for the transmission and delivery of the voice signal.
  • the definition of STS in the Telecommunications (Consumer Protection and Service Standards) Act 1999 also covers other forms of communication equivalent to voice telephony for end users with a disability, e.g. to allow people to communicate via methods other than speaking and/or hearing.

Some examples of technologies which may be used to deliver an STS include:

  • analogue transmission within the voice frequency band, e.g. on a twisted pair copper line, 4-wire leased line.
  • digital transmission, e.g. basic access and primary rate ISDN or PCM channels on an E1 link.
  • transmission to/from remote network interface units over various media, e.g. remote switches, remote multiplexers, analogue or digital pair gain, HFC, FTTP, WLL, satellite.

The network interface units will present digital or analogue interfaces as referred to above, at the network boundary.

In Note 2 of Schedule 1 of the Telecommunications Labelling (Customer Equipment and Cabling) Notice 2001 there is an exception to network interoperability for packet based technologies, e.g. ATM. for earlier revisions of some Standards.

Indicating mandatory requirements for CE interfaced with a STS

In each Communications Alliance Standard, in the Interpretative Guidelines Section under the Categories of Requirements clause, the following wording shall be incorporated stating the applicability of requirements to STS:

‘Clauses qualified as applying to ‘STS CE’ or to ‘CE used for the supply of the Standard Telephone Service’, identify requirements that are mandatory only for CE interfaced to an STS as defined by the Telecommunications (Consumer Protection and Service Standards) Act 1999.’

Equivalent CE used to provide an equivalent service to voice telephony to the STS shall be required to meet the above qualification regardless of the technology used.


3.12 Emergency call access

Ensuring that CE can be used to give access to an emergency call is one of the four ACMA’s Heads of Power under s376 of the Telecommunications Act 1997.

Requirements for emergency call access for customer equipment are specified in the following three Standards:

  • AS/ACIF S002 Analogue interworking and non-interference requirements for Customer Equipment for connection to the Public Switched Telephone Network.
  • AS/ACIF S003 Customer Access Equipment for connection to a Telecommunications Network.
  • AS/ACIF S031 Requirements for ISDN Basic Access Interface.
  • AS/ACIF S038 Requirements for ISDN Primary Rate Access Interface.
  • AS/ACIF S042.1 Requirements for connection to an air interface of a Telecommunications Network.
  • AS/CA S043.1 Requirements for Customer Equipment for connection to a metallic local loop interface of a Telecommunications Network - Part 1: General.

In addition the ACMA regulates and monitors the provision of the Emergency Call Services. The ACMA has made determinations placing requirements on C/CSPs and emergency call persons with respect to the Emergency Call Service. This includes obligations on VoIP Service Providers who supply two-way VoIP services and VoIP-out only services that are capable of dialling into the PSTN.


3.13 Health and safety

Protecting the health or safety of persons who operate or work on or use services supplied by means of a telecommunications network or a facility is one of the four ACMA’s Heads of Power under s376 of the Telecommunications Act 1997.

Requirements for health and safety as applied under the Heads of Power to CE are specified in the following Standards:

  • AS/NZS 60950.1 Information technology equipment — Safety — Part 1: General requirements.
  • AS/NZS 4117 Surge Protective Devices for Telecommunications Applications.
  • AS/ACIF S004 Voice frequency performance requirements for Customer Equipment  and AS/CA S042.1 Requirements for connection to an air interface of a Telecommunications Network — Part 1: General (specifically for acoustic safety).
  • AS/CA S008 Requirements for customer cabling products (products within this category are not subject to AS/NZS 60950.1 except for those parts of AS/NZS 60950.1 referenced by S008).
  • AS/ACIF S009 Installation requirements for customer cabling (Wiring rules).

The IEC 62368-1 ed1.0 Audio/video, information and communication technology equipment - Part 1: Safety requirements Standard was published in 2010. The scope of this Standard covers the scopes of the two IEC standards that it is intended to replace in 2015, IEC 60065 Audio, Video and Similar Electronic Apparatus – Safety Requirements and IEC 60950-1. IEC 62368-1 is technology-neutral and performance-based, rather than based on prescribed constructions like the two standards it is replacing. It employs a new form of safety testing, Hazard Based Safety Engineering (HBSE), which evaluates hazards that can be transferred to end users and how technology products safeguard against these potential dangers.

IEC 62368-1 will only become mandatory in Australia when called up under the ACMA’s Telecommunications Labelling Notice. It will eventually address requirements for acoustic safety which are currently under development within the IEC. Until such time the applicable Australian acoustic safety requirements will remain in AS/ACIF S004 and AS/CA S042.1.

Optical fibre safety is currently addressed by the above Standards under Australian telecommunications legislation. In addition, the non-mandatory Standard, AS/NZS 2967 Optical fibre communication systems safety, addresses the following optical fibre equipment considerations:

  • handling, use and disposal of optical fibre materials and associated chemicals
  • testing and use of laser light sources
  • use, installation and operation of an optical fibre cabling system (OFCS)
  • laser warning labels

3.14 Telecommunications Network Boundary

The Telecommunications Network Boundary is defined in the Telecommunications Act 1997 and:

  • is a nominal demarcation point between carrier-owned and customer owned cabling and equipment;
  • determines whether cabling or equipment is subject to ACMA technical regulation; and
  • is a physical boundary and not a service boundary.

Further information and examples of network boundaries can be found in Appendix J of AS/ACIF S009


3.15 Compliance statements

Compliance statements are located after requirement clauses in Section 5 of a Standard. They provide a mechanism by which methodologies are suggested for demonstrating Customer Equipment’s compliance with a particular requirement. The Interpretative Guidelines in Section 1 of every Standard provides guidance on compliance statements.

Compliance statements only suggest methodologies but cannot mandate them. In Clause 6.1, it notes that ‘alternative methods of demonstrating compliance to those described may be used if the risk of passing non-compliant CE is not increased because of increased measurement uncertainty.’

There is no defined format for a compliance statement but typically it will follow the lines of ‘Compliance with Clause 5.x should be checked by using the method described in Clause 6.y and may also refer to an associated Figure if relevant. Alternatively, a compliance statement may be self-contained and detail the method in the statement itself, for example, if it refers to a simple measurement procedure. Where a requirement only requires inspection of the CE in operation, the compliance statement can also be worded to indicate that this is the proposed methodology.

Compliance statements should not refer to record keeping as a methodology for demonstrating compliance, e.g. to test reports, Notified Body (NB) Expert Opinions or a manufacturer’s Declaration of Conformity. Section 408 of the Telecommunications Act 1997 sets out ancillary matters to the requirement to apply a label to CE, including the record keeping requirements to demonstrate compliance with a particular applicable standard. If a Working Committee wishes for particular record keeping requirement to be adopted, this can be included as a recommendation for inclusion in the Telecommunications Labelling Notice (TLN) as a part of the submission sent to the ACMA for the making of the Standard.