SPN - Services and Protocols for Networks

DTS/ESI-0019182-1

RES/MTS-201873-8T3ed481

RES/MTS-202785v181

RES/MTS-202784ed181

RES/MTS-201873-11 v4.9.1

RES/MTS-201873-9v4121

The present document provides an overview of the Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3] based
certificate profiles and the statements for EU Qualified Certificates specified in other parts of ETSI EN 319 412 ([i.4] to
[i.7]). It specifies common data structures that are referenced from other parts of ETSI EN 319 412 ([i.4] to [i.7]).
The profiles specified in this multi-part deliverable aim to support both the Regulation (EU) No 910/2014 [i.9] and use
of certificates in a wider international context. Within the European context, it aims to support both EU Qualified
Certificates and other forms of certificate.

The present document specifies generally applicable policy and security requirements for Trust Service Providers
(TSPs) issuing public key certificates, including trusted web site certificates.
The policy and security requirements are defined in terms of requirements for the issuance, maintenance and life-cycle
management of certificates. These policy and security requirements support several reference certificate policies,
defined in clauses 4 and 5.
A framework for the definition of policy requirements for TSPs issuing certificates in a specific context where
particular requirements apply is defined in clause 7.
The present document covers requirements for CA hierarchies, however this is limited to supporting the policies as
specified in the present document. It does not include requirements for root CAs and intermediate CAs for other
purposes.
The present document is applicable to:
• the general requirements of certification in support of cryptographic mechanisms, including digital signatures
for electronic signatures and seals;
• the general requirements of certification authorities issuing TLS/SSL certificates;
• the general requirements of the use of cryptography for authentication and encryption.
The present document does not specify how the requirements identified can be assessed by an independent party,
including requirements for information to be made available to such independent assessors, or requirements on such
assessors.
NOTE: See ETSI EN 319 403 [i.2] for guidance on assessment of TSP's processes and services. The present
document references ETSI EN 319 401 [8] for general policy requirements common to all classes of
TSP's services.
The present document includes provisions consistent with the requirements from the CA/Browser Forum in EVCG [4]
and BRG [5].

The present document specifies policy and security requirements for the issuance, maintenance and life-cycle
management of EU qualified certificates as defined in Regulation (EU) No 910/2014 [i.1]. These policy and security
requirements support reference certificate policies for the issuance, maintenance and life-cycle management of EU
qualified certificates issued to natural persons (including natural persons associated with a legal person or a website)
and to legal persons (including legal persons associated with a website), respectively.
The present document does not specify how the requirements identified can be assessed by an independent party,
including requirements for information to be made available to such independent assessors, or requirements on such
assessors.
NOTE: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP's processes and services. The present
document references ETSI EN 319 411-1 [2] for general requirements on TSP issuing certificates.

The present document specifies general policy requirements relating to Trust Service Providers (TSPs) that are
independent of the type of TSP. It defines policy requirements on the operation and management practices of TSPs.
Other specifications refine and extend these requirements as applicable to particular forms of TSP. The present
document does not specify how the requirements identified can be assessed by an independent party, including
requirements for information to be made available to such independent assessors, or requirements on such assessors.
NOTE: See ETSI EN 319 403 [i.6] for details about requirements for conformity assessment bodies assessing
Trust Service Providers.

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.

The present document defines the support for object-oriented features in TTCN-3. TTCN-3 can be used for the
specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are
protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module
testing, testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can
be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing.
The specification of test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

The scope of the present document is to present a methodology for specification and testing of RESTful APIs,
i.e. telecommunication interfaces based on the Representational State Transfer paradigm, suitable for application in the
standardization context.
In particular, the present guide is meant to serve ETSI membership and groups in the effort to unify and consolidate the
approaches and practices in current and future standardization activities at ETSI and its Partnership Projects.
The Guide collects the best practices from standardization, industry and research in order to provide a modern and
future-proofed approach to the subject.
The intended audience is primarily standardization groups at ETSI, but the guide may also serve as reference for users
and vendors in industry, with a special focus in Open Source communities.
The Guide recommendations on conventions, methodologies, design-patterns and architectural choices to be used in
standardization of RESTful APIs, specification and execution of standardized conformance and interoperability test
suites.

The present document is based on requirements from ETSI TS 102 656 [2].
The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.
The present document considers both the requesting of retained data and the delivery of the results.
The present document defines an electronic interface. An informative annex describes how this interface may be
adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.

The present document defines power feeding solutions for 5G, converged wireless and wireline access equipment and
network, taking into consideration their enhanced requirements on service availability and reliability, the new
deployment scenarios, together with the environmental impact of the proposed solutions.
The minimum requirements of different solutions including power feeding structures, components, backup, safety
requirements, environmental conditions are also defined.
The present document is applicable to powering of both mobile and fixed access network elements, in particular on
equipment that have similar configurations and needs.
The future development of 5G networks will create a new scenario in which the density of radio cells will increase
considerably, together with the increase of wireline network equipment that are going to be installed in the vicinity to
the users, thereby creating the need to define new solutions for powering that will be environmentally friendly,
sustainable, dependable, smart and visible remotely.
The -48 V DC, up to 400 V DC local and remote power solutions defined respectively in ETSI EN 300 132-2 [2],
ETSI EN 302 099 [i.10] and ETSI EN 300 132-3-1 [3] or Recommendation ITU-T L.1200 [i.13] will be considered as
the standards in force for power facilities, together with IEEE 802.3TM [i.18] (PoE).

The present document is aimed at defining the topology and level of analysis to assess the energy efficiency of mobile
networks. Within the scope of the present document there is the radio access part of the mobile networks, and namely
there are radio base stations, backhauling systems, radio controllers and other infrastructure radio site equipment. The
covered technologies are GSM, UMTS, LTE and 5G New Radio (NR). In particular the present document defines
metrics for mobile network energy efficiency and methods for assessing (and measuring) energy efficiency in
operational networks. The purpose of the present document is to allow better comprehension of networks energy
efficiency, in particular considering the networks' evolution in different periods in time.
Aiming to consider also the slicing approach of the networks from 5G onwards the metrics are extended to the latency
of the network itself related to the energy consumed, additionally to the metrics based on traffic and on coverage,
already existing for legacy networks and still valid.
The present document deals with both a homogeneous and heterogeneous "network" considering a network whose size
and scale could be defined by topologic, geographic or demographic boundaries. For networks defined by topologic
boundaries, a possible example of a network covered by the present document consists of a control node (whenever
applicable), its supported access nodes as well as the related network elements. Networks could be defined by
geographic boundaries, such as city-wide, national or continental networks and could be defined by demographic
boundaries, such as urban or rural networks.
The present document applies to the so-called "partial" networks for which a measurement method is also
recommended. The specification extends the measurements in partial networks to wider so-called "total" networks
energy efficiency estimations (i.e. the network in a geographic area, the network in a whole country, the network of a
MNO, etc.).
Terminal (end-user) equipment is outside the scope of the present document and is not considered in the energy
efficiency measurement.

The present document version covers base stations with the following radio access technologies:
• GSM.
• WCDMA.
• LTE.
• NR.
The methodology described in the present document is to measure base station static power consumption and RF output
power. Within the present document it is referred to as static measurements.
The results based on "static" measurements provide power and energy consumption figures for BS under static load.
Energy consumption of terminal (end-user) equipment is outside the scope of the present document.
The scope of the present document is not to define target values for the BS power and energy consumption.
The results should only be used to assess and compare the power and energy consumption of complete base stations.
Wide Area Base Stations and Medium Range Base Stations (as defined in ETSI TS 125 104 [2], ETSI TS 136 104 [12],
and ETSI TS 138 104 [15]) are covered in the present document.

The present document specifies the functional accessibility requirements applicable to ICT products and services,
together with a description of the test procedures and evaluation methodology for each accessibility requirement in a
form that is suitable for use in public procurement within Europe. The present document is intended to be used with web
based technologies, non-web technologies and hybrids that use both. It covers both software and hardware as well as
services. It is intended for use by both providers and procurers, but it is expected that it will also be of use to many
others as well.
The relationship between the present document and the essential requirements of Directive 2016/2102 on the
accessibility of the websites and mobile applications of public sector bodies [i.28] is given in Annex A.
The present document contains the necessary functional requirements and provides a reference document such that if
procedures are followed by different actors, the results of testing are similar and the interpretation of those results is
clear. The test descriptions and evaluation methodology included in the present document are elaborated to a level of
detail compliant with ISO/IEC 17007:2009 [i.14], so that conformance testing can give conclusive results.

The present document describes the principles for powering of Telecommunications Equipment (TE) in access
networks (both traditional copper based and Next Generation fibre and/or hybrid based) and contains requirements for
the powering systems, laying down:
• the characteristics of the input and output interfaces of the power units; the recommendations for TE power
protection, also regarding network integrity and public services availability requirements;
• the management data, necessary to guarantee the required availability of the network and provided public
services and to ensure the maintenance of the TE power units.
The present document takes into account the innovative characteristics of fibre-based access network equipment, for
which the intrinsic limitation of the local power plants should be considered regarding the equipment installed inside
telecom centre or local exchanges or installed in streets or inside buildings: it goes from "complete integration of the
power plant in the TE" to "remote power feeding from a distant power plant".
The present document provides detailed information in annex A on the improved reliability of public electric power grid
and on the improved reliability and availability of new fibre-based NGA network. It should be considered that, for street
cabinet TE, the local power scenario is common and, in that case, the main power supply availability characteristics are
mainly based on electrical energy provider's performance.
The present document applies to the powering of all equipment of the access network (copper, fibre or radio networks)
located inside or outside telecommunications centres or local exchanges, differentiating the applicable and sustainable
power protection requirements. The access network is defined as the part of the telecommunications network, which
comprises the network termination (passive or active) that is installed inside customer premises and the first exchange
that can be also the broadband local exchange.
As innovative fibre-based and hybrid-based NGA network TE are changing the traditional powering paradigm, the
present document proposes the viable measures to comply with the integrity, availability and uninterrupted
telephone/VoIP provision that European regulatory defines for public networks [i.18].
The present document describes different configurations of powering the TE and the impacts on networks and services
continuity and reliability:
• Local power supply for TE (e.g. street cabinet, active network termination, etc.).
• Remote Feeding to TE from central office through copper access pair.
• Cluster Power supply feeding power for a cluster of TE.
• Remote power feeding to TE from centre or cluster power through a power cable.
• Back feeding or Reverse Powering architecture that can supply power to Access Network Units such as ONU
or ONT or remote DSL unit from the customer premises through its final distribution access copper pair.

The present document specifies test severities and methods for the verification of the required resistibility of equipment
according to the relevant environmental class.
The tests in the present document apply to stationary use of equipment at weatherprotected locations covering the
environmental conditions stated in ETSI EN 300 019-1-3 [1].

The present document specifies an extension of the Test Description Language (TDL) enabling the specification of
structured test objectives. The extension covers the necessary additional constructs in the abstract syntax, their
semantics, as well as the concrete graphical syntactic notation for the added constructs. In addition textual syntax
examples of the TDL Structured Test Objectives extensions as well as BNF rules for a textual syntax for TDL with the
Structured Test Objectives extensions are provided. The intended use of the present document is to serve both as a
foundation for TDL tools implementing support for the specification of structured test objectives, as well as a reference
for end users applying the standardized syntax for the specification of structured test objectives with TDL.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

The present document specifies how the elements of the Test Description Language (TDL) should be mapped to Testing
and Test Control Notation version 3 (TTCN-3) [2]. The intended use of the present document is to serve as the basis for
the development of TDL tools. The meta-model of TDL and the meanings of the meta-classes are described in ETSI
ES 203 119-1 [1].

The present document specifies the concrete graphical syntax of the Test Description Language (TDL). The intended
use of the present document is to serve as the basis for the development of graphical TDL tools and TDL specifications.
The meta-model of TDL and the meanings of the meta-classes are described in ETSI ES 203 119-1 [1].
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

The present document specifies the abstract syntax of the Test Description Language (TDL) in the form of a
meta-model based on the OMG® Meta Object Facility™ (MOF) [1]. It also specifies the semantics of the individual
elements of the TDL meta-model. The intended use of the present document is to serve as the basis for the development
of TDL concrete syntaxes aimed at TDL users and to enable TDL tools such as documentation generators, specification
analysers and code generators.
The specification of concrete syntaxes for TDL is outside the scope of the present document. However, for illustrative
purposes, an example of a possible textual syntax together with its application on some existing ETSI test descriptions
are provided.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

The present document defines extensions to the Test Description Language (TDL) to support the re-use of test
configurations.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

The present document specifies the exchange format of the Test Description Language (TDL) in the form of an XML
Schema derived from the TDL meta-model [1]. The intended use of the present document is to serve as the specification
of the format used for exchange of model instances and tool interoperability between TDL-compliant tools.
NOTE: OMG®, UML®, OCL™ and UTP™ are the trademarks of OMG (Object Management Group). This
information is given for the convenience of users of the present document and does not constitute an
endorsement by ETSI of the products named.

The present document is based on requirements from ETSI TS 102 656 [2].
The present document contains handover requirements and a handover specification for the data that is identified in
national legislations on Retained Data.
The present document considers both the requesting of retained data and the delivery of the results.
The present document defines an electronic interface. An informative annex describes how this interface may be
adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.

The present document specifies requirements on the content of certificates issued to natural persons. This profile builds
on IETF RFC 5280 [1] for generic profiling of Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3].
This profile supports the requirements of EU Qualified Certificates as specified in the Regulation (EU)
No 910/2014 [i.5] as well as other forms of certificate. The scope of the present document is primary limited to
facilitate interoperable processing and display of certificate information. This profile therefore excludes support for
some certificate information content options, which can be perfectly valid in a local context but which are not regarded
as relevant or suitable for use in widely deployed applications.
The present document focuses on requirements on certificate content. Requirements on decoding and processing rules
are limited to aspects required to process certificate content defined in the present document. Further processing
requirements are only specified for cases where it adds information that is necessary for the sake of interoperability.
Certain applications or protocols impose specific requirements on certificate content. The present document is based on
the assumption that these requirements are adequately defined by the respective application or protocol. It is therefore
outside the scope of the present document to specify such application or protocol specific certificate content.

The present document specifies high-level security and data protection provisions for consumer IoT devices that are
connected to network infrastructure (such as the Internet or home network) and their interactions with associated
services. The associated services are out of scope. A non-exhaustive list of examples of consumer IoT devices includes:
• connected children's toys and baby monitors;
• connected smoke detectors, door locks and window sensors;
• IoT gateways, base stations and hubs to which multiple devices connect;
• smart cameras, TVs and speakers;
• wearable health trackers;
• connected home automation and alarm systems, especially their gateways and hubs;
• connected appliances, such as washing machines and fridges; and
• smart home assistants.
Moreover, the present document addresses security considerations specific to constrained devices.
EXAMPLE: Window contact sensors, flood sensors and energy switches are typically constrained devices.
The present document provides basic guidance through examples and explanatory text for organizations involved in the
development and manufacturing of consumer IoT on how to implement those provisions. Table B.1 provides a schema
for the reader to give information about the implementation of the provisions.
Devices that are not consumer IoT devices, for example those that are primarily intended to be used in manufacturing,
healthcare or other industrial applications, are not in scope of the present document.
The present document has been developed primarily to help protect consumers, however, other users of consumer IoT
equally benefit from the implementation of the provisions set out here.
Annex A (informative) of the present document has been included to provide context to clauses 4, 5 and 6 (normative).
Annex A contains examples of device and reference architectures and an example model of device states including data
storage for each state.

The present document provides an overview of the Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3] based certificate profiles and the statements for EU Qualified Certificates specified in other parts of ETSI EN 319 412 ([i.4] to [i.7]). It specifies common data structures that are referenced from other parts of ETSI EN 319 412 ([i.4] to [i.7]).
The profiles specified in this multi-part deliverable aim to support both the Regulation (EU) No 910/2014 [i.9] and use of certificates in a wider international context. Within the European context, it aims to support both EU Qualified Certificates and other forms of certificate.

The present document specifies a certificate profile for certificates issued to legal persons. The profile defined in the
present document builds on requirements defined in ETSI EN 319 412-2 [2].
The present document supports the requirements of EU qualified certificates as specified in the Regulation (EU)
No 910/2014 [i.3] as well as other forms of certificate.

The present document contains requirements for the competence, consistent operation and impartiality of conformity
assessment bodies assessing and certifying the conformity of Trust Service Providers (TSPs) and the trust services they
provide towards defined criteria against which they claim conformance.
NOTE 1: Those requirements are independent of the type and class of trust service provided.
The present document also contains requirements for the conformity assessment of trust services component services,
which later forms part of a separate conformity assessment of a TSP.
NOTE 2: This enables a provider of such component services, which are used as part of the service provided by
several TSPs, to avoid having to be assessed several times, or even for a TSP to provide a service based
just on a component service or collection of components whether or not they are recognized as a trust
service under Regulation (EU) No 910/2014 [i.1].
The present document applies the general requirements of ISO/IEC 17065 [1] to the specific requirements of
conformity assessment of TSPs.
The present document is part 1 of a multi-part deliverable. Other parts include:
• ETSI TS 119 403-2 [i.14]: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity
Assessment; Part 2: Additional requirements for Conformity Assessment Bodies auditing Trust Service
Providers that issue Publicly-Trusted Certificates".
• ETSI TS 119 403-3 [i.15]: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity
Assessment; Part 3: Additional requirements for conformity assessment bodies assessing EU qualified trust
service providers".

The present document is based on requirements from ETSI TS 102 656 [2].
The present document contains handover requirements and a handover specification for the data that is identified in national legislations on Retained Data.
The present document considers both the requesting of retained data and the delivery of the results.
The present document defines an electronic interface. An informative annex describes how this interface may be adapted for manual techniques. Apart from in annex I, the present document does not consider manual techniques.

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

The present document provides speech transmission performance requirements for 8 kHz wideband VoIP loudspeaking and hands-free terminals; it addresses all types of IP based terminals, including wireless, softphones and group audio terminals. DECT terminals are covered in ETSI EN 300 175-8 [i.6] and ETSI EN 300 176-2 [i.7]. In contrast to other standards which define minimum performance requirements it is the intention of the present document to specify terminal equipment requirements which enable manufacturers and service providers to enable good quality end-to-end speech performance as perceived by the user. In addition to basic testing procedures, the present document describes advanced testing procedures taking into account further quality parameters as perceived by the user. NOTE: The present document does not concern headset terminals.

The present document provides speech transmission performance requirements for narrowband VoIP loudspeaking and hands-free terminals; it addresses all types of IP based terminals, including wireless, softphones and group audio terminals. DECT terminals are covered in ETSI EN 300 175-8 [i.6] and ETSI EN 300 176-2 [i.7]. In contrast to other standards which define minimum performance requirements it is the intention of the present document to specify terminal equipment requirements which enable manufacturers and service providers to enable good quality end-to-end speech performance as perceived by the user. In addition to basic testing procedures, the present document describes advanced testing procedures taking into account further quality parameters as perceived by the user. NOTE: The present document does not concern headset terminals.

The present document defines the Advanced Parameterization package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines:
• Value parameters of types.
• Type parameterization.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines types for behaviour definitions in TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

The present document defines the Extended TRI package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language or in its interfaces TRI and TCI, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines a more efficient handling of software values by a version of TRI, that does not use binary encoded messages for the communication with the SUT, but uses the values as they are; meaning e.g. that software objects or serialized data can be passed directly between the SUT and the TE. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

The present document provides speech transmission performance requirements for narrowband and wideband media gateways from a QoS perspective as perceived by the user. Media gateways can be network or home based, they may include a transcoding function. The present document covers the following types of IP-based media gateways:
• ATA (Analogue Terminal Adapter), home gateway IP to POTS
• ITA (ISDN Terminal Adapter), home gateway IP to ISDN
• IAD (Integrated Access device), home router including ATA or ITA
• Network based ATA and ITA
• Carrier grade media gateway, network gateway IP to TDM
• IP-to-IP media gateway, network gateway with transcoding and/or other media processing
• New Generation DECT Fixed part with IP interface (only parameters not covered by New Generation DECT) Interfaces of media gateways used together with terminals as a system (i.e. connected via Ethernet or with a proprietary interface) are excluded in the present document and should be measured according to the relevant terminal standard. If a media gateway includes more than one interface type (e.g. POTS and ISDN), each interface has to be dealt with differently. The requirements available in the present document will ensure a high compatibility with IP- and TDM-based fixed and wireless terminals and networks, including DECT and mobile terminals. It is the aim to optimize interoperability, the listening and talking quality and the conversational performance. Related requirements and test methods are defined in the present document. The present document does not apply to media gateways with 4-wire analogue interfaces. The requirements for MGWs with respect to voiceband data (VBD) are out of scope in the present document. These requirements are covered in ETSI TS 102 929 [i.4].

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control
Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test
system to a particular test platform. The present document defines the interfaces as a set of operations independent of a
target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the
CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present
language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#.
A summary of the IDL-based interface specification is provided in annex A.
NOTE: Java™ is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

The present document defines the support of advance matching of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of OMG CORBA® based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

The present document provides speech transmission performance requirements for 3,4 kHz narrowband VoIP handset and headset terminals; it addresses all types of IP based terminals, including wireless and soft phones. DECT terminals are covered in ETSI EN 300 175-8 [i.6] and ETSI EN 300 176-2 [i.7]. In contrast to other standards which define minimum performance requirements it is the intention of the present document to specify terminal equipment requirements which enable manufacturers and service providers to enable good quality end-to-end speech performance as perceived by the user. In addition to basic testing procedures, the present document describes advanced testing procedures taking into account
further quality parameters as perceived by the user.

The present document proposes an evolved version of the Green Abstraction Layer formulation capable of operating within ETSI NFV environments.

The present document defines the support for object-oriented features in TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of OMG CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2], X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered by the present document.

The present document provides speech transmission performance requirements for 8 kHz wideband VoIP handset and headset terminals; it addresses all types of IP based terminals, including wireless and soft phones. DECT terminals are covered in ETSI EN 300 175-8 [i.9] and ETSI EN 300 176-2 [i.10]. In contrast to other standards which define minimum performance requirements it is the intention of the present document to specify terminal equipment requirements which enable manufacturers and service providers to enable good quality end-to-end speech performance as perceived by the user. In addition to basic testing procedures, the present document describes advanced testing procedures taking into account
further quality parameters as perceived by the user.

The present document defines specific QCStatement for the qcStatements extension as defined in IETF
RFC 3739 [2], clause 3.2.6, including requirements for their use in EU qualified certificates. Some of these
QCStatements can be used for other forms of certificate.
The QCStatements defined in the present document can be used in combination with any certificate profile, either
defined in ETSI EN 319 412-2 [i.2], ETSI EN 319 412-3 [i.5] and ETSI EN 319 412-4 [i.6], or defined elsewhere.
The QCStatements defined in clause 4.3 may be applied to regulatory environments outside the EU. Other
requirements specified in clause 4 are specific to Regulation (EU) No 910/2014 [i.8] but may be adapted for other
regulatory environments.