id stringlengths 7 13 | title stringlengths 26 396 | type stringclasses 2
values | version stringclasses 152
values | url stringlengths 90 98 | scope stringlengths 0 9.03k |
|---|---|---|---|---|---|
104 229 | Publicly Available Specification (PAS); O-RAN R1 interface Test Specification (O-RAN.WG2.TS.R1TS-R004-v03.00) | TS | 3.0.0 | http://www.etsi.org/deliver/etsi_ts/104200_104299/104229/03.00.00_60/ts_104229v030000p.pdf | The present document specifies test cases for conformance testing and interoperability testing of the rApps and R1 services over R1 interface. |
104 230 | Publicly Available Specification (PAS); O-RAN R1 interface Use Cases and Requirements (O-RAN.WG2.TS.R1UCR-R004-v10.00) | TS | 10.0.0 | http://www.etsi.org/deliver/etsi_ts/104200_104299/104230/10.00.00_60/ts_104230v100000p.pdf | The present document specifies the Use cases and Requirements for R1 interface. |
104 231 | Publicly Available Specification (PAS); O-RAN R1 interface Application Protocols for R1 Services (O-RAN.WG2.TS.R1AP-R004-v08.00) | TS | 8.0.0 | http://www.etsi.org/deliver/etsi_ts/104200_104299/104231/08.00.00_60/ts_104231v080000p.pdf | The present document specifies the Application Protocols for R1 Services. |
104 232 | Publicly Available Specification (PAS); O-RAN Type Definitions for R1 Services (O-RAN.WG2.TS.R1TD-R004-v04.01) | TS | 4.1.0 | http://www.etsi.org/deliver/etsi_ts/104200_104299/104232/04.01.00_60/ts_104232v040100p.pdf | The present document specifies the Type Definitions for R1 Services. It is part of a TS-family covering the R1 interface specifications. |
104 233 | Publicly Available Specification (PAS); O-RAN Transport Protocols for R1 Services (O-RAN.WG2.R1TP-R004-v4.03) | TS | 4.3.0 | http://www.etsi.org/deliver/etsi_ts/104200_104299/104233/04.03.00_60/ts_104233v040300p.pdf | The present document specifies the transport protocols for R1 services. |
104 246 | TCCE Security; Application of ETSI CVD process within TCCE | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/104200_104299/104246/01.01.01_60/tr_104246v010101p.pdf | The present document defines the policy of the Technical Committee (TC) Terrestrial Trunked Radio and Critical Communications Evolution (TCCE) in the ETSI Coordinated Vulnerability Disclosure (CVD) [i.1]. This policy is based on the ETSI CVD and applies to ETSI deliverables of the TCCE [i.2] only. The present document is intended for all roles in the ETSI CVD process and provides guidance to: Finder, ETSI CVD Steering Committee, TC TCCE and the rapporteur(s) of the impacted standard(s). It details the process for Finders of potential vulnerabilities, explains the actions of the TC TCCE and may be used as guidance for all roles. For Finders not acquainted with Terrestrial Trunked Radio (TETRA) the present document outlines typical TETRA network environments and explains typical constraints and complexities in vulnerability mitigations. |
104 409 | Data Solutions (DATA); Data Act (art. 33) requirement and references analysis | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/104400_104499/104409/01.01.01_60/tr_104409v010101p.pdf | The present document supports the preparation of the answer to the EU standardisation request "Standardisation request to the European standardisation organisations as regards a European Trusted Data Framework in support of Regulation (EU) 2023/2854 of the European Parliament and of the Council" [i.3] further on called "SReq" in the present document. The scope of the present document is to analyse the requirements contained in the "Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act)" [i.4], further on called "EU Data Act" in the present document, with particular reference to its article 33, and those in the final version of the SReq [i.3] including their references (e.g. the "DSSC Blueprint V1.5" [i.5]). This analysis is conducted with reference to the existing ETSI applicable specifications and standards (e.g. oneM2M [i.6], SAREF [i.1], NGSI-LD [i.7], [i.8], etc.). The present document provides the input for the ETSI Technical Report on "Data ACT (art. 33) standardization suggestions" ETSI TR 104 410 [i.2]. Both reports (the present document and ETSI TR 104 410 [i.2]) will prepare the normative work to satisfy the SReq. The present document is structured as follows: • Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations, which are used in the present document. • Clause 4 provides an introduction to the EU Data Act [i.4] with a focus on its structure and the technically relevant parts of it. Specifically, it establishes the reference to standardisation in the field of interoperability of data and services. Further on, it lists requirements derived from the EU Data Act [i.4] article 33 ("Essential requirements regarding interoperability of data, of data sharing mechanisms and services, as well as of common European data spaces)". The draft of the SReq [i.3] is addressing this article 33. Also, clause 4 provides a list of requirements derived from the EU Data Act [i.4] article 35 (Interoperability of data processing services). It addresses several items, which are related to, even if not being in the focus of, the SReq. • Clause 5 provides an introduction to the SReq to European Standards Organisations as regards to a European Trusted Data Framework [i.3]. The focus is on ontologies and data models as well as on approaches to manage them. It lists requirements derived from the SReq, which are additional to the published EU Data Act [i.4]. Clause 5 provides an overview of the "DSSC Blueprint, version 1.5" [i.5] and an overview of the "Data Catalog Vocabulary (DCAT) - Version 3" [i.9] within the context of potential application to SAREF [i.1]. • Clause 6 provides an overview of which parts of the standardisation requirements derived from the documents EU Data Act [i.4] and SReq [i.3] can be satisfied by the oneM2M standards [i.6], the SAREF ecosystem [i.1] with the SAREF core and on all extensions and the NGSI-LD specifications [i.7], [i.8]. Also it identifies the gaps which need to be filled. It also describes the relationship between oneM2M and SAREF, with special emphasis on how oneM2M standards [i.6] can be used as the means for practical SAREF deployment. Furthermore, clause 6 analyses the relation between DSSC Blueprint [i.5] and the oneM2M standards [i.6]. • Clause 7 provides a summary of conclusions from the requirements and references analysis and gives an outlook to further potential activities. • Annex A provides an overview of the EU Data Act structure. • Annex B shows some highlights of articles with technical/standardisation relevance. |
104 410 | Data Solutions (DATA); Data Act (art. 33) standardization suggestions | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/104400_104499/104410/01.01.01_60/tr_104410v010101p.pdf | The present document supports the preparation of the answer to C(2025)4135 - Standardisation Request M/614 [i.3] further on called "SReq" in the present document. The present document is based on the input from ETSI TR 104 409 [i.1]. Both reports (the present document and ETSI TR 104 409 [i.1]) will prepare the normative work to satisfy the SReq [i.3]. The present document is structured as follows: • Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations, which are used in the present document. • Clause 4 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how oneM2M fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It presents guidelines about how oneM2M can be used to fulfil as much as possible the standardization requirements of these two documents without the need for changes to oneM2M specifications. Additionally, this clause lists potential Change Requests (CRs) that would enable oneM2M to fulfil some of the aspects of these two documents (i.e. ETSI TR 104 409 [i.1] and the present document) that are currently not covered. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make oneM2M compliant with the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. Some requirements of the two documents fall outside the scope of oneM2M specifications. Where possible, this clause provides clarification of such boundaries together with additional guidelines that may help define a clear positioning for oneM2M in the context of the two documents. • Clause 5 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how SAREF fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It lists feasible improvements that would enable SAREF [i.4] to fulfil the standardization requirements of these two documents. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make SAREF compliant with the two documents. Clause 5 provides possible additional guidelines for aligning SAREF with the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. • Clause 6 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how NGSI-LD fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It provides guidelines about how NGSI-LD can be used to fulfil as much as possible the two documents without carrying out changes within the NGSI-LD methodology. Clause 6 lists feasible improvements that would enable NGSI-LD to fulfil the standardization requirements of these two documents. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make NGSI-LD compliant with the EU Data Act [i.2] with particular reference to Article 33 and the EU Standardisation Request, e.g. the definition of the mappings between NGSI-LD and DCAT-AP provided in [i.7]. • Clause 7 provides insights about if the union of the three assets enables the fulfilment of the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. • Clause 8 provides a summary of conclusions from the standardization suggestions. |
105 174-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/10517401/01.02.01_60/ts_10517401v010201p.pdf | The present document gives an overview of this multi-part deliverable covering energy management and broadband deployment. Clause 2 and clause 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Clause 6 describes the network sub-systems applicable to broadband deployment and their interconnections. Clause 7 considers the measures which may be taken to optimize energy management of the end-to-end network and introduces the concept of key performance indicators (KPI) to enable consistent monitoring of energy management for each of the network sub-systems described in clause 5. Clause 8 contains details of the subsequent parts and sub-parts of this multi-part deliverable which, for each of the network sub-systems described in clause 5: • identify the standardization bodies working on the design and installation of the cabling within and between the network sub-systems and the relevant interfaces; • provide a more strategic analysis of energy consumption trends, in a range of different broadband deployment scenarios; • outline further work needed to ensure the improvement of energy efficiency in communication networks. This will enable the proper implementation of services, applications and content using an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for the power distribution systems or physical design of data centres. |
105 174-1-1 | Access and Terminals (AT); Relationship between installations, cabling and communications systems; Standardization work published and in development; Part 1: Overview, common and generic aspects; Sub-part 1: Generalities, common view of the set of documents | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740101/01.01.01_60/tr_1051740101v010101p.pdf | The present document gives an overview of the set of documents relevant for installations, interfaces and cabling for communications infrastructures and studies common and generic aspects. This multi-part deliverable studies the relationship between installations, cabling, their interfaces and other aspects of communications infrastructures. It identifies standardization work published and in development. It also provides guidance for standardization work needed for implementation of communications networks. It is not the goal of this multi-part deliverable to provide detailed standardized solutions. This multi-part deliverable will be used to properly implement services, applications and content on infrastructure. |
105 174-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Lifecycle Resource Management; Part 2: ICT Sites: Implementation of energy and lifecycle management practices | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/10517402/01.03.01_60/ts_10517402v010301p.pdf | ETSI EN 305 174-2 [3] specifies a minimum set of required practices for energy management which are applicable to ICT sites of all sizes and business models. These are taken from a sub-set of those practices recommended by CLC/TR 50600-99-1 [1]. CLC/TR 50600-99-1 [1] also contains a much wider range of recommended practices which are applicable to specific designs of ICT site and may be applied to improve the energy management beyond the minimum requirements of ETSI EN 305 174-2 [3]. The present document: • maps the practices of CLC/TR 50600-99-1 [1] to general application of ETSI EN 305 174-2 [3] and also to the specific design options which may apply in a given ICT site; • details examples of the impact of such practices in relation to reductions in energy consumption or improvements in energy efficiency or management. In addition, the present document addresses the end-of-life and maintenance aspects of WEEE (as in ETSI EN 305 174-8 [4] and ETSI TS 105 174-8 [5]). |
105 174-2-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 2: Network sites; Sub-part 1: Operator sites | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740201/01.01.01_60/tr_1051740201v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency within operator's sites for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 introduces operator sites concepts; • clause 5 details the approaches that may be employed to improve energy efficiency within the areas of the operator site containing network telecommunications equipment; • clause 6 details the approaches that may be employed to improve energy efficiency within the areas of the operator site containing information telecommunications equipment. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for network architecture. The present document focuses on energy efficiency. The CO2 footprint is not taken in account in the present document. |
105 174-2-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 2: Network sites; Sub-part 2: Data centres | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051740202/01.01.01_60/ts_1051740202v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency within operators sites and data centres for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 introduces data centre concepts including those specifically related to network operators; • clause 5 develops the concept of Key Performance Indicators (KPI), introduced in TS 105 174-1 [13], to enable consistent monitoring of energy efficiency; • clause 6 details the approaches that may be employed to improve energy efficiency within the information technology infrastructure; • clause 7 details the approaches that may be employed to improve energy efficiency within the environmental control systems; • clause 8 details the approaches that may be employed to improve energy efficiency via the physical infrastructure of the buildings; • clause 9 details the approaches that may be employed to improve energy efficiency within the power distribution system; • clause 10 provides a summary of energy efficiency approaches within existing data centres; • clause 11 provides a summary of energy efficiency approaches within new data centres and introduces wider issues concerning their location; • clause 12 contains the conformance mechanisms of the present document; • clause 13 contains the recommendations of the present document; • clause 14 introduces future opportunities for improvements of energy efficiency; • annex A provides indications of the first order effect of applying the approaches outlined in clauses 6, 7 and 9. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for network architecture. The present document focuses on energy efficiency. The CO2 footprint is not taken in account in the present document. Two separate aspects of energy efficiency are considered as shown in figure 1: • actions to improve energy efficiency in existing data centres in the short or medium term; • actions to improve energy efficiency in new data centres, in medium or long term. The domains under study are: • in the Information Technology (IT) infrastructure: all aspects of the technical infrastructure in the data centre, including servers, storage arrays, backup libraries and network equipment including routers, switches, etc.; • in the IT operational strategy: all consolidation initiatives, such as virtualization, physical or logical consolidations, usage of specific software and processes; • in the technical environment: all aspects concerning energy usage, cooling and, more generally, all disciplines involved in the technical environment of the data centre. ETSI ETSI TS 105 174-2-2 V1.1.1 (2009-10) 8 Figure 1: Aspects of data centres under consideration |
105 174-4 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 4: Access networks | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/10517404/01.01.01_60/tr_10517404v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency the access networks for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Clause 4 of the present document: • identifies the standardization bodies working on interfaces to, cabling within, installation of, and other aspects of the communication infrastructures of, access networks; • outlines some of the principal access network topographies and their differences in respect of energy consumption; • provides strategic analysis of energy consumption trends within access networks; • develops the concept of Key Performance Indicators (KPI), introduced in Part 1 of this multi-part set of documents, to enable consistent monitoring of energy efficiency; • outlines further work needed to ensure the improvement of energy efficiency in communication networks. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
105 174-4-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 4: Access Networks; Sub-part 1: Fixed access networks (excluding cable) | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051740401/01.02.01_60/ts_1051740401v010201p.pdf | The present document details measures which may be taken to improve the energy efficiency of access networks for broadband deployment. The present document: • identifies the standardization bodies working on diverse aspects of the access networks infrastructures interfaces, cabling, installation, operation, etc.; • outlines some of the principal access network topographies and their differences in respect of energy consumption; • provides strategic analysis of energy consumption trends within access networks. This enables the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
105 174-5-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Lifecycle Resource Management; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant) | TS | 1.4.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051740501/01.04.01_60/ts_1051740501v010401p.pdf | The present document details measures which may be taken to improve the energy efficiency within homes (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions of terms and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within homes (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
105 174-5-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 2: Office premises (single-tenant) | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740502/01.01.01_60/tr_1051740502v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency within office premises (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within office premises (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
105 174-5-4 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 4: Data centres (customer) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051740504/01.01.01_60/ts_1051740504v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency within industrial premises (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in data centres (customer), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within data centres (customer) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
105 174-6 | Integrated broadband cable telecommunication networks (CABLE); Broadband Deployment and Energy Management; Part 6: Cable Access Networks | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/10517406/01.01.01_60/tr_10517406v010101p.pdf | The present document describes the cable access network, and progressive network access architectures that reduce the network energy consumption and the metrics required to benchmark the network and its components to support and enable the proper implementation of services, applications and content on an energy efficient infrastructure and describe measures that may improve the energy efficiency of cable access networks. Within the present document: • clause 4 presents the schematic for cable access network infrastructures, the evolution of the network architectures to meet consumer capacity demand and bandwidth growth and the main components of the cable access network energy consuming elements; • clause 5 presents measurement key performance indicators to baseline and measure network energy performance; • clause 6 explains power consumption metrics of the CAN; • clause 7 describes and gives consideration to power metrics of field deployed access network elements; • clause 8 describes the electrical powering of the CAN components and the distributed usage of the electrical power. This clause explains ways to improve the power consumption and benchmarking the HFC CAN plant; • clause 9 considers the calculations to measure the data throughput of a CAN. |
105 174-7-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Energy Management; Part 7: Digital multiservice cities; Sub-part 1: Multiservice Street Furnitures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051740701/01.01.01_60/ts_1051740701v010101p.pdf | The present document details measures which may be taken to ease the deployment of smart new services and their multiservice street furnitures of digital multiservice city within the IP network of a single city or an association of cities administratively clustered. Furthermore, the suggested measures will enable to engineer a reliable common networking infrastructure which can improve the Total Cost of Ownership (TCO) for the public administration while improving the energy efficiency of the overall deployment. The present document also lists the requirements which have led to this common architecture. Clause 4 identifies and presents a general overview of a city from small entity to significantly large municipality clustering several cities and villages. Clause 5 presents the pursued objectives behind the concept of smart city. Clause 6 describes the general theoretical pillars which bears the engineering requirements to deploy a digital multi service city. Clause 7 identifies the general needs from the cities. Clause 8 of the present document present a suggestion of an engineered digital multiservice city. This will enable the proper introduction and implementation of a new service, application or content within the city digital portfolio on a unified energy efficient network, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
105 174-8 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment and Lifecycle Resource Management; Part 8: Implementation of WEEE practices for ICT equipment during maintenance and at end-of-life | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/10517408/01.02.01_60/ts_10517408v010201p.pdf | The present document supports the requirements of ETSI EN 305 174-8 [9] providing a framework for, and detailing, the necessary implementation procedures. The present document specifically extends the end-of-life aspects of ICT equipment to the treatment of components and sub-assemblies replaced during maintenance procedures. With reference to Figure 2 (from ETSI EN 305 174-8 [9]), which is a schematic representation of the different broadband networks implemented by telecommunications operators, the ICT equipment covered comprises the ITE and NTE in ICT sites together with the Terminal Equipment (TE) and Network Interface Unit (NIU) at the Customer Premises (CP) together with other User Equipment (UE) such as mobile telephones and other devices. Figure 2: Schematic of fixed and mobile communication networks Annex A details all actions in terms of treatment of e-waste, in accordance with the standards, from the perspective of recycler. |
105 175-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s | TS | 2.0.0 | http://www.etsi.org/deliver/etsi_ts/105100_105199/10517501/02.00.00_60/ts_10517501v020000p.pdf | The present document specifies the POF cabling system 100 Mbit/s and 1 Gbit/s for interoperability among different suppliers. The system comprises the active optical elements, the cables, connectors and wall plugs. A future step could be to achieve integration of POF interfaces into end user equipment. |
105 175-1-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibres; Part 1: Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s; Sub-part 1: Application requirements for physical layer specifications for high-speed operations over Plastic Optical Fibres | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051750101/01.01.01_60/ts_1051750101v010101p.pdf | The present document provides a compendium of application requirements for full-duplex 100 Mbit/s and 1 Gbit/s Ethernet based home networking infrastructures based on Plastic Optical Fibre (POF) transmission media. The description of applications covers different network topologies as well as different field particularities. |
105 176-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Ethernet and power over cables; Part 2: Ethernet and power over coaxial cables for IP video surveillance | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/10517602/01.01.01_60/ts_10517602v010101p.pdf | The present document specifies Ethernet & Power over Coax system characteristics in such a way that interoperability issues arising from the connection of several Ethernet & Power over Coax devices in such system are minimized, providing a specification that can be used as the basis for testing and certification. |
105 177 | Access, Terminals, Transmission and Multiplexing (ATTM); Benefit Analysis of Ethernet and power over coaxial cables - IP Video Surveillance Case Studies | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/105177/01.01.01_60/tr_105177v010101p.pdf | The present document reviews the benefit analyses and environmental impact for selected use cases (such as mass transit systems) of using coaxial cables to support both Ethernet and power over coaxial equipment for IP Video Surveillance Systems (VSS) when: a) upgrading existing analogue VSS using legacy coaxial cables as compared with installation of alternative transmission media; and b) building new VSS by installing coaxial cables as compared with other transmission media. |
105 178 | Access, Terminals, Transmission and Multiplexing (ATTM); Comparison of sustainability parameters between internal and external, including "cloud-based", ICT hosting solutions | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/105178/01.01.01_60/tr_105178v010101p.pdf | The present document provides methods to enable a comparison of sustainability parameters between both internal and external (including "cloud-based") ICT hosting solutions addressing: • energy consumption; • Green House Gas (GHG) emission; • water consumption; • treatment of electrical and electronic equipment including maintenance at End of Life (EoL). The present document does not address: • technical aspects of whether a given external hosting solution is able to provide a functional replacement of Users ICT needs; • methods of improving resource management within data centres/ICT sites (reference should be made to ETSI EN 305 174-2 [i.8] and ETSI TS 105 174-2 [i.12]. |
105 200-2-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Operational infrastructures; Implementation of Global KPIs; Part 2: Specific requirements; Sub-part 2: Fixed broadband access networks | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/105200_105299/1052000202/01.03.01_60/ts_1052000202v010301p.pdf | The reporting of Global KPIs in accordance with ETSI EN 305 200-2-2 [2] requires the collection of data to enable the calculation of the following aspects: • Objective KPI relating to task efficiency (KPITE) based on data_volume and total energy consumption (KPIEC). • Objective KPI relating to the use of renewable energy (KPIREN). The present document supports the requirements of ETSI EN 305 200-2-2 [2] providing a framework for, and detailing, the implementation procedures including any necessary techniques for estimation of energy consumption together with clarification and treatment of different types of data volume. |
105 200-2-3 | Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Operational infrastructures; Implementation of Global KPIs; Part 2: Specific requirements; Sub-part 3: Mobile broadband access networks | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/105200_105299/1052000203/01.02.01_60/ts_1052000203v010201p.pdf | The reporting of Global KPIs in accordance with ETSI EN 305 200-2-3 [2] requires the collection of data to enable the calculation of the following aspects: • Objective KPI relating to task efficiency (KPITE) based on data_volume and total energy consumption (KPIEC). • Objective KPI relating to the use of renewable energy (KPIREN). The present document supports the requirements of ETSI EN 305 200-2-3 [2] providing a framework for, and detailing, the implementation procedures including any necessary techniques for estimation of energy consumption together with clarification and treatment of different types of data volume. |
105 200-3-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Energy management; Operational infrastructures; Implementation of Global KPIs; Part 3: ICT Sites; Sub-part 1: DCEM | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/105200_105299/1052000301/01.02.01_60/ts_1052000301v010201p.pdf | The reporting of Global KPIs in accordance with ETSI EN 305 200-3-1 [2] requires the collection of data to enable the calculation of the following aspects: • objective KPI relating to the total energy consumption (KPIEC); • objective KPI relating to the use of energy performance (KPIEP) which combines KPIEC with other measurements of energy consumption to provide Objective KPIs related to task efficiency (KPITE), the reuse of energy (KPIREUSE) and the use of renewable energy (KPIREN). The present document supports the requirements of ETSI EN 305 200-3-1 [2] providing a framework for, and detailing, the implementation procedures including any necessary techniques for estimation of energy consumption together with constants to be employed for weighting and banding purposes. |
105 388 | Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Asymmetric Digital Subscriber Line (ADSL2plus) - European specific requirements [ITU-T Recommendation G.992.5 modified] | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105300_105399/105388/01.01.01_60/ts_105388v010101p.pdf | The present document specifies European requirements for ADSL2plus. The present document endorses ITU-T Recommendation G.992.5 [1] and amendments 1 [2], 2 [3] and 3 [4], the contents of which apply together with the addition of the modifications being covered herein, to the exclusion of annex C of G.992.5. In particular the aspects covered by the present document are related to: 1) Define INP values as mandatory. 2) Define specific European tests. 3) Define mandatory S&D values. 4) Define mandatory support of extended interleaving memory. |
110 174-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Cities (SDMC); Broadband Deployment and Energy Management; Part 1: Overview, common and generic aspects of societal and technical pillars for sustainability | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/110100_110199/11017401/01.01.01_60/ts_11017401v010101p.pdf | The present document introduces the common and generic aspects of the societal and technical pillars to achieve sustainability objectives behind the deployment of smart new services within the IP network of a single city or an association of cities administratively clustered. Clause 4 identifies and presents a general overview of a city from small entity to significantly large municipality clustering several cities and villages. Clause 5 presents the pursued objectives behind the concept of smart city. Clause 6 describes the general theoretical pillars which bear the engineering requirements to deploy a digital multi service city. Clause 7 identifies the general needs from the cities. |
110 174-2-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Cities; Broadband Deployment and Energy Management; Part 2: Multiservice Networking Infrastructure and Associated Street Furniture; Sub-part 1: General requirements | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/110100_110199/1101740201/01.01.01_60/ts_1101740201v010101p.pdf | The present document details measures which may be taken to ease the deployment of smart new services and their multiservice street furniture of digital multiservice city within the IP network of a single city or an association of cities administratively clustered. Furthermore, the suggested measures will enable to engineer a reliable common networking infrastructure which can improve the Total Cost of Ownership (TCO) for the public administration while improving the energy efficiency of the overall deployment. The present document also lists the requirements which have led to this common architecture. Clause 4 presents a suggestion of an engineered digital multiservice city. Clause 5 introduces the active role categorized urban assets can play in the delivery of digital services across the territory of the city. Clause 6 reviews the spread efforts within the standardization organizations for the digital multiservice city. Clause 7 suggests both the common engineering required to transform an urban asset into an active network nodes of the digital multiservice city while presenting a concrete illustration of network design for one of the categories. This will enable the proper introduction and implementation of a new service, application or content within the city digital portfolio on a unified energy efficient network, though it is not the goal of the present document to provide detailed standardized solutions for network architecture. |
110 174-2-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Broadband Deployment and Energy Management; Part 2: Multiservice Networking Infrastructure and Associated Street Furniture; Sub-part 2: The use of lamp-posts for hosting sensing devices and 5G networking | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/110100_110199/1101740202/01.02.01_60/ts_1101740202v010201p.pdf | The present document addresses the opportunities and challenges offered by the use of lamp-posts to provide facilities supporting services required by sustainable digital multiservice cities and communities. The replacement of existing luminaires by LED light sources offers an opportunity to increase the functionality provided by the lamp-posts - beginning with improved operational control of the lighting provided. However, additional functionality can be supported by simultaneous installation of an electronics package to enable the lamp-post to host sensing devices. The present document describes the functions to be supported by this package together with consideration of power supply to any hosted sensing devices. A more comprehensive replacement approach includes the incorporation of 5G services by the separate installation of wireless network components acting as a Remote Radio Unit (RRU). The present document describes the technical challenges associated with the physical installation, provision of power, cabling and other infrastructures necessary to meet the required level of availability for these services. |
118 101 | oneM2M; Functional Architecture (oneM2M TS-0001 version 4.15.0 Release 4) | TS | 4.15.0 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118101/04.15.00_60/ts_118101v041500p.pdf | The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points. oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services. |
118 102 | oneM2M Requirements (oneM2M TS-0002 version 3.1.2 Release 3) | TS | 3.1.2 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118102/03.01.02_60/ts_118102v030102p.pdf | The present document contains an informative functional role model and normative technical requirements for oneM2M. |
118 103 | oneM2M; Security Solutions (oneM2M TS-0003 version 4.7.1 Release 4) | TS | 4.7.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118103/04.07.01_60/ts_118103v040701p.pdf | The present document defines security solutions applicable within the M2M system. |
118 104 | oneM2M; Service Layer Core Protocol Specification (oneM2M TS-0004 version 2.7.1 Release 2) | TS | 2.7.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118104/02.07.01_60/ts_118104v020701p.pdf | The present document specifies the communication protocol(s) for oneM2M compliant Systems, M2M Applications, and/or other M2M systems. The present document also specifies the common data formats, interfaces and message sequences to support reference points(s) defined by oneM2M. |
118 105 | oneM2M; Management Enablement (OMA) (oneM2M TS-0005 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118105/04.00.01_60/ts_118105v040001p.pdf | The present document specifies the protocol translation and mappings between the oneM2M service layer and the management technologies specified by OMA such as OMA DM 1.3, OMA DM 2.0 and OMA LightweightM2M. Note that OMA DM 1.3 and OMA DM 2.0 are collectively referenced as OMA DM in the present document. |
118 106 | oneM2M; Management Enablement (BBF) (oneM2M TS-0006 version 3.6.2 Release 3) | TS | 3.6.2 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118106/03.06.02_60/ts_118106v030602p.pdf | The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181 [6]. |
118 108 | oneM2M; CoAP Protocol Binding (oneM2M TS-0008 version 4.4.1 Release 4) | TS | 4.4.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118108/04.04.01_60/ts_118108v040401p.pdf | The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as 'RESTful CoAP binding'. The scope of the present document is (not limited to as shown below): • Binding oneM2M primitives to CoAP messages. • Binding oneM2M Response Status Codes to CoAP Response Codes. • Defining behaviour of a CoAP Client and Server depending on oneM2M parameters. |
118 109 | oneM2M; HTTP Protocol Binding (oneM2M TS-0009 version 4.4.1 Release 4) | TS | 4.4.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118109/04.04.01_60/ts_118109v040401p.pdf | The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types. |
118 110 | oneM2M; MQTT Protocol Binding (oneM2M TS-0010 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118110/04.00.01_60/ts_118110v040001p.pdf | The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies: 1) How a CSE or AE connects to MQTT. 2) How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver. 3) How a Receiver listens for incoming Requests. 4) How that Receiver can formulate and transmit a Response. |
118 111 | oneM2M; Common Terminology (oneM2M TS-0011 version 4.1.1 Release 4) | TS | 4.1.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118111/04.01.01_60/ts_118111v040101p.pdf | The present document contains a collection of specialist technical terms, definitions and abbreviations referenced within the oneM2M specifications. Having a common collection of definitions and abbreviations related to oneM2M documents will: • ensure that the terminology is used in a consistent manner across oneM2M documents; • provide a reader with convenient reference for technical terms that are used across multiple documents. The present document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and abbreviations as given in the present document are either externally created and included here, or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation. In addition in oneM2M Technical Specifications and Technical Reports there are also clauses dedicated for locally unique definitions and abbreviations. |
118 112 | oneM2M; Base Ontology (oneM2M TS-0012 version 3.7.3 Release 3) | TS | 3.7.3 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118112/03.07.03_60/ts_118112v030703p.pdf | The present document contains the specification of the oneM2M Base Ontology. A formal OWL representation of the Base Ontology can be found at http://www.onem2m.org/ontology/Base_Ontology. The present document also specifies an instantiation of the Base Ontology in oneM2M resources which can be used for semantic annotation and for ontology based interworking [4]. Finally an example is given how external ontologies can be mapped to the Base Ontology. The example uses the Smart Appliances REFerence (SAREF) ontology (http://ontology.tno.nl/saref). |
118 113 | oneM2M; Interoperability Testing (oneM2M TS-0013 version 3.3.1 Release 3) | TS | 3.3.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118113/03.03.01_60/ts_118113v030301p.pdf | The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in ETSI TS 118 101 [1], oneM2M TS-0004 [2], the bindings ETSI TS 118 108 [3], ETSI TS 118 109 [4] and ETSI TS 118 110 [5]. |
118 114 | oneM2M; LWM2M Interworking (oneM2M TS-0014 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118114/04.00.01_60/ts_118114v040001p.pdf | The present document specifies the interworking capabilities of the M2M Service Layer between ASN/IN/MN CSEs and LWM2M Endpoints using the architecture identified in Annex F of ETSI TS 118 101 [2] for the following interworking scenarios: • Interworking for transparent transport of encoded LWM2M Objects and commands in Content Sharing Resources between LWM2M Endpoints and M2M Applications. • Interworking with full mapping of LWM2M Objects in LWM2M Endpoints to semantically enabled Content Sharing Resources that are utilized by M2M Applications. • Interworking with one-to-one mapping of LWM2M Objects with oneM2M <mgmtObj> resources NOTE: The present document limits Content Sharing Resources to <container> and <contentInstance> resources. |
118 115 | oneM2M; Testing Framework (oneM2M TS-0015 version 2.0.0 Release 2) | TS | 2.0.0 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118115/02.00.00_60/ts_118115v020000p.pdf | The present document specifies a testing framework defining a methodology for development of conformance and interoperability test strategies, test systems and the resulting test specifications for oneM2M standards. |
118 116 | oneM2M; Secure Environment Abstraction (oneM2M TS-0016 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118116/04.00.01_60/ts_118116v040001p.pdf | The present document specifies mechanisms and interfaces to abstract from different technical implementations of a secure environment as defined in ETSI TS 118 103 [1]. |
118 118 | oneM2M Test Suite Structure and Test Purposes (oneM2M TS-0018 version 2.13.1 Release 2) | TS | 2.13.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118118/02.13.01_60/ts_118118v021301p.pdf | The present document specifies oneM2M test suite structure and test purposes that are designed to evaluate the conformity of oneM2M implementations to the oneM2M specifications. It also specifies: • guidelines for description of test behaviours and definition of test purpose structure; • notations to define a test purpose for conformance testing; and • test configurations for conformance testing. |
118 119 | oneM2M Abstract Test Suite and Implementation eXtra Information for Test (oneM2M TS-0019 version 2.3.0 Release 2) | TS | 2.3.0 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118119/02.03.00_60/ts_118119v020300p.pdf | The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in ETSI TS 118 101 [1] and ETSI TS 118 104 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5]. The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of inter-operability between different manufacturers' equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [3] and ISO/IEC 9646-2 [4]) as well as ETSI TS 118 115 [i.2] are used as a basis for the test methodology. |
118 120 | oneM2M; WebSocket Protocol Binding (oneM2M TS-0020 version 3.0.1 Release 3) | TS | 3.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118120/03.00.01_60/ts_118120v030001p.pdf | The present document specifies the binding of Mca and Mcc primitives onto the WebSocket binding. It specifies: • Procedures and message formats for operating and closing of WebSocket connections. • How request and response primitives are mapped into the payload of the WebSocket protocol. |
118 121 | oneM2M; oneM2M and AllJoyn® Interworking (oneM2M TS-0021 version 2.0.1 Release 2A) | TS | 2.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118121/02.00.01_60/ts_118121v020001p.pdf | The present document specifies the oneM2M and AllJoyn interworking technologies that enable AllJoyn Applications and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the AllJoyn IPE is hosted and how the IPE is composed with. Clause 6 defines the architecture aspects that mainly describes AllJoyn services to oneM2M resource mapping structure and rules. Furthermore, this explains the IPE registration and AllJoyn service discovery by the IPE. Clause 7 defines the IPE interworking procedures that consists of the initial setup and the service interworking procedures. |
118 122 | oneM2M; Field Device Configuration (oneM2M TS-0022 version 4.5.1 Release 4) | TS | 4.5.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118122/04.05.01_60/ts_118122v040501p.pdf | The present document specifies the architectural options, resources and procedures needed to pre-provision and maintain devices in the Field Domain (e.g. ADN, ASN/MN) in order to establish M2M Service Layer operation between the device's AE and/or CSE and a Registrar and/Hosting CSE. The resources and procedures includes information about the Registrar CSE and/or Hosting CSE needed by the AE or CSE to begin M2M Service Layer operation. |
118 123 | oneM2M; SDT based Information Model and Mapping for Vertical Industries [oneM2M TS-0023 version 4.8.1 Release 4] | TS | 4.8.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118123/04.08.01_60/ts_118123v040801p.pdf | The present document describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model. |
118 124 | oneM2M; OCF Interworking (oneM2M TS-0024 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118124/04.00.01_60/ts_118124v040001p.pdf | The present document specifies the detailed methods for oneM2M and OCF interworking using the architecture identified in ETSI TS 118 133 [5] and annex F of ETSI TS 118 101 [2] for the following scenario: • Interworking with full mapping of the semantics of the non-oneM2M data model to Mca, see scenario number 1 listed in clause F.2 of ETSI TS 118 101 [2]. This is also in line with the interworking concepts specified in ETSI TS 118 133 [5]. This interworking scenario allows for interworking between OCF devices and oneM2M entities purely based on the common understanding of aligned information models - such as the models defined in ETSI TS 118 123 [6]. There is no limitation regarding the direction of exposure of services: Services provided by OCF devices (OCF servers) can be exposed to oneM2M entities or vice versa. The oneM2M entities do not need to be aware of any details of the OCF protocols or interfaces. |
118 125 | Definition of product profiles (oneM2M TS-0025 version 2.0.0 Release 2A) | TS | 2.0.0 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118125/02.00.00_60/ts_118125v020000p.pdf | The present document specifies the detailed defined product profiles that can be used by manufactures and service providers where for each dedicated product, one of the defined product profile can be selected. The product profile would provide guidance to what features will be implemented, what features should be implemented and what features may be implemented. The present document also describes the test purposes that need to go through if the product need to be certified. |
118 130 | oneM2M; Ontology based Interworking (oneM2M TS-0030 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118130/04.00.01_60/ts_118130v040001p.pdf | The present document specifies Generic Interworking of the oneM2M System with external systems (e.g. Area Networks containing non-oneM2M devices) that can be described with ontologies that are compliant with oneM2M's Base Ontology, specified in ETSI TS 118 112 [3]. In oneM2M Release 2 the specification for Ontology based Interworking had been contained in clauses 8 and 9 of ETSI TS 118 112 [3]. |
118 132 | MAF and MEF Interface Specification (oneM2M TS-0032 version 4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118132/04.00.01_60/ts_118132v040001p.pdf | The present document specifies communication between the M2M Authentication Function (MAF) and MAF clients on the reference point Mmaf and between the M2M Enrolment Function (MEF) and MEF clients on the reference point Mmef. |
118 133 | Interworking Framework (oneM2M TS-0033 v4.0.1 Release 4) | TS | 4.0.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118133/04.00.01_60/ts_118133v040001p.pdf | The present document defines general guidelines when interworking between external Proximal IoT technologies which are not aware of oneM2M-defined functionality, and the oneM2M system (i.e. the interaction between non-oneM2M- aware devices, gateways or applications (non-oneM2M entities) and oneM2M-defined entities). In the present document guidelines are defined on how to use oneM2M-defined resources to represent the state, events, actions, procedures, services provided by the non-oneM2M entities and how to expose oneM2M functions or services represented by oneM2M-defined resource to non-oneM2M Proximal IoT technologies. Therefore, services provided by non-oneM2M entities can be consumed by oneM2M entities via the oneM2M defined interfaces and vice versa. When following these guidelines, oneM2M-aware entities consuming services provided by non-oneM2M-aware entities via the specified interworking methods do not need to know anything about external Proximal IoT technologies. Also entities in an external Proximal IoT network that are not oneM2M-aware can consume services provided by oneM2M entities when exposed to the external Proximal IoT network according to the specified methods. |
118 140 | oneM2M Modbus Interworking (oneM2M TS-0040 version 4.0.0 Release 4) | TS | 4.0.0 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118140/04.00.00_60/ts_118140v040000p.pdf | The present document specifies the oneM2M and Modbus interworking technologies that enable Modbus devices and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the Modbus IPE is hosted and how the IPE is composed with. Clause 6 defines the architecture aspects that mainly describes Modbus services to oneM2M resource mapping structure and rules. Furthermore, this explains the IPE registration and interworking procedures. |
118 141 | oneM2M; SensorThings Interworking (oneM2M TS-0041 version 5.4.1 Release 5) | TS | 5.4.1 | http://www.etsi.org/deliver/etsi_ts/118100_118199/118141/05.04.01_60/ts_118141v050401p.pdf | The present document provides the interworking specification between the oneM2M service layer and the OGC SensorThings API to enable seamless integration of IoT data and services, particularly in smart city environments. |
118 501 | oneM2M Use Case collection | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118501/01.00.00_60/tr_118501v010000p.pdf | The present document includes a collection of use cases from a variety of M2M industry segments (listed in table 1.1). Each use case may include a description, source, actors, pre-conditions, triggers, normal and alternative flow of sequence of interactions among actors and system, post-conditions, illustrations and potential requirements. The potential requirements provide an initial view of what oneM2M requirements could arise from the Use Case as seen by the contributor. These are intended to help the reader understand the use case's needs. These potential requirements may have been subsequently submitted by the contributor for consideration as candidate oneM2M requirements, which may or may not have been agreed as a oneM2M requirement (often after much editing). As such, there may not be a direct mapping from the potential requirements to agreed oneM2M requirements [i.14]. Table 1.1 Industry Segment oneM2M Use Cases Agriculture Energy Wide area Energy related measurement/ control system for advanced transmission and distribution automation Analytics for oneM2M Smart Meter Reading Environmental Monitoring for Hydro-Power Generation using Satellite M2M Oil and Gas Pipeline Cellular /Satellite Gateway Enterprise Smart building Finance Healthcare M2M Healthcare Gateway Wellness services Secure remote patient care and monitoring Industrial Public Services Street Light Automation Devices, Virtual devices and Things Car/Bicycle Sharing Services Smart parking Information Delivery service in the devastated area Residential Home Energy Management Home Energy Management System Plug-In Electrical Charging Vehicles and power feed in home scenario Real-time Audio/Video Communication Event Triggered Task Execution Semantic Home Control Semantic Device Plug and Play Retail Transportation Vehicle Diagnostic & Maintenance Report Remote Maintenance services Neighbourhood Alerting on Traffic Accident Fleet management service using Digital Tachograph Other Extending the M2M Access Network using Satellites M2M data traffic management by underlying network operator Optimizing connectivity management parameters with mobile networks Optimizing mobility management parameters with mobile networks Sleepy nodes Collection of M2M system data Leveraging Broadcasting/ Multicasting Capability of Underlying Networks Service Provisioning for Equipment with Built-in Device ETSI ETSI TR 118 501 V1.0.0 (2015-05) 12 |
118 502 | Architecture Part 1: Analysis of the architectures proposed for consideration by oneM2M | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118502/01.00.00_60/tr_118502v010000p.pdf | The present document provides an analysis and comparison of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. In addition, architectural work by other non-oneM2M Partner Type 1 organizations is provided for consideration. The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications (TS). The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group. |
118 503 | oneM2M Architecture Part 2: Study for the merging of architectures proposed for consideration by oneM2M | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118503/01.00.00_60/tr_118503v010000p.pdf | The present document provides an evaluation of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. Common Functional Entities and Reference Points are identified, as well as critical differences. New functionality will not be considered as part of this study. The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications. The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group. |
118 506 | Study of Management Capability Enablement Technologies for Consideration by oneM2M | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118506/01.00.00_60/tr_118506v010000p.pdf | The present document describes and collects the state-of-art of the existing technologies on management capability, evaluates if the technologies can match the requirements defined in oneM2M, analyzes how the technologies can leverage the design of the architecture of oneM2M. |
118 508 | Analysis of Security Solutions for the oneM2M System | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118508/01.00.00_60/tr_118508v010000p.pdf | The scope of the present document is to create a common understanding on security within oneM2M systems. To achieve that, security services are explained, threats analysed and security requirements within oneM2M identified and derived from use cases. In addition the present document discusses how security mechanisms relate to the oneM2M architecture. Suitable security procedures and mechanisms are defined within [i.12]. |
118 512 | oneM2M; End-to-End Security and Group Authentication (oneM2M TR-0012 version 2.0.0) | TR | 2.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118512/02.00.00_60/tr_118512v020000p.pdf | The present document provides options and analyses for the security features and mechanisms providing end-to-end security and group authentication for oneM2M. The scope of this technical report includes use cases, threat analyses, high level architecture, generic requirements, available options, evaluation of options, and detailed procedures for executing end-to-end security and group authentication. |
105 175-1-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Plastic Optical Fibres; Part 1: Plastic Optical Fibre System Specifications for 100 Mbit/s and 1 Gbit/s; Sub-part 2: 1 Gbit/s and 100 Mbit/s physical layer for Plastic Optical Fibres | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/105100_105199/1051750102/01.01.01_60/ts_1051750102v010101p.pdf | The present document provides a description of an OSI physical networking layer to communicate data over plastic optical fibre at 100 Mbit/s and 1 000 Mbit/s. A full duplex physical layer is described. Multi data type interface is proposed, as well as its encapsulation, coding and modulation needed to achieve 1 Gbit/s link over a bandwidth limited optical channel like the plastic optical fibre. Multiple link speeds are handled by this physical layer. |
118 517 | oneM2M; Home Domain Abstract Information Model (oneM2M TR-0017 version 2.0.0) | TR | 2.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118517/02.00.00_60/tr_118517v020000p.pdf | The present document allows application developers to describe the status of devices as resources on oneM2M-based platform in various ways. Thus different application developers can create different resource trees even when they build the same kinds of applications. Moreover when handling the same kinds of devices from different vendors on M2M platforms, application developers may create disunited resource trees without common information model. In order to solve such issues, the present document intends to provide the common and unified APIs on one M2M platform for the home domain by defining an abstract information model for the home domain devices such as TV, refrigerator, air conditioner, smart meter, and lighting equipment. The definition of the abstract information model will be based on data models that currently exist in the home domain. The home domain abstract information model does not intend to define the interworking function between the oneM2M system and protocols of the data models from which the abstract data model is defined. Also, the present document intends to define how the developed abstract information model for a device could be represented in the CSEs of the oneM2M system. |
118 518 | oneM2M; Industrial Domain Enablement (oneM2M TR-0018 version 2.5.1 Release 2A) | TR | 2.5.1 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118518/02.05.01_60/tr_118518v020501p.pdf | The present document collects the use cases of the industrial domain and the requirements needed to support the use cases collectively. In addition it identifies the necessary technical work needed to be addressed while enhancing future oneM2M specifications. |
118 522 | oneM2M; Continuation & integration of HGI Smart Home activities (oneM2M TR-0022 version 2.0.0) | TR | 2.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118522/02.00.00_60/tr_118522v020000p.pdf | The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements. It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M. |
118 525 | oneM2M; Application Developer Guide (oneM2M version 1.0.0 Release 1) | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118525/01.00.00_60/tr_118525v010000p.pdf | The present document provides a guide for application developers to develop applications using functionalities provided by any oneM2M compliant service platform with thescope of as follows: • Objective of the use case, • The architecture of the use case mapped into an oneM2M service platform, • The execution procedures for implementation of the use case, and • Implementation details of the use case. |
104 147-2 | Mission Critical (MC) services; Mission Critical Push To Talk (MCPTT) Application Server (AS) Protocol conformance specification for server-to-client interface; Part 2: Test Applicability and Implementation Conformance Statement (ICS) pro forma specification | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/104100_104199/10414702/01.01.01_60/ts_10414702v010101p.pdf | The present document provides the Implementation Conformance Statement (ICS) pro forma for testing Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [i.6] and ISO/IEC 9646-7 [2]. The present document specifies the recommended applicability statement for the test cases included in ETSI TS 104 147-1 [4]. These applicability statements are based on the features implemented in the Server respectively. The present document is valid for Mission Critical Push to Talk (MCPTT) Servers implemented according to 3GPP releases starting from Release 14 up to Release 15. The present document does not specify applicability or ICS for protocol conformance testing for the EPS (LTE) bearers which carry the Mission Critical Services data sent or received by the Client and/or the Server. These are defined in ETSI TS 136 523-2 [i.5] (3GPP TS 36.523-2). |
118 546 | oneM2M: Study on Public Warning Service Enabler (oneM2M TR-0046 v4.0.0 Release 4) | TR | 4.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118546/04.00.00_60/tr_118546v040000p.pdf | The present document results of studies on public warning service enabler of oneM2M system. To enable public warning service over oneM2M system, the study includes following technical scope: • Case studies of existing public warning systems. • Use cases and potential requirements. • Architecture analysis for the new use cases and requirements with current oneM2M system. • Abstract data models for public warning services. |
118 551 | oneM2M API guide (oneM2M TR-0051 version 2.0.0) | TR | 2.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118551/02.00.00_60/tr_118551v020000p.pdf | The present document is a collection of the CRUDN messages used for managing some of the main resources defined in ETSI TS 118 101 [i.2]. It also provides the description and associated flow in basic examples. It aims to use this list as a common sets of APIs to help developers to write applications that can run across different platforms and specific implementations. When an application developer would need to build software code for managing a specific resource, he could have an immediate access to the list of CRUDN message with description and its associated examples of requests to send and its expected responses. The REST API examples are sorted by resource type and CRUDN operations, which allows a quick and easy access to the information. |
118 565 | oneM2M-SensorThings API interworking (oneM2M TR-0065 version 5.0.0) | TR | 5.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118565/05.00.00_60/tr_118565v050000p.pdf | The present document defines an interworking of both standards oneM2M and OGC SensorThings API. The present document is structured as followed: • Introduction and background to OGC-SensorThings API. • Describing interworking scenarios that are relevant but not exclusive for Smart City (there are also examples from other areas and verticals as well). • Technical comparison of oneM2M and OGC/STA. • Describing a technical solution for interworking of both standards; there might be interworking on different level: - opaque data routing; - data model mapping between oneM2M-SDT and OGC. • Developing test cases for interworking between oneM2M and OGC SensorThings API. |
118 567 | oneM2M: Study on Management Object migration to SDT (oneM2M TR-0067 version 4.0.0) | TR | 4.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118567/04.00.00_60/tr_118567v040000p.pdf | The present document studies the completion of SDT (Smart Device Template) using <flexContainer> resource specializations and the possible migration of the existing device management model using Management Object (<mgmtObj>). The present document is initiated in the context of the Management Object Migration having the following objectives (extract): In Release 4, SDT (Smart Device Template) has been extended to include device management functions in addition to the existing services. This justified extension creates a new way to perform device management compared to the existing Device Management (DM) Common Services Function (CSF) model using <mgmtObj>. In order not to live with 2 solutions for the same purpose, the present document proposes to work on a transition phase allowing implementation using DM <mgmtObj> to migrate towards SDT model. The scope of the present document is to study the Device Management model based on Management Object (<mgmtObj>) model migration towards SDT model. This action plan includes to: 1) Provide a temporary TR with a mapping between <mgmtObj> and the SDT DM <flexContainer>. 2) List in the present document all the specifications and sections that will have to be updated when <mgmtObj> will be replaced by SDT. 3) List in the present document the issues to be resolved by removing the <mgmtObj> after migration and the proposed solutions. 4) Depending on the present document outcomes, decide whether <mgmtObj> should be removed or not in oneM2M Release 4. New tasks may be added during the process if necessary. The present document intends to provide the study as part of the action plan above. |
118 568 | AI enablement to oneM2M (oneM2M TR-0068 version 5.0.1) | TR | 5.0.1 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118568/05.00.01_60/tr_118568v050001p.pdf | The present document is analysing existing AI/ML technologies that can be resourced into oneM2M architecture. The present document is also investigating potential AI/ML service use cases that use data collected in the oneM2M system. The study on existing AI/ML technologies and use cases are further analysed in the present document to understand what features are supported and unsupported by the oneM2M system. Based on the result of the present document, it will identify potential requirements and key features to enable AI/ML in the oneM2M system. |
119 000 | Electronic Signatures and Infrastructures (ESI); The framework for standardization of digital signatures and trust services; Overview | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/119000_119099/119000/01.03.01_60/tr_119000v010301p.pdf | The present document describes the general structure for ETSI/CEN digital signature standardization outlining existing and potential standards for such signatures, hereafter referred to as the framework for standardization of signatures. This framework identifies six areas of standardization with a list of existing and potential future standards in each area. NOTE: Each title providing the name of a listed standard in the framework for standardization of signatures includes a hyperlink that leads to download facilities for such a standard, including all its versions, both as TS/TR and/or as EN when applicable. |
119 001 | Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/119000_119099/119001/01.02.01_60/tr_119001v010201p.pdf | The present document provides definitions and abbreviations for use in the ETSI ESI framework for standardization of signatures. |
119 100 | Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for signature creation and validation | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/119100/01.01.01_60/tr_119100v010101p.pdf | The present document, which addresses area 1 of the Framework [i.1], provides a business driven guided process for implementing generation and validation of digital signatures in business' electronic processes. Starting from a business analysis and risk analysis of the business' electronic processes, stakeholders are guided for making the best choice among the wide offer of standards in order to ensure the best implementation of digital signatures within the addressed application/business electronic processes. The target audience includes enterprise/business process architects, application architects, application developers, and signature policy issuers. |
119 101 | Electronic Signatures and Infrastructures (ESI); Policy and security requirements for applications for signature creation and signature validation | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/119101/01.01.01_60/ts_119101v010101p.pdf | The present document provides general security and policy requirements for applications for signature creation, validation and augmentation. The present document is primarily relevant to the following actors: • Implementers and providers of applications for signature creation, signature validation and/or signature augmentation, who need to ensure that relevant requirements are covered. • Actors that integrate applications for signature creation, signature validation and/or signature augmentation components with business process software (or use standalone software), who want to ensure proper functioning of the overall signature creation/validation/augmentation process and that the signature creation/validation is done in a sufficiently secure environment. The present document is applicable to these actors, and their evaluators (for a self-evaluation or an evaluation by a third party) to have a list of criteria against which to check the implementation. The requirements cover applications for signature creation, signature validation and/or signature augmentation, i.e. the implementation and provision of the Signature Creation/Validation/Augmentation Application modules (SCA/SVA/SAA), the driving application (DA), the communication between the SCA and the signature creation device (SCDev) and the environment in which the SCA/SVA/SAA is used. It also specifies user interface requirements, while the user interface can be part of the SCA/SVA/SAA or of the DA which calls the SCA/SVA/SAA. Any entity using SCA/SVA/SAA components in its business process acts as driving application. The document covers: • Legal driven policy requirements. • Information security (management system) requirements. • Signature creation, signature validation and signature augmentation processes requirements. • Development and coding policy requirements. • General requirements. Protection Profiles (PP) for signature creation applications and signature validation applications are out of scope and are defined in the CEN standard "Protection Profiles for Signature Creation & Validation Applications" [i.9]. General requirements for trust service providers are provided in ETSI EN 319 401 [i.24]. Requirements for trust service providers providing signature creation or validation services are out of scope. Requirements on trust service providers providing signature creation services are to be defined in ETSI TS 119 431 [i.22], with CEN EN 419 241 [i.21] defining requirements for a remote signature creation device. Requirements on trust service providers providing signature validation services are to be defined in ETSI TS 119 441 [i.23]. |
119 102-2 | Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 2: Signature Validation Report | TS | 1.4.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11910202/01.04.01_60/ts_11910202v010401p.pdf | The present document specifies a general structure and an XML format for reporting the validation of AdES digital signatures (specified in ETSI EN 319 122-1 [i.1], ETSI EN 319 132-1 [4], ETSI EN 319 142-1 [i.3] respectively). The present document is aligned with the requirements specified in ETSI EN 319 102-1 [1]. |
119 112 | Electronic Signatures and Infrastructures (ESI); Most significant differences between AdES/ASiC ENs and previous TSs | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/119112/01.01.01_60/tr_119112v010101p.pdf | The present document summarizes: • The most relevant differences between the CAdES digital signatures specified in ETSI EN 319 122-1 [i.2] and ETSI EN 319 122-2 [i.26], and the CAdES signatures specified in ETSI TS 101 733 (V2.2.1) [i.3] and ETSI TS 103 173 (V2.2.1) [i.4]. • The most relevant differences between the PAdES digital signatures specified in ETSI EN 319 142-1 [i.8] and ETSI EN 319 142-2 [i.9], and the PAdES signatures specified in the latest versions of the different parts ETSI TS 102 778 ([i.10] to [i.15]) and ETSI TS 103 172 (V2.2.2) [i.16]. • The most relevant differences between the XAdES digital signatures specified in ETSI EN 319 132-1 [i.1] and ETSI EN 319 132-2 [i.5], and the XAdES signatures specified in ETSI TS 101 903 (V1.4.2) [i.6] and ETSI TS 103 171 (V2.1.1) [i.7]. • The most relevant differences between the ASiC containers specified in ETSI EN 319 162-1 [i.17] and ETSI EN 319 162-2 [i.18] and the ASiC containers specified in ETSI TS 102 918 (V1.3.1) [i.19] and ETSI TS 103 174 (V2.2.1) [i.20]. |
119 122-3 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 3: Incorporation of Evidence Record Syntax (ERS) mechanisms in CAdES | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11912203/01.01.01_60/ts_11912203v010101p.pdf | The present document provides mechanism to incorporate evidence records in ASN.1 format within a CAdES signature as outlined in ETSI EN 319 122-1 [4], annex B. It specifies the attributes to be used and profiles the ERS standard (IETF RFC 4998 [2]) to provide clear rules how to incorporate ERS within a CAdES signature or a legacy CAdES signature. |
119 124-1 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/11912401/01.01.01_60/tr_11912401v010101p.pdf | The present document provides an overview of the set of test suites for testing interoperability and conformance of CAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of CAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of CAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable. |
119 124-2 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of CAdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11912402/01.01.01_60/ts_11912402v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to CAdES baseline signatures [1]. The test suites are defined with four different layers reflecting the four different levels of CAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of CAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 124-3 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of extended CAdES signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11912403/01.01.01_60/ts_11912403v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended CAdES signatures [2]. The present document defines test suites for each level defined in ETSI EN 319 122-2 [2]. Test suites also cover augmentation of extended CAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 124-4 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of CAdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11912404/01.01.01_60/ts_11912404v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of CAdES signatures against CAdES baseline signatures as specified in ETSI EN 319 122-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by CAdES [1]. Regarding CAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for CAdES baseline signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by CAdES [1]. |
119 124-5 | Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended CAdES signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11912405/01.01.01_60/ts_11912405v010101p.pdf | The present document defines the checks to be performed for testing conformance of CAdES signatures against extended CAdES signatures as specified in ETSI EN 319 122-2 [2]. It defines only the checks that are specific to extended CAdES signatures. The set of checks that are common to both extended and baseline CAdES signatures, are defined in ETSI TS 119 124-4 [3]. The complete set of checks to be performed by any tool on CAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 122-1 [1] and ETSI EN 319 122-2 [2] defined in ETSI TS 119 124-4 [3], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by CAdES [1]. Regarding CAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for extended CAdES signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by CAdES [1]. |
119 132-3 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 3: Incorporation of Evidence Record Syntax (ERS) mechanisms in XAdES | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11913203/01.01.01_60/ts_11913203v010101p.pdf | The present document specifies the semantics and the syntax for a new unsigned XAdES qualifying property able to contain evidence records. The present document specifies the rules that govern the incorporation of evidence records within a XAdES signature or a legacy XAdES signature. NOTE: The present specification allows to incorporate Evidence Records in two different formats, namely: the XML format for ERS specified in IETF RFC 6283 (2011): "Extensible Markup Language Evidence Record Syntax (XMLERS)" [5], and the ASN.1 format for ERS specified in IETF RFC 4998 (2007): "Evidence Record Syntax (ERS)" [8]. The present document also specifies a new level for XAdES signatures, incorporating one or more than one of the aforementioned qualifying properties. The signatures specified in the present document are not baseline XAdES signatures. |
119 134-1 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/11913401/01.01.01_60/tr_11913401v010101p.pdf | The present document provides an overview of the set of test suites for testing interoperability and conformance of XAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of XAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of XAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable. |
119 134-2 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of XAdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11913402/01.01.01_60/ts_11913402v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to XAdES baseline signatures as specified in ETSI EN 319 132-1 [1]. The test suites are defined with four different layers reflecting the four different levels of XAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of XAdES baseline and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 134-3 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of extended XAdES signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11913403/01.01.01_60/ts_11913403v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended XAdES signatures as specified in ETSI EN 319 132-2 [2]. The present document defines test suites for each level defined in ETSI EN 319 132-2 [2]. Test suites also cover augmentation of extended XAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 134-4 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of XAdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11913404/01.01.01_60/ts_11913404v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of XAdES signatures against XAdES baseline signatures as specified ETSI EN 319 132-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by XAdES [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:DigestMethod, ds:DigestValue). Regarding XAdES properties, the present document explicitly differentiates between structural requirements that are defined by the XAdES XML Schema, and the rest of the requirements specified by XAdES [1]. Checks corresponding to the first set of requirements are specified in the normative annex A. Checks corresponding to the second set of requirements are specified in the body part of the present document. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1]. |
119 134-5 | Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended XAdES signatures | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11913405/02.01.01_60/ts_11913405v020101p.pdf | The present document defines the sets of checks required for testing conformance of XAdES signatures against extended XAdES signatures as specified ETSI EN 319 132-2 [2]. It defines only the checks that are specific to extended XAdES signatures. The set of checks that are common to both extended and baseline XAdES signatures, are defined in ETSI TS 119 134-4 [4]. The complete set of checks to be performed by any tool on XAdES extended signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2] defined in ETSI TS 119 134-4 [4], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. The only possible inferences are the ones explicitly mentioned in the second paragraph of the present clause. Checks specified by the present document are exclusively constrained to elements specified by ETSI EN 319 132-1 [1] and to certain elements specified by XMLSig [3] that are re-used in XAdES schema definition (like ds:keyInfo). Regarding XAdES properties, the present document does not addresses the structural requirements that are defined by the XAdES XML Schema that are suitably addressed in ETSI TS 119 134-4 [4]. The present document does not address either requirements that are common to both XAdES signatures as specified in ETSI EN 319 132-1 [1] and ETSI EN 319 132-2 [2]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by XAdES [1]. |
119 142-3 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 3: PAdES Document Time-stamp digital signatures (PAdES-DTS) | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11914203/01.01.01_60/ts_11914203v010101p.pdf | The present document specifies a type of PDF digital signatures, as specified in ISO 32000-1 [1], based on time-stamps. It specifies a format for PAdES digital signatures using a Document Time-stamp - as defined in ETSI EN 319 142-1 [2] - as a digital signature intended to specifically prove the integrity and existence of a PDF document as defined in ISO 32000-1 [1], rather than proving any form of authentication or proof of origin. NOTE: This format does not meet the requirements of advanced electronic signature and advanced electronic seal as defined in Regulation (EU) No 910/2014 [i.4], as it is not capable of identifying the signer. |
119 144-1 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/11914401/01.01.01_60/tr_11914401v010101p.pdf | The present document provides an overview of the set of test suites for testing interoperability and conformance of PAdES signatures. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of PAdES signatures; and b) lists the features of every test suite for testing interoperability and conformance of PAdES signatures. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable. |
119 144-2 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of PAdES baseline signatures | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11914402/02.01.01_60/ts_11914402v020101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to PAdES baseline signatures [2]. The test suites are defined with four different layers reflecting the four different levels of PAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of PAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 144-3 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 3: Test suites for testing interoperability of additional PAdES signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11914403/01.01.01_60/ts_11914403v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to additional PAdES signatures profiles [3]. The present document defines test suites for each profile defined in ETSI EN 319 142-2 [3]. Test suites also cover augmentation of additional PAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.