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-03 | Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework | TS | 6.7.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-670.zip | |
29.198-04-1 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 1: Call control common definitions | TS | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-651.zip | |
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 | 6.4.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-641.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 | 6.6.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-661.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 | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-651.zip | |
29.198-05 | Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF) | TS | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-651.zip | |
29.198-06 | Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF) | TS | 6.6.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-661.zip | |
29.198-07 | Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF) | TS | 6.4.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-641.zip | |
29.198-08 | Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF) | TS | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-651.zip | |
29.198-11 | Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF) | TS | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-651.zip | |
29.198-12 | Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF) | TS | 6.5.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-651.zip | |
29.198-13 | Open Service Access (OSA) Application Programming Interface (API); Part 13: Policy management Service Capability Feature (SCF) | TS | 6.4.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-641.zip | |
29.198-14 | Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF) | TS | 6.3.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-631.zip | |
29.198-15 | Open Service Access (OSA) Application Programming Interface (API); Part 15: Multi-media Messaging (MM) Service Capability Feature (SCF) | TS | 6.6.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-15/29198-15-661.zip | |
29.199-01 | Open Service Access (OSA); Parlay X web services; Part 1: Common | TS | 6.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-01/29199-01-660.zip | |
29.199-02 | Open Service Access (OSA); Parlay X web services; Part 2: Third party call | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-02/29199-02-650.zip | |
29.199-03 | Open Service Access (OSA); Parlay X web services; Part 3: Call notification | TS | 6.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-03/29199-03-660.zip | |
29.199-04 | Open Service Access (OSA); Parlay X web services; Part 4: Short messaging | TS | 6.8.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-04/29199-04-680.zip | |
29.199-05 | Open Service Access (OSA); Parlay X web services; Part 5: Multimedia messaging | TS | 6.8.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-05/29199-05-680.zip | |
29.199-06 | Open Service Access (OSA); Parlay X web services; Part 6: Payment | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-06/29199-06-650.zip | |
29.199-07 | Open Service Access (OSA); Parlay X web services; Part 7: Account management | TS | 6.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-07/29199-07-660.zip | |
29.199-08 | Open Service Access (OSA); Parlay X web services; Part 8: Terminal status | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-08/29199-08-650.zip | |
29.199-09 | Open Service Access (OSA); Parlay X web services; Part 9: Terminal location | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-650.zip | |
29.199-10 | Open Service Access (OSA); Parlay X web services; Part 10: Call handling | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-650.zip | |
29.199-11 | Open Service Access (OSA); Parlay X web services; Part 11: Audio call | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-650.zip | |
29.199-12 | Open Service Access (OSA); Parlay X web services; Part 12: Multimedia conference | TS | 6.6.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-660.zip | |
29.199-13 | Open Service Access (OSA); Parlay X web services; Part 13: Address list management | TS | 6.5.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-650.zip | |
29.199-14 | Open Service Access (OSA); Parlay X web services; Part 14: Presence | TS | 6.7.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-670.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 | |
29.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 6.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-610.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. |
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. |
29.209 | Policy control over Gq interface | TS | 6.8.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.209/29209-680.zip | The present document provides the stage 3 specification of the Gq interface. The functional requirements and the stage 2 specifications of the Gq interface are contained in 3GPP TS 23.002 [2] and 3GPP TS 23.207 [3]. The Gq interface is used for session based policy set-up information exchange between the Policy Decision Function (PDF) and the Application Function (AF).
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. |
29.210 | Charging rule provisioning over Gx interface | TS | 6.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.210/29210-670.zip | The present document provides the stage 3 specification of the Gx reference point. The functional requirements and the stage 2 specifications of the Gx reference point are contained in 3GPP TS 23.125 [3]. The Gx reference point is for provisioning service data flow based charging rules between the Traffic Plane Function (TPF) and the Charging Rules Function (CRF), also known as Service Data Flow Based Charging Rules Function.
The present document defines:
- the protocol to be used between TPF and CRF over the Gx reference point;
- the information to be exchanged between TPF and CRF over the Gx reference point.
Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
3GPP TS 29.211 [15] provides callflows for Flow Based Charging, covering the signalling on the Gx reference point. |
29.211 | Rx Interface and Rx/Gx signalling flows | TS | 6.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.211/29211-640.zip | The present document provides the stage 3 specification of the Rx reference point interface.
The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.125 [2]. The Rx reference point is used to exchange Flow Based Charging information between the Charging Rules Function (CRF) and the Application Function (AF).
Whenever it is possible the present document specifies the protocol by reference to specifications produced by the IETF within the scope of Diameter and to the Gq specification 3GPP TS 29.209 [4].
The present specification also provides detailed signalling flows for FBC procedures over the interfaces that correspond to Rx and Gx reference points. |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 6.17.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-6h0.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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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.102 | Characteristics of the Universal Subscriber Identity Module (USIM) application | TS | 6.23.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-6n0.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 | |
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 | |
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 | |
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 | |
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 | |
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.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.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 | |
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.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.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 | |
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 | |
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 | |
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.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-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-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.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 | |
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-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 | |
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.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.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.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 | |
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 | |
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 | |
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 | |
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 | |
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.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.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 | |
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 | |
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.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.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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.