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 |
|---|---|---|---|---|---|---|
26.131 | Terminal acoustic characteristics for telephony; Requirements | TS | 5.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.131/26131-520.zip | |
26.171 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; General description | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.171/26171-500.zip | |
26.190 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions | TS | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.190/26190-510.zip | |
26.191 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Error concealment of erroneous or lost frames | TS | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.191/26191-510.zip | |
26.192 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Comfort noise aspects | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.192/26192-500.zip | |
26.173 | ANSI-C code for the Adaptive Multi-Rate - Wideband (AMR-WB) speech codec | TS | 5.12.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.173/26173-5c0.zip | |
26.194 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD) | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.194/26194-500.zip | |
26.201 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Frame structure | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.201/26201-500.zip | |
26.174 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec test sequences | TS | 5.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.174/26174-540.zip | |
26.193 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Source controlled rate operation | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.193/26193-500.zip | |
26.231 | Cellular text telephone modem; Minimum performance requirements | TS | 5.2.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.231/26231-521.zip | |
26.204 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; ANSI-C code | TS | 5.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.204/26204-540.zip | |
26.202 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Interface to Iu, Uu and Nb | TS | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.202/26202-510.zip | |
26.233 | Transparent end-to-end Packet-switched Streaming service (PSS); General description | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.233/26233-500.zip | The present document contains a general description of a transparent packet-switched streaming service in 3GPP-defined networks. In particular, it defines the usage scenarios, overall high-level end-to-end service concept, and lists terminal related functional components. It also lists any identified service interworking requirements. |
26.230 | Cellular text telephone modem; Transmitter bit exact C-code | TS | 5.0.2 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.230/26230-502.zip | |
26.235 | Packet switched conversational multimedia applications; Default codecs | TS | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-510.zip | The present document introduces the set of default codecs for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document is applicable, but not limited, to services such as PS video telephony and Push to talk over Cellular (PoC) as well as Combined CS and IMS services (CSI). For Multimedia Telepphony Service for IMS (MTSI), all media handling, including codecs, is defined in TS 26.114 [50]. This specification does not apply for MTSI.
The applicability of this specification to GERAN is FFS. |
26.236 | Packet switched conversational multimedia applications; Transport protocols | TS | 5.7.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.236/26236-570.zip | The present document introduces the required protocols for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communications are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document describes the required protocol related elements for 3G PS multimedia terminal:
• required SDP signalling regarding the media type bit rate, packet size, packet transport frequency;
• usage of RTP payload for media types;
• bandwidth adaptation;
• QoS negotiation.
The present document is applicable, but not limited, to packet switched video telephony. All media handling, including codecs, for Multimedia Telephony Service for IMS (MTSI) service is defined in [35]. This specification does not apply to MTSI.
The applicability of the present document to GERAN is FFS. |
26.226 | Cellular text telephone modem; General description | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.226/26226-500.zip | |
26.937 | Transparent end-to-end Packet-switched Streaming Service (PSS); Real-time Transport Protocol (RTP) usage model | TR | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.937/26937-500.zip | |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-500.zip | |
26.976 | Performance characterization of the Adaptive Multi-Rate Wideband (AMR-WB) speech codec | TR | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.976/26976-510.zip | |
27.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 5.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-5a0.zip | |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 5.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-500.zip | |
26.911 | Codec(s) for Circuit-Switched (CS) multimedia telephony service; Terminal implementor’s guide | TR | 5.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.911/26911-510.zip | |
26.234 | Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs | TS | 5.7.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-570.zip | |
27.005 | Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) | TS | 5.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-501.zip | |
27.007 | AT command set for User Equipment (UE) | TS | 5.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-570.zip | |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 5.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-500.zip | |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 5.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-500.zip | |
27.103 | Wide Area Network Synchronization | TS | 5.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.103/27103-500.zip | This specification provides a definition of a Wide Area Synchronization protocol. The synchronization protocol is based upon current synchronization industry standards.
The present document covers Wide Area Network Synchronization between current and future mobile communication end-user devices, desktop applications and server-based information servers. This is a living document and, as such, it will evaluate new technologies (e.g. XML) for inclusion as they become readily available. |
27.901 | Report on Terminal Interfaces - An Overview | TR | 5.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.901/27901-500.zip | The present document discusses external and internal interfaces of a terminal, with the exception of the radio and USIM interfaces. The focus of the study has been on external interfaces, to identify where existing industry standards can be used and whether there would be a need for specifications to be produced within 3GPP. |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 5.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-550.zip | |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 5.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-560.zip | |
29.011 | Signalling Interworking for supplementary services | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-500.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 5.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-510.zip | |
29.007 | General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) | TS | 5.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-5e0.zip | |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 5.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-500.zip | |
29.010 | Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) | TS | 5.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-570.zip | |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 5.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-550.zip | |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 5.9.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-591.zip | |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-500.zip | |
29.198-01 | Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview | TS | 5.8.3 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-583.zip | The present document is the first part of the 3GPP Specification defining the Application Programming Interface (API) for Open Service Access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
The OSA-specifications define an architecture that enables service application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.198-02 | Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions | TS | 5.11.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-5b0.zip | The present document is Part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Common Data definitions of the OSA. The Common Data definitions contain data-types that are common across the rest of the OSA API. All aspects of the Common Data are defined here, these being:
- Data definitions;
- IDL Description of the data types;
- WSDL Description of the data types;
- Reference to the Java™ API description of the data types.
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
29.198-03 | Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework | TS | 5.9.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-591.zip | The present document is Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Framework aspects of the interface. All aspects of the Framework are defined in the present document, these being:
• Sequence Diagrams;
• Class Diagrams;
• Interface specification plus detailed method descriptions;
• State Transition diagrams;
• Data definitions;
• IDL Description of the interfaces.
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
29.198-04-1 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 1: Call control common definitions | TS | 5.8.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-581.zip | The present document is Part 4, Sub-part 1 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the common definitions used by the Call Control Service Capability Features (SCF).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is Part 4, Sub-part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Generic Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Generic Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
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 | The present document is Part 4, Sub-Part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Party Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Party Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is Part 4, Sub-part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multi-Media Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Media Call Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | This document is Part 5 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the User Interaction (UI) Service Capability Feature (SCF) aspects of the interface. All aspects of the User Interaction SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is Part 6 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of the Mobility SCF are defined here, these being:
- Sequence Diagrams
- Class Diagrams
- Interface specification plus detailed method descriptions
- State Transition diagrams
- Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
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 | The present document is part of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
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 | The present document is Part 8 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Data Session Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Data Session Control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is Part 11 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Account Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is Part 12 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Charging Service Capability Feature (SCF) aspects of the interface. All aspects of the Charging SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is part 13 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Policy Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. |
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 | The present document is part 14 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA).
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 concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence and Availability Management Service Capability Feature (SCF) aspects of the interface. All aspects of the Presence and Availability Management SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-operation with a number of JAIN™ Community member companies. |
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 | 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 | 5.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.208/29208-590.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.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 5.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-5e0.zip | |
29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 5.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-540.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.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 5.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-5a0.zip | The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140‑1 [26]. Descriptions and definitions provided by ETSI EN 301 140‑1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. |
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.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-500.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.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.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 | 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.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.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 | 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.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.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 | 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.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.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 | 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 | 5.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-500.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-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 | 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-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 | 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.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 | 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. |
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 | 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]. |
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.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 | 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. |
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 | |
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.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.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 | 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.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 | 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.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.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.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.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 | |
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 | |
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 | 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.102 | Telecommunication management; Architecture | TS | 5.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.