id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 560 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 4.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-401.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 4.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-440.zip | |
29.998-04-1 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping | TR | 4.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-420.zip | The present document investigates how the OSA Call Control Interface Class methods defined in 3GPP TS 29.198-4 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
29.998-05-1 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-400.zip | The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
29.998-05-4 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-400.zip | The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations, within the context of SMS. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
30.902 | Guidelines for the modification of the Mobile Application Part (MAP) in Phase 2+ | TR | 4.0.2 | C4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.902/30902-402.zip | After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects. |
29.414 | Core network Nb data transport and transport signalling | TS | 4.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-450.zip | |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 4.17.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-4h0.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 4.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-421.zip | |
29.998-06 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User Location and User Status Service Mapping to MAP | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06/29998-06-400.zip | The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
29.998-08 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-400.zip | The present document investigates how the OSA Data Session Control Interface Class methods defined in 3GPP TS 29.198-8 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 4.17.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-4h0.zip | |
31.110 | Numbering system for telecommunication IC card applications | TS | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.110/31110-410.zip | The present document describes the numbering system for Application IDentifiers (AID) for 3G telecommunication Integrated Circuits (IC) card applications.
The numbering system described in the present document provides a means for an application and related services offered by a provider to identify if a given card contains the elements required by its application and related services.
An AID is used to address an application in the card. It consists of a Registered application provider IDentifier (RID) and a Proprietary application Identifier eXtension (PIX).
The present document describes the coding of the PIX. |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-400.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-400.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 4.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-421.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 4.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-421.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-410.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 4.14.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-4e1.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 4.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-480.zip | |
32.200 | Telecommunication management; Charging management; Charging principles | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.200/32200-450.zip | The present document describes the principles of charging and billing for the provision of service and services by a 3G‑system.
The present document elaborates on the charging requirements described in the Charging Principles in 3GPP TS 22.101 [1]. It allows the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and references these where appropriate.
The Charging Data Records (CDRs) generated by the network elements of the 3G network, are required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network operators and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as archival information in dealing with customer service and billing complaints.
In addition to the information collected from network elements, network management functions are required for the administration of charging data.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in the present document which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs used in the Circuit Switched (CS) domain are specified in document3GPP TS 32.205 [5]. The CDRs content and transport within the PS domain are described in3GPP TS 32.215 [6] document, while CDRs used for application services are defined in document3GPP TS 32.235 [17].
The relationship among these charging specifications is illustrated in figure 1.1.
Figure 1.1: Charging Documents Structure
For the purpose of the present document, the charging data is considered to be generated and collected by charging functions in the network elements.
Charging data fields are collected and CDRs generated by the network elements for transfer to the billing system. For the packet switched domain, the CDRs are first sent to the Charging Gateway Function (CGF) for storage and further processing. The CGF may be a distinct network element or may be integrated into the packet domain network elements themselves.
The objectives of the present document are:
- to describe principles of charging in a 3G network;
- to provide a description of the charging architecture; and
- to provide the descriptions of events and triggers for the generation of Charging Data Records (CDRs). |
32.205 | Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain | TS | 4.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.205/32205-480.zip | The GSM and UMTS PLMNs support a wide range of circuit based services. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in TS 32.200 [22] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node.
The present document specifies the structure and the contents of the CDRs that are collected by the relevant network elements for circuit switched services in 2G (GSM) and 3G (UMTS) networks. It also defines the syntax for the transfer of these CDRs from the collecting nodes to billing post-processing systems using standard file transfer protocols.
The CDRs content and transport within the PS domain are described in TS 32.215 [23] document, while CDRs used for application services are defined in document TS 32.235 [24].
The relationship among these charging specifications is illustrated in figure 1.
Figure 1: Charging Documents Structure
The interface definitions of GSM 12.05 are maintained for 2G, in order to assure backward compatibility to earlier GSM releases.
The charging architecture and principles that the present document is based on are specified in TS 32.200 [22].
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella TS 32.200 [22]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential. |
32.215 | Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain | TS | 4.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.215/32215-490.zip | The GSM and UMTS PLMN support a wide range of packet based services by means of the General Packet Radio Service (GPRS), as defined in 3GPP TS 22.060 [1] and 3GPP TS 23.060 [2]. In order to enable operators the ability to provide a commercially viable service, there is a need to provide charging functions. For GPRS these functions include the generation of Charging Data Records (CDRs) by the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN) as well as the transport of these CDRs to a Billing System (BS) through a Charging Gateway Function (CGF).
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in document TS 32.200 [3] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs content and transport within the PS domain are described in the present document. The CDRs used in the Circuit Switched (CS) domain are specified in document TS 32.205 [4] while CDRs used for application services are defined in document TS 32.235 [5]. The present document structure is depicted in figure 1.
Figure 1: Charging Documents Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella document [3]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential. |
32.225 | Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS) | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.225/32225-000.zip | The present document covers both online and offline charging for the IMS. For clarity, the terms Offline Charging and Online charging as applied to the IMS are defined here in clause 3. These definitions are the same as listed in TS 32.200 [2].
The IMS charging architecture details, requirements, definitions and principles are listed in TS 32.200 [2] and therefore are not repeated here.
In the present document the charging data triggers, message content and format are specified along with the transport of these messages using the Diameter protocol. Details about charging message flows and the definitions of the Diameter AVPs are also included in the present document. This information is divided into two main clauses: Online Charging and Offline Charging. |
32.235 | Telecommunication management; Charging management; Charging data description for application services | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.235/32235-460.zip | The present document is part of a series of documents specifying charging functionality in UMTS network with application services. The UMTS core network charging principles are specified in document TS 32.200 [2], which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The document structure is defined in figure 1. The CDR content and transport for application services are described in the present document especially for MMS. As the basis and reference for this work is taken the functional description of the MMS specified for stage 1 in TS 22.140[3] and stage 2 in TS 23.140 [4].
Figure 1 Charging Document Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common are defined in the 3GPP Vocabulary [1] and specialised to charging in UMTS domains or subsystems are provided in the umbrella document [2]. |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 4.1.2 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-412.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 4.0.2 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-402.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 4.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-401.zip | |
32.111-4 | Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-460.zip | The present document defines the alarm integration reference point for the CMIP solution set. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.111-2 (V6.3.X). |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-420.zip | |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-450.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [5]).
This Solution Set specification is related to 3GPP TS 32.302. |
32.304 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.304/32304-421.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.302 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Notification Management over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.302 V6.2.X. |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-460.zip | The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.111-2 V7.1.X. |
32.102 | Telecommunication management; Architecture | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-450.zip | |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-410.zip | |
32.403 | Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM | TS | 4.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-4a0.zip | The present document describes the measurements for UMTS and combined UMTS/GSM.
TS 32.401 [12] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements. |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-430.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-410.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-400.zip | |
32.603 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.603/32603-431.zip | The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types and methods.
This Solution Set specification is related to 3G TS 32.602 V8.1.X. |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-450.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM, UMTS and LTE networks. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in the Network Elements (NEs) and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The basic Performance Management concept that the present document is built upon is described in clause 4.
The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
- TS 52.402 for GSM systems;
- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
- TS 32.409 for IMS networks;
- TS 32.425 for E-UTRAN;
- TS 32.426 for EPC;
- TS 32.452 for Home Node B (HNB) Subsystem (HNS);
- TS 32.453 for Home enhanced Node B (HeNB) Subsystem (HeNS);
- TS 28.402 for Evolved Packet Core (EPC) and non-3GPP access Interworking System;
- TS 28.403 for Wireless Local Area Network (WLAN).
Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in Performance Measurement File Format Definition (3GPP TS 32.432 [29]).
The following is beyond the scope of the present document, and therefore the present document does not describe:
- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objectives of this standardisation are:
- to provide the descriptions for a standard set of measurements;
- to produce a common description of the management technique for measurement administration and result accumulation; and
- to define a method for the bulk transmission of measurement results across a management interface.
The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardised across all vendors' implementations.
As far as possible, existing standardisation in the area of Performance Management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
The present document considers all the above aspects of Performance Management for a GSM, UMTS or LTE network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS/LTE system and particular to wireless network operation are included in the present document. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-400.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-460.zip | |
32.615 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-450.zip | The present document provides the main part of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [1].
The other parts of this XML file format definition are NRM-specific parts.
Those NRM-specific parts are provided by 3GPP TS 32.625 [11], 32.635 [12], 32.645 [13], 32.655 [14], 32.695 [16], 32.715 [17], 32.735 [18], 32.745 [15], 32.755 [20], 32.765 [19], 32.525 [21], 32.175 [22], 32.725 [23], 32.775 [24] and 32.785 [25].
Bulk CM XML file formats are based on XML [2], XML Schema [3] [4] [5] and XML Namespace [6] standards.
This File Format Definition specification is related to 3GPP TS 32.612 V9.1.X. |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-400.zip | |
32.604 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.604/32604-420.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Reference Point (IRP): Information Service defined in TS 32.602 [6]. In detail:
• Clause 4 provides the basic concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in TS 32.602 (Basic Configuration Management IRP: Information Service) [6] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Basic Configuration Management IRP over the CMIP interfaces,
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.602 V6.1.X. |
32.614 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.614/32614-430.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Bulk CM Integration Reference Point (IRP): Information Service defined in TS 32.612 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.612 V6.2.X. |
32.622 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-440.zip | The present document specifies the Generic network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
The document specifies the information in a generic manner in that the information specified is a base from which all other NRM IRP ISs such as GERAN NRM IRP IS [20] can inherit or have associations with. |
32.623 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-430.zip | The TS 32.62x-series (Generic Network Resources IRP) define an Integration Reference Point (IRP) through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the CORBA Solution Set.
This Solution Set specification is related to 3GPP TS 32.622 V9.0.X. |
32.624 | Telecommunication management; Configuration Management (CM); Generic network resources: Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.624/32624-460.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Generic Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.622 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.622 V6.4.X [4]. |
32.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-400.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Resources IRP. |
32.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-410.zip | The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.632 V9.1.X. |
32.621 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-400.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resources IRP. |
32.613 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-440.zip | The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service 3GPP TS 32.612 [3] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.612 V9.1.X. |
32.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-400.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP. |
32.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-440.zip | The present document is part of an Integration Reference Point (IRP) named "Core Network Resources IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning CN resources.
The present document specifies the protocol neutral Core Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [16], either by direct reuse or sub-classing, and in addition to that defines CN specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP 3GPP TS 32.60x [17]. However, which Interface IRP that is applicable is outside the scope of the present document. |
32.634 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.634/32634-411.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the CN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.632 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.632 V6.2.X [4]. |
32.643 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-440.zip | The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see TS 32.642 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.642 V9.3.X. |
32.644 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-430.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.642 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.642 V6.4.X. |
32.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-400.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resources IRP. |
32.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-450.zip | The present document specifies the UTRAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
The present document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.653 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.653/32653-420.zip | The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.652 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.652 V9.2.X. |
32.800 | Telecommunication management; Management level procedures and interaction with UTRAN | TR | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.800/32800-400.zip | The principle objective of the present document is to provide supporting information for the O&M standardisation of a (multi-vendor) UTRAN network. The actual specification work relating to the O&M interface between Network and Network Manager can be found in [9], [10] and [11] and for the Iub interface in [1]. For this reason the present document may contain information or working assumptions which are not a direct part of the specifications, but are essential to the progress and informed decision making. |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-450.zip | The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.654 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.654/32654-420.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.652 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.652 V6.0.X. |
33.102 | 3G security; Security architecture | TS | 4.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-450.zip | This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
A security feature is a service capability that meets one or several security requirements. The complete set of security features address the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133 [1]) and implement the security objectives and principles described in TS 33.120 [2]. A security mechanism is an element that is used to realise a security feature. All security features and security mechanisms taken together form the security architecture.
An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e. intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
GSM security functions are defined in the TS 43.020 [36].
NOTE: The usage of the authentication management field (AMF) is specified in Annex H and applies for the third (UMTS), fourth (LTE) and fifth (5G system) generation of mobile telecommunication systems. |
33.106 | 3G security; Lawful interception requirements | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-400.zip | |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 4.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-420.zip | |
33.103 | 3G security; Integration guidelines | TS | 4.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-420.zip | This technical specification defines how elements of the 3G-security architecture are to be integrated into the following entities of the system architecture.
- Home Environment Authentication Centre (HE/AuC)
- Serving Network Visited Location Register (VLR/SGSN)
- Radio Network Controller (RNC)
- Mobile station User Identity Module (UIM)
- Mobile Equipment (ME)
This specification is derived from 3G "Security architecture". [1]
The structure of this technical specification is a series of tables, which describe the security information and cryptographic functions to be stored in the above entities of the 3G system.
For security information, this is in terms of multiplicity, lifetime, parameter length and whether mandatory or optional.
For the cryptographic functions, the tables also include an indication of whether the implementation needs to be standardised or can be proprietary.
The equivalent information for the alternative Temporary Key proposal is included in an appendix to this document. |
33.200 | 3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security | TS | 4.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.200/33200-430.zip | This technical specification covers the security mechanisms and procedures necessary to protect the MAP protocol. The complete set of enhancements and extensions to facilitate security protection for the MAP protocol is termed MAPsec and it covers transport security in the MAP protocol itself and the security management procedures.
The security mechanisms specified for MAP are on the application layer. This means that MAPsec is independent of the network and transport protocols to be used.
This technical specification contains the stage-2 specification for security protection of the MAP protocol. The actual implementation (stage-3) specification can be found in the MAP stage-3 specification, TS 29.002 [4].
NOTE: It is explicitly noted that automated key management and key distribution is not part of Rel‑5. All key management and key distribution in Rel‑5 shall therefore be carried out by other means (see Annex A). |
33.120 | Security Objectives and Principles | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-400.zip | The present document gives the objectives and principles of 3GPP security.
The principles state what is to be provided by 3G security as compared to the security of second generation systems. The principles will also ensure that 3G security can secure the new services and new service environments offered by 3G systems.
The objectives give general, high level requirements for 3GPP security which will be expanded upon in 3G TS 21.133 [1].
The priorities for the implementation of 3GPP security are also given. |
33.107 | 3G security; Lawful interception architecture and functions | TS | 4.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-430.zip | |
33.908 | 3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-400.zip | This technical report is a description of the work undertaken by SAGE Task Force for the design of the standard 3GPP Confidentiality and Integrity Algorithms (SAGE TF 3GPP), and to formally approve the release of these algorithms to 3GPP.
With regard to the design of the algorithms, the scope of the present document is confined to a description of the design criteria, the design methodology and an outline of the content and structure of the specification and test data documents.
The standard 3GPP Confidentiality and Integrity Algorithms are based on a Block Cipher named KASUMI. The algorithms specification and associated test data are documented in the Specification of the 3GPP Confidentiality and Integrity Algorithms which consists of the following four documents:
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 specifications (TS 35.201).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI algorithm specification (TS 35.202).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' test data (TS 35.203).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design conformance test data (TS 35.204).
With regard to the evaluation of the algorithm, the scope of this report is restricted to a description of the evaluation criteria, the method of evaluation and the main conclusions from the evaluation that led to the Task Force approving the specification. A detailed summary of conclusions of the evaluation is provided in a public evaluation report [3] produced by the Task Force. |
33.902 | Formal Analysis of the 3G Authentication Protocol | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-400.zip | This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol.
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 refers to the main body of this report. The main body is only referred to because it is not available in Word-, but only in pdf-format. The corresponding .pdf-documents are attached to this document. |
33.909 | 3G Security; Report on the design and evaluation of the MILENAGE algorithm set; Deliverable 5: An example algorithm for the 3GPP authentication and key generation functions | TR | 4.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.909/33909-401.zip | This public report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and the general project report, ref. [4]. |
33.901 | Criteria for cryptographic Algorithm design process | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-400.zip | This report discusses the possibilities for acquisition of the cryptographic algorithms that has to be standardised in UMTS. The focus is on the encryption function used in the data confidentiality mechanism and the message authentication function used in the signalling data integrity mechanism.
First certain aspects of the process and desired results for an algorithm specification and their pro's and cons will be given. These aspects will include the possible design strategies, the evaluation strategies, the possibilities for distribution of the algorithms and the options for the liability and responsibility for the algorithm.
Then a number of the most realistic scenarios for the algorithm specification will be presented. These scenarios will be used as a basis to make a final choice for the specification process for cryptographic algorithms in third generation mobile systems. Finally, a preferred procedure will be described. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 4.6.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-460.zip | |
34.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 4.10.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-4a0.zip | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 4.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-430.zip | The present document specifies the protocol conformance testing for the 3rd Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- the description of the tests’ procedures, the specific test requirements and the messages exchanged.
The following information relevant to the tests described in the present document can be found in accompanying specifications:
- the default setting of the test parameters [9];
- the applicability of each test case and the Implementation Conformance Statement (ICS) pro-forma [11].
Note: The present document does not contain any tests on the USIM, or the interface between the UE and the USIM. These tests are documented elsewhere.
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.123-2 | User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification | TS | 4.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-430.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.123-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [45] and the common test environments are included in 3GPP TS 34.108 [44].
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 4.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-4b0.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures for use in UE conformance tests. |
34.121 | Terminal conformance specification, Radio transmission and reception (FDD) | TS | 4.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-410.zip | The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 4.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-420.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-410.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-400.zip | |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-400.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-400.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-400.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-400.zip | |
35.208 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-400.zip | |
41.033 | Lawful Interception requirements for GSM | TR | 4.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-401.zip | This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in 3GPP TS 43.033. |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 4.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-400.zip | |
35.205 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-400.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force. |
41.061 | General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.061/41061-400.zip | This TS constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60.
This TS 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 this specification. |
41.101 | Technical Specifications and Technical Reports for a GERAN-based 3GPP system | TS | 4.18.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.101/41101-4i0.zip | |
42.019 | Subscriber Identity Module Application Programming Interface (SIM API); Stage 1 | TS | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.019/42019-410.zip | The present document defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
The present document includes information applicable to network operators, service providers and terminal, SIM, switch and database manufacturers.
The present document contains the core requirements which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a SIM API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service. |
35.909 | 3G Security; Specification of the MILENAGE algorithm set: an example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Summary and results of design and evaluation | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-400.zip | |
42.033 | Lawful Interception; Stage 1 | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-400.zip | This Technical Specification provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for this specification to encompass all of them. The purpose of this specification is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of this specification general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications". |
42.009 | Security aspects | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.009/42009-410.zip | Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a special nature compared to classical distribution transmission techniques used in the fixed networks, such a category of features is related to security aspects.
In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of third parties. However, measures should be provided for in order to insure maximum protection of the rights of the individuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services.
The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up‑grading of the security in a GSM PLMN. In particular, end‑to‑end security is outside the scope of the present document.
The implementation aspects of security features are described in GSM 03.20. |
42.043 | Support of Localised Service Area (SoLSA); Service description; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.043/42043-400.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.