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
|
|---|---|---|---|---|---|---|
29.198-04-2 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 2: Generic call control Service Capability Feature (SCF) | TS | 5.9.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-591.zip | |
29.198-04-3 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 3: Multi-party call control Service Capability Feature (SCF) | TS | 5.10.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-5a0.zip | |
29.198-04-4 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 4: Multimedia call control Service Capability Feature (SCF) | TS | 5.9.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-591.zip | |
29.198-05 | Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF) | TS | 5.10.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-5a0.zip | |
29.198-06 | Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF) | TS | 5.8.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-580.zip | |
29.198-07 | Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF) | TS | 5.8.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-581.zip | |
29.198-08 | Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF) | TS | 5.9.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-590.zip | |
29.198-11 | Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF) | TS | 5.8.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-580.zip | |
29.198-12 | Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF) | TS | 5.9.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-590.zip | |
29.198-13 | Open Service Access (OSA) Application Programming Interface (API); Part 13: Policy management Service Capability Feature (SCF) | TS | 5.7.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-570.zip | |
29.198-14 | Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF) | TS | 5.7.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-571.zip | |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 5.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-520.zip | |
29.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 5.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-520.zip | |
29.207 | Policy control over Go interface | TS | 5.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.207/29207-590.zip | |
29.208 | End-to-end Quality of Service (QoS) signalling flows | TS | 5.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.208/29208-590.zip | |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 5.22.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-5m0.zip | |
29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | TS | 5.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-5d0.zip | |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 5.22.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-5m0.zip | |
29.278 | Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS) | TS | 5.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-540.zip | |
29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | TS | 5.16.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-5g0.zip | |
29.329 | Sh interface based on the Diameter protocol; Protocol details | TS | 5.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-5b0.zip | |
29.414 | Core network Nb data transport and transport signalling | TS | 5.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-510.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 5.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-520.zip | |
29.903 | Feasibility Study on SS7 signalling transport in the core network with SCCP-User Adaptation (SUA) layer | TR | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.903/29903-500.zip | |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 5.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-501.zip | |
29.998-01 | Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping | TR | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-500.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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-500.zip | |
29.998-04-4 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 4: Multiparty Call Control ISC | TR | 5.0.3 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-503.zip | |
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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-500.zip | |
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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-500.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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06/29998-06-500.zip | |
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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-500.zip | |
30.531 | Work Plan and Working Procedures - RAN WG3 | TR | 0.35.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.531/30531-0z1.zip | |
30.902 | Guidelines for the modification of the Mobile Application Part (MAP) in Phase 2+ | TR | 5.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.902/30902-501.zip | |
31.048 | Security mechanisms for the (U)SIM application toolkit; Test specification | TS | 5.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.048/31048-510.zip | The present document covers the minimum characteristics considered as necessary in order to provide compliance to 3GPP TS 23.048 " Security Mechanisms for the (U)SIM application toolkit; Stage 2" [6].
The present document describes the technical characteristics and methods of test for testing the Security Mechanisms for the (U)SIM application toolkit. It specifies the following parts:
- test applicability
- test environment description
- tests format
- test area reference
- conformance requirements
- Test Area Files
- test procedure
- test coverage
- a description of the associated testing tools that shall be used. |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 5.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-521.zip | |
31.102 | Characteristics of the Universal Subscriber Identity Module (USIM) application | TS | 5.15.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-5f0.zip | |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 5.14.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-5e0.zip | |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 5.12.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-5c0.zip | |
31.112 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter architecture description | TS | 5.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.112/31112-520.zip | |
31.113 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter byte codes | TS | 5.6.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.113/31113-560.zip | |
31.114 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter protocol and administration | TS | 5.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.114/31114-530.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 5.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-500.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 5.4.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-541.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 5.0.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-501.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 5.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-500.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 5.6.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-560.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-550.zip | |
32.102 | Telecommunication management; Architecture | TS | 5.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-560.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 5.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-511.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 5.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-590.zip | |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.7.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-571.zip | |
32.111-4 | Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-5a0.zip | |
32.200 | Telecommunication management; Charging management; Charging principles | TS | 5.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.200/32200-590.zip | The present document describes the principles of charging and billing for the provision of service and services by a 3G‑system.
The present document elaborates on the charging requirements described in the Charging Principles in 3GPP TS 22.101 [1]. It allows the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and references these where appropriate.
The Charging Data Records (CDRs) generated by the network elements of the 3G network, are required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network operators and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as archival information in dealing with customer service and billing complaints.
In addition to the information collected from network elements, network management functions are required for the administration of charging data.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in the present document which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs used in the Circuit Switched (CS) domain are specified in document3GPP TS 32.205 [5]. The CDRs content and transport within the PS domain are described in3GPP TS 32.215 [6] document, while CDRs used for application services are defined in document3GPP TS 32.235 [17].
The relationship among these charging specifications is illustrated in figure 1.1.
Figure 1.1: Charging Documents Structure
For the purpose of the present document, the charging data is considered to be generated and collected by charging functions in the network elements.
Charging data fields are collected and CDRs generated by the network elements for transfer to the billing system. For the packet switched domain, the CDRs are first sent to the Charging Gateway Function (CGF) for storage and further processing. The CGF may be a distinct network element or may be integrated into the packet domain network elements themselves.
The objectives of the present document are:
- to describe principles of charging in a 3G network;
- to provide a description of the charging architecture; and
- to provide the descriptions of events and triggers for the generation of Charging Data Records (CDRs). |
32.205 | Telecommunication management; Charging management; Charging data description for the Circuit Switched (CS) domain | TS | 5.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.205/32205-590.zip | The GSM and UMTS PLMNs support a wide range of circuit based services. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions.
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in TS 32.200 [22] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node.
The present document specifies the structure and the contents of the CDRs that are collected by the relevant network elements for circuit switched services in 2G (GSM) and 3G (UMTS) networks. It also defines the syntax for the transfer of these CDRs from the collecting nodes to billing post-processing systems using standard file transfer protocols.
The CDRs content and transport within the PS domain are described in TS 32.215 [23] document, while CDRs used for application services are defined in document TS 32.235 [24].
The relationship among these charging specifications is illustrated in figure 1.
Figure 1: Charging Documents Structure
The interface definitions of GSM 12.05 are maintained for 2G, in order to assure backward compatibility to earlier GSM releases.
The charging architecture and principles that the present document is based on are specified in TS 32.200 [22].
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella TS 32.200 [22]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential. |
32.215 | Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain | TS | 5.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.215/32215-590.zip | The GSM and UMTS PLMN support a wide range of packet based services by means of the General Packet Radio Service (GPRS), as defined in 3GPP TS 22.060 [1] and 3GPP TS 23.060 [2]. In order to enable operators the ability to provide a commercially viable service, there is a need to provide charging functions. For GPRS these functions include the generation of Charging Data Records (CDRs) by the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN) as well as the transport of these CDRs to a Billing System (BS) through a Charging Gateway Function (CGF).
The present document is part of a series of documents specifying charging functionality in UMTS networks. The UMTS charging architecture and principles are specified in document TS 32.200 [3] which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The CDRs content and transport within the PS domain are described in the present document. The CDRs used in the Circuit Switched (CS) domain are specified in document TS 32.205 [4] while CDRs used for application services are defined in document TS 32.235 [5]. The present document structure is depicted in figure 1.
Figure 1: Charging Documents Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common to charging in UMTS domains or subsystems are provided in the umbrella document [3]. To avoid unnecessary duplications, they are not repeated in the present document unless it is essential. |
32.225 | Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS) | TS | 5.11.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.225/32225-5b0.zip | The present document covers both online and offline charging for the IMS. For clarity, the terms Offline Charging and Online charging as applied to the IMS are defined here in clause 3. These definitions are the same as listed in TS 32.200 [2].
The IMS charging architecture details, requirements, definitions and principles are listed in TS 32.200 [2] and therefore are not repeated here.
In the present document the charging data triggers, message content and format are specified along with the transport of these messages using the Diameter protocol. Details about charging message flows and the definitions of the Diameter AVPs are also included in the present document. This information is divided into two main clauses: Online Charging and Offline Charging. |
32.235 | Telecommunication management; Charging management; Charging data description for application services | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.235/32235-550.zip | The present document is part of a series of documents specifying charging functionality in UMTS network with application services. The UMTS core network charging principles are specified in document TS 32.200 [2], which provides an umbrella for other charging documents that specify the structure and content of the CDRs and the interface protocol that is used to transfer them to the collecting node. The document structure is defined in figure 1. The CDR content and transport for application services are described in the present document especially for MMS. As the basis and reference for this work is taken the functional description of the MMS specified for stage 1 in TS 22.140[3] and stage 2 in TS 23.140 [4].
Figure 1 Charging Document Structure
All references, abbreviations, definitions, descriptions, principles and requirements that are common are defined in the 3GPP Vocabulary [1] and specialised to charging in UMTS domains or subsystems are provided in the umbrella document [2]. |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 5.0.2 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-502.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 5.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-501.zip | |
32.301-1 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): requirements | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-1/32301-1-200.zip | |
32.301-2 | Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service | TS | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-2/32301-2-200.zip | |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 5.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-520.zip | |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-520.zip | |
32.304 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.304/32304-521.zip | |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 5.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-510.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 5.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-510.zip | |
32.321 | Telecommunication management; Test management Integration Reference Point (IRP); Requirements | TS | 5.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-501.zip | |
32.322 | Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) | TS | 5.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-510.zip | |
32.323 | Telecommunication management; Test management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.323/32323-510.zip | |
32.324 | Telecommunication management; Test management Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.324/32324-510.zip | |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-550.zip | |
32.403 | Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM | TS | 5.12.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-5c0.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 5.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-501.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 5.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-501.zip | |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 5.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-530.zip | |
32.603 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.603/32603-530.zip | |
32.604 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.604/32604-500.zip | |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 5.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-511.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-550.zip | |
32.613 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-511.zip | |
32.614 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.614/32614-501.zip | |
32.615 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 5.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-560.zip | |
32.621 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-500.zip | |
32.622 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-550.zip | |
32.623 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-540.zip | |
32.624 | Telecommunication management; Configuration Management (CM); Generic network resources: Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.624/32624-550.zip | |
32.625 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.625/32625-550.zip | |
32.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-500.zip | |
32.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 5.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-590.zip | |
32.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-530.zip | |
32.634 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.634/32634-540.zip | |
32.635 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.635/32635-550.zip | |
32.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-500.zip | |
32.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 5.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-560.zip | |
32.643 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 5.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-550.zip | |
32.644 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 5.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-560.zip | |
32.645 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 5.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.645/32645-570.zip | |
32.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-500.zip | |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 5.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-530.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.