id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
25.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. |
25.887 | Beamforming enhancements | TR | 1.7.1 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.887/25887-171.zip | |
25.888 | Improvement of inter frequency and inter system measurement for 1,28 Mcps TDD | TR | 1.1.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.888/25888-110.zip | |
25.890 | High Speed Downlink Packet Access (HSDPA); User Equipment (UE) radio transmission and reception (FDD) | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.890/25890-100.zip | |
25.951 | FDD Base Station (BS) classification | TR | 1.5.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.951/25951-151.zip | |
27.104 | vObjects and other constructs for data synchronization | TS | 0.1.1 | T2 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.104/27104-011.zip | This specification serves as a vessel to manage the process of adding new vObjects and other constructs as data store types for use in data synchronisation activities within the 27.103 Wide Area Synchronisation specification.
While this first release is identified as a Release 4 specification, this is a living document and, as such, it encompasses the addition of new vObjects and other constructs for inclusion in data synchronisation activities as they become readily available, an evolving task that will continue beyond a single release. |
29.162 | Interworking between the IM CN subsystem and IP networks | TS | 1.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-130.zip | |
29.198-04 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control Service Capability Feature (SCF) | TS | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04/29198-04-500.zip | |
30.002 | Guidelines for the modification of the Mobile Application Part (MAP) | TR | 5.0.0 | N4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.002/30002-500.zip | After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects. |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-100.zip | |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-100.zip | |
31.123 | (Universal) Subscriber Interface Module ((U)SIM) toolkit interpreter test | TS | 0.3.0 | T3 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.123/31123-030.zip | |
31.131 | C-language binding to (U)SIM API | TS | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-100.zip | |
32.108 | Telecommunication management; Subscriber and equipment trace | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.108/32108-010.zip | [Editor’s note: The text is still partly from 12.08. More updating needed.]
This Technical Specification (TS) specifies the Trace facility for GSM 3G mobile networks where it refers to:
- Subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI or Public ID));
- Equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- Types of trace which relate more to network elements than to individual subscribers e.g. tracing events within a Base Station System (BSS), and so on;
- Tracing of all possible parties in e.g. a multi-party call, (although multiple calls related to the IMSI specified in the trace type field are traceable).
The control signalings on different interfaces and the characteristics of user data are within the scope of this TS, but not the actual contents of the user data.
This TS does not specify any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer.
This TS does not specify any data compression mechanisms for trace data transfer. |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 0.5.5 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-055.zip | |
33.900 | Guide to 3G security | TR | 0.4.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.900/33900-041.zip | |
41.103 | GSM Release 5 specifications | TS | 5.4.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.103/41103-540.zip | The present document identifies the GSM system specifications for Release 5. The specifications and reports of 3GPP Release 5 have a major version number 5 (e.g. 5.x.y).
Most of the core Release 5 Technical Specifications and Technical Reports were functionally frozen at either the 15th Technical Specification Group meetings in March 2002 or the 16th in June 2002.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 5 version 5.x.y specifications throughout 2002 and beyond. |
42.031 | Fraud Information Gathering System (FIGS); Service description; Stage 1 | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.031/42031-500.zip | This Technical Specification specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
This specification enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN. |
43.031 | Fraud Information Gathering System (FIGS); Service description; Stage 2 | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.031/43031-500.zip | This Technical Specification specifies the stage 2 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
Three levels of FIGS service are defined, levels 1 to 3.
Level 1 will use the facilities provided by Transferred Account Procedure (TAP).
Levels 2 and 3 will use facilities provided by Customised Applications for Mobile network Enhanced Logic (CAMEL), in particular, the information flows between the GSM Service Switching Function (gsmSSF) and GSM Service Control Function (gsmSCF). Phase 1 and Phase 2 CAMEL facilities will be used.
Connection-orientated services only are covered. |
43.900 | Support for voice optimization for the IMS in the GERAN | TR | 1.0.0 | G1 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.900/43900-100.zip | The present document provides an overview of the architecture and issues related to the provision of voice optimisation within the GERAN. |
43.930 | Iur-g interface; Stage 2 | TR | 5.1.0 | G2 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.930/43930-510.zip | The present document provides an overview of the Iur-g interface. It describes the motivation, principles and functionality of this interface. It does not contain the detailed description, which it is included in the stage 3 Technical Specifications. |
51.010-5 | Mobile Station (MS) conformance specification; Part 5: Inter-Radio-Access-Technology (RAT) (GERAN / UTRAN) interaction Abstract Test Suite (ATS) | TS | 2.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-5/51010-5-200.zip | |
51.011 | Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface | TS | 5.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.011/51011-500.zip | |
21.102 | 3rd Generation mobile system Release 4 specifications | TS | 4.9.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.102/21102-490.zip | The present document identifies the 3rd generation mobile system specifications for Release 4. The specifications and reports of 3G Release 4 have a major version number 4 (e.g. 4.x.y).
Most of the core Release 4 Technical Specifications and Technical Reports were functionally frozen at the 11th Technical Specification Group meetings (TSG#11) in March 2001.
NOTE 1: Functionally frozen means that no further functionality/features may be incorporated into the set of specifications, and that only corrective Change Requests (CRs) are to be accepted and agreed.
NOTE 2: It can be expected that corrective CRs will be introduced into the Release 4 version 4.x.y specifications throughout 2001 and beyond. |
22.112 | USIM Application Toolkit (USAT) Interpreter; Stage 1 | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.112/22112-400.zip | |
23.073 | Support of Localised Service Area (SoLSA); Stage 2 | TS | 4.0.0 | N4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.073/23073-400.zip | The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43. |
23.171 | Location Services (LCS); Functional description; Stage 2 (UMTS) | TS | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.171/23171-400.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-200.zip | |
23.814 | Separating RR and MM specific parts of the MS Classmark | TR | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.814/23814-400.zip | |
23.821 | Architecture Principles for Reelase 2000 | TR | 1.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.821/23821-101.zip | The scope of this Technical Report is to list architectural requirements, features, functions and solutions of UMTS inside the scope of UMTS Release 00. These are working assumptions agreed by TSG SA WG2. The TR focuses on
- new/modified functionality as compared to Release 99
- technical description of the features, functions and solutions of R00.
It is expected that this TR will act as a basis for the detailed Stage 2 specification work.
This TR has been created to ease the development of R00 work prior to the finalization of the R99 specifications. In conjunction with when R99 is finalized, work on the TR will cease and the relevant CRs will be produced to incorporate the contents of this TR within the R00 version of the specifications." |
23.874 | Feasibility study of architecture for network requested PDP context activation with User-ID | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.874/23874-130.zip | The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope. |
23.907 | Quality of Service (QoS) concept | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.907/23907-120.zip | Scope of this document is to provide the framework for Quality of Service in UMTS. The document shall be used as a living document which will cover all issues related Quality of Service in UMTS. |
23.913 | UMTS Turbo-Charger | TR | 1.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.913/23913-100.zip | |
23.922 | Architecture for an All IP network | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.922/23922-400.zip | This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS standard
in order to provide this architectural option within Release 2000. |
23.923 | Combined GSM and Mobile IP mobility handling in UMTS IP CN | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.923/23923-400.zip | |
23.972 | Circuit switched multimedia telephony | TR | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.972/23972-400.zip | |
24.004 | Layer 1 - General Requirements | TS | 4.0.0 | G2 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.004/24004-400.zip | |
25.107 | UTRA Repeater; Conformance testing | TS | 0.0.1 | - | https://www.3gpp.org/ftp/Specs/archive/25_series/25.107/25107-001.zip | |
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.839 | Uplink Synchronous Transmission Scheme (USTS) (Iur/Iub aspects) | TR | 0.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.839/25839-030.zip | |
25.842 | Smart antenna | TR | 1.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.842/25842-100.zip | |
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.932 | Delay budget within the access stratum | TR | 2.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.932/25932-200.zip | |
25.933 | IP transport in UTRAN | TR | 2.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.933/25933-200.zip | |
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.226 | Cellular text telephone modem; General description | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.226/26226-400.zip | |
26.230 | Cellular text telephone modem; Transmitter bit exact C-code | TS | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.230/26230-400.zip | |
26.235 | Packet switched conversational multimedia applications; Default codecs | TS | 4.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-410.zip | |
25.952 | TDD Base Station (BS) classification | TR | 1.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.952/25952-110.zip | |
30.504 | Work Plan and Study Items - RAN WG4 | TR | 2.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.504/30504-220.zip | |
26.078 | Results of the AMR noise suppression selection phase | TR | 4.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.078/26078-400.zip | |
30.002 | Guidelines for the modification of the Mobile Application Part (MAP) | TR | 4.0.1 | N4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.002/30002-401.zip | |
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.801 | Overall Project Plan | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.801/30801-110.zip | |
30.802 | Project plan on Bearer Services and QoS | TR | 4.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.802/30802-400.zip | After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects. |
30.804 | Project plan on GSM/UMTS Interoperation and Mobility Management | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.804/30804-100.zip | |
30.806 | Project plan on Location based services | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.806/30806-100.zip | |
30.808 | Project plan on Packet Architecture and Circuit Architecture | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.808/30808-100.zip | |
30.810 | Project plan on Security | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.810/30810-100.zip | |
30.812 | Project plan on Services and Service platforms | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.812/30812-100.zip | |
32.104 | Telecommunication management; 3G Performance Management | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.104/32104-400.zip | |
32.105 | 3G charging and billing; Stage 2 description | TS | 0.0.4 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.105/32105-004.zip | This Technical Specification describes the Architecture, Principals and Call Event specifications of charging and billing for the provision of service and services by a 3G system.
This standard is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. This standard will elaborate on the charging requirements described in the Charging Principles in UMTS 22.01 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
The call and event data generated by the network elements of the 3G network, is required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as historical evidence in dealing with customer service and billing complaints;
In addition to the information collected from these network elements, network management functions are required for the administration of charging data.
For the purpose of the present document, the call and event data is considered to be collected, in real-time, by network element function (NEF) blocks located within the recording entities.
The data collected by the NEFs is sent to, or collected by, the appropriate Operations System Function (OSF) blocks for storage and further processing.
The location of the OSF is implementation specific and may, for example, be provided either by an Administration Centre (ADC) or integrated within the network elements themselves.
The following is beyond the scope of this TS, and therefore this TS does not describe:
-
The objectives of this standardisation are:
• to provide the descriptions of events and triggers for the generation of Call detail records;
- to provide the descriptions for Call and event Call detail records;
- to produce a description of the collection techniques for accounting administration and CDR generation;
and
- to define a method for the transmission of CDRs over an open interface. |
32.106-1 | Telecommunication management; Configuration Management (CM); Part 1: Concept and requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-1/32106-1-400.zip | |
32.106-8 | Telecommunication management; Configuration Management (CM); Part 8: Name convention for Managed Objects | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-8/32106-8-400.zip | |
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.112-1 | Telecommunication management; Generic Integration Reference Point (IRP) management; Part 1: Requirements | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.112-1/32112-1-200.zip | |
32.112-2 | Telecommunication management; Generic Integration Reference Point (IRP) management; Part 2: Information service | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.112-2/32112-2-200.zip | |
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. |
33.800 | Principles for Network Domain Security | TR | 0.3.5 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.800/33800-035.zip | |
33.904 | Report on the Evaluation of 3GPP Standard Confidentiality and Integrity Algorithms | TR | 2.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.904/33904-200.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.