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.230 | Diameter applications; 3GPP specific codes and identifiers | TS | 6.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-6b0.zip | |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 6.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-6e0.zip | |
29.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3 | TS | 6.18.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.234/29234-6i0.zip | The present document defines the stage-3 protocol description for several reference points in the WLAN-3GPP Interworking System.
The present document is applicable to:
• The Dw reference point between the 3GPP AAA Server and an SLF.
• The Wa reference point between the WLAN AN and the 3GPP AAA Proxy.
• The Wd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
• The Wx reference point between the 3GPP AAA Server and the HSS.
• The Wm reference point between the 3GPP AAA Server and the PDG.
• The Wg reference point between the 3GPP AAA Server/Proxy and the WAG.
• The Pr reference point between the 3GPP AAA Server and the PNA. |
29.240 | 3GPP Generic User Profile (GUP); Stage 3; Network | TS | 6.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-610.zip | |
29.278 | Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS) | TS | 6.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-610.zip | |
29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | TS | 6.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-6f0.zip | |
29.329 | Sh interface based on the Diameter protocol; Protocol details | TS | 6.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-670.zip | |
29.332 | Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface | TS | 6.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-6e0.zip | |
29.414 | Core network Nb data transport and transport signalling | TS | 6.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-610.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 6.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-610.zip | |
29.846 | Multimedia Broadcast/Multicast Service (MBMS); CN1 procedure description | TR | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.846/29846-600.zip | The present document discusses procedures required in the Core Network to support the Multimedia Broadcast/Multicast Service (MBMS) requirements that are outlined in 3GPP TS 22.146 [2] within the architectural solutions discussed in 3GPP TS 23.246 [3]. |
29.847 | Conferencing based on SIP, SDP, and other protocols; Functional models, information flows and protocol details | TR | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.847/29847-600.zip | The present document is a temporary container for the functional models, flows and protocol details for the conferencing service within the IP Multimedia Core Network subsystem (IMS) based on the Session Initiation Protocol (SIP), SIP Events, the Session Description Protocol (SDP) , the Conference Policy Control Protocol (CPCP) and other protocols. The document covers also instant messaging conferences. The contents of this report when stable will be moved into the Technical Specification 3GPP TS 23.218 [3], 3GPP TS 24.228 [4] and 3GPP TS 24.229 [5].
Editor's note: This TR will also include information on conference floor control, which will be using different protocols than SIP and SDP (see clause 9), as e.g. described in draft-wu-sipping-floor-control-04.txt. This information might be moved either to TS 24.229 or to another 3GPP document.
Editor's note: The "other protocols" that are mentioned here need to be listed in detail, in order to replace the phrase "other protocols". This TR only covers protocols in the scope of CN1.
Editor's note: The work on instant messaging conferences is related to the work under the work item for IMS messaging, WID 11039, and the decision is to be made on contributed text as in which document it will appear.
Editor's note: The ongoing work on floor control and conferencing in CN5 needs to be taken into account.
This document does not cover the signalling between a MRFC and a MRFP.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SIP Events, SDP and other protocols. Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document includes information applicable to network operators, service providers and manufacturers.
Editor's note: Agreed material is held in this TR for an interim period of time, and the material transferred into release 6 versions of 23.218, 24.228 and 24.229 at a later time. This has the advantage that:
It creates a location where the material may stabilise outside a document under CR control, thus fulfilling the function of the original annexes in the IN CN subsystem documents.
It avoids the need to create release 6 mirror CRs for all release 5 changes to the IM CN subsystem.
This TR will not be published. |
29.903 | Feasibility Study on SS7 signalling transport in the core network with SCCP-User Adaptation (SUA) layer | TR | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.903/29903-600.zip | The scope of this Technical Report (TR) is to capture the results of a feasibility study on SS7 signalling transport (e.g. MAP & CAP) in a 3GPP core network with SCCP-User Adaptation (SUA) for Release-5.
With this purpose in mind, this TR evaluates the advantages and disadvantages associated with the implementation of SUA in the core network, and compares it with the SCCP/M3UA option. Therefore, an overview of M3UA is provided in this document for reference. This TR covers all scenarios such as SUA peer to peer as well as interworking with legacy SS7 network, plus the interworking between SUA and SCCP/M3UA. This TR also identifies and studies the technical issues related to SUA implementation and proposes the possible technical solutions that will enable the effient implementation of SUA, with minimum impacts on the available services.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the core network signalling. At the end of the feasibility study, the open issues are reported and their importance is assessed. Also discussed are the benefits and drawbacks with respect to the introduction of SUA into 3GPP core network signalling. |
29.962 | Signalling interworking between the 3GPP profile of the Session Initiation Protocol (SIP) and non-3GPP SIP usage | TR | 6.1.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.962/29962-611.zip | The present document investigates the SIP signalling interworking between entities of IM CN subsystems behaving as specified in the 3GPP profile of SIP and SDP in 3GPP TS 24.229 [1], with related call flow examples in 3GPP TS 24.228 [2], and SIP network entities external to the IM CN subsystems, which may not adhere to the 3GPP profile of SIP and SDP.
The present document assumes that GPRS access and service based local policy using the Go interface is applied.
Non-GPRS access to IMS may have implications on the TR, which are not yet discussed.
The considered SIP network entities external to the IM CN subsystems may feature different SIP capabilities, such as the support of arbitrary SIP options.
The document focuses on scenarios where the non-3GPP UA does not support one or more of the following SIP extensions:
Preconditions: "Integration of Resource Management and SIP" RFC 3312 [5];
Update: "The Session Initiation Protocol UPDATE Method" RFC 3311 [7];
100rel: "Reliability of Provisional Responses in SIP" RFC 3262 [6].
The present document focuses on the preconditions, the update and 100rel extensions because only these extensions imply interworking issues since they require the end-to-end cooperation of both UAs.
Security interworking may also have implications on the TR, which are not yet discussed.
The present document does not make any a priori assumptions where a possible interworking is performed within the IM CN subsystem. Any SIP network entity within the IM CN subsystem may take part in the interworking. The network entities that may become involved in a certain interworking topic are identified for each of these topics separately.
The present document features a discussion of topics, where an interworking is possibly required. Aspects of the 3GPP profile of SIP and SDP, which obviously do not require any interworking, are not discussed. An assessment of the impact and probability of occurrence of the discussed scenarios is also provided.
Problems due to network elements within the IM CN subsystem, which do not or only partly satisfy the 3GPP profile of SIP and SDP, in particular non 3GPP compliant SIP UAs, are out of scope of the present document.
The present document is dedicated exclusively to issues inherent in the SIP and SDP signalling. Related topics in a wider sense, such as IPv6 to IPv4 address translation or user plane transcoding are out of scope.
For brevity, in what follows the above SIP extensions are only mentioned if a SIP UA does not make use of them. Otherwise, it is understood that the UA makes use of them. |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-600.zip | |
29.998-01 | Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping | TR | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-600.zip | The present document is suggesting a mapping of the Application Programming Interface (API) for Open Service Access (OSA) onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations, and provides an overview of the content and structure of the various parts of the present document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-600.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 normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.4 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-604.zip | The present document investigates how the OSA Call Control Interface Class methods defined in [5] can be mapped onto SIP methods.
The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-600.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 normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-600.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 informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06/29998-06-600.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 normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
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 | 6.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-600.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 normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2]. |
30.902 | Guidelines for the modification of the Mobile Application Part (MAP) in Phase 2+ | TR | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.902/30902-600.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.101 | UICC-terminal interface; Physical and logical characteristics | TS | 6.5.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-651.zip | |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 6.14.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-6e0.zip | |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 6.15.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-6f0.zip | |
31.112 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter architecture description | TS | 6.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.112/31112-600.zip | The present document defines the stage 2 description for the USAT Interpreter system. As the second stage of a three-level structure, it is derived from the stage 1 service description.
The present document defines the overall architecture for the USAT Interpreter system:
Role models;
System architecture;
Function and information flow.
The stage 3 documents shall conform to the present document. |
31.113 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter byte codes | TS | 6.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.113/31113-630.zip | The present document specifies the byte codes that are recognised by an USAT Interpreter. The byte codes primary purpose is to provide efficient programmatic access to the SIM Application Toolkit commands.
The design objectives of the byte code set are:
- Compact representation for efficient transmission over the air interface.
- Minimisation of USAT Interpreter complexity to minimise SIM footprint and ease compliance testing.
- Easily configured and extended.
- Source language independent although XML-style mark-up languages are explicitly envisioned.
- Transport bearer independent (e.g. SMS, GPRS...)
- Transport protocol independent.
- Independent from design of external entities. |
31.114 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter protocol and administration | TS | 6.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.114/31114-600.zip | The present document specifies the transmission protocol to be used to communicate with the USAT Interpreter and the administrative structures and procedures to administer the USAT Interpreter.
The present document does not specify any USAT Interpreter byte code commands. |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 6.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-650.zip | |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-600.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 6.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-600.zip | |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 6.8.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-680.zip | |
29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | TS | 6.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-6b0.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 6.8.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-680.zip | |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 6.7.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-670.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 6.10.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-6a0.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 6.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-650.zip | |
29.208 | End-to-end Quality of Service (QoS) signalling flows | TS | 6.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.208/29208-670.zip | The present specification gives examples of QoS signalling flows for resource reservation to provide end-to-end QoS. The flows are used as bases of developing QoS related protocol descriptions for new and existing specifications.
The present specification adds detailed flows of Service Based Local Policy (SBLP) procedures over the Go and Gq interfaces and their relationship with the bearer level signalling flows over the Gn interface.
The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in TS 29.207 [7] shall be taken into consideration.
The present specification also describes the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters. |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 6.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-620.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 6.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-620.zip | |
29.207 | Policy control over Go interface | TS | 6.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.207/29207-650.zip | The present document provides the stage 3 specification of the Go interface. The functional requirements and the stage 2 specifications of the Go interface are contained in 3GPP TS 23.002 [2] and 3GPP TS 23.207 [3]. The Go interface is the interface between the GGSN and the Policy Decision Function (PDF).
The present document defines:
- the protocol to be used between PDF and GGSN over the Go interface;
- the signalling interactions to be performed between PDF and GGSN over the Go interface;
- the information to be exchanged between PDF and GGSN over the Go interface. |
31.919 | 2G/3G Java Card™ Application Programming Interface (API) based applet interworking | TR | 6.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.919/31919-610.zip | The present document describes:
- Description of TS 43.019 [1] APIs and TS 102 241 [2] / TS 31.130 [7] APIs interworking.
- The behaviour and limitations of the TS 43.019 [1] APIs used in 3G environment. |
31.131 | C-language binding to (U)SIM API | TS | 6.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-610.zip | |
32.102 | Telecommunication management; Architecture | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-630.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-690.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-620.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 6.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-601.zip | |
32.111-5 | Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions | TS | 6.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-631.zip | The present document specifies the XML Definitions for the Alarm Integration Reference Point (Alarm IRP) as it applies to Itf-N, in accordance with Alarm IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
The present document defines the XML syntax of Alarm IRP notifications that is to be used for the Alarm IRP SOAP Solution Set and in conjunction with Notification Log IRP XML Definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format [4]. The document defines also the XML syntax for the IOC definitions of the Alarm IRP IS [3], which are used by the XML definitions for the Alarm IRP notifications and the Alarm IRP IS operations.
This specification is related to 3GPP TS 32.111-2 V9.0.X. |
32.111-4 | Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-650.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 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.111-2 (V6.3.X). |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-670.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 and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.111-2 V7.1.X. |
32.150 | Telecommunication management; Integration Reference Point (IRP) Concept and definitions | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-650.zip | |
32.141 | Telecommunication management; Subscription Management (SuM) architecture | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-610.zip | |
32.152 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-630.zip | 3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire. |
32.175 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.175/32175-620.zip | The purpose of this Subscription Management (SuM) Network Resource Model IRP XML definition is to define the mapping of the IRP information model (see TS 32.172 [5]) to the protocol specific details necessary for implementation of this IRP in an XML environment.
This specification is related to 3GPP TS 32.172 V9.3.X. |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-640.zip | |
32.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-640.zip | |
32.151 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-630.zip | The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. |
32.172 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.172/32172-650.zip | The present document defines the Network Resources Model (NRM) for the SuM IRP. |
32.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 6.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-6a0.zip | The present document is part of a series of Technical Specifications (TSs) specifying charging functionality and charging management in Packet Switched networks (GSM/UMTS, EPS). The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain / subsystem / service (offline charging);
- the content of real-time charging messages per domain / subsystem /service (online charging);
- the functionality of online and offline charging for those domains / subsystems / services;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for the charging TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for the Packet Switched (PS) domain based on the functional stage 2 description in TS 23.060 [201], TS 23.401 [208] and TS 23.402 [209].
The offline and online charging description for the PS domain encompasses also fixed broadband access in the convergent scenario deployment (i.e. both the fixed broadband access network and Evolved Packet Core (EPC) owned by a single operator) based on the functional stage 2 description in the corresponding Annex of TS 23.203 [215].
This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PS domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52];
- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in TS 32.299 [50].
Note that a CAMEL based prepaid function and protocol is also specified for the PS domain (TS 23.078 [206] and TS 29.078 [202]). CAMEL entities and functions are outside the scope of the present document.
All terms, definitions and abbreviations used in the present document, which are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in PS domains, services or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.250 | Telecommunication management; Charging management; Circuit Switched (CS) domain charging | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-670.zip | |
32.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-620.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify
- the content of the CDRs per domain and subsystem (converged and offline charging);
- the content of real-time charging events per domain / subsystem (converged charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240 [1].
The present document specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in TS 23.271 [201], and the Ranging and Sidelink Positioning Converged Charging description based on TS 23.586 [206]. This charging description includes the offline and online charging architecture and scenarios specific to the LCS and converged charging architecture and scenarios specific to the Ranging and Sidelink Positioning, as well as the mapping of the common 3GPP architecture specified in TS 32.240 [1] onto the LCS domain including Ranging and Sidelink Positioning. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator’s billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52].
- The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 [50].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [55].
- The charging service of 5G system is specified in TS 32.291 [56].
All terms, definitions and abbreviations, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.270 | Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-670.zip | |
32.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 6.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-680.zip | |
32.171 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.171/32171-610.zip | The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present SuM NRM IRP. |
32.273 | Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging | TS | 6.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-660.zip | |
32.272 | Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-650.zip | |
32.296 | Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-630.zip | |
32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-610.zip | |
32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-690.zip | |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 6.12.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-6c0.zip | |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-620.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102]. |
32.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-620.zip | |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 6.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-631.zip | |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-660.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.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-630.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 6.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-601.zip | |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-610.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-630.zip | |
32.304 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.304/32304-611.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 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.
This Solution Set specification is related to 3GPP TS 32.302 V6.2.X. |
32.314 | Telecommunication management; Generic Integration Reference Point (IRP) management; Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.314/32314-600.zip | The present document specifies the CMIP Solution Set (SS) for Generic Integration Reference Point (IRP) management whose capabilities are specified in Generic Integration Reference (IRP) management: Information Service (TS 32.312 [1]).
Clauses 1 to 3 provide background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notifications, parameters and attributes defined in the IS onto their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the GDMO/ ASN.1 specification.
This Solution Set specification is related to TS 32.312 V6.0.X. |
32.313 | Telecommunication management; Generic Integration Reference Point (IRP) management; Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.313/32313-640.zip | The present document specifies the CORBA Solution Set for Generic Integration Reference Point (IRP) management whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
This Solution Set specification is related to TS 32.312 V9.0.X. |
32.322 | Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-640.zip | |
32.321 | Telecommunication management; Test management Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-600.zip | |
32.324 | Telecommunication management; Test management Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.324/32324-600.zip | The present document specifies the CMIP SS for the Test Management IRP IS defined in 3GPP TS 32.322 [8].
In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.322 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Test Management IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.322 (V6.0.X). |
32.331 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements | TS | 6.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.331/32331-601.zip | |
32.305 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.305/32305-630.zip | The present document specifies the XML Definitions for the Notification Integration Reference Point (Notification IRP) as it applies to Itf-N, in accordance with Notification IRP IS definitions [3].
This XML Definitions specification defines the Notification IRP XML Notification header format.
This specification is related to 3GPP TS 32.302 V9.0.X. |
32.323 | Telecommunication management; Test management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.323/32323-640.zip | The present document specifies the CORBA SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [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 and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to 3GPP TS 32.322 V9.0.X. |
32.334 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.334/32334-620.zip | The present document specifies the CMIP SS for the Notification Log IRP IS defined in 3GPP TS 32.332 [8].
In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.332 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Notification Log IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.332 (V6.2.X). |
32.333 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.333/32333-610.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 32.332 [6] Notification Log IRP: Information Service.
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 and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.332 V9.0.X. |
32.341 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.341/32341-620.zip | |
32.342 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS) | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.342/32342-620.zip | |
32.343 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.343/32343-630.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in File Transfer IRP: Information Service 3GPP TS 32.342 [7].
This Solution Set specification is related to 3GPP TS 32.342 V9.0.X. |
32.335 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); eXtensible Markup Language (XML) solution definitions | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.335/32335-620.zip | The present document specifies the XML Definitions for the Notification Log IRP as it applies to Itf-N, in accordance with the requirements in 3GPP TS 32.331 [3] and Information Service definitions in 3GPP TS 32.332 [4].
This XML Definitions specification defines the XML syntax of the NL IRP XML Data File.
This specification is related to 3GPP TS 32.332 V9.0.X. |
32.352 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.352/32352-630.zip | |
32.351 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.351/32351-600.zip | |
32.354 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.354/32354-600.zip | The present document specifies the CMIP SS for the Communication Surveillance IRP IS defined in 3GPP TS 32.352 [8]. In detail:
• Clause 4 provides the basic architectural concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in 3GPP TS 32.352 [8] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Communication Surveillance IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.352 (V6.0.X). |
32.361 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.361/32361-600.zip | |
32.362 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.362/32362-640.zip | |
32.363 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.363/32363-640.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
This Solution Set specification is related to 3GPP TS 32.362 V9.0.X. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.