id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
---|---|---|---|---|---|---|
29.199-09
|
Open Service Access (OSA); Parlay X web services; Part 9: Terminal location
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-900.zip
|
The present document is Part 9 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Location Web Service aspects of the interface. All aspects of the Terminal Location Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-10
|
Open Service Access (OSA); Parlay X web services; Part 10: Call handling
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-900.zip
|
The present document is Part 10 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Handling Web Service aspects of the interface. All aspects of the Call Handling Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-11
|
Open Service Access (OSA); Parlay X web services; Part 11: Audio call
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-900.zip
|
The present document is Part 11 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Audio Call Web Service aspects of the interface. All aspects of the Audio Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The web service had been extended to support media.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-12
|
Open Service Access (OSA); Parlay X web services; Part 12: Multimedia conference
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-900.zip
|
The present document is Part 12 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia Conference Web Service aspects of the interface. All aspects of the Multimedia Conference Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-13
|
Open Service Access (OSA); Parlay X web services; Part 13: Address list management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-900.zip
|
The present document is Part 13 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Address List Management Web Service aspects of the interface. All aspects of the Address List Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-14
|
Open Service Access (OSA); Parlay X web services; Part 14: Presence
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-900.zip
|
The present document is Part 14 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence Web Service aspects of the interface. All aspects of the Presence Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
|
29.199-15
|
Open Service Access (OSA); Parlay X web services; Part 15: Message broadcast
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-15/29199-15-900.zip
|
The present document is Part 15 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Message Broadcast Web Service aspects of the interface. All aspects of the Message Broadcast Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-16
|
Open Service Access (OSA); Parlay X web services; Part 16: Geocoding
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-16/29199-16-900.zip
|
The present document is Part 16 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Geocoding Web Service aspects of the interface. All aspects of the Geocoding Web Service are defined here, these being:
• Name spaces
• Sequence diagrams
• Data definitions
• Interface specification plus detailed method descriptions
• Fault definitions
• Service policies
• WSDL Description of the interfaces
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-17
|
Open Service Access (OSA); Parlay X web services; Part 17: Application-driven Quality of Service (QoS)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-17/29199-17-900.zip
|
The present document is Part 17 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Application-driven Quality of Service (QoS) Web Service aspects of the interface. All aspects of the Application-driven QoS Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-18
|
Open Service Access (OSA); Parlay X web services; Part 18: Device capabilities and configuration
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-18/29199-18-900.zip
|
The present document is Part 18 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Device Capabilities and Configuration Web Service aspects of the interface. All aspects of the Device Capabilities and Configuration Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-19
|
Open Service Access (OSA); Parlay X web services; Part 19: Multimedia streaming control
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-19/29199-19-900.zip
|
The present document is Part 19 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia streaming control Web Service aspects of the interface. All aspects of the Multimedia streaming control Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-20
|
Open Service Access (OSA); Parlay X web services; Part 20: Multimedia multicast session management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-20/29199-20-900.zip
|
The present document is Part 20 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-21
|
Open Service Access (OSA); Parlay X web services; Part 21: Content management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-21/29199-21-900.zip
|
The present document is Part 21 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-22
|
Open Service Access (OSA); Parlay X web services; Part 22: Policy
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-22/29199-22-900.zip
|
The present document is Part 22 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Web Service aspects of the interface. All aspects of the Policy Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
|
29.202
|
Signalling System No. 7 (SS7) signalling transport in core network; Stage 3
|
TS
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-900.zip
| |
29.204
|
Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details
|
TS
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.204/29204-900.zip
| |
29.205
|
Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-930.zip
| |
29.212
|
Policy and Charging Control (PCC); Reference points
|
TS
|
9.19.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.212/29212-9j0.zip
| |
29.213
|
Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping
|
TS
|
9.16.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.213/29213-9g0.zip
| |
29.214
|
Policy and charging control over Rx reference point
|
TS
|
9.17.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.214/29214-9h0.zip
| |
29.215
|
Policy and Charging Control (PCC) over S9 reference point; Stage 3
|
TS
|
9.14.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.215/29215-9e0.zip
| |
29.228
|
IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents
|
TS
|
9.12.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-9c0.zip
| |
29.229
|
Cx and Dx interfaces based on the Diameter protocol; Protocol details
|
TS
|
9.7.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-970.zip
| |
29.230
|
Diameter applications; 3GPP specific codes and identifiers
|
TS
|
9.18.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-9i0.zip
| |
29.231
|
Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3
|
TS
|
9.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.231/29231-910.zip
| |
29.232
|
Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3
|
TS
|
9.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-920.zip
| |
29.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3
|
TS
|
9.4.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.234/29234-941.zip
| |
29.272
|
Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol
|
TS
|
9.14.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.272/29272-9e0.zip
| |
29.238
|
Interconnection Border Control Functions (IBCF) - Transition Gateway (TrGW) interface, Ix interface; Stage 3
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.238/29238-930.zip
| |
29.240
|
3GPP Generic User Profile (GUP); Stage 3; Network
|
TS
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-900.zip
| |
29.235
|
Interworking between SIP-I based circuit-switched core network and other networks
|
TS
|
9.11.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.235/29235-9b0.zip
| |
29.273
|
Evolved Packet System (EPS); 3GPP EPS AAA interfaces
|
TS
|
9.15.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.273/29273-9f0.zip
| |
29.274
|
3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3
|
TS
|
9.14.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.274/29274-9e0.zip
| |
29.275
|
Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3
|
TS
|
9.8.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.275/29275-980.zip
| |
29.276
|
3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3
|
TS
|
9.5.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.276/29276-950.zip
| |
29.277
|
Optimised handover procedures and protocol between EUTRAN access and non-3GPP accesses (S102); Stage 3
|
TS
|
9.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.277/29277-920.zip
| |
29.278
|
Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS)
|
TS
|
9.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-900.zip
| |
29.279
|
Mobile IPv4 (MIPv4) based mobility protocols; Stage 3
|
TS
|
9.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.279/29279-910.zip
| |
29.280
|
Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC
|
TS
|
9.9.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.280/29280-990.zip
| |
29.281
|
General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.281/29281-930.zip
| |
29.282
|
Mobile IPv6 vendor specific option format and usage within 3GPP
|
TS
|
9.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.282/29282-910.zip
| |
29.292
|
Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS)
|
TS
|
9.7.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.292/29292-970.zip
| |
29.303
|
Domain Name System Procedures; Stage 3
|
TS
|
9.5.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.303/29303-950.zip
| |
29.305
|
InterWorking Function (IWF) between MAP based and Diameter based interfaces
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.305/29305-930.zip
| |
29.311
|
Service Level Interworking (SLI) for messaging services
|
TS
|
9.3.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.311/29311-930.zip
| |
29.328
|
IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents
|
TS
|
9.16.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-9g0.zip
| |
29.329
|
Sh interface based on the Diameter protocol; Protocol details
|
TS
|
9.5.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-950.zip
| |
29.332
|
Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface
|
TS
|
9.5.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-950.zip
| |
29.333
|
Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.333/29333-930.zip
| |
29.334
|
IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3
|
TS
|
9.3.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.334/29334-930.zip
| |
29.335
|
User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3
|
TS
|
9.4.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.335/29335-941.zip
| |
29.364
|
IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability
|
TS
|
9.4.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.364/29364-940.zip
| |
29.414
|
Core network Nb data transport and transport signalling
|
TS
|
9.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-900.zip
| |
29.415
|
Core network Nb interface user plane protocols
|
TS
|
9.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-910.zip
| |
29.658
|
SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification
|
TS
|
9.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.658/29658-910.zip
| |
29.909
|
Diameter-based protocols usage and recommendations in 3GPP
|
TR
|
9.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-900.zip
| |
29.994
|
Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults
|
TR
|
9.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-900.zip
| |
29.998-01
|
Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-900.zip
|
The present document is suggesting a mapping of the Application Programming Interface (API) for Open Service Access (OSA) onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations, and provides an overview of the content and structure of the various parts of the present document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-04-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in 3GPP TS 29.198-4 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-04-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 4: Multiparty Call Control ISC
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in [5] can be mapped onto SIP methods.
The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-05-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-05-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations, within the context of SMS. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-06-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 1: Mapping to Mobile Application Part (MAP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-1/29998-06-1-900.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-06-2
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 2: Mapping to Session Initiation Protocol (SIP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-2/29998-06-2-900.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto IMS ISC Interface (SIP) operations.
The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-08
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-900.zip
|
The present document investigates how the OSA Data Session Control Interface Class methods defined in 3GPP TS 29.198-8 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
30.819
|
Telecommunication management; Project scheduling and open issues for SA5, Release 9
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.819/30819-900.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
|
31.101
|
UICC-terminal interface; Physical and logical characteristics
|
TS
|
9.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-920.zip
| |
31.102
|
Characteristics of the Universal Subscriber Identity Module (USIM) application
|
TS
|
9.19.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-9j0.zip
| |
31.103
|
Characteristics of the IP Multimedia Services Identity Module (ISIM) application
|
TS
|
9.4.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-940.zip
| |
31.111
|
Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)
|
TS
|
9.12.2
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-9c2.zip
| |
31.115
|
Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications
|
TS
|
9.1.1
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-911.zip
| |
31.116
|
Remote APDU Structure for (U)SIM Toolkit applications
|
TS
|
9.4.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-940.zip
| |
31.120
|
UICC-terminal interface; Physical, electrical and logical test specification
|
TS
|
9.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-900.zip
| |
31.121
|
UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification
|
TS
|
9.6.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-960.zip
| |
31.122
|
Universal Subscriber Identity Module (USIM) conformance test specification
|
TS
|
9.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-920.zip
| |
31.124
|
Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification
|
TS
|
9.7.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-970.zip
| |
31.130
|
(U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card
|
TS
|
9.4.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-940.zip
| |
31.131
|
C-language binding to (U)SIM API
|
TS
|
9.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-900.zip
| |
31.133
|
IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™
|
TS
|
9.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-920.zip
| |
31.213
|
Test specification for (U)SIM; Application Programming Interface (API) for Java Card™
|
TS
|
9.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-920.zip
| |
31.220
|
Characteristics of the Contact Manager for 3GPP UICC applications
|
TS
|
9.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-910.zip
| |
31.221
|
Contact Manager Application Programming Interface (API); Contact Manager API for Java Card
|
TS
|
9.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-910.zip
| |
31.900
|
SIM/USIM internal and external interworking aspects
|
TR
|
9.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-900.zip
| |
32.101
|
Telecommunication management; Principles and high level requirements
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-920.zip
| |
32.102
|
Telecommunication management; Architecture
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-900.zip
| |
32.111-1
|
Telecommunication management; Fault Management; Part 1: 3G fault management requirements
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-910.zip
| |
32.111-2
|
Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-930.zip
| |
32.111-3
|
Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-910.zip
|
The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.111-2 V7.1.X.
|
32.111-5
|
Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-900.zip
|
The present document specifies the XML Definitions for the Alarm Integration Reference Point (Alarm IRP) as it applies to Itf-N, in accordance with Alarm IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
The present document defines the XML syntax of Alarm IRP notifications that is to be used for the Alarm IRP SOAP Solution Set and in conjunction with Notification Log IRP XML Definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format [4]. The document defines also the XML syntax for the IOC definitions of the Alarm IRP IS [3], which are used by the XML definitions for the Alarm IRP notifications and the Alarm IRP IS operations.
This specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.111-7
|
Telecommunication management; Fault Management; Part 7: Alarm IRP SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-7/32111-7-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Alarm IRP: Information Service (3GPP TS 32.111-2 [4]).
This Solution Set specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.121
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-900.zip
| |
32.122
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.122/32122-900.zip
| |
32.123
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.123/32123-900.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP CORBA Solution Set, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.0.
|
32.125
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.125/32125-930.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP XML file format definition, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This file format definition specification is related to TS 32.122 v9.0.X.
|
32.127
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.127/32127-910.zip
|
The present specifies the SOAP Solution Set for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.X.
|
32.140
|
Telecommunication management; Subscription Management (SuM) requirements
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-910.zip
| |
32.141
|
Telecommunication management; Subscription Management (SuM) architecture
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-900.zip
| |
32.150
|
Telecommunication management; Integration Reference Point (IRP) Concept and definitions
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-920.zip
| |
32.151
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
|
TS
|
9.4.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-940.zip
| |
32.152
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-930.zip
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.