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
22.98
Network composition feasibility study
TR
1.0.0
S1
https://www.3gpp.org/ftp/Specs/archive/22_series/22.98/2298-100.zip
22.982
Study of Customised Alerting Tone (CAT) requirements
TR
0.3.0
S1
https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-030.zip
23.125
Overall high level functionality and architecture impacts of flow based charging; Stage 2
TS
7.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.125/23125-700.zip
23.259
Personal Network Management (PNM); Procedures and information flows; Stage 2
TS
0.4.0
C1
https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-040.zip
23.803
Evolution of policy control and charging
TR
7.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.803/23803-700.zip
The present document intends to study the following items: 1) Complete harmonization and merger of the policy control and flow based charging architecture and procedures; 2) Possible architectures and solutions for adding end-user subscription differentiation and general policy control aspects to the policy- and charging control; 3) Alternative solutions for binding bearers to services (provided today by the authorization token). This includes studying solutions for the network to control bearer usage by service flows. Editors Note: The document may also study the impact on policy control and flow based charging architecture based on the conclusion and approved recommendations of the E2E QoS Work Item in a Release 7 context if deemed feasible.
23.805
Selective disabling of User Equipment (UE) capabilities; Report on technical options and conclusions
TR
0.3.1
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.805/23805-031.zip
The present document presents an assessment of different service architecture implementations for the new Selective Disabling of UE Capabilities specified in TS 22.011, Section 4.5. For each service architecture the document provides: • A detailed description of the architecture • An assessment of the architecture against the SA1 requirements described in TS 22.011, Section 4.5. • An assessment of the architecture’s strengths and weaknesses The document provides a conclusion identifying the preferred service architecture of the SA2 TSG.
23.807
Feasibility study for enhancement of radio performance for Voice over IP Multimedia Subsystem (VoIMS); Report on technical options and conclusions
TR
0.3.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.807/23807-030.zip
The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain. Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC. Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data. Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR.
23.808
Supporting Globally Routable User Agent URI in IMS; Report and conclusions
TR
1.0.1
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.808/23808-101.zip
The present document is a temporary container for the architectural impacts on IM CN subsystem for supporting GRUU. The contents of this report when stable will be the base for CRs to 3GPP Technical Specifications e.g. TS 23.228 [2]. GRUU is a URI, the creation and use of which is defined in an IETF specification draft-ietf-sip-gruu-0 [1] in order to route SIP messages to a specific SIP User Agent (UA) instance. The support of GRUU in IMS is to enable routing of SIP messages to a specific instance of a registered public user identity even when a single public user id is registered from multiple UEs.
23.809
One Tunnel solution for Optimisation of Packet Data Traffic
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.809/23809-100.zip
The present document is a temporary container for a stage-2 like description of an architecture that uses direct tunnelling of user plane data between the RNC and the GGSN, which is known as One Tunnel approach. The content of this report when stable will be moved into 3GPP Technical Specification TS 23.060 [1]. This report will further develop the One Tunnel approach described in TR 23.873 [2] and identify what changes are needed to PS core and potentially to UTRAN functionalities and protocols to support the One Tunnel functionality. This include the investigation of the functions added after Rel‑4 up to Rel‑6 (e.g. Iu-flex, Network sharing, MBMS, etc) and either verify that they are not affected or address any conflicts between these functions and the One Tunnel function. The resulting system architecture shall be fully interoperable with pre-Rel‑7 nodes and it should retain the existing network capabilities, or those that cannot be delivered need to be clearly documented.
23.817
Feasibility study on enhancement of radio performances for Voice over IMS (VoIMS); Report on Technical options and conclusions
TR
0.1.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.817/23817-010.zip
The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain. Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC. Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data. Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR.
23.818
Optimisations and Enhancements for Realtime IMS Communication
TR
0.10.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.818/23818-0a0.zip
The scope of the technical report is to capture the results of a study into the optimisations and enhancements of the system for mass market real-time communication (IMS multimedia telephony). The objective is to provide a study into optimisations and enhancements for the support realtime services based on IMS with regards to the following aspects: - Analysis of IMS session establishment procedures (e.g. signalling flows, bearer establishment) in order to reduce call establishment time for multimedia telephony to obtain the same, or at least similar, characteristics as exists for CS telephony; - Analysis of impacts of any non call related IMS signalling (e.g. due to Presence) on the efficiency and service aspects of active real time communication sessions and the establishment of such sessions; - Analysis into mechanisms to inform the IMS of loss of the signalling bearer transport through the IP-CAN; - Analysis and identification of architecture and information flow impacts due to the dynamic allocation of users to Application Servers, including analysing any potential impacts at initial registration, session establishment and provision of user data in the HSS; - Identification of any stage 2 impacts in order to support multimedia telephony services; - Efficient interworking with other VoIP networks, e.g. regarding call establishment time and simplified call flows. The study is intended to provide conclusions on the above aspects with respect to future normative specification work.
23.819
Terminating session handling
TR
1.3.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.819/23819-130.zip
3GPP has specified how to combine CS call and IMS Sessions but has not yet addressed the interworking between e.g. a pure IMS voice/video session and a combination of a CS call and an IMS session. The present document studies how to handle terminating real-time sessions and calls taking into account different domains (CS, IMS) and different UE capabilities (CSI, IMS VoIP, etc.).
23.836
Quality of Service (QoS) and policy aspects of 3GPP - Wirless Local Area Network (WLAN) interworking
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.836/23836-100.zip
Some 3GPP PS based services (e.g. VoIP over IMS, PS streaming, etc) require strict QoS provisioning. In order to support such services over I-WLAN, QoS Provisioning in 3GPP-WLAN Interworking is required. IEEE 802.11 WLAN standards are currently not supporting QoS mechanisms, therefore QoS provisioning was not considered in Rel-6 work for 3GPP-WLAN Interworking. As IEEE is currently finalizing QoS amendments to 802.11 WLAN standards, QoS-related aspects of the 3GPP-WLAN architecture should be studied. In the context of end-to-end QoS provisioning being studied in TR 23.802, provisioning of QoS within I-WLAN as an IP-CAN is important. It shall be defined if and how QoS provisioning in I-WLAN can interact with the end-to-end QoS framework. Flow based charging and service/subscription based policy control are studied in TR 23.803 as generic features to support the access to PS based services from different IP-CANs. In order to leverage the generic charging and service/subscription based policy control within I-WLAN as another IP-CAN, the Gateway element in case of 3GPP-WLAN Interworking has to provide the needed functionalities, e.g. for Policy Enforcement. The followings are objectives of the document. - investigate the necessity and reliability of the applicable QoS mechanism between the WLAN UE and PDG, and the possible impacts to the 3GPP-WLAN interworking entities; - ensure that the architecture for 3GPP/WLAN Interworking defined by TS 23.234 is supported by the following QoS-related mechanisms being developed in 3GPP: a. E2E QoS architecture being studied in TR 23.802; b. Policy and charging evolution capabilities being studied in TR 23.803.
23.837
Location Services (LCS) architecture for 3GPP system - Wireless Local Area Network (WLAN) interworking
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.837/23837-100.zip
The present document investigates solutions for providing LCS over 3GPP WLAN interworking architecture. The architectural requirements and different possible LCS architectures to provide the location services over I-WLAN are analyzed. The procedures to obtain the location information of a WLAN UE attached to I-WLAN network are also studied. The LCS aspects for I-WLAN as IP-CAN in the IMS Emergency call, i.e., the emergency location information handling for I-WLAN are described in this TR.
23.847
Enhancements to IMS service functionalities facilitating multicast bearer services
TR
0.2.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.847/23847-020.zip
23.882
3GPP system architecture evolution (SAE): Report on technical options and conclusions
TR
1.15.1
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.882/23882-1f1.zip
24.259
Personal Network Management (PNM); Stage 3
TS
0.6.2
C1
https://www.3gpp.org/ftp/Specs/archive/24_series/24.259/24259-062.zip
24.88
Media server control using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3
TR
1.4.0
C1
https://www.3gpp.org/ftp/Specs/archive/24_series/24.88/2488-140.zip
25.812
Requirements for evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN)
TR
0.0.0
RP
https://www.3gpp.org/ftp/Specs/archive/25_series/25.812/25812-000.zip
This document is related to the technical report for the study item “Evolved UTRA and UTRAN” [1]. The objective of the study item is to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data-rate, low-latency and packet-optimized radio access technology. This document provides guidance and collects requirements which an evolved UTRA and UTRAN system should meet.
25.819
7.68 Mcps TDD option: Layer 2 and 3 protocol aspects
TR
1.0.0
R2
https://www.3gpp.org/ftp/Specs/archive/25_series/25.819/25819-100.zip
The present document identifies RAN2 the specifications impacted by the introduction of 7.68 Mcps TDD. It describes the various options for implementing the 7.68 Mcps TDD option in specifications and presents a brief description of the decisions and changes agreed.
25.904
Improved support of gaming over HSDPA/EDCH
TR
0.0.2
R2
https://www.3gpp.org/ftp/Specs/archive/25_series/25.904/25904-002.zip
This document is related to the technical report for physical layer aspect of the study item “Evolved UTRA and UTRAN” [1]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, along with the complexity evaluation of each technique. This activity involves the Radio Access 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 gains vs. complexity, and draw a conclusion on way forward. This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. The purpose of this TR is to help 3GPP TSG RAN WG2 define, describe and improve the support for gaming using HSDPA/HSUPA (HS-DSCH/E-DCH), focusing on minimizing delay and the service interruption time in case of handover. The latency of radio, core network, and terminals should be included in this TR with evaluations of the various complexity issues affecting both real time gaming (such as RT Shooting and RT auto racing) and less than real time gaming (such as chess and other less demanding gaming). Inclusion of 2 way RT gaming plus 2 way synchronized voice should also be included in this TR. All evaluations shall include complexity analysis and any end-user complexities and relevant issues. The activity involved in this TR involves both Radio Access and has impacts that include Radio Access Network and Mobile Equipment. This TR is intended to work in conjunction with other WI’s that are currently employed in reducing the latency of the radio network. The conclusion of this work item shall be CR’s that will be presented to RAN WG2 and other WG’s
26.967
eCall data transfer; In-band modem solution
TR
0.1.1
S4
https://www.3gpp.org/ftp/Specs/archive/26_series/26.967/26967-011.zip
29.14
Multimedia Messaging Service (MMS); MM10 interface based on Diameter protocol; Stage 3
TS
7.0.0
C4
https://www.3gpp.org/ftp/Specs/archive/29_series/29.14/2914-700.zip
30.301
3.84 Mcps TDD enhanced uplink: RAN WG2 Stage 2 decisions
TR
0.2.0
R2
https://www.3gpp.org/ftp/Specs/archive/30_series/30.301/30301-020.zip
This document is a Technical Report which captures the Stage 2 decisions on the support of 3.84 Mcps TDD Enhanced Uplink in UTRA.
32.153
Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines
TS
0.3.1
S5
https://www.3gpp.org/ftp/Specs/archive/32_series/32.153/32153-031.zip
32.403
Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM
TS
7.1.0
S5
https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-710.zip
32.807
Telecommunication management; Project scheduling and open issues for SA5, Release 7
TR
0.0.3
S5
https://www.3gpp.org/ftp/Specs/archive/32_series/32.807/32807-003.zip
The purpose of this document is to contain the updated Work Item Descriptions (WIDs) and capture status of all TSG SA WG5 work items of the current 3GPP Release in order for the group to get an overview of current ongoing work. This TR is used as a mean to provide input to the complete 3GPP work plan that is handled by MCC.
32.808
Telecommunication management; Study of Common Profile Storage (CPS) Framework of User Data for network services and management
TR
2.0.0
S5
https://www.3gpp.org/ftp/Specs/archive/32_series/32.808/32808-200.zip
33.2
3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security
TS
7.0.0
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.2/332-700.zip
33.223
Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function
TS
0.5.0
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-050.zip
33.801
Access security review
TR
1.0.0
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.801/33801-100.zip
33.802
Feasibility study on IMS security extensions
TR
0.2.0
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.802/33802-020.zip
Editor’s Note: The current version of this document represents the state of discussion in 3GPP SA3 after meetings #39 and #40. It consists of a compilation of input documents to SA3 #39 and SA3 #40. The annexes describe solutions proposed for signalling protection for fixed broadband access to IMS. They are based on input documents to SA3 #39 and SA3 #40 (S3-050402, S3-050539, S3-050571). Section 5 (Analysis) represents the contents of the analysis contributions discussed (S3-050333, S3-050372, S3-050427, S3-050570). The current text in section 5 is not endorsed by SA3 at this point of time. The scope of the present document is to study security requirements and solutions related fixed broadband access to IMS. Both solutions for ETSI TISPAN NGN R1 and ETSI TISPAN NGN R2 need to be studied. Based on this document, solutions to meet the fixed broadband access security needs are to be specified in TS 33.203 within the time frame of NGN R1 and NGN R2.
33.828
IP Multimedia Subsystem (IMS) media plane security
TR
0.8.1
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.828/33828-081.zip
33.923
Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function
TR
0.0.1
S3
https://www.3gpp.org/ftp/Specs/archive/33_series/33.923/33923-001.zip
43.935
Feasibility study of enhanced support for video telephony service over GERAN via the A interface
TR
0.4.0
G1
https://www.3gpp.org/ftp/Specs/archive/43_series/43.935/43935-040.zip
The present document provides an overview of the possible enhancements to the circuit switched vide telephony service in GERAN.
50.099
GERAN project plan and open issues
TR
0.55.0
GP
https://www.3gpp.org/ftp/Specs/archive/50_series/50.099/50099-005500.zip
21.877
Radio optimization impacts on the Packet Switched (PS) domain architecture
TR
0.7.0
S2
https://www.3gpp.org/ftp/Specs/archive/21_series/21.877/21877-070.zip
22.976
Study on PS domain services and capabilities
TR
2.0.0
S1
https://www.3gpp.org/ftp/Specs/archive/22_series/22.976/22976-200.zip
23.127
Virtual Home Environment (VHE) / Open Service Access (OSA)
TS
6.1.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.127/23127-610.zip
23.241
3GPP Generic User Profile (GUP); Stage 2; Data Description Method (DDM)
TS
6.1.0
N4
https://www.3gpp.org/ftp/Specs/archive/23_series/23.241/23241-610.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.801
Potential mechanisms for Circuit Switched (CS) domain video and voice service improvements
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.801/23801-100.zip
This TR studies different mechanisms which might permit 3GPP based systems to rapidly enhance their customers Circuit Switched Videotelephony experience. Many operators regard circuit video services as a key part of UMTS. However there is a strong desire to have an effective and user friendly method of switching between voice and video services when the user desires and/or when radio conditions change and video mode is no longer available. There are several situations where swapping between video and voice calls is needed. Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included.
23.825
Overall architecture aspects of IP flow based bearer level charging; Stage 2
TR
1.4.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.825/23825-140.zip
The present document identifies the overall architecture aspects of IP flow based bearer level charging. It is expected that the content of this TR will act as a basis for: - Change requests against the architecture specifications [5] of SA2, clarifying the architecture implications of IP flow based bearer charging - Change requests against the Charging Principles specification [3] of SA5, which contains the charging architecture and mechanisms.
23.835
Study into applicability of Galileo in Location Services (LCS)
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.835/23835-100.zip
Based on the March 2003 GALILEO system definition, in the present document, as proposed in [1]: • the potential benefits of using Galileo (alone or combined with GPS) on service performance: in particular the availability improvements for in urban/indoor environment are highlighted. • the expected complexity differential between 3GPP mobiles utilizing A-GPS and those that might utilize a combination of A-GPS plus “Assisted GALILEO” is described. • the changes that might be needed to 3GPP standards to support “assisted Galileo” in addition or in combination with the currently specified assisted GPS are identified • from the 3GPP community point of view, the desirable characteristics of GALILEO that would minimize the impact to 3GPP mobiles when introducing the extension of A-GPS techniques to GALILEO are proposed. These informations will allow 3GPP to decide whether or not to initialise 3GPP standard changes to introduce GALILEO. The final 3GPP standard modifications should be reassessed against the final GALILEO definition.
23.864
Commonality and interoperability between IP Multimedia System (IMS) core networks
TR
0.6.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.864/23864-060.zip
The present document defines the key architectural items that are the building blocks for achieving commonality and interoperability between IMSs that possibly use different IP Connectivity Networks. Specific IP-connectivity access network technologies and their details are not within the scope of the present document.It is expected that one solution will be developped and finetuned for each of these architectural items. The present Technical Report serves as a placeholder for the solutions under development. When the solution reaches maturity, Change Requests against the relevant Technical Specifications will be raised.
23.867
Internet Protocol (IP) based IP Multimedia Subsystem (IMS) emergency sessions
TR
0.9.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.867/23867-090.zip
23.876
Push architecture
TR
0.5.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.876/23876-050.zip
This technical report defines methods for supporting push services by 3GPP bearers. The mechanisms defined apply to existing bearers for the 3GPP Packet Switched Domain (PS domain), Circuit-Switched Domain (CS Domain), and the IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast Multicast Service, and Wireless LAN. This technical report addresses the requirements for supported push services as defined in 3GPP TS 22.174 Push Service; Service aspects (Stage 1). Any necessary changes identified during this work will be introduced by means of CRs to the appropriate specifications. Definition of push functions that apply to push application servers is outside the scope of this work. The definition of push functions that are best implemented in push application servers such as a Push Proxy and Push Initiator will be undertaken by other standards bodies and industry forums.
23.881
Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.881/23881-100.zip
The present document studies study interworking and migration scenarios related to IPv4 based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4 based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6.
23.898
Access Class Barring and Overload Protection (ACBOP)
TR
1.3.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.898/23898-130.zip
23.899
Combining Circuit Switched (CS) bearers with IP Multimeida Subsystem (IMS)
TR
1.2.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.899/23899-120.zip
The present document investigates architectural requirements and architectural alternatives for using existing CS bearers in association with an IM session. The document considers overall requirements, architectural requirements, considerations for evaluation of potential architectural solutions and proposed alternative architectures. The Feasibility Study covers different solutions for offering existing IMS simultaneous services (real-time media + non-real-time media) also in GERAN, where conversational PS spectrum efficiency is too low. The target is to seek for an architectural solution that is completely transparent for the end-user, and is easily interoperable with existing IMS services&networks that don’t use this solution. The solutions studied within the Feasibility Study are not necessarily restricted by existing service requirements. However, if an alternative is chosen to be included in specifications, it must be cross-checked with existing service requirements.
23.917
Dynamic policy control enhancements for end-to-end Quality of Service (QoS)
TR
1.2.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.917/23917-120.zip
23.934
3GPP system to Wireless Local Area Network (WLAN) interworking; Functional and architectural definition
TR
1.0.0
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.934/23934-100.zip
Editor’s note : Identify and analyse possible system architectures for allowing WLAN based radio networks to Interwork with 3GPP based systems.
23.964
Commonality and interoperability between IP Multimedia System (IMS) core networks
TR
0.3.1
S2
https://www.3gpp.org/ftp/Specs/archive/23_series/23.964/23964-031.zip
The present document defines the key architectural items that are the building blocks for achieving commonality and interoperability between IMS core networks that possibly use different IP Connectivity Networks. Specific IP-connectivity access network technologies and their details are not within the scope of the present document.It is expected that one solution will be developped and finetuned for each of these architectural items. The present Technical Report serves as a placeholder for the solutions under development. When the solution reaches maturity, Change Requests against the relevant Technical Specifications will be raised.
24.241
3GPP Generic User Profile (GUP) Common objects; Stage 3
TS
0.5.0
C4
https://www.3gpp.org/ftp/Specs/archive/24_series/24.241/24241-050.zip
This specification serves as a vessel for storing and listing new DatatypesProfiles, Generic User Profile Component Groups, Profile Components, Datatypes,Fragments, and other constructs for use in 3GPP applications within various specifications, thereby serving as a means to manage the process of adding new entities of these typesDatatypes, Generic User Profile Fragments, and other constructs The present document defines the stage three description to the 3GPP Generic User Profile (GUP) Common Objects. This document serves as a vessel to manage the process for addition of new Datatypes, Generic User Profile Group Components Fragments, Common Profile Components, and other constructs for use in 3GPP applications within various specifications. 3GPP GUP architecture, storage, distribution, ownership, etc are included in [11] and [12]. […]
25.802
Remote control of electrical tilting antennas
TR
6.0.0
R3
https://www.3gpp.org/ftp/Specs/archive/25_series/25.802/25802-600.zip
The present document is for the Release 6 work item "Remote Control of Electrical Tilting Antennas" (see [1]). The objectives of this work item are the specification of a standardised open interface to enable local RET antenna-controlling functionality situated in the Node B to allow the RET antenna system being provided by a third party vendor and to enable the control of the antenna from the Network Manager, so that the operator is able to control the RET antenna remotely and consistently across the network. The purpose of the present document is to record the required changes of the specifications and 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 a solution for the remote control of electrical tilting antennas is sufficiently stable, the needed CRs can be issued. Therefore, 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.805
DS-CDMA introduction in the 800 MHz band
TR
1.0.0
R4
https://www.3gpp.org/ftp/Specs/archive/25_series/25.805/25805-100.zip
This document is a technical report of the DS-CDMA Introduction in the 800 MHz Band work items. The purpose of these work items is to provide UMTS specification support for UTRA/FDD in the 800 MHz (ITU region 3, Japan). In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, 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.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
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
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
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
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.173
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TS
1.0.0
S5
https://www.3gpp.org/ftp/Specs/archive/32_series/32.173/32173-100.zip
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
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
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
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
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
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.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
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
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
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
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
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
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
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
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.