id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
---|---|---|---|---|---|---|
26.234
|
Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs
|
TS
|
9.10.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-9a0.zip
| |
26.235
|
Packet switched conversational multimedia applications; Default codecs
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-900.zip
| |
26.236
|
Packet switched conversational multimedia applications; Transport protocols
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.236/26236-900.zip
| |
26.237
|
IP Multimedia Subsystem (IMS) based Packet Switch Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) User Service; Protocols
|
TS
|
9.11.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.237/26237-9b0.zip
| |
26.243
|
ANSI-C code for the fixed-point distributed speech recognition extended advanced front-end
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.243/26243-900.zip
| |
26.244
|
Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)
|
TS
|
9.5.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.244/26244-950.zip
| |
26.245
|
Transparent end-to-end Packet switched Streaming Service (PSS); Timed text format
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.245/26245-900.zip
| |
26.246
|
Transparent end-to-end Packet-switched Streaming Service (PSS); 3GPP SMIL language profile
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.246/26246-900.zip
| |
26.267
|
eCall data transfer; In-band modem solution; General description
|
TS
|
9.3.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.267/26267-930.zip
| |
26.268
|
eCall data transfer; In-band modem solution; ANSI-C reference code
|
TS
|
9.4.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.268/26268-940.zip
| |
26.269
|
eCall data transfer; In-band modem solution; Conformance testing
|
TS
|
9.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.269/26269-920.zip
| |
26.273
|
ANSI-C code for the fixed-point Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.273/26273-900.zip
| |
26.274
|
Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec; Conformance testing
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.274/26274-900.zip
| |
26.290
|
Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Transcoding functions
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.290/26290-900.zip
| |
26.304
|
Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Floating-point ANSI-C code
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.304/26304-900.zip
| |
26.346
|
Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs
|
TS
|
9.15.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.346/26346-9f0.zip
| |
26.401
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.401/26401-900.zip
| |
26.402
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Additional decoder tools
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.402/26402-900.zip
| |
26.403
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification; Advanced Audio Coding (AAC) part
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.403/26403-900.zip
| |
26.404
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Enhanced aacPlus encoder Spectral Band Replication (SBR) part
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.404/26404-900.zip
| |
26.405
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Encoder specification parametric stereo part
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.405/26405-900.zip
| |
26.406
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Conformance testing
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.406/26406-900.zip
| |
26.410
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.410/26410-900.zip
| |
26.411
|
General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.411/26411-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.430
|
Timed graphics
|
TS
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.430/26430-900.zip
| |
26.902
|
Video codec performance
|
TR
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.902/26902-900.zip
| |
26.903
|
Improved video support for Packet Switched Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) Services
|
TR
|
9.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.903/26903-900.zip
| |
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.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.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.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
| |
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.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.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
| |
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
| |
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
| |
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
| |
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
| |
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
| |
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.002
|
Mobile Application Part (MAP) specification
|
TS
|
9.13.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-9d0.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
| |
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.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
| |
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.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
| |
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
| |
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
| |
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
| |
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
| |
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
| |
29.165
|
Inter-IMS Network to Network Interface (NNI)
|
TS
|
9.21.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.165/29165-9l0.zip
| |
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.198-01
|
Open Service Access (OSA) Application Programming Interface (API); Part 1: Overview
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-01/29198-01-900.zip
|
The present document is the first part of the 3GPP Specification defining the Application Programming Interface (API) for Open Service Access (OSA), and provides an overview of the content and structure of the various parts of this specification, and of the relation to other standards documents.
The OSA-specifications define an architecture that enables service application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN™ Community member companies.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.198-02
|
Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions
|
TS
|
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.
|
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-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-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.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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.