SPN - Services and Protocols for Networks

The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. It is foreseen that regular maintenance of the present document is required. As such, release management requirements will be defined. Before accepting any new common parameter, the present document will provide a set of requirements the parameter has to comply to in order to become a common parameter.

The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4].
For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9].
For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.

The present document defines Product Specific Requirements for Life Cycle Assessment (LCA) of Smartphones so that it is possible to compare the LCA between different smartphone models on SKU level (e.g. considering different memory configurations). The present document provides a methodology for evaluating the environmental impact of smartphones objectively and transparently and is based upon the Life Cycle Assessment (LCA) framework standardized in ETSI ES 203 199 [1] and IEC 63366 [i.1]. The purpose of the present document is to:• Provide smartphone-specific requirements, i.e. Product Specific Rules (PSR), in addition to those of ETSI ES 203 199 [1] and IEC 63366 [i.1] to ensure comparability of LCA studies of smartphones on SKU level. • Harmonize the LCAs of smartphones. • Increase the transparency and facilitate the interpretation of LCA studies of smartphones. • Facilitate the communication of LCA studies of smartphones on SKU level. The present document is valid for all types of smartphones. Moreover, the present document defines a set of requirements for which the LCA practitioners will comply. Comparisons of results from LCA studies of smartphones which belong to the same product family, including assessments which have been performed by different organizations, are within the scope of the present document.

The present document specifies the accessibility requirements applicable to ICT products and services, together with a description of the test procedures and evaluation methodology for each accessibility requirement.
The present document is intended for use by designers, developers, evaluators, manufacturers, market surveillance entities, procurers, researchers, and anyone else interested in the accessibility of ICT products and services.
The present document is not intended to apply to assistive technologies that are designed specifically for use by people with disabilities, except for requirement 11.5.2.4 that requires assistive technologies to use the documented platform accessibility services, although making assistive technologies usable and applicable for people with multiple disabilities is desirable. The requirements do apply to the launch of assistive technologies since that is a function of the platform, not the assistive technology.
The present document supports the implementation of Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies [i.27], and of Directive (EU) 2019/882 on the accessibility of ICT products and services [i.29]. The coverage of the essential requirements of these Directives is given in Annexes ZA and ZB.
The present document contains the necessary accessibility 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 defines classes of environmental conditions and their severities to which telecommunication equipment may be exposed. The severities specified are those which will have a low probability of being exceeded; generally less than 1 % of the operating time in a year. The present document applies to equipment mounted for stationary use including periods of erection work, down time, maintenance and repair at weatherprotected locations defined in clause 5.

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 purpose of the present document is to define a class of environmental conditions and their severities to which equipment may be exposed. Only severe conditions, which may be harmful to the equipment, are included. The severities specified are those which will have a low probability of being exceeded; generally less than 1 % of the operating time in a year. The present document applies to equipment mounted for stationary use including periods of erection work, down time, maintenance and repair at non-weatherprotected locations defined in clause 5.

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 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 can 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.

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 Regulation (EU) No 910/2014 [i.9] and the 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 the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.

The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. It is foreseen that regular maintenance of the present document is required. As such, release management requirements will be defined. Before accepting any new common parameter, the present document will provide a set of requirements the parameter has to comply to in order to become a common parameter.

The present document specifies technical characteristics and methods of measurements applicable to radio equipment used in MultiPoint (MP) Digital Fixed Radio Systems (DFRS) designed for use in the following sub-ranges (see note 2):
• 30 MHz to 1 GHz.
• 1 GHz to 3 GHz.
• 3 GHz to 11 GHz.
• 24,25 GHz to 29,5 GHz.
• 31,0 GHz to 33,4 GHz.
• 40,5 GHz to 43,5 GHz.
NOTE 1: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU [i.1] is given in Annex A.
NOTE 2: For more information on the applicable frequency bands, refer to Annex F.
The present document is applicable to multipoint radio system equipment using any arbitrary access method. It applies to all equipment composing the MP systems, i.e. to Central Station (CS), Terminal Station (TS) and Repeater Station (RS). Time Division Duplex (TDD) or Frequency Division Duplex (FDD or H-FDD) can be used on an equivalent basis. Equipment are classified according to one set of Equipment Classification (EqC) (summarized in clause C.4). The EqC set of the equipment under assessment is indicated in the technical documentation (see note 3). Equipment not fitting any of the set of EqC provided by Annex C are not in the scope of the present document.
NOTE 3: See definition in clause 3.2.
Equipment providing undetachable antennas or providing active antennas (eventually requiring radiated test procedures) are not in the scope of the present document (see note 4).
NOTE 4: Rationale is that even if antenna characteristics are not relevant for access to radio spectrum of MP fixed radio systems (see technical description in ETSI TR 101 506 [i.6]), the essential equipment parameters are defined at antenna port and their radiated test procedures are not available. For information, the most common types of antennas are standardized in Part 3 of this multi-part
deliverable [i.2]. Systems referring to an EqC with "H" code (see clause C.2.2) as Primary Equipment Classification (PET), implementing an actual FH-CDMA access method with frequency hopping period exceeding 400 ms, are not considered within the scope of the present document. Applications intended for offering in the bands 3,4 GHz to 3,8 GHz the option of Nomadic Wireless Access (NWA), according to the NWA definition in Recommendation ITU-R F.1399 [i.14], are not considered in the scope of the present document.

The present document aims at further simplifying end-user access to ICT devices, services, and applications by providing recommended terms for basic and commonly-used ICT-related objects and activities, notably those terms that end users are commonly exposed to. Recommended terms are provided in 27 languages: Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Icelandic , Irish, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Rhaeto Romance, Romanian, Slovak, Slovenian, Spanish, and Swedish (as spoken in their respective European countries).
The recommended terms apply to mobile ICT devices and mobile applications (whether they are standalone or provide access to related services) commonly found in mobile ICT devices. Though developed in a mobile ICT context, most of the recommended terms are applicable to both mobile and fixed-network devices, services, and applications. The recommended terms are applicable to the User Interface (UI) design for a product as well as that of any user documentation accompanying it.
User requirements and, when available, industry-originated documents as well as results of previous standardization work have been considered and integrated in the present document, providing implementation-oriented guidance. Wherever possible, a Design-for-All approach has been adopted, taking functional abilities of users, including elderly users and users with cognitive, physical, or sensory limitations into account.
The present document provides recommendations for terms that may be used by those who consider supporting the languages addressed in future products and services. It does not provide design guidance, nor does it intend to restrict the ability of market players to further improve and develop their devices and services. Neither does it intend to limit their options to trademark user interface elements or profile the user experience of brand-specific user interface implementations as a competitive edge.

The quality of background noise transmission is an important factor, which significantly contributes to the perceived overall quality of speech. Both existing and, even more notably, the new generation of terminals, networks and system configurations, including broadband services, can be greatly improved when designed properly, with consideration and presence of background noise. The present document:
• describes a noise simulation environment using realistic background noise scenarios for laboratory use;
• contains a database including the relevant background noise samples for subjective and objective evaluation.
The present document provides information about the recording techniques needed for background noise recordings and discusses the advantages and drawbacks of existing methods. Additionally, the present document describes the requirements for laboratory conditions. The loudspeaker setup and the loudspeaker calibration and equalization procedure are described. The simulation environment specified can be used for the evaluation and optimization of terminals and of complex configurations including terminals, networks and other configurations. The main application areas should be: office, home and car environment. The setup and database as described in the present document are applicable for:
• Objective performance evaluation of terminals in different (simulated) background noise environments.
• Speech processing evaluation by using the pre-processed speech signal in the presence of background noise, recorded by a terminal.
• Subjective evaluation of terminals by performing conversational tests, specific double talk tests or talking and listening tests in the presence of background noise.
• Subjective evaluation in third party listening tests by recording the speech samples of terminals in the presence of background noise.

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.
The present document aims to support the requirements on NIS2 Directive [i.13] and addresses the general requirements for security management and cybersecurity of trust services (qualified and non-qualified).
NOTE: See ETSI EN 319 403-1 [i.2] for details about requirements for conformity assessment bodies assessing Trust Service Providers.

The present document defines baseline security requirements for AI models and systems. The present document includes in its scope systems that incorporate deep neural networks, such as generative AI. For consistency, the term "AI systems" is used throughout the present document when framing the scope of provisions and the term "AI security", which is considered a subset of cybersecurity, is used when addressing any cybersecurity issues in the scope of the provisions. The present document is not designed for academics who are creating and testing AI systems only for research purposes (AI systems which are not going to be deployed).

The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks.
The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.

The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3]. The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [1].

The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. It is foreseen that regular maintenance of the present document is required. As such, release management requirements will be defined. Before accepting any new common parameter, the present document will provide a set of requirements the parameter has to comply to in order to become a common parameter.

The present document is based on requirements from ETSI TS 102 656 [i.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 addresses the accessibility of ETSI deliverables for users with physical and/or cognitive disabilities. It contains recommendations that are based on the consultation of different sources: expert judgement for the identification of improvements that are easily implemented and that can immediately improve the accessibility of ETSI deliverables, the consultation of authors of ETSI deliverables with a focus on their requirements related to the creation of content for accessible deliverables, and the consultation of users of ETSI deliverables who have physical and/or cognitive disabilities. The results of the analysis take the form of a comprehensive set of recommendations and guidelines to ensure accessible and usable ETSI deliverables, including recommendations for the needed modifications of the ETSI publication processes and specifications of most suitable tools for publication. For this task, short-term, mid-term and, long-term perspectives have been adopted, ranging from immediate changes to a strategic outlook of a future publication environment of ETSI deliverables.

DES/ATTM-0020013

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [8]) 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 applies to Battery unit and Battery Systems with integrated control and monitoring for telecommunication and datacom (ICT) equipment. It applies to battery systems with a dedicated monitoring and control unit.
The present document defines:
• Monitored and controlled battery system architectures.
• The minimum set of exchanged information required at the interface, described in "natural language" in text tables. Battery autonomous protective circuitry without communication, self protection.

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 is based on requirements from ETSI TS 102 656 [i.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 the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.

The present document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The present document includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets. The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1 [2].

The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications. Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use. It is encouraged to use the present document in the development of new specifications. It is foreseen that regular maintenance of the present document is required. As such, release management requirements will be defined. Before accepting any new common parameter, the present document will provide a set of requirements the parameter has to comply to in order to become a common parameter.

The present document specifies Lawful Interception for an Access Provider that has access to layer 2 session information and that is not required to have layer 3 information. In this case, the focus of Lawful Interception (LI) for IP Network Access is on the portion of the network, commonly referred to as "layer 2 interception", that facilitates subscriber access to the Public IP network. The present document describes the LI at the interception domain of the access network. The present document contains:
• a stage 1 description of the Lawful Interception service;
• a stage 2 description of the information flows between the functional entities (including the information elements involved) and triggering events; and
• a stage 3 description of the protocol and procedures to be used in mapping from stage 2 information flows and elements to Intercept Related Information (IRI) and Content of Communication (CC). The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2].
NOTE 1: Layer 3 interception is described in ETSI TS 102 232-3 [12].
NOTE 2: Layer 2 interception is not applicable to the PS domain of the GSM/UMTS networks (3GPP TS 23.060 [15]).

The present document gives guidelines for hosting accessible ETSI meetings on ETSI premises, those of ETSI members, or in public environments (e.g. conference centres). It proposes changes to the meeting registration procedure on the ETSI portal allowing participants to register accessibility requirements. It provides a resource collection that links to the most pertinent existing sign language interpreter databases and additionally includes a collection of recommended tools for speech-to-text tools and services, to help make meetings accessible for deaf and hard-of-hearing participants. It further includes a comparison of accessibility features of available meeting tools, recommendations for tool selection, an evaluation of the accessibility of joint editing and presentation tools and related recommendations for ETSI and for meeting hosts.

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 and guidelines for this package in combination with other packages is outside the scope of the present document

The present document provides detailed functional, service and accessibility requirements from the Human Factors perspective for the implementation of and compliance with the European Accessibility Act [i.27] which requires the provision of interoperable total conversation services wherever voice and video communication is available. It details how to provide an interoperable total conversation service, with voice, real-time text and sign language-supportive video communication media synchronized, as a context-optimized service, with no need for additional pre-registration. It also details viable fall-back options. Effective wireless coupling to hearing technologies, with the avoidance of interferences with assistive devices, and beyond, is also addressed. The necessary background information and specifications containing technical parameters is provided as informative annexes to the present document. The present document additionally provides guidance on how to implement the interoperable total conversation services for emergency communications so that the needs of all users, including people with disabilities, are met. As such the present document complements other standards developed in the area, such as EN 301 549 [1] and ETSI TS 101 470 [29].

The present document defines measurement and monitoring of power, energy and environmental parameters for ICT equipment in telecommunications or data centre or customer premises. It defines the power, energy and environmental parameters monitoring interface of ICT equipment based on generic ETSI ES 202 336-1 [1] interface so that correlations can be made with ICT equipment parameters (traffic, flowrate, number of connected lines, radio setting, QoS KPI, etc.) in the Network Management System (NMS). Correlations of monitored data (power, energy consumption and environmental values) with other ICT equipment functional parameters and settings are not in the scope of the present document. The monitoring interface covers:
• Internal power consumption measurement on the ICT equipment powered in DC and AC.
• Power consumption measurement external to the ICT equipment (if not implemented internally, e.g. legacy equipment).
• Energy metering based on power consumption measurement.
• Environmental parameters of the ICT equipment (e.g. temperature at air inlet of equipment).
The present document defines:
• The minimum set of exchanged information required at the interface, including parameters such as measurement type (e.g. RMS), accuracy, range, etc. and settings such as data acquisition and transmission period, etc. This includes the data preparation, recording and transmission functions.
• The testing method of some parameters and functions.
Text tables in annexes A and B with data exchange described in "natural language"

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 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 [3] or Recommendation ITU-T L.1200 [i.13] will be considered as the standards in force for power facilities, together with IEEE 802.3 [i.18] (PoE).

The present document specifies the concrete textual syntax of the Test Description Language (TDL). The intended use of the present document is to serve as the basis for the development of textual 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 ® and OCL™ are the trademarks of Object Management Group (OMG). Xtext™ is
trademark of the Eclipse ® Foundation. 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 architecture for the execution environment of TDL test descriptions and functional requirements for the components in the form of function declarations that will be provided by an implementation of the components and data types used as input and output parameters of the functions. The test executor component will interpret the elements of test descriptions according to operational semantics specified in [1]. The present document will be used for developing a code generator or interpreter for mapping abstract TDL constructs to code and the required test environment components that are specific to a chosen test execution platform.

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 specifies policy and security requirements relating to the operation and management practices of TSPs issuing time-stamps. These policy requirements are applicable to TSPs issuing time-stamps. Such time-stamps can be used in support of digital signatures or for any application requiring to prove that a datum existed before a particular time. The present document can be used by independent bodies as the basis for confirming that a TSP can be trusted for issuing time-stamps. The present document does not specify protocols used to access the TSUs.
NOTE 1: A time-stamping protocol is defined in IETF RFC 3161 [i.2] including optional update in IETF RFC 5816 [i.3] and profiled in ETSI EN 319 422 [5].
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 2: See ETSI EN 319 403-1 [i.9] for guidance on assessment of TSP's processes and services.
NOTE 3: The present document references ETSI EN 319 401 [4] for general policy requirements common to all classes of TSP's services.

The present document specifies technical characteristics and methods of measurements for Point-to-point (P-P) Digital Fixed Radio Systems (DFRS) operating in frequency bands allocated to Fixed Service (FS) from 1 GHz to 174,8 GHz, corresponding to the appropriate frequency bands from 1,4 GHz to 174,8 GHz as described in relevant annexes B through L. Systems in the scope of the present document are generally intended to operate in full Frequency Division Duplex (FDD) and cover also unidirectional links applications. Time Division Duplex (TDD) applications, when possibly applicable in a specific band, are explicitly mentioned as appropriate in the relevant annexes B through L. Other possible prescriptions, limitations and requirements, for operation in specific bands are also explicitly mentioned, as appropriate, in the relevant annexes B through L. Systems in the scope of the present document are intended to operate only in combination with directive fixed gain antennas respecting the technical requirements in ETSI EN 302 217-4 [6]. Systems in the scope of the present document may be composed by equipment without antennas (see informative annex Q for background) or equipment including integral (but physically detachable) or dedicated antenna. Systems including integral antennas physically undetachable from the radio equipment are not in the scope of the present document (see note 1).
NOTE 1: For additional information, the rationale is that the present document as well as ETSI EN 301 126-1 [1] (radio equipment parameters testing) do not provide radiated test methods and ETSI EN 301 126-3-1 [2] (antenna parameters testing) does not provide test methods for undetachable antennas; future revisions could fill this vacancy.
NOTE 2: The relationship between the present document and the essential requirements of article 3.2 of Directive 2014/53/EU [i.1] is given in annex A.

The present document defines the characteristics and requirements of antennas for point-to-point radio equipment operating in the frequency range from 1 GHz to 174,8 GHz falling within the scope (see note) of ETSI EN 302 217-2 [i.2].
For technical commonalities that range is here divided into sub-ranges as follows:
Range 0: 1 GHz to 3 GHz;
Range 1: 3 GHz to 14 GHz;
Range 2: 14 GHz to 20 GHz;
Range 3: 20 GHz to 24 GHz;
Range 4: 24 GHz to 30 GHz;
Range 5: 30 GHz to 47 GHz;
Range 6: 47 GHz to 71 GHz;
Range 7: 71 GHz to 86 GHz;
Range 8: 92 GHz to 114,25 GHz;
Range 9: 130 GHz to 174,8 GHz.
The present document is applicable to fixed radio equipment with integral (see note) or dedicated antennas.
NOTE: For information, ETSI EN 302 217-2 [i.2] includes in its scope only the use of detachable integral antennas; undetachable integral antennas are not considered due to the present lack of radiated test procedures for the radio equipment parameters.
The present document also applies to stand-alone antennas, placed separately on the market. In this case the present document is to be used by radio equipment manufacturers to provide guidance as to the information for the user, as required by article 10 paragraph 8 of Directive 2014/53/EU [i.1], regarding the antenna characteristics required so as the radio equipment, supplied without antenna, can operate as intended in its technical documentation. The present document is applicable to fixed beam antennas, as well as to "self-alignment tracking" antenna, with limited tracking range, so that all requirements in the present document are respected throughout the tracking angle indicated in the technical documentation. The main body of the present document specifies the characteristics that define the various antenna classes, whilst the annexes provide additional information that is useful to both antenna manufacturers and user/installers.

The present document applies to monitoring and control of Infrastructure Environment i.e. power, cooling and building environment systems for telecommunication centres and access network locations; also, the monitoring of energy and environmental parameters: Power Energy Environmental (PEE) parameters for ICT equipment in telecommunications sites or datacenter or customer premises are considered. Interoperability of heterogeneous management interfaces and systems with multi-vendor equipment is the key issue. The present document gives a general approach from equipment to management system. The multi-part deliverable is composed of a generic core part (the present document) and several specific parts for equipment category.
The present document defines:
• The site equipment maps and its division in functional subsets e.g. DC system which introduces following parts of this multi-part deliverable.
• The generic set of exchanged information required at the interface of equipment, which is instanced for each equipment covered by following parts of this multi-part deliverable.
• The minimum requirement for network architecture allowing some compatibility with old existing interface and the mechanism to exchange data between network elements.
• The data interface protocol for remote or local site management (Machine to Machine Interface MMI) and Human Machine Interface HMI for monitoring and controlling.
• Recommendations for a management network such as dependability, data back-up, data coherence and synchronization all along the management network, response time, fault detection and partial service in case of failure.
• The Measurement accuracy of Power, Energy and Environmental Parameters (PEE).

The present document defines multiple profiles for PAdES digital signatures which are digital signatures embedded within a PDF file.
The present document contains a profile for the use of PDF signatures, as described in ISO 32000-2 [1] and based on CMS digital signatures [i.6], that enables greater interoperability for PDF signatures by providing additional restrictions beyond those of ISO 32000-2 [1]. This first profile is not related to ETSI EN 319 142-1 [4].
The present document also contains a second set of profiles that extend the scope of the profile in ETSI EN 319 142-1 [4], while keeping some features that enhance interoperability of PAdES signatures. These profiles define three levels of PAdES extended signatures addressing incremental requirements to maintain the validity of the
signatures over the long term, in a way that a certain level always addresses all the requirements addressed at levels that are below it. These PAdES extended signatures offer a higher degree of optionality than the PAdES baseline signatures specified in ETSI EN 319 142-1 [4]. The present document also defines a third profile for usage of an arbitrary XML document signed with XAdES signatures that is embedded within a PDF file. The profiles defined in the present document provide equivalent requirements to profiles found in ETSI TS 102 778 [i.10]. Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in ETSI EN 319 102-1 [i.11]. Guidance on creation, augmentation and validation of PAdES digital signatures including the usage of the different attributes is provided in ETSI TR 119 100 [i.9]. The present document does not repeat the base requirements of the referenced standards, but instead aims to maximize interoperability of digital signatures in various business areas.

The present document applies to Digital Fixed Radio Systems (DFRS) in point-to-point operation with integral and external antennas in the frequency range of 1 GHz to 86 GHz corresponding to the appropriate frequency bands 1,4 GHz to 86 GHz as described in ETSI EN 302 217-2 [16], annex B to annex L. The present document summarizes:
• all characteristics, principles and, of utmost importance, terms and definitions that are common to all P-P equipment and antennas and its consultation is necessary when using all other parts of ETSI EN 302 217 series;
• all system-dependent requirements for Point-to-Point (P-P) equipment. These requirements are introduced in two different clauses sub-sets:
- Main requirements are requirements that are also related to the "essential requirements" under article 3.2 of Directive 2014/53/EU [i.1] and further detailed in the Harmonised Standard ETSI EN 302 217-2 [16].
- Complementary requirements are requirements that are not related to essential requirements under article 3.2 of Directive 2014/53/EU [i.1]. Nevertheless they have been commonly agreed for proper system operation and deployment when specific deployment conditions or compatibility requirements are present. Compliance to all or some of these requirements is left to manufacturer decision.
Health and safety requirements and EMC conditions and requirements (articles 3.1a and 3.1b of Directive 2014/53/EU [i.1]), as well as other special conditions and requirements (articles 3.3(a) to 3.3(i) of Directive 2014/53/EU [i.1]) are not considered in the ETSI EN 302 217 series.

The present document details standardized procedures for conformance test of radio interface parameters for Point to Point (PP) equipment used for Digital Fixed Radio Systems (DFRS). Three sets of procedures (for ER, OR and CP) are considered in the scope of the present document:
• Procedures for radio parameters relevant to Essential Requirements (ER) and Optional Requirements (OR), relevant to article 3.2 of Directive 2014/53/EU [i.1]. Requirements for these parameters are detailed in ETSI EN 302 217-2 [9].
• Procedures for Complementary Requirements (CP) that, even if not considered "essential" in the light of article 3.2 of Directive 2014/53/EU [i.1], are considered important for the operations of PP equipment. These parameters are detailed in clause 8 of ETSI EN 302 217-1 [8].
The present document is mainly intended to be applied in conjunction with the above equipment relevant standards and will enable commonality of test results, irrespective of the body carrying out the test. However, the present document can be used also in conjunction with other DFRS relevant standards that would refer to the parameters and test methods hereby described. The conformance tests described in the present document are those related to radio specific parameters required directly by the radio equipment relevant standards at antenna ports in conducted test methods. Conformance tests to other boundary standards (e.g. those for system input/output interfaces (i.e. set at X/X' interface, shown in figure 2, and related baseband process) are outside the scope of the present document. Also, tests described in the present document are not applicable to radio equipment with integral antenna of undetachable antenna type requiring radiated test methods.

The present document is based upon benchmark for server Energy Efficiency (EE) tool for general and heterogeneous servers [i.6].
The present document specifies:
1) test conditions and product configuration for the assessment of EE of heterogeneous servers using reliable, accurate and reproducible measurement methods;
2) an EE metric to support procurement requirements;
3) requirements for equipment to perform the measurements and analysis;
4) requirements for the measurement process;
5) requirements for the management of the EE metric calculation;
6) operation or run rules to configure, execute, and monitor the testing;
7) documentation and reporting requirements.
The metrics and methods apply to heterogeneous servers with various configurations, including type and count of APAs, CPU, memory, storage and any other add-on hardware expected to be present when deployed.
NOTE: Products whose feature set and intended operation are not addressed by active mode testing parameters are excluded from this evaluation method.

The present document defines a dictionary of parameters that are commonly used in multiple TC LI specifications.
Aside from defining a dictionary, the present document aims to provide technical means for other specifications to use.
It is encouraged to use the present document in the development of new specifications.
It is foreseen that regular maintenance of the present document is required. As such, release management requirements
will be defined.
Before accepting any new common parameter, the present document will provide a set of requirements the parameter
has to comply to in order to become a common parameter.

The present document is based on requirements from ETSI TS 102 656 [i.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 the general aspects of HI2 and HI3 interfaces for handover via IP based networks.
The present document:
• specifies the modular approach used for specifying IP based handover interfaces;
• specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively;
• specifies protocols for the transfer of IRI and CC across the handover interfaces;
• specifies protocol profiles for the handover interface.
The present document is designed to be used where appropriate in conjunction with other deliverables that define the
service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI
TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI
TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns
with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI
TS 101 331 [i.9] and ETSI TR 101 944 [i.4].
For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override
or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4].
For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document
and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.