id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 245
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
103 681-2
|
Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information models and protocols for generalized software reconfiguration architecture; Part 2: generalized Reconfigurable Radio Frequency Interface (gRRFI)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10368102/01.01.01_60/ts_10368102v010101p.pdf
|
The present document defines an information model and protocol for generalized reconfigurable radio frequency interface for reconfigurable REs. The work is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI TS 103 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI TS 103 648 [i.2]. The present document will be based on ETSI EN 303 146-2 [i.7] and provide a generalized interface definition for the generalized Reconfigurable Radio Frequency Interface.
|
103 681-1
|
Reconfigurable Radio Systems (RRS); Radio Equipment (RE) information models and protocols for generalized software reconfiguration architecture; Part 1: generalized Multiradio Interface (gMURI)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10368101/01.01.01_60/ts_10368101v010101p.pdf
|
The present document defines an information model and protocol for multiradio interface for reconfigurable RE. The work is based on the Use Cases defined in ETSI TR 103 585 [i.1], on the system requirements defined in ETSI TS 103 641 [1] and on the radio reconfiguration related architecture for reconfigurable RE defined in ETSI TS 103 648 [i.2]. The present document is based on ETSI EN 303 146-1 [i.6] and provide a generalized interface definition for the generalized Software Reconfiguration Architecture.
|
103 673
|
SmartM2M; SAREF Development Framework and Workflow, Streamlining the Development of SAREF and its Extensions
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103673/01.02.01_60/ts_103673v010201p.pdf
|
The present document defines the development framework for the SAREF ontology [1] and its extensions (referred to in a general way in the present document as SAREF projects) based on the ETSI forge. The development framework defines the different workflows to be followed for new SAREF project versions, SAREF project version development, and SAREF project release. The present document also defines how SAREF project versions are specified and documented in the SAREF public forge. The accompanying SAREF pipeline software enables to automatically check the conformance of SAREF project versions with respect to the present document. The accompanying SAREF public portal https://saref.etsi.org enables to browse the documentation of SAREF project versions and engage the community of users. The present document, the SAREF pipeline, and the SAREF public portal, enable the SAREF developers to speed up the development of SAREF and its extensions as well as the SAREF community of users to actively contribute in the development. The present document is based on the requirements and guidelines defined in the associated ETSI TR 103 608 [i.1].
|
103 672
|
Rail Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol with ISUP encapsulation (SIP-I) and other IP based protocols for interconnection of GSM-R networks
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103672/01.01.01_60/ts_103672v010101p.pdf
|
The present document defines the IP based signaling and media interfaces between any two GSM-R Core networks of a set of GSM-R Core networks that share a GIRA and that agree to interconnect via IP based technology. Furthermore it defines the IP based signaling and media interface between any GSM-R Core network that wants to interconnect with other GSM-R Core networks via IP based technology - and a centralized hub during a distinct phase of migration. The present document defines the IP Interconnect between 2 GSM-R Core networks - together with the interworking with BICC/ISUP at the edges of the networks - and the IP Interconnection between a GSM-R Core network and the current TDM hub - together with the interworking with ISUP at the current TDM hub and the interworking with BICC/ISUP at the edge of the GSM-R network. Only the network layer (e.g. IP) and layers that build on the network layer are considered. The lower layers are denoted as L2 and L1 and are out of scope in the present document. The present document will address all services (bearer services, tele services, supplementary services and railway services) that are defined by relevant EIRENE SRS [1]. The present document could address all domains of the GSM-R networks (e.g. CS domain, PS domain, IMS domain, etc.), however in a first step only the CS domain and the PS domain are covered. The present document does not address any specific 3GPP Release or Architecture.
|
103 666-4
|
Smart Secure Platform (SSP); Part 4: Embedded SSP (eSSP) Type 2 characteristics (Release 17)
|
TS
|
17.0.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366604/17.00.00_60/ts_10366604v170000p.pdf
|
The present document details the technical specifications for the Smart Secure Platform (SSP) in a discrete non removable hardware component, also known as eSSP. The present document defines specific attributes on top of the generic SSP specified in ETSI TS 103 666-1 [1] for eSSP Type 2, including the external interfaces (e.g. ISO 7816 [9], SPI, SWP). More in details the physical layer and related features are inherited from ETSI TS 103 666-3 [3] and the software architecture with virtualization interface, based on ETSI TS 103 666-2 [2].
|
103 666-3
|
Smart Secure Platform (SSP); Part 3: Embedded SSP (eSSP) Type 1 characteristics (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366603/16.00.00_60/ts_10366603v160000p.pdf
|
The present document details the technical specifications for the Smart Secure Platform (SSP) in a discrete hardware non removable component, also known as eSSP. The present document defines specific attributes on top of the generic SSP specified in ETSI TS 103 666-1 [1] for eSSP Type 1, including the external interfaces (e.g. ISO/IEC 7816-3 [11], SPI, SWP). The eSSP Type 1 class implements an operating system directly accessing the SSP hardware platform, as described in ETSI TS 103 666-1 [1] in clause 5.2.
|
103 666-2
|
Smart Secure Platform (SSP); Part 2: Integrated SSP (iSSP) characteristics (Release 17)
|
TS
|
17.1.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366602/17.01.00_60/ts_10366602v170100p.pdf
|
The present document details the technical specifications for the Smart Secure Platform (SSP) integrated into an SoC, also known as iSSP. The present document defines specific attributes on top of the generic SSP specified in ETSI TS 103 666-1 [3].
|
103 666-2
|
Smart Secure Platform (SSP); Part 2: Integrated SSP (iSSP) characteristics (Release 16)
|
TS
|
16.1.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366602/16.01.00_60/ts_10366602v160100p.pdf
|
The present document details the technical specifications for the Smart Secure Platform (SSP) integrated into an SoC, also known as iSSP. The present document defines specific attributes on top of the generic SSP specified in ETSI TS 103 666-1 [3].
|
103 666-2
|
Smart Secure Platform (SSP); Part 2: Integrated SSP (iSSP) characteristics (Release 15)
|
TS
|
15.5.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366602/15.05.00_60/ts_10366602v150500p.pdf
|
The present document details the technical specifications for the Smart Secure Platform (SSP) integrated into an SoC, also known as iSSP. The present document defines specific attributes on top of the generic SSP specified in ETSI TS 103 666-1 [3].
|
103 666-1
|
Smart Secure Platform (SSP); Part 1: General characteristics (Release 17)
|
TS
|
17.3.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366601/17.03.00_60/ts_10366601v170300p.pdf
|
The present document is part of a series of documents that specify the technical solution for the Smart Secure Platform (SSP), according to the requirements listed in ETSI TS 103 465 [i.2]. The present document contains generic technical solutions for different aspects of SSP functionality. It does not specify any specific type of SSP. The types of SSP are referred to as classes. The class specifications (for example the integrated SSP technical specification in ETSI TS 103 666-2 [8], the embedded SSP Type 1 technical specification in ETSI TS 103 666-3 [44] or the embedded SSP Type 2 technical specification in ETSI TS 103 666-4 [45]) refer to the present document for common SSP functionality.
|
103 666-1
|
Smart Secure Platform (SSP); Part 1: General characteristics (Release 16)
|
TS
|
16.8.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366601/16.08.00_60/ts_10366601v160800p.pdf
|
The present document is part of a series of documents that specify the technical solution for the Smart Secure Platform (SSP), according to the requirements listed in ETSI TS 103 465 [i.2]. The present document contains generic technical solutions for different aspects of SSP functionality. It does not specify any specific type of SSP. The types of SSP are referred to as classes. The class specifications (for example the integrated SSP technical specification in ETSI TS 103 666-2 [8], the embedded SSP Type 1 technical specification in ETSI TS 103 666-3 [44] or the embedded SSP Type 2 technical specification in ETSI TS 103 666-4 [45]) refer to the present document for common SSP functionality.
|
103 666-1
|
Smart Secure Platform (SSP); Part 1: General characteristics (Release 15)
|
TS
|
15.12.0
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366601/15.12.00_60/ts_10366601v151200p.pdf
|
The present document is part of a series of documents that specify the technical solution for the Smart Secure Platform (SSP), according to the requirements listed in ETSI TS 103 465 [i.2]. The present document contains generic technical solutions for different aspects of SSP functionality. It does not specify any specific type of SSP. The types of SSP are referred to as classes. The class specifications (for example the integrated SSP technical specification in ETSI TS 103 666-2 [8], the embedded SSP Type 1 technical specification in ETSI TS 103 666-3 [44] or the embedded SSP Type 2 technical specification in ETSI TS 103 666-4 [45]) refer to the present document for common SSP functionality.
|
103 663-3
|
Methods for Testing and Specification (MTS); Conformance Test Suite for TTCN-3 Object Oriented Features; Part 3: Abstract Test Suite (ATS) and Implementation eXtra Information for Testing (IXIT)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366303/01.03.01_60/ts_10366303v010301p.pdf
|
The present document specifies the Abstract Test Suite (ATS) for the TTCN-3 conformance test suite, as defined in ETSI ES 203 790 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 103 663-2 [8]. The objective of the present document is to provide a basis for conformance tests for TTCN-3 tools giving a high probability of standard conformance with respect to TTCN-3 tools from different vendors. In the present document only the core language features, specified in ETSI ES 203 790 [1] have been considered but not the tool implementation (see ETSI ES 201 873-5 [i.1] and ETSI ES 201 873-6 [i.2]), language mapping (see ETSI ES 201 873-7 [i.3], ETSI ES 201 873-8 [i.4] and ETSI ES 201 873-9 [i.5]) and language extension (see e.g. ETSI ES 202 781 [i.6], ETSI ES 202 784 [i.7] and ETSI ES 202 785 [i.8]) aspects. The test notation used in the ATS attached in a zipped file is in TTCN-3 and it is part of the present document. Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS. Annex B provides the Partial Implementation eXtra Information for Testing (PIXIT) pro forma of the ATS.
|
103 663-2
|
Methods for Testing and Specification (MTS); Conformance Test Suite for TTCN-3 Object Oriented Features; Part 2: Test Suite Structure and Test Purposes (TSS&TP)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366302/01.03.01_60/ts_10366302v010301p.pdf
|
The present document provides the Implementation Conformance Statement (ICS) pro forma for the conformance test suite for TTCN-3 Object Oriented Features, as defined in ETSI ES 203 790 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 103 663 (multi-part) [4]. In the present document only the core language features, specified in ETSI ES 203 790 [1] have been considered but not the tool implementation (see ETSI ES 201 873-5 [i.1] and ETSI ES 201 873-6 [i.2]), language mapping (see ETSI ES 201 873-7 [i.3], ETSI ES 201 873-8 [i.4] and ETSI ES 201 873-9 [i.5]) and language extension (see e.g. ETSI ES 202 781 [i.6], ETSI ES 202 784 [i.7] and ETSI ES 202 785 [i.8]) aspects.
|
103 663-1
|
Methods for Testing and Specification (MTS); Conformance Test Suite for TTCN-3 Object Oriented Features; Part 1: Implementation Conformance Statement (ICS)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10366301/01.03.01_60/ts_10366301v010301p.pdf
|
The present document provides the Implementation Conformance Statement (ICS) pro forma for the conformance test suite for TTCN-3 Object Oriented Features, as defined in ETSI ES 203 790 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 103 663-2 [4]. In the present document only the core language features, specified in ETSI ES 203 790 [1] have been considered but not the tool implementation (see [i.1] and [i.2]), language mapping (see [i.3], [i.4] and [i.5]) and language extension (see e.g. [i.6], [i.7] and [i.8]) aspects. The supplier of an implementation which is claimed to conform to ETSI ES 203 790 [1] is required to complete a copy of the ICS pro forma provided in the annex A of the present document.
|
103 655-2
|
Reconfigurable Radio Systems (RRS); Radio Interface Engine (RIE); Part 2: Architecture
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365502/01.01.01_60/ts_10365502v010101p.pdf
|
The scope of the present document is to define the Radio Interface Engine related system architecture. The work is based on the system requirements defined in ETSI TS 103 655-1 [1], and the feasibility study including Use Cases defined in ETSI TR 103 587 [i.1].
|
103 655-1
|
Reconfigurable Radio Systems (RRS); Radio Interface Engine (RIE); Part 1: Technical requirements
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365501/01.02.01_60/ts_10365501v010201p.pdf
| |
103 652-3
|
Reconfigurable Radio Systems (RRS); evolved Licensed Shared Access (eLSA); Part 3: Information elements and protocols for the interface between eLSA Controller (eLC) and eLSA Repository (eLR)
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365203/01.01.02_60/ts_10365203v010102p.pdf
|
The present document defines the application protocol on the eLSA1 interface, between eLSA Controller (eLC) and eLSA Repository (eLR) (eLSA1 protocol) [i.3], and the content of the eLSA Spectrum Resource Availability Information (eLSRAI) conveyed by this protocol. It is based on the System Requirements defined in ETSI TS 103 652-1 [i.2] and the System Architecture and High-Level Procedures defined in ETSI TS 103 652-2 [i.3]. The present document supports the operation of MFCNs operated by vertical sector players under the evolved Licensed Shared Access (eLSA) system, aimed at enabling the automatic provision of local spectrum access rights to vertical sector players through: • licenses acquired in advanced from the NRA and provided by the eLSA procedures; and/or • licenses/leases acquired and provided by the eLSA procedures. The operation of eLSA is frequency agnostic. The application of eLSA to concrete frequency bands depends on national regulatory decisions.
|
103 652-2
|
Reconfigurable Radio Systems (RRS); evolved Licensed Shared Access (eLSA); Part 2: System architecture and high-level procedures
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365202/01.01.01_60/ts_10365202v010101p.pdf
|
The present document specifies the system architecture for the operation of an Evolved Licensed Shared Access (eLSA) System, enabling the provision of spectrum access to many local high-quality wireless networks in dedicated licensed and leasing scenarios. The eLSA system architecture specification will include the identification and definition of the logical functional elements, interfaces, reference points, the mapping of functions to logical entities as well as the definition of the high- level procedures and information flows enabling assignment and handling of spectrum for the different scenarios considered. The present document has been developed following, and in accordance with, the system requirements for eLSA captured in ETSI TS 103 652-1 [1] and the feasibility study on temporary spectrum access for local high-quality wireless networks as documented in ETSI TR 103 588 [i.1].
|
103 652-1
|
Reconfigurable Radio Systems (RRS); evolved Licensed Shared Access (eLSA); Part 1: System requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365201/01.01.01_60/ts_10365201v010101p.pdf
|
The objective of evolving the LSA framework towards an eLSA (evolved LSA) system is to support spectrum access to local high-quality wireless networks operated by vertical sector operators, as introduced in ETSI TR 103 588 [i.1]. The present document specifies system requirements for that purpose. ETSI TC RRS work on eLSA is of technical nature aiming to provide an automatic tool to facilitate spectrum sharing coordination between incumbents, NRAs and eLSA Licensees (e.g. vertical sector operators). To meet the spectrum access demand and needs of local high-quality wireless networks, eLSA aims to offer technical means to facilitate the spectrum allocation procedure, including automatic local area licensing and leasing agreements, and to manage the conditions of spectrum use. The work is based on the generic aspects of the current ETSI specifications [i.2], [i.3] and [i.4] for Licensed Shared Access (LSA) in the 2 300 - 2 400 MHz band and on the functional enhancements proposed in ETSI TR 103 588 [i.1]. The work targets operation of local high-quality wireless networks in licensed bands to guarantee predictable QoS levels. It is agnostic to the radio frequency bands. The work on eLSA is based on the LSA concept [i.5], i.e. same architecture, role assumptions and applicable functionality. The requirements in the present document are intended to be used for the definition of an evolved LSA system architecture specification for providing spectrum access for local high-quality wireless networks.
|
103 650-2
|
EMTEL; Testing - Conformance test specifications for core elements for network independent access to emergency services (NG112); Part 2: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365002/01.02.01_60/ts_10365002v010201p.pdf
|
The present document contains the Abstract Test Suite (ATS) for core elements for network independent access to emergency services (NG112) as defined in standards listed in clause 2.1 of the present document.
|
103 650-1
|
EMTEL; Testing - Conformance test specifications for core elements for network independent access to emergency services (NG112); Part 1: Protocol Implementation Conformance Statement (PICS), Test Suite Structure and Test Purposes (TSS & TP)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10365001/01.02.01_60/ts_10365001v010201p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) and Test Suite Structure and Test Purposes (TSS & TP) for core elements for network independent access to emergency services (NG112) as defined in standards listed in clause 2.1 of the present document.
|
103 648
|
Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration architecture
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103648/01.01.01_60/ts_103648v010101p.pdf
|
The scope of the present document is to define the radio reconfiguration related architecture for reconfigurable Radio Equipment. The work is based on the system requirements defined in ETSI TS 103 641 [1] and the Use Cases defined in ETSI TR 103 062 [i.1], ETSI TR 102 944 [i.2] and ETSI TR 103 585 [i.3].
|
103 646
|
Methods for Testing and Specification (MTS); Test Specification for foundational Security IoT-Profile
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103646/01.01.01_60/ts_103646v010101p.pdf
|
The present document details test purposes to ensure a minimum security level for IoT devices. The underlying requirements are a subset of the IEC 62443-4-2 [1] standard containing functional security requirements for components. IEC 62443-4-2 [1] was initially started with the focus on Industrial Automation and Control systems. Due to its generic nature, the standard turned out to be applicable also to other domains. This is in especially possible as the standard allows the application of defined subsets in terms of so-called profiles. Profiles were meant to adapt the set of requirements to particular domains beyond industrial automation and control systems. It resolves the mapping of requirements to one of the four security level. So, the selection is not bound to existing security level, which might be seen as profiles as well. The IoT profile is a collection of those IEC 62443-4-2 [1] requirements that were seen foundational for any IoT device. Not fulfilling the IoT-profile-requirements does not mean that a device cannot be used at all. But it does mean, that the related risks need to be mitigated by other means. This applies especially to constrained devices with limited capabilities. The starting point for the IoT profile were IEC 62443-4-2 [1] requirements mapped to the lowest security level SL1. As IoT devices are typically running standalone without any integration into a central management system, all requirements related to integration into a central management system have been excluded. This applies in especially to requirements related to: • central account management integration; • central event management; • auditing. The only requirements seen mandatory for all IoT devices although mapped to higher security level in IEC 62443-4-2 [1] relate to: • software authenticity check (to prevent unauthorized software modifications); and • session integrity (to prevent e.g. replay attacks).
|
103 645
|
CYBER; Cyber Security for Consumer Internet of Things: Baseline Requirements
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103645/03.01.01_60/ts_103645v030101p.pdf
|
The present document specifies high-level security and data protection provisions for consumer IoT devices that are connected to network infrastructure (such as the Internet or home network) and their interactions with associated services. A non-exhaustive list of examples of consumer IoT devices includes: • connected children's toys and baby monitors; • connected smoke detectors, door locks and window sensors; • IoT gateways, base stations and hubs to which multiple devices connect; • smart cameras, smart speakers and smart TVs together with their remote controls; • wearable health trackers; • connected home automation and alarm systems, especially their gateways and hubs; • connected appliances, such as washing machines and fridges; and • smart home assistants. Moreover, the present document addresses security considerations specific to constraints in device resources. EXAMPLE: Typical device resources that might constrain the security capabilities are energy supply, communication bandwidth, processing power or (non-)volatile memory capacity. The present document provides basic guidance through examples and explanatory text for organizations involved in the development and manufacturing of consumer IoT on how to implement those provisions. Table B.1 provides a schema for the reader to give information about the implementation of the provisions. Devices that are not consumer IoT devices, for example those that are primarily intended to be used in manufacturing, healthcare or other industrial applications, are not in scope of the present document. The present document has been developed primarily to help protect consumers, however, other users of consumer IoT equally benefit from the implementation of the provisions set out here. Annex A (informative) of the present document has been included to provide context to clauses 4, 5 and 6 (normative). Annex A contains examples of device and reference architectures and an example model of device states including data storage for each state.
|
103 645
|
CYBER; Cyber Security for Consumer Internet of Things: Baseline Requirements
|
TS
|
2.1.2
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103645/02.01.02_60/ts_103645v020102p.pdf
|
The present document specifies high-level security and data protection provisions for consumer IoT devices that are connected to network infrastructure (such as the Internet or home network) and their interactions with associated services. A non-exhaustive list of examples of consumer IoT devices includes: • connected children's toys and baby monitors; • connected smoke detectors, door locks and window sensors; • IoT gateways, base stations and hubs to which multiple devices connect; • smart cameras, smart speakers and smart TVs together with their remote controls; • wearable health trackers; • connected home automation and alarm systems, especially their gateways and hubs; • connected appliances, such as washing machines and fridges; and • smart home assistants. Moreover, the present document addresses security considerations specific to constraints in device resources. EXAMPLE: Typical device resources that might constrain the security capabilities are energy supply, communication bandwidth, processing power or (non-)volatile memory capacity. The present document provides basic guidance through examples and explanatory text for organizations involved in the development and manufacturing of consumer IoT on how to implement those provisions. Table B.1 provides a schema for the reader to give information about the implementation of the provisions. Devices that are not consumer IoT devices, for example those that are primarily intended to be used in manufacturing, healthcare or other industrial applications, are not in scope of the present document. The present document has been developed primarily to help protect consumers, however, other users of consumer IoT equally benefit from the implementation of the provisions set out here. Annex A (informative) of the present document has been included to provide context to clauses 4, 5 and 6 (normative). Annex A contains examples of device and reference architectures and an example model of device states including data storage for each state.
|
103 645
|
CYBER; Cyber Security for Consumer Internet of Things
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103645/01.01.01_60/ts_103645v010101p.pdf
|
The present document specifies high-level security and data protection provisions for consumer IoT devices that are connected to network infrastructure (such as the Internet or home network) and their interactions with associated services. A non-exhaustive list of examples of consumer IoT devices includes: • connected children's toys and baby monitors; • connected smoke detectors, door locks and window sensors; • IoT gateways, base stations and hubs to which multiple devices connect; • smart cameras, smart speakers and smart TVs together with their remote controls; • wearable health trackers; • connected home automation and alarm systems, especially their gateways and hubs; • connected appliances, such as washing machines and fridges; and • smart home assistants. Moreover, the present document addresses security considerations specific to constraints in device resources. EXAMPLE: Typical device resources that might constrain the security capabilities are energy supply, communication bandwidth, processing power or (non-)volatile memory capacity. The present document provides basic guidance through examples and explanatory text for organizations involved in the development and manufacturing of consumer IoT on how to implement those provisions. Table B.1 provides a schema for the reader to give information about the implementation of the provisions. Devices that are not consumer IoT devices, for example those that are primarily intended to be used in manufacturing, healthcare or other industrial applications, are not in scope of the present document. The present document has been developed primarily to help protect consumers, however, other users of consumer IoT equally benefit from the implementation of the provisions set out here. Annex A (informative) of the present document has been included to provide context to clauses 4, 5 and 6 (normative). Annex A contains examples of device and reference architectures and an example model of device states including data storage for each state.
|
103 643
|
Techniques for assurance of digital material used in legal proceedings Assuring digital material
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103643/01.02.01_60/ts_103643v010201p.pdf
|
The present document defines a process of receiving, transforming and outputting material that can be assured digitally. The process is called the "Digital Evidence Bag" (DEB). The present document identifies the ways that a DEB can be used to provide assurance of material used in legal proceedings. Specifically, the assurance of the material is not dependent on the process having been carried out by a qualified or trained human expert. The present document is designed to be used in situations where a risk assessment of the handling of digital material has identified that extra assurance of the integrity, provenance, continuity and validity of the digital data is required.
|
103 641
|
Reconfigurable Radio Systems (RRS); Radio Equipment (RE) reconfiguration requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103641/01.01.01_60/ts_103641v010101p.pdf
|
The scope of the present document is to define the high level system requirements for reconfigurable Radio Equipment enabling the provision of Radio Applications. The work is based on the Use Cases defined in ETSI TR 103 062 [i.1], ETSI TR 102 944 [i.2], ETSI TR 103 585 [i.3] and ETSI EN 302 969 [i.4].
|
103 640
|
Speech and multimedia Transmission Quality (STQ); Test Methods and Performance Requirements for Active Noise Cancellation Headsets and other Earphones
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103640/01.03.01_60/ts_103640v010301p.pdf
|
The present document specifies test methods and performance requirements for wireless and wired Active Noise Cancellation (ANC) devices such as headsets, earphones, headphones, hearables, and other ear worn devices (herein referred to as devices). The test methods and performance requirements cover the various functionalities of ANC devices including e.g. noise cancellation, media playback, voice calls, and pass-through mode. Test methods and performance aspects covered in the following clauses might not be relevant (or not applicable) for certain types of ANC devices and/or for specific qualification/certification purposes. For this reason, several test suites and subsets are defined in Annex B, which represent typical application scenarios of ANC devices and can be used for conformance testing. If not specified otherwise, an ANC device should meet all requirements for the tests in Annex B test suite #1, without an additional test subset. ANC performance metrics and requirements for handsets are out of scope.
|
103 636-5
|
DECT-2020 New Radio (NR); Part 5: DLC and Convergence layers; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363605/02.01.01_60/ts_10363605v020101p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Data Link Control (DLC) and Convergence layer (CVG) between DECT-2020 radio interface and different application protocols.
|
103 636-5
|
DECT-2020 New Radio (NR); Part 5: DLC and Convergence layers; Release 1
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363605/01.06.01_60/ts_10363605v010601p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Data Link Control (DLC) and Convergence layer (CVG) between DECT-2020 radio interface and different application protocols.
|
103 636-4
|
DECT-2020 New Radio (NR); Part 4: MAC layer; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363604/02.01.01_60/ts_10363604v020101p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Medium Access Control (MAC) layer and interactions between the MAC layer and physical layer and higher layers.
|
103 636-4
|
DECT-2020 New Radio (NR); Part 4: MAC layer; Release 1
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363604/01.06.01_60/ts_10363604v010601p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Medium Access Control (MAC) layer and interactions between the MAC layer and physical layer and higher layers.
|
103 636-3
|
DECT-2020 New Radio (NR); Part 3: Physical layer; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363603/02.01.01_60/ts_10363603v020101p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Physical layer and interaction between PHY and MAC layer.
|
103 636-3
|
DECT-2020 New Radio (NR); Part 3: Physical layer; Release 1
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363603/01.06.01_60/ts_10363603v010601p.pdf
|
The present document is one of the parts of the specification of the DECT-2020 New Radio (NR). The present document specifies the Physical layer and interaction between PHY and MAC layer.
|
103 636-2
|
DECT-2020 New Radio (NR); Part 2: Radio reception and transmission requirements; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363602/02.01.01_60/ts_10363602v020101p.pdf
|
The present document establishes the minimum RF requirements for DECT-2020 New Radio (NR) Radio Devices (RDs). For clarity these requirements cover both Fixed Termination point (FT) as well as Portable Termination point (PT).
|
103 636-2
|
DECT-2020 New Radio (NR); Part 2: Radio reception and transmission requirements; Release 1
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363602/01.06.01_60/ts_10363602v010601p.pdf
|
The present document establishes the minimum RF requirements for DECT-2020 New Radio (NR) Radio Devices (RDs). For clarity these requirements cover both Fixed Termination point (FT) as well as Portable Termination point (PT).
|
103 636-1
|
DECT-2020 New Radio (NR); Part 1: Overview; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363601/02.01.01_60/ts_10363601v020101p.pdf
|
The present document provides an overview on DECT-2020 NR including layers, system and network architectures envisioned for this release. Further it provides an overview to ETSI TS 103 636-2 [1], ETSI TS 103 636-3 [2], ETSI TS 103 636-4 [3], ETSI TS 103 636-5 [4] and their interrelation.
|
103 636-1
|
DECT-2020 New Radio (NR); Part 1: Overview; Release 1
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/10363601/01.06.01_60/ts_10363601v010601p.pdf
|
The present document provides an overview on DECT-2020 NR including layers, system and network architectures envisioned for this release. Further it provides an overview to ETSI TS 103 636-2 [1], ETSI TS 103 636-3 [2], ETSI TS 103 636-4 [3], ETSI TS 103 636-5 [4] and their interrelation.
|
103 634
|
Digital Enhanced Cordless Telecommunications (DECT); Low Complexity Communication Codec plus (LC3plus)
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103634/01.05.01_60/ts_103634v010501p.pdf
|
The present document contains the specification of the Low Complexity Communication Codec plus (LC3plus). The specification includes a full algorithmic description of both the encoder and the decoder. It includes reference fixed-point and floating-point ANSI C source code and conformance test procedures. The codec has been designed on the one hand for Digital Enhanced Cordless Telecommunications (DECT) and the New Generation DECT (NG-DECT) systems but also for VoIP and other applications such as music streaming. The LC3plus codec provides the following basic features: • Capability for speech and audio coding • Several low delay modes • Low computational complexity • Multiple bitrates from 16 kbit/s up to 320 kbit/s and more • Multiple audio bandwidth from narrow band to full-band and ultra-band • High- resolution mode for high precision, high dynamic range and audio bandwidth up to the Nyquist frequency also for ultra-band • Advanced error concealment • Application Layer Forward Error Correction (AL-FEC) including channel coder functionality • RTP payload format
|
103 632
|
Digital Audio Broadcasting (DAB); Open Mobile Radio Interface (OMRI); Application Programming Interface (API)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103632/01.01.01_60/ts_103632v010101p.pdf
|
The present document specifies an Application Programming Interface (API) for the Open Mobile Radio Interface (OMRI) which can be used by application developers to gain access to broadcast radio tuners in consumer electronic devices such as smartphones, tablets and/or other devices, and which allows the execution of program code often referred to as apps.
|
103 625
|
Emergency Communications (EMTEL); Transporting Handset Location to PSAPs for Emergency Communications - Advanced Mobile Location
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103625/01.03.01_60/ts_103625v010301p.pdf
|
The present document describes the content and the transport methods used for AML messages with handset derived location information and associated data. It also considers the future evolution of transport methods as PSAPs, networks and terminals become increasingly IP based.
|
103 624
|
Speech and multimedia Transmission Quality (STQ); Characterization Methodology and Requirement Specifications for the ETSI LC3plus speech codec
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103624/01.04.01_60/ts_103624v010401p.pdf
|
The present document specifies the subjective and objective methodologies developed in cooperation between TC STQ and TC DECT for the characterization of the Low Complexity Communication Codec Plus (LC3plus) speech codec. It describes experimental tests and conditions used for subjective and objective testing. Based on these methodologies the performance requirements for this codec are specified. The requirements in the present document are specified to characterize a high-quality codec for use in modern telecommunication networks, including but not limited to DECT and VoIP. A special focus is placed on the fact that end-to-end connections are often of hybrid nature concatenating different technologies and thus tandeming (i.e. transcoding) different codecs. In addition to its speech capabilities, the LC3plus codec has the option for high quality music streaming. This is out of scope of the present document. The 2021 revision of the present document adds the test plan for the auditory test, see annex B, the results of the subjective characterization test for the ETSI LC3plus codec, see annex C as well as the related electronic attachment(s). The 2024 revision of the present document adds the objective test results, see annex D and the Ie derivation as well as a new Ie derivation methodology for fullband conditions, see annex E together with the related electronic attachments. The 2025 revision of the present document aligns the derivation of fullband Ie and Bpl values with those agreed to in Recommendation ITU-T P.834.2 [41]. This relates to clauses E.3.3.1 and E.4.3 and the POLQA SWB results in the electronic attachmen contained in archive ts_103624v010401p0.zip which accompanies the present document.
|
103 615
|
Digital Video Broadcasting (DVB); Metadata generation and deterministic DVB-T-mega-frame/DVB-T2-MI stream generation from MPEG-2 Transport Stream(s) for a DVB Single Illumination System (DVB-SIS)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103615/01.01.01_60/ts_103615v010101p.pdf
|
The present document describes the Single Illumination System, which allows to deliver Parent Signals for direct reception by consumer receivers and, at the same time, for a deterministic generation of daughter streams for terrestrial retransmission. Parent Signals can be provided to the daughter site via all defined TS-based DVB means - be it satellite, cable or terrestrial. Metadata may be provided as part of the Parent Signal(s) (called "in-band" in the present document). Part of the metadata may also be provided "out-of-band". A typical use case is described by the present document and is based on satellite broadcast signals on parent side - be it DVB-S (ETSI EN 300 421 [8]), -S2 (ETSI EN 302 307-1 [9]) or -S2X signals (ETSI EN 302 307-2 [10]) - that are addressing consumer Direct-to-Home (DTH) receivers and terrestrial transmitters on daughter side in parallel. For terrestrial retransmission of the whole or partial content, the DTH signal(s) of MPEG-2 TS format (ISO/IEC 13818-1 [5]) from one or several satellites can be used and services and service components can be selected according to terrestrial broadcasters' needs. Also other non-satellite Parent Signals and out-of-band metadata feeds can be integrated into the preparation of the terrestrial DVB-T2, ETSI EN 302 755 [2], and/or DVB-T, ETSI EN 300 744 [3] signals on daughter site. Single Frequency Networks (SFN) operation of the terrestrial networks driven by the Single Illumination System is enabled.
|
103 613
|
Intelligent Transport Systems (ITS); Access layer specification for Intelligent Transport Systems using LTE Vehicle to everything communication in the 5,9 GHz frequency band
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103613/01.01.01_60/ts_103613v010101p.pdf
|
The present document defines the physical layer and the data link layer and radio resource configuration, grouped into the access layer of the ITS station reference architecture ETSI EN 302 665 [i.5]. The access layer technology that is specified in the present document refers to what is known as the sidelink or PC5 interface of LTE Vehicle to everything (LTE-V2X) for the following frequency bands: • Operation in frequency band dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,925 GHz. • Operation in frequency bands dedicated to ITS non-safety applications in the frequency range 5,855 GHz to 5,875 GHz. The LTE-V2X technology is based on 3GPP specifications.
|
103 607
|
Speech and multimedia Transmission Quality (STQ); Transmission requirements for wearable wireless wideband speech terminals from a QoS perspective as perceived by the user
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103607/01.01.01_60/ts_103607v010101p.pdf
|
The present document provides objective measurement methodologies and speech transmission performance requirements for wireless wearable speech terminals; Headsets are out of scope. The present standard defines minimum performance requirements regardless of the physical and data link layers, enabling manufacturers and service providers to enable good quality end-to-end speech performance as perceived by the user. When an additional radio link between the terminal and external electroacoustical devices is used (e.g. Bluetooth® link), the standard will address the overall quality. It is the aim to optimize the listening and talking quality, conversational performance, as well as the use in noisy environments. Related requirements and test methods are defined in the present document. For all the functions, the standard considers the limitations in audio performance due to different form factors (e.g. size, shape, wearing style and location).
|
103 606
|
Hybrid Broadcast Broadband Television; Operator Applications
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103606/01.02.01_60/ts_103606v010201p.pdf
|
The present document specifies a platform, based on the existing HbbTV® specification ETSI TS 102 796 [1], that supports the signalling, transport and presentation of an operator application. The operator application is able to replace some of the terminal's user interface. The extent to which the terminal user interface is replaced by an operator application depends on the type of the operator application and the business models of the operator and manufacturer. The present document assumes the presence of an agreement between an operator and the device manufacturer. Operator applications will not run in the absence of such an agreement. Topics that could or need to be covered by such a bilateral agreement are listed in annex D. The present document makes use of functionalities described in ETSI TS 102 796 which is describing a platform for signalling, transport, and presentation of enhanced and interactive applications intended for running on hybrid terminals that include both a DVB compliant broadcast connection and a broadband connection to the Internet. The usage of a hybrid terminal for IPTV delivered audio-visual content is described in "IP-delivered Broadcast Channels and Related Signalling of HbbTV® Applications" [i.4].
|
103 605
|
Digital Video Broadcasting (DVB); Second Generation Common Interface (CI); Implementation Using the Universal Serial Bus (USB)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103605/01.01.01_60/ts_103605v010101p.pdf
|
The present document defines USB physical, link and transport layers for the DVB Common Interface to replace the PC Card interface defined in CENELEC EN 50221 [1]. The present document also profiles and extends the application layer defined in CENELEC EN 50221 [1], ETSI TS 101 699 [2] and CI Plus specification [3] to cater for the use over USB.
|
103 601
|
Intelligent Transport Systems (ITS); Security; Security management messages communication requirements and distribution protocols; Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103601/02.01.01_60/ts_103601v020101p.pdf
|
The present document defines communication requirements and profiles to support communications from/to ITS-S stations (e.g. fixed road side ITS-S, mobile ITS-S) for the support of security management services specified in ETSI TS 102 941 [2] (i.e. certificate management, trust and revocation lists distribution). The present document also defines the related protocol handling for the selected messages as well as the requirements for the lower layer protocol stacks and for the Security Management entity in order to support message dissemination and reception.
|
103 567
|
Requirements on signal interferer handling
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103567/01.01.01_60/ts_103567v010101p.pdf
|
The present document specifies a limited set of baseline receiver requirements aiming to meet the essential requirements of Article 3.2 of the Radio Equipment Directive [i.4] by developing provisions for harmonised standards, see clauses 2.8.2 and 2.10.2 in Vademecum Part III [i.8] to support assessment of compliance of harmonised standards, see clause 7 in Vademecum Part I [i.7]. These receiver requirements are related to effective and efficient use of the radio spectrum and not to quality aspects of products. These baseline receiver parameters are equivalent to the receiver parameter as given in ETSI EG 203 336 [i.1].
|
103 601
|
Intelligent Transport Systems (ITS); Security; Security management messages communication requirements and distribution protocols
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103601/01.01.01_60/ts_103601v010101p.pdf
|
The present document defines communication requirements and profiles to support communications from/to ITS-S stations (e.g. fixed road side ITS-S, mobile ITS-S) for the support of security management services specified in ETSI TS 102 941 [2] (i.e. certificate management, trust and revocation lists distribution). The present document also defines the related protocol handling for the selected messages as well as the requirements for the lower layer protocol stacks and for the Security Management entity in order to support message dissemination and reception.
|
103 586
|
Environmental Engineering (EE); Liquid cooling solutions for Information and Communication Technology (ICT) infrastructure equipment
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103586/01.03.01_60/ts_103586v010301p.pdf
|
The present document covers following applications: • Liquid cooling at the cabinet/rack level. • Liquid cooling at the product level. • Liquid cooling via immersion in dielectric liquid. The present document specifies the following items: • Liquid circulation layout (connection of multiple units). • Liquid flow rate range vs. dissipated power. • Maximum pressure drop per liquid flow rate. • Maximum pressure drop per air flow rate. • External pipe diameter range and pipe threads. • Valves requirements. • Coolants and cooling distribution unites. • Max pressure and tightness. • Reliability requirement Furthermore, the present document provides: • Benchmark methods to evaluated different cooling system efficiency.
|
103 584
|
DTS-UHD Point Source Renderer
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103584/01.01.01_60/ts_103584v010101p.pdf
|
The present document defines an audio renderer associated with the DTS-UHD codec defined in ETSI TS 103 491 [1]. The inputs to the renderer are one or more sets of audio waveforms along with mixing instructions, and the output is a single set of waveforms mapped to a defined speaker configuration. Each set of waveforms may represent either audio channels or audio objects. The mixing instructions may vary with time and they come from metadata carried in the DTS-UHD bitstream and from other application interfaces described herein.
|
103 574
|
Intelligent Transport Systems (ITS); Congestion Control Mechanisms for C-V2X PC5 interface; Access layer part; Release 2
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103574/02.00.00_60/ts_103574v020000p.pdf
|
The present document is the baseline for the definition of the Release 2 Congestion Control Access Layer part for the Cellular-V2X PC5 Interface.
|
103 574
|
Intelligent Transport Systems (ITS); Congestion Control Mechanisms for C-V2X PC5 interface; Access layer part
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103574/01.01.01_60/ts_103574v010101p.pdf
|
The present document is the baseline for the definition of the Release 2 Congestion Control Access Layer part for the Cellular-V2X PC5 Interface.
|
103 572
|
HDR Signalling and Carriage of Dynamic Metadata for Colour Volume Transform; Application #1
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103572/01.03.01_60/ts_103572v010301p.pdf
|
The present document specifies the format of the SEI or VSEI messages for the carriage of SMPTE ST 2094-10 [4] HDR dynamic metadata. The present document includes references for the carriage and signalling the presence of SMPTE ST 2094-10 [4] HDR dynamic metadata (carried in SEI messages defined in the present document) for DVB systems, as defined in ETSI TS 101 154 [i.3], ETSI TS 103 285 [9] and ETSI EN 300 468 [i.2].
|
103 569
|
ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Study into extending the upper limit of the range of radiated emissions requirements up to 40 GHz
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103569/01.01.01_60/ts_103569v010101p.pdf
|
The aim of the present document is to control unintentional radiated emissions generated by digital devices to protect radio services operating at frequencies up to 40 GHz. The upper frequency limit of 6 GHz for unintentional radiated electric field emissions within current ETSI EMC standards is insufficient to protect these higher frequencies. Therefore, there is a need to develop requirements to control higher frequency digital noise to improve EMC. Within the present document, the upper limit of the frequency range is extended to 40 GHz and includes the following main elements: • radiated electric field emission limits for unintentional signals; • test site specifications; • measurement methods; • uncertainty analysis.
|
103 589
|
Higher Order Ambisonics (HOA) Transport Format
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103589/01.01.01_60/ts_103589v010101p.pdf
|
Higher Order Ambisonics (HOA) signals are able to deliver a significantly enhanced immersive sound compared to conventional stereo or 5.1 channel audio signals. However, there are some use cases where HOA signals cannot be transported because of the large number of HOA input channels. The present document provides an HOA transport format which allows unrestricted HOA order signals to be transported.
|
103 551
|
Digital Audio Broadcasting (DAB); Transport of TPEG services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103551/01.01.01_60/ts_103551v010101p.pdf
|
The present document describes the standardized method to carry TPEG services over Digital Audio Broadcast (DAB).
|
103 564
|
PlugtestsTM scenarios for Mission Critical Services
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103564/01.06.01_60/ts_103564v010601p.pdf
|
The present document specifies interoperability tests with the purpose of supporting the Mission Critical Push-To-Talk (MCPTT) PlugtestsTM events.
|
103 557
|
Speech and multimedia Transmission Quality (STQ); Methods for reproducing reverberation for communication device measurements
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103557/01.03.01_60/ts_103557v010301p.pdf
|
The present document describes a methodology for recording and reproducing different room characteristics and realistic reverberation under conditions that are well-defined and tailored for a calibrated setup in a lab environment. The individual aspects of the description are: • Measurement of room impulse responses. • Processing of test signals. • Loudspeaker setup, calibration and equalization. The methodology is fundamentally designed for use without access to internals of the Device Under Test (DUT), e.g. the exact positions and orientations of the device's microphones or the unprocessed microphone signals. The methodology is intended to be used for performance evaluation of all types of devices where the room characteristics may impact the performance.
|
103 556
|
Speech and multimedia Transmission Quality (STQ); DTMF transmission over VoIP using RTP Telephony Events
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103556/01.01.01_60/ts_103556v010101p.pdf
|
The present document provides the level of detail that will enable manufacturers of telecommunications equipment incorporating Telephony Events described in IETF RFC 4733 [1] for the transport of DTMF signalling to design the equipment. The present document specifies the signal receiver and transmitter requirements of DTMF signals.
|
103 555
|
IP-delivered Broadcast Channels and Related Signalling of HbbTV Applications
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103555/01.01.01_60/ts_103555v010101p.pdf
|
The present document describes how IPTV Terminals can make use of HbbTV features. It does not, in any way, describe an IPTV delivery system itself. As such, technologies like fast channel change, retransmission and forward error correction are out-of-scope. Instead it defines how several technologies may be used in combination with HbbTV in a form that can be referenced by markets or organizations that have made choices. Please note that the scope of the present document only includes channels that use either MPEG-2 Transport Stream or MPEG DASH in the way defined in clause 6.2.
|
103 553-3
|
Environmental Engineering (EE); Innovative energy storage technology for stationary use; Part 3: Supercapacitor
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10355303/01.01.01_60/ts_10355303v010101p.pdf
|
The present document provides an overview of available SuperCapacitor (SC) technology, with details of SC characteristics (electrical, mechanical, thermal) and applicability in the Telecommunication/Information and Communication Technology (TLC/ICT) domain [i.1]. A general overview of the evolution of energy storage technologies is provided in ETSI TS 103 553-1 [i.4] and Recommendation ITU-T L.1220 [i.5]. The adoption of SC technology is recommended for coverage of micro-interruptions of the public grid for indoor and outdoor applications. Examples of sizing and essential tests used in the network are described.
|
103 553-2
|
Environmental Engineering (EE); Innovative energy storage technology for stationary use; Part 2: Battery
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10355302/01.01.01_60/ts_10355302v010101p.pdf
|
The present document contains the main requirements for evaluating appropriate innovative batteries for stationary use for powering ICT equipment in telecom sites, active network units and data centres or customer premises with standardized power interfaces in -48 V, up to 400 VDC or 12 V. Based on the general selection and evaluation method proposed in ETSI TS 103 553-1 [1], the present document introduces the main battery technologies, characteristics and the method to select, evaluate and test battery products adapted to a defined application. The present document describes the selection criteria and possible tests for making the appropriate or optimal choice of battery technology for an ICT stationary application. This includes mechanical performance, electrical performance, (voltage, current, power and capacity ratings, efficiency and self-discharge, etc.), environmental performance (temperature range), lifetime performance (cycling and calendar life, tolerance of partial charge and depth of discharge), installation, operation and maintenance complexity (parallel operation), safety (risk to and protection of humans and environment, error and fault tolerance), management/monitoring (including anti-theft solution) at battery and cell level and Total Cost Ownership (TCO) assessment. The present document specifies evaluation methods and tests which complement those of existing relevant standards requirements.
|
103 600
|
Intelligent Transport Systems (ITS); Testing; Interoperability test specifications for security
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103600_103699/103600/01.02.01_60/ts_103600v010201p.pdf
|
The present document contains specification of interoperability test descriptions to validate implementations of ETSI TS 103 097 [1], ETSI TS 102 941 [3] and ETSI TS 102 940 [i.1].
|
103 548
|
SmartM2M; SAREF reference ontology patterns
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103548/01.02.01_60/ts_103548v010201p.pdf
|
The present document specifies the set of SAREF reference ontology patterns [2] for the modelling and the description of any kind of applications-related data/information/systems. The SAREF reference ontology patterns can be applied to different verticals to provide the SAREF suite of ontologies [1] a homogeneous and predictable structure, and to achieve higher semantic interoperability. They extend and are aligned with the core of the following ontologies: W3C&OGC SOSA (Sensing, Observation, Sampling and Actuation) and SSN (Semantic Sensor Network) [i.1], QUDT (Quantity, Unit, Dimension and Type) [i.2], DUL (Dolce+DnS Ultralite Ontology) [i.3]. The present document is based on the requirements and guidelines defined in ETSI TR 103 549 [i.4] and ETSI TR 103 781 [i.5].
|
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 558
|
Speech and multimedia Transmission Quality (STQ); Methods for objective assessment of listening effort
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103558/01.03.01_60/ts_103558v010301p.pdf
|
The present document describes auditory and instrumental testing methodologies, which can be used to evaluate the perceived listening effort in the following speech communication scenarios at acoustical interfaces in the presence of acoustical near-end ambient noise. Similar to other instrumental quality prediction methods like e.g. ETSI TS 103 281 [4] or Recommendation ITU-T P.863 [i.2] valid objective predictions can only be made based on a specific listening test design and on auditory results obtained in such tests. The present document specifies the test design and reference conditions used to evaluate listening effort subjectively. The objective prediction model specified are based on this test design and validated against the results of the underlying subjective tests; only normal hearing listeners are considered. The usage for hearing impaired listeners is for further study. Several application scenarios and types of terminals are covered: • (Mobile) Handset. • In-car communication systems. The following applications are for further study: • Headset (including active noise cancelling devices). • Group audio terminals. • Mobile handheld hands-free. • Vehicle hands-free. • Fixed, mobile and IP-based networks (including impairments). Binaural as well as monaural recording situations are covered. The listening effort prediction model utilizes binaural signals for acoustical recordings and monaural signals for electrical recordings.
|
103 596-3
|
Methods for Testing and Specification (MTS); Test Specification for CoAP; Part 3: Performance Tests
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359603/01.01.01_60/ts_10359603v010101p.pdf
|
The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the Constrained Application Protocol (CoAP) protocol. It will be a reference base for both client side test campaigns and server side test campaigns addressing the performance issues.
|
103 596-2
|
Methods for Testing and Specification (MTS); Test Specification for CoAP; Part 2: Security Tests
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359602/01.01.01_60/ts_10359602v010101p.pdf
|
The present document provides general security considerations and guidelines about the Constrained Application Protocol (CoAP). The collective ideas presented in the present document are enriched with example Test Purposes (TPs) to outline possible implementations.
|
103 596-1
|
Methods for Testing and Specification (MTS); Test Specification for CoAP; Part 1: Conformance Tests
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359601/01.01.01_60/ts_10359601v010101p.pdf
|
The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the Constrained Application Protocol (CoAP). It will be a reference base for both client-side test campaigns and server- side test campaigns addressing the conformance issues.
|
103 553-1
|
Environmental Engineering (EE); Innovative energy storage technology for stationary use; Part 1: Overview
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10355301/01.01.01_60/ts_10355301v010101p.pdf
|
The present document identifies the main needs and applications of stationary electrical energy storage for ICT sites such as back-up on different grid quality and cyclic use of renewable energy systems. It also provides possible selection criteria for the correct choice for the end system. The topics considered are: • families of electrical energy storage such as batteries or super-capacitors; • technologies types and their main properties; • adaptation to requirements (functionalities, technology availability, electrical characteristics, environmental adaptation, maintenance type, cost, etc.); • national or regional rules and regulations. The present document highlights the need of evaluation methods that are complementary to existing battery standards as they allow different time frame including shorter tests compared to common energy storage industry tests. The present document introduces a series of subparts that covers energy storage technologies (battery, super-capacitor, etc.) applicable to stationary Telecom/ICT equipment used in telecom networks, data centres and customer premises (CPE).
|
103 597-3
|
Methods for Testing and Specification (MTS); Test Specification for MQTT; Part 3: Performance Tests
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359703/01.01.01_60/ts_10359703v010101p.pdf
|
The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the Message Queuing Telemetry Transport (MQTT) protocol. It will be a reference base for both client side test campaigns and server side test campaigns addressing the performance issues.
|
103 597-2
|
Methods for Testing and Specification (MTS); Test Specification for MQTT; Part 2: Security Tests
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359702/01.01.01_60/ts_10359702v010101p.pdf
|
The present document provides general security considerations and guidelines about the Message Queuing Telemetry Transport (MQTT) protocol. The collective ideas presented in the present document are enriched with example Test Purposes (TPs) to outline possible implementations.
|
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-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-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-26
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 26: Consumer Experience Principles and Basic Features
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354426/01.03.01_60/ts_10354426v010301p.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 is a single protocol that defines how a MirrorLink enabled Client device (typically the consumer's in-vehicle infotainment system) and a MirrorLink enabled Server device (typically the consumer's mobile device) communicate and provide an integrated consumer experience, where the MirrorLink Server is creating the consumer experience, running MirrorLink applications, whose user interfaces are presented via the MirrorLink Client. Consumers will only interact with the MirrorLink Client device, leaving the MirrorLink Server device stored away, allowing for responsible interactions, while the vehicle is in motion. The MirrorLink protocol enables mobile device's consumer experience to be projected on the in-vehicle infotainment system. It enables the consumer to use the controls of the infotainment system to manipulate the mobile device. By using applications, following application-level requirements, either for use in drive or non-drive situations, consumers will see an experience optimized for the current situation. Whereas the MirrorLink protocol specifies a consumer experience, it is open to implementation specific decisions and variations from Client and Server manufacturers. Differentiation in the consumer experience and supported features is encouraged. However, MirrorLink does need to be predictable and recognizable to the consumer. It is also critical for a MirrorLink brand recognition. The present document specifies the basic consumer experience, for which MirrorLink stands for and many of the features MirrorLink enables. The present document intends to focus on the consumer experience level and does not intend to replace any requirements of the other technical specifications. Whether or not a MirrorLink Client or Server device follow the requirements defined within the present document will be mainly evaluated and tested through IOP testing.
|
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 544-9
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 9: UPnP Application Server Service
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354409/01.03.01_60/ts_10354409v010301p.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 TmApplicationServer service is a UPnP service that allows UPnP Control Points to remotely launch and terminate applications on MirrorLink Server devices. Through this service, UPnP control points can provide more fine-grained control and access to specific remote applications.
|
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.
|
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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 597-1
|
Methods for Testing and Specification (MTS); Test Specification for MQTT; Part 1: Conformance Tests
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10359701/01.01.02_60/ts_10359701v010102p.pdf
|
The present document provides a test specification, i.e. an overall test suite structure and catalogue of test purposes for the MQ Telemetry Transport (MQTT). It will be a reference base for both client-side test campaigns and server-side test campaigns addressing the conformance issues.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.