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 |
|---|---|---|---|---|---|---|
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 3.10.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-3a0.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 3.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-300.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 3.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-330.zip | |
32.005 | Telecommunications management; Charging management; 3G call and event data for the Circuit Switched (CS) domain | TS | 3.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.005/32005-370.zip | The present document is concerned with the administration of subscriber related event and call data. This includes both the collection of call data from, and the distribution of tariff data to, the Network Elements.
The subscriber (IMSI) and mobile equipment (IMEI) related call and event data collected is employed by a number of management activities including billing & accounting, statistical analysis and customer care.
The tariff data in the Network Elements is required to support the supplementary service "Advice of Charge".
The aim of the present document is to describe both the network management functions required and the data involved. |
32.015 | Telecommunications management; Charging management; 3G call and event data for the Packet Switched (PS) domain | TS | 3.12.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.015/32015-3c0.zip | The GSM and UMTS PLMN support a range of packet-based services in the same network. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions. The present document describes the functionality of charging, which includes the General Packet Radio Service (GPRS) in GSM and UMTS, as defined in 3GPP TS 22.060 [3] and 3GPP TS 23.060 [8] (packet based services). |
32.101 | Telecommunication management; Principles and high level requirements | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-340.zip | |
32.102 | Telecommunication management; Architecture | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-320.zip | |
32.104 | Telecommunication management; 3G Performance Management | TS | 3.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.104/32104-390.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a 3G network. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in the Network Elements (NEs) and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The basic Performance Management concept that the present document is built upon is described in clause 4. The requirements how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Annex A specifies the file format for the bulk transfer of performance measurement results to the NM, while annex B discusses the file transfer procedure utilised on that interface. A set of measurements available for collection by NEs are described in annex C, effort has been made to ensure consistency in the definition of measurements between different NEs.
The following is beyond the scope of the present document, and therefore the present document does not describe:
- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objectives of this standardisation are:
- to provide the descriptions for a standard set of measurements;
- to produce a common description of the management technique for measurement administration and result accumulation; and
- to define a method for the bulk transmission of measurement results across a management interface.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor 3G network, for those measurement types that can be standardised across all vendors' implementations.
As far as possible, existing standardisation in the area of Performance Management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
The present document considers all the above aspects of Performance Management for a 3G network and its NEs defined in the 3G core Technical Specifications. However, only those aspects which are specific to a 3G system and particular to 3G-network operation are included in the present document. |
32.106-1 | Telecommunication management; Configuration Management (CM); Part 1: Concept and requirements | TS | 3.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-1/32106-1-310.zip | The present document describes the Configuration Management (CM) aspects of managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 32.102 [2].
The present document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant 3G NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality.
Clause 7 contains the specific definitions for the standardised N interface, which are necessary to follow for compliance to this specification.
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 [1] and 3G TS 32.102 [2]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as by other specifications for Telecom Management produced by 3GPP. All these are included in Parts 2 through 8 of the present document as follows:
Notification IRP Information Service Version 1: 32.106 Part 2
Notification IRP CORBA Solution Set Version 1:1: 32.106 Part 3
Notification IRP CMIP Solution Set Version 1:1: 32.106 Part 4
Basic Configuration Management IRP Information Model (including NRM) Version 1: 32.106 Part 5
Basic Configuration Management IRP CORBA Solution Set Version 1:1: 32.106 Part 6
Basic Configuration Management IRP CMIP Solution Set Version 1:1: 32.106 Part 7
Name Convention for Managed Objects: 32.106 Part 8 |
32.106-2 | Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service (IS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-2/32106-2-330.zip | Network Elements (NEs) under management generate events to inform event receivers about occurrences within the network that may be of interest to event receivers. There are a number of categories of events. Alarm, as specified in Alarm IRP: Information Service 3GPP TS 32.111-2 [1], is one member of this category.
The purpose of Notification IRP is to define an interface through which an IRPManager (typically a network management system) can subscribe to IRPAgent (typically an Element Manager (EM) or a NE) for receiving network events. It also specifies attributes carried in the network events. These attributes are common among all event categories. Attributes that are specific to a particular event category are not part of the present document. For example, perceivedSeverity is an attribute specific for alarm event category. This attribute is not defined the present document but in Alarm IRP 3GPP TS 32.111-2 [1]. |
32.106-3 | Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-3/32106-3-330.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.106-2 [5]). |
32.106-4 | Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 3.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-4/32106-4-321.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.106-2 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5. |
32.106-5 | Telecommunication management; Configuration Management (CM); Part 5: Basic CM Integration Reference Point (IRP): Information model (including Network Resource Model (NRM) | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-5/32106-5-320.zip | The present document (Basic Configuration Management (CM) IRP: Information Model) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate basic Configuration Management related information to one or several 'IRPManagers' (typically Network Managers). This version of the IRP is mainly intended for “passive management” of high-level network configuration and status information as required by a Network Manager.
The present document is divided in three main parts:
1. specifies a generic IRP Information Service with operations and notifications to be used by an ‘IRPManager’ to retrieve information on managed objects maintained by an ‘IRPAgent’.
2. specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Managed Object Classes.
3. defines the UMTS management NRM by reusing this generic model either by direct reuse or sub-classing.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like Security management, Software management, Network & Service provisioning, etc. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs are consistent. The Basic CM IRP here provides a base for all CM-related resource modelling.
To summarize, the Basic CM IRP has three main purposes:
(1) to define an interface for retrieval of Configuration Management information,
(2) to define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit, and
(3) to define the applied UMTS management Network Resource Model. |
32.106-6 | Telecommunication management; Configuration Management (CM); Part 6: Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-6/32106-6-340.zip | The purpose of this Basic Configuration Management (CM) IRP: Information Service CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.106-5 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
The present document does not describe any Network Resource Model (NRM) – this is described in 3GPP TS 32.106-5 [4]. Please note that 3GPP TS 32.106-5 [4] defines an IRP Information Model, which comprises both an IS and NRM definition. |
32.106-7 | Telecommunication management; Configuration Management (CM); Part 7: Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 3.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-7/32106-7-330.zip | The present document defines a CMIP Solution Set for the Basic CM IRP introduced in 3GPP TS 32.106-5 [15].
The version of this CMIP Solution Set is 1:1, where the first “1” means that it corresponds to the Information Model version 1, and the second “1” means that it is the first CMIP Solution Set corresponding to Information Model version 1.
Clause 4 maps the protocol- and technology-independent operations, parameters, notifications and the Network Resource Model specified in the Basic CM IRP Information Model (Chapter 6 of 3GPP 3GPP TS 32.106-5 [15]) onto the corresponding CMIP/CMISE equivalences. The important technical aspects specific to this CMIP Solution Set are also described there. The GDMO definitions are introduced in Clause5. Clause 6 contains the ASN.1 definitions related to the GDMO definitions provided in clause 5. |
32.106-8 | Telecommunication management; Configuration Management (CM); Part 8: Name convention for Managed Objects | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-8/32106-8-320.zip | A more detailed background and introduction of the IRP concept is given in 3G TS 32.101 [11] and 3G TS 32.102 [12].
To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context.
To facilitate integration of network management information obtained via multiple IRPs of different technologies such as CMIP and CORBA, identical network resource name semantics must be conveyed in all IRPs. The present document specifies one such name convention. |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-320.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 3.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-340.zip | |
32.111-3 | Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 3.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-3/32111-3-360.zip | The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.111-2 V7.1.X. |
32.111-4 | Telecommunication management; Fault Management; Part 4: Alarm Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-4/32111-4-320.zip | The present document defines the alarm integration reference point for the CMIP solution set. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.111-2 (V6.3.X). |
33.102 | 3G security; Security architecture | TS | 3.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-3d0.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.103 | 3G security; Integration guidelines | TS | 3.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-370.zip | This technical specification defines how elements of the 3G-security architecture are to be integrated into the following entities of the system architecture.
- Home Environment Authentication Centre (HE/AuC)
- Serving Network Visited Location Register (VLR/SGSN)
- Radio Network Controller (RNC)
- Mobile station User Identity Module (UIM)
- Mobile Equipment (ME)
This specification is derived from 3G "Security architecture". [1]
The structure of this technical specification is a series of tables, which describe the security information and cryptographic functions to be stored in the above entities of the 3G system.
For security information, this is in terms of multiplicity, lifetime, parameter length and whether mandatory or optional.
For the cryptographic functions, the tables also include an indication of whether the implementation needs to be standardised or can be proprietary.
The equivalent information for the alternative Temporary Key proposal is included in an appendix to this document. |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 3.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-380.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-310.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 3.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-350.zip | |
33.120 | Security Objectives and Principles | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-300.zip | The present document gives the objectives and principles of 3GPP security.
The principles state what is to be provided by 3G security as compared to the security of second generation systems. The principles will also ensure that 3G security can secure the new services and new service environments offered by 3G systems.
The objectives give general, high level requirements for 3GPP security which will be expanded upon in 3G TS 21.133 [1].
The priorities for the implementation of 3GPP security are also given. |
33.901 | Criteria for cryptographic Algorithm design process | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-300.zip | This report discusses the possibilities for acquisition of the cryptographic algorithms that has to be standardised in UMTS. The focus is on the encryption function used in the data confidentiality mechanism and the message authentication function used in the signalling data integrity mechanism.
First certain aspects of the process and desired results for an algorithm specification and their pro's and cons will be given. These aspects will include the possible design strategies, the evaluation strategies, the possibilities for distribution of the algorithms and the options for the liability and responsibility for the algorithm.
Then a number of the most realistic scenarios for the algorithm specification will be presented. These scenarios will be used as a basis to make a final choice for the specification process for cryptographic algorithms in third generation mobile systems. Finally, a preferred procedure will be described. |
33.902 | Formal Analysis of the 3G Authentication Protocol | TR | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-310.zip | This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol.
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 refers to the main body of this report. The main body is only referred to because it is not available in Word-, but only in pdf-format. The corresponding .pdf-documents are attached to this document. |
33.908 | 3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-300.zip | This technical report is a description of the work undertaken by SAGE Task Force for the design of the standard 3GPP Confidentiality and Integrity Algorithms (SAGE TF 3GPP), and to formally approve the release of these algorithms to 3GPP.
With regard to the design of the algorithms, the scope of the present document is confined to a description of the design criteria, the design methodology and an outline of the content and structure of the specification and test data documents.
The standard 3GPP Confidentiality and Integrity Algorithms are based on a Block Cipher named KASUMI. The algorithms specification and associated test data are documented in the Specification of the 3GPP Confidentiality and Integrity Algorithms which consists of the following four documents:
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 specifications (TS 35.201).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI algorithm specification (TS 35.202).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' test data (TS 35.203).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design conformance test data (TS 35.204).
With regard to the evaluation of the algorithm, the scope of this report is restricted to a description of the evaluation criteria, the method of evaluation and the main conclusions from the evaluation that led to the Task Force approving the specification. A detailed summary of conclusions of the evaluation is provided in a public evaluation report [3] produced by the Task Force. |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 3.16.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-3g0.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 | 3.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-3a0.zip | |
34.121 | Terminal conformance specification, Radio transmission and reception (FDD) | TS | 3.14.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-3e0.zip | The present document specifies the 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.
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.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 3.12.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-3c0.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 | 3.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-350.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 | 3.5.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-350.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 | 3.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-340.zip | |
34.901 | Test Time Optimisation based on statistical approaches; Statistical theory applied and evaluation of statistical significance | TR | 3.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.901/34901-300.zip | The present document describes the statistical theory and concepts applied in the conformance test of the user equipment (UE) so as to improve test speed. |
34.907 | Report on electrical safety requirements and regulations | TR | 3.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.907/34907-300.zip | The present document, that will not be maintained, provides information describing the situation in March 1999.
The present document provides the information on electrical safety requirements for Information and Technical equipment including 3G mobile phone in each country and region.
[The main objective of the present document is to give an outline on electrical safety in each country and region, to people who are not familiar with this issue. Therefore, the information in the present document will not be kept updated with the latest information.] The present document summarizes the differences between international standards IEC60950 and national standards and also refers to regulations with regard to the conformity assessment because each country has standards, which are different from other countries.
Most information in the present document is quoted from IEC's publications. Therefore the present document neither defines any new electrical safety requirements nor contradicts IEC's policy. |
34.925 | Specific Absorption Rate (SAR) requirements and regulations in different regions | TR | 3.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.925/34925-300.zip | The present document, that will not be maintained, provides information describing the situation in May 1999.
The present document provides information on Radio Frequency (RF) exposure limits and assessment methods for IMT-2000 terminals. It summarises international, regional and national recommendations, standards and regulations relevant to current and future mobile communication devices.
The present document cover only terminal devices that are normally operated close to the user, approximately within 20 cm of any part of the body. For other IMT-2000 RF transmitting equipment, for example base stations, other RF exposure standards, limits and assessment methods than those described in the present document may be applied.
The present document does not define any new RF exposure limits or assessment methods. It refers to recommendations, standards and regulations that already exist or are under development. Like other existing mobile communication terminals, IMT-2000 terminals will be recommended or requested to comply with these guidelines. |
35.201 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification | TS | 3.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.201/35201-320.zip | |
35.202 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification | TS | 3.1.2 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.202/35202-312.zip | |
35.203 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data | TS | 3.1.2 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.203/35203-312.zip | |
35.204 | 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data | TS | 3.1.2 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.204/35204-312.zip | |
55.216 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specifications | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.216/55216-300.zip | |
55.217 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.217/55217-300.zip | |
55.218 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design conformance test data | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.218/55218-300.zip | |
55.919 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 4: Design and evaluation report | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.919/55919-300.zip | |
24.437 | Digital asset, Spatial mapping and Spatial anchors server - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; | TS | 0.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.437/24437-010.zip | The present document specifies the protocol aspects and APIs for the metaverse application over the 3GPP network for SAn-UU and SM-UU reference points. The APIs are specified as RESTful APIs except for custom operations wherever required.
The present document is applicable to the user equipment (UE) supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor client functionalities as described in 3GPP TS 23.437 [2], to the application server supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor server functionalities as described in 3GPP TS 23.437 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
NOTE: The specification of the VAL server for a specific VAL service is out of scope of the present document. |
35.237 | Specification of the MILENAGE-256 algorithm set: An example set of 256-bit 3GPP Authentication and Key Generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 4: Summary and Results of Design and Evaluation | TS | 0.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.237/35237-010.zip | Editor's Note: This clause contains scope information from ETSI SAGE for selected option.
The present document … |
37.719-11-10 | Rel-19 Dual Connectivity of EN-DC and NE-DC configurations with one or two NR Supplemental Uplink (SUL) band(s) and with/without UL sharing from the UE perspective (ULSUP) | TR | 0.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.719-11-10/37719-11-10-010.zip | The present document is a technical report for Rel-19 Dual Connectivity of EN-DC and NE-DC configurations with one or two NR Supplemental Uplink (SUL) band(s) and with/without UL sharing from the UE perspective (ULSUP). The purpose is to gather the relevant background information and studies in order to address SUL for the Rel-19 bands/band combinations.
This TR contains a general part and specific band combination part. The actual requirements are added to the corresponding technical specifications. |
33.742 | 5G Security Assurance Specification (SCAS); Split gNB product classes | TS | 0.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.742/33742-030.zip | The present document contains objectives, requirements and test cases that are specific to the various split gNB network product classes. The gNB can be deployed as more than one entity by splitting the gNB into gNB-CU and gNB-DU(s) and possibly further splitting the gNB-CU into gNB-CU-CP and gNB-CU-UP(s) (see TS 38.401 [5]). Test cases for such deployments are provided. The present document refers to the Catalogue of General Security Assurance Requirements (see TS 33.117 [2]) and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the various split gNB network product class. |
33.929 | Lawful Interception (LI) implementation guidance | TR | 0.0.21 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.929/33929-00l.zip | The present document provides architectural diagrams, conceptual scenarios, flow-diagrams, examples, and other background information which can be useful to implement the LI functions defined in TS 33.126 [2], TS 33.127 [3] and TS 33.128 [4]. |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 3.19.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-3j0.zip | |
28.544 | Management and orchestration; Self-Organizing Networks (SON) for 5G networks; Network Resource Model (NRM) | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.544/28544-000.zip | The present document … |
33.535 | Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) | TS | 16.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.535/33535-g20.zip | |
36.276 | Overall description of LTE-based 5G broadcast | TR | 1.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.276/36276-100.zip | The present document provides an overview and overall description of the LTE-based 5G terrestrial broadcast comprising:
- a service delivering Free To Air content [2];
- a radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- Receive Only Mode (ROM) devices and UEs supporting FeMBMS [4] as receivers.
Details of the radio interface protocols and procedures are specified in companion specifications of the 36 series.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
38.173 | TDD operating band in Band n48 | TS | 0.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.173/38173-001.zip | The present document is a technical report for the work item of TDD operating band in Band n48. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 16.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-g00.zip | |
22.969 | Feasibility study on enhancements of Public Warning System (PWS) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.969/22969-100.zip | The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements. |
24.568 | WLAN connectivity for 5GS Management Object (MO) | TS | 0.1.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.568/24568-011.zip | The present document defines WLAN connectivity for 5GS management objects used by the network and the UE.
The Management Objects consist of following relevant parameters for:
- WLAN access network discovery; and
- non-3GPP access node (e.g. N3IWF) selection;
that can be managed by the network.
Editor's note: The content of scope will have more information when related stage 2 is completed. |
28.542 | Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 1 | TS | 1.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.542/28542-100.zip | The present document specifies the requirements for the Network Resource Model (NRM) definitions of 5G Core Network (5GC), to support the management of variety of 5GC network functions and features defined in 3GPP TS 23.501 [2]. |
28.543 | Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 2 and stage 3 | TS | 1.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.543/28543-110.zip | The present document specifies the Information Model definitions and Solution Set definitions for 5G Core Network (5GC) network resource model, to fulfil the requirements identified in 3GPP TS 28.542 [2].
The Information Model definitions define the semantics and behaviour of information object class attributes and relations visible on the management interfaces in a protocol and technology neutral way. And Solution Set definitions define one or more solution set(s) with specific protocol(s) according to the Information Model definitions |
28.546 | Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 2 and stage 3 | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.546/28546-030.zip | The present document … |
28.551 | Management and orchestration of networks and network slicing; Performance Management (PM); Stage 2 and stage 3 | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.551/28551-030.zip | |
28.553 | Management and orchestration of networks and network slicing; 5G Core Network (5GC) performance measurements and assurance data | TS | 0.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.553/28553-040.zip | This document specifies the performance measurements and assurance data for 5GC Network Functions.
The performance measurements and assurance data are defined based on the measurement template as described in TS 32.404 [3]. |
29.516 | 5G System; Interworking between 5G Network and external Data Networks; Stage 3 | TS | 0.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.516/29516-010.zip | The present document defines the stage 3 interworking procedures for 5G Network interworking between:
a) PLMN and external DN; and
b) PLMN and PLMN.
The stage 2 requirements and procedures are contained in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
For interworking between 5G PLMN and external DNs, the present document is valid for both 3GPP accesses and non-3GPP accesses. |
32.159 | TS template for stage 2 and stage 3 of management service definitions | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.159/32159-000.zip | The present document contains the template to be used for the production of all Management Services stage 2 and stage 3 specifications. |
36.934 | LTE Extended 1.5 GHz SDL band (1427 – 1518 MHz) | TR | 0.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.934/36934-010.zip | The present document is a technical report for the LTE Extended 1.5 GHz FDD supplemental downlink (SDL) band covering 1427 – 1518 MHz. It is intended to be specified for E-UTRA for operations at least in Europe with the possibility of other countries outside of Europe. As it is defined as SDL, the band is to be used in CA for E-UTRA. The LTE CA combination of Band 20 + FDD SDL Band 1427 – 1518 MHz has selected. |
38.141 | NR; Base Station (BS) conformance testing | TS | 0.0.3 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.141/38141-003.zip | The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Base Station (BS). These have been derived from, and are consistent with the NR BS specification defined in [2]. The technical specification is in 2 parts, part 1 covers conducted requirements and part 2 covers radiated requirements. |
38.475 | NG-RAN; F1 interface user plane protocol | TS | 0.3.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.475/38475-030.zip | The present document specifies the F1 user plane protocol being used over the F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 15.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-f00.zip | |
21.866 | Study on Energy Efficiency Aspects of 3GPP Standards | TR | 1.3.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.866/21866-130.zip | The present document identifies and studies the key issues and the potential solutions in defining Energy Efficiency Key Performance Indicators and the Energy Efficiency optimization operations in existing and future 3GPP networks.
The study includes:
- identifying the 3GPP system wide high-level goals and feasible tasks including the definition of system-wide energy efficiency KPIs where it is applicable to systematically address energy efficiency aspects more effectively;
- investigating feasible common approaches and methodology including the assessment of the relevance and the applicability of existing energy efficiency definitions and the related work to address and improve 3GPP system-wide energy efficiency.
Recommendations are provided applicable to EPS (taking into account backward compatibility to legacy UEs), and to 5G systems. |
23.782 | Study on mission critical communication interworking between LTE and non-LTE systems | TR | 0.6.1 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.782/23782-061.zip | The objective of this technical report is to study and identify solutions suitable for interworking between LTE mission critical systems and non-LTE mission critical systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [2] and the MCData requirements in 3GPP TS 22.282 [20] (SDS only).
The present document refers to an IWF entity as an editorial convenience. The structure and functionality of the IWF is out of scope of the present document. The definition of IWF-1 and interactions with IWF-1 by the MCPTT system and the definition of IWF-2 and interactions with IWF-2 by the MCData (SDS only) are in scope of the present document. |
23.798 | Study on Isolated E-UTRAN Operation for Public Safety; Enhancements | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.798/23798-060.zip | The present document studies potential enhancements to the "Isolated E-UTRAN Operation for Public Safety" feature specified in TS 23.401 [2].
Whereas this feature assumes a complete absence of backhaul, the present study considers following cases:
- the backhaul is not completely lost but suffers from a limited bandwidth, which does not suffice for normal operation; or
- the backhaul is completely lost and a backup link is set up (by means outside the scope of this study) to provide backhaul with a limited bandwidth as above.
Under such scenario it is desirable to use the available backhaul for signalling between an E-UTRAN site and other PLMN entities, for local mission critical communications. The present document studies enhancements to realize this in an optimal manner. |
26.918 | Virtual Reality (VR) media services over 3GPP | TR | 0.7.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.918/26918-070.zip | |
26.931 | Evaluation of Additional Acoustic Tests for Speech Telephony | TR | 0.2.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.931/26931-021.zip | |
26.932 | Study on User Equipment (UE) characteristics and performance for video telephony | TR | 0.3.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.932/26932-030.zip | [The present document reports the study on video UE characteristics and performance for video telephony.
It identifies some of the UE characteristics that impact the video telephony quality of experience beyond those related to the acoustic performance already specified for speech.
For these characteristics that are specific to video and video call, the document investigates the technical metrics that can be used to assess their performance level. It is also discusses the related possible requirements or objectives that could be specified to achieve the minimum quality of experience expected for the 3GPP video telephony services.
This Technical Report finally studies how these performance requirements/objectives can be verified and the suitable test methodologies are proposed and described where needed.] |
28.801 | Telecommunication management;Study on management and orchestration of network slicing for next generation network | TR | 1.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.801/28801-130.zip | The present document investigates and makes recommendations on management and orchestration for network slicing on the Network Slice Instance Layer [2] and for non-virtualised NE's also the Resource layer:
1) Use cases and requirements for management and orchestration of network slicing
2) Management and orchestration terminology and concepts for slices. The relationship between network slice management and orchestration concepts developed in the present document and the management and orchestration concepts defined by ETSI NFV.
3) Management of network function sharing in the context of network slicing (e.g. network function sharing support, and lifecycle management functions of the mobile network resources for network slices).
4) Impacts to management when a slice instance is shared between multiple parties (e.g. multiple partners and multiple domains etc.) based on the slice sharing, see reference 3GPP TR 23.799 [2].
5) Isolation of management data between different parties within a slice instance if needed.
6) Impacts derived from Management of 3GPP Network Slices on the ETSI MANO architecture and procedures.
7) Automation of management and orchestration of network slice instances and the related policy configurations.
8) Management and orchestration mechanisms to support the isolation/separation of mobile network resources used by different network slice instances and the corresponding configuration of isolation/separation.
9) Solution for management and orchestration of network slicing and how it affects the specifications (e.g. Interface IRPs, Network Resource models and trace specifications).
Furthermore, the 3GPP role for Service Instance Layer has been investigated.
The Resource layer for VNFs is excluded from the present document. |
28.802 | Telecommunication management;Study on management aspects of next generation network architecture and features | TR | 0.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.802/28802-080.zip | The present document studies the management aspects of next generation network architecture and features.
The study includes:
- the use cases for management aspects of the next generation network in terms of network architecture and high level features;
- the potential impact of the next generation network architecture and high level features to the functional blocks of 3GPP management system;
- the location and role of management functionality to support next generation network architecture;
- the potential management related requirements for the next generation network in terms of network architecture and high level features;
- the possible solutions to support the management requirements brought from the end to end next generation network architecture;
- the possible solutions of management aspects to support the key features of the next generation network.
The study also makes conclusions on the preferred solution(s), and provides recommendations based on the conclusions of the study. |
29.387 | V2X Control Function to V2X Application Server aspects (V2); Stage 3 | TS | 0.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.387/29387-010.zip | This document defines the stage 3 specification of V2 reference point between the V2X Control Function and V2X Application Server.
The V2 reference point and related stage 2 procedures are defined in 3GPP TS 23.285 [2]. |
32.151 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 14.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-e00.zip | The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. |
32.152 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire | TS | 14.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-e10.zip | 3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire. |
32.856 | Study on Operations, Administration and Maintenance (OAM) support for assessment of energy efficiency in mobile access networks | TR | 1.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.856/32856-110.zip | The present document reports how 3GPP OAM specifications can provide support for the assessment of energy efficiency in radio access networks as defined by ETSI ES 203 228 [2], thanks to measuring both network performance and energy consumption. It provides a gap analysis between ETSI ES 203 228 [2] and 3GPP OAM Technical Specifications, and provides recommendations towards ETSI ES 203 228 [2] compliance, including suggestions for further 3GPP specification enhancements. It also provides an analysis of how ETSI ES 202 336-12 [31] architecture, interfaces and information model may fit with the 3GPP management reference model defined in 3GPP TS 32.101 [32] and 3GPP IRPs, identifies potential use cases and requirements and studies potential solutions for interfaces that are in the scope of 3GPP. Finally, it provides recommendations for normative work. |
32.857 | Study on management aspects of selected Internet of Things (IoT)-related features | TR | 0.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.857/32857-070.zip | This document investigates management aspects of LTE IoT related functionalities such as eMTC and NB-IoT RAN Features, to identify functionalities that should be added to the existing 3GPP OAM specifications. The document outlines basic use cases, sets potential requirements and suggests potential solutions. |
32.865 | Study on Operations, Administration and Maintenance (OAM) aspects of Self-Organizing Network (SON) for Active Antenna System (AAS) based deployments | TR | 1.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.865/32865-120.zip | The present document studies the OAM aspects of SON (Self-Organizing Network) for AAS (Active Antenna Systems) based deployments in LTE.
The study includes use cases, potential requirements and possible solutions of OAM aspects of SON for AAS-based deployments in LTE, for both OAM centralized architecture and eNB distributed architecture with OAM supervision.
The study also makes conclusions on the preferred solution(s), and provides recommendations based on the conclusions of the study. |
33.899 | Study on the security aspects of the next generation system | TR | 1.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.899/33899-130.zip | NOTE: TR 33.899 is a collection of proposed security requirements, and solutions that were collected during the study of the next generation architecture. The study item was stopped in August 2017. The content of TR 33.899 reflects the state of the work when the study item was stopped. Proposed requirements and solutions are not fully evaluated.
In the scope of this TR are the threats, potential requirements and solutions for the security of next generation mobile networks.
The work will include:
- Collection, analysis and further investigation of potential security threats and requirements for the next generation systems, based on the service, architectural and radio related requirements for the next generation mobile networks.
- Investigation of the security architecture and access security.
The complete or partial conclusions of this study will form the basis for the normative work and/or for any further study.
The security threats and requirements, and the security architecture may additionally include standalone security topics. These topics may not be covered by the security work described above but they shall not be in conflict with service, architectural or radio related requirements for next generation mobile networks. It is part of the study to determine whether such topics need to be dealt with, and, if so, what they are. |
37.843 | Evolved Universal Terrestrial Radio Access (E-UTRA) and Universal Terrestrial Radio Access (UTRA); Radio Frequency (RF) requirement background for Active Antenna System (AAS) Base Station (BS) radiated requirements | TR | 0.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.843/37843-070.zip | The present document is the Technical Report for the Work Item on Base Station (BS) radiated Radio Frequency (RF) requirements for Active Antenna System (AAS) [2]. The present document captures the background and the decisions on the specification of radiated RF requirements that are applicable to AAS BS.
The AAS BS specification contains requirements for both single RAT UTRA FDD, UTRA TDD and E-UTRA as well as MSR (including single RAT MSR requirements for each of the RATS), it was agreed that it may not be necessary to support so many variants for the OTA AAS BS hence a specification complexity reduction investigation was carried out. It was found the following was not needed for the OTA AAS BS requirements:
1. Radiated requirements applicable for eAAS not support UTRA TDD.
2. Radiated requirements applicable for eAAS not include UTRA pilot requirements.
NOTE: In Rel-15, multiple clauses related to the OTA measurements of the BS were shifted to the OTA BS testing TR 37.941 [36], which includes such aspects as e.g., test tolerance and measurement uncertainty derivations, OTA test chambers descriptions, calibration and test procedure descriptions, etc.. |
41.033 | Lawful Interception requirements for GSM | TR | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-e00.zip | This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in 3GPP TS 43.033. |
22.802 | Study on scenarios where multiple APNs are needed | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.802/22802-100.zip | The scope of this study is:
- to provide details about the use cases where there is a need of control of APNs;
- to identify potential new requirements to fulfil the use cases;
- to identify potential solutions to fulfil the use cases;
The scope of the study is focussed on Machine-To-Machine UEs but can take into account a more generic set of UEs.
This study will identify what connectivity use-cases that are needed to be fulfilled, and study if multiple APN or a multi-purpose APN per subscription (IMSI) combined with other 3GPP specified features can support those connectivity use-cases. The study will also analyse the impacts in scenarios where the service provider decides to change the MNO. |
22.815 | Study on Multimedia Broadcast Supplement for Public Warning System (MBSP) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.815/22815-100.zip | This TR considers enhancements to 3GPP PWS via the addition of multimedia broadcast capability. The use cases for this capability are documented and derived requirements are gathered and consolidated. This TR does not cover use cases or potential requirements for specific PWS based systems (i.e. ETWS, CMAS, EU-ALERT, and Korean Public Alert System).
This TR covers:
- Scenarios and use cases to provide multi-media information supplemental to PWS;
- UE awareness of, and ability to receive, multi-media information via PWS;
- Handling of UEs in limited service mode;
- Priority of multimedia information |
22.818 | Feasibility Study on Control of Applications when Third party Servers encounter difficulties | TR | 2.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.818/22818-200.zip | With the spread of applications on UEs (also known as "smart phones"), coupled with the rapidly growing number of UEs designed for usage with little or no human involvement (machine type communications), the potential for issues to occur in the overall "system" involving these applications and the third party entities they interact with increases. When these third party entities experience difficulties, they may be able to manage their problems without undue impact on operator networks, but there will be times when they are not able to do so.
When a third party server becomes congested or fails, the communication by the UE applications that make use of that server need to be controlled so that excessive use of 3GPP network resources is avoided while not affecting other applications and their associated servers that are functioning normally.
The 3GPP network needs to be able to detect or receive an indication from a third party server of its congestion status or failure status and control UE applications (or their traffic in the 3GPP network) that make use of a third party server that has encountered difficulties. HTTP and other third party (possibly proprietary) protocols can have status codes but these can be insufficient as they cannot provide a suitable indication to the UE application of the nature of the issue and therefore could result in frequent retries even when these will fail, thus burdening the network with connection attempts that will fail.
The present document identifies potential requirements that will enable the 3GPP network to detect or receive an indication from a third party server of its congestion status or failure status and control the traffic of individual UE applications (or their traffic in the 3GPP network) when the 3GPP network becomes aware that a third party server has run into difficulties. This will make it possible to
- Reduce or avoid unproductive traffic in 3GPP network (i.e., traffic that the 3rd party server is not able to receive) by blocking it either in the UE or in the 3GPP network (primary objective)
- Allow 3GPP network to help 3rd party servers to handle overload and recover from failures (secondary objective) |
22.899 | Study on enhancements to user location reporting support | TR | 2.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.899/22899-200.zip | |
23.717 | Enabling Transcoder Free Operation During SRVCC (PS to CS) | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.717/23717-100.zip | Editor's note: This clause will define the scope of the Stage 2.
This TR describes various alternatives to enhance the SRVCC procedures to enable Transcoder free operation (TrFO) where possible and ensure that the proper CS radio resources are reserved for optimal RAN codec. |
24.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.234/24234-d00.zip | The present document specifies the network selection, including authentication and access authorization using authentication, authorization and accounting (AAA) procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification the network includes the WLAN and 3GPP network.
Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology specific protocols, however this signalling is transparent to the WLAN.
Tunnel management procedures are defined to be independent of the underlying WLAN access technology and as such can be reused independently of the underlying technology.
The present document specifies procedures within I-WLAN necessary in order for IMS emergency calls to be supported when I-WLAN is used as the underlying access network. These involve both network selection as well as tunnel management procedures.
WLAN Network Selection supersedes I-WLAN for UE WLAN selection as specified in 3GPP TS 24.302 [28] from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications. |
24.235 | 3GPP System to Wireless Local Area Network (WLAN) interworking Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.235/24235-d00.zip | This document defines the 3GPP System to Wireless Local Area Network interworking Management Object (MO) for I-WLAN PLMN selection as specified in 3GPP TS 24.234 [3]. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD_DM-V1_2 [2].
The 3GPP System to Wireless Local Area Network interworking Management Object consists of relevant parameters that can be managed for WLAN UE as specified in 3GPP TS 24.234 [3].
The Access Network Discovery and Selection Function MO as specified in 3GPP TS 24.312 [13] supercedes the Wireless Local Area Network interworking MO for I-WLAN PLMN selection from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-d00.zip | |
24.327 | Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN) and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.327/24327-d00.zip | This document specifies the signalling procedures for handling the mobility of a UE between 3GPP Wireless Local Area Network Interworking (I-WLAN) and GPRS systems.
The present document is applicable to the User Equipment (UE) and the network nodes supporting mobility between 3GPP I-WLAN and GPRS systems.
In addition, the present document specifies the procedures used between the UE and the network nodes for the attach and the detach cases. It also specifies how the UE performs handover when moving from 3GPP I-WLAN to GPRS systems and vice-versa.
This document is based on DSMIPv6 procedures specified in 3GPP TS 24.303 [3] and will specify additional details specific to the 3GPP I-WLAN and GPRS systems in the context of mobility. |
26.879 | Mission Critical Push To Talk (MCPTT); Media, codecs and Multimedia Broadcast/Multicast Service (MBMS) enhancements for MCPTT over LTE | TR | 13.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.879/26879-d00.zip | The present document covers the enhancement required to support MCPTT. |
26.916 | Media handling and Quality aspects of SRVCC | TR | 1.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.916/26916-110.zip | Enhanced Single Radio - Voice Call Continuity (eSRVCC) is an existing standard ([3], [4]) specifying the handover of a Voice or Video call from LTE access to CS-radio access, either to GERAN (2G) or to UTRAN (3G) or other CS networks. The present document considers only enhanced SRVCC for voice calls between 3GPP accesses.
This study assumes that the Codecs defined in TS 26.114 are used on the LTE access and the Codecs defined in 3GPP TS 26.103 [7] on the CS accesses. Since Rel-13, the specifications for CS networks include the Codec Type UMTS_EVS with several Configurations, called UMTS_EVS (Set 0) to UMTS_EVS (Set 3).
In the IMS Core Network, the voice call is typically anchored in the ATCF/ATGW (Access Transfer Control Function/ Access Transfer Gate Way).
The eSRVCC procedure, as specified, may cause additional transcoding between the target radio leg and the ATGW, even though in theory it would be possible to avoid it. As a result, the eSRVCC procedures may add one or more unnecessary transcoding point(s) for the call and thereby degrade the quality of the ongoing call unnecessarily.
The main objectives of this study are to analyse example call scenarios and find potential solutions to minimize the number of transcoding cases. Another objective is to optimize the interworking and the transition between EVS and AMR-WB during eSRVCC. The study should also show the reasons and potential solutions for too long speech path interruptions during eSRVCC.
The present Technical Report has the following detailed objectives:
- Identify relevant eSRVCC scenarios, especially with Codec Mode Control;
from AMR-WB and/or EVS in VoLTE to AMR-WB and/or EVS in CS;
but include also other important Codecs, such as AMR and G.722.
- Analyse Speech Quality Aspects and Media Handling Aspects, based on these scenarios.
- Analyse Codec Mode Control before, during and after eSRVCC;
recently SA4 has clarified some essential details on Rate Control for AMR and AMR-WB;
Rate Control and Audio Bandwidth Control for EVS are still under discussion to some extent.
- Analyse the existing SDP Offer - Answer protocol between Target MSC and Anchor-ATCF during eSRVCC,
as specified in 3GPP TS 23.216 [3], Stage 2;
This analysis will include the whole eSRVCC procedure for at least one essential scenario
(e.g. eSRVCC to GERAN) and will identify the potential reasons for transcoding and too long speech path interruptions.
- Clarify the existing Codec Compatibility aspects for eSRVCC;
especially the interworking between CS and IMS for AMR, AMR-WB and EVS needs to be documented.
- Propose enhancements for media and quality aspects of eSRVCC with the aims:
a) to avoid transcoding cases as much as possible;
b) to minimize the speech path interruption time during eSRVCC;
- Support the SA2 SETA work by SA4 expertise in speech quality and media handling. |
26.953 | Interactivity support for 3GPP-based streaming and download services | TR | 0.8.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.953/26953-080.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.