id
stringlengths 7
13
| title
stringlengths 7
396
| type
stringclasses 2
values | version
stringclasses 249
values | url
stringlengths 90
98
| scope
stringlengths 0
83.8k
|
|---|---|---|---|---|---|
102 310
|
Smart Cards; Extensible Authentication Protocol support in the UICC (Release 7)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102310/07.00.00_60/ts_102310v070000p.pdf
|
The present document defines additional features that are to be provided by the UICC to support EAP authentication capabilities. The goal of these new features is to adapt the UICC to provide support of different EAP methods, ensuring interoperability between the UICC and any terminal independently of their respective manufacturers. The present document defines: • The architectural framework. • The additional commands required.
|
102 310
|
Smart Cards; Extensible Authentication Protocol support in the UICC (Release 6)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102310/06.02.00_60/ts_102310v060200p.pdf
|
The present document defines additional features that are to be provided by the UICC to support EAP authentication capabilities. The goal of these new features is to adapt the UICC to provide support of different EAP methods, ensuring interoperability between the UICC and any terminal independently of their respective manufacturers. The present document defines: • The architectural framework. • The additional commands required.
|
102 302-2
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 5; Emergency Priority Telecommunications Service (EPTS); Part 2: System description for EPTS in TIPHON networks
|
TS
|
5.1.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/10230202/05.01.01_60/ts_10230202v050101p.pdf
|
The present document defines the operation of the Emergency Priority Telecommunications Service (EPTS) in a generic form. It defines the provision of EPTS, the invocation of EPTS by an authorized user, the validation and authentication mechanisms used to prove the credentials of the EPTS user, the extensions required to the TIPHON generic simple call for EPTS, and the inter-domain carriage of EPTS calls. In addition the mechanisms for revocation of user authorization and of the EPTS service are defined.
|
102 295
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; BSM Traffic Classes
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102295/01.01.01_60/ts_102295v010101p.pdf
|
The scope of the present document is the definition of qualitative classes to sort the traffic entering the BSM according to generic class descriptors. The quantitative performance levels expected from a BSM link for each of these classes is beyond the scope of the present document.
|
102 357
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Common Air interface specification; Satellite Independent Service Access Point (SI-SAP) interface: Primitives
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102357/01.02.01_60/ts_102357v010201p.pdf
|
The present document specifies the Satellite Independent Service Access Point (SI-SAP) for the provision of standard Broadband Satellite Multimedia (BSM) services. The SI-SAP defines the Satellite Independent to Satellite Dependent (SI-SD) interface as described in the BSM Services and Architectures report ETSI TR 101 984 [i.1]. This interface also corresponds to the endpoints of the BSM bearer services as illustrated in figure 1. Figure 1: Satellite Independent Service Access Point (SI-SAP) The SI-SAP services are accessed via the SI-SAP interface and they can be used to transport standard IP-based network services. These SI-SAP services are applicable to any IP-based satellite network, including both transparent and regenerative satellites, and including both star and mesh topologies. For example, in the case of a star network topology, one SI-SAP would be located in the remote Satellite Terminal (ST) and the other in the hub ST; whereas in the case of a mesh network topology, the SI-SAPs would be located in the source and destination STs. The present document divides the services into user plane (U-plane), control plane (C-plane), and management plane (M-plane) services. This is a logical (functional) division but these different planes may also be physically separated. For example, in the case of a star topology being used to provide mesh connectivity using bridging at the hub, the SI-SAP will be located in the remote STs for the U-plane but will be located in the remote STs plus the hub ST for the C-plane and M-plane. Similar separations may be required for fully meshed network topologies. The SI-SAP is a logical interface and the service primitives are defined in abstract functional terms. The present document is only intended to define the functionality of this interface and is not intended to constrain the implementation of the interface. The SI-SAP may be implemented as a physical external interface (e.g. using message based exchanges, as reported in annex B of ETSI TS 103 275 [6]); as a logical interface (e.g. using API function calls); as an internal interface (e.g. using embedded procedure calls) or in any other format that provides the specified functionality. More details of the models and concepts used in the present document can be found in the associated SI-SAP guidelines ETSI TR 102 353 [i.2]. Satellite Terminal A Satellite Satellite Terminal B End System A End System B Transmission bearer service BSM Bearer Service TCP transport services & IP network services SI-SAP SI-SAP External Bearer Service External Bearer Service Transmission bearer service ETSI ETSI TS 102 357 V1.2.1 (2015-05) 7
|
102 293
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; IP Interworking over satellite; Multicast group management; IGMP adaptation
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102293/01.01.01_60/ts_102293v010101p.pdf
|
The Internet Group Management Protocol (IGMP) is an integral part of IP and is required to be implemented by all hosts wishing to receive IP multicasts. The present document specifies modifications to IGMP which improve its performance when applied over satellite links. These modifications are internal to IGMP and do not affect the system's interoperability with IP. The modifications concern particularly the so-called "IGMPv2 mode" (described in RFC 2236 [2]) which falls under the umbrella of IGMPv3 (RFC 3376 [1]). IGMPv3 offers automatic backwards reversion capability with the alternative IGMP modes. The adapted mode of IGMP is termed S-IGMP. This solution is suitable for multicast groups on geostationary satellite systems with two-way links. It is suitable for systems based on Any-Source Multicast (e.g. star networks) and especially for those which do not automatically retransmit IP multicast packets on return links to all group members. It is also beneficial to systems which do have this ability for full subnet multicast.
|
102 345
|
Corporate telecommunication Networks (CN); Tunnelling of QSIG over SIP
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102345/01.03.01_60/ts_102345v010301p.pdf
|
The present document specifies tunnelling of "QSIG" over the Session Initiation Protocol (SIP) within a corporate telecommunication network (CN). "QSIG" is a signalling protocol that operates between Private Integrated services Network eXchanges (PINX) within a Private Integrated Services Network (PISN). A PISN provides circuit-switched basic services and supplementary services to its users. QSIG is specified in Standards, in particular [1] (call control in support of basic services), [2] (generic functional protocol for the support of supplementary services) and a number of Standards specifying individual supplementary services. NOTE: The name QSIG was derived from the fact that it is used for signalling at the Q reference point. The Q reference point is a point of demarcation between two PINXs [1]. SIP is an application layer protocol for establishing, terminating and modifying multimedia sessions. It is typically carried over IP [4], [6]. Telephone calls are considered as a type of multimedia session where just audio is exchanged. SIP is defined in [9]. Often a CN comprises both PISNs employing QSIG and IP networks employing SIP. A call or call independent signalling can originate at a user connected to a PISN and terminate at a user connected to an IP network or vice versa. In either case, a gateway provides interworking between QSIG and SIP at the boundary between the PISN and the IP network. Basic call interworking at a gateway is specified in [3]. Another case is where a call or call independent signalling originates at a user connected to a PISN, traverses an IP network using SIP, and terminates at a user connected to another (or another part of the same) PISN. The present document addresses this last case in a way that preserves all QSIG capabilities across the IP network. It achieves this by tunnelling QSIG messages within SIP requests and responses in the context of a SIP dialog. The tunnelling of QSIG through a public IP network employing SIP is outside the scope of the present document. However, the functionality specified in thhe present document is in principle applicable to such a scenario when deployed in conjunction with other relevant functionality (e.g. address translation, security functions, etc.) The present document is applicable to any interworking unit that can act as a gateway between a PISN employing QSIG and a corporate IP network employing SIP, with QSIG tunnelled within SIP requests and responses.
|
102 289
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS Harmonization: Guidelines for implementation of service capabilities
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102289/01.01.01_60/ts_102289v010101p.pdf
|
The present document specifies how UMTS IP Multimedia Subsystem (IMS) services can be realized using the TIPHON service capabilities specified in TS 101 878 [1] and TS 102 283 [2].
|
102 361-1
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Digital Mobile Radio (DMR) Systems; Part 1: DMR Air Interface (AI) protocol
|
TS
|
2.6.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/10236101/02.06.01_60/ts_10236101v020601p.pdf
|
The present document contains technical requirements for Digital Mobile Radio (DMR) operating in the existing licensed land mobile service frequency bands, as identified in CEPT/ERC/T/R 25-08 [i.3]. The present document describes the Air Interface of a scalable Digital Mobile Radio system which covers three tiers of possible products: • Tier I: DMR equipment having an integral antenna and working in direct mode (communication without infrastructure) under a general authorization with no individual rights operation. • Tier II: DMR systems operating under individual licences working in direct mode or using a Base Station (BS) for repeating. • Tier III: DMR trunking systems under individual licences operating with a controller function that automatically regulates the communications. NOTE 1: Tier II and Tier III products encompass both simulcast and non-simulcast systems. NOTE 2: The three tiers of possible products only work independently and there is no interoperability across the tiers. (For more information see the System reference documents ETSI TR 102 335-1 [i.1] and ETSI TR 102 335-2 [i.2].) The present document specifies the Air Interface, complying with either ETSI EN 300 113-1 [1] and ETSI EN 300 113-2 [2] or ETSI EN 300 390-1 [3] and ETSI EN 300 390-2 [4], that has been specifically developed with the intention of being suitable for all identified product tiers. A polite spectrum access protocol for sharing the physical channel has also been specified. Specifically, in this case for use in the existing land mobile service bands with the intention of causing minimum change to the spectrum planning and regulations. Thus the DMR protocol is intended to be applicable to the land mobile frequency bands, physical channel offset, duplex spacing, range assumptions and all other spectrum parameters without need for any change.
|
102 351
|
Methods for Testing and Specification (MTS); IP Testing; TTCN-3 IPv6 Test Specification Toolkit
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102351/01.01.01_60/ts_102351v010101p.pdf
|
The present document gives guidelines for the use of a common method for developing test specifications for IPv6. This method is applicable to all IPv6 categories including the core specification, mobility, security and transitioning to IPv6 from IPv4. The underlying method is based on the methodologies specified in ISO/IEC 9646-1 [4] for conformance tests and TS 102 237-1 [1] for interoperability tests. It provides guidance on the development and use of the following key elements of the method: - a Requirements Catalogue (RC); - a Test Suite Structure (TSS) and Test Purposes (TP); - Test Descriptions (TD) - interoperability; - a TTCN-3 library of data types and values, templates and functions; - an Abstract Test Suite (ATS) - conformance. The methodology also offers guidance on naming conventions and other style-related issues. Although the present document has been developed primarily for use in the testing of IPv6 standards, it could equally be used in other areas of protocol test specification.
|
102 284
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS Harmonization; Extensions and additions to the Network Architecture and Reference Points
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102284/01.01.01_60/ts_102284v010101p.pdf
|
The present document provides an analysis of the TIPHON Release 4 Network Architecture and Reference Points [1] in comparing to the UMTS IP Multimedia Subsystem (IMS) architecture with a view to identifying where, if necessary, the TIPHON architecture needs to be extended to ensure harmonization between the two. Clause 4 provides a comparison of the TIPHON and UMTS architectural concepts. Clause 5 identifies UMTS functional groupings and identifies where the equivalent TIPHON functionality is found in the TIPHON architecture.
|
102 283
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS harmonization; Service capabilities for harmonization between TIPHON and 3G UMTS
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102283/01.01.01_60/ts_102283v010101p.pdf
|
The present document identifies where the service capabilities defined in TS 101 878 [2] Release 4 are insufficient to support the service suite of UMTS as identified in TS 102 285 [1].
|
102 346
|
NFCIP-1; RF interface test methods
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102346/01.01.01_60/ts_102346v010101p.pdf
|
The present document is part of a suite of ECMA standards that specify tests for ECMA-340. It defines test methods for the RF-interface. The present document specifies RF-test methods for NFC devices with antennas fitting within the rectangular area of 85 mm by 54 mm.
|
102 281
|
Railways Telecommunications (RT); Global System for Mobile communications (GSM); Detailed requirements for GSM operation on Railways
|
TS
|
2.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102281/02.04.00_60/ts_102281v020400p.pdf
|
The present document collects all the 3GPPTM Change Requests (CRs) required for operation of GSM for Railways. It complements ETSI EN 301 515 [1].
|
102 268
|
Smart Cards; Test specification for the UICC Application Programming Interface (API) for Java Card(TM) (Release 7)
|
TS
|
7.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102268/07.03.00_60/ts_102268v070300p.pdf
|
The present document covers the minimum characteristics considered necessary in order to provide compliance to ETSI TS 102 241 [9]. It describes the technical characteristics and methods for testing the UICC API for Java CardTM (ETSI TS 102 241 [9]) implemented in a UICC Platform. It specifies the following parts: • test applicability; • test environment description; • tests format; • test area reference; • conformance requirements; • test area files; • test coverage; • test procedure; • a description of the associated testing tools that is used.
|
102 286
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS Harmonization; Extensions and additions to the protocol framework definition: General
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102286/01.01.01_60/ts_102286v010101p.pdf
|
The present document defines extensions to the TIPHON meta-protocol suite of service capabilities to enable full harmonization with the UMTS services identified in 3GPP TR 24.841 [9].
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 18)
|
TS
|
18.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/18.00.00_60/ts_102267v180000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 17)
|
TS
|
17.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/17.00.00_60/ts_102267v170000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/16.00.00_60/ts_102267v160000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/15.00.00_60/ts_102267v150000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/14.00.00_60/ts_102267v140000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 361-2
|
Electromagnetic compatibility and Radio spectrum Matters (ERM); Digital Mobile Radio (DMR) Systems; Part 2: DMR voice and generic services and facilities
|
TS
|
1.2.6
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/10236102/01.02.06_60/ts_10236102v010206p.pdf
|
The present document contains technical requirements for Digital Mobile Radio (DMR) operating in the existing licensed land mobile service frequency bands, as identified in CEPT/ERC/T/R 25-08 [i.1]. The present document describes the voice and generic services and facilities of a scalable Digital Mobile Radio system which covers three tiers of possible products: Tier I: DMR equipment having an integral antenna and working in direct mode (communication without infrastructure) under a general authorization with no individual rights operation. Tier II: DMR systems operating under individual licences working in direct mode (unit-to-unit) or using a Base Station (BS) for repeating. Tier III: DMR trunking systems under individual licences operating with a controller function that automatically regulates the communications. NOTE 1: Tier II and Tier III products encompass both simulcast and non-simulcast systems. NOTE 2: The three tiers of possible products only work independently and there is no interoperability across the tiers. The present document specifies the voice and generic services and facilities of DMR that has been specifically developed with the intention of being suitable for all identified product tiers. The DMR protocol is intended to be applicable to the land mobile frequency bands, physical channel offset, duplex spacing, range assumptions and all other spectrum parameters without need for any change.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/12.00.00_60/ts_102267v120000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/11.01.00_60/ts_102267v110100p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 349
|
Digital Radio Mondiale (DRM); Receiver Status and Control Interface (RSCI)
|
TS
|
4.2.1
|
http://www.etsi.org/deliver/etsi_ts/102300_102399/102349/04.02.01_60/ts_102349v040201p.pdf
|
The present document defines the actual content to be transported in the DRM-specific protocol Receiver Status and Control Interface (RSCI) based on the generic and application-independent Distribution and Communications Protocol (DCP) [2]. The RSCI protocol covers the transport of receiver's status information (output protocol) in addition to the DRM multiplex as well as commands (control protocol) to control the receiver's behaviour. The available TAG items for the RSCI TAG layer within the DCP protocol are defined in the present document. The present document has been revised to provide full support for the xHE-AAC audio codec.
|
102 265
|
Digital Enhanced Cordless Telecommunications (DECT); DECT access to IP networks
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102265/01.02.01_60/ts_102265v010201p.pdf
|
The present document specifies additional requirements for DECT Internet Protocol (IP) applications including networking aspects, Voice over IP (VoIP) and other multimedia exchange over IP, mobility and quality of service properties. It provides an end system, i.e. termination of IP into the DECT Fixed Termination (FT). NOTE: Transparent IP packet service is described in EN 301 649 [16], DPRS standard.
|
102 261
|
Open Network Services and Architecture (ONSA); Abstract architecture and reference points definition; Mapping of functional architectures and requirements for NGN
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102261/01.01.01_60/ts_102261v010101p.pdf
|
The present document is an analysis of the mapping of concrete functional architectures as defined in UMTS IMS and MSF to the TIPHON release 3.0 call control architecture. Whilst developing a generic NGN reference model, reference points and the requirements for protocols and interfaces for interconnection are identified. The objective of the present document is to verify implementation oriented architectures against the Release 3 architecture, as developed in EP TIPHON TS 101 314 [6]. This will highlight if there are incompatibilities between the architectures. This study will use the framework for interconnection reference points as defined by ITU-T SG13 in ITU-T Recommendation Y.140 [50]. Ideally, the generic reference model defines a reference architecture, which is technology independent. A functional architecture for NGN study approaches this subject by considering a decomposed call control reference model and collecting functional entities into a simplified logical structure, and referencing possible implementations.
|
102 257
|
Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Make Call Request supplementary service
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102257/01.01.01_60/ts_102257v010101p.pdf
|
The present document specifies the signalling protocol for the support of the Supplementary Service Make Call Request (SS-MCR) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). Supplementary service MCR enables a Requesting User to request a Co-operating User to establish a new Requested Call to a Destination User. This new Requested Call between the Co-operating and Destination User can be either a Basic call or a Call Independent Signalling Connection. The Q reference point is defined in ECMA-133 [1]. Service specifications are produced in three stages and according to the method specified in ETS 300 387 [6]. The present document contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ECMA-343 [4]. The signalling protocol for SS-MCR operates on top of the signalling protocol for basic circuit switched call control, as specified in ECMA-143 [2], and uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165 [3]. The present document also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between SS-MCR and other supplementary services and ANFs. The present document is applicable to PINXs, which can interconnect to form a PISN.
|
102 256
|
Private Integrated Services Network (PISN); Specification, functional model and information flows; Make Call Request supplementary service
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102256/01.01.01_60/ts_102256v010101p.pdf
|
The present document specifies Supplementary Service Make Call Request (SS-MCR), which is related, but not limited, to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ECMA-142 [2]. The supplementary service MCR enables a Requesting User to request a Co-operating User to establish a new Requested Call to a Destination User. This new Requested Call between the Co-operating and Destination User can be either a Basic call or call independent signalling connection. Service specifications are produced in three stages, according to the method described in ETS 300 387 [4]. The present document contains the stage 1 and stage 2 specifications of SS-MCR. The stage 1 specification (clause 6) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (clause 7) specifies the functional entities involved in the supplementary service and the information flows between them.
|
102 255
|
Private Integrated Services Network (PISN); Inter-exchange Signalling Protocol; Message Centre Monitoring and Mailbox Identification supplementary service
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102255/01.01.01_60/ts_102255v010101p.pdf
|
The present document specifies the signalling protocol for the support of the Message Centre Monitoring supplementary service (SS-MCM) as well as the Mailbox Identification supplementary service (SS-MID) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). The supplementary service MCM enables a Served User to get informed by a Message Centre about the status and status changes of messages stored in that Served Users Mailbox. The supplementary service MID enables a Message Centre to identify a specific mailbox of a Served User in case the Served User has more than one mailbox within the Message Centre. In addition SS-MID enables a Served User to authenticate himself/herself at a specific mailbox located within the Messages Centre. The Q reference point is defined in ECMA-133 [1]. Service specifications are produced in three stages and according to the method specified in ETS 300 387 [9]. The present document contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ECMA-346 [8]. The signalling protocol for SS-MCM and SS-MID uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165 [4]. The present document also specifies additional signalling protocol requirements for the support of interactions at the Q reference point between SS-MCM as well as SS-MID and other supplementary services and ANFs. NOTE: Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications.
|
102 285
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS Harmonization; General aspects
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102285/01.01.01_60/ts_102285v010101p.pdf
|
The present document provides a comparison between TIPHON Releases 3 and 4 and 3GPP UMTS Release 5 system specifications (concentrating on IMS) with a view to harmonize the two. It provides a gap analysis between the two systems, and identifies actions to be taken to resolve any gaps, and achieve harmonization between the two approaches.
|
102 253
|
Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access (MCA) Profile Standard
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102253/01.01.01_60/ts_102253v010101p.pdf
|
The present document specifies the combination of base standards, together with the selection of appropriate options and parameter values, necessary to specify how QSIG / PSS1 can be used for Message Centre Access (MCA) procedures. The present document identifies the necessary or optional employment of particular functions, procedures and services for: • a Calling User to deposit messages for a Served User at a Message Centre; • a Served User to monitor the Served User's Mailbox for new messages; • a Served User to browse through the messages saved in the Served User's Mailbox; • a Served User to retrieve the messages saved in the Served User's Mailbox; and • a Served User to get connected to the Originator of a message or any other destination.
|
102 250-8-1
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 8: Formalized definition of Quality of Service parameters and their computation; Sub-part 1: General aspects and terminology
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/1022500801/01.01.01_60/ts_1022500801v010101p.pdf
|
The present document defines a consistent terminology for the formalized definition of quality of service (QoS) parameters and their computation. In doing so, it carefully distinguishes between measurable quantities and associated statistical aggregation formulas. For frequently used types of quantities and aggregations, generic symbols and calculation formulas are specified. For a large class of QoS parameters, which are basically determined by the observation of events, the present document specifies a methodology for constructing definitions in two stages, using the concept of abstract events and their representation by technical events at well-defined points of observation. In addition, a framework is presented which indicates how QoS parameters may be derived in a generic way via sub- dividing the usage of a service into meaningful sub-transactions, called "phases".
|
102 250-7
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 7: Network based Quality of Service measurements
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225007/01.02.01_60/ts_10225007v010201p.pdf
|
The present document specifies how the quality of service parameters, listed in ETSI TS 102 250-2 [1], should be used for measurements done inside a network, in contrary to measurements done in the end-point with a test tool. A test tool can be either stationary or a drive test tool. The measurements of the QoS parameters according to the present document should be done using standardized interfaces and protocols. This is done to ensure that all measurements in a multi-vendor network can be compared.
|
102 250-6
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 6: Post processing and statistical methods
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225006/01.03.01_60/ts_10225006v010301p.pdf
|
The present document describes definitions and procedures to be used for statistical calculations which are related to Quality of Service (QoS) measurements done by serving probing systems in mobile communications networks, especially GSM and 3G networks. Network performance measurements and their related post-processing are only marginally covered in the present document.
|
102 250-5
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 5: Definition of typical measurement profiles
|
TS
|
2.5.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225005/02.05.01_60/ts_10225005v020501p.pdf
|
The present document specifies test profiles which are required to enable benchmarking of different mobile networks both within and outside national boundaries. It is necessary to have these profiles so that when a specific set of tests is carried out then users are comparing "like for like" performance. All timeouts (as part of the profiles) given in the present document are examples from proven experience. It should be noted that most timeouts given in the present document do, with respect to failure ratios as defined in ETSI TS 102 250-2 [1], have a direct impact on measurement results. A timeout value might for example directly relate to the stop trigger point in the sense of the timeout reached event being the point in time where a certain state has not been reached.
|
102 268
|
Smart Cards; Test specification for the UICC Application Programming Interface (API) for Java Card(TM) (Release 6)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102268/06.02.00_60/ts_102268v060200p.pdf
|
The present document covers the minimum characteristics considered necessary in order to provide compliance to ETSI TS 102 241 [9]. It describes the technical characteristics and methods for testing the UICC API for Java CardTM (ETSI TS 102 241 [9]) implemented in a UICC Platform. It specifies the following parts: • test applicability; • test environment description; • tests format; • test area reference; • conformance requirements; • test area files; • test coverage; • test procedure; • a description of the associated testing tools that is used.
|
102 254
|
Private Integrated Services Network (PISN); Specification, functional model and information flows; Message Centre Monitoring and Mailbox Identification supplementary service
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102254/01.01.01_60/ts_102254v010101p.pdf
|
The present document specifies supplementary service Message Centre Monitoring/Mailbox Identification (SS- MCM/MID), which is related, but not limited, to various basic services supported by Private Integrated Services Networks (PISNs). Basic services are specified in ECMA-142 [2]. The supplementary service MCM enables a Served User to get informed by a Message Centre about the status and status changes of messages stored in that Served Users Mailbox. The supplementary service MID enables a Message Centre to identify a specific mailbox of a Served User in case that the Served User has more than one Mailbox within the Message Centre. In addition SS-MID enables a Served User to authenticate himself/herself at a specific Mailbox located within the Message Centre. Service specifications are produced in three stages, according to the method described in ETS 300 387 [1]. The present document contains the stage 1 and stage 2 specifications of SS-MCM/MID. The stage 1 specification (see clauses 6 and 7) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (see clauses 8 and 9) specifies the functional entities involved in the supplementary service and the information flows between them.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 7)
|
TS
|
7.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/07.01.00_60/ts_102267v070100p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 250-3
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 3: Typical procedures for Quality of Service measurement equipment
|
TS
|
2.4.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225003/02.04.01_60/ts_10225003v020401p.pdf
|
The present document describes typical procedures used for QoS measurements on mobile communication networks, along with settings and parameters for such measurements. Where possible, existing ITU-T or ETSI definitions are referenced. In some cases ITU-T or ETSI definitions do not exist or are considered too generic, then a more service and mobile network specific definition is chosen.
|
102 250-3
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in GSM and 3G networks; Part 3: Typical procedures for Quality of Service measurement equipment
|
TS
|
1.5.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225003/01.05.01_60/ts_10225003v010501p.pdf
|
The present document describes typical procedures used for QoS measurements on mobile communication networks, along with settings and parameters for such measurements. Where possible, existing ITU-T or ETSI definitions are referenced. In some cases ITU-T or ETSI definitions do not exist or are considered too generic, then a more service and mobile network specific definition is chosen.
|
102 292
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102292/01.02.01_60/ts_102292v010201p.pdf
|
The present document presents the architecture that relates the work done in SES BSM TRs on standardization (see ETSI TR 101 984 [i.5] and ETSI TR 101 985 [i.1], Addressing and Routing (see ETSI TR 102 155 [i.2]), Multicasting (see ETSI TR 102 156 [i.3]) and Performance and QoS (see ETSI TR 102 157 [i.4]). The present document provides the introduction to the subsequent Technical Specifications (TSs). The focus of the BSM work is on IP version 4 (IPv4). Actual protocol specification is beyond the scope of the present document and will be issued in specific Technical Specifications (TSs).
|
102 250-2
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in GSM and 3G networks; Part 2: Definition of Quality of Service parameters and their computation
|
TS
|
1.7.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225002/01.07.01_60/ts_10225002v010701p.pdf
|
The present document defines QoS parameters and their computation for popular services in mobile networks. The harmonized definitions given in the present document are considered as the prerequisite for the comparison of QoS measurements and their results. It is assumed that the end user can handle his mobile terminal and the services he wants to use (operability is not evaluated). The computation of specific QoS parameters may vary depending on the respective mobile network, e.g. GSM or 3GPP specified 3G system. In this case a respective notification is provided. Other standardization bodies may request an approved document containing specific QoS parameters to be used as reference in their documents. Therefore, the present document may contain incomplete QoS parameter definitions, e.g. giving a description but missing technical trigger points. Such points are marked as "tbd" (to be defined) and will be updated as soon as possible.
|
102 250-1
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 1: Assessment of Quality of Service
|
TS
|
2.3.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225001/02.03.01_60/ts_10225001v020301p.pdf
|
The present document serves as a generic umbrella document for the further documents part 2 to part 8 of this series. It gives an overview over the topics addressed by these documents and enables the reader to work with the documents in the intended way. It is important to understand that the complete series of documents focuses on Quality of Service which stands for the objective discussion of quality measures from a rather technical perspective. Based on existing quality standards and further definitions, a complete picture of Quality of Service as seen from a user's point of view is drawn. Wherever possible, existing ITU-T or ETSI definitions are referenced. If ITU-T or ETSI definitions do not exist or are considered as too generic, a more service and mobile network specific definition is made. The present document comprises the theoretical backgrounds to understand terms like "Quality of Service", "Network Performance" and "Quality of Experience". Their meaning and interrelation are discussed by taking different QoS models into account.
|
102 250-1
|
Speech Processing, Transmission and Quality Aspects (STQ); QoS aspects for popular services in GSM and 3G networks; Part 1: Identification of Quality of Service criteria
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225001/01.02.01_60/ts_10225001v010201p.pdf
|
The present document serves as a generic umbrella document for the further documents part 2 to part 8 of this series. It gives an overview over the topics addressed by these documents and enables the reader to work with the documents in the intended way. It is important to understand that the complete series of documents focuses on Quality of Service which stands for the objective discussion of quality measures from a rather technical perspective. Based on existing quality standards and further definitions, a complete picture of Quality of Service as seen from a user's point of view is drawn. Wherever possible, existing ITU-T or ETSI definitions are referenced. If ITU-T or ETSI definitions do not exist or are considered as too generic, a more service and mobile network specific definition is made. The present document comprises the theoretical backgrounds to understand terms like "Quality of Service", "Network Performance" and "Quality of Experience". Their meaning and interrelation are discussed by taking different QoS models into account.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 18)
|
TS
|
18.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/18.01.00_60/ts_102241v180100p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 17)
|
TS
|
17.5.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/17.05.01_60/ts_102241v170501p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 16)
|
TS
|
16.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/16.02.00_60/ts_102241v160200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 15)
|
TS
|
15.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/15.04.00_60/ts_102241v150400p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 14)
|
TS
|
14.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/14.02.00_60/ts_102241v140200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card™ (Release 13)
|
TS
|
13.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/13.02.00_60/ts_102241v130200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 250-4
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 4: Requirements for Quality of Service measurement equipment
|
TS
|
2.3.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225004/02.03.01_60/ts_10225004v020301p.pdf
|
The present document defines the minimum requirements of QoS measurement equipment for digital wireless networks in the way that the values and trigger-points needed to compute the QoS parameter as defined in ETSI TS 102 250-2 [3] can be measured following the procedures defined in ETSI TS 102 250-3 [4]. Test-equipment fulfilling the specified minimum requirements, will allow performing the proposed measurements in a reliable and reproducible way.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/11.01.00_60/ts_102241v110100p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/10.00.00_60/ts_102241v100000p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 9)
|
TS
|
9.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/09.02.00_60/ts_102241v090200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 8)
|
TS
|
8.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/08.02.00_60/ts_102241v080200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 7)
|
TS
|
7.10.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/07.10.00_60/ts_102241v071000p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 6)
|
TS
|
6.12.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/06.12.00_60/ts_102241v061200p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description (Release 18)
|
TS
|
18.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/18.01.00_60/ts_102240v180100p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description (Release 17)
|
TS
|
17.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/17.01.00_60/ts_102240v170100p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/11.01.00_60/ts_102240v110100p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description (Release 10)
|
TS
|
10.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/10.01.00_60/ts_102240v100100p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description; (Release 9)
|
TS
|
9.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/09.01.00_60/ts_102240v090100p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description; (Release 8)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/08.00.00_60/ts_102240v080000p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description; (Release 7)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/07.00.00_60/ts_102240v070000p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 241
|
Smart Cards; UICC Application Programming Interface (UICC API) for Java Card (TM) (Release 12)
|
TS
|
12.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102241/12.01.00_60/ts_102241v120100p.pdf
|
The present document defines the stage 2 description of the "Application Programming Interface and Loader Requirements" [11] internal to the UICC. This stage 2 describes the functional capabilities and the information flow for the UICC API implemented on the Java Card™ Platform, 3.1 Classic Edition [2], [3] and [4]. The present document includes information applicable to network operators, service providers and UICC, server and database manufacturers.
|
102 237-2
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 2: H.323-SIP interoperability test scenarios to support multimedia communications in NGN environments
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223702/04.01.01_60/ts_10223702v040101p.pdf
|
The present document describes an H.323-SIP Interoperability Test Suite focusing on test cases for functionality that include protocol interworking. It is based on the documents TS 101 883 [11] (H.323 Profile) and TS 101 884 [12] (SIP Profile) of TIPHON Release 3.
|
102 237-1
|
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interoperability test methods and approaches; Part 1: Generic approach to interoperability testing
|
TS
|
4.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223701/04.01.01_60/ts_10223701v040101p.pdf
|
The present document, "A generic approach to interoperability testing", gives general guidance on the specification and execution of interoperability tests for communication systems in Next Generation Networks (NGN). It provides a framework within which interoperability test specifications for a wide range of product types can be developed. The guidelines are expressed as recommendations rather than strict rules and leave enough freedom to allow test specifiers to adopt and adapt processes to suit each particular project while still ensuring that test specifications accurately reflect the requirements of the base standards and can be executed consistently across a range of configurations. Interoperability testing is the structured and formal testing of functions supported remotely by two or more items of equipment communicating by means of standardized protocols. It is not the detailed verification of protocol requirements specified in a conformance test suite, neither is it the less formal development testing often associated with plug-fest and interop events (frequently referred to as "bake-offs"). Although some consideration is given within the methodology to the operating and reporting aspects of interoperability testing, the primary focus of the present document is on the specification of interoperability testing architectures, test plans and test suites.
|
102 281
|
Rail Telecommunications (RT); Global System for Mobile communications (GSM); Detailed requirements for GSM operation on Railways
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102281/03.01.01_60/ts_102281v030101p.pdf
|
The present document collects all the 3GPPTM Change Requests (CRs) required for operation of GSM for Railways. It complements ETSI EN 301 515 [1].
|
102 250-2
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in mobile networks; Part 2: Definition of Quality of Service parameters and their computation
|
TS
|
2.7.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225002/02.07.01_60/ts_10225002v020701p.pdf
|
The present document defines QoS parameters and their computation for popular services in mobile networks. The harmonized definitions given in the present document are considered as the prerequisite for the comparison of QoS measurements and their results. It is assumed that the end user can handle his mobile terminal and the services he wants to use (operability is not evaluated). The computation of specific QoS parameters may vary depending on the respective mobile network, e.g. GSM or 3GPP specified 3G system. In this case a respective notification is provided. Other standardization bodies may request an approved document containing specific QoS parameters to be used as reference in their documents. Therefore, the present document may contain incomplete QoS parameter definitions, e.g. giving a description but missing technical trigger points. Such points are marked as "tbd" (to be defined) and will be updated as soon as possible.
|
102 250-5
|
Speech and multimedia Transmission Quality Aspects (STQ); QoS aspects for popular services in GSM and 3G networks; Part 5: Definition of typical measurement profiles
|
TS
|
1.6.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225005/01.06.01_60/ts_10225005v010601p.pdf
|
The present document specifies test profiles which are required to enable benchmarking of different mobile networks both within and outside national boundaries. It is necessary to have these profiles so that when a specific set of tests is carried out then users are comparing "like for like" performance. All timeouts (as part of the profiles) given in the present document are examples from proven experience. It should be noted that most timeouts given in the present document do, with respect to failure ratios as defined in ETSI TS 102 250-2 [1], have a direct impact on measurement results. A timeout value might for example directly relate to the stop trigger point in the sense of the timeout reached event being the point in time where a certain state has not been reached.
|
102 240
|
Smart Cards; UICC Application Programming Interface and Loader Requirements; Service description; (Release 6)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102240/06.02.00_60/ts_102240v060200p.pdf
|
The present document defines the service description of the UICC Application Programming Interface (UICC API) internal to the UICC. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to network operators, service providers and terminal, UICC, Network Access Application (NAA) providers, switch and database manufacturers. The present document contains the core requirements, which are sufficient to provide a complete service. It is highly desirable however, that technical solutions for a UICC API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network wide basis, nation-wide basis or particular to a group of users. It is expected that such additional functionality does not compromise conformance to the core requirements of the service.
|
102 294
|
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; IP interworking via satellite; Multicast functional architecture
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102294/01.01.01_60/ts_102294v010101p.pdf
|
The present document presents a functional multicast services architecture bringing together the previous BSM TRs on Standardisation (see TR 101 984 and TR 101 985) and Multicasting (see TR 102 156) and the TS on BSM Functional Architecture (see TS 102 292). It also links in a common framework the current Work Items on Multicast Protocols over the BSM. Finally, it provides a functional structure to the subsequent Multicast Technical Specifications (TSs) to be produced by the SES Technical Committee. The focus of the present document is on the IP version 4 (IPv4) protocols; this is consistent with the other protocol work performed in the BSM working group.
|
102 232-6
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 6: Service-specific details for PSTN/ISDN services
|
TS
|
3.5.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223206/03.05.01_60/ts_10223206v030501p.pdf
|
The present document contains service-specific details for the handover of the lawfully intercepted PSTN/ISDN Services (including emulated services such as those defined in ETSI ES 282 002 [i.3]) using packet-based techniques as defined in ETSI TS 102 232-1 [2].
|
102 250-4
|
Speech and multimedia Transmission Quality (STQ); QoS aspects for popular services in GSM and 3G networks; Part 4: Requirements for Quality of Service measurement equipment
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10225004/01.03.01_60/ts_10225004v010301p.pdf
|
The present document defines the minimum requirements of QoS measurement equipment for digital wireless networks in the way that the values and trigger-points needed to compute the QoS parameter as defined in ETSI TS 102 250-2 [3] can be measured following the procedures defined in ETSI TS 102 250-3 [4]. Test-equipment fulfilling the specified minimum requirements, will allow performing the proposed measurements in a reliable and reproducible way.
|
102 267
|
Smart Cards; Connection Oriented Service API for the Java Card(TM) platform (Release 13)
|
TS
|
13.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102267/13.00.00_60/ts_102267v130000p.pdf
|
The present document defines an Application Programming Interface for the Java CardTM to use transport protocols (e.g. CAT_TP as defined in ETSI TS 102 127 [1]) for CAT applications. This stage 2 document describes the interface functionalities, the interface working mechanisms and its information flow.
|
102 232-7
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 7: Service-specific details for Mobile Services
|
TS
|
3.13.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223207/03.13.01_60/ts_10223207v031301p.pdf
|
Introduction The present document specifies an approach for the handover of the lawfully-intercepted information that is defined in the two standards: 3GPP TS 33.108 [3] and 3GPP TS 33.128 [6]. The present document uses the handover techniques defined in ETSI TS 102 232-1 [2]. In this way, the present document allows additional services to be delivered through a common interface. 3GPP TS 33.108 The scope of the present document includes the handover of lawfully-intercepted information from the following parts of 3GPP TS 33.108 [3]: • Intercept Related Information (IRI) and the Content of Communication (CC) from the mobile circuit-switched domain (3GPP TS 33.108 [3], clause 5). • IRI and CC from the mobile packet-switched domain (3GPP TS 33.108 [3], clause 6). • IRI and CC from the multi-media domain (3GPP TS 33.108 [3], clause 7). • IRI and CC from the EPS domain (3GPP TS 33.108 [3], clause 10). • IRI and CC from the IMS Conference domain (3GPP TS 33.108 [3], clause 11). • IRI and CC from the IMS-based VoIP domain (3GPP TS 33.108 [3], clause 12). • IRI from the Proximity Services domain (3GPP TS 33.108 [3], clause 13). • IRI and CC from the Group Communication System Enablers domain (3GPP TS 33.108 [3], clause 14). The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [3]. 3GPP TS 33.128 The scope of the present document includes the handover of lawfully-intercepted information in accordance with 3GPP TS 33.128 [6].
|
102 232-5
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 5: Service-specific details for IP Multimedia services
|
TS
|
3.22.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223205/03.22.01_60/ts_10223205v032201p.pdf
|
The present document specifies interception of Internet Protocol (IP) Multimedia (MM) Services based on the Session Initiation Protocol (SIP) and Realtime Transport Protocol (RTP) and Message Session Relay Protocol (MSRP) and IP MM services as described by the Recommendations ITU-T H.323 [6] and H.248-1 [i.3]. The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. The present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [1].
|
102 232-4
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 4: Service-specific details for Layer 2 services
|
TS
|
3.8.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223204/03.08.01_60/ts_10223204v030801p.pdf
|
The present document specifies Lawful Interception for an Access Provider that has access to layer 2 session information and that is not required to have layer 3 information. In this case, the focus of Lawful Interception (LI) for IP Network Access is on the portion of the network, commonly referred to as "layer 2 interception", that facilitates subscriber access to the Public IP network. The present document describes the LI at the interception domain of the access network. The present document contains: • a stage 1 description of the Lawful Interception service; • a stage 2 description of the information flows between the functional entities (including the information elements involved) and triggering events; and • a stage 3 description of the protocol and procedures to be used in mapping from stage 2 information flows and elements to Intercept Related Information (IRI) and Content of Communication (CC). The present document is consistent with the definition of the Handover Interface, as described in ETSI TS 102 232-1 [2]. NOTE 1: Layer 3 interception is described in ETSI TS 102 232-3 [12]. NOTE 2: Layer 2 interception is not applicable to the PS domain of the GSM/UMTS networks (3GPP TS 23.060 [15]).
|
102 232-3
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 3: Service-specific details for internet access services
|
TS
|
3.16.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223203/03.16.01_60/ts_10223203v031601p.pdf
|
The present document contains a stage 1 description of the interception information in relation to the process of binding a "target identity" to an IP address when providing Internet access and a stage 2 description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. The present document includes but is not restricted to IRI based on application of Dynamic Host Configuration Protocol (DHCP) and Remote Authentication Dial-In User Service (RADIUS) technology for binding a "target identity" to an IP address and CC for the intercepted IP packets. The definition of the Handover Interface 2 (HI2) and Handover Interface 3 (HI3) is outside the scope of the present document. For the handover interface is referred to ETSI TS 102 232-1 [2].
|
102 232-2
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 2: Service-specific details for messaging services
|
TS
|
3.16.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223202/03.16.01_60/ts_10223202v031601p.pdf
|
The present document contains a stage 1 like description of the interception information in relation to the process of sending and receiving asynchronous messages. The present document also contains a stage 2 like description of when Intercept Related Information (IRI) and Content of Communication (CC) need to be sent, and what information it needs to contain. Examples of asynchronous messages include email, unified messaging and chat applications. The definition of handover transport and encoding of HI2 and HI3 is outside the scope of the present document. Refer to ETSI TS 102 232-1 [3]. The present document is designed to be used where appropriate in conjunction with other deliverables that define the service specific IRI data formats. The present document aligns with 3GPP TS 33.108 [5], ETSI TS 101 671 [i.3], ETSI TS 101 331 [1] and ETSI TR 101 944 [i.1].
|
102 232-1
|
Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery
|
TS
|
3.35.1
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223201/03.35.01_60/ts_10223201v033501p.pdf
|
The present document specifies the general aspects of HI2 and HI3 interfaces for handover via IP based networks. The present document: • specifies the modular approach used for specifying IP based handover interfaces; • specifies the header(s) to be added to IRI and CC sent over the HI2 and HI3 interfaces respectively; • specifies protocols for the transfer of IRI and CC across the handover interfaces; • specifies protocol profiles for the handover interface. The present document is designed to be used where appropriate in conjunction with other deliverables that define the service-specific IRI data formats (including ETSI TS 102 227 [i.1], ETSI TS 101 909-20-1 [33], ETSI TS 101 909-20-2 [34], ETSI TS 102 232-2 [5], ETSI TS 102 232-3 [6], ETSI TS 102 232-4 [32], ETSI TS 102 232-5 [37], ETSI TS 102 232-6 [36] and ETSI TS 102 232-7 [38]). Where possible, the present document aligns with 3GPP TS 33.108 [9] and ETSI TS 101 671 [4] and supports the requirements and capabilities defined in ETSI TS 101 331 [i.9] and ETSI TR 101 944 [i.4]. For the handover of intercepted data within GSM/UMTS PS and CS domains, the present document does not override or supersede any specifications or requirements in 3GPP TS 33.108 [9] and ETSI TS 101 671 [4]. For the handover of services defined in 3GPP TS 33.128 [46], in the event of conflict between the present document and 3GPP TS 33.128 [46], the terms of 3GPP TS 33.128 [46] apply.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 17)
|
TS
|
17.4.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/17.04.00_60/ts_10223002v170400p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/16.00.00_60/ts_10223002v160000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/15.00.00_60/ts_10223002v150000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 14)
|
TS
|
14.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/14.00.00_60/ts_10223002v140000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 13)
|
TS
|
13.3.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/13.03.00_60/ts_10223002v130300p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/12.00.00_60/ts_10223002v120000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 11)
|
TS
|
11.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/11.00.00_60/ts_10223002v110000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 10)
|
TS
|
10.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/10.00.00_60/ts_10223002v100000p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-2
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 2: UICC features (Release 9)
|
TS
|
9.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223002/09.02.00_60/ts_10223002v090200p.pdf
|
The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 221 [1]. The present document specifies the test cases for: • the electrical characteristics of the UICC; • the initial communication establishment and the transport protocols; • the communication layers between the UICC and the UICC-enabled terminal. Test cases for the USB ICC relating to ETSI TS 102 221 [1] interface as well as test cases for SWP/HCI relating to ETSI TS 102 613 [19] and ETSI TS 102 622 [i.1] are out of scope of the present document.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 17)
|
TS
|
17.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/17.02.00_60/ts_10223001v170200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 16)
|
TS
|
16.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/16.00.00_60/ts_10223001v160000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 15)
|
TS
|
15.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/15.00.00_60/ts_10223001v150000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 14)
|
TS
|
14.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/14.02.00_60/ts_10223001v140200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 13)
|
TS
|
13.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/13.02.00_60/ts_10223001v130200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 12)
|
TS
|
12.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/12.00.00_60/ts_10223001v120000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230-1
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification; Part 1: Terminal features (Release 11)
|
TS
|
11.1.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/10223001/11.01.00_60/ts_10223001v110100p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 10)
|
TS
|
10.2.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/10.02.00_60/ts_102230v100200p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
102 230
|
Smart Cards; UICC-Terminal interface; Physical, electrical and logical test specification (Release 9)
|
TS
|
9.0.0
|
http://www.etsi.org/deliver/etsi_ts/102200_102299/102230/09.00.00_60/ts_102230v090000p.pdf
|
The present document specifies the interface test for the Terminal/UICC. The present document specifies the tests of: • physical characteristics of the UICC; • the electrical interface between the UICC and the Terminal; • the initial communication establishment and the transport protocols; • the application independent procedures.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.