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.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-f10.zip | |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-f10.zip | |
32.666 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.666/32666-f10.zip | |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-f10.zip | |
32.848 | Study on Volume based charging aspects for Voice Over LTE (VoLTE) | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.848/32848-f00.zip | The present document studies requirements, architecture, and possible functional enhancements of volume based charging for VoLTE.
The study investigates how to associate the identifiers of caller and callee with volume based charging for VoLTE.
The study investigates how to support the volume based charging for different IMS based services (e.g. CAT and voice calls, 3PTY conference, Call waiting, Call Hold).
The study investigates how to collect accounting information to determine the status of VoLTE service delivery in PS offline charging.
The complete or partial conclusions of this study form the basis for the normative work and/or for any further study. |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-f10.zip | |
32.857 | Study on management aspects of selected Internet of Things (IoT)-related features | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.857/32857-f00.zip | This document investigates management aspects of LTE IoT related functionalities such as eMTC and NB-IoT RAN Features, to identify functionalities that should be added to the existing 3GPP OAM specifications. The document outlines basic use cases, sets potential requirements and suggests potential solutions. |
32.864 | Telecommunication management;Study on management aspects of virtualized network functions that are part of the New Radio (NR) | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.864/32864-f00.zip | The present document studies on the management of virtualized network functions that are part of the NR that includes the following aspects:
- The management use cases and requirements for the virtualized network functions that are part of the NR, and their relations with non-virtualized part of the RAN and the core networks.
- Analysis to identify the gaps for the use cases and requirements that cannot be supported by the management solutions of mobile networks that include virtualized core network functions (EPC or IMS).
- The potential solutions for the gaps identified above.
- Recommendations on the next step. |
32.865 | Study on Operations, Administration and Maintenance (OAM) aspects of Self-Organizing Network (SON) for Active Antenna System (AAS) based deployments | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.865/32865-f00.zip | The present document studies the OAM aspects of SON (Self-Organizing Network) for AAS (Active Antenna Systems) based deployments in LTE.
The study includes use cases, potential requirements and possible solutions of OAM aspects of SON for AAS-based deployments in LTE, for both OAM centralized architecture and eNB distributed architecture with OAM supervision.
The study also makes conclusions on the preferred solution(s), and provides recommendations based on the conclusions of the study. |
32.866 | Telecommunication management;Study on a REST(REpresentational State Transfer)-ful HTTP-based Solution Set (SS) | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.866/32866-f00.zip | The present document evaluates REST, HTTP and JSON for their applicability to design and implement management interfaces. It provides also best practices and guidelines for designing management interfaces with REST, HTTP and JSON. |
32.867 | Telecommunication management;Study on management enhancement of Control and User Plane Split (CUPS) of Evolved Packet Core (EPC) nodes | TR | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.867/32867-f10.zip | |
32.856 | Study on Operations, Administration and Maintenance (OAM) support for assessment of energy efficiency in mobile access networks | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.856/32856-f00.zip | The present document reports how 3GPP OAM specifications can provide support for the assessment of energy efficiency in radio access networks as defined by ETSI ES 203 228 [2], thanks to measuring both network performance and energy consumption. It provides a gap analysis between ETSI ES 203 228 [2] and 3GPP OAM Technical Specifications, and provides recommendations towards ETSI ES 203 228 [2] compliance, including suggestions for further 3GPP specification enhancements. It also provides an analysis of how ETSI ES 202 336-12 [31] architecture, interfaces and information model may fit with the 3GPP management reference model defined in 3GPP TS 32.101 [32] and 3GPP IRPs, identifies potential use cases and requirements and studies potential solutions for interfaces that are in the scope of 3GPP. Finally, it provides recommendations for normative work. |
32.869 | Telecommunication management; Charging management; Study on Overload Control for Diameter Charging Applications | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.869/32869-f00.zip | The present document studies the overload control mechanisms for Rc, Re, Rf and Ro interfaces based on the conclusion of TR 29.809 [212].
For 3GPP Diameter Charging interfaces, the Diameter overload control mechanism are based on the IETF Draft "Diameter Overload Indication Conveyance" that defines the AVPs for the transport of overload information of Diameter application as well as the basic behaviour of the Diameter endpoints receiving this information.
The IETF RFC 7683 [404] is considered as the reference of the present document and not the IETF Draft draft-ietf-dime-ovli-02 referenced by TR 29.809 [212].
As per TR 29.809 [212], the following conclusions apply and are not studied in the present document:
- How a reporting node determines it is entering into an overload condition is implementation dependent.
- How a reporting node determines the contents value of the overload report (i.e. OC-OLR AVP) is implementation dependent.
- How a reacting node achieves traffic reduction (i.e. selection of impacted sessions) is implementation dependent.
The following issues are covered by the present document:
- Application and/or modification of current failure handling functionality defined in TS 32.299 [50] for Diameter online and offline charging in the Charging Trigger Function when reacting to overload control indication from the OCS or CDF, respectively. |
32.868 | Telecommunication management;Study on Operations, Administration and Maintenance (OAM) aspects of Long Term Evolution (LTE) and Wireless LAN (WLAN) integration | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.868/32868-f00.zip | The present document studies the following OAM aspects of LWA (for both co-located and non-co-located deployment scenarios) and LWIP, based on the solutions defined by 3GPP RAN WGs:
- the WLAN related information needs to be configured to the eNB to support LWA and LWIP.
- how the 3GPP management system manages the WT function for the case that the WT function is implemented in a non-3GPP NE (e.g., WLAN AC, WLAN AP).
- the management model for WT for co-located and non-co-located LWA deployment scenarios.
- the performance measurements to monitor the LWA and LWIP.
- the FM (Fault Management) of LWA and LWIP.
The study also makes conclusions on the potential solution(s), and provides recommendations for the normative work based on the conclusions of the study. |
32.871 | Study on policy management for mobile networks based on Network Function Virtualization (NFV) scenarios | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.871/32871-f00.zip | From mobile service and network function management perspective, the present document studies the end-to-end network policy management for mobile network based on NFV scenarios:
- Study the concepts and classification of the policy management for mobile networks based on the NFV scenarios, analyse and classify the potential policy management scenarios.
- Identify the use cases and requirements of policy management for mobile networks based on the NFV scenario.
- Study the potential logical roles of the policy management for mobile networks based on the NFV scenarios.
- Identify the impacts of logical architecture and the potential requirements to 3GPP management system. Analyse the existing 3GPP Management reference model, interfaces, protocols and procedures to determine what can be re-used, adapted or extended. Propose enhancements or extensions to the 3GPP solutions, if an impact is foreseen.
- Identify the impacts to NFV-MANO framework from the 3GPP service perspective.
- Provide recommendations to the standardization of policy management for mobile networks based on the NFV scenario.
The study will focus on the policy solutions which are related to NFV scenarios and will take into account of the outcome of SA5 existing specifications and the outcome produced by ETSI. The study will investigate whether the existing specification can be reused or not. |
32.870 | Telecommunication management;Charging management;Study on forward compatibility for 3GPP Diameter charging applications | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.870/32870-f00.zip | The present document studies forward compatibility for 3GPP Charging Applications over Rf and Ro Reference Points, specified by using IETF Diameter protocol.
In particular, it is investigated how to conform with TR 29.819 [413] conclusion on Diameter extensibility rules, per following clause 5.3.1.4 statement:
"For 3GPP Diameter Accounting application using the Diameter Base Protocol Accounting (application Id =3), such as specified in the 3GPP TS 32.299 [16], further studies are required to evaluate how AVPs can be added to existing commands with the M-bit cleared to avoid backward compatible issues. "
This document is independent of whether IETF RFC 3588 [401] or IETF RFC 6733 [412] is referred to as the Diameter Base protocol for Rf and Ro. Update from IETF RFC 3588 [401] to IETF RFC 6733 [412] can be decided prior to any conclusion from this study. |
32.899 | Telecommunication management; Charging management;Study on charging aspects of 5G system architecture phase 1 | TR | 15.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.899/32899-f10.zip | The present document studies the charging architecture, principles and functionalities for a 5G System Phase 1 specified in TS 23.501 [201] and TS 23.502 [202], based on the TR 23.799 [200] conclusions.
The stage 1 requirements from TS 22.115 [101] and TS 22.261 [102] are also input for this study.
The charging architecture and functionalities are studied for the set of features and capabilities supported by the 5G System Phase 1, and for interworking scenarios between the 5G System and existing systems as well.
Evolution of charging mechanisms and charging models to support the Third Parties are investigated.
The study provides a prioritisation between the different features, if evaluated as necessary, to allow a potential phased approach for the normative work. |
32.880 | Telecommunication management;Study on implementation for the partitioning of Itf-N | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.880/32880-f00.zip | The present document examines the IRP Information Service (IS) of Itf-N from existing TS 32-series specifications and identifies one subset of IRP functionality according to the IRP requirements in TR 32.861[2], also studies diverse solution sets and compares them between each other on efficiency and complexity. Finally, this document gives a suggestion of one or more solution set(s) for above identified IS subset. |
32.972 | Telecommunication management;Study on system and functional aspects of energy efficiency in 5G networks | TR | 0.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.972/32972-060.zip | |
33.102 | 3G security; Security architecture | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-f10.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. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-f00.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-f10.zip | |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-f00.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 15.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-f80.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.107 | 3G security; Lawful interception architecture and functions | TS | 15.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-f60.zip | |
33.116 | Security Assurance Specification (SCAS) for the MME network product class | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.116/33116-f10.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.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-f00.zip | |
33.122 | Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs | TS | 15.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.122/33122-f40.zip | |
33.117 | Catalogue of general security assurance requirements | TS | 15.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.117/33117-f50.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.127 | Lawful Interception (LI) architecture and functions | TS | 15.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.127/33127-f50.zip | |
33.128 | Security; Protocol and procedures for Lawful Interception (LI); Stage 3 | TS | 15.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.128/33128-fd0.zip | |
32.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 15.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-f00.zip | |
33.163 | Battery Efficient Security for very low throughput Machine Type Communication (MTC) devices (BEST) | TS | 15.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.163/33163-f60.zip | |
33.141 | Presence service; Security | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-f00.zip | |
33.185 | Security aspect for LTE support of Vehicle-to-Everything (V2X) services | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.185/33185-f00.zip | |
33.180 | Security of the Mission Critical (MC) service | TS | 15.14.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.180/33180-fe0.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 15.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-f30.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.187 | Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-f10.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 15.2.2 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-f22.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-f00.zip | |
33.126 | Lawful Interception requirements | TS | 15.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.126/33126-f20.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.216 | Security Assurance Specification (SCAS) for the evolved Node B (eNB) network product class | TS | 15.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.216/33216-f30.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.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-f00.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-f00.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-f00.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-f00.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 15.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-f40.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-f00.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-f00.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 | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.250/33250-f10.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.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 15.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-f20.zip | |
33.303 | Proximity-based Services (ProSe); Security aspects | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.303/33303-f00.zip | |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-f00.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 15.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-fc0.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-f10.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-f00.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-f10.zip | |
33.501 | Security architecture and procedures for 5G System | TS | 15.18.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.501/33501-fi0.zip | |
33.841 | Study on the support of 256-bit algorithms for 5G | TR | 0.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.841/33841-070.zip | The present document details the following:
- An assessment of threats and potential countermeasures posed due to quantum computing and a resulting assessment of relevant countermeasures in the 5G system.
- An assessment of the timelines for the introduction of any countermeasures, in particular the increase of key lengths to 256 bits. This includes an alignment with the timeline for strengthening asymmetric cryptographic algorithms used in 5G systems.
- An assessment of which parts of the 5G system will be affected and in which way.
- A Study of full entropy 256 bit keys in the 5G key hierarchy, beginning with the permanent pre-shared key. Including a study into modifying the derivation algorithms in order to derive child keys from the 256-bit master key instead of the 128-bit key.
- A study to determine whether a longer MAC is appropriate for 5G.
- A study of the coexistence of different size keys. In 3GPP networks, 256-bit keys in 5G will need to coexist with 128-bit keys in legacy networks or earlier 5G phases. This includes storage of keys and separate key derivation algorithms both on the UE and in the core network.
- A study into the desired number of 256-bit algorithms, e.g. if two 256-bit AKA key generation algorithm sets are needed.
- A study of the desired performance aspects for the new 256-bit algorithms taking into account software and hardware aspects.
- A study of key size negotiation.
- A study into whether the current methods for distribution and refresh of security keys are equally applicable to larger key sizes and can remain the same.
- A study into the Encryption and integrity algorithms that could be needed. This includes 256-bit session/intermediate keys in 5G, may, in some cases, simply entail using larger-key versions of current algorithms, while in other cases new algorithms may need to be chosen altogether.
- Recommendations for suitable requirements for the needed algorithms for use with 256-bit keys and ask ETSI SAGE to provide those algorithms. |
33.842 | Study on Lawful Interception (LI) service in 5G | TR | 0.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.842/33842-000.zip | The present document is a study based on the output (both studies and normative specifications) from other 3GPP groups such as those for 5G Phase 1 as well as issues which arise out of regulatory LI requirements as well LI service specific issues such as those arising from national regulations. Potential solutions will be examined along with considerations of the trade-offs between the solutions will be described. These solutions can include changes to the LI service, architecture and/or stage 3 along.
It is expected that this TR will address stage 1, 2 & 3 aspects, and the completion of each stage’s section will correspond at least to the overall Release 15 schedule with the corresponding start of SA 3 LI stage normative work. |
33.843 | Study on security architecture enhancements to Proximity Services (ProSe) User Equipment (UE)-to-network relay | TR | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.843/33843-f10.zip | The present document contains a study of the security aspects of enhancements to ProSe UE-to-Network Relay. Its objective is to identify threats when an Evolved ProSe Remote UE with UICC connects to the network via an Evolved ProSe UE-to-Network Relay. The potential requirements are identified based on threat and the potential solutions are studied. Evaluations of solutions are captured and the conclusion forms the basis for the potential normative work. |
33.834 | Study on Long Term Key Update Procedures (LTKUP) | TR | 0.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.834/33834-090.zip | The present document is a study on the remote update of 3GPP long term secret keys held in a SIM / USIM.
It:
- Identifies which Long Term Keys should be updatable within this proposed feature.
- Identifies the 3GPP/non 3GPP elements that would be affected by the update of these keys.
- Identifies the Key Issues relating to the updating of long term keys.
- Identifies potential requirements for the updating of long term keys.
- Identifies the applicability of Long Term Key Updating to GSM, UMTS, LTE and 5G and how the requirements may change across these technologies.
- Identifies solutions for the updating of long term keys.
- Evaluates solutions for the updating of long term keys.
- Concludes on the best solutions(s) for the updating of long term keys.
- Makes recommendations for further work.
This study will consider existing and new solutions that can be used for the update of 3GPP Long Term Keys.
The management of subscriptions is out of scope for the present document. |
33.856 | Study on security aspects of single radio voice continuity from 5G to UTRAN | TR | 0.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.856/33856-030.zip | The present document studies the security aspects of single radio voice continuity from 5G to UTRAN CS. In particular, the goal of the present document is to study the impacts on 3GPP security architecture which may result from 5GS to UTRAN CS voice continuity, e.g. security context mapping from 5G and UTRAN, security procedure for the emergency call, etc. |
33.855 | Study on security aspects of the 5G Service Based Architecture (SBA) | TR | 1.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.855/33855-190.zip | 3GPP TS 23.501 [2] defines 5G services with a new service based architecture (SBA) approach.
The present document reviews the interactions in this new architecture, determines key issues relating to the security of SBA elements and interfaces, details potential solutions and recommends normative work . |
33.905 | Recommendations for Trusted Open Platforms | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-f00.zip | |
33.880 | Study on mission critical security enhancements | TR | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.880/33880-f10.zip | This document contains a study of the security aspects of the Mission-Critical service. It enhances the security solutions defined for MCPTT in TS 33.179 [3] to support the common functional architecture (MC_ARCH), enhancements to MCPTT (eMCPTT), data services (MCData), video services (MCVideo) and migration and interconnect services with partner systems (MCSMI).
In each case, this study includes an analysis of the threats to the service, the security requirements to mitigate those threats and an evaluation of possible technical solutions designed to meet the security requirements of the service.
Stage 2 aspects of the mission critical services are defined within TS 23.179 [2], TS 23.280 [8], TS 23.281 [9], TS 23.282 [10], TR 23.781 [11], TR 23.782 [12] and TS 33.179 [3]. Stage 1 requirements are defined in TS 22.179 [4], TS 22.280 [5], TS 22.281 [6] and TS 22.282 [7]. |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-f00.zip | |
33.916 | Security Assurance Methodology (SECAM) for 3GPP network products | TR | 15.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-f20.zip | |
33.811 | Study on security aspects of 5G network slicing management | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.811/33811-f00.zip | The present document is a study on the threats, potential security requirements and solutions for the features of 5G network slicing management as described in TS 28.530 [2] and TS 28.531[3]. |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-f00.zip | |
33.969 | Study on security aspects of Public Warning System (PWS) | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-f00.zip | |
33.937 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-f00.zip | |
33.995 | Study on security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.995/33995-f00.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 15.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-f20.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures for use in UE conformance tests. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 15.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-f00.zip | |
33.980 | Liberty Alliance and 3GPP security interworking; Interworking of Liberty Alliance Identity Federation Framework (ID-FF), Identity Web Services Framework (ID-WSF) and Generic Authentication Architecture (GAA) | TR | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-f00.zip | |
33.926 | Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes | TR | 15.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.926/33926-f20.zip | The present document captures the network product class descriptions, threats and critical assets that have been identified in the course of the work on 3GPP security assurance specifications. The main body of the present document contains generic aspects that are believed to apply to more than one network product class, while Annexes cover the aspects specific to one network product class. |
34.121-1 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification | TS | 15.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-f40.zip | The present document specifies the UTRA measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode. In addition it specifies conformance testing of RRM requirements for support of E-UTRA when the UE operates in UTRA mode.
NOTE: Conformance testing of RRM requirements for support of UTRA when the UE operates in E-UTRA mode are specified in TS 36.521-3 [38].
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 15.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-f80.zip | The present document specifies the protocol conformance testing for the 3rd Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- the description of the tests’ procedures, the specific test requirements and the messages exchanged.
The following information relevant to the tests described in the present document can be found in accompanying specifications:
- the default setting of the test parameters [9];
- the applicability of each test case and the Implementation Conformance Statement (ICS) pro-forma [11].
Note: The present document does not contain any tests on the USIM, or the interface between the UE and the USIM. These tests are documented elsewhere.
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.123-2 | User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification | TS | 15.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-f70.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.123-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [45] and the common test environments are included in 3GPP TS 34.108 [44].
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.121-2 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 2: Implementation Conformance Statement (ICS) | TS | 15.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-f10.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.121-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [19] and the common test environments are included in 3GPP TS 34.108 [18] and 3GPP TS 36.508 [29].
The present document is valid for UE implemented according to 3GPP releases starting from Release 99 up to the Release indicated on the cover page of the present document. |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 15.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-f00.zip | |
34.229-2 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification | TS | 15.9.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-f90.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 15.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-f00.zip | |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 15.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-f00.zip | |
34.229-3 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) | TS | 15.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-f80.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-f00.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-f00.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-f00.zip | |
35.205 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-f00.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force. |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-f00.zip | |
35.208 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-f00.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-f00.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-f00.zip | |
35.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-f00.zip | |
35.218 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-f00.zip | |
35.217 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-f00.zip | |
35.222 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 2: ZUC specification | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.222/35222-f00.zip | |
35.223 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 3: Implementors' test data | TS | 15.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.223/35223-f00.zip | |
35.231 | Specification of the TUAK algorithm set: A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: Algorithm specification | TS | 15.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.231/35231-f10.zip | The present document and the other Technical Specifications in the series, TS 35.232 [15] and 35.233 [16] contain an example set of algorithms which could be used as the authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5* for 3GPP systems. All seven functions are operator-specifiable rather than being fully standardised and other algorithms could be envisaged. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.