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.531 | Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.531/32531-c00.zip | |
32.532 | Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.532/32532-c00.zip | |
32.407 | Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.407/32407-c00.zip | |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-c00.zip | |
32.551 | Telecommunication management; Energy Saving Management (ESM); Concepts and requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.551/32551-c00.zip | |
32.571 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.571/32571-c00.zip | |
32.572 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.572/32572-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.581/32581-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.582/32582-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.583/32583-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.584/32584-c00.zip | |
32.506 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.506/32506-c00.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 | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-c10.zip | |
32.508 | Telecommunication management; Procedure flows for multi-vendor plug-and-play eNode B connection to the network | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.508/32508-c00.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.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.594/32594-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.591/32591-c00.zip | |
32.536 | Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.536/32536-c00.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 | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.593/32593-c00.zip | |
32.421 | Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements | TS | 12.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.421/32421-c30.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-c00.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-c00.zip | |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-c00.zip | |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-c00.zip | |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-c00.zip | |
32.666 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.666/32666-c00.zip | |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-c00.zip | |
32.830 | Telecommunication management; Study on version handling over Itf-N | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.830/32830-c00.zip | The scope of the study is to:
• Document current version handling capabilities in SA5 OAM specifications (clause 5)
• Identify and agree on the use cases and requirements (clause 6) for a coherent approach for version handling capabilities for SA5 OAM specifications
• Identify solution(s) with pros and cons to support the identified requirements (clause 7). The solutions may require enhancement or modification of rules in the IRP methodology as well as enhancements of existing or addition of new IRP specifications, utilizing SOA capabilities where appropriate. This includes:
1. The identification of entities that require version control (clause 7.1)
2. The protocol(s) by which the entity version can be discovered and registered (clause 7.2)
• Recommend a solution (clause 8).
Note: "Version handling" in the context of this study addresses what kind of support for version information that is available over the Itf-N interface, i.e. what the IRPManager can "see" regarding which versions of the 3GPP specifications that are supported by the IRPAgent, for which object instances etc. |
32.835 | Telecommunication management; Study of heterogeneous networks management | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.835/32835-c00.zip | The present document investigates and makes recommendations on how management information can be selected by the manager over Itf-N for heterogeneous networks (see TR 21.905 [1]) nodes that are owned, deployed and maintained by the operator.
The nodes that are owned, deployed or maintained by residential users are out of scope of the present document, such as Home NodeBs, Home eNodeBs. |
32.836 | Telecommunication management; Study on Network Management (NM) centralized Coverage and Capacity Optimization (CCO) Self-Organizing Networks (SON) function | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.836/32836-c00.zip | The present document summarizes the result of the study on "Enhanced Network Management (NM) centralized Coverage and Capacity Optimization".
A CCO function that resides outside the NM is out of the scope for this study. |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-c00.zip | |
32.606 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.606/32606-c00.zip | |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-c00.zip | |
32.844 | Study of charging support of Proximity-based Services (ProSe) direct communication for public safety use | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.844/32844-c00.zip | The present document contains the outcome of the study on the charging architecture for the one-to-many "ProSe Direct Communication for ProSe-enabled Public Safety UEs".
The study covers the "ProSe Direct Communication for Public Safety use" as specified in TS 23.303 [238], in order to meet the charging requirements specified in TS 22.115 [101].
The present document makes recommendations for the following aspects of ProSe Direct Communication for Public Safety use:
- charging requirements and principles;
- charging architecture and charging scenarios, with the support of delayed reporting;
- charging interfaces; and
- recommendations to CT1 on UE reporting configuration and usage information elements. |
32.851 | Telecommunication management; Study on Operations, Administration and Maintenance (OAM) aspects of Network Sharing | TR | 12.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.851/32851-c20.zip | The present document is aimed at addressing the operational implications of network sharing.
There are a wide variety of deployment scenarios for network sharing.
Scenarios identified in 3GPP TS 23.251 [3] and TR 22.951 [2] are taken into consideration to identify OAM impacts.
3GPP TS 23.251 "Network sharing; Architecture and functional description" specifies the stage 2 descriptions which are also considered to address OAM aspects.
NGCOR defined RAN sharing requirements are taken into account as input for this study. |
32.859 | Telecommunication management; Study on Alarm Management | TR | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.859/32859-c10.zip | The scope of the present document is to study how to improve the quality of alarms and enhance usability of alarm systems. |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-c00.zip | |
33.102 | 3G security; Security architecture | TS | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-c20.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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-c00.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 12.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-c60.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 12.14.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-ce0.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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-c00.zip | |
33.141 | Presence service; Security | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-c00.zip | |
33.187 | Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TS | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.187/33187-c20.zip | |
32.841 | Telecommunication management; Study on Wireless Local Area Network (WLAN) management | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.841/32841-c00.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-c00.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-c20.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 12.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-c30.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-c00.zip | |
32.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-c00.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 12.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-c10.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 12.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-c90.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.107 | 3G security; Lawful interception architecture and functions | TS | 12.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-cd0.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-c20.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.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 12.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-c30.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-c00.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 12.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-c10.zip | |
33.303 | Proximity-based Services (ProSe); Security aspects | TS | 12.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.303/33303-c70.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 12.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-c90.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 12.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-c10.zip | |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-c00.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 12.16.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-cg0.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-c20.zip | |
33.823 | Security for usage of Generic Bootstrapping Architecture (GBA) with a User Equipment (UE) browser | TR | 12.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.823/33823-c20.zip | This work in this Technical Report has the following scope:
- Study the potential threats for different GBA credentials use scenarios via a web browser. These new use scenarios (e.g. using HTML forms, using Javascript, using widgets) are not covered by current specifications.
The scope of this Technical Report will cover the following:
- Study, identify and specify any protection mechanism that maybe additionally required for the GBA credentials;
- Study, identify and potentially specify usage control for GBA credentials;
- Study, identify and potentially specify access control mechanism for GBA module;
- Study, identify and potentially specify the usage of web based GBA as an extension on the current protocol mechanisms used on Ua reference point (e.g. new Ua protocol identifier);
- Identify and outline how GBA can be used with HTML Forms and Javascript securely (e.g. describing GBA - web specific common practices and examples).
This Technical Report will collect the potential specification improvements, which are then at a later stage of work transferred to the appropriate Technical Specifications. The potential improvements for access control to GBA credentials and potential Ua protocol impacts will then be documented in TS 33.220 [2]. The threat analysis, common security implementation practices and examples may build a new chapter 5 in TS 33.222 [3].
Relation to GBA variants defined in other documents: Web based GBA aims at defining web enhancements for the use of HTML forms with GBA. It is a new variant for the Ua interface and does not affect the Ub interface, as opposed to the GBA variants defined in TS 33.220. Web based GBA is orthogonal to these other GBA variants and can be used with any of them. |
33.829 | Extended IP Multimedia Subsystem (IMS) media plane security features | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.829/33829-c00.zip | The present document details relevant use cases/services for different user groups and corresponding solutions for IMS media plane security which are not covered by TS 33.328 [3]. The corresponding requirements in the Rel-9 study documented in TR 33.828 [2] will be used as a basis. The covered use cases/services are: conference calls, protection of non-RTP media, early media, communication diversion, deferred delivery, protected media recording, video on demand, AS-terminated media security, transcoder functionality and SRVCC. Example user groups are enterprises, National Security and Public Safety (NSPS) organizations, different government authorities, and general public.
Editor’s Note: The list of covered use cases/services shall be updated when the study is finalized.
Editor’s Note: It is for further study whether protection of early media is possible in IMS. |
33.831 | Study on security on spoofed call detection and prevention (Stage 2) | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.831/33831-c00.zip | The present document studies the means to identify calls with spoofed Calling Line Identification terminating in the CS domain where the call could have originated from either inside or outside the CS domain. Calling Line Identification (CLI or CLID), also called Caller Identification (CID), evaluates and transmits a caller's number while Calling Line Identity Presentation (CLIP) enables displaying the caller's number during call setup or ringing. Usual applications for CLIP are:
to display the original number of the caller;
to display a caller's presentation number, e.g. a doctor calling a patient out of hours who doesn't want to disclose his private number but showing instead the number of his office;
to display a number unrelated to the calling line, e.g. call centers displaying numbers related to their customers (depending on national regulations).
But CLI can also be misused to display a misleading number in the display that is in no way related to the originator of the call. This behaviour is called CLI spoofing or spoofed call. CLI spoofing ranges from harmless hoax to criminal activities like for example Voice Phishing (vishing) by displaying the forged number of a bank in order to steal the callee's credentials. And although CLI may be unreliable, people use it to decide whether to accept a call or not.
This study item studies the detection of a spoofed call as the first step, and prevention as a second step if detection is achievable. In particular, the goals of this document are:
• Outline valid threat scenarios for spoofed calls coming to 2G and 3G CS domains;
• Analyze and evaluate if any tools in 3GPP can be used to counteract spoofed call detection and prevention;
• Study and identify any other suitable techniques or mechanisms for spoofed call detection and prevention.
NOTE: When the "potential requirements" and "potential solutions" from the present document might be introduced into normative documents (Technical Specifications - TSs), the word "should" needs to be changed into "shall" (with bold characters). |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 12.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-c60.zip | |
33.849 | Study on subscriber privacy impact in 3GPP | TR | 0.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.849/33849-080.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.804 | Single Sign On (SSO) application security for Common IP Multimedia Subsystem (IMS) based on Session Initiation Protocol (SIP) Digest | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.804/33804-c00.zip | The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated. |
33.868 | Study on security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TR | 12.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.868/33868-c10.zip | The present document studies the security aspects of System Improvements for Machine Type Communication. In particular, the goals of the present document are:
- To identify and analyze the threats to the MTC system within the scope of the service requirements, functionality and use cases as specified in TS 22.368 [9].
- To identify possible security and privacy impacts induced by the system architecture improvement for machine type communications based on TR 23.887 [26] and TS 23.682 [23].
- To determine possible security requirements based on the analysis above and describe the possible solutions to meet those requirements.
Machine-type communication aspects of (x)SIMs and/or new models for the management of (x)SIM are out of scope of the present document. |
33.869 | Security aspects of Public Warning System (PWS) | TR | 0.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.869/33869-070.zip | The present document studies security features and mechanisms for protection against false Base Stations broadcasting false Warning Notifications.
The default terminal behaviour is to accept all Warning Notifications even if their authenticity is unknown (i.e. no security protection). The default terminal behaviour is therefore open to the presentation of false Warning Notifications issued by false BSs even in countries without a Public Warning System (PWS) deployed.
Examples of false BS risks include, but are not limited to:
• False Warning Notifications to induce panic;
• Abuse of warning system broadcast channel to send advertising / spam.
These security features and mechanisms are optional since there are regions and countries that do not require this functionality. |
33.805 | Study on security assurance methodology for 3GPP network products | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.805/33805-c00.zip | The present document studies methodologies for specifying network product security assurance and hardening requirements, with associated test cases when feasible, of 3GPP network products. Network product security assurance and hardening refers to protection against unwanted access to a 3GPP network product, its Operating System, and main running Application(s). The suitability of industry standard methodologies and the potential need for collaboration with bodies such as GSMA, CCRA, ISO and ITU will be assessed. The study will also consider regulatory aspects and the potential need for security certification. The suitability of the candidate methodologies will be assessed with reference to real world examples.
Part of the scope of this work is to conclude which 3GPP network products, if not all, would be subject to 3GPP network product security assurance and hardening requirements. There is likely to be a long list with the result that prioritisation will be required. LTE network product classes will be the first priority. The work will also study exactly what should constitute a 3GPP network product in the context of this study e.g. whether it should be an individual 3GPP functional entity, a group of 3GPP functional entities or some other realisation.
The study will also include assessing the extent to which individual 3GPP network products need to be hardened beyond a common baseline and should take into consideration network vs. environment. |
33.905 | Recommendations for Trusted Open Platforms | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-c00.zip | |
33.871 | Study on security for Web Real Time Communications (WebRTC) IP Multimedia Subsystem (IMS) client access to IMS | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.871/33871-c00.zip | The goal of WebRTC IMS Client access to IMS is to significantly expand the pool of clients able to access IMS.
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 WebRTC IMS Client access to IMS.
For this purpose the present document is addressing:
• WebRTC IMS Client authentication mechanisms, including the re-use of existing IMS authentication mechanisms from WebRTC IMS Clients;
• Required enhancements to IMS media plane security;
• Control plane security related aspects. |
33.865 | Security Aspects of WLAN Network Selection for 3GPP Terminals | TR | 0.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.865/33865-050.zip | The present document studies the security aspects of WLAN Network Selection for 3GPP Terminals. In particular, the goals of this document are:
-To work on security impacts and threats of key issues and solutions of SA2’s specifications.
-To identify potential conflicts between security mechanisms provided by non-3GPP providers via Hotspot 2.0 and security mechanisms provided by 3GPP operators, and define security solutions if needed.
-To identify possible impacts to the current authentication method of non-seamless WLAN offload.
Editor Notes: Need to update the scope with relevant TS and TR. |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-c00.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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-c00.zip | |
33.888 | Study on security issues to support Group Communication System Enablers (GCSE) for LTE | TR | 12.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.888/33888-c10.zip | The present document studies the security aspects of the Group Communication Service Enabler for LTE (GCSE_LTE) and gives an evaluation of possible technical security solutions supporting such an Enabler. The present document looks at security from system perspective and defines functional security requirements for all entities.
Stage 1 requirements for these services are defined in 3GPP TS 22.468 [2].
Different possible Stage 2 solutions for GCSE have been studied in 3GPP TR 23.768 [3].
3GPP TS 23.468 [8] provides the stage 2 description for the 3GPP system provided enablers to support GC services using E-UTRAN in Rel-12.
Based on the work done in 3GPP TS 22.468 [2], 3GPP TR 23.768 [3], and 3GPP TS 23.468 [8] the objectives of the present document are to identify the threats and deduce security requirements, develop GCSE_LTE security solutions, and determine which solution(s) from the present document (Study/TR phase) should be converted into normative specifications for Rel-12.
NOTE: The present document collects requirements that are not normative. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 12.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-c00.zip | |
34.114 | User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing | TS | 12.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.114/34114-c20.zip | The present document describes the test procedure for the radiated performances measurements of the 3G/2G user equipment/mobile stations (UE/MS) in active mode in both the uplink and the downlink. The FDD UE test procedure is based on the test method developed as a result of COST 273 Sub-Working Group (SWG) 2.2 members’ contributions. Background work has also been made in the former COST259 project. The TDD UE test procedure is based on the test method developed as a result of CCSA TC9 WG1 members’ contributions. Background work has been made in the former CCSA TC9 project.
The measurement procedure explained in this document applies to UE/MS used under the “speech mode” conditions that correspond to predefined positions for voice application when the handset is held close to the user’s head. This method is also applicable to free space measurements for UE/MS devices. The data transfer position (free space) explained in this document applies when the UE is used away from the user’s head. For LME and LEE devices free space configuration without head and hand phantoms is applicable. Free space measurements are applicable to devices used in the data transfer position that consist of the laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
The tests apply to UEs and laptops using single or multiple receive antennas. For GSM technology this is applicable to all MSs and for 3G technology this is applicable to “one antenna” UEs and “RxDiversity” UEs.
The testing methodology applies to any single or multi-mode (GSM / UMTS / TD-SCDMA) terminals.
The radio tests considered here are:
1. The measurement of the Total Radiated Power (TRP)
2. The measurement of the Total Radiated Sensitivity (TRS)
The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user.
The major parts of this test procedure are based on the 3-D pattern measurement method. It has been considered necessary to define some items and components in the test procedure in detail, such as test channels and phantom set-ups, in order to make the testing in different laboratories harmonized. The procedure is, however, not limited to some specific antenna chambers or positioners. |
34.121-1 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification | TS | 12.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-c50.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 | 12.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-c60.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 | 12.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-c80.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 | 12.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-c80.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 | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-c00.zip | |
33.969 | Study on security aspects of Public Warning System (PWS) | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.969/33969-c00.zip | |
33.937 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-c00.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 | 12.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-cb0.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 | 12.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-c20.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 12.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-c50.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.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-c00.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 12.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-c00.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-c00.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-c00.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-c00.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-c00.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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-c00.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.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-c00.zip | |
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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-c00.zip | |
35.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-c00.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 | 12.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-c00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.