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
|
|---|---|---|---|---|---|---|
32.446 | Telecommunication management; Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.446/32446-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Trace Management IRP: Information Service (3GPP TS 32.442 [5]). This specification is applicable to UMTS networks and EPS networks. GSM Trace is outside of the scope of this specification.
The conditions for supporting Network Sharing are stated in 3GPP TS 32.441 [6].
This Solution Set specification is related to 3GPP TS 32.442 V14. 0.X [6]. |
32.450 | Telecommunication management; Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN): Definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.450/32450-i00.zip | The present document specifies definitions of Key Performance Indicators (KPIs) for E-UTRAN. |
32.451 | Telecommunication management; Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.451/32451-i00.zip | The present document specifies requirements (business level requirements, specification level requirements and use case descriptions) related to Key Performance Indicators (KPIs) for E-UTRAN. |
32.452 | Telecommunication management; Performance Management (PM); Performance measurements Home Node B (HNB) Subsystem (HNS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.452/32452-i00.zip | The present document describes the measurements for Home Node B subsystem (HNS).
HNS [3] is consists of a HNB and HNB-GW. And, it appears as an RNS to the core network and is connected by means of the Iu-CS interface to the MSC and by means of the Iu-PS interface to the SGSN.
TS 32.401 [4] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a HNS.
Only measurement types that are specific to HNS are defined within the present documents. Vendor specific measurement types used in HNS are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to HNB and HNB GW);
- Header 2: Measurement function (e.g. HNB registration measurements);
- Header 3: Measurements. |
32.453 | Telecommunication management; Performance Management (PM); Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.453/32453-i00.zip | The present document describes the measurements for Home enhanced Node B Subsystem (HeNS).
HeNS [3] is consists of a HeNB and optionally a HeNB GW. And, it is connected by means of the standard S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME interface and to the Serving Gateway (S-GW) by means of the S1-U interface
TS 32.401 [4] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of HeNS.
Only measurement types that are specific to HeNS are defined within the present documents. Vendor specific measurement types used in HeNS are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to HeNB and HeNB GW);
- Header 2: Measurement function (e.g. HeNB registration measurements);
- Header 3: Measurements. |
32.454 | Telecommunication management; Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS); Definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.454/32454-i00.zip | The present document specifies Key Performance Indicators (KPIs) for the IP Multimedia Subsystem (IMS). |
32.455 | Telecommunication management; Key Performance Indicators (KPI) for the Evolved Packet Core (EPC); Definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.455/32455-i00.zip | The present document specifies Key Performance Indicators (KPIs) for the EPC. |
32.500 | Telecommunication management; Self-Organizing Networks (SON); Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.500/32500-i00.zip | The present document describes the requirements and architecture for the Self Organizing Network (SON) functions within the OAM system. SON includes:
Provision of infrastructure for SON, in the OAM system
- Enabling SON operations;
- Provide SON capabilities (each of which can either be distributed or centralised) within the OAM infrastructure, including their management;
- Access to SON relevant attributes;
- Identification of SON relevant Measurements;
- Access to and transfer of SON relevant measurements;
- Transfer of SON relevant alarms.
Define necessary Interface IRPs
the automation of neighbour relation lists in E-UTRAN, UTRAN and between different 3GPP Radio Access Technologies,
self establishment of a new eNodeB in the network,
self-configuration and self-healing of eNodeBs,
automated coverage and capacity optimisation,
optimisation of parameters due to troubleshooting,
continuous optimisation due to dynamic changes in the network,
automated handover optimisation,
optimisation of QoS related radio parameters.
The SON concept and architecture are described in clause 4.
The high-level requirements for SON are defined in clause 5.
Use cases for SON are described in clause 5. |
32.501 | Telecommunication management; Self-configuration of network elements; Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.501/32501-i00.zip | The present document describes the concepts how self-configuration works and what IRP requirements need to be met to support this functionality. The document also captures if a requirement shall be met via the Itf-N interface or via other protocols. This version of the TS is restricted to self-configuration of eNBs. The requirements in this document are not imposed on HNBs. |
32.502 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.502/32502-i00.zip | The present document defines the Information Service (IS) part of the Self-Configuration IRP (SCIRP).
It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
The information is specified by means of Information Object Classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information.
The scope of this version of the TS is restricted to self-configuration of eNBs.
The present documents also describes how already defined Itf-N functionalities are used in the context of Self-Configuration. |
32.506 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.506/32506-i00.zip | |
32.511 | Telecommunication management; Automatic Neighbour Relation (ANR) management; Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.511/32511-i00.zip | The present document describes the concepts and requirements for the management of Automatic Neighbour Relation (ANR) in UTRAN and E-UTRAN across the Itf-N. The ANR management is a key feature of Self Organizing Networks (SON) [4].
The NCR concept and background information are described in clause 4.
The requirements for management of NCR are defined in clause 5. |
32.531 | Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.531/32531-i00.zip | The present document describes the concepts how SWM of NEs works and what IRP requirements need to be met to support this functionality.
In the 3GPP Rel-8 the present document focuses on automated software management of eNBs. |
32.532 | Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.532/32532-i00.zip | The present document contains the Software Management Interface IRP Information Services descriptions. |
32.536 | Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.536/32536-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Software Management IRP Information Service (3GPP TS 32.532 [5]).
This Solution Set definitions specification is related to 3GPP TS 32.532 V14.0.X [5]. |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-i00.zip | The present document describes concept and requirements of OAM for Self-Healing of Self-Organizing Networks (SON). |
32.551 | Telecommunication management; Energy Saving Management (ESM); Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.551/32551-i00.zip | The present document describes the concepts and requirements how energy savings functionalities are managed what requirements need to be met to support this. The document also describes if a requirement shall be met via the Itf-N interface or via other means. |
32.571 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.571/32571-i00.zip | The present document describes requirements and concepts including architecture supporting Home Node B and Home eNode B OAM&P for interface Type 2. |
32.572 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.572/32572-i00.zip | The present document describes requirements and concepts including architecture supporting Home NB and Home eNB OAM&P for interface Type 2. |
32.581 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Concepts and requirements for Type 1 interface HNB to HNB Management System (HMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.581/32581-i00.zip | The present document describes the concepts and requirements of OAM for Home NodeB (HNB). The requirements captured in this document shall be met via Type 1 interface between HNB and HMS. |
32.582 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HNB to HNB Management System (HMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.582/32582-i00.zip | The present document describes the architecture for Home NodeB (HNB) Management and Data class definition for Fault Management, Configuration Management and Performance Measurements. The stage 2 definitions captured in this document shall be met via type 1 interface between HNB and Domain Manager. |
32.583 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HNB to HNB Management System (HMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.583/32583-i00.zip | The present document describes the procedure flows between HNB & HMS for the OAM of HNB Management. |
32.584 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.584/32584-i00.zip | The present document describes the data format for Configuration Management and Performance Management for Home Node B (HNB). The XML definitions captured in this document shall be met via Type 1 interface between HNB and HNB Management System (HMS). |
32.591 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Concepts and requirements for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.591/32591-i00.zip | The present document describes the concepts and requirements of OAM for Home eNodeB (HeNB). The requirements captured in this document shall be met via Type 1 interface between HeNB and HeMS. |
32.592 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-i00.zip | The present document describes the Information Model definition for Fault Management, Configuration Management and Performance measurements of Home eNodeBs.
The stage 2 definitions captured in the present document shall be met via type 1 interface between HeNB and HMS. |
32.593 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.593/32593-i00.zip | The present specification describes the procedure flows between network entities involved in HeNB management-related tasks. These procedures are based on the requirements specified in [4]. Information model for management-related information exchanged in these procedures is specified in [5] and references therein. XML file formats used to encapsulate the information exchanged in these procedures are specified in [6]. The communication protocol used for HeNB management is the TR-069 protocol, specified in [7].
Management interface affected by these procedures is the Type 1 interface between HeNB and HeMS. Procedures flows over the Type 2 interface (between Element Management and Network Management layer) for the management of HeNB are outside of scope of this document |
32.594 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.594/32594-i00.zip | The present document describes the data format for Configuration Management, Fault Management, and Performance Management for Home eNodeB (HeNB). The Stage 3 definitions captured in this document shall be met via type 1 interface between HeNB and Home eNodeB Management System (HeMS). |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-i00.zip | The present document describes the Configuration Management (CM) aspects of managing a PLMN network. This is described from the management perspective in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
The present document defines a set of controls to be employed to effect set-up and changes to a PLMN network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality.
Clause 7 contains the specific definitions for the standardised Itf-N, which are necessary to follow for compliance to this specification.
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.150 [9]. For CM, a number of IRPs (and a Name Convention see 3GPP TS 32.300 [8]) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP. |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-i00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: Basic Configuration Management IRP. |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-i00.zip | The present document defines a component of an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate basic Configuration Management related information to one or several 'IRPManagers' (typically Network Managers).
The function of this Basic CM IRP Information Service is to define an interface for the retrieval and modification of Configuration Management Information.
This Basic CM IRP IS is aligned with ITU-T M.3700 [15] in that ITU-T M.3700 is a subset of the Basic CM IRP IS in terms of the definitions of operations for the retrieval and modification of Configuration Management Information. |
32.606 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.606/32606-i00.zip | The purpose of this document is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 [8]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment and in a SOAP/WSDL environment.
This document defines NRM independent data types and methods.
This Solution Set specification is related to 3GPP TS 32.602 [8]. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-i00.zip | The present document describes the Bulk Configuration Management (CM) requirements for managing a 3G network. This is described from the management perspective in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2].
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention 3GPP TS 32.300 [3], which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2]. For CM, a number of IRPs (and a Name Convention) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP. These IRPs are defined in separate 3GPP specifications, and listed in the table in the Introduction clause above. This document defines the requirements for the Bulk CM IRP. |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-i00.zip | The present document (Bulk Configuration Management IRP: Information Service) defines a number of Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate bulk Configuration Management related information to one or several 'IRPManagers' (typically Network Managers). |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-i00.zip | The present document specifies the Solution Sets for the IRP whose semantics are specified in Bulk CM IRP: Information Service (3GPP TS 32.612 [9]).
This Solution Set specification is related to 3GPP TS 32.612 [9]. |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-i00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: Kernel Configuration Management IRP. It is the intent of Kernel Configuration Management to provide an IRP that contains the configuration management functionality that is basic and minimal. It is the functionality that is common to and required by both Basic CM and Bulk CM. While neither the Basic CM IRP nor Bulk CM IRP requires the other, they each require the Kernel CM IRP. |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-i00.zip | The present document defines Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management related information to one or several 'IRPManagers' (typically Network Managers).
The function of this Kernel CM IRP Information Service is to define an interface that provides the essential CM services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, The Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the Basic CM IRP or the Bulk CM IRP, each of which require the Kernel CM IRP. |
32.666 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.666/32666-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in Kernel CM (Configuration Management) IRP: Information Service 3GPP TS 32.662 [7].
This Solution Set definitions specification is related to 3GPP TS 32.662 [7]. |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-i00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: Inventory Management IRP. |
32.847 | Study on Charging Aspects for Network Slicing Phase 2 | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.847/32847-i00.zip | The present document continues the study on charging aspects of network slicing covered by TR 32.845 [2] but no longer limited to charging data collection functionalities without quota management as specified for Network Slice management charging in TS 28.202 [3] and for Network slice performance and analytics charging in 3GPP TS 28.201 [4].
The following is studied:
- Network slice converged charging for Network Slices enabled over 3GPP 5GS;
- Correlation aspects between Network Slice charging and the end user charging accessing the Network Slice;
- Inter-Provider (B2B) charging aspects by considering the different Organizations (e.g. MNO, Verticals).
The Converged Charging service aspects associated to the TR 23.700-40 [5] conclusion on network slice information is also considered. |
32.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-i00.zip | 3GPP TR 22.985 Service requirement for the UDC [5] describes the architecture of the User Data Convergence, a concept that proposes to move the user data from where it has been distributed and siloed in Network Elements, Applications, and other network resources to a single logical consolidated facility here called User Data Repository (UDR) where it can be accessed, stored and managed in a common way.
The introduction of a User Data Convergence of user data for network services and management applications could significantly enhance the ability of 3GPP based networks to offer complex and combined services. User data can be decomposed and reformed by a common data model framework (e.g. tree-like data model, rational data model) provided by UDR. In that case, user data categorized by services can be regrouped and identified by user ID, leaving no data redundancy. Also, convergence in data model will unify the user data access interface and its protocol, which will promote new service application development. Thereby, the capability of user data convergence can be open to creation of data-less applications.
Methods for data protection against access by unauthorized parties are outside the scope of this document.
3GPP TS 32.181 UDC Framework for Model Handling and Management [3] and 3GPP TS 29.335 UDC; User Data Repository Access Protocol over the Ud interface; Stage 3 [4] provide various types of information and data models associated with the architecture of UDC.
These include the Common Baseline Information Model (CBIM) (see 3GPP TS 32.182 [7]), the Specialized Information Model (SpIM), Application Information Models (AIMs), Application Data Models (ADMs), and the Consolidated Data Model (CDM) of the User Data Repository (UDR).
Figure 1 from 3GPP TS 32.181 UDC Framework for Model Handling and Management [3] shows the operational environment of the UDC.
Figure 1.1: Evolution of the CDM in a UDR
In addition to the models previously mentioned, Figure 1.1 introduces the aspect of the Provisioning Gateway, which is essential for the operation of the UDR. The Provisioning Gateway provides a single logical point for access to provisioning of user data for all services in the UDR. The Provisioning Gateway is shown supporting an interaction with the operator's BSS; by implication this interaction is associated with the provisioning of user subscription and service data in the UDR via the Provisioning Gateway.
This study analyzes the progression of information models displayed in the above figure using some specific application examples, in particular the applications of HSS-IMS and MMTel. It provides guidelines and preliminary requirements for the BSS provisioning capabilities and information model handling when new applications and related services are implemented in the operator's UDR by doing the following:
- Develop several example initial SpIMs for discussion purposes.
- Examine what BSS interactions with the Provisioning Gateway would be required to support provisioning of user service and subscription data in the UDR for these SpIMs.
- Study the relationship to the information model of 3GPP TS 32.172 Subscription Management (SuM) Network Resource Model (NRM) IRP Information Service [9].
- Develop understanding of CBIM-derived entities of Application Information Models (AIM) for HSS-IMS and MMTel from application data elements available in 3GPP TS 29.364 IMS Application Server service data descriptions for AS interoperability [11], 3GPP TS 23.008 Organization of subscriber data [12], and other relevant specifications.
- Discuss the integration and consolidation of these AIM entities with the example initial SpIMs above.
- Evaluate the potential changes to the BSS provisioning interactions for the implementation of HSS-IMS and MMTel applications in the UDR and implications concerning the information model of 3GPP TS 32.172 Subscription Management (SuM) Network Resource Model (NRM) IRP Information Service [9].
This study does not derive findings concerning the Ud reference point, the subject of 3GPP TR 23.845 Study on UDC Evolution [10]. |
32.972 | Telecommunication management;Study on system and functional aspects of energy efficiency in 5G networks | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.972/32972-i00.zip | The present document studies energy efficiency aspects of 5G networks, at both network function level and at 3GPP system level. The study covers:
- energy efficiency KPI definitions, including already existing definitions from other 3GPP WGs and other SDOs and potentially new ones for 5G networks;
- measurement methods, including already existing measurement methods from other 3GPP WGs and other SDOs and potentially new ones for 5G networks;
- potential solutions to improve energy efficiency of 5G networks;
- energy efficiency control framework, as a SON-like framework for the control of energy efficiency of 5G networks.
The study also makes conclusions on the preferred solution(s), and provides recommendations for them. |
33.102 | 3G security; Security architecture | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-i00.zip | |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-i00.zip | This specification constitutes a requirements specification for the security functions which may be used to provide the network access security features defined in [1].
The specification covers the intended use of the functions, the technical requirements on the functions and the requirements as regards standardization.
For those functions that require standardization, it also covers the intended use of the algorithm specification, the requirements on test data, and quality assurance requirements on both the algorithm and its documentation. |
33.106 | 3G security; Lawful interception requirements | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-i00.zip | The present document contains historical Stage 1 lawful interception requirements within a 3GPP network for Rel-14 and earlier.
This specification is replaced by TS 33.126 [28] from Rel-15 onwards and should only be used as a historical reference to pre Rel-15 LI requirements. |
33.107 | 3G security; Lawful interception architecture and functions | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-i00.zip | The present document describes the architecture and functional requirements within a Third Generation Mobile Communication System (3GMS) and the Evolved Packet System (EPS).
The present document shows the service requirements from a Law Enforcement point of view only. The aim of this document is to define a 3GMS and EPS interception system that supports a number of regional interception regulations, but these regulations are not repeated here as they vary. Regional interception requirements shall be met by using specific (regional) mediation functions allowing only required information to be transported.
The handover interfaces for Lawful Interception (LI) of Packet-Data Services, Circuit Switched Services, and Multimedia Services within the UMTS network and Evolved Packet System for Stage 3 are described in TS 33.108 [11]. |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-i00.zip | |
33.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-i00.zip | The present document describes the security features and mechanisms to provision a shared key between a UICC and a terminal that may host the UICC or be connected to the device hosting the UICC via a local interface. Candidate applications to use this key establishment mechanism include but are not restricted to secure channel between a UICC and a terminal ETSI TS 102 484 [8].
The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC and the terminal. |
33.116 | Security Assurance Specification (SCAS) for the MME network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.116/33116-i00.zip | |
33.117 | Catalogue of general security assurance requirements | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.117/33117-i30.zip | |
33.122 | Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs | TS | 18.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.122/33122-i40.zip | |
33.126 | Lawful Interception requirements | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.126/33126-i20.zip | |
33.127 | Lawful Interception (LI) architecture and functions | TS | 18.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.127/33127-ic0.zip | |
33.128 | Security; Protocol and procedures for Lawful Interception (LI); Stage 3 | TS | 18.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.128/33128-ic0.zip | |
33.141 | Presence service; Security | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-i00.zip | The present document is the Stage 2 specification for the security requirements, security architecture, security features and security mechanisms for the Presence Service, which includes the elements necessary to realise the requirements in TS 22.141 [2] and TS 23.141 [3]. As far as SIP-based procedures are concerned, this specification refers to TS 33.203 [4]. The main content of this specification is the security for the Ut reference point, which is HTTP–based, as applied in presence services.
The present document includes information applicable to network operators, service providers and manufacturers. |
33.163 | Battery Efficient Security for very low throughput Machine Type Communication (MTC) devices (BEST) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.163/33163-i00.zip | The present document defines communication security processes designed for very low throughput Machine Type Communication (MTC) devices that are battery constrained.
These processes consist of:
- A Key agreement service for End to Middle and End to End security use
- An End to Middle secure transport service that includes the ability to verify and confidentiality protect low throughput data.
- An End to End secure transport service that includes the ability to verify and confidentiality protect low throughput data. |
33.180 | Security of the Mission Critical (MC) service | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.180/33180-i10.zip | |
33.185 | Security aspect for LTE support of Vehicle-to-Everything (V2X) services | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.185/33185-i00.zip | The present document specifies the security aspects of V2X features in LTE, including security architecture, security requirements on the network entities that are used to support V2X services, as well as the procedures and solutions which are provided to meet those requirements. |
33.187 | Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-i00.zip | The present document specifies the security architecture enhancements (i.e., enhancements to the security features and the security mechanisms) to facilitate Machine-Type and other mobile data applications Communications enhancements (MTCe) as per the use cases and service requirements defined in 3GPP TS 22.368 [2] and the architecture enhancements and procedures defined in 3GPP TS 23.682 [3]. |
33.203 | 3G security; Access security for IP-based services | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-i10.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-i00.zip | This technical specification covers the security mechanisms and procedures necessary to protect all TCAP user messages which are sent between different security domains. The complete set of enhancements and extensions to facilitate security protection for the TCAP protocol is termed TCAPsec and it covers transport security in the TCAP protocol itself and the security management procedures.
This technical specification contains the stage 2 specification for security protection of the TCAP protocol. The actual implementation (stage 3) specification can be found in TS 29.204 [9]. |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-i10.zip | |
33.216 | Security Assurance Specification (SCAS) for the evolved Node B (eNB) network product class | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.216/33216-i10.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-i30.zip | The present document describes the security features and mechanisms to bootstrap authentication and key agreement for application security. Candidate applications to use this bootstrapping mechanism include but are not restricted to subscriber certificate distribution TS 33.221 [5]. Subscriber certificates support services whose provision mobile operator assists, as well as services that mobile operator provides.
The scope of this specification includes generic bootstrapping functions, an architecture overview and the detailed procedure how to bootstrap the credential.
Clause 4 of this specification describes a mechanism, called GBA_ME, to bootstrap authentication and key agreement, which does not require any changes to the UICC. Clause 5 of this specification describes a mechanism, called GBA_U, to bootstrap authentication and key agreement, which does require changes to the UICC, but provides enhanced security by storing certain derived keys on the UICC. Annex I of this specification describes a mechanism, called 2G GBA, to bootstrap authentication and key agreement using 2G AKA protocol. Annex M of this specification describes a mechanism, called GBA_Digest, to bootstrap authentication and key agreement using HTTP Digest protocol with SIP Digest credentials. |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-i00.zip | The present document describes subscriber certificate distribution by means of generic bootstrapping architecture (GBA) TS 33.220 [11]. Subscriber certificates support services whose provision the mobile operator assists, as well as services that are offered by the mobile operator.
The scope of this specification presents signalling procedures for support of issuing certificates to subscribers and the standard format of certificates and digital signatures. It is not intended to duplicate existing standards being developed by other groups on these topics, and will reference these where appropriate. |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-i00.zip | The present document specifies secure access methods to Network Application Functions (NAF) using HTTP over TLS in the Generic Authentication Architecture (GAA), and provides Stage 2 security requirements, principles and procedures for the access. The present document describes both direct access to an Application Server (AS) and access to an Application Server through an Authentication Proxy (AP).
NOTE: Any application specific details for access to Applications Servers are not in scope of this specification and are covered in separate documents. An example of such a document is TS 33.141 [5], which specifies the security for presence services. |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-i00.zip | The present document specifies a Push Function as a functional add-on for the Generic Authentication Architecture (GAA) [1]. |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-i00.zip | The present document specifies a generic push layer that makes use of the GBA Push Function as specified in TS 33.223 [3]. The GPL specification includes a message format, cipher suites and processing model. GPL assumes that keys and other SA parameters have been preinstalled in the Push-NAF and UE in the form of a NAF SA. GPL is a protection protocol that can be applied in a unidirectional fashion.
The rationale for GPL is that having each application specify its own security mechanisms would for obvious reasons lead to duplication of work, specifications and implementations. Using a generic secure push layer avoids these problems. A generic secure push layer may also relieve the applications using the service of having to be aware of inner working of the security layer. As an analogy, TS 33.222 [4] can be mentioned, which provides a generic security layer for HTTP based applications. |
33.226 | Security assurance for IP Multimedia Subsystem (IMS) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.226/33226-i00.zip | The present document contains objectives, requirements and test cases that are specific to the IMS network product classes. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the IMS network product classes. |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-i00.zip | The present document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLAN ).
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications. |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-i00.zip | |
33.250 | Security assurance specification for the PGW network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.250/33250-i00.zip | |
33.256 | Security aspects of Uncrewed Aerial Systems (UAS) | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.256/33256-i20.zip | |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-i00.zip | The present document describes the security features and mechanisms to provision a shared key between a UICC Hosting Device and a Remote Device connected via a local interface. The shared secret is then intended to be used to secure the interface between the Remote Device and the UICC hosting device. Candidate applications to use this key establishment mechanism include but are not restricted to Personal Network Management (see TS 22.259 [4]).
The scope of this specification includes an architecture overview and the detailed procedure how to establish the shared key between the UICC Hosting Device and the Remote Device. This is different from the Technical Specification TS 33.110 [5] that describes an architecture overview and the detailed procedure how to establish the shared key between the UICC itself and the terminal hosting the UICC. The use cases utilizing the mechanisms described in this specification are seen to be different to the use cases where "Key establishment between a UICC and a terminal", PSK TLS as specified in TS 33.310 [19], is utilized.
The solution described in this document is built on the existing infrastructure defined in "GBA", TS 33.220 [3]. |
33.303 | Proximity-based Services (ProSe); Security aspects | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.303/33303-i00.zip | The present document specifies the security aspects of the Proximity Services (ProSe) features in EPS.
Based on the common security procedures (clause 5) for
- interfaces between network entities (using NDS),
- configuration of ProSe-enabled UEs, and
- data transfer between the ProSe Function and a ProSe enabled UE (PC3 interface)
security for the following ProSe features is covered:
- Open ProSe Direct Discovery in network coverage (clause 6.1);
- One-to-many ProSe direct communication for ProSe-enabled Public Safety UEs (clause 6.2);
- EPC-level Discovery of ProSe-enabled UEs (clause 6.3);
- EPC support for WLAN Direct Discovery and Communication (clause 6.4) ;
- One-to-one ProSe direct communication for ProSe-enabled Public Safety UEs (clause 6.5);
- Prose Public Safety Discovery (clause 6.6);
- Prose UE-to-network relays (clause 6.7); |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 18.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-i70.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-i00.zip | The present document specifies the security architecture for the H(e)NB subsystem. This includes security requirements on Home Node Bs, Home eNode Bs, and other H(e)NB-associated network nodes (e.g. SeGW and H(e)MS), as well as the procedures and features which are provided to meet those requirements. |
33.326 | Security Assurance Specification (SCAS) for the Network Slice-Specific Authentication and Authorization Function (NSSAAF) network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.326/33326-i00.zip | The present document contains requirements and test cases that are specific to the NSSAAF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases, as well as specifying requirements and test cases unique to the NSSAAF network product class. |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 18.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-i40.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-i30.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-i10.zip | The present document specifies the security architecture, i.e., the security feature groups and the security mechanisms performed during inter working between non-3GPP accesses and the Evolved Packet System (EPS). |
33.434 | Security aspects of Service Enabler Architecture Layer (SEAL) for verticals | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.434/33434-i20.zip | |
33.501 | Security architecture and procedures for 5G System | TS | 18.10.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.501/33501-ia0.zip | |
33.503 | Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) | TS | 18.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.503/33503-i50.zip | |
33.511 | Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.511/33511-i30.zip | |
33.512 | 5G Security Assurance Specification (SCAS); Access and Mobility management Function (AMF) | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.512/33512-i20.zip | |
33.513 | 5G Security Assurance Specification (SCAS); User Plane Function (UPF) | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.513/33513-i10.zip | |
33.514 | 5G Security Assurance Specification (SCAS) for the Unified Data Management (UDM) network product class | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.514/33514-i30.zip | |
33.515 | 5G Security Assurance Specification (SCAS) for the Session Management Function (SMF) network product class | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.515/33515-i10.zip | |
33.516 | 5G Security Assurance Specification (SCAS) for the Authentication Server Function (AUSF) network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.516/33516-i00.zip | The present document contains objectives, requirements and test cases that are specific to the AUSF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the AUSF network product class. |
33.517 | 5G Security Assurance Specification (SCAS) for the Security Edge Protection Proxy (SEPP) network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.517/33517-i00.zip | |
33.518 | 5G Security Assurance Specification (SCAS) for the Network Repository Function (NRF) network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.518/33518-i00.zip | |
33.519 | 5G Security Assurance Specification (SCAS) for the Network Exposure Function (NEF) network product class | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.519/33519-i00.zip | The present document contains requirements and test cases that are specific to the NEF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the NEF network product class. |
33.520 | Security Assurance Specification (SCAS) for Non-3GPP InterWorking Function (N3IWF) | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.520/33520-i10.zip | The present document contains objectives, requirements and test cases that are specific to the Non-3GPP InterWorking Function (N3IWF) network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the N3IWF network product class. |
33.521 | 5G Security Assurance Specification (SCAS);Network Data Analytics Function (NWDAF) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.521/33521-i00.zip | The present document contains requirements and test cases that are specific to the NWDAF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases, as well as specifying requirements and test cases unique to the NWDAF network product class. |
33.522 | 5G Security Assurance Specification (SCAS); Service Communication Proxy (SCP) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.522/33522-i00.zip | The present document contains objectives, requirements and test cases that are specific to the SCP network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the SCP network product class. |
33.523 | 5G Security Assurance Specification (SCAS); Split gNB product classes | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.523/33523-i20.zip | |
33.526 | Security assurance specification for the Management Function (MnF) | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.526/33526-i10.zip | The present document contains objectives, requirements and test cases that are specific to the MnF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the MnF network product class. In the present document, the MnF network product class represents independently deployed management product supporting 3GPP defined management services. |
33.527 | Security Assurance Specification (SCAS) for 3GPP virtualized network products | TS | 18.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.527/33527-i30.zip | |
33.528 | Security Assurance Specification (SCAS) for the Policy Control Function (PCF) | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.528/33528-i00.zip | The present document contains requirements and test cases that are specific to the PCF network product class. It refers to the Catalogue of General Security Assurance Requirements [2] and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the PCF network product class. |
33.533 | Security aspects of ranging based services and sidelink positioning | TS | 18.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.533/33533-i50.zip | The present document specifies the security and privacy aspects of Ranging based services and Sidelink positioning in the 5G System (5GS) for commercial, V2X and public safety use cases, with the UE in coverage, partial coverage, and out-of-coverage of 5G network using 5G NR PC5 RAT, based on the architecture defined in TS 23.586 [2].
Security features for Ranging based services and Sidelink positioning include:
- authorization for Ranging/SL positioning service;
- security and privacy protection for Ranging/SL positioning UE discovery;
- security and privacy protection for unicast communication of Ranging/SL positioning control; and
- security and privacy protection for broadcast/groupcast communication of Ranging/SL positioning control. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.