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.422 | Telecommunication management; Subscriber and equipment trace; Trace control and configuration management | TS | 13.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.422/32422-d20.zip | |
32.423 | Telecommunication management; Subscriber and equipment trace; Trace data definition and management | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.423/32423-d10.zip | |
32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | TS | 13.6.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.425/32425-d61.zip | |
32.426 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Packet Core (EPC) network | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.426/32426-d10.zip | |
32.432 | Telecommunication management; Performance measurement: File format definition | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.432/32432-d00.zip | |
32.435 | Telecommunication management; Performance measurement; eXtensible Markup Language (XML) file format definition | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.435/32435-d00.zip | |
32.436 | Telecommunication management; Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.436/32436-d00.zip | |
32.441 | Telecommunication management; Trace Management Integration Reference Point (IRP); Requirements | TS | 13.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.441/32441-d01.zip | |
32.442 | Telecommunication management; Trace Management Integration Reference Point (IRP); Information Service (IS) | TS | 13.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.442/32442-d01.zip | |
32.446 | Telecommunication management; Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.446/32446-d01.zip | |
32.450 | Telecommunication management; Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN): Definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.450/32450-d10.zip | |
32.451 | Telecommunication management; Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.451/32451-d00.zip | |
32.452 | Telecommunication management; Performance Management (PM); Performance measurements Home Node B (HNB) Subsystem (HNS) | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.452/32452-d00.zip | |
32.453 | Telecommunication management; Performance Management (PM); Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS) | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.453/32453-d00.zip | |
32.454 | Telecommunication management; Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS); Definitions | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.454/32454-d00.zip | |
32.455 | Telecommunication management; Key Performance Indicators (KPI) for the Evolved Packet Core (EPC); Definitions | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.455/32455-d00.zip | |
32.500 | Telecommunication management; Self-Organizing Networks (SON); Concepts and requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.500/32500-d00.zip | |
32.501 | Telecommunication management; Self-configuration of network elements; Concepts and requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.501/32501-d00.zip | |
32.502 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Information Service (IS) | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.502/32502-d10.zip | |
32.506 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.506/32506-d10.zip | |
32.508 | Telecommunication management; Procedure flows for multi-vendor plug-and-play eNode B connection to the network | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.508/32508-d00.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.509 | Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.509/32509-d00.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]. |
32.511 | Telecommunication management; Automatic Neighbour Relation (ANR) management; Concepts and requirements | TS | 13.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.511/32511-d20.zip | |
32.531 | Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.531/32531-d00.zip | |
32.532 | Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS) | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.532/32532-d00.zip | |
32.536 | Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.536/32536-d10.zip | |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 13.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-da0.zip | |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-d00.zip | |
32.366 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.366/32366-d10.zip | |
32.572 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.572/32572-d00.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.581/32581-d00.zip | |
32.571 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements | TS | 13.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.571/32571-d01.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.583/32583-d00.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.582/32582-d00.zip | |
32.551 | Telecommunication management; Energy Saving Management (ESM); Concepts and requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.551/32551-d00.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.584/32584-d00.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 | 13.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.591/32591-d01.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 | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-d10.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-d00.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-d00.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.593/32593-d00.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-d00.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 | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.594/32594-d00.zip | |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-d10.zip | |
32.606 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.606/32606-d10.zip | |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-d00.zip | |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-d00.zip | |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-d00.zip | |
32.838 | Telecommunication management; Gap analysis between 3GPP SA5 specifications and NGMN Top Operational Efficiency (OPE) recommendations | TR | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.838/32838-d10.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.842 | Telecommunication management; Study on network management of virtualized networks | TR | 13.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.842/32842-d10.zip | The present document studies the network management of virtualized 3GPP specified core networks based on the architectural framework in ETSI GS NFV-MAN 001 [2]. It studies the network management of mobile networks that include virtualized core networks functions.
It also identifies the potential impacts on the existing 3GPP management architecture and to propose potential solutions for the network management of fully virtualized networks and mixed networks.
The objectives of this study are:
- Study the use cases and concepts for the network management of virtualized networks, which are applicable to 3GPP, taking into account the relevant use cases from ETSI.
- Analyse and classify the network management scenarios when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Analyse and classify the network management scenarios when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks). Study whether or not a single management system for mixed networks is required.
- Identify the potential impacts on the existing 3GPP Management reference model.
- Analyse the existing 3GPP Management reference model, interfaces, protocols and procedures to determine what can be re-used, adapted or extended and whether new IRPs are needed for network management of virtualized networks.
- Propose enhancements or extensions to the 3GPP Management reference model, if an impact is foreseen.
- If needed, solution(s) for a single management system for mixed networks should be studied.
- Provide recommendations for the standardization of the network management of fully virtualized networks and mixed networks, based on the result of the analysis and the potentially identified impacts, enhancements or extensions. |
32.843 | Telecommunication management; Charging management; Study on Inter-Public-Land-Mobile-Network (PLMN) Packet Switched (PS) domain online charging | TR | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.843/32843-d00.zip | The present document studies PS domain Online Charging in a roaming context, when the Gateway node implementing the IP access to the PDN for data traffic, pertains to the VPLMN, whereas the Online Charging System (OCS) pertains to the HPLMN.
The study will focus, in a first phase, on high level scenarios for Flow Based Charging, relying on defined TS 23.203 [207] PCC roaming architectures with Gy crossing PLMNs, in order to investigate the following aspects:
- Information availability in both PLMNs
- Inter-PLMN connection mechanisms for Diameter messages
- Impacts on Inter-operator charging
- Whether a "proxy OCS" is needed
The two following configurations will be addressed:
- Gy between OCS residing in HPLMN and PCEF located in PGW VPLMN, for Local Breakout Roaming configuration defined by TS 23.401 [208] and TS 23.203 [207].
- Gy between OCS residing in HPLMN and PCEF located in IP-Edge fixed broadband access owned by a Convergent fixed-mobile VPLMN, for Non Seamless WLAN Offload (NSWO) 3GPP UEs traffic defined by annex S of TS 23.203 [207].
During this first phase, the study will also investigate a basic set of Online Charging features and parameters, to be used in an inter-PLMN situation.
Based on conclusions and recommendations for the first phase, the second phase of the study will address the inter-PLMN Gyn Reference Point for the support of Application Based Charging. |
32.849 | Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks | TR | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-d00.zip | The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues. |
32.850 | Study on determination of completeness of charging information in IMS | TR | 2.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.850/32850-200.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 | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.855/32855-100.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.861 | Telecommunication management; Study on application and partitioning of Interface N (Itf-N) | TR | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.861/32861-d00.zip | The present document examines IRP requirements selected from existing IRPs' requirement and identifies one or more subsets of these requirements. It also studies the grouping of IRP functionality to recommend which functionality is needed in a network management context to satisfy every given subset of requirements. |
32.862 | Study on Key Quality Indicators (KQIs) for service experience | TR | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.862/32862-100.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.863 | Telecommunication management; Fixed Mobile Convergence (FMC) metadefinitions for measurements and Key Performance Indicators (KPIs) | TR | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.863/32863-d00.zip | The present document defines the metadata for Performance Management (PM) performance measurements (KPIs/counters). The definition would enforce consistency in description/definition of all standardized performance measurements (counters/KPIs) by various SDOs and organizations (or Multi-SDO) involved in the Management of Converged Networks [6]. This consistency would facilitate encoding and decoding of performance measurements (counters/KPIs) exchanged (via management protocols) and/or stored in (database or files).
The metadata related to PM operations/notifications is not part of this PM measurement metadata.
The present document takes into account the recommendations from the Fixed Mobile Convergence (FMC) model repertoire [2] developed by the Multi-SDO JWG on Model Alignment. |
32.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 13.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-d00.zip | |
33.102 | 3G security; Security architecture | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-d00.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 | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-d00.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 13.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-d40.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 13.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-d80.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 13.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-d70.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 | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-d00.zip | |
33.116 | Security Assurance Specification (SCAS) for the MME network product class | TS | 1.3.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.116/33116-131.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 | 1.4.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.117/33117-141.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 | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-d00.zip | |
33.179 | Security of Mission Critical Push To Talk (MCPTT) over LTE | TS | 13.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.179/33179-dc0.zip | The present document specifies the security architecture, procedures and information flows needed to protect the mission critical push to talk (MCPTT) service. The architecture includes mechanisms for authentication, protection of MCPTT signalling and protection of MCPTT media. Security for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The functional architecture for MCPTT is defined in 3GPP TS 23.179 [2], the corresponding service requirements are defined in 3GPP TS 22.179 [3].
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. As the security model is based on the public safety environment, some security features may not be applicable to MCPTT for commercial purposes. |
33.187 | Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TS | 13.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-d01.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 13.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-d40.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 | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-d00.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-d00.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 13.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-d20.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-d00.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-d00.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-d10.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-d10.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-d10.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-d10.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.259 | Key establishment between a UICC hosting device and a remote device | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-d00.zip | |
33.303 | Proximity-based Services (ProSe); Security aspects | TS | 13.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.303/33303-d50.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 13.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-d20.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-d00.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-d10.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 13.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-d50.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-d10.zip | |
33.832 | Study on IMS Enhanced Spoofed Call Prevention and Detection | TR | 0.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.832/33832-030.zip | The present document evaluates the IETF STIR working group active drafts for use in 3GPP networks for spoofed call detection and make recommendations on what aspects of IETF STIR active drafts should be incorporated into 3GPP IMS security specifications.
Additionally 3GPP technology specific aspects not considered or addressed in the IETF STIR Working Group will be identified and studied such as service interactions and deployment scenarios including (but not limited to):
• * Roaming
• * Business line trunking/PBX
• * CS to IMS transition scenarios |
33.833 | Study on security issues to support Proximity Services (ProSe) | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-d00.zip | The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document. |
33.849 | Study on subscriber privacy impact in 3GPP | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.849/33849-110.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.860 | Study on Enhanced General Packet Radio Service (EGPRS) access security enhancements with relation to cellular Internet of Things (IoT) | TR | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.860/33860-d10.zip | The present document contains a study of the EGPRS access security in relation to cellular IoT, and an evaluation of possible technical security enhancements needed to support such services. Different possible deployment scenarios for Cellular IoT, and related stage 2 solutions are being studied in TR 45.820 [2].
The scope of this study is limited to investigate the feasibility of improving the access security aspects of Gb mode. In more detail, the scope includes:
1) Investigate potential security threats, such as man in the middle attacks.
2) Investigate potential security enhancements between the UE and SGSN to mitigate said threats.
3) Define what security procedures and security algorithms that are recommended to be used by for Cellular IoT devices in Gb mode. This may be procedures and algorithms already specified in earlier 3GPP releases or it could be new procedures and algorithms being introduced as part of this feasibility study.
4) The potential security enhancements as part of this study item should aim at minimising the impacts to the GPRS core network. |
33.863 | Study on battery efficient security for very low throughput Machine Type Communication (MTC) devices | TR | 1.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.863/33863-120.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.872 | Study on security enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS) | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.872/33872-d00.zip | The present document contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).
In particular, the present document focuses on:
• Support for end to end WebRTC security, subject to regulatory constraints, that avoids conversion between WebRTC and IMS security protocols , including the feasibility of end to end security aspects
• Third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block where the associated subscription corresponds to a class of users supported by the WebRTC environment (e.g., enterprise associates) rather than a single end user |
33.879 | Study on security enhancements for Mission Critical Push To Talk (MCPTT) over LTE | TR | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.879/33879-d10.zip | The present document contains a study of the security aspects of the Mission-Critical Push-To-Talk (MCPTT) service and its interaction with the network. This 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.
The Stage 1 requirements for the service are defined in TS 22.179 [2]. An evaluation of Stage 2 architectural solutions for MCPTT is performed in TR 23.779 [3] and TS 23.179 [10]. This study will include consideration of relevant 3GPP specifications, particularly for ProSe (TS 33.303 [4], TS 23.303 [5]) and GCSE (TS 23.468 [6]).
The focus of the present document is to support public-safety use cases of MCPTT. Commercial scenarios are not specifically considered and some features may not be applicable to them. |
33.889 | Study on security aspects of Machine-Type Communications (MTC) architecture and feature enhancements | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.889/33889-d00.zip | The present document captures requirements, solution alternatives, evaluations and conclusions for the SA2-led Rel-13 Features:
• GROUPE (Group based Enhancements) [4],
• MONTE (Monitoring Enhancements) [5] and
• AESE (Architecture Enhancements for Service Capability Exposure [3].
The present document captures the conclusions of the study on security and privacy implications for the requirements identified in Stage 1 and Stage 2 specifications for the above mentioned Rel-13 MTC features.
Based on the outcome of the present document, any new normative text will be incorporated in TS 33.187 [2] and/or suitable existing SA3 specifications.
Editor’s Note: SA3 is supposed to work only on security solutions for architectural solutions that are covered in SA2 Rel-13 TRs TR 23.769[4], TR 23.789[5], TR 23.708 [3]. |
33.897 | Study on isolated E-UTRAN operation for public safety; Security aspects | TR | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.897/33897-d10.zip | The present document contains the results of a Stage 2 study and evaluation of possible 3GPP security solutions in support of Isolated E-UTRAN Operation for Public Safety (IOPS). The solutions are based on the Stage 1 requirements in 3GPP TS 22.346 [2], the architectural enhancements to support IOPS presented in the Stage 2 study report 3GPP TR 23.797 [3] and resulting informative Annex K in 3GPP TS 23.401 [10]. For the current release of specification the solution in 3GPP TS 23.401 [10] is based on a Local EPC with no backhaul.
The present document identifies key issues, security threats, deduces security requirements and presents proposed security solutions for IOPS.
Throughout this Technical Report the terms 'IOPS network' and 'Isolated E-UTRAN' are used synonymously. |
33.905 | Recommendations for Trusted Open Platforms | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-d00.zip | |
33.916 | Security Assurance Methodology (SECAM) for 3GPP network products | TR | 1.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.916/33916-130.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-d00.zip | |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-d00.zip | |
33.926 | Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes | TR | 13.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.926/33926-d10.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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.