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.192 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Comfort noise aspects | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.192/26192-700.zip | |
26.191 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Error concealment of erroneous or lost frames | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.191/26191-700.zip | |
26.190 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.190/26190-700.zip | |
26.201 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Frame structure | TS | 7.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.201/26201-710.zip | |
26.194 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD) | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.194/26194-700.zip | |
26.230 | Cellular text telephone modem; Transmitter bit exact C-code | TS | 7.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.230/26230-710.zip | |
26.202 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Interface to Iu, Uu and Nb | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.202/26202-700.zip | |
26.231 | Cellular text telephone modem; Minimum performance requirements | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.231/26231-700.zip | |
26.193 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Source controlled rate operation | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.193/26193-700.zip | |
26.226 | Cellular text telephone modem; General description | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.226/26226-700.zip | |
26.204 | Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; ANSI-C code | TS | 7.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.204/26204-710.zip | |
26.234 | Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs | TS | 7.9.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-790.zip | |
26.233 | Transparent end-to-end Packet-switched Streaming service (PSS); General description | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.233/26233-700.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.235 | Packet switched conversational multimedia applications; Default codecs | TS | 7.4.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-740.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.245 | Transparent end-to-end Packet switched Streaming Service (PSS); Timed text format | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.245/26245-700.zip | |
26.244 | Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP) | TS | 7.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.244/26244-730.zip | |
26.246 | Transparent end-to-end Packet-switched Streaming Service (PSS); 3GPP SMIL language profile | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.246/26246-700.zip | |
26.243 | ANSI-C code for the fixed-point distributed speech recognition extended advanced front-end | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.243/26243-700.zip | |
26.236 | Packet switched conversational multimedia applications; Transport protocols | TS | 7.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.236/26236-730.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.273 | ANSI-C code for the fixed-point Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.273/26273-700.zip | |
26.401 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.401/26401-700.zip | |
26.274 | Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec; Conformance testing | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.274/26274-700.zip | |
26.290 | Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Transcoding functions | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.290/26290-700.zip | |
26.402 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.402/26402-700.zip | |
26.405 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.405/26405-700.zip | |
26.404 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder Spectral Band Replication (SBR) part | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.404/26404-700.zip | |
26.403 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification; Advanced Audio Coding (AAC) part | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.403/26403-700.zip | |
26.304 | Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Floating-point ANSI-C code | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.304/26304-700.zip | |
26.406 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Conformance testing | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.406/26406-700.zip | |
26.410 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code | TS | 7.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.410/26410-720.zip | |
26.902 | Video codec performance | TR | 7.1.2 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.902/26902-712.zip | |
26.411 | General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code | TS | 7.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.411/26411-730.zip | |
26.346 | Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs | TS | 7.11.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.346/26346-7b0.zip | |
26.914 | Multimedia telephony over IP Multimedia Subsystem (IMS); Optimization opportunities | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.914/26914-700.zip | |
26.412 | Source code for 3GP file format | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.412/26412-700.zip | |
26.911 | Codec(s) for Circuit-Switched (CS) multimedia telephony service; Terminal implementor’s guide | TR | 7.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.911/26911-710.zip | |
26.936 | Performance characterization of 3GPP audio codecs | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.936/26936-700.zip | |
26.937 | Transparent end-to-end Packet-switched Streaming Service (PSS); Real-time Transport Protocol (RTP) usage model | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.937/26937-700.zip | |
26.935 | Packet Switched (PS) conversational multimedia applications; Performance characterisation of default codecs | TR | 7.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.935/26935-720.zip | |
26.943 | Recognition performance evaluations of codecs for Speech Enabled Services (SES) | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.943/26943-700.zip | |
26.976 | Performance characterization of the Adaptive Multi-Rate Wideband (AMR-WB) speech codec | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.976/26976-700.zip | |
26.946 | Multimedia Broadcast/Multicast Service (MBMS) user service guidelines | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.946/26946-700.zip | |
26.978 | Results of the Adaptive Multi-Rate (AMR) noise suppression selection phase | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.978/26978-700.zip | |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-700.zip | |
26.944 | End-to-end multimedia services performance metrics | TR | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.944/26944-700.zip | |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-700.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 | 7.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-700.zip | |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-700.zip | |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-700.zip | |
27.007 | AT command set for User Equipment (UE) | TS | 7.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-760.zip | |
27.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-700.zip | |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-700.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 | 7.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-740.zip | |
29.011 | Signalling Interworking for supplementary services | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-700.zip | |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 7.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-710.zip | |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 7.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-700.zip | |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 7.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-730.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 | 7.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-710.zip | |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-700.zip | |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 7.17.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-7h0.zip | |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-700.zip | |
29.109 | Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 | TS | 7.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.109/29109-7d0.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 | 7.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.161/29161-720.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.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 7.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-710.zip | |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 7.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-760.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.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-700.zip | |
29.198-01 | Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-700.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.164 | Interworking between the 3GPP CS domain with BICC or ISUP as signalling protocol and external SIP-I networks | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.164/29164-700.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.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 7.12.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-7c0.zip | |
29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | TS | 7.28.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.163/29163-7s0.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.198-04-1 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 1: Call control common definitions | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-1/29198-04-1-700.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.162 | Interworking between the IM CN subsystem and IP networks | TS | 7.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-740.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.198-03 | Open Service Access (OSA) Application Programming Interface (API); Part 3: Framework | TS | 7.1.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-03/29198-03-710.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-02 | Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-02/29198-02-700.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-04-2 | Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 2: Generic call control Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-2/29198-04-2-700.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-06 | Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-06/29198-06-700.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-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 | 7.0.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-3/29198-04-3-701.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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-4/29198-04-4-700.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 | 7.0.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-04-5/29198-04-5-701.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-07 | Open Service Access (OSA) Application Programming Interface (API); Part 7: Terminal capabilities Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-07/29198-07-700.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-13 | Open Service Access (OSA) Application Programming Interface (API); Part 13: Policy management Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-13/29198-13-700.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-12 | Open Service Access (OSA) Application Programming Interface (API); Part 12: Charging Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-12/29198-12-700.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-11 | Open Service Access (OSA) Application Programming Interface (API); Part 11: Account management Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-11/29198-11-700.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-08 | Open Service Access (OSA) Application Programming Interface (API); Part 8: Data session control Service Capability Feature (SCF) | TS | 7.0.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-08/29198-08-701.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-16 | Open Service Access (OSA) Application Programming Interface (API); Part 16: Service broker Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-16/29198-16-700.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 | 7.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-01/29199-01-720.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 | 7.4.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-02/29199-02-740.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 | 7.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-03/29199-03-720.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 | 7.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-04/29199-04-720.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 | 7.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-05/29199-05-720.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 | 7.2.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-06/29199-06-722.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 | 7.2.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-07/29199-07-722.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-08/29199-08-702.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 | 7.2.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-722.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-702.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 | 7.2.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-720.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 | 7.1.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-711.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-702.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 | 7.4.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-741.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 | 7.2.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-15/29199-15-721.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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.