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 |
|---|---|---|---|---|---|---|
33.511 | Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class | TS | 17.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.511/33511-h60.zip | |
33.512 | 5G Security Assurance Specification (SCAS); Access and Mobility management Function (AMF) | TS | 17.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.512/33512-h30.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 | 17.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.513/33513-h20.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 | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.514/33514-h10.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.515/33515-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.516/33516-h00.zip | |
33.517 | 5G Security Assurance Specification (SCAS) for the Security Edge Protection Proxy (SEPP) network product class | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.517/33517-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.518/33518-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.519/33519-h00.zip | |
33.520 | Security Assurance Specification (SCAS) for Non-3GPP InterWorking Function (N3IWF) | TS | 0.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.520/33520-030.zip | |
33.521 | 5G Security Assurance Specification (SCAS);Network Data Analytics Function (NWDAF) | TS | 17.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.521/33521-h20.zip | |
33.522 | 5G Security Assurance Specification (SCAS); Service Communication Proxy (SCP) | TS | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.522/33522-h10.zip | |
33.535 | Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) | TS | 17.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.535/33535-hc0.zip | |
33.536 | Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services | TS | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.536/33536-h10.zip | |
33.558 | Security aspects of enhancement of support for enabling edge applications | TS | 17.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.558/33558-h30.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.809 | Study on 5G security enhancements against False Base Stations (FBS) | TR | 0.21.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.809/33809-0l0.zip | The present document studies the potential threats and privacy issues associated with false base station scenarios.
The present document identifies the potential solutions for mitigating the risks caused by false base station. |
33.818 | Security Assurance Methodology (SECAM) and Security Assurance Specification (SCAS) for 3GPP virtualized network products | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.818/33818-h10.zip | The present document studies the SECAM (Security Assurance Methodology) and SCAS (Security Assurance Specification) for 3GPP virtualised network products based on SECAM and SCAS defined in TR 33.916 [2]. It makes thorough gap analysis between current SECAM/SCAS work in TR 33.916 [2] and SECAM/SCAS work for 3GPP virtualised network products. It also identifies, defines ToE and roles of SECAM/SCAS for 3GPP virtualised network products according to deployment scenarios and decoupling ways. Based on the identified ToE and roles, the present document details the needed change or additional work to current security assurance methodology for the creation, evaluation procedure of related SCAS documents, etc. It studies new threats of the identified ToE and identifies the additional security requirements of the ToE, or/and identifies existing relevant/supporting requirements specified in ETSI NFV specifications or the equivalent. The present document also provides potential new SECAM/SCAS proposals and points out the impact to existing SECAM/SCAS documents (including TR 33.916 [2], TR 33.926 [3], TS 33.117 [4], etc.).
NOTE: SECAM/SCAS of 3GPP virtualised network products in the present document considers only the scenario that 3GPP VNF deployed in the virtual machines. |
33.824 | Study on Security for Next Radio (NR) Integrated Access and Backhaul (IAB) | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.824/33824-h00.zip | The present document:
- Describes potential security threats and vulnerabilities that are applicable to the enhanced IAB architecture specified in the TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10].
- Identifies potential security requirements for those potential security threats and vulnerabilities.
- Proposes candidate solutions to ensure that the enhanced IAB architecture specified in the 3GPP TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10] does not introduce security vulnerabilities in the 5G system providing a secure connection for the UEs connecting to the NR through IAB node(s).
- Concludes with the solutions that should be included in a future normative phase. |
33.839 | Study on security aspects of enhancement of support for edge computing in the 5G Core (5GC) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.839/33839-h10.zip | The present document studies the security enhancements on the support for Edge Computing in the 5G Core network define in TR 23.748 [3], and application architecture for enabling Edge Applications defined in TR 23.758 [4] and TS 23.558 [2].
Potential security requirements are provided and possible security enhancements to 5GS and edge application architecture are proposed that meet these security requirements.
NOTE: The user consent for exposure of information to Edge Applications is addressed in TR 33.867 [20]. |
33.845 | Study on storage and transport of 5G Core (5GC) security parameters for Authentication Credential Repository Processing Function (ARPF) authentication | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.845/33845-h00.zip | The present document details the following:
- The security assumptions relating to security communication in 5G.
- The security assumptions related to protecting subscriber privacy.
- The home network parameters that are relevant to securing the communication in 5G and protecting subscriber privacy.
- Key Issues, threats and requirements relevant to securing the communication in 5G and protecting subscriber privacy.
- Solutions that potentially resolve the key issues described.
The present document does not describe the storage of security parameters in the UE or the serving network or the transportation of secure information between the home network and the serving network. |
33.846 | Study on authentication enhancements in the 5G System (5GS) | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.846/33846-h00.zip | The scope of the present document is the following:
- key issues, potential security requirements and solutions of how to enhance the authentication process to ensure the security of session anchor keys in case the long-term key is leaked.
- key issues, potential security requirements and solutions of how to mitigate the linkability attacks.
- key issues, potential security requirements and solutions of how to mitigate the impacts of potential DDoS threats due to concealing the SUPI.
- key issues, potential security requirements and solution of how to mitigate the leaking of SQN values during AKA re-synchronisation. |
33.847 | Study on security aspects of enhancement for proximity based services in the 5G System (5GS) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.847/33847-h10.zip | The present document studies the security and privacy aspects of proximity based services (including public safety and commercial proximity services) in the 5G system. It ensures that the security solutions are aligned with the work in TR 23.752 [2], TS 22.278 [3] and TS 22.261 [4]. The present document covers the following issues:
- Security and privacy key issues, threats and potential requirements of proximity based services in 5G system.
- Potential security solutions to cover these potential requirements.
Both roaming and non-roaming scenarios are considered. |
33.850 | Study on security aspects of enhancements for 5G Multicast-Broadcast Services (MBS) | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.850/33850-h00.zip | The present document studies the security of 5G multicast-broadcast services based on FS_5MBS study in TR 23.757 [2]. Potential security requirements are identified and possible security solutions are proposed to address these security requirements. |
33.851 | Study on security for enhanced support of Industrial Internet of Things (IIoT) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.851/33851-h10.zip | The present document studies the security impact of time sensitive communication aspects in Industrial IoT based on FS_IIoT study in TR 23.700-20 [4] and the architecture described in 3GPP TS 23.501 [3]. |
33.853 | Study on key issues and potential solutions for integrity protection of the User Plane (UP) | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.853/33853-h00.zip | The present document studies the key issues and potential solutions for integrity protecting the user plane, including potential enhancements needed to support UP IP up to the full data rate, in the following combinations as defined in 3GPP TR 38.801 [2] (clause 7.2):
- Option 1 - eUTRA with EPC
- Option 2 - NR standalone with 5G Core
- Option 3 - EPC based Dual Connectivity of eUTRA and NR RAT
- Option 4 - 5G Core based Dual Connectivity (NR master - eUTRA secondary)
- Option 5 - 5G Core with eUTRA
- Option 7 - 5G Core based Dual Connectivity (eUTRA master - NR secondary)
The present document does not detail key issues, solutions, evaluations, conclusions and recommendations for GERAN and UTRAN. |
33.854 | Study on security aspects of Uncrewed Aerial Systems (UAS) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.854/33854-h10.zip | The present document contains a study on the security aspects of Uncrewed Aerial Systems (UASs). TS 22.125 [2] contains the service requirements for UAS while TR 23.754 [3] is studying aspects like the UAS connectivity, identification and tracking and TR 23.755 [4] studies UAV services and application layer features. The security study of the present document provides key issue including security threat and potential requirements related to the work in these other specifications and develops and analyses solutions to these key issues. Finally the study provides some conclusions for potential normative work. |
33.857 | Study on enhanced security support for Non-Public Networks (NPN) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.857/33857-h10.zip | The aim of the present document is to study the security aspects for any potential enhancements based on the outcome of the study in TR 23.700-07 [3]. For each of the objectives in the scope of the study in TR 23.700-07 [3], the security aspects that are to be covered in the present document are as follows:
- Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN
- Study potential solutions for authentication using credentials owned by an entity separate from the SNPN
- UE Onboarding and remote provisioning of non-USIM credentials
- Identify security Key Issues relating to UE Onboarding and remote provisioning with non-USIM credentials
- Identify methods by which the UE can be verified as "uniquely identifiable and verifiably secure"
- Critically review the security aspects of the proposed solutions in TR 23.700-07 [3] and make recommendations for security improvements where required.
- Study potential solutions for the secure provisioning of non-USIM credentials taking into account different deployment scenarios.
NOTE 1: The term USIM in this context denotes the IMSI accompanied by AKA credentials (i.e. for primary authentication with the PLMN).
- Support of IMS voice and emergency services for SNPN:
- Analyse potential security impacts from supporting IMS voice and IMS services in SNPNs. In Rel-16 SNPNs do not support IMS emergency services but for Rel-17 its expected that the enabling of IMS and IMS services for SNPNs is to be studied.
NOTE 2: Key issue 2 in TR 23.700-07 [3] is assumed to not require any study from a security perspective. |
33.862 | Study on security aspects of the Message Service for MIoT over the 5G System (MSGin5G) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.862/33862-h10.zip | The present document studies the security aspects on the support of the 5GMSG Service defined in TR 23.700-24 [2], determines key issues of potential security requirements and proposed possible security solutions to meet these security requirements. |
33.864 | Study on the security of Access and Mobility Management Function (AMF) re-allocation | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.864/33864-h00.zip | The present document aims at addressing the case for the indirect reroute procedure for UE registration. The intention is to enable deployment scenarios with stricter slice isolation requirements on the core network, for example where the AMFs are unable to communicate with each other.
The aim of the present document is to:
- Collect the potential requirements related to the AMF re-allocation procedure.
- Study the potential enhancements to the security mechanisms in order to fulfil the requirements for the AMF re-allocation. |
33.866 | Study on security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) Phase 2 | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.866/33866-h00.zip | The present document studies the security aspects of enablers for network automation for the 5G system based on the outcome of TR 23.700-91 [1]. More specifically, the present document identifies security issues, requirements and corresponding potential security solutions related to the following objectives:
- UE data collection protection to fulfil the NWDAF functionalities including privacy consideration, data authenticity, data integrity, and accessibility aspects requirements.
- Detection of cyber-attacks and anomaly events supported by NWDAF and its related functions, specifically to identify parameters provided by UE and NFs, which can help to detect attacks and abnormal behaviours;
- Protection of data transferring (e.g. privacy consideration) in the inter-NWDAF/NWDAF instances.
NOTE: The user consent for UE data collection is not addressed in the present document, it will be discussed in TR 33.867 [2]. |
33.867 | Study on user consent for 3GPP services | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.867/33867-h10.zip | The scope of present document is to identify and evaluate the requirements and solutions to support user consent for 3GPP services while complying with user privacy considerations.
The details are as follows:
- Review TR 33.849 [3] with regards to the concept of user consent for 3GPP users, and identify what types of data collection and conditions under which the support of the user consent is required; then update them if needed.
- Identify target usage scenarios and trust domains.
- Analyse potential security threats and requirements for conditions under which user sensitive data are collected without user consent, and when user consent indication is not protected.
- Identify potential solutions to address the above security requirements.
NOTE 1: Principles, regulations, and definitions related to privacy, which are recognized differently in each different country or area, are taken into account when deriving the concept of user consent for 3GPP users.
NOTE 2: Even where solutions exist to obtain user consent, collection and exposure of user sensitive data should be minimized and only be allowed where critical to the operation of the related feature. |
33.873 | Study on the security of the system enablers for devices having Multiple Universal Subscriber Identity Modules (MUSIM) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.873/33873-h10.zip | The present document contains the study of system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) in the EPS and 5G system architecture are studied in 3GPP TR 23.761 [2]. The present document provides the security and privacy issues related to MUSIM architecture and lists potential solutions for identified key issues including.
- Security and privacy issues exposing the Paging Cause in clear text in paging message.
- Security aspects of the communication between UE and Paging Server and exposing Paging server address.
- Security and Privacy implications if a Multi-USIM device needs to explicitly indicate to the MNO owning one USIM and that UE is also registered via another USIM at the same or different PLMNs.
- Security aspects of Paging Response with cause value busy indication.
Finally, the present document provides some conclusions for potential normative work. |
33.874 | Study on enhanced security for network slicing phase 2 | TR | 0.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.874/33874-070.zip | The present document identifies key issues, potential security and privacy requirements and solutions with respect to network slicing Phase 2 work TS 23.501 [2], TS 23.502 [3], TS 23.503 [4] and studies TR 23.700-40 [5] and TR 38.832 [6], specifically,
- Define the security requirements and security services for new NF(s) introduced for UEs' network slice access control.
- Study potential security risks/threats (i.e. DoS, sensitive information leakage) and solutions if needed with respect to slice-related quota management, data rate limitation, and constraints on simultaneous use of slices.
- Study potential security risks/threats related to broadcasting slice-related cell selection/reselection info, and provide security solutions if needed. |
33.875 | Study on enhanced security aspects of the 5G Service Based Architecture (SBA) | TR | 1.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.875/33875-170.zip | The present document studies enhanced security aspects of the 5G Service Based Architecture. It will analyse potential threats, study necessary security enhancements, and document decisions of solutions to be adopted or not adopted after evaluating the risks versus the complexity.
In particular, the following topics are addressed:
- Need and mechanism of enabling end to end authentication in roaming case if no cross-certification between operators is enabled;
- Need and mechanism of enabling NF Service Consumer authentication of NRF and the NF Service Producer;
- Need for addressing potential security impact of different deployment scenarios including the several SCPs;
- Verification of URI in subscription/notification;
- Dynamic authorization between SCPs or NF and SCP;
- End-to-End Critical HTTP headers/body parts integrity protection;
- Access token usage in NF Sets;
- Authorization mechanism determination;
- Security of NRF service management;
- Inter-Slice access authorization;
- N32 roaming security considerations for deployment scenarios including roaming hub and hosted SEPP. |
33.876 | Study on automated certificate management in Service-Based Architecture (SBA) | TR | 0.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.876/33876-080.zip | The objectives of this study are to identify key issues, potential security and privacy requirements and solutions with respect to
- Standardise the use of a single automated certificate management protocol and procedures for certificate life cycle events within intra-PLMN 5G SBA (i.e. to be used by all 5GC NFs including NRF, SCP, SEPP etc.).
- Study the impact of service mesh in certificate management within 5G SBA.
- Study which lifecycle events (e.g., enrolment, renewal, revocation (e.g., OCSP, CRLs), status monitoring) of a certificate need to be covered.
- Study the relation between certificate management lifecycle and NF management lifecycle.
- Study to reference at minimum following principles:
- Principle to be reusable when 5G SBA is for NPN (standalone and PNI)
- Principles standardised to be able to support NFs doing mutual TLS in Slicing.
- Principles standardised to support both intra and inter PLMN, in the latter referring to SEPP certificates in N32 interfaces and potential cross-certification considerations.
- Principles involving 'Chain of Trust' of Certificate Authorities hierarchies.
- Principles for security of CA's cryptographic private key. |
33.881 | Study on Non-Seamless WLAN Offload (NSWO) in 5G System (5GS) using 3GPP credentials | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.881/33881-h10.zip | The scope of the present document is to support Non-seamless WLAN Offload (NSWO) in 5GS. The following will be studied in this document:
1) Solutions to support NSWO in 5GS.
2) Procedures to support authentication methods for the respective solutions in objective.
3) Maintain privacy of subscription identifier similar to 3GPP/non-3GPP access to 5GC, even for NSWO authentication from WLAN. |
33.905 | Recommendations for Trusted Open Platforms | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-h00.zip | |
33.916 | Security Assurance Methodology (SECAM) for 3GPP network products | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-h00.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-h00.zip | |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-h00.zip | |
33.926 | Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes | TR | 17.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.926/33926-h90.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. |
33.935 | Study on detailed Long Term Key Update Process (LTKUP) detailed solutions | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.935/33935-h00.zip | |
33.937 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-h00.zip | |
33.969 | Study on security aspects of Public Warning System (PWS) | TR | 17.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-h10.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-h00.zip | |
33.995 | Study on security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.995/33995-h00.zip | |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-h00.zip | |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 17.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-h10.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 17.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-h00.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 | 17.3.1 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-h31.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 | 17.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-h70.zip | |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-h00.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-h00.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-h00.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-h00.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-h00.zip | |
35.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-h00.zip | |
35.216 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-h00.zip | |
35.217 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-h00.zip | |
35.218 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-h00.zip | |
35.221 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.221/35221-h00.zip | |
35.222 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 2: ZUC specification | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.222/35222-h00.zip | |
35.223 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 3: Implementors' test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.223/35223-h00.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 | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.231/35231-h00.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. |
35.232 | 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 2: Implementers’ test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.232/35232-h00.zip | |
35.233 | 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 3: Design conformance test data | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.233/35233-h00.zip | |
35.909 | 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 5: Summary and results of design and evaluation | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-h00.zip | |
35.919 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-h00.zip | |
35.924 | Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 4: Design and Evaluation Report | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.924/35924-h00.zip | |
35.934 | 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 4: Report on the design and evaluation | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.934/35934-h00.zip | |
35.935 | 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 5: Performance evaluation | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.935/35935-h00.zip | |
35.936 | 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 6: Security assessment | TR | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.936/35936-h00.zip | |
36.106 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater radio transmission and reception | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.106/36106-h00.zip | |
36.111 | Location Measurement Unit (LMU) performance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.111/36111-h00.zip | |
36.112 | Location Measurement Unit (LMU) conformance specification; Network based positioning systems in Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.112/36112-h00.zip | |
36.113 | Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC) | TS | 17.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.113/36113-h30.zip | |
36.116 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.116/36116-h00.zip | |
36.117 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay conformance testing | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.117/36117-h00.zip | |
36.124 | Evolved Universal Terrestrial Radio Access (E-UTRA); Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 17.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.124/36124-h10.zip | |
36.143 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing | TS | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.143/36143-h00.zip | |
36.171 | Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for Support of Assisted Global Navigation Satellite System (A-GNSS) | TS | 17.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.171/36171-h30.zip | |
36.201 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description | TS | 17.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.201/36201-h00.zip | |
36.214 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements | TS | 17.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.214/36214-h00.zip | |
36.216 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for relaying operation | TS | 17.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.216/36216-h00.zip | |
36.302 | Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the physical layer | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.302/36302-h00.zip | |
36.304 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode | TS | 17.6.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.304/36304-h60.zip | |
36.305 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN | TS | 17.3.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.305/36305-h30.zip | |
36.306 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities | TS | 17.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.306/36306-ha0.zip | |
36.307 | Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band | TS | 17.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.307/36307-h70.zip | The present document specifies requirements for Rel-18 UEs supporting release independent features like:
- additional E-UTRA operating frequency bands on top of Rel-18 of TS 36.101 [2], TS 36.102 [6] and TS 36.133 [3];
- additional E-UTRA CA configurations (intra-band/inter-band) on top of Rel-18 of TS 36.101 [2] and TS 36.133 [3];
- additional operating bands and/or CA configurations for specific features (like UE category 0, M1, NB1);
- other release independent features (like 4Rx antenna port, high speed scenario, 8Rx antenna port, NB-IoT or eMTC operation over NTN). |
36.314 | Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.314/36314-h00.zip | |
36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | TS | 17.7.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.321/36321-h70.zip | |
36.322 | Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.322/36322-h00.zip | |
36.323 | Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification | TS | 17.2.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.323/36323-h20.zip | |
36.355 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP) | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.355/36355-h00.zip | |
36.360 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.360/36360-h00.zip | |
36.361 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Radio Level Integration Using Ipsec Tunnel (LWIP) encapsulation; Protocol specification | TS | 17.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.361/36361-h00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.