id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 561 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
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. |
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 | |
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 | |
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 | |
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 | |
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). |
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. |
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 | |
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 | |
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]. |
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 | |
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 … |
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. |
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. |
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.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 | |
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. |
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. |
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. |
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 | |
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 |
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.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 | |
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. |
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]. |
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 | |
32.837 | Gap analysis between 3GPP SA5 specifications and Next Generation Mobile Networks (NGMN) Next Generation Operations Requirements (NGCOR) | TR | 0.13.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.837/32837-0d0.zip | The present document makes a gap analysis between the Next Generation Mobile Networks (NGMN) Alliance's "Next Generation Converged Operations Requirements (NGCOR) Requirements" [2] as compared to 3GPPRelease 13 OAM Technical Specifications, and provides recommendation towards NGCOR compliance including suggestions for further 3GPP specification enhancements.
This document addresses the compliance information corresponding to the publication of NGCOR phase II, "NGCOR NEXT GENERATION CONVERGED OPERATIONS REQUIREMENTS" V1.4 [22]. |
33.806 | Pilot development of Security Assurance Specification for MME Network Product class for 3GPP network product classes | TR | 0.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.806/33806-090.zip | The present document … |
33.895 | Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 1.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.895/33895-100.zip | The present study investigates the security aspects of the service requirements specified by SA1 in TS 22.101 [11] clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations (e.g. configurations using GBA or not using GBA).
In particular, this study evaluates existing interworking solutions between SSO frameworks and 3GPP authentication mechanisms against the SA1 service requirements. The study is not limited to evaluation of existing interworking solutions and new interworking solutions may be developed as appropriate.
The study covers the security requirements to enable the operator to become the preferred SSO Identity Provider by allowing the usage of credentials on the UE for SSO services, as well as ways for the 3GPP operator to leverage its trust framework and its reliable and robust secure credential handling infra-structure to provide SSO service based on operator-controlled credentials. |
36.833-1-08 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 8 | TR | 0.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-08/36833-1-08-040.zip | The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 8 which was initially approved at TSG RAN #67 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.881 | Study on latency reduction techniques for LTE | TR | 0.8.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.881/36881-080.zip | This document is related to the technical report for the study item “Study on latency reduction techniques for LTE” [2]. The purpose of this TR is to capture the findings from TSG RAN WG2 and WG1 according to their respective objectives, and to draw a conclusion on way forward.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings. |
36.898 | Network Assistance for Network Synchronization | TR | 1.9.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.898/36898-190.zip | The present document captures the results of the study item on Network Assistance for Network Synchronization in LTE in RP-151084 [2]. It identifies the existing LTE functions that may need network based synchronization and their synchronization-related requirements, and reviews and compares techniques for enhancement of RAN functionality. |
37.544 | Universal Terrestrial Radio Access (UTRA) and Evolved UTRA (E-UTRA); User Equipment (UE) Over The Air (OTA) performance; Conformance testing | TS | 2.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.544/37544-210.zip | The present document describes the test procedure for the radiated performances measurements of the user equipment (UE).
The handheld UE measurement procedures explained in this document are defined for roaming bands for the speech mode position (beside the head and beside the head and hand) and hand phantom browsing mode position. Laptop mounted equipment (LME) measurement procedures are defined for roaming bands for the data mode transfer position (laptop ground plane phantom). Laptop embedded equipment (LEE) measurement procedures are defined for roaming bands for the data mode transfer position (free space).
The browsing mode position explained in this document applies when the UE is held in hand, but not pressed against ear (such as web browsing and navigation).
The data mode transfer position (free space) explained in this document applies when the UE is used away from the user’s head. Free space measurements are applicable to devices used in the data mode transfer position that consist of the laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
All bands are potential roaming bands, and the requirements for roaming bands shall therefore be fulfilled for all bands supported by a UE.
Radiated performance of multiple-antenna receivers for handheld UE is defined for roaming bands in free space configuration.
Recommended performance values for operating bands (Annex I) are however included in this specification for information. It should be recognised that the ability to meet the recommended performance values depends on the number of frequency bands supported by the UE.
The radiated radio tests considered here are:
1. The measurement of the Total Radiated Power (TRP)
2. The measurement of the Total Radiated Sensitivity (TRS)
3. The measurement of Total Radiated Multi-antenna Sensitivity (TRMS)
The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user. |
41.033 | Lawful Interception requirements for GSM | TR | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-d00.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. |
42.033 | Lawful Interception; Stage 1 | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-d00.zip | This Technical Specification provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for this specification to encompass all of them. The purpose of this specification is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of this specification general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications". |
43.033 | 3G security; Lawful Interception; Stage 2 | TS | 13.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/43_series/43.033/43033-d00.zip | The present document gives the stage 2 description of Lawful Interception within a PLMN for circuit switched systems and GPRS. It does not address the interface between the PLMN and the LEA lawful intercepted product and related information collection functions. This is outside the scope of the GSM standard.
The structure of the present document is as follows:
- clause 4 covers the architecture of the interception system;
- clause 5 describes how interception is activated, deactivated and interrogated within the interception system;
- clause 6 describes how the system is provisioned, defines events at which interception takes place and what kind of information is generated at each event;
- clause 7 provides brief descriptions of various intercept cases;
- clause 8 reviews security requirements for access to the interception system;
- annex A provides information flows to illustrate when intercepted traffic and related data is generated;
- annex B describes an interception system for GPRS. The annex is subdivided into 5 sections that are identical in structure to clauses 4 through 8, but applicable to a GPRS clause rather than a GSM circuit switched system. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 13.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-d00.zip | |
44.160 | 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 | 13.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.160/44160-d00.zip | |
22.817 | Study on UICC/USIM enhancements | TR | 0.4.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.817/22817-041.zip | The present report identifies use cases and potential requirements for new USIM services with a focus on:
- Instances where the USIM is used inside terminals with specialised functionalities (e.g. radio modems, 3G Notebook terminals);
- Possible enhancements to facilitate USIM-UICC support for new services;
• Possible enhancements to facilitate an improved user experience when interacting with the UE; and
- Evolution from the USAT towards multimedia USIM toolkit support.
The present report covers only use cases and services that cannot be fully implemented and easily realised using the existing standards, but instead require some enhancement of the present UICC/USIM requirements. Alternative technical solutions (i.e. non USIM-based solutions) are also introduced and referenced for use cases in order to provide a more complete picture of how they might best be realised. |
23.704 | Study on Circuit Switched (CS) / Packet Switched (PS) coordination in shared network; Stage 2 | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.704/23704-110.zip | The present document investigates relevant scenarios and possible solutions to enhance the CS/PS Coordination in a shared UTRAN/GERAN network as currently specified in TS 23.251 [2].
Within this technical report relevant mobility scenarios shall be investigated and it shall be evaluated per scenario if any issues with CS/PS Coordination can be expected. The investigation shall be done for non-supporting UEs and for any UE in shared networks where no Multiple PLMN list is broadcasted. Solutions to solve found issues shall be evaluated and agreed for subsequent normative specification.
The scenarios that need to be handled will at least include:
- CS handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- PS Handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- Redirection;
- Cell reselection;
- CSFB;
- rSRVCC and SRVCC;
- PLMN selection at handover based on UE capability;
- Registration to PS domain in a shared network after CS only registration has been performed. |
23.705 | Study on system enhancements for user plane congestion management | TR | 0.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.705/23705-0b0.zip | The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document. |
23.861 | Network based IP flow mobility | TR | 1.16.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.861/23861-1g0.zip | Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel‑13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel‑10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel‑13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel‑13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel‑13 consider the following aspects:
- The support of a PDN Connection active over multiple accesses simultaneously.
- The association of one or multiple IP flows belonging to a PDN connection to an access system.
- The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
- The triggers for IP flow mobility in the UE and the network.
- UE-initiated and network-initiated NBIFOM.
- The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used. |
23.896 | Technical Report on Support for fixed broadband access networks convergence | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.896/23896-c00.zip | Editor's note: This clause will describe the scope of the feasibility study for P4C.
This Technical Report addresses stage 2 study for the Evolved Packet System (EPS) to facilitate policy and charging control in the fixed broadband access network in the convergent scenario where a single operator is deploying both the fixed broadband access network and the Evolved Packet Core (EPC).
The scope of this TR is to consider the convergent scenario where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the BPCF defined in TS 23.139 [20].
The work in this TR takes the fixed broadband accesses as specified by BroadBand Forum as a reference. This does not preclude the applicability of the solutions described in this TR to other types of fixed broadband accesses.
This TR will address policy and charging control for:
- Traffic to/from fixed devices connected to the fixed broadband access network (e.g. PC, IPTV Set top Box).
- Traffic exchanged by 3GPP UEs connected via WLAN or H(e)NB when both the fixed broadband access network and the EPC are under the control of the EPS operator.
The work is organized in the building blocks and this TR address the Building block listed below, for an outline of the content of each building block refers to clause 4:
- BB1: Policy and Charging Control for supporting traffic from fixed terminals and NSWO traffic from 3GPP UEs in fixed broadband access networks (P4C-F).
- BB3: Policy and Charging Control for 3GPP UEs connected to fixed broadband access network via S2b and S2c reference points for EPC routed traffic (P4C-S2bc).
- BB4: Policy and Charging Control for EPC routed traffic over fixed broadband access networks of 3GPP UEs connected via H(e)NB in convergent scenarios (P4C-HeNB).
- BB5: Policy and Charging Control for supporting Layer 2 traffic in fixed broadband access network (P4C-FL2).
- BB6: Policy and Charging Control for 3GPP UEs connected to fixed broadband forum access networks as Trusted network in Convergence scenario (P4C-TC).
NOTE: The Building Block 2 P4C-TI is addressed in TR 23.839 [28]. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-c00.zip | |
28.403 | Telecommunication management; Performance Management (PM); Performance measurements for Wireless Local Area Network (WLAN) | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.403/28403-010.zip | |
28.601 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.601/28601-c00.zip | The present document describes the Network Resource Model (NRM) Integration Reference Point (IRP) requirements for Interworking WLAN (IWLAN). According to the structure of IWLAN defined in 3GPP TS 23.234 [6], the present document is focusing on the definition of NRM IRP requirements on the 3GPP part (e.g. WAG, PDG, 3GPP AAA, etc). |
28.602 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.602/28602-c00.zip | The present document is an Integration Reference Point (IRP) named "Core Network (CN) and non-3GPP access interworking system Network Resource Model IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management (CM) information to one or several 'IRPManagers' (typically Network Managers) concerning interworking network resources.
According to the structure of IWLAN defined in 3GPP TS 23.234 [5], several nodes are defined in 3GPP (e.g. WAG, PDG, 3GPP AAA, etc). The present document is focusing on the definition of NRM IRP IOCs for management support.
It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines I-WLAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which Interface IRP that is applicable is outside the scope of the present document.
The present document supports the Federated Network Information Model (FNIM) concept described in 3GPP TS 32.107 [16] in that the relevant Information Object Classes (IOCs) defined in the present document are directly or indirectly inherited from those specified in the Umbrella Information Model (UIM) of 3GPP TS 28.620 [17]. |
28.606 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.606/28606-c10.zip | The present document is part of an Integration Reference Point (IRP) named Core Network (CN) and non-3GPP access Interworking System Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Core Network (CN) and non-3GPP access Interworking System resources. The Core Network (CN) and non-3GPP access Interworking System NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Core Network (CN) and non-3GPP access Interworking System NRM IRP.
This Solution Set specification is related to 3GPP TS 28.602 V12. 0.X [4]. |
45.876 | Uplink Multi-User MIMO | TR | 0.2.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/45_series/45.876/45876-020.zip | The present document details the output of the 3GPP study item on UL MU-MIMO [2]. It is intended to gather information in order to draw a conclusion on the UL MU-MIMO technology based on the link level and system level evaluations.
The following items are covered in this document:
• Objectives for the study.
• Concept description.
• Performance evaluations.
• Complexity analysis. |
28.682 | Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 0.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.682/28682-020.zip | |
29.161 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services with Wireless Local Area Network (WLAN) access and Packet data Networks (PDN) | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.161/29161-c00.zip | The present document defines the requirements for Packet Domain interworking between a:
a) PLMN with WLAN access and PDN;
b) PLMN with WLAN access and PLMN.
The present document also defines, in clause 12, the usage of Radius at the Pp Reference Point between the Packet Data Gateway and the Presence Network Agent, see 3GPP TS 23.141 [18]. |
31.901 | Review of dedicated 3GPP UICC features (Red_UCe) | TR | 1.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.901/31901-100.zip | The present document presents a review of the USIM, ISIM and the related Toolkit aspects (respectively found in TS 31.102 [3], TS 31.103 [4] and TS 31.111 [5]) features and their mandatory/optional support in the light of actual use or demand in the field is to be conducted. The technical report documents the justification for the support of features identified as not being implemented or required (e.g. from SA1 requirements). When a common understanding is reached about a potential need for a modification of the required support of a feature, it will be listed for further consideration by CT6. Should any normative work be derived from the content of the study, it will be carried out as part of a separate work item. |
32.176 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.176/32176-c00.zip | The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the SuM NRM IRP.
This specification is related to 3GPP TS 32.172 [5] V10.2.X. |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-c00.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102]. |
32.646 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.646/32646-c00.zip | The present document specifies the Solution Sets for the UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.642 V11.4.X [4]. |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-c00.zip | The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.656 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.656/32656-c00.zip | The present document specifies the Solution Sets for the GERAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.652 V11.2.X [4]. |
32.676 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.676/32676-c00.zip | The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
This Solution Set definitions specification is related to 3GPP TS 32.672 V11.0.X. |
32.796 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 12.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.796/32796-c00.zip | The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Generic RAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.792 V11.0.X [4]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.