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.911 | Codec(s) for Circuit-Switched (CS) multimedia telephony service; Terminal implementor’s guide | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.911/26911-900.zip | |
26.935 | Packet Switched (PS) conversational multimedia applications; Performance characterisation of default codecs | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.935/26935-900.zip | |
26.914 | Multimedia telephony over IP Multimedia Subsystem (IMS); Optimization opportunities | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.914/26914-900.zip | |
26.943 | Recognition performance evaluations of codecs for Speech Enabled Services (SES) | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.943/26943-900.zip | |
26.944 | End-to-end multimedia services performance metrics | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.944/26944-900.zip | |
26.946 | Multimedia Broadcast/Multicast Service (MBMS) user service guidelines | TR | 9.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.946/26946-901.zip | |
26.967 | eCall data transfer; In-band modem solution | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.967/26967-900.zip | |
26.969 | eCall data transfer; In-band modem solution; Characterization report | TR | 9.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.969/26969-910.zip | |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-900.zip | |
26.412 | Source code for 3GP file format | TS | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.412/26412-900.zip | |
26.978 | Results of the Adaptive Multi-Rate (AMR) noise suppression selection phase | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.978/26978-900.zip | |
27.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 9.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-910.zip | |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 9.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-910.zip | |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 9.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-900.zip | |
26.937 | Transparent end-to-end Packet-switched Streaming Service (PSS); Real-time Transport Protocol (RTP) usage model | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.937/26937-900.zip | |
26.976 | Performance characterization of the Adaptive Multi-Rate Wideband (AMR-WB) speech codec | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.976/26976-900.zip | |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 9.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-910.zip | |
26.936 | Performance characterization of 3GPP audio codecs | TR | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.936/26936-900.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 | 9.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-901.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 | 9.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-920.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 | 9.4.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-941.zip | |
29.011 | Signalling Interworking for supplementary services | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-900.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-900.zip | |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-900.zip | |
27.007 | AT command set for User Equipment (UE) | TS | 9.9.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-990.zip | |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 9.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-9e0.zip | |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 9.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-910.zip | |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 9.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-920.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.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 9.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-900.zip | |
29.109 | Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 | TS | 9.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.109/29109-970.zip | |
29.118 | Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification | TS | 9.9.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.118/29118-990.zip | CS Fallback in the Evolved Packet System (EPS) enables the provisioning of CS-domain services (e.g. voice call, Location Services (LCS) or supplementary services) by reuse of CS infrastructure when the UE is served by E-UTRAN. Additionally, SMS delivery via the CS core network is realized without CS fallback.
The present document specifies the procedures and the SGs Application Part (SGsAP) messages used on the SGs interface between the Mobility Management Entity (MME) in the EPS and the Visitor Location Register (VLR), to allow location management coordination and to relay certain messages related to GSM circuit switched services over the EPS system.
The present document also specifies the use of Stream Control Transmission Protocol (SCTP) for the transport of SGsAP messages.
The present document is applicable to the MME in the EPS and to the VLR. The functional split between the MME and the VLR is defined in 3GPP TS 23.272 [7]. |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-900.zip | |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-900.zip | |
29.161 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services with Wireless Local Area Network (WLAN) access and Packet data Networks (PDN) | TS | 9.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.161/29161-900.zip | The present document defines the requirements for Packet Domain interworking between a:
a) PLMN with WLAN access and PDN;
b) PLMN with WLAN access and PLMN.
The present document also defines, in clause 12, the usage of Radius at the Pp Reference Point between the Packet Data Gateway and the Presence Network Agent, see 3GPP TS 23.141 [18]. |
29.162 | Interworking between the IM CN subsystem and IP networks | TS | 9.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-970.zip | The IM CN subsystem interworks with the external IP networks through the Mb reference point.
This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking and, user plane interworking for specific interworking use cases. Clause 10 describes the IMS-Ix interface requirements in the form of Use Cases which require H.248 protocol procedures. Subclause 10.4 then details the additional Information Elements required to perform the specific procedures.
The IP version Interworking, between IP version 4 (IETF RFC 791 [9] ) and IP version 6 (IETF RFC 2460 [10] ) detailed in terms of the processes and protocol mappings required in order to support both IMS originated and terminated calls. |
29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | TS | 9.26.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.163/29163-9q0.zip | The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls.
The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice and multimedia calls.
Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229 [9]) and BICC or ISUP, as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30] and ITU-T Q761 to Q764 [4] respectively.
The present document also specifies the interworking between circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] 3GPP TS 26.111 [79], and ITU-T Recommendation H.324 [81] and packet switched multimedia services, as described in 3GPP TS 26.114 [104], in particular and the interworking between the 3GPP profile of SIP and the inband control protocols for multimedia communication as specified in ITU-T Recommendations H.245 [82] and H.324 Annex K [81].
The present document addresses two interworking scenarios with respect to the properties of the CS network:
- The CS network does not use any 3GPP specific additions.
- The CS network uses 3GPP specific additions. |
29.164 | Interworking between the 3GPP CS domain with BICC or ISUP as signalling protocol and external SIP-I networks | TS | 9.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.164/29164-920.zip | The present document defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205 [2]) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5 [20], Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW.
The present specification reuses existing interworking procedures of 3GPP TS 29.163 [4] and ITU-T Q.1912.5 [20], Profile C, as far as possible. |
29.168 | Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 | TS | 9.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.168/29168-960.zip | |
29.171 | Location Services (LCS); LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs interface | TS | 9.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.171/29171-940.zip | |
29.172 | Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface | TS | 9.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.172/29172-960.zip | |
29.173 | Location Services (LCS); Diameter-based SLh interface for Control Plane LCS | TS | 9.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.173/29173-940.zip | |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 9.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-930.zip | |
29.198-02 | Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-900.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-04-5 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 5: Conference call control Service Capability Feature (SCF) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-5/29198-04-5-900.zip | The present document is Part 4, Sub-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 Conference call control Service Capability Feature (SCF) aspects of the interface. All aspects of the Conference 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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-900.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. |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-900.zip | |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 9.16.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-9g0.zip | |
29.198-11 | Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-900.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 | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-900.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.198-10 | Open Service Access (OSA) Application Programming Interface (API); Part 10: Connectivity manager Service Capability Feature (SCF) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-10/29198-10-900.zip | The present document is Part 10 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 Connectivity Manager Service Capability Feature (SCF) aspects of the interface. All aspects of the Connectivity Manager 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-16 | Open Service Access (OSA) Application Programming Interface (API); Part 16: Service broker Service Capability Feature (SCF) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-16/29198-16-900.zip | The present document is Part 16 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 Service Broker Capability Feature (SCF) aspects of the interface. All aspects of the Service Broker 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.199-01 | Open Service Access (OSA); Parlay X web services; Part 1: Common | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-01/29199-01-900.zip | The present document is Part 1 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 aspects of the Parlay X Web Services. The following are defined here:
Name spaces.
Data definitions.
Fault definitions.
WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-02 | Open Service Access (OSA); Parlay X web services; Part 2: Third party call | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-02/29199-02-900.zip | The present document is Part 2 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Third Party Call Web Service aspects of the interface. All aspects of the Third Party Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-03 | Open Service Access (OSA); Parlay X web services; Part 3: Call notification | TS | 9.3.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-03/29199-03-930.zip | The present document is Part 3 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Call Notification Web Service aspects of the interface. All aspects of the Call Notification Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-04 | Open Service Access (OSA); Parlay X web services; Part 4: Short messaging | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-04/29199-04-900.zip | The present document is Part 4 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Short Messaging Web Service aspects of the interface. All aspects of the Short Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-05 | Open Service Access (OSA); Parlay X web services; Part 5: Multimedia messaging | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-05/29199-05-900.zip | The present document is Part 5 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Multimedia Messaging Web Service aspects of the interface. All aspects of the Multimedia Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-06 | Open Service Access (OSA); Parlay X web services; Part 6: Payment | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-06/29199-06-900.zip | The present document is Part 6 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Payment Web Service aspects of the interface. All aspects of the Payment Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-07 | Open Service Access (OSA); Parlay X web services; Part 7: Account management | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-07/29199-07-900.zip | The present document is Part 7 of the Stage 3 Parlay X Web Service specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Web Service aspects of the interface. All aspects of the Account Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-08 | Open Service Access (OSA); Parlay X web services; Part 8: Terminal status | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-08/29199-08-900.zip | The present document is Part 8 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Status Web Service aspects of the interface. All aspects of the Terminal Status Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-09 | Open Service Access (OSA); Parlay X web services; Part 9: Terminal location | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-900.zip | The present document is Part 9 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Location Web Service aspects of the interface. All aspects of the Terminal Location Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
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.199-10 | Open Service Access (OSA); Parlay X web services; Part 10: Call handling | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-900.zip | The present document is Part 10 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Call Handling Web Service aspects of the interface. All aspects of the Call Handling Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-11 | Open Service Access (OSA); Parlay X web services; Part 11: Audio call | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-900.zip | The present document is Part 11 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Audio Call Web Service aspects of the interface. All aspects of the Audio Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The web service had been extended to support media.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-12 | Open Service Access (OSA); Parlay X web services; Part 12: Multimedia conference | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-900.zip | The present document is Part 12 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Multimedia Conference Web Service aspects of the interface. All aspects of the Multimedia Conference Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-13 | Open Service Access (OSA); Parlay X web services; Part 13: Address list management | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-900.zip | The present document is Part 13 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Address List Management Web Service aspects of the interface. All aspects of the Address List Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-14 | Open Service Access (OSA); Parlay X web services; Part 14: Presence | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-900.zip | The present document is Part 14 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Web Service aspects of the interface. All aspects of the Presence Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium. |
29.199-15 | Open Service Access (OSA); Parlay X web services; Part 15: Message broadcast | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-15/29199-15-900.zip | The present document is Part 15 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Message Broadcast Web Service aspects of the interface. All aspects of the Message Broadcast Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-16 | Open Service Access (OSA); Parlay X web services; Part 16: Geocoding | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-16/29199-16-900.zip | The present document is Part 16 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Geocoding Web Service aspects of the interface. All aspects of the Geocoding Web Service are defined here, these being:
• Name spaces
• Sequence diagrams
• Data definitions
• Interface specification plus detailed method descriptions
• Fault definitions
• Service policies
• WSDL Description of the interfaces
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-17 | Open Service Access (OSA); Parlay X web services; Part 17: Application-driven Quality of Service (QoS) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-17/29199-17-900.zip | The present document is Part 17 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Application-driven Quality of Service (QoS) Web Service aspects of the interface. All aspects of the Application-driven QoS Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-18 | Open Service Access (OSA); Parlay X web services; Part 18: Device capabilities and configuration | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-18/29199-18-900.zip | The present document is Part 18 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Device Capabilities and Configuration Web Service aspects of the interface. All aspects of the Device Capabilities and Configuration Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-19 | Open Service Access (OSA); Parlay X web services; Part 19: Multimedia streaming control | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-19/29199-19-900.zip | The present document is Part 19 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Multimedia streaming control Web Service aspects of the interface. All aspects of the Multimedia streaming control Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-20 | Open Service Access (OSA); Parlay X web services; Part 20: Multimedia multicast session management | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-20/29199-20-900.zip | The present document is Part 20 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
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.199-21 | Open Service Access (OSA); Parlay X web services; Part 21: Content management | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-21/29199-21-900.zip | The present document is Part 21 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. |
29.199-22 | Open Service Access (OSA); Parlay X web services; Part 22: Policy | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-22/29199-22-900.zip | The present document is Part 22 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized 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 Web Service aspects of the interface. All aspects of the Policy Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces. |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-900.zip | |
29.204 | Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.204/29204-900.zip | |
29.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-930.zip | |
29.212 | Policy and Charging Control (PCC); Reference points | TS | 9.19.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.212/29212-9j0.zip | |
29.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping | TS | 9.16.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.213/29213-9g0.zip | |
29.215 | Policy and Charging Control (PCC) over S9 reference point; Stage 3 | TS | 9.14.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.215/29215-9e0.zip | |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 9.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-9c0.zip | |
29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | TS | 9.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-970.zip | |
29.230 | Diameter applications; 3GPP specific codes and identifiers | TS | 9.18.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-9i0.zip | |
29.231 | Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3 | TS | 9.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.231/29231-910.zip | The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231 [1]. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 [1] and TS 23.153 [2].
Interworking of SIP-I on Nc to external networks is described by TS 29.235 [3].
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later. |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 9.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-920.zip | |
29.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3 | TS | 9.4.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.234/29234-941.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.235 | Interworking between SIP-I based circuit-switched core network and other networks | TS | 9.11.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.235/29235-9b0.zip | |
29.238 | Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3 | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.238/29238-930.zip | |
29.240 | 3GPP Generic User Profile (GUP); Stage 3; Network | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-900.zip | |
29.198-15 | Open Service Access (OSA) Application Programming Interface (API); Part 15: Multi-media Messaging (MM) Service Capability Feature (SCF) | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-15/29198-15-900.zip | The present document is Part 15 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 standardized 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 Messaging Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi Media Messaging 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).
The present document 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.214 | Policy and charging control over Rx reference point | TS | 9.17.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.214/29214-9h0.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.