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 |
|---|---|---|---|---|---|
103 458 | CYBER; Application of Attribute Based Encryption (ABE) for PII and personal data protection on IoT devices, WLAN, cloud and mobile services - High level requirements | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103458/01.01.01_60/ts_103458v010101p.pdf | The present document specifies high level requirements for the application of Attribute Based Encryption (ABE) to protect PII and personal data on IoT devices/services, cloud services, Wireless Local Area Networks and mobile services, where access to data has to be given to multiple parties and under different conditions. With a main focus on the confidentiality of data, including personal data and Personally Identifiable Information, the present document may help in supporting the General Data Protection Regulation [i.19]. The following use cases are described: 1) The Mobile use case describes a situation of user access from less trusted networks. The objective is to provide user identity protection preserving disclosure to unauthorized entity. 2) The federated WLAN use case where users can access different WLAN networks using their credentials - issued by different authorities/domains - while preserving their privacy. 3) Many Internet of Things use cases or edge scenarios where data access mechanisms are actioned either in the network or on the device. 4) The Cloud use case where a third party accesses personal data from the Cloud Service Provider. The present document also provides recommendations on the ABE scheme to use for each use case. |
103 459 | Rail Telecommunications (RT); Future Rail Mobile Communication System (FRMCS); Study on system architecture | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103459/01.02.01_60/tr_103459v010201p.pdf | The present document is a technical report, in line with the scope and field of application of its related Work Item. In particular, it covers: • Definition of key terms and a high-level description of the FRMCS architecture, as agreed among UIC and ETSI (see clauses 3 and 4, respectively). • An analysis of the architectural implications of various requirements on the FRMCS system captured in UIC TOBA and 3GPP TR 22.889 [i.3], and of aspects such as identification and addressing, security, positioning and migration (see clause 5). • A description of the logical architecture of the FRMCS system, including a description of the main logical entities and key reference points among these (see clause 6). • A derivation of key deployment and border-crossing scenarios that the FRMCS architecture should support (see clause 7). • An investigation of possible technical realizations of the FRMCS system, based on the usage of building blocks from 3GPP and other standards bodies (see clause 8). • A gap analysis and identification of risks related to the FRMCS standardization, for instance due to its dependency on timelines of different standards bodies (see clause 9). Finally, the present document identifies the next steps to ensure the complete definition of the FRMCS system. |
103 460 | Intelligent Transport Systems (ITS); Security; Pre-standardization study on Misbehavior Detection; Release 2 | TR | 2.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103460/02.01.01_60/tr_103460v020101p.pdf | The present document provides an overview of the relevant misbehaviour detection mechanisms suitable for C-ITS and provides comments on performance and applicability of different misbehaviour detection mechanisms. The present document provides also hints on potential minimum requirements for the security architecture and misbehaviour detection distribution mechanisms, i.e. misbehaviour reporting. |
103 461 | Digital Audio Broadcasting (DAB); Domestic and in-vehicle digital radio receivers; Minimum requirements and Test specifications for technologies and products | TS | 1.2.2 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103461/01.02.02_60/ts_103461v010202p.pdf | The present document describes the minimum requirements for digital radios, both domestic and in-vehicle, and the necessary test methods that lead to compliance with the requirements. It may be used as the technical basis for a Digital Radio Certification Mark scheme. A Digital Radio Certification Mark is designed to be used on product packaging and provides an easily recognized mark to correspond to public information campaigns on the necessary requirements for consumers to make a switch to digital radio. Manufacturers are, of course, free to include additional features or increased performance compared to the minimum requirements specified in the present document. This version adds support for tuned ensemble alarm announcements for all receivers to the minimum requirements and provides clarification for the text display requirements which now accommodate the place of the regional profiles. There are consequential changes to the core technology testing and there are two additional product tests. These updates reflect changes to the DAB standards base since 2017. |
103 462 | Lawful Interception (LI); Inter LEMF Handover Interface | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103462/01.03.01_60/ts_103462v010301p.pdf | The present document specifies the LEMF to LEMF interface to support (as a minimum) European Investigation Orders (EIOs) related to LI and/or RD. The present document aims to be capable of securely handling real-time and stored data transfer between LEMFs in accordance with ETSI TS 102 232 parts 1 [6] to 7 [12] and the related 3GPP TS 33.108 [5] for LI. In the present document RD is for further study. Local LI handover interfaces frequently use dedicated networks for delivery with local specific security features. With the EIO Directive in place, there is a need to have a common Handover Interface to allow real-time exchange between LEMFs that can be located in different countries, under different jurisdictions. |
103 463-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Key Performance Indicators for Sustainable Digital Multiservice Areas; Part 1: Description of Key Performance Indicators | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/10346301/01.02.01_60/ts_10346301v010201p.pdf | The present document defines indicators (KPIs) for Smart Cities expressing city level in terms of People, Planet, Prosperity, Governance and Propagation. |
103 463-2 | Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Key Performance Indicators for Sustainable Digital Multiservice Areas; Part 2: Global KPIs for Sustainable Digital Multiservice Areas | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/10346302/01.01.01_60/ts_10346302v010101p.pdf | The present document defines Global Key Performance Indicators (Global KPIs) to describe the social, environmental sustainability and economic attractiveness of Sustainable Digital Multiservice Areas - addressing urban (cities) and rural communities. The Global KPIs are combinations of the Key Performance Indicators selected from those of ETSI TS 103 463-1 [i.1] which are either measurable or based on publicly available data and relevant to the Sustainable Digital Multiservice Area (SDMA) under consideration. |
103 464 | Hybrid Broadcast Broadband TV; Application Discovery over Broadband | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103464/01.03.01_60/ts_103464v010301p.pdf | The present document augments clause 6 of ETSI TS 102 796 [1], which states that broadcast-related applications are signalled as part of the broadcast. It defines a method for discovery of HbbTV® applications in settings where AIT signalling via the broadcast network is not available to the terminal. In this situation, an HbbTV® terminal may discover broadcast-related HbbTV® services via a broadband internet connection. |
103 465 | Smart Secure Platform (SSP); Requirements Specification (Release 16) | TS | 16.6.0 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103465/16.06.00_60/ts_103465v160600p.pdf | The present document defines the use cases and requirements for the definition of the interfaces and protocols for interfacing with a secure element. This secure element is called Smart Secure Platform (SSP). |
103 466 | Digital Audio Broadcasting (DAB); DAB audio coding (MPEG Layer II) | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103466/01.02.01_60/ts_103466v010201p.pdf | The present document defines the method to code and transmit audio services using the MPEG Layer II audio coder for Digital Audio Broadcasting (DAB) (ETSI EN 300 401 [1]) and details the necessary mandatory requirements for decoders. The permitted audio modes and the data protection and encapsulation are detailed. This audio coding scheme permits the full use of the PAD channel for carrying dynamic labels and user applications. |
103 467 | Speech and multimedia Transmission Quality (STQ); Quality of Service aspects for IoT; Discussion of QoS aspects of services related to the IoT ecosystem | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103467/01.01.01_60/tr_103467v010101p.pdf | The present document discusses Quality of Service (QoS) aspects of services related to the Internet of Things (IoT) ecosystem from an end-to-end perspective; a strict end-user, service-oriented point of view. Here, end-to-end is understood as "from a service user/terminal/provider to a service user/terminal/provider". The discussion deals with two questions. The first question is if the existing framework for QoS parameter definitions and methodologies is sufficient to also include the IoT angle of view. The second question is if the existing portfolio of QoS parameters needs extensions or adaptations. |
103 468 | Speech and multimedia Transmission Quality (STQ); Quality of Service aspects for 5G; Discussion of QoS aspects of services related to the 5G ecosystem | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103468/01.01.01_60/tr_103468v010101p.pdf | The present document summarizes the results of an analysis of the impact of the upcoming 5G on existing QoS metrics, and the question if extensions or modifications of the portfolio of QoS parameters portfolio are required to capture respective properties of 5G. The analysis starts with a summary of features and properties of 5G which can be expected to be relevant for QoS assessment. The first question addressed is if there are features of the 5G roadmap - as far as technically stable as of the time of publication, or reasonably stable projections - which constitute new services which would then require new sets of QoS parameters. The second question is in what way projected 5G properties may require adaptations with respect to measurement methodologies, computation, or usage of existing QoS parameters. |
103 473 | Evolution of management towards Autonomic Future Internet (AFI); Autonomicity and Self-Management in the Broadband Forum (BBF) Architectures | TR | 1.1.2 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103473/01.01.02_60/tr_103473v010102p.pdf | The present document aims at providing recommendations for the introduction of autonomics (management and control intelligence) into the fixed broadband access and aggregation networks specified in the Broadband Forum (BBF) Architecture specifications. To this effect, it covers the instantiation of the reference model for Autonomic Networking, Cognition and Self-Management, called GANA (Generic Autonomic Networking Architecture) [i.1], starting from the reference architecture defined in BBF TR 101 [i.6], and considering also BBF TR 178 [i.7] and BBF TR 317 [i.28] reports. It superimposes GANA Decision Elements (DEs) into nodes/devices and the overall BBF network architecture, so that the DEs and their associated control-loops can be further designed to perform autonomic management and control of the specific resources (Managed Entities) in the target architecture. Based on this, the present document identifies the requirements for autonomic behaviours (Autonomics Functions/DEs) across the fixed broadband access and aggregation network segments of the BBF reference architecture and provides recommendations on where and how the GANA Functional Blocks (including DEs) should be instantiated. It further extends these recommendations to the virtualized manifestation of these segments considering their virtualized evolution in conjunction with SDN and NFV technologies. Finally, it also provides recommendations on the interworking and coordination between autonomic functions among GANA-BBF and GANA-3GPP (Core Network) domains, as well as recommendations on the Interworking and coordination between virtualized GANA-BBF and virtualized GANA-3GPP (Core Network) domains. |
103 476 | Environmental Engineering (EE); Circular Economy (CE) in Information and Communication Technology (ICT); Definition of approaches, concepts and metrics | TR | 1.1.2 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103476/01.01.02_60/tr_103476v010102p.pdf | The present document investigates current approaches, concepts and metrics of CE and RE and their applicability for the ICT infrastructure goods. The present document: 1) introduces CE and RE, 2) describes CE as used in the ICT industry, 3) describes existing CE and RE metrics and examples of their use, 4) proposes next steps in CE and RE standardization. The scope of the present document includes the following aspects: upgradability, reparability, removability, durability, reusability, recyclability, recoverability, refurbishability, manufacturability. The following additional parameters, indicators and metrics are included: recycled content, use of critical raw materials, proportion of re-used parts. The present document is revision of ETSI TR 103 476 (V1.1.1) [i.73]. It has the same technical content , but it clearly clarifies its relation to M/543 [i.2]. The first version [i.73] was prepared jointly by ETSI TC EE and ITU-T Study Group 5. It is published respectively by ITU and ETSI as Supplement ITU-T L.Suppl.28 [i.72] and the present document, which are equivalent in technical content. The present document provides a guide to CE aspects, parameters, metrics, indicators for ICT infrastructure goods. |
103 477 | eHEALTH; Standardization use cases for eHealth | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103477/01.03.01_60/tr_103477v010301p.pdf | The present document presents a number of typical use cases in the eHealth domain and their analysis to identify gaps in standardization. The analysis covers aspects of link connectivity, network interconnectivity, semantic and syntactic interoperability, security (risks and provisions) and the existence of standards to meet each aspect. Furthermore the analysis identifies actors and their roles, for each of primary, secondary and tertiary involvement in the use case. The use case examples have been drawn or informed by publications from industry, from completed FP7 and H2020 projects, from ETSI Technical Bodies, and from current eHealth and Health industry practices. The update in V1.2.1 of the present document added therapeutic use cases in addition to the baseline diagnostic use cases of the previous edition (V1.1.1), and the update in the present version (V1.3.1) adds consideration of data for machine based processing and non-clinical medical use cases. |
103 478 | Emergency Communications (EMTEL); Pan-European Mobile Emergency Application | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103478/01.03.01_60/ts_103478v010301p.pdf | The present document is divided into two parts. The first part provides the requirements and functional architecture while the second part provides the protocol and procedures for implementing the Pan-European Mobile Emergency Application (PEMEA). The first part identifies the key functional entities involved in the emergency application architecture, the interfaces between each functional entity, and the requirements on each interface. The second part defines the data exchanges, message, protocols and procedures used across each of the identified PEMEA interfaces. It is recognized that many existing application implementations combine the functional entities identified in the present document into a single entity. The most common example of combined functional entities is the combined Application Provider (AP) and PSAP Service Provider (PSP), these are common because it is often the PSAP that writes or engages a third-party to write a local emergency application that interfaces directly with the PSAP. The present document does not seek to disallow integrated node implementations, however, it does not define how additional applications or application providers using proprietary Application Programming Interfaces (APIs) and protocols can provide PEMEA extended features, such solutions are left to the integrated node providers. |
103 479 | Emergency Communications (EMTEL); Core elements for network independent access to emergency services | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103479/01.03.01_60/ts_103479v010301p.pdf | The present document describes the architecture, the core elements and corresponding technical interfaces for network independent access to emergency services. Elements are: Border Control Function (BCF), Emergency Service Routing Proxy (ESRP), Emergency Call Routing Function (ECRF), Public Safety Answering Point (PSAP), the Location Information Server (LIS), and the Call Transfer Bridge (BRIDGE). The described architecture is currently named Next Generation 112 architecture. |
103 482 | Speech and multimedia Transmission Quality (STQ); Framework for multi-service testing | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103482/01.01.01_60/tr_103482v010101p.pdf | The present document provides a framework for concurrent tests of multiple services, using a top-level approach which is also modular and scalable with respect to new services. Also, the framework explicitly integrates measurement methodology, in particular reproducibility aspects. |
103 484-1 | Smart Cards; Test specification for the Secure Channel interface; Part 1: Terminal features (Release 9) | TS | 9.0.0 | http://www.etsi.org/deliver/etsi_ts/103400_103499/10348401/09.00.00_60/ts_10348401v090000p.pdf | The present document covers the minimum characteristics which are considered necessary for the terminal or terminal and terminal application in order to provide compliance to TS 102 484 [1]. The present document specifies the test cases for the Secured APDU - Application to Application type of secure channel and includes tests for: • the characteristics of the Secure Channel interface between the UICC and the UICC-enabled terminal; • the Discovery and Channel Administration; • Key Agreement for Strong Pre-shared Keys - Proprietary Pre-Shared Keys; • the Channel Operation between the UICC-enabled terminal and the UICC. Both tests for Terminal capability and Terminal applications are specified. The following are out of scope of this document: • TLS- Application to Application. • IPsec - USB Class to USB Class. • Secured APDU - Platform to Platform. • Strong Pre-shared Keys - GBA key agreement. • Weak Pre-shared Keys - Proprietary Pre-Shared Keys key agreement. • Certificate Exchange key agreement. |
103 484-2 | Smart Cards; Test specification for the Secure Channel interface; Part 2: UICC features (Release 9) | TS | 9.0.0 | http://www.etsi.org/deliver/etsi_ts/103400_103499/10348402/09.00.00_60/ts_10348402v090000p.pdf | The present document covers the minimum characteristics which are considered necessary for the UICC or UICC and UICC application in order to provide compliance to TS 102 484 [1]. The present document specifies the test cases for the Secured APDU - Application to Application type of secure channel and includes tests for: • the characteristics of the Secure Channel interface between the UICC and the UICC-enabled terminal; • the Discovery and Channel Administration; • Key Agreement for Strong Pre-shared Keys - Proprietary Pre-Shared Keys; • the Channel Operation between the UICC-enabled terminal and the UICC. Both tests for UICC capability and UICC applications are specified. The following are out of scope of the present document: • TLS- Application to Application. • IPsec - USB Class to USB Class. • Secured APDU - Platform to Platform. • Strong Pre-shared Keys - GBA key agreement. • Weak Pre-shared Keys - Proprietary Pre-Shared Keys key agreement. • Certificate Exchange key agreement. |
103 485 | CYBER; Mechanisms for privacy assurance and verification | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103485/01.01.01_60/ts_103485v010101p.pdf | The present document defines the means to enable assurance of privacy, using the conventional CIA (Confidentiality, Integrity, Availability) paradigm and with reference to the functional capabilities for privacy protection described in Common Criteria for Information Technology Security Evaluation [1]. The present document addresses privacy assurance within the context of Identity Management following the model described in ETSI TS 103 486 [i.17]. The present document addresses the cases where both transient and persistent identifiers are used, and where identifiers are used in isolation and where identifiers are used in combination. The mechanisms defined in the present document have been informed by the requirements found in articles and recitals of the General Data Protection Regulation (EU) 2016/679 [i.6] (GDPR) and can be considered in assisting in achieving compliance to the requirements in GDPR. NOTE: The GDPR contains a very large number of requirements and the present document addresses only a very small number of the technical ones thus the present document is not a solution to the GDPR but where it may assist in addressing specific requirements this has been identified in the body of the present document. The present document identifies assurance protection levels for privacy and mechanisms for achieving those protection levels. It does not, however, provide any guarantee that application of the mechanisms will prevent abuse of private information and user privacy. |
103 231 | White Space Devices (WSD); Wireless Access Systems operating in the 470 MHz to 790 MHz TV broadcast band; Information on weblistings of TV White Space Databases (TVWSDBs) | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103200_103299/103231/01.01.01_60/tr_103231v010101p.pdf | The present document provides information on the status of implementation of TV White Space Databases (TVWSDs) under the regulatory framework of a regulatory domain. This information can be used by manufacturers as guidance to identify regulatory domains providing weblistings of TV White Space Databases (TVWSDBs) for the usage of TV White Space Devices (TVWSDs) in the 470 MHz to 790 MHz TV broadcast band. |
103 486 | CYBER; Identity Management and Discovery for IoT | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103486/01.01.01_60/ts_103486v010101p.pdf | The present document describes a model of secure and attestable identity management applicable to IoT devices. The present document defines a data structure, described as Authority-Attribute Trees, for managing identifiers and properties of a device (as attributes), where identifiers and properties are exposed in a number of use cases including discovery, attachment and communication. The present document outlines the requirements for cryptographic methods to establish trust in Authority-Attribute Trees. The present document does not define or make recommendations about policies for users or devices with regards to revealing identity information, or accepting or rejecting discovery based on this information. |
103 487 | CYBER; Baseline security requirements regarding sensitive functions for NFV and related platforms | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103487/01.01.01_60/ts_103487v010101p.pdf | The present document defines security baseline requirements for sensitive functions including lawful interception (LI) and retained data (RD) in an NFV hardware/platform environment. |
103 488 | Speech and Multimedia Transmission Quality (STQ); Guidelines on OTT Video Streaming; Service Quality Evaluation Procedures | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103488/01.01.01_60/tr_103488v010101p.pdf | The present document's scope is to provide guidance on OTT video streaming testing approach with a set of minimum desired and most meaningful QoE centric QoS parameters along with recommendations to create a figure of merit quantifying the OTT video streaming session quality, where possible. In addition, the set of introduced QoE centric QoS parameters aim to help with the identification of the possible roots of video quality degradation. The present document also offers means to understand aspects related with network and services optimization and troubleshooting, such as the trade-off between bandwidth usage or controlled throttling and end-to-end video quality. The scope of the present document complements ETSI TS 102 250-2 [i.1] and ETSI TR 101 578 [i.2] while not being as exhaustive, but rather focused on QoE centric characterization and an end-to-end view on the video streaming session as a whole. Furthermore, the present document takes into consideration QoE centric evaluation by means of passive, non-intrusive network monitoring of SSL/QUIC OTT Video Services bitstreams. In addition, the present document aims to complement the scope of ETSI TR 102 493 [i.3] with respect to QoE models for video streaming integrity as perceived by users. |
103 491 | DTS-UHD Audio Format; Delivery of Channels, Objects and Ambisonic Sound Fields | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103491/01.02.01_60/ts_103491v010201p.pdf | The present document describes a compressed audio delivery system comprised of a metadata component and a compressed audio component. This system is referred to as DTS-UHD. The stream and metadata structures described here allow efficient delivery of immersive audio. Additionally, the bitstream format of a new audio compression engine is defined. DTS-UHD supports delivery of Channel-Based Audio (CBA), Object-Based Audio (OBA) and High Order Ambisonic presentations up to the fourth order (HOA Soundfields). This support includes the metadata for signaling content, loudness and dynamics, and the necessary coefficients for rendering the final presentation. The present document is organized into two main parts, with clauses 4 through 7 describing the DTS-UHD metadata and some system interfaces, which is independent of the coding scheme being used. Clauses 8 through 10 describe the Audio Compression Engine (ACE), which is designed for efficient delivery of compressed audio in broadcast and streaming environments. |
103 492 | System Reference document (SRdoc); Critical Infrastructure Utility Operations requirements for Smart Grid systems, other radio systems, and future radio spectrum access arrangements below 1,5 GHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103492/01.01.01_60/tr_103492v010101p.pdf | The present document considers: 1) the essential functional requirements for existing and future radio systems suitable for controlling critical national infrastructure utility systems; and 2) the long-term spectrum requirements for critical national infrastructure utility systems. The present document does not include the high data rate microwave link backhaul requirements of the Smart Grids or satellite connectivity. Nor does it include any licence exempt spectrum requirements for Smart Meters or similar Smart systems. Access to those spectrum blocks are not expected to be an issue. Requirements for Smart Cities or Smart Homes are not within the scope of the present document. |
103 493 | System Reference document (SRdoc); Wireless Power Transmission (WPT) systems operating below 30 MHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103493/01.01.01_60/tr_103493v010101p.pdf | The present document provides information of existing and future wireless power transmission (WPT) systems using technologies other than radio frequency beam, operating in the frequency range below 30 MHz and complements the published ETSI TR 103 409 [i.20], which contains information about WPT systems for electrical vehicles (WPT-EV) in the frequency range 79 - 90 kHz. The related harmonised standard for WPT systems is ETSI EN 303 417 [i.11] and it currently applies to WPT technologies other than radio frequency beam, in the frequency ranges 19 - 21 kHz, 59 - 61 kHz, 79 - 90 kHz, 100 - 300 kHz and 6 765 - 6 795 kHz. During the development of ETSI EN 303 417 [i.11], concerns were raised whether the frequency allocations for inductive SRDs according to EC Decision 2013/752/EU [i.3] and the ERC/REC 70-03 [i.2], annex 9 are applicable for WPT systems. Therefore the present document aims to request CEPT to clarify whether the WPT systems using the inductive frequency range below 30 MHz could be seen as "inductive SRDs" and could use the frequency allocations from Decision 2013/752/EU [i.3] and the ERC/REC 70-03 [i.2], annex 9. The present document deals only with WPT based on technologies other than radio frequency beam (e.g. magnetic induction). It reviews the present regulations for inductive WPT systems, the related markets and the evolution of the technology, and it identifies requirements to amend the limits for WPT systems operating below 30 MHz. The present document contains the necessary information to support the possible co-existence and compatibility studies to be conducted by the CEPT/ECC, including: • market information; • technical information; • regulatory issues. |
103 494 | Broadband Radio Access Networks (BRAN); Study of central coordination of WAS/RLANs operating in the 5 GHz frequency band | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103494/01.01.01_60/tr_103494v010101p.pdf | The present document contains studies of the architectures and the protocols supporting the central coordination of WAS including RLANs (WAS/RLAN) operating in the 5 GHz bandIt also includes information provided by a radio node/network of radio nodes and the procedures for the coordination of the operation of these nodes. |
103 495 | Network Technologies (NTECH); Autonomic network engineering for the self-managing Future Internet (AFI); Autonomicity and Self-Management in Wireless Ad-hoc/Mesh Networks: Autonomicity-enabled Ad-hoc and Mesh Network Architectures | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103495/01.01.01_60/tr_103495v010101p.pdf | The present document aims to provide recommendations for the introduction of autonomics (management and control intelligence) into Ad-hoc and Mesh Network architectures and their associated management and control architectures. The present document describes: • Autonomicity-enabled Ad-hoc and Mesh Network Architecture that is a result of the instantiation of the GANA (Generic Autonomic Networking Architecture) Reference Model on the Ad-hoc and Mesh Network architecture to enable developers of autonomics to introduce autonomics in the architecture • Relevant autonomicity-enabled functions and operations • Relevant GANA Decision Elements (DEs) and Reference Points between those DEs The present document describes the specific desirable features for autonomic management and control of Ad-hoc and mesh network functions through the introduction of Decision Elements (DEs) and their associated control loops at the Network, Node and Function level of the GANA reference model. The Protocol level needed to be additionally addressed due to the need for accommodating the specifics of Ad-hoc and mesh set-ups. |
103 496 | Intelligent Transport Systems (ITS); Cooperative ITS (C-ITS) support for transport pollution management applications; Use cases and standardization study; Release 2 | TR | 2.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103496/02.01.01_60/tr_103496v020101p.pdf | The present document provides the overview of how C-ITS architecture and any V2X communication technology could be used to enable new type of transport emissions control and management applications. Based on the identification and analysis of major use cases, the report provides a recommendation for the extension of the existing ETSI ITS standards with new ITS applications reducing the environmental transport impact and improving the transport emissions control. |
103 498 | System Reference document (SRdoc); Short Range Devices (SRD) using Ultra Wide Band (UWB); Transmission characteristics; Technical characteristics for SRD equipment using Ultra Wide Band technology (UWB); Radiodetermination application within the frequency range 120 GHz to 260 GHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103498/01.01.01_60/tr_103498v010101p.pdf | The present document describes UWB radiodetermination applications within the frequency range 120 GHz to 260 GHz which may require a change of the present frequency designation/utilization within CEPT. The described UWB radiodetermination applications for future systems are split into the following classes and use cases: • object detection and classification/characterization; • motion, speed and presence detection; • distance measurement; • displacement measurement. The present document includes in particular: • market information; • technical information including expected sharing and compatibility issues; NOTE: The information on sharing and compatibility issues is required when new spectrum or new spectrum usage is requested. • regulatory issues. |
103 501 | Speech and multimedia Transmission Quality (STQ); Guidelines for the Measurement of Data Throughput on Devices connected to Mobile Networks | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103501/01.01.01_60/tr_103501v010101p.pdf | The present document provides a systematic overview of methods to measure throughput in mobile networks, with special focus on measurements using a viewpoint at, or close to, application level. Also, it provides a holistic, integrated view of the measurement process, which also includes a selection of methodologies according to intended goals of measurement, and also covers post-processing and data aggregation aspects. |
103 502 | Reconfigurable Radio Systems (RRS); Applicability of RRS with existing Radio Access Technologies and core networks; Security aspects | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103502/01.01.01_60/tr_103502v010101p.pdf | The present document shows a mapping of existing Radio Access Technologies (RATs) to the Reconfigurable Radio System (RRS) model in order to identify missing security requirements, in particular identify the boundary of an RRS Radio Application with regard to the security functions present in existing RAT. Recognizing that a RAT is not bound to a single link but may be supported by functions in the network the present document also considers the role of core networks in supporting any triggering of the Reconfigurable Equipment to reconfigure itself using a push mechanism. |
103 503 | Speech and multimedia Transmission Quality (STQ); Procedures for Multimedia Transmission Quality Testing with Parallel Task including Subjective Testing | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103503/01.02.01_60/tr_103503v010201p.pdf | The present document describes the methods for assessment of subjective audio (including speech) quality and speech intelligibility under parallel task condition. This approach can be used to evaluate the perceived listening quality or speech intelligibility in situations which better mimics real operation of the tested telecommunication equipment or algorithm. The present document describes possible parallel task generation and scenarios, the test design and reference conditions used to evaluate the quality or intelligibility subjectively. Several parallel task scenarios are covered: • Physically oriented. • Mentally oriented. • Hybrid. |
103 504 | Speech and multimedia Transmission Quality (STQ); Methods and procedures for evaluating performance of voice-controlled devices and functions: far talk voice assistant devices | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/103504/01.01.01_60/ts_103504v010101p.pdf | The present document defines test methods, performance metrics and requirements for the voice assistance functionality of devices, including devices meant to be used in far talk conditions. The methods include definition of: input speech signals, positional relations of talkers and devices; acoustic environment characterization and reproduction, including background noise and reverberation; and collection of performance characteristics and statistical analyses. The test methods, performance metrics and requirements of devices meant to be used in close and near talk conditions are out of scope. The voice call functionality of voice assistant devices are out of scope and covered by ETSI ES 202 738 (narrowband) [i.1], ETSI ES 202 740 (wideband) [i.2] and ETSI TS 102 925 (super-wideband) [i.3]. |
103 506 | SmartM2M; SAREF extension investigation; Requirements for Smart Cities | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103506/01.01.01_60/tr_103506v010101p.pdf | The present document specifies the requirements for an initial semantic model for the smart cities domain based on a limited set of use cases and from available existing data models. The present document has been developed in close collaboration with AIOTI, the H2020 Large Scale Pilots and with ETSI activities in the smart cities domain. Further extensions are envisaged in the future to cover different aspects in the smart cities domain, for example focusing in public equipment. The associated ETSI TS 103 410-4 [i.9] will define the ontology extension (i.e. the semantic model) for the smart cities domain based on the requirements and use cases specified in the present document. |
103 507 | SmartM2M; SAREF extension investigation; Requirements for industry and manufacturing domains | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103507/01.01.01_60/tr_103507v010101p.pdf | The present document specifies the requirements for an initial semantic model for industry and manufacturing domains based on a limited set of use cases and from available existing data model. It includes deployment and related services aspects. The present document is developed in close collaboration with AIOTI, the H2020 Large Scale Pilots and with ETSI activities in this domain. Further extensions are envisaged in the future to cover entirely the industry and manufacturing domains. The associated ETSI TS 103 410-5 [i.9] will define the extension (i.e. the semantic model) for the industry and manufacturing domains based on the requirements and use cases specified in the present document. |
103 508 | SmartM2M; SAREF extension investigation; Requirements for Automotive | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103508/01.01.01_60/tr_103508v010101p.pdf | The present document provides the requirements for an initial semantic model in the smart automotive domain based on a limited set of use cases and from available existing data models. The present document is developed in close collaboration with AIOTI, the H2020 Large Scale Pilots, with ETSI activities in the automotive domain and with oneM2M. Further extensions are envisaged in the future to cover entirely the smart automotive domain. The associated technical specification will define the extension (i.e. the semantic model) for the smart automotive domain (SAREF4AUTO) based on the requirements and use cases described in the present document. |
103 509 | SmartM2M; SAREF extension investigation; Requirements for eHealth/Ageing-well | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103509/01.01.01_60/tr_103509v010101p.pdf | The present document provides requirements for an initial semantic model extending SAREF for eHealth/Ageing-well. This initial SAREF extension is based on a limited set of use cases and existing data models identified within available initiatives that are summarized in dedicated clauses of the present document. The conducted work is expected to be developed in close collaboration with in particular ETSI (in particular EP eHealth and TC SmartBAN), oneM2M, AIOTI (in particular WG 05 "Smart Living Environment for Ageing Well"), and the H2020 Large Scale Pilots (ACTIVAGE project). Other initiatives coming from eHealth/Ageing-well industrial/medical world and alliances (e.g. HL7, PCHAlliance) will also be investigated. Further extensions are envisaged in the future for entirely covering the eHealth/Ageing-well domain. |
103 510 | SmartM2M; SAREF extension investigation; Requirements for Wearables | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103510/01.01.01_60/tr_103510v010101p.pdf | The present document lists the requirements for an initial semantic model extending SAREF for the wearables domain. This initial SAREF extension will be based on both a limited set of use cases and available existing data models. The present document is developed in close collaboration with ETSI activities in the wearables and eHealth domains, SmartM2M/oneM2M, and Wearables related EU projects and H2020 Large Scale Pilots. Further extensions are planned in the future to cover entirely the wearables domain. |
103 511 | SmartM2M; SAREF extension investigation; Requirements for AgriFood domain | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103511/01.01.01_60/tr_103511v010101p.pdf | The present document specifies the requirements for an initial semantic model for smart agriculture and food chain domain (AgriFood) based on a limited set of use cases and from available existing data models. The present document is developed in close collaboration with AIOTI, the H2020 Large Scale Pilots and with ETSI activities in the smart agriculture and food chain domain. Further extensions are envisaged in the future to cover entirely the smart agriculture and food chain domain. The associated ETSI TS 103 410-6 [i.13] will define the extension (i.e. the semantic model) for the smart agriculture and food chain domain based on the requirements and use cases specified in the present document. |
103 267 | SmartM2M; Smart Applications; Communication Framework | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/103200_103299/103267/02.01.01_60/ts_103267v020101p.pdf | The present document defines a framework for Smart Applications communication based on oneM2M specifications. It also provides adjustments as required by the interested stakeholders. The present document includes: • An introduction to the oneM2M framework and its relation with the ETSI M2M one. • The specification of the interworking framework for Smart Applications with normative reference to oneM2M specifications. • The specification about how to interwork with the oneM2M framework. |
103 514 | Digital Enhanced Cordless Telecommunications (DECT); DECT-2020 New Radio (NR) interface; Study on Physical (PHY) layer | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103514/01.01.01_60/tr_103514v010101p.pdf | The present document aims on studying "DECT-2020: New Radio", a new radio interface based on state of the art paradigms able to offer the required data rates, propagation characteristics and spectrum efficiency, while maintaining compatibility with the carrier and time structure of the DECT band. The present document is focused on the Physical layer. DECT-2020, as defined by the present document, will be based on OFDM and may support space multiplexing (MIMO). The study focuses on: 1) Review of use cases and key application areas for DECT-2020. 2) Identification of methodology, initial sources, simulation tools and models. 3) Initial definition of "DECT-2020: New Radio" PHY layer, providing guidance for a following technical specification. 4) Preliminary simulation results and preliminary study on spatial multiplexing (MIMO). |
103 515 | Digital Enhanced Cordless Telecommunications (DECT); Study on URLLC use cases of vertical industries for DECT evolution and DECT-2020 | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103515/01.01.01_60/tr_103515v010101p.pdf | The present document presents a study of use cases and vertical scenarios for Ultra-Reliable Low-Latency Communications (URLLC) intended to be used as base requirements for evolving DECT. The proposed use cases can be classified as belonging to the following three major application areas: • Home and Building Automation, including Smart Living; • Industry automation - Factories of the Future, Industry 4.0; • Media and entertainment industry - Programme Making and Special Events (PMSE). The identified scenarios are intended to be implementable under 5G technology assumptions and timeframe. However some of them may also be implementable enhancements of current DECT technology. By 5G technology assumptions, it is meant state of the art radio interfaces based on OFDM with optional use of MIMO. The present document also describes the methodology and sources used for the identification of use cases, and describes the required DECT standard specifications for the implementation of the different evolution paths. The present document is a preparation of follow-up technical specifications within DECT, DECT ULE, DECT evolution and DECT-2020. |
103 517 | System Reference document (SRdoc); Short Range Devices (SRD) using Nuclear Magnetic Resonance (NMR); Technical characteristics for SRD equipment using Nuclear Magnetic Resonance (NMR) technology in the frequency range 0,1 kHz to 130 MHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103517/01.01.01_60/tr_103517v010101p.pdf | The present document provides information on NMR systems operating in the frequency range below 130 MHz. It deals only with NMR systems using earth magnetic field strength of rare earth magnets and electromagnets and not with superconducting magnets. This limits the maximum static magnetic field strength to less than 3 Tesla. As a direct result, the maximum proton nuclear magnetic resonance is limited to less than 130 MHz. The minimum nuclear resonances of nuclei in scope are below 1 kHz in earth magnetic field. There are two types of NMR devices: 1) "enclosed NMR sensor": Material under Test is put inside the device; 2) "open NMR sensor": - material under Test is placed on the device; - opened to one side for measurement of building materials like a GPR or WPR generating wanted field emission at the sensor boundaries; - opened 360°, e.g. like a pole inside a Material under Test generating wanted field emission at the sensor boundaries; - there is no enclosure around the sensor, called "open NMR sensor". Only "enclosed NMR" sensors" are in the scope of the present document. Nuclear Magnetic Resonance Imaging (MRI) and Magnetic Resonance Tomography (MRT) systems are out of scope. It reviews the present regulations for NMR systems (if any), the related markets and the evolution of the technology and it identifies limits for NMR systems operating below 130 MHz. The present document contains the necessary information to support the possible co-existence and compatibility studies to be conducted by the CEPT/ECC, including: • market information; • technical information; • regulatory issues. |
103 521 | 5 GHz RLAN; Receiver Blocking Performance | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/103521/01.01.01_60/ts_103521v010101p.pdf | The present document specifies Receiver Blocking for 5 GHz RLAN devices. |
103 523-1 | CYBER; Middlebox Security Protocol; Part 1: MSP Framework and Template Requirements | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352301/01.01.01_60/ts_10352301v010101p.pdf | The present document is the first part of the Middlebox Security Protocol (MSP) series [i.22]. It is intended to be used by MSP profile developers, MSP profile implementors and MSP specification writers to create MSP profiles and analyse their security. The present document does not specify an MSP profile itself. The present document defines a security baseline that MSP profiles fulfil to be included in the MSP series. This baseline (defined via the MSP Framework and MSP Template Requirements) facilitates creation of MSP profiles for a wide array of implementations and applications, by simplifying the security analysis required for each profile. The present document is intended to be a human-readable guide to the security methodology and principles applied to create the MSP Framework and resulting MSP Template Requirements (see Clauses 6.2 to 6.5). Clause 5 and Clause 6, together with profile-specific analysis, form the security analysis for the MSP series. The present document is not and does not attempt to be a security proof; security proofs are only as strong as the assumptions made [i.20] and can lead to a false sense of security [i.25]. The present document describes the motivations behind MSP's creation, how MSP differs to previous middlebox protocols and some of MSP's architectures. The present document introduces the MSP Framework: a common set of security provisions that underpins all MSP specifications (MSP Template Requirements). The present document describes the motivation for having such a framework, the issues addressed by it and the four principles that guided its creation. The remainder of the present document defines the usage and applicability of the MSP Framework to subsequent parts of the MSP series: how the MSP Framework is to be used by MSP profile developers, MSP profile implementors and MSP specification writers. The present document includes informative annexes to aid readers in its usage. Annex A contains a non-exhaustive list of use cases for MSP. Annex B contains an exemplar MSP Conformance Analysis, performed against the Enterprise Transport Security (ETS) profile, ETSI TS 103 523-3 [i.6]. Annex C describes how a traditional TLS split proxy does not meet the MSP standard set out in the present document. Comprehensive mitigations for all potential attacks are out of scope. Security requirements of generic and well-known cryptographic algorithms, and assessment of security properties of cryptographic primitives, are out of scope. Attacks that are not attacks on the MSP specification itself, such as implementation vulnerabilities, are out of scope. |
103 523-2 | CYBER; Middlebox Security Protocol; Part 2: Transport layer MSP, profile for fine grained access control | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352302/01.02.01_60/ts_10352302v010201p.pdf | The present document specifies a protocol to enable secure transparent communication sessions between network endpoints with one or more middleboxes between these endpoints, using data encryption and integrity protection, as well as authentication of the identity of the endpoints and the identity of any middlebox present. This protocol can be mapped to the abstract MSP protocol capability requirements in ETSI TS 103 523-1 [i.5]. The Middlebox Security Protocol builds on TLS 1.2 [1] and is an extensively modified version of the mcTLS protocol [i.1]. Whilst basic concepts are inherited from the mcTLS variant, the protocol specified in the present document also contains significant additional functionality and feature changes that would render it incompatible with the original version published. The present document focuses on TLMSP usage with TCP as it is the most common usage. Usages with other transport protocols are possible but left out of scope. In the remainder of the present document, unless otherwise noted, the word TLS refers to TLS 1.2 [1]. The present document defines a set of five sub-protocols for specific purposes: Handshake (authenticating endpoints and middleboxes and negotiating cryptographic configuration among those entities); Alert (signalling errors and notifications); Application (carrying data generated by higher layers); ChangeCipherSpec (signalling the activation of the negotiated cryptographic configuration) and a Record protocol, (responsible for applying the activated security configuration to all of the other aforementioned sub-protocols). Since TLMSP is a generic protocol, usable with a wide range of applications, issues related to mapping of application-specific security policy to explicit configurations of TLMSP is largely left out of scope. Further, out-of-band provisioning aspects relating to policies, pre-configuration of the client, details on actions in error situations are also out of scope. While some informal discussion on the security properties of TLMSP is provided, a complete (formal) security analysis of the protocol is currently left out of scope. A reference implementation of TLMSP is being developed and can be accessed at [i.7]. |
103 523-3 | CYBER; Middlebox Security Protocol; Part 3: Enterprise Transport Security | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352303/01.03.01_60/ts_10352303v010301p.pdf | The present document specifies the "Enterprise Transport Security" profile to enable secure communication sessions between network endpoints whilst enabling network operations. The Enterprise Transport Security (ETS) profile enables use of Transport Layer Security (TLS) version 1.3 [2] in, for example, compliance constrained environments. The present document describes three Enterprise Transport Security architectures: • In the first architecture, both the TLS 1.3 client and the Enterprise Transport Security server are located inside the enterprise. • In the second architecture, the server is an Enterprise Transport Security server inside the enterprise and the TLS 1.3 client is external to the enterprise. TLS 1.3 is terminated at the enterprise edge such that Enterprise Transport Security is used only inside the enterprise. • In the third architecture, the TLS 1.3 server is external to the enterprise and the TLS 1.3 client is internal to the enterprise. TLS 1.3 is again terminated at the network edge such that Enterprise Transport Security is used only inside the enterprise. The Diffie-Hellman key exchange and visibility information for indicating the Enterprise Transport Security profile setup is specified. The actions of the client on receiving the visibility information and structure of the policy included in the visibility information are not normatively defined; however, capabilities for an "Enterprise Transport Security aware client" are defined in annex B, which is optional. The means by which the Enterprise Transport Security endpoints share the Diffie-Hellman key with key consumers is specified, and examples are provided. The present document describes a variant of the Enterprise Transport Security profile in annex A for circumstances in which visibility information is not suitable and in which the client operator has been informed by other means that connections can be inspected. The means by which the client operator is informed is out of scope. The present document also includes the security assurances made by the Enterprise Transport Security profile, based on the security assurances of TLS 1.3. Annex C gives details of the MSP profile capabilities that are applicable to the Enterprise Transport Security profile, taken from the draft specification of ETSI TS 103 523-1 [i.1], such that this MSP Part may be a standalone document. A final mapping of MSP profile capabilities to the Enterprise Transport Security profile is left to a future version of the present document. |
103 523-5 | CYBER; Middlebox Security Protocol; Part 5: Enterprise Network Security | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352305/01.01.01_60/ts_10352305v010101p.pdf | The present document specifies a protocol implementation profile to enable secure communication between IPsec-protected network endpoints while enabling network operations. The Enterprise Network Security profile depends on two protocols in the IPsec family of protocols. First, Internet Key Exchange Protocol Version 2 (IKEv2) [1] is used to establish Security Associations (SAs). In this profile, when certificates are used to provide authentication in IKEv2, those certificates include an extension to provide notice that this profile is being used. Second, the IP Encapsulating Security Payload (ESP) [i.2] is used to encrypt packets. This profile describes two deployment scenarios. In the first one, one of the IPsec peers is inside the enterprise and the other one is outside the enterprise. In the other scenario, both IPsec peers are inside the enterprise. This profile describes the Diffie-Hellman key exchange, and it specifies the certificate extension that provides visibility information to indicate that the ENS profile is being used. The actions the IPsec peers take upon receiving the visibility information in the certificate extension and structure of the policy included in the visibility information are not normatively defined; however, capabilities for an optional "Enterprise Network Security aware IPsec peer" are defined. The means by which the IPsec endpoints obtain the longer- lived Diffie-Hellman public/private key pairs is specified, and some examples are provided. A variant of the ENS profile is also provided to enable visibility in circumstances where the operator of an IPsec peer has been informed by other means that packets can be decrypted and inspected. The present document also includes the security guarantees made by the ENS profile, based on the security guarantees of the IPsec family of protocols. |
103 524 | System Reference document (SRdoc); Wireless access systems including radio local area networks (WAS/RLANs) in the band 5 925 MHz to 6 725 MHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103524/01.01.01_60/tr_103524v010101p.pdf | The System Reference Document provides information on the intended applications, the technical parameters, mitigation techniques, the relation to the existing spectrum regulation and additional new radio spectrum requirements for Wireless access systems including radio local area networks (WAS/RLANs). The SRdoc contains information to support the CEPT activities resulting from Work Item SE45_1 (covering the band 5 925 MHz to 6 425 MHz). In addition, the present document contains a request for considering additional frequencies up to 6 725 MHz. The document includes the necessary information to support the co-operation between ETSI and the Electronic Communications Committee (ECC) of the European Conference of Post and Telecommunications Administrations (CEPT). |
103 525-1 | Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 1: Protocol Implementation Conformance Statement (PICS); Release 2 | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352501/02.01.01_60/ts_10352501v020101p.pdf | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specifications for security algorithms as specified in ETSI TS 102 941 [1] and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 406 [i.3]. |
103 525-2 | Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 2: Test Suite Structure and Test Purposes (TSS & TP); Release 2 | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352502/02.01.01_60/ts_10352502v020101p.pdf | The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology. |
103 525-3 | Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT); Release 2 | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10352503/02.01.01_60/ts_10352503v020101p.pdf | The present document provides parts of the Abstract Test Suite (ATS) for ITS PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to provide a basis for conformance tests for security communication over GeoNetworking equipment in order to guarantee interoperability between different manufacturers' equipment. The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology. |
103 526 | System Reference document (SRdoc); Technical characteristics for Low Power Wide Area Networks Chirp Spread Spectrum (LPWAN-CSS) operating in the UHF spectrum below 1 GHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103526/01.01.01_60/tr_103526v010101p.pdf | The present document describes the LPWAN-CSS (Low Power Wide Area Networks - Chirp Spread Spectrum) system, and aims to respond a CEPT ECC Working Group Frequency Management request to better understand the LPWAN-CSS characteristics in view of allowing spectrum considerations for conventional SRDs and SRD networks healthy sharing. It includes in particular: • Market information. • Technical information (including expected sharing and compatibility issues). • Regulatory considerations. |
103 527 | SmartM2M; Virtualized IoT Architectures with Cloud Back-ends | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103527/01.01.01_60/tr_103527v010101p.pdf | The present document: • makes a description of some use cases that benefit from virtualization and outlines which one will be used for the Proof-of-Concept that is described in depth in ETSI TR 103 529 [i.2]; • addresses the rationale and requirements for the use of virtualization - and of the cloud in general - in support of IoT systems. It also introduces some features that will be key for the definition and further implementation of virtualized IoT systems such as microservices; • provides the identification of new architectural elements (components, mappings, Application Programming Interfaces (API), etc.) that are required to address IoT on a cloud back-end. In particular, one objective of the present document is to describe how current IoT nodes e.g. the oneM2M CSE, can be modified and improved by the introduction of micro-services. |
103 528 | SmartM2M; Landscape for open source and standards for cloud native software applicable for a Virtualized IoT service layer | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103528/01.01.01_60/tr_103528v010101p.pdf | The present document: • Recalls the main elements of the High-Level Architecture (HLA) in support of IoT Virtualization as it is described in ETSI TR 103 527 [i.1] and how Open Source Software (OSS) and Standards can be used in the implementation of virtualized IoT systems. • Presents, for each of the layers (and sub-layers) of the HLA, several of the OSS components that have been developed by the open source communities. • Presents on-going developments in standardization that can be used in support of such implementations. |
103 529 | SmartM2M; IoT over Cloud back-ends: A Proof of Concept | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103529/01.01.01_60/tr_103529v010101p.pdf | The present document: • Recalls the main elements of the Proof-of-Concept (PoC) in support of IoT Virtualization: use case description, high-level architecture of the application developed, main technical choices. • Presents the main implementation choices. • Outlines the lessons learned and the possible impact of future IoT Virtualization implementations. |
103 531 | Environmental Engineering (EE); Impact on ICT equipment architecture of multiple AC, -48 VDC or up to 400 VDC power inputs | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/103531/01.02.01_60/ts_103531v010201p.pdf | The present document is applicable to the case of multiple power feeding configurations at the input of ICT equipment in ICT system. The present document describes the combination of three power interfaces as A1 (AC), A (-48 VDC), P or A3 (up to 400 VDC) that could potentially be used single or in combination for each input. The present document also provides details of the power structure within the ICT equipment, between the ICT equipment interfaces and ICT equipment system loads that is inclusive of system power converters. The input power configurations are categorized to allow for better understanding and identification of each new multiple power feeding interface, providing details of the impacts and benefits of adopting them. Information is also provided on the impact on battery test function when used with the different dual power inputs combinations. Lastly requirements are given for avoiding the potential risk of voltage back feeding from one input to the other and for general isolation requirements in all multiple power feeding configurations. |
103 532 | CYBER; Attribute Based Encryption for Attribute Based Access Control | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/103532/01.02.01_60/ts_103532v010201p.pdf | The present document specifies trust models, functions and protocols using attribute based encryption as a foundation of an attribute based access control scheme. It covers both the Ciphertext-Policy (CP-ABE) and Key-Policy (KP-ABE) variants of Attribute-Based Encryption. The specifications address the following aspects: • Identification of an ABE scheme covering both the Ciphertext-Policy and Key-Policy variants. • Definition of interactions between the data sources, the service providers and the authority releasing attributes and key material. • Mechanisms for keys, policies, and attributes distribution. • Mechanisms for secret key expiration and revocation. • Definition of semantics for a basic set of attributes to ensure interoperability. • Mapping to a standard Public Key Infrastructure X.509. • Mapping to a standard assertion protocol (SAML). • Definition of a policy schema for data access control. • Identification of limitations compared to traditional ABAC features. • Translation rules to XACML. • Definition of new protocol bindings when existing bindings do not cover the deployment scenario (e.g. a CoAP binding for the IoT case). |
103 533 | SmartM2M; Security; Standards Landscape and best practices | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf | |
103 534-1 | SmartM2M; Teaching material; Part 1: Security | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/10353401/01.01.01_60/tr_10353401v010101p.pdf | |
103 534-2 | SmartM2M; Teaching material; Part 2: Privacy | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/10353402/01.01.01_60/tr_10353402v010101p.pdf | |
103 535 | SmartM2M; Guidelines for using semantic interoperability in the industry | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103535/01.01.01_60/tr_103535v010101p.pdf | |
103 536 | SmartM2M; Strategic/technical approach on how to achieve interoperability/interworking of existing standardized IoT Platforms | TR | 1.1.2 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103536/01.01.02_60/tr_103536v010102p.pdf | |
103 450 | System Reference document (SRdoc); Technical characteristics and parameters for Wireless Multichannel Audio Systems (WMAS) | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/103400_103499/103450/01.02.01_60/tr_103450v010201p.pdf | The present document describes the necessary technical background information on Wireless Multichannel Audio System (WMAS). It includes in particular: • Market information. • Technical information including expected sharing and compatibility issues. • Regulatory issues. |
103 155 | Speech and multimediaTransmission Quality (STQ); Frequency responses of different Mouth simulators and Head And Torso Simulators (HATS) | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103100_103199/103155/01.01.01_60/tr_103155v010101p.pdf | The present document presents measurement results of various mouth simulators as well as Head And Torso Simulators (HATS). These measurements have been produced in the context of a study related to the extension of HATS use in super wide band (SWB). These measurement results are presented for information purpose. |
103 540 | Environmental Engineering (EE); Mobile Network (MN) Energy Consumption (EC) estimation method; Energy estimation method based on statistical approach | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103540/01.01.01_60/tr_103540v010101p.pdf | The present document is aimed to define an estimation method for anticipating the total energy consumption of a radio access network based on measuring energy consumption of a few randomly chosen sites. The present document is used when measuring energy consumption of the whole network is either impossible or costly to an operator. Two different methods have been presented in the present document , one based on Basic Estimation Method and another based on stratified Estimation Method. The present document deals with any type of radio access network such as homogeneous and heterogeneous network and technologies such as GSM, UMTS and LTE. The estimation of energy consumption User Equipment (UE) is not within the scope of the present document. |
103 541 | Environmental Engineering (EE); Best practice to assess energy performance of future Radio Access Network (RAN) deployment | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103541/01.01.01_60/tr_103541v010101p.pdf | The aim of the present document is to find and describe methods and best practice to assess energy performance (Energy Consumption and Energy Efficiency) of a future RAN deployment. The results documented will include a summary of previous work, a collection of important preconditions as traffic aspects (growth, new traffic classes, potential disruption), collection of energy efficiency/saving solutions and strategies and energy issues in current networks. Network energy performance assessment method examples based on set of scenarios including different solutions. The assessment period is at least until 2020, optionally also including 5G impact. Energy consumption and efficiency definitions from ETSI ES 202 706 [i.18] and ETSI ES 203 228 [i.19] are preferred. |
103 542 | Environmental Engineering (EE); Study on methods and metrics to evaluate energy efficiency for future 5G systems | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103500_103599/103542/01.01.01_60/tr_103542v010101p.pdf | The present document analyses the energy efficiency issues for the future 5G systems, object of standardization in 3GPP and ITU and foreseen to be available from 2018 in various countries. The focus is about methods and metrics to measure energy efficiency in 5G systems, considering the degree of stability of the systems known so far and the experience of the legacy systems and the related measurement procedures. In this approach, the present document will rely on the existing standards for legacy radio systems, especially ETSI ES 202 706 [i.1] and [i.2] for single base station measurements in a laboratory environment and ETSI ES 203 228 [i.3] for access network aggregate measurements of energy efficiency. These standards are currently studying 2G, 3G and 4G energy efficiency topics. Moreover, the present document considers also the state of the art in 5G energy efficiency studies to elaborate a first view on 5G, to be further agreed for the possible future development towards a new standard of Energy Efficiency evaluation for 5G future systems. |
103 543 | Mobile Standards Group (MSG); Pan-European eCall In-Vehicle Systems; Guidelines for IVS conformity assessment | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/103543/01.01.01_60/ts_103543v010101p.pdf | The scope of the present document is to provide technical guidelines for assessing device conformity to Pan-European eCall (according to CEN EN 16072:2015 [i.2]) and essential performance (CEN EN 16072 [i.3], ETSI TS 103 428 [i.4] and CEN EN 15722:2015 [i.6]). The present document compiles existing test cases / procedures and guides device suppliers and integrators by differentiating between regulatory and functional test cases. The resulting compilation of test procedures is a guideline towards regulatory conformance declaration mandated by the EU commission and IVS full functional conformance self-declaration in regards to Pan-European eCall. This assessment is also seen as a suitable preparation for the type approval homologation. The main purpose of the present document is to: a) Analyse existing regulations on Pan European eCall and provide a conformance relevant list of test cases based on existing specifications. b) Guide device supplier and integrators by evaluating test case relevance (regulatory and functional). This provides an efficient method for indication of Pan-European eCall conformance. c) Assist device suppliers and integrators in the vehicle type approval homologation. |
103 544-1 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 1: Connectivity | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354401/01.03.01_60/ts_10354401v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The connectivity between the MirrorLink Server and Client is the basis to provide interoperability between both. The Connectivity stack is specified in the following, starting from the low layer and going up the protocol stack. It is not the objective of the present document to provide a detailed overview of the different protocols. Instead the present document highlights the components and parameters required to ensure proper connectivity. The connectivity solution is built purely on existing wireless and wired standards. Therefore, detailed information is available in the respective documents. |
103 544-10 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 10: UPnP Client Profile Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354410/01.03.01_60/ts_10354410v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The TmClientProfile service is a UPnP service that allows control points to register client profiles with the MirrorLink Server device and notifies it regarding MirrorLink Client preferences, settings and capabilities, which is be used for governing the interaction between the MirrorLink Server and the Client. |
103 544-11 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 11: UPnP Notification Server Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354411/01.03.01_60/ts_10354411v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The TmNotificationServer service is an UPnP service that allows control points to receive diverse notifications from the devices that support the TmNotificationServer service. The TmNotificationServer service enables the following features to: • send a notification to the head unit; • get an action described in the notification. |
103 544-12 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 12: UPnP Server Device | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354412/01.03.01_60/ts_10354412v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document defines the device: urn:schemas-upnp-org:device:TmServerDevice:1. This device can be a UPnP root device or embedded within a different device. The TmServerDevice encapsulates all services for the MirrorLink UPnP Server Device Control Protocol (DCP). |
103 544-13 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 13: Core Architecture | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354413/01.03.01_60/ts_10354413v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document defines the core MirrorLink architecture, linking the different MirrorLink related protocols together, and providing MirrorLink session management related information. |
103 544-14 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 14: Application Certificates | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354414/01.03.01_60/ts_10354414v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. MirrorLink provides the ability to run certified applications on MirrorLink server devices that can be launched from the MirrorLink client device. In order to improve safety and ensure a quality user experience, an application certification program is implemented that will control, which applications can be used with MirrorLink in drive on in non-drive situations. |
103 544-15 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 15: Application Programming Interface (API) Level 1 & 2 | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354415/01.03.01_60/ts_10354415v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The MirrorLink API specifies an interface to the MirrorLink Server, which allows any application to either get information about MirrorLink Server's or Client's properties or to set them to specific values. In addition, the API specifies callback functions, which are used from the MirrorLink Server to inform the application about any change. |
103 544-16 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 16: Application Developer Certificates | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354416/01.03.01_60/ts_10354416v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. MirrorLink provides the ability to run certified applications on MirrorLink server devices that can be launched from the MirrorLink Client device. In order to improve safety and ensure a quality user experience, an application certification program is implemented that will control which applications can be used with MirrorLink in drive on in non-drive situations. Application developers will be able to use specific application development certificates, which simplifies the development of applications on the one side, but which will be usable only on a small set of MirrorLink Server devices - as well as a potentially restricted set of MirrorLink Client devices. |
103 544-17 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 17: MirrorLink® over Wi-Fi Display (WFD) | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354417/01.03.01_60/ts_10354417v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present specification describes the integration of Wi-Fi Display to MirrorLink. |
103 544-18 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 18: IEEE 802.11TM Car Connectivity Consortium (CCC) Information Element | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354418/01.03.01_60/ts_10354418v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. IEEE allows defining vendor-specific Information elements, which are used to carry information not defined in the IEEE standard within a single defined format. The IE (Information Element) is located at the end of management frames, such as the beacon frame defined in IEEE 802.11 [1]. Multiple IEs can be concatenated. Based on the usage of IE, IEEE defines the formats of different kinds of IEs identified by the Element ID. The present document specifies the IEEE 802.11 [1] CCC vendor-specific Information Element. |
103 544-19 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 19: Network Information Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354419/01.03.01_60/ts_10354419v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document specifies Network Information Data Service based on SBP (Service Binary Protocol) framework [i.2]. The service is used to provide network capabilities and status information of Access Point to Client. |
103 544-2 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 2: Virtual Network Computing (VNC) based Display and Control | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354402/01.03.01_60/ts_10354402v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The contents of the MirrorLink Server device's screen are transferred to the MirrorLink Client device. The control inputs are transferred from the MirrorLink Client to the MirrorLink Server. Screen copy methods can be used to copy the content of the MirrorLink Server's framebuffer to the MirrorLink Client's display. The copy operation can include rotation or colour conversion. The frame buffer is used as an abstraction layer, allowing any changes to the applications and services running on the mobile device to be avoided. For this purpose, the Virtual Networking Computing (VNC) protocol is used. |
103 544-20 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 20: Internet Accessibility | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354420/01.03.01_60/ts_10354420v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document specifies MirrorLink Device Discovery on Wi-Fi Direct. The procedure is used to provide MirrorLink Server and Client's Internet configuration prior to Wi-Fi P2P group formation. |
103 544-21 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 21: High Speed Media Link (HSML) | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354421/01.03.01_60/ts_10354421v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document describes the High-Speed Media Link, a video transmission mechanism that utilizes the USB to project the screen of one device onto another device with a larger screen. |
103 544-22 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 22: Android Specific Specifications enabling AIDL-based MirrorLink® Applications | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354422/01.03.01_60/ts_10354422v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document provides the elements of the MirrorLink specification that apply only to Android MirrorLink Server devices. The API javadoc files contained in the archive CCC-TS-065_Mirrorlink_API-Level2-AIDL-files__v138.zip, contained in ts_10354422v010301p0.zip, are an integral part of the present document. |
103 544-23 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 23: Bluetooth® Out-of-Band Pairing Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354423/01.03.01_60/ts_10354423v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The purpose of the Automatic Bluetooth Pairing feature is to eliminate the complexity of Bluetooth Pairing an IVI with a the MirrorLink connected phone by utilizing the trusted MirrorLink connection as a Bluetooth Out of Band (OOB) pairing transport. Some potential benefits include: • Single connection (USB or Wi-Fi) user configuration of a complete MirrorLink connection. • Obfuscation of protocol/transport complexity from the user (USB/Wi-Fi + Bluetooth). • More security around information used for link key generation due to OOB information exchange. • Net-neutral cost to enable OOB pairing on head units that already include USB ports. The MirrorLink Secure Bluetooth Out-of-Band pairing using MirrorLink CDB/SBP is modelled after Bluetooth Out-of- Band pairing using NFC. |
103 544-24 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 24: Media Meta Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354424/01.03.01_60/ts_10354424v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. Current MirrorLink solutions are concentrated on utilization of MirrorLink Client’s main display to mirror applications or provide variety services on the MirrorLink Server. However, there are so many MirrorLink Clients which have several other displays, such as cluster display panel, Heads-up Display (HUD) and so on. Instead of applications mirroring, using these displays, the driver and the passenger can be provided with a variety meta information such as turn by turn information, photo or graphic information, meta data information of audio and video clip, text information, etc. Those Meta Information Data Services are based on the SBP (Service Binary Protocol) framework. The present document specifies media meta data service based on SBP (Service Binary Protocol) framework. By receiving this data, the MirrorLink Client (e.g. a car) can provide media information to driver and passenger e.g. through the car's cluster display panel, or heads-up display. |
103 544-25 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 25: Navigation Meta Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354425/01.03.01_60/ts_10354425v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. Current MirrorLink solutions are concentrated on utilization of MirrorLink Client's main display to mirror applications or provide variety services on the MirrorLink Server. However, there are so many MirrorLink Clients which have several other displays, such as cluster display panel, Heads-up Display (HUD) and so on. Instead of applications mirroring, using these displays, the driver and the passenger can be provided with a variety meta information such as turn by turn information, photo or graphic information, meta data information of audio and video clip, text information, etc. Those Meta Information Data Services are based on the SBP (Service Binary Protocol) framework. The present document specifies navigation meta data service based on SBP (Service Binary Protocol) framework. By receiving this data, the MirrorLink Client (e.g. a car) can provide navigation information to driver and passenger e.g. through the car's cluster display panel, or heads-up display. |
103 311-2 | Integrated broadband cable telecommunication networks (CABLE); Fourth Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 2: Physical Layer; DOCSIS® 3.1 | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/103300_103399/10331102/01.01.01_60/ts_10331102v010101p.pdf | The present document is part of a series of specifications that defines the fourth generation of high-speed data-over-cable systems, commonly referred to as the DOCSIS 3.1 specifications. The present document was developed for the benefit of the cable industry, and includes contributions by operators and vendors from North and South America, Europe and Asia. This generation of the DOCSIS specifications builds upon the previous generations of DOCSIS specifications (commonly referred to as the DOCSIS 3.0 and earlier specifications), leveraging the existing Media Access Control (MAC) and Physical (PHY) layers, but with the addition of a new PHY layer designed to improve spectral efficiency and provide better scaling for larger bandwidths (and appropriate updates to the MAC and management layers to support the new PHY layer). It includes backward compatibility for the existing PHY layers in order to enable a seamless migration to the new technology. There are differences in the cable spectrum planning practices adopted for different networks in the world. For the new PHY layer defined in the present document, there is flexibility to deploy the technology in any spectrum plan; therefore, no special accommodation for different regions of the world is required for this new PHY layer. However, due to the inclusion of the DOCSIS 3.0 PHY layers for backward compatibility purposes, there is still a need for different region-specific physical layer technologies. Therefore, three options for physical layer technologies are included in the present document, which have equal priority and are not required to be interoperable. One technology option is based on the downstream channel identification plan that is deployed in North America using 6 MHz spacing. The second technology option is based on the corresponding European multi-program television distribution. The third technology option is based on the corresponding Chinese multi-program television distribution. All three options have the same status, notwithstanding that the document structure does not reflect this equal priority. The first of these options is defined in clauses 5 and 6, whereas the second is defined by replacing the content of those sections with the content of Annex C. The third is defined by replacing the content of those sections with the content of Annex D. Correspondingly, [18] and [2] apply only to the first option, and [8] apply to the second and third. Compliance with the present document requires compliance with one of these implementations, but not with all three. It is not required that equipment built to one option shall interoperate with equipment built to the other. Compliance with frequency planning and EMC requirements is not covered by the present document and remains the operators' responsibility. In this respect, [14] and [15] are relevant to the USA; [1] and [i.5] to Canada; [7], [9], [10], [11], [12] and [13] are relevant to the European Union; [16] and [i.4] are relevant to China. The present document defines the interface for the physical layer, and corresponds to the CableLabs specification [i.8]. |
103 544-27 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 27: Basic Meta Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354427/01.03.01_60/ts_10354427v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document specifies the basic meta data service based on SBP (Service Binary Protocol) framework. The service is used as a basis for other meta information data services, providing MirrorLink Client's with MirrorLink Server services. |
103 544-28 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 28: Weather Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354428/01.03.01_60/ts_10354428v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document specifies weather data service based on SBP (Service Binary Protocol) framework. The service is used to provide weather data in car environments. |
103 544-29 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 29: Schedule Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354429/01.03.01_60/ts_10354429v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document specifies schedule data service based on SBP (Service Binary Protocol) framework. The service is used to provide schedule data in car environments. |
103 544-3 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 3: Audio | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354403/01.03.01_60/ts_10354403v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document defines the MirrorLink Audio architecture, based on an RTP forward and back channel, plus an possible Bluetooth HFP and A2DP setup. |
103 544-4 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 4: Device Attestation Protocol (DAP) | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354404/01.03.01_60/ts_10354404v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The term "device attestation" in this context refers to the MirrorLink client verifying that the MirrorLink server is from a compliant manufacturer and running approved software. The attestation will be based on standard X.509 certificates [2] and attestation mechanisms defined by Trusted Computing Group®. |
103 544-5 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 5: Common Data Bus (CDB) | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354405/01.03.01_60/ts_10354405v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The Common Data Bus (CDB) is a simple, low-bandwidth shared bus, which allows exchanging data between two CDB endpoints, residing in the MirrorLink Server and Client. The Common Data Bus is fully symmetrical, i.e. services can be provided on both endpoints independently from each other. |
103 544-6 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 6: Service Binary Protocol (SBP) | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354406/01.03.01_60/ts_10354406v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The Service Binary Protocol (SBP) is a simple, low-bandwidth data service framework, enabling a CDB data service provider and subscriber to utilize common functions like reading, writing or subscribing to objects of a data service. |
103 544-7 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 7: GPS Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354407/01.03.01_60/ts_10354407v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document specifies GPS service based on SBP (Service Binary Protocol) framework. The service is used to provide better GPS data in car environments. The present document is based on NMEA specification 0183 [1] as bearer of GPS. |
103 544-8 | Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 8: Location Data Service | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/103500_103599/10354408/01.03.01_60/ts_10354408v010301p.pdf | The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document specifies location service based on SBP (Service Binary Protocol) framework. The service is used to provide better location data in car environments. Note that this service provides high-level abstraction of location compared to com.mirrorlink.GPS service, which focuses on NMEA based GPS data. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.