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.852 | Iu enhancements for IP Multimedia (IMS) support in UTRAN | TR | 0.1.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.852/25852-012.zip | This present document is for the 3GPP Release 6 Work Item “Iu Enhancements for IMS Support in UTRAN”(see [1]).
Release 5 enables the basic support for IMS in the RAN but evaluation of possible further enhancements was decided in RAN#19.
The purpose of the present document is to aid TSG RAN WG3 to standardise these possible improvements in release 6 by refining the requirements from a RAN thorough perspective and evaluate the associated optimisations in the handling of IMS RAB in the RNC.
This document is intended to gather all this information, assess the proposals of enhancements and agree on some of them in section 7 before integrating them into the Technical Specifications.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
25.867 | Feasibility study for wideband distribution systems in 3rd generation networks | TR | 1.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.867/25867-130.zip | The present document summarises the results of the feasibility study about inclusion of Wideband Distribution Systems, or WDS, as part of third generation networks in 3GPP standards.
It covers the history of the proposal, shows and discusses the results of relevant analysis and simulation activities, highlights the possible degree of integration to the current status of 3GPP network architecture and concludes with the indication for a possible way forward in the standardisation path. |
25.869 | Transmitter diversity solutions for multiple antennas | TR | 1.2.1 | R1 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.869/25869-121.zip | The study done in this TR focuses on transmit diversity methods with more than 2 antennas at the Node B and 1 antenna at the UE. The functionality introduced to support more than 2 antennas at the Node B could permit consideration of compatible operation with 2 antennas.
A proposal for a new transmit diversity method using multiple antennas may be included in the TR if at least the following requirements are fulfilled:
a) it should be shown that there is significant benefit in at least one realistic scenario, e.g. one of the (multi-)path models of table 7; for closed loop methods also feedback errors and delays need to be considered.
b) the description should be detailed enough to see how it fits into the current specification (so it is in principle clear what changes need to be done).
c) relevant R99 schemes should be used as reference cases depending on the proposal (open or closed loop, or both)
d) backwards compatibility needs to be addressed
This evaluation of different transmit diversity schemes for multiple antennas is within the scope of this TR. |
25.876 | Multiple Input Multiple Output (MIMO) antennae in UTRA | TR | 1.8.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.876/25876-180.zip | This document captures the working assumptions and evaluation criteria of the different techniques being considered for Multiple-Input Multiple-Output (MIMO) in UTRA.
The purpose of this TR is to help TSG RAN WG1 to define and describe the potential enhancements under consideration and compare the benefits of each enhancement with earlier releases for improving the performance of the dedicated and shared transport channels in UTRA downlink, along with the complexity evaluation of each technique. |
25.891 | Improvement of Radio Resource Management (RRM) across RNS and RNS/BSS post-Rel-5 | TR | 0.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.891/25891-030.zip | This present document is for the Release 6 work item “Improvement of RRM across RNS and RNS/BSS”(see [1]).
Based on the Release 5 study (see 3GPP TR 25.881[2]), a Release 5 solution was accepted. The objective of this work item is to work on possible further improvements to the Release 5 solution.
The purpose of the present document is to help TSG RAN WG3 to specify the different schemes to improve the RRM acoross RNS and RNS/BSS and to compare them.
This document is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
This document identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
25.897 | Feasibility study on the evolution of UTRAN architecture | TR | 0.3.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.897/25897-031.zip | This present document is for the 3GPP Release 6 Study Item “Evolution of UTRAN Architecture”(see [1]).
The purpose of the present document is to help TSG RAN WG3 to define different UTRAN Architecture scenarios and compare the benefits of each of them. The study on the evolved architecture shall be performed for both transport options, the ATM transport option and IP transport option.
This document is intended to gather all information in order to compare the solutions and to draw a conclusion on the way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
25.898 | Power control enhancements for UTRA | TR | 0.1.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.898/25898-010.zip | The present document is the technical report on features that are proposed to enhance the existing power control procedures in UTRA.
The purpose of this TR is to help TSG RAN WG1 to define and describe potential power control enhancements under consideration and compare the benefits of each enhancement with earlier releases for improving system capacity or coverage in UTRA, along with a complexity and backwards compatibility evaluation of each technique. The impact beyond the physical layer of each proposed technique shall clearly be addressed.
This activity involves the Radio Access Network work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information in order to compare the solutions and system gains vs. complexity and draw a conclusion on a way forward. |
25.909 | Enhanced uplink UTRA FDD; UTRAN Iub/Iur protocol aspects | TR | 0.0.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.909/25909-001.zip | The present document is part of the Release 6 work item “FDD Enhanced Uplink”. The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing Iub/Iur specifications, needed for the introduction of the “FDD Enhanced Uplink” feature for Release 6. This work task belongs to the TSG RAN Building Block “FDD Enhanced Uplink: UTRAN Iub/Iur Protocol Aspects”. |
25.998 | UTRAN recommendation and UE allowance for non-essential corrections of a feature made only in a later release | TR | 0.0.1 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.998/25998-001.zip | The present document identifies functional errors in a given Release of the UTRAN technical specifications which, due to their late discovery and inessential nature, have not been corrected until a later Release.
For each such error, the approved corrective changes (pertaining to later Releases) are identified and guidance is offered as to whether and how they may be incorporated into the design of an earlier Release UTRAN and / or UE.
The present document provides recommended measures which may be adopted by UTRAN when a feature which belongs to a given release is found (totally or partially).erroneous but has only been corrected in a later release due to the late discovery and the non-essential nature of the correction.
For these features, this TR also describes whether a UE is allowed to implement the correction in the release where the feature belongs i.e. before the actual release in which the CR was made, so as to enable the same UE behaviour (implementation) irrespective of the release, as a facility to UE manufacturers and without any intension to provide this information to the network (“Early UE” , which applies to essential corrections, should not apply here). |
29.199 | Open Service Access (OSA); Web Services Application Programming Interface (API) for OSA; Parlay X services | TS | 1.0.1 | N5 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199/29199-101.zip | The present document specifies an initial set of Parlay X Web Services. For each selected Web Service, this document describes the motivation for its inclusion, the commercial and technical rationale, and an illustrative usage scenario(s). This document also specifies the message(s) exchanged during invocations of each Web Service, by defining the semantics in English and the syntax using W3C WSDL.
The OSA APIs are designed to enable creation of telephony applications as well as to "telecom-enable" IT applications. IT developers, who develop and deploy applications outside the traditional telecommunications network space and business model, are viewed as crucial for creating a dramatic whole-market growth in next generation applications, services and networks.
The Parlay X Web Services are intended to stimulate the development of next generation network applications by developers in the IT community who are not necessarily experts in telephony or telecommunications. The selection of Web Services should be driven by commercial utility and not necessarily by technical elegance. The goal is to define a set of powerful yet simple, highly abstracted, imaginative, telecommunications capabilities that developers in the IT community can both quickly comprehend and use to generate new, innovative applications. |
32.307 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set (SS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.307/32307-030.zip | The present document specifies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [4]).
This Solution Set specification is related to 3GPP TS 32.302 V9.0.X. |
32.317 | Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP Solution Set (SS) | TS | 0.5.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.317/32317-051.zip | The present document specifies the SOAP Solution Set for Generic IRP management whose capabilities are specified in Generic IRP management: Information Service (3GPP TS 32.312 [1]).
This Solution Set specification is related to TS 32.312 V9.0.X. |
32.344 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.344/32344-600.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the IRP whose semantics is specified in File Transfer IRP: Information Service [7]. |
32.350 | Telecommunication management; Communication Surveillance (CS) requirements | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.350/32350-100.zip | The present document describes the requirements of the Communication Surveillance. |
32.431 | Telecommunication management; Performance measurement collection Integration Reference Point (IRP); Requirements | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.431/32431-100.zip | The present document defines, in addition to the requirements defined in [1], [2], and [3], the requirements for the present IRP: Performance measurement collection IRP. |
32.607 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); SOAP Solution Set (SS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.607/32607-030.zip | The purpose of this Basic CM IRP: SOAP Solution Set is to define the mapping of the Basic CM IRP: IS (3GPP TS 32.602 [4]) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment.
The present document defines NRM independent data types and methods.
This Solution Set specification is related to 3G TS 32.602 V9.0.X. |
32.667 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); SOAP Solution Set (SS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.667/32667-030.zip | The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (3GPP TS 32.662 [4]) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment.
This Solution Set specification is related to 3GPP TS 32.662 V9.0.X. |
32.681 | Telecommunication management; Inventory Management (IM) Integration Reference Point (IRP): Requirements | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.681/32681-100.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Inventory Management IRP. |
33.109 | Bootstrapping of application security using AKA and support for subscriber certificates; System description | TS | 0.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.109/33109-030.zip | The present document describes the security features and a mechanism to bootstrap authentication and key agreement for application security from the 3GPP AKA mechanism. Candidate applications to use this bootstrapping mechanism include but are not restricted to subscriber certificate distribution, etc. Subscriber certificates support services whose provision mobile operator assists, as well as services that mobile operator provides.
The scope of this specification includes two parts. The first part presents a generic AKA bootstrapping function, an architecture overview and the detailed procedure how to bootstrap the credential. The second part is the requirement for applications utilizing the bootstrapping function, as well as the procedure of the utilization. Specifically the present document presents signalling procedures for support of issuing certificates to subscribers and the standard format of certificates and digital signatures. It is not intended to duplicate existing standards being developed by other groups on these topics, and will reference these where appropriate.
Editor’s note: The specification objects are scheduled currently in phases. For the first phase of standardisation, only the case is considered where bootstrapping server functionality and network application function are located in the same network as the HSS. In later phases, other configurations may be considered. |
33.878 | Security aspects of early IMS | TR | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.878/33878-100.zip | The present document specifies an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. |
33.917 | (Universal) Subscriber Interface Module (U)SIM security reuse by peripheral devices on local interfaces | TR | 0.7.3 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.917/33917-073.zip | This feasibility study report conducts a threat analysis and determines the feasibility of Reuse of a Single (U)SIM, USIM, or ISIM by peripheral devices on local interfaces to access multiple networks. Most important for this Reuse is the authentication and key agreement (AKA) function provided by these applications. The peripheral devices include 3GPP and WLAN devices that function as integrated or attachable peripherals on Laptops or PDAs or other mobile data devices. The multiple access networks of interest correspondingly include 3GPP and WLAN type networks. The objective of this study is to realize the diverse usage models with multiple external (wired or wireless) interfaces from a security point of view, without incorporating significant changes to the 3GPP and WLAN infrastructure. It also studies the impact on current security specifications for 3GPP, especially given that some issues have already been identified surrounding key setting procedures, USIM sequence number synchronization, UICC presence detection/UICC application presence detection and termination of the UICC usage etc. It also studies additional user authentication requirements (e.g. PINs) when used over local interfaces like Bluetooth, IR or USB. Further more it studies the impact on having many entities using the same security mechanism and any 3GPP core network elements. Reuse of security functions provided by applications on the UICC does not have an impact on ownership and control of the UICC, which remains with the issuer of the UICC. |
33.941 | Presence service; Security | TR | 0.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.941/33941-060.zip | The present document describes the Stage 2 description (security architectural solution and functionalities) for the Presence Service, which includes the elements necessary to realise the stage 1 requirements in 3GPP TS 22.141 [2] and 3GPP TS 23.141 [3].
The present document includes information applicable to network operators, service providers and manufacturers. |
43.019 | Subscriber Identity Module Application Programming Interface (SIM API) for Java Card; Stage 2 | TS | 6.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.019/43019-600.zip | The present document defines the stage two description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM.
This stage two describes the functional capabilities and the information flow for the SIM API implemented on the Java Card 2.1 API specification [6].
The present document includes information applicable to network operators, service providers and SIM, server and database manufacturers. |
44.933 | Seamless support of streaming services in GERAN A/Gb mode | TR | 1.3.0 | G2 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.933/44933-130.zip | The present document provides a study on requirements, performance and possible enhancements for seamless support of streaming services in GERAN A/Gb mode. |
51.010-6 | Mobile Station (MS) conformance specification; Part 6: Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification | TS | 0.0.1 | G3new | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-6/51010-6-001.zip | The present document specifies and provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma for the GSM/EDGE Radio Access Network Digital cellular telecommunications system (Phase 2+);Mobile Station (MS) conformance specification Conformance specification as defined in 3GPP TS 51.010‑1 [6]. |
55.226 | 3G Security; Specification of the A5/4 Encryption Algorithms for GSM and ECSD, and the GEA4 Encryption Algorithm for GPRS | TS | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.226/55226-100.zip | |
21.103 | 3rd Generation mobile system Release 5 specifications | TS | 5.4.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.103/21103-540.zip | The present document identifies the 3rd generation mobile system specifications for Release 5. The specifications and reports of 3GPP Release 5 have a major version number 5 (e.g. 5.x.y).
Most of the core Release 5 Technical Specifications and Technical Reports were functionally frozen at either the 15th Technical Specification Group meetings in March 2002 or the 16th in June 2002.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 5 version 5.x.y specifications throughout 2002 and beyond. |
22.141 | Presence service; Stage 1 | TS | 5.2.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.141/22141-521.zip | |
22.146 | Multimedia Broadcast/Multicast Service (MBMS); Stage 1 | TS | 5.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.146/22146-520.zip | |
22.240 | Service requirements for 3GPP Generic User Profile (GUP); Stage 1 | TS | 0.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.240/22240-050.zip | |
22.243 | Speech recognition framework for automated voice services; Stage 1 | TS | 1.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.243/22243-120.zip | |
22.946 | Broadcast and multicast services | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.946/22946-100.zip | |
23.121 | Architectural requirements for Release 1999 | TS | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.121/23121-500.zip | The present document covers issues related to the evolution of the GSM platform towards UMTS with the overall goal of fulfilling the UMTS service requirements, the support of the UMTS role model, support of roaming and support of new functionality, signalling systems and interfaces. |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 0.12.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-0c0.zip | |
23.241 | 3GPP Generic User Profile (GUP); Stage 2; Data Description Method (DDM) | TS | 0.4.3 | N4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.241/23241-043.zip | The present document is the Stage Two description for the Data Description Method (DDM) and the Datatype Definition Method (DtDM) of the 3GPP Generic User Profile.
The present document specifies the method for describing the logical structure of the data description, Generic User Profile, Profile Components, methods for describing Datatypes and other constructs for use in 3GPP. The GUP data description method is designed to coexist with other data description technologies.
The document includes:
• DDM and DtDM features and definition;
• Process and procedures for administration of GUP/DDM and 3GPP TS 24.241 [12]. |
23.841 | Presence service architecture | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.841/23841-110.zip | |
23.846 | Multimedia Broadcast/Multicast Service (MBMS); Stage 2 | TR | 0.5.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.846/23846-051.zip | The present document discusses architectural issues and describes functionalities required for the Multimedia Broadcast/Multicast Service. MBMS requirements are discussed in [2] and it is the intention of this document to present one or more alternatives to achieving the required functionality within 3GPP networks. |
23.908 | Technical report on Pre-Paging | TR | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.908/23908-500.zip | The purpose of the present document is to study:
1. The potential applications of Pre-paging in GSM/UMTS networks.
2. The impact of Pre-paging on the GSM/UMTS specifications.
3. The interaction of Pre-paging with the work carried out by SMG2 and SMG3 on Classmarks for UMTS (i.e. Service Classmark and Terminal classmark).
It is a requirement of the report that the Pre-paging mechanism does not require an upgrade of the MAP application context version. |
23.909 | Technical report on the Gateway Location Register | TR | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.909/23909-500.zip | The present document describes the use of a Gateway Location Register within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
One of the requirements of the present document is to describe a network architecture where the presence of a GLR within a UMTS PLMN is not visible to either a second generation PLMN (i.e. GSM release 98 or earlier) or a 3G PLMN (i.e. GSM Release 99 or later). So the objective of this report is that changes to GSM specified interfaces or procedures will not be needed in order to:
- integrate a GLR into a UMTS PLMN;
- allow interworking between a GLR-enabled UMTS network and a GSM or UMTS network without a GLR.
The present document will be restricted to the study of the case where the GLR supports one VPLMN only. A separate TR will be required if support of multiple VPLMNs by the GLR is to be studied.
The present document will study support of multiple HPLMNs by the GLR. |
23.911 | Technical report on Out-of-band transcoder control | TR | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.911/23911-500.zip | The purpose of the present document is to study:
1. The feasibility of out-of-band transcoder control in UMTS/IMT-2000 networks.
2. The impact of out-of-band transcoder control on the UMTS/IMT-2000 specifications.
The present document introduces one enhanced in-band transcoder control procedure and four out‑of‑band transcoder control procedures that might be adaptable for transcoder control in UMTS/IMT-2000 networks. Then compare each procedure from various point of views to seek the most feasible procedure. |
23.912 | Technical report on Super-Charger | TR | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.912/23912-500.zip | The present document describes the use of Super-Charger mechanism within UMTS to reduce the signalling traffic associated with mobility. This document provides a technical proposal and example uses of the Super-Charger concept but also identifies issues that require further study. Finally, this document highlights the advantages and disadvantages, and identifies the UMTS Technical Specifications that would require enhancing to support this functionality. |
23.955 | Virtual Home Environment (VHE) concepts | TR | 0.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.955/23955-010.zip | The present document is to capture VHE concepts. It is not limited to any specific type of services. It includes OSA, CAMEL, SIP, MExE USAT etc..
Contributions for VHE/OSA concerning the document TS 23.127 have to be provided in the form of Change Requests. Since a lot of changes are expected due to the shift of the focus of the document from OSA to VHE this is an inflexible procedure.
Consequently this document was created to collect contributions, ideas and proposals for TS 23.127. They have to be written against the current structure of the document. It is planned to dissolve the TR and to create Change Requests against the TS 23.127 or other applicable documents from it at the end.
The body of this document is planned to be incorporated into appropriate TS documents. |
23.974 | Support of push service | TR | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.974/23974-200.zip | The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope. |
25.855 | High Speed Downlink Packet Access (HSDPA); Overall UTRAN description | TR | 5.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.855/25855-500.zip | The present document captures the agreements and evaluation criteria for the different techniques being considered for HSDPA with regards to the overall support of UTRAN for HSDPA. |
22.941 | IP based multimedia framework; Stage 0 | TR | 0.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.941/22941-070.zip | |
25.887 | Beamforming enhancements | TR | 1.7.1 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.887/25887-171.zip | The scope of this TR is to define potential measurements for UTRA FDD and their performance requirements for efficient support of RRM in case beamforming is used in UTRAN. |
25.888 | Improvement of inter frequency and inter system measurement for 1,28 Mcps TDD | TR | 1.1.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.888/25888-110.zip | In order to improve monitoring other RAT systems or performing inter-frequency measurements in 1.28 Mcps TDD , the channel re-assigning scheme with signaling support and other possible solutions are proposed and investigated, potentially allowing the UE to have a longer measurement window or to avoid possible measurement failures.The purpose of this document is to help the TSG RAN WG1, WG2, WG3 and WG4 to understand potential benefits with respect to the respective study areas, to investigate the proposed method and to identify the impacts to current specifications, which is needed for the introduction of the improvement of inter-frequency and inter-system measurement for1.28 Mcps TDD.
The different study areas will be described in subsequent chapters.
It is intended to gather all information in order to trace the history and the status of the SI in each WGs.
The TR should:
• describe the proposed methods for each study area.
• describe the impacts due to this SI.
• describe agreed requirements related to the SI.
• identify the affected specifications according to the introduction of inter frequency and inter system measurement for 1.28 Mcps TDD and
• also describes the schedule of the SI. |
25.885 | UMTS 1800 / 1900 MHz work items report | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.885/25885-100.zip | This clause shall start on a new page. No text block identified. Should start:
This document is a technical report of the UMTS1800/1900 work items. The purpose of these work items is to provide UMTS specification support for UTRA/FDD in the 1800 MHz (ITU region 1 and 3) and 1900 MHz bands (ITU region 2). In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, and methodology, study results and specification recommendations.
This document is a ‘living’ document, periodically updated and presented at all TSG-RAN meetings until all related CRs are agreed and approved. |
25.951 | FDD Base Station (BS) classification | TR | 1.5.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.951/25951-151.zip | |
27.104 | vObjects and other constructs for data synchronization | TS | 0.1.1 | T2 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.104/27104-011.zip | This specification serves as a vessel to manage the process of adding new vObjects and other constructs as data store types for use in data synchronisation activities within the 27.103 Wide Area Synchronisation specification.
While this first release is identified as a Release 4 specification, this is a living document and, as such, it encompasses the addition of new vObjects and other constructs for inclusion in data synchronisation activities as they become readily available, an evolving task that will continue beyond a single release. |
29.162 | Interworking between the IM CN subsystem and IP networks | TS | 1.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-130.zip | The IM CN subsystem interworks with the external IP networks through the Mb reference point.
This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking and, user plane interworking for specific interworking use cases. Clause 10 describes the IMS-Ix interface requirements in the form of Use Cases which require H.248 protocol procedures. Subclause 10.4 then details the additional Information Elements required to perform the specific procedures.
The IP version Interworking, between IP version 4 (IETF RFC 791 [9] ) and IP version 6 (IETF RFC 2460 [10] ) detailed in terms of the processes and protocol mappings required in order to support both IMS originated and terminated calls. |
29.198-04 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control Service Capability Feature (SCF) | TS | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04/29198-04-500.zip | The present document is Part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
30.002 | Guidelines for the modification of the Mobile Application Part (MAP) | TR | 5.0.0 | N4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.002/30002-500.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. |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-100.zip | |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-100.zip | |
31.123 | (Universal) Subscriber Interface Module ((U)SIM) toolkit interpreter test | TS | 0.3.0 | T3 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.123/31123-030.zip | |
31.131 | C-language binding to (U)SIM API | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-100.zip | |
32.108 | Telecommunication management; Subscriber and equipment trace | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.108/32108-010.zip | [Editor’s note: The text is still partly from 12.08. More updating needed.]
This Technical Specification (TS) specifies the Trace facility for GSM 3G mobile networks where it refers to:
- Subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI or Public ID));
- Equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- Types of trace which relate more to network elements than to individual subscribers e.g. tracing events within a Base Station System (BSS), and so on;
- Tracing of all possible parties in e.g. a multi-party call, (although multiple calls related to the IMSI specified in the trace type field are traceable).
The control signalings on different interfaces and the characteristics of user data are within the scope of this TS, but not the actual contents of the user data.
This TS does not specify any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer.
This TS does not specify any data compression mechanisms for trace data transfer. |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 0.5.5 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-055.zip | |
41.103 | GSM Release 5 specifications | TS | 5.4.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.103/41103-540.zip | The present document identifies the GSM system specifications for Release 5. The specifications and reports of 3GPP Release 5 have a major version number 5 (e.g. 5.x.y).
Most of the core Release 5 Technical Specifications and Technical Reports were functionally frozen at either the 15th Technical Specification Group meetings in March 2002 or the 16th in June 2002.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 5 version 5.x.y specifications throughout 2002 and beyond. |
42.031 | Fraud Information Gathering System (FIGS); Service description; Stage 1 | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.031/42031-500.zip | This Technical Specification specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
This specification enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN. |
43.031 | Fraud Information Gathering System (FIGS); Service description; Stage 2 | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.031/43031-500.zip | This Technical Specification specifies the stage 2 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
Three levels of FIGS service are defined, levels 1 to 3.
Level 1 will use the facilities provided by Transferred Account Procedure (TAP).
Levels 2 and 3 will use facilities provided by Customised Applications for Mobile network Enhanced Logic (CAMEL), in particular, the information flows between the GSM Service Switching Function (gsmSSF) and GSM Service Control Function (gsmSCF). Phase 1 and Phase 2 CAMEL facilities will be used.
Connection-orientated services only are covered. |
43.900 | Support for voice optimization for the IMS in the GERAN | TR | 1.0.0 | G1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.900/43900-100.zip | The present document provides an overview of the architecture and issues related to the provision of voice optimisation within the GERAN. |
43.930 | Iur-g interface; Stage 2 | TR | 5.1.0 | G2 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.930/43930-510.zip | The present document provides an overview of the Iur-g interface. It describes the motivation, principles and functionality of this interface. It does not contain the detailed description, which it is included in the stage 3 Technical Specifications. |
51.010-5 | Mobile Station (MS) conformance specification; Part 5: Inter-Radio-Access-Technology (RAT) (GERAN / UTRAN) interaction Abstract Test Suite (ATS) | TS | 2.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-5/51010-5-200.zip | The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM/3GPP mobile stations (MS) conforming to the TSs for Layer 3, for the digital cellular telecommunications systems.
The present document is valid for MS implemented according to R99, 3GPP Release 4, Release 5, Release 6, Release 7, Release 8, Release 9 or Release 10.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications. |
51.011 | Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface | TS | 5.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.011/51011-500.zip | The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in the 3GPP TS 42.017 [6]. The requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols are all defined in accordance with the 3GPP TS 31.101 [55] except when stated otherwise in the present document.
The present document defines:
‑ the model which shall be used as a basis for the design of the logical structure of the SIM;
‑ the security features;
‑ the interface functions;
‑ the commands;
‑ the contents of the files required for the GSM application;
‑ the application protocol.
The present document does not specify any aspects related to the administrative management phase. Any internal technical reallocation of either the SIM or the ME are only specified where these reflect over the interface. It does not specify any of the security algorithms which may be used.
The present document defines the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification. |
21.102 | 3rd Generation mobile system Release 4 specifications | TS | 4.9.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.102/21102-490.zip | The present document identifies the 3rd generation mobile system specifications for Release 4. The specifications and reports of 3G Release 4 have a major version number 4 (e.g. 4.x.y).
Most of the core Release 4 Technical Specifications and Technical Reports were functionally frozen at the 11th Technical Specification Group meetings (TSG#11) in March 2001.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 4 version 4.x.y specifications throughout 2001 and beyond. |
22.112 | USIM Application Toolkit (USAT) Interpreter; Stage 1 | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.112/22112-400.zip | The present document specifies a system to make Mobile Operator services, based on USAT functionality and USIM based security functionality, available to an internet environment. This is achieved by specifying the necessary components and protocols for a secure narrow band channel between the internet application and an USAT Interpreter on the USIM. The actual application could be developed using the application language of choice. Two types of applications interfaces are used as examples, i.e., mark-up language based on WML and Remote Procedure Call (RPC).
The interpreter and the secure narrow band channel form a core platform to enable services like:
- Advanced security functionality, e.g., digital signatures in m-commerce applications
- Value added services based on position and roaming
- Controlled activation and management of other applications, e.g. multimedia and payment type of applications.
The secure narrow band channel is achieved by specifying the following:
- specific application and content related functionalities of the interface between the application system and the USAT Gateway;
- specific functionalities and protocols of the interface between the USAT Gateway and the USAT Interpreter associated with a USIM, achieved by defining a low level command set for interpretation by the USAT Interpreter;
- defined level of functionality available to the application server for the implementation of USIM based services such as PKI, location services, push and broadcast services, event based services, etc..
The present document does not specify any elements of the protocol stack between the application server and the USAT Gateway, the mark-up language definition, and the transport protocols between the USAT Gateway and the USAT Interpreter. |
23.073 | Support of Localised Service Area (SoLSA); Stage 2 | TS | 4.0.0 | N4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.073/23073-400.zip | The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43. |
23.171 | Location Services (LCS); Functional description; Stage 2 (UMTS) | TS | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.171/23171-400.zip | The present document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
Location Services may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
This stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc. |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-200.zip | |
23.821 | Architecture Principles for Reelase 2000 | TR | 1.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.821/23821-101.zip | The scope of this Technical Report is to list architectural requirements, features, functions and solutions of UMTS inside the scope of UMTS Release 00. These are working assumptions agreed by TSG SA WG2. The TR focuses on
- new/modified functionality as compared to Release 99
- technical description of the features, functions and solutions of R00.
It is expected that this TR will act as a basis for the detailed Stage 2 specification work.
This TR has been created to ease the development of R00 work prior to the finalization of the R99 specifications. In conjunction with when R99 is finalized, work on the TR will cease and the relevant CRs will be produced to incorporate the contents of this TR within the R00 version of the specifications." |
23.874 | Feasibility study of architecture for network requested PDP context activation with User-ID | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.874/23874-130.zip | The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope. |
23.907 | Quality of Service (QoS) concept | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.907/23907-120.zip | Scope of this document is to provide the framework for Quality of Service in UMTS. The document shall be used as a living document which will cover all issues related Quality of Service in UMTS. |
23.913 | UMTS Turbo-Charger | TR | 1.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.913/23913-100.zip | |
23.922 | Architecture for an All IP network | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.922/23922-400.zip | This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS standard
in order to provide this architectural option within Release 2000. |
23.923 | Combined GSM and Mobile IP mobility handling in UMTS IP CN | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.923/23923-400.zip | The present document contains a feasibility study on using Mobile IP+ as a tunnelling and mobility management protocol in combination with GSM/UMTS mobility management in the packet domain of UMTS CN. A target architecture will be described and evaluated and the migration path from the current GPRS architecture towards the target architecture will be defined. It shall also describe the driving forces for moving from GTP towards Mobile IP+ as well as the benefits and disadvantages of the target architecture. A time schedule, i.e. UMTS releases, for the standardisation of such an architecture shall be proposed. Work on Mobile IP+ in the IETF should be taken into account.
This report will also contain a study on how to offer Mobile IP+ as an overlay to GPRS. This would allow an end user device, which is connected to the Internet (or intranet etc.) via LAN, to be reconnected during an active session via GPRS/UMTS or visa versa, without the need for any re-configuration or re-start of applications. The outcome of this part shall be part of UMTS release 99. Proposed solutions need to be balanced between the requirement to minimise the impact on the current GPRS standards and the requirements generated by further development of using Mobile IP+ within the CN in an efficient way. The output of this study is a description of the system and a set of CR's for those standards handled by 3GPP-TSG SA-WG2. |
23.972 | Circuit switched multimedia telephony | TR | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.972/23972-400.zip | This document collects the requirements and working assumptions for multimedia for release 99. The description is at a level of detail, which is required in the detailed procedure design in N1 and N3.
The target release for the Multimedia specifications is (in general) R99, and the specifications apply to UMTS as well as GSM. |
25.835 | Report on hybrid ARQ type II/III | TR | 1.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.835/25835-100.zip | This technical report captures the results of the work on the work item “Hybrid ARQ Type II/III”. This includes technical solutions and their comparison. The report covers impacts on all RAN WGs. |
25.837 | Hybrid ARQ Type II/III (Iub/Iur aspects) | TR | 0.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.837/25837-010.zip | The purpose of the present document is to gather all information concerning the impacts of Hybrid ARQ Type II/III on RAN WG3. |
25.845 | FDD RACH and AICH performance requirements | TR | 0.0.3 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.845/25845-003.zip | This document is a Technical Report concerning the WG4 work item “Performance specification of demodulation of common channels”. In this report FDD RACH and AICH receptions are considered. |
25.924 | Opportunity Driven Multiple Access (ODMA) | TR | 1.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.924/25924-100.zip | The present document provides a description of Opportunity Driven Multiple Access (ODMA).
ODMA is a relay transmission protocol to be applied to UMTS TDD. ODMA will provide the ability to maintain high data rates within a TDD towards the edges of traditional TDD coverage. The main purpose of ODMA is:
- Increase the high data rate coverage within a cell.
- Increase the capacity of TDD.
- Provide distributed network architecture for spot coverage and traffic hotspots. |
25.933 | IP transport in UTRAN | TR | 2.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.933/25933-200.zip | The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of "IP Transport" option in the UTRAN for Release 5. It is intended to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task, and split the Work Task into "Study Areas" in order to group contributions in a consistent way.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
The present document is a "living" document, i.e. it is permanently updated and presented to all TSG-RAN meetings. |
25.938 | Terminal power saving features | TR | 2.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.938/25938-200.zip | The pupose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the “Terminal Power Saving Features” option for Release 2000.
WG1 is the leading working group of this Work Item (WI) and has its own TR. The purpose of this TR is not to replace the TR or any decisions made in the leading WG. Rather, it is intended to gather all the information in order to trace the history and the status of the Work Task in other RAN WGs, and discuss issues that WG3 has impact on.
It is not intended to replace contributions and Change Requests, but only to list conclusions and make references to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings |
25.952 | TDD Base Station (BS) classification | TR | 1.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.952/25952-110.zip | This document is a Technical Report on Release 5 work item “TDD Base Station Classification”. |
26.226 | Cellular text telephone modem; General description | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.226/26226-400.zip | |
26.230 | Cellular text telephone modem; Transmitter bit exact C-code | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.230/26230-400.zip | |
26.235 | Packet switched conversational multimedia applications; Default codecs | TS | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-410.zip | The present document introduces the set of default codecs for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document is applicable, but not limited, to services such as PS video telephony and Push to talk over Cellular (PoC) as well as Combined CS and IMS services (CSI). For Multimedia Telepphony Service for IMS (MTSI), all media handling, including codecs, is defined in TS 26.114 [50]. This specification does not apply for MTSI.
The applicability of this specification to GERAN is FFS. |
26.920 | Architectural Model for the 3G Transcoders | TR | 0.1.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.920/26920-011.zip | The present document is a description of the transcoder in the UMTS networksl. The initial aim of this document is to have a reference model for the standardization work carried out by the 3GPP Technical Specification Groups. |
30.002 | Guidelines for the modification of the Mobile Application Part (MAP) | TR | 4.0.1 | N4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.002/30002-401.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. |
30.504 | Work Plan and Study Items - RAN WG4 | TR | 2.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.504/30504-220.zip | |
30.801 | Overall Project Plan | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.801/30801-110.zip | |
30.802 | Project plan on Bearer Services and QoS | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.802/30802-400.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. |
32.104 | Telecommunication management; 3G Performance Management | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.104/32104-400.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.105 | 3G charging and billing; Stage 2 description | TS | 0.0.4 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.105/32105-004.zip | This Technical Specification describes the Architecture, Principals and Call Event specifications of charging and billing for the provision of service and services by a 3G system.
This standard is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. This standard will elaborate on the charging requirements described in the Charging Principles in UMTS 22.01 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
The call and event data generated by the network elements of the 3G network, is 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 and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as historical evidence in dealing with customer service and billing complaints;
In addition to the information collected from these network elements, network management functions are required for the administration of charging data.
For the purpose of the present document, the call and event data is considered to be collected, in real-time, by network element function (NEF) blocks located within the recording entities.
The data collected by the NEFs is sent to, or collected by, the appropriate Operations System Function (OSF) blocks for storage and further processing.
The location of the OSF is implementation specific and may, for example, be provided either by an Administration Centre (ADC) or integrated within the network elements themselves.
The following is beyond the scope of this TS, and therefore this TS does not describe:
-
The objectives of this standardisation are:
• to provide the descriptions of events and triggers for the generation of Call detail records;
- to provide the descriptions for Call and event Call detail records;
- to produce a description of the collection techniques for accounting administration and CDR generation;
and
- to define a method for the transmission of CDRs over an open interface. |
32.106-1 | Telecommunication management; Configuration Management (CM); Part 1: Concept and requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-1/32106-1-400.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.106-8 | Telecommunication management; Configuration Management (CM); Part 8: Name convention for Managed Objects | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-8/32106-8-400.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.111 | 3G Fault Management | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111/32111-400.zip | The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardisation of these functions across the different vendors' equipment is not required. The functional areas to be specified in this part of the document cover:
• fault surveillance and detection in the NEs;
• notification of alarms (including alarm cease) and operational state changes;
• retrieval of current alarms from the NEs;
• fault isolation and defence mechanisms in the NEs;
• alarm filtering;
• management of alarm severity levels;
• alarm and operational state data presentation and analysis at the OS;
• retention of alarm and operational state data in the NEs and the OS; and
• the management of tests.
Any (re)configuration activity exerted from the OMC as a consequence of faults will not be subject of the present document, these are described in [1].
Clauses 6 and 7 of the present document describe specific aspects of the Fault Management for the UTRAN and the CN, respectively, with particular emphasis on the exact fault definitions and alarm information to be generated. The definition of the test procedures and the relationship with the UTRAN resp. CN management architecture as defined in [3].
Finally, Clause 8 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3G networks, as seen from the Network Manager (NM). The Itf-N is fully standardised so as to connect systems of any vendor to the NM via this interface. |
32.301-4 | Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point: Common Management Information Protocol (CMIP) solution | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-4/32301-4-200.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 3G TS 32.301-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 Notification Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5. |
32.301-3 | Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-3/32301-3-200.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 [5]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.