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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.455/32455-e00.zip | |
32.500 | Telecommunication management; Self-Organizing Networks (SON); Concepts and requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.500/32500-e00.zip | |
32.501 | Telecommunication management; Self-configuration of network elements; Concepts and requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.501/32501-e00.zip | |
32.502 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Information Service (IS) | TS | 14.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.502/32502-e11.zip | |
32.506 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.506/32506-e10.zip | |
32.508 | Telecommunication management; Procedure flows for multi-vendor plug-and-play eNode B connection to the network | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.508/32508-e00.zip | The present document describes the procedure flows between network entities involved in the
multi-vendor plug-and-play eNB connection to network.
These procedures are based on requirements and use cases specified in 3GPP TS 32.501 [4].
The format of the data exchanged in these procedures is defined in 3GPP TS 32.509 [5]. |
32.407 | Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.407/32407-e00.zip | |
32.511 | Telecommunication management; Automatic Neighbour Relation (ANR) management; Concepts and requirements | TS | 14.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.511/32511-e20.zip | |
32.531 | Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.531/32531-e00.zip | |
32.532 | Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS) | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.532/32532-e00.zip | |
32.536 | Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.536/32536-e10.zip | |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-e00.zip | |
32.551 | Telecommunication management; Energy Saving Management (ESM); Concepts and requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.551/32551-e00.zip | |
32.571 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.571/32571-e00.zip | |
32.572 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.572/32572-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.581/32581-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.582/32582-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.583/32583-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.584/32584-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.591/32591-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.593/32593-e00.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 | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.594/32594-e00.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-e00.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-e00.zip | |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-e00.zip | |
32.606 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.606/32606-e10.zip | |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-e00.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-e00.zip | |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-e10.zip | |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-e00.zip | |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-e00.zip | |
32.666 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.666/32666-e10.zip | |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-e00.zip | |
32.817 | Study on management of measurement collection in network sharing context | TR | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.817/32817-e10.zip | The study is to investigate:
- Solutions for how to manage measurement collection in network sharing context over Itf-N.
- Solutions for how to indicate high reliability to different E-UTRAN measurements.
- Whether the PM file format would need to be changed and possible solutions.
The solution is intended to be valid for data volume measurements, but a more generically applicable solution should be considered, if feasible. The solution can be valid also for non-shared networks. |
32.838 | Telecommunication management; Gap analysis between 3GPP SA5 specifications and NGMN Top Operational Efficiency (OPE) recommendations | TR | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.838/32838-e10.zip | The present document provides a gap analysis between NGMN Top OPE Recommendations [2] and OAM capabilities offered by 3GPP SA5 Integration Reference Points (IRPs).
Based on this gap analysis, it provides a support status of SA5 specifications against NGMN Top OPE Recommendations. For each Top OPE Recommendation, the SA5 solution is described when it exists. Otherwise, some action may be considered to address the Top OPE recommendation.
Based on that information, a support status is produced which can take the following values:
- Supported,
- Partially Supported,
- Not Supported,
- Not Applicable. |
32.850 | Study on determination of completeness of charging information in IMS | TR | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.850/32850-e00.zip | The objective of this study item is to identify and document methods to guarantee that all the relevant charging data for an IMS session has been received in order to charge the IMS session correctly.
Within the study scenarios could be covered where a concatenation of applications leads to an correlation of charging relevant information.
In addition a method to identify all network elements generating CDR for offline charging within an IMS call in order to serve for an effective and accurate IMS Charging correlation is in focus of this study.
The following scenarios are be covered this study:
• IMS calls where the service invocation is done in the originating and/or terminating home network. Scenarios to be considered should cover different network scenarios like roaming, transit, PSTN interworking, intra home network or home-a to home-b network. IMS Calls where a concatenation of applications appear. The invoked applications can be provided by AS from different networks.
• IMS Calls where an Application Server hosts several applications invoked during one call.
- IMS Calls where call leg manipulation apply and more than one application is involved.
• IMS Calls where only several IMS network elements are necessary to generate charging information based on operator's configuration.
• IMS Other scenarios where a correlation of charging relevant information created by application servers is needed.
The study will identify recommended enhancements to the charging architecture, message and CDR content, and internode signalling.
It will analyse operator requirements in consideration of the roaming scenarios and the existing charging specifications.
The conclusions are presented in a further section with assumptions made and proposed further proceedings on that issues. |
32.855 | Study on OAM support for Licensed Shared Access (LSA) | TR | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.855/32855-e00.zip | The present document studies the architecture, the interfaces and solutions with regards to Licensed Shared Access, LSA ETSI TS 103 154 [5] relevant to a 3GPP mobile network operator. The study includes:
- Study how the solution and architecture defined in ETSI TS 103 235 [3] may provide a global solution.
- Study the impact on the 3GPP management reference model defined in 3GPP TS 32.101 [2].
- Analyse the LSA functionalities and the information flow defined in ETSI TS 103 235 [3] towards a 3GPP mobile network operator and any impact on Itf-N.
- Study how to support the static and semi-static spectrum sharing scenarios and reference use case defined in ETSI TR 103 113 [4].
Interfaces and functionality specified for LSA that are not involving the 3GPP mobile network operator are out of scope for this study. |
32.860 | Telecommunication management; Study on enhancements of Operations, Administration and Maintenance (OAM) aspects of distributed Self-Organizing Networks (SON) functions | TR | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.860/32860-e00.zip | The present document aims the following:
- Identify whether Distributed SON (D-SON) Mobility Load Balancing (MLB) as currently specified in 3GPP can be improved;
- In case potential areas of improvement are identified, propose possible solutions. |
32.862 | Study on Key Quality Indicators (KQIs) for service experience | TR | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.862/32862-e00.zip | The present document will address:
1) Service KQI scenarios
2) Service KQIs corresponding to the identified scenarios
KQIs will be described for the below services:
- Bidirectional voice
- Unidirectional voice streaming
- Unidirectional video streaming
- Short Messaging
- Multimedia Messaging
- Web browsing
- File transfer
- E-mail
The present document will consider already defined metrics and requirements from:
- NGMN NGCOR phase 2 requirements
- ETSI TS 102.250
- 3GPP TR 26.944
- NGMN P-SERQU
- QuEST Forum TL9000 |
32.864 | Telecommunication management;Study on management aspects of virtualized network functions that are part of the New Radio (NR) | TR | 0.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.864/32864-050.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.866 | Telecommunication management;Study on a REST(REpresentational State Transfer)-ful HTTP-based Solution Set (SS) | TR | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.866/32866-030.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 | 0.5.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.867/32867-051.zip | |
32.869 | Telecommunication management; Charging management; Study on Overload Control for Diameter Charging Applications | TR | 0.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.869/32869-080.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.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-e00.zip | |
33.102 | 3G security; Security architecture | TS | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-e10.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 | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-e00.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-e10.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 14.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-e70.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 14.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-e60.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 | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-e00.zip | |
33.116 | Security Assurance Specification (SCAS) for the MME network product class | TS | 14.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.116/33116-e20.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 | 14.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.117/33117-e60.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.141 | Presence service; Security | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-e00.zip | |
32.509 | Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.509/32509-e00.zip | The present document describes the data formats used between network entities involved in the multi-vendor plug and play eNB connection to network.
These data formats are based on requirements and use cases specified in 3GPP TS 32.501 [4].
The procedure flows where these data exchanged are defined in 3GPP TS 32.508 [5]. |
33.185 | Security aspect for LTE support of Vehicle-to-Everything (V2X) services | TS | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.185/33185-e10.zip | |
32.422 | Telecommunication management; Subscriber and equipment trace; Trace control and configuration management | TS | 14.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.422/32422-e20.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 14.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-e30.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 | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-e00.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-e00.zip | |
33.216 | Security Assurance Specification (SCAS) for the evolved Node B (eNB) network product class | TS | 0.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.216/33216-040.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 | 14.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-e20.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-e00.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-e00.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-e00.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-e00.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-e00.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 14.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-e20.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 | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.250/33250-e10.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.187 | Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TS | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-e10.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-e00.zip | |
31.970 | UICC power optimisation for Machine-Type Communication (MTC) | TR | 14.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.970/31970-e00.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-e00.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-e10.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 14.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-e60.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 14.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-e30.zip | |
33.827 | Study on providing for Lawful Interception (LI) in the S8 Home Routeing (S8HR) architecture for Voice over LTE (VoLTE) | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.827/33827-e00.zip | The present document studies and identifies the changes to the LI architecture, function and protocols for inbound roamers in the VPLMN when S8HR is employed which is equivalent to the LI service level for Local Breakout (LBO) in the VPLMN for VoLTE services. Covered by the present document includes:
- Potential enhancements to the LI service architecture to accommodate the S8HR roaming architecture in the VPLMN to meet all the current LI regulatory requirements applicable to voice and other IMS service roaming are considered and compared.
- Considerations on maximizing re-use of existing 3GPP defined capabilities such as PCC is considered.
- Exploration of the changes that may be needed to TS 33.107 [3] and TS 33.108 [4].
Finally, the present document provides recommendations for proceeding with implementing the selected approach.
This study item takes into account GSMA related activities. |
33.849 | Study on subscriber privacy impact in 3GPP | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.849/33849-e00.zip | The present document studies the subscriber privacy impact in 3GPP. In particular, the goals of the present document are:
- Identify and understand privacy related key issues impacting 3GPP networks.
- Identify and potentially harmonize privacy requirements, e.g. MDT/SON.
- Identify existing/ongoing work relevant to 3GPP privacy issues in external standard bodies, for potential reuse in 3GPP, e.g. IETF RFC 6973 [2].
- Identify privacy risk mitigation approaches and establish privacy handling guidelines/principle and/or best practices for 3GPP for future specifications.
It is not an objective of the study to examine all existing 3GPP specifications in retrospect with respect to privacy.
NOTE: The result of this study is captured in Annex F. |
33.863 | Study on battery efficient security for very low throughput Machine Type Communication (MTC) devices | TR | 14.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.863/33863-e20.zip | The present document's objectives are to:
a) Investigate whether battery efficient 'device to enterprise' mechanisms to provide sufficient security exist.
b) Investigate potential enhancements to 3GPP's security architecture(s) that enable the Home Operator to be able to offer well guaranteed security to enterprises e.g. to provide security between the UE and a node in the home operator domain.
c) Both S1 and Gb based architectures should be considered when undertaking b, above.
The impacts of relevant authentication and key agreement procedures are also presented.
The following should be taken into account for the study:
- The potential solutions should aim at minimising the energy consumption of devices to help meet the objective of a ten year battery life in the extended coverage situation and take into consideration the very low data rate capability of the radio interface when using the Energy Consumption Evaluation Methodology described in TR 45.820. |
33.880 | Study on mission critical security enhancements | TR | 1.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.880/33880-160.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.885 | Study on security aspects for LTE support of Vehicle-to-Everything (V2X) services | TR | 14.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.885/33885-e10.zip | The present document contains a study of the security aspects of V2X services and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.185 [2]. Potential stage 2 solutions for V2X Services are being studied in TR 23.785[3]. |
33.905 | Recommendations for Trusted Open Platforms | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-e00.zip | |
33.916 | Security Assurance Methodology (SECAM) for 3GPP network products | TR | 14.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-e40.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-e00.zip | |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-e00.zip | |
33.926 | Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.926/33926-e00.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.937 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-e00.zip | |
33.969 | Study on security aspects of Public Warning System (PWS) | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-e00.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 | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-e00.zip | |
33.995 | Study on security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.995/33995-e00.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 14.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-e30.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 | 14.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-e00.zip | |
34.121-1 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification | TS | 14.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-e40.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.121-2 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 2: Implementation Conformance Statement (ICS) | TS | 14.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-e20.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.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 14.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-e60.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 | 14.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-e50.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.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 14.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-e00.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 14.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-e00.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 | 14.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-e80.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 | 14.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-e60.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.