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
|
|---|---|---|---|---|---|
101 231
|
Television systems; Register of Country and Network Identification (CNI), Video Programming System (VPS) codes and Application codes for Teletext based systems
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101231/01.03.01_60/ts_101231v010301p.pdf
|
The present document contains the so-far allocated values of the Network Identification (NI) field of the Teletext Broadcast Service Data Packet (extension data packet of type 8/30 format 1), and the Country and Network Identification (CNI) fields of the Programme Delivery Control (PDC) data packets (extension data packets X/26 and 8/30 format 2). The present document also contains identification codes related to Video Programme System (VPS) CNI, which apply to German, Austrian and Swiss TV programme providers. Services like Teletext, PDC or VPS that contain Network Identification data in their formats may be used (besides their primary purpose) also as a reference for a source display or for Automatic Tuning Systems (ATS). The CNI codes are also used in Electronic Programme Guide transmissions.
|
101 225
|
Digital Video Broadcasting (DVB); Home Local Network Specification based on IEEE 1394
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101225/01.01.01_60/ts_101225v010101p.pdf
|
The present document standardizes the topology, physical interfaces and a complete stack of protocols for the Home Local Network (HLN). This includes the specification of the APIs that an application on an HLN device can use to access the services provided by this HLN device or any other HLN device, as well as a Java language binding for these APIs. This allows e.g. Java applications to be downloaded to a DVB Receiver and use the services from other HLN devices such as storage devices. The HLN services and APIs allow any HLN device, to access (interactive) DVB services, Internet services, or other services even if that device itself is not directly connected to a Home Access Network (HAN) or to the corresponding Access Network that delivers these services to the home. The HLN specification covers the possibility of connecting multiple DVB receivers or devices providing access to other services, to the HLN. This HLN specification also allows for multiple applications to execute simultaneously on multiple HLN Devices and share, in a cooperative way, the HLN resources such as bandwidth or a DVB receiver. The present document is based on the commercial requirements in TM1690 (rev 2) (see Bibliography), the role of the HLN in the total architecture of the In-Home Digital Network (IHDN) given in DVB-IHDN 012 (rev 6) (see Bibliography), as well as the technical requirements given in DVB-IHDN 012 (rev 6) (see Bibliography).
|
101 224
|
Digital Video Broadcasting (DVB); Home Access Network (HAN) with an active Network Termination (NT)
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101224/01.01.01_60/ts_101224v010101p.pdf
| |
101 220
|
<empty>
|
TS
|
18.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/18.02.00_60/ts_101220v180200p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 17)
|
TS
|
17.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/17.02.00_60/ts_101220v170200p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 16)
|
TS
|
16.1.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/16.01.00_60/ts_101220v160100p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 15)
|
TS
|
15.3.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/15.03.00_60/ts_101220v150300p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 14)
|
TS
|
14.1.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/14.01.00_60/ts_101220v140100p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 13)
|
TS
|
13.1.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/13.01.00_60/ts_101220v130100p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 12)
|
TS
|
12.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/12.02.00_60/ts_101220v120200p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 11)
|
TS
|
11.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/11.02.00_60/ts_101220v110200p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 10)
|
TS
|
10.4.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/10.04.00_60/ts_101220v100400p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 9)
|
TS
|
9.3.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/09.03.00_60/ts_101220v090300p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 8)
|
TS
|
8.5.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/08.05.00_60/ts_101220v080500p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 7)
|
TS
|
7.13.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/07.13.00_60/ts_101220v071300p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 283
|
Digital cellular telecommunications system (Phase 2+) (GSM); Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 (GSM 03.93 version 6.2.0 Release 1997)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101283/06.02.00_60/ts_101283v060200p.pdf
|
The present document gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 5)
|
TS
|
5.2.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/05.02.00_60/ts_101220v050200p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 297
|
Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) (GSM 04.65 version 6.7.0 Release 1997)
|
TS
|
6.7.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101297/06.07.00_60/ts_101297v060700p.pdf
|
The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS). The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g., AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer [4] and the Session Management (SM) sub-layer [2]. The main functions of SNDCP are: - Multiplexing of several PDPs. - Compression / decompression of user data. - Compression / decompression of protocol control information. - Segmentation of a network protocol data unit (N-PDU) into Logical Link Control Protocol Data Units (LL-PDUs) and re-assembly of LL-PDUs into an N-PDU. GSM 04.65 is applicable to GPRS MS and SGSN.
|
101 209-2
|
Identification card systems; Telecommunications IC cards and terminals; Interoperability with synchronous prepaid cards; Part 2: Security requirements
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120902/01.01.01_60/ts_10120902v010101p.pdf
|
The present document defines security requirements of the interoperability of synchronous prepaid cards in order to provide a common security level for compliant systems. It focuses mainly on the three elements of the complete system that are directly related to interoperability security. These three elements are: - the Security Module (SM); - the Secure Device (SD); - the Trusted Third Party (TTP). In the standard ES 201 209-1 [1], the following mechanisms are defined: - acceptance of User Memory Cards (UMC) for payment purposes; - claim of money for proven UMC usage from card issuers; - key management between system operators and card issuer. A security framework is necessary to support an interoperability scheme on the basis of ES 201 209-1 [1]. For card issuers who want to participate in such an interoperability scheme, trust in the security of the system is necessary, whereby two basic targets are most important: - sufficient protection of the master keys of the card applications; - correct billing. These security targets are mostly reflected in the following two aspects of the architecture of the system described in [1], which are also described in annex A of [1]. - initial key download supported by the Trusted Third Party (TTP); and - security requirements fulfilled by the Security Module (SM). In the present document, the basic security requirements to reach the above mentioned security targets are specified. Systems can be evaluated against these requirements. This gives a common security level for systems in compliance with the present document. In order to achieve this, the present document describes: - the security architecture of the system; - security targets to be achieved in the system; - security requirements for the security relevant components; - security requirements for the roles; and - basic security requirements for the development and production of security products. The present document does not imply the mandatory use of specific security mechanisms, if not already specified in ES 201 209-1 [1]. ETSI TS 101 209-2 V1.1.1 (1998-05) 9
|
101 207-3
|
Identification card systems; Telecommunications IC cards and terminals; Test methods and conformance testing for EN 726-7; Part 3: Abstract Test Suite (ATS) and Implementation eXtra Information for Testing (IXIT) proforma specification.
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120703/01.02.01_60/ts_10120703v010201p.pdf
|
The present document specifies the Abstract Test Suite (ATS) and Implementation eXtra Information for Testing (IXIT) proforma for Application independent card requirements defined in TS 101 200-7 [1]. ISO/IEC 9646-1 [2], ISO/IEC 9646-2 [3], ISO/IEC 9646-3 [4], ISO/IEC 9646-4 [5] and ISO/IEC 9646-5 [6] are used as the basis for the test methodology.
|
101 207-2
|
Identification card systems; Telecommunications IC cards and terminals; Test methods and conformance testing for EN 726-7; Part 2: Test Suite Structure and Test Purposes (TSS & TP) specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120702/01.02.01_60/ts_10120702v010201p.pdf
|
The present document provides Test Suite Structure and Test Purposes (TSS&TP). It applies to the Security Module (SM) defined in TS 101 206-7 [7] in compliance with the relevant requirements, and according to the relevant guidance given in ISO/IEC 9646-7 [12] and ETS 300 406 [10]. The set of test purposes described herein is intended to proof the compliance of a security module with the standard TS 101 206-7 [7] (about 140 tests) and it is seen as an extension of the test purposes made for TS 101 206-3 [6] (about 645 tests), however the number of tests and the depth of testing is not sufficient for a product qualification test. For a product qualification at least the following tests should be added: - User profile test: - to test whether the SM suits the need for a specific application. Here all possible scenarios should be run. - Life cycle test: - to test the behaviour of a SM after it has been used for X transactions, where X is a multiple of the guaranteed life cycle of the programmable memory. - Stress test: - to test the behaviour of the SM at physical stress, such as under voltage, over voltage, too high or low frequencies and spikes on the VCC/VPP line. - Performance test: - to test whether the implementation is able to handle the defined scenarios within the defined time limits. - Key test: - each key in a SM should be used for its specified purpose at least once and the result should be checked. - Additional file tests: - each file present in the SM should be selected and read out, if possible. The answer to SELECT and the contents of the file should be checked against the specification. Tests for additional functions. For a compliance with the specification the SM should at least be tested with: - each allowed parameter, or at least their extreme values; - at least one invalid parameter; - each return code should at least be provoked once; - the successful operation of the function should be tested. In addition to that, tests can be added for: - all invalid parameter combinations; - undefined situations; etc. ETSI TS 101 207-2 V1.2.1 (1999-05) 8
|
101 270-1
|
Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Functional requirements
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10127001/01.04.01_60/ts_10127001v010401p.pdf
|
The present document specifies requirements for transceivers providing very high bit-rate digital transmission on metallic, unshielded, access network wire pairs. The technology is referred to as Very high speed Digital Subscriber Line (VDSL). The present document is part 1 of the specification for VDSL and is applicable to metallic access transmission systems designed to provide multi-megabit/s digital access over part of the existing, unshielded, metallic access network. It is concerned with the key functional and electrical requirements for VDSL. It is linecode independent and is intended to set the boundary requirements that all compliant VDSL transceivers shall meet. TS 101 270-2 [18] is concerned with requirements of the linecode method that enable the requirements of the present document to be met. The definition of physical interfaces is outside the scope of the present document. If an appropriate interface for a specific application exists it may be included to describe how these requirements map to it. The VDSL transmission system, in its most basic form, consists of an application independent core and an application specific block. The core is purely an application independent bit-pump which transports information from one end of the metallic access link to the other. The digital data is mapped into a core frame that is defined logically and not physically. The core frame is therefore considered to be the interface between the application specific and the application independent part of the VDSL system. The application specific part may be subdivided into (at least) two smaller parts: mapping and interface. The scope of the present document is shown graphically in figure 1 and figure 2, where the Network Termination (NT) and Line Termination (LT) are considered separately. Interface Wire-pair VDSL Network Termination Out of scope Within scope VDSL core frame VDSL application frame UNI at T reference point Mapping Transceiver UNI Figure 1: NT reference model scope ETSI ETSI TS 101 270-1 V1.4.1 (2005-10) 8 Wire-pair VDSL Line Termination VDSL core frame Within scope Out of scope ONU or Exchange line card Transceiver Mapping UPF VDSL application frame Figure 2: LT reference model scope
|
101 263
|
Transmission and Multiplexing (TM); Passive optical components; Fibre optic mechanical splices for single-mode optical fibre communications systems for indoor and outdoor applications; Common requirements and conformance testing
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101263/01.02.01_60/ts_101263v010201p.pdf
|
The present document specifies requirements for mechanical splices to be used in single-mode optical fibre telecommunication land based (not submarine) systems. The scope covers the establishment of minimum uniform requirements for the following aspects: • optical, environmental and mechanical properties; • test conditions; • acceptance criteria. Reliability aspects of connector sets are not covered by the present document. Some users may have additional specific requirements, such as a need to verify performance at lower temperatures. These users should specify mechanical splices conforming to the basic ETSI performance standard, plus additional tests or more severe test conditions. Two grades of mechanical splices have been established in the present document regarding their performance in environmental tests. These are referred to as grades V and T.
|
101 376-5-2
|
GEO-Mobile Radio Interface Specifications (Release 3); Third Generation Satellite Packet Radio Service; Part 5: Radio interface physical layer specifications; Sub-part 2: Multiplexing and Multiple Access; Stage 2 Service Description; GMR-1 3G 45.002
|
TS
|
3.5.1
|
http://www.etsi.org/deliver/etsi_ts/101300_101399/1013760502/03.05.01_60/ts_1013760502v030501p.pdf
|
The present document defines the structure of the physical channels for the radio subsystem in the GMR-1 3G Mobile Satellite System. It describes the GMR-1 3G concept of logical channels and the timing concepts of TDMA frames, timeslots, and bursts. It defines the relationship between logical and physical channels, and defines the logical channels in terms of size, structure and timing relationships.
|
101 376-5-2
|
GEO-Mobile Radio Interface Specifications (Release 2); General Packet Radio Service; Part 5: Radio interface physical layer specifications; Sub-part 2: Multiplexing and Multiple Access; Stage 2 Service Description; GMPRS-1 05.002
|
TS
|
2.3.1
|
http://www.etsi.org/deliver/etsi_ts/101300_101399/1013760502/02.03.01_60/ts_1013760502v020301p.pdf
|
The present document defines the structure of the physical channels for the radio subsystem in the GMR-1 3G Mobile Satellite System. It describes the GMR-1 3G concept of logical channels and the timing concepts of TDMA frames, timeslots, and bursts. It defines the relationship between logical and physical channels, and defines the logical channels in terms of size, structure and timing relationships.
|
101 211
|
Digital Video Broadcasting (DVB); Implementation and usage of Service Information (SI)
|
TS
|
1.13.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101211/01.13.01_60/ts_101211v011301p.pdf
|
The present document provides implementation guidelines for the use and implementation of the DVB Service Information (SI) coding in a DVB digital TV environment including satellite- cable- and terrestrial networks. The guidelines are intended to be highly recommended rules for the usage of the DVB SI syntax specified in ETSI EN 300 468 [1]. As such, they facilitate the efficient and reliable implementation of basic user-interaction functions in Integrated Receiver-Decoders (IRD). The rules apply to broadcasters, network operators as well as manufacturers. The rules are specified in the form of constraints on the DVB SI streams or in terms of intended interpretation by IRDs. The specification of these functions in no way prohibits IRD manufacturers from including additional features, and should not be interpreted as stipulating any form of upper limit to the performance. The guidelines do not cover features related to user-interface details or advanced Electronic Program Guides (EPG). Such issues are left to the marketplace. NOTE: It is highly recommended that the IRD should be designed to allow for future compatible extensions to the DVB SI syntax. All the fields "reserved" (for ISO), "reserved_future_use" (for ETSI), and "user defined" in the ETSI EN 300 468 [1] should be ignored by IRDs designed not to make use of them. The "reserved" and "reserved_future_use" fields may be specified in the future by the respective bodies, whereas the "user defined" fields will not be standardized. The present document uses the terminology defined in ETSI EN 300 468 [1] and should be read in conjunction with that EN.
|
101 220
|
Smart Cards; ETSI numbering system for telecommunication application providers (Release 6)
|
TS
|
6.7.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101220/06.07.00_60/ts_101220v060700p.pdf
|
The present document provides for the administration of shared name spaces in use by applications on the UICC, as defined in ETSI TS 102 221 [43], including the managed allocation of identifiers from these name spaces.
|
101 252
|
Digital cellular telecommunications system (Phase 2+) (GSM); Description for the use of a Shared Inter Working Function (SIWF) in a GSM PLMN; Stage 2 (GSM 03.54 version 6.0.0 Release 1997)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/101252/06.00.00_60/ts_101252v060000p.pdf
|
The present document defines the stage two description of the Shared Inter Working Function (SIWF) on Global System for Mobile communications (GSM). A stage one description does not exist because this service is not visible to the service subscribers and users. This stage two identifies the functional Capabilities and information flows needed to support the service. The signalling system protocols and switching functions needed to implement this service are defined in the relevant specifications. Interworking with other networks (e.g. PSTN) needs the presence of specific functions associated with the MSC, known as interworking functions (IWF). The IWFs depend on the type of network with which it is desired to interconnect and the type of service desired. A Shared Inter Working Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain number of MSCs). SIWF is applied to data services in GSM Phase 2 and GSM Phase 2+ (as defined in GSM 02.02, GSM 02.03 and GSM 02.34). The usage of a SIWF requires no additional manipulation at the MS. There is an interest to have a Shared Interworking Function (SIWF) for the following reasons: - possibility to fabricate/obtain the specific functionality needed for data services in areas where data traffic is expected to be low, - handling of data calls in case of local overload of the data traffic, - quick introduction and roll-out of new data services.
|
101 206-7
|
Identification card systems; Telecommunications IC cards and terminals; Part 7: Security module
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120607/01.03.01_60/ts_10120607v010301p.pdf
|
The present document specifies: a) the minimum security requirements for a Security Module (SM); b) the general card related functions embedded in the SM - terminal protocols including minimum data exchange. The data elements and cryptographic processing described in annex A for the case where the SM is an IC card shall be supported if the SM is not an IC card or the configuration of the system, e.g. where the SM handles more than one terminal/user card. Configurations where the SM handles more than one terminal/user card are not fully described in the present document. Further mechanisms may be required to enable these configurations; c) the necessary security services and mechanisms to provide application and cryptographic security information for the processing of telecommunication transactions, considering several types of SM at different locations in the system and different system configurations. The present document allows interaction between the IC card and the SM via the terminal in a way that may be functionally transparent to the terminal and possibly also the network(s). This provides the flexibility to use different techniques, commands and message formats at the terminal - SM interface. The present document supports IC cards with payment applications following EN 726-5 [3] and all card applications following clauses 4 to 7 of the present document. The present document supports IC cards following TS 101 206-3 [2]. Other telecommunication IC cards which do not follow EN 726, e.g. simple memory cards, may also be supported by the SM described in the present document.
|
101 206-4
|
Identification card systems; Telecommunications IC cards and terminals; Part 4: Application independent card related terminal requirements
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120604/01.03.01_60/ts_10120604v010301p.pdf
|
The present document specifies the application independent card related characteristics of card terminals able to process cards complying with TS 101 206-3 [1]. All common characteristics which are necessary for a standardized card use in the terminals are defined. The present document does not preclude letting terminals accept and process cards complying with other standards. The application-specific characteristics are not defined in the present document. They are defined and described in the relevant application requirements. The present document does not specify any internal realization of a card-terminal. It describes: a) the requirements for the physical and environmental specifications on the card terminal, the electronic signals and transmission protocols; b) the application independent logical model, which should be used as a basic design of the logical structure of card specific requirements supported by the terminal; c) the description of the application independent functions and general scenarios to be used by most of the applications; d) the error handling.
|
101 206-3
|
Identification card systems; Telecommunications IC cards and terminals; Part 3: Application independent card requirements
|
TS
|
1.3.2
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120603/01.03.02_60/ts_10120603v010302p.pdf
|
The present document specifies the application-independent characteristics of multi-application Integrated Circuit (IC) cards and plug-in modules for telecommunication applications in order to ensure interoperability for telecommunication cards with the various systems and terminals. Mono-application cards are considered to be a subset of multi-application cards. All common characteristics, necessary for the interactions between the card and the external world are defined. The present document does not preclude cards from other sectors from containing telecommunication application(s) based on the present document. The application-specific characteristics are not defined in the present document. They are defined and described in the relevant application requirements. The present document does not specify any internal technical implementation. It describes: a) the requirements for the physical characteristics of the card, the electronic signals and the transmission protocols; b) the application-independent logical model which should be used as a basis for the design of the logical structure of, optionally, several applications in the card; c) the security facilities concerning the access to the different parts within the card and the possible interactions between these parts. Also the description of security functions which should be needed generally by the various applications. They should be available as a common set; d) the description of the application-independent functions between card and external world, should be used as a standardized common set for all basic functions used in international applications; e) the mapping of these application messages (commands and responses) under standardized protocols; f) the contents of the Master File (MF); g) the interoperability of IC cards; h) the overall security aspects for card-manufacturers, application providers and card-issuers.
|
101 204-2
|
Identification card systems; Telecommunications IC cards and terminals; Test methods and conformance testing for EN 726-4; Part 2: Test Suite Structure and Test Purposes (TSS & TP) specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120402/01.02.01_60/ts_10120402v010201p.pdf
|
The present document provides Test Suite Structure and Test Purposes (TSS&TP). It applies to the application independent card related terminal requirements defined in TS 101 200-4 [7]. The TSS&TP is in compliance with the relevant requirements and according to the relevant guidance given in ISO/IEC 9646-7 [11] and ETS 300 406 [9]. The set of tests described herein is intended to proof the compliance of a terminal with the standard TS 101 200-4 [7]. However the number of tests and the depth of testing is not sufficient for a product qualification test, especially as the standard TS 101 200-4 [7] does not define any application. For a product qualification at least the following tests should be added: - application tests: - each application implemented in the terminal shall be tested against the specifications for these applications. - User Card (UC) and Security Module (SM) interface test: - the interface between the user card and the security module shall be tested to verify the correct coding of all the used commands. The reaction of the terminal to every error code possible shall also be tested and be as specified for the application. - performance test: - to test whether the terminal complies with all the environmental conditions required and reacts within the specified time.
|
101 203-2
|
Identification card systems; Telecommunications IC cards and terminals; Test methods and conformance testing for EN 726-3; Part 2: Test Suite Structure and Test Purposes (TSS&TP) specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120302/01.02.01_60/ts_10120302v010201p.pdf
|
The present document provides the Test Suite Structure and Test Purposes (TSS&TP). It applies to the User Card (UC) defined in TS 101 206-3 [10] in compliance with the relevant requirements, and according to the relevant guidance given in ISO/IEC 9646-7 [14] and ETS 300 406 [11]. DISCLAIMER: The present document provides conformance tests for the TS 101 206-3 [10]. To guarantee usefulness of an IC card it might be necessary to perform additional implementation dependent tests regarding: - performance aspects; - quality of security concepts; - implementation dependent details not described in base standard. Tests for behaviour of the IUT in case of memory problems are mandatory but it is out of the scope of the present document how to create situations of failing memory. It might be possible to create a failing memory situation by either stressing memory long enough or by using an emulator.
|
101 203-1
|
Identification card systems; Telecommunications IC cards and terminals; Test methods and conformance testing for EN 726-3; Part 1: Implementation Conformance Statement (ICS) proforma specification
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101200_101299/10120301/01.02.01_60/ts_10120301v010201p.pdf
|
To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a telecommunication specification. Such a statement is called an Implementation Conformance Statement (ICS). The present document provides the ICS proforma for Application independent card requirements defined in TS 101 206-3 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and ETS 300 406 [2]. The supplier of an implementation which is claimed to conform to the present document is required to complete a copy of the ICS proforma provided in annex A and is required to provide the information necessary to identify both the supplier and the implementation.
|
101 197
|
Digital Video Broadcasting (DVB); DVB SimulCrypt; Head-end architecture and synchronization
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101197/01.02.01_60/ts_101197v010201p.pdf
|
The present document specifies the system architecture, timing relationships and messaging structures of DVB SimulCrypt. The components within the system architecture represent functional units. The boundaries between physical units are not required to match the boundaries between functional units. It is possible that the SimulCrypt Synchronizer (SCS) could be in the Multiplexer (MUX) or the SCS and MUX could be built independently. Neither architecture is mandated.
|
101 191
|
Digital Video Broadcasting (DVB); DVB mega-frame for Single Frequency Network (SFN) synchronization
|
TS
|
1.4.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101191/01.04.01_60/ts_101191v010401p.pdf
|
The present document specifies a mega-frame, including a Mega-frame Initialization Packet (MIP), which may be used for synchronization of Single Frequency Networks (SFN) as well as for the optional control of other important parameters in an SFN.
|
101 181
|
Digital cellular telecommunications system (Phase 2+) (GSM); Security Mechanisms for the SIM application toolkit; Stage 2 (GSM 03.48 version 7.0.1 Release 1998)
|
TS
|
7.0.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101181/07.00.01_60/ts_101181v070001p.pdf
|
The present document specifies the structure of the Secured Packets in a general format and in an implementation using the Short Message Service (SMS). Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in GSM 11.11 [5] and allows remote management of files on the Subscriber Identity Module (SIM) in conjunction with SMS and the SIM Data Download feature of GSM 11.14 [6]. The present document is applicable to the exchange of secured packets between an entity in a GSM PLMN and an entity in the SIM. Secured Packets contain application messages to which certain mechanisms according to GSM 02.48 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the GSM PLMN and on the SIM. The Sending/Receiving Entity in the GSM PLMN and the SIM are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
101 181
|
Digital cellular telecommunications system (Phase 2+) (GSM); Security Mechanisms for the SIM application toolkit; Stage 2 (GSM 03.48 version 6.2.0 Release 1997)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101181/06.02.00_60/ts_101181v060200p.pdf
|
The present document specifies the structure of the Secured Packets in a general format and in an implementation using the Short Message Service (SMS). Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in GSM 11.11 [5] and allows remote management of files on the Subscriber Identity Module (SIM) in conjunction with SMS and the SIM Data Download feature of GSM 11.14 [6]. The present document is applicable to the exchange of secured packets between an entity in a GSM PLMN and an entity in the SIM. Secured Packets contain application messages to which certain mechanisms according to GSM 02.48 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the GSM PLMN and on the SIM. The Sending/Receiving Entity in the GSM PLMN and the SIM are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
101 180
|
Digital cellular telecommunications system (Phase 2+) (GSM); Security mechanisms for the SIM application toolkit; Stage 1 (GSM 02.48 version 8.0.0 Release 1999)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101180/08.00.00_60/ts_101180v080000p.pdf
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48). The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
101 180
|
Digital cellular telecommunications system (Phase 2+) (GSM); Security mechanisms for the SIM application toolkit; Stage 1 (GSM 02.48 version 7.0.0 Release 1998)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101180/07.00.00_60/ts_101180v070000p.pdf
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48). The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
101 180
|
Digital cellular telecommunications system (Phase 2+) (GSM); Security mechanisms for the SIM application toolkit; Stage 1 (GSM 02.48 version 6.0.0 Release 97)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101180/06.00.00_60/ts_101180v060000p.pdf
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM. The security mechanisms which are specified are independent of applications. The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48). The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
101 162
|
Digital Video Broadcasting (DVB); Allocation of identifiers and codes for Digital Video Broadcasting (DVB) systems
|
TS
|
1.9.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101162/01.09.01_60/ts_101162v010901p.pdf
|
The present document defines codes, and identifiers (also referred to as code points) used in DVB systems. These codes are allocated by the DVB Project Office at the request of potential service providers and once allocated, become part of ETSI EN 300 468 [i.1] by reference. Further details can be obtained by contacting DVB Services Sàrl. DVB Services Sàrl c/o EBU L'Ancienne Route 17a CH-1218 Grand-Saconnex Switzerland Tel: +41 22 717 27 19 Email: info@dvbservices.com Web: http://www.dvbservices.com
|
101 158
|
Telecommunications security; Lawful Interception (LI); Requirements for network functions
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101158/01.03.01_60/ts_101158v010301p.pdf
|
The present document describes the general requirements of Network Operators (NWOs), Service Providers (SvPs) and Access Providers (APs) relating to the provision of lawful interception, with particular reference to the Handover Interface (HI). The provision of lawful interception is a requirement of national law, which is usually mandatory. From time to time, a NWO and/or SvP and/or AP will be required, according to a lawful authorization, to make available results of interception, relating to specific identities, to a specific Law Enforcement Agency (LEA). The general approach of the HI described in the present document is to be applied for every network technique, present or future, as long as the intercept requirements can be satisfied.
|
101 154
|
Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcast and Broadband Applications
|
TS
|
2.9.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101154/02.09.01_60/ts_101154v020901p.pdf
|
The present document provides implementation guidelines and conformance points for the use of audio-visual coding utilizing MPEG-2 Systems in satellite, cable and terrestrial broadcasting systems and in IP-based networks, and for the use of video coding for adaptive bitrate delivery over IP-based networks. The present document covers Standard Definition Television (SDTV), High Definition Television (HDTV), Plano Stereoscopic 3DTV and Ultra High Definition Television (UHDTV). More specifically, the present document covers the first and second phases of the DVB UHDTV specification, as well as the DVB Next Generation Audio specification.
|
101 154
|
Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream
|
TS
|
1.11.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101154/01.11.01_60/ts_101154v011101p.pdf
|
The present document provides implementation guidelines and conformance points for the use of audio-visual coding utilizing MPEG-2 Systems in satellite, cable and terrestrial broadcasting systems and in IP-based networks, and for the use of video coding for adaptive bitrate delivery over IP-based networks. The present document covers Standard Definition Television (SDTV), High Definition Television (HDTV), Plano Stereoscopic 3DTV and Ultra High Definition Television (UHDTV). More specifically, the present document covers the first and second phases of the DVB UHDTV specification, as well as the DVB Next Generation Audio specification.
|
101 139
|
Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2; Implementors guide
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101139/01.01.01_60/ts_101139v010101p.pdf
|
The present document is a compilation of reported defects, their resolutions and minor upgrades to the 2nd Edition of ETS 300 287-1 [1]. It includes all approved technical corrigenda and is intended to be an additional authoritative source of information for implementors to be read in conjunction with the ETS 300 287-1 [1] itself.
|
101 136
|
Satellite Earth Stations and Systems (SES); Guidance for general purpose earth stations transmitting in the 5,7 GHz to 30,0 GHz frequency bands towards geostationary satellites and not covered by other ETSI specifications or standards
|
TS
|
1.3.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101136/01.03.01_60/ts_101136v010301p.pdf
|
The present document is applicable to General Purpose Earth Stations (GPESs) not covered by other ETSI specifications or standards. The present document is intended to provide guidance for compliance of GPESs with the Radio and Telecommunications Terminal Equipment directive [1] requirements for the protection of other services from harmful interference. However, for some GPES, it is recognized that relaxation of the specified limits may be necessary and may be accepted, taking into account the particular environment of the GPES installation on a case-by-case basis. NOTE 1: More stringent specifications may be needed and required by satellite operators. NOTE 2: A GPES will be subject to a site clearance and a standard frequency co-ordination process. The present document is applicable to GPESs which have the following characteristics: • GPESs designed to transmit in all or part of any of the applicable frequency bands allocated to the Fixed Satellite Service (FSS),including feeder links for the Broadcast Satellite Service (BSS), as defined in table 1; and • GPESs designed to operate through geostationary satellites with a typical orbital separation as defined in table 1 away from any other geostationary satellite operating in the same frequency band and covering common areas; and • GPESs designed for operation at a fixed location; and • GPESs designed for attended operation. Table 1: Transmit frequency bands Transmit frequency bands Typical orbital separation 5,725 GHz - 7,075 GHz 3° 10,7 GHz - 11,7 GHz 3° 12,75 GHz - 14,50 GHz 3° 17,30 GHz - 18,40 GHz 3° 27,50 GHz - 30,00 GHz 2° A GPES typically comprises six main parts as defined in clause 3.1. The present document does not contain any recommendation or information about the method of modulation. The present document applies to the GPES with its various equipment, its ancillary equipment and its various terrestrial ports when operated within the boundary limits of the operational environmental profile (including the ranges of humidity, temperature and supply voltage) declared by the applicant. NOTE 3: Limits for spurious radiation from a GPES when transmitting multiple carriers simultaneously (multicarrier operation) have not been taken into consideration in the present document. ETSI ETSI TS 101 136 V1.3.1 (2001-06) 6
|
101 135
|
Transmission and Multiplexing (TM); High bit-rate Digital Subscriber Line (HDSL) transmission systems on metallic local lines; HDSL core specification and applications for combined ISDN-BA and 2 048 kbit/s transmission
|
TS
|
1.5.3
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101135/01.05.03_60/ts_101135v010503p.pdf
|
The present document describes a transmission technique called High bit-rate Digital Subscriber Line (HDSL), as a means for the transportation of several types of applications. The present document defines the requirements for the individual HDSL transmission system, the transmission performance, the HDSL maintenance requirements and procedures and the mapping of information from the dedicated applications. An individual HDSL transceiver system is a two wire bi-directional transceiver for metallic wires using the echo cancellation method. Three systems may be utilized, one transporting a bit rate of 784 kbit/s over each of three pairs used in parallel, a second with an increased bit rate of 1 168 kbit/s and two pairs in parallel only and a third with a more increased bit rate of 2 320 kbit/s on one pair only. The line codes of systems specified in the present document are 2B1Q (2 Binary 1 Quaternary) and CAP (Carrierless Amplitude Phase modulation). Systems using a CAP line code are covered in annex B. Annex C summarizes the Committee T1 recommendation for the frame structure of 1 544 kbit/s applications. Only one of the line codes has to be realized in a transmission system. The present document defines the common circuitry for combining and controlling one, two or three HDSL transceiver systems, depending on the bit rate of the transceiver system used, for the support of applications with a 2 048 kbit/s hierarchy. The common circuitry and the necessary number of HDSL transceiver systems form the HDSL core, which is independent from the different applications defined in the present document. The applications of HDSL are determined by the functionality of the mapping and interface part, some of which are defined as follows: - ISDN primary rate access digital section in accordance with ETS 300 233 [1]; - ONP leased line access D2048U based on ETS 300 246 [2] and ETS 300 247 [3]; - ONP leased line access D2048S based on ETS 300 418 [4] and ETS 300 419 [5]; - 2 Mbit/s access to the Synchronous Digital Hierarchy (SDH) via a TU-12. The HDSL core may be used for applications that are not restrictive to the access portion of the network but this is outside the scope of the present document. NOTE: If further applications are identified in future the present document may be enhanced to define the relevant interface and mapping requirements as far as these do not violate the specification of the HDSL core. Special applications of the HDSL core or part of the HDSL core can be: - fractional installation, which provides reduced access capability only by a reduced number of HDSL transceivers, to cater for an inexpensive system if the total capacity of 30 × 64 kbit/s is not needed; - partial operation, which is the persistent operation of the operable HDSL transceiver systems when others become inoperable; - fractional payload, e.g. H0-channel. The bit-rate at the application interface will also be 2 048 kbit/s in these applications, but not all the time slots in the ITU-T Recommendation G.704 [32] frame may be used, or there may be network specific interfaces used for these applications, the definition of which is outside the scope of the present document. The present document does not specify all the requirements for the implementation of NTU, LTU or REG. It serves only to describe the functionality needed. ETSI ETSI TS 101 135 V1.5.3 (2000-09) 13
|
101 116
|
Digital cellular telecommunications system (Phase 2+) (GSM); Specification of the 1.8 Volt Subscriber Identity Module - Mobile Equipment (SIM - ME) interface (GSM 11.18 version 7.0.1 Release 1998)
|
TS
|
7.0.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101116/07.00.01_60/ts_101116v070001p.pdf
|
The present document defines the aspects of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface which are based on 1.8V technology to be used in the Mobile Station (MS). It specifies the electrical and logical requirements necessary for the operation of the 1.8V SIM - ME interface where it differs from GSM 11.11 [1]. For all aspects of the SIM - ME interface which are not covered by the present document, GSM 11.11 [1] applies.
|
101 113
|
Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); Service description; Stage 1 (GSM 02.60 version 7.5.0 Release 1998)
|
TS
|
7.5.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101113/07.05.00_60/ts_101113v070500p.pdf
|
The present document defines the stage one description of the General Packet Radio Service (GPRS) on Global System for Mobile communications (GSM) networks. Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. The present document includes information applicable to network operators, service providers and terminal, switch and data base manufacturers. The present document contains the core requirements for the GPRS on GSM, which are sufficient to provide a complete service. The present document also documents some additional requirements which may be implemented (but do not have to be implemented). In addition, additional functionalities not documented in the present document may be implemented. The requirements of which are considered outside the scope of the present document and consequently outside the scope of the corresponding stage 2 and stage 3 TSs. This additional functionality may be on a network-wide basis, or particular to one or a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. The interface between the Mobile Station (MS) and any external applications are outside the scope of the present document. Charging principles are outside the scope of the present document, unless specific service requirements are stated. These requirements deal with the allocation of certain call charges to particular users. A later phase of GPRS may include interworking with circuit switched networks (e.g. PSTN, ISDN) and may emulate certain circuit switched services. These aspects are outside the scope of this version of the present document.
|
101 109
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Geographical Area Description (GAD) (GSM 03.32 version 6.0.0 Release 1997)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101109/06.00.00_60/ts_101109v060000p.pdf
|
The present document defines an intermediate universal Geographical Area Description which subscriber applications or GSM services can use and the network can convert into an equivalent radio coverage map. For GSM services which involve the use of an "area", it can be assumed that in the majority of cases the Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service Requester will not have direct access to network entities (e.g. BSC/BTS). The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document.
|
101 109
|
Digital cellular telecommunications system (Phase 2+) (GSM); Universal Geographical Area Description (GAD) (GSM 03.32 version 5.2.0 Release 1996)
|
TS
|
5.2.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101109/05.02.00_60/ts_101109v050200p.pdf
|
The present document defines an intermediate universal Geographical Area Description which subscriber applications or GSM services can use and the network can convert into an equivalent radio coverage map. For GSM services which involve the use of an "area", it can be assumed that in the majority of cases the Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service Requester will not have direct access to network entities (e.g. BSC/BTS). The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document.
|
101 108
|
Digital cellular telecommunications system (Phase 2+); Tandem Free Operation (TFO); Service Description; Stage 1 (GSM 02.53 version 8.0.1 Release 1999)
|
TS
|
8.0.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101108/08.00.01_60/ts_101108v080001p.pdf
|
The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid using two GSM speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements. In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
101 108
|
Digital cellular telecommunications system (Phase 2+) (GSM); Tandem Free Operation (TFO); Service Description; Stage 1 (GSM 02.53 version 7.0.1 Release 1998)
|
TS
|
7.0.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101108/07.00.01_60/ts_101108v070001p.pdf
|
The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid using two GSM speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements. In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
101 107
|
Digital cellular telecommunications system (Phase 2+) (GSM); Fraud Information Gathering System (FIGS); Service description - Stage 1 (GSM 02.31 version 7.1.1 Release 1998)
|
TS
|
7.1.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101107/07.01.01_60/ts_101107v070101p.pdf
|
The present document specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN. The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system. The present document enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills. HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
|
101 106
|
Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements (GSM 01.61 version 8.0.0 Release 1999)
|
TS
|
8.0.0
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101106/08.00.00_60/ts_101106v080000p.pdf
|
The present document constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60. The present document is intended to provide the ETSI Security Algorithms Group of Experts (SAGE) with the information it requires in order to design and deliver a technical specification for such an algorithm. The specification covers the intended use of the algorithm and use of the algorithm specification, technical requirements on the algorithm, requirements on the algorithm specification and test data, and quality assurance requirements on both the algorithm and its documentation. The specification also outlines the background to the production of the present document.
|
101 106
|
Digital cellular telecommunications system (Phase 2+) (GSM); General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements (GSM 01.61 version 6.0.1)
|
TS
|
6.0.1
|
http://www.etsi.org/deliver/etsi_ts/101100_101199/101106/06.00.01_60/ts_101106v060001p.pdf
|
The present document constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60. The present document is intended to provide the ETSI Security Algorithms Group of Experts (SAGE) with the information it requires in order to design and deliver a technical specification for such an algorithm. The specification covers the intended use of the algorithm and use of the algorithm specification, technical requirements on the algorithm, requirements on the algorithm specification and test data, and quality assurance requirements on both the algorithm and its documentation. The specification also outlines the background to the production of the present document.
|
101 064-2
|
Telecommunications Management Network (TMN); Information models and protocols for the management and control of the Asynchronous Transfer Mode (ATM) switching network element; Part 2: Enhanced broadband switch management
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10106402/01.01.01_60/ts_10106402v010101p.pdf
|
The present document specifies the Q3 interface between an ATM switch with enhanced functionality and the Telecommunications Management Network (TMN). The interface specified is that between TMN Network Elements or Q-Adapters which interface to TMN Operations Systems (OSs) without mediation and between OSs and Mediation Devices, as defined in ITU-T Recommendation M.3010 [5]. The scope of the present document includes the management of switched VPs as defined in ITU-T Recommendations Q.2766.1 [10] and Q.2934 [12] and of soft PVCs as defined in ITU-T Recommendation Q.2767.1 [11]. The associated management for customer administration and for call routing is also within the scope of the present document. The object model in the present document is based on and extends the model in ITU-T Recommendation Q.824.6 [9]. The definition of the functionality of TMN Operations Systems is outside the scope of the present document. Security management is also outside the scope of the present document. Existing protocols are used where possible, and the focus of the work is on defining the object model.
|
101 059
|
Corporate Telecommunication Networks (CN); CEPT signalling systems (L1 and L2) for analogue inter-PABX lines
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101059/01.01.01_60/ts_101059v010101p.pdf
|
The present document collects together (as annexes) 10 former CEPT Recommendations on the subject of "CEPT signalling systems (L1 and L2) for analogue inter-PABX lines".
|
101 053-7
|
Rules for the management of the TETRA standard encryption algorithms; Part 7: TEA7
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105307/01.02.01_60/ts_10105307v010201p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA7. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA7 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives’ section of part 1 of the specification has been published as ETSI TS 104 053-2 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA7 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA7 (ETSI, ETSI Technical Committee TCCE, TEA7 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA7 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA7 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA7 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-6
|
Rules for the management of the TETRA standard encryption algorithms; Part 6: TEA6
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105306/01.02.01_60/ts_10105306v010201p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA6. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA6 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-2 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA6 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA6 (ETSI, ETSI Technical Committee TCCE, TEA6 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA6 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA6 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA6 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-5
|
Rules for the management of the TETRA standard encryption algorithms; Part 5: TEA5
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105305/01.01.01_60/ts_10105305v010101p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard encryption algorithm TEA5. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA5 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to licensing organizations to manufacture, possess, install, repair, hold, use and destroy equipment and components containing the TEA5 algorithm and to delivering parts 1, 2 and 3 of the TEA5 specifications. Parts 1 and 2 of the specification are confidential. Part 3 of the specification is not confidential and can be obtained directly from the TEA5 Custodian (see clause 7.2). There are no restrictions on the distribution of this part of the specification. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA5 (ETSI, ETSI Technical Committee TETRA and Critical Communications Evolution, TEA5 Custodian and approved recipients) together with the relationships and interactions between them. Clause 5 is concerned with the rules for the use of TEA5. This clause is supplemented by annex H, which provides an exemplary list of the states and territories in which a User may become an approved recipient. Clause 6 describes the types of licence that may be requested. The procedures for delivering TEA5 specifications to approved recipients are defined in clause 7. This clause is supplemented by annex A, which specifies the items that are to be delivered. Clause 8 is concerned with the criteria for approving an organization for receipt of TEA5 deliverables and with the responsibilities of an approved recipient. This clause is supplemented by annexes B to G which contain the Confidentiality and Restricted Usage Undertakings to be signed by the TEA5 Custodian and approved recipients of TEA5 specifications and/or equipment and components containing TEA5. Clause 9 is concerned with the appointment and responsibilities of the TEA5 Custodian.
|
101 053-4
|
Rules for the management of the TETRA standard encryption algorithms; Part 4: TEA4
|
TS
|
3.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105304/03.02.01_60/ts_10105304v030201p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA4. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA4 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 of the specification are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA4 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA4 (ETSI, ETSI Technical Committee TCCE, TEA4 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA4 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA4 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA4 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-4
|
Rules for the management of the TETRA standard encryption algorithms; Part 4: TEA4
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105304/02.01.01_60/ts_10105304v020101p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA4. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA4 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 of the specification are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA4 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA4 (ETSI, ETSI Technical Committee TCCE, TEA4 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA4 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA4 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA4 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-3
|
Rules for the management of the TETRA standard encryption algorithms; Part 3: TEA3
|
TS
|
3.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105303/03.02.01_60/ts_10105303v030201p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA3. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA3 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA3 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA3 (ETSI, ETSI Technical Committee TCCE, TEA3 Custodian and approved recipients(beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA3 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA3 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA3 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-3
|
Rules for the management of the TETRA standard encryption algorithms; Part 3: TEA3
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105303/02.01.01_60/ts_10105303v020101p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA3. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA3 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA3 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA3 (ETSI, ETSI Technical Committee TCCE, TEA3 Custodian and approved recipients(beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA3 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA3 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA3 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-2
|
Rules for the management of the TETRA standard encryption algorithms; Part 2: TEA2
|
TS
|
3.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105302/03.01.01_60/ts_10105302v030101p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard encryption algorithm TEA2. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA2 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to licensing organizations to manufacture, possess, install, repair, hold, use and destroy equipment and components containing the TEA2 algorithm and to delivering parts 1, 2 and 3 of the TEA2 specifications. Parts 1 and 2 of the specification are confidential. Part 3 of the specification is not confidential and can be obtained directly from the TEA2 Custodian (see clause 7.2). There are no restrictions on the distribution of this part of the specification. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA2 (ETSI, ETSI Technical Committee TETRA and Critical Communications Evolution, TEA2 Custodian and approved recipients) together with the relationships and interactions between them. Clause 5 is concerned with the rules for the use of TEA2. This clause is supplemented by annex H, which provides an exemplary list of the states and territories in which a User may become an approved recipient. Clause 6 describes the types of licence that may be requested. The procedures for delivering TEA2 specifications to approved recipients are defined in clause 7. This clause is supplemented by annex A, which specifies the items that are to be delivered. Clause 8 is concerned with the criteria for approving an organization for receipt of TEA2 deliverables and with the responsibilities of an approved recipient. This clause is supplemented by annexes B to G which contain the Confidentiality and Restricted Usage Undertakings to be signed by the TEA2 Custodian and approved recipients of TEA2 specifications and/or equipment and components containing TEA2. Clause 9 is concerned with the appointment and responsibilities of the TEA2 Custodian.
|
101 053-2
|
Rules for the management of the TETRA standard encryption algorithms; Part 2: TEA2
|
TS
|
2.5.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105302/02.05.01_60/ts_10105302v020501p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard encryption algorithm TEA2. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA2 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to licensing organizations to manufacture, possess, install, repair, hold, use and destroy equipment and components containing the TEA2 algorithm and to delivering parts 1, 2 and 3 of the TEA2 specifications. Parts 1 and 2 of the specification are confidential. Part 3 of the specification is not confidential and can be obtained directly from the TEA2 Custodian (see clause 7.2). There are no restrictions on the distribution of this part of the specification. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA2 (ETSI, ETSI Technical Committee TETRA and Critical Communications Evolution, TEA2 Custodian and approved recipients) together with the relationships and interactions between them. Clause 5 is concerned with the rules for the use of TEA2. This clause is supplemented by annex H, which provides an exemplary list of the states and territories in which a User may become an approved recipient. Clause 6 describes the types of licence that may be requested. The procedures for delivering TEA2 specifications to approved recipients are defined in clause 7. This clause is supplemented by annex A, which specifies the items that are to be delivered. Clause 8 is concerned with the criteria for approving an organization for receipt of TEA2 deliverables and with the responsibilities of an approved recipient. This clause is supplemented by annexes B to G which contain the Confidentiality and Restricted Usage Undertakings to be signed by the TEA2 Custodian and approved recipients of TEA2 specifications and/or equipment and components containing TEA2. Clause 9 is concerned with the appointment and responsibilities of the TEA2 Custodian.
|
101 053-1
|
Rules for the management of the TETRA standard encryption algorithms; Part 1: TEA1
|
TS
|
3.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105301/03.02.01_60/ts_10105301v030201p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA1. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA1 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA1 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA1 (ETSI, ETSI Technical Committee TCCE, TEA1 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA1 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA1 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA1 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 053-1
|
Rules for the management of the TETRA standard encryption algorithms; Part 1: TEA1
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105301/02.01.01_60/ts_10105301v020101p.pdf
|
The present document has been designed to specify the rules for the management of the TETRA standard encryption algorithm TEA1. This algorithm is intended for air interface encryption in TETRA products. The specification for TEA1 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-1 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TEA1 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TEA1 (ETSI, ETSI Technical Committee TCCE, TEA1 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TEA1 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TEA1 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TEA1 Custodian. Clause 8 describes an overview of the algorithm and its dimensions.
|
101 052-2
|
Rules for the management of the TETRA standard authentication and key management algorithm sets; Part 2: TAA2
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105202/01.02.01_60/ts_10105202v010201p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard authentication and key management algorithm set TAA2. This algorithm set is intended for air interface security in TETRA products. The specification for TAA2 consists of the following three parts: Part 1: Algorithm specifications. Part 2: Design conformance test data. Part 3: Algorithms input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential for each of the algorithms. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-4 [i.1]. Part 3 of of the specification is not confidential and can be obtained directly from the TAA2 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specification. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TAA2 (ETSI, ETSI Technical Committee TCCE, TAA2 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TAA2 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TAA2 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TAA2 Custodian. Clause 8 describes an overview of the algorithms.
|
101 052-1
|
Rules for the management of the TETRA standard authentication and key management algorithm sets; Part 1: TAA1
|
TS
|
3.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/10105201/03.02.01_60/ts_10105201v030201p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard authentication and key management algorithm set TAA1. This algorithm set is intended for air interface security in TETRA products. The specification for TAA1 consists of the following three parts: Part 1: Algorithm specification. Part 2: Design conformance test data. Part 3: Algorithm input/output test data. The procedures described in the present document apply to parts 1 and 2 of the specification. Parts 1 and 2 are confidential for each of the algorithms. The algorithm primitives' section of part 1 of the specification has been published as ETSI TS 104 053-3 [i.1]. Part 3 of the specification is not confidential and can be obtained directly from the TAA1 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specification. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TAA1 (ETSI, ETSI Technical Committee TCCE, TAA1 Custodian and approved recipients (beneficiaries)) together with the relationships and interactions between them. The procedures for delivering TAA1 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TAA1 and with the responsibilities of an approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TAA1 Custodian. Clause 8 describes an overview of the algorithms.
|
101 052
|
Rules for the management of the TETRA standard authentication and key management algorithm set TAA1
|
TS
|
2.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101052/02.01.01_60/ts_101052v020101p.pdf
|
The purpose of the present document is to specify the rules for the management of the TETRA standard authentication and key management algorithm set TAA1. This algorithm set is intended for air interface security in TETRA products. The specification for TAA1 consists of the following three parts: Part 1: Algorithm specification; Part 2: Design conformance test data; Part 3: Algorithm input/output test data. The procedures described in the present document apply to Parts 1 and 2 of the specifications. Parts 1 and 2 are confidential for each of the algorithms. Part 3 of each of the specifications is not confidential and can be obtained directly from the TAA1 Custodian (see clause 5.2). There are no restrictions on the distribution of this part of the specifications. The management structure is defined in clause 4. This structure is defined in terms of the principals involved in the management of TAA1 (ETSI, ETSI Technical Committee TCCE, TAA1 Custodian and approved recipients) together with the relationships and interactions between them. The procedures for delivering TAA1 to approved recipients are defined in clause 5. This clause is supplemented by annex A which specifies the items which are to be delivered. Clause 6 is concerned with the criteria for approving an organization for receipt of TAA1 and with the responsibilities of an approved recipient. This clause is supplemented by annex B which contains a Confidentiality and Restricted Usage Undertaking to be signed by each approved recipient. Clause 7 is concerned with the appointment and responsibilities of the TAA1 Custodian.
|
101 046
|
Digital cellular telecommunications system (Phase 2+) (GSM); Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification (GSM 09.78 version 7.1.0 Release 1998)
|
TS
|
7.1.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101046/07.01.00_60/ts_101046v070100p.pdf
|
The present document specifies the CAMEL Application Part (CAP) supporting the second phase of the network feature Customised Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the CS1 Core INAP as specified by ETS 300 374-1 [13]. Descriptions and definitions provided by ETS 300 374-1 [13] are directly referenced by the present document in case no additions or clarifications are needed for the use in the CAP.
|
101 046
|
Digital cellular telecommunications system (Phase 2+) (GSM); Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification (GSM 09.78 version 6.5.0 Release 1997)
|
TS
|
6.5.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101046/06.05.00_60/ts_101046v060500p.pdf
|
The present document specifies the CAMEL Application Part (CAP) supporting the second phase of the network feature Customised Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the CS1 Core INAP as specified by ETS 300 374-1 [13]. Descriptions and definitions provided by ETS 300 374-1 [13] are directly referenced by the present document in case no additions or clarifications are needed for the use in the CAP.
|
101 046
|
Digital cellular telecommunications system (Phase 2+) (GSM); Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification (GSM 09.78 version 5.7.0 Release 1996)
|
TS
|
5.7.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101046/05.07.00_60/ts_101046v050700p.pdf
|
The present document specifies the CAMEL Application Part (CAP) supporting the second phase of the network feature Customised Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the CS1 Core INAP as specified by ETS 300 374-1 [13]. Descriptions and definitions provided by ETS 300 374-1 [13] are directly referenced by the present document in case no additions or clarifications are needed for the use in the CAP.
|
101 045
|
Digital cellular telecommunications system (Phase 2+) (GSM); Support of Optimal Routeing (SOR); Technical realisation (GSM 03.79 version 7.3.0 Release 1998)
|
TS
|
7.3.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101045/07.03.00_60/ts_101045v070300p.pdf
|
The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides: - as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN; - a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber; - a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above. OR of a call is permitted only if all entities involved in handling the call support OR. Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases.
|
101 045
|
Digital cellular telecommunications system (Phase 2+) (GSM); Support of Optimal Routeing (SOR); Technical realisation (GSM 03.79 version 6.3.0 Release 1997)
|
TS
|
6.3.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101045/06.03.00_60/ts_101045v060300p.pdf
|
The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides: - as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN; - a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber; - a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above. OR of a call is permitted only if all entities involved in handling the call support OR. Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases.
|
101 045
|
Digital cellular telecommunications system (Phase 2+) (GSM); Support of Optimal Routeing (SOR); Technical realisation (GSM 03.79 version 5.5.0 Release 1996)
|
TS
|
5.5.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101045/05.05.00_60/ts_101045v050500p.pdf
|
The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides: - as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN; - a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber; - a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above. OR of a call is permitted only if all entities involved in handling the call support OR. Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases.
|
101 044
|
Digital cellular telecommunications system (Phase 2+) (GSM); Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2 (GSM 03.78 version 5.8.0 Release 1996)
|
TS
|
5.8.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101044/05.08.00_60/ts_101044v050800p.pdf
|
The present document specifies the stage 2 description for the first phase (see GSM 02.78 [2]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized GSM services even when roaming outside the HPLMN. The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN. In the present document, the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN. The regulatory environment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinct entities. In the first phase the CAMEL feature supports: - mobile originated and forwarded calls; - mobile terminating calls; - any time interrogation; - suppression of announcements; Note that CAMEL is not applicable to Emergency Setup (TS 12), i.e., in case an Emergency call has been requested the gsmSSF shall not be invoked. The mechanism described in the present document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator specific services. Any user procedures for the control of operator specific services are outside the scope of the present document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or to the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN. The specification of operator specific services in HPLMN is outside the scope of the present document.
|
101 043
|
Digital cellular telecommunications system (Phase 2+) (GSM); Basic call handling; Technical realization (GSM 03.18 version 5.6.0 Release 1996)
|
TS
|
5.6.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101043/05.06.00_60/ts_101043v050600p.pdf
|
This Technical Specification (TS) specifies the technical realization of the handling of calls originated by a GSM mobile subscriber and calls directed to a GSM mobile subscriber, up to the point where the call is established. Normal release of the call after establishment is also specified. The handling of DTMF signalling and Off-Air Call setup (OACSU) are not described in this specification. The details of the effects of GSM supplementary services on the handling of a call are described in the relevant GSM 03.8x and GSM 03.9x series of specifications. The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling, but is required for both CAMEL (GSM 03.78 [5]) and optimal routeing (GSM 03.79 [6]). The use of the Provide Subscriber Information message flow is shown in GSM 03.78 [5] and GSM 03.79 [6]. The specification of the handling of data calls re-routed to a SIWFS is described in GSM 03.54 [4]. The logical separation of the MSC and VLR (shown in clauses 4, 5 & 7), and the messages transferred between them (described in clause 8) are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour. If there is any conflict between this specification and the corresponding stage 3 specifications (ETS 300 557 [14], ETS 300 590 [16] and ETS 300 599 [17]), the stage 3 specification shall prevail.
|
101 038
|
Digital cellular telecommunications system (Phase 2+) (GSM); High Speed Circuit Switched Data (HSCSD) - Stage 2 (GSM 03.34 version 7.0.0 Release 1998)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101038/07.00.00_60/ts_101038v070000p.pdf
|
The present document contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on GSM. In analogy with CCITT Recommendations I.130 [6] (refer to annex A) and with reference of CCITT Recommendations VI.1 Q.65 [7] (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows. Stage 2 identifies the functional capabilities and information flows needed to support the service as described in High Speed Circuit Switched Data (HSCSD) - Stage 1, GSM 02.34 [9]. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
|
101 038
|
Digital cellular telecommunications system (Phase 2+) (GSM); High Speed Circuit Switched Data (HSCSD); Stage 2 (GSM 03.34 version 6.0.0 Release 1997 )
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101038/06.00.00_60/ts_101038v060000p.pdf
|
The present document contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on GSM. In analogy with CCITT Recommendations I.130 [6] (refer to annex A) and with reference of CCITT Recommendations VI.1 Q.65 [7] (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows. Stage 2 identifies the functional capabilities and information flows needed to support the service as described in High Speed Circuit Switched Data (HSCSD) - Stage 1, GSM 02.34 [9]. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
|
101 038
|
Digital cellular telecommunications system (Phase 2+) (GSM); High Speed Circuit Switched Data (HSCSD) - Stage 2 (GSM 03.34 version 5.2.0 Release 1996 )
|
TS
|
5.2.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101038/05.02.00_60/ts_101038v050200p.pdf
|
The present document contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on GSM. In analogy with CCITT Recommendations I.130 [6] (refer to annex A) and with reference of CCITT Recommendations VI.1 Q.65 [7] (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows. Stage 2 identifies the functional capabilities and information flows needed to support the service as described in High Speed Circuit Switched Data (HSCSD) - Stage 1, GSM 02.34 [9]. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
|
101 032
|
Digital cellular telecommunications system (Phase 2+) (GSM); Compression algorithm for text messaging services (GSM 03.42 version 7.1.1 Release 1998)
|
TS
|
7.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101032/07.01.01_60/ts_101032v070101p.pdf
|
The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
|
101 032
|
Digital cellular telecommunications system (Phase 2+) (GSM); Compression algorithm for text messaging services (GSM 03.42 version 6.0.0 Release 1997)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101032/06.00.00_60/ts_101032v060000p.pdf
|
The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
|
101 032
|
Digital cellular telecommunications system (Phase 2+) (GSM); Compression algorithm for text messaging services (GSM 03.42 version 5.2.0)
|
TS
|
5.2.0
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101032/05.02.00_60/ts_101032v050200p.pdf
|
The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
|
101 012
|
Transmission and Multiplexing (TM); Broadband Access Digital Section and NT functional requirements
|
TS
|
1.2.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101012/01.02.01_60/ts_101012v010201p.pdf
|
The present document defines the functional requirements for an "ATM over xDSL" Broadband Access Digital Section (ADS), between the UNI interface at T/S reference point and the Access Network End System at the VB1 reference point, operated over an xDSL connection between an xDSL based Broadband Network Termination and an xDSL based Broadband Line Termination, both these elements being essential constituents of the B-ADS. The definition of B-ADS functional characteristics and protocols should enable proper interworking of the B-NT with: a) the Customer Premises Network (B-NT2 or TE) on the customer side; b) the B-LT and more generally the Access Network End System on the other side, for the provision of ATM connectivity. At the same time, the specified operational and management requirements will enable proper interworking of the B-ADS elements with the remaining Access Network elements and with the Service Node, as well as proper B-ADS management. The present document also identifies proper protocols and relevant supporting facilities for the control and management of the Customer Premises Network.
|
101 010
|
Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); Network protection schemes; Interworking: rings and other schemes
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101010/01.01.01_60/ts_101010v010101p.pdf
|
The present document describes the criteria, principles, objectives, requirements and architectures of protection interworking between multiplex section shared protected rings, multiplex section linear protection, and Higher Order/lower Order (HO/LO) Virtual Container (VC) trail and subnetwork connection protection schemes. The SDH protection interworking scenarios between the same and different protection schemes are described. The network objectives, architectures, functional modelling and operations of the various SDH protection schemes are described in TS 101 009 [1]. The protection switching initiation criteria and the Automatic Protection Switching (APS) protocols of the various SDH protection schemes are specified in ETS 300 746 [2].
|
101 009
|
Transmission and Multiplexing (TM); Synchronous Digital Hierarchy (SDH); Network protection schemes; Types and characteristics
|
TS
|
1.1.1
|
http://www.etsi.org/deliver/etsi_ts/101000_101099/101009/01.01.01_60/ts_101009v010101p.pdf
|
The present document describes the functional requirements and classification of Synchronous Digital Hierarchy (SDH) protection schemes, namely SDH multiplex section trail shared protection ring, multiplex section trail dedicated protection ring, multiplex section trail linear protection, and Lower Order/Higher Order (LO/HO) Virtual Container (VC) trail and Sub-Network Connection (SNC) protection schemes. The various SDH protection schemes are specified in terms of their network objectives, network architectures, functional modelling and network operations.
|
100 977
|
Digital cellular telecommunications system (Phase 2+) (GSM); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface (GSM 11.11 version 6.3.0 Release 1997)
|
TS
|
6.3.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100977/06.03.00_60/ts_100977v060300p.pdf
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in the GSM 02.17 [6]. The present document defines: - the requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols; - the model which shall be used as a basis for the design of the logical structure of the SIM; - the security features; - the interface functions; - the commands; - the contents of the files required for the GSM application; - the application protocol. Unless otherwise stated, references to GSM also apply to DCS 1800. The present document does not specify any aspects related to the administrative management phase. Any internal technical reallocation of either the SIM or the ME are only specified where these reflect over the interface. It does not specify any of the security algorithms which may be used. The present document defines the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification.
|
100 976
|
Digital cellular telecommunications system (Phase 2+) (GSM); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) (GSM 09.07 version 7.2.0 Release 1998)
|
TS
|
7.2.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100976/07.02.00_60/ts_100976v070200p.pdf
|
The present document identifies the Mobile-services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between: a) PLMN and PSTN b) PLMN and ISDN It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D-channel signalling. Within the present document, the requirements for voice and non-voice (data) calls are considered separately.
|
100 976
|
Digital cellular telecommunications system (Phase 2+) (GSM); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) (GSM 09.07 version 6.2.0 Release 1997)
|
TS
|
6.2.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100976/06.02.00_60/ts_100976v060200p.pdf
|
The present document identifies the Mobile-services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between: a) PLMN and PSTN b) PLMN and ISDN It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D-channel signalling. Within the present document, the requirements for voice and non-voice (data) calls are considered separately.
|
100 975
|
Digital cellular telecommunications system (Phase 2+) (GSM); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services (GSM 09.06 version 7.0.0 Release 1998)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100975/07.00.00_60/ts_100975v070000p.pdf
|
The present document identifies the Interworking Functions (IWF's) and requirements for the interworking between a GSM PLMN and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet services in GSM PLMNs. In the GSM PLMN context the packet services are associated with bearer services and are described in GSM 02.02. The generally defined GSM PLMN user-network access as defined in the respective GSM specifications (see references) forms the basis for defining the particularities for the provision of packet services to the GSM PLMN subscribers. Network internal interfaces for the support of packet services in the pan-European ISDN are defined in ETSI standards, which are also taken as a basis. User-network access and network internal interfaces are defined to provide the packet services.
|
100 975
|
Digital cellular telecommunications system (Phase 2+) (GSM); Interworking between a Public Land Mobile Network (PLMN)and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services (GSM 09.06 version 6.0.0 Release 1997)
|
TS
|
6.0.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100975/06.00.00_60/ts_100975v060000p.pdf
|
The present document identifies the Interworking Functions (IWF's) and requirements for the interworking between a GSM PLMN and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet services in GSM PLMNs. In the GSM PLMN context the packet services are associated with bearer services and are described in GSM 02.02. The generally defined GSM PLMN user-network access as defined in the respective GSM specifications (see references) forms the basis for defining the particularities for the provision of packet services to the GSM PLMN subscribers. Network internal interfaces for the support of packet services in the pan-European ISDN are defined in ETSI standards, which are also taken as a basis. User-network access and network internal interfaces are defined to provide the packet services.
|
100 956
|
Digital cellular telecommunications system (Phase 2+) (GSM); Call Barring (CB) supplementary services; Stage 3 (GSM 04.88 version 7.0.0 Release 1998)
|
TS
|
7.0.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100956/07.00.00_60/ts_100956v070000p.pdf
|
The present document specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call restriction supplementary services and are described in this specification: - Barring of outgoing calls (clause 1): - Barring of all outgoing calls (BAOC) (Barring program 1); - Barring of outgoing international calls (BOIC) (Barring program 2); - Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3). - Barring of incoming calls (clause 2): - Barring of all incoming calls (BAIC) (Barring program 1); - Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2).
|
100 956
|
Digital cellular telecommunications system (Phase 2+) (GSM); Call Barring (CB) supplementary services; Stage 3 (GSM 04.88 version 6.0.1 Release 1997)
|
TS
|
6.0.1
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100956/06.00.01_60/ts_100956v060001p.pdf
|
The present document specifies the procedures used at the radio interface (reference point Um as defined in GSM 04.02) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. In GSM 04.10 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. GSM 04.80 specifies the formats and coding for the supplementary services. Definitions and descriptions of supplementary services are given in GSM 02.04, GSM 02.8x and GSM 02.9x-series. Technical realization of supplementary services is described in GSM 03.11, GSM 03.8x and GSM 03.9x-series. The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in GSM 04.07 and GSM 04.08. The following supplementary services belong to the call restriction supplementary services and are described in this specification: - Barring of outgoing calls (clause 1): - Barring of all outgoing calls (BAOC) (Barring program 1); - Barring of outgoing international calls (BOIC) (Barring program 2); - Barring of outgoing international calls EXCEPT those directed to the home PLMN country (BOIC-exHC) (Barring program 3). - Barring of incoming calls (clause 2): - Barring of all incoming calls (BAIC) (Barring program 1); - Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) (Barring program 2).
|
100 949
|
Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 8.1.0 Release 1999)
|
TS
|
8.1.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100949/08.01.00_60/ts_100949v080100p.pdf
|
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface.
|
100 949
|
Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 7.2.0 Release 1998)
|
TS
|
7.2.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100949/07.02.00_60/ts_100949v070200p.pdf
|
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface.
|
100 949
|
Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 6.3.0 Release 1997)
|
TS
|
6.3.0
|
http://www.etsi.org/deliver/etsi_ts/100900_100999/100949/06.03.00_60/ts_100949v060300p.pdf
|
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.