id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
25.322 | Radio Link Control (RLC) protocol specification | TS | 3.18.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.322/25322-3i0.zip | |
25.323 | Packet Data Convergence Protocol (PDCP) specification | TS | 3.10.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.323/25323-3a0.zip | |
25.324 | Broadcast/Multicast Control (BMC) | TS | 3.9.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.324/25324-390.zip | |
25.331 | Radio Resource Control (RRC); Protocol specification | TS | 3.21.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.331/25331-3l0.zip | |
25.401 | UTRAN overall description | TS | 3.10.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.401/25401-3a0.zip | |
25.402 | Synchronisation in UTRAN Stage 2 | TS | 3.10.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.402/25402-3a0.zip | |
25.410 | UTRAN Iu interface: General aspects and principles | TS | 3.8.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.410/25410-380.zip | |
25.411 | UTRAN Iu interface layer 1 | TS | 3.5.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.411/25411-350.zip | |
25.412 | UTRAN Iu interface signalling transport | TS | 3.6.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.412/25412-360.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.414 | UTRAN Iu interface data transport and transport signalling | TS | 3.13.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.414/25414-3d0.zip | |
25.415 | UTRAN Iu interface user plane protocols | TS | 3.12.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.415/25415-3c0.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.420 | UTRAN Iur interface general aspects and principles | TS | 3.5.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.420/25420-350.zip | |
25.421 | UTRAN Iur interface layer 1 | TS | 3.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.421/25421-310.zip | |
25.422 | UTRAN Iur interface signalling transport | TS | 3.6.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.422/25422-361.zip | |
25.423 | UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling | TS | 3.14.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.423/25423-3e2.zip | |
25.424 | UTRAN Iur interface data transport & transport signalling for Common Transport Channel data streams | TS | 3.9.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.424/25424-390.zip | |
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.426 | UTRAN Iur and Iub interface data transport & transport signalling for DCH data streams | TS | 3.9.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.426/25426-390.zip | |
25.427 | UTRAN Iub/Iur interface user plane protocol for DCH data streams | TS | 3.11.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.427/25427-3b0.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.431 | UTRAN Iub interface Layer 1 | TS | 3.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.431/25431-310.zip | |
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.433 | UTRAN Iub interface Node B Application Part (NBAP) signalling | TS | 3.14.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.433/25433-3e2.zip | |
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.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.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 | |
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 | |
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 | |
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 | |
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 | |
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.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 | |
25.941 | Document structure | TR | 3.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.941/25941-310.zip | |
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 | |
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 | |
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 | |
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 | |
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.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.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.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 | |
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. |
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.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.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 | |
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.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 | |
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.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.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 | |
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 | |
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 | |
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 | |
29.002 | Mobile Application Part (MAP) specification | TS | 3.20.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-3k0.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.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.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.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.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 | |
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 | |
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.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 | |
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.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.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. |
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.102 | Characteristics of the Universal Subscriber Identity Module (USIM) application | TS | 3.18.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-3i0.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 | |
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 | |
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 | |
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 | |
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. |
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.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.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-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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.