id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
29.199-16 | Open Service Access (OSA); Parlay X web services; Part 16: Geocoding | TS | 7.1.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-16/29199-16-712.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-17/29199-17-702.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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-18/29199-18-700.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-19/29199-19-702.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 | 7.0.2 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-20/29199-20-702.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.198-15 | Open Service Access (OSA) Application Programming Interface (API); Part 15: Multi-media Messaging (MM) Service Capability Feature (SCF) | TS | 7.1.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-15/29198-15-711.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-05 | Open Service Access (OSA) Application Programming Interface (API); Part 5: User interaction Service Capability Feature (SCF) | TS | 7.1.1 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-05/29198-05-711.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.205 | Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 | TS | 7.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.205/29205-710.zip | |
29.198-14 | Open Service Access (OSA) Application Programming Interface (API); Part 14: Presence and Availability Management (PAM) Service Capability Feature (SCF) | TS | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.198-14/29198-14-700.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.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping | TS | 7.12.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.213/29213-7c0.zip | |
29.204 | Signalling System No. 7 (SS7) security gateway; Architecture, functional description and protocol details | TS | 7.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.204/29204-710.zip | |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 7.18.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-7i0.zip | |
29.229 | Cx and Dx interfaces based on the Diameter protocol; Protocol details | TS | 7.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.229/29229-7c0.zip | |
29.230 | Diameter applications; 3GPP specific codes and identifiers | TS | 7.16.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-7g0.zip | |
29.232 | Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3 | TS | 7.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.232/29232-7b0.zip | |
29.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3 | TS | 7.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.234/29234-7f0.zip | The present document defines the stage-3 protocol description for several reference points in the WLAN-3GPP Interworking System.
The present document is applicable to:
• The Dw reference point between the 3GPP AAA Server and an SLF.
• The Wa reference point between the WLAN AN and the 3GPP AAA Proxy.
• The Wd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
• The Wx reference point between the 3GPP AAA Server and the HSS.
• The Wm reference point between the 3GPP AAA Server and the PDG.
• The Wg reference point between the 3GPP AAA Server/Proxy and the WAG.
• The Pr reference point between the 3GPP AAA Server and the PNA. |
29.240 | 3GPP Generic User Profile (GUP); Stage 3; Network | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.240/29240-700.zip | |
29.278 | Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS) | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.278/29278-700.zip | |
29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | TS | 7.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-7d0.zip | |
29.202 | Signalling System No. 7 (SS7) signalling transport in core network; Stage 3 | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.202/29202-700.zip | |
29.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3 | TS | 7.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.333/29333-750.zip | |
29.212 | Policy and Charging Control (PCC); Reference points | TS | 7.16.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.212/29212-7g0.zip | |
29.329 | Sh interface based on the Diameter protocol; Protocol details | TS | 7.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-780.zip | |
29.214 | Policy and charging control over Rx reference point | TS | 7.12.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.214/29214-7c0.zip | |
29.414 | Core network Nb data transport and transport signalling | TS | 7.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-730.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-700.zip | |
29.332 | Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface | TS | 7.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-7c0.zip | |
29.421 | TISPAN; NGN Release 1; Endorsement of 3GPP TS 29.162 Interworking between IM CN Sub-system and IP networks | TS | 7.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.421/29421-710.zip | The present document describes the interworking between the TISPAN IMS and an external IP network including other IMS networks for IP multimedia service support.
The present document addresses the areas of control and user plane interworking through the network functions, which include the IBCF and I-BGF. For the specification of control plane interworking, the interworking between IMS SIP and an external SIP profile are detailed in terms of the procedures required for the support of both IMS originated and terminated SIP sessions.
In particular, the present document describes the protocol mappings for support of communications between networks using different IP versions or between networks with NATs operating at their border. |
29.424 | TISPAN; H.248 Profile for controlling Trunking Media Gateways; Protocol specification | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.424/29424-700.zip | The present document defines the profile of the Gateway Control Protocol (ITU-T Recommendation H.248.1 [3]), for controlling Trunking Media Gateways (TMGW) for both the PSTN/ISDN Emulation and IMS Core Subsytems. Thus the scope of this Profile is a subset of the 3GPP profile for the Mn interface defined in TS 129 332 [2]. |
29.433 | TISPAN; IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 and 29.229 modified] | TS | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.433/29433-700.zip | The present document provides the ETSI TISPAN endorsement of the 3GPP TS 29.228 [1] " Cx and Dx interfaces; Signalling flows and messages contents" and the 3GPP TS 29.229 [2] "IP Multimedia (IM) Subsystem Cx and Dx interfaces based on the DIAMETER protocol; Protocol details".
The present document provides the necessary adaptations to the above specifications, in order to comply with the requirements of NGN Release 2. |
29.412 | TISPAN; Interworking; Trunking Gateway Control Procedures for interworking between NGN and external CS networks | TS | 7.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.412/29412-700.zip | The present document defines the control procedures for trunk gateways when PSTN/ISDN emulation and PSTN/ISDN simulation services in an NGN Network require interworking with ETSI PSTN/ISDN services in a ISUP network. Interworking with BICC networks is not included in the scope of TISPAN R2.
Existing profiles will be evaluated, in order to determine if they can be re-used, with possible modifications, or if a completely new profile is to be defined. |
29.427 | TISPAN; Endorsement of the SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched CS) networks [3GPP TS 29.163 (Release 7), modified] | TS | 7.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.427/29427-710.zip | The present document provides the ETSI endorsement of the 3GPP TS 29.163 (V7.1.0) [1].
The clauses 7.2.3 and 7.4 of 3GPP TS 29.163 [1] specify the signalling interworking between ISDN User Part (ISUP) protocols and SIP in order to support services that can be commonly supported by ISUP and SIP-based network domains.
The clause 9.2.3.3.5 specifies how ringing tone is applied at the gateway when interworking ISUP and SIP.
The present document specifies the principles of interworking between the ETSI TISPAN IMS and ISUP based legacy CS networks, in order to support IM basic voice calls, therefore all the references to interworking between IMS and BICC are out of scope of the present document.
The present document is a protocol interworking specification; therefore all references to the user plane interworking are out of scope of the present document.
The present document specifies the interworking between ETSI SIP profile (as specified within ES 283 003 [3]) and ISUP, as specified in EN 300 356-1 [2] respectively. |
29.800 | Signalling System No. 7 (SS7) Security Gateway; Architecture, functional description and protocol details | TR | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.800/29800-700.zip | The present document is a temporary container for the functional description of the SS7 Security Gateway. The document covers also network architecture, routeing considerations, and protocol details. The contents of this report when stable will be moved into a Technical Specification 3GPP TS ab.cde. At the same time specific material related to MAPsec will be removed from 3GPP TS 29.002 [1]. |
29.802 | (G)MSC-S - (G)MSC-S Nc Interface based on the SIP-I protocol | TR | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.802/29802-700.zip | The present document provides a study into providing a SIP-I based Nc interface (G)MSC-S - (G)MSC-S as an alternative to the existing BICC definition. The document covers the functional description, network architecture and protocol definition for the SIP-I based solution. The contents of this report when stable shall be moved into a Technical Specification 3GPP TS ab.cde along with modifications to existing specifications. |
29.801 | Feasibility study of using M2PA in 3GPP networks | TR | 7.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.801/29801-700.zip | The present document provides a study into the advantage and disadvantage of M2PA comparing with M3UA and provides a study into the possibility of introducing M2PA in 3GPP.
The present document also specifies the functionalities required on the protocol level to meet the requirements of BICC, MAP and CAP.
If necessary, the interactive between M2PA and M3UA should be studied. |
29.998-01 | Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping | TR | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-700.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.814 | Bandwidth saving at Nb interface with IP transport | TR | 7.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.814/29814-710.zip | The present document investigates solutions for a simple, optional transport format for the Nb interface and IP transport that allows transporting several RTP/NbFP/codec payload PDUs of different user plane connections within one packet. The solution shall minimise impacts to existing network characteristics, in particular jitter and packet delay. The transport format shall be suitable for any type of payload transported within NbFP. Though primarily intended and possibly optimised for NbFP transport within 3GPP circuit-switched core networks, the multiplexing design shall be generic and future proof by not precluding support of non-NbFP payload types, e.g. standard VoIP bearers or other interfaces such as Iu.
Furthermore, backward compatible signalling extensions required to negotiate the use of this transport option, to set up multiplexing connections, and to assign bearers to these connections are investigated.
The benefits and drawbacks of multiplexing at the Nb interface are investigated. |
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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-700.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.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 7.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-700.zip | |
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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-700.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.863 | Feasibility Study for the multimedia inter-working between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks | TR | 7.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.863/29863-720.zip | The present document provides a feasibility study for the interworking of multimedia calls between the IP Multimedia CN Subsystem and CS networks (i.e. PSTN, ISDN and GSM/UMTS CS networks).
The present document study and outlines different solutions and functionality required within the MGW to deliver the user plane aspects between IM CN subsystems and CS networks for support of basic multimedia calls. It also outlines the solutions and functionality required within the MGCF and SGW to deliver the control plane aspects between IM CN subsystems and CS networks to support basic multimedia calls.
The document also studies the MONA interworking impacts, and which parts of MONA are feasible, or even possible, to interwork.
The user plane interworking necessary to cover the basic multimedia calls is also outlined and studied.
The different aspects studied for the different scenarios should encompass the transport protocol, transcoding and signalling issues for negotiation and mapping of bearer capabilities and QoS information. |
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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-1/29998-06-1-700.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-08 | Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP | TR | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-700.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]. |
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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-700.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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-700.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]. |
30.302 | 1.28 Mcps TDD enhanced uplink: RAN WG2 Stage 2 decisions | TR | 7.1.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.302/30302-710.zip | This document is a Technical Report which captures the Stage 2 decisions on the support of 1.28 Mcps TDD Enhanced Uplink in UTRA. |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 7.7.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-770.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 7.2.2 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-722.zip | |
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 | 7.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-2/29998-06-2-700.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]. |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 7.17.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-7h0.zip | |
30.817 | Telecommunication management; Project scheduling and open issues for SA5, Release 7 | TR | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.817/30817-700.zip | The purpose of this document is to contain the updated Work Item Descriptions (WIDs) and capture status of all SA5 work items of the current 3GPP Release in order for the group to get an overview of current ongoing work.
This TR is used as a mean to provide input to the complete 3GPP work plan that is handled by MCC.
Status list of Work items can be found at the end of the present document.
List of SA5 Release 7 specifications can be found at the end of the present document.
The SA5 Release 7 work has been started in September 2005 and finished in June 2007. |
31.114 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter protocol and administration | TS | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.114/31114-700.zip | The present document specifies the transmission protocol to be used to communicate with the USAT Interpreter and the administrative structures and procedures to administer the USAT Interpreter.
The present document does not specify any USAT Interpreter byte code commands. |
31.112 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter architecture description | TS | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.112/31112-700.zip | The present document defines the stage 2 description for the USAT Interpreter system. As the second stage of a three-level structure, it is derived from the stage 1 service description.
The present document defines the overall architecture for the USAT Interpreter system:
Role models;
System architecture;
Function and information flow.
The stage 3 documents shall conform to the present document. |
31.113 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter byte codes | TS | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.113/31113-700.zip | The present document specifies the byte codes that are recognised by an USAT Interpreter. The byte codes primary purpose is to provide efficient programmatic access to the SIM Application Toolkit commands.
The design objectives of the byte code set are:
- Compact representation for efficient transmission over the air interface.
- Minimisation of USAT Interpreter complexity to minimise SIM footprint and ease compliance testing.
- Easily configured and extended.
- Source language independent although XML-style mark-up languages are explicitly envisioned.
- Transport bearer independent (e.g. SMS, GPRS...)
- Transport protocol independent.
- Independent from design of external entities. |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 7.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-710.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-700.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 7.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-710.zip | |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 7.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-730.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 7.7.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-770.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 7.6.2 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-762.zip | |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 7.9.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-790.zip | |
31.131 | C-language binding to (U)SIM API | TS | 7.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-710.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 7.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-750.zip | |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 7.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-730.zip | |
31.919 | 2G/3G Java Card™ Application Programming Interface (API) based applet interworking | TR | 7.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.919/31919-700.zip | The present document describes:
- Description of TS 43.019 [1] APIs and TS 102 241 [2] / TS 31.130 [7] APIs interworking.
- The behaviour and limitations of the TS 43.019 [1] APIs used in 3G environment. |
32.102 | Telecommunication management; Architecture | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-720.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-700.zip | |
32.111-5 | Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions | TS | 7.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-701.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. |
31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | TS | 7.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-740.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 7.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-710.zip | |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-700.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 | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-720.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-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-710.zip | |
32.154 | Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.154/32154-700.zip | |
32.150 | Telecommunication management; Integration Reference Point (IRP) Concept and definitions | TS | 7.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-730.zip | |
32.151 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-720.zip | The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. |
32.152 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-710.zip | 3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire. |
32.172 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.172/32172-710.zip | The present document defines the Network Resources Model (NRM) for the SuM IRP. |
32.141 | Telecommunication management; Subscription Management (SuM) architecture | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-700.zip | |
32.171 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.171/32171-700.zip | The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present SuM NRM IRP. |
32.175 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.175/32175-700.zip | The purpose of this Subscription Management (SuM) Network Resource Model IRP XML definition is to define the mapping of the IRP information model (see TS 32.172 [5]) to the protocol specific details necessary for implementation of this IRP in an XML environment.
This specification is related to 3GPP TS 32.172 V9.3.X. |
32.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 7.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-780.zip | The present document is part of a series of Technical Specifications (TSs) specifying charging functionality and charging management in Packet Switched networks (GSM/UMTS, EPS). The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain / subsystem / service (offline charging);
- the content of real-time charging messages per domain / subsystem /service (online charging);
- the functionality of online and offline charging for those domains / subsystems / services;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for the charging TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for the Packet Switched (PS) domain based on the functional stage 2 description in TS 23.060 [201], TS 23.401 [208] and TS 23.402 [209].
The offline and online charging description for the PS domain encompasses also fixed broadband access in the convergent scenario deployment (i.e. both the fixed broadband access network and Evolved Packet Core (EPC) owned by a single operator) based on the functional stage 2 description in the corresponding Annex of TS 23.203 [215].
This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PS domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52];
- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in TS 32.299 [50].
Note that a CAMEL based prepaid function and protocol is also specified for the PS domain (TS 23.078 [206] and TS 29.078 [202]). CAMEL entities and functions are outside the scope of the present document.
All terms, definitions and abbreviations used in the present document, which are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in PS domains, services or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-700.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102]. |
32.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 7.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-770.zip | |
32.270 | Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-720.zip | |
32.273 | Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-710.zip | |
32.250 | Telecommunication management; Charging management; Circuit Switched (CS) domain charging | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-710.zip | |
32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-700.zip | |
32.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-720.zip | |
32.296 | Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-700.zip | |
32.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-710.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify
- the content of the CDRs per domain and subsystem (converged and offline charging);
- the content of real-time charging events per domain / subsystem (converged charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240 [1].
The present document specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in TS 23.271 [201], and the Ranging and Sidelink Positioning Converged Charging description based on TS 23.586 [206]. This charging description includes the offline and online charging architecture and scenarios specific to the LCS and converged charging architecture and scenarios specific to the Ranging and Sidelink Positioning, as well as the mapping of the common 3GPP architecture specified in TS 32.240 [1] onto the LCS domain including Ranging and Sidelink Positioning. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator’s billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52].
- The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 [50].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [55].
- The charging service of 5G system is specified in TS 32.291 [56].
All terms, definitions and abbreviations, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.272 | Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging | TS | 7.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-750.zip | |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 7.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-790.zip | |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 7.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-720.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-700.zip | |
32.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | TS | 7.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-710.zip | |
32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 7.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-750.zip | |
32.305 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.305/32305-700.zip | The present document specifies the XML Definitions for the Notification Integration Reference Point (Notification IRP) as it applies to Itf-N, in accordance with Notification IRP IS definitions [3].
This XML Definitions specification defines the Notification IRP XML Notification header format.
This specification is related to 3GPP TS 32.302 V9.0.X. |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-700.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [5]).
This Solution Set specification is related to 3GPP TS 32.302. |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 7.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-700.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.