id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
34.123-3 | User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS) | TS | 3.9.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-3/34123-3-390.zip | |
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 … |
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 | |
33.84 | Study on security aspects of the disaggregated gNB architecture | TR | 0.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.84/3384-020.zip | |
24.89 | CT WG1 aspects of 5G; System Phase 1 | TR | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.89/2489-g00.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 … |
28.9 | Telecommunications management; Study on integration of Open Network Automation Platform (ONAP) ata Collection, Analytics and Events (DCAE) and 3GPP reference management architecture | TR | 1.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.9/289-101.zip | |
31.89 | CT WG6 aspects of 5G System Phase 1 | TR | 16.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.89/3189-g00.zip | |
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 | |
44.16 | General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol Iu mode | TS | 16.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.16/4416-g00.zip | |
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]. |
28.9 | Telecommunications management; Study on integration of Open Network Automation Platform (ONAP) ata Collection, Analytics and Events (DCAE) and 3GPP reference management architecture | TR | 0.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.9/289-070.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. |
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]. |
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. |
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.101 | NR; User Equipment (UE) radio transmission and reception | TS | 0.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101/38101-001.zip | |
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 | |
44.16 | General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol Iu mode | TS | 15.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.16/4416-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 | |
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 | |
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 | |
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.8 | Study on management and orchestration architecture of next generation networks and services | TR | 0.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.8/288-0a0.zip | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
32.87 | Telecommunication management;Charging management;Study on forward compatibility for 3GPP Diameter charging applications | TR | 0.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.87/3287-040.zip | |
32.88 | Telecommunication management;Study on implementation for the partitioning of Itf-N | TR | 0.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.88/3288-090.zip | |
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. |
36.74 | Study of LTE bandwidth flexibility enhancements | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.74/3674-100.zip | |
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 | |
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 | |
44.16 | General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol Iu mode | TS | 14.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.16/4416-e00.zip | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.