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
|
|---|---|---|---|---|---|---|
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.852
|
Iu enhancements for IP Multimedia (IMS) support in UTRAN
|
TR
|
0.1.2
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.852/25852-012.zip
|
This present document is for the 3GPP Release 6 Work Item “Iu Enhancements for IMS Support in UTRAN”(see [1]).
Release 5 enables the basic support for IMS in the RAN but evaluation of possible further enhancements was decided in RAN#19.
The purpose of the present document is to aid TSG RAN WG3 to standardise these possible improvements in release 6 by refining the requirements from a RAN thorough perspective and evaluate the associated optimisations in the handling of IMS RAB in the RNC.
This document is intended to gather all this information, assess the proposals of enhancements and agree on some of them in section 7 before integrating them into the Technical Specifications.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
25.867
|
Feasibility study for wideband distribution systems in 3rd generation networks
|
TR
|
1.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.867/25867-130.zip
|
The present document summarises the results of the feasibility study about inclusion of Wideband Distribution Systems, or WDS, as part of third generation networks in 3GPP standards.
It covers the history of the proposal, shows and discusses the results of relevant analysis and simulation activities, highlights the possible degree of integration to the current status of 3GPP network architecture and concludes with the indication for a possible way forward in the standardisation path.
|
25.869
|
Transmitter diversity solutions for multiple antennas
|
TR
|
1.2.1
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.869/25869-121.zip
|
The study done in this TR focuses on transmit diversity methods with more than 2 antennas at the Node B and 1 antenna at the UE. The functionality introduced to support more than 2 antennas at the Node B could permit consideration of compatible operation with 2 antennas.
A proposal for a new transmit diversity method using multiple antennas may be included in the TR if at least the following requirements are fulfilled:
a) it should be shown that there is significant benefit in at least one realistic scenario, e.g. one of the (multi-)path models of table 7; for closed loop methods also feedback errors and delays need to be considered.
b) the description should be detailed enough to see how it fits into the current specification (so it is in principle clear what changes need to be done).
c) relevant R99 schemes should be used as reference cases depending on the proposal (open or closed loop, or both)
d) backwards compatibility needs to be addressed
This evaluation of different transmit diversity schemes for multiple antennas is within the scope of this TR.
|
25.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.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.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.
|
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].
|
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.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.955
|
Virtual Home Environment (VHE) concepts
|
TR
|
0.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.955/23955-010.zip
|
The present document is to capture VHE concepts. It is not limited to any specific type of services. It includes OSA, CAMEL, SIP, MExE USAT etc..
Contributions for VHE/OSA concerning the document TS 23.127 have to be provided in the form of Change Requests. Since a lot of changes are expected due to the shift of the focus of the document from OSA to VHE this is an inflexible procedure.
Consequently this document was created to collect contributions, ideas and proposals for TS 23.127. They have to be written against the current structure of the document. It is planned to dissolve the TR and to create Change Requests against the TS 23.127 or other applicable documents from it at the end.
The body of this document is planned to be incorporated into appropriate TS documents.
|
23.974
|
Support of push service
|
TR
|
2.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.974/23974-200.zip
|
The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope.
|
25.855
|
High Speed Downlink Packet Access (HSDPA); Overall UTRAN description
|
TR
|
5.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.855/25855-500.zip
|
The present document captures the agreements and evaluation criteria for the different techniques being considered for HSDPA with regards to the overall support of UTRAN for HSDPA.
|
25.885
|
UMTS 1800 / 1900 MHz work items report
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.885/25885-100.zip
|
This clause shall start on a new page. No text block identified. Should start:
This document is a technical report of the UMTS1800/1900 work items. The purpose of these work items is to provide UMTS specification support for UTRA/FDD in the 1800 MHz (ITU region 1 and 3) and 1900 MHz bands (ITU region 2). In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, and methodology, study results and specification recommendations.
This document is a ‘living’ document, periodically updated and presented at all TSG-RAN meetings until all related CRs are agreed and approved.
|
27.104
|
vObjects and other constructs for data synchronization
|
TS
|
0.1.1
|
T2
|
https://www.3gpp.org/ftp/Specs/archive/27_series/27.104/27104-011.zip
|
This specification serves as a vessel to manage the process of adding new vObjects and other constructs as data store types for use in data synchronisation activities within the 27.103 Wide Area Synchronisation specification.
While this first release is identified as a Release 4 specification, this is a living document and, as such, it encompasses the addition of new vObjects and other constructs for inclusion in data synchronisation activities as they become readily available, an evolving task that will continue beyond a single release.
|
30.002
|
Guidelines for the modification of the Mobile Application Part (MAP)
|
TR
|
5.0.0
|
N4
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.002/30002-500.zip
|
After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects.
|
31.123
|
(Universal) Subscriber Interface Module ((U)SIM) toolkit interpreter test
|
TS
|
0.3.0
|
T3
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.123/31123-030.zip
| |
32.108
|
Telecommunication management; Subscriber and equipment trace
|
TS
|
0.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.108/32108-010.zip
|
[Editor’s note: The text is still partly from 12.08. More updating needed.]
This Technical Specification (TS) specifies the Trace facility for GSM 3G mobile networks where it refers to:
- Subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI or Public ID));
- Equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- Types of trace which relate more to network elements than to individual subscribers e.g. tracing events within a Base Station System (BSS), and so on;
- Tracing of all possible parties in e.g. a multi-party call, (although multiple calls related to the IMSI specified in the trace type field are traceable).
The control signalings on different interfaces and the characteristics of user data are within the scope of this TS, but not the actual contents of the user data.
This TS does not specify any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer.
This TS does not specify any data compression mechanisms for trace data transfer.
|
41.103
|
GSM Release 5 specifications
|
TS
|
5.4.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.103/41103-540.zip
|
The present document identifies the GSM system specifications for Release 5. The specifications and reports of 3GPP Release 5 have a major version number 5 (e.g. 5.x.y).
Most of the core Release 5 Technical Specifications and Technical Reports were functionally frozen at either the 15th Technical Specification Group meetings in March 2002 or the 16th in June 2002.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 5 version 5.x.y specifications throughout 2002 and beyond.
|
43.031
|
Fraud Information Gathering System (FIGS); Service description; Stage 2
|
TS
|
5.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.031/43031-500.zip
|
This Technical Specification specifies the stage 2 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
Three levels of FIGS service are defined, levels 1 to 3.
Level 1 will use the facilities provided by Transferred Account Procedure (TAP).
Levels 2 and 3 will use facilities provided by Customised Applications for Mobile network Enhanced Logic (CAMEL), in particular, the information flows between the GSM Service Switching Function (gsmSSF) and GSM Service Control Function (gsmSCF). Phase 1 and Phase 2 CAMEL facilities will be used.
Connection-orientated services only are covered.
|
42.031
|
Fraud Information Gathering System (FIGS); Service description; Stage 1
|
TS
|
5.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.031/42031-500.zip
|
This Technical Specification specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
This specification enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
|
43.930
|
Iur-g interface; Stage 2
|
TR
|
5.1.0
|
G2
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.930/43930-510.zip
|
The present document provides an overview of the Iur-g interface. It describes the motivation, principles and functionality of this interface. It does not contain the detailed description, which it is included in the stage 3 Technical Specifications.
|
43.900
|
Support for voice optimization for the IMS in the GERAN
|
TR
|
1.0.0
|
G1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.900/43900-100.zip
|
The present document provides an overview of the architecture and issues related to the provision of voice optimisation within the GERAN.
|
21.102
|
3rd Generation mobile system Release 4 specifications
|
TS
|
4.9.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.102/21102-490.zip
|
The present document identifies the 3rd generation mobile system specifications for Release 4. The specifications and reports of 3G Release 4 have a major version number 4 (e.g. 4.x.y).
Most of the core Release 4 Technical Specifications and Technical Reports were functionally frozen at the 11th Technical Specification Group meetings (TSG#11) in March 2001.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 4 version 4.x.y specifications throughout 2001 and beyond.
|
23.073
|
Support of Localised Service Area (SoLSA); Stage 2
|
TS
|
4.0.0
|
N4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.073/23073-400.zip
|
The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43.
|
23.821
|
Architecture Principles for Reelase 2000
|
TR
|
1.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.821/23821-101.zip
|
The scope of this Technical Report is to list architectural requirements, features, functions and solutions of UMTS inside the scope of UMTS Release 00. These are working assumptions agreed by TSG SA WG2. The TR focuses on
- new/modified functionality as compared to Release 99
- technical description of the features, functions and solutions of R00.
It is expected that this TR will act as a basis for the detailed Stage 2 specification work.
This TR has been created to ease the development of R00 work prior to the finalization of the R99 specifications. In conjunction with when R99 is finalized, work on the TR will cease and the relevant CRs will be produced to incorporate the contents of this TR within the R00 version of the specifications."
|
23.874
|
Feasibility study of architecture for network requested PDP context activation with User-ID
|
TR
|
1.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.874/23874-130.zip
|
The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope.
|
23.907
|
Quality of Service (QoS) concept
|
TR
|
1.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.907/23907-120.zip
|
Scope of this document is to provide the framework for Quality of Service in UMTS. The document shall be used as a living document which will cover all issues related Quality of Service in UMTS.
|
23.913
|
UMTS Turbo-Charger
|
TR
|
1.0.0
|
-
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.913/23913-100.zip
| |
23.922
|
Architecture for an All IP network
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.922/23922-400.zip
|
This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS standard
in order to provide this architectural option within Release 2000.
|
25.835
|
Report on hybrid ARQ type II/III
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.835/25835-100.zip
|
This technical report captures the results of the work on the work item “Hybrid ARQ Type II/III”. This includes technical solutions and their comparison. The report covers impacts on all RAN WGs.
|
25.837
|
Hybrid ARQ Type II/III (Iub/Iur aspects)
|
TR
|
0.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.837/25837-010.zip
|
The purpose of the present document is to gather all information concerning the impacts of Hybrid ARQ Type II/III on RAN WG3.
|
25.845
|
FDD RACH and AICH performance requirements
|
TR
|
0.0.3
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.845/25845-003.zip
|
This document is a Technical Report concerning the WG4 work item “Performance specification of demodulation of common channels”. In this report FDD RACH and AICH receptions are considered.
|
25.924
|
Opportunity Driven Multiple Access (ODMA)
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.924/25924-100.zip
|
The present document provides a description of Opportunity Driven Multiple Access (ODMA).
ODMA is a relay transmission protocol to be applied to UMTS TDD. ODMA will provide the ability to maintain high data rates within a TDD towards the edges of traditional TDD coverage. The main purpose of ODMA is:
- Increase the high data rate coverage within a cell.
- Increase the capacity of TDD.
- Provide distributed network architecture for spot coverage and traffic hotspots.
|
25.938
|
Terminal power saving features
|
TR
|
2.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.938/25938-200.zip
|
The pupose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the “Terminal Power Saving Features” option for Release 2000.
WG1 is the leading working group of this Work Item (WI) and has its own TR. The purpose of this TR is not to replace the TR or any decisions made in the leading WG. Rather, it is intended to gather all the information in order to trace the history and the status of the Work Task in other RAN WGs, and discuss issues that WG3 has impact on.
It is not intended to replace contributions and Change Requests, but only to list conclusions and make references to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings
|
26.920
|
Architectural Model for the 3G Transcoders
|
TR
|
0.1.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.920/26920-011.zip
|
The present document is a description of the transcoder in the UMTS networksl. The initial aim of this document is to have a reference model for the standardization work carried out by the 3GPP Technical Specification Groups.
|
30.802
|
Project plan on Bearer Services and QoS
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.802/30802-400.zip
|
After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects.
|
33.129-2
|
Security Assurance Specification for 3GPP Lawful Interception Functions; NF Embedded LI Functions
|
TS
|
0.0.10
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.129-2/33129-2-00a.zip
| |
33.129-1
|
Security Assurance Specification for 3GPP Lawful Interception Functions; Common Baseline
|
TS
|
0.0.8
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.129-1/33129-1-008.zip
| |
26.858
|
Study on APIs for 3GPP Speech and Audio Codecs
|
TR
|
0.6.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.858/26858-060.zip
| |
32.105
|
3G charging and billing; Stage 2 description
|
TS
|
0.0.4
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.105/32105-004.zip
|
This Technical Specification describes the Architecture, Principals and Call Event specifications of charging and billing for the provision of service and services by a 3G system.
This standard is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. This standard will elaborate on the charging requirements described in the Charging Principles in UMTS 22.01 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
The call and event data generated by the network elements of the 3G network, is required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as historical evidence in dealing with customer service and billing complaints;
In addition to the information collected from these network elements, network management functions are required for the administration of charging data.
For the purpose of the present document, the call and event data is considered to be collected, in real-time, by network element function (NEF) blocks located within the recording entities.
The data collected by the NEFs is sent to, or collected by, the appropriate Operations System Function (OSF) blocks for storage and further processing.
The location of the OSF is implementation specific and may, for example, be provided either by an Administration Centre (ADC) or integrated within the network elements themselves.
The following is beyond the scope of this TS, and therefore this TS does not describe:
-
The objectives of this standardisation are:
• to provide the descriptions of events and triggers for the generation of Call detail records;
- to provide the descriptions for Call and event Call detail records;
- to produce a description of the collection techniques for accounting administration and CDR generation;
and
- to define a method for the transmission of CDRs over an open interface.
|
32.111
|
3G Fault Management
|
TS
|
4.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111/32111-400.zip
|
The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardisation of these functions across the different vendors' equipment is not required. The functional areas to be specified in this part of the document cover:
• fault surveillance and detection in the NEs;
• notification of alarms (including alarm cease) and operational state changes;
• retrieval of current alarms from the NEs;
• fault isolation and defence mechanisms in the NEs;
• alarm filtering;
• management of alarm severity levels;
• alarm and operational state data presentation and analysis at the OS;
• retention of alarm and operational state data in the NEs and the OS; and
• the management of tests.
Any (re)configuration activity exerted from the OMC as a consequence of faults will not be subject of the present document, these are described in [1].
Clauses 6 and 7 of the present document describe specific aspects of the Fault Management for the UTRAN and the CN, respectively, with particular emphasis on the exact fault definitions and alarm information to be generated. The definition of the test procedures and the relationship with the UTRAN resp. CN management architecture as defined in [3].
Finally, Clause 8 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3G networks, as seen from the Network Manager (NM). The Itf-N is fully standardised so as to connect systems of any vendor to the NM via this interface.
|
32.301-3
|
Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-3/32301-3-200.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service [5].
|
32.301-4
|
Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point: Common Management Information Protocol (CMIP) solution
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-4/32301-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in 3G TS 32.301-2 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Notification Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.402
|
Telecommunication management; Performance Management (PM); Performance measurements - GSM
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.402/32402-200.zip
|
The present document describes the TMN model for the administration of measurements and the collection of measurement result data in a GSM system. It also includes the measurement definitions for GSM. The concept and functional requirements for performance management in wireless GSM and UMTS systems is set out in TS 32.401 [31], while the measurements for UMTS and combined UMTS/GSM systems are specified in TS 32.403 [32].
|
32.601-1
|
Telecommunication management; Configuration Management (CM); Part 1: Basic CM Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-1/32601-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Basic Configuration Management IRP.
|
32.601-2
|
Telecommunication management; Configuration Management (CM); Part 2: Basic CM Integration Reference Point (IRP) information model
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-2/32601-2-200.zip
|
The present document defines a component of an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate basic Configuration Management related information to one or several 'IRPManagers' (typically Network Managers).
This version of the IRP is mainly intended for “passive management” of high-level network configuration and status information as required by a Network Manager.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service. The Basic CM IRP: IS defined herein provides one such Information Service.
Thus, to summarize, the Basic CM IRP: IS defined in the present document has the following main purpose: to define an interface for retrieval of Configuration Management information.
(1)
|
32.601-3
|
Telecommunication management; Configuration Management (CM); Part 3: Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-3/32601-3-200.zip
|
The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.601-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types, methods and notifications.
|
32.601-4
|
Telecommunication management; Configuration Management (CM); Part 4: Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-4/32601-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.601-2. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.602-1
|
Telecommunication management; Configuration Management (CM); CMt: Bulk CM Integration Reference Point (IRP) requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-1/32602-1-200.zip
|
The present document describes the Bulk Configuration Management (CM) requirements for managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 32.102 [2].
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention 3G TS 32.300 [3], which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 [1] and 3G TS 32.102 [2]. For CM, a number of IRPs (and a Name Convention) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP. These IRPs are defined in separate 3GPP specifications, and listed in the table in the Introduction clause above. This document defines the requirements for the Bulk CM IRP.
|
32.602-2
|
Telecommunication management; Configuration Management (CM); CMt: Bulk Configuration Management Integration Reference Point (IRP): Information service
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-2/32602-2-200.zip
| |
32.602-3
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-3/32602-3-200.zip
|
The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP information service (see 3GPP TS 32.602-2 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
The present document does not describe any Network Resource Model (NRM) – they are described in Generic Network Resources IRP: NRM 3GPP TS 32.620-2 [4], UTRAN Network Resources IRP: NRM 3GPP TS 32.622-2 [11], GERAN Network Resources IRP: NRM 3GPP TS 32.623-2 [12].
|
32.602-4
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-4/32602-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Bulk CM Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.602-2. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.602-5
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): XML file format definition
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-5/32602-5-200.zip
|
The present document defines the XML file formats for the configuration data files and session log files of Bulk CM IRP IS [1].
Those file formats are based on XML [2], XML Schema [3] [4] [5] and XML Namespace [6] standards.
|
32.620-1
|
Telecommunication management; Configuration Management (CM); Part 1: Generic network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-1/32620-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resources IRP.
|
32.620-2
|
Telecommunication management; Configuration Management (CM); Part 2: Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-2/32620-2-200.zip
|
The present document (Generic Network Resources IRP: Network Resource Model) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
The present document specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like Security management, Software management, Network & Service provisioning, etc. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs are consistent. The Generic Network Resources IRP here provides a base for all resource modelling.
To summarize, the Generic Network Resources IRP main purpose is to define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit or have associations with.
|
32.620-3
|
Telecommunication management; Configuration Management (CM); Part 3: Generic network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-3/32620-3-200.zip
|
The TS 32.620 series (Generic Network Resources IRP) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
This series of documents specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes and Managed Object Classes.
The present document specifies the Corba Solution set.
|
32.620-4
|
Telecommunication management; Configuration Management (CM); Part 4: Generic network resources: Integration Reference Point (IRP) Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-4/32620-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Generic Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.620-2. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.621-1
|
Telecommunication management; Configuration Management (CM); Part 1: Core network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-1/32621-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Resources IRP.
|
32.621-2
|
Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-2/32621-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “Core Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning CN resources. This version of the IRP is mainly intended for “passive management” of high-level network configuration and status information as required by a Network Manager. The “Core Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral Core Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines CN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has the following main purpose: to define the applied CN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17]. However, which Information Service that is applicable is outside the scope of this document.
|
32.621-3
|
Telecommunication management; Configuration Management (CM); Part 3: Core network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-3/32621-3-200.zip
|
The purpose of this Core Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.621-2 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.621-4
|
Telecommunication management; Configuration Management (CM); Part 4: Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-4/32621-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the CN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.621-2. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.622-1
|
Telecommunication management; Configuration Management (CM); Part 1: UTRAN network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-1/32622-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP.
|
32.622-2
|
Telecommunication management; Configuration Management (CM); Part 2: UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-2/32622-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “UTRAN Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning UTRAN resources. The “UTRAN Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document
1. specifies the protocol neutral UTRAN Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines UTRAN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has the following main purpose:
(1) to define the applied UTRAN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17] or the Bulk CM IRP: IS [18]. However, which Information Service that is applicable is outside the scope of this document.
|
32.622-3
|
Telecommunication management; Configuration Management (CM); Part 3: UTRAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-3/32622-3-200.zip
|
The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.622-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.622-4
|
Telecommunication management; Configuration Management (CM); Part 4: UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-4/32622-4-200.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.622-2. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.623-1
|
Telecommunication management; Configuration Management (CM); Part 1: GERAN network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-1/32623-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resources IRP.
|
32.623-2
|
Telecommunication management; Configuration Management (CM); Part 2: GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-2/32623-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “GERAN Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning GERAN resources. The “GERAN Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral GERAN Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines GERAN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has following main purpose: to define the applied GERAN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17] or the Bulk CM IRP: IS [18]. However, which Information Service that is applicable is outside the scope of this document.
|
32.623-3
|
Telecommunication management; Configuration Management (CM); Part 3: GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-3/32623-3-200.zip
|
The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.623-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.623-4
|
Telecommunication management; Configuration Management (CM); Part 4: GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-4/32623-4-200.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.623-2. 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.
|
34.910
|
Identification of test requirements for regulatory purposes in different regions/countries
|
TR
|
1.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.910/34910-100.zip
|
The present document contains a collection of test requirements identified for regulatory purposes in different regions/countries.
The actual test case descriptions will be contained in other documents.
|
41.102
|
GSM Release 4 specifications
|
TS
|
4.9.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.102/41102-490.zip
|
The present document identifies the GSM system specifications for GSM Release 4.
|
42.032
|
Immediate Service Termination (IST); Service description; Stage 1
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.032/42032-400.zip
|
This Technical Specification specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
|
42.048
|
Security mechanisms for the SIM Application Toolkit; Stage 1
|
TS
|
4.0.0
|
T3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.048/42048-400.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM.
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 (GSM 03.48).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
43.035
|
Immediate Service Termination (IST); Stage 2
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.035/43035-410.zip
|
This TS specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP command.
|
43.046
|
Technical Realization of Facsimile Group 3 Service - non transparent
|
TS
|
4.0.0
|
N3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.046/43046-400.zip
|
The present document deals with the procedures allowing the technical realization of the real time end to end facsimile group 3 service within the GSM PLMN using nontransparent network support according to the definition of the Teleservices 61 and 62 specified in GSM 22.003. Within the present document particular attention is given to Teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to Teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions the term "Teleservice" denotes both Teleservice 61 and Teleservice 62 as appropriate.
NOTE: Some facilities associated with alternate speech/ facsimile group 3 may not be available with version 1 of MAP. In particular, the incall modification procedure following an inter MSC handover is not supported by this version. This imposes the limitation that for all calls it will not be possible to change between speech and facsimile following an inter MSC handover.
|
43.048
|
Security Mechanisms for SIM Toolkit Application; Stage 2
|
TS
|
4.0.0
|
T3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.048/43048-400.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 GSM 11.11 [5] and allows remote management of files on the Subscriber Identity Module (SIM) in conjunction with SMS and the SIM Data Download feature of GSM 11.14 [6].
For SIM cards based on GSM 03.19 [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 SIM cards 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 GSM PLMN and an entity in the SIM.
Secured Packets contain application messages to which certain mechanisms according to GSM 02.48 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the GSM PLMN and on the SIM. The Sending/Receiving Entity in the GSM PLMN and the SIM are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
43.063
|
Packet Data on Signalling channels service (PDS) Service description, Stage 2
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.063/43063-400.zip
|
The present document specifies stage two of the Packet Data on Signalling channels service (PDS) which allows packet data transmission in GSM networks on dedicated channels.
|
44.008
|
Mobile radio interface layer 3 specification
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.008/44008-400.zip
|
This EN specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM), Radio Resource (RR) management and Session Management (SM). The detailed descriptions of the protocols and the related procedures are described in GSM 04.18, TS 23.108 and TS 24.008.
When the notations for "further study" or "FS" or "FFS" are present in this ETS they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in GSM 04.03.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07.
|
44.063
|
Packet Data on Signalling channels Service (PDS) Service Description, Stage 3
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.063/44063-400.zip
|
The present document specifies the protocols for connection management of packet data on signalling channels which is applied on the air interface, the PDSS1 protocol and the PDSS2 protocol.
|
52.071
|
Location Services (LCS); Location services (LCS) management
|
TS
|
4.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/52_series/52.071/52071-410.zip
|
The present document describes the network management for LCS O&M within the digital cellular telecommunications system.
The present document addresses the network management architecture, functions, and protocol for LCS operations and maintenance. The information model included here defines the managed entities and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the network management interface to be open to allow interoperation between LMUs and GMLCs of different manufacturers working to the same SMLC. The present document addresses this requirement from an operations and maintenance point of view, which allows this interworking to take place. It shows the split of network management functions between GMLC, SMLC and LMU. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document, it is necessary that the content of manufacturer-dependent information fields be specified to fulfil the functionality.
It is essential for operation that a SMLC can handle the functions used by all its LMUs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
NOTE: This version contains only the SMLC-LMU interface. Other work will be undertaken in the future.
|
01.00
|
Working Procedures for SMG and PT SMG
|
TR
|
8.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.00/0100-800.zip
|
This document outlines the working methods [to be] used by SMG and its sub-groups and by PT SMG in relation to document management, i.e. handling of specifications, updating procedures, change request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures defined in ETSI. This document does not stipulate the details of the internal working of the TB sub-groups. From the Technical Specification Group point of view, a task and responsibility is given to a Working Group (WG) directly answering to SMG. In practice, the work/task may be carried out in a subgroup of that WG.
|
01.56
|
GSM Cordless Telephony System (CTS) (Phase 1); CTS Authentication and Key Generation Algorithms Requirements
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.56/0156-800.zip
|
This specification constitutes a requirement specification for a set of associated cryptographic algorithms which is used for Cordless Telephony System (CTS) Radio Interface authentication and key management in the GSM Cordless Telephony System.
This specification is intended to provide ETSI SAGE with the information it requires in order to design and deliver a technical specification for such an algorithm set.
This specification covers the intended use of the algorithm set and use of the algorithm set specification, technical requirements on the algorithm set, requirements on the algorithm set specification and test data, and quality assurance requirements on both the algorithm set and its documentation. The document also outlines the background to the production of this specification.
|
02.01
|
Principles of telecommunication services supported by a GSM Public Land Mobile Network(PLMN)
|
TS
|
8.2.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.01/0201-821.zip
|
The present document coversthe definition of the telecommunication services supported by a GSM PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services.
|
02.02
|
Bearer Services (BS) Supported by a GSM Public Land Mobile Network (PLMN)
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.02/0202-800.zip
|
This European Telecommunication Standard (ETS) defines a set of Bearer Services to be provided to GSM PLMN subscribers by a GSM PLMN itself and in connection with other networks. This ETS should also be used as a reference for defining the corresponding required mobile network capabilities which are specified by means of the "GSM PLMN connection type" concept, defined in GSM 03.10 [4].
The recommended provision of the Bearer Services is under the control of the GSM MoU and is out of the scope of ETSI TC-SMG.
Bearer Services not included in this ETS that require modifications to the GSM signalling specifications should not be introduced unilaterally by a mobile network operator.
|
02.03
|
Teleservices Supported by a GSM Public Land Mobile Network (PLMN)
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.03/0203-800.zip
|
The present document describes and defines a recommended set of Teleservices to be supported by a GSM PLMN in connection with other networks as a basis for defining the network capabilities required.
Teleservices not included in the present document should not be introduced unilaterally by a mobile network operator, if the provision of this service requires that the GSM signalling specifications are modified.
|
02.04
|
General on Supplementary Services
|
TS
|
8.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.04/0204-810.zip
|
The purpose of this Technical Specification (TS) is to define a recommended set of supplementary services to the Teleservices and Bearer services which will be supported by a GSM PLMN in connection with other networks as a basis for the definition of the network capabilities required.
The descriptions of the different supplementary services are contained in the GSM 02.80 series.
Supplementary services not covered in GSM 02.04 or GSM 02.80 series cannot be introduced unilaterally in any GSM PLMN if they require modification of the GSM signalling Specifications.
Technical realization of supplementary services is described in GSM 03.11 and 04.10.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.