id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 561 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
25.432 | UTRAN Iub interface: signalling transport | TS | 3.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.432/25432-310.zip | |
25.413 | UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling | TS | 3.14.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.413/25413-3e0.zip | |
25.430 | UTRAN Iub Interface: general aspects and principles | TS | 3.8.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.430/25430-380.zip | |
25.419 | UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP) | TS | 3.11.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.419/25419-3b0.zip | |
25.832 | Manifestations of Handover and SRNS relocation | TR | 3.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.832/25832-300.zip | The present document identifies a number of handover and SRNS Relocation scenarios for UTRAN. It is intended to reflect and clarify the requirements on UTRAN, and to assist in the development of procedures and capabilities. |
25.833 | Physical layer items not for inclusion in Release 99 | TR | 3.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.833/25833-300.zip | This Technical Report collects material on UTRA physical layer items which have already been in the specifications, but were decided not to be included in release ’99.
The items are described by text from the specifications or by text proposals which have been accepted by WG1. |
25.853 | Delay budget within the access stratum | TR | 3.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.853/25853-310.zip | The present document evaluates the delay components introduced within the Access Stratum to provide guidelines useful both to provider for the dimensioning of a network and to manufacturers for the design of node elements. While the analysis of the possible delay sources is performed in an exhaustive way, the evaluation of single and global delay figures is limited to the case of Real Time services.
The estimation of Non Real Time service delays is not in scope of Release 99 and, therefore, it will not be considered in the present version of the Technical Report.
The figures of the present document sow possible scenarios and shall not be interpreted as requirements for a specific UTRAN implementation. |
25.921 | Guidelines and principles for protocol description and error handling | TR | 3.11.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.921/25921-3b0.zip | The present document provides a guideline for protocol specification of UMTS stage 2 and 3 including the usage of formal languages and rules for error handling. The present document covers control-plane and user-plane protocols specified in TSG-RAN such as RRC, RLC, RANAP, RNSAP, NBAP, PCAP, and SABP. |
25.922 | Radio resource management strategies | TR | 3.9.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.922/25922-390.zip | The present document shall describe RRM strategies supported by UTRAN specifications and typical algorithms.
This report is a release independent report. This means that the latest release applicable to 3GPP is the reference that this TR is defined upon, and contains information on all previous releases. Actual release where a given example applies is indicated in the relevant section. |
25.425 | UTRAN Iur interface user plane protocols for Common Transport Channel data streams | TS | 3.8.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.425/25425-380.zip | |
25.435 | UTRAN Iub interface user plane protocols for Common Transport Channel data streams | TS | 3.11.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.435/25435-3b0.zip | |
25.925 | Radio Interface for Broadcast/Multicast Services | TR | 3.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.925/25925-350.zip | The present document shall provide a general overview on radio interface related aspects of broadcast/multicast services. This report covers stage 2 and stage 3 aspects of the radio interface.
This report is organised as follows: clause 4 gives an overview on the broadcast/multicast services and their requirements. Clause 5 provides a common model and describes aspects common to all point-to-multipoint services. Clause 6 is devoted to the Cell Broadcast Service describing the impacts on the interface functions and the protocol aspects. The present document covers only those items, which are in the scope of 3GPP TSG RAN WG 2. Information from Technical Specifications or other documents are provided when it is necessary to understand the requirements described.
Table 1.1: Schedule of the broadcast/multicast services onto the UMTS phases and annual releases
Release
Broadcast/multicast service
1999
Cell Broadcast Service CBS (GSM)
Cell Broadcast Service (ANSI-41)
NOTE: A decision to map the services to releases is required for all other broadcast/multicast services. |
25.942 | Radio Frequency (RF) system scenarios | TR | 3.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.942/25942-330.zip | |
25.944 | Channel coding and multiplexing examples | TR | 3.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.944/25944-350.zip | The present document describes examples of channel coding and multiplexing for physical channels of FDD mode and TDD mode. |
25.434 | UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams | TS | 3.8.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.434/25434-380.zip | |
25.993 | Typical examples of Radio Access Bearers (RABs) and Radio Bearers (RBs) supported by Universal Terrestrial Radio Access (UTRA) | TR | 3.2.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.993/25993-320.zip | |
26.071 | Mandatory speech CODEC speech processing functions; AMR speech Codec; General description | TS | 3.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.071/26071-301.zip | |
26.073 | ANSI-C code for the Adaptive Multi Rate (AMR) speech codec | TS | 3.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.073/26073-330.zip | |
25.931 | UTRAN functions, examples on signalling procedures | TR | 3.7.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.931/25931-371.zip | |
26.090 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Transcoding functions | TS | 3.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.090/26090-310.zip | |
26.091 | Mandatory Speech Codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Error concealment of lost frames | TS | 3.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.091/26091-310.zip | |
26.092 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Comfort noise aspects | TS | 3.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.092/26092-301.zip | |
26.093 | Mandatory speech codec speech processing functions Adaptive Multi-Rate (AMR) speech codec; Source controlled rate operation | TS | 3.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.093/26093-330.zip | |
26.094 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec; Voice Activity Detector (VAD) | TS | 3.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.094/26094-300.zip | |
26.101 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec frame structure | TS | 3.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.101/26101-330.zip | |
26.102 | Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec; Interface to Iu, Uu and Nb | TS | 3.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.102/26102-340.zip | |
25.442 | UTRAN implementation-specific O&M transport | TS | 3.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.442/25442-310.zip | |
26.104 | ANSI-C code for the floating-point Adaptive Multi-Rate (AMR) speech codec | TS | 3.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.104/26104-350.zip | |
26.110 | Codec for circuit switched multimedia telephony service; General description | TS | 3.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.110/26110-310.zip | |
26.111 | Codec for circuit switched multimedia telephony service; Modifications to H.324 | TS | 3.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.111/26111-340.zip | |
26.131 | Terminal acoustic characteristics for telephony; Requirements | TS | 3.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.131/26131-340.zip | |
26.132 | Speech and video telephony terminal acoustic test specification | TS | 3.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.132/26132-350.zip | |
26.912 | Codec for Circuit switched Multimedia Telephony Service; Quantitative performance evaluation of H.324 Annex C over 3G | TR | 3.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.912/26912-300.zip | The present document is meant to function as guidance in the work of other 3GPP work groups or work items. Such work may include conclusion on how to achieve detailed Stage 1 service requirements or suggestion of a set of recommended RAB parameters giving satisfactory user-to-user quality for a circuit switched multimedia service using 3G-324M. |
26.911 | Codec(s) for Circuit-Switched (CS) multimedia telephony service; Terminal implementor’s guide | TR | 3.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.911/26911-340.zip | |
26.103 | Speech codec list for GSM and UMTS | TS | 3.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.103/26103-320.zip | |
26.074 | Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec test sequences | TS | 3.1.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.074/26074-311.zip | |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 3.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-350.zip | |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 3.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-310.zip | |
27.005 | Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) | TS | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-320.zip | |
26.915 | Echo Control For Speech and Multi-Media Services | TR | 3.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.915/26915-300.zip | The present document specifies minimum performance requirements for the gateway echo control of 3G speech and multi-media services. The present document is applicable to any narrow band speech telephony or multimedia service. |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 3.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-340.zip | |
27.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 3.16.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-3g0.zip | |
27.103 | Wide Area Network Synchronization | TS | 3.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.103/27103-310.zip | This specification provides a definition of a Wide Area Synchronization protocol. The synchronization protocol is based upon current synchronization industry standards.
The present document covers Wide Area Network Synchronization between current and future mobile communication end-user devices, desktop applications and server-based information servers. This is a living document and, as such, it will evaluate new technologies (e.g. XML) for inclusion as they become readily available. |
27.901 | Report on Terminal Interfaces - An Overview | TR | 3.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.901/27901-310.zip | The present document discusses external and internal interfaces of a terminal, with the exception of the radio and USIM interfaces. The focus of the study has been on external interfaces, to identify where existing industry standards can be used and whether there would be a need for specifications to be produced within 3GPP. |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 3.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-350.zip | |
27.007 | AT command set for User Equipment (UE) | TS | 3.14.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-3e0.zip | |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 3.8.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-380.zip | |
29.011 | Signalling Interworking for supplementary services | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-300.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-310.zip | |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 3.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-310.zip | |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 3.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-3b0.zip | |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 3.19.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-3j0.zip | |
27.903 | Discussion of synchronization standards | TR | 3.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.903/27903-300.zip | The present document provides information on existing synchronization protocols. It summarizes proprietary and standard protocols relevant to current and future mobile communication devices.
The present document covers only synchronization between end-user devices, desktop applications, and server-based information services. It does not refer to replication or synchronization between enterprise databases. |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 3.16.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-3g0.zip | The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140‑1 [26]. Descriptions and definitions provided by ETSI EN 301 140‑1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. |
29.010 | Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) | TS | 3.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-3c0.zip | |
29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 3.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-330.zip | |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 3.14.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-3e1.zip | |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-310.zip | |
29.007 | General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) | TS | 3.15.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-3f0.zip | |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 3.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-301.zip | |
29.998 | Open Services Architecture (OSA) Application Programming Interface (API) part 2 | TR | 3.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998/29998-320.zip | The present document investigates how the OSA Interface Class methods can be mapped onto CAMEL Application Part operations and MAP Application Part operations. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative.
The Open Service Architecture (OSA) defines an architecture that enables operator and third party applications to make use of network functionality through an open standardized interface (the OSA Interface). OSA provides the glue between applications and service capabilities provided by the network. In this way applications become independent from the underlying network technology. The applications constitute the top level of the Open Service Architecture (OSA). This level is connected to the Service Capability Servers (SCSs) via the OSA interface. The SCSs map the OSA interface onto the underlying telecommunications specific protocols (e.g. MAP, CAP, etc.) and are therefore hiding the network complexity from the applications.
The specific Service Capability Server under consideration in this technical report is the CSE. In this case, the OSA API provides the operator or third party applications access to the CAMEL Application Part protocol operations, via the OSA Interface Class methods. On the gsmSCF, the OSA Interface Class methods need to be mapped, or translated, onto the relevant CAP and/or MAP operations. Only the non-framework Service Capability Features will be taken into account for the mapping. This document is not exhaustive in covering all the mappings that can be expected. It provides several examples, but it should be noted that several other possibilities exist. In particular, only general cases of normal operations are covered and exception scenarios are not within the scope of the document.
In addition to the configuration of SCS and CSE, this technical report contains some recommendations for a configuration consisting of SCS and HLR. On the HLR, the OSA Interface Class methods need to be mapped, or translated, onto the relevant MAP protocol operations. The mappings contained in this technical report for the SCS/HLR case are not intended to be exhaustive.
The OSA API to CAP and MAP mapping is part of Release99. |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 3.3.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-331.zip | |
31.110 | Numbering system for telecommunication IC card applications | TS | 3.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.110/31110-320.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.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 3.14.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-3e0.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 3.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-310.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 3.15.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-3f1.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 3.10.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-3a0.zip | |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-300.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 3.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-330.zip | |
29.198 | Open Service Architecture (OSA) Application Programming Interface (API) - Part 1 | TS | 3.4.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198/29198-340.zip | This document specifies the stage 3 of the Open Service Architecture (OSA) Application Programming Interface (API). The concepts and the functional architecture of the Open Service Architecture (API) are described by 3GPP TS 23.127 [2]. This document describes the stage 3 specification of the Open Service Architecture API.
The Open Service Architecture defines an architecture that enables service providers to make use of network functionality through an open standardised interface, i.e. the OSA API. The network functionality is describes as Service Capability Servers. Within the OSA concepts the following Service Capability Servers are identified:
CAMEL Service Environment (see in 3GPP TS 23.078 [4])
WAP execution platform (i.e. WAP Gateway & WAP Push Proxy, see in [13] )
Home Location Register (HLR)
The stage 3 documentation of the OSA R’99 API consists of two parts:
The API specification (Part 1).
This is a normative stage 3 specification of the capabilities of the OSA R’99 API and describes the OSA API interface classes, containing class diagrams (see section 6), state transition diagrams (see section 7), data type definitions (section 8), and the IDLs (see section 9).
- The Mapping specification of the OSA R’99 API and the network protocols (Part2).
This is an informative specification to provide an example how the OSA API can be mapped on the network protocols (i.e. MAP [7], CAP[8] and WAP[9]). It is an informative document, since this mapping is considered as implementation/vendor dependent. On the other hand this mapping will provide potential service designers with a better understanding of the relationship of the OSA API interface classes and the behavior of the network associated to these interface classes.
The OSA API Stage 3 activity is performed jointly with ETSI SPAN3’s Service Provider Access Requirements activity. The contents of this document is related to the jointly owned 3GPP & ETSI document referred as the API Master document, which contains the API interface descriptions that are common and differentiated between ETSI & 3GPP. |
32.101 | Telecommunication management; Principles and high level requirements | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-340.zip | |
32.102 | Telecommunication management; Architecture | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-320.zip | |
32.005 | Telecommunications management; Charging management; 3G call and event data for the Circuit Switched (CS) domain | TS | 3.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.005/32005-370.zip | The present document is concerned with the administration of subscriber related event and call data. This includes both the collection of call data from, and the distribution of tariff data to, the Network Elements.
The subscriber (IMSI) and mobile equipment (IMEI) related call and event data collected is employed by a number of management activities including billing & accounting, statistical analysis and customer care.
The tariff data in the Network Elements is required to support the supplementary service "Advice of Charge".
The aim of the present document is to describe both the network management functions required and the data involved. |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 3.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-300.zip | |
32.015 | Telecommunications management; Charging management; 3G call and event data for the Packet Switched (PS) domain | TS | 3.12.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.015/32015-3c0.zip | The GSM and UMTS PLMN support a range of packet-based services in the same network. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions. The present document describes the functionality of charging, which includes the General Packet Radio Service (GPRS) in GSM and UMTS, as defined in 3GPP TS 22.060 [3] and 3GPP TS 23.060 [8] (packet based services). |
32.106-1 | Telecommunication management; Configuration Management (CM); Part 1: Concept and requirements | TS | 3.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-1/32106-1-310.zip | The present document describes the Configuration Management (CM) aspects of managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 32.102 [2].
The present document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant 3G NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality.
Clause 7 contains the specific definitions for the standardised N interface, which are necessary to follow for compliance to this specification.
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 [1] and 3G TS 32.102 [2]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as by other specifications for Telecom Management produced by 3GPP. All these are included in Parts 2 through 8 of the present document as follows:
Notification IRP Information Service Version 1: 32.106 Part 2
Notification IRP CORBA Solution Set Version 1:1: 32.106 Part 3
Notification IRP CMIP Solution Set Version 1:1: 32.106 Part 4
Basic Configuration Management IRP Information Model (including NRM) Version 1: 32.106 Part 5
Basic Configuration Management IRP CORBA Solution Set Version 1:1: 32.106 Part 6
Basic Configuration Management IRP CMIP Solution Set Version 1:1: 32.106 Part 7
Name Convention for Managed Objects: 32.106 Part 8 |
32.104 | Telecommunication management; 3G Performance Management | TS | 3.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.104/32104-390.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a 3G network. 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 how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Annex A specifies the file format for the bulk transfer of performance measurement results to the NM, while annex B discusses the file transfer procedure utilised on that interface. A set of measurements available for collection by NEs are described in annex C, effort has been made to ensure consistency in the definition of measurements between different NEs.
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 data produced in a multi-vendor 3G 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 3G network and its NEs defined in the 3G core Technical Specifications. However, only those aspects which are specific to a 3G system and particular to 3G-network operation are included in the present document. |
32.106-2 | Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service (IS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-2/32106-2-330.zip | Network Elements (NEs) under management generate events to inform event receivers about occurrences within the network that may be of interest to event receivers. There are a number of categories of events. Alarm, as specified in Alarm IRP: Information Service 3GPP TS 32.111-2 [1], is one member of this category.
The purpose of Notification IRP is to define an interface through which an IRPManager (typically a network management system) can subscribe to IRPAgent (typically an Element Manager (EM) or a NE) for receiving network events. It also specifies attributes carried in the network events. These attributes are common among all event categories. Attributes that are specific to a particular event category are not part of the present document. For example, perceivedSeverity is an attribute specific for alarm event category. This attribute is not defined the present document but in Alarm IRP 3GPP TS 32.111-2 [1]. |
32.106-3 | Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-3/32106-3-330.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.106-2 [5]). |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-340.zip | |
32.106-5 | Telecommunication management; Configuration Management (CM); Part 5: Basic CM Integration Reference Point (IRP): Information model (including Network Resource Model (NRM) | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-5/32106-5-320.zip | The present document (Basic Configuration Management (CM) IRP: Information Model) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate basic Configuration Management related information to one or several 'IRPManagers' (typically Network Managers). This version of the IRP is mainly intended for “passive management” of high-level network configuration and status information as required by a Network Manager.
The present document is divided in three main parts:
1. specifies a generic IRP Information Service with operations and notifications to be used by an ‘IRPManager’ to retrieve information on managed objects maintained by an ‘IRPAgent’.
2. specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Managed Object Classes.
3. defines the UMTS management NRM by reusing this generic model either by direct reuse or sub-classing.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like Security management, Software management, Network & Service provisioning, etc. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs are consistent. The Basic CM IRP here provides a base for all CM-related resource modelling.
To summarize, the Basic CM IRP has three main purposes:
(1) to define an interface for retrieval of Configuration Management information,
(2) to define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit, and
(3) to define the applied UMTS management Network Resource Model. |
32.106-6 | Telecommunication management; Configuration Management (CM); Part 6: Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-6/32106-6-340.zip | The purpose of this Basic Configuration Management (CM) IRP: Information Service CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.106-5 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
The present document does not describe any Network Resource Model (NRM) – this is described in 3GPP TS 32.106-5 [4]. Please note that 3GPP TS 32.106-5 [4] defines an IRP Information Model, which comprises both an IS and NRM definition. |
33.102 | 3G security; Security architecture | TS | 3.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-3d0.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.103 | 3G security; Integration guidelines | TS | 3.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-370.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.105 | 3G Security; Cryptographic algorithm requirements | TS | 3.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-380.zip | |
32.106-4 | Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 3.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-4/32106-4-321.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.106-2 [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 Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5. |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-360.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. |
33.120 | Security Objectives and Principles | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-300.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.901 | Criteria for cryptographic Algorithm design process | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-300.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. |
33.902 | Formal Analysis of the 3G Authentication Protocol | TR | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-310.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.908 | 3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-300.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. |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 3.16.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-3g0.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.109 | Terminal logical test interface; Special conformance testing functions | TS | 3.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-3a0.zip | |
34.121 | Terminal conformance specification, Radio transmission and reception (FDD) | TS | 3.14.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-3e0.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.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 3.12.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-3c0.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 | 3.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-350.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 | 3.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-350.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. |
32.106-8 | Telecommunication management; Configuration Management (CM); Part 8: Name convention for Managed Objects | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-8/32106-8-320.zip | A more detailed background and introduction of the IRP concept is given in 3G TS 32.101 [11] and 3G TS 32.102 [12].
To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context.
To facilitate integration of network management information obtained via multiple IRPs of different technologies such as CMIP and CORBA, identical network resource name semantics must be conveyed in all IRPs. The present document specifies one such name convention. |
32.106-7 | Telecommunication management; Configuration Management (CM); Part 7: Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-7/32106-7-330.zip | The present document defines a CMIP Solution Set for the Basic CM IRP introduced in 3GPP TS 32.106-5 [15].
The version of this CMIP Solution Set is 1:1, where the first “1” means that it corresponds to the Information Model version 1, and the second “1” means that it is the first CMIP Solution Set corresponding to Information Model version 1.
Clause 4 maps the protocol- and technology-independent operations, parameters, notifications and the Network Resource Model specified in the Basic CM IRP Information Model (Chapter 6 of 3GPP 3GPP TS 32.106-5 [15]) onto the corresponding CMIP/CMISE equivalences. The important technical aspects specific to this CMIP Solution Set are also described there. The GDMO definitions are introduced in Clause5. Clause 6 contains the ASN.1 definitions related to the GDMO definitions provided in clause 5. |
33.106 | 3G security; Lawful interception requirements | TS | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-310.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.