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.776 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.776/32776-a10.zip | The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS 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 Solution Sets for the HNS NRM IRP.
This specification is related to 3GPP TS 32.772 V11.0.X. |
32.781 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.781/32781-a00.zip | The document describes the requirements for Home eNodeB Subsystem (HeNS), which include Home eNodeB (HeNB) and Home eNodeB gateway (HeNB GW). The HeNS NRM IRP requirements are targeted on both HeNB and HeNB GW NRM. |
32.782 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS) | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.782/32782-a10.zip | The present document is an Integration Reference Point (IRP) named " Home enhanced Node B Subsystem (HeNS) 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 HeNB-GW resources.
The present document specifies the protocol neutral HeNS Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [5], either by direct reuse or sub-classing, and in addition to that defines HeNB-GW specific Information Object Classes.
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [6]) or the Bulk CM IRP IS (3GPP TS 32.612 [7]). However, which IS that is applicable is outside the scope of the present document.
The present document (NRM specification) is related to the IS in 3GPP TS 32.672 [8] |
32.786 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.786/32786-a10.zip | The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS 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 Solution Sets for the HeNS NRM IRP.
This Solution Set specification is related to 3GPP TS 32.782 V11.0.X. |
32.791 | Telecommunication management; Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.791/32791-a00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the Common RAT NRM IRP for equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared. |
32.792 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.792/32792-a20.zip | The present document specifies the Generic Radio Access Network (RAN) network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This 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.
This document specifies equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
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 [5]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.796 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.796/32796-a11.zip | The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN 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 Solution Sets for the Generic RAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.792 V11.0.X [4]. |
32.825 | Telecommunication management; Charging management; Rc reference point study | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.825/32825-a00.zip | The present document is a study report for Rc reference point supported by ABMF (Accounting Balance Management Function).
The study covers the drive and requirement analysis, existing architectures, key issues analysis, recommandations, etc.
The study aims at producing recommendations for the following aspects:
- 3GPP work item and specification;
- Charging requirements and principles;
- Charging architecture and Rc networking scenarios;
- Charging data and protocols;
- Technical recommandations |
32.826 | Telecommunication management; Study on Energy Savings Management (ESM) | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.826/32826-a00.zip | In the context of 3GPP Self-Organizing Networks (SON), this study investigates about Energy Savings Management in LTE / SAE networks, with the objective to contribute to the protection of our environment and the environment of future generations. One is forced to admit that, in addition, network energy consumption reduction will enable mobile network operators to save their OPEX.
The present document covers:
• Motivations of mobile network operators for the introduction of energy savings control mechanisms
• Analysis of possible mechanisms for Energy Savings Management via OAM
• Usage of existing IRPs to be used for the purpose of Energy Savings Management
• Identification of new IRP to be potentially defined
• Conclusions
• Recommendations on Energy Savings Management
• Identification of items for standardization as a result of this study |
32.827 | Telecommunication management; Integration of device management information with Itf-N | TR | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.827/32827-a10.zip | UE Management provides the network operator with the opportunity to manage and monitor the actual user experience of their subscribers via the remote management of the user equipement.
UE management over Itf-N provides the ability to minimize the complexibity and reduce the OPEX and CAPEX costs of managing the UE by the ingegrated management capabilities.
UE management over Itf-N provides the capabilites for service provisioning and personalized subscriber profile backup for the UE via DMS, to improve the subscriber satisfaction and thus contribute to subscriber retention.
The UE can provide measurments of the quality of radio network and the actual service being delivered to the user, collection of these measurements via Itf-N can be used by Centralized SON or manual optimization.
This document is to study UE management over Itf-N, including the following aspects:
- Subscriber profile configuration over Itf-N;
- Collection of UE measurements over Itf-N. Includes protocol definition over Itf-N and study of appropriate UE measurements defined in RAN WGs;
- Retrieval of UE measurement logs over Itf-N. Includes file format definition over Itf-N and study of appropriate solutions for measurement logging policy configuration and log retrieval over Itf-N.
To support the UE measurement log collection via Itf-N, this document will study how to support the UE measurement log transfer mechanisms measurement logging policy configuration and measurement log retrieval by DMS using existing UE management protocol procedures, and identify a suitable protocol from a network management perspective. This document will also study how to do the mapping between the selected protocol and Itf-N. |
32.828 | Telecommunication management; Study on alignment of 3GPP generic Network Resource Model (NRM) Integration Reference Point (IRP) and the TeleManagement Forum (TMF) Shared Information/Data (SID) model | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.828/32828-a00.zip | The present document studies how to allow the two organizations (3GPP and TMF) to evolve their respective NRMs and SID in a manner that they would become aligned to support consistent and integrated management of mobile and fixed networks. This study:
• identifies the non-aligned, contradicting or overlapping parts between NRMs and SID
• identifies the non-aligned, contradicting or overlapping parts regarding specification methodology
• proposes possibilities to align the parts identified above;
• ensures that the proposal allows usage of the 3GPP Generic NRM IRP independently of SID
• ensures that the proposal allows usage of mobile specific NRMs to be used as they are
• drives the alignment process with TMF
• identifies any required changes in the 3GPP specifications
• identifies required changes in the TMF specifications to be communicated to the TMF
• ensures that 3GPP remains full owner of the aligned part of the NRM specifications
• defines a procedure how aligned specifications can be maintained and updated in a consistent manner
Special emphasis has been given to the borderline between generic and harmonized part and the network technology specific parts of the models. In case new requirements had been identified during the alignment process, they have been taken into account as well.
It is not intended to add the mobile specific parts of the 3GPP Network Resource Models to the TMF SID.
These model aspects are published by 3GPP only. Interface aspects (e. g. the Alarm IRP) are outside of the scope of this Study. |
32.829 | Telecommunication management; Study on alignment of 3GPP alarm Integration Reference Point (IRP) and TeleManagement Forum (TMF) Interface Program (TIP) fault management | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.829/32829-a00.zip | The present document collects, compares and analyzes the specifications of Fault Management (FM) as defined by 3GPP and TMF. These two organizations have both a complete set of FM specifications consisting of requirement, technology-independent and solution set specification for
- Fault Management interface – operations and notifications and
- Alarm content
The present documentidentifies similarities and differences of the Fault Management capabilities in 3GPP and TMF and provides recommendations to align these capabilities. |
32.831 | Telecommunication management; Study on alignment of 3GPP Performance Management (PM) and TeleManagement Forum (TMF) Interface Program (TIP) Performance Management | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.831/32831-a00.zip | The present document provides consistent and aligned PM and PM interfaces in 3GPP and TMF. The present document:
• identifies similarities and differences of the PM capabilities in 3GPP and TMF TIP PM BA;
• proposes enhancements to 3GPP PM solutions for converged networks and to satisfy TMF TIP PM BA requirements;
• identifies any required changes in the 3GPP specifications;
• identifies any required changes in the TMF specifications (to be communicated to TMF).
Backwards compatibility of the PM IRP should be maintained as much as possible by re-using existing specifications to the maximum extent.
The counter collected by each of the Network Elements (NE) and the definition of those are NE specific and there is no intention to harmonize those.
However KPIs with a network view should be explored. |
32.832 | Telecommunication management; Study on alarm correlation and alarm root cause analysis | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.832/32832-a00.zip | The present document:
• defines the management services offered by Alarm Correlation (AC) process and alarm root cause analysis (ARCA) process;
• Identifies the benefits of the AC process and ARCA process from views of network operators;
• Identifies the possible locations of the AC and ARCA processes within the IRP framework.
• Identifies possible IRP standard solutions, including enhancement of existing IRP standard solutions. |
33.102 | 3G security; Security architecture | TS | 10.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-a20.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. |
32.692 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.692/32692-a20.zip | The present document defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
The present document specifies an Inventory Management Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes. |
33.106 | 3G security; Lawful interception requirements | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-a10.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 10.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-a50.zip | |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 10.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-a70.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 | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-a10.zip | |
33.141 | Presence service; Security | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-a00.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 10.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-a30.zip | The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
Since the scope also encompasses the use of these security features and mechanisms for secure access to IMS in the context of fixed broadband networks and 3GPP2 networks, Annex L and Annex S specify how the material in the main body and other normative Annexes of this document apply to the fixed broadband networks and 3GPP2 networks respectively.
The IMS supports IP Multimedia applications such as video, audio and multimedia conferences. SIP, Session Initiation Protocol, was chosen as the signalling protocol for creating and terminating Multimedia sessions, cf. RFC 3261 [6]. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS. |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-a00.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 10.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-a30.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-a10.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-a00.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 10.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-a01.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-a10.zip | |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-a00.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 10.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-a20.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-a10.zip | The Technical Specification covers the security procedures of the Multimedia Broadcast/Multicast Service (MBMS) for 3GPP systems (UTRAN, GERAN and E-UTRAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application. |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-a00.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 10.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-a70.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 10.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-a50.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-a00.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 10.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-a70.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 10.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-a30.zip | |
33.828 | IP Multimedia Subsystem (IMS) media plane security | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.828/33828-a00.zip | |
33.905 | Recommendations for Trusted Open Platforms | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-a00.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-a00.zip | |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-a10.zip | |
33.937 | Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI) | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.937/33937-a00.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 | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.980/33980-a00.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 10.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-a10.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures for use in UE conformance tests. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 10.3.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-a30.zip | |
34.114 | User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing | TS | 10.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.114/34114-a30.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 | 10.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-a80.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 | 10.9.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-2/34121-2-a90.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.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 10.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-a10.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 | 10.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-a70.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 | 10.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-a70.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 | 10.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-a20.zip | |
34.172 | Terminal conformance specification; Assisted Global Navigation Satellite Systems (A-GNSS); Frequency Division Duplex (FDD) | TS | 10.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.172/34172-a20.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) that supports Assisted Global Navigation Satellite Systems (A-GNSS). It includes the measurement procedures for the conformance test of both UE‑based and UE‑assisted A‑GNSS. It excludes performance requirements for UEs where the only A-GNSS supported is A-GPS L1C/A which are specified in TS 34.171 [26].
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. |
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 | 10.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-a40.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 | 10.8.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-3/34229-3-a80.zip | |
34.902 | Derivation of test tolerances for multi-cell Radio Resource Management (RRM) conformance tests | TR | 10.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.902/34902-a00.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. |
34.926 | Electromagnetic compatibility (EMC); Table of international requirements for mobile terminals and ancillary equipment | TR | 10.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.926/34926-a00.zip | |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-a00.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-a00.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-a00.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-a00.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 | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-a00.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force. |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-a00.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 | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-a00.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 | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-a00.zip | |
35.215 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.215/35215-a00.zip | |
35.216 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification | TS | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.216/35216-a00.zip | |
35.217 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.217/35217-a10.zip | |
35.218 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.218/35218-a10.zip | |
35.909 | 3G Security; Specification of the MILENAGE algorithm set: an example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 5: Summary and results of design and evaluation | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.909/35909-a00.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 10.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-a10.zip | |
36.106 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater radio transmission and reception | TS | 10.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.106/36106-a70.zip | |
36.113 | Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC) | TS | 10.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.113/36113-a50.zip | |
34.131 | Test Specification for C-language binding to (Universal) Subscriber Interface Module ((U)SIM) Application Programming Interface (API) | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.131/34131-a00.zip | |
36.124 | Evolved Universal Terrestrial Radio Access (E-UTRA); Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 10.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.124/36124-a40.zip | |
36.143 | Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing | TS | 10.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.143/36143-a70.zip | |
36.171 | Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for Support of Assisted Global Navigation Satellite System (A-GNSS) | TS | 10.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.171/36171-a20.zip | |
36.201 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE physical layer; General description | TS | 10.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.201/36201-a00.zip | |
36.214 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements | TS | 10.1.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.214/36214-a10.zip | |
36.216 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for relaying operation | TS | 10.3.1 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.216/36216-a31.zip | |
36.302 | Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by the physical layer | TS | 10.6.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.302/36302-a60.zip | |
36.304 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode | TS | 10.9.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.304/36304-a90.zip | |
35.919 | Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 5: Design and evaluation report | TR | 10.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.919/35919-a00.zip | |
36.307 | Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User Equipments (UEs) supporting a release-independent frequency band | TS | 10.24.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.307/36307-ao0.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.305 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN | TS | 10.5.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.305/36305-a50.zip | |
36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | TS | 10.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.321/36321-aa0.zip | |
36.314 | Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements | TS | 10.2.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.314/36314-a20.zip | |
36.323 | Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification | TS | 10.3.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.323/36323-a30.zip | |
36.355 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP) | TS | 10.12.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.355/36355-ac0.zip | |
36.401 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description | TS | 10.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.401/36401-a40.zip | |
36.410 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles | TS | 10.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.410/36410-a30.zip | |
36.411 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 layer 1 | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.411/36411-a10.zip | |
36.412 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling transport | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.412/36412-a10.zip | |
36.414 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 data transport | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.414/36414-a10.zip | |
36.420 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 general aspects and principles | TS | 10.2.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.420/36420-a20.zip | |
36.421 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 layer 1 | TS | 10.0.1 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.421/36421-a01.zip | |
36.422 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling transport | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.422/36422-a10.zip | |
36.424 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 data transport | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.424/36424-a10.zip | |
36.440 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN | TS | 10.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.440/36440-a30.zip | |
36.441 | Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Layer 1 for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN | TS | 10.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.441/36441-a10.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.