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
|
|---|---|---|---|---|---|
102 671
|
Secure Elements; Additional UICC form factors and environmental conditions; Physical and logical characteristics (Release 18)
|
TS
|
18.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102671/18.01.00_60/ts_102671v180100p.pdf
|
The present document details the technical specifications for additional form factors and extended environmental conditions for the UICC. Specifically, the present document specifies: • Physical, logical and electrical specifications for additional form factors of the UICC. • Extension of the environmental class specifications as originally defined in ETSI TS 102 221 [1]. These may optionally be applied to all specified UICC form factors (including the form factors defined in ETSI TS 102 221 [1]). • Device pairing mechanisms that allow the UICC to verify the terminal with which it is operating.
|
102 671
|
Smart Cards; Machine to Machine UICC; Physical and logical characteristics (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102671/16.00.00_60/ts_102671v160000p.pdf
|
The present document details the technical specifications for additional form factors and extended environmental conditions for the UICC. Specifically, the present document specifies: • Physical, logical and electrical specifications for additional form factors of the UICC. • Extension of the environmental class specifications as originally defined in ETSI TS 102 221 [1]. These may optionally be applied to all specified UICC form factors (including the form factors defined in ETSI TS 102 221 [1]). • Device pairing mechanisms that allow the UICC to verify the terminal with which it is operating.
|
102 650
|
<empty>
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102650/01.01.01_60/ts_102650v010101p.pdf
|
The present document represents an analysis of the work done by various ETSI work groups and other standards bodies worldwide on the acquisition and transmission of caller location information in various communications network types. It also contains information about the protocols used and of any known deployments for the location of users making emergency calls. It is not intended to examine the detailed workings of the protocols described or their possible use in other communications network types. The document does not mandate any new requirements but does report on the normative requirements from other standards and regulatory bodies. It also refers, in part, to operating methods and national regulations in various jurisdictions but does not intend to endorse these as requirements. The hypothetical accuracy of the caller location and the accuracy achieved by the assessing methods are also documented. Alternative methods for the coding of the emergency location information are also examined. The present document also indicates a number of scenarios where location information may not be available or may be inaccurate to various degrees and may suggest solutions for improvement.
|
102 639-5
|
Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 5: Security Services [ITU-T Recommendation J.222.3 (07/2007), modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263905/01.01.01_60/ts_10263905v010101p.pdf
|
The present document defines the security requirements as part of a series of specifications for the third generation of high-speed Data-Over-Cable Systems Interface Specifications (DOCSIS®). They were developed for the benefit of the cable industry, including contributions by operators and vendors from, Europe, North America and other regions. The source material for this specification was provided by the ITU-T Recommendation J.222.3 [3] for which the most recent version can be found at http://www.itu.int/ITU-T/.
|
102 639-4
|
Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 4: MAC and Upper Layer Protocols [ITU-T Recommendation J.222.2 (07/2007), modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263904/01.01.01_60/ts_10263904v010101p.pdf
|
The present document is part of a series of ETSI standards that define the third generation of high-speed data-over-cable systems. The third-generation transmission systems introduces a number of new features that build upon what was present in previous versions (ES 201 488 [4] and ES 202 488-2 [3]). The present document includes key new features for the MAC and Upper Layer Protocol Interface, and defines the MAC layer protocols as well as requirements for upper layer protocols (e.g. IP, DHCP, etc.). These series of ETSI standards were developed for the benefit of the cable industry, including contributions by operators and vendors from, Europe, North America and other regions. The source material for this specification was provided by the ITU-T Recommendation J.222.2 [8] for which the most recent version can be found at http://www.itu.int/ITU-T/. NOTE: Also refer to TS 102 639-1 [i.2] for the background and overview of the DOCSIS® 3.0 family of ETSI standards.
|
102 639-3
|
Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 3: Downstream Interface [ITU-T Recommendation J.210 (11/2006), modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263903/01.01.01_60/ts_10263903v010101p.pdf
|
The present document provides physical layer requirements for Cable Modem Termination System (CMTS) transmitters in the Data-Over-Cable Systems Interface Specifications (DOCSIS®) architecture. It defines the downstream interface specifications for: • an edgeQAM (EQAM) device in a modular CMTS architecture; or • an integrated CMTS It was developed for the benefit of the cable industry, including contributions by operators and vendors from, Europe, North America and other regions. The source material for this specification was provided by the ITU-T Recommendation J.210 [3] for which the most recent version can be found at http://www.itu.int/ITU-T/. There are differences in the cable spectrum planning practices adopted for different networks in the world. Therefore two definitions for physical layer technology are included, which have equal priority and are not required to be interoperable. One technology definition is based on the downstream multi-programme television distribution that is deployed using 8 MHz channelling. The second technology definition is based on a multi-programme television distribution using 6 MHz channel spacing. Both options have equal status. The choices of physical-layer technologies allow operators some flexibility within any frequency planning, EMC and safety requirements that are mandated for their area of operation. EXAMPLE: The 6 MHz downstream-based option might be deployable within an 8 MHz channel plan. It is the network operator's choice of which technology definition to deploy. NOTE: The present document references both physical layer technologies and where there are parameter differences both are specified for both options: (i) 8 MHz channel spacing; and. (ii) 6 MHz channel spacing. All optional physical-layer technologies are required to be backwards compatible with the earlier versions of those options defined in ES 201 488 [i.2] and ES 202 488 [i.3]. Requirements for EMC and safety are outside the scope of the present document. EMC and safety standards for European applications are published by CENELEC. NOTE 1: Examples of such CENELEC product safety standards are EN 60950 [i.4] and EN 50083-1 [i.5]. NOTE 2: For CENELEC safety categories of interfaces, see EG 201 212 [i.6]. NOTE 3: Examples of such CENELEC product EMC standards are EN 50081-1 [i.7], EN 50082-1 [i.8] and EN 50083-2 [i.9]. ETSI ETSI TS 102 639-3 V1.1.1 (2009-04) 6
|
102 639-2
|
Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 2: Physical Layer [ITU-T Recommendation J.222.1 (07/2007), modified]
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263902/01.01.01_60/ts_10263902v010101p.pdf
|
The present document defines the physical layer requirements as part of a series of specifications for the third generation of high-speed Data-Over-Cable Systems Interface Specifications (DOCSIS®). They were developed for the benefit of the cable industry, including contributions by operators and vendors from, Europe, North America and other regions. The source material for the present document was provided by the ITU-T Recommendation J.222.1 [5] for which the most recent version can be found at http://www.itu.int/ITU-T/. There are differences in the cable spectrum planning practices adopted for different networks in the world. Therefore two definitions for physical layer technology are included, which have equal priority and are not required to be interoperable. One technology definition is based on the downstream multi-programme television distribution that is deployed using 8 MHz channelling, and supports upstream transmission in the 5 MHz to 65 MHz region. The second technology definition is based on a multi-programme television distribution using 6 MHz channel spacing and supports upstream in the 5 MHz to 42 MHz region. Both options have equal status. The choices of physical-layer technologies allow operators some flexibility within any frequency planning, EMC and safety requirements that are mandated for their area of operation. EXAMPLE: The 6 MHz downstream-based option might be deployable within an 8 MHz channel plan. It is the network operator's choice of which technology definition to deploy. NOTE: The current document references both physical layer technologies and where there are parameter differences both are specified for both options: i) 8 MHz channel spacing; and. ii) 6 MHz channel spacing. All optional physical-layer technologies are required to be backwards compatible with the earlier versions of those options defined in ES 201 488 [i.4] and ES 202 488 [i.5]. Requirements for EMC and safety are outside the scope of the present document. EMC and safety standards for European applications are published by CENELEC. NOTE 1: Examples of such CENELEC product safety standards are EN 60950 [i.6] and EN 50083-1 [i.6]. NOTE 2: For CENELEC safety categories of interfaces, see EG 201 212 [i.2]. NOTE 3: Examples of such CENELEC product EMC standards are EN 50081-1 [i.7], EN 50082-1 [i.8] and EN 50083-2 [i.3]. ETSI ETSI TS 102 639-2 V1.1.1 (2009-04) 6
|
102 639-1
|
Access and Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Services - IP Cable Modems; Part 1: General
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263901/01.01.01_60/ts_10263901v010101p.pdf
|
The present document is an overview of the third generation of transmission systems for interactive cable television systems. It identifies the four components specifying the physical layer interface, downstream interface, the MAC and upper layer protocols interfaces and the security services. The present document presents an overview of a series of specifications for the third generation of high-speed Data- Over-Cable Systems Interface Specifications (DOCSIS®) applicable to the European region. They were developed for the benefit of the cable industry, including contributions by operators and vendors from, Europe, North America and other regions. The source material for this specification was provided by the ITU-T Recommendations J.222 [7] series and J.210 [8] for which the most recent version can be found at http://www.itu.int/ITU-T/.
|
102 624-1
|
Broadband Radio Access Networks (BRAN); HiperMAN; Conformance Testing for the Network layer of HiperMAN/WiMAX terminal devices; Part 1: Protocol Implementation Conformance Statement (PICS) proforma
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10262401/01.02.01_60/ts_10262401v010201p.pdf
|
The present document specifies the Protocol Implementation Conformance Statement (PICS) proforma for WiMAX Network Layer Release 1.5 per ISO/IEC 9646-7 [23], ITU-T Recommendation X.296 [24] and EG 201 058 [i.4] for conformance of HiperMAN1.3.1/WiMAX compliant terminals.
|
102 637-2
|
Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263702/01.02.01_60/ts_10263702v010201p.pdf
|
The present document provides: • general overview of the Cooperative Awareness Basic Service; • quality requirements; • messages formats and specifications. This includes definition of the syntax and semantics of the Cooperative Awareness Message (CAM) and detailed specifications on the message handling. Furthermore, the present document considers the CAM specifications defined by CAR 2 CAR Communication Consortium [i.3].
|
102 637-1
|
Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 1: Functional Requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263701/01.01.01_60/ts_10263701v010101p.pdf
|
The present document provides the functional requirements for the applications and their use cases as defined in the BSA [i.3]. The intended audience of the document is those stakeholders developing standards for applications in the BSA. The present document can also serve as a reference document for stakeholders developing and implementing the BSA use cases. It is not the intention of the present document to specify the development neither the implementation procedure of BSA use cases.
|
102 636-7-2
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 7: Amendments for LTE-V2X; Sub-part 2: Amendments to ETSI EN 302 636-5-1 (Basic Transport Protocol)
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360702/01.01.02_60/ts_1026360702v010102p.pdf
|
The present document specifies amendments to ETSI EN 302 636-5-1 (V2.1.1) [1] to extend BTP for the transport of packets among ITS stations that utilize LTE-V2X as the access layer technology. The present document is no longer maintained. Future amendments (if any) will be included in an errata document to ETSI EN 302 636-5-1 [1]
|
102 636-7-1
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 7: Amendments for LTE-V2X; Sub-part 1: Amendments to ETSI EN 302 636-4-1 (Media-Independent Functionality)
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360701/01.01.02_60/ts_1026360701v010102p.pdf
|
The present document specifies amendments to ETSI EN 302 636-4-1 (V1.3.1) [1] to extend the GeoNetworking protocol for communication of packets among ITS stations that utilize LTE-V2X as the access layer technology. The present document is no longer maintained. Contents were moved to ETSI TS 102 636-4-3 [i.2] and ETSI EN 302 636-4-1 [1] was changed accordingly.
|
102 636-6-1
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over GeoNetworking Protocols
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360601/01.01.01_60/ts_1026360601v010101p.pdf
|
The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol [i.25] via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL. The techniques specified in the present document fulfil the requirements for GeoNetworking and IPv6 integration described in [3], clause 5.9. In particular, these techniques allow for the transport of IPv6 packets by ETSI GeoNetworking protocol [i.25], enabling sub-IP multi-hop delivery of IPv6 packets, e.g. in a vehicular network. As a result, the connectivity provided by point-of-attachments to IPv6 infrastructure networks is extended by means of mobile relay nodes. In addition to that, the techniques described in the present document allow for geocasting of IPv6 multicast packets. The scope of the GN6ASL is limited to the fulfilment of the requirements for GeoNetworking and IPv6 integration described in [3], clause 5.9, by enabling an ITS station including a Geoadhoc router [5] running GeoNetworking and an IPv6-compliant protocol layer to: 1) exchange IPv6 packets with other ITS stations using link-local IPv6 addresses; 2) acquire globally routable IPv6 unicast addresses and communicate with an arbitrary IPv6 host located in the Internet, whenever an ITS station including a Geoadhoc router and including or connected to an access router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations; 3) to perform the operations required by [20] for a Mobile Router whenever i) an ITS mobile router supporting Network Mobility Basic Support (NEMO BS) [20] is present in the ITS station and runs on top of the GN6ASL and ii) an ITS station including a Geoadhoc router and including or connected to an access router [5] providing IPv6 connectivity to the Internet is reachable directly or via other relay ITS stations. NOTE: The present document adopts the definition of "IPv6-compliant" and "sub-IP multi-hop delivery" introduced in clause 3.1. Extending the IPv6 basic standards [7], [8], [9], [10] and [12] to support new features is outside the scope of the present document. Extensions to NEMO BS [15] are outside the scope of the present document. Mechanisms for the dissemination of IPv6 routing information for hosts and routers not directly attaching to the network where GeoNetworking is used are outside the scope of the present document (e.g. discovery of IPv6 in-vehicle prefixes). However, the present document aims at providing the underlying support for the dissemination of such routing information, i.e. IPv6 multicast support for the network where the GeoNetworking protocol is used. With respect to IPv6 multicast and anycast support, the present document is limited to the support required to enable distribution of IPv6 multicast and anycast traffic on a shared link. Amendments to specific IPv6 multicast forwarding mechanisms are out of the scope of the present document. However, the present document aims at not preventing existing IPv6 multicast forwarding mechanisms from being used in conjunction with the GN6ASL. In order to facilitate the deployment of ITS systems, the present document aims at maintaining backward compatibility with pre-existent IPv6-compliant protocol implementations and NEMO BS implementations compliant with [15]. An exemplary usage of NEMO BS with the GN6ASL is overviewed in the informative annex F. The present document does not request any assignment or reservation of IPv6 prefixes or suffixes for specific purposes. The mechanisms specified in the present document are distinct from but compatible with the IPv6-related functionalities in [i.24], which specifies how IPv6 networking is generally operated in ITS stations. The techniques described in the present document provide a way to transport IPv6 packets that is fully compatible with the IPv6 specifications and pre-existing implementations, and hence is compatible with [i.19]. ETSI ETSI TS 102 636-6-1 V1.1.1 (2011-03) 9
|
102 636-5-1
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360501/01.01.01_60/ts_1026360501v010101p.pdf
|
The present document specifies the ITS Basic Transport Protocol (BTP) for the transport of packets among ITS stations in the ITS ad hoc network. It provides an end-to-end, connection-less and unreliable transport service.
|
102 636-4-3
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-multipoint communications; Sub-part 3: Media-dependent functionalities for LTE-V2X
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360403/01.01.01_60/ts_1026360403v010101p.pdf
|
The present document specifies the media-dependent functionalities for GeoNetworking [1] over LTE-V2X [2] as a network protocol for ad hoc routing in vehicular environments.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/15.00.00_60/ts_102622v150000p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 637-3
|
Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263703/01.01.01_60/ts_10263703v010101p.pdf
|
The present document provides the specification of the DEN basic service, which mainly supports the RHW application. More specifically, the present document specifies the semantics of the Decentralized Environmental Notification Message (DENM) and the DENM handling. A DENM transmission is triggered by a cooperative RHW use case to provide information about a specific driving environment event or traffic event to other ITS stations. The ITS station that receives the DENM is able to provide appropriate HMI information to the end user, who makes use of these information or takes actions in its driving and travelling. The concept of the DEN basic service is derived from the functional requirements of BSA as defined in [i.4] and operational requirements of BSA as defined in [i.5]. Detailed specifications of the RHW use cases are out of scope of the present document. The present document is based on DENM specifications defined in [i.1] and [i.2].
|
102 636-3
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 3: Network architecture
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263603/01.01.01_60/ts_10263603v010101p.pdf
|
The present document specifies the network architecture for communication-based Intelligent Transport Systems (ITS). The network architecture is focused on, but not limited to, vehicular communication. The architecture enables a wide range of ITS applications for road safety, traffic efficiency as well as for infotainment and business. The present document defines the framework for network and data transport protocols that provide data exchange among ITS stations. A particular aspect is the GeoNetworking protocol that provides ad hoc and multi-hop communication over short-range wireless technologies utilizing geographical positions.
|
102 636-2
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 2: Scenarios
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263602/01.01.01_60/ts_10263602v010101p.pdf
|
The present document classifies and specifies all communication scenarios that shall be supported by GeoNetworking.
|
102 636-1
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 1: Requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10263601/01.01.01_60/ts_10263601v010101p.pdf
|
The present document specifies the general, functional and performance requirements for ITS network and transport layer at a high level. The present document is applicable to different types of ITS access technologies.
|
102 624-3
|
Broadband Radio Access Networks (BRAN); HiperMAN; Conformance Testing for the Network layer of HiperMAN/WiMAX terminal devices; Part 3: Abstract Test Suite (ATS)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10262403/01.02.01_60/ts_10262403v010201p.pdf
|
The present document contains the Abstract Test Suite (ATS) to test BRAN HiperMAN/WiMAX terminal devices for conformance across WiMAX networks. The objective of the present document is to provide a basis for conformance tests for WiMAX terminal equipment giving a high probability of air interface inter-operability between different manufacturers' WiMAX equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [39] and ISO/IEC 9646-2 [40]) as well as the ETSI rules for conformance testing (ETS 300 406 [35] are used as a basis for the test methodology. Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the SS side ATS. Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the MS side ATS.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 10)
|
TS
|
10.3.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/10.03.00_60/ts_102622v100300p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 624-2
|
Broadband Radio Access Networks (BRAN); HiperMAN; Conformance Testing for the Network layer of HiperMAN/WiMAX terminal devices; Part 2: Test Suite Structure and Test Purposes (TSS&TP)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10262402/01.02.01_60/ts_10262402v010201p.pdf
|
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the HiperMAN/WiMAX terminals based on the WiMAX Forum Network Architecture specifications Release 1.5. The objective of the present document is to provide a basis for conformance tests for WiMAX terminal equipment giving a high probability of air interface inter-operability between different manufacturers' WiMAX equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [21] and ISO/IEC 9646-2 [22]) as well as the ETSI rules for conformance testing (ETS 300 406 [20]) are used as a basis for the test methodology.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 8)
|
TS
|
8.4.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/08.04.00_60/ts_102622v080400p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 7)
|
TS
|
7.10.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/07.10.00_60/ts_102622v071000p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 9)
|
TS
|
9.4.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/09.04.00_60/ts_102622v090400p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 9)
|
TS
|
9.4.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/09.04.00_60/ts_102613v090400p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/16.00.00_60/ts_102613v160000p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 11)
|
TS
|
11.4.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/11.04.00_60/ts_102622v110400p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/13.00.00_60/ts_102613v130000p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/12.00.00_60/ts_102613v120000p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/11.01.00_60/ts_102613v110100p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 620
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv4 to IPv6 Transitioning; Interoperability Test Suite
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102620/01.01.01_60/ts_102620v010101p.pdf
|
The present document specifies the interoperability Test Descriptions (TDs) with integrated Test Purposes (TPs) for the selected IPv4 to IPv6 TRansitioning standards. The TDs are presented in the tabular form specified in TS 102 424 [11]and the TPs are defined using the TPLan notation also described in ES 202 553 [2].
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 13)
|
TS
|
13.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/13.01.00_60/ts_102622v130100p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 12)
|
TS
|
12.2.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/12.02.00_60/ts_102622v120200p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 8)
|
TS
|
8.4.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/08.04.00_60/ts_102613v080400p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 7)
|
TS
|
7.11.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/07.11.00_60/ts_102613v071100p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 636-4-2
|
Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-multipoint communications; Sub-part 2: Media-dependent functionalities for ITS-G5
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360402/01.04.01_60/ts_1026360402v010401p.pdf
|
The present document specifies the media-dependent functionalities for GeoNetworking defined in ETSI EN 302 636-4-1 [1] over ITS-G5 defined in ETSI EN 302 663 [2] as a network protocol for ad hoc routing in vehicular environments.
|
102 636-4-1
|
Intelligent Transport System (ITS); Vehicular communications; GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-multipoint communications; Sub-part 1: Media-Independent Functionality
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/1026360401/01.01.01_60/ts_1026360401v010101p.pdf
|
The present document specifies the media-independent functionality of the GeoNetworking protocol.
|
102 622
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI) (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102622/14.00.00_60/ts_102622v140000p.pdf
|
The present document specifies a logical interface that enables contactless applications hosted on the UICC. The present document covers the configuration where the one host is embedded in the UICC which is connected to the host controller embedded in the CLF. The interface is specified in two parts: • the HCI core as described in the first part of the present document (clauses 4 to 8), specifies an application independent logical interface; and • the contactless platform as described in the second part of the present document (clauses 9 to 11) specifies an implementation of the HCI core for contactless applications using the UICC and the CLF. Lower layer protocols that support the HCI like the SWP specified in ETSI TS 102 613 [2] are out of the scope of the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 10)
|
TS
|
10.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/10.01.00_60/ts_102613v100100p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 606-2
|
Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 2: Logical Link Control (LLC)
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10260602/01.03.01_60/ts_10260602v010301p.pdf
|
The present document specifies a Logical Link Control (LLC) method to be used on DVB streams where the Generic Stream Encapsulation (GSE) [1] protocol is used as the link layer.
|
102 606-1
|
Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 1: Protocol
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10260601/01.03.01_60/ts_10260601v010301p.pdf
|
The present document specifies the Generic Stream Encapsulation (GSE) protocol.
|
102 606
|
Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102606/01.01.01_60/ts_102606v010101p.pdf
|
The present document includes the definition of the Generic Stream Encapsulation (GSE) protocol, which allows for efficient encapsulation of IP and other network layer packets over a "generic" physical layer. Such a "generic" physical layer is intended as a transport mode that carries a sequence of data bits or data packets, possibly organized in frames, but with no specific timing constraints. The first generation of DVB standards only supported data transport using the MPEG format (see ISO/IEC 13818-1 [2]), with a Transport Stream packet multiplex (MPEG-TS). Multi Protocol Encapsulation (EN 301 192 [3]) is the DVB standard for encapsulation of audio/video and other content on MPEG-TS packets. The second generation of DVB standards features backwards compatibility modes for carrying MPEG-TS as well as generic modes for carrying arbitrary packets of variable length. These are referred to as Generic Streams (GS). The GSE protocol has been devised as an adaptation layer to provide network layer packet encapsulation and fragmentation functions over Generic Stream. GSE provides efficient encapsulation of IP datagrams over variable length Layer 2 packets, which are then directly scheduled on the physical layer into Base Band frames. GSE maximizes efficiency of IP datagrams transport reducing overhead by a factor 2 to 3 with respect to MPE over MPEG-TS. This is achieved without any compromise of the functionalities provided by the protocol, due to the variable length Layer 2 packet size, suited to IP traffic characteristics. For example in an interactive DVB-S2 system, the overhead is reduced on average from about 10 % for MPE/MPEG-TS to 2 % to 3 % for GSE. Hence yielding an overall throughput gain of about 5 % to 15 %, the actual benefit is of course dependent on the concrete system and traffic characteristics. In addition to the overhead reduction, GSE provides a more efficient system operation for interactive systems that utilize advanced physical layer techniques such as for instance Adaptive Coding and Modulation (ACM). The inherent channel rate variability experienced in ACM systems makes the Generic Stream format more suited than the Transport Stream. GSE provides a flexible fragmentation and encapsulation method, which permits use of a smart scheduler to optimize system performance, either by increasing the total throughput and/or by improving the average packet end-to- end delay. In addition, GSE flexibility leads to a reduction in packet loss under fading variations, allowing the scheduler at the transmitter to dynamically change transmission parameters (for example modulation format, coding rate) for a particular network layer packet. GSE also provides additional features that increase the protocol flexibility and applicability. Some key GSE functions/characteristics are: 1) Support for multi-protocol encapsulation (IPv4, IPv6, MPEG, ATM, Ethernet, 802.1pQ VLANs, etc.). 2) Transparency to network layer functions, including IP encryption and IP header compression. 3) Support of several addressing modes: In addition to the 6-byte MAC address (including multicast and unicast), it supports a MAC addressless mode, and an optional 3-byte address mode. 4) A mechanism for fragmenting IP datagrams or other network layer packets over Base Band frames to support ACM/VCM. 5) Support for hardware filtering. 6) Extensibility: additional link protocols can be included through specific protocol type values (e.g. Layer 2 security, IP Header Compression, etc.). 7) Low complexity. ETSI ETSI TS 102 606 V1.1.1 (2007-10) 6
|
102 602
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia; Connection Control Protocol (C2P) for DVB-RCS; Specifications
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102602/01.01.01_60/ts_102602v010101p.pdf
|
The present BSM document defines and specifies a Connection Control Protocol (C2P) for DVB-RCS satellite networks, relying on specific DVB-RCS layer 2 signalling (DULM on the return link, unicast TIM on the forward link). C2P is part of the control plane layer 2 functionality and is generally used for the dynamic establishment and management of connections between the ground elements of DVB-RCS networks (RCSTs, Gateways, NCC), regardless of their architectures and topologies (single-beam/multiple-beam architectures, transparent/regenerative satellite payloads, star/mesh topologies). In this context C2P can be seen as a complement to the functionality of the interfaces already defined in the DVB-RCS and DVB-S/S2 standards [1] and [i.1]. The present document is organized as follows: • Clause 4 contains the description of the network reference scenarios (clause 4.2), of the C2P core elements (clause 4.3), of the connection types (clause 4.4) and of various data structures for dynamic connectivity support (clause 4.6). • Clause 5 describes the state machines, including the timer and counter definitions and examples of state machines diagrams. • Clause 6 describes the normal procedures and a few examples of exception procedures. • Clause 7 describes the C2P Information Elements (IEs). • Clause 8 defines the C2P messages. • Annex A includes the description of C2P State Machines in UML format. • Annex B includes examples of C2P scenarios. • Annex C provides additional examples of exception procedures. • Annex D includes examples of the formatting of C2P messages. Further and more detailed background information for C2P definition and specification is provided in the C2P TR Background Information document [i.5]. The specifications in the present document apply to DVB-RCS network elements that are part of the same Interactive Network (IN). The RCSTs in the IN are Type A RCSTs (clause 8.1.1 in [1]). All RCSTs are capable of transmitting in ATM or MPEG2-TS formats and of receiving in MPEG2-TS format. The present document defines Version 01 of the C2P Specifications. This is the first release of the C2P Specifications. ETSI ETSI TS 102 602 V1.1.1 (2009-01) 9
|
102 600
|
Smart Cards; UICC-Terminal interface; Characteristics of the USB interface (Release 10)
|
TS
|
10.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102600/10.01.00_60/ts_102600v100100p.pdf
|
The present document specifies the Inter-Chip USB interface between the USB UICC and the USB UICC-enabled terminal, subsequently referred to as the IC-USB interface. It describes: • the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the USB UICC-enabled terminal; • the initial communication establishment and the transport protocols; • the communication layers between the USB UICC and the USB UICC-enabled terminal. The physical characteristics (including mechanical aspects) defined in ETSI TS 102 221 [1] apply to USB UICCs. The present document comes as an extension of ETSI TS 102 221 [1] complementing the electrical characteristics of contacts C1 and C5 and describing the behaviour of contacts C4 and C8 when the USB interface is supported. The Inter-Chip USB interface provides access to the existing UICC resources such as the file system and security features specified in ETSI TS 102 221 [1] and to other resources and functionalities specified in the present document.
|
102 600
|
Smart Cards; UICC-Terminal interface; Characteristics of the USB interface (Release 9)
|
TS
|
9.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102600/09.01.00_60/ts_102600v090100p.pdf
|
The present document specifies the Inter-Chip USB interface between the USB UICC and the USB UICC-enabled terminal, subsequently referred to as the IC-USB interface. It describes: • the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the USB UICC-enabled terminal; • the initial communication establishment and the transport protocols; • the communication layers between the USB UICC and the USB UICC-enabled terminal. The physical characteristics (including mechanical aspects) defined in ETSI TS 102 221 [1] apply to USB UICCs. The present document comes as an extension of ETSI TS 102 221 [1] complementing the electrical characteristics of contacts C1 and C5 and describing the behaviour of contacts C4 and C8 when the USB interface is supported. The Inter-Chip USB interface provides access to the existing UICC resources such as the file system and security features specified in ETSI TS 102 221 [1] and to other resources and functionalities specified in the present document.
|
102 600
|
Smart Cards; UICC-Terminal interface; Characteristics of the USB interface (Release 8)
|
TS
|
8.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102600/08.01.00_60/ts_102600v080100p.pdf
|
The present document specifies the Inter-Chip USB interface between the USB UICC and the USB UICC-enabled terminal, subsequently referred to as the IC-USB interface. It describes: • the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the USB UICC-enabled terminal; • the initial communication establishment and the transport protocols; • the communication layers between the USB UICC and the USB UICC-enabled terminal. The physical characteristics (including mechanical aspects) defined in ETSI TS 102 221 [1] apply to USB UICCs. The present document comes as an extension of ETSI TS 102 221 [1] complementing the electrical characteristics of contacts C1 and C5 and describing the behaviour of contacts C4 and C8 when the USB interface is supported. The Inter-Chip USB interface provides access to the existing UICC resources such as the file system and security features specified in ETSI TS 102 221 [1] and to other resources and functionalities specified in the present document.
|
102 600
|
Smart Cards; UICC-Terminal interface; Characteristics of the USB interface (Release 7)
|
TS
|
7.9.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102600/07.09.00_60/ts_102600v070900p.pdf
|
The present document specifies the Inter-Chip USB interface between the USB UICC and the USB UICC-enabled terminal, subsequently referred to as the IC-USB interface. It describes: • the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the USB UICC-enabled terminal; • the initial communication establishment and the transport protocols; • the communication layers between the USB UICC and the USB UICC-enabled terminal. The physical characteristics (including mechanical aspects) defined in ETSI TS 102 221 [1] apply to USB UICCs. The present document comes as an extension of ETSI TS 102 221 [1] complementing the electrical characteristics of contacts C1 and C5 and describing the behaviour of contacts C4 and C8 when the USB interface is supported. The Inter-Chip USB interface provides access to the existing UICC resources such as the file system and security features specified in ETSI TS 102 221 [1] and to other resources and functionalities specified in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 15)
|
TS
|
15.1.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/15.01.00_60/ts_102613v150100p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 613
|
Smart Cards; UICC - Contactless Front-end (CLF) Interface; Physical and data link layer characteristics (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102613/14.00.00_60/ts_102613v140000p.pdf
|
The present document specifies the Single Wire Protocol (SWP). SWP is the interface between the UICC and the CLF. The present document defines: • Layer 1: The physical layer which is responsible for activating, maintaining and deactivating the physical link between the UICC and the CLF. It defines electrical (voltage and current levels, timing and coding of voltage and current levels), mechanical (physical contacts) and functional (data rates) specifications. It also defines the initial communication establishment and the end of the connection. • Layer 2: The data link layer which is responsible for the physical addressing of the data through frames and Link Protocol Data Units (LPDU). The data link layer is also responsible for error notification, ordered delivery of frames and flow control. This layer can be split into two sub-layers: - The Medium Access Control (MAC) layer which manages frames. - The Logical Link Control layer which manages LPDUs and is responsible for the error-free exchange of data between nodes. Three different Logical Link Control layers are defined in the present document.
|
102 611-2
|
Digital Video Broadcasting (DVB); IP Datacast: Implementation Guidelines for Mobility; Part 2: IP Datacast over DVB-SH
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10261102/01.02.01_60/ts_10261102v010201p.pdf
|
The present document presents contextual information on handover required in DVB-SH networks. Handover is considered as the procedure used within one IP platform in order to continue IP Datacast service consumption under specific network modifications. The present document relies on the DVB-SH (see [12], [13] and [i.7]) and IP Datacast phase 1 (see [2] to [8]) set of specifications. The present document plainly references DVB-H specification [4] for the support of roaming and special mobility use cases.
|
102 611-1
|
Digital Video Broadcasting (DVB); IP Datacast: Implementation Guidelines for Mobility; Part 1: IP Datacast over DVB-H
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10261101/01.03.01_60/ts_10261101v010301p.pdf
|
The present document presents guidelines on how to develop terminals and network infrastructure equipment to allow seamless handover within the scope of one IP Platform, one ESG, and one IPDC Operator, in order to continue IP Datacast service consumption. Additionally, the present document specifies enablers for mobility between IP Platforms, ESGs, and IPDC Operators.
|
102 611
|
Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Implementation Guidelines for Mobility
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102611/01.01.01_60/ts_102611v010101p.pdf
|
The present document presents guidelines on how to develop terminals and network infrastructure equipment to allow seamless handover within one IP platform, in order to continue IP Datacast service consumption. These guidelines rely on the DVB-H [1], TR 102 377 [14], and IP Datacast phase 1 [2] specifications. Roaming between IP platforms will be addressed in a subsequent version of the present document.
|
102 610
|
Railways Telecommunications (RT); Global System for Mobile communications (GSM); Usage of the User-to-User Information Element for GSM Operation on Railways
|
TS
|
1.3.0
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/102610/01.03.00_60/ts_102610v010300p.pdf
|
The present document defines the contents of the User-to-User Information Element when used in the GSM-R environment. This includes the basic EIRENE features Functional Addressing, Location Dependant Addressing, Confirmation of High Priority Calls (including, but not exclusively, REC and eREC) and Presentation of Functional Numbers. In addition the present document defines layouts for further features: Enhanced Presentation of Functional Numbers, Enhanced Location Dependent Addressing, Driver's Safety Device alarm, Plain Text Messages, Presentation of the Functional Number of the initiator of a Railway Emergency Call and Alerting of a Controller. Finally, the present document describes the requirements to be followed by network operators to ensure compatibility and interoperability if they wish to define specific fields for national and/or network use. The details of such fields are outside the scope of the present document.
|
102 606-3
|
Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE); Part 3: Robust Header Compression (ROHC) for IP
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102600_102699/10260603/01.02.01_60/ts_10260603v010201p.pdf
|
The present document specifies a Robust Header Compression (ROHC) method to be used on DVB streams where the Generic Stream Encapsulation (GSE) ETSI TS 102 606-1 [1] protocol is used as the link layer for IP.
|
102 599
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv4 to IPV6 Transitioning; Requirements Catalogue
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102599/01.01.01_60/ts_102599v010101p.pdf
|
The present document is a catalogue of all of the IPv4 to IPv6 transitioning-related requirements extracted from the following IETF specifications: RFC 2529 [1]: "Transmission of IPv6 over IPv4 Domains without Explicit Tunnels". RFC 2765 [2]: "Stateless IP/ICMP Translation Algorithm (SIIT)". RFC 2766 [3]: "Network Address Translation - Protocol Translation (NAT-PT)". RFC 2893 [4]: "Transition Mechanisms for IPv6 Hosts and Routers". RFC 3056 [5]: "Connection of IPv6 Domains via IPv4 Clouds". RFC 3596 [6]: "DNS Extensions to Support IP Version 6". RFC 4213 [7]: "Basic Transition Mechanisms for IPv6 Hosts and Routers". RFC 4214 [8]: "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)".
|
102 598
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Mobility; Interoperability Test Suite
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102598/01.01.01_60/ts_102598v010101p.pdf
|
The present document specifies the interoperability Test Descriptions (TDs) with integrated Test Purposes (TPs) for the IPv6 Mobility standards. The TDs are presented in the tabular form specified in TS 102 424 (see Bibliography) and the TPs are defined using the TPLan notation also described in ES 202 553 (see Bibliography).
|
102 597
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Security; Interoperability Test Suite
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102597/01.01.01_60/ts_102597v010101p.pdf
|
The present document specifies the interoperability Test Descriptions (TDs) with integrated Test Purposes (TPs) for the selected IPv6 Security standards. The TDs are presented in the tabular form specified in TS 102 424 [8] and the TPs are defined using the TPLan notation also described in ES 202 553 (see bibliography).
|
102 596
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Mobility; Conformance Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma
|
TS
|
1.2.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102596/01.02.00_60/ts_102596v010200p.pdf
|
The present document specifies the Abstract Test Suite (ATS) for the mobility functions of the Internet Protocol, Version 6, as defined in the specifications [11] through to [14]. The ATS is based on the requirements defined in the IPv6 requirements catalogue TS 102 559 [2], the IPv6 test purposes TS 102 595 [3] and written according to the guidelines of TS 102 351 [1], ISO/IEC 9646-2 [5] and ETS 300 406 [9]. The objective of the present document is to provide a basis for conformance tests for IPv6 equipment giving a high probability of inter-operability between different manufacturer's IPv6 equipments. Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the ATS. NOTE: Annex B provides only the PIXIT items relevant for the mobility functions of IPv6. It is therefore necessary to also fill the core PIIXT item in TS 102 516 [15] to gain all PIXIT values needed to run the mobility test campaign.
|
102 595
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Mobility; Conformance Test Suite Structure and Test Purposes (TSS&TP)
|
TS
|
1.2.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102595/01.02.00_60/ts_102595v010200p.pdf
|
The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS&TP) for conformance tests of the mobility IPv6 protocol based on the requirements defined in the IPv6 requirements catalogue (TS 102 559 [2]) and written according to the guidelines of TS 102 351 [1], ISO/IEC 9646-2 [4] and ETS 300 406 [5].
|
102 594
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Security; Conformance Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma
|
TS
|
1.2.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102594/01.02.00_60/ts_102594v010200p.pdf
|
The present document specifies the Abstract Test Suite (ATS) for the mobility functions of the Internet Protocol, Version 6, as defined in the specifications [11] through to [14]. The ATS is based on the requirements defined in the IPv6 requirements catalogue (TS 102 558 [2]) and the IPv6 test purposes (ETSI TS 102 593 [3]) and written according to the guidelines of TS 102 514 [16], ISO/IEC 9646-2 [5] and ETS 300 406 [9]. The objective of the present document is to provide a basis for conformance tests for IPv6 equipment giving a high probability of inter-operability between different manufacturers' IPv6 equipments. • Annex A provides the Tree and Tabular Combined Notation (TTCN-3) part of the ATS. • Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the ATS. • Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the ATS. NOTE: Annex B provides only the PIXIT items relevant for the security functions of IPv6. It is therefore necessary to also fill the core PIIXT item in TS 102 516 [15] to gain all PIXIT values needed to run the mobility test campaign.
|
102 593
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); IPv6 Security; Conformance Test Suite Structure and Test Purposes (TSS&TP)
|
TS
|
1.2.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102593/01.02.00_60/ts_102593v010200p.pdf
|
The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS&TP) for conformance tests of the security IPv6 protocol based on the requirements defined in the IPv6 requirements catalogue (TS 102 558 [2]) and written according to the guidelines of TS 102 351 [1], ISO/IEC 9646-2 [4] and ETS 300 406 [5].
|
102 592-2
|
Digital Video Broadcasting (DVB); IP Datacast: Electronic Service Guide (ESG) Implementation Guidelines; Part 2: IP Datacast over DVB-SH
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10259202/01.02.01_60/ts_10259202v010201p.pdf
|
The present document gives implementation guidelines on the use of the electronic service guide in IP Datacast over DVB-SH system ([4] to [6]) for the announcement of services to the terminal. The present document intends in particular to guide implementers of IP Datacast over DVB-SH Services, Servers and Terminals to make best use of the specification IP Datacast over DVB-H: Electronic Service Guide TS 102 471 [3]. The present document must also be considered as complementary to the ESG implementation guidelines applicable in DVB-H context (TS 102 592-1 [2]), in particular for supporting ESG regionalization, one of the specific features provided by a DVB-SH network. These implementation guidelines apply to both "DVB-H ESG phase 1" defined in TS 102 471 (V1.2.1) [1] and "DVB-H ESG phase 2" defined in TS 102 471 [3]. These two versions of the same specification mandate in particular the use of different ESG bootstrap structures, which particularly affects some procedures defined in the present document. The present document is structured into three main clauses. Clause 4 provides an overview of hypothesis and requirements followed in the DVB-SH context. Clause 5 describes how regionalization can be ensured in some specific scenarios. Annex A provides guidance on different types of ESG implementation, including DVB-H based ESG implementations, and their interoperability. Annex B provides more details on the DVB-SH network physical capabilities.
|
102 592-1
|
Digital Video Broadcasting (DVB); IP Datacast: Electronic Service Guide (ESG) Implementation Guidelines; Part 1: IP Datacast over DVB-H
|
TS
|
1.1.2
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10259201/01.01.02_60/ts_10259201v010102p.pdf
|
The present document gives implementation guidelines on the use of the electronic service guide in IP Datacast over DVB-H system [1] to [8] for the announcement of services to the terminal. The present document intends in particular to guide implementers of IP Datacast over DVB-H Services, Servers and Terminals to make best use of the specification IP Datacast over DVB-H: Electronic Service Guide TS 102 471 [1]. The document is structured into three main clauses, some of them addressing particular groups of readers. Clause 5 provides an overview of the ESG data model which might be of interest for all readers. The following clause 6 describe typical business and usage scenarios of service delivery over broadcast and related instantiation examples of the ESG data model. Accordingly clause 6 is especially relevant for service implementers. Clause 7 provides guidelines for the terminal behaviour which might be of interest in particular to terminal implementers. Clause 8 provides ESG delivery guidelines for those implementing DVB IPDC headend systems. As those main clauses have particular groups of readers in focus and it should be possible to read those clauses independently of each other. However, it might wise to read the guideline in whole if the reasoning of implementation guidelines in particular clauses are of interest.
|
102 592
|
Digital Video Broadcasting (DVB); IPDC over DVB-H: Electronic Service Guide (ESG) Implementation Guidelines
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102592/01.01.01_60/ts_102592v010101p.pdf
|
The present document gives implementation guidelines on the use of the electronic service guide in IP Datacast over DVB-H system [1] to [8] for the announcement of services to the terminal. The present document intends in particular to guide implementers of IP Datacast over DVB-H Services, Servers and Terminals to make best use of the specification IP Datacast over DVB-H: Electronic Service Guide TS 102 471 [1]. The document is structured into three main clauses, some of them addressing particular groups of readers. Clause 5 provides an overview of the ESG datamodel which might be of interest for all readers. The following clause 6 describe typical business and usage scenarios of service delivery over broadcast and related instantiation examples of the ESG datamodel. Accordingly clause 6 is especially relevant for service implementers. Clause 7 provides guidelines for the terminal behaviour which might be of interest in particular to terminal implementers. Clause 8 provides ESG delivery guidelines for those implementing DVB IPDC headend systems. As those main clauses have particular groups of readers in focus and it should be possible to read those clauses independently of each other. However, it might wise to read the guideline in whole if the reasoning of implementation guidelines in particular clauses are of interest.
|
102 591-2
|
Digital Video Broadcasting (DVB); IP Datacast: Content Delivery Protocols (CDP) Implementation Guidelines; Part 2: IP Datacast over DVB-SH
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10259102/01.01.01_60/ts_10259102v010101p.pdf
|
The present document provides necessary adaptations of the Content Delivery Protocols specified [3] for IP Datacast over DVB-H for the usage in DVB-SH. In particular, the document provides specification as well as usage and implementation guidelines on the use of Content Delivery Protocols (CDP) and different reliability control techniques in IP Datacast over DVB-SH system for the whole delivery chain from the network to the terminal in a DVB-SH system.
|
102 591-1
|
Digital Video Broadcasting (DVB); IP Datacast: Content Delivery Protocols (CDP) Implementation Guidelines; Part 1: IP Datacast over DVB-H
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10259101/01.03.01_60/ts_10259101v010301p.pdf
|
The present document gives implementation guidelines on the use of content delivery protocols and different reliability control techniques in IP Datacast over DVB-H system [1] to [6] and [i.1] to [i.2] for the whole delivery chain from the network to the terminal. The present document intends in particular to guide implementers of basic use cases for IP Datacast over DVB-H to make best use of the specification IP Datacast over DVB-H: Content Delivery Protocols [2].
|
102 591
|
Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Content Delivery Protocols (CDP) Implementation Guidelines
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102591/01.02.01_60/ts_102591v010201p.pdf
|
The present document gives implementation guidelines on the use of content delivery protocols and different reliability control techniques in IP Datacast over DVB-H system [1] to [6] and [i.1] to [i.2] for the whole delivery chain from the network to the terminal. The present document intends in particular to guide implementers of basic use cases for IP Datacast over DVB-H to make best use of the specification IP Datacast over DVB-H: Content Delivery Protocols [2].
|
102 589
|
Forward Link Only Air Interface; Specification for Terrestrial Mobile; Multimedia Multicast
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102589/01.01.01_60/ts_102589v010101p.pdf
|
The present document specifies the Forward Link Only air interface by referencing TIA Terrestrial Mobile Multimedia Multicast standards and by their use.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 17)
|
TS
|
17.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/17.00.00_60/ts_102588v170000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/16.00.00_60/ts_102588v160000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/15.00.00_60/ts_102588v150000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/14.00.00_60/ts_102588v140000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/13.00.00_60/ts_102588v130000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/12.00.00_60/ts_102588v120000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 11)
|
TS
|
11.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/11.00.00_60/ts_102588v110000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/10.00.00_60/ts_102588v100000p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 9)
|
TS
|
9.2.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/09.02.00_60/ts_102588v090200p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 8)
|
TS
|
8.3.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/08.03.00_60/ts_102588v080300p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 588
|
Smart Cards; Application invocation Application Programming Interface (API) by a UICC webserver for Java Card™ platform (Release 7)
|
TS
|
7.5.0
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102588/07.05.00_60/ts_102588v070500p.pdf
|
The present document defines an API that allows a UICC based SCWS defined by OMA to forward HTTP requests to an Applet and to receive the response from the Applet. It also defines an API for the Applet to register and unregister to the SCWS.
|
102 587-6
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 6: Interoperability testing; Test Descriptions (TD)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258706/01.02.01_60/ts_10258706v010201p.pdf
|
The present document contains the Test Descriptions (TD) for interoperability testing of the ERM; Peer-to-Peer Digital Private Mobile Radio using FDMA with a channel spacing of 6,25 kHz with e.r.p of up to 500 mW as defined in TS 102 490 [1]. The objective of this test specification is to provide a basis for interoperability tests for ERM Peer-to-Peer Digital Private Mobile Radio equipment giving a high probability of inter-operability between different manufacturer's ERM DMR equipment.
|
102 587-5
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 5: Interoperability testing; Interoperability Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258705/01.03.01_60/ts_10258705v010301p.pdf
|
The present document specifies the interoperability Test Purposes (TPs) for the Peer-to-Peer Digital Private Mobile Radio (dPMR) standard, TS 102 490 [1]. TPs are defined using the TPLan notation described in ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 587-4
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 4: Conformance testing; Abstract Test Suite (ATS)
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258704/01.02.01_60/ts_10258704v010201p.pdf
|
The present document contains the Abstract Test Suite (ATS) to test the dPMR Call Control (CCL) and Data Link Layer (DLL). The objective of the present document is to provide a basis for conformance tests for ERM dPMR equipment giving a high probability of air interface inter-operability between different manufacturer's ERM dPMR equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [4]) and the ETSI rules for conformance testing (ETS 300 406 [7]) are used as a basis for the test methodology: • Clause 4 describes the Test Configuration used to test the dPMR Dynamic Link Layer (DLL) and the Call Control Layer (CCL). • Clause 5 describes the ATS conventions, which are intended to give a better understanding of the ATS. • Annex A provides guidelines for upper tester implementation as well as testing with an emulated and simulated SUT. • Annex B provides the TTCN-3 part of the ATS. • Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of dPMR. • Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of dPMR.
|
102 587-3
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 3: Requirements catalogue
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258703/01.03.01_60/ts_10258703v010301p.pdf
|
The present document is to provide a catalogue of requirements extracted from ETSI Specifications. The catalogues has been written based on the test specification framework defined in TS 102 351 [2].
|
102 587-2
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 2: Conformance testing; Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258702/01.03.01_60/ts_10258702v010301p.pdf
|
The present document specifies the conformance Test Purposes (TPs) for the Peer-to-Peer digital Private Mobile Radio (dPMR) standard, TS 102 490 [1]. TPs are defined using the TPLan notation described in ES 202 553 [i.1]. Test purposes have been written based on the test specification framework described in TS 102 351 [2] and based on the methodology defined in ISO/IEC 9646-2 [3].
|
102 587-1
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Peer-to-Peer Digital Private Mobile Radio; Part 1: Conformance testing; Protocol Implementation Conformance Statement (PICS) proforma
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/10258701/01.04.01_60/ts_10258701v010401p.pdf
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for the ERM; Peer-to-Peer Digital Private Mobile Radio using FDMA with a channel spacing of 6,25 kHz with e.r.p. of up to 500 mW as defined in TS 102 490 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [3] and ETS 300 406 [4]. The present document details in tabular form the implementation options, i.e. the optional functions additional to those which are mandatory to implement.
|
102 585
|
Digital Video Broadcasting (DVB); System Specifications for Satellite services to Handheld devices (SH) below 3 GHz
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102585/01.02.01_60/ts_102585v010201p.pdf
|
The present document specifies DVB-SH by referencing and making use of ETSI Digital Video Broadcasting standards.
|
102 584
|
Digital Video Broadcasting (DVB); DVB-SH Implementation Guidelines
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102584/01.03.01_60/ts_102584v010301p.pdf
|
The present document provides guidelines for the use and implementation of ETSI Digital Video Broadcasting-Satellite to Handheld (DVB-SH) standard EN 302 583 [1] in the context of providing an efficient way of carrying multimedia services over digital hybrid satellite/terrestrial broadcasting networks to handheld terminals. The present document should be read in conjunction with the: • DVB-SH waveform specifications [1]; • DVB-SH system specifications [2]; • DVB IP Datacast specifications [21] and [22]; • DVB Data broadcasting specifications [9]; • DVB Specifications for Service Information (SI) [24]. Objective The present document draws attention to the technical questions that need to be answered when setting up DVB-SH services and networks and offers some guidance in finding answers to them. It does not cover in detail, issues linked to the content of the broadcasts such as Coding Formats, Electronic Programme Guides (EPG), Access Control (CA), etc. Target readers The present document is aimed at the Technical Departments of organizations that are considering implementing digital hybrid satellite/terrestrial broadcasting to handheld devices. It assumes that readers are familiar with digital satellite and terrestrial networks. Contributors The present document was prepared by members of the Ad-hoc group TM-SSP from the DVB Project. Members include broadcasters, network operators and professional as well as domestic equipment manufacturers.
|
102 578
|
PowerLine Telecommunications (PLT); Coexistence between PLT Modems and Short Wave Radio broadcasting services
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102578/01.02.01_60/ts_102578v010201p.pdf
|
The present document specifies a mechanism for PLT modems to avoid possible coexistence difficulties between PLT and Short Wave radio broadcast. Frequency allocation of the radio broadcasting services are defined by ITU-R Radio Regulations [1]. The mechanism described here is called "smart notching" whereby the PLT-spectrum mask is adjusted to avoid the use of frequencies which are found to be coincident with receivable broadcast signals.
|
102 577
|
Human Factors (HF); Public Internet Access Points (PIAPs)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102577/01.01.01_60/ts_102577v010101p.pdf
|
The present document will establish and set out guidance that should be followed by organizations that design or operate PIAPs. A broad definition of PIAPs has been adopted. This definition includes general purpose desktop computers on a desk, Internet/Information kiosks and public hotspots. A "Design for All" approach has been followed to ensure that PIAPs will be more readily accessible to all people including elderly or users with disabilities and users from a range of cultural backgrounds. The present document identifies approaches to enhancing eInclusion in the provision and use of PIAPs. The present document: • addresses issues that have arisen from previous studies and reports on the use of PIAPs; • identifies existing standards, recommendations and guidelines (especially from ETSI, the ITU-T and CEN) that provide useful guidance to reduce barriers to the use of PIAPs; • proposes new normative requirements, guidelines as well as identifying the need for updates to existing standards, recommendations and guidelines to support eInclusion for PIAPs; • identifies the need for and content of new standards, specifications and guidelines that need to be developed. The primary focus of the present document is on issues related to PIAP customers rather than to the staff at the PIAP.
|
102 576
|
Radio access network equipment specification; Mobile Communication On Board Aircraft (MCOBA) systems; Operational requirements and methodology for showing conformance
|
TS
|
2.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102576/02.02.01_60/ts_102576v020201p.pdf
|
The present document specifies operational requirements and the methodology for showing conformance to the operational requirements for a Mobile Communication Onboard Aircraft system, which allows communication in the GSM and LTE (FDD) 1 800 MHz frequency band and the UMTS 2 100 MHz frequency band to ensure, that mobile terminals will not connect to ground based mobile networks. The present document further specifies measurement methodologies allowing the definition of the key RF parameters of the aircraft, which are: • the aircraft attenuation as observed at the windows; • the aircraft attenuation in combination of the antenna system as observed at the antenna system feeding point; • the effective cabin coupling loss within the aircraft cabin. The present document also provides a way to translate the power level generated by the Mobile Communication Onboard Aircraft system at the antenna system output port to an E.I.R.P. defined outside the aircraft.
|
102 576
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Digital cellular telecommunications system (Phase 2+); Radio access network equipment specification; GSM onboard aircraft; Methodology for showing conformance with operational requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102576/01.01.01_60/ts_102576v010101p.pdf
|
The present document specifies operational requirements and the methodology for showing conformance to the operational requirements for a Mobile Communication Onboard Aircraft system, which allows communication in the GSM and LTE (FDD) 1 800 MHz frequency band and the UMTS 2 100 MHz frequency band to ensure, that mobile terminals will not connect to ground based mobile networks. The present document further specifies measurement methodologies allowing the definition of the key RF parameters of the aircraft, which are: • the aircraft attenuation as observed at the windows; • the aircraft attenuation in combination of the antenna system as observed at the antenna system feeding point; • the effective cabin coupling loss within the aircraft cabin. The present document also provides a way to translate the power level generated by the Mobile Communication Onboard Aircraft system at the antenna system output port to an E.I.R.P. defined outside the aircraft.
|
102 566
|
Access, Terminals, Transmission and Multiplexing (ATTM) Common Requirements for Automated Distribution Frames (ADF) at Street Cabinet
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102566/01.01.01_60/ts_102566v010101p.pdf
|
Due to the requirements for the spreading of xDSL based broadband services, in particular combining more confined coverage areas, faster speeds and multiple services support, operators have primary interest in solutions for automated distribution frames in street cabinets and operators' room down to the building. The present document gathers a first set of common requirements for ADF (Automated Distribution Frames) systems in configurations for street cabinets. The aim of the present document is also to have an integrated view of the architecture, configurations and related management systems required to maintain the overall systems at street cabinets, as today's evolution scenarios predict the possibility of having automated distribution frames spread across networks.
|
102 563
|
Digital Audio Broadcasting (DAB); DAB+ audio coding (MPEG HE-AACv2)
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102563/02.01.01_60/ts_102563v020101p.pdf
|
The present document defines the method to code and transmit audio services using the HE-AACv2 [2] audio coder for Eureka-147 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.
|
102 563
|
Digital Audio Broadcasting (DAB); Transport of Advanced Audio Coding (AAC) audio
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102563/01.02.01_60/ts_102563v010201p.pdf
|
The present document defines the method to code and transmit audio services using the HE-AACv2 [2] audio coder for Eureka-147 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.
|
102 559
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Mobility; Requirements Catalogue
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102559/01.01.01_60/ts_102559v010101p.pdf
|
The present document is a catalogue of all of the mobility-related IPv6 requirements extracted from the following IETF specifications: RFC3775 [2]: Mobility Support in IPv6 (MIPv6). RFC3776 [3]: Using IPsec to Protect Mobile IPv6 Signalling between Mobile Nodes and Home Agents. RFC4068 [4]: Fast Handovers for Mobile IPv6. RFC2473 [1]: Generic Packet Tunnelling in IPv6.
|
102 558
|
Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT): IPv6 Security; Requirements Catalogue
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102558/01.01.01_60/ts_102558v010101p.pdf
|
The present document is a catalogue of all of the security-related IPv6 requirements extracted from the following IETF specifications: RFC 4301 [1]: "Security Architecture for the Internet Protocol". RFC 4302 [2]: "IP Authentication Header". RFC 4303 [3]: "IP Encapsulating Security Payload (ESP)". RFC 4305 [4]: "Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)". RFC 4306 [5] "Internet Key Exchange (IKEv2) Protocol". RFC 2405 [6]: "The ESP DES-CBC Cipher Algorithm With Explicit IV".
|
102 556
|
Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Protection Profile
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102500_102599/102556/01.01.01_60/ts_102556v010101p.pdf
|
The present document defines 3 partial Protection Profiles (PPs) for security capabilities in the NGN and conforms to the guidance and PP Proforma available in ES 202 382 [6] with respect to the guidelines found in EG 202 387 [4]. The background and input for the PPs are presented in clause 4. The PPs are detailed in annexes to the present document as follows: • Annex A: PP for NGN-IMS authentication, source document TS 133 203 [9]. • Annex B: PP for NGN-NDS source authentication, source document TS 133 210 [10]. • Annex C: PP for NGN H.248 deployment, source document ES 283 002 [8]. The present document is for the use of NGN standards developers and may be used in the context of formal evaluation. NOTE 1: A PP is one of the document types subject to evaluation under the evaluation criteria defined in ISO/IEC 15408 [11]. The evaluation criteria are commonly known as the Common Criteria (CC) and in the present document "Common Criteria" is used synonymously to ISO/IEC 15408 [11] (and its Part 1-3 derivatives). NOTE 2: The present document has not been submitted by ETSI for formal evaluation. Its intended use is to be a basis for future PPs in the area. The context of the present document is depicted in figure 1. cd STF292-7008 «Document» TS102165-3 «Document» ISO15408 «Document» 15408-1 «Document» 15408-2 «Document» 15408-3 «Document» EG202387 «Document» ES202382 «Document» ES202387 «Document» TS133203 «Document» TS133210 «Document» ES283002 +Gives guidance on +Adopts proforma from +Provides outline PP for Figure 1: Context of the present document, with main source documents + Adopts PP requirements from + Adopts PP guidance ETSI ETSI TS 102 556 V1.1.1 (2006-11) 7 The PPs in the present document may be primarily considered as measures of completeness of the standardization effort. A security standard is considered complete and suitable for evaluation when every part of the proforma can be filled in by reference to the standardization process and the output documents from that process. Thus it can be conveyed to an assessor that the security development process and the steps towards assurance have been dealt with properly. The purpose of the PPs in the present document is to assist manufacturers by having agreed content that may be used by them in the process of having a product evaluated using the Common Criteria concept. The PPs may be used as part of the manufacturer's documentation suite for use in an evaluation of a product. The intention of ETSI is not to have the presented PPs evaluated and certified in ETSI's name. The PPs in the present document are not complete enough for submission for evaluation, but provides the basis to be added to (worked on) for use in group development. Thus the annexes show generic outlines of PPs open for further refinement. Each PP is open for extended functionality as described in the Common Criteria ISO/IEC 15408-3 [14]. NOTE 1: Extension, according to the Common Criteria ISO/IEC 15408-3 [14], of any of these PPs is open for future work, and should be performed to improve the commercial usability. NOTE 2: The present Protection Profiles are provided as examples only. They are not intended to be registered or stored by ETSI in any archive or registry in any Common Criteria context. The PP format used in the present document complies with the proforma in annex A of ES 202 382 [6]. NOTE 3: Relevant requirements from other sources than the target document and the guidance documents have been included in the requirement section.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.