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.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-800.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP. |
32.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-800.zip | The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.632 V9.1.X. |
32.732 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.732/32732-810.zip | The present document is part of an Integration Reference Point (IRP) named IMS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral IMS NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [9], either by direct reuse or sub-classing, and in addition to that defines IMS specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP in 3GPP TS 32.602 [10]. However, which Interface IRP that is applicable is outside the scope of the present document. |
32.733 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.733/32733-800.zip | The purpose of this IMS NRM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service (see TS 32.732 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.732. |
32.635 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.635/32635-800.zip | The present document provides the NRM-specific part related to the Core Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.632 V9.1.X. |
32.735 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.735/32735-800.zip | The present document provides the NRM-specific part related to the IMS NRM IRP [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.732 V9.1.X. |
32.745 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-800.zip | The present document provides the NRM-specific part related to the STN Network Resources IRP NRM in 32.742 [1] of the XML file format definition for the Bulk Configuration Management IRP IS (TS 32.612 [2]).
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.742 V9.0.X. |
32.741 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-800.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the Signalling Transport Network (STN) interface NRM IRP. |
32.743 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-800.zip | The present document maps the IRP information model in 32.742 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V9.0.X. |
32.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 8.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-860.zip | The present document specifies the UTRAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
The present document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.752 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.752/32752-820.zip | The present document specifies the protocol neutral EPC Network Resource Model IRP Information Service, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate information to one or several 'IRPManagers' (typically Network Managers) concerning EPC resources. It reuses relevant parts of the Generic NRM in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines EPC specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.753 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.753/32753-830.zip | The present document is part of an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning EPC resources. The EPC NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the EPC Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.752 v9.3.X. |
32.762 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 8.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.762/32762-840.zip | The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral E-UTRAN NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines E-UTRAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.751 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.751/32751-800.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the EPC Network Resource Model (NRM) IRP. |
32.742 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-800.zip | The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Signalling Transport resources. This IRP comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral STN resources IRP NRM. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the NRMs defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Signalling Transport Network specific NRM, based on the generic NRM in 3GPP TS 32.622 [6].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which IS is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRMs of one release shall support the same State Management IRP version. |
32.761 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.761/32761-810.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the E‑UTRAN Network Resource Model (NRM) IRP. |
32.765 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 8.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.765/32765-840.zip | The present document provides the XML definitions for the E-UTRAN Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
This specification is related to 3GPP TS 32.762 V9. 5.X. |
32.763 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 8.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.763/32763-840.zip | The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the E-UTRAN Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.762 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.762 v9. 5.X. |
32.816 | Telecommunication management; Study on management of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet Core (EPC) | TR | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.816/32816-800.zip | |
32.820 | Telecommunication management; Study on charging management; 3GPP Evolved Packet Core (EPC): Charging aspects | TR | 8.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.820/32820-801.zip | The present document intends to study the impact of the evolved 3GPP system architecture with respect to charging.
The study covers the relevant non-roaming and roaming use cases for both 3GPP and non-3GPP accesses specified in TS 23.401 [3] and TS 23.402 [4].
The study aims at producing recommendations for the following aspects:
- 3GPP work item and specification structure;
- charging requirements and principles;
- charging architecture and charging scenarios; and
- charging data and protocols.
The aspect of charging requirements and principles includes the study of the reuse of 3GPP Release 7 charging specifications. |
32.755 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 8.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.755/32755-820.zip | The present document provides the XML file format definition for the EPC Network Resource Model IRP IS [2] V9.3.X.
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6]. |
32.819 | Telecommunications management; Element management layer - Operation System Function (E-OSF) definition | TR | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.819/32819-800.zip | The present document identifies and defines the needs in the E-OSFs.
The intention is not to define new requirements for the eventual standardization of new Interface IRP or NRM IRP and/or System Context.
The present document proposes to define the E-OSFs including the following main aspects:
• Define functional scope of Element-OSF (E-OSF)
• Define functional requirement of Elements-OSF (E-OSF)
The present document identifies a set of functions require by operators to operate mobile networks.
By identifying these functional capabilities and then comparing them with the 3GPP IRP capabilities, widely used functions and omissions in the 3GPP set of IRPs are indicated.
Change Requests and new IRPs are expected to be created in order to narrow the functional gap. |
33.102 | 3G security; Security architecture | TS | 8.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-870.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 | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-800.zip | |
32.818 | Telecommunication management; Study on 3GPP SA5 / MTOSI XML harmonization | TR | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.818/32818-800.zip | The present document is the outcome of the SA5 MTOSI XML harmonization study.
MTOSI version 1.1 is considered in the present document.
The goal of the present document is multiple:
• At first, it mainly consists in studying the MTOSI XML recommendations and estimate whether or not they are applicable and useful to SA5.
• Then, a delta calculation, in terms of Methodology, Specifications and Models, will be studied and presented in order to define, in case MTOSI recommendations prove to be useful to SA5, what are the main differences between MTOSI and SA5 specifications. Once those will be identified, they will be ordered in priority and a decision will be made, whether or not the harmonization process for such or such items can be kicked off.
• Finally, a proposed roadmap for those activities will be presented. This roadmap is likely to evolve as we move along the harmonization effort between MTOSI and SA5.
The content of the present document is subject to 3GPP SA5 discussion and decisions will be made based on the output thereof. |
32.808 | Telecommunication management; Study of Common Profile Storage (CPS) Framework of User Data for network services and management | TR | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.808/32808-800.zip | The present document investigates possibilities to introduce an end-user profile storage framework into 3GPP conformant communication networks. To this end the following topics are covered:
• Analysis of the consequences of creating one common data model structure for an end user:
- Existing data specifications concerning an end-user or a subscriber in 3GPP, TISPAN, OMA and other relevant standardization groups are listed and used as a basis for the proposal of a structure for a common end-user data model.
- Topics connected to the fact that one common data model exists, like minimizing data redundancy, access control, providing views for applications are highlighted.
- The relationship between an end user and a subscriber as defined by 3GPP is revisited in light of the fact that the relations between subscribers (contract holders) and end-users can be n:m.
• Current initiatives connected to subscription information carried out inside and outside 3GPP are covered.
• Analysis of differences and deficiencies concerning 3GPP's current status of specifications (e.g. GUP, SuM, etc.) in comparison to existing/emerging solutions with centralized or distributed storage models.
• Identification of items for standardization as a result of the analysis described in the bullet above. |
33.106 | 3G security; Lawful interception requirements | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-810.zip | |
33.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-800.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 8.14.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-8e0.zip | The present document specifies the handover interfaces for Lawful Interception (LI) of Packet-Data Services, Circuit Switched Services, Multimedia Services within the UMTS network and Evolved Packet System (EPS). The handover interface in this context includes the delivery of Intercept Related Information (IRI) through the Handover Interface 2 (HI2) and Content of Communication (CC) through the Handover Interface 3 (HI3) to the Law Enforcement Monitoring Facility (LEMF). |
33.107 | 3G security; Lawful interception architecture and functions | TS | 8.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-8c0.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-800.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 8.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-830.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 8.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-890.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 8.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-880.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.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-800.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 8.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-840.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.141 | Presence service; Security | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-810.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-810.zip | |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 8.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-820.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 8.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-840.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 8.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-880.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 8.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-870.zip | |
33.821 | Rationale and track of security decisions in Long Term Evolution (LTE) RAN / 3GPP System Architecture Evolution (SAE) | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.821/33821-800.zip | The scope of this 3GPP Technical Report is rationale and track of security decisions in Long Term Evolved (LTE) RAN and 3GPP System Architecture Evolution (SAE) for release 8.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.401. This TR is useful to better understand the basis on which decisions in TS 33.401 were taken, and the alternatives that were discussed towards the decision. Some of the text in this TR reflected 3GPP SA3’s decision. However 3GPP’s position on EPS Security Architecture is reflected in the normative text in TS 33.401. |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 8.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-880.zip | |
33.822 | Security aspects for inter-access mobility between non 3GPP and 3GPP access network | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.822/33822-800.zip | This document studies the security architecture, i.e. the security features and the security mechanisms for inter-access mobility between 3GPP access system and non-3GPP access systems. For the general architecture for inter-access mobility cf. TR 23.882. This report is meant to provide more detail on the security aspects of inter-access mobility.
The scope should be extended to the mobility between two non-3GPP access systems, which interwork with 3GPP core entities. An example would be the mobility between two WLAN access systems providing 3GPP IP access.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.402 [14]. This TR may therefore be useful to better understand the basis on which decisions in TS 33.402 [14] were taken, and which alternatives were under discussion. However, none of the text in this TR shall be quoted as reflecting 3GPP’s position in any way. Rather, 3GPP’s position on security for non-3GPP access to EPS is reflected in the normative text in TS 33.402 [14]. Information in the TR may be inaccurate and outdated. One example of outdated text can be found in clauses 4.1 and 4.2 on alternatives for authentication protocols. The choices of authentication protocols finally made by 3GPP can be found in TS 33.401 [13] and TS 33.402 [14] respectively. |
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 | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-800.zip | |
33.820 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TR | 8.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.820/33820-830.zip | The present document identifies special security threats of H(e)NB and study the countermeasures to these threats.
The study should include, but not be limited to, threat analysis of H(e)NB, mutual authentication and security protection between H(e)NB and rest of network, maintenance of the security context between H(e)NB and rest of network, security requirements on the H(e)NB, provisioning of security credentials on the H(e)NB, security solution for verifying the location of the H(e)NB etc.
With regard to security protection between the H(e)NB and the rest of the network, bandwidth efficiency should be taken into consideration. |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-800.zip | |
33.905 | Recommendations for Trusted Open Platforms | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-800.zip | |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 8.2.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-820.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 8.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-8b0.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.121-1 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification | TS | 8.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-8b0.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.114 | User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing | TS | 8.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.114/34114-840.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.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 8.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-860.zip | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 8.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-8b0.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 | 8.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-8b0.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.123-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [45] and the common test environments are included in 3GPP TS 34.108 [44].
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.121-2 | User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 2: Implementation Conformance Statement (ICS) | TS | 8.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-8b0.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.121-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [19] and the common test environments are included in 3GPP TS 34.108 [18] and 3GPP TS 36.508 [29].
The present document is valid for UE implemented according to 3GPP releases starting from Release 99 up to the Release indicated on the cover page of the present document. |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 8.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-840.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-800.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 8.0.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-801.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 | 8.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-860.zip | |
34.171 | Terminal conformance specification; Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD) | TS | 8.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.171/34171-820.zip | The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in 3GPP TS 34.172 [18].
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. |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-800.zip | |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 8.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-800.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-800.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 | 8.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-870.zip | |
34.902 | Derivation of test tolerances for multi-cell Radio Resource Management (RRM) conformance tests | TR | 8.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.902/34902-810.zip | The present document specifies a method used to derive Test Tolerances for multi-cell Radio Resource Management tests, and establishes a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
The present document is applicable to Release 99 up to the release indicated on the front page of the present Terminal conformance specifications. |
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 | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-800.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 | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-800.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.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-810.zip | |
35.216 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-800.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 | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-800.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-800.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-800.zip | |
35.919 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report | TR | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-800.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-800.zip | |
36.106 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater radio transmission and reception | TS | 8.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.106/36106-870.zip | |
36.113 | Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC) | TS | 8.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.113/36113-830.zip | |
36.124 | Evolved Universal Terrestrial Radio Access (E-UTRA); Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 8.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.124/36124-830.zip | |
36.143 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing | TS | 8.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.143/36143-850.zip | |
36.201 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description | TS | 8.3.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.201/36201-830.zip | |
36.214 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements | TS | 8.7.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.214/36214-870.zip | |
36.302 | Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the physical layer | TS | 8.2.1 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.302/36302-821.zip | |
36.304 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode | TS | 8.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.304/36304-8a0.zip | |
36.306 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities | TS | 8.9.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.306/36306-890.zip | |
36.307 | Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band | TS | 8.17.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.307/36307-8h0.zip | The present document specifies requirements for Rel-18 UEs supporting release independent features like:
- additional E-UTRA operating frequency bands on top of Rel-18 of TS 36.101 [2], TS 36.102 [6] and TS 36.133 [3];
- additional E-UTRA CA configurations (intra-band/inter-band) on top of Rel-18 of TS 36.101 [2] and TS 36.133 [3];
- additional operating bands and/or CA configurations for specific features (like UE category 0, M1, NB1);
- other release independent features (like 4Rx antenna port, high speed scenario, 8Rx antenna port, NB-IoT or eMTC operation over NTN). |
36.314 | Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements | TS | 8.3.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.314/36314-830.zip | |
36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | TS | 8.12.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.321/36321-8c0.zip | |
36.322 | Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification | TS | 8.8.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.322/36322-880.zip | |
36.323 | Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification | TS | 8.6.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.323/36323-860.zip | |
36.401 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description | TS | 8.8.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.401/36401-880.zip | |
36.410 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles | TS | 8.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.410/36410-830.zip | |
36.411 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 layer 1 | TS | 8.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.411/36411-810.zip | |
36.412 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling transport | TS | 8.6.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.412/36412-860.zip | |
36.414 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 data transport | TS | 8.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.414/36414-840.zip | |
36.420 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects and principles | TS | 8.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.420/36420-810.zip | |
36.421 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 layer 1 | TS | 8.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.421/36421-800.zip | |
36.422 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling transport | TS | 8.6.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.422/36422-860.zip | |
35.218 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-810.zip | |
35.217 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data | TS | 8.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-810.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.