id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
32.644
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-630.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.642 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.642 V6.4.X.
|
32.654
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.654/32654-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.652 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.652 V6.0.X.
|
32.664
|
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.664/32664-620.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Kernel Configuration Management IRP: Information Service defined in 3GPP TS 32.662 [7]. 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 Kernel Configuration Management IRPover the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.662 V6.3.X.
|
32.674
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.674/32674-610.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the State Management IRP: Information Service defined in 3GPP TS 32.672 [6]. 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 State Management IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set is related to 3GPP TS 32.672 V6.0.X [6].
|
32.714
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) 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.714/32714-600.zip
|
The purpose of this Transport Network (TN) interface Network Resource Model IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.712 [4]) to the protocol specific details necessary for implementation of this IRP in a Q3 environment.
This Solution Set specification is related to 3GPP TS 32.712 V6.0.X
|
32.744
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.744/32744-610.zip
|
The purpose of this STN Network Resources IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.742 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V6.0.X.
|
32.803
|
Telecommunication management; Process guide; Use cases in Unified Modelling Language (UML)
|
TR
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.803/32803-600.zip
|
The present document is a guide for developing subscription management requirements in the form of use cases.
The present document is used to allow use case process information to be removed from 3GPP TS 32.140 on "Telecommunication management; Subscription Management (SuM) Requirements". It is intended that this applies only to the Subscription Management (SuM) work item in Release 6.
|
32.804
|
Telecommunication management; Control of Remote Electrical Tilting (RET) antennas; Requirements
|
TR
|
6.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.804/32804-620.zip
|
The present document defines the requirements for the network wide control of RET antennas via the Itf-N.
Two example types of RET antennas are those that are tilted using a mechanical tilting mechanism and those that use a phased array.
The control of RET antennas has been studied in 3GPP RAN3 with an approved work item for “Remote Control of Electrical Tilting Antennas” provided in RP-030193 at RAN#19 in March 2003, producing TR 25.802 [1].
The RET control mechanism makes use of the Iuant interface, which is defined in the following set of specifications for General Aspects and Principles [8], Layer 1 [9], Signalling Transport [10], and Remote Electrical Tilting (RET) Antennas Application Part (RETAP) Signalling [11].
The ability to control Antenna tilt permits cell size to be adjusted, thereby permitting control of up and downlink throughput.
The ability to control Antenna tilts remotely from a network management system permits a network wide perspective to be obtained and for settings to be adjusted in response to predicted population movements, or in response to performance monitoring data to help make the best use of the available radio access network.
Figure 1 shows the main Network Elements (NEs) and depicts the two system contexts A and B where the IRPagent may be located either in the Element Manager (EM), or within the Network Element (NE).
Figure 1
|
32.805
|
Telecommunication management; Process guide; Backward compatibility recommendations
|
TR
|
6.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.805/32805-600.zip
|
The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
Clause 2 provides the list of references. Clause 3 provides the definitions and abbreviations used in the document. Clause 4 specifies the Recommendations. Clause 5 describes the system context where the Recommendations are applicable.
|
32.815
|
Telecommunication management; Charging management; Online Charging System (OCS) architecture study
|
TR
|
6.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.815/32815-610.zip
|
The present document analyses the architectures and functions of the OCS and thereby derives the functionality of the OCS reference points. It is expected that the content of the present document will serve as a basis for detailed 3GPP specifications of reference points between the logical OCS functionalities. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
|
33.200
|
3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security
|
TS
|
6.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.200/33200-610.zip
|
This technical specification covers the security mechanisms and procedures necessary to protect the MAP protocol. The complete set of enhancements and extensions to facilitate security protection for the MAP protocol is termed MAPsec and it covers transport security in the MAP protocol itself and the security management procedures.
The security mechanisms specified for MAP are on the application layer. This means that MAPsec is independent of the network and transport protocols to be used.
This technical specification contains the stage-2 specification for security protection of the MAP protocol. The actual implementation (stage-3) specification can be found in the MAP stage-3 specification, TS 29.002 [4].
NOTE: It is explicitly noted that automated key management and key distribution is not part of Rel‑5. All key management and key distribution in Rel‑5 shall therefore be carried out by other means (see Annex A).
|
33.810
|
3G Security; Network Domain Security / Authentication Framework (NDS/AF); Feasibility Study to support NDS/IP evolution
|
TR
|
6.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.810/33810-600.zip
|
The scope of this feasibility study is limited to authentication of network elements which are using NDS/IP, and located in the inter-operator domain.
It means that this study concentrates on authentication of Security Gateways (SEG), and the corresponding Za‑interfaces. Authentication of elements in the intra-operator domain is considered as an internal issue for the operators. This is quite much in line with [6] which states that only Za is mandatory, and that the security domain operator can decide if the Zb-interface is deployed or not, as the Zb-interface is optional for implementation.
However, NDS/AF can easily be adapted to intra-operator use. This is just a simplification of the inter-operator case as all NDS/IP NEs and the PKI infrastructure belong to the same operator. Validity of certificates may be restricted to the operator's domain.
This work might also later be extended to provide entity authentication services to non-control plane nodes, but this has not been studied.
Possible use of multi-purpose PKI solutions (e.g. providing end-user security) for NDS/AF has not been studied. On the contrary, it is recommended to use a dedicated and profiled PKI for NE authentication in NDS/IP. Different applications make different demands on a PKI and it may make sense to build a lightweight PKI for each purpose rather than to build one that solves all problems. Complexity is one of the main impediments to PKI deployment today [11].
The NDS architecture for IP-based protocols is illustrated in figure 1.
Figure 1: NDS architecture for IP-based protocols [6]
|
33.817
|
Feasibility study on (Universal) Subscriber Interface Module (U)SIM security reuse by peripheral devices on local interfaces
|
TR
|
6.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.817/33817-610.zip
|
This Feasibility Study report conducts a threat analysis and determines the feasibility of Reuse of a Single 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. This Feasibility Study may be used as a basis for future CRs to TS 33.234 as and when any of the proposals are developed by SA WG3.
|
34.121
|
Terminal conformance specification, Radio transmission and reception (FDD)
|
TS
|
6.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-640.zip
|
The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself.
|
45.811
|
Uplink - Time Difference Of Arrival (U-TDOA) in GSM and GPRS
|
TR
|
6.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.811/45811-600.zip
|
The following document describes how the Uplink Time Difference Of Arrival (U-TDOA) location method works in GSM and GPRS environments.
|
49.001
|
General network interworking scenarios
|
TR
|
6.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/49_series/49.001/49001-601.zip
|
The present document serves as an introduction to the GSM 09.xx‑series.
In clause 4, the technical requirements for Public Land Mobile Network (PLMN) interworking are introduced, and in clause 5 there is a summary of the contents of the GSM 09.xx‑series.
|
51.010-3
|
Mobile Station (MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS)
|
TS
|
6.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-3/51010-3-630.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, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI (the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
The present document is valid for MS implemented according GSM Phase2 or Phase2+ R96, or R97, or R98, or R99, or 3GPP Release 4, or Release 5.
The test suite in the current document is an example of TTCN implementation, and is not intended for direct use in formal conformance testing.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications.
|
22.048
|
Security mechanisms for the (U)SIM application toolkit; Stage 1
|
TS
|
5.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.048/22048-500.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a 3G or GSM PLMN Entity and a UICC.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (TS 23.048).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
Within the scope of this document, the UICC refers here to a ICC which support at least one application in order to access a cellular network.
The ICC is considered as a platform, which is either based on TS 31.101 [13], here called "3G platform", or TS 51.011 [23], here called "2G platform".
|
22.121
|
Service aspects; The Virtual Home Environment (VHE); Stage 1
|
TR
|
5.3.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.121/22121-531.zip
|
The present document specifies the content of the Stage 1 requirement for realisation of VHE.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
|
23.039
|
Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs)
|
TR
|
5.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-500.zip
|
The present document describes a range of alternative interfaces which may be utilised by Short Message Service Centre (SMSC), and Short Message Entity (SME), developers for the connection of SMEs to SMSCs.
The purpose of the present document is to provide a single document within which the various proprietary SMSC to SME interface standards may be accommodated as optional implementations.
As stated in 3GPP TS 23.040 [1], the functionality of the SMSC is outside of the scope of the 3GPP Technical Specifications. As a result, no standardised interfaces have been specified for the connection of SMEs to the SMSC. In the absence of a prevailing standard, SC (Service Centre), developers have devised their own protocols which have not necessarily been based on any existing standards and are therefore largely incompatible with one another.
This document by referring to the various de-facto protocols will limit the further proliferation of proprietary standards and will benefit new SC/SME developers who may then adopt one or more of the existing protocols outlined in the present document.
This document does not provide recommendations, as to the preferred protocol implementation as all are regarded as being of equal merit. SC/SME implementors should therefore adopt the protocol most suited to their particular implementation, application or market.
|
23.048
|
Security mechanisms for the (U)SIM application toolkit; Stage 2
|
TS
|
5.9.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.048/23048-590.zip
|
The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in 3GPP TS 51.011 [5] and allows remote management of files on the UICC in conjunction with SMS and the Data Download to UICC feature of 3GPP TS 31.111.
For UICCs based on 3GPP TS 43.019 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For UICCs based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the UICC.
Secured Packets contain application messages to which certain mechanisms according to 3GPP TS 22.048 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the UICC. The Sending/Receiving Entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
23.127
|
Virtual Home Environment (VHE) / Open Service Access (OSA)
|
TS
|
5.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.127/23127-520.zip
|
The present document specifies the stage 2 of the Virtual Home Environment.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
For Release 5, e.g. CAMEL, MExE, OSA and USAT are considered the mechanisms supporting the VHE concept.
Stage 2 specifications for CAMEL, MExE and USAT are addressed in other documents [1], [2], [3]. However, there is no separate stage 2 specification document for OSA. Therefore, the present document addresses stage 2 aspects for OSA.
|
23.195
|
Provision of User Equipment Specific Behaviour Information (UESBI) to network entities
|
TS
|
5.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.195/23195-540.zip
|
The present document defines the stage-2 description of the mechanism to provide the 3GPP network entities with UE Specific Behaviour Information (UESBI). UESBI may be used by correcting mechanisms to overcome some of the issues that have been recognized by 3GPP in TR 25.994 (Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults) [13], and other such documents. The description of these correcting mechanisms is out of the scope of this TS.
ITU-T Recommendation I.130 [1] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [2] defines stage 2 of the method.
|
23.227
|
Application and user interaction in the User Equipment (UE); Principles and specific requirements
|
TS
|
5.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.227/23227-510.zip
|
The present document defines the principles for scheduling UE resources and controlling UE interactions and resolving conflicts between independently running applications in different application execution environment (e.g. MExE, USAT etc.) and internal and external peripherals (e.g. infra-red, Bluetooth, USIM, radio interface, MMI, memory etc.).
The present document is divided in two parts: clause 4 defines a framework for event handling. Clause 5 addresses some specific issues.
Annex A contains an informative background to the problem area.
|
23.815
|
Charging implications of IMS architecture
|
TR
|
5.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.815/23815-500.zip
|
The present document identifies the charging implications of the IMS architecture, which is described in 23.002 [5] and 23.228 [4].
It is expected that the content of this TR will act as a basis for:
- change requests against the architecture specifications [4, 5] of SA2, clarifying the architecture implications on charging;
- change requests against the Charging Principles specification [3] of SA5, which contains the charging architecture and mechanisms;
- detailed specification of Charging Data Description [6] in SA5.
|
23.871
|
Enhanced support for user privacy in Location Services (LCS)
|
TR
|
5.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.871/23871-500.zip
| |
23.873
|
Feasibility study for transport and control separation in the PS CN domain
|
TR
|
2.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.873/23873-200.zip
|
The scope of this Technical Report (TR) is to capture the results of a feasibility study on how to introduce a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference logical architecture for R’00.
With this separation in view, functional elements of the PS CN domain that provide both significant control and transport functions may be decomposed into two separate functional entities: one entity taking care of the control functionality and an other entity handling the payload transport. An exact distribution of the functions currently supported by a single functional entity between new functional entities and other network entities will be defined as the result of this feasibility study, if necessary.
A standard control protocol should be used between the control and transport entities, if applicable, e.g. H.248. The required functionality, e.g. extensions to H.248 or any other protocol which may be chosen for this task, would have to be defined and standardised within 3GPP. This TR will identify and define these extensions, and extensions to other interfaces if applicable.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the PS CN domain. At the end of the feasibility study, the remaining open issues will be reported and their importance will be assessed. An analysis of the benefits and drawbacks of separating the control and transport functions in the PS CN domain will also be performed.
|
23.875
|
Support of Push service
|
TR
|
5.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.875/23875-510.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.910
|
Circuit switched data bearer services
|
TR
|
5.5.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.910/23910-550.zip
|
The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
24.228
|
Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
|
TS
|
5.15.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.228/24228-5f0.zip
|
The present document gives examples of signalling flows for the IP multimedia call control based on SIP and SDP.
These signalling flows demonstrate the interaction with the IP-connectivity network (GPRS), and with the protocol provided at the Cx interface.
These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228 [2].
NOTE: The detailed signalling flows in the present document can be referenced, but the specification will not be further maintained. The example flows can contain errors and can only be regarded as guidelines for persons wanting an overview of how SIP messages with detailed header information could in some example cases look like within 3GPP. Other not documented signalling flows can be as relevant and compliant as the ones that are outlined in this specification.
|
25.854
|
Uplink Synchronous Transmission Scheme (USTS)
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.854/25854-500.zip
|
The present document describes the techniques behind the concept of uplink synchronous transmission scheme and how this concept should be integrated into the overall architecture of UTRA. It also deals with the feasibility of USTS, including performance and expected complexity.
|
25.858
|
Physical layer aspects of UTRA High Speed Downlink Packet Access
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.858/25858-500.zip
|
The purpose of this document is to capture the agreements and evaluation criteria of the different techniques being considered for HSDPA with regards to the overall support of UTRAN for HSDPA.
|
25.859
|
User Equipment (UE) positioning enhancements for 1.28 Mcps TDD
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.859/25859-500.zip
|
The present document identifies and describes UE positioning methods for use with the 1.28 Mcps TDD option and methods for their enhancements. It should provide the basis for the evaluation and comparison of these methods. The report covers the impact of the positioning methods and their potential enhancements on the layer 1 and UTRAN interfaces.
Change Requests to affected specifications should be created based on this TR.
|
25.860
|
Radio acces bearer support enhancements
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.860/25860-500.zip
|
The present document is a technical report that summarises the work on the UTRAN Release 5 work item "Radio Access Bearer Support Enhancements". The work items comprises of two areas of study:
1) Robust header compression
2) SRNS context relocation
Each study area includes the requirements of the proposed feature, a description of the basic mechanism and a discussion of the issues involved. A recommended solution is provided and impacts to other RAN WGs are analysed.
|
25.868
|
Node B synchronization for 1,28 Mcps TDD
|
TR
|
5.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.868/25868-501.zip
|
The present document describes the solution recommended to enable the synchronisation of Node Bs over the air in 1.28Mcps TDD for Rel-5.
|
25.870
|
Enhancement on the DSCH Hard Split mode
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.870/25870-500.zip
|
The purpose of the present document is to help the TSG RAN WGs to understand the proposed method and to specify the impacts to existing specifications, which is needed for the introduction of the “Enhancement on the DSCH hard split mode” for Release 5.
“Enhancement on the DSCH hard split mode” is proposed to specify the enhancements of TFCI coding and power control in DSCH hard split mode for UTRA FDD. Based on [1], this work item is composed of two work tasks.
1) TFCI coding in DSCH hard split mode
2) TFCI power control in DSCH hard split mode
The different WTs will be described in subsequent chapters. It is intended to gather all information in order to trace the history and the status of the WTs in each WG.
It describes the proposed methods for each area.
It describes the impacts due to this WI.
It describes agreed requirements related to the WTs.
It identifies the affected specifications according to the introduction of “Enhancement on the DSCH hard split mode”.
It also describes the schedule of the WTs.
|
25.875
|
NAS node selector function
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.875/25875-500.zip
|
The purpose of the present document provides the current status of the work "Intra Domain Connection of RAN Nodes to Multiple CN Nodes: Overall System Architecture" within 3GPP TSG RAN WG3.
Currently an RNC can only be connected to one MSC and/or one SGSN. This can bring about inefficient usage of hardware and disproportionate spread of signalling loads across a network.
This Work Item concentrates primarily on a solution where a (standardised) routing function in the RNC enables the connection of multiple MSCs/SGSNs to an RNC. It is hoped that this will bring about a reduction in mobility management signalling and improved efficiency in hardware utilisation.
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 discusses the impact upon RAN3 specifications, and identifies the affected specifications. If information needs to be communicated to groups outside of TSG RAN WG3, it is recorded in this document. When solutions are sufficiently stable, the CRs to the various impacted RAN3 specifications can be issued.
It also describes the schedule of the Work Task.
The present document is a 'living' document, i.e. it is continuously updated and presented to all TSG-RAN meetings.
|
25.877
|
High Speed Downlink Packet Access (HSDPA) - Iub/Iur Protocol Aspects
|
TR
|
5.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.877/25877-510.zip
|
The present document is part of the Release 5 work item "High Speed Downlink Packet Access (HSDPA) Iub/Iur protocol aspects". 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 "High Speed Downlink Packet Access" feature for Release 5. This work task belongs to the TSG RAN Building Block "High Speed Downlink Packet Access (HSDPA)".
|
25.878
|
RL timing adjustment
|
TR
|
5.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.878/25878-510.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 the Radio Link Timing Adjustment worktask., as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.879
|
Separation of resource reservation and radio link activation
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.879/25879-500.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 the Separation of resource reservation and radio link activation worktask, as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.880
|
Re-arrangement of Iub transport bearers
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.880/25880-500.zip
|
Based on [1], the objective of this work item is to introduce a new procedure in the NBAP to enable the Node B to indicate the request for switching the transport bearers and a Communication Control Port from one physical termination point to another. The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to the existing NBAP specification.
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 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.881
|
Improvement of Radio Resource Management (RRM) across RNS and RNS/BSS
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.881/25881-500.zip
|
This document is for part of the Rel 5 study item “Improvement of RRM across RNS and RNS/BSS”.
This study report describes the techniques to improve the RRM across RNS and RNS/BSS. It also deals with the feasibility of the techniques which are described in this document and their benefits.
|
25.882
|
1,28 Mcps TDD option base station classification
|
TR
|
5.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.882/25882-500.zip
|
The present document is a Technical Report on Release 5 work item “Base Station Classification for 1,28 Mcps TDD option.
|
25.883
|
Direct Transport Bearers Between SRNC and Node-B
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.883/25883-500.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to study aspects of the direct Node-B to SRNC transport bearers in preparation for a WI on this topic, as proposed in [1].
As requested by TSG-RAN, the document describes the identified consequences of the direct transport bearers, and classifies these main consequences as benefits or drawbacks.
Since the consequences might be different for an ATM and IP TNL, these different TNL’s are handled separately.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.884
|
Iur Neighbouring cell reporting efficiency optimisation
|
TR
|
5.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.884/25884-500.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 the Neighbouring Cells Reporting Optimization worktask., as proposed in [1].
The document describes the agreed requirements related to the worktask, the different areas that were studied, the agreements that were made, and it identifies the affected specifications with related Change Requests. It also describes the schedule of the worktask.
The present document is a 'living' document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.933
|
IP transport in UTRAN
|
TR
|
5.4.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.933/25933-540.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.945
|
RF requirements for low chip rate TDD option
|
TR
|
5.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.945/25945-520.zip
|
This technical Report identifies the RF Radio Transmission/Reception and Radio Resource Management requirements for the 1.28 Mcps UTRA TDD option, including the commonalties and differences. Furthermore, the impact on the RF system Scenarios and BS conformance testing is also identified.
|
25.952
|
TDD Base Station (BS) classification
|
TR
|
5.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.952/25952-520.zip
|
This document is a Technical Report on Release 5 work item “TDD Base Station Classification”.
|
25.991
|
Feasibility study on the mitigation of the effect of common pilot channel (CPICH) interference at the user equipment
|
TR
|
5.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.991/25991-510.zip
|
The present document assesses the feasibility of mitigating the effect of CPICH interference at the UE. The report includes performance evaluation of this feature using radio network level simulations and link level simulations, and complexity evaluation.
|
25.994
|
Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.994/25994-500.zip
|
The present document clarifies recommended measures which may be adopted by UTRAN to enable inter-working to be obtained between network and various early User Equipment (UE) implementations of the 3GPP specification. If possible, the 3GPP core specifications should be updated accordingly.
|
25.995
|
Measures employed by the UMTS Radio Access Network (RAN) to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification
|
TR
|
5.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.995/25995-500.zip
|
The present document clarifies recommended measures employed by the UTRAN to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification. If possible, the 3GPP core specifications should be updated accordingly.
|
27.103
|
Wide Area Network Synchronization
|
TS
|
5.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.103/27103-500.zip
|
This specification provides a definition of a Wide Area Synchronization protocol. The synchronization protocol is based upon current synchronization industry standards.
The present document covers Wide Area Network Synchronization between current and future mobile communication end-user devices, desktop applications and server-based information servers. This is a living document and, as such, it will evaluate new technologies (e.g. XML) for inclusion as they become readily available.
|
27.901
|
Report on Terminal Interfaces - An Overview
|
TR
|
5.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.901/27901-500.zip
|
The present document discusses external and internal interfaces of a terminal, with the exception of the radio and USIM interfaces. The focus of the study has been on external interfaces, to identify where existing industry standards can be used and whether there would be a need for specifications to be produced within 3GPP.
|
31.048
|
Security mechanisms for the (U)SIM application toolkit; Test specification
|
TS
|
5.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.048/31048-510.zip
|
The present document covers the minimum characteristics considered as necessary in order to provide compliance to 3GPP TS 23.048 " Security Mechanisms for the (U)SIM application toolkit; Stage 2" [6].
The present document describes the technical characteristics and methods of test for testing the Security Mechanisms for the (U)SIM application toolkit. It specifies the following parts:
- test applicability
- test environment description
- tests format
- test area reference
- conformance requirements
- Test Area Files
- test procedure
- test coverage
- a description of the associated testing tools that shall be used.
|
32.200
|
Telecommunication management; Charging management; Charging principles
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.200/32200-590.zip
|
The present document describes the principles of charging and billing for the provision of service and services by a 3G‑system.
The present document elaborates on the charging requirements described in the Charging Principles in 3GPP TS 22.101 [1]. It allows the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and references these where appropriate.
The Charging Data Records (CDRs) generated by the network elements of the 3G network, are required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network operators and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as archival information in dealing with customer service and billing complaints.
In addition to the information collected from network elements, network management functions are required for the administration of charging data.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in the present document which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs used in the Circuit Switched (CS) domain are specified in document3GPP TS 32.205 [5]. The CDRs content and transport within the PS domain are described in3GPP TS 32.215 [6] document, while CDRs used for application services are defined in document3GPP TS 32.235 [17].
The relationship among these charging specifications is illustrated in figure 1.1.
Figure 1.1: Charging Documents Structure
For the purpose of the present document, the charging data is considered to be generated and collected by charging functions in the network elements.
Charging data fields are collected and CDRs generated by the network elements for transfer to the billing system. For the packet switched domain, the CDRs are first sent to the Charging Gateway Function (CGF) for storage and further processing. The CGF may be a distinct network element or may be integrated into the packet domain network elements themselves.
The objectives of the present document are:
- to describe principles of charging in a 3G network;
- to provide a description of the charging architecture; and
- to provide the descriptions of events and triggers for the generation of Charging Data Records (CDRs).
|
32.205
|
Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.205/32205-590.zip
|
The GSM and UMTS PLMNs support a wide range of circuit based services. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in TS 32.200 [22] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node.
The present document specifies the structure and the contents of the CDRs that are collected by the relevant network elements for circuit switched services in 2G (GSM) and 3G (UMTS) networks. It also defines the syntax for the transfer of these CDRs from the collecting nodes to billing post-processing systems using standard file transfer protocols.
The CDRs content and transport within the PS domain are described in TS 32.215 [23] document, while CDRs used for application services are defined in document TS 32.235 [24].
The relationship among these charging specifications is illustrated in figure 1.
Figure 1: Charging Documents Structure
The interface definitions of GSM 12.05 are maintained for 2G, in order to assure backward compatibility to earlier GSM releases.
The charging architecture and principles that the present document is based on are specified in TS 32.200 [22].
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella TS 32.200 [22]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential.
|
32.215
|
Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain
|
TS
|
5.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.215/32215-590.zip
|
The GSM and UMTS PLMN support a wide range of packet based services by means of the General Packet Radio Service (GPRS), as defined in 3GPP TS 22.060 [1] and 3GPP TS 23.060 [2]. In order to enable operators the ability to provide a commercially viable service, there is a need to provide charging functions. For GPRS these functions include the generation of Charging Data Records (CDRs) by the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN) as well as the transport of these CDRs to a Billing System (BS) through a Charging Gateway Function (CGF).
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in document TS 32.200 [3] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs content and transport within the PS domain are described in the present document. The CDRs used in the Circuit Switched (CS) domain are specified in document TS 32.205 [4] while CDRs used for application services are defined in document TS 32.235 [5]. The present document structure is depicted in figure 1.
Figure 1: Charging Documents Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella document [3]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential.
|
32.225
|
Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS)
|
TS
|
5.11.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.225/32225-5b0.zip
|
The present document covers both online and offline charging for the IMS. For clarity, the terms Offline Charging and Online charging as applied to the IMS are defined here in clause 3. These definitions are the same as listed in TS 32.200 [2].
The IMS charging architecture details, requirements, definitions and principles are listed in TS 32.200 [2] and therefore are not repeated here.
In the present document the charging data triggers, message content and format are specified along with the transport of these messages using the Diameter protocol. Details about charging message flows and the definitions of the Diameter AVPs are also included in the present document. This information is divided into two main clauses: Online Charging and Offline Charging.
|
32.235
|
Telecommunication management; Charging management; Charging data description for application services
|
TS
|
5.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.235/32235-550.zip
|
The present document is part of a series of documents specifying charging functionality in UMTS network with application services. The UMTS core network charging principles are specified in document TS 32.200 [2], which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The document structure is defined in figure 1. The CDR content and transport for application services are described in the present document especially for MMS. As the basis and reference for this work is taken the functional description of the MMS specified for stage 1 in TS 22.140[3] and stage 2 in TS 23.140 [4].
Figure 1 Charging Document Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common are defined in the 3GPP Vocabulary [1] and specialised to charging in UMTS domains or subsystems are provided in the umbrella document [2].
|
32.301-1
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-1/32301-1-200.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the « Requirements » of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
How IRPManager discovers the IRPAgent’s address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
|
32.301-2
|
Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-2/32301-2-200.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. This document is the « Information Service » of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system’s client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP : Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent’s emission of notifications (suspendSubscription and resumeSubscription operations).
Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP : Information Service [1].
How IRPManager discovers the IRPAgent’s address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
|
32.800
|
Telecommunication management; Management level procedures and interaction with UTRAN
|
TR
|
5.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.800/32800-500.zip
|
The principle objective of the present document is to provide supporting information for the O&M standardisation of a (multi-vendor) UTRAN network. The actual specification work relating to the O&M interface between Network and Network Manager can be found in [9], [10] and [11] and for the Iub interface in [1]. For this reason the present document may contain information or working assumptions which are not a direct part of the specifications, but are essential to the progress and informed decision making.
|
32.802
|
Telecommunication management; User Equipment Management (UEM) feasibility study
|
TR
|
5.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.802/32802-510.zip
|
The scope of the present document is a Release 5 feasibility study that evaluate aspects of User Equipment Management (UEM) which would be beneficial to standardise post-Release-5. For Release 5 the present document does not have a factual impact on other 3GPP Work Items (WIs).
User Equipment (UE) includes both the USIM and Mobile Equipment (ME) domains and so it is emphasised that the scope of UEM includes both the USIM and ME domains.
The present document is focussed on the UEM interface to the UE Over-The-Air (OTA). There is a potential direct interface between the UE Managers and the UE; for example, a user may be able to upgrade the operating system in its UE by taking it to the UE manufacturer's service centre. This direct interface is outside the scope of the present document .
The user interface will be important in delivering UEM. However, the user interface is both outside the scope of the present document and outside the scope of the standardisation of UEM.
|
34.943
|
Analysis of difference between FDD and 1.28 Mcps TDD and corresponding effect on terminal conformance test in radio access stratum protocol aspects
|
TR
|
5.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.943/34943-500.zip
|
The present document analyzes the differences of Uu/Iub interface between 1.28Mcps TDD and FDD, and the effect on UE conformance testing for 3rd Generation Terminals.
The actual test case descriptions will be contained in other documents.
|
42.019
|
Subscriber Identity Module Application Programming Interface (SIM API); Stage 1
|
TS
|
5.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.019/42019-510.zip
|
The present document defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
The present document includes information applicable to network operators, service providers and terminal, SIM, switch and database manufacturers.
The present document contains the core requirements which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a SIM API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in the present document may implement requirements which are considered outside the scope of the present document. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
|
43.019
|
Subscriber Identity Module Application Programming Interface (SIM API) for Java Card; Stage 2
|
TS
|
5.6.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.019/43019-560.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.
|
21.133
|
3G security; Security threats and requirements
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.133/21133-410.zip
|
This specification takes notice of the Security Principles and Objectives as set out in [1]. It contains an evaluation of perceived threats to 3GPP and produces subsequently a list of security requirements to address these threats.
As teleservices and applications will not, in general, be standardised, it is difficult to predict their exact nature. Therefore, this specification considers all security threats and aims at listing generic security requirements that shall be applicable irrespective of the actual services offered. The list of threats and requirements may however need to be updated as the 3GPP system evolves.
The threat analysis performed relies to a large extent on previous experiences with 2G systems, in particular GSM, and takes into account known problems from that area.
The security requirements listed in this specification shall be used as input for the choice of security features and the design of the 3GPP security architecture as specified in [2].
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 contains a reference to the general objectives for 3G security;
clause 5 contains an overview of the context in which the security architecture of 3G is designed;
clause 6 contains a list of identified security threats to 3G, and gives some results from the threat analyses that have been performed;
clause 7 contains an overview of the risk assessment resulting from the threat analyses performed
clause 8 contains the resulting list of security requirements for 3G and indicates how these requirements relate to the threats and the security objectives .
Finally, Annex A gives some more detailed information on threats and risks connected to so called false base station attacks.
|
23.908
|
Technical report on Pre-Paging
|
TR
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.908/23908-400.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
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.909/23909-400.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
|
4.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.911/23911-400.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
|
4.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.912/23912-410.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.930
|
Iu principles
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.930/23930-400.zip
|
This report identifies the requirements on the Iu and studies relevant principles to guide further standardisation of the related interface(s).
The different instances of the UMTS radio access currently identified are the following:
UMTS radio access network (URAN)
UMTS Terrestrial Radio Access Network (UTRAN)
Broadband Radio Access Network (BRAN)
UMTS satellite radio access network
|
25.832
|
Manifestations of Handover and SRNS relocation
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.832/25832-400.zip
|
The present document identifies a number of handover and SRNS Relocation scenarios for UTRAN. It is intended to reflect and clarify the requirements on UTRAN, and to assist in the development of procedures and capabilities.
|
25.834
|
UTRA TDD low chip rate option; Radio protocol aspects
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.834/25834-410.zip
|
The present document describes the services provided by the physical layer and the layer 2/3 functionality for support of the 1.28 Mcps low chip rate option of UTRA TDD. Based on the protocol structure existing for UTRA TDD / FDD, it is identified which modifications will be required in order to enable the layer 1 characteristics and key features of the low chip rate option.
|
25.836
|
Node B synchronization for TDD
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.836/25836-410.zip
|
This TR describes the solution recommended to enable the synchronisation of NodeBs in UTRA TDD beyond that included in Rel. 99.
|
25.838
|
Node B Synchronisation for TDD (Iub/Iur aspects)
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.838/25838-410.zip
|
The purpose of the present document is to help the TSG RAN WG3 group to specify the changes to existing WG3 specifications, needed for the introduction of the “Node B Synchronisation for TDD”. 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.
This TR 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.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.840
|
Terminal power saving features
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.840/25840-400.zip
|
The present document is the Technical Report of the Release 4 work item “Terminal Power Saving Features”.
|
25.841
|
DSCH power control improvement in soft handover
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.841/25841-410.zip
|
This document is the Technical Report for the DSCH power control improvement in soft handover, part of the Release 4 work item "DSCH power control improvement in soft handover”.
|
25.843
|
1.28 Mcps TDD UE Radio Access Capabilities
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.843/25843-410.zip
|
The present document describes the UE radio access capabilities for 1,28 Mcps TDD, identifies the commonalties and explains the differences to 3,84 Mcps TDD.
|
25.844
|
Radio acces bearer support enhancements
|
TR
|
4.3.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.844/25844-430.zip
|
The present document is a technical report that summarises the work on the UTRAN Release 2000 work item "Radio Access Bearer Support Enhancements". The work items comprises of five areas of study:
1) Robust header compression
2) PDCP multiplexing
3) Variable Iu frame formats and unequal error protection over Uu
4) Channel type switching per logical channel
5) Header removal
Each study area includes the requirements of the proposed feature, a description of the basic mechanism and a discussion of the issues involved. A recommended solution is provided and impacts to other RAN WGs are analysed.
|
25.847
|
UE positioning enhancements
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.847/25847-400.zip
|
The present document identifies possible UE positioning enhancements and new methods for UTRA TDD and FDD for Release 4. It builds the basis for evaluation and comparison of these methods and enhancements. The report also covers the impacts on Layer1 and UTRAN interfaces.
Finally, CRs to the affected specifications should be created based on this TR.
|
25.848
|
Physical Layer Aspects of UTRA High Speed Downlink Packet Access
|
TR
|
4.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.848/25848-400.zip
| |
25.849
|
DSCH power control improvement in soft handover
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.849/25849-400.zip
|
The present document is for part of the Release 4 work item "DSCH power control improvement in soft handover".
|
25.850
|
UE positioning in UTRAN Iub/Iur protocol aspects
|
TR
|
4.3.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.850/25850-430.zip
|
The present document helps the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the UE positioning in UTRAN for Release 2000.
Based on [1], standard location services are defined as the:
- cell coverage based positioning method;
- OTDOA method with network configurable idle periods; and
- network assisted GPS method.
Since cell coverage based positioning method in WG3 group is already standardised the present document will cover the Iub/Iur protocol aspects for OTDOA method with network configurable idle periods and network assisted GPS method.
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.851
|
RAB Quality of Service (QoS) Renegotiation over Iu
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.851/25851-400.zip
|
The present document provides the current status of the work item “RAB Quality of Service Renegotiation over Iu” within 3GPP TSG RAN WG3. It describes the requirements, discusses the renegotiation procedure, and identifies the affected specifications. If information needs to be communicated to groups outside of TSG RAN WG3, it is recorded in this document.
The document is a ‘living’ document, i.e. it is continuously updated and presented to all TSG-RAN meetings.
|
25.853
|
Delay budget within the access stratum
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.853/25853-400.zip
|
The present document evaluates the delay components introduced within the Access Stratum to provide guidelines useful both to provider for the dimensioning of a network and to manufacturers for the design of node elements. While the analysis of the possible delay sources is performed in an exhaustive way, the evaluation of single and global delay figures is limited to the case of Real Time services.
The estimation of Non Real Time service delays is not in scope of Release 99 and, therefore, it will not be considered in the present version of the Technical Report.
The figures of the present document sow possible scenarios and shall not be interpreted as requirements for a specific UTRAN implementation.
|
25.928
|
1,28 Mcps functionality for UTRA TDD physical layer
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.928/25928-401.zip
|
The present document describes the 1.28Mcps functionality for UTRA TDD physical layer, identifies commonalties and explains the differences to the 3.84Mcps chip rate. Suggestions for alignment will be provided too.
|
25.934
|
AAL2 QoS optimization
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.934/25934-400.zip
|
The present document clarifies:
• the issue to be improved under the work task,
• requirements for the solution from UTRAN transport network configuration point of view,
• solution to solve the issue,
• backward compatibility mechanism between Release 4 and Release 99 specifications for the solution, and
• what Change request is needed to reflect the solution to enhance Release 99 specifications to Release 4 specifications.
|
25.935
|
RRM optimisation
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.935/25935-410.zip
| |
25.936
|
Handover for realtime services from PS-domain
|
TR
|
4.0.1
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.936/25936-401.zip
|
The purpose of the present document is to help the relevant 3GPP groups to specify the changes to existing specifications, needed for the introduction of the “Handover for real-time services from PS domain” Building Block for Release 2000.
The purpose of this R00 work task is to define the relocation procedure to be used when real time services are supported in the PS domain.
The intention with this work item is to provide support for services such as voice over IP and multimedia over IP.
This TR focuses on the requirements for the solution. Possible solutions have been further studied and they are also described in this TR for comparison and evaluation against the requirements. In doing this work, RAN3 has identified some areas of study that are not primarily under RAN3’s responsibility. These are mentioned here so that work can be coordinated with the other 3GPP groups.
Changes to the signalling protocols in UTRAN and CN interfaces have also been studied at a high level.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
25.937
|
UTRAN TDD low chiprate
|
TR
|
4.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.937/25937-410.zip
|
The work item "Low chip rate TDD Iub/Iur protocol aspects" is a Building Block which has been agreed at TSG RAN#8 as described in contribution [1]. Its parent feature is "Low chip rate TDD" which has been agreed at TSG-RAN#6 and updated at RAN#7. The purpose of the work item "Low chip rate TDD Iub/Iur protocol aspects" is to update the Iub/Iur interface protocol specifications and related overview specifications in RAN WG3 in support of the several aspects of the feature "Low chip rate TDD".
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 the low chip rate TDD option in the UTRAN for Rel.4. 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.944
|
Channel coding and multiplexing examples
|
TR
|
4.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.944/25944-410.zip
|
The present document describes examples of channel coding and multiplexing for physical channels of FDD mode and TDD mode.
|
25.946
|
RAB Quality of Service (QoS) Negotiation over Iu
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.946/25946-400.zip
|
The present document gives a presentation of the current status of the Work Item “RAB Quality of Service Negotiation over Iu” within TSG RAN WG3.
It describes requirements, additional studies needed, and agreements reached so far for the Work Item.
It identifies the affected specifications.
It also describes the schedule of the Work Task.
If information needs to be communicated to groups outside of TSG RAN WG3, this is also indicated.
The document is a ‘living’ document, i.e. it is continuously updated and presented to all TSG-RAN meetings.
|
25.950
|
UTRA High Speed Downlink Packet Access (HSDPA)
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.950/25950-401.zip
|
The present document describes several techniques, which facilitate high-speed downlink packet access. Furthermore, it describes how these concepts should be integrated into the overall architecture of UTRA. The techniques should be applicable to streaming, interactive and background services.
|
25.953
|
TrFO/TFO
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.953/25953-400.zip
|
The present document provides the current status of the work item “Transcoder Free Operation” within 3GPP TSG RAN WG3.
The purpose of this Rel4 Work Task is to define necessary enhancements of specifications under RAN WG3 control to support the procedures specified within the parent Building Block “Out of Band Transcoder Control”.
|
25.954
|
Migration to modification procedure
|
TR
|
4.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.954/25954-400.zip
|
The present document clarifies:
• rational to introduce transport bearer modification procedure on Iub, Iur, and Iu,
• requirement for the solution of transport bearer modification,
• study area in order to introduce the modification procedure,
• way to solve the study area , and
• Change request needs to be given in order to enhance Release 99 specification to Release 4 specification for the work task.
|
26.901
|
Adaptive Multi-Rate Wideband (AMR-WB) speech codec; Feasibility study report
|
TR
|
4.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.901/26901-401.zip
|
The present document presents the outcome of the Feasibility Study Phase of wideband Adaptive Multi-rate codec. Clauses 4 to 6 provide an overview and background for introducing AMR wideband. Clause 7 provides a review of relevant standardization activities. Feasibility aspects such as codec performance, speech coding bit-rates, implementation complexity and transmission delay are discussed in clauses 8 and 9. Clause 10 outlines the target timeplan for AMR-WB codec development, testing, selection and standardization. Clauses 11, 12 and 13 conclude with a summary of the risks and recommendations.
|
26.912
|
Codec for Circuit switched Multimedia Telephony Service; Quantitative performance evaluation of H.324 Annex C over 3G
|
TR
|
4.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.912/26912-400.zip
|
The present document is meant to function as guidance in the work of other 3GPP work groups or work items. Such work may include conclusion on how to achieve detailed Stage 1 service requirements or suggestion of a set of recommended RAB parameters giving satisfactory user-to-user quality for a circuit switched multimedia service using 3G-324M.
|
27.903
|
Discussion of synchronization standards
|
TR
|
4.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.903/27903-400.zip
|
The present document provides information on existing synchronization protocols. It summarizes proprietary and standard protocols relevant to current and future mobile communication devices.
The present document covers only synchronization between end-user devices, desktop applications, and server-based information services. It does not refer to replication or synchronization between enterprise databases.
|
29.198-04
|
Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control Service Capability Feature (SCF)
|
TS
|
4.11.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04/29198-04-4b0.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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.