id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.853
|
Operator Policies for IP Interface Selection (OPIIS)
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.853/23853-c00.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.859
|
Local IP access (LIPA) mobility and Selected IP Traffic Offload (SIPTO) at the local network
|
TR
|
12.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.859/23859-c01.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
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.862/23862-c00.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
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.863/23863-c00.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.865
|
Study on Wireless Local Area Network (WLAN) network selection for 3GPP terminals; Stage 2
|
TR
|
12.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.865/23865-c10.zip
|
This Technical Report describes enhancements to solutions for WLAN network selection. The solutions are based on architectures as specified in TS 23.402 [9] and will take into account Hotspot 2.0 specifications developed by the WFA. 3GPP operator's policies for WLAN network selection will be provisioned on 3GPP terminals via pre-configuration or using the ANDSF server for their delivery. The scope of the technical report will be as follows:
1. Evaluate existing 3GPP WLAN PLMN and access network selection procedures for 3GPP terminals which use Hotspot 2.0 procedures and provisioned network operator policy (e.g. mechanisms based on WLAN and ANDSF) for any needed changes to current specifications. This may require enhancements to the ANDSF framework. The established 3GPP PLMN network selection (according to TS 23.122) shall not be impacted. The work must ensure there are no conflicts between existing 3GPP PLMN network selection and the 3GPP WLAN PLMN access network selection procedures defined by this WID.
2. Ensure that the content in the Management Object related to 3GPP operator policy provisioning for WLAN network selection procedures and the operator policy provisioning in WFA MO for WLAN network selection are consistent.
3. Identify solutions to resolve potential conflicts between policies provided by non-3GPP providers via Hotspot 2.0 mechanisms and policies provided by 3GPP operators using ANDSF.
This work applies to non-seamless WLAN offload as well as to trusted and untrusted WLAN access to EPC with/without seamless offload. It will be investigated whether changes to 3GPP specifications are needed and if so which ones.
|
23.866
|
Study on system improvements for energy efficiency
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.866/23866-c00.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.
|
23.887
|
Study on Machine-Type Communications (MTC) and other mobile data applications communications enhancements
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.887/23887-c00.zip
|
The present document studies and evaluates architectural enhancements for Machine-Type and other mobile data applications Communications.
Specifically, the following system improvements are considered:
- Small Data Transmission (SDT) which includes the following aspects:
- SDT as per the service requirements (TS 22.368, clause 7.2.5); and
- Efficient handling of frequent SDT as per the service requirement (TS 22.101, clause 4.3.1).
- Triggering enhancements which includes the following aspects:
- Device triggering enhancements including T5 based device trigger and other triggering efficiency optimizations.
- Monitoring enhancements which includes the following aspect:
- Monitoring as per the service requirements (TS 22.368, clause 7.2.8).
- UE Power optimizations which includes the following aspects:
- Optimizations to prevent battery drain (that may come from e.g. frequent changes between idle and connected mode or too long periods in connected mode); and
- Lower UE power consumption as per the service requirements (TS 22.368, clause 7.1.1).
- Group based features which include the following aspects:
- Fulfil the group based policing requirements (TS 22.368 clause 7.2.14.2);
- Fulfil the group based addressing requirements (TS 22.368 clause 7.2.14.3); and
- Fulfil the group based charging requirements (TS 22.368 clause 7.1.5).
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services as provided by the 3GPP system and the related optimizations are considered in this study.
The present document analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
|
23.890
|
Optimized offloading to Wireless Local Area Network (WLAN) in 3GPP Radio Access Technology (RAT) mobility
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.890/23890-c00.zip
|
This technical report describes key issues and solutions for optimized offloading of traffic to WLAN access when PS mobility between 3GPP RAT takes place. The technical report analyzes the user and service impact due to mobility between 3GPP RATs. The technical report analyzes the key issues and solutions in order to identify whether current mechanisms documented in SA2 specifications are sufficient, identify potential inefficiencies, and identify whether additional solutions are needed to address the key issues.
The technical report also describes proposed extensions to ANDSF in order to enable policy differentiation for 3GPP RATs (e.g. E-UTRAN versus UTRAN, GERAN versus UTRAN) with respect to WLAN, in order to enable a UE to distinguish preferences of WLAN with respect to specific 3GPP RATs upon acquiring connectivity (e.g. PDN creation in a 3GPP RAT or WLAN, or establishing NSWO connectivity) or upon mobility.
|
23.897
|
Feasibility study on IP Multimedia Subsystem (IMS) business trunking for Internet Protocol Private Branch Exchange (IP-PBX) in Static Mode of Operation
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.897/23897-c00.zip
|
During the production of the 3GPP Release 7 specifications it was recognized that the IP Multimedia Subsystem was suitable for serving both mobile and fixed installations and a number of specifications developed by ETSI TISPAN were therefore embedded in the 3GPP specifications to form the Common IMS. Among other aspects, Common IMS requires that the IMS is able to connect with Next Generation Corporate Networks (NGCN), also known as IP-PBXs (see ETSI TS 181 019 [3]).
Managing the connection to IP-PBXs which do not use registration procedures when connecting to the IMS and operate in a static mode that is to enable the IMS to receive and send traffic to an IP-PBX, is realized by means of configuration within the network. The static mode of operation can be used in 2 scenarios, peering based business trunking and subscription based business trunking. The static mode of operation for both of the above mentioned scenarios can be studied in this TR.
It was however observed that the number of implementations of IP-PBXs that are operated in a static mode (e.g. based on the SIPConnect specifications recently released by the SIP Forum) increases.
The purpose of this study is to enable the IMS to manage connections to a large number of IP-PBXs that are operated in a static mode, with minimized configuration in the network.
|
24.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3
|
TS
|
12.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.234/24234-c20.zip
|
The present document specifies the network selection, including authentication and access authorization using authentication, authorization and accounting (AAA) procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification the network includes the WLAN and 3GPP network.
Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology specific protocols, however this signalling is transparent to the WLAN.
Tunnel management procedures are defined to be independent of the underlying WLAN access technology and as such can be reused independently of the underlying technology.
The present document specifies procedures within I-WLAN necessary in order for IMS emergency calls to be supported when I-WLAN is used as the underlying access network. These involve both network selection as well as tunnel management procedures.
WLAN Network Selection supersedes I-WLAN for UE WLAN selection as specified in 3GPP TS 24.302 [28] from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
24.235
|
3GPP System to Wireless Local Area Network (WLAN) interworking Management Object (MO)
|
TS
|
12.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.235/24235-c10.zip
|
This document defines the 3GPP System to Wireless Local Area Network interworking Management Object (MO) for I-WLAN PLMN selection as specified in 3GPP TS 24.234 [3]. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD_DM-V1_2 [2].
The 3GPP System to Wireless Local Area Network interworking Management Object consists of relevant parameters that can be managed for WLAN UE as specified in 3GPP TS 24.234 [3].
The Access Network Discovery and Selection Function MO as specified in 3GPP TS 24.312 [13] supercedes the Wireless Local Area Network interworking MO for I-WLAN PLMN selection from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
24.327
|
Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN) and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3
|
TS
|
12.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.327/24327-c00.zip
|
This document specifies the signalling procedures for handling the mobility of a UE between 3GPP Wireless Local Area Network Interworking (I-WLAN) and GPRS systems.
The present document is applicable to the User Equipment (UE) and the network nodes supporting mobility between 3GPP I-WLAN and GPRS systems.
In addition, the present document specifies the procedures used between the UE and the network nodes for the attach and the detach cases. It also specifies how the UE performs handover when moving from 3GPP I-WLAN to GPRS systems and vice-versa.
This document is based on DSMIPv6 procedures specified in 3GPP TS 24.303 [3] and will specify additional details specific to the 3GPP I-WLAN and GPRS systems in the context of mobility.
|
24.802
|
Study on Indication of Network to Network Interface (NNI) routeing scenarios in Session Initiation Protocol (SIP) requests in the IP Multimedia Subsystem (IMS)
|
TR
|
12.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.802/24802-c10.zip
|
The present document provides a study of the IMS impacts for providing a solution for determination of Inter‑IMS Network to Network Interface (II-NNI) traversal scenario type. The document describes and analyses different II‑NNI traversal scenarios. The present document describes requirements and investigates the implementation options to fulfil requirements for determination of II-NNI traversal scenario type.
Examples of scenarios to study are:
- the visited to home scenario;
- the home to visited scenario;
- the loopback scenario;
- the invocation of MRB/MRF in visited network from an AS in home network scenario; and
- a request sent from the home network on the originating side to the home network on the terminating side.
The present document includes the study of the existing protocol mechanism and new protocol mechanism for further evaluation what is needed to identify a particular II-NNI traversal scenario type.
The study also considers existing deployments.
The present document analyses and evaluates different solutions.
|
24.803
|
Study on telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3
|
TR
|
12.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.803/24803-c00.zip
|
The present document contains the study on Telepresence using IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), Session Description Protocol (SDP) and other protocols of controlling multiple streams for Telepresence based on service requirements.
The study aims, within the defined CT1 work areas, at:
- analysing IMS session procedures and signalling between the UE and core network for Telepresence creation, establishment with media negotiation and configuration, session modification and termination, with the incorporation of new protocol (i.e. CLUE as under developing in IETF);
- investigating impacts for presentation in Telepresence and floor control in IMS;
- analysing similar impacts to allow legacy devices interworked with Telepresence using IMS; and
- studying potential enhancements and extensions to facilitate these procedures.
This study will identify specification areas, if any, that lie within the scope of other 3GPP working groups, and seek input from those 3GPP working groups to define that related specification work.
|
25.700
|
Study on Further Enhanced Uplink (EUL) enhancements
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.700/25700-c00.zip
|
In the past few years, a considerable increase in number of users as well as offered traffic per user has been experienced in HSPA networks, both in the downlink and in the uplink.
In response to this, several features have been standardized in 3GPP. These include multi-carrier HSPA, downlink and uplink CELL_FACH state enhancements, and introduction of downlink and uplink MIMO. However, much of the focus has been on improving downlink performance and further enhancements are needed for the uplink to handle increasing traffic load as well as new traffic types.
|
25.701
|
Study on scalable UMTS Frequency Division Duplex (FDD) bandwidth
|
TR
|
12.2.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.701/25701-c20.zip
|
The present document is the result of the study item "Scalable UMTS FDD Bandwidth".
This study identifies target scenarios and investigates candidate solutions by considering benefits and technical complexity. The detailed objectives are described in RP-130221 [3].
|
25.702
|
Study on Dedicated Channel (DCH) enhancements for UMTS
|
TR
|
12.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.702/25702-c10.zip
|
The present document captures design options, evaluation results and analysis from the study item on "DCH enhancements for UMTS" described in [2].
The work under this study intends to capture the merits and feasibility of DCH Enhancements in terms of the reduction in the average required power per user on the downlink and the average RoT consumed on the uplink. An evaluation of the increase in UE data throughput in a mixed voice-data traffic scenario when DCH enhancements were applied is also conducted.
The following enhancements are considered in the study:
• DL Physical Layer Enhancements
◦ DL DPCCH Slot Format Optimization
◦ DL DPDCH Frame Early Termination
◦ DL ACK Indicator design for UL FET
◦ DPCH Time Domain Multiplexing
◦ Reduced power control rate schemes
◦ Node B DTX/UE DRX Mechanisms
• UL Physical Layer Enhancements
◦ UL DPCCH Slot Format Optimization
◦ UL Frame Early Termination
◦ UL ACK Indication for DL Frame Early Termination
◦ DTCH/DCCH time compression
◦ Reduced power control rate schemes
◦ UE DTX/Node B DRX mechanisms
Additionally, the following aspects are also investigated:
• UE Power Consumption Efficiency
• Impact on Network implementation
• Impact on UE implementation
• Impact on specifications
|
25.703
|
Universal Terrestrial Radio Access (E-UTRA); Study on Home Node B (HNB) emergency warning area
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.703/25703-c00.zip
|
The present document captures the result of the Study on HNB Emergency Warning Area for UTRA (RP-131258 [2]).
|
25.704
|
Study on enhanced broadcast of system information
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.704/25704-c00.zip
|
The present document captures the studies for [2] about the need to introduce mechanisms in UMTS to provide additional broadcast capacity, considering:
- the currently existing deployments and their future evolutions,
- the broadcast load expected from different releases, including Rel-11 and estimate for Rel-12,
- the impact on system performance and end-user experience in case of increased system information scheduling latency.
|
25.800
|
Technical Report on UMTS Heterogeneous Networks
|
TR
|
12.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.800/25800-c10.zip
|
The present document captures evaluation results and analysis from the study item on "UMTS Heterogeneous Networks" described in [2].
|
26.235
|
Packet switched conversational multimedia applications; Default codecs
|
TS
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-c00.zip
|
The present document introduces the set of default codecs for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document is applicable, but not limited, to services such as PS video telephony and Push to talk over Cellular (PoC) as well as Combined CS and IMS services (CSI). For Multimedia Telepphony Service for IMS (MTSI), all media handling, including codecs, is defined in TS 26.114 [50]. This specification does not apply for MTSI.
The applicability of this specification to GERAN is FFS.
|
26.236
|
Packet switched conversational multimedia applications; Transport protocols
|
TS
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.236/26236-c00.zip
|
The present document introduces the required protocols for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communications are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document describes the required protocol related elements for 3G PS multimedia terminal:
• required SDP signalling regarding the media type bit rate, packet size, packet transport frequency;
• usage of RTP payload for media types;
• bandwidth adaptation;
• QoS negotiation.
The present document is applicable, but not limited, to packet switched video telephony. All media handling, including codecs, for Multimedia Telephony Service for IMS (MTSI) service is defined in [35]. This specification does not apply to MTSI.
The applicability of the present document to GERAN is FFS.
|
26.827
|
IP Multimedia Subsystem (IMS) based streaming and download delivery enhancements
|
TR
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.827/26827-c00.zip
|
The objectives of the Work Item on IMS-based Streaming and Download Delivery Enhancements (IMS_SDE) include:
- Identify use cases and recommended requirements based on Release 10/11 functionality included in the PSS and MBMS specifications to be addressed for IMS-based streaming and download enhancements, and document the adopted use cases.
- Develop procedures towards enabling the IMS-based extensions of the identified use cases in TS 26.237.
The present document is written in a form that the recommendations made and assumptions stated are directed to authors and contributors to Technical Specifications being affected as a result of the study presented here.
|
26.848
|
Multimedia Broadcast/Multicast Service (MBMS); Enhanced MBMS operation
|
TR
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.848/26848-c00.zip
|
The present document covers the MBMS enhancement aspects, including MBMS Over The Air (OTA) efficiency, MBMS for datacasting and real-time content, and generic signalling of DASH transport over broadcast, multicast and unicast.
|
26.849
|
Multimedia Broadcast/Multicast Service (MBMS) improvements; MBMS operation on demand
|
TR
|
12.1.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.849/26849-c10.zip
|
The present document covers:
- Use cases on the dynamically establishment of MBMS User Services to offload unicast delivery of certain contents, either real-time or non-real-time based, which reach a certain traffic volume due to the popularity of those contents.
- Use cases for terminating a previously established MBMS User Service due to subsequently decrease in its consumption.
- Recommended requirements on the BM-SC and UE to support on-demand MBMS.
- Gap analyses in the existing TR 26.346 specification for supporting the recommended requirements for MooD operation.
- High-level MBMS and unicast network architecture in the context of MooD.
- Message sequence diagrams illustrating examples of MooD operation.
- Description of solution frameworks that enable MooD operation, including configuration data, necessary interaction between BM-SC and UE to activate or trigger the MBMS client for reception of newly-established MBMS User Service, and the reporting of ongoing consumption of the MBMS service to enable measurement of ongoing demand for that service.
|
28.820
|
Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbrella Operation Model (UOM)
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.820/28820-c00.zip
|
The present document is the result of the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules.
Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original, for comparison with the corresponding TMF version.
Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report.
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 3GPP TR 32.833 [1], TM Forum TR 166 [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. The present document defines these common model elements.
To be noted:
- The Umbrella Operation Model (UOM) described in the present 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.
|
29.806
|
Study on IP Multimedia Subsystem (IMS) Proxy Call Session Control Function (P-CSCF) restoration procedures
|
TR
|
12.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.806/29806-c10.zip
|
The present document analyses existing P-CSCF restoration mechanism limitations and drawbacks, as defined by 3GPP TS 23.380 [2] and 3GPP TS 24.229 [3], and proposes alternative solutions that could minimize such limitations.
Expected output from this document is a proposal of an enhanced P-CSCF restoration mechanism.
|
29.807
|
Study on General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTP-C) overload control mechanisms
|
TR
|
12.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.807/29807-c00.zip
|
The present document investigates various aspects related to the support of the GTP-C signalling based load / overload control solution as specified in 3GPP TS 23.401 [2] and TS 23.060 [3], as also concluded in TR 23.843 [4], with the main focus on:
• Definition of "Load Control" and "Overload Control" related information with enough precision to guarantee a common multi-vendor interpretation of this information allowing inter-operability between various GTP-C nodes;
• Mechanisms to address various "Notes", which are targeted to the stage 3, specified in clause 8.2.5, clause 8.2.6 & clause 10.2 of the 3GPP TR 23.843 v1.0.0 [4].
This technical report addresses the following aspects related to the "GTP-C signalling based load and overload control" feature in detail:
- Investigation and study of the following aspects related to the "Load Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Load Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of "Load Control Information" in GTP-C messages.
- Potential enhancements to the existing node selection algorithm to take information received from "Load Control Information" into account.
- Investigation and study of the following aspects related to the "Overload Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Overload Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of the "Overload Control Information" in GTP-C messages.
- Message throttling algorithms and message prioritization when congestion mitigation is applied.
- Propagation of the MME/SGSN identity to the PGW to ensure that the overload mitigation is always applied to the currently serving MME/SGSN.
- Potential interactions with the existing overload control mechanisms when the overload factor is received within the "Overload Control Information".
- Investigation and study of the following the other deployment related aspects to fulfill the normative requirements or to produce recommendations.
- Applicability of this feature to 3GPP and non-3GPP based GTP-C interfaces.
- Methods to discover the support of this feature by the peer node in the network.
- Supporting the feature across the PLMN boundary.
- Issues within the network with partial support of this feature.
- Overload mitigation policies when this feature support is not enabled in the network.
|
29.809
|
Study on Diameter overload control mechanisms
|
TR
|
12.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.809/29809-c00.zip
|
The present document investigates possible enhancements of the Diameter base protocol (IETF RFC 6733 [2] and existing Diameter applications to support overload control mechanisms in 3GPP core networks.
This work is based on the results of the feasibility study on Core Network Overload available in 3GPP TR 23.843 [3] and the related work done in the IETF Diameter Maintenance and Extensions (DiME) working group.
This study will cover:
- Identification of the set of requirements for an improved overload control mechanism over Diameter based signaling interfaces used in 3GPP core networks.
- Identification, evaluation and selection of candidate solutions for overload control mechanisms, including:
- Mechanisms to detect overload situations e.g. notification of Diameter end-point signaling load;
- Mechanisms to exchange overload control policies between Diameter end-points;
- Details on the expected behaviour of 3GPP core network nodes supporting the defined overload control mechanism (Diameter end-points and Diameter agent);
- Evaluation of the impacts of the proposed solution(s) on existing Diameter-based Technical Specifications and Diameter based signalling networks (internal operator networks, inter-operator network (e.g. IPX).
- Recommendations on the solutions to select depending of the applicability context (interfaces, application, network, etc.)
The results of this study will contribute to the work done within the IETF DiME working group on Diameter overload control, through official liaison statement from 3GPP or company-driven individual contributions, which includes:
- Provide feedback from 3GPP on the requirements for Diameter overload control mechanisms defined in IETF Draft draft-ietf-dime-overload-reqs-06 [4]);
- Contribute to the specification of the IETF standard mechanism for overload control over Diameter.
The results of this study will be used to identify the changes required in the 3GPP specifications to support overload control mechanisms over Diameter-based 3GPP interfaces and applications.
|
29.817
|
Study on eXtensible Markup Language (XML) based access of the Application Function (AF) to the Policy and Charging Rules Function (PCRF)
|
TR
|
12.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.817/29817-c10.zip
|
The Technical Report describes solutions for an XML based protocol (e.g. SOAP, Restful HTTP, etc.) between the AF and the PCRF for the case of non IMS applications. The scope of this work is to provide an XML based equivalent to the Diameter based signalling that is presently specified in 3GPP TS 29.214 [5].
This study covers the following alternatives:
- XML based protocol between AF and PCRF;
- Adding a new protocol converter (as a stand-alone entity) between PCRF and AF
Investigate a suitable transport protocol for XML, charging issues in case of 3rd party SPs, security issues.
Roaming in both home routed and local break out and signalling routing aspects (e.g. DRA handling and others aspects) has also been included.
Necessary changes to 3GPP specifications are identified.
|
29.828
|
Study on extended IP Multimedia Subsystem (IMS) media plane security features and Transmission Control Protocol (TCP) related Network Address Translation (NAT) traversal support; IMS H.248 profiles aspects
|
TR
|
12.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.828/29828-c10.zip
|
The present document investigates the IMS H.248 profiles requirements and procedures to support the stage 2 requirements specified in 3GPP TS 33.328 [2] for Extended IMS media plane security features.
This includes in particular the following aspects:
1. Provide end-to access edge protection of session based messaging (MSRP) traffic using TLS and certificates fingerprints exchanged over SDP;
2. Provide end-to-end protection of session based messaging (MSRP) traffic using TLS;
3. Provide end-to access edge protection of BFCP based traffic, using TLS and certificates fingerprints exchanged over SDP;
4. Provide optional support of TLS protection of BFCP and MSRP based traffic at the Conference Server.
5. Analyse requirements and procedures for end-to-end TCP bearer connection control and related NAT traversal support.
NOTE: this aspect is not specific to media security and may result in normative work via another work item.
6. Provide support of TCP-based IP transport connections for TLS security sessions, which includes possible NAT traversal support during the TCP connection establishment phase, possible correlations between the establishment (and release) events of TCP connections with TLS session establishment (and release).
7. Provide end-to access edge protection of T.38 fax using DTLS.
This study will cover:
- Identification of the key issues and the main design considerations that should drive the definition of stage 2 requirements and procedures for the Iq, Ix and Mp profiles;
- Identification of the requirements and procedures for the Iq, Ix and Mp profiles for support of end-to-access edge and end-to-end media security for session-based messaging (MSRP [6]) and conferencing (BFCP [16]);
- Identification of the requirements and procedures for the Iq profile for support of end-to-access edge media security for T.38 fax over UDPTL/UDP transport;
- Identification of the ITU-T H.248 extensions necessary to fulfil the 3GPP requirements and identification of potential missing gaps that should be taken into account by ITU-T Q3/16;
- Conclusions and Recommendations for the normative work.
The results of this study will be used to identify the changes required in the 3GPP specifications to support Extended IMS media plane security.
|
29.854
|
Study on shared data update for multiple subscribers
|
TR
|
12.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.854/29854-c20.zip
|
The present document analyses the use cases for the need of update of subscription data shared by multiple subscribers, the existing mechanisms in 3GPP networks which is or may be used for shared data update, possible solutions and impact on the existing interfaces and relevant elements.
The recommendation of the document is used to decide whether it is required to standardize any solution, and which is the final preferred solution if further standardization is needed.
|
32.830
|
Telecommunication management; Study on version handling over Itf-N
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.830/32830-c00.zip
|
The scope of the study is to:
• Document current version handling capabilities in SA5 OAM specifications (clause 5)
• Identify and agree on the use cases and requirements (clause 6) for a coherent approach for version handling capabilities for SA5 OAM specifications
• Identify solution(s) with pros and cons to support the identified requirements (clause 7). The solutions may require enhancement or modification of rules in the IRP methodology as well as enhancements of existing or addition of new IRP specifications, utilizing SOA capabilities where appropriate. This includes:
1. The identification of entities that require version control (clause 7.1)
2. The protocol(s) by which the entity version can be discovered and registered (clause 7.2)
• Recommend a solution (clause 8).
Note: "Version handling" in the context of this study addresses what kind of support for version information that is available over the Itf-N interface, i.e. what the IRPManager can "see" regarding which versions of the 3GPP specifications that are supported by the IRPAgent, for which object instances etc.
|
32.835
|
Telecommunication management; Study of heterogeneous networks management
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.835/32835-c00.zip
|
The present document investigates and makes recommendations on how management information can be selected by the manager over Itf-N for heterogeneous networks (see TR 21.905 [1]) nodes that are owned, deployed and maintained by the operator.
The nodes that are owned, deployed or maintained by residential users are out of scope of the present document, such as Home NodeBs, Home eNodeBs.
|
32.836
|
Telecommunication management; Study on Network Management (NM) centralized Coverage and Capacity Optimization (CCO) Self-Organizing Networks (SON) function
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.836/32836-c00.zip
|
The present document summarizes the result of the study on "Enhanced Network Management (NM) centralized Coverage and Capacity Optimization".
A CCO function that resides outside the NM is out of the scope for this study.
|
32.841
|
Telecommunication management; Study on Wireless Local Area Network (WLAN) management
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.841/32841-c00.zip
| |
32.844
|
Study of charging support of Proximity-based Services (ProSe) direct communication for public safety use
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.844/32844-c00.zip
|
The present document contains the outcome of the study on the charging architecture for the one-to-many "ProSe Direct Communication for ProSe-enabled Public Safety UEs".
The study covers the "ProSe Direct Communication for Public Safety use" as specified in TS 23.303 [238], in order to meet the charging requirements specified in TS 22.115 [101].
The present document makes recommendations for the following aspects of ProSe Direct Communication for Public Safety use:
- charging requirements and principles;
- charging architecture and charging scenarios, with the support of delayed reporting;
- charging interfaces; and
- recommendations to CT1 on UE reporting configuration and usage information elements.
|
32.851
|
Telecommunication management; Study on Operations, Administration and Maintenance (OAM) aspects of Network Sharing
|
TR
|
12.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.851/32851-c20.zip
|
The present document is aimed at addressing the operational implications of network sharing.
There are a wide variety of deployment scenarios for network sharing.
Scenarios identified in 3GPP TS 23.251 [3] and TR 22.951 [2] are taken into consideration to identify OAM impacts.
3GPP TS 23.251 "Network sharing; Architecture and functional description" specifies the stage 2 descriptions which are also considered to address OAM aspects.
NGCOR defined RAN sharing requirements are taken into account as input for this study.
|
32.859
|
Telecommunication management; Study on Alarm Management
|
TR
|
12.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.859/32859-c10.zip
|
The scope of the present document is to study how to improve the quality of alarms and enhance usability of alarm systems.
|
33.804
|
Single Sign On (SSO) application security for Common IP Multimedia Subsystem (IMS) based on Session Initiation Protocol (SIP) Digest
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.804/33804-c00.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.
|
33.805
|
Study on security assurance methodology for 3GPP network products
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.805/33805-c00.zip
|
The present document studies methodologies for specifying network product security assurance and hardening requirements, with associated test cases when feasible, of 3GPP network products. Network product security assurance and hardening refers to protection against unwanted access to a 3GPP network product, its Operating System, and main running Application(s). The suitability of industry standard methodologies and the potential need for collaboration with bodies such as GSMA, CCRA, ISO and ITU will be assessed. The study will also consider regulatory aspects and the potential need for security certification. The suitability of the candidate methodologies will be assessed with reference to real world examples.
Part of the scope of this work is to conclude which 3GPP network products, if not all, would be subject to 3GPP network product security assurance and hardening requirements. There is likely to be a long list with the result that prioritisation will be required. LTE network product classes will be the first priority. The work will also study exactly what should constitute a 3GPP network product in the context of this study e.g. whether it should be an individual 3GPP functional entity, a group of 3GPP functional entities or some other realisation.
The study will also include assessing the extent to which individual 3GPP network products need to be hardened beyond a common baseline and should take into consideration network vs. environment.
|
33.823
|
Security for usage of Generic Bootstrapping Architecture (GBA) with a User Equipment (UE) browser
|
TR
|
12.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.823/33823-c20.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
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.829/33829-c00.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.831
|
Study on security on spoofed call detection and prevention (Stage 2)
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.831/33831-c00.zip
|
The present document studies the means to identify calls with spoofed Calling Line Identification terminating in the CS domain where the call could have originated from either inside or outside the CS domain. Calling Line Identification (CLI or CLID), also called Caller Identification (CID), evaluates and transmits a caller's number while Calling Line Identity Presentation (CLIP) enables displaying the caller's number during call setup or ringing. Usual applications for CLIP are:
to display the original number of the caller;
to display a caller's presentation number, e.g. a doctor calling a patient out of hours who doesn't want to disclose his private number but showing instead the number of his office;
to display a number unrelated to the calling line, e.g. call centers displaying numbers related to their customers (depending on national regulations).
But CLI can also be misused to display a misleading number in the display that is in no way related to the originator of the call. This behaviour is called CLI spoofing or spoofed call. CLI spoofing ranges from harmless hoax to criminal activities like for example Voice Phishing (vishing) by displaying the forged number of a bank in order to steal the callee's credentials. And although CLI may be unreliable, people use it to decide whether to accept a call or not.
This study item studies the detection of a spoofed call as the first step, and prevention as a second step if detection is achievable. In particular, the goals of this document are:
• Outline valid threat scenarios for spoofed calls coming to 2G and 3G CS domains;
• Analyze and evaluate if any tools in 3GPP can be used to counteract spoofed call detection and prevention;
• Study and identify any other suitable techniques or mechanisms for spoofed call detection and prevention.
NOTE: When the "potential requirements" and "potential solutions" from the present document might be introduced into normative documents (Technical Specifications - TSs), the word "should" needs to be changed into "shall" (with bold characters).
|
33.865
|
Security Aspects of WLAN Network Selection for 3GPP Terminals
|
TR
|
0.5.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.865/33865-050.zip
|
The present document studies the security aspects of WLAN Network Selection for 3GPP Terminals. In particular, the goals of this document are:
-To work on security impacts and threats of key issues and solutions of SA2’s specifications.
-To identify potential conflicts between security mechanisms provided by non-3GPP providers via Hotspot 2.0 and security mechanisms provided by 3GPP operators, and define security solutions if needed.
-To identify possible impacts to the current authentication method of non-seamless WLAN offload.
Editor Notes: Need to update the scope with relevant TS and TR.
|
33.868
|
Study on security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements
|
TR
|
12.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.868/33868-c10.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.
|
33.869
|
Security aspects of Public Warning System (PWS)
|
TR
|
0.7.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.869/33869-070.zip
|
The present document studies security features and mechanisms for protection against false Base Stations broadcasting false Warning Notifications.
The default terminal behaviour is to accept all Warning Notifications even if their authenticity is unknown (i.e. no security protection). The default terminal behaviour is therefore open to the presentation of false Warning Notifications issued by false BSs even in countries without a Public Warning System (PWS) deployed.
Examples of false BS risks include, but are not limited to:
• False Warning Notifications to induce panic;
• Abuse of warning system broadcast channel to send advertising / spam.
These security features and mechanisms are optional since there are regions and countries that do not require this functionality.
|
33.871
|
Study on security for Web Real Time Communications (WebRTC) IP Multimedia Subsystem (IMS) client access to IMS
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.871/33871-c00.zip
|
The goal of WebRTC IMS Client access to IMS is to significantly expand the pool of clients able to access IMS.
The present document contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of WebRTC IMS Client access to IMS.
For this purpose the present document is addressing:
• WebRTC IMS Client authentication mechanisms, including the re-use of existing IMS authentication mechanisms from WebRTC IMS Clients;
• Required enhancements to IMS media plane security;
• Control plane security related aspects.
|
33.888
|
Study on security issues to support Group Communication System Enablers (GCSE) for LTE
|
TR
|
12.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.888/33888-c10.zip
|
The present document studies the security aspects of the Group Communication Service Enabler for LTE (GCSE_LTE) and gives an evaluation of possible technical security solutions supporting such an Enabler. The present document looks at security from system perspective and defines functional security requirements for all entities.
Stage 1 requirements for these services are defined in 3GPP TS 22.468 [2].
Different possible Stage 2 solutions for GCSE have been studied in 3GPP TR 23.768 [3].
3GPP TS 23.468 [8] provides the stage 2 description for the 3GPP system provided enablers to support GC services using E-UTRAN in Rel-12.
Based on the work done in 3GPP TS 22.468 [2], 3GPP TR 23.768 [3], and 3GPP TS 23.468 [8] the objectives of the present document are to identify the threats and deduce security requirements, develop GCSE_LTE security solutions, and determine which solution(s) from the present document (Study/TR phase) should be converted into normative specifications for Rel-12.
NOTE: The present document collects requirements that are not normative.
|
34.114
|
User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing
|
TS
|
12.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.114/34114-c20.zip
|
The present document describes the test procedure for the radiated performances measurements of the 3G/2G user equipment/mobile stations (UE/MS) in active mode in both the uplink and the downlink. The FDD UE test procedure is based on the test method developed as a result of COST 273 Sub-Working Group (SWG) 2.2 members’ contributions. Background work has also been made in the former COST259 project. The TDD UE test procedure is based on the test method developed as a result of CCSA TC9 WG1 members’ contributions. Background work has been made in the former CCSA TC9 project.
The measurement procedure explained in this document applies to UE/MS used under the “speech mode” conditions that correspond to predefined positions for voice application when the handset is held close to the user’s head. This method is also applicable to free space measurements for UE/MS devices. The data transfer position (free space) explained in this document applies when the UE is used away from the user’s head. For LME and LEE devices free space configuration without head and hand phantoms is applicable. Free space measurements are applicable to devices used in the data transfer position that consist of the laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
The tests apply to UEs and laptops using single or multiple receive antennas. For GSM technology this is applicable to all MSs and for 3G technology this is applicable to “one antenna” UEs and “RxDiversity” UEs.
The testing methodology applies to any single or multi-mode (GSM / UMTS / TD-SCDMA) terminals.
The radio tests considered here are:
1. The measurement of the Total Radiated Power (TRP)
2. The measurement of the Total Radiated Sensitivity (TRS)
The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user.
The major parts of this test procedure are based on the 3-D pattern measurement method. It has been considered necessary to define some items and components in the test procedure in detail, such as test channels and phantom set-ups, in order to make the testing in different laboratories harmonized. The procedure is, however, not limited to some specific antenna chambers or positioners.
|
36.809
|
Radio Frequency (RF) pattern matching location method in LTE
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.809/36809-c00.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.833-1-03
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 3
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-03/36833-1-03-c00.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] (revised to [17]).
The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-23
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 23
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-23/36833-1-23-c00.zip
|
The present document is a technical report of the work item for LTE Advanced intra-band contiguous Carrier Aggregation in Band 23, which was approved at TSG RAN #60 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-27
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 27
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-27/36833-1-27-c00.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.833-1-39
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 39
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-39/36833-1-39-c00.zip
|
The present document is a technical report of the work item for LTE-Advanced Intra-band Contiguous Carrier Aggregation in Band 39 which 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.833-1-42
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 42
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-42/36833-1-42-c00.zip
|
The present document is a technical report of the work item on LTE-Advanced Intra-band Contiguous Carrier Aggregation in Band 42 which was approved at TSG RAN #62 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-2-02
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 2
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-02/36833-2-02-c00.zip
|
The present document is a technical report of the work item for LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 23, which was approved at TSG RAN #60 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-2-03
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 3
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-03/36833-2-03-c00.zip
|
The present document is a technical report of the LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 3 work item which was approved at TSG RAN #55 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 3.
The report provides background, requirements and a list of recommended changes to the specifications.
|
36.833-2-04
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 4
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-04/36833-2-04-c00.zip
|
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 [9].
|
36.833-2-07
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 7
|
TR
|
12.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-07/36833-2-07-c20.zip
|
The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 7 work item which was approved at TSG RAN #57 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 7.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.833-2-23
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 23
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-23/36833-2-23-c00.zip
|
The present document is a technical report of the work item for LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 23, which was approved at TSG RAN #60 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-2-25
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 25
|
TR
|
12.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-25/36833-2-25-c10.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.
An additional technical report is also included for additional bandwidth combinations for intra-band non-contiguous CA in Band 25 work item which was approved at TSG RAN#63[3].
|
36.833-2-42
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 42
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-2-42/36833-2-42-c00.zip
|
The present document is a technical report of the work item for LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 42, which was approved at TSG RAN #62 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-4
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) for 2 uplinks (2UL); Framework
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-4/36833-4-c00.zip
|
The present document is a technical report for REL-12 2UL non-contiguous intra-band CA framework WI and it contains both the UE and BS studies.
|
36.833-4-04
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 4 for 2 uplinks (2UL)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-4-04/36833-4-04-c00.zip
|
The present document is the technical report for the LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 4 for 2UL work item, which was approved at TSG RAN #60 [3].
|
36.833-5-40
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 40 for 3 downlinks (3DL)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-5-40/36833-5-40-c00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 40 for 3DL work item which was approved at TSG RAN #63 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 40 for 3DL.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.833-5-41
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 41 for 3 downlinks (3DL)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-5-41/36833-5-41-c00.zip
|
The present document was approved at TSG RAN #61 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 41 for 3DL.
The present document provides motivation, requirements and a list of recommended changes to the specifications.
|
36.833-6-41
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 41 for 3 downlinks (3DL)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-6-41/36833-6-41-c00.zip
|
The present document is a technical report of the LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 41 for 3 DL work item which was approved at TSG RAN #62 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE TDD Band 41 for 3DL.
The present document provides motivation, requirements and a list of recommended changes to the specifications.
|
36.836
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on mobile relay
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.836/36836-c00.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.840
|
LTE 450 MHz in Brazil Work Item Technical Report
|
TR
|
12.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.840/36840-c10.zip
|
The present document is a technical report for the introduction of LTE 450 in Brazil work item, which was approved at TSG RAN#57. The objective of this work item is to specify technical requirements for deploying LTE operation in 450 MHz band in Brazil.
|
36.842
|
Study on Small Cell enhancements for E-UTRA and E-UTRAN; Higher layer aspects
|
TR
|
12.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.842/36842-c00.zip
|
The present document is related to the technical report for the study item "Study on Small Cell Enhancements for
E-UTRA and E-UTRAN – Higher layer aspects" (RP-122033 [2]).
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
The present document gathers all technical outcome of the study item, and draws a conclusion on the way forward.
|
36.843
|
Study on LTE device to device proximity services; Radio aspects
|
TR
|
12.0.1
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.843/36843-c01.zip
|
The present document contains the result of the Device to Device (D2D) study item.
The Feasibility Study on Proximity-based Services (FS_ProSe, TR 22.803 [2]) has identified services that could be provided by the 3GPP system based on UEs being in proximity to each other. The identified areas include services related to commercial services and Public Safety that would be of interest to operators and users.
The objectives of this feasibility study are to evaluate LTE Device to Device proximity services, as follows:
Within network coverage
Outside network coverage
Discovery
Non public safety &
public safety requirements
Public safety only
Direct Communication
At least public safety requirements
Public safety only
In particular:
1. Define an evaluation methodology and channel models for LTE device to device proximity services, including scenarios to compare different technical options to realize proximal device discovery and communication, appropriate performance metrics, and performance targets (e.g. range, throughput, number of UEs supported). [RAN1]
2. Identify physical layer options and enhancements to incorporate in LTE the ability for devices within network coverage: [RAN1]:
- to discover each other in proximity directly in a power-efficient manner.
- to communicate directly, including enhancements to LTE interference management and scheduling that allow the LTE network to enable, manage, and continuously control all direct, over the air, device to device communications.
3. Identify and evaluate options, solutions and enhancements to the LTE RAN protocols within network coverage [RAN2 primary, RAN3 secondary]:
- to enable proximal device discovery among devices under continuous network management and control,
- to enable direct communication connection establishment between devices under continuous network management and control,
- to allow service continuity to/from the macro network
4. Consider terminal and spectrum specific aspects, e.g. battery impact and requirements deriving from direct device to device discovery and communication [RAN4].
5. Evaluate, for non public safety use cases, the gains obtained by LTE device to device direct discovery with respect to existing device to device mechanisms (e.g. WiFi Direct, Bluetooth), and existing location techniques for proximal device discovery (e.g. in terms of power consumption, and signaling overhead) [RAN1, RAN2].
6. The possible impacts on existing operator services (e.g. voice calls) and operator resources should be investigated [RAN1].
7. For the purposes of addressing public safety requirements, identify and study the additional enhancements and control mechanisms required to realize discovery and communication outside network coverage [RAN1, RAN2].
The identified options/enhancements should reuse the features of LTE as much as possible.
The study will cover:
- Single and multi-operator scenarios, including the spectrum sharing case where a carrier is shared by multiple operators (subject to regional regulation and operator policy)
- LTE FDD and LTE TDD operations
In this study item, the study of direct communication shall address at least public safety requirements and use cases..
It is assumed that aspects related to service authorization, system level architecture, security, and lawful interception are covered in the 3GPP TSG SA Working Groups.
|
36.846
|
LTE in the US Wireless Communications Service (WCS) band
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.846/36846-c00.zip
|
Previously the deployment of the 3GPP LTE technology in the bands 2305 to 2315 MHz and 2350 to 2360 MHz (known as the Wireless Communications Service band, or ‘WCS' in the United States), could not be accommodated due to technical and operational constraints present in FCC regulations. This is commonly known as Block A (2305 - 2315/2350 - 2355 MHz) and Block B (2310 - 2315/2355 - 2360 MHz) in the WCS Band. The FCC on October 17, 201 amended and confirmed the technical and operational characteristics for WCS which enable the deployment of LTE FDD technology in Blocks A & B in the frequency band covering 2305 - 2315 MHz and 2350 - 2360 MHz.
|
36.847
|
Study on LTE Time Division Duplex (TDD) - Frequency Division Duplex (FDD) joint operation including Carrier Aggregation (CA)
|
TR
|
12.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.847/36847-c00.zip
|
The present document contains a Study on FDD and TDD joint operation for E-UTRA and E-UTRAN.
The objective of the present document is as follows:
• Identify deployment scenarios of joint operation on FDD and TDD spectrum, and network/UE requirement to support joint FDD/TDD operation;
• Based on the identified deployment scenarios and network/UE requirements, identify possible solutions for FDD-TDD joint operation.
• Based on the above, consider whether such solutions, if any, need to be added to the Work Item itself, or in separate Work Items.
|
36.848
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Study on smart congestion mitigation
|
TR
|
12.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.848/36848-c00.zip
|
The present document is related to the technical report for the study item "Study on Smart Congestion Mitigation in E-UTRAN" [2].
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all technical outcome of the study item, and draw a conclusion on way forward.
|
36.852-12
|
LTE Advanced inter-band Carrier Aggregation (CA) (2DL/1UL)
|
TR
|
12.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.852-12/36852-12-c20.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.
The present document 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
LTE_CA_B4_B12_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 12
A2
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
LTE_CA_B25_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 25, Band 41 and Band 41
-
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.853-12
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced 3 Band Carrier Aggregation (CA) (3DL/1UL)
|
TR
|
12.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.853-12/36853-12-c20.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.
The present document 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_B2_B4_B4
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 4
LTE_CA_B2_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 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_B3_B26
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 26
LTE_CA_B1_B19_B21
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 19 and Band 21
LTE_CA_B2_B2_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2 and Band 5
LTE_CA_B2_B5_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 13
LTE_CA_B1_B18_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 18 and Band 28
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_B4_B4_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 5
LTE_CA_B4_B5_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 13
LTE_CA_B4_B4_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 12
LTE_CA_B3_B3_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 8
LTE_CA_B41_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 41, Band 42 and Band 42
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_B25_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 25, Band 41, and Band 41
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.856
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Study on RAN sharing enhancements
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.856/36856-c00.zip
|
The present document is a technical report of the study item for Study of RAN aspects of RAN Sharing Enhancements for LTE - Core Part which was approved at TSG RAN #62. The report provides background, analysis of the requirements set out in [1], and a list of recommended changes to the specifications.
|
36.860
|
LTE-Advanced dual uplink inter-band Carrier Aggregation (CA)
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.860/36860-100.zip
|
The present document is a technical report for LTE Advanced Dual Uplink Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Uplink Inter-band Carrier Aggregation requirements.
|
36.860-12
|
LTE-Advanced dual uplink inter-band Carrier Aggregation (CA)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.860-12/36860-12-c00.zip
|
The present document is a technical report for LTE Advanced Dual Uplink Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Uplink Inter-band Carrier Aggregation requirements.
|
36.863
|
Study on Cell-specific Reference Signals (CRS) interference mitigation for homogenous deployments of LTE
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.863/36863-c00.zip
|
The objectives of this Study Items are:
● Identify the partial traffic loading levels and other realistic system level parameters (e.g. traffic and interference models including interference level, time offset between cells and frequency offset between cells) and performance metrics for studying the feasibility of CRS IM in a synchronized homogenous network assuming:
- 3GPP Case 1 as a starting point
- non-colliding CRS between serving and dominant aggressor/interfering cells and
- non-colliding CRS between dominant aggressor/interfering cells
- The homogeneous deployment and relevant system parameters should reuse as much as possible those defined in the Rel-11 performance study of MMSE-IRC
● Identify the baseline receiver which can be used for evaluating the gain of CRS IM in a synchronized homogenous network considering:
- Reuse of CRS IM receiver assumed for Release 11 FeICIC.
- Reuse of MMSE-IRC receiver as the baseline receiver. MMSE-IRC does not differentiate CRS or data interference when suppressing them and was assumed for Release 11 work item on interference rejection combining.
● Agree on interference levels, interference models and simulation parameters for link level evaluations.
● Evaluate the system level and link level gains of CRS IM with respect to the baseline MMSE-IRC receiver in a synchronized homogenous network deployment under the various loading levels identified.
- Gains of CRS IM from 1 and 2 aggressor cells CRS shall be evaluated and compared.
- Modeling of realistic CRS IM receiver for system level performance evaluation should be clarified and agreed if possible
● Investigate UE complexity tradeoffs e.g. tradeoff between number of interferers to cancel and the number of transmit antenna ports.
● The introduction of CRS IM based receiver requirements for homogenous deployments will only use the existing Release 11 signaling of CRS assistance information.
Note 1: Interference from neighboring cells’ PDSCH is not the focus of this study item. Any interference from data, which varies according to the traffic loading level, is assumed to be suppressed in the same way as in Rel-11 with the baseline MMSE-IRC receivers.
Note 2: Non-colliding CRS is prioritized and will be studied first while colliding CRS is not precluded. But the study will focus only on UE demodulation aspects.
|
36.866
|
Study on Network-Assisted Interference Cancellation and Suppression (NAIC) for LTE
|
TR
|
12.0.1
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.866/36866-c01.zip
|
This document is related to the technical report for the study item “Study on Network Assisted Interference Cancellation and Suppression for LTE” [1]. The purpose of this TR is to capture the findings from TSG RAN WG1 and WG4 according to their respective objectives, and to draw a conclusion on way forward.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.868
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on group communication for E-UTRA
|
TR
|
12.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.868/36868-c00.zip
|
The present document is related to the study item "Study on Group Communication for E-UTRA" [2]. This Technical Report is to study and perform an evaluation of existing E-UTRA procedures to support Group Communication for E-UTRA. The Stage-1 requirements for this study are defined in 3GPP TS 22.468 [3].
This document is intended to gather all technical outcomes of the study and analysis, and draw a conclusion on the way forward.
|
36.872
|
Small cell enhancements for E-UTRA and E-UTRAN - Physical layer aspects
|
TR
|
12.1.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.872/36872-c10.zip
|
The present document contains the result of the study item "Small Cell Enhancements for E-UTRA and E-UTRAN – Physical-layer Aspects" [2].
The purpose of the present document is to help TSG RAN WG1 to define and describe the potential physical layer small cell enhancements under consideration and compare the benefits of each enhancement technique, along with the complexity evaluation of each technique.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
The present document is intended to gather all information and draw a conclusion on a way forward.
The present document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.873
|
Study on 3D channel model for LTE
|
TR
|
12.7.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.873/36873-c70.zip
|
The present document captures the findings of the study item "Study on 3D-channel model for Elevation Beamforming and FD-MIMO studies for LTE" [3] and aims to help TSG RAN WG1 to properly model and evaluate the performance of physical layer techniques using 3D channel models.
This document relates to the 3GPP evaluation methodology and covers the modelling of the physical layer of both Mobile Equipment (ME) and Access Network (AN) of 3GPP systems.
It intends to capture the scenarios relevant to 3D channel models and the modifications to the 3GPP evaluation methodology needed to support 3D channel modelling.
|
36.874
|
Coordinated multi-point operation for LTE with non-ideal backhaul
|
TR
|
12.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.874/36874-c00.zip
|
This document is related to the technical report for the study item “Study on CoMP for LTE with Non-Ideal Backhaul” [1]. The purpose of this TR is to help TSG RAN WG1 to assess the performance benefits of CoMP operation involving multiple eNBs with non-ideal backhaul and the required specification support for the inter-eNB operation.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information and draw a conclusion on way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.877
|
LTE Device to Device Proximity Services; User Equipment (UE) radio transmission and reception
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.877/36877-c00.zip
|
The present document is the Technical Report on TR on LTE Device to Device Proximity Services (UE).
The purpose of the present document is to study the radio requirements LTE Device to Device Proximity Services as part of the Rel-12 work item. The normative requirements resulting from the present document will be addressed in the applicable release 12 Technical Specifications (TS).
|
36.887
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Study on energy saving enhancement for E-UTRAN
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.887/36887-c00.zip
|
The present document is the technical report for the study item Study on Energy Saving Enhancement for E-UTRAN [2] which was approved at TSG RAN#58. The objectives of this study item are to identify potential solutions for energy saving scenarios for the LTE coverage layer scenario and the overlaid scenario and to perform their initial evaluation so that a subset of them can be used as the basis for further investigation and standardization.
|
36.888
|
Study on provision of low-cost Machine-Type Communications (MTC) User Equipments (UEs) based on LTE
|
TR
|
12.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.888/36888-c00.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.810
|
Study of Base Station (BS) specification structure
|
TR
|
12.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.810/37810-c20.zip
|
The present document is the technical report for the study item on Base Station specification structure.
|
37.808
|
Passive Intermodulation (PIM) handling for Base Stations (BS)
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.808/37808-c00.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.
|
37.813
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Study on LTE - High Rate Packet Data in 3GPP2 (HRPD) Inter-Radio-Access-Technology (RAT) self-configuring and self-optimizing network (SON) use cases and solutions
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.813/37813-c00.zip
|
The present document provides descriptions of agreed use cases and solutions with regards to self configuring and self optimizing networks for LTE-HRPD Inter-RAT cases.
The scope of the self configuring and self optimizing functionality is defined in 3GPP TS 36.300 [2].
|
37.822
|
Study on next generation Self-Optimizing Network (SON) for UTRAN and E-UTRAN
|
TR
|
12.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.822/37822-c10.zip
|
The objectives of the study are:
- Identify SON enhancements and new features needed for the interworking between existing features and user type differentiation based on of UE configuration UE capability UE characteristic or location (considering SA5 work).
- identify SON enhancements and new features needed for the deployments based on active antennas
- Evaluate the benefits and impacts of the identified solutions
For pre-release 12 Small Cells:
- Identify any gaps between existing SON and further enhancements needed specifically for Small Cells
- Reduce Network planning efforts for small cells
- Enhance network optimization efforts including aspects like mobility robustness and load balancing (duplication with HetNET mobility enhancement WI should be avoided)
The present document provides descriptions and possible solutions of use cases and analysis of these solutions. Considerations with regards to requested functionality in scope of other 3GPP groups if any, may be captured in this document as well.
|
37.834
|
Study on Wireless Local Area Network (WLAN) - 3GPP radio interworking
|
TR
|
12.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.834/37834-c00.zip
|
The present document constitutes the output of the Study on "WLAN/3GPP Radio Interworking" [2].
The present document captures agreements related to requirements, scenarios and key issues that shall be addressed by the study, candidate solutions as well as conclusions and recommendations for further work.
|
37.814
|
Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); L-band for Supplemental Downlink
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.814/37814-c00.zip
|
The present document is a technical report for the L-band for supplemental downlink (SDL) for 1452-1492 MHz. It is intended to be specified for both UTRA and E-UTRA for operations in Region 1. The band is to be used in CA or DB-DC-HSDPA/DB-4C-HSDPA configuration in E-UTRA and UTRA, respectively.
|
37.846
|
Study on 2GHz Frequency Division Duplex) FDD for Universal Terrestrial Radio Access (UTRA) and LTE in Region 1 (1980-2010 MHz and 2170-2200 MHz Bands)
|
TR
|
12.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.846/37846-c10.zip
|
The present document is the technical report for the 2GHz FDD for UTRA and LTE in Region 1 (1980-2010MHz and 2170-2200MHz Bands) study item in RP-122031 approved at TSG RAN#58 (Barcelona, Dec 2012).
The objective of the study item is to facilitate and harmonize the efficient use of the bands 1 980-2 010 MHz and
2 170-2 200 MHz for UMTS and LTE technologies in FDD in applicable countries in Region 1.
This study addresses only the case of a terrestrial network operating as a complementary ground component in the MSS frequency band 1 980 - 2 010 MHz / 2 170 - 2 200 MHz. Inter-operation and coexistence between the terrestrial network part of the complementary ground component and the satellite component are not part of this study.
The satellite component is not within the scope of 3GPP, and will therefore not be within the scope of this study either.
|
37.840
|
Study of Radio Frequency (RF) and Electromagnetic Compatibility (EMC) requirements for Active Antenna Array System (AAS) base station
|
TR
|
12.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.840/37840-c10.zip
|
The present document is a Technical Report of the Study Item for RF and EMC requirements for AAS, which was approved at TSG RAN #53 [2]. The report provides definition of AAS BS, the analysis of RF and EMC requirements for the corresponding deployment scenarios, as well as the test aspects of AAS BS. The possible impacts on the BS specifications are also included.
|
37.852
|
RAN enhancements for UMTS/HSPA and LTE interworking
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.852/37852-c00.zip
|
The present document captures the results of the study item on RAN Enhancements for UMTS/HSPA and LTE Interworking in RP-122036[2]. It identifies the existing mobility functions for HSPA and LTE interworking, the use cases and requirements for enhancements, and reviews and compares scenarios and techniques for enhancement of interworking functionality. The evaluation and comparison between existing and enhanced solutions is also included.
|
37.869
|
Study on enhancements to Machine-Type Communications (MTC) and other mobile data applications; Radio Access Network (RAN) aspects
|
TR
|
12.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.869/37869-c00.zip
|
The present document constitutes the output of the "RAN aspects of Machine-Type and other Mobile Data Applications Communications Enhancements" (FS_MTCe_RAN) study. The TR captures RAN view on the possible solutions identified during the study and the conclusions and recommendations for further work.
|
41.033
|
Lawful Interception requirements for GSM
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.033/41033-c00.zip
|
This Technical Report describes the interface requirements of a mechanism which will deliver intercept from GSM mobile stations, including both speech and data product.
The stage 1 description of Lawful Interception will be specified in 3GPP TS 42.033.
The stage 2 description of Lawful Interception will be specified in 3GPP TS 43.033.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.