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.909 | Diameter-based protocols usage and recommendations in 3GPP | TR | 8.1.2 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-812.zip | |
29.882 | Customized Alerting Tone (CAT) in 3G CS domain | TR | 8.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.882/29882-801.zip | The present document provides a study into providing a Customized Alerting Tones in the 3GPP CS domain. The document covers the functional description, network architecture and protocol definition to support CAT in the 3GPP CS domain for speech and multimedia calls. |
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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-800.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.863 | Feasibility Study for the multimedia inter-working between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks | TR | 8.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.863/29863-820.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-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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-800.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-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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-800.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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-800.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-01 | Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping | TR | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-800.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-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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-1/29998-06-1-800.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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-800.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]. |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 8.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-830.zip | |
31.112 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter architecture description | TS | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.112/31112-800.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.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 8.6.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-860.zip | |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-800.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 | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-2/29998-06-2-800.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 | 8.15.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-8f0.zip | |
31.113 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter byte codes | TS | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.113/31113-800.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 | 8.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-820.zip | |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 8.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-810.zip | |
31.114 | Universal Subscriber Identity Module Application Toolkit (USAT) interpreter protocol and administration | TS | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.114/31114-800.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.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 8.2.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-821.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 8.0.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-801.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 8.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-850.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 8.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-840.zip | |
31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | TS | 8.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-820.zip | |
31.131 | C-language binding to (U)SIM API | TS | 8.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-810.zip | |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 8.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-830.zip | |
31.221 | Contact Manager Application Programming Interface (API); Contact Manager API for Java Card | TS | 8.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-810.zip | |
31.220 | Characteristics of the Contact Manager for 3GPP UICC applications | TS | 8.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-820.zip | |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 8.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-820.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 8.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-860.zip | |
32.102 | Telecommunication management; Architecture | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-830.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-800.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-810.zip | |
32.111-5 | Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-810.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-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-810.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-7 | Telecommunication management; Fault Management; Part 7: Alarm IRP SOAP Solution Set (SS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-7/32111-7-810.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.122 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.122/32122-810.zip | |
32.121 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements | TS | 8.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-801.zip | |
31.919 | 2G/3G Java Card™ Application Programming Interface (API) based applet interworking | TR | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.919/31919-800.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.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-830.zip | |
32.123 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.123/32123-800.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.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-800.zip | |
32.125 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.125/32125-820.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.150 | Telecommunication management; Integration Reference Point (IRP) Concept and definitions | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-830.zip | |
32.141 | Telecommunication management; Subscription Management (SuM) architecture | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-800.zip | |
32.155 | Telecommunication management; Requirements template | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.155/32155-830.zip | |
32.152 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-800.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.171 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.171/32171-800.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.151 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 8.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-821.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.172 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.172/32172-810.zip | The present document defines the Network Resources Model (NRM) for the SuM IRP. |
32.175 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition | TS | 8.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.175/32175-811.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.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 8.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-860.zip | |
32.250 | Telecommunication management; Charging management; Circuit Switched (CS) domain charging | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-830.zip | |
32.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 8.16.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-8g0.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.153 | Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.153/32153-810.zip | |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-820.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.270 | Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-800.zip | |
32.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 8.19.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-8j0.zip | |
32.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-800.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 | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-830.zip | |
32.154 | Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.154/32154-800.zip | |
32.275 | Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging | TS | 8.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.275/32275-860.zip | |
32.280 | Telecommunication management; Charging management; Advice of Charge (AoC) service | TS | 8.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.280/32280-840.zip | |
32.273 | Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-820.zip | |
32.274 | Telecommunication management; Charging management; Short Message Service (SMS) charging | TS | 8.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.274/32274-870.zip | |
32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-810.zip | |
32.296 | Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-830.zip | |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 8.25.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-8p0.zip | |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-800.zip | |
32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 8.22.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-8m0.zip | |
32.303 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.303/32303-800.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.305 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.305/32305-800.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.307 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set (SS) | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.307/32307-830.zip | The present document specifies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [4]).
This Solution Set specification is related to 3GPP TS 32.302 V9.0.X. |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-800.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-800.zip | |
32.313 | Telecommunication management; Generic Integration Reference Point (IRP) management; Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.313/32313-800.zip | The present document specifies the CORBA Solution Set for Generic Integration Reference Point (IRP) management whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
This Solution Set specification is related to TS 32.312 V9.0.X. |
32.317 | Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP Solution Set (SS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.317/32317-810.zip | The present document specifies the SOAP Solution Set for Generic IRP management whose capabilities are specified in Generic IRP management: Information Service (3GPP TS 32.312 [1]).
This Solution Set specification is related to TS 32.312 V9.0.X. |
32.321 | Telecommunication management; Test management Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-800.zip | |
32.322 | Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-810.zip | |
32.323 | Telecommunication management; Test management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.323/32323-800.zip | The present document specifies the CORBA SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [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 3GPP TS 32.322 V9.0.X. |
32.325 | Telecommunication management; Test management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.325/32325-800.zip | The present document specifies the XML Definitions for the Test Management IRP (TMIRP) as it applies to Itf-N, in accordance with TM IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.322 V9.0.X. |
32.331 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.331/32331-800.zip | |
32.332 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.332/32332-800.zip | |
32.333 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.333/32333-800.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 32.332 [6] Notification Log IRP: Information Service.
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.332 V9.0.X. |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-800.zip | |
32.335 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); eXtensible Markup Language (XML) solution definitions | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.335/32335-800.zip | The present document specifies the XML Definitions for the Notification Log IRP as it applies to Itf-N, in accordance with the requirements in 3GPP TS 32.331 [3] and Information Service definitions in 3GPP TS 32.332 [4].
This XML Definitions specification defines the XML syntax of the NL IRP XML Data File.
This specification is related to 3GPP TS 32.332 V9.0.X. |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-800.zip | |
32.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-820.zip | |
32.341 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.341/32341-800.zip | |
32.343 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.343/32343-800.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in File Transfer IRP: Information Service 3GPP TS 32.342 [7].
This Solution Set specification is related to 3GPP TS 32.342 V9.0.X. |
32.342 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.342/32342-800.zip | |
32.351 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.351/32351-800.zip | |
32.355 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.355/32355-800.zip | The present document specifies the XML Definitions for the Communication Surveillance IRP (CSIRP) as it applies to Itf-N, in accordance with CS IRP IS definitions [3], for usage with the Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.352 V9.0.X. |
32.352 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.352/32352-800.zip | |
32.361 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.361/32361-800.zip | |
32.353 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.353/32353-800.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in TS 32.352 [6] Communication Surveillance IRP: Information Service.
This Solution Set specification is related to 3GPP TS 32.352 V9.0.X. |
32.362 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.362/32362-810.zip | |
32.363 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.363/32363-820.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
This Solution Set specification is related to 3GPP TS 32.362 V9.0.X. |
32.365 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 8.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.365/32365-801.zip | The present document specifies the XML Definitions for the Entry Point IRP (EPIRP) as it applies to Itf-N, in accordance with EP IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.362 V9.0.X. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.