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 |
|---|---|---|---|---|---|---|
32.838 | Telecommunication management; Gap analysis between 3GPP SA5 specifications and NGMN Top Operational Efficiency (OPE) recommendations | TR | 1.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.838/32838-190.zip | The present document provides a gap analysis between NGMN Top OPE Recommendations [2] and OAM capabilities offered by 3GPP SA5 Integration Reference Points (IRPs).
Based on this gap analysis, it provides a support status of SA5 specifications against NGMN Top OPE Recommendations. For each Top OPE Recommendation, the SA5 solution is described when it exists. Otherwise, some action may be considered to address the Top OPE recommendation.
Based on that information, a support status is produced which can take the following values:
- Supported,
- Partially Supported,
- Not Supported,
- Not Applicable. |
32.839 | Management Specification Tooling Environment | TR | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.839/32839-011.zip | As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed [1], [2]. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. This document defines these common model elements.
To be noted:
- The Umbrella Operation Model (UOM) described in this document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile environments.
- The UOM is necessary but not sufficient for implementation.
- The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism.
- Classes derived from those in the UOM (e.g. for the fixed environment) may use different names from those used in the UOM. |
32.849 | Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks | TR | 1.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-110.zip | The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues. |
33.268 | Security aspects of Public Warning System (PWS) | TS | 0.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.268/33268-001.zip | This clause shall start on a new page.
The present document … |
33.833 | Study on security issues to support Proximity Services (ProSe) | TR | 1.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-180.zip | The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document. |
33.895 | Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 0.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.895/33895-0c0.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.832 | LTE in the 1670-1675MHz Band for the United States | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.832/36832-100.zip | The present document constitutes the output of the initial evaluation phase for the work item “LTE RAN Enhancements for Diverse Data Applications” (LTE_eDDA). The document captures agreements and descriptions related to the evaluation methodology used, descriptions of enhancement proposals and their evaluation results, and conclusions and recommendations for further work within the scope of the LTE_eDDA work item. |
36.834 | LTE Advanced intra-band contiguous Carrier Aggregation in Band 3 | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.834/36834-030.zip | The present document is a technical report of the work item for LTE-Advanced Intra-band Contiguous Carrier Aggregation in Band 3 which was approved at TSG RAN #57 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.838 | Intra-band contiguous CA in Band 27 for LTE | TR | 0.0.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.838/36838-001.zip | The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 27 which was initially approved at TSG RAN #58 [2]. A revised WID was approved at TSG RAN #59 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.841 | Evolved Universal Terrestrial Radio Access (E-UTRA); Intra-band non-contiguous Carrier Aggregation (CA) for band 25 for LTE | TR | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.841/36841-c00.zip | The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 25 work item which was approved at TSG RAN #53 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 25.
The report provides motivation, requirements and a list of recommended changes to the specifications. |
36.833 | Intra-band Non-contiguous CA for Band 4 for LTE | TR | 0.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.833/36833-020.zip | This clause shall start on a new page.
The present document is the technical report for the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 4 work item, which was approved at TSG RAN #56 [2]. |
36.851 | Inter-band carrier aggregation | TR | 1.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.851/36851-100.zip | The present document is a technical report for Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B1_B7
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 7
A3
LTE_CA_B2_B4
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 4
A4
LTE_CA_B23_B29
LTE Advanced inter-band Carrier Aggregation of Band 23 and Band 29
A1
LTE_CA_B3_B26
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 26
A1
LTE_CA_B3_B19
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 19
A1
LTE_CA_B1_B8
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 8
A1
LTE_CA_B3_B28
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 28
A1
LTE_CA_B1_B26
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 26
A1
LTE_CA_B39_B41
LTE Advanced inter-band Carrier Aggregation of Band 39 and Band 41
A3
LTE_CA_B2_B12
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 12
A1
LTE_CA_B2_B13
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 13
A1
LTE_CA_B19_B21
LTE Advanced inter-band Carrier Aggregation of Band 19 and Band 21
A5
LTE_CA_B12_B25
LTE Advanced inter-band Carrier Aggregation of Band 12 and Band 25
A1
LTE_CA_B2_B5
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
LTE_CA_B1_B18
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B7_B28
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 28
A1
LTE_CA_B5_B25
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 25
A1
LTE_CA_B1_B11
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 11
A5
LTE_CA_B8_B11
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 11
A5
LTE_CA_B5_B7
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 7
A1
LTE_CA_B1_B3
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 3
A3
LTE_CA_B1_B28
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 28
A2
LTE_CA_B4_B27
LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 27
A1
LTE_CA_B3_B27
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 27
A1
LTE_CA_B8_B27
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 27
A3
LTE_CA_B3_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B7_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B41_B42
LTE Advanced inter-band Carrier Aggregation of Band 41 and Band 42
A5
LTE_CA_B5_B13
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 13
A3
LTE_CA_B7_B22
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 22
A5
LTE_CA_B2_B5_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
The scope of the report has been further extended [6] to cover the 2 DL fallback modes for the 3 DL Carrier Aggregation combinations with single UL configuration. These 3 DL/1UL combinations are listed in table 1-2. In addition, the report also covers the LTE TDD-FDD joint operation including Carrier Aggregation combinations [7], captured in Table 1-3.
Table 1-2: Release 12 inter-band carrier aggregation combinations (3 DL/1UL)
WI code
WI title
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 5 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 29 and Band 30
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B1_B18_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 18 and Band 28
LTE_CA_3DL_FB_BW
Additional bandwidth combinations for LTE Advanced inter-band Carrier Aggregation to support 3DL fallback
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
Table 1-3: Release 12 inter-band carrier aggregation combinations (LTE TDD-FDD joint operation)
WI code
WI title
Class
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 41)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 42)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 40)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 8 and Band 40)
A1
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 42)
A2
LTE_CA_B26_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 26, Band 41 and Band 41
-
LTE_CA_B3_B38
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 38
A3
LTE_CA_B19_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 19, Band 42 and Band 42
A1
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
36.844 | Study on expansion of LTE in the 1670-1675 MHz Band for the United States to include 1670-1680 MHz Band | TR | 12.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.844/36844-c00.zip | The present document is a technical report for “Expansion of LTE_FDD_1670_US to include 1670-1680 MHz Band for LTE in the US” study item, which was approved at 3GPP TSG RAN#59 [2]. The ID assigned to the study item is FS_LTE_FDD_1670_US. The objective of this study item is to facilitate and harmonize the characteristics and efficient use of 1670-1680MHz DL duplexed with band 24 UL for LTE FDD deployment in US. In addition to the schedule and status of the study items, the report includes a description of the motivation, requirements, study results and specification recommendations. |
36.855 | Feasibility of positioning enhancements for E-UTRA | TR | 0.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.855/36855-070.zip | Positioning mechanisms were specified in 3GPP as a key feature for E-UTRA networks since Release 9, e.g. OTDOA, E-CID etc. They are not only used in helping meet regulatory requirements, but also utilized with increasing importance to enable all kinds of location based applications.
The proliferation of heterogeneous network deployments brings some challenges also in the area of efficient terminal positioning and calls for the study of enhanced mechanisms and positioning performance requirements.
The addition of multiple nodes in heterogeneous networks can improve the position accuracy remarkably if the specificities of such deployments are taken into account in the positioning mechanisms. Some examples include the support of several transmission points with identical cell IDs and improved support for positioning in carrier aggregation.
Furthermore, the accuracy of current positioning mechanisms and in particular OTDOA and E-CID based on UE Rx-Tx time difference measurement is only defined for limited scenarios:
• Limited channel bandwidth for the cells to be measured (reference and neighbour cells)
• Tests defined assuming single Tx antenna. Practical network might have Tx diversity on antenna port 6 which is used for RSTD measurements
It is desirable to study the possibility of enhanced accuracy for other practical deployment scenarios.
The present document is the Technical Report for the Study Item on positioning enhancements for E-UTRA. |
36.861 | Technical Report for Study Item: Study on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz | TR | 0.5.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.861/36861-051.zip | The present document contains the result of the Study item on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz, which has been approved in RP-121420 [5] at TSG RAN#57, Sep 2012.
The objective of this study is to facilitate and harmonize the efficient use of these bands for terrestrial IMT, especially LTE, for Korea and other applicable countries in Region 3. |
36.978 | Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) antenna test function definition for two-stage Multiple Input Multiple Output (MIMO) Over The Air (OTA) test method | TR | 1.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.978/36978-110.zip | The present document contains the findings of the Study Item (FS_LTE_MIMO_OTA_ATF) to describe the antenna test function for the two-stage MIMO OTA test method. |
37.544 | Universal Terrestrial Radio Access (UTRA) and Evolved UTRA (E-UTRA); User Equipment (UE) Over The Air (OTA) performance; Conformance testing | TS | 0.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.544/37544-070.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. |
37.842 | 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) | TR | 1.9.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.842/37842-190.zip | The present document is the Technical Report for the Work Item on Base Station (BS) Radio Frequency (RF) requirements for Active Antenna System (AAS), which was approved at TSG RAN#59. The present document captures the background and the decisions on the specification of RF requirements that are applicable to AAS BS. |
36.853 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced; LTE-Advanced 3 Band Carrier Aggregation (CA) (3DL/1UL) | TR | 2.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.853/36853-220.zip | The present document is a technical report for 3DL Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 3DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_B2_B2_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 2 and Band 1
LTE_CA_B2_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 4 and Band 13
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 30
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 29 and Band 30
LTE_CA_B4_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 4, Band 4 and Band 13
LTE_CA_B4_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 30
LTE_CA_B4_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 30
LTE_CA_B4_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 29 and Band 30
LTE_CA_B1_B3_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 8
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B4_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 5
LTE_CA_B2_B4_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 12
LTE_CA_B2_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 12
LTE_CA_B2_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 12
LTE_CA_B3_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 20
LTE_CA_B3_B8_B27
LTE Advanced 3 band Carrier Aggregation (3DL/1UL) for Band 3, Band 8 and Band 27
LTE_CA_B4_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 12
LTE_CA_B4_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 12
LTE_CA_B1_B3_B5
LTE Advanced 3 Band Carrier Aggregation(3DL/1UL) for Band 1, Band 3 and Band 5
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B3_B7_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 7
LTE_CA_B3_B3_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 7
LTE_CA_B1_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 42 and Band 42
LTE_CA_B3_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 42 and Band 42
LTE_CA_B1_B3_B19
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 19
LTE_CA_B2_B4_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 29
LTE_CA_B4_B4_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 7
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
LTE_CA_B39_B39_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 39 and Band 41
LTE_CA_B39_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 41 and Band 41
LTE_CA_B2_B2_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2 and Band 29
LTE_CA_B1_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 41, and Band 41
LTE_CA_B2_B2_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2, and Band 12
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
37.905 | Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test points for User Equipment (UE) radio transmission and reception conformance test cases | TR | 0.0.2 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.905/37905-002.zip | The present document specifies and contains the derivation of Test Points for RF test cases, thereby 3GPP TSG RAN WG5 will have a way of storing the input contributions provided. The test cases are described in TS36.521-1[2].
The test cases which have been analysed to determine Test Points are included as .zip files.
The present document is applicable from Release 10 up to the release indicated on the front page of the present Terminal conformance specifications. |
44.118 | Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode | TS | 12.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-c00.zip | |
45.871 | Study on Multiple Input Multiple Output (MIMO) for GSM/EDGE downlink | TR | 0.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.871/45871-040.zip | The present document contains investigations carried out and during the 3GPP study item on MIMO for GSM/EDGE Downlink.
The following items are covered in this study report:
- Objectives for the study
- Overview of MIMO for Downlink concept
- Conceptual design of several functional blocks of this solution
- Performance evaluations related to envisaged functional blocks belonging to MIMO for Downlink
- Compatibility analysis |
45.926 | Solutions for GSM/EDGE Base Transceiver Station (BTS) energy saving | TR | 1.7.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.926/45926-170.zip | |
22.801 | Study on non-MTC mobile data applications impacts | TR | 1.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.801/22801-110.zip | To make the network better suited for mobile data applications, the aim/scope of this study is to:
• Capture real world data / analysis.
• Identify services scenarios / use cases for mobile data applications.
• Identify potential problems / issues caused by different mobile data applications.
• Identify potential service and operational requirements for possible enhancements to the system. |
22.888 | Study on enhancements for Machine-Type Communications (MTC) | TR | 0.8.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.888/22888-081.zip | Objective of this work item is to study additional requirements, use cases and functionality beyond that specified by the Release 10 NIMTC work item on the following aspects:
• network improvements for MTC Device to MTC Device communications via one or more PLMNs.
Note: direct-mode communication between devices is out of scope.
• possible improvements for MTC Devices that act as a gateway for 'capillary networks' of other devices.
Note: capillary networks themselves are out of scope of 3GPP.
• network improvements for groups of MTC Devices that are co-located with other MTC Devices.
• improvements on network selection mechanisms and steering of roaming for MTC devices.
• possible enhancements to IMS to support MTC.
• possible improvements for location tracking of MTC Devices.
• service requirements on communications between PLMN and the MTC User/MTC Server (e.g. how the MTC User can set event to be monitored with MTC Monitoring).
• possible service requirements to optimize MTC Devices.
• possible New MTC Features to further improve the network for MTC.
For each of the aspects above, the Study will need to identify what kind of (if any) impacts there are on 3GPP standards. |
22.895 | Study on service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.895/22895-100.zip | The Single Sign-On (SSO) framework integration with 3GPP network resource and services intends to execute a comprehensive set of use cases and service requirements to serve various operator authentication configurations.
The scope of the Single Sign-On (SSO) integration study is to:
- provide service and deployment scenarios for 3GPP operators adopting an integrated approach to SSO, including web, person-to-person and M2M service scenarios;
- provide transparent identification and seamless authentication to Application Services on behalf of the user;
- support a comprehensive set of use cases of integration of different Identity and SSO frameworks (e.g OpenID) for various operator authentication configurations;
- define use cases and provide service requirements for Operators sharing controlled user credentials with Affiliated Application Service Providers;
- define use cases and service requirements associated with ensuring that the intended user is making use of the associated SSO capability (including the case when the UE has been stolen or lost);
- realize the Identity Provider role within the 3GPP network ecosystem and its influence among outside internet web service providers; and
- provide an enhanced user experience with secure, reliable access and authentication to Affiliated Application Services. |
22.896 | Study on continuity of data sessions to local networks | TR | 1.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.896/22896-110.zip | The present document studies use cases and potential requirements for Continuity of Data Sessions of a UE to Local Networks.
Local IP Access (LIPA) signifies the capability of a UE to obtain access to a local residential/enterprise IP network (subsequently called a local network) that is connected to one or more H(e)NBs and to communicate with entities in the local network through Data Sessions. Basic functionality for Local IP Access (LIPA) has been specified in 3GPP
Rel-10.
The current study item investigates extending LIPA functionality to allow access to the local network when a UE is under coverage of the macro network and provide related mobility support. |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-100.zip | |
23.839 | Study on support of Broadband Forum (BBF) access Interworking | TR | 1.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-1a0.zip | Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 [3] and TS 23.203 [4].
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block. |
23.843 | Study on Core Network Overload (CNO) solutions | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.843/23843-090.zip | The present document investigates core network signalling overload scenarios and potential general handling solutions, in particular:
1. Identify and document events that have occurred and caused network disturbances due to signalling overload. In addition, identify and document scenarios that have high probability of occurrence in the 3GPP network, which may result in signalling overload for core network entities. Such scenarios/events may include HLR/HSS overload by RNC restart, denial of service attacks, and misbehaving/3GPP-non-compliant mobiles causing unpredictable system response;
2. Analyse the criticality of the scenarios and determine whether it is required to take actions for the identified scenarios;
3. Study ways to mitigate and/or eliminate the impact on the core network from signalling overload scenarios that are identified to be critical.
The information provided about the HSS/HLR overload will serve as a starting basis for the study. All currently deployed 3GPP networks should be covered in the study, including LTE
The study should avoid overlap with other parallel activities within 3GPP, and work in close cooperation with the specific WG needs to be maintained.
During the study, if potential security threats such as denial of service attack scenarios are identified, SA WG3 must then be informed to take appropriate measures. |
23.844 | Feasibility study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2 | TR | 0.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.844/23844-050.zip | This study focuses on the enhancement of IMS to support Peer-to-Peer Content Distribution Services in respect of GPRS, EPC and other underlying access network technologies but not intend to modify GPRS or EPC for P2P mechanism.
The objectives are to study IMS based Peer-to-Peer Content Distribution Services on the architectural level with the following aspects:
- Creating solutions in order to fulfil the use cases and requirements as defined by SA WG1 while avoiding duplicate work in other SDOs, such as IETF [e.g., PPSP, P2PSIP, ALTO, and DECADE], and re-using their work. The solutions should:
- Apply the same IMS user management/registration procedure as other IMS services;
- Be able to provide the UE with the appropriate AS to obtain the addresses of other Peers, from which the UE can retrieve the requested content;
- Re-use ISC interface for service triggering;
- Be able to select qualified User Peers among available UEs according to the policies preconfigured in the network.
- Elaborate alternative solutions, which support the following network access technologies:
- Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);
- Fixed access only (e.g. xDSL, LAN);
- Fixed and mobile convergence scenarios.
- Evaluate possible impacts and improvements on network when IMS based Peer-to-Peer Content Distribution Services are deployed, such as the interactions that are needed to adapt the peer-to-peer overlay properties to the configuration and the resources of the network.
- Identify QoS, mobility, charging and security related requirements in the case of Peer-to-Peer Content Distribution Services on IMS.
The assessment on alternative solutions and the final conclusion of this study should not only take TR 22.906 [2] into consideration but also comply with the related normative work in SA WG1. |
23.852 | Study on S2a Mobility based on GPRS Tunnelling Protocol (GTP) and Wireless Local Area Network (WLAN) access to the Enhanced Packet Core (EPC) network (SaMOG); Stage 2 | TR | 1.7.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.852/23852-171.zip | This Study item is to study:
1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a.
2. Supporting WLAN access to EPC through S2a via mechanisms:
2.1 with no impact to the UE;
2.2 with impact to the UE.
Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI). |
23.853 | Operator Policies for IP Interface Selection (OPIIS) | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.853/23853-060.zip | This Technical Report describes solutions that define:
- operator policies for selecting an IP interface in the UE for routing of IP flows among a choice of available interfaces in both 3GPP and non-3GPP accesses;
- system architecture for distribution of these policies to the UE.
Editor's note: The working assumption is that the ANDSF architecture is used for distribution of the operator policies defined in this TR.
The solutions described in this TR shall clarify how the operator policies defined in this TR relate with the ANDSF policies.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to select a solution and include it in the relevant technical specifications. |
23.858 | Usage Monitoring Control PCC Enhancement | TR | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-070.zip | The scope of this technical report is to capture the results of a study that investigates if enhancements to the existing policy control architecture are needed in the area of usage monitoring control. The goals of the study are to derive possible requirements and architecture enhancements for:
1. Monitoring of service (s) / application (s) in more than one usage monitoring group;
2. Disabling a service (s) / application (s) from the existing usage monitoring group of services/group of applications;
3. Excluding the usage of a particular service (s) / application (s) from the accumulated usage for the IP-CAN session/TDF session;
4. Usage control for a subscriber group, e.g. the members of a family or a company subscriber, or a group of devices belonging to subscribers that share the same usage allowance threshold.
In addition, study the different proposed solutions for effective time based usage monitoring and how associated start and end of usage is defined. |
23.859 | Local IP access (LIPA) mobility and Selected IP Traffic Offload (SIPTO) at the local network | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.859/23859-090.zip | This Technical Report describes the solutions to implement the architectural aspects based on the requirements from TS 22.220 [3], clauses 5.7 and 5.9, and TS 22.101 [2], clause 4.3.5, for LIPA and SIPTO at the local network.
This includes:
- the support of mobility for LIPA between the H(e)NBs located in the local IP network;
- functionality to support Selected IP Traffic Offload requirements at the local network, including mobility.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to include the solutions in the relevant technical specifications. |
23.862 | Evolved Packet Core (EPC) enhancements to support interworking with data application providers; Stage 2 | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.862/23862-040.zip | This Technical Report describes solutions for interworking between mobile operators and data application providers. The solutions developed will describe a framework for authentication, authorization, policy and charging for various interworking scenarios.
Solutions developed as part of this work item will cover the following different relationships between mobile operators and data application providers for both roaming and non-roaming cases when
- mobile operator owns all the application layer entities;
- mobile operator does not own all the application layer entities.
The technical report will investigate charging, policy and group addressing capabilities for interworking between mobile operators and data application providers. Updates to 3GPP functions and interfaces will be specified for solutions based on IMS and/or EPC.
On-going work for authentication and other aspects in other 3GPP work items will not be duplicated. It will be investigated whether changes to 3GPP specifications are needed and if so which ones. The work item will focus on impacts to IMS and EPC. |
23.863 | Support of Short Message Service (SMS) in IP Multimedia Subsystem (IMS) without Mobile Station International ISDN Number (MSISDN); Stage 2 | TR | 1.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.863/23863-150.zip | This Technical Report is to specify architecture enhancement toward SMS submit/delivery mechanism in IMS to allow IMS registered UE to:
- Receive and send SMS without requiring an MSISDN associated as part of their IMS subscription record in HSS and
- any possible enhancements towards the related storing and forwarding mechanism if the UE is out of reach.
There are three potential aspects for these IMS UEs without MSISDN that need to be investigated:
1) Server - IMS UE communication via SMS (e.g. for M2M).
2) IMS UE to IMS UE communication via SMS for person to person communications. Both UEs do not have MSISDN.
3) SMS Interworking between IMS UE without MSISDN and traditional UE (e.g. CS) with MSISDN.
Normative specification work (if needed or feasible) for each of these areas can be started independently. |
23.866 | Study on system improvements for energy efficiency | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.866/23866-040.zip | The present document is for investigating deployment aspects that relate to energy efficiency, including potential system enhancements that support energy efficient deployments. System enhancements may be anticipated in the area of functions that have major influence on deployment like functions that support pools of CN nodes or functions that enable multiple CN nodes to serve the same or overlapping areas. The initial focus is on PS domain. This study should avoid any overlap with the work by RAN/CT/SA5 by taking into account the work that has been and is going on in these WGs. Proposals have to be well justified to be considered in this document. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-b00.zip | |
25.317 | High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band combination | TS | 11.0.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.317/25317-b00.zip | The present document specifies requirements on UEs supporting a frequency band combination that is independent of release. TSG-RAN has agreed that the standardisation of new frequency band combinations of DB-DC-HSDPA may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band combination of operation that is specified in a later release, it is necessary to specify some extra requirements.
For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
All DB-DC-HSDPA configurations are fully specified in this release of the specifications. The present document does not contain any requirements for UEs supporting DB-DC-HSDPA configurations independent of release. |
28.101 | Management of Converged Networks; Requirements | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.101/28101-000.zip | The present document is part of a TS family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
TS 32.xy1 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Requirements
TS 32.xy2 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Stage 2
In a fixed mobile convergent (FMC) network, the services offered to end users need resources from networks of different technologies.
NM standards of different technologies are the responsibilities of various standardization organizations (SDOs) and organizations. Various SDO/organizations may have defined different network management (NM) protocols to manage their respective network resources. Their managed resource models are mostly different from one another. Different parts of the large FMC network may be managed by different organizations.
The key challenge of FMC NM is the production of a set of specifications whose implementations would
a) Reduce FMC operators’ CAPEX and OPEX and
b) Facilitate OSS (playing the role of IRPManager) to integrate the various NM services consumed into the so-called “end-to-end” view of the FMC network under management.
Since network resource models are designed and maintained by different SDO/organizations and the provision of the “end-to-end” view requires defined relations among network resource models, this set of specifications would include:
1. Model architecture, called Federated Network Model (FNM), identifying various network resource models and their relations among each other;
2. The governance of each network resource model and the working procedures among SDO/organizations (that are designers and maintainers of the network resource model) involved.
The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for item 1 and item 2 above.
This clause shall start on a new page.
The present document … |
28.102 | Management of Converged Networks; Stage 2 | TS | 0.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.102/28102-000.zip | FFS |
28.401 | Telecommunication management; Performance Management (PM); Performance measurements for Core Network (CN) and non-3GPP access Interworking System | TS | 0.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.401/28401-020.zip | The present document describes the measurements for CN and non-3GPP interworking system.
TS 32.401 [3] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a interworking system. Only measurement types that are specific to interworking system are defined within the present documents. Vendor specific measurement types used in interworking system are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to WAG, PDG and so on);
- Header 2: Measurement function (e.g. FFS);
- Header 3: Measurements. |
28.601 | Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.601/28601-011.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 | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.602/28602-030.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 | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.606/28606-010.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]. |
28.611 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 0.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.611/28611-011.zip | |
28.612 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 0.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.612/28612-030.zip | |
28.616 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 0.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.616/28616-010.zip | |
30.007 | Guideline on WI/SI for new Operating Bands | TR | 0.2.0 | RP | https://www.3gpp.org/ftp/Specs/archive/30_series/30.007/30007-020.zip | The present document a technical report for the <Work item name> work item.
The Scope of the TR should be kept short. Details of the Work Item objective should be given in the Background section (Clause 4). |
33.823 | Security for usage of Generic Bootstrapping Architecture (GBA) with a User Equipment (UE) browser | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.823/33823-110.zip | This work in this Technical Report has the following scope:
- Study the potential threats for different GBA credentials use scenarios via a web browser. These new use scenarios (e.g. using HTML forms, using Javascript, using widgets) are not covered by current specifications.
The scope of this Technical Report will cover the following:
- Study, identify and specify any protection mechanism that maybe additionally required for the GBA credentials;
- Study, identify and potentially specify usage control for GBA credentials;
- Study, identify and potentially specify access control mechanism for GBA module;
- Study, identify and potentially specify the usage of web based GBA as an extension on the current protocol mechanisms used on Ua reference point (e.g. new Ua protocol identifier);
- Identify and outline how GBA can be used with HTML Forms and Javascript securely (e.g. describing GBA - web specific common practices and examples).
This Technical Report will collect the potential specification improvements, which are then at a later stage of work transferred to the appropriate Technical Specifications. The potential improvements for access control to GBA credentials and potential Ua protocol impacts will then be documented in TS 33.220 [2]. The threat analysis, common security implementation practices and examples may build a new chapter 5 in TS 33.222 [3].
Relation to GBA variants defined in other documents: Web based GBA aims at defining web enhancements for the use of HTML forms with GBA. It is a new variant for the Ua interface and does not affect the Ub interface, as opposed to the GBA variants defined in TS 33.220. Web based GBA is orthogonal to these other GBA variants and can be used with any of them. |
33.829 | Extended IP Multimedia Subsystem (IMS) media plane security features | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.829/33829-110.zip | The present document details relevant use cases/services for different user groups and corresponding solutions for IMS media plane security which are not covered by TS 33.328 [3]. The corresponding requirements in the Rel-9 study documented in TR 33.828 [2] will be used as a basis. The covered use cases/services are: conference calls, protection of non-RTP media, early media, communication diversion, deferred delivery, protected media recording, video on demand, AS-terminated media security, transcoder functionality and SRVCC. Example user groups are enterprises, National Security and Public Safety (NSPS) organizations, different government authorities, and general public.
Editor’s Note: The list of covered use cases/services shall be updated when the study is finalized.
Editor’s Note: It is for further study whether protection of early media is possible in IMS. |
33.868 | Study on security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TR | 0.17.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.868/33868-0h0.zip | The present document studies the security aspects of System Improvements for Machine Type Communication. In particular, the goals of the present document are:
- To identify and analyze the threats to the MTC system within the scope of the service requirements, functionality and use cases as specified in TS 22.368 [9].
- To identify possible security and privacy impacts induced by the system architecture improvement for machine type communications based on TR 23.887 [26] and TS 23.682 [23].
- To determine possible security requirements based on the analysis above and describe the possible solutions to meet those requirements.
Machine-type communication aspects of (x)SIMs and/or new models for the management of (x)SIM are out of scope of the present document. |
36.416 | Mobile Relay for E-UTRA | TS | 0.0.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.416/36416-002.zip | The present document is the technical report for the study item on Mobile Relay for E-UTRA [1], which was approved at TSG RAN#53. The objective of the SI is to first identify the scenario(s) and requirements then identify the key properties of mobile relays and assess the benefits of mobile relays over existing solutions in fast-moving environments. |
36.809 | Radio Frequency (RF) pattern matching location method in LTE | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.809/36809-030.zip | The objective of this study [20] is to evaluate the use of measurements for positioning, which are currently specified for UE and eNodeB for other purposes but are not currently included in LPP and LPPa, for an RF pattern matching positioning technology in LTE.
The RFPM performance with these measurements will be compared to the RFPM performance based on the measurements currently specified for the E-CID location method.
The implementation could be an E-SMLC based eNodeB-assisted location service using existing E-UTRAN measurements which are provided to the E-SMLC via the LPPa positioning protocol and UE-assisted location service using existing UE measurements (RSRP, RSRQ and UE Rx-Tx time difference only) which are provided to the E-SMLC via LPP positioning protocol.
The present document is intended to complement already 3GPP standardized location methods and existing 3GPP location work items. |
36.827 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced carrier aggregation band 41 | TR | 11.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.827/36827-b00.zip | The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 41 work item which was approved at TSG RAN #52 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 41.
The report provides motivation, requirements and a list of recommended changes to the specifications. |
26.951 | Enhancements to Multimedia (EMM); EMM, DDE and IPME Aspects | TR | 2.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.951/26951-200.zip | The present document contains the results of the work items EMM , EMM-DDE and EMM-IPME as approved in SA in SP-120025. This document does not include the results from the EMM-EFEC work item. |
36.831 | Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced Carrier Aggregation (CA) in band 7 | TR | 11.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.831/36831-b00.zip | The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 7 which was approved at TSG RAN #53 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications. |
36.836 | Evolved Universal Terrestrial Radio Access (E-UTRA); Study on mobile relay | TR | 2.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.836/36836-210.zip | The present document covers the Study on Mobile Relay for E-UTRA . The objective is to first identify scenario(s) and requirements then identify the key properties of Mobile Relays and assess the benefits of Mobile Relays over existing solutions in fast-moving environments. |
36.841 | Evolved Universal Terrestrial Radio Access (E-UTRA); Intra-band non-contiguous Carrier Aggregation (CA) for band 25 for LTE | TR | 0.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.841/36841-010.zip | The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 25 work item which was approved at TSG RAN #53 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 25.
The report provides motivation, requirements and a list of recommended changes to the specifications. |
36.888 | Study on provision of low-cost Machine-Type Communications (MTC) User Equipments (UEs) based on LTE | TR | 2.1.1 | R1 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.888/36888-211.zip | As LTE deployments evolve, operators would like to reduce the cost of overall network maintenance by minimising the number of RATs. Machine-Type Communications (MTC) is a market that is likely to continue expanding in the future. Many MTC UE's are targeting low-end (low average revenue per user, low data rate) applications that can be handled adequately by GSM/GPRS. Owing to the low-cost of these devices and good coverage of GSM/GPRS, there is very little motivation for MTC UE suppliers to use modules supporting the LTE radio interface. As more and more MTC UE's are deployed in the field, this naturally increases the reliance on GSM/GPRS networks. This will cost operators not only in terms of maintaining multiple RATs, but it will also prevent operators from reaping the maximum benefit out of their spectrum (given the non-optimal spectrum efficiency of GSM/GPRS). Given the likely high number of MTC UE's, the overall resource they will need for service provision may be correspondingly significant, and inefficiently assigned.
Therefore, it is necessary to find a solution to ensure that there is a clear business benefit to MTC UE vendors and operators for migrating low-end MTC UE's from GSM/GPRS to LTE networks. |
37.808 | Passive Intermodulation (PIM) handling for Base Stations (BS) | TR | 0.6.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.808/37808-060.zip | The present document is the technical report for the study item on Passive InterModulation (PIM) handling for Base Stations, which was approved at TSG RAN#55 [7]. The objective of the WI is to investigate the PIM issue from an overall perspective and to conclude on a way forward for the PIM problem and propose corresponding requirements for the BS specifications. |
33.914 | Single Sign On (SSO) application security for common IP Multimedia Subsystem (IMS) based on SIP Digest | TR | 2.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.914/33914-200.zip | The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated. |
37.977 | Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Verification of radiated multi-antenna reception performance of User Equipment (UE) | TR | 0.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.977/37977-050.zip | |
43.801 | Solutions for Voice services over Adaptive Multi-user channels on One Slot (VAMOS) enhancements | TR | 0.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.801/43801-050.zip | The present document contains the results from the 3GPP study item on VAMOS Enhancements. This includes study of the following aspects:
- Objectives of the study.
- Common assumptions for the evaluation of candidate techniques.
- Candidate techniques including those that utilize network synchronization, and further those that use inter-cell interference coordination/mitigation and inter-cell channel state sharing in and between BSS. A candidate technique will support frequency hopping.
- Evaluations of candidate techniques based on the objectives.
VAMOS enhancements will also investigate a new logical interface between BSSs in A/Gb mode which applies to control plane only and can be utilised by VAMOS enhancement solutions, since no logical interface between BSSs in A/Gb mode exists in current specifications. |
43.802 | GERAN study on mobile data applications | TR | 0.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.802/43802-040.zip | The present document contains the results from the feasibility study on efficient support of mobile data applications for human communications in GERAN.
The following aspects shall be covered in the study:
- Analysis on relevant traffic profiles from GERAN perspective for the mobile data applications of human communications
- Analysis on the impacts on GERAN network based on the identified traffic profiles
- GERAN enhancements to alleviate these impacts with regards to: Radio resource utilization; signalling procedures; RR states and transition between them and Battery lifetime
- Common assumptions on simulations and evaluations for candidate solutions |
43.868 | GERAN improvements for Machine-Type Communications (MTC) | TR | 2.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.868/43868-200.zip | The present document contains the results from the study of improvements for Machine-type Communications in GERAN.
The following items are in the scope of the study:
- GERAN enhancements for Smart metering
- Enhancements which enable or improve efficient use of RAN resources and/or which lower complexity when a large number of MTC devices are served.
- GERAN enhancements for overload and congestion control on the radio, A and Gb interface
- GERAN enhancements regarding identifiers used for MTC devices in the radio access network |
23.812 | Feasibility study on IP Multimedia Subsystem (IMS) evolution | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-120.zip | The scope of the technical report is to capture the results of a study into the feasibility of enhancing IMS network architecture. This report intends to study the feasibility of enhancing IMS network architecture as follows,
- Investigating architectural improvements to reduce the complexity of signalling procedures by reducing the signalling hops, or the number of options and combinations (by looking at different groupings of combining existing entities);
- Investigating means to improve system-level load balancing and reliability;
- Investigating possibilities for reducing configuration workload to save OPEX.
- Investigating the introduction of IMS Overload Control mechanisms.
Backward compatibility with current IMS specifications shall be ensured.
NOTE: overlap with SA5 and CT4 work need to be monitored.
This report is intended to explore potential architecture improvements and also provide conclusions on the above aspects with respect to potential future normative specification work.
There are a number of functions involved in call session setup in IMS network. Interfaces and interactions between network elements may be a little complicated and not that efficient. It is deemed beneficial to review the current IMS architecture including aspects such as the possible optimization of interfaces/reference points (by looking at different groupings of combining existing entities), reducing options of solutions for the same issues, relevancy of certain functions etc.
IMS network service availability largely relies on the reliability of network entities. If some network elements implementing critical functions (e.g. S-CSCF, HSS) fail, service availability may be impacted. Moreover network elements may not be fully utilized because network load may not be well distributed, e.g. some nodes may be overloaded due to sudden traffic increase, while others may be under loaded to some extent. Though there are some element level approaches to solve these problems, some system level solutions should be studied, for example, the method to distribute load between network elements in different geographical locations especially when a disaster happens, such as earthquake.
Network expansion may require significant manual configurations, and the network maintenance and upgrade may be time-consuming and also may be costly for operators. Introducing self-organization features may improve the network intelligence and reduce the efforts of manual configuration.
The objectives of the study for investigating the introduction of IMS Overload Control mechanisms are to:
- Determine the parts of IMS architecture for which overload control mechanisms are needed;
- Evaluate the applicability of candidate solutions for Overload Control to the SIP entities of the IP multimedia core network architecture, including:
- mechanisms having already been specified or studied within 3GPP and their possible enhancements,
- mechanisms specified or studied by other bodies (e.g. ETSI TISPAN, IETF) and their possible enhancements,
- other mechanisms, if proposed within this work item;
- Provide recommendations based on analysis. |
23.813 | Study on policy solutions and enhancements | TR | 0.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.813/23813-060.zip | The objective is to study an evolved policy solution through enhancement of 3GPP policy framework. One of the aims of the study is to ensure a policy architecture that provides an extensible framework for easy reuse with new IP based services by identifying areas where improvement of specifications are feasible. The study item will look into solutions for the examples in the section above.
Existing components for consideration in the Policy Study are functions and interfaces to/from
- PCRF, PCEF and BBERF;
- SPR, HSS;
- ANDSF;
- IMS policy decision making entities.
The study aims to provide a more comprehensive way (e.g. going beyond existing 3GPP PCC framework) to handle operator policies for all IP / service flows (IMS and non-IMS) in a coordinated manner and under varying network conditions while keeping in view aspects such as:
- user preferences;
- user subscriptions;
- service requirements;
- terminal capabilities (including converged terminals);
- network capabilities (3GPP and those non 3GPP accesses inter- working with 3GPP);
- Session transfer and terminating policies;
- Security policy control, e.g. firewalling and gating.
Roaming scenarios are considered as part of this study. Compatibility with existing system architecture elements are protected and backward compatibility is expected. All types of policies i.e. static/pre-provisioned, dynamic, network based, UE based are considered in the study.
When a key issue is resolved sufficiently to be incorporated into the specification in an independent manner, the study work may move forward for a decision for normative specification work on such issue(s) using a new work item or a TEI. |
23.823 | Intra Domain Connection of RAN Nodes to Multiple CN Nodes | TR | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.823/23823-200.zip | This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. |
23.839 | Study on support of Broadband Forum (BBF) access Interworking | TR | 0.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-070.zip | Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 [3] and TS 23.203 [4].
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block. |
23.857 | Study of Evolved Packet Core (EPC) nodes restoration | TR | 1.10.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.857/23857-1a1.zip | The present document contains the study on EPC nodes failure and restoration.
This document will consider any necessary operational protocol recovery mechanisms in the EPS in order to restore the subscriber service in the event of EPC node failure or clean up the hanging resource in other EPC nodes if the recovery of the failed node is not possible. The document will address the following aspects:
- list the different network failure scenarios to be analyzed for EPC nodes: MME, S4-SGSN, SGW and PGW;
- identify precisely the problems resulting from the current definition of the standards;
- list various possible solutions;
- identify pros and cons of possible solutions;
- conclude on potential enhancements to the standards (depending on gains vs complexity). |
23.885 | Feasibility Study of Single Radio Voice Call Continuity (SRVCC) from UTRAN/GERAN to E-UTRAN/HSPA; Stage 2 | TR | 1.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.885/23885-140.zip | The objective of the feasibility study is to investigate a solution for supporting Single Radio Voice Call Continuity (SRVCC) from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access, for voice call initiated in LTE/HSPA access and previously handed over to UTRAN/GERAN CS access, as well as for the voice call directly initiated in UTRAN/GERAN CS access.
This Technical Report investigates solutions for SRVCC for voice calls that are anchored in the IMS.
Coordination between the SRVCC for voice call and the handover of non‑voice PS bearers is also covered. |
23.888 | System improvements for Machine-Type Communications (MTC) | TR | 1.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.888/23888-170.zip | This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368 [2].
Specifically, the following system improvements are considered:
- Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network;
- Architectural enhancements to fulfil MTC service requirements;
- Support combinations of architectural enhancements for MTC, though not all combinations may by possible.
The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR.
Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report.
This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.682 [20], TS 23.060 [21], TS 23.401 [5], TS 23.221 [22] and TS 23.272 [23]. The text of the present document was not updated to align with normative specifications. |
23.975 | IPv6 migration guidelines | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-130.zip | |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-a00.zip | |
24.826 | Study on impacts on signalling between User Equipment (UE) and core network from energy saving | TR | 1.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.826/24826-110.zip | The present document contains the result of the study on the impacts on signalling between the UE and core network when energy saving measures are applied to network entities.
The study aims, within the defined CT1 work areas, at:
- analysing UE idle mode procedures and signalling between the UE and core network resulting from switch on/off of radio equipment in all types of 3GPP accesses, including home cell deployment and I-WLAN, as well as power adaptation of radio equipment (where applicable);
- performing a corresponding analysis for connected mode UEs;
- analysing similar impacts from activation status of non-3GPP access networks;
- documenting limitations, weaknesses and inefficiencies in these procedures, with emphasis on mass effects in the signalling between the UE and core network; and
- studying potential optimizations and enhancements to these procedures.
The study also evaluates potential enhancements to 3GPP specifications under CT1 responsibility.
This study takes into account decisions made by other 3GPP working groups in their related work. |
29.935 | Study on User Data Convergence (UDC) data model | TR | 0.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.935/29935-0a0.zip | |
32.833 | Telecommunication management; Study on management of converged networks | TR | 0.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.833/32833-060.zip | The present document investigates which new functionalities regarding a true end to end management are enabled by a converged OSS. The fragments looked at are Fault Management, Performance Management and Configuration Management. |
33.859 | Study on the Introduction of Key Hierarchy in Universal Terrestrial Radio Access Network (UTRAN) | TR | 1.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.859/33859-110.zip | The objective of this work item is to study potential solutions for introducing an "E-UTRAN-like" key hierarchy in UTRAN, to improve the security level in UTRAN in the presence of the new deployment scenarios and to ensure that a security breach in UTRAN will not propagate into E-UTRAN. The study covers the technical feasibility and consequences. The impacts of such potential solution on UTRAN of earlier releases are identified. Interworking with earlier releases of UTRAN, GERAN and E-UTRAN is also studied.
The UTRAN key hierarchy is assumed to be built on top of (R99+) UMTS AKA, without requiring any changes to the authentication protocol or USIM. Therefore, it could in principle be used also in GERAN as long as USIMs are used and the SGSN, MSC/VLR, and ME are updated. However, the benefit of introducing the key hierarchy in GPRS is smaller than for the circuit switched part, as the traffic protection already terminates in the core network. Solution details for GERAN are not discussed further.
The study covers both PS and CS part of UTRAN. |
33.914 | Single Sign On (SSO) application security for common IP Multimedia Subsystem (IMS) based on SIP Digest | TR | 0.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.914/33914-060.zip | The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated. |
36.116 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception | TS | 0.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.116/36116-040.zip | |
36.816 | Evolved Universal Terrestrial Radio Access (E-UTRA); Study on signalling and procedure for interference avoidance for in-device coexistence | TR | 1.3.1 | R2 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.816/36816-131.zip | The present document is intended to capture the output of the study item on Signalling and procedure for interference avoidance for in-device coexistence, which was approved at TSG RAN#48.
The objective of the SI is to investigate suitable mechanisms for interference avoidance from signalling and procedure point of view to facilitate the coexistence scenario that LTE and GPS/ ISM radio within the same device working in adjacent frequencies or sub-harmonic frequencies. The work under this study should take the following steps:
（1） Evaluate whether existing RRM mechanisms could be utilized to effectively solve the coexistence problems that arise in supporting the scenarios abovementioned and guarantee the required QoS in LTE with proper GPS/ISM operation.
（2） If legacy signaling and procedure are not sufficient to ensure required performance in the interested coexistence scenario, study enhanced mechanisms to better avoid interference and mitigate the impact caused by ISM radio.
Impact on legacy LTE UEs should be minimized.
NOTE: The candidate solutions should be firstly considered in the non-CA (carrier aggregation) cases. |
36.826 | Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception | TR | 0.17.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.826/36826-0h0.zip | The present document is the technical report on the "Relays for LTE” work item [2]. The overall objective of the WI is to specify Relays for LTE in Rel-10 timeframe.
This document is intended to gather the relevant background information in order to address Relay Node (RN) requirements as well as propose suitable updates to the specifications under the responsibility of RAN4. RAN4 have agreed to focus on fixed RN. |
37.806 | Extending 850 MHz study Technical Report | TR | 0.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.806/37806-030.zip | The present document contains the findings of the Study Item [28] of a more harmonised frequency variant approach within the frequency range of 806-849/851-894 MHz. |
37.976 | Measurement of radiated performance for Multiple Input Multiple Output (MIMO) and multi-antenna reception for High Speed Packet Access (HSPA) and LTE terminals | TR | 1.8.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.976/37976-180.zip | |
43.868 | GERAN improvements for Machine-Type Communications (MTC) | TR | 0.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.868/43868-050.zip | The present document contains the results from the study of improvements for Machine-type Communications in GERAN.
The following items are in the scope of the study:
- GERAN enhancements for Smart metering
- Enhancements which enable or improve efficient use of RAN resources and/or which lower complexity when a large number of MTC devices are served.
- GERAN enhancements for overload and congestion control on the radio, A and Gb interface
- GERAN enhancements regarding identifiers used for MTC devices in the radio access network |
22.168 | Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.168/22168-900.zip | This Technical Specification defines the stage one description of the Earthquake and Tsunami Warning System (ETWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of ETWS. ETWS deployment depends on operator decision or national regulations.
This TS contains the core requirements for the Earthquake and Tsunami Warning System, which are sufficient to provide a complete service.
This TS also contains regional requirements for Earthquake and Tsunami Warning System. |
22.813 | Study of use cases and requirements for enhanced voice codecs for the Evolved Packet System (EPS) | TR | 0.9.9 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.813/22813-099.zip | This study defines and analyses the new use cases in the environment of EPS and its future services. It evaluates how much the newly defined requirements are met by the already available codecs in 3GPP releases prior to Rel-10. Potential new requirements for voice codecs are elaborated in due course.
Specifically, the objective of this study item is to:
• Identify service and system requirements,
• Identify high level requirements,
• Assess the existing codecs in respect to identified requirements,
• Define a strategy for EPS voice codec(s) standardization,
• Identify some use cases for enhanced voice and mixed content conversational multimedia service for EPS (see Annex A).
Starting from Rel-8 timeframe, MTSI as a conversational multimedia service is provided over EPS. MTSI is the main service for which the enhancements are targeted. This does not however exclude the enhanced service requirements from being later adopted to other services where such enhancements are needed and are found suitable. |
22.893 | Advanced requirements for IP interconnect | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.893/22893-100.zip | This document studies the technical requirements for carrier grade inter-operator IP Interconnection of Services for the support of Multimedia services provided by IMS and for legacy voice and video PSTN/PLMN services transported over IP infrastructure (e.g. VoIP). These requirements should take into account the new and developing, convergent interconnect models currently being developed outside 3GPP.
Requirements should fulfil:
• Identification of the technical requirements for IP Service Interconnection (service control and user plane aspects) between Service Providers.
• Identification of requirements for the Stage 2 & 3 work to identify relevant existing specifications, initiate enhancements and the development of the new specifications as necessary.
• Supporting of IP Service Interconnection models as defined by other bodies (e.g. GSMA, ETSI, ITU-T). |
22.913 | Location Services (LCS) support in Evolved Packet Core (EPC) for non-3GPP accesses | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.913/22913-100.zip | This Technical Report (TR) presents the results of the Study on LCS support for non-3GPP accesses.
One main concept of EPC is to support a variety of different access systems (existing and future) ensuring mobility and service continuity between these access systems. In that perspective, the LCS support for non 3GPP accesses should be also taken into account. However, historically, TS 22.071 has been applicable only to 3GPP accesses and any new requirements for non 3GPP accesses have not been discussed yet.
Therefore we need to consider how to support LCS in EPC for non 3GPP accesses, e.g. 3GPP2 and WiMAX. Supporting LCS in EPC for non 3GPP access does not necessarily mean that all positioning methods available in various kinds of non 3GPP accesses should be supported in EPC or inventing new positioning methods for other accesses. However, how to realize the presentation of location information in EPC when users are connected in non 3GPP accesses should be at least taken into account. In addition, the service scenarios should be discussed whether new service requirements are needed for the users camping on non 3GPP accesses through EPC.
This work will examine whether requirements in TS 22.071 would be applicable for non 3GPP accesses and specify new service requirements for the users connected to non 3GPP accesses through EPC.
Consideration will be given, but not limited, to the following:
• High level requirements of LCS support for non 3GPP accesses;
• Location information provided to the LCS client for non 3GPP accesses;
• QoS requirements of LCS support for non 3GPP accesses.
• Priority between different LCS services for non 3GPP accesses.
• Privacy requirements of LCS support for non 3GPP accesses.
• Periodic location report of LCS services for non 3GPP accesses.
• Impact on the LCS client and the LCS server to support LCS services for non 3GPP accesses |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 1.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-100.zip | |
23.812 | Feasibility study on IP Multimedia Subsystem (IMS) evolution | TR | 0.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-080.zip | The scope of the technical report is to capture the results of a study into the feasibility of enhancing IMS network architecture. This report intends to study the feasibility of enhancing IMS network architecture as follows,
- Investigating architectural improvements to reduce the complexity of signalling procedures by reducing the signalling hops, or the number of options and combinations (by looking at different groupings of combining existing entities);
- Investigating means to improve system-level load balancing and reliability;
- Investigating possibilities for reducing configuration workload to save OPEX.
- Investigating the introduction of IMS Overload Control mechanisms.
Backward compatibility with current IMS specifications shall be ensured.
NOTE: overlap with SA5 and CT4 work need to be monitored.
This report is intended to explore potential architecture improvements and also provide conclusions on the above aspects with respect to potential future normative specification work.
There are a number of functions involved in call session setup in IMS network. Interfaces and interactions between network elements may be a little complicated and not that efficient. It is deemed beneficial to review the current IMS architecture including aspects such as the possible optimization of interfaces/reference points (by looking at different groupings of combining existing entities), reducing options of solutions for the same issues, relevancy of certain functions etc.
IMS network service availability largely relies on the reliability of network entities. If some network elements implementing critical functions (e.g. S-CSCF, HSS) fail, service availability may be impacted. Moreover network elements may not be fully utilized because network load may not be well distributed, e.g. some nodes may be overloaded due to sudden traffic increase, while others may be under loaded to some extent. Though there are some element level approaches to solve these problems, some system level solutions should be studied, for example, the method to distribute load between network elements in different geographical locations especially when a disaster happens, such as earthquake.
Network expansion may require significant manual configurations, and the network maintenance and upgrade may be time-consuming and also may be costly for operators. Introducing self-organization features may improve the network intelligence and reduce the efforts of manual configuration.
The objectives of the study for investigating the introduction of IMS Overload Control mechanisms are to:
- Determine the parts of IMS architecture for which overload control mechanisms are needed;
- Evaluate the applicability of candidate solutions for Overload Control to the SIP entities of the IP multimedia core network architecture, including:
- mechanisms having already been specified or studied within 3GPP and their possible enhancements,
- mechanisms specified or studied by other bodies (e.g. ETSI TISPAN, IETF) and their possible enhancements,
- other mechanisms, if proposed within this work item;
- Provide recommendations based on analysis. |
23.823 | Intra Domain Connection of RAN Nodes to Multiple CN Nodes | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.823/23823-120.zip | This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. |
23.832 | IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2 | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.832/23832-100.zip | This Technical Report describes an IMS capable HNB SubSystem (the HNB and the HNB Gateway) as an optional capability of HNB that allows e.g. an operator to offload CS traffic to the IMS. The HNB and HNB Gateway are described in TR 23.830 [5], and the capabilities of these network elements are assumed by this TR.
To achieve this and to satisfy the related requirements and use cases captured in TS 22.220 [2], the objective is to investigate the following:
• an architecture to enable IMS capable HNB Subsystem to use the IMS for CS terminals using a corresponding equivalent IMS services (voice service in IMS Multimedia Telephony);
• the impacts of the IMS capable HNB Subsystem to idle mode mobility for all supported UE types (e.g. IMS registration/de-registration);
• service continuity at least in the direction from IMS capable HNB Subsystem to macro network;
• support for pre-Rel‑9 CS and IMS UEs when using IMS capable HNB Subsystem.
The TR will analyze solutions for the related architectural issues and capture the conclusions. |
23.848 | Study on enhancements to IP Multimedia Subsystem (IMS) border functions for interconnection of IMS based services | TR | 0.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.848/23848-090.zip | The objective of this document is to analyse and identify enhancements needed in the current 3GPP IMS interconnection architecture driven by the needs that new business models/service delivery scenarios impose at the interconnection points of the IMS operators.
The present document will covers network to network interconnection as main objective and addresses the issues related to both control and user plane functionalities including:
- signalling treatment,
- numbering/naming/addressing,
- IP interworking,
- policy management,
- e2e QoS,
- transcoding,
- security,
- charging.
The purpose of this document is to formulate architectural solutions for the enhanced functionalities identified to cover all IMS operator’s needs in this widespread environment. These solutions should be applicable for an IMS operator in a common IMS environment (i.e. regardless the access being used) as well as for direct and indirect interconnection paradigms. Finally, the best solution/s should be agreed and impacted normative work in 3GPP identified to update current 3GPP specifications with the output of this work. |
23.884 | Local Call Local Switching, Feasibility Study | TR | 0.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.884/23884-010.zip | The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of potential correlation information between the two legs of the call to be sent to the BSS (e.g. in case of MSC pooling)
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications. |
23.889 | Local Call Local Switch (LCLS) system impacts; Feasibility study | TR | 1.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.889/23889-140.zip | The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of correlation information between the two legs of the call to the BSS
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
- Impacts to the MSC-S – MSC-S Interface (Nc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications. |
23.894 | System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media | TR | 1.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-130.zip | This study intends to investigate the general problem of system enhancements for the use of IMS services in local breakout and optimal routeing of media.
In particular the above issues will be addressed identifying
- solutions for the home operator to control
- whether the IMS user may connect to a PDN in the visited network, and
- whether connections to PDNs provided from the home and visited network may exist in parallel;
- solutions to enable the IMS network to be aware of whether local breakout can be invoked or not;
- solutions to allow the home operator to determine which of the IMS sessions (for a given UE) can be handled in local breakout and which in home routed mode, and what information (e.g. operator's policies, customer's subscription profile, UE connectivity, and location of the remote end terminal/service) is needed for the decision;
- solutions to allow the UE to concurrently use IMS services through local breakout and other IMS services through home routeing;
- the feasibility of having the local breakout option in IMS service nodes:
- is there a need for a P-CSCF at both PDN accesses?
- if one P-CSCF is enough, what requirements are there for connectivity between the PDNs?
- if methods are necessary to discover an additional P-CSCF in the visited network after the UE has moved to the visited network, even if the network-layer mobility mechanisms can sustain IP connectivity to the previously discovered P-CSCF in the home network;
- the exact location of the decision point in the home network whether to use local breakout (application or delegated to IP-CAN);
- solutions for SIP/SDP signalling related to the use of IMS services through local breakout.
- interactions with network entities such as NAT (as specified in TS 23.228 [8]) when providing IMS services through local breakout;
- interactions with and support of PCC to provide IMS services through local breakout;
- security implications if there is need for multiple P-CSCFs per UE.
Moreover:
- describing a set of scenarios where the selection of an alternative media path (i.e., different to the signalling path) provides benefits to IMS operators by reducing the number of network entities in the media path;
- providing requirements for suitable mechanisms to achieve optimal media routeing;
- analysing the potential solution(s) to solve those scenarios in line with IMS procedures, while taking into account any impact of extensions required to existing functions/procedures (e.g., NAT, transcoding, Security, PCC, BCF, LI, etc.);
- reducing the number of options for solving the same requirement and agree on a preferred solution.
In the end this study will provide conclusions with respects to what further specification work is required in order to fulfil the requirements for the use of IMS services through local breakout and achieve optimal routeing of media. |
24.323 | 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-900.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.