id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 4.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-401.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 4.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-440.zip | |
29.998-04-1 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping | TR | 4.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-420.zip | The present document investigates how the OSA Call Control Interface Class methods defined in 3GPP TS 29.198-4 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not... |
29.998-05-1 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-400.zip | The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normati... |
29.998-05-4 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-400.zip | The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations, within the context of SMS. The mapping of the OSA API to the CAP and relevant MAP operations is considered i... |
30.902 | Guidelines for the modification of the Mobile Application Part (MAP) in Phase 2+ | TR | 4.0.2 | C4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.902/30902-402.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 as... |
29.414 | Core network Nb data transport and transport signalling | TS | 4.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-450.zip | |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 4.17.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-4h0.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 4.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-421.zip | |
29.998-06 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User Location and User Status Service Mapping to MAP | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06/29998-06-400.zip | The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not nor... |
29.998-08 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP | TR | 4.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-400.zip | The present document investigates how the OSA Data Session Control Interface Class methods defined in 3GPP TS 29.198-8 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not nor... |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 4.17.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-4h0.zip | |
31.110 | Numbering system for telecommunication IC card applications | TS | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.110/31110-410.zip | The present document describes the numbering system for Application IDentifiers (AID) for 3G telecommunication Integrated Circuits (IC) card applications.
The numbering system described in the present document provides a means for an application and related services offered by a provider to identify if a given card con... |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-400.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-400.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 4.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-421.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 4.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-421.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-410.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 4.14.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-4e1.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 4.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-480.zip | |
32.200 | Telecommunication management; Charging management; Charging principles | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.200/32200-450.zip | The present document describes the principles of charging and billing for the provision of service and services by a 3G‑system.
The present document elaborates on the charging requirements described in the Charging Principles in 3GPP TS 22.101 [1]. It allows the generation of accurate charging information to be used in... |
32.205 | Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain | TS | 4.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.205/32205-480.zip | The GSM and UMTS PLMNs support a wide range of circuit based services. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charg... |
32.215 | Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain | TS | 4.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.215/32215-490.zip | The GSM and UMTS PLMN support a wide range of packet based services by means of the General Packet Radio Service (GPRS), as defined in 3GPP TS 22.060 [1] and 3GPP TS 23.060 [2]. In order to enable operators the ability to provide a commercially viable service, there is a need to provide charging functions. For GPRS the... |
32.225 | Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS) | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.225/32225-000.zip | The present document covers both online and offline charging for the IMS. For clarity, the terms Offline Charging and Online charging as applied to the IMS are defined here in clause 3. These definitions are the same as listed in TS 32.200 [2].
The IMS charging architecture details, requirements, definitions and princi... |
32.235 | Telecommunication management; Charging management; Charging data description for application services | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.235/32235-460.zip | The present document is part of a series of documents specifying charging functionality in UMTS network with application services. The UMTS core network charging principles are specified in document TS 32.200 [2], which provides an umbrella for other charging documents that specify the structure and content of the CDRs... |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 4.1.2 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-412.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 4.0.2 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-402.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 4.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-401.zip | |
32.111-4 | Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-460.zip | The present document defines the alarm integration reference point for the CMIP solution set. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definition... |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-420.zip | |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-450.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 (3GPP TS 32.302 [5]).
This Solution Set specification is related to 3GPP TS 32.302. |
32.304 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.304/32304-421.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 3GPP TS 32.302 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the... |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-460.zip | The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters an... |
32.102 | Telecommunication management; Architecture | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-450.zip | |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-410.zip | |
32.403 | Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM | TS | 4.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-4a0.zip | The present document describes the measurements for UMTS and combined UMTS/GSM.
TS 32.401 [12] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
Only measurement types that ar... |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-430.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-410.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-400.zip | |
32.603 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.603/32603-431.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.602 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types and methods.
Th... |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-450.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM, UMTS and LTE networks. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in... |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-400.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-460.zip | |
32.615 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-450.zip | The present document provides the main part of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [1].
The other parts of this XML file format definition are NRM-specific parts.
Those NRM-specific parts are provided by 3GPP TS 32.625 [11], 32.635 [12], 32.645 [13], 32.655 [14]... |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-400.zip | |
32.604 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.604/32604-420.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 TS 32.602 [6]. In detail:
• Clause 4 provides the basic concept of the CMIP SS and the mapping between the IOCs, operations and notificati... |
32.614 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.614/32614-430.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 TS 32.612 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP inte... |
32.622 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-440.zip | The present document specifies the Generic network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics of information object class attributes and relations visible across the reference point in a protocol... |
32.623 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-430.zip | The TS 32.62x-series (Generic Network Resources IRP) define 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 TS-family specifies a g... |
32.624 | Telecommunication management; Configuration Management (CM); Generic network resources: Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.624/32624-460.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.622 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific... |
32.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-400.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.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-410.zip | The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.632 V9.1.X. |
32.621 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-400.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.613 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-440.zip | The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service 3GPP TS 32.612 [3] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.612 V9.1.X. |
32.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-400.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.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-440.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... |
32.634 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.634/32634-411.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.632 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspe... |
32.643 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-440.zip | The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see TS 32.642 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.642 V9.3.X. |
32.644 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-430.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.642 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific a... |
32.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-400.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.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-450.zip | The present document specifies the UTRAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
The present document specifies the semantics and behaviour of information object class attributes and relations visible across the reference ... |
32.653 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.653/32653-420.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.652 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.652 V9.2.X. |
32.800 | Telecommunication management; Management level procedures and interaction with UTRAN | TR | 4.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.800/32800-400.zip | The principle objective of the present document is to provide supporting information for the O&M standardisation of a (multi-vendor) UTRAN network. The actual specification work relating to the O&M interface between Network and Network Manager can be found in [9], [10] and [11] and for the Iub interface in [1]. For thi... |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 4.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-450.zip | The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point i... |
32.654 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 4.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.654/32654-420.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.652 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific a... |
33.102 | 3G security; Security architecture | TS | 4.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-450.zip | This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
A security feature is a service capability that meets one or several security requirements. The complete set of security features address the security ... |
33.106 | 3G security; Lawful interception requirements | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-400.zip | |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 4.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-420.zip | |
33.103 | 3G security; Integration guidelines | TS | 4.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-420.zip | This technical specification defines how elements of the 3G-security architecture are to be integrated into the following entities of the system architecture.
- Home Environment Authentication Centre (HE/AuC)
- Serving Network Visited Location Register (VLR/SGSN)
- Radio Network Controller (RNC)
- Mobile station User I... |
33.200 | 3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security | TS | 4.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.200/33200-430.zip | This technical specification covers the security mechanisms and procedures necessary to protect the MAP protocol. The complete set of enhancements and extensions to facilitate security protection for the MAP protocol is termed MAPsec and it covers transport security in the MAP protocol itself and the security managemen... |
33.120 | Security Objectives and Principles | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-400.zip | The present document gives the objectives and principles of 3GPP security.
The principles state what is to be provided by 3G security as compared to the security of second generation systems. The principles will also ensure that 3G security can secure the new services and new service environments offered by 3G systems.... |
33.107 | 3G security; Lawful interception architecture and functions | TS | 4.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-430.zip | |
33.908 | 3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-400.zip | This technical report is a description of the work undertaken by SAGE Task Force for the design of the standard 3GPP Confidentiality and Integrity Algorithms (SAGE TF 3GPP), and to formally approve the release of these algorithms to 3GPP.
With regard to the design of the algorithms, the scope of the present document is... |
33.902 | Formal Analysis of the 3G Authentication Protocol | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-400.zip | This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol.
The structure of this technical specification is a... |
33.909 | 3G Security; Report on the design and evaluation of the MILENAGE algorithm set; Deliverable 5: An example algorithm for the 3GPP authentication and key generation functions | TR | 4.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.909/33909-401.zip | This public report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and... |
33.901 | Criteria for cryptographic Algorithm design process | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-400.zip | This report discusses the possibilities for acquisition of the cryptographic algorithms that has to be standardised in UMTS. The focus is on the encryption function used in the data confidentiality mechanism and the message authentication function used in the signalling data integrity mechanism.
First certain aspects o... |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 4.6.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-460.zip | |
34.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 4.10.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-4a0.zip | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are... |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 4.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-430.zip | The present document specifies the protocol conformance testing for the 3rd Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference... |
34.123-2 | User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification | TS | 4.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-430.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended appl... |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 4.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-4b0.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures fo... |
34.121 | Terminal conformance specification, Radio transmission and reception (FDD) | TS | 4.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-410.zip | The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode.
The requirements are lis... |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 4.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-420.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-410.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-400.zip | |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-400.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-400.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-400.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-400.zip | |
35.208 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-400.zip | |
41.033 | Lawful Interception requirements for GSM | TR | 4.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-401.zip | This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in... |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 4.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-400.zip | |
35.205 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-400.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced ... |
41.061 | General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.061/41061-400.zip | This TS constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60.
This TS is intended to provide the ETSI Security Algorithms Group of Experts (SAGE) with the information it requires in order to design and deliver a te... |
41.101 | Technical Specifications and Technical Reports for a GERAN-based 3GPP system | TS | 4.18.0 | SP | https://www.3gpp.org/ftp/Specs/archive/41_series/41.101/41101-4i0.zip | |
42.019 | Subscriber Identity Module Application Programming Interface (SIM API); Stage 1 | TS | 4.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.019/42019-410.zip | The present document defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
The present document includes information applicable to net... |
35.909 | 3G Security; Specification of the MILENAGE algorithm set: an example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Summary and results of design and evaluation | TR | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-400.zip | |
42.033 | Lawful Interception; Stage 1 | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-400.zip | This Technical Specification provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for this specification... |
42.009 | Security aspects | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.009/42009-410.zip | Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a P... |
42.043 | Support of Localised Service Area (SoLSA); Service description; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.043/42043-400.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.