id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
A security feature is a service capability that meets one or several security requirements. The complete set of security features address the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133 [1]) and implement the security objectives and principles described in TS 33.120 [2]. A security mechanism is an element that is used to realise a security feature. All security features and security mechanisms taken together form the security architecture.
An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e. intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
GSM security functions are defined in the TS 43.020 [36].
NOTE: The usage of the authentication management field (AMF) is specified in Annex H and applies for the third (UMTS), fourth (LTE) and fifth (5G system) generation of mobile telecommunication systems. |
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 | |
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 | |
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 | |
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 | The present document specifies the handover interfaces for Lawful Interception (LI) of Packet-Data Services, Circuit Switched Services, Multimedia Services within the UMTS network and Evolved Packet System (EPS). The handover interface in this context includes the delivery of Intercept Related Information (IRI) through the Handover Interface 2 (HI2) and Content of Communication (CC) through the Handover Interface 3 (HI3) to the Law Enforcement Monitoring Facility (LEMF). |
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 | |
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 | The present document contains objectives, requirements and test cases that are specific to the MME 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 MME network product class. |
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 | The present document contains objectives, requirements and test cases that are deemed applicable, possibly after adaptation, to several network product classes.
Several network product classes share very similar if not identical security requirements for some aspects. Therefore, these are collected in this "catalogue" document applicable to many network product classes. In addition to this catalogue, requirements specific to different network product classes will be captured in separate documents. |
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 | The present document specifies Stage 1 Lawful Interception requirements for 3GPP networks and services.
Regional interception requirements can be satisfied by meeting the correct subset of requirements from the present document. Which CSP services are subject to Lawful Interception is defined by national regulations.
The presence of a requirement in the present document does not in itself imply or mandate that a 3GPP operator has an obligation to implement any network service capability, which is not otherwise required to meet LI obligation compliance in relation to specific regulated services, offered by that 3GPP operator. Only those specific requirements and sub-clauses of the present document which are applicable to specific network and/or service capabilities implemented in a 3GPP operator's network will be considered in scope for that operator. In all cases, laws and regulations define which requirements are applicable to 3GPP operators in each country relative to the services offered by each 3GPP operator.
As such not all requirements in the present document will apply in all national jurisdictions or to all 3GPP operator deployments (e.g. if an operator does not offer voice services, then voice LI requirement in the present document do not apply).
The interception system defined in the present document provides LI based on specific target identifiers. |
33.127 | Lawful Interception (LI) architecture and functions | TS | 18.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.127/33127-id0.zip | |
33.128 | Security; Protocol and procedures for Lawful Interception (LI); Stage 3 | TS | 18.14.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.128/33128-ie0.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 | |
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 | |
33.180 | Security of the Mission Critical (MC) service | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.180/33180-i20.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 | |
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 | |
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 | The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
Since the scope also encompasses the use of these security features and mechanisms for secure access to IMS in the context of fixed broadband networks and 3GPP2 networks, Annex L and Annex S specify how the material in the main body and other normative Annexes of this document apply to the fixed broadband networks and 3GPP2 networks respectively.
The IMS supports IP Multimedia applications such as video, audio and multimedia conferences. SIP, Session Initiation Protocol, was chosen as the signalling protocol for creating and terminating Multimedia sessions, cf. RFC 3261 [6]. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS. |
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 | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-i20.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 | The present document contains objectives, requirements and test cases that are specific to the eNB 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 eNB network product class. |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | The Technical Specification covers the security procedures of the Multimedia Broadcast/Multicast Service (MBMS) for 3GPP systems (UTRAN, GERAN and E-UTRAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application. |
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 | The present document contains requirements and test cases that are specific to the PGW 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 PGW network product class. |
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 | |
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 | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 18.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-i80.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 | |
33.326 | Security Assurance Specification (SCAS) for the Network Slice-Specific Authentication and Authorization Function (NSSAAF) network product class | TS | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.326/33326-i10.zip | |
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 | |
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 | The present document specifies the security features and mechanisms to support the Service Enabler Architecture Layer (SEAL) in 5G. Specifically security architecture, functional model(s), security aspects of SEAL reference points (e.g. SEAL-UU, etc.), Key Management (KM) procedures, Identity Management (IdM) procedures and SEAL access authentication and authorization for supporting efficient use and deployment of vertical applications over the 3GPP systems are specified. |
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 | The present document contains objectives, requirements and test cases that are specific to the AMF 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 AMF network product class. |
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 | The present document contains requirements and test cases that are specific to the UPF network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases. It also specifies the requirements and test cases unique to the UPF network product class. |
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 | The present document contains requirements and test cases that are specific to the UDM network product class. It refers to the Catalogue of General Security Assurance Requirements and formulates specific adaptions of the requirements and test cases. It also specifies the requirements and test cases unique to the UDM network product class. |
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 | The present document contains requirements and test cases that are specific to the SMF 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 SMF network product class. |
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 | |
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 | The present document contains objectives, requirements and test cases that are specific to the SEPP 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 SEPP network product class. |
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 | The present document contains objectives, requirements and test cases that are specific to the NRF 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 NRF network product class. |
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 | |
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 | |
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 | |
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 | |
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 | The gNB can be deployed as more than one entity by splitting the gNB into gNB-CU and gNB-DU(s) and possibly further splitting the gNB-CU into gNB-CU-CP and gNB-CU-UP(s) (see TS 38.401 [5]). The present document contains objectives, requirements and test cases that are specific to the various split gNB network product classes. Test cases for such deployments are provided, are based upon and borrow heavily from the specification for the gNB product class (see TS 33.511 [6]). The main differences are the inclusion of cases for the F1 signalling and user plane connection and the E1 signalling connection on the top of the gNB cases as well as some revised cases to account for the split functionality. The present document also refers to the Catalogue of General Security Assurance Requirements (see TS 33.117 [2]) and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the various split gNB network product class. |
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 | |
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 | The present document contains objectives, requirements and test cases to virtualized network product classes.
Several virtualized network product classes share very similar if not identical security requirements for some aspects. Therefore, these are collected in the present document applicable to many virtualized network product classes. In addition to this catalogue, requirements specific to different network product classes will be captured in separate documents. |
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 | |
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 | |
33.535 | Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) | TS | 18.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.535/33535-i80.zip | |
33.536 | Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.536/33536-i00.zip | |
33.537 | Security Assurance Specification (SCAS) for the Authentication and Key Management for Applications (AKMA) Anchor Function (AAnF) | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.537/33537-i20.zip | The present document contains requirements and test cases that are specific to the AAnF 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 AAnF network product class. |
33.558 | Security aspects of enhancement of support for enabling edge applications | TS | 18.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.558/33558-i20.zip | The present document specifies the security features and mechanisms to support the application architecture for enabling Edge Applications in 5G, i.e. security for the interfaces, procedures for the authentication and authorization between the entities of the application architecture, and procedures for the EES capability exposure. |
33.700-28 | Study on security aspects of satellite access | TR | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.700-28/33700-28-i00.zip | The present document investigates the security and privacy aspects of satellite access/NTN. The study is based on the architectural and functional requirements on integration of satellite components in the 5GS/EPS architecture, so as to ensure that the proposed solutions address the security and privacy implications on the architecture enhancements agreed in TR 23.700-28 [x]. Specifically, it covers the following:
- The identified security and privacy issues, threats, and potential requirements for protecting the UE in the enhanced 5GS/EPS architecture supporting discontinuous coverage with satellite access;
- The potential solutions addressing the identified security and privacy issues as above. |
33.737 | Study on Authentication and Key Management for Applications (AKMA) phase 2 | TR | 18.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.737/33737-i10.zip | The present document studies key issues and potential solutions to support roaming aspects and the Authentication Proxy in AKMA, which is specified in TS 33.535 [2]. Specifically, the present document:
- Investigates AKMA roaming architecture and requirements by taking regulatory compliance into account;
- Studies the architecture impact and procedures of introducing the Authentication Proxy (similar as the AP specified in GBA) into AKMA. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.