id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
29.379 | Mission Critical Push To Talk (MCPTT) call control interworking with Land Mobile Radio (LMR) systems; Stage-3 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.379/29379-j00.zip | The present document specifies the call control protocols needed to support a Mission Critical Push To Talk (MCPTT) system interworking with a Land Mobile Radio (LMR) system.
The IWF supports the basic group and other features as specified in 3GPP TS 23.283 [28]. The present document describes functionality modelled on 3GPP TS 24.379 [29]. |
29.392 | Application layer support for MMTel; MMTel Enabler Server Services; stage 3 | TS | 0.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.392/29392-010.zip | The present document specifies the stage 3 protocol and data model for enabling the support of MMTel enabler Services for vertical applications and Controlling Application Server. It provides stage 3 protocol definitions and message flows, and specifies the API of MMTel-2/3 offered by the MMTel enabler server. The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for MMTel Service are contained in 3GPP TS 23.392 [2]. |
29.435 | Service Enabler Architecture Layer for Verticals (SEAL); Network Slice Capability Enablement (NSCE) Server Services | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.435/29435-j10.zip | The present document specifies the stage 3 protocol and data model for the Network Slice Capability Exposure (NSCE) Server Services, for enabling the support of Network Slice Capability Exposure (NSCE) Server services for vertical applications. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSCE Server.
The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for enabling Network Slice Capability Exposure (NSCE) are specified in 3GPP TS 23.435 [14].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [2]. |
29.437 | Service Enabler Architecture Layer for Verticals (SEAL); Metaverse Enablement Services; Stage 3 | TS | 1.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.437/29437-100.zip | The present document specifies the stage 3 protocol and data model for the SAn and SM Service(s), for enabling the support of Spatial Anchor and Spatial Map management services for vertical applications. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SAn and SM servers.
The stage 2 architecture and procedures are specified in 3GPP TS 23.437 [13].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [2]. |
29.482 | Service Enabler Architecture Layer for Verticals (SEAL); Artificial Intelligence Machine Learning Enablement (AIMLE) Services; Stage 3 | TS | 1.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.482/29482-100.zip | The present document specifies the stage 3 protocol and data model for the AIML Enablement (AIMLE) Services, for enabling the support of AIMLE Services for vertical applications. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AIMLE Services.
The stage 2 architecture and procedures are specified in 3GPP TS 23.482 [13].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [2]. |
29.486 | V2X Application Enabler (VAE) Services; Stage 3 | TS | 19.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.486/29486-j20.zip | The present document specifies the stage 3 protocol and data model for Vs interface between the V2X application specific server and VAE server and VAE-E interface between VAE servers. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the VAE server. The Vs, VAE-E interfaces and the related stage 2 functional requirements are defined in 3GPP TS 23.286 [4].
The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for enabling Vehicle-to-Everything (V2X) are specified in 3GPP TS 23.286 [4].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [27]. |
29.500 | 5G System; Technical Realization of Service Based Architecture; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.500/29500-j30.zip | The present document specifies the technical realization of the 5GC Service Based Architecture, protocols supported over the Service Based Interfaces, and the functionalities supported in the Service Based Architecture.
The service requirements for the 5G system are defined in 3GPP TS 22.261 [2]. The system architecture requirements are defined in 3GPP TS 23.501 [3] and the procedures and flows in 3GPP TS 23.502 [4].
The design principles and documentation guidelines for 5GC SBI APIs are specified in 3GPP TS 29.501 [5]. |
29.501 | 5G System; Principles and Guidelines for Services Definition; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.501/29501-j20.zip | The present document defines design principles and documentation guidelines for 5GC SBI APIs. These principles and guidelines should be followed when drafting the 5G System SBI Stage 3 specifications. |
29.502 | 5G System; Session Management Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.502/29502-j30.zip | The present document specifies the stage 3 protocol and data model for the Nsmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMF other than the Session Management Event Exposure service and Session Management services for Non-IP Data Delivery (NIDD).
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Session Management Event Exposure Service is specified in 3GPP TS 29.508 [6]. The Session Management services for Non-IP Data Delivery (NIDD) are specified in 3GPP TS 29.542 [37]. |
29.503 | 5G System; Unified Data Management Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.503/29503-j30.zip | The present document specifies the stage 3 protocol and data model for the Nudm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDM.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.504 | 5G System; Unified Data Repository Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.504/29504-j30.zip | The present document specifies the stage 3 protocol and high level data model for the Nudr Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Unified Data Repository (UDR). The data model and usage of the subscription data is specified in 3GPP TS 29.505 [2], and the data model and usage of the policy data, structured data for exposure and application data are specified in 3GPP TS 29.519 [3].
The 5G System architecture is specified in 3GPP TS 23.501 [4]. The stage 2 definition and related procedures for Nudr SBI service are specified in 3GPP TS 23.502 [5] and 3GPP TS 23.503 [6].
The Technical Realization of the Service Based Architecture is specified in 3GPP TS 29.500 [7] and the Principles and Guidelines for Services Definition is specified in 3GPP TS 29.501 [8]. |
29.505 | 5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.505/29505-j30.zip | The present document specifies the usage of the Unified Data Repository services for subscription data. It provides the resource definition and data model for subscription data used over the Nudr Service Based Interface. The protocol definition for Nudr Service Based Interface which is specific to subscription data is also specified in the present document.
The stage 3 protocol definition for Nudr Service Based Interface which is common for subscription data, policy data, structure data and application data for exposure is specified in 3GPP TS 29.504 [2]. |
29.506 | 5G System; Usage of the Unified Data Repository services for AIoT Device Profile Data, Stage 3 | TS | 0.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.506/29506-000.zip | This clause will describe the scope of the corresponding service specification.
The present document specifies the stage 3 protocol and data model for the <NNF, e.g. Nsmf> Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the <NF, e.g. SMF>.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2] and TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5]. |
29.507 | 5G System; Access and Mobility Policy Control Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.507/29507-j30.zip | The present specification provides the stage 3 definition of the Access and Mobility Policy Control Service (Npcf_AMPolicyControl) of the 5G System.
The stage 2 definition and procedures of the Access and Mobility Policy Control Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Access and Mobility Policy Control Service is provided by the Policy Control Function (PCF). This service provides Access and Mobility Policies. |
29.508 | 5G System; Session Management Event Exposure Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.508/29508-j30.zip | The present specification provides the stage 3 definition of the Session Management Event Exposure Service (Nsmf_EventExposure) of the 5G System.
The stage 2 definition and procedures of the Session Management Event Exposure Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows for policy and charging control use cases are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Session Management Event Exposure Service is provided by the Session Management Function (SMF). This service exposes events related to PDU Sessions observed at the SMF. |
29.509 | 5G System; Authentication Server Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.509/29509-j30.zip | The present document specifies the stage 3 protocol and data model for the Nausf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AUSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 33.501 [8].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.510 | 5G System; Network function repository services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.510/29510-j30.zip | The present document specifies the stage 3 protocol and data model for the Nnrf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NRF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.512 | 5G System; Session Management Policy Control Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.512/29512-j30.zip | The present document provides the stage 3 specification of the Session Management Policy Control Service of 5G system. The stage 2 definition and related procedures of the Session Management Policy Control Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Policy Control Function with session related policies provides the Session Management Policy Control Service to the NF server consumers (e.g. Session Management Function). |
29.513 | 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.513/29513-j30.zip | The present document specifies detailed call flows of Policy and Charging Control (PCC) over the Npcf, Nsmf, Namf, Nudr, Nnef, Nchf, Nbsf, Nnwdaf and Nmbsmf service-based interfaces and their relationship with the flow level signalling in 5G system.
NOTE: The call flows depicted in this Technical Specification do not cover all traffic cases.
The stage 2 definition and procedures of PCC are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
The stage 2 definition and procedures for PCC specific for wireless and wireline convergence are contained in 3GPP TS 23.316 [70].
The stage 2 definition and procedures of PCC for 5G multicast/broadcast services are contained in 3GPP TS 23.247 [54].
Detailed stage 3 procedures are provided in 3GPP TS 29.507 [7], 3GPP TS 29.508 [8], 3GPP TS 29.512 [9], 3GPP TS 29.514 [10], 3GPP TS 29.520 [11], 3GPP TS 29.519 [12], 3GPP TS 29.521 [22], 3GPP TS 29.594 [23], 3GPP TS 29.522 [24], 3GPP TS 29.551 [25], 3GPP TS 29.525 [31], 3GPP TS 29.554 [26] and 3GPP TS 29.537 [55].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The present specification also describes the PCC reference architectures for non-roaming and roaming scenarios in 5G system.
The present specification also describes the mapping of QoS parameters at AF, PCF,| SMF and MB-SMF.
The present specification also describes the session binding at PCF, and the QoS flow binding at SMF and MB-SMF.
The present specification also describes the PCF addressing.
The present specification also describes the Race condition handling. |
29.514 | 5G System; Policy Authorization Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.514/29514-j30.zip | The present specification provides the stage 3 definition of the Policy Authorization Service of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for the Npcf Policy Authorization Service are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Policy Authorization Service is provided by the Policy Control Function (PCF). This service creates policies as requested by the authorised AF for the PDU Session to which the AF session is bound. |
29.515 | 5G System; Gateway Mobile Location Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.515/29515-j30.zip | The present document specifies the stage 3 protocol and data model for the Ngmlc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the GMLCc.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6]. |
29.517 | 5G System; Application Function Event Exposure Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.517/29517-j30.zip | The present document specifies the stage 3 protocol and data model for the Application Function Event Exposure Service of the 5G System. It provides stage 3 protocol definitions, message flows and specifies the API for the Naf_EventExposure service.
The 5G System stage 2 architecture and the procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], and 3GPP TS 23.288 [4].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Application Function Event Exposure Service is provided by the Application Function (AF). This service exposes service experience events observed at the AF. |
29.518 | 5G System; Access and Mobility Management Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.518/29518-j30.zip | The present document specifies the stage 3 protocol and data model for the Namf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AMF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.247 [55].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.519 | 5G System; Usage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.519/29519-j30.zip | The present specification provides the stage 3 definition for the usage of the Unified Data Repository service (Nudr_DataRepository) of 5G System for Policy Data, Application Data and Structured Data for Exposure.
The Unified Data Repository (UDR) provides the Unified Data Repository service. This service provides a repository for policy data, application data and exposure data.
The stage 3 protocol definition for Nudr Service Based Interface which is common for subscription data, policy data, application data and exposure data is specified in 3GPP TS 29.504 [6]. |
29.520 | 5G System; Network Data Analytics Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.520/29520-j30.zip | The present specification provides the stage 3 definition of the Network Data Analytics Function Services of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for Network Data Analytics Function Services are specified in 3GPP TS 23.288 [17] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.552 [25] and 3GPP TS 29.513 [5].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [6] and 3GPP TS 29.501 [7].
The Network Data Analytics Function Services are provided by the Network Data Analytics Function (NWDAF). |
29.521 | 5G System; Binding Support Management Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.521/29521-j30.zip | The present specification provides the stage 3 definition of the Binding Support Management Service of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for Binding Support Management Service is specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [5].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [6] and 3GPP TS 29.501 [7].
The Binding Support Management Service is provided by the Binding Support Function (BSF). |
29.522 | 5G System; Network Exposure Function Northbound APIs; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.522/29522-j30.zip | The present specification describes the protocol for the NEF Northbound interface between the NEF and the AF. The NEF Northbound interface and the related stage 2 functional requirements are defined in 3GPP TS 23.501 [3], 3GPP TS 23.502 [2], 3GPP TS 23.316 [28], 3GPP TS 23.288 [29], 3GPP TS 23.273 [36], 3GPP TS 23.548 [42], 3GPP TS 23.247 [53], 3GPP TS 23.503 [70], 3GPP TS 33.501 [6], 3GPP TS 33.535 [37], 3GPP TS 33.558 [56], 3GPP TS 26.531 [59], 3GPP TS 26.532 [60], 3GPP TS 26.502 [65], 3GPP TS 23.586 [76] and 3GPP TS 23.256 [77]. |
29.523 | 5G System; Policy Control Event Exposure Service; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.523/29523-j10.zip | The present document specifies the stage 3 protocol and data model for the Policy Control Event Exposure Service of the 5G System. It provides stage 3 protocol definitions, message flows and specifies the API for the Npcf Event Exposure service.
The 5G System stage 2 architecture and the procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [8].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Policy Control Event Exposure Service is provided by the Policy Control Function (PCF). This service exposes policy control events observed at the PCF. |
29.525 | 5G System; UE Policy Control Service; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.525/29525-j30.zip | The present specification provides the stage 3 definition of the UE Policy Control Service (Npcf_UEPolicyControl) of the 5G System.
The stage 2 definition and procedures of UE Policy Control Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows are provided in 3GPP TS 29.513 [7].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The UE Policy Control Service is provided by the Policy Control Function (PCF). This service provides UE policies and N2 PC5 policy. |
29.526 | 5G System; Network Slice-Specific and SNPN Authentication and Authorization services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.526/29526-j10.zip | The present document specifies the stage 3 protocol and data model for the Nnssaaf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSSAAF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.531 | 5G System; Network Slice Selection Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.531/29531-j30.zip | The present document specifies the stage 3 protocol and data model for the Nnssf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.532 | 5G System; 5G Multicast-Broadcast Session Management Services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.532/29532-j10.zip | The present document specifies the stage 3 protocol and data model for the Nmbsmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MB-SMF with the exception of the MB-SMF Event Exposure service.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The 5G Multicast-Broadcast Session Management Services for 5G System is specified in 3GPP TS 23.247 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.534 | 5G System; Access and Mobility Policy Authorization Service; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.534/29534-j10.zip | The present document specifies the stage 3 protocol and data model for the Access and Mobility Policy Authorization service (Npcf_AMPolicyAuthorization) of the 5G System.
The 5G System stage 2 architecture of the Access and Mobility Policy Authorization service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
Stage 3 call flows for policy and charging control use cases are provided in 3GPP TS 29.513 [15].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Access and Mobility Policy Authorization service is provided by the Policy Control Function (PCF). This service creates access and mobility policies (e.g. service area restrictions, or access stratum time distribution information) as requested by an authorized NF service consumer (e.g. AF, NEF, or TSCTSF) for the Access and Mobility Policy Context to which the related NF service consumer's context (e.g. AF, NEF, or TSCTSF) is bound. This service also enables subscription/notifications on UE 5G ProSe Policy event(s) related to the UE context to which the NF service consumer's context (e.g. 5G DDNMF) is bound. |
29.535 | 5G System; AKMA Anchor Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.535/29535-j30.zip | The present document specifies the stage 3 protocol and data model for the AAnF Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AAnF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 33.535 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.536 | 5G System; Network Slice Admission Control Services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.536/29536-j10.zip | The present document specifies the stage 3 protocol and data model for the Nnsacf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSACF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.537 | 5G System; Multicast/Broadcast Policy Control services; Stage 3 | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.537/29537-j00.zip | The present document specifies the stage 3 protocol and data model for the Service Based Interfaces of the Multicast/Broadcast Policy Control Services. It provides stage 3 protocol definitions and message flows, and specifies the APIs of the Multicast/Broadcast Services provided by the PCF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The stage 2 architecture and procedures for 5G Multicast/Broadcast Services are specified in 3GPP TS 23.247 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.538 | Enabling MSGin5G Service; Application Programming Interfaces (API) specification; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.538/29538-j30.zip | The present document specified the Application Programming Interface (API) for enabling the MSGin5G Service over MSGin5G-2/3/4/7/8 interfaces. The application layer architecture, functional requirements, procedures and information flows necessary for MSGin5G Service are contained in 3GPP TS 23.554 [2]. The requirements for MSGin5G are specified in 3GPP TS 22.262 [3]. |
29.540 | 5G System; SMS Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.540/29540-j20.zip | The present document specifies the stage 3 protocol and data model for the Nsmsf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.541 | 5G System; Network Exposure (NE) function services for Non-IP Data Delivery (NIDD) and Short Message Services (SMS); Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.541/29541-j10.zip | The present document specifies the stage 3 protocol and data model for the Nnef Service Based South-Bound Interfaces for NIDD. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NEF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.542 | 5G System; Session management services for Non-IP Data Delivery (NIDD); Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.542/29542-j10.zip | The present document specifies the stage 3 protocol and data model for the Nsmf Service Based Interfaces for Non-IP Data Delivery (NIDD). It provides stage 3 protocol definitions and message flows, and specifies the API for the service offered by the SMF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.543 | 5G System; Data Transfer Policy Control Services; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.543/29543-j10.zip | The present document specifies the stage 3 protocol and data model for the Service Based Interface (SBI) of the Data Transfer Policy Control Services. It provides stage 3 protocol definitions and message flows, and specifies the APIs of the Data Transfer Policy Control Services offered by the Policy Control Function (PCF).
The 5G System stage 2 architecture is specified in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for Data Transfer Policy Control Services are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [14].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [15].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.544 | 5G System; Secured Packet Application Function (SP-AF) services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.544/29544-j10.zip | The present document specifies the stage 3 protocol and data model for the Nspaf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SP-AF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.548 | Service Enabler Architecture Layer for Verticals (SEAL); SEAL Data Delivery (SEALDD) Server Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.548/29548-j30.zip | The present document specifies the stage 3 protocol and data model for the SEAL Data Delivery (SEALDD) Server Services, for enabling the support of SEAL Data Delivery (SEALDD) services for vertical applications. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SEALDD Server.
The stage 2 application layer architecture, functional requirements, procedures and information flows necessary for enabling SEAL Data Delivery (SEALDD) are specified in 3GPP TS 23.433 [7].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [2]. |
29.549 | Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.549/29549-j30.zip | The present specification describes the APIs for the Service Enabler Architecture Layer for Verticals (SEAL). The related stage 2 architecture, functional requirements and information flows are specified in 3GPP TS 23.434 [2] and 3GPP TS 23.433 [34] (for SEAL Data Delivery). |
29.550 | 5G System; Steering of roaming application function services; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.550/29550-j00.zip | The present document specifies the stage 3 protocol and data model for the Nsoraf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SOR-AF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The stage 2 architecture and procedures for 5G Steering of Roaming are specified in 3GPP TS 23.122 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.551 | 5G System; Packet Flow Description Management Service; Stage 3 | TS | 19.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.551/29551-j20.zip | The present document provides the stage 3 specification of the PFD Management Service of the 5G system.
The stage 2 definition and related procedures of the PFD Management Service are contained in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4]. The 5G System Architecture is defined in 3GPP TS 23.501 [2].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
The Packet Flow Description Function (PFDF) provides the PFD Management Service to NF service consumers (e.g. Session Management Function). The PFDF is functionality within the NEF. |
29.552 | 5G System; Network Data Analytics signalling flows; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.552/29552-j30.zip | The present document specifies detailed call flows of Network Data Analytics and the related data collection over the Nnwdaf, Nsmf, Nnsacf, Namf, Nnrf, Nnssf, Nnef, Naf, Ndccf, Nadrf, Nmfaf, Nudm, Nupf, Ngmlc, Npcf, and Nlmf service-based interfaces and/or from OAM, and their relationship with the flow level signalling in 5G system.
NOTE 1: The call flows depicted in this Technical Specification do not cover all traffic cases.
NOTE 2: There is no data collected from the PCF by the NWDAF defined in this Release of the specification.
The stage 2 definition and procedures of Network Data Analytics are contained in 3GPP TS 23.288 [2] and 3GPP TS 23.502 [3]. The 5G System Architecture is defined in 3GPP TS 23.501 [4].
Detailed definitions of the involved services are provided in 3GPP TS 29.520 [5], 3GPP TS 29.508 [6], 3GPP TS 29.554 [8], 3GPP TS 29.522 [10], 3GPP TS 29.591 [11], 3GPP TS 29.517 [12], 3GPP TS 29.551 [39], 3GPP TS 29.574 [15], 3GPP TS 29.575 [16], 3GPP TS 29.576 [17], 3GPP TS 29.503 [22], 3GPP TS 29.510 [23], 3GPP TS 29.507 [24], 3GPP TS 29.512 [25], 3GPP TS 29.564 [40], 3GPP TS 29.515 [41], 3GPP TS 29.572 [47], 3GPP TS 29.523 [51], and 3GPP TS 29.244 [45] for NF service-based interfaces, 3GPP TS 28.552 [27], 3GPP TS 28.532 [19], 3GPP TS 28.533 [28], 3GPP TS 28.550 [31] , 3GPP TS 28.554 [30], 3GPP TS 36.331 [34], 3GPP TS 37.320 [29], 3GPP TS 38.331 [33] and 3GPP TS 38.215 [35] for data collection from OAM.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [13] and 3GPP TS 29.501 [14]. |
29.553 | 5G System; 5G ProSe Anchor Services; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.553/29553-j00.zip | The present document specifies the stage 3 protocol and data model for the Npanf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the 5G PAnF.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2] and TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5]. |
29.554 | 5G System; Background Data Transfer Policy Control Service; Stage 3 | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.554/29554-j00.zip | The present specification provides the stage 3 definition of the Background Data Transfer (BDT) Policy Control Service (Npcf_BDTPolicyControl) of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for BDT Policy Control Service are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [5].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [6] and 3GPP TS 29.501 [7].
The Policy Control Function (PCF) provides the BDT Policy Control Service. This service provides background data transfer policy negotiation function. |
29.555 | 5G System; 5G Direct Discovery Name Management Services; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.555/29555-j00.zip | The present document specifies the stage 3 protocol and data model for the N5g-ddnmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the 5G DDNMF as specified in 3GPP TS 23.304 [4].
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6]. |
29.556 | Edge Application Server Discovery Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.556/29556-j20.zip | The present document specifies the stage 3 protocol and data model for the Neasdf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the EASDF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.548 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.557 | 5G System; Application Function ProSe Service; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.557/29557-j10.zip | The present document specifies the stage 3 protocol and data model for the Application Function ProSe Service of the 5G System. It provides stage 3 protocol definitions and message flows, and specifies the API for the Naf_ProSe service.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.304 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Application Function ProSe Service is provided by the Application Function (AF). This service supports 5G ProSe Direct Discovery authorization. |
29.558 | Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.558/29558-j30.zip | The present document specifies the APIs for enabling the edge applications over 3GPP networks. The application layer architecture, functional requirements, procedures and information flows necessary for enabling edge applications over 3GPP networks are specified in 3GPP TS 23.558 [2]. The APIs are specified as RESTful APIs except for custom operations wherever required. |
29.559 | 5G System; 5G ProSe Key Management Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.559/29559-j20.zip | The present document specifies the stage 3 protocol and data model for the Npkmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the 5G PKMF as specified in 3GPP TS 33.503 [4].
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6]. |
29.561 | 5G System; Interworking between 5G Network and external Data Networks; Stage 3 | TS | 19.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.561/29561-j20.zip | The present specification defines the stage 3 interworking procedures for 5G Network interworking between PLMN and external DN or Network Slice Specific AAA.
The stage 2 requirements and procedures are contained in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
For interworking between 5G PLMN and external DNs, the present document is valid for both 3GPP accesses and non-3GPP accesses. |
29.562 | 5G System; Home Subscriber Server (HSS) services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.562/29562-j20.zip | The present document specifies the stage 3 protocol, including message flows and API specification details, for the Nhss services, as part of the 5G Service-Based Architecture, offered by the HSS.
The HSS services specified in the present document include:
- Services for interworking with the IP Multimedia Subsystem (IMS)
- Services for interworking with the Generic Bootstrapping Architecture (GBA)
NOTE: The HSS services for Interworking with the Unified Data Management (UDM) Network Function are specified in 3GPP TS 29.563 [39].
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The IP Multimedia Subsystem (IMS) stage 2 architecture and procedures are specified in 3GPP TS 23.228 [6].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The stage 2 architecture and procedures of SBA-enabled GBA is specified in 3GPP TS 33.220 [40] and 3GPP TS 33.223 [41]. |
29.563 | 5G System; Home Subscriber Server (HSS) services for interworking with Unified Data Management (UDM); Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.563/29563-j10.zip | The present document specifies the stage 3 protocol, including message flows and API specification details, for the Nhss services, as part of the 5G Service-Based Architecture, offered by the HSS for interworking with the 5G UDM Network Function.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The User Data Interworking, Coexistence and Migration stage 2 architecture and procedures are specified in 3GPP TS 23.632 [8].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.564 | 5G System; User Plane Function Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.564/29564-j30.zip | The present document specifies the stage 3 protocol and data model for the Nupf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UPF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.548[14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.565 | 5G System; Time Sensitive Communication and Time Synchronization Function Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.565/29565-j30.zip | The present document specifies the stage 3 protocol and data model for the Ntsctsf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the TSCTSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [19].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.566 | 5G System; Energy Information Function Services; Stage 3 | TS | 1.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.566/29566-100.zip | This clause will describe the scope of the corresponding service specification.
The present document specifies the stage 3 protocol and data model for the <NNF, e.g. Nsmf> Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the <NF, e.g. SMF>.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2] and TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5]. |
29.569 | 5G System; Ambient IoT Function (AIOTF) Services, Stage 3 | TS | 1.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.569/29569-100.zip | The present document specifies the stage 3 protocol and data model for the Naiotf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the AIOTF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.369 [14], 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.570 | 5G System; Service Communication Proxy (SCP) Services; Stage 3 | TS | 1.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.570/29570-100.zip | The present document specifies the stage 3 protocol and data model for the Nscp Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SCP.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2], TS 23.288 [14], and TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5]. |
29.571 | 5G System; Common Data Types for Service Based Interfaces; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.571/29571-j30.zip | The present document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
The Principles and Guidelines for Services Definition are specified in 3GPP TS 29.501 [2]. |
29.572 | 5G System; Location Management Services; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.572/29572-j30.zip | The present document specifies the stage 3 protocol and data model for the Nlmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the LMF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.573 | 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.573/29573-j30.zip | The present document specifies the stage 3 protocol and data model for the PLMN and/or SNPN interconnection Interface. It provides stage 3 protocol definitions and message flows, and specifies the APIs for the procedures on the PLMN interconnection interface (i.e N32).
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The stage 2 level N32 procedures are specified in 3GPP TS 33.501 [6]. |
29.574 | 5G System; Data Collection Coordination Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.574/29574-j30.zip | The present document specifies the stage 3 protocol and data model for the Ndccf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Data Collection Coordination Function (DCCF).
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.288 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.575 | 5G System; Analytics Data Repository Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.575/29575-j30.zip | The present document specifies the stage 3 protocol and data model for the ADRF Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the ADRF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The stage 2 definition and procedures of store and retrieve the collected data and analytics are contained in 3GPP TS 23.288 [14] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.576 | 5G System; Messaging Framework Adaptor Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.576/29576-j30.zip | The present document specifies the stage 3 protocol and data model for the MFAF Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MFAF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The stage 2 definition and procedures of Messaging Framework Adaptation are contained in 3GPP TS 23.288 [14] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.577 | 5G System; IP Short Message Gateway and SMS Router For Short Message Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.577/29577-j20.zip | The present document specifies the stage 3 protocol and data model for the Nipsmgw and Nrouter Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the IP-SM-GW and SMS Router.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4] and TS 29.501 [5].
The Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS) is specified in 3GPP TS 23.540 [14]. |
29.578 | 5G System; Mobile Number Portability Services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.578/29578-j10.zip | The present document specifies the stage 3 protocol and data model for the Nmnpf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MNPF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
Stage 2 requirements for the Nmnpf services are specified in 3GPP TS 23.540 [14]. |
29.579 | 5G System; Interworking MSC For Short Message Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.579/29579-j20.zip | The present document specifies the stage 3 protocol and data model for the Niwmsc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMS-IWMSC.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
Stage 2 requirements for the Niwmsc services are specified in 3GPP TS 23.540 [14]. |
29.580 | 5G System; Multicast/Broadcast Service Function services; Stage 3 | TS | 19.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.580/29580-j20.zip | The present document specifies the stage 3 protocol and data model for the Nmbsf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MBSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The stage 2 architecture and procedures for 5G Multicast/Broadcast Services are specified in 3GPP TS 23.247 [14] and 3GPP TS 26.502 [15].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.581 | 5G System; Multicast/Broadcast Service Transport Services; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.581/29581-j00.zip | The present document specifies the stage 3 protocol and data model for the Nmbstf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MBSTF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The 5G Multicast-Broadcast Session Management Services for 5G System is specified in 3GPP TS 23.247 [15] and the User Service Architecture for 5G Multicast-Broadcast Services is specified in 3GPP TS 26.502 [17].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.586 | 5G System; SideLink Positioning Key Management Services; Stage 3 | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.586/29586-j10.zip | The present document specifies the stage 3 protocol and data model for the Nslpkmf Service Based Interface to support ranging based service and sidelink positioning in 5G system. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SLPKMF as specified in 3GPP TS 33.533 [2].
The 5G System stage 2 architecture and procedures for ranging based service and sidelink positioning are specified in 3GPP TS 23.586 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [6]. |
29.591 | 5G System; Network Exposure Function Southbound Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.591/29591-j30.zip | The present document specifies the stage 3 protocol and data model for the Nnef southbound Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Network Exposure Function (NEF).
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.288 [14].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.594 | 5G System; Spending Limit Control Service; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.594/29594-j10.zip | The present specification provides the stage 3 definition of the Spending Limit Control Service of the 5G System.
The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The stage 2 definition and related procedures for the Spending Limit Control Service are specified in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [6].
The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [12].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
The Spending Limit Control Service is provided by the Charging Function (CHF) and enables the NF service consumer to retrieve policy counter status information. The internal CHF functionality for policy counter management provisioning is specified in 3GPP TS 32.240 [7]. |
29.598 | Unstructured data storage services | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.598/29598-j20.zip | The present document specifies the stage 3 protocol and data model for the Nudsf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.673 | 5G System; UE radio capability management services; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.673/29673-j00.zip | The present document specifies the stage 3 protocol and data model for the Nucmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Nucmf.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.675 | User Equipment (UE) radio capability provisioning service; Stage 3 | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.675/29675-j00.zip | The present document specifies the stage 3 protocol and data model for the Nucmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UCMF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5]. |
29.857 | Study on Reducing Information Exposure over SBI | TR | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.857/29857-j00.zip | The present document identifies scenarios where excessive data may be exposed over SBI when an NF-Consumer accesses an API exposed by an NF-Producer, and studies potential solutions to limit the same. The document will focus on following aspects:
- To study the need and potential solutions for avoiding excessive data exposure over SBI.
- To study the need and potential solutions for avoiding indirect access to data via, e.g. subscriptions, even as direct access to the data-set is not allowed.
NOTE 1: The study does not preclude API specific solutions or a generic solution applicable to all APIs.
NOTE 2: The study does not preclude issues not relating to security aspects of excessive data exposure. |
29.866 | Study on IMS Disaster Prevention and Restoration Enhancement | TR | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.866/29866-j00.zip | The present document identifies IMS restoration mechanisms as specified in 3GPP TS 23.380 [2] and studies potential optimization solutions. The document will focus on the following aspects:
- Create/enhance corresponding the restoration mechanism to support the normal use of voice, video and SMS services in the IMS network. Specifically, it adopts the context data of registered online users stored by HSS/UDM, S-CSCF, P-CSCF and MMTEL to bypass the involved faulty network functions or links. That supports the following procedures:
- Re-registration procedure for registered online users;
- Mobile terminated procedure for registered online users;
- EPS fallback procedure for registered online users;
- Initial registration procedure for registered online users after deregistration.
- Create/enhance corresponding network disaster-prevention mechanisms, including:
- UE specific registration analysis mechanism, to prevent registration with missing parameter or incorrect parameters repeatedly. |
29.867 | Study on IMS resiliency | TR | 0.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.867/29867-010.zip | The present document investigates and identifies enhancements on 5GS and IMS to support the network resiliency. The document will focus on the following aspects:
- Study and identify IMS congestion scenarios and whether lack of coordination between UE and network exacerbates the congestion
- Study whether the current standardised solutions can work for the identified scenarios or not
- If the existing solutions cannot work for the identified scenarios, then study new potential solutions |
29.889 | Study on Protocol for AI Data Collection from UPF | TR | 1.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.889/29889-100.zip | The present document aims at studying UPF data Collection for AI/ML and whether alternative protocols, or enhancements to the existing SBI protocol, are needed to optimize the AI/ML data collection while ensuring secure, scalable and reliable data transfers across the core network identifies. The present document will focus on the following aspects:
- To identify the use cases for UPF data Collection for AI/ML where current mechanisms do not suffice.
- To study on the potential optimized protocol solutions for efficient AI/ML data collection.
- To study on the mechanisms to optimize the protocol selection when different protocols exist.
NOTE 1: Data collection from 5GC NFs other than UPF is out of scope of this study.
NOTE 2: The study remains within the limits of the existing 5GC architecture and stage 2 requirements. Only the protocol for collecting the data is the object of this study. |
31.102 | Characteristics of the Universal Subscriber Identity Module (USIM) application | TS | 19.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-j20.zip | The present document defines the USIM application for 3GPP telecom network operation.
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 (USIM) and ME.
This is to ensure interoperability between a USIM 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 USIM. Any internal technical realisation of either the USIM 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.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 19.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-j20.zip | The present document defines the interface between the UICC and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "USIM Application Toolkit".
The present document refers in its majority to the ETSI TS 102 223 [32], which describes the generic aspects of application toolkits within the UICC.
USAT is a set of commands and procedures for use during 3GPP network operation phase, in addition to those defined in TS 31.101 [13].
Specifying the interface is to ensure interoperability between a UICC and an ME independently of the respective manufacturers and operators.
The present document defines for:
- the commands;
- the application protocol;
- the mandatory requirements on the UICC and ME for each procedure.
The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the UICC or the ME are only specified where these reflect over the interface. The present document does not specify any of the security algorithms which may be used.
For the avoidance of doubt, references to clauses of ETSI TS 102 223 [32] include all the clauses of that clause, unless specifically mentioned.
The target specification ETSI TS 102 223 [32] 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. |
32.130 | Telecommunication management; Network sharing; Concepts and requirements | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.130/32130-j10.zip | The present document describes concepts and high-level requirements for the Operations, Administration, Maintenance and Provisioning (OAM&P) of network sharing.
Network sharing scenarios considered in the present document are Multiple Operator Core Network (MOCN) and Gateway Core Network (GWCN) for GERAN, UTRAN and E-UTRAN, as defined in TS 23.251 [7] , and Multiple Operator Core Network (MOCN) for NG-RAN as defined in TS 23.501[7]. |
32.156 | Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.156/32156-j30.zip | UML provides a rich set of concepts, notations and model elements to model distributive systems. This paper documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>> to model network management systems and their managed nodes. This set of notations and model elements is called the FMC (developed by the Converged Management of Fixed/Mobile Networks project) Model Repertoire; see also 3GPP TS 32.107 [5] and 3GPP TS 28.620 [6]. |
32.160 | Management and orchestration; Management service template | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.160/32160-j30.zip | The present document contains the templates to be used for the production of Management service component specifications type A, type B and type C [2]. |
32.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-j30.zip | The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks/systems. The 3GPP core network charging architecture and principles are specified in the present document, which thus 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 events 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 purposes of the present document are:
- to lay down common principles of charging in the network; and
- to specify a logical common charging architecture that applies to all 3GPP domains, subsystems and services.
A set of domain/subsystem/service specific TSs covers the domains (CS, PS, 5GS), subsystem (IMS) and service (MMS, LCS, PoC, MBMS, SMS, MMTel, TSN etc.) levels, respectively, in the TS 32.25x, TS 32.26x, TS 32.27x and TS 32.28x TS number ranges. Network Slicing is covered under TS 28.201[70], TS 28.202 [71], TS 28.203 [72] and TS 28.204 [73].These TSs describe the mapping of the common architecture specified in the present document onto the specific domain/subsystem/service and the scenarios and information for online, and converged charging that are specific to the domain/subsystem/service. They are commonly referred to as the middle tier charging TSs.
A set of TSs in the TS 32.28x range covers common services, such as the Advice of Charge service.
A set of TSs in the TS 32.29x range covers common aspects, such as CDR parameter and syntax descriptions, online and offline charging applications, converged charging API, and the charging interactions within the network (CDR transfer) as well as between the network and the Billing Domain (CDR file transfer).
The complete document structure for these TSs is outlined in the following figure 1.1:
Figure 1.1: Charging specifications structure
NOTE: TSs which are indicated with "Nchf" in Figure 1.1 are those which include the converged charging architecture.
In addition to 3GPP core networks/systems charging architecture and principles, this document encompasses charging architecture and principles for the convergent scenario (i.e. both the Fixed Broadband Access network and Evolved Packet Core (EPC) owned by a single operator), which is specified in annex C.
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 domains, services or subsystems are provided in the present document (umbrella TS), and are copied into clause 3 of the other TSs depicted in the figure 1.1, 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.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-j00.zip | The present document is part of a series of Technical Specifications (TSs) specifying charging functionality and charging management in Packet Switched networks (GSM/UMTS, EPS). The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain / subsystem / service (offline charging);
- the content of real-time charging messages per domain / subsystem /service (online charging);
- the functionality of online and offline charging for those domains / subsystems / services;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for the charging TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for the Packet Switched (PS) domain based on the functional stage 2 description in TS 23.060 [201], TS 23.401 [208] and TS 23.402 [209].
The offline and online charging description for the PS domain encompasses also fixed broadband access in the convergent scenario deployment (i.e. both the fixed broadband access network and Evolved Packet Core (EPC) owned by a single operator) based on the functional stage 2 description in the corresponding Annex of TS 23.203 [215].
This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PS domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52];
- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in TS 32.299 [50].
Note that a CAMEL based prepaid function and protocol is also specified for the PS domain (TS 23.078 [206] and TS 29.078 [202]). CAMEL entities and functions are outside the scope of the present document.
All terms, definitions and abbreviations used in the present document, which are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in PS domains, services or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.254 | Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.254/32254-j10.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], 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, online and converged charging description for Northbound Application Program Interfaces (API), based on the functional stage 2 description in TS 23.682 [243] for transaction over T8 reference point between SCEF and SCS/AS and in TS 23.501 [200] for Network Exposure Function (NEF). This charging description includes the offline, online and converged charging architecture and scenarios specific to Northbound Application Program Interfaces (API), as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the Northbound Application Program Interfaces (API). 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 Northbound Application Program Interfaces (API) 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.255 | Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.255/32255-j20.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], 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 converged offline and online charging description for the 5G Data Connectivity domain based on the functional stage 2 description in TS 23.501 [200], TS 23.502 [201] and TS 23.503 [202].
This charging description includes the converged offline and online charging architecture and scenarios specific to the 5G Data Connectivity domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the 5G Data Connectivity domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for converged online and 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 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 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]. 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.256 | Charging management; 5G connection and mobility domain charging; Stage 2 | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.256/32256-j20.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], 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 the converged offline and online charging description for the 5G connection and mobility domain based on the functional stage 2 description in TS 23.501 [200], TS 23.502 [201] and TS 23.503 [202].
This charging description includes the converged offline and online charging architecture and scenarios specific to the 5G connection and mobility domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the 5G connection and mobility domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for converged online and 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 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 references, abbreviations, terms, descriptions, principles and requirements, 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 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.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-j00.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 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 events 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 description for the IP Multimedia Subsystem (IMS), based on the functional descriptions of the IMS in TS 23.228 [200]. This charging description includes the offline, online and converged charging architecture and scenarios specific to IMS, as well as the mapping of common 3GPP charging architecture specified in TS 32.240 [1] onto IMS. 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 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 IMS 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 [45].
- The charging service of 5G system is specified in TS 32.291 [46].
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-j20.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify
- the content of the CDRs per domain and subsystem (converged and offline charging);
- the content of real-time charging events per domain / subsystem (converged charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240 [1].
The present document specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in TS 23.271 [201], and the Ranging and Sidelink Positioning Converged Charging description based on TS 23.586 [206]. This charging description includes the offline and online charging architecture and scenarios specific to the LCS and converged charging architecture and scenarios specific to the Ranging and Sidelink Positioning, as well as the mapping of the common 3GPP architecture specified in TS 32.240 [1] onto the LCS domain including Ranging and Sidelink Positioning. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator’s billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52].
- The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 [50].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [55].
- The charging service of 5G system is specified in TS 32.291 [56].
All terms, definitions and abbreviations, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.274 | Telecommunication management; Charging management; Short Message Service (SMS) charging | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.274/32274-j00.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 [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 Offline and Online Charging description for the Short Message Service (SMS), based on the functional description in TS 23.040 [7], TS 23.204 [8] for SMS over IP, and TS 23.682 [17] for SMS procedures using T4. The present document does not replace existing offline SMS charging functionality defined for Circuit Switched in TS 32.250 [9] and for Packet Switched in TS 32.251 [10], and therefore is in addition to those specifications. This charging description includes the offline and online charging architecture and scenarios specific to SMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [2] onto SMS. 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 [2];
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [3];
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [6];
- 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 [5];
- The 3GPP Diameter application that is used for SMS offline and online charging is specified in TS 32.299 [4].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [19].
- The charging service of 5G system is specified in TS 32.291 [20].
Furthermore, requirements that govern the charging work are specified in TS 22.115 [102]. |
32.277 | Telecommunication management; Charging management; Proximity-based Services (ProSe) charging | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.277/32277-j10.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], which provides an umbrella for other charging management specifications that specify:
- the content of the CDRs per domain / subsystem / service (offline and convergedcharging);
- the content of real-time charging messages per domain / subsystem / service (online and converged 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 specifications is defined in TS 32.240 [1].
The present document specifies the offline, online and converged charging description for the Proximity-based Services (ProSe), based on the stage 2 description of ProSe in TS 23.303 [238] and TS 23.304 [241]. This charging description includes the offline, online and converged charging architecture and scenarios specific to the ProSe, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the ProSe. 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 ProSe offline and online charging is specified in TS 32.299 [50].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [55].
- The charging service of 5G system is specified in TS 32.291 [56].
All 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]. Those that are common across charging management in GSM/UMTS 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.290 | Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-j30.zip | The present document specifies service, operations and procedures of 5G charging for service based interface. This charging description includes the charging architecture and scenarios as well as the mapping of the common charging architecture specified in TS 32.240 [1]. 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 protocol that are used for service based interface is specified in TS 32.291 [58].
The description is following the same methodology as used in TS 23.501 [201] and TS 23.502 [202] for the 5G system. |
32.291 | Telecommunication management; Charging management; 5G system, charging service; Stage 3 | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.291/32291-j30.zip | The present document specifies the protocol that is used for service based interface. The API definitions and data type definitions are aligned with the common charging architecture specified in TS 32.240 [1]. 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 5G data connectivity charging is specified in TS 32.255 [30].
- The 5G connection and mobility charging is specified in TS 32.256 [31].
- The service, operations and procedures of 5G charging for service based interface is specified in TS 32.290 [58].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition of the 5G System are specified in 3GPP TS 29.500 [299] and 3GPP TS 29.501 [300]. |
32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-j20.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 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 and converged charging);
- the content of real-time charging events per domain/subsystem (online and converged charging);
- the functionality of online, offline and converged 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 present document specifies the CDR parameters, the abstract syntax and encoding rules for all the CDR types that are defined in the charging management TSs described above. The mechanisms used to transfer the CDRs from the generating node to the operator's Billing Domain (e.g. the billing system or a mediation device) are specified in TS 32.297 [52]. Further details with respect to internal functions of the operator's Billing Domain are out of scope of 3GPP standardisation.
The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1].
- 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 applications used for offline and online charging are 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 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]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.