id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
29.582
|
Mission Critical Data (MCData) interworking with Land Mobile Radio (LMR) systems; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.582/29582-i00.zip
|
The present document specifies the protocols needed to support a Mission Critical Data (MCData) system interworking with a Land Mobile Radio (LMR) system based on the IWF-2 interface between an MCData server and an Interworking Function (IWF) as described in 3GPP TS 23.283 [80].
|
29.583
|
Application layer support for Personal IoT Network (PINAPP); Personal IoT Network (PIN) server services
|
TS
|
18.1.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.583/29583-i11.zip
|
The present document specifies the stage 3 protocol and data model for PIN-9 interface between the PIN application server and PIN server. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the PIN server over PIN-9 interface. The stage 2 functional requirements are defined in 3GPP TS 23.542 [10].
|
29.585
|
5G System (5GS); Session Management Function (SMF) / Centralized User Configuration (CUC) to Access Network Talker Listener (AN-TL) and Core Network Talker Listener (CN-TL) protocol aspects; Stage 3
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.585/29585-i10.zip
|
The present document specifies the protocol of communication in the 5G System between:
- the SMF/CUC and the (R)AN/AN-TL, and
- the SMF/CUC and the UPF/CN-TL,
when the (R)AN and the UPF support the Talker and Listener functionality, for the support of Time Sensitive Networking (TSN) enabled Transport Network (TN) as specified in clauses 4.4.8, 5.28a and Annex M of 3GPP TS 23.501 [2] and Annex F of 3GPP TS 23.502 [3].
|
29.641
|
3GPP Registry for Service Names and Port Numbers
|
TS
|
18.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.641/29641-i20.zip
|
The present document defines 3GPP procedures for Service Name and Port Number registry management. These procedures should be followed by 3GPP WGs when requesting new port numbers for the 3GPP allocated port number solution#6, which is specified in clause 4.4 of the 3GPP TR 29.941 [2].
The present document also maintains a database of the 3GPP allocated port numbers.
|
29.658
|
SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.658/29658-i00.zip
|
The present document specifies the Stage 3 of the real-time transfer of Tariff Information between a Charge Determination Point (CDP) and a Charge Generation Point (CGP) by means of the Session Initiation Protocol (SIP).
It identifies the protocol procedures and switching functions needed to support the transfer of tariff information related to IP multimedia services. The information needed to support the ISDN User part (ISUP) signalling aspects of charging (ES 201 296 [6]) for Advice of Charge information purposes is also specified, however, it can be used for other purposes as well where applicable.
The present document is applicable to an environment where different operators are working together. It is also applicable to a single network operator environment.
Whether the present document is applicable to a national environment and/or can be used for inter-network purposes depends on regulatory demands and/or bilateral agreements. It should be noted that there are network requirements and signalling limitations that are not covered because they are outside the scope of the present document. Examples of these are as follows:
- the on-line provided advice of charge information may not accurately reflect the correct charging rate due to discount rates, special charging arrangements, etc. It is out of scope to ensure alignment of this information;
- complaint handling between network operators in case of incorrect advice of charge information;
- explicit encryption or special security mechanisms;
- usage of the transferred tariff information for charging purposes;
- interaction between UE and CGP for possible confirmation of provided tariffs;
- any function behind the CGP towards the UE.
|
29.674
|
Interface between the UE radio Capability Management Function (UCMF) and the Mobility Management Entity (MME); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.674/29674-i00.zip
|
The present document specifies the UE Radio Capability Management Protocol used on the interface between the MME and UCMF as specified in 3GPP TS 23.401 [2]. In the related stage 2 specifications the prefix S17 is used for these common procedures realised by URCMP.
NOTE: As an alternative of URCMP, the MME could use SBI interface to access UCMF Services.
|
29.831
|
Study on NRF API enhancements to avoid signalling and storing of redundant data
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.831/29831-i00.zip
|
The present document identifies deficiencies of the NRF APIs as specified in 3GPP TS 29.510 [2] and studies potential optimization solutions. The document will focus on the following aspects:
-avoid data storage overhead in the NRF due to many NFs (especially NFs from the same NF set) registering with identical information,
-avoid signalling overhead (both in terms of payload size and number of HTTP requests) due to discovery responses containing lots of duplicate information and due to the number of data change notification sent when duplicated data are changed one by one.
-avoid processing overhead (both at NRF and its consumers) resulting e.g. from signalling overhead.
|
29.893
|
Study on IETF QUIC Transport for 5GC Service Based Interfaces
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.893/29893-i00.zip
|
The present document analyses the IETF QUIC protocol and its potential use as a transport protocol for the 5GC Service Based Interfaces.
This technical report provides an analysis of the following aspects:
- Features of transport protocol required for 5GC SBI;
- Features of QUIC applicable to 5GC SBI;
- Comparison of the applicable features of QUIC against TCP for the 5GC SBI;
- Key requirements for 5GC SBI in order to support QUIC as a transport protocol;
- Solutions for supporting the key requirements;
- Impacts to 5GC Service Based Interfaces due to introduction of QUIC.
|
29.909
|
Diameter-based protocols usage and recommendations in 3GPP
|
TR
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-i00.zip
|
The present document contains a common set of principles, rules and recommendations across 3GPP WGs to ensure Diameter-based interfaces have the same treatment for release control and generating new applications-id. Also to address in a unified manner the use/re-use of AVPs, and other Diameter BASE (see IETF RFC 3588 [x]) related decisions.
The present document covers all aspects of Diameter usage within 3GPP, including description of the current situation of Diameter usage in different 3GPP WGs (CT3, CT4, SA5) in Release 6/7, describe recommendations and conditions to re-use existing Diameter applications (3GPP or IETF application-id), commands, AVPs and/or AVP values, describe recommendations and conditions to define new Diameter applications, commands, AVPs and/or AVP values, and any other related issues, e.g. the cross-release issue, whether to apply proposed guideline back to existing Diameter applications or not, or only new SAE Diameter interfaces, etc.
To achieve maximum benefit from this work it is strongly recommended that all 3GPP Diameter-based protocols follow the recommendations in the present document.
The present document also serves a placeholder for Diameter inter-operator considerations with brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure.
|
29.935
|
Study on User Data Convergence (UDC) data model
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.935/29935-i00.zip
|
The present document analyses and evaluates the definition of a Reference Data Model (RDM) for Ud interface between Front-Ends (FEs) for the HSS application and the User Data Repository (UDR).
The stage 3 of the Ud interface in the User Data Convergence (UDC architecture) is defined in 3GPP TS 29.335 [2].
The Reference Data Model (RDM) shall comply with the Common Baseline Information Model for UDC as defined in 3GPP TS 32.182 [3] and it shall follow the concepts of the Framework for Model Handling and Management as defined in 3GPP TS 32.181 [4].
The analysis will comprise the general considerations impacting the RDM for HSS.
The analysis will comprise the following topics:
- The general considerations impacting the RDM for HSS;
- Attributes definition: names, syntax, semantics;
- Object classes & Directory Information Tree: object classes names, attributes grouping, LDAP entries, Distinguished Names and Relative Distinguished Names.
Directory information trees, object classes and attributes in this report should be considered informative since they are subject to additions and/or modification depending on the specific implementation as illustrated in the presented alternatives in this technical report. Even the assignment of attributes to object classes may be redistributed, for example,because the normalization of object classes across different domains may result in attributes being moved to a superclass. Naming is provisional. Diagrams used and naming convention are not standardized.
|
29.941
|
Guidelines on Port Allocation for New 3GPP Interfaces
|
TR
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.941/29941-i00.zip
|
IETF has indicated to 3GPP that future IANA port number assignment requests for protocol only used inside 3GPP networks will be likely rejected except if there is a strong justification for it. The present document provides guidelines for resolving the problem with allocating port numbers for new 3GPP interfaces, as an alternative to IANA assigned port numbers.
Starting from 3GPP Rel-17, any 3GPP working group can rely on these guidelines when defining new interfaces, which require new default port number allocation.
|
29.949
|
Study on technical aspects on roaming end-to-end scenarios with Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) and other networks
|
TR
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.949/29949-i00.zip
|
The present document describes end-to-end use cases and signalling flows based on the roaming architecture for voice over IMS with local breakout. It summarizes the contents of existing 3GPP technical specifications which are needed for roaming use cases. The scenarios used cover the following use cases:
- registration when roaming;
- routeing from originating visited network to originating home network;
- loopback routeing from originating home network to originating visited network;
- routeing when the originating and terminating user reside in the same home network;
- routeing from the originating home network to the terminating home network;
- routeing from the originating visited network to the terminating home network;
- routeing in terminating home network when user resides in this network;
- routeing from terminating home network to the terminating visited network;
- insertion of service related media in the originating home network;
- routeing through transit networks; and
- access transfer scenarios (SRVCC).
Editor's note: It is ffs if the call forwarding service invocation in a Call Deflection case will be considered.
|
29.994
|
Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults
|
TR
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-i00.zip
|
The present document clarifies recommended measures which may be adopted by 3GPP infrastructure utilising GSM or GERAN as access network to enable inter-working to be obtained between network and various User Equipment (UE) implementations of the 3GPP specification. The objective is to obtain compatibility without changing the consolidated set of specifications. The present document describes the recommended changes to the infrastructure to cater for specific faults within some types of UE.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document.
|
30.531
|
Work Plan and Working Procedures - RAN WG3
|
TR
|
1.58.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.531/30531-015800.zip
|
The present document presents the workplan for TSG RAN WG3. It describes the working procedures of TSG RAN WG3. The document also contains a list of all specifications under responsibility of RAN WG3, and a list of all open work and study items relevant for TSG RAN WG3 for the different releases.
|
31.101
|
UICC-terminal interface; Physical and logical characteristics
|
TS
|
18.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-i10.zip
|
The present document specifies the interface between the UICC and the Terminal for 3GPP telecom network operation.
The present document specifies:
- the requirements for the physical characteristics of the UICC;
- the electrical interface between the UICC and the Terminal;
- the initial communication establishment and the transport protocols;
- the model which serves as a basis for the logical structure of the UICC;
- the communication commands and the procedures;
- the application independent files and protocols.
The administrative procedures and initial card management are not part of the present document.
For the avoidance of doubt, references to clauses of ETSI TS 102 221 [1] include all the clauses of that clause, unless specifically mentioned.
The target specification ETSI TS 102 221 [1] contains material that is outside of the scope of 3GPP requirements and the present document indicates which parts are in the scope and which are not.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP.
|
31.103
|
Characteristics of the IP Multimedia Services Identity Module (ISIM) application
|
TS
|
18.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-i20.zip
|
The present document defines the ISIM application for access to IMS services.
The present document specifies:
- specific command parameters;
- file structures;
- contents of EFs (Elementary Files);
- security functions;
- application protocol to be used on the interface between UICC (ISIM) and Terminal.
This is to ensure interoperability between an ISIM and Terminal independently of the respective manufacturer, card issuer or operator.
The present document does not define any aspects related to the administrative management phase of the ISIM. Any internal technical realisation of either the ISIM or the Terminal is only specified where these are reflected over the interface. The present document does not specify any of the security algorithms that may be used.
|
31.104
|
Characteristics of the Hosting Party Subscription Identity Module (HPSIM) application
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.104/31104-i00.zip
|
The present document applies to a H(e)NB supporting the HPSIM for H(e)NB Hosting Party authentication. The present document defines the HPSIM application, the UICC application residing in the Hosting Party Module for H(e)NB Hosting Party authentication and provisioning.
The present document specifies
- identification of the Hosting Party
- security mechanism, e.g. authentication based on EAP-AKA method
- support of information for the initial provisioning (e.g. O&M system contact)
- initialisation procedure on H(e)NB-UICC interface
- O&M procedure
|
31.105
|
Characteristics of the Slice Subscriber Identity Module application
|
TS
|
18.3.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.105/31105-i30.zip
|
The present document defines the SSIM application for 3GPP telecom network operation related to Network Slice-Specific Authentication and Authorization procedure.
The present document specifies:
- specific command parameters;
- file structures;
- contents of EFs (Elementary Files);
- security functions;
- application protocol to be used on the interface between UICC (SSIM) and ME.
This is to ensure interoperability between a SSIM and an ME independently of the respective manufacturer, card issuer or operator.
The present document does not define any aspects related to the administrative management phase of the SSIM. Any internal technical realisation of either the SSIM or the ME is only specified where these are reflected over the interface. The present document does not specify any of the security algorithms which may be used.
|
31.115
|
Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-i00.zip
|
The present document specifies the structure of the Secured Packets in implementations using Short Message Service Point to Point (SMS-PP), Short Message Service Cell Broadcast (SMS-CB), Unstructured Supplementary Service Data (USSD) and and Hyper Text Transfer Protocol (HTTP) based on ETSI TS 102 225 [9].
The structure of the Secured Packets shall comply with the one defined in ETSI TS 102 225 [9]. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
It is applicable to the exchange of secured packets between an entity in a PLMN and an entity in the (U)SIM.
Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the PLMN and on the (U)SIM. The Sending/Receiving Entity in the PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
31.116
|
Remote APDU Structure for (U)SIM Toolkit applications
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-i00.zip
| |
31.117
|
Universal Subscriber Identity Module Application Toolkit (USAT) application behavioural test specification
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.117/31117-i00.zip
|
The present document describes behavioural tests for the USIM Application Toolkit implemented in Mobile Equipment (ME) or Mobile Stations (MS) supporting a non-removable UICC only within the 3GPP digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [7] and ETSI ETS 300 406 [20].
This document shall provide alternative verification and testing approaches for test cases initially defined in TS 31.124 [2] or ETSI TS 102 384 respectively. To guarantee the highest possible reliability, the verification of existing requirements shall be done using methods defined by ETSI or 3GPP.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. Thus, the present document does not contain tests or references to ETSI TS 102 384 [3] tests for features which are out of scope of 3GPP.
Due to possible limitations in profile handling and updating it is not intended to use the test cases defined within this document with MEs implemented in accordance with Rel-12 or earlier.
|
31.120
|
UICC-terminal interface; Physical, electrical and logical test specification
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-i00.zip
|
The present document specifies the interface test for the Terminal / UICC.
The present document specifies the tests of:
- physical characteristics of the UICC;
- the electrical interface between the UICC and the Terminal;
- the initial communication establishment and the transport protocols;
- the application independent procedures.
|
31.121
|
UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification
|
TS
|
18.3.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-i30.zip
| |
31.122
|
Universal Subscriber Identity Module (USIM) conformance test specification
|
TS
|
18.4.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-i40.zip
|
The present document provides the Conformance Test Specification for a Universal IC Card (UICC) defined in TS 31.101 [2] with Universal Subscriber Identity Module (USIM) defined in TS 31.102 [3].
|
31.124
|
Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification
|
TS
|
18.3.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-i30.zip
| |
31.127
|
UICC-terminal interaction; non-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specification
|
TS
|
18.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.127/31127-i20.zip
|
The present document provides application behavioural tests for a UE to interoperability with dedicated 3GPP network operations. Where there shall be a description for each compliant implementation including the:
- the test case specific setting of the USIM;
- the applicability of each test case;
- the test configurations;
- the conformance requirement(s) and reference(s) to the related core specifications;
- the test purposes; and
- a brief description of the test procedure and the specific acceptance criteria.
The present document is applicable for MEs supporting a non-removable UICC only. MEs that allow access to the physical card interface as defined in ETSI TS 102 221 [8] or ETSI TS 102 671 [29] shall be tested in accordance to TS 31.121 [2].
This document shall provide alternative verification and testing approaches for test cases initially defined in TS 31.121 [2]. If no ETSI or 3GPP defined alternative method to verify an existing requirement is available or if the result generated by the proposed verification method is less reliable, this has to be clearly stated in the test description.
Due to possible limitations in profile handling and updating it is not intended to use the test case defined within this document with 2G only MEs or MEs implemented in accordance to Rel-12 or earlier.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. The present document does not contain tests for features that are out of scope of 3GPP.
In the present document, unless explicitly stated otherwise, for Rel-13 onwards the term E-UTRAN implicitly refers to E-UTRAN in WB-S1 mode. E-UTRAN in NB-S1 mode is always explicitly referred to as NB-IoT.
|
31.130
|
(U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card
|
TS
|
18.4.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-i40.zip
|
The present document defines the (U)SIM Application Programming Interface extending the "UICC API for Java Card™" [2].
This API allows to develop a (U)SAT application running together with a (U)SIM application and using 3GPP network features.
The present document includes information applicable to 3GPP network operators, service providers, server – (U)SIM – database manufacturers.
|
31.131
|
C-language binding to (U)SIM API
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-i00.zip
|
A Subscriber Identity Module Application Programming Interface (SIM API) has been defined in TS 42.019 [4] as a technology-independent API by which toolkit applications and (U)SIMs co-operate. That specification is independent of the programming language technology used to create the application, the platform used to host the application and the runtime environment used to execute the application.
The present document includes information applicable to (U)SIM toolkit application developers creating applications using the C programming language ISO/IEC 9899 [7]. The present document describes an interface between toolkit applications written in the C programming language and the (U)SIM in order to realize the co-operation set forth in TS 42.019 [4]. In particular, the API described herein provides the service of assembling proactive commands and disassembling the responses to these commands for the application programmer.
Software tools, integrated software development environments and software management systems that may be used to create application programs are explicitly out of scope of the present document.
|
31.133
|
IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-i00.zip
|
The present document defines the ISIM Application Programming Interface extending the "UICC API for Java Card™" [2].
This API allows to develop an application running together with a ISIM application.
The present document includes information applicable to network operators, service providers, server -,–ISIM – and database anufactures.
|
31.213
|
Test specification for (U)SIM; Application Programming Interface (API) for Java Card™
|
TS
|
18.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-i10.zip
|
The present document covers the minimum characteristics considered necessary in order to provide compliance to TS 31.130 [2].
The present document describes the technical characteristics and methods of test for testing the (U)SIM API for Java CardTM (TS 31.130 [2]) implemented in the (U)SIM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test suite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used.
|
31.220
|
Characteristics of the Contact Manager for 3GPP UICC applications
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-i00.zip
|
The present document defines the Contact Manager for 3GPP UICC applications based on OMA DS [7].
The present document specifies the external interface between the Contact Manager Server in the UICC and the Contact Manager External Client in the ME;
Any internal technical realization of either the Contact Manager Server or clients is only specified where these are reflected over the interfaces.
|
31.221
|
Contact Manager Application Programming Interface (API); Contact Manager API for Java Card
|
TS
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-i00.zip
|
The present document defines the internal interface characteristics of the Contact Manager for 3GPP UICC applications [2].
The internal interface between the Contact Manager Server application on the UICC and the Contact Manager Client application on the UICC enables Java Card™ platform based applets, defined in [3], [4] and [5], to invoke and register to the Contact Manager Server services. In particular, the Contact Manager Java Card™ based API provides methods to:
- Read/Update/Create/Delete contact(s) in the Contact Manager Server;
- Manage group of contacts in the Contact Manager Server;
- Search for a contact in the Contact Manager Server storage;
- manage the contacts structure;
- Register/Un-register the application to pre-defined events (e.g. application to be notified when contacts are modified in the Contact Manager Server).
This API allows to develop an application running together with a Contact Manager [2].
|
31.822
|
Study on GBA_U Based APIs
|
TR
|
18.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.822/31822-i10.zip
|
The present document studies the GBA_U based APIs.
|
31.826
|
Study on new UICC application for NSSA
|
TR
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.826/31826-i00.zip
|
The aim of this Technical Report is to study the aspects for any potential enhancements on the UICC to be developed by CT6 based on the outcome of 3GPP TS 33.501. This work does not include selecting or standardizing any specific EAP method or associated EAP credential types for NSSAA.
For each of the objectives in the scope of the CT6 study, the UICC aspects that are to be covered in this study are as follows:
- Enhancements to support network slice-specific authentication and authorization using the UICC
- Study potential solutions for slice-specific authentication using new specific UICC application
- Study information the UICC application for NSSAA needs to contain
- Study information needed by the ME to select the correct UICC application used for NSSAA, in the case where multiple such UICC applications are available on the UICC. This information will not include UICC application selection based on a specific EAP method or type of EAP credentials.
- Study the interface that the new UICC application should feature in order to support NSSAA
Note: The study item in CT6 will not cover any security-related aspects within SA3's remit.
|
31.900
|
SIM/USIM internal and external interworking aspects
|
TR
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-i00.zip
|
The present document describes
- the different cases of interworking between a 2G or 3G ICC and a 2G or 3G ME.
- the different cases of interworking between any given ME/ICC combination and the rest of the network
- the possibilities of interworking between a SIM and a USIM together on a single UICC
- the possibilities of interworking between several USIMs on a single UICC
|
31.970
|
UICC power optimisation for Machine-Type Communication (MTC)
|
TR
|
18.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.970/31970-i00.zip
|
The present document has the objective to describe the power consumption caused by UICC when it is idle and identify the potential solutions to allow the reduction or removal of the UICC power supply in order to save power when the UICC is not required for long periods of time.
This document identifies conditions which might need to be applied to the UICC platform.
|
32.101
|
Telecommunication management; Principles and high level requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-i00.zip
|
The present document establishes and defines the management principles and high-level requirements for the management of PLMNs.
In particular, the present document identifies the requirements for:
- the upper level of a management system;
- the reference model, showing the elements the management system interacts with;
- the network operator processes needed to run, operate and maintain a network;
- the functional architecture of the management system;
- the principles to be applied to management interfaces.
The requirements identified in the present document are directed to the further development of management specifications as well as the development of management products. The present document can be seen as guidance for the development of all other Technical Specification addressing the management of PLMNs.
The present document does not provide physical architectures of the management system. These aspects are defined and discussed in more detail in TS 32.102 [101].
Verbal forms used to indicate requirements in the present document (e.g. "shall", "should", "may") are used in compliance with 3GPP specification Drafting Rules TR 21.801 [104].
|
32.102
|
Telecommunication management; Architecture
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-i00.zip
|
The present document identifies and standardises the most important and strategic contexts in the physical architecture for the management of PLMNs. It serves as a framework to help define a telecom management physical architecture for a planned PLMN and to adopt standards and provide products that are easy to integrate.
The requirements identified in the present document are applicable to all further development of 3GPP Telecom Management specifications as well as the development of PLMN Management products. The present document can be seen as guidance for the development of all other Technical Specification addressing the management of PLMNs, except TS 32.101 [2].
|
32.103
|
Telecommunication management; Integration Reference Point (IRP) overview and usage guide
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.103/32103-i00.zip
|
The present document gives an overview about 3GPP's management capabilities and related functionality.
This document is intended to be a guide into the world of 3GPP management specifications, enabling also non-subject matter experts to gain an understanding about 3GPP's management solutions.
|
32.107
|
Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.107/32107-i00.zip
|
On-going industry convergence and pressure to reduce cost is placing an ever-increasing emphasis on the need to rationalize and align various network management aspects across boundaries of standards/specifications producing organizations. The cost, resulting from integration and management challenges, of the lack of a coherent treatment of the whole network has becoming increasingly apparent to the point where operators of networks are demanding action.
This document provides key concepts and principles for the Federated Network Information Model covering all key aspects of a solution to the on-going industry convergence challenge. The proposal focuses on Information Model federation and is constructed to best deal with the various contradictory pressures of the current environment providing a pragmatic and realizable approach. The structure proposed will be called the Federated Network Information Model (FNIM).
The proposal set out in this document:
Explains:
- How, from a technical perspective, a number of standards and specifications generated by different organizations can function together to bring greater coherence to the management of converged networks and hence reduce operations costs.
- Specifically how TM Forum and 3GPP can work with each other and with other industry groups in a Standards Federation to develop a Federated Network Information Model drawing on insights from the broad community (including the TM Forum SID [7], TM Forum MTNM/MTOSI [8], 3GPP SA5 IRPs [14], DMTF CIM [15]).
- How the Federated Network Information Model can be used from a technical perspective (with the focus here being the Network Model).
Recognizes:
- The network is “always on”, therefore changes in management solutions should not impact networks in operation.
- There will always be on-going change.
- That this is only a start on a very long journey.
Allows and enables:
- Decoupling of concerns across the industry whilst growing industry coherence.
- Differing delivery pace across the industry whilst aiming for industry convergence.
- Variety from innovation whilst removing unnecessary variety in management infrastructure.
- Temporary divergences and overlaps during the convergence process.
Ensures:
- Change is made only as a result of understanding of specific market needs.
- Progress by providing coherent solutions to satisfy the needs of all participating industry partners in order not to be blocked by the slowest laggard.
Highlights:
- The challenges of dealing with differing methodologies/tooling used across the standards arena and points out that methodology/tooling differences if ignored will significantly slow progress towards the target.
- The need for development of a new governance regime and points to some of the attributes of such a regime.
- An approach of gradual restructuring and a controlled converging coherence starting small and growing step by value-justified step.
- The challenge of presenting the models so all can have an identical understanding.
- The challenge of interpreting models from different origins, with their different terminology and viewpoints, to arrive at a shared understanding through a federated model. This leads to recognition of the need for a deeper uniform semantic analysis of the area covered by the umbrella information model (UIM) and the navigation points among concrete models which may further lead to the need for the development of information architectures and patterns.
This document focuses on the Information Model aspect of the problem as it is clear that the lack of an agreed-upon, coherent information model across organizational boundaries to support the FMC aspects of the industry that defines the things to be managed and the way they should be expressed is one of the first aspects that need to be tackled.
Editor’s note: Prior to embarking on a further summary of the proposal and its benefits, it is important to emphasize that the definition of the term “model” has to be carefully considered. A model is comprised of parts that themselves can be seen as models. As a consequence whether this activity results in a single model or a set of models depends upon perspective. The critical consideration is whether the parts of the solution can be interrelated and from the perspective of the problem highlighted above whether the parts can be interrelated across what were previously un-navigable barriers. The solution offers this navigability. Conversely it is critical that the solution offers appropriate decoupling of concerns and of governance. Whether this is considered one model or many is not relevant as long as the solution offers the properties, such as those noted above, that are critical for industry success.
This document proposes a Federated approach to model development and emphasizes the need for the development of an Umbrella Information Model (UIM) and its relationships with the other domain specific models. The document also deals with direct relationships between domain/technology specific concrete models.
It is proposed that:
- The work will be published and expressed in UML and will also be published in formats appropriate for each of the participating bodies to absorb (this may require nothing more than the UML format in some cases). The output form required by a particular body will be generated by resources contributed by that body.
- As necessary the model will be embellished using stereotype to express all aspects/properties of the model.
The proposal recognizes that the TM Forum Information Framework (SID) [7] and the TM Forum Integration Framework (MTNM/MTOSI) [8] work provide an enterprise-wide structure and model that can be used to seed the converged model. The proposal recognizes that the 3GPP SA5 group work [14] provides models relating to mobile networks (including RANs, CNs and IMS) that can be used to seed the converged model.
The proposal:
- Ensures on-going reduction in cost of integration and improvement of degree of integration for the purpose of End-to-End management;
- Enables models from many organizations to be used together for the purpose of End-to-End management (recognizing that there are a number of critical governance issues to be overcome to enable this);
- Provides structure for the alignment on a deeper understanding of the semantics and for the development and maintenance of an information architecture and associated patterns;
- Provides both an initial pragmatic solution form and a longer term target;
- Recognizes that the model will evolve in stages, but will never be “completed” and hence this is an on-going activity;
- Recognizes the importance of providing solutions that are backward compatible to existing standards. See [13, 17]
This content of this document has been jointly developed by 3GPP and TM Forum as part of the Joint Working Group on Resource Model Alignment [18].
|
32.111-1
|
Telecommunication management; Fault Management; Part 1: 3G fault management requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-i00.zip
|
The present document specifies the overall requirements for 3GPP Fault Management (FM) as it applies to the Network Elements (NE), Element Manger (EM) and Network Manager (NM).
Clause 4 defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3GPP systems. These functions are described on a non-formal level since the formal standardization of these functions across the different vendors' equipment is not required. The functional areas specified in the present document cover:
- fault surveillance and detection in the NEs;
- notification of alarms (including alarm cease) and operational state changes;
- retrieval of current alarms from the NEs;
- fault isolation and defence mechanisms in the NEs;
- alarm filtering;
- management of alarm severity levels;
- alarm and operational state data presentation and analysis at the Operations System (OS);
- retention of alarm and operational state data in the NEs and the OS; and
- the management of tests.
Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of the present document. These are described in [19].
Clause 5 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3GPP systems , as seen from the Network Manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface.
|
32.111-2
|
Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-i00.zip
|
The present document defines the Alarm Integration Reference Point (IRP) Information Service (IS), which addresses the alarm surveillance aspects of Fault Management (FM), applied to the Itf-N.
The purpose of the AlarmIRP is to define an interface through which a "system" (typically a Network Element Manager or a Network Element) can communicate alarm information for its managed objects to one or several Manager Systems (typically Network Management Systems).
The Alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters.
|
32.111-6
|
Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-6/32111-6-i00.zip
|
The present document contains the Solution Sets for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [4]).
These Solution Set specifications are related to 3GPP TS 32.111-2 V14. 0.X [4].
|
32.121
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-i00.zip
|
The purpose of this set of specifications is to provide a mechanism enabling the IRP Manager to improve the information content of alarms, thereby contributing to reduce the time-to-repair. For this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applying such advanced alarm filtering.
The present document contains the Requirements of Advanced Alarm Management (AAM) on Itf-N IRP.
It defines, for the purpose of AAM on Itf-N, the basic requirements to be fulfilled on Itf-N.
|
32.122
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.122/32122-i00.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 Information Service of AAM. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information.
|
32.126
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.126/32126-i00.zip
|
The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [6]).
This Solution Set specification is related to TS 32.122 v14.0.X [6].
|
32.140
|
Telecommunication management; Subscription Management (SuM) requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-i00.zip
|
The present document defines the service requirements and high-level architecture for SuM, including Converged Management of fixed and mobile networks.
SuM is expected evolve in stages over several releases of 3GPP specifications.
The present document provides additional supporting material, which whilst not within the scope of this release, provides an insight towards the future evolution. This is in order that initial work may be done with an appreciation of the wider context expected in future releases of 3GPP specifications.
SuM for 3GPP is primarily concerned with the ability to define subscription profiles and associate the profile with subscribers, users and services that are authorized by agreements. The subscription profile may be used in the process of configuring various network resources (access and core) to make the service a reality for the user.
The management capabilities extend to the creation, modification, synchronization, and re application of subscription profiles.
The present document is oriented towards a standardized interface into the Home Subscriber Server (HSS) in order that services can be provisioned and maintained.
The present document includes information applicable to Network Operators, content providers, and terminal and network manufacturers.
The present document contains the core requirements for SuM, which are sufficient to provide management services.
The method by which applications subscribe to OSA is not within the scope of the present document.
|
32.141
|
Telecommunication management; Subscription Management (SuM) architecture
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-i00.zip
|
The present document defines the architecture for Subscription Management (SuM) , including Converged Management of fixed and mobile networks.
|
32.150
|
Telecommunication management; Integration Reference Point (IRP) Concept and definitions
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-i10.zip
|
The present document provides the overall concept for all Integration Reference Point (IRP) specifications.
Relevant IRP overview and high-level definitions are already provided in 3GPP TS 32.101 [1] and TS 32.102 [2].
IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference Point in subclause 3.1).
|
32.153
|
Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.153/32153-i00.zip
|
The present document contains the templates to be used for the production of Integration Reference Point (IRP) technology-specific specifications.
|
32.154
|
Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.154/32154-i00.zip
|
The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
Editor's Note: The “forward compatability” part is FFS.
|
32.155
|
Telecommunication management; Requirements template
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.155/32155-i00.zip
|
The present document contains the template to be used for the production of all IRP based requirements TSs for the 3GPP Telecommunication management.
This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6].
|
32.157
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.157/32157-i00.zip
|
The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications for Converged Management.
|
32.158
|
Management and orchestration;Design rules for REpresentational State Transfer (REST) Solution Sets (SS)
|
TS
|
18.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.158/32158-i20.zip
|
The present document defines design rules for REpresentational State Transfer (REST) Solution Sets (SS). These rules are applied when specifying REST Solution Sets.
|
32.161
|
Management and orchestration; JSON expressions (Jex)
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.161/32161-i10.zip
|
The present TS introduces JSON expressions (Jex).
|
32.181
|
Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.181/32181-i00.zip
|
The present document specifies the framework for overall management of the User Data Convergence.
In order to accommodate multiple applications and services, existing and new ones, the framework for model handling and management of the UDC as identified by TS 22.101 includes the following items:
- UDC information models:
- UDC information model infrastructure containing the common baseline information model (CBIM), application information models (AIM), and the specialised information model (SIM). The CBIM is standardised in TS 32.cde [4].
- UDC information model handling:
- provide a template and guidelines explaining the design of application information models to be used together with the common baseline information model to create the specialized information model
- describe the process to combine the common baseline information model with application information models in order to produce an operator-specific specialised information model
- Application management data:
- access control data for an application to UDC: identification and authentication
- assignment to an application data model, including linkage to the consolidated data model
- subscription rights for specific events on specific data of specific users
- Consolidated data model management
- lifecycle management of the consolidated data model in the UDR and in the provisioning entity.
- activation/deactivation of application adaptation
|
32.182
|
Telecommunication management; User Data Convergence (UDC); Common baseline information model (CBIM)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.182/32182-i00.zip
|
The present document specifies a Common Baseline Information Model for UDC [2]. This information model denotes an abstract, formal representation of entity types that are common to many applications using the UDR. CBIM describes the basic IOCs of UDC, their properties and their relationships. Detailed requirements for the specification of this Common Baseline Information Model are given in 3GPP TR 22.985 [2] and 3GPP TS 22.101 [3].
From the Common Baseline Information Model specialized information models and data models can be derived. All these derived models are out of the scope of this specification.
|
32.250
|
Telecommunication management; Charging management; Circuit Switched (CS) domain charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 TS 32.240 [1].
The present document specifies the Offline Charging description for the 3GPP Circuit Switched domain, based on the functional descriptions of the 3GPP bearer-, tele- and supplementary services in TS 22.002 [200], TS 22.003 [201] and TS 22.004 [202], respectively. This charging description includes the offline charging architecture and scenarios specific to the CS domain, as well as the mapping of the common charging architecture specified in TS 32.240 [1] onto the CS domain. It further specifies the structure and content of the CDRs for offline 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].
- 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].
Note that online charging for the CS domain is solely based on CAMEL (TS 23.078 [207] and TS 29.078 [213]) and therefore outside the scope of the 32 series of charging specifications.
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.253
|
Telecommunication management; Charging management; Control Plane (CP) data transfer domain charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.253/32253-i00.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS/LTE networks. The GSM/UMTS/LTE core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for Control Plane (CP) data transfer domain, based on the functional stage 2 description in TS 23.682 [243] for Non-IP Data Delivery (NIDD) using SCEF procedures. This charging description includes the offline and online charging architecture and scenarios specific to Control Plane (CP) data transfer domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the Control Plane (CP) data transfer domain. It further specifies the structure and content of the CDRs for offline 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 Control Plane (CP) data transfer domain offline and online charging is specified in TS 32.299 [50].
Control Plane (CP) data transfer is also provided by Short Message Service (SMS), for which charging functionalities are not specified in the present document. SMS charging functionality is defined for Circuit Switched domain in TS 32.250 [10], for Packet Switched domain in TS 32.251 [11] and for SMS Nodes in TS 32.274 [34].
|
32.257
|
Telecommunication management; Charging management; Edge computing domain charging
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.257/32257-i10.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in 3GPP TS 32.240 [2], which provides an umbrella for other charging management TSs 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 these TSs is defined in 3GPP TS 32.240 [2].
The present document specifies the converged offline and online charging description for the Edge Computing domain based on the functional stage 2 description in 3GPP TS 23.501 [8] and 3GPP TS 23.558 [9].
Edge computing in 5G environment involves the services or capabilities provided by multiple service providers and entities in the form of following business roles:
- ASP providing edge application service to the subscribers;
- ECSP providing edge enabling infrastructure and edge enabling services to ASP;
- MNO providing 5GS capabilities supporting edge computing.
The present document specifies following charging aspects for Edge Computing:
- Subscriber charging:
- MNO charges the subscribers for usage of 5GS capabilities supporting edge computing.
- Service-provider charging:
- MNO charges the industry consumer (e.g. ECSP, ASP) for 5GS capabilities provided to support edge computing in total instead of for each individual subscriber;
- ECSP charges the ASP for the edge enabling infrastructure and services.
NOTE: In the Edge Computing deployments, there could be scenarios where one or more of the business roles are supported by a single enterprise, i.e. one enterprise may play a single business role or multiple business roles, for instance the enterprise may only play the MNO role, or play both MNO and ESCP roles. There could be various business models between the service providers and the served consumer(s) for edge computing in 5G environment in manifold business modes such as B2C, B2B and B2B2X, for example (but not limited to). The present document does not impose restrictions to any possible business model or deployment scenario for Edge Computing.
|
32.270
|
Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging
|
TS
|
18.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-i30.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in document 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 TS 32.240 [1].
The present document specifies the offline and online charging description for MMS charging, based on the functional stage 2 descriptions of the MMS in TS 23.140 [201]. This charging description includes the offline and online charging architecture and scenarios specific to the MMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto MMS. 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 MMS online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 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
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 TS 32.240 [1].
The present document specifies the offline and online charging description for the "Push-to-Talk over Cellular" (PoC) service, based on the functional description of the PoC service in TR 23.979 "3GPP enablers for OMA PoC Services" [200], in OMA-AD-POC "Push to talk over Cellular (PoC) - Architecture" [203], in OMA-CP-POC "OMA PoC Control Plane" [204] and in OMA-UP-POC: "OMA POC User Plane"[205], respectively. This charging description includes the offline and online charging architecture and scenarios specific to PoC, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PoC service. 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 PoC offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains 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.273
|
Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the Multimedia Broadcast and Multicast Service (MBMS), based on the functional stage 2 description in TS 23.246 [200].
This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto MBMS.
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 MBMS offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains 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.275
|
Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.275/32275-i00.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 TSs 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 TS 32.240 [1].
The present document specifies the offline, online and converged charging for MultiMedia Telephony (MMTel) service and supplementary services, based on the functional description of MMTel in TS 22.173 [200]. Charging for the following supplementary services is specified:
- Communications Diversion (CDIV);
- Communication Hold (HOLD);
- CONFerence (CONF);
- Message Waiting Indication (MWI);
- Originating Identity Presentation (OIP) / Originating Identity Restriction (OIR);
- Terminating Identity Presentation (TIP) / Terminating Identity Restriction (TIR);
- Call Barring (CB);
- Explicit Call Transfer (ECT);
- Communication Wait (CW);
- Completion of Communications to Busy Subscriber (CCBS);
- Completion of Communications by No Reply (CCNR);
- Malicious Communication Identification (MCID);
- Customized Alerting Tone (CAT);
- Closed User Group (CUG);
- Personal Network Management (PNM);
- Customized Ringing Signal (CRS);
- Reverse Charging;
- Advice of Charge (AoC).
Charging of these supplementary services is performed at the respective MMTel AS. The MMTel charging aspects are an extension of the basic IMS charging capabilities as specified in the TS 32.260 [20].
This charging description includes the offline, online and converged charging architecture and scenarios specific to the MMTel, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the MMTel. It further specifies the structure and content of the CDRs, and the charging events.
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 common IMS charging principles are specified in the TS 32.260 [20].
- 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 MMTel 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 [57].
- The charging service of 5G system is specified in TS 32.291 [58].
|
32.276
|
Telecommunication management; Charging management; Voice Call Service (VCS) charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.276/32276-i00.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 TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
- the content of the Charging Data Records (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 these TSs is defined in TS 32.240 [1].
The present document specifies the online charging description for Voice Call Service (VCS) charging from a Proxy Function, based on the functional description of the Voice Call Service charging in the EU Roaming Regulations III specifications [298, 299].
The concept of voice call is interpreted as any CS call, whatever the teleservice used (speech, 3.1 kHz audio, Fax, or CS data) except CS video telephony calls (BS 37, 64 kbit/s unrestricted digital info mode).
Voice over LTE is not included in this definition. This charging specification includes the online charging architecture and scenarios specific to VCS charging from a Proxy Function, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto VCS. It further specifies 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 3GPP Diameter application that is used for VCS online charging is specified in TS 32.299 [50].
Offline charging for the VCS is solely based on TS 32.250 [10] and is outside the scope of the present document.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100] "Vocabulary for 3GPP Specifications".
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.
|
32.278
|
Telecommunication management;Charging management;Monitoring event charging
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.278/32278-i00.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS/LTE networks. The GSM/UMTS/LTE core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the Offline Charging description for Monitoring Events, based on the functional stage 2 description in TS 23.682 [243]. This charging description includes the offline charging architecture and scenarios specific to Monitoring Events, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the 3GPP Architecture for Service Capability Exposure. It further specifies the structure and content of the CDRs for offline 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 Monitoring Event offline charging is specified in TS 32.299 [50].
The online charging functionality for Monitoring Events is outside the scope of 3GPP standardisation.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS/LTE 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.
|
32.279
|
Charging management; 5G Multicast-broadcast Services charging
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.279/32279-i10.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [2], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [2].
The present document specifies the converged charging description for the 5G MBS Session based on the functional stage 2 description in TS 23.247 [9], TS 23.501 [10], TS 23.502 [11] and TS 23.503 [12].
This charging description includes the converged charging architecture and scenarios specific to the 5G MBS Session, with focus on the following charging scenarios:
- MBS session charging for multicast communication.
- MBS session charging for broadcast communication.
It further specifies the structure and content of the CDRs and the charging events for converged charging.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [1]. Those that are common across charging management in 3GPP networks/domains, services or subsystems are provided in the umbrella TS 32.240 [2] 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.
|
32.280
|
Telecommunication management; Charging management; Advice of Charge (AoC) service
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.280/32280-i00.zip
|
The present document specifies the Advice of Charge (AoC) framework for relevant events, sessions, and services. The 3GPP umbrella charging architecture and principles are defined in TS 32.240 [1].
The AoC framework detailed herein provides for both offline and online charging models. It specifies the following:
- The AoC architecture.
- The common principles that govern AoC.
- The AoC function that enables the IMS AoC framework.
- Exemplary message flows.
- AoC interface data description.
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP network, services or subsystems are provided in the umbrella document TS 32.240 [1] and may be 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.
Requirements that govern the AoC work are specified in TS 22.115 [101].
|
32.281
|
Telecommunication management; Charging management; Announcement service
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.281/32281-i00.zip
|
During any phase of a voice or video call, the Online Charging System (OCS) or Converged Charging System (CCS)may need to deliver billing/charging in-session notifications to the end user via announcements as part of the rating, balance management and billing process. For example, the CCS/OCS may need to inform the user about usage states, threshold crossings, offer statuses, reason for call rejection, alerts about low balances, etc.
Such notifications can be delivered pre-, mid- or post-call.
The Announcement service in the present document provides announcement capabilities for use in a Diameter based online or converged charging session. The CCS/OCS is able to specify that a given announcement be played to a call party in order to deliver charging/billing related notifications.
|
32.282
|
Charging management; Time-Sensitive Networking (TSN) charging
|
TS
|
18.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.282/32282-i20.zip
|
The present document is part of a series of documents 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].
The present document specifies the converged charging description for the time sensitive networking domain based on the functional stage 2 description in TS 23.501 [11], TS 23.502 [12] and TS 23.503 [13].
This charging description includes the converged charging architecture, principles, requirements and scenarios specific to the time sensitive networking, with focus on the following charging scenarios: .
- the TSN 5GS bridge configuration and management charging.
- the enabler for time sensitive communication and time synchronization charging.
- the time sensitive communication traffic charging.
It further specifies the structure and content of the CDRs and the charging events for converged charging.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [8]. Those that are common across charging management in 3GPP networks/domains, services or subsystems are provided in the umbrella 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.
|
32.293
|
Telecommunication management; Charging management; Proxy function
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.293/32293-i00.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 TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
- the content of the Charging Data Records (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 these TSs is defined in TS 32.240 [1].
The present document specifies the Proxy Function in Domestic Service Provider (DSP).
The present document contains the architecture and functions of the Proxy Function logical components and thereby derives the functionality of the Proxy Function interfaces. This charging description only defines the interworking between CAMEL and Diameter. The Ro interface between the Proxy Function and Online Charging System (OCS) is out of scope of the present document.
The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- Voice Call Service (VCS) charging is specified in TS 32.276[36].
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100] "Vocabulary for 3GPP Specifications". 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.
|
32.295
|
Telecommunication management; Charging management; Charging Data Record (CDR) transfer
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP 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 TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the transaction based mechanism for the near real time transfer of CDRs
within the network.
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];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the post-processing system or a mediation device) is specified in TS 32.297 [52];
The 3GPP Diameter application that is used for offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP 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.296
|
Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The GSM/UMTS 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 (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 of the charging management TSs is defined in TS 32.240 [1].
The present document covers all internal aspects of the Online Charging System (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
The interfaces connecting to the OCS (e.g. Ro, CAP) are out of the scope of the present document.
NOTE: In the current release the present document is limited to the interface between the charging function and the Rating Function(RF), namely Re.
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 3GPP domains, services, or subsystems are provided in the umbrella document TS 32.240 [1]. 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.297
|
Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-i10.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 TSs that specify:
- the content of the CDRs per domain / subsystem / service (offline and converged charging);
- the content of real-time charging messages per domain / subsystem / service (online and converged charging);
- the functionality of online, offline and converged 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 these TSs is defined in TS 32.240 [1].
The present document specifies file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the post-processing system or a mediation device).
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 3GPP Diameter application that is used for 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 [57].
- The charging service of 5G system is specified in TS 32.291 [58].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP 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.299
|
Telecommunication management; Charging management; Diameter charging applications
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-i00.zip
|
The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS 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 (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 TS 32.240 [1].
The present document specifies in detail the Diameter based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows..
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.300
|
Telecommunication management; Configuration Management (CM); Name convention for Managed Objects
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-i10.zip
|
The present document is valid for TSs using IRPs and SBMA.
A more detailed background and introduction of the IRP concept is given in 3GPP TS 32.150 [16] and more detailed background for SBMA in 3GPP TS 28.533 [21].
To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the 3GPP context.
To facilitate integration of network management information obtained via multiple management interfaces based on different Solution Set technologies, identical network resource name semantics shall be conveyed in all management interfaces. The present document specifies one such name convention.
The present document also specifies an IOC/MOC name recommendation (see annex E) in order to avoid potential problems with valid characters in some programming languages.
In this document, the name convention and name recommendation (see annex E) are specified for MO instances whose MO class stereotype is IOC. These specifications are also for MO instances whose MO class stereotype is Support IOC (SupportIOC).
|
32.301
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-i00.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Requirements" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
|
32.302
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-i00.zip
|
The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Information Service" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).
Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP: Information Service [1].
How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
This IRP IS is aligned with ITU-T M.3702 [13] in terms of the definitions of operations for Notification management.
|
32.306
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.306/32306-i00.zip
|
The present document contains the Solution Sets for the IRP whose semantics is specified in Notification IRP: Information Service (TS 32.302 [7]).
These Solution Set specifications are related to 3GPP TS 32.302 V14.0.X [7].
|
32.311
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-i00.zip
|
The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Requirements" part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service.
With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP.
|
32.312
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-i00.zip
|
The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controllable by management system's client (i.e. IRPManager) via the Itf-N.
It also specifies the semantics of and the interactions used to carry this information.
With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP.
|
32.316
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.316/32316-i00.zip
|
The present document provides the Solution Set definitions 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 Definition specification is related to 3GPP TS 32.312 V14.0.X.
|
32.321
|
Telecommunication management; Test management Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-i00.zip
|
The present document describes, in addition to the requirements defined in [1] and [2], the requirements for the Test Management IRP.
|
32.322
|
Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-i00.zip
|
The present document defines the IS part of the Test Management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
|
32.326
|
Telecommunication management; Test management Integration Reference Point (IRP): Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.326/32326-i00.zip
|
The present document contains the Solution Sets for the IRP whose semantics is specified in Test management IRP IS (3GPP TS 32.322 [5]).
This Solution Set specification is related to 3GPP TS 32.322 V14.0.X [5].
|
32.331
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.331/32331-i00.zip
|
The present document specifies overall requirements for Notification Log Management over Itf-N.
Clause 4 provides the Notification Log Management concept for the manipulation of Notification Logs and the retrieval of notifications selected for logging.
Clause 5 of the present document defines the functional requirements for the Notification Log IRP, for the purpose of Notification Log Management, as seen from a Network Manager (NM) though Itf-N. The Itf-N is fully standardized so as to connect systems of any vendor to an NM via this interface.
|
32.332
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.332/32332-i00.zip
|
The present document specifies the Information Service for the Notification Log Integration Reference Point (NLIRP) as it applies to Itf-N.
This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
|
32.336
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.336/32336-i00.zip
|
The present document specifies the Solution Sets for the IRP whose semantics is specified in Notification Log (NL) IRP IS (3GPP TS 32.332 [5]).
This Solution Set specification is related to 3GPP TS 32.332 V14.0.X.
|
32.341
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.341/32341-i00.zip
|
The present document specifies the overall requirements for the File Transfer Integration Reference Point (FT IRP) as it applies to the Itf-N.
|
32.342
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.342/32342-i00.zip
|
The present document specifies the Information Service for the File Transfer Integration Reference Point (FileTransferIRP) as it applies to the Itf-N.
The present document defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
|
32.346
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.346/32346-i00.zip
|
The present document contains the Solution Sets for the IRP whose semantics are specified in File Transfer IRP: Information Service (3GPP TS 32.342 [15]).
This Solution Set specification is related to 3GPP TS 32.342 V14.0.X [15].
|
32.351
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.351/32351-i00.zip
|
The present document describes the requirements of the Communication Surveillance IRP (CSIRP).
|
32.352
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.352/32352-i00.zip
|
The present document defines the Information Service (IS) part of the Communication Surveillance IRP (CSIRP).
It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
The information is specified by means of Information Object Classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
|
32.356
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.356/32356-i00.zip
|
The present document specifies the Solution Set definitions for the IRP whose semantics is specified in TS 32.352 [6] Communication Surveillance IRP: Information Service..
This Solution Set definitions specification is related to 3GPP TS 32.352 V14.0.X [6].
|
32.361
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.361/32361-i00.zip
|
The present document describes the requirements of the EPIRP.
|
32.362
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.362/32362-i00.zip
|
The present document defines the Information Service (IS) part of the Entry Point IRP (EPIRP).
It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
The information is specified by means of Information Object Classes (IOCs) and SupportIOCs, and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
|
32.366
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.366/32366-i00.zip
|
The present document specifies the Solution Set definitions for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
This Solution Set definitions specification is related to 3GPP TS 32.362 V14.0.X [6].
|
32.371
|
Telecommunication management; Security Management concept and requirements
|
TS
|
18.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.371/32371-i10.zip
|
The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2], the requirements for Security Management IRP.
The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf‑N.
Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP‑defined Interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
Appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined Interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
The business case for secured Itf-N is complex as it does not relate to the functions of the Interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing Security Management, all of which differs depending on specific deployment scenarios.
The present document describes the security functions for a 3G network in terms of Security Domains (subclause 4.1). Clause 5 defines the Itf-N Security Management scope in terms of its context (subclause 5.1) and the possible threats that can occur there are defined in clause 6. Clause 7 specifies the Itf‑N security Requirements.
|
32.372
|
Telecommunication management; Security services for Integration Reference Point (IRP); Information Service (IS)
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.372/32372-i00.zip
|
The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf‑N.
The present document specifies the Security Service for IRP Information Service.
This Security Service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
This Information Service specification is related to 3GPP TS 32.371 [6].
|
32.376
|
Telecommunication management; Security services for Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
18.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.376/32376-i00.zip
|
The present document specifies the Solution Set for the IRP whose semantics is specified in 3GPP TS 32.372 [5] Security Service for IRP Information Service.
This Solution Set specification is related to 3GPP TS 32.372 V14.0.X [5].
Note that within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats, and to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.