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
|
|---|---|---|---|---|---|---|
26.925 | Typical traffic characteristics of media services on 3GPP networks | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.925/26925-j00.zip | The present document includes following information:
- Media centric Third-Party and Operator services currently deployed or expected to be deployed until 2025 on 3GPP defined 4G and 5G networks.
- Typical deployment characteristics today, such as bandwidth requirements, client buffered and rate adaptation reception characteristics, codecs, protocols in use and latency requirements.
- An overview on technological developments for existing and emerging services and their impact on typical traffic characteristics of media services, e.g. evolution of compression technologies, new demands for high quality, new experiences, etc.
- A summary on typical characteristics and requirements for different media services on 3GPP networks.
- An identification of the applicability of existing 5QIs for such services and potentially identify requirements for new 5QIs or QoS related parameters. |
26.926 | Traffic Models and Quality Evaluation Methods for Media and XR Services in 5G Systems | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.926/26926-j00.zip | The present document provides traffic models and quality evaluation methods for different media and eXtended Reality (XR) Services. In order to address this, generic modelling considerations are introduced and for different services reference designs, simulation models and suitable quality metrics are reported. This information permits to obtain accurate information on exact bitrate and delay requirements in uplink and downlink, develop detailed traffic traces, develop suitable statistical models for media and XR traffic and to evaluate the expected media quality of such services. The information may be used by other 3GPP groups in order to assess media quality for different configuration of 5G System parameters, as well as for evaluating the requirements in terms of QoS for XR and media services. |
26.927 | Study on Artificial Intelligence and Machine learning in 5G media services | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.927/26927-j00.zip | Editor’s note: to be defined based on the content of the TR |
26.933 | Study on Diverse Audio Capturing system | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.933/26933-j00.zip | The goal of this technical report is to study diverse audio capturing methods and applicable audio formats for the end-user device, considering the current physical and software constraints. The scope of the work is shown in Figure 1-1.
Figure 1‑1: Scope of TR 26.933 under the scope of the FS_DaCED study item
This document addresses audio capturing configurations for end-user devices, with the aim of equipping these devices with audio capturing capability to provide a truly immersive voice and audio service.
The document aims to study the following aspects:
1) Factors related to audio capture in different UE categories.
2) Components used in audio capture.
3) Acoustic design for audio capture.
4) Signal processing, such as microphone array beamforming processing, AEC processing etc.
5) Example of audio capture processing solutions. |
26.941 | Network Slicing Extensions for 5G media services | TR | 19.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.941/26941-j01.zip | The present document identifies standardization needs and potential standards gaps relevant to media streaming while using 5G network slicing. In specific, the following aspects are addressed in this document:
- To identify relevant use cases that can be addressed using network slicing, and study collaboration scenarios and deployment architectures to support network slicing for media services.
- To identify any missing provisioning aspects for configuring media services with one or more network slices including QoS configuration, reporting and dynamic policy.
- To identify impact of network slicing on dynamic policy invocation APIs, including selection of appropriate network slices for dynamic policy requests, possible migration of UE application traffic flows between network slices due to dynamic policy procedures, discovery of dynamic policy AF, and necessary routing considerations.
- To determine the need and describe methods for AF-to-AF communication to support interoperability if 5GMS AF instances from different vendors are deployed in the same 5GMS System.
- To identify methods for deploying, supporting, and resolving slice-specific 5GMS AS instances.
- To identify potential areas for normative work and communicate/align with SA2 as well as other potential 3GPP WGs (SA5, SA6) on relevant aspects related to the study. |
26.942 | Study on Media enerGy consumption exposuRE and EvaluatioN framework | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.942/26942-j00.zip | The present document identifies potential sustainable media metrics, architectural impacts (APIs), functional extensions required for media service enablers in the 5G system and evaluate the feasibility of an evaluation framework to facilitate efficient energy use and energy saving for media services. |
26.956 | Evaluation and Characterization of Beyond 2D Video Formats and Codecs | TR | 1.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.956/26956-100.zip | The present document collects beyond 2D video formats within 3GPP services, as well as a set of beyond 2D video end-to-end reference scenarios and corresponding workflows. It also documents relevant implementation constraints, performance characteristics, and interoperability requirements of existing 3GPP codecs as well as potentially new codecs to support these scenarios. [The primary scope of the present document includes the following aspects:
1. Identify and document beyond 2D formats, that are market-relevant within the next few years, generated from established and emerging capturing systems (including cameras for spatial video capturing), contribution, and usable on display technologies (smartphones, VR HMDs, AR glasses, autostereoscopic and multiscopic displays).
2. Establish and document a set of beyond 2D video end-to-end reference scenarios, including real-time communication, streaming services, split rendering, and messaging and corresponding workflows (capturing, encoding, packaging, delivery, decoding, rendering, including general constraints on latency, as well as complexity) to support 3GPP network related delivery and devices leveraging the generation or display technologies. This includes identifying and defining relevant beyond 2D formats in the context of above workflows, and representation technologies to support delivery of these formats within 3GPP networks.
3. Prioritize the scenarios and the associated formats based on market relevance for further evaluation.
4. Define concrete evaluation framework per scenario (test conditions, KPIs, Metrics, test sequences, agreed reference signals) based on the above prioritized reference scenarios, and evaluate the feasibility and performance of existing 3GPP codecs as well as potentially new codecs to support the scenarios.
5. Based on the findings in steps 1, 2, and 4 document (i) interoperability requirements, (ii) traffic characteristics and (iii) potential QoS optimizations or requirements, to support the above workflows and evaluate the feasibility of new formats with different services, considering the implementation constraints and performance indicators such as encoding, decoding, and rendering complexity, bandwidth utilization, and interoperability considerations.
6. Based on the findings in steps 1, 2, 4 and 5, identify potential gaps or deficiencies of existing 3GPP codecs, and offer recommendations to potentially extend 3GPP video specifications and capabilities.
7. Identify potential areas for normative work as the next phase and communicate with other 3GPP WGs regarding relevant aspects related to the study to the extent needed.]
Editor’s note: The scope may be updated as study progressed. |
27.007 | AT command set for User Equipment (UE) | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-j30.zip | The present document specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and network services from a Terminal Equipment (TE) through Terminal Adaptor (TA). The command prefix +C is reserved for Digital Cellular in ITU‑T Recommendation V.250 [14]. The present document has also the syntax details used to construct extended commands. Commands from ITU‑T Recommendation V.250 [14] and existing digital cellular standards (TIA IS‑99 [15] and TIA IS‑135 [16]) are used whenever applicable. Some of the new commands are defined such way that they can be easily applied to MT of other networks.
NOTE: The terms GSM and GSM/UMTS are used whenever appropriate for SIM/UICC GSM applications or GSM/UMTS bearer services or to represent specific mobile accesses covered by the present specification.
ITU‑T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12] fax AT commands may be used for GSM/UMTS fax transmission from TE. Short Message Service AT commands are defined in 3GPP TS 27.005 [24]. AT commands for packet systems are defined in clause 10 of this specification. The present document assumes an abstract architecture comprising a TE (e.g. a computer) and a MT interfaced by a TA (see figure 1). The span of control of the defined commands should allow handling of any physical implementation that this abstract architecture may lead to:
‑ TA, MT and TE as three separate entities;
‑ TA integrated under the MT cover, and the TE implemented as a separate entity;
‑ TA integrated under the TE cover, and the MT implemented as a separate entity; and
‑ TA and MT integrated under the TE cover as a single entity.
The commands described in the present document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the MT, not about the TA.
Figure 1: Setup
Interface between TE and TA is intended to operate over existing serial (ITU‑T Recommendation V.24) cables, infrared link, and all link types with similar behaviour. For correct operation many of the defined commands require eight bit data and therefore it is recommended that TE‑TA link is set to eight bits/ byte mode. (For infrared operation implementation, refer informative references IrDA. For embedding AT commands and data during on-line data state, refer TIA‑617/ITU-T V.80.) Interface between TA and MT is dependent on the interface in the MT.
The functional blocks shown in figure 1, using AT commands, shall follow the principles described in the interactions handling framework 3GPP TS 23.227 [63]. |
28.104 | Management and orchestration; Management Data Analytics (MDA) | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.104/28104-j20.zip | The present document specifies the MDA capabilities with corresponding analytics inputs and analytics outputs (reports), as well as processes and requirements for MDAS (Management Data Analytics Service), historical data handling for MDA, and ML support for MDA.
The present document also describes the MDA functionality and service framework, and MDA role in the management loop. |
28.105 | Management and orchestration; Artificial Intelligence/ Machine Learning (AI/ML) management | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.105/28105-j20.zip | The present document specifies the Artificial Intelligence / Machine Learning (AI/ML) management capabilities and services for 5GS where AI/ML is used, including management and orchestration (e.g., MDA, see 3GPP TS 28.104 [2]) and 5G networks (e.g. NWDAF, see 3GPP TS 23.288 [3]) and NG-RAN (see TS 38.300 [16] and TS 38.401 [17]). |
28.111 | Management and orchestration; Fault management (FM) | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.111/28111-j20.zip | The present document describes the SBMA based Fault Management service (see [14]). It includes stages 1, 2 and 3.
The present document of the Fault Management MnS is based on the SBMA principles using CRUD operations, modeled OAM data in the NRM together with fault management specific notifications. An IRP based solution for fault management is out of scope for the present document. |
28.201 | Charging management; Network slice performance and analytics charging in the 5G System (5GS); Stage 2 | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.201/28201-j10.zip | The present document is part of a series of documents that specify charging aspects of network slicing.
The present document includes the charging aspects of network slice performance and analytics, including charging scenarios, data and way of data transfer specific for the network slice.
The architecture for network slice charging follows common architecture and concepts specified in TS 32.240 [1].
The charging aspect of network slice charging on PDU session charging is specified in TS 32.255 [15].
The network slice performance and analytics charging collects and processes charging information related to performance metrics of a network slice.
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]. 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. |
28.202 | Charging management; Network slice management charging in the 5G System (5GS); Stage 2 | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.202/28202-j00.zip | The present document specifies the Converged Charging description for network slice management charging in the 5G System (5GS). The present document specifies the charging aspects for management of network slicing in mobile networks.
The following management operations are within the scope:
- Network Slice Instance creation, modification and termination;
- Network Slice Instance activation and deactivation. |
28.310 | Management and orchestration; Energy efficiency of 5G | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.310/28310-j10.zip | The present document specifies concepts, use cases, requirements and solutions for the energy efficiency assessment and optimization for energy saving of 5G networks. |
28.312 | Management and orchestration; Intent driven management services for mobile networks | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.312/28312-j20.zip | The present document specifies concept, use cases, requirements and solutions for the intent driven management for service or network management. |
28.313 | Management and orchestration; Self-Organizing Networks (SON) for 5G networks | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.313/28313-j20.zip | The present document specifies the concepts, use cases, requirements, and procedures for the SON functions in 5GS. |
28.314 | Management and orchestration; Plug and Connect; Concepts and requirements | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.314/28314-j00.zip | The present document specifies concepts, use cases and requirements for Plug and Connect NE in 3GPP systems. |
28.315 | Management and orchestration; Plug and Connect; Procedure flows | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.315/28315-j00.zip | The present document specifies procedure flows for Plug and Connect NE in 3GPP systems. |
28.317 | Management and orchestration;Self-configuration of Radio Access Network Entities (RAN NEs) | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.317/28317-j10.zip | The present document describes the functionality for RAN NE self-configuration and network configuration data handling to enable RAN NE self-establishment, as well as requirements need to be met to support this functionality. The concepts, use cases, requirements, procedure and management service definition for RAN NE self-configuration management and network configuration data handling of RAN NEs are specified in the present document.
The NE within virtualization is not in the scope of the present document. |
28.318 | Management and Orchestration; Network and services operations for energy utilities | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.318/28318-j10.zip | The present document provides normative specifications of Stage 1, stage 2, and stage 3 to realize network and service operations to support energy utility use cases by 5G networks.
The present document does not specify all aspects required to support network service operations for energy utilities. Annex D identifies unspecified configuration and functionality that are needed in order to complement the normative specification. This configuration and functionality that is not standardized has to be supported in order to deploy and operate the management services specified in the present document. |
28.319 | Management and orchestration; Access Control for Management services | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.319/28319-j00.zip | The present document specifies access control for management services. |
28.405 | Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration | TS | 19.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.405/28405-j30.zip | The present document addresses the mechanisms used for the function Quality of Experience (QoE) measurement collection in 3GPP networks . The measurements that are collected are DASH [6], MTSI [7] and Virtual Reality (VR) (see TS 26.118 [13]) measurements.
The function includes collecting QoE information from UEs frequenting a specified area or an individual UE for a specified end user service/end user service type. The document describes the activation and deactivation of a network request session, UE request session and recording session and also the reporting of recorded information [2]. |
28.530 | Management and orchestration; Concepts, use cases and requirements | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.530/28530-j00.zip | The present document specifies the concepts, use cases and requirements for management of network slicing in mobile networks. The 3GPP management system directly manages only the parts of the network that consist of network functions specified in 3GPP (e.g. 5G RAN, 5G CN and IMS). For the network functions specified by other SDOs, the management impact of network slicing is addressed as required. For example, regarding the Transport Network (TN) part supporting connectivity within and between CN and RAN parts, 3GPP management system may provide link requirements (e.g. topology, QOS parameters) to the TN management system. |
28.531 | Management and orchestration; Provisioning | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.531/28531-j10.zip | The present document specifies use cases, requirements, management services and procedures for provisioning of 5G networks. For the cases when a NF taking part in these networks contains virtualized parts, interactions with ETSI NFV MANO system are described. |
28.532 | Management and orchestration; Generic management services | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-j10.zip | The present document specifies the stage 2 and stage 3 of generic management services for mobile network. |
28.533 | Management and orchestration; Architecture framework | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.533/28533-j20.zip | The present document defines the network management and orchestration architecture SBMA for 3GPP networks including network slicing. The use cases and requirements are specified in TS 28.530 [3].
SBMA applies to 5G. |
28.536 | Management and orchestration; Management services for communication service assurance; Stage 2 and stage 3 | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.536/28536-j10.zip | The present document describes the management services for communication service assurance and specifies stage 2 and stage 3 for closed control loop communication service assurance solution that adjusts and optimizes the services provided by NG-RAN and 5GC. |
28.537 | Management and orchestration; Management capabilities | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.537/28537-j20.zip | The present document specifies use cases, requirements and procedures for management capabilities of 5G networks. |
28.538 | Management and orchestration; Edge Computing Management | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.538/28538-j40.zip | The present document specifies the management aspects of edge computing including concepts, use cases, requirements and procedural flows that covers lifecycle management, provisioning, performance assurance and fault supervision for edge computing. |
28.540 | Management and orchestration; 5G Network Resource Model (NRM); Stage 1 | TS | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.540/28540-j10.zip | The present document specifies the requirements for the Network Resource Model (NRM) definition of NR, NG-RAN, 5G Core Network (5GC) and network slice, to support the management for:
- variety of 5G radio access network functions and features, covering management for NR connectivity options defined in 3GPP TS 37.340 [5] and NG-RAN architectural options defined in 3GPP TS 38.401 [4].
- variety of 5GC network functions and features defined in 3GPP TS 23.501 [2].
- network slice and network slice subnet. |
28.541 | Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.541/28541-j40.zip | The present document specifies the Information Model and Solution Set for the Network Resource Model (NRM) definitions of NR, NG-RAN, 5G Core Network (5GC) and network slice, to fulfil the requirements identified in TS 28.540 [10].
The Information Model defines the semantics and behaviour of information object class attributes and relations visible on the management interfaces in a protocol and technology neutral way. And Solution Set defines one or more solution set(s) with specific protocol(s) according to the Information Model definitions. |
28.550 | Management and orchestration; Performance assurance | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.550/28550-j00.zip | The present document specifies the stage 1, 2 and 3 of performance assurance related management services for 5G networks including network slicing.
The present document does not specify the performance data, i.e. performance measurements, Key Performance Indicators (KPIs). |
28.552 | Management and orchestration; 5G performance measurements | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.552/28552-j40.zip | This document specifies the performance measurements for 5G networks including network slicing. Performance measurements for NG-RAN are defined in this document (clause 5.1), and some L2 measurement definitions are inherited from TS 38.314 [29]. The performance measurements for 5GC are all defined in this document (clause 5.2 to 5.6). Related KPIs are defined to those measurements are defined in TS 28.554 [8].
The performance measurements for NG-RAN applies also to EN-DC described in TS 37.340 [60] in many cases, but not to the RRC connection related measurements which are handled by E-UTRAN for EN-DC (those are measured according to TS 32.425 [9] and related KPIs in TS 32.451 [10]).
The performance measurements are defined based on the measurement template as described in TS 32.404 [3]. |
28.554 | Management and orchestration; 5G end to end Key Performance Indicators (KPI) | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.554/28554-j40.zip | The present document specifies end-to-end Key Performance Indicators (KPIs) for the 5G network and network slicing. |
28.558 | Management and orchestration; UE level measurements for 5G system | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.558/28558-j40.zip | The present document specifies the UE level measurements for 5G system, and the corresponding collection and reporting mechanisms. |
28.560 | Management and orchestration; Signalling traffic monitoring management (Stage 1, stage 2, and stage 3) | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.560/28560-j20.zip | The present document specifies the definitions of signalling traffic monitoring management. This monitoring is performed at network signalling level on 5GC control plane. When the monitoring is enabled, the 5GC network function collects the required decrypted signalling message and forwards it to the configured collection entity. |
28.561 | Management and orchestration; Management aspects of Network Digital Twins | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.561/28561-100.zip | The present document specifies the terms and concepts of Network Digital Twin, as well as the use cases, requirements, and solutions for Network Digital Twins within the 3GPP management system.
The present document applies to the service based management architecture. |
28.567 | Management and orchestration; Management Aspects of Closed Control Loops | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.567/28567-030.zip | |
28.572 | Management and orchestration; Management of planned configurations | TS | 0.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.572/28572-050.zip | The present document … |
28.579 | Management and orchestration; Management services exposure to external consumers through CAPIF | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.579/28579-100.zip | The present document specifies use cases, requirements and solutions for exposing management services to external consumers through the CAPIF. |
28.620 | Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) | TS | 19.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.620/28620-j20.zip | As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed [6], [14]. These use cases led to the recognition that it would be necessary to define common model elements applicable for wire-line and wireless networks. This document defines these common model elements. |
28.622 | Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.622/28622-j40.zip | The present document specifies the Generic network resource information that can be communicated between an MnS producer and MnS consumer for telecommunication network management purposes, including management of converged networks and networks that include virtualized network functions.
This document specifies the semantics of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
This document supports the Federated Network Information Model (FNIM) concept described in TS 32.107 [8] in that the relevant Information Object Class (IOC)s defined in this specification are directly or indirectly inherited from those specified in the Umbrella Information Model (UIM) of TS 28.620 [9].
Note that the present document is applicable to deployment scenarios using the Service Based Management Architecture (SBMA) as defined in TS 28.533 [32]. For deployment scenarios using the IRP framework as defined in TS 32.102 [2] the latest Rel-14 version of TS 28.622 is applicable. |
28.623 | Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 19.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.623/28623-j40.zip | This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the Solution Set definition for the Generic NRM IRP.
The Solution Set definition is related to 3GPP TS 28.622 [4].
Note that the present document is applicable to deployment scenarios using the Service Based Management Architecture (SBMA) as defined in TS 28.533 [20]. For deployment scenarios using the IRP framework the latest Rel-14 version of TS 28.623 is applicable. |
28.657 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.657/28657-j00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the E‑UTRAN and ng-eNB Network Resource Model (NRM). |
28.658 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.658/28658-j00.zip | The present document specifies the E-UTRAN network resource information that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral E-UTRAN NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines E-UTRAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document.
The present document also specifies the ng-eNB network resource information that can be communicated among NG-RAN management system, including management of MR-DC operations which ng-eNB is involved in. |
28.659 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.659/28659-j00.zip | The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the E-UTRAN NRM IRP, see 3GPP TS 28.658 [4]. |
28.662 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.662/28662-j00.zip | The present document specifies the Generic Radio Access Network (RAN) network resource model (NRM) that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [5]). However, which Interface IRP is applicable is outside the scope of the present document. |
28.708 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.708/28708-j00.zip | The present document specifies Evolved Packet Core (EPC) network resource information that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks. . It reuses relevant parts of the Generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines EPC specific Information Object Classes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document. |
28.709 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.709/28709-j00.zip | The present document specifies the Solution Sets for the EPC NRM IRP.
The Solution Set definition is related to 3GPP TS 28.708 [3]. |
28.846 | Study on charging aspects of satellite access phase 3 | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.846/28846-j10.zip | The present document studies on charging aspects of satellite access Phase 3 based on the TS 22.261 [2] and TR 23.700-29 [3]:
This study item is to investigate the following aspects of the satellite access:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements based on business scenarios;
- Identify the potential charging solutions. |
28.849 | Study on charging aspects of Common API Framework for Northbound APIs (CAPIF) phase 2 | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.849/28849-j10.zip | The present document focus on how CAPIF can be supported by the current Converged charging Architecture.
The following items are studied:
- possible charging scenarios and requirements for supporting CAPIF.
- identify NEF functionalities which can implement CAPIF functionalities for charging scenarios
- potential charging solutions for supporting CAPIF. |
28.851 | Study on charging aspects of next generation real time communication services phase 2 | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.851/28851-j10.zip | The present document studies the charging aspects for enhanced support of next generation real time communication services phase 2 on the TS 23.501 [2], TS 23.502 [3], TS 23.503 [4], TS 23.228 [5], TS 22.011 [6], TS 22.156 [7] and TS 26.114 [8] incorporating conclusions from TR 23.700-77 [9].
The following is studied:
- Identify charging scenarios and potential charging requirements to support the following aspects of IMS network capabilities exposure, standalone IMS data channel, avatar communication, services over IMS data channel as a part of 3GPP PS Data Off Exempt Services, and IMS data channel applications download.
- Investigate the potential solutions to support the above charging scenarios and charging requirements. |
28.853 | Study on charging aspects of uncrewed aerial systems | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.853/28853-j10.zip | The present document studies the charging aspects for the support of uncrewed aerial systems based on the TS 22.125 [2], TS 23.256 [3], TS 23.501 [4], TS 23.502 [5] and TS 23.503 [6].
The following is studied:
- Identify charging scenarios and requirements for supporting uncrewed aerial systems.
- Evaluate the potential solutions to support the above charging scenarios and charging requirements. |
28.858 | Study on Artificial Intelligence / Machine Learning (AI/ML) management phase 2 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.858/28858-j00.zip | The present document studies the enhanced Artificial Intelligence / Machine Learning (AI/ML) management capabilities and services building on the work of Rel-18, as well as new management aspects related to AI/ML functionalities across various 3GPP working groups within 5GS. It focuses particularly on the management of AI/ML-enabled features utilized in management and orchestration, 5GC, and NG-RAN. Furthermore, the study also investigates the AI/ML management capabilities supporting the emerging AI/ML technologies (e.g. Federated Learning, Reinforcement Learning, Pre-training, Fine-tuning and Distributed training) and the sustainability and trustworthiness of AI/ML in 5G system. |
28.866 | Study on Management Data Analytics (MDA) – Phase 3 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.866/28866-j00.zip | The present document investigates new capabilities and improvements to the Management Data Analytics (MDA) which are defined in TS 28.104 [2]. |
28.867 | Study on closed control loop management | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.867/28867-j00.zip | The present document will study closed control loop management. |
28.869 | Study on Cloud Aspects of Management and Orchestration | TR | 1.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.869/28869-150.zip | The present document studies cloud aspects of management and orchestration of the 5GS; specifically, use of ETSI VNF generic OAM functions [2], use of industry solutions including ETSI NFV MANO, open source and other solutions for management (including life cycle management and other management aspects) of cloud native network functions, and support of different cloud deployment scenarios. |
28.870 | Study on Enablers for Security Monitoring | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.870/28870-j00.zip | The present document presents a study on enablers for security monitoring |
28.871 | Study on Service Based Management Architecture enhancement phase 3 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.871/28871-j00.zip | The present document describes use cases, potential requirements, and solutions for the enhancement of the Service-Based Management Architecture (SBMA). The present document provides conclusions and recommendations on the next steps in the standardization. |
28.872 | Study on Management of planned configurations | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.872/28872-j00.zip | The present document contains a study on the management of planned configurations. |
28.873 | Study on data management, subscriptions and reporting | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.873/28873-j10.zip | The present document investigates how unique "job reference id" (e.g. Trace Reference, QoE Reference, Job Id) can be unique within a 3GPP system and whether it is possible to decrease the load in the NFs when there are several consumers asking for the same data within a PLMN.
The study is done for SBMA. |
28.874 | Study on Management Aspects of NTN Phase 2 | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.874/28874-j10.zip | The present document studies the management aspects of NTN in R19. It mainly investigates use cases, potential requirements and potential solutions of NTN management. |
28.875 | Study on management of IAB nodes | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.875/28875-j00.zip | The present document studies the use cases and identifies the potential requirements and solutions for the management of IAB nodes for 5G. |
28.876 | Study on management aspect of RedCap feature | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.876/28876-j00.zip | The present document describes use cases, potential requirements, and solutions for the management aspects of RedCap feature. |
28.877 | Study on Enhancement of the management aspects related to Network Data Analytics Functions (NWDAF) Phase 2 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.877/28877-j00.zip | The present document records the 2nd phase of the study on the management enhancement for NWDAF (Network Data Analytics Function).
In the present document, the use cases, requirements and potential solutions on two major aspects of management enhancement related to the NWDAF are studied. The 1st aspect is the management enhancement supporting NWDAF Roaming Exchange Capability in a roaming scenario, so that the operator can configure the NWDAF with this capability and monitor the performance related. The 2nd aspect is on the management enhancements related to NWDAF data collection, including monitoring the amount of data collected and the efficiency of the NWDAF data collection.
The present document also provides recommendations for the normative specifications work. |
28.878 | Study on Management of Network Sharing Phase3 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.878/28878-j00.zip | The present document study the management of network sharing including Trace job and collection requirements for POPs, some issues related Rel-18, such as enhancements for SBMA based MOCN scenario, scenario related to access rights on CRUD operation of MOCN management data, and potential enhancements for Indirect Network Sharing scenarios. |
28.879 | Study on OAM for service management and exposure to external consumers | TR | 19.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.879/28879-j10.zip | The present document identifies potential use cases and requirements for a generic approach for exposure of management services to external consumers. It documents and evaluates potential solutions and provides recommendations for the normative work. |
28.880 | Study on energy efficiency and energy saving aspects of 5G networks and services | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.880/28880-j00.zip | The present document investigates the opportunities for defining new energy related information, new Energy Consumption (EC) KPIs, new Energy Efficiency (EE) KPIs and new Energy Saving (ES) solutions for 5G. It identifies and documents use cases and requirements related to energy related information (e.g. carbon emission, carbon emission efficiency, renewable energy factor), energy consumption, energy efficiency and energy saving. It documents and evaluates potential solutions, and provides recommendations for the normative work. |
28.914 | Study on intent driven management service for mobile network phase 3 | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.914/28914-j00.zip | The present document investigates new areas for enhancing the intent driven management services for mobile networks. |
28.915 | Study on management aspect of Network Digital Twin | TR | 19.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.915/28915-j00.zip | The present document will study scenarios which use NDT. For these scenarios, the study will identify issues, potential requirements and potential solutions, based on which the recommendations can be provided. |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-j00.zip | The present document defines the requirements for Packet Domain interworking between a:
a) PLMN and PDN;
b) PLMN and PLMN.
The present document is valid for a PLMN in A/Gb mode as well as for a PLMN in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note, that the A interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
For inter-working between EPC PLMN and external networks, the present document is valid for both 3GPP accesses and non-3GPP accesses.
The present document also defines, in clause 17, the protocol for the Gmb interface, in clause 20, the protocol for the SGmb interface, and in clause 19, the protocol for the Mz interface.
The present document also defines, in clause 18, the usage of Radius at the Pk Reference Point between the GGSN and the Presence Network Agent.
The term "Packet Domain" includes both EPC based and non-EPC based Packet Domains.
The present document also defines the specific requirements for rate control related to CIoT optimisations. |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-j00.zip | The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic. CAP is based on a sub-set of the ETSI Core INAP CS-2 as specified by ETSI EN 301 140‑1 [26]. Descriptions and definitions provided by ETSI EN 301 140‑1 [26] are directly referenced by this standard in the case no additions or clarifications are needed for the use in the CAP. |
29.118 | Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification | TS | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.118/29118-j10.zip | CS Fallback in the Evolved Packet System (EPS) enables the provisioning of CS-domain services (e.g. voice call, Location Services (LCS) or supplementary services) by reuse of CS infrastructure when the UE is served by E-UTRAN. Additionally, SMS delivery via the CS core network is realized without CS fallback.
The present document specifies the procedures and the SGs Application Part (SGsAP) messages used on the SGs interface between the Mobility Management Entity (MME) in the EPS and the Visitor Location Register (VLR), to allow location management coordination and to relay certain messages related to GSM circuit switched services over the EPS system.
The present document also specifies the use of Stream Control Transmission Protocol (SCTP) for the transport of SGsAP messages.
The present document is applicable to the MME in the EPS and to the VLR. The functional split between the MME and the VLR is defined in 3GPP TS 23.272 [7]. |
29.122 | T8 reference point for Northbound APIs | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/29122-j30.zip | The present specification describes the protocol for the T8 reference point between the SCEF and the SCS/AS. The T8 reference point and the related stage 2 functional requirements are defined in 3GPP TS 23.682 [2]. |
29.128 | Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.128/29128-j10.zip | The present document describes the Diameter-based interfaces between the SCEF/IWK-SCEF and other network entities such as MME/SGSN for the Architecture enhancements to facilitate communications with packet data networks and applications.
In particular, this document specifies the T6a interface between the MME and the SCEF, the T6ai interface between the MME and the IWK-SCEF, the T6b interface between the SGSN and the SCEF, the T6bi interface between the SGSN and the IWK-SCEF and the T7 interface between the SCEF and the IWK-SCEF. The procedures over those interfaces are defined in 3GPP TS 23.682 [2]. |
29.162 | Interworking between the IM CN subsystem and IP networks | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.162/29162-j00.zip | The IM CN subsystem interworks with the external IP networks through the Mb reference point.
This document details the interworking between the IM CN subsystem and external IP networks for IM service support. It addresses the issues of control plane interworking and, user plane interworking for specific interworking use cases. Clause 10 describes the IMS-Ix interface requirements in the form of Use Cases which require H.248 protocol procedures. Subclause 10.4 then details the additional Information Elements required to perform the specific procedures.
The IP version Interworking, between IP version 4 (IETF RFC 791 [9] ) and IP version 6 (IETF RFC 2460 [10] ) detailed in terms of the processes and protocol mappings required in order to support both IMS originated and terminated calls. |
29.163 | Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.163/29163-j00.zip | The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls.
The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice and multimedia calls.
Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information.
The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229 [9]) and BICC or ISUP, as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30] and ITU-T Q761 to Q764 [4] respectively.
The present document also specifies the interworking between circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] 3GPP TS 26.111 [79], and ITU-T Recommendation H.324 [81] and packet switched multimedia services, as described in 3GPP TS 26.114 [104], in particular and the interworking between the 3GPP profile of SIP and the inband control protocols for multimedia communication as specified in ITU-T Recommendations H.245 [82] and H.324 Annex K [81].
The present document addresses two interworking scenarios with respect to the properties of the CS network:
- The CS network does not use any 3GPP specific additions.
- The CS network uses 3GPP specific additions. |
29.164 | Interworking between the 3GPP CS domain with BICC or ISUP as signalling protocol and external SIP-I networks | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.164/29164-j00.zip | The present document defines interworking procedures between a 3GPP CS domain (see 3GPP TS 23.205 [2]) which applies either BICC or ISUP as signalling protocol, and external networks that use SIP-I (see ITU-T Q.1912.5 [20], Profile C) as signalling protocol. The document also describes the related interworking architecture. The control plane interworking is performed by an interworking unit at the interconnection between the 3GPP CS domain and an external SIP-I network. The user plane interworking is performed by an MGW. The present document defines stage 2 procedures for the control of the MGW.
The present specification reuses existing interworking procedures of 3GPP TS 29.163 [4] and ITU-T Q.1912.5 [20], Profile C, as far as possible. |
29.165 | Inter-IMS Network to Network Interface (NNI) | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.165/29165-j00.zip | The objective of this document is to address the Inter-IMS Network to Network Interface (II-NNI) consisting of Ici and Izi reference points between IMS networks in order to support end-to-end service interoperability.
The present document addresses the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP header fields) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications. A profiling of the Inter-IMS Network to Network Interface (II-NNI) is also provided.
Charging aspects are addressed as far as SIP signalling is concerned.
IMS emergency session establishment between IMS networks is addressed as far as SIP signalling is concerned.
SIP signalling traversing the NNI between a CSCF and MRB, e.g. for media control or Voice Interworking with Enterprise IP-PBX, and SIP signalling traversing the NNI on the Mr interface between the CSCF and the MRFC, or on the Mr' interface between the AS and MRFC, or on the Rc interface between AS and MRB is not considered in the present release of this specification.
SIP signalling traversing the NNI between an application server and the remaining IMS functional entities (e.g. for MCPTT interface SIP-2 in figure 7.3.1-2 in 3GPP TS 23.280 [200]) is not considered in the present release of this specification.
SIP signalling traversing the NNI between an ISC gateway and an AS in an enterprise network, e.g. for media control and voice interworking with enterprise IP-PBX, on the ISC interface between the ISC gateway and the enterprise network is not considered in the present release of this specification. |
29.175 | IP Multimedia Subsystem (IMS) Application Server (AS) Services Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.175/29175-j20.zip | The present document specifies the stage 3 protocol and data model for the Nimsas Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the IMS AS.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2] and TS 23.502 [3].
The IP Multimedia Subsystem (IMS) supporting DC architecture and procedures are specified in TS 23.228 [14].
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.176 | IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.176/29176-j20.zip | The present document specifies the stage 3 protocol and data model for the Nmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Media Function (MF).
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) Data Channel (DC) architecture and procedures are specified in annex AC of 3GPP TS 23.228 [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.213 | Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.213/29213-j10.zip | The present specification adds detailed flows of Policy and Charging Control (PCC) over the Diameter-based Rx, Gx, Gxx, Sd, Sy, S9, Nt, Diameter-based St and Np reference points and their relationship with the bearer level signalling flows over the Gn/Gp, S4, S5/S8, S2a and S2c interfaces.
The calls flows depicted in this Technical Specification represent usual cases, i.e. not all situations are covered. Detailed information provided in 3GPP TS 29.212 [9], 3GPP TS 29.214 [10], 3GPP TS 29.215 [22], 3GPP TS 29.217 [36] , 3GPP TS 29.154 [56] and 3GPP TS 29.219 [28] shall be taken into consideration.
The present specification also describes the PCC reference architectures for non-roaming and roaming scenarios.
The present specification also describes the binding and the mapping of QoS parameters among SDP, UMTS QoS parameters, and QoS authorization parameters.
The present specification also describes the PCRF addressing using DRA.
The present specification also describes Diameter race condition handling for Gx based applications, i.e Gx, Gxx, Sd and S9. |
29.214 | Policy and charging control over Rx reference point | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.214/29214-j10.zip | The present document provides the stage 3 specification of the Rx reference point for the present release. The functional requirements and the stage 2 specifications of the Rx reference point are contained in 3GPP TS 23.203 [2].
The Rx reference point lies between the Application Function (AF) and the Policy and Charging Rule Function (PCRF). In the 5GS the Rx reference point resides between the AF and the Policy Control Function (PCF) as specified in 3GPP TS 23.501 [55] and 3GPP TS 23.503 [56].
NOTE: Interactions between the PCF and the AF using the 5GS Npcf_PolicyAuthorization service (the N5 reference point) are defined in 3GPP TS 29.514 [57].
The Rx interface which is based on RESTful HTTP and XML is specified in 3GPP TS 29.201 [37].
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. |
29.222 | Common API Framework for 3GPP Northbound APIs | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.222/29222-j30.zip | The present specification describes the protocol for the Common API Framework (CAPIF) for 3GPP Northbound APIs. The CAPIF and the related stage 2 architecture and functional requirements are defined in 3GPP TS 23.222 [2]. |
29.228 | IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.228/29228-j10.zip | This 3GPP Technical Specification (TS) specifies:
1. The interactions between the HSS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface.
2. The interactions between the CSCF and the SLF (Server Locator Function), referred to as the Dx interface.
3. The interactions between the SIP Core and the SIP database, referred to as the Cx interface, for the Mission Critical Services, where this interface is named as AAA-1, as described in 3GPP TS 23.280 [30].
NOTE: In the 3GPP TS 23.280 [30] the term SIP database is used for the HSS and the term SIP Core is used for the P-CSCF, the I-CSCF and the S-CSCF when compared to this specification.
The IP Multimedia (IM) Subsystem stage 2 is specified in 3GPP TS 23.228 [1] and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3GPP TS 24.228 [2].
This document addresses the signalling flows for Cx and Dx interfaces.
This document also addresses how the functionality of Px interface is accomplished.
The Presence Service Stage 2 description (architecture and functional solution) is specified in 3GPP TS 23.141 [10]. |
29.230 | Diameter applications; 3GPP specific codes and identifiers | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.230/29230-j20.zip | The present document lists the 3GPP specific Diameter protocol codes, including the AVP codes and Experimental result codes.
This document lists also the application identifiers assigned to 3GPP specific Diameter applications by IANA and the Diameter command code range which is assigned to 3GPP by IANA. |
29.231 | Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.231/29231-j00.zip | The present document describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see 3GPP TS 23.231 [1]. The SIP-I protocol operates between (G)MSC servers. The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.231 [1] and TS 23.153 [2].
Interworking of SIP-I on Nc to external networks is described by TS 29.235 [3].
The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later. |
29.244 | Interface between the Control Plane and the User Plane nodes | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.244/29244-j20.zip | The present document specifies the Packet Forwarding Control Protocol (PFCP) used on the interface between the control plane and the user plane function.
PFCP shall be used over:
- the Sxa, Sxb, Sxc and the combined Sxa/Sxb reference points specified in 3GPP TS 23.214 [2].
- the Sxa' and Sxb' reference points specified in 3GPP TS 33.107 [20]. In the rest of this specification, no difference is made between Sxa and Sxa', or between Sxb and Sxb'. The Sxa' and Sxb' reference points reuse the protocol specified for the Sxa and Sxb reference points, but comply in addition with the security requirements specified in clause 8 of 3GPP 33.107 [20].
- the N4 interface specified in 3GPP TS 23.501 [28] and 3GPP TS 23.502 [29].
- the N4mb interface specified in 3GPP TS 23.247 [72].
In this specification the term CP function applies to control plane nodes such as SGW-C, PGW-C, TDF-C, SMF and MB-SMF.
In this specification the term UP function applies to user plane nodes such as SGW-U, PGW-U, TDF-U, UPF and MB-UPF.
The prefix PFCP in message and procedure names is used to indicate that messages and procedures are common and used on Sx, N4 and N4mb reference points. A PFCP session refers to both Sx and/or N4 sessions, or to an N4mb session. A PFCP association is established between a CP function and a UP function, i.e., for EPC, between an SGW-C/PGW-C/TDF-C and an SGW-U/PGW-U/TDF-U, and for 5GC, between an SMF and a UPF or between an MB-SMF and MB-UPF.
In the related stage 2 specifications the prefix Sx, N4 and N4mb is used for these common procedures realised by PFCP.
Clauses or paragraphs that only apply to EPC or 5GC are indicated by the label "for EPC" or "for 5GC". |
29.255 | Uncrewed Aerial System Service Supplier (USS) Services; Stage 3 | TS | 19.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.255/29255-j10.zip | The present document specifies the stage 3 protocol and data model for the UAS-specific Naf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UAS-specific AF.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2], TS 23.502 [3], and TS 23.256 [14].
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.122 [16].
The UAS Service Supplier (USS) provides the UAS-specific AF services to NF service consumers (e.g. NEF (UAS-NF)). The USS is functionality within the AF. |
29.256 | Uncrewed Aerial Systems Network Function (UAS-NF); Aerial Management Services; Stage 3 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.256/29256-j20.zip | The present document specifies the stage 3 protocol and data model for the UAS-NF functionality of the Nnef Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NEF (UAS-NF).
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 Uncrewed Aerial System Network Function (UAS-NF) provides the UAS-specific NEF services to NF service consumers (e.g. AMF, SMF). The UAS-NF is functionality within the NEF. |
29.257 | Application layer support for Uncrewed Aerial System (UAS); UAS Application Enabler (UAE) Server Services; Stage 3 | TS | 19.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.257/29257-j30.zip | The present document specifies the stage 3 Protocol and data model for the UAS Application Enabler (UAE) Server services, for enabling the support of Uncrewed Aerial System (UAS) applications over 3GPP networks. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UAE Server.
The stage 2 application layer architecture for Uncrewed Aerial System (UAS), functional requirements, procedures and information flows necessary for enabling Uncrewed Aerial System (UAS) applications over 3GPP networks are specified in 3GPP TS 23.255 [6].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [2]. |
29.272 | Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.272/29272-j20.zip | The present document describes the Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related diameter-based interfaces towards the Home Subscriber Server (HSS) or the CSG Subscriber Server (CSS), and the MME and the SGSN related diameter-based interface towards the Equipment Identity Register (EIR).
This specification defines the Diameter application for the MME-HSS, S6a reference point, for the MME-CSS, S7a reference point, for the SGSN-HSS, S6d reference point, and for the SGSN-CSS, S7d reference point. The interactions between the HSS/CSS and the MME/SGSN are specified, including the signalling flows.
This specification defines the Diameter application for the MME-EIR, S13 reference point, and for the SGSN-EIR, S13' reference point. The interactions between the MME/SGSN and the EIR are specified, including the signalling flows.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which at least supports the S4 interface and may support Gn and Gp interfaces.
- "S4-SGSN" refers to an SGSN which supports the S4 interface and does not support Gn and Gp interfaces.
- Gn/Gp-SGSN refers to an SGSN which supports the Gn and Gp interfaces and does not support S4 interface.
- "GPRS subscription data" refers to the parameters in the HLR column in Table 5.2. in 3GPP TS 23.008 [30].
- "EPS subscription data" refers to the parameters in the HSS column in Table 5.2A-1 in 3GPP TS 23.008 [30].
The Evolved Packet System stage 2 description (architecture and functional solutions) is specified in 3GPP TS 23.401 [2] and in 3GPP TS 23.060 [12].
SGSN CAMEL Subscription Data are not supported over S6d interface. |
29.273 | Evolved Packet System (EPS); 3GPP EPS AAA interfaces | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.273/29273-j10.zip | The present document defines the stage-3 protocol description for several reference points for the non-3GPP access in EPS:
- The SWa reference point between an un-trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
- The STa reference point between a trusted non-3GPP IP access and the 3GPP AAA Server/Proxy.
- The SWd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
- The SWx reference point between the 3GPP AAA Server and the HSS.
- The S6b reference point between the 3GPP AAA Server/Proxy and the PDN GW.
- The SWm reference point between the 3GPP AAA Server/Proxy and the ePDG.
- The reference point between the 3GPP AAA Server/Proxy and the EIR.
The present document also defines the stage 3 protocol description for the following reference points defined for Non-seamless WLAN offload in 5GS:
- the SWa' reference point between a non-3GPP WLAN access, possibly via a 3GPP AAA Proxy, and the NSWO NF; and
- the SWd' reference point between the 3GPP AAA Proxy, possibly via an intermediate 3GPP AAA Proxy, and the NSWO NF. |
29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.274/29274-j30.zip | The present document specifies the stage 3 of the control plane of the GPRS Tunnelling Protocol, Version 2 (GTPv2-C).
GTPv2-C shall be used over:
- the S2a, S2b, S3, S4, S5, S8, S10, S11, S16, Sm and Sn signalling interfaces in EPC, specified in 3GPP TS 23.401 [3] and 3GPP TS 23.402 [45].
- the N26 signalling interface between EPC and 5GC, specified in 3GPP TS 23.501 [82] and 3GPP TS 23.502 [83].
GTPv2-C based protocols shall also be used over the Sv (see 3GPP TS 29.280 [15]) and S101/S121 (see 3GPP TS 29.276 [14]) interfaces.
In this document, unless otherwise specified, the S2a, S2b, S5 and S8 interfaces refer to the GTP-based S2a, S2b, S5 and S8 interfaces respectively.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
29.281 | General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.281/29281-j10.zip | The present document defines the user plane of GTP used on:
- the Gn and Gp interfaces of the General Packet Radio Service (GPRS);
- the Iu, Gn and Gp interfaces of the UMTS system;
- the S1-U, S11-U, S2a, S2b, X2, S4, S5, S8, S12, M1 and Sn interfaces of the Evolved Packet System (EPS);
- the F1-U, Xn, W1-U, N3, N9, N19, N3mb and N19mb interfaces of the 5G System (5GS).
This definition ensures full backwards compatibility with RNC, SGSN and GGSN implementations according to release 7 of 3GPP TS 29.060 [6].
NOTE: Releases previous to Release-8 have used 3GPP TS 29.060 [6] as normative definition of the user plane of GTP. This shall be considered when essential corrections are included in the present document or in pre-release-8 version of 3GPP TS 29.060 [6].
Fallback from GTPv1-U to GTPv0-U shall not be supported. Therefore, 3GPP Rel-8 and onwards GTPv1-U entity should not listen to the well-known GTPv0 port 3386. If GTPv1 entity listens to the GTPv0 port, the entity shall silently discard any received GTPv0-U message. |
29.328 | IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.328/29328-j00.zip | This 3GPP Technical Specification (TS) specifies:
1. The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point.
2. The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS and the SLF. This interface is referred to as the Dh reference point.
The IP Multimedia (IM) Core Network Subsystem stage 2 is specified in 3GPP TS 23.228 [1] and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3GPP TS 24.228 [2].
The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in 3GPP TS 23.218 [4].
This document addresses the signalling flows and message contents for the protocol at the Sh and Dh interface.
This document also addresses how the functionality of Ph interface is accomplished.
The Presence Service Stage 2 description (architecture and functional solution) is specified in 3GPP TS 23.141 [18]. |
29.336 | Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.336/29336-j10.zip | The present document describes the Diameter-based interfaces between the HSS and other network elements involved in the architecture for interworking with packet data networks and applications, such as Machine-Type Communications (MTC).
In particular, this document specifies the S6m interface between the Home Subscriber Server (HSS) and the MTC Interworking Function (MTC-IWF), the S6n interface between the HSS and the MTC-AAA and the S6t interface between the HSS and the Service Capability Exposure Function (SCEF). The procedures over those interfaces are defined in 3GPP TS 23.682 [2]. |
29.338 | Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs) | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.338/29338-j20.zip | The present document defines the Diameter-based interfaces specific to SMS when they are used in conjunction with the "SMS in MME" architecture specified in 3GPP TS 23.272 [2] or for SGSN supporting EPS interfaces, or the" SMS in 5GS" architecture specified in 3GPP TS 23.501 [21]. It comprises:
- the Diameter application for the S6c interface between the HSS/UDM and the central SMS functions (SMS-GMSC, SMS Router) ;
- the Diameter application
- for the SGd interface between the MME/SMSF, the SMS-IWMSC, the SMS-GMSC and the SMS Router.
- for the Gdd interface between the SGSN, the SMS-IWMSC, the SMS-GMSC and the SMS Router.
For the purpose of supporting SMS in 5GS, the UDM may implement the requirements specified in the present specification for HSS, with the following modification:
- "HSS" is to be replaced with "UDM". |
29.364 | IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability | TS | 19.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.364/29364-j10.zip | This specification standardizes
- the structure and the coding of the service data that are transported over the Sh interface between an Application Server supporting Multimedia Telephony supplementary services as defined in 3GPPP TS 22.173 [1] and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses an XML format and supports the full set of MMTEL Services.
- the structure and the coding of a set of generic IMS user group data over the Sh interface.
- the structure and the coding of the service data (ODB Information for IMS Oriented Services) that are transported over the Sh interface between an Application Server supporting services that are subject to IMS-ODB as defined in 3GPP TS 22.041[25] and the HSS.
- the structure and the coding of the IMS CAMEL subscription data transported using Sh interface. |
29.369 | 5G System; Ambient IoT Data Management (ADM) Services, Stage 3 | TS | 0.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.369/29369-020.zip | The present document specifies the stage 3 protocol and data model for the Nadm Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the ADM.
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.369[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]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.