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 544-21
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 21: High Speed Media Link (HSML)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354421/01.03.01_60/ts_10354421v010301p.pdf
|
The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The present document describes the High-Speed Media Link, a video transmission mechanism that utilizes the USB to project the screen of one device onto another device with a larger screen.
|
103 544-12
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 12: UPnP Server Device
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354412/01.03.01_60/ts_10354412v010301p.pdf
|
The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The present document defines the device: urn:schemas-upnp-org:device:TmServerDevice:1. This device can be a UPnP root device or embedded within a different device. The TmServerDevice encapsulates all services for the MirrorLink UPnP Server Device Control Protocol (DCP).
|
103 544-11
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 11: UPnP Notification Server Service
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354411/01.03.01_60/ts_10354411v010301p.pdf
|
The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. The TmNotificationServer service is an UPnP service that allows control points to receive diverse notifications from the devices that support the TmNotificationServer service. The TmNotificationServer service enables the following features to: • send a notification to the head unit; • get an action described in the notification.
|
103 544-10
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 10: UPnP Client Profile Service
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354410/01.03.01_60/ts_10354410v010301p.pdf
|
The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a color display, audio input/output and user input mechanisms. The TmClientProfile service is a UPnP service that allows control points to register client profiles with the MirrorLink Server device and notifies it regarding MirrorLink Client preferences, settings and capabilities, which is be used for governing the interaction between the MirrorLink Server and the Client.
|
103 544-24
|
Publicly Available Specification (PAS); Intelligent Transport Systems (ITS); MirrorLink®; Part 24: Media Meta Data Service
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10354424/01.03.01_60/ts_10354424v010301p.pdf
|
The present document is part of the MirrorLink® specification which specifies an interface for enabling remote user interaction of a mobile device via another device. The present document is written having a vehicle head-unit to interact with the mobile device in mind, but it will similarly apply for other devices, which provide a colour display, audio input/output and user input mechanisms. Current MirrorLink solutions are concentrated on utilization of MirrorLink Client’s main display to mirror applications or provide variety services on the MirrorLink Server. However, there are so many MirrorLink Clients which have several other displays, such as cluster display panel, Heads-up Display (HUD) and so on. Instead of applications mirroring, using these displays, the driver and the passenger can be provided with a variety meta information such as turn by turn information, photo or graphic information, meta data information of audio and video clip, text information, etc. Those Meta Information Data Services are based on the SBP (Service Binary Protocol) framework. The present document specifies media meta data service based on SBP (Service Binary Protocol) framework. By receiving this data, the MirrorLink Client (e.g. a car) can provide media information to driver and passenger e.g. through the car's cluster display panel, or heads-up display.
|
103 525-1
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 1: Protocol Implementation Conformance Statement (PICS); Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352501/02.01.01_60/ts_10352501v020101p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specifications for security algorithms as specified in ETSI TS 102 941 [1] and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 406 [i.3].
|
103 525-1
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 1: Protocol Implementation Conformance Statement (PICS)
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352501/01.02.02_60/ts_10352501v010202p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specifications for security algorithms as specified in ETSI TS 102 941 [1] and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.2] and ETSI ETS 300 406 [i.3].
|
103 523-5
|
CYBER; Middlebox Security Protocol; Part 5: Enterprise Network Security
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352305/01.01.01_60/ts_10352305v010101p.pdf
|
The present document specifies a protocol implementation profile to enable secure communication between IPsec-protected network endpoints while enabling network operations. The Enterprise Network Security profile depends on two protocols in the IPsec family of protocols. First, Internet Key Exchange Protocol Version 2 (IKEv2) [1] is used to establish Security Associations (SAs). In this profile, when certificates are used to provide authentication in IKEv2, those certificates include an extension to provide notice that this profile is being used. Second, the IP Encapsulating Security Payload (ESP) [i.2] is used to encrypt packets. This profile describes two deployment scenarios. In the first one, one of the IPsec peers is inside the enterprise and the other one is outside the enterprise. In the other scenario, both IPsec peers are inside the enterprise. This profile describes the Diffie-Hellman key exchange, and it specifies the certificate extension that provides visibility information to indicate that the ENS profile is being used. The actions the IPsec peers take upon receiving the visibility information in the certificate extension and structure of the policy included in the visibility information are not normatively defined; however, capabilities for an optional "Enterprise Network Security aware IPsec peer" are defined. The means by which the IPsec endpoints obtain the longer- lived Diffie-Hellman public/private key pairs is specified, and some examples are provided. A variant of the ENS profile is also provided to enable visibility in circumstances where the operator of an IPsec peer has been informed by other means that packets can be decrypted and inspected. The present document also includes the security guarantees made by the ENS profile, based on the security guarantees of the IPsec family of protocols.
|
103 523-3
|
CYBER; Middlebox Security Protocol; Part 3: Enterprise Transport Security
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352303/01.03.01_60/ts_10352303v010301p.pdf
|
The present document specifies the "Enterprise Transport Security" profile to enable secure communication sessions between network endpoints whilst enabling network operations. The Enterprise Transport Security (ETS) profile enables use of Transport Layer Security (TLS) version 1.3 [2] in, for example, compliance constrained environments. The present document describes three Enterprise Transport Security architectures: • In the first architecture, both the TLS 1.3 client and the Enterprise Transport Security server are located inside the enterprise. • In the second architecture, the server is an Enterprise Transport Security server inside the enterprise and the TLS 1.3 client is external to the enterprise. TLS 1.3 is terminated at the enterprise edge such that Enterprise Transport Security is used only inside the enterprise. • In the third architecture, the TLS 1.3 server is external to the enterprise and the TLS 1.3 client is internal to the enterprise. TLS 1.3 is again terminated at the network edge such that Enterprise Transport Security is used only inside the enterprise. The Diffie-Hellman key exchange and visibility information for indicating the Enterprise Transport Security profile setup is specified. The actions of the client on receiving the visibility information and structure of the policy included in the visibility information are not normatively defined; however, capabilities for an "Enterprise Transport Security aware client" are defined in annex B, which is optional. The means by which the Enterprise Transport Security endpoints share the Diffie-Hellman key with key consumers is specified, and examples are provided. The present document describes a variant of the Enterprise Transport Security profile in annex A for circumstances in which visibility information is not suitable and in which the client operator has been informed by other means that connections can be inspected. The means by which the client operator is informed is out of scope. The present document also includes the security assurances made by the Enterprise Transport Security profile, based on the security assurances of TLS 1.3. Annex C gives details of the MSP profile capabilities that are applicable to the Enterprise Transport Security profile, taken from the draft specification of ETSI TS 103 523-1 [i.1], such that this MSP Part may be a standalone document. A final mapping of MSP profile capabilities to the Enterprise Transport Security profile is left to a future version of the present document.
|
103 523-2
|
CYBER; Middlebox Security Protocol; Part 2: Transport layer MSP, profile for fine grained access control
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352302/01.02.01_60/ts_10352302v010201p.pdf
|
The present document specifies a protocol to enable secure transparent communication sessions between network endpoints with one or more middleboxes between these endpoints, using data encryption and integrity protection, as well as authentication of the identity of the endpoints and the identity of any middlebox present. This protocol can be mapped to the abstract MSP protocol capability requirements in ETSI TS 103 523-1 [i.5]. The Middlebox Security Protocol builds on TLS 1.2 [1] and is an extensively modified version of the mcTLS protocol [i.1]. Whilst basic concepts are inherited from the mcTLS variant, the protocol specified in the present document also contains significant additional functionality and feature changes that would render it incompatible with the original version published. The present document focuses on TLMSP usage with TCP as it is the most common usage. Usages with other transport protocols are possible but left out of scope. In the remainder of the present document, unless otherwise noted, the word TLS refers to TLS 1.2 [1]. The present document defines a set of five sub-protocols for specific purposes: Handshake (authenticating endpoints and middleboxes and negotiating cryptographic configuration among those entities); Alert (signalling errors and notifications); Application (carrying data generated by higher layers); ChangeCipherSpec (signalling the activation of the negotiated cryptographic configuration) and a Record protocol, (responsible for applying the activated security configuration to all of the other aforementioned sub-protocols). Since TLMSP is a generic protocol, usable with a wide range of applications, issues related to mapping of application-specific security policy to explicit configurations of TLMSP is largely left out of scope. Further, out-of-band provisioning aspects relating to policies, pre-configuration of the client, details on actions in error situations are also out of scope. While some informal discussion on the security properties of TLMSP is provided, a complete (formal) security analysis of the protocol is currently left out of scope. A reference implementation of TLMSP is being developed and can be accessed at [i.7].
|
103 523-1
|
CYBER; Middlebox Security Protocol; Part 1: MSP Framework and Template Requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352301/01.01.01_60/ts_10352301v010101p.pdf
|
The present document is the first part of the Middlebox Security Protocol (MSP) series [i.22]. It is intended to be used by MSP profile developers, MSP profile implementors and MSP specification writers to create MSP profiles and analyse their security. The present document does not specify an MSP profile itself. The present document defines a security baseline that MSP profiles fulfil to be included in the MSP series. This baseline (defined via the MSP Framework and MSP Template Requirements) facilitates creation of MSP profiles for a wide array of implementations and applications, by simplifying the security analysis required for each profile. The present document is intended to be a human-readable guide to the security methodology and principles applied to create the MSP Framework and resulting MSP Template Requirements (see Clauses 6.2 to 6.5). Clause 5 and Clause 6, together with profile-specific analysis, form the security analysis for the MSP series. The present document is not and does not attempt to be a security proof; security proofs are only as strong as the assumptions made [i.20] and can lead to a false sense of security [i.25]. The present document describes the motivations behind MSP's creation, how MSP differs to previous middlebox protocols and some of MSP's architectures. The present document introduces the MSP Framework: a common set of security provisions that underpins all MSP specifications (MSP Template Requirements). The present document describes the motivation for having such a framework, the issues addressed by it and the four principles that guided its creation. The remainder of the present document defines the usage and applicability of the MSP Framework to subsequent parts of the MSP series: how the MSP Framework is to be used by MSP profile developers, MSP profile implementors and MSP specification writers. The present document includes informative annexes to aid readers in its usage. Annex A contains a non-exhaustive list of use cases for MSP. Annex B contains an exemplar MSP Conformance Analysis, performed against the Enterprise Transport Security (ETS) profile, ETSI TS 103 523-3 [i.6]. Annex C describes how a traditional TLS split proxy does not meet the MSP standard set out in the present document. Comprehensive mitigations for all potential attacks are out of scope. Security requirements of generic and well-known cryptographic algorithms, and assessment of security properties of cryptographic primitives, are out of scope. Attacks that are not attacks on the MSP specification itself, such as implementation vulnerabilities, are out of scope.
|
103 521
|
5 GHz RLAN; Receiver Blocking Performance
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103521/01.01.01_60/ts_103521v010101p.pdf
|
The present document specifies Receiver Blocking for 5 GHz RLAN devices.
|
103 504
|
Speech and multimedia Transmission Quality (STQ); Methods and procedures for evaluating performance of voice-controlled devices and functions: far talk voice assistant devices
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103504/01.01.01_60/ts_103504v010101p.pdf
|
The present document defines test methods, performance metrics and requirements for the voice assistance functionality of devices, including devices meant to be used in far talk conditions. The methods include definition of: input speech signals, positional relations of talkers and devices; acoustic environment characterization and reproduction, including background noise and reverberation; and collection of performance characteristics and statistical analyses. The test methods, performance metrics and requirements of devices meant to be used in close and near talk conditions are out of scope. The voice call functionality of voice assistant devices are out of scope and covered by ETSI ES 202 738 (narrowband) [i.1], ETSI ES 202 740 (wideband) [i.2] and ETSI TS 102 925 (super-wideband) [i.3].
|
103 543
|
Mobile Standards Group (MSG); Pan-European eCall In-Vehicle Systems; Guidelines for IVS conformity assessment
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103543/01.01.01_60/ts_103543v010101p.pdf
|
The scope of the present document is to provide technical guidelines for assessing device conformity to Pan-European eCall (according to CEN EN 16072:2015 [i.2]) and essential performance (CEN EN 16072 [i.3], ETSI TS 103 428 [i.4] and CEN EN 15722:2015 [i.6]). The present document compiles existing test cases / procedures and guides device suppliers and integrators by differentiating between regulatory and functional test cases. The resulting compilation of test procedures is a guideline towards regulatory conformance declaration mandated by the EU commission and IVS full functional conformance self-declaration in regards to Pan-European eCall. This assessment is also seen as a suitable preparation for the type approval homologation. The main purpose of the present document is to: a) Analyse existing regulations on Pan European eCall and provide a conformance relevant list of test cases based on existing specifications. b) Guide device supplier and integrators by evaluating test case relevance (regulatory and functional). This provides an efficient method for indication of Pan-European eCall conformance. c) Assist device suppliers and integrators in the vehicle type approval homologation.
|
103 532
|
CYBER; Attribute Based Encryption for Attribute Based Access Control
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103532/01.02.01_60/ts_103532v010201p.pdf
|
The present document specifies trust models, functions and protocols using attribute based encryption as a foundation of an attribute based access control scheme. It covers both the Ciphertext-Policy (CP-ABE) and Key-Policy (KP-ABE) variants of Attribute-Based Encryption. The specifications address the following aspects: • Identification of an ABE scheme covering both the Ciphertext-Policy and Key-Policy variants. • Definition of interactions between the data sources, the service providers and the authority releasing attributes and key material. • Mechanisms for keys, policies, and attributes distribution. • Mechanisms for secret key expiration and revocation. • Definition of semantics for a basic set of attributes to ensure interoperability. • Mapping to a standard Public Key Infrastructure X.509. • Mapping to a standard assertion protocol (SAML). • Definition of a policy schema for data access control. • Identification of limitations compared to traditional ABAC features. • Translation rules to XACML. • Definition of new protocol bindings when existing bindings do not cover the deployment scenario (e.g. a CoAP binding for the IoT case).
|
103 531
|
Environmental Engineering (EE); Impact on ICT equipment architecture of multiple AC, -48 VDC or up to 400 VDC power inputs
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/103531/01.02.01_60/ts_103531v010201p.pdf
|
The present document is applicable to the case of multiple power feeding configurations at the input of ICT equipment in ICT system. The present document describes the combination of three power interfaces as A1 (AC), A (-48 VDC), P or A3 (up to 400 VDC) that could potentially be used single or in combination for each input. The present document also provides details of the power structure within the ICT equipment, between the ICT equipment interfaces and ICT equipment system loads that is inclusive of system power converters. The input power configurations are categorized to allow for better understanding and identification of each new multiple power feeding interface, providing details of the impacts and benefits of adopting them. Information is also provided on the impact on battery test function when used with the different dual power inputs combinations. Lastly requirements are given for avoiding the potential risk of voltage back feeding from one input to the other and for general isolation requirements in all multiple power feeding configurations.
|
103 525-3
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT); Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352503/02.01.01_60/ts_10352503v020101p.pdf
|
The present document provides parts of the Abstract Test Suite (ATS) for ITS PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to provide a basis for conformance tests for security communication over GeoNetworking equipment in order to guarantee interoperability between different manufacturers' equipment. The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology.
|
103 525-3
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352503/01.02.02_60/ts_10352503v010202p.pdf
|
The present document provides parts of the Abstract Test Suite (ATS) for ITS PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to provide a basis for conformance tests for security communication over GeoNetworking equipment in order to guarantee interoperability between different manufacturers' equipment. The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology.
|
103 525-2
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 2: Test Suite Structure and Test Purposes (TSS & TP); Release 2
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352502/02.01.01_60/ts_10352502v020101p.pdf
|
The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology.
|
103 525-2
|
Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS PKI management; Part 2: Test Suite Structure and Test Purposes (TSS & TP)
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103500_103599/10352502/01.02.02_60/ts_10352502v010202p.pdf
|
The present document provides the Test Suite Structure and Test Purposes (TSS & TP) for PKI management as defined in ETSI TS 102 941 [1] in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) are used as a basis for the test methodology.
|
103 491
|
DTS-UHD Audio Format; Delivery of Channels, Objects and Ambisonic Sound Fields
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103491/01.02.01_60/ts_103491v010201p.pdf
|
The present document describes a compressed audio delivery system comprised of a metadata component and a compressed audio component. This system is referred to as DTS-UHD. The stream and metadata structures described here allow efficient delivery of immersive audio. Additionally, the bitstream format of a new audio compression engine is defined. DTS-UHD supports delivery of Channel-Based Audio (CBA), Object-Based Audio (OBA) and High Order Ambisonic presentations up to the fourth order (HOA Soundfields). This support includes the metadata for signaling content, loudness and dynamics, and the necessary coefficients for rendering the final presentation. The present document is organized into two main parts, with clauses 4 through 7 describing the DTS-UHD metadata and some system interfaces, which is independent of the coding scheme being used. Clauses 8 through 10 describe the Audio Compression Engine (ACE), which is designed for efficient delivery of compressed audio in broadcast and streaming environments.
|
103 487
|
CYBER; Baseline security requirements regarding sensitive functions for NFV and related platforms
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103487/01.01.01_60/ts_103487v010101p.pdf
|
The present document defines security baseline requirements for sensitive functions including lawful interception (LI) and retained data (RD) in an NFV hardware/platform environment.
|
103 486
|
CYBER; Identity Management and Discovery for IoT
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103486/01.01.01_60/ts_103486v010101p.pdf
|
The present document describes a model of secure and attestable identity management applicable to IoT devices. The present document defines a data structure, described as Authority-Attribute Trees, for managing identifiers and properties of a device (as attributes), where identifiers and properties are exposed in a number of use cases including discovery, attachment and communication. The present document outlines the requirements for cryptographic methods to establish trust in Authority-Attribute Trees. The present document does not define or make recommendations about policies for users or devices with regards to revealing identity information, or accepting or rejecting discovery based on this information.
|
103 485
|
CYBER; Mechanisms for privacy assurance and verification
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103485/01.01.01_60/ts_103485v010101p.pdf
|
The present document defines the means to enable assurance of privacy, using the conventional CIA (Confidentiality, Integrity, Availability) paradigm and with reference to the functional capabilities for privacy protection described in Common Criteria for Information Technology Security Evaluation [1]. The present document addresses privacy assurance within the context of Identity Management following the model described in ETSI TS 103 486 [i.17]. The present document addresses the cases where both transient and persistent identifiers are used, and where identifiers are used in isolation and where identifiers are used in combination. The mechanisms defined in the present document have been informed by the requirements found in articles and recitals of the General Data Protection Regulation (EU) 2016/679 [i.6] (GDPR) and can be considered in assisting in achieving compliance to the requirements in GDPR. NOTE: The GDPR contains a very large number of requirements and the present document addresses only a very small number of the technical ones thus the present document is not a solution to the GDPR but where it may assist in addressing specific requirements this has been identified in the body of the present document. The present document identifies assurance protection levels for privacy and mechanisms for achieving those protection levels. It does not, however, provide any guarantee that application of the mechanisms will prevent abuse of private information and user privacy.
|
103 484-2
|
Smart Cards; Test specification for the Secure Channel interface; Part 2: UICC features (Release 9)
|
TS
|
9.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10348402/09.00.00_60/ts_10348402v090000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC or UICC and UICC application in order to provide compliance to TS 102 484 [1]. The present document specifies the test cases for the Secured APDU - Application to Application type of secure channel and includes tests for: • the characteristics of the Secure Channel interface between the UICC and the UICC-enabled terminal; • the Discovery and Channel Administration; • Key Agreement for Strong Pre-shared Keys - Proprietary Pre-Shared Keys; • the Channel Operation between the UICC-enabled terminal and the UICC. Both tests for UICC capability and UICC applications are specified. The following are out of scope of the present document: • TLS- Application to Application. • IPsec - USB Class to USB Class. • Secured APDU - Platform to Platform. • Strong Pre-shared Keys - GBA key agreement. • Weak Pre-shared Keys - Proprietary Pre-Shared Keys key agreement. • Certificate Exchange key agreement.
|
103 484-1
|
Smart Cards; Test specification for the Secure Channel interface; Part 1: Terminal features (Release 9)
|
TS
|
9.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10348401/09.00.00_60/ts_10348401v090000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the terminal or terminal and terminal application in order to provide compliance to TS 102 484 [1]. The present document specifies the test cases for the Secured APDU - Application to Application type of secure channel and includes tests for: • the characteristics of the Secure Channel interface between the UICC and the UICC-enabled terminal; • the Discovery and Channel Administration; • Key Agreement for Strong Pre-shared Keys - Proprietary Pre-Shared Keys; • the Channel Operation between the UICC-enabled terminal and the UICC. Both tests for Terminal capability and Terminal applications are specified. The following are out of scope of this document: • TLS- Application to Application. • IPsec - USB Class to USB Class. • Secured APDU - Platform to Platform. • Strong Pre-shared Keys - GBA key agreement. • Weak Pre-shared Keys - Proprietary Pre-Shared Keys key agreement. • Certificate Exchange key agreement.
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 16)
|
TS
|
16.4.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/16.04.00_60/ts_103481v160400p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/15.00.00_60/ts_103481v150000p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/14.00.00_60/ts_103481v140000p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/13.00.00_60/ts_103481v130000p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/12.00.00_60/ts_103481v120000p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 481
|
Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 11)
|
TS
|
11.4.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/11.04.00_60/ts_103481v110400p.pdf
|
The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1].
|
103 479
|
Emergency Communications (EMTEL); Core elements for network independent access to emergency services
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103479/01.02.01_60/ts_103479v010201p.pdf
|
The purpose of the present document is to describe the architecture, the core elements and corresponding technical interfaces for network independent access to emergency services. Elements are: Border Control Function (BCF), Emergency Service Routing Proxy (ESRP), Emergency Call Routing Function (ECRF), Public Safety Answering Point (PSAP), the Location Information Server (LIS), and the Call Transfer Bridge (BRIDGE). The described architecture is currently named Next Generation 112 architecture.
|
103 478
|
Emergency Communications (EMTEL); Pan-European Mobile Emergency Application
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103478/01.03.01_60/ts_103478v010301p.pdf
|
The present document is divided into two parts. The first part provides the requirements and functional architecture while the second part provides the protocol and procedures for implementing the Pan-European Mobile Emergency Application (PEMEA). The first part identifies the key functional entities involved in the emergency application architecture, the interfaces between each functional entity, and the requirements on each interface. The second part defines the data exchanges, message, protocols and procedures used across each of the identified PEMEA interfaces. It is recognized that many existing application implementations combine the functional entities identified in the present document into a single entity. The most common example of combined functional entities is the combined Application Provider (AP) and PSAP Service Provider (PSP), these are common because it is often the PSAP that writes or engages a third-party to write a local emergency application that interfaces directly with the PSAP. The present document does not seek to disallow integrated node implementations, however, it does not define how additional applications or application providers using proprietary Application Programming Interfaces (APIs) and protocols can provide PEMEA extended features, such solutions are left to the integrated node providers.
|
103 466
|
Digital Audio Broadcasting (DAB); DAB audio coding (MPEG Layer II)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103466/01.02.01_60/ts_103466v010201p.pdf
|
The present document defines the method to code and transmit audio services using the MPEG Layer II audio coder for Digital Audio Broadcasting (DAB) (ETSI EN 300 401 [1]) and details the necessary mandatory requirements for decoders. The permitted audio modes and the data protection and encapsulation are detailed. This audio coding scheme permits the full use of the PAD channel for carrying dynamic labels and user applications.
|
103 465
|
Smart Secure Platform (SSP); Requirements Specification (Release 16)
|
TS
|
16.6.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103465/16.06.00_60/ts_103465v160600p.pdf
|
The present document defines the use cases and requirements for the definition of the interfaces and protocols for interfacing with a secure element. This secure element is called Smart Secure Platform (SSP).
|
103 465
|
Smart Cards; Smart Secure Platform (SSP); Requirements Specification (Release 15)
|
TS
|
15.3.0
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103465/15.03.00_60/ts_103465v150300p.pdf
|
The present document defines the use cases and requirements for the definition of the interfaces and protocols for interfacing with a secure element. This secure element is called Smart Secure Platform (SSP).
|
103 464
|
Hybrid Broadcast Broadband TV; Application Discovery over Broadband
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103464/01.03.01_60/ts_103464v010301p.pdf
|
The present document augments clause 6 of ETSI TS 102 796 [1], which states that broadcast-related applications are signalled as part of the broadcast. It defines a method for discovery of HbbTV® applications in settings where AIT signalling via the broadcast network is not available to the terminal. In this situation, an HbbTV® terminal may discover broadcast-related HbbTV® services via a broadband internet connection.
|
103 463-2
|
Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Key Performance Indicators for Sustainable Digital Multiservice Areas; Part 2: Global KPIs for Sustainable Digital Multiservice Areas
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10346302/01.01.01_60/ts_10346302v010101p.pdf
|
The present document defines Global Key Performance Indicators (Global KPIs) to describe the social, environmental sustainability and economic attractiveness of Sustainable Digital Multiservice Areas - addressing urban (cities) and rural communities. The Global KPIs are combinations of the Key Performance Indicators selected from those of ETSI TS 103 463-1 [i.1] which are either measurable or based on publicly available data and relevant to the Sustainable Digital Multiservice Area (SDMA) under consideration.
|
103 463-1
|
Access, Terminals, Transmission and Multiplexing (ATTM); Sustainable Digital Multiservice Communities; Key Performance Indicators for Sustainable Digital Multiservice Areas; Part 1: Description of Key Performance Indicators
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10346301/01.02.01_60/ts_10346301v010201p.pdf
|
The present document defines indicators (KPIs) for Smart Cities expressing city level in terms of People, Planet, Prosperity, Governance and Propagation.
|
103 462
|
Lawful Interception (LI); Inter LEMF Handover Interface
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103462/01.02.01_60/ts_103462v010201p.pdf
|
The present document specifies the LEMF to LEMF interface to support (as a minimum) European Investigation Orders (EIOs) related to LI and/or RD. The present document aims to be capable of securely handling real-time and stored data transfer between LEMFs in accordance with ETSI TS 102 232 parts 1 [6] to 7 [12] and the related ETSI TS 133 108 [5] for LI. In the present document RD is for further study. Local LI handover interfaces frequently use dedicated networks for delivery with local specific security features. With the EIO Directive in place, there is a need to have a common Handover Interface to allow real-time exchange between LEMFs that can be located in different countries, under different jurisdictions.
|
103 461
|
Digital Audio Broadcasting (DAB); Domestic and in-vehicle digital radio receivers; Minimum requirements and Test specifications for technologies and products
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103461/01.02.02_60/ts_103461v010202p.pdf
|
The present document describes the minimum requirements for digital radios, both domestic and in-vehicle, and the necessary test methods that lead to compliance with the requirements. It may be used as the technical basis for a Digital Radio Certification Mark scheme. A Digital Radio Certification Mark is designed to be used on product packaging and provides an easily recognized mark to correspond to public information campaigns on the necessary requirements for consumers to make a switch to digital radio. Manufacturers are, of course, free to include additional features or increased performance compared to the minimum requirements specified in the present document. This version adds support for tuned ensemble alarm announcements for all receivers to the minimum requirements and provides clarification for the text display requirements which now accommodate the place of the regional profiles. There are consequential changes to the core technology testing and there are two additional product tests. These updates reflect changes to the DAB standards base since 2017.
|
103 458
|
CYBER; Application of Attribute Based Encryption (ABE) for PII and personal data protection on IoT devices, WLAN, cloud and mobile services - High level requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103458/01.01.01_60/ts_103458v010101p.pdf
|
The present document specifies high level requirements for the application of Attribute Based Encryption (ABE) to protect PII and personal data on IoT devices/services, cloud services, Wireless Local Area Networks and mobile services, where access to data has to be given to multiple parties and under different conditions. With a main focus on the confidentiality of data, including personal data and Personally Identifiable Information, the present document may help in supporting the General Data Protection Regulation [i.19]. The following use cases are described: 1) The Mobile use case describes a situation of user access from less trusted networks. The objective is to provide user identity protection preserving disclosure to unauthorized entity. 2) The federated WLAN use case where users can access different WLAN networks using their credentials - issued by different authorities/domains - while preserving their privacy. 3) Many Internet of Things use cases or edge scenarios where data access mechanisms are actioned either in the network or on the device. 4) The Cloud use case where a third party accesses personal data from the Cloud Service Provider. The present document also provides recommendations on the ABE scheme to use for each use case.
|
103 457
|
CYBER; Trusted Cross-Domain Interface: Interface to offload sensitive functions to a trusted domain
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103457/01.02.01_60/ts_103457v010201p.pdf
|
The present document specifies a high-level service-oriented interface, as an application layer with a set of mandatory functions, to access secured services provided by, and executed in a More Trusted Domain. The transport layer is out of scope and left to the architecture implementation. This interface is not considered as a replacement of the already existing technologies (such as PKCS#11, KMIP, etc.) but rather operating on top of these.
|
103 448
|
AC-4 Object Audio Renderer for Consumer Use
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103448/01.01.01_60/ts_103448v010101p.pdf
|
The present document defines an extension to the AC-4 codec. The present document specifies a consumer object-based audio renderer for use with the AC-4 codec as specified in ETSI TS 103 190-2 [1], and the object-based audio metadata specified therein. The renderer takes the object audio essence and the corresponding metadata defined in ETSI TS 103 190-2 [1] as inputs, and produces loudspeaker feeds for consumer loudspeaker layouts.
|
103 443-6
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 6: 6RD
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344306/01.01.01_60/ts_10344306v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of the IPv6 transition technology 6RD as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is Part 6 of a multi-part series and presents the operational aspects of the IPv6 transition technology 6RD across the cable network domains. Only those elements of the network that have to be engineered to operate the IPv6 transition technology 6RD are presented. Descriptions and interface details of network elements that do not change are already addressed by the relevant equipment cable standards and therefore this information is not included in the present document. The conformity of the 6RD implementation is relevant when assessing its implementation and operational requirements across the cable network to ensure the implementation is correctly engineered to conform to the requirements of the base standard ETSI TS 101 569-1 [1]. These conformance tests are not specified in the present document as they are already specified by ETSI TS 103 243 parts 1 [14] to 3 [16]. The operational aspects for the IPv6 transition technology 6RD are considered when engineered end to end across the cable network domains; • CPE Home Networking Domain • Access Network Domain • Core Network Domain • Data Centre Domain • DMZ Service Domain • Transit and Peering Domain • Management and Monitoring Domain • Security Domain The present document specifies the requirements to be considered when the defined IPv6 transition technology 6RD is engineered across the cable network domains.
|
103 443-5
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 5: 464XLAT
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344305/01.01.01_60/ts_10344305v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of the IPv6 transition technology 464XPAT as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is part 5 of a multi-part series and presents the operational aspects of the IPv6 transition technology 464XPAT across the cable network domains. Only those elements of the network that have to be engineered to operate the IPv6 transition technology 464XPAT are presented. Descriptions and interface details of network elements that do not change are already addressed by the relevant equipment cable standards and therefore this information is not included in the present document. The conformity of the 464XPAT implementation is relevant when assessing its implementation and operational requirements across the cable network to ensure the implementation is correctly engineered to conform to the requirements of the base standard ETSI TS 101 569-1 [1]. These conformance tests are not specified in the present document as they are already specified by ETSI TS 103 242 part 1 [11] to 3 [13]. The operational aspects for the IPv6 transition technology 464XPAT are considered when engineered end to end across the cable network domains; • CPE Home Networking Domain • Access Network Domain • Core Network Domain • Data Centre Domain • DMZ Service Domain • Transit and Peering Domain • Management and Monitoring Domain • Security Domain The present document specifies the requirements to be considered when the defined IPv6 transition technology 464XPAT is engineered across the cable network domains.
|
103 443-4
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 4: MAP-E
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344304/01.01.01_60/ts_10344304v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of the IPv6 transition technology MAP-E as defined by ETSI TS 101 569-1 (IPv6 Transition Requirements) [1] implemented within an integrated broadband cable network end to end across its network domains. The present document is part 4 of a multi-part series and presents the operational aspects of the IPv6 transition technology MAP-E across the cable network domains. Only those elements of the network that have to be engineered to operate the IPv6 transition technology MAP-E are presented. Descriptions and interface details of network elements that do not change are already addressed by the relevant equipment cable standards and therefore this information is not included in the present document. The conformity of the MAP-E implementation is relevant when assessing its implementation and operational requirements across the cable network to ensure the implementation is correctly engineered to conform to the requirements of the base standard ETSI TS 101 569-1 [1]. These conformance tests are not specified in the present document as they are already specified by ETSI TS 103 239 parts 1 [5] to 3 [7]. The operational aspects for the IPv6 transition technology MAP-E are considered when engineered end to end across the cable network domains: • CPE Home Networking Domain. • Access Network Domain. • Core Network Domain. • Data Centre Domain. • DMZ Service Domain. • Transit and Peering Domain. • Management and Monitoring Domain. • Security Domain. The present document specifies the requirements to be considered when the defined IPv6 transition technology MAP-E is engineered across the cable network domains.
|
103 443-3
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 3: DS-Lite
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344303/01.01.01_60/ts_10344303v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of the IPv6 transition technology DS-Lite as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is part 3 of a multi-part series and presents the operational aspects of the IPv6 transition technology DS-Lite across the cable network domains. Only those elements of the network that have to be engineered to operate the IPv6 transition technology DS-Lite are presented. Descriptions and interface details of network elements that do not change are already addressed by the relevant equipment cable standards and therefore this information is not included in the present document. The conformity of the DS-Lite implementation is relevant when assessing its implementation and operational requirements across the cable network to ensure the implementation is correctly engineered to conform to the requirements of the base standard ETSI TS 101 569-1 [1]. These conformance tests are not specified in the present document as they are already specified by ETSI TS 103 241 parts 1 to 3 [8], [9] and [10]. The operational aspects for the IPv6 transition technology DS-Lite are considered when engineered end to end across the cable network domains: • CPE Home Networking Domain • Access Network Domain • Core Network Domain • Data Center Domain • DMZ Service Domain • Transit and Peering Domain • Management and Monitoring Domain • Security Domain The present document specifies the requirements to be considered when the defined IPv6 transition technology DS-Lite is engineered across the cable network domains.
|
103 443-2
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 2: NAT64
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344302/01.01.01_60/ts_10344302v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of the IPv6 transition technology NAT64 as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is part 2 of a multi-part series and presents the operational aspects of the IPv6 transition technology NAT64 across the cable network domains. Only those elements of the network that have to be engineered to operate the IPv6 transition technology NAT64 are presented. Descriptions and interface details of network elements that do not change are already addressed by the relevant equipment cable standards and therefore this information is not included in the present document. The conformity of the NAT64 implementation is relevant when assessing its implementation and operational requirements across the cable network to ensure the implementation is correctly engineered to conform to the requirements of the base standard ETSI TS 101 569-1 [1]. These conformance tests are not specified in the present document as they are already specified by ETSI TS 103 243 parts 1 [15] to 3 [17]. The operational aspects for the IPv6 transition technology NAT64 are considered when engineered end to end across the cable network domains: • CPE Home Networking Domain • Access Network Domain • Core Network Domain • Data Centre Domain • DMZ Service Domain • Transit and Peering Domain • Management and Monitoring Domain • Security Domain The present document specifies the requirements to be considered when the defined IPv6 transition technology NAT64 is engineered across the cable network domains.
|
103 443-1
|
Integrated broadband cable telecommunication networks (CABLE); IPv6 Transition Technology Engineering and Operational Aspects; Part 1: General
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10344301/01.01.01_60/ts_10344301v010101p.pdf
|
The present document presents the engineering and operational requirements for the application of IPv6 transition technologies as defined by ETSI TS 101 569-1 [1] (IPv6 Transition Requirements) implemented within an integrated broadband cable network end to end across its network domains. The present document is part 1 of a multi-part series and presents a generic view of a typical end to end cable network when considering the key aspects to engineer and operate the IPv6 transition technology across its network domains. The technical requirements addressing each network domain relative to the IPv6 transition technology in question is described in the clauses of the part specific to the IPv6 transition technology. The operational aspects for the IPv6 transition technologies, NAT64, DS-Lite, MAP-E, 464XLAT and 6RD are considered when engineered end to end across the cable network domains: • CPE Home Networking Domain • Access Network Domain • Core Network Domain • Data Centre Domain • DMZ Service Domain • Transit and Peering Domain • Management and Monitoring Domain • Security Domain The present document specifies the requirements to be considered when the defined IPv6 transition technology DS-Lite is engineered across the cable network domains.
|
103 436
|
Reconfigurable Radio Systems (RRS); Security requirements for reconfigurable radios
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103436/01.02.01_60/ts_103436v010201p.pdf
|
The present document defines the security requirements for reconfigurable radio systems arising from the use case analysis in ETSI TR 103 087 [i.1]. The present document applies to the lifecycle of Radio Application Packages between a Radio application store and an RRS Reconfigurable Equipment.
|
103 434
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103434/01.01.01_60/ts_103434v010101p.pdf
|
The present document focuses on Gigabit Home Networking for Very High Speed Internet video distribution using video transcoding for the distribution of HD and UHD video streams over SISO and MIMO PLT networks [i.1]. The present document defines the transcoding of HD and UHD video for improvement of the house coverage of powerline networks for existing or forthcoming new video services as streaming and VOD MIMO-PLT and filling the gap between MIMO-PLT channels capacity and new services as UHD and HD video for forthcoming UHDTV, namely transcoding of H264/AVC into HEVC/H265. The SISO/MIMO Powerline networks channels have time varying capacities depending on noises, overage, range as HD and UHD encoded in H264/AVC video streams have additional bit rate compared to stream [3], [4] encoded in HEVC/H265, the usage of transcoding for video streaming over Powerline using SISO & MIMO PLT modems is explored by testing. The present document includes the technical specification for video transcoding and transportation standards impact on Powerline Networks coverage and produce technical guidance to the Powerline telecommunication vendors to cope with very high rate services over Powerline communication for the UHD and HD video transcoding coding.
|
103 433-3
|
High-Performance Single Layer High Dynamic Range (HDR) System for use in Consumer Electronics devices; Part 3: Enhancements for Hybrid Log Gamma (HLG) transfer function based High Dynamic Range (HDR) Systems (SL-HDR3)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10343303/01.02.01_60/ts_10343303v010201p.pdf
|
of the document Informative Clause
|
103 433-2
|
High-Performance Single Layer High Dynamic Range (HDR) System for use in Consumer Electronics devices; Part 2: Enhancements for Perceptual Quantization (PQ) transfer function based High Dynamic Range (HDR) Systems (SL-HDR2)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10343302/01.03.01_60/ts_10343302v010301p.pdf
|
of the document Informative Clause
|
103 433-1
|
High-Performance Single Layer High Dynamic Range (HDR) System for use in Consumer Electronics devices; Part 1: Directly Standard Dynamic Range (SDR) Compatible HDR System (SL-HDR1)
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10343301/01.04.01_60/ts_10343301v010401p.pdf
|
of the document Informative 1 Clause
|
103 433
|
High-Performance Single Layer Directly Standard Dynamic Range (SDR) Compatible High Dynamic Range (HDR) System for use in Consumer Electronics devices (SL-HDR1)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103433/01.01.01_60/ts_103433v010101p.pdf
|
The present document specifies the SDR-to-HDR content-based dynamic metadata and the post-decoding process enabling reconstruction of an HDR signal from an SDR signal and the specified metadata. This reconstruction process is typically invoked in a Consumer Electronics device such as a TV set, a smartphone, a tablet, or a Set Top Box. Besides, it provides information and recommendations on the usage of the described HDR system.
|
103 430
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103430/01.01.01_60/ts_103430v010101p.pdf
|
The present document defines a method to improve the coexistence by mitigating the interference between the DSL transceiver and PLT transceiver operating in overlapping frequency band but on different cables. In-home PLT networks operate over the same spectrum as DSL networks. This increases the likelihood of crosstalk between PLT and DSL communications systems. For instance, two home networks that operate at the same frequency range, one over copper twisted-pairs (138 kHz - 30 MHz) and the other over power lines (1,8 MHz - 30 MHz ), would interfere with each other.(ETSI TR 102 930 [i.1]). The DSL and PLT interference environment is discussed in more detail. Communication standards for PLT, have been developed with mechanisms that prevent any interference between various systems within the home environment.
|
103 429
|
Integrated broadband cable telecommunication networks (CABLE); Cable Customer Premises Equipment (CPE) with Integrated Radio and Non-Radio Interfaces; Technical Specification covering the cable equipment technical requirements in support of Harmonised Standards for the essential requirements of article 3.1b of the Directive 2014/53/EU
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103429/01.01.01_60/ts_103429v010101p.pdf
|
The present document provides technical requirements for cable CPE with integrated radio and non-radio interfaces in support of Harmonised Standards for the essential requirements of article 3.1b of the Radio Equipment Directive 2014/53/EU [i.1]. Cable equipment comprises integrated non-radio and radio network interfaces. These functions are integrated either on the same integrated electronic components on the same printed circuit board or by separate integrated components on the same printed circuit boards but housed in the same equipment enclosure. The non-radio function is the Cable RF as specified by ETSI EN 302 878-2 [1] for data communication services and by ETSI EN 300 429 [2] for video communication services. The radio function is a wireless local area network operating in the 2,4 GHz and 5 GHz frequency bands according to IEEE 802.11 [3]. NOTE: Cable equipment does not comprise separate radio and non-radio products that are combined in one enclosure. Where cable equipment of this type exist then the essential requirements of article 3.1b of Directive 2014/53/EU [i.1] apply to the equipment and the equipment requirements are as specified by ETSI draft harmonised standard ETSI EN 303 446-1 [i.5], at the time of writing it is under development ETSI TC ERM WGEMC.
|
103 428
|
Mobile Standards Group (MSG); eCall HLAP Interoperability Testing
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103428/01.02.02_60/ts_103428v010202p.pdf
|
The present document defines Interoperability Test Descriptions for the eCall High Level Application Protocol (HLAP).
|
103 427
|
Core Network and Interoperability Testing (INT); Framework of Internet related performance measurements [Recommendation ITU-T Q.3960 (2016)]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103427/01.01.01_60/ts_103427v010101p.pdf
|
The present document is a transposition of Recommendation ITU-T Q.3960 [1] without modifications.
|
103 426
|
Publicly Available Specification (PAS); Smart Machine-to-Machine communications (SmartM2M) Home Gateway Initiative RD048-HG Requirements For HGI Open Platform 2.1
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103426/01.01.01_60/ts_103426v010101p.pdf
| |
103 425
|
Publicly Available Specification (PAS); Smart Machine-to-Machine communications (SmartM2M) Home Gateway Initiative RD039-Requirements for Wireless Home Area Networks (WHANs) Supporting Smart Home Services
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103425/01.01.01_60/ts_103425v010101p.pdf
| |
103 424
|
Publicly Available Specification (PAS); Smart Machine-to-Machine communications (SmartM2M) Home Gateway Initiative RD036-Smart Home architecture and system requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103424/01.01.01_60/ts_103424v010101p.pdf
|
The rapid increase in the number of smart devices in the home, from entertainment systems to appliances and medical devices and the now near ubiquitous broadband connectivity have created a significant new potential market for service providers. However, in order to exploit this market and provide an integrated customer experience there is a central component which is still missing - a set of standards for the home gateway which will enable interoperability between smart home entities. Defining smart home related standards for the home gateway can benefit the market in several ways: • Avoiding duplication of hardware and software and the associated costs of having several disparate systems. • Providing opportunities for new 'blended' services based on combining data from different HANs and appliances. • Enabling automated, intelligent reaction to the environment - e.g. demand-side energy management. The present document defines a smart home system architecture and derives requirements for the Home Gateway.
|
103 420
|
Backwards-compatible object audio carriage using Enhanced AC-3
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103420/01.02.01_60/ts_103420v010201p.pdf
|
The present document specifies an extension to the E-AC-3 codec. The extension adds an object-based three-dimensional spatial representation of coded audio information and metadata. It is backward compatible with the one- and two-dimensional channel-based spatial representation of coded audio information as defined in ETSI TS 102 366 [1]. NOTE: In this context, backward compatibility is defined as follows: The three-dimensional spatial representation specified in the present document can be decoded on a device compliant with the syntax and semantics specified in ETSI TS 102 366 [1]. In this case, such a device will output one- or two-dimensional channel-based audio as per the coding algorithm defined in ETSI TS 102 366 [1] alone. Thus, support for decoders specified in ETSI TS 102 366 [1] and associated user experiences are fully maintained with the extension defined herein. The present document specifies the following: 1) Syntax and semantics of the OBA metadata, carried via the extensible metadata delivery format (EMDF), specified in ETSI TS 102 366 [1] 2) Syntax and semantics of metadata to control a tool for conversion of one- or two-dimensional channel-based audio to a higher number of audio signals, part of the three-dimensional spatial representation (JOC) 3) Additional requirements on the E-AC-3 decoder as specified in ETSI TS 102 366 [1] 4) Requirements on the OBA, the JOC tool, the quadrature mirror filter bank tool, packaging the bitstream into ISO based media file format, the signalling in an MPEG DASH media presentation description, and requirements on a MPEG CMAF compliant media file, containing a bitstream as defined in the present document. 5) Informative guidance for conversion from 1) to the ADM as defined in Recommendation ITU-R BS.2076 [i.1]
|
103 418
|
Railway Telecommunications (RT); SMS to Railway numbering plan in roaming environment
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103418/01.01.01_60/ts_103418v010101p.pdf
|
The present document describes the message flows and the specific messages to be used between GSM-R networks to enable numbering plan mapping functionality for the exchange of SMS. In detail: • Message flows covering the different call types using functional numbers as part of the EIRENE numbering plan. • Description of USSD Messages to allow the functional number/E.164 [i.2] mapping between the involved GSM-R network entities. • Description of the SMS address field content to allow presentation of the functional number or E.164 number [i.2] to the terminating party. Mapping of EIRENE/Recommendation ITU-T E.164 [i.2] numbering plans and the resolution of the functional number that belongs to the subscribers located in the home network is out of scope of the present document. NOTE: To minimize standardization and implementation effort, all protocols used to exchange the numbering plan mapping information are standard 3GPP/ITU protocols and only specific settings are used for the exchange of the relevant information.
|
103 412
|
Mobile Standards Group (MSG); Pan-European eCall end to end and in-band modem conformance testing; Prose test specification
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103412/01.03.01_60/ts_103412v010301p.pdf
|
The present document specifies the Pan-European eCall end to end and in-band modem conformance testing. This is a complete test specification. The following information can be found in the present document: • the overall test structure; • the test configurations; • the conformance requirement and reference to the core specifications; • the test purposes; and • a brief description of the test procedure, the specific test requirements and <eventually> short message exchange table; • the default setting of the test parameters; • the applicability of each test case. The present document is valid for a Pan-European (PE) eCall IVS.
|
103 410-12
|
SmartM2M; Extension to SAREF; Part 12: Smart Grid Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341012/02.01.01_60/ts_10341012v020101p.pdf
|
The present document presents SAREF4GRID, an extension of SAREF for the Smart Grid domain.
|
103 410-12
|
SmartM2M; Extension to SAREF; Part 12: Smart Grid Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341012/01.01.01_60/ts_10341012v010101p.pdf
|
The present document presents SAREF4GRID, an extension of SAREF for the Smart Grid domain.
|
103 410-11
|
SmartM2M; Extension to SAREF; Part 11: Lift Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341011/02.01.01_60/ts_10341011v020101p.pdf
|
The present document presents SAREF4LIFT, an extension of SAREF for the Smart Lifts domain.
|
103 410-11
|
SmartM2M; Extension to SAREF; Part 11: Lift Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341011/01.01.01_60/ts_10341011v010101p.pdf
|
The present document presents SAREF4LIFT, an extension of SAREF for the Smart Lifts domain.
|
103 410-10
|
SmartM2M; Extension to SAREF; Part 10: Water Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341010/02.01.01_60/ts_10341010v020101p.pdf
|
The present document presents SAREF4WATR, an extension of SAREF for the Water domain. SAREF4WATR V2.1.1 is a major revision of SAREF4WATR, using updated reference ontology patterns [3] to solve the harmonization needs [i.9], with updated development framework and tools [i.10].
|
103 410-10
|
SmartM2M; Extension to SAREF; Part 10: Water Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341010/01.01.01_60/ts_10341010v010101p.pdf
|
The present document presents SAREF4WATR, an extension of SAREF for the Water domain. SAREF4WATR V2.1.1 is a major revision of SAREF4WATR, using updated reference ontology patterns [3] to solve the harmonization needs [i.9], with updated development framework and tools [i.10].
|
103 410-9
|
SmartM2M; Extension to SAREF; Part 9: Wearables Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341009/02.01.01_60/ts_10341009v020101p.pdf
|
The present document presents the SAREF4WEAR ontology, an extension of SAREF [1] for the Wearables domain. SAREF4WEAR V2.1.1 is a major revision of the SAREF4WEAR, using updated reference ontology patterns [2] to solve the harmonization needs [i.4], with updated development framework and tools [3].
|
103 410-9
|
SmartM2M; Extension to SAREF; Part 9: Wearables Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341009/01.01.01_60/ts_10341009v010101p.pdf
|
The present document presents the SAREF4WEAR ontology, an extension of SAREF [1] for the Wearables domain. SAREF4WEAR V2.1.1 is a major revision of the SAREF4WEAR, using updated reference ontology patterns [2] to solve the harmonization needs [i.4], with updated development framework and tools [3].
|
103 410-8
|
SmartM2M; Extension to SAREF; Part 8: eHealth/Ageing-well Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341008/02.01.01_60/ts_10341008v020101p.pdf
|
The present document presents SAREF4EHAW, an extension of SAREF for the eHealth/Ageing-well Domain.
|
103 410-8
|
SmartM2M; Extension to SAREF; Part 8: eHealth/Ageing-well Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341008/01.01.01_60/ts_10341008v010101p.pdf
|
The present document presents SAREF4EHAW, an extension of SAREF for the eHealth/Ageing-well Domain.
|
103 410-7
|
SmartM2M; Extension to SAREF; Part 7: Automotive Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341007/02.01.01_60/ts_10341007v020101p.pdf
|
The present document presents SAREF4AUTO, an extension of SAREF for the Automotive Domain.
|
103 410-7
|
SmartM2M; Extension to SAREF; Part 7: Automotive Domain
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341007/01.01.01_60/ts_10341007v010101p.pdf
|
The present document presents SAREF4AUTO, an extension of SAREF for the Automotive Domain.
|
103 410-6
|
SmartM2M; Extension to SAREF; Part 6: Smart Agriculture and Food Chain Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341006/02.01.01_60/ts_10341006v020101p.pdf
|
The present document presents SAREF4AGRI, an extension of SAREF for the Smart Agriculture and Food Chain Domain.
|
103 410-6
|
SmartM2M; Extension to SAREF; Part 6: Smart Agriculture and Food Chain Domain
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341006/01.01.02_60/ts_10341006v010102p.pdf
|
The present document presents SAREF4AGRI, an extension of SAREF for the Smart Agriculture and Food Chain Domain.
|
103 410-5
|
SmartM2M; Extension to SAREF; Part 5: Industry and Manufacturing Domains
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341005/02.01.01_60/ts_10341005v020101p.pdf
|
The present document presents SAREF4INMA, a SAREF extension for the Industry and Manufacturing domains. SAREF4INMA V2.1.1 is a major revision of the SAREF4INMA, using updated reference ontology patterns [2] to solve the harmonization needs [i.12], with updated development framework and tools [3].
|
103 410-5
|
SmartM2M; Extension to SAREF; Part 5: Industry and Manufacturing Domains
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341005/01.01.02_60/ts_10341005v010102p.pdf
|
The present document presents SAREF4INMA, a SAREF extension for the Industry and Manufacturing domains. SAREF4INMA V2.1.1 is a major revision of the SAREF4INMA, using updated reference ontology patterns [2] to solve the harmonization needs [i.12], with updated development framework and tools [3].
|
103 410-4
|
SmartM2M; Extension to SAREF; Part 4: Smart Cities Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341004/02.01.01_60/ts_10341004v020101p.pdf
|
The present document presents SAREF4CITY, an extension of SAREF for the Smart Cities domain.
|
103 410-4
|
SmartM2M; Extension to SAREF; Part 4: Smart Cities Domain
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341004/01.01.02_60/ts_10341004v010102p.pdf
|
The present document presents SAREF4CITY, an extension of SAREF for the Smart Cities domain.
|
103 410-3
|
SmartM2M; Extension to SAREF; Part 3: Building Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341003/02.01.01_60/ts_10341003v020101p.pdf
|
The present document presents the SAREF extension for the building domain, based on the ISO 16739 [i.2] standard (IFC).
|
103 410-3
|
SmartM2M; Extension to SAREF; Part 3: Building Domain
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341003/01.01.02_60/ts_10341003v010102p.pdf
|
The present document presents the SAREF extension for the building domain, based on the ISO 16739 [i.2] standard (IFC).
|
103 410-2
|
SmartM2M; Extension to SAREF; Part 2: Environment Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341002/02.01.01_60/ts_10341002v020101p.pdf
|
The present document presents SAREF4ENVI, an extension of SAREF for the Environment Domain.
|
103 410-2
|
SmartM2M; Extension to SAREF; Part 2: Environment Domain
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341002/01.01.02_60/ts_10341002v010102p.pdf
|
The present document presents SAREF4ENVI, an extension of SAREF for the Environment Domain.
|
103 410-1
|
SmartM2M; Extension to SAREF; Part 1: Energy Domain
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341001/02.01.01_60/ts_10341001v020101p.pdf
|
The present document presents SAREF4ENER V2.1.1, the SAREF extension for energy.
|
103 410-1
|
SmartM2M; Extension to SAREF; Part 1: Energy Domain
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/10341001/01.02.01_60/ts_10341001v010201p.pdf
|
The present document presents SAREF4ENER V2.1.1, the SAREF extension for energy.
|
103 407
|
Cross Platform Authentication for limited input hybrid consumer equipment
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103400_103499/103407/01.01.01_60/ts_103407v010101p.pdf
| |
103 389
|
Rail Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways
|
TS
|
3.4.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103389/03.04.01_60/ts_103389v030401p.pdf
|
The present document defines the signalling and media interface between the Network Switching Subsystem and the Fixed Terminal Subsystem in order to provide a clear set of services needed for GSM-R operations. This includes voice call service and available call-related supplementary services. In addition, requirements for specific implementation of the signalling and media interface within either the Network Switching Subsystem or the Fixed Terminal Subsystem are stated where applicable. The present document addresses the Internet Layer and upwards of the Internet Protocol Suite IETF RFC 1122 [i.18] on the signalling and media interface. Any service other than voice call service and call-related supplementary services (such as data services, Short Message Service, etc.) is out of scope of the present document; additional features may be addressed in future releases. The present document does not specify any other interface between the Network Switching Subsystem and the Fixed Terminal Subsystem nor does it cover any internal interfaces of either NSS or FTS. Such interfaces may be addressed in a future release of the present document. The present document does not address any specific 3GPP Release or Architecture.
|
103 389
|
Railway Telecommunications (RT); Global System for Mobile communications (GSM); Usage of Session Initiation Protocol (SIP) on the Network Switching Subsystem (NSS) to Fixed Terminal Subsystem (FTS) interface for GSM Operation on Railways
|
TS
|
2.0.0
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103389/02.00.00_60/ts_103389v020000p.pdf
|
The present document defines the signalling and media interface between the Network Switching Subsystem and the Fixed Terminal Subsystem in order to provide a clear set of services needed for GSM-R operations. This includes voice call service and available call-related supplementary services. In addition, requirements for specific implementation of the signalling and media interface within either the Network Switching Subsystem or the Fixed Terminal Subsystem are stated where applicable. The present document addresses the Internet Layer and upwards of the Internet Protocol Suite IETF RFC 1122 [i.18] on the signalling and media interface. Any service other than voice call service and call-related supplementary services (such as data services, Short Message Service, etc.) is out of scope of the present document; additional features may be addressed in future releases. The present document does not specify any other interface between the Network Switching Subsystem and the Fixed Terminal Subsystem nor does it cover any internal interfaces of either NSS or FTS. Such interfaces may be addressed in a future release of the present document. The present document does not address any specific 3GPP Release or Architecture.
|
103 328
|
Rail Telecommunications (RT); GPRS/EGPRS requirements for European Train Control System (ETCS)
|
TS
|
1.2.2
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103328/01.02.02_60/ts_103328v010202p.pdf
|
The present document defines the minimum set of 3GPP GPRS features to support ETCS application and to guarantee QoS required. Two operational cases are applicable in GSM-R networks: • GSM-R GPRS packet switched bearer service is only utilized by ETCS PS-mode operation - ETCS only operation. • GSM-R GPRS packet switched bearer service is utilized by simultaneous ETCS and other packet data oriented applications - Simultaneous operation of ETCS and non-ETCS applications. Both operational scenarios require basic GPRS features but in case of simultaneous ETCS and non-ETCS operation, ETCS packet data session requires priority over non-ETCS packet data traffic. The present document is focussing on the relevant references needed for the GSM-R PS-domain. It does not describe the detailed requirements for each of the referred GSM feature. The minimum requirements on ETSI/3GPP for the use of GSM for application on railway networks are based on the Release 99 version of the Technical Specifications and are described in ETSI EN 301 515 [i.1]. The features serving as the basis for GSM-R PS-domain are described in releases later than Release 99. So the present document is referring to specifications versions later than Release 4 but is not mandating any other functionality than covered by the applicable 3GPP Work Items and referenced in the applicable clauses as listed in clauses 5.1.10 and 5.2.2.
|
103 388
|
Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Asymmetric Digital Subscriber Line (ADSL2) - European specific requirements [ITU-T Recommendation G.992.3 modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103388/01.01.01_60/ts_103388v010101p.pdf
|
The present document specifies European requirements for ADSL2. The present document endorses ITU-T Recommendation G.992.3 [1] and amendments 1 [2], 2 [3] and 3 [4], the contents of which apply together with the addition of the modifications being covered herein, to the exclusion of annex C in ITU-T Recommendation G.992.3 [1]. In particular the aspects covered by the present document are related to: 1) Define INP values as mandatory. 2) Define European specific tests. 3) Define mandatory S&D values.
|
103 379
|
Reconfigurable Radio Systems (RRS); Information elements and protocols for the interface between LSA Controller (LC) and LSA Repository (LR) for operation of Licensed Shared Access (LSA) in the 2 300 MHz - 2 400 MHz band
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103379/01.01.01_60/ts_103379v010101p.pdf
|
The present document defines the application protocol on the LSA1 interface, between LSA Controller (LC) and LSA Repository (LR) [i.2] (LSA1 protocol), and the content of the LSA Spectrum Resource Availability Information (LSRAI) conveyed by this protocol. It is based on the System Requirements defined in ETSI TS 103 154 [i.1] and the System Architecture and High Level Procedures defined in ETSI TS 103 235 [i.2]. The present document supports the operation of mobile broadband service in the 2 300 MHz - 2 400 MHz band under Licensed Shared Access (LSA), aimed at enabling access for mobile/fixed communication networks (MFCNs) in those CEPT countries where access to the band is foreseen but cannot be provided without restrictions due to Incumbent usage, as documented in ETSI TR 103 113 [i.3]. Application to other bands is not precluded and depends on future regulatory decisions.
|
103 378
|
Smart Body Area Networks (SmartBAN) Unified data representation formats, semantic and open data model
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103378/01.01.01_60/ts_103378v010101p.pdf
|
The present document specifies and formalizes SmartBAN unified data representation formats (including in particular sensor/actuator/relay/coordinator/Hub descriptions and sensed/measured data), semantic open data model and corresponding ontology. The present document is applicable to a BAN and/or a Smart BAN comprising wearable sensors/actuators devices, a relay/coordinator device and a Hub. The relay/Coordinator and the Hub functionalities may be handled by a single device or by two distinct devices. The present document does not yet address the specification and the formalization of the SmartBAN service ontology and associated enablers. This will be addressed in the future release of the present document.
|
103 371
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103371/01.01.01_60/ts_103371v010101p.pdf
|
Proofs of Concept are an important tool to demonstrate the viability of a new technology during its early days and or pre-standardisation phase. The present document defines a framework to coordinate and promote multivendor Proofs of Concept (PoC) projects illustrating key aspects of the autonomic management and control technology [i.1]. The main objectives of this PoC framework are: • to ensure the PoC projects are scoped around relevant topics; • to ensure that the PoC results, lessons learnt and identified gaps are feedback to the AFI working group of TC NTECH; • to build confidence on the viability of autonomic management and control technology; • to encourage the development of a diverse and open ecosystem by fostering the integration of components from different players; • to support standardization activities of the AFI working group of TC NTECH. This framework describes: • the different roles and responsibilities in the PoC process; • the PoC process; • the acceptance criteria for PoC Proposals and Reports.
|
103 368
|
Rail Telecommunications; Commands necessary for mobile radio equipment operation on railways
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/103300_103399/103368/01.02.01_60/ts_103368v010201p.pdf
|
The present document defines the minimum set of commands necessary for mobile radio systems operation on Railways. The following operational cases are addressed within the present document: • GSM-R Circuit Switched Voice (including ASCI calls, Enhanced Railway Emergency Call, etc.). • GSM-R Circuit Switched Data (CS) bearer service. • GSM-R Packet Switched (PS) bearer service.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.