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
|
|---|---|---|---|---|---|---|
22.816
|
3GPP enhancement for TV service
|
TR
|
14.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.816/22816-e10.zip
|
This Technical Report describes use cases, proposes assumptions and potential requirements and analyzes the gap in order to enhance 3GPP system for TV service support. The supported TV service includes linear TV, Live, Video on Demand, smart TV, and Over The Top (OTT) content.
|
22.818
|
Feasibility Study on Control of Applications when Third party Servers encounter difficulties
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.818/22818-e00.zip
|
With the spread of applications on UEs (also known as "smart phones"), coupled with the rapidly growing number of UEs designed for usage with little or no human involvement (machine type communications), the potential for issues to occur in the overall "system" involving these applications and the third party entities they interact with increases. When these third party entities experience difficulties, they may be able to manage their problems without undue impact on operator networks, but there will be times when they are not able to do so.
When a third party server becomes congested or fails, the communication by the UE applications that make use of that server need to be controlled so that excessive use of 3GPP network resources is avoided while not affecting other applications and their associated servers that are functioning normally.
The 3GPP network needs to be able to detect or receive an indication from a third party server of its congestion status or failure status and control UE applications (or their traffic in the 3GPP network) that make use of a third party server that has encountered difficulties. HTTP and other third party (possibly proprietary) protocols can have status codes but these can be insufficient as they cannot provide a suitable indication to the UE application of the nature of the issue and therefore could result in frequent retries even when these will fail, thus burdening the network with connection attempts that will fail.
The present document identifies potential requirements that will enable the 3GPP network to detect or receive an indication from a third party server of its congestion status or failure status and control the traffic of individual UE applications (or their traffic in the 3GPP network) when the 3GPP network becomes aware that a third party server has run into difficulties. This will make it possible to
- Reduce or avoid unproductive traffic in 3GPP network (i.e., traffic that the 3rd party server is not able to receive) by blocking it either in the UE or in the 3GPP network (primary objective)
- Allow 3GPP network to help 3rd party servers to handle overload and recover from failures (secondary objective)
|
22.838
|
Paging policy enhancements and procedure optimizations in LTE
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.838/22838-e00.zip
|
The objective is to study use cases and propose potential requirements to enhance the information set (e.g., user’s subscription, application characteristics) upon which paging policies may be based to allow optimization of the paging procedures in LTE.
|
22.861
|
Massive Internet of Things
|
TR
|
14.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.861/22861-e10.zip
|
Emerging from the FS_SMARTER work [2], the present document aims to identify and document the key families of use cases and their consolidated potential requirements, and to capture desired system requirements and capabilities to support the needs of new services and markets related to massive Internet of Things.
The focus of this work is on the use cases and requirements that cannot be met with EPS.
|
22.862
|
Feasibility study on new services and markets technology enablers for critical communications; Stage 1
|
TR
|
14.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.862/22862-e10.zip
|
The present document covers Critical Communications. The main areas where the 3GPP system falls short in meeting the requirements of Critical Communications is latency, reliability, and availability. These requirements can be met with an improved radio interface, optimised architecture, and dedicated core and radio resources. Other requirements having emerged in 3GPP TR 22.891 [2], such, as, high bandwidth, high connection density, low complexity, low power consumption, and massive number of devices, are often irrelevant for Critical Communications.
|
22.863
|
Feasibility study on new services and markets technology enablers for enhanced mobile broadband; Stage 1
|
TR
|
14.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.863/22863-e10.zip
|
Emerging from the FS_SMARTER work [2], the present document aims to identify and document the use cases and consolidated potential requirements, and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of enhanced mobile Broadband.
The focus of this work is on the use cases and requirements that cannot be met with EPS.
|
22.879
|
Feasibility study on Mission Critical (MC) video services over LTE
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.879/22879-e00.zip
|
The present document studies use cases and identifies potential requirements for operation of the MCVideo Service. MCVideo makes use of capabilities included in Group Communications System Enablers for LTE (GCSE_LTE), Proximity based Services (ProSe), and Isolated E-UTRAN operation for Public Safety, with additional requirements specific to the MCVideo Service. The MCVideo Service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
As far as possible, the MCVideo service will reuse applicable elements from MCPTT service.
|
22.880
|
Feasibility study on Mission Critical (MC) data communications
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.880/22880-e00.zip
|
The present document studies use cases and identifies potential requirements for operation of the MCData service. MCData makes use of capabilities included in Group Communications System Enablers for LTE (GCSE_LTE), Proximity based Services (ProSe), and Isolated E-UTRAN Operation for Public Safety (IOPS) with additional requirements specific to the MCData Service. The MCData Service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
As far as possible, the MCData service will reuse applicable elements from the MCPTT service.
|
22.885
|
Study on LTE support for Vehicle-to-Everything (V2X) services
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.885/22885-e00.zip
|
The objective of this TR is to identify use cases and associated potential requirements for LTE support of V2X services taking into account V2X Services and parameters defined in other SDOs (e.g. GSMA Connected Living, ETSI ITS (Intelligent Transportation System), US SAE) or related governmental agency (e.g. C-ITS project in Korean Ministry of Land, Infrastructure and Transport). The essential use cases for LTE V2X (V2V, V2I, and V2P) to be studied and requirements identified are as follows;
- V2V: covering LTE-based communication between vehicles.
- V2P: covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger).
- V2I: covering LTE-based communication between a vehicle and a roadside unit.
This TR includes safety and non-safety aspects.
|
22.891
|
Study on new services and markets technology enablers
|
TR
|
14.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.891/22891-e20.zip
| |
22.898
|
Study on user control dver spoofed calls
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.898/22898-e00.zip
|
The present document studies new service capabilities and enhancements to existing service capabilities needed to allow the called user to control:
- How spoofed calls are reported to the called user.
- The treatment given to the spoofed call and calling user.
- Provide the called user the ability to review the results of spoofed call detection.
- Allow the called user to provide feedback to the network of incorrect detection decisions (false positive and false negative).
New service network capabilities and enhancements to existing network capabilities needed to support network operator policies regarding treatment of spoofed calls are also covered including:
- Support for law enforcement and network operator fraud investigations into originators of spoofed calls.
- Setting default or limiting spoofed call controls the user is able to access.
The present document also studies the interaction between spoofed call control capabilities available to users using MTSI voice services.
|
22.899
|
Study on enhancements to user location reporting support
|
TR
|
14.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.899/22899-e00.zip
| |
23.702
|
Study on 3GPP PS Data Off
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.702/23702-e00.zip
|
The objective of this study is to investigate and evaluate architecture enhancements to introduce for the specification of the 3GPP PS Data Off feature so as to meet the requirement defined in TS 22.011[2].
|
23.710
|
Study on improvement of awareness of user location change
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.710/23710-e00.zip
|
The scope of the present document is to study improvements of awareness of user location change in connected mode e.g. for differentiated charging and/or QoS.
Solutions will be studied for following areas:
- Extending the existing PRA change reporting mechanism for both UE dedicated and CN predefined PRA to support multiple PRAs per PDN connection.
- Optimizing signalling load in PLMN partitioning scenario.
|
23.711
|
Enhancements of dedicated core networks selection mechanism
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.711/23711-e00.zip
|
The present document investigates and evaluates possible solutions to improve the DCN selection of DECOR feature by adding assistance from the UE.
The assistance information from the UE is intended to reduce signalling required to select a DCN associated with the UE. It shall complement the Rel-13 DECOR selection mechanism. All 3GPP RATs are supported i.e. E-UTRAN, UTRAN, GERAN and NB-IOT. The enhancement can also improve the separation between dedicated core networks by avoiding redirections between DCNs i.e. avoiding UEs accessing DCN in which it is not allowed. It is advantageous if the solution works when the UE change serving PLMN.
|
23.714
|
Study on Control Plane (CP) and User Plane (UP) separation of Evolved Packet Core (EPC) nodes
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.714/23714-e00.zip
|
The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for the separation of user plane functionality from control plane functionality in the EPC's S-GW, P-GW and TDF to further enable flexible (i.e. distributed or centralized) network deployment and operation.
Specifically, the following aspects are covered:
- Functional separation of the S-GW, P-GW and TDF into control plane and user plane functions, while not affecting the overall functionality provided by these nodes.
- The needed reference points between the separated control plane and user plane functions of the S-GW, P-GW and TDF and the corresponding procedures.
- Impacts to other EPC entities and interfaces that are essential to support the separation of S-GW, P-GW and TDF into control plane and user plane functions, and to enable the flexible placement of the separated control plane and user plane functions for supporting diverse deployment scenarios.
|
23.719
|
Feasibility study on service domain centralization
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.719/23719-e00.zip
|
The objective of this Technical Report is to study and specify potential modifications to the ICS architecture in order to enable all services to be controlled via IMS rather than via CS legacy mechanisms (single service domain), for all subscribers of a network and also for inbound roamers.
As part of Release 8, 3GPP developed the concept of IMS Centralized Services which was then further extended in Release 9. While the goal of ICS was to enable an operator to provide communication services (such that all services and service control are centralized based on IMS mechanisms) on a per-subscriber basis, it has however not seen widespread deployment, as support of both domains is still necessary.
To achieve the goal of fully centralizing services and service control in the IMS domain, network based solutions will be studied that address the key issues and architectural assumptions defined in this document. In addition, these potential solutions will be evaluated against the existing mechanisms available in 3GPP technical specifications, before deciding whether to make changes to the relevant technical specifications.
|
23.721
|
Study on sponsored data connectivity improvements
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.721/23721-e00.zip
|
The scope of the present document is to study sponsored data connectivity improvements including:
- Solutions for sponsored data connectivity to cope with the increasing configuration update capacity requirements, possible maintenance difficulties and long deployment cycle. This work covers both PCEF and TDF.
- Solutions for provisioning of the information needed to support detection while traffic is encrypted in the operator's network for sponsored data services. This work includes identification of the required information. This work covers both PCEF and TDF.
- Introduce sponsored data connectivity functionality to TDF as currently exists in case of PCEF.
Normative specifications should be developed based on the evaluations and conclusions of this study item.
|
23.730
|
Study on extended architecture support for Cellular Internet of Things (CIoT)
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.730/23730-e00.zip
|
The present document studies and evaluates the architecture enhancement to support Cellular Internet of Things (CIoT). The scope includes NB-IoT, eMTC, and EC-GSM-IoT.
The study will consider architecture enhancements/simplifications in the following areas:
- Support of authorization of use of Coverage Enhancement functionality;
- Reliable communication service between UE and SCEF;
- Inter-RAT idle mode mobility support for NB-IoT;
- Review existing multicast/broadcast services architecture to ensure suitability for NB-IoT;
- Review existing Location services architecture to ensure suitability for UEs using Control Plane CIoT EPS optimisation;
- QoS differentiation between UEs using control plane EPS CIoT optimizations; and
- CN overload protection for UE supporting control plane EPS CIoT optimizations.
|
23.746
|
Study on System Architecture Enhancements to eMBMS for Television Video Service
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.746/23746-e00.zip
|
Editor's note: This clause will describe the scope of the feasibility study.
The present document studies enhancements to the 3GPP system and UE procedures that are meant to cover essential functionality to enable new TV services by a 3GPP network. The scope of the work has three main components:
- A broadcast component where mechanisms to enable decoupling of content, MBMS service and MBMS transport, allowing the system to: offer eMBMS transport only, a shared eMBMS network between MNOs, broadcast only TV service to devices with no MNO subscription, will be studied.
- A unicast component, in which MNO subscription for TV service is required, where mechanisms for broadcast/unicast fall-back support, consumption-based switching between unicast/broadcast, and system enhancements for providing guaranteed QoS across large geographical areas will be studied.
- An MBMS user service exposure to 3rd party server, in which mechanisms in order to enable delivery of TV content based on the information provided by the 3rd party content/service providers, e.g. the expected broadcast area and time will be studied.
|
23.749
|
Study on S8 Home Routing Architecture for VoLTE
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.749/23749-e00.zip
|
GSMA has identified a new roaming model for VoLTE called "S8 Home Routed (S8HR)" whereby the PGW, PCRF and P-CSCF are located in the HPLMN also when the UE is roaming in a VPLMN. S8HR roaming architecture aims to provide IMS services to UEs roaming in VPLMN with the UE to network IMS interface (Gm) between the UE and the HPLMN only and not requiring any IMS network to network interface (NNI) between the VPLMN and HPLMN.
The present document studies and evaluates the architecture enhancements required to support S8HR for VoLTE. The architecture enhancements should also be applicable to other IMS services.
The study will cover at a minimum the following topics:
- Support of Emergency calls to meet regulatory requirement
- Impacts on SRVCC for the S8HR roaming scenarios required by GSMA.
- Coexistence of LBO and S8HR roaming architectures
- Providing VPLMN Identity to IMS entities in HPLMN
- Handling of geo-local number
|
23.750
|
Study for robust call setup for VoLTE subscriber in LTE
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.750/23750-e00.zip
|
The study is to investigate solutions to minimize call setup failure and improve user experience for VoLTE subscriber in LTE with bad coverage.
The study shall consider the scenarios where UE is both PS and CS registered or only PS registered and UE is already IMS registered initially.
The study will cover at a minimum the following scenarios:
1) LTE with bad coverage is overlaid with 2/3G CS coverage.
2) LTE with bad coverage is overlaid with WiFi access.
3) LTE with bad coverage is overlaid with both 2/3G CS coverage and WiFi access.
|
23.773
|
Study on group based enhancements in the network capability exposure functions
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.773/23773-e00.zip
|
The present document aims at identifying group-based enhancements in the 3GPP capability exposure functions.
The network capability exposure functions introduced within the MONTE and AESE work items apply on a per-UE basis. The study shall investigate whether these network capability exposure functions can benefit from being performed based on a per-group basis.
The target procedures are the Monitoring procedures (clause 5.6 in TS 23.682 [2]) and the Communication Pattern Parameters Provisioning procedure (clause 5.10 in TS 23.682 [2]).
NOTE: The Group Message Delivery using MBMS procedure is performed based on a per-group basis.
|
23.780
|
Study on Multimedia Broadcast and Multicast Service (MBMS) usage for mission critical communication services
|
TR
|
14.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.780/23780-e00.zip
|
The objective of this technical report is to study how mission critical communication services utilize MBMS. This may include study of modifications to the MCPTT architectures and/or procedures as specified in 3GPP TS 23.179 [6]. This technical report will identify any enhancements needed to support mission critical services delivered over MBMS, based on the stage 1 requirements, including 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 [5].
|
23.785
|
Study on architecture enhancements for LTE support of V2X services
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.785/23785-e00.zip
|
The objective of this Technical Report is to identify and evaluate potential architecture enhancements needed to operate LTE-based V2X (V2V, V2I, V2N, and V2P), based on vehicular services requirements defined in SA WG1 V2XLTE (TS 22.185 [3] and TS 22.278 [2]) and determine which of the solutions can proceed to normative specifications.
|
23.799
|
Study on Architecture for Next Generation System
|
TR
|
14.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.799/23799-e00.zip
|
The objective is to design a system architecture for the next generation mobile networks. The new architecture shall support at least the new RAT(s), the Evolved E-UTRA, non-3GPP accesses and minimize access dependencies.
Proposals for the new architecture can be based on an evolution of the current architecture or based on a "clean slate" approach.
The study shall consider scenarios of migration to the new architecture.
The expected work will include:
- Investigation of high-level architectural requirements.
- Definition of the terminology to be used as common language for architecture discussions.
- Definition of the high-level system architecture as the collection of required capabilities, and high level functions with their interactions between each other.
The complete or partial conclusions of this study will form the basis for the normative work and/or for any further study.
|
25.707
|
Multi-carrier enhancements for UMTS
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.707/25707-e00.zip
|
The study on multi-carrier enhancements is to investigate the potential gains obtained by enabling 10ms TTI configuration in one of the carriers or both of the carriers in the DB-DC-HSUPA and DC-HSUPA scenarios. It is also targeted to investigate the potential solutions for multi-carrier enhancements in both DB-DC-HSUPA and DC-HSUPA [2].
|
25.927
|
Solutions for energy saving within UTRA Node B
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.927/25927-e00.zip
|
The present document summarizes the study done under the SI “Solutions for energy saving within UTRA Node B” defined in [1] by listing technical concepts addressing the objectives of the study item (see below), analysing these technical concepts and selecting the best solution (which might be a combination of technical concepts).
The objective is to do an initial study to identify potential solutions to enable energy saving within UMTS Node-Bs, and do light initial evaluation of the proposed solutions, with the aim that a subset of them can be taken forward for further investigation as part of a more focused study in 3GPP.
The main objective is to save power of RBS but other savings are also to be investigated. Preference for solutions to be studied can be prioritized as follows.
a) no impact to legacy or new UEs,
b) no impact to legacy but impact to new UEs,
c) impact to both, but minimise impact to legacy.
Solutions that provide energy saving for UMTS NodeB are captured in this Technical report including the ones that do not require specification changes. - Energy saving of site support solutions and NodeB peripheral parts (e.g. rectifier, backup system, Cooling etc) are outside the scope of RAN1 studies.
“Non-backward compatible” techniques are not excluded from discussion at this stage; the impact of the “non-backward-compatibility” on legacy terminals should be assessed.
The present document provides the base for the following preparation of change requests to the corresponding RAN specifications if any solution are identified as beneficial require specification changes.
|
26.852
|
Multimedia Broadcast/Multicast Service (MBMS); Extensions and profiling
|
TR
|
14.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.852/26852-e20.zip
|
The present document identifies a set of profiles for based on the most relevant use cases for the usage of MBMS. It also studies the feasibility of using MBMS as a regular transport enabler through the definition of an MBMS URL scheme and the procedures to resolve such URL schemes. In addition, it identifies a set of APIs for controlling MBMS user service reception and retrieving resources that are delivered over MBMS. Finally, the present document also addresses the issue of defining QoE reporting for DASH over MBMS.
|
26.880
|
Study on MBMS usage and codecs for MC Video Service
|
TR
|
14.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.880/26880-e00.zip
|
The present document describes the enhancements of MBMS for MCVideo service support. Codec(s) and media handling to enable delivery of MCVideo are documented.
|
26.916
|
Media handling and Quality aspects of SRVCC
|
TR
|
14.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.916/26916-e20.zip
|
Enhanced Single Radio - Voice Call Continuity (eSRVCC) is an existing standard ([3], [4]) specifying the handover of a Voice or Video call from LTE access to CS-radio access, either to GERAN (2G) or to UTRAN (3G) or other CS networks. The present document considers only enhanced SRVCC for voice calls between 3GPP accesses.
This study assumes that the Codecs defined in TS 26.114 are used on the LTE access and the Codecs defined in 3GPP TS 26.103 [7] on the CS accesses. Since Rel-13, the specifications for CS networks include the Codec Type UMTS_EVS with several Configurations, called UMTS_EVS (Set 0) to UMTS_EVS (Set 3).
In the IMS Core Network, the voice call is typically anchored in the ATCF/ATGW (Access Transfer Control Function/ Access Transfer Gate Way).
The eSRVCC procedure, as specified, may cause additional transcoding between the target radio leg and the ATGW, even though in theory it would be possible to avoid it. As a result, the eSRVCC procedures may add one or more unnecessary transcoding point(s) for the call and thereby degrade the quality of the ongoing call unnecessarily.
The main objectives of this study are to analyse example call scenarios and find potential solutions to minimize the number of transcoding cases. Another objective is to optimize the interworking and the transition between EVS and AMR-WB during eSRVCC. The study should also show the reasons and potential solutions for too long speech path interruptions during eSRVCC.
The present Technical Report has the following detailed objectives:
- Identify relevant eSRVCC scenarios, especially with Codec Mode Control;
from AMR-WB and/or EVS in VoLTE to AMR-WB and/or EVS in CS;
but include also other important Codecs, such as AMR and G.722.
- Analyse Speech Quality Aspects and Media Handling Aspects, based on these scenarios.
- Analyse Codec Mode Control before, during and after eSRVCC;
recently SA4 has clarified some essential details on Rate Control for AMR and AMR-WB;
Rate Control and Audio Bandwidth Control for EVS are still under discussion to some extent.
- Analyse the existing SDP Offer - Answer protocol between Target MSC and Anchor-ATCF during eSRVCC,
as specified in 3GPP TS 23.216 [3], Stage 2;
This analysis will include the whole eSRVCC procedure for at least one essential scenario
(e.g. eSRVCC to GERAN) and will identify the potential reasons for transcoding and too long speech path interruptions.
- Clarify the existing Codec Compatibility aspects for eSRVCC;
especially the interworking between CS and IMS for AMR, AMR-WB and EVS needs to be documented.
- Propose enhancements for media and quality aspects of eSRVCC with the aims:
a) to avoid transcoding cases as much as possible;
b) to minimize the speech path interruption time during eSRVCC;
- Support the SA2 SETA work by SA4 expertise in speech quality and media handling.
|
29.844
|
Study on Control and User Plane Separation of EPC Nodes
|
TR
|
14.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.844/29844-e00.zip
|
The present document analyses the aspects with regard to the new interface between Control Plane and User Plane due to the separation of the following EPC nodes: S-GW, P-GW and TDF.
Specifically, the following aspects are to be analysed:
- Restoration procedure enhancements for the separated nodes;
- Signalling with regards to Load control;
- Signalling with regards to Overload control;
- Path management and path failure handling.
|
31.901
|
Review of dedicated 3GPP UICC features (Red_UCe)
|
TR
|
14.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.901/31901-e00.zip
|
The present document presents a review of the USIM, ISIM and the related Toolkit aspects (respectively found in TS 31.102 [3], TS 31.103 [4] and TS 31.111 [5]) features and their mandatory/optional support in the light of actual use or demand in the field is to be conducted. The technical report documents the justification for the support of features identified as not being implemented or required (e.g. from SA1 requirements). When a common understanding is reached about a potential need for a modification of the required support of a feature, it will be listed for further consideration by CT6. Should any normative work be derived from the content of the study, it will be carried out as part of a separate work item.
|
32.817
|
Study on management of measurement collection in network sharing context
|
TR
|
14.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.817/32817-e10.zip
|
The study is to investigate:
- Solutions for how to manage measurement collection in network sharing context over Itf-N.
- Solutions for how to indicate high reliability to different E-UTRAN measurements.
- Whether the PM file format would need to be changed and possible solutions.
The solution is intended to be valid for data volume measurements, but a more generically applicable solution should be considered, if feasible. The solution can be valid also for non-shared networks.
|
32.838
|
Telecommunication management; Gap analysis between 3GPP SA5 specifications and NGMN Top Operational Efficiency (OPE) recommendations
|
TR
|
14.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.838/32838-e10.zip
|
The present document provides a gap analysis between NGMN Top OPE Recommendations [2] and OAM capabilities offered by 3GPP SA5 Integration Reference Points (IRPs).
Based on this gap analysis, it provides a support status of SA5 specifications against NGMN Top OPE Recommendations. For each Top OPE Recommendation, the SA5 solution is described when it exists. Otherwise, some action may be considered to address the Top OPE recommendation.
Based on that information, a support status is produced which can take the following values:
- Supported,
- Partially Supported,
- Not Supported,
- Not Applicable.
|
32.850
|
Study on determination of completeness of charging information in IMS
|
TR
|
14.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.850/32850-e00.zip
|
The objective of this study item is to identify and document methods to guarantee that all the relevant charging data for an IMS session has been received in order to charge the IMS session correctly.
Within the study scenarios could be covered where a concatenation of applications leads to an correlation of charging relevant information.
In addition a method to identify all network elements generating CDR for offline charging within an IMS call in order to serve for an effective and accurate IMS Charging correlation is in focus of this study.
The following scenarios are be covered this study:
• IMS calls where the service invocation is done in the originating and/or terminating home network. Scenarios to be considered should cover different network scenarios like roaming, transit, PSTN interworking, intra home network or home-a to home-b network. IMS Calls where a concatenation of applications appear. The invoked applications can be provided by AS from different networks.
• IMS Calls where an Application Server hosts several applications invoked during one call.
- IMS Calls where call leg manipulation apply and more than one application is involved.
• IMS Calls where only several IMS network elements are necessary to generate charging information based on operator's configuration.
• IMS Other scenarios where a correlation of charging relevant information created by application servers is needed.
The study will identify recommended enhancements to the charging architecture, message and CDR content, and internode signalling.
It will analyse operator requirements in consideration of the roaming scenarios and the existing charging specifications.
The conclusions are presented in a further section with assumptions made and proposed further proceedings on that issues.
|
32.855
|
Study on OAM support for Licensed Shared Access (LSA)
|
TR
|
14.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.855/32855-e00.zip
|
The present document studies the architecture, the interfaces and solutions with regards to Licensed Shared Access, LSA ETSI TS 103 154 [5] relevant to a 3GPP mobile network operator. The study includes:
- Study how the solution and architecture defined in ETSI TS 103 235 [3] may provide a global solution.
- Study the impact on the 3GPP management reference model defined in 3GPP TS 32.101 [2].
- Analyse the LSA functionalities and the information flow defined in ETSI TS 103 235 [3] towards a 3GPP mobile network operator and any impact on Itf-N.
- Study how to support the static and semi-static spectrum sharing scenarios and reference use case defined in ETSI TR 103 113 [4].
Interfaces and functionality specified for LSA that are not involving the 3GPP mobile network operator are out of scope for this study.
|
32.860
|
Telecommunication management; Study on enhancements of Operations, Administration and Maintenance (OAM) aspects of distributed Self-Organizing Networks (SON) functions
|
TR
|
14.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.860/32860-e00.zip
|
The present document aims the following:
- Identify whether Distributed SON (D-SON) Mobility Load Balancing (MLB) as currently specified in 3GPP can be improved;
- In case potential areas of improvement are identified, propose possible solutions.
|
32.862
|
Study on Key Quality Indicators (KQIs) for service experience
|
TR
|
14.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.862/32862-e00.zip
|
The present document will address:
1) Service KQI scenarios
2) Service KQIs corresponding to the identified scenarios
KQIs will be described for the below services:
- Bidirectional voice
- Unidirectional voice streaming
- Unidirectional video streaming
- Short Messaging
- Multimedia Messaging
- Web browsing
- File transfer
- E-mail
The present document will consider already defined metrics and requirements from:
- NGMN NGCOR phase 2 requirements
- ETSI TS 102.250
- 3GPP TR 26.944
- NGMN P-SERQU
- QuEST Forum TL9000
|
33.827
|
Study on providing for Lawful Interception (LI) in the S8 Home Routeing (S8HR) architecture for Voice over LTE (VoLTE)
|
TR
|
14.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.827/33827-e00.zip
|
The present document studies and identifies the changes to the LI architecture, function and protocols for inbound roamers in the VPLMN when S8HR is employed which is equivalent to the LI service level for Local Breakout (LBO) in the VPLMN for VoLTE services. Covered by the present document includes:
- Potential enhancements to the LI service architecture to accommodate the S8HR roaming architecture in the VPLMN to meet all the current LI regulatory requirements applicable to voice and other IMS service roaming are considered and compared.
- Considerations on maximizing re-use of existing 3GPP defined capabilities such as PCC is considered.
- Exploration of the changes that may be needed to TS 33.107 [3] and TS 33.108 [4].
Finally, the present document provides recommendations for proceeding with implementing the selected approach.
This study item takes into account GSMA related activities.
|
33.849
|
Study on subscriber privacy impact in 3GPP
|
TR
|
14.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.849/33849-e00.zip
|
The present document studies the subscriber privacy impact in 3GPP. In particular, the goals of the present document are:
- Identify and understand privacy related key issues impacting 3GPP networks.
- Identify and potentially harmonize privacy requirements, e.g. MDT/SON.
- Identify existing/ongoing work relevant to 3GPP privacy issues in external standard bodies, for potential reuse in 3GPP, e.g. IETF RFC 6973 [2].
- Identify privacy risk mitigation approaches and establish privacy handling guidelines/principle and/or best practices for 3GPP for future specifications.
It is not an objective of the study to examine all existing 3GPP specifications in retrospect with respect to privacy.
NOTE: The result of this study is captured in Annex F.
|
33.863
|
Study on battery efficient security for very low throughput Machine Type Communication (MTC) devices
|
TR
|
14.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.863/33863-e20.zip
|
The present document's objectives are to:
a) Investigate whether battery efficient 'device to enterprise' mechanisms to provide sufficient security exist.
b) Investigate potential enhancements to 3GPP's security architecture(s) that enable the Home Operator to be able to offer well guaranteed security to enterprises e.g. to provide security between the UE and a node in the home operator domain.
c) Both S1 and Gb based architectures should be considered when undertaking b, above.
The impacts of relevant authentication and key agreement procedures are also presented.
The following should be taken into account for the study:
- The potential solutions should aim at minimising the energy consumption of devices to help meet the objective of a ten year battery life in the extended coverage situation and take into consideration the very low data rate capability of the radio interface when using the Energy Consumption Evaluation Methodology described in TR 45.820.
|
33.885
|
Study on security aspects for LTE support of Vehicle-to-Everything (V2X) services
|
TR
|
14.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.885/33885-e10.zip
|
The present document contains a study of the security aspects of V2X services and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.185 [2]. Potential stage 2 solutions for V2X Services are being studied in TR 23.785[3].
|
36.714-00-00
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for x Down Link (DL) / y Up Link (UL) including contiguous and non-contiguous spectrum
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-00-00/36714-00-00-e00.zip
|
The present document is a technical report for Intra-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address Intra-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 intra-band carrier aggregation combinations
CA combination
REL independent from
CA_2DL_1A-1A_1UL_BCS0
Rel-11
CA_2DL_1C_1UL_BCS1
Rel-11
CA_2DL_3B_1UL_BCS0
Rel-10
CA_2DL_3A-3A_1UL_BCS2
Rel-11
CA_2DL_3A-3A_1UL_BCS3
Rel-11
CA_2DL_5B_2UL_BCS0
Rel-11
CA_2DL_5B_1UL_BCS1
Rel-11
CA_2DL_5A_5A_1UL_BCS1
Rel-11
CA_2DL_7A-7A_2UL_7A-7A_BCS1
Rel-11
CA_2DL_7A-7A_1UL_BCS2
Rel-11
CA_2DL_7A-7A_1UL_BCS3
Rel-11
CA_2DL_7A-7A_2UL_7A-7A_BCS3
Rel-11
CA_2DL_12A-12A_1UL_BCS0
Rel-11
CA_3DL_40D_1UL_BCS1
Rel-11
CA_3DL_40D_3UL_BCS0
Rel-12
CA_4DL_40E_1UL_BCS0
Rel-11
CA_2DL_40A-40A_1UL_BCS1
Rel-11
CA_3DL_40A-40C_1UL_BCS0
Rel-11
CA_4DL_40C-40C_1UL_BCS0
Rel-11
CA_3DL_41D_3UL_BCS0
Rel-12
CA_3DL_41A-41C_2UL_41C_BCS0
Rel-11
CA_4DL_41E_2UL_41C_BCS0
Rel-11
CA_5DL_41C-41D_2UL_41C_BCS0
Rel-12
CA_2DL_42C_2UL_BCS1
Rel-11
CA_3DL_42D_2UL_BCS1
Rel-11
CA_5DL_42F_1UL_BCS0
Rel-11
CA_5DL_42F_2UL_BCS0
Rel-11
CA_2DL_43C_1UL_BCS0
Rel-11
CA_2DL_46C_0UL_BCS0
Rel-13
CA_2DL_46C_0UL_BCS1
Rel-13
CA_3DL_46D_0UL_BCS0
Rel-13
CA_3DL_46D_0UL_BCS1
Rel-13
CA_4DL_46E_0UL_BCS0
Rel-13
CA_4DL_46E_0UL_BCS1
Rel-13
CA_2DL_46A-46A_0UL_BCS0
Rel-13
CA_3DL_46A-46C_0UL_BCS0
Rel-13
CA_4DL_46A-46D_0UL_BCS0
Rel-13
CA_2DL_48A-48A_1UL_BCS0
Rel-11
CA_2DL_48C_1UL_BCS0
Rel-11
CA_3DL_48A-48C_1UL_BCS0
Rel-11
CA_3DL_48D_1UL_BCS0
Rel-11
CA_4DL_48A-48D_1UL_BCS0
Rel-11
CA_5DL_48A-48E_1UL_BCS0
Rel-11
CA_4DL_48C-48C_1UL_BCS0
Rel-11
CA_4DL_48E_1UL_BCS0
Rel-11
CA_5DL_48C-48D_1UL_BCS0
Rel-11
CA_5DL_48F_1UL_BCS0
Rel-11
CA_3DL_66D_1UL_BCS0
Rel-10
CA_3DL_66A-66B_1UL_BCS0
Rel-11
CA_3DL_66A-66C_1UL_BCS0
Rel-11
CA_2DL_66A-66A_2UL_66A-66A_BCS0
Rel-13
CA_2DL_66B_2UL_66B_BCS0
Rel-13
CA_2DL_66C_2UL_66C_BCS0
Rel-13
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-00-02
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for x Down Link (DL) / y Up Link (UL) with x=3, 4, 5
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-00-02/36714-00-02-e10.zip
|
The present document is a technical report for LTE Advanced 2ULs and xDLs Carrier Aggregation with x=3,4,5 under Rel-14 time frame. The purpose is to gather the relevant background information and studies in order to address 2ULs and xDLs Carrier Aggregation requirements.
This TR covers relevant background information and studies core & performance requirements for the Rel-14 band combinations in Table 1-1, 1-10 and 1-11.
Table 1-1: 3DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3C
CA_1A-3A or
CA_3C
1
Yes
Yes
Yes
Yes
60
0
3
See CA_3C BCS0 in Table 1-6
CA_1A-3A-7A
CA_1A-3A or CA_1A-7A or CA_3A-7A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
CA_1A-3A-21A
CA_1A-3A or
CA_1A-21A or
CA_3A-21A
1
Yes
Yes
Yes
Yes
55
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_1A-3A-28A
CA_1A-3A, CA_1A-28A, CA_3A-28A
1
Yes
Yes
Yes
Yes
50
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
CA_1A-3A-40A
CA_1A-3A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-3A-42A
CA_1A-3A or
CA_1A-42A or
CA_3A-42A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-5A-40A
CA_1A-5A
1
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
40
Yes
Yes
Yes
CA_1A-5A-46A
CA_1A-5A
1
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
46
Yes
CA_1A-7A-7A
CA_1A-7A
1
Yes
Yes
Yes
Yes
60
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-7A-8A
CA_1A-7A or CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
7
Yes
Yes
Yes
8
Yes
Yes
CA_1A-7A-46A
CA_1A-7A
1
Yes
Yes
Yes
Yes
60
0
7
Yes
Yes
Yes
46
Yes
CA_1A-8A-40A
CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-19A-42A
CA_1A-19A or
CA_1A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
55
0
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-21A-28A
CA_1A-21A, CA_1A-28A, CA_21A-28A
1
Yes
Yes
Yes
Yes
45
0
21
Yes
Yes
Yes
28
Yes
Yes
CA_1A-21A-42A
CA_1A-21A or
CA_1A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
55
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-28A-42A
CA_1A-28A, CA_1A-42A, CA_28A-42A
1
Yes
Yes
Yes
Yes
50
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-42C
CA_1A-42A
1
Yes
Yes
Yes
Yes
60
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_2A-4A-5A
CA_2A-4A
2
Yes
Yes
Yes
Yes
50
0
4
Yes
Yes
Yes
Yes
5
Yes
Yes
CA_2A-4A-7A
.CA_2A-4A
2
Yes
Yes
Yes
Yes
60
0
4
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
Yes
CA_2A-4A-29A
CA_2A-4A
2
Yes
Yes
Yes
Yes
50
0
4
Yes
Yes
Yes
Yes
29
Yes
Yes
CA_2A-12A-30A
CA_2A-12A
2
Yes
Yes
Yes
Yes
40
0
12
Yes
Yes
30
Yes
Yes
CA_2A-12B
CA_2A-12A
2
Yes
Yes
Yes
Yes
35
0
CA_12B
See CA_12B BCS0 in Table 1-2
CA_3A-3A-8A
CA_3A-8A
CA_3A-3A
See CA_3A-3A BCS0 in Table 1-5
50
0
8
Yes
Yes
CA_3A-3A
See CA_3A-3A BCS1 in Table 1-5
40
1
8
Yes
Yes
CA_3A-5A-7A
CA_3A-5A or
CA_3A-7A or
CA_5A-7A
3
Yes
Yes
Yes
50
0
5
Yes
Yes
7
Yes
Yes
Yes
CA_3A-5A-40A
CA_3A-5A
3
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
40
Yes
Yes
Yes
CA_3A-7A-7A
CA_3A-7A
3
Yes
Yes
Yes
Yes
60
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_3A-7A-8A
CA_3A-7A or CA_3A-8A or CA_7A-8A
3
Yes
Yes
Yes
40
0
7
Yes
Yes
8
Yes
Yes
3
Yes
Yes
Yes
Yes
50
1
7
Yes
Yes
Yes
8
Yes
Yes
CA_3C-8A
CA_3A-8A or
CA-3C
3
See CA_3C BCS0 in Table 1-6
50
0
8
Yes
Yes
Yes
CA_3A-8A-40A
CA_3A-8A
3
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_3A-19A-21A
CA_3A-19A or
CA_3A-21A or
CA_19A-21A
3
Yes
Yes
Yes
Yes
50
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_3A-19A-42A
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
3
Yes
Yes
Yes
Yes
55
0
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-21A-28A
CA_3A-21A, CA_3A-28A, CA_21A-28A
3
Yes
Yes
Yes
Yes
45
0
21
Yes
Yes
Yes
28
Yes
Yes
CA_3A-21A-42A
CA_3A-21A or
CA_3A-42A or
CA_21A-42A
3
Yes
Yes
Yes
Yes
55
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-28A-42A
CA_3A-28A, CA_3A-42A, CA_28A-42A
3
Yes
Yes
Yes
Yes
50
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-41A-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
60
0
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_3A-42C
CA_3A-42A, CA_42C
3
Yes
Yes
Yes
Yes
60
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_4A-12A-30A
CA_4A-12A
4
Yes
Yes
Yes
Yes
40
0
12
Yes
Yes
30
Yes
Yes
CA_4A-12B
CA_4A-12A
4
Yes
Yes
Yes
Yes
35
0
CA_12B
See CA_12B BCS0 in Table 1-2
CA_5A-7A-7A
CA_5A-7A
5
Yes
Yes
50
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_5A-7A-46A
CA_5A-7A
5
Yes
Yes
50
0
7
Yes
Yes
Yes
46
Yes
CA_7C-28A
CA_7C or CA_7A-28A
7
See CA_7C BCS2 in Table 1-3
60
0
28
Yes
Yes
Yes
CA_19A-21A-42A
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
19
Yes
Yes
Yes
50
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_19A-42C
CA_19A-42A
19
Yes
Yes
Yes
55
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_21A-42C
CA_21A-42A
21
Yes
Yes
Yes
55
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_21A-28A-42A
CA_21A-28A, CA_21A-42A, CA_28A-42A
21
Yes
Yes
Yes
45
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_28A-41A-42A
CA_41A-42A
28
Yes
Yes
50
0
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_28A-42C
CA_28A-42A, CA_42C
28
Yes
Yes
50
0
42
See CA_42C BCS0 in Table 1-4
CA_41A-42C
CA_41A-42A or CA_42C
41
Yes
Yes
Yes
60
0
42
See CA_42C BCS1 in Table 1-4
CA_41C-42A
CA_41A-42A or CA_41C
41
See CA_41C BCS0 in Table 1-7
60
0
42
Yes
Yes
Yes
CA_xA-yA-zA
CA_xA-yA or
CA_yA-zA or
CA_xA-zA
X
Up to 60
0
Y
Z
Table 1-2: E-UTRA CA_12B configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_12B
5
5, 10
15
0
Table 1-3: E-UTRA CA_7C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Uplink CA configurations
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_7C
CA_7C
15
15
40
0
20
20
10
20
40
1
15
15, 20
20
10, 15, 20
15
10, 15
40
2
20
15, 20
Table 1-4: E-UTRA CA_42C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_42C
5, 10, 15, 20
20
40
0
20
5, 10, 15
10, 15, 20
20
40
1
20
10, 15
Table 1-5: E-UTRA CA_3A-3A configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRACA configuration
Uplink CA configurations (NOTE 1)
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
CA_3A-3A
-
5, 10, 15, 20
5, 10, 15, 20
40
0
5, 10
5, 10, 15, 20
30
1
Table 1-6: E-UTRA CA_3C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_3C
5, 10, 15
20
40
0
20
5, 10, 15, 20
Table 1-7: E-UTRA CA_41C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_41C
10
20
40
0
15
15, 20
20
10, 15, 20
Table 1-8: E-UTRA CA_46C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_46C
20
20
40
0
Table 1-9: E-UTRA CA_7A-7A configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRACA configuration
Uplink CA configurations (NOTE 1)
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
CA_7A-7A
-
5
15
40
0
10
10, 15
15
15, 20
20
20
5, 10, 15, 20
5, 10, 15, 20
40
1
5, 10, 15, 20
5, 10
30
2
10, 15, 20
10, 15, 20
40
3
Table 1-10: 4DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3A-5A-7A
CA_1A-3A or
CA_1A-5A or
CA_1A-7A or
CA_3A-5A or
CA_3A-7A or
CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
5
Yes
Yes
7
Yes
Yes
Yes
CA_1A-3A-7A-7A
CA_1A-3A or CA_1A-7A or CA_3A-7A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-3A-8A-40A
CA_1A-3A,
CA_1A-8A,
CA_3A-8A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-3A-5A-40A
CA_1A-3A,
CA_1A-5A,
CA_3A-5A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
5
Yes
Yes
40
Yes
Yes
Yes
CA_1A-3A-7A-8A
CA_1A-3A,
CA_1A-7A,
CA_1A-8A, CA_3A-7A, CA_3A-8A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
8
Yes
Yes
CA_1A-3C-8A
CA_1A-3A or
CA_1A-8A or
CA_3A-8A or
CA_3C
1
Yes
Yes
Yes
Yes
70
0
3
See CA_3C BCS0 in Table 1-6
8
Yes
Yes
Yes
CA_1A-3A-19A-21A
CA_1A-3A,
CA_1A-19A,
CA_1A-21A,
CA_3A-19A,
CA_3A-21A,
CA_19A-21A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_1A-3A-19A-42A
CA_1A-3A or
CA_1A-19A or
CA_1A-42A or
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
75
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-21A-28A
CA_1A-3A,
CA_1A-21A,
CA_1A-28A,
CA_3A-21A,
CA_3A-28A,
CA_21A-28A
1
Yes
Yes
Yes
Yes
65
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
28
Yes
Yes
CA_1A-3A-21A-42A
CA_1A-3A,
CA_1A-21A,
CA_1A-42A,
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
1
Yes
Yes
Yes
Yes
75
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-28A-42A
CA_1A-3A,
CA_1A-28A,
CA_1A-42A,
CA_3A-28A,
CA_3A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-42C
CA_1A-3A or
CA_1A-42A or
CA_3A-42A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-5A-7A-7A
CA_1A-5A or CA_1A-7A or CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-5A-7A-46A
CA_1A-5A or
CA_1A-7A or
CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
7
Yes
Yes
Yes
46
Yes
CA_1A-5A-46C
CA_1A-5A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_1A-7A-46C
CA_1A-7A
1
Yes
Yes
Yes
Yes
80
0
7
Yes
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_1A-19A-21A-42A
CA_1A-19A or
CA_1A-21A or
CA_1A-42A or
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
70
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-19A-42C
CA_1A-19A or
CA_1A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
75
0
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-21A-28A-42A
CA_1A-21A,
CA_1A-28A,
CA_1A-42A,
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
65
0
21
Yes
Yes
Yes
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-21A-42C
CA_1A-21A or
CA_1A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
75
0
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-28A-42C
CA_1A-28A,
CA_1A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_2A-4A-5A-29A
CA_2A-4A
2
Yes
Yes
Yes
Yes
60
0
4
Yes
Yes
Yes
Yes
5
Yes
Yes
29
Yes
Yes
CA_2A-4A-7A-7A
CA_2A-4A
2
Yes
Yes
Yes
Yes
80
0
4
Yes
Yes
Yes
Yes
7
See the CA_7A-7A BCS1 in Table 1-9
CA_3A-5A-7A-7A
CA_3A-5A or CA_3A-7A or CA_5A-7A
3
Yes
Yes
Yes
70
0
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_3C-7C
CA_3A-7A
3
See CA_3C Bandwidth Combination Set 0 in Table 1-6
80
0
7
See CA_7C Bandwidth Combination Set 2 in Table 1-3
3
See CA_3C Bandwidth Combination Set 0 in Table 1-6
80
1
7
See CA_7C Bandwidth Combination Set 1 in Table 1-3
CA_3A-7C-28A
CA_3A-7A,
CA_7C,
CA_7A-28A
3
Yes
Yes
Yes
80
0
7
See CA_7C Bandwidth Combination Set 2 in Table 1-3
28
Yes
Yes
Yes
CA_3A-19A-42C
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
3
Yes
Yes
Yes
Yes
75
0
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_3A-21A-42C
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
3
Yes
Yes
Yes
Yes
75
0
21
Yes
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_3A-28A-41A-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_3A-28A-42C
CA_3A-28A,
CA_3A-42A,
CA_28A-42A,
CA_42C
3
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_3A-41A-42C
CA_42C, CA_41A-42A
3
Yes
Yes
Yes
Yes
80
0
41
Yes
Yes
Yes
42
See CA_42C Bandwidth combination set 0 in Table 1-4
CA_3A-41C-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
80
0
41
See CA_41C Bandwidth combination set 0 in Table 1-7
42
Yes
Yes
Yes
CA_5A-7A-46C
CA_5A-7A
5
Yes
Yes
70
0
7
Yes
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_19A-21A-42C
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
19
Yes
Yes
Yes
70
0
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_21A-28A-42C
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
21
Yes
Yes
Yes
65
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_28A-41A-42C
CA_42C, CA_41A-42A
28
Yes
Yes
70
0
41
Yes
Yes
Yes
42
See CA_42C Bandwidth combination set 0 in Table 1-4
CA_28A-41C-42A
CA_41A-42A
28
Yes
Yes
70
0
41
See CA_41C Bandwidth combination set 0 in Table 1-7
42
Yes
Yes
Yes
CA_41C-42C
CA_41A-42A or CA_42C or CA_41C
41
See CA_41C BCS0 in Table 1-7
80
0
42
See CA_42C BCS1 in Table 1-4
CA_wA-xA-yA-zA
CA_wA-xA,
CA_wA-yA,
CA_wA-zA,
CA_xA-yA,
CA_xA-zA,
CA_yA-zA
W
Up to 80
X
Y
Z
Table 1-11: 5DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3A-5A-7A-7A
CA_1A-3A or CA_1A-5A or CA_1A-7A or CA_3A-5A or CA_3A-7A or CA_5A-7A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-3A-19A-42C
CA_1A-3A or
CA_1A-19A or
CA_1A-42A or
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
95
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-3A-21A-42C
CA_1A-3A,
CA_1A-21A,
CA_1A-42A,
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
1
Yes
Yes
Yes
Yes
95
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_1A-3A-28A-42C
CA_1A-3A,
CA_1A-28A,
CA_1A-42A,
CA_3A-28A,
CA_3A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_1A-19A-21A-42C
CA_1A-19A or
CA_1A-21A or
CA_1A-42A or
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
90
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-21A-28A-42C
CA_1A-21A,
CA_1A-28A,
CA_1A-42A,
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
85
0
21
Yes
Yes
Yes
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_vA-wA-xA-yA-zA
CA_vA-wA or
CA_vA-xA or
CA_vA-yA or
CA_vA-zA or
CA_wA-xA or
CA_wA-yA or
CA_wA-zA or
CA_xA-yA or
CA_xA-zA or
CA_yA-zA
V
Up to 100
0
W
X
Y
Z
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-02-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-02-01/36714-02-01-e00.zip
|
The present document is a technical report for 2DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 2DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 2DL/1UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_1A-3A
10
CA_1A-32A
10
CA_1A-38A
12
CA_1A-41A
12
CA_1A-46A
13
CA_2A-48A
14
CA_2A-66A
10
CA_3A-11A
10
CA_3A-21A
10
CA_3A-28A
10
CA_3A-32A
10
CA_3A-40A
12
CA_3A-41A
12
CA_3A-46A
13
CA_3A-5A
10
CA_3A-69A
10
CA_5A-28A
10
CA_5A-41A
12
CA_5A-46A
13
CA_5A-46A
13
CA_5A-48A
14
CA_5A-66A
10
CA_7A-26A
10
CA_7A-32A
10
CA_7A-46A
13
CA_7A-66A
10
CA_7A-8A
10
CA_8A-28A
10
CA_8A-39A
12
CA_8A-41A
12
CA_8A-46A
13
CA_8A-46A
13
CA_11A-28A
10
CA_11A-41A
12
CA_11A-42A
12
CA_11A-46A
13
CA_12A-66A
10
CA_13A-46A
13
CA_13A-48A
14
CA_13A-66A
10
CA_19A-46A
13
CA_20A-32A
10
CA_20A-28A
10
CA_21A-28A
10
CA_21A-46A
13
CA_26A-46A
13
CA_28A-41A
12
CA_28A-46A
13
CA_29A-66A
10
CA_29A-70A
10
CA_30A-66A
10
CA_39A-40A
10
CA_39A-42A
10
CA_39A-46A
13
CA_40A-41A
10
CA_40A-42A
10
CA_40A-46A
13
CA_40A-46A
13
CA_41A-46A
13
CA_46A-66A
13
CA_46A-70A
13
CA_48A-66A
14
CA_66A-70A
10
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
Feasibility study on LTE Advanced Carrier Aggregation for Band 3 and Band 39 [FS_LTE_CA_B3_B39] input is also in this TR in chapter 7.
|
36.714-02-02
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 2 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-02-02/36714-02-02-e00.zip
|
The present document is a technical report for 2DL/2UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 2DL/2UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 2DL/2UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_3A-41A
Rel-12
CA_8A-41A
Rel-12
CA_3A-42A
Rel-12
CA_19A-42A
Rel-12
CA_21A-42A
Rel-12
CA_2A-7A
Rel-11
CA_7A-8A
Rel-11
CA_8A-39A
Rel-12
CA_41A-42A
Rel-12
CA_3A-21A
Rel-11
CA_28A-42A
Rel-12
CA_3A-28A
Rel-11
CA_21A-28A
Rel-11
CA_5A-66A
Rel-11
CA_2A-66A
Rel-11
CA_12A-30A
Rel-11
CA_2A-30A
Rel-11
CA_5A-30A
Rel-11
CA_2A-66A
Rel-11
CA_2A-66A
Rel-11
CA_12A-66A
Rel-11
CA_30A-66A
Rel-11
CA_3A-40A
Rel-12
CA_5A-40A
Rel-12
CA_1A-46A
Rel-14
CA_41A-46A
Rel-14
CA_42A-46A
Rel-14
CA_2A-46A
Rel-14
CA_3A-46A
Rel-14
CA_7A-46A
Rel-14
CA_46A-66A
Rel-14
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-03-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 3 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-03-01/36714-03-01-e00.zip
|
The present document is a technical report for 3DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 3DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 3DL/1UL inter-band carrier aggregation combinations
CA combination
BCS
REL independent from
CA_1A-1A-3A
0
Rel-11
CA_1A-3A-3A
0
Rel-11
CA_1A-1A-5A
0
Rel-11
CA_1A-1A-28A
0
Rel-11
CA_1C-3A
0
Rel-10
CA_1A-7A-7A
0
Rel-11
CA_1A-7C
1
Rel-10
CA_1A-40C
0
Rel-12
CA_1A-46C
0, 1
Rel-13
CA_2A-5B
0
Rel-10
CA_2A-7A-7A
0
Rel-11
CA_2A-7C
0
Rel-10
CA_2A-12A-12A
0
Rel-11
CA_2A-2A-30A
0
Rel-11
CA_2A-46C
0
Rel-13
CA_2A-48C
0
Rel-10
CA_2A-48A-48A
0
Rel-11
CA_2A-46A-46A
0
Rel-13
CA_2A-66B
0
Rel-10
CA_2A-66C
0
Rel-10
CA_2A-2A-66A
0
Rel-11
CA_2A-66A-66A
0
Rel-11
CA_3A-3A-7A
0, 1
Rel-11
CA_3A-7A-7A
0, 1
Rel-11
CA_3C-8A
0
Rel-10
CA_3C-20A
0
Rel-10
CA_3A-3A-20A
0
Rel-11
CA_3A-40A-40A
0
Rel-12
CA_3C-40A
0
Rel-12
CA_3A-3A-41A
0
Rel-11
CA_3C-41A
0
Rel-12
CA_3A-46C
0, 1
Rel-13
CA_4A-5B
0
Rel-10
CA_4A-7A-7A
0
Rel-11
CA_4A-7C
0
Rel-10
CA_4A-12A-12A
0
Rel-11
CA_4A-46C
0
Rel-13
CA_4A-46A-46A
0
Rel-13
CA_5A-7C
0
Rel-10
CA_5A-7A-7A
0
Rel-11
CA_5A-12A-12A
0
Rel-11
CA_5B-30A
0
Rel-10
CA_5A-5A-40A
0
Rel-11
CA_5A-40A-40A
0
Rel-12
CA_5A-46C
0, 1
Rel-13
CA_5A-66B
0
Rel-10
CA_5A-66C
0
Rel-10
CA_5B-66A
0
Rel-10
CA_5A-5A-66A
0
Rel-11
CA_5A-66A-66A
0
Rel-11
CA_7A-7A-8A
0, 1
Rel-11
CA_7A-7A-26A
0
Rel-11
CA_7A-46C
0
Rel-13
CA_7C-46A
0
Rel-10
CA_8A-39C
0
Rel-12
CA_8B-39A
0
Rel-12
CA_8B-41A
0
Rel-12
CA_8A-46C
0
Rel-13
CA_8B-46A
0
Rel-13
CA_11A-41C
0
Rel-12
CA_11A-42C
0
Rel-12
CA_11A-46C
0
Rel-13
CA_12A-66C
0
Rel-10
CA_12A-66A-66A
0
Rel-11
CA_12B-66A
0
Rel-10
CA_13A-46C
0
Rel-13
CA_13A-66B
0
Rel-10
CA_13A-66C
0
Rel-10
CA_13A-66A-66A
0
Rel-11
CA_19A-46C
0
Rel-13
CA_21A-46C
0
Rel-13
CA_28A-46C
0
Rel-13
CA_29A-46A-46A
0
Rel-13
CA_29A-66C
0
Rel-13
CA_29A-66A-66A
0
Rel-11
CA_30A-66A-66A
0
Rel-11
CA_39A-40C
0
Rel-10
CA_39C-40A
0
Rel-10
CA_39A-42C
0
Rel-10
CA_39C-42A
0
Rel-10
CA_39A-46C
0
Rel-13
CA_39C-46A
0
Rel-13
CA_40A-42C
0
Rel-12
CA_40C-42A
0
Rel-12
CA_40A-46C
0,1
Rel-13
CA_40C-46A
0
Rel-13
CA_41C-46A
0
Rel-13
CA_41A-46C
0
Rel-13
CA_46A-66C
0
Rel-13
CA_46C-66A
0
Rel-13
CA_46A-46A-66A
0
Rel-13
CA_46A-66A-66A
0
Rel-13
CA_48A-48A-66A
0
Rel-11
CA_48C-66A
0
Rel-10
CA_1A-3A-11A
0
Rel-10
CA_1A-3A-21A
0
Rel-10
CA_1A-3A-26A
1
Rel-10
CA_1A-3A-38A
0
Rel-12
CA_1A-3A-41A3
0
Rel-12
CA_1A-5A-41A
0
Rel-12
CA_1A-5A-46A
0
Rel-13
CA_1A-7A-20A
1
Rel-10
CA_1A-7A-26A
0
Rel-10
CA_1A-7A-28A
2
Rel-10
CA_1A-7A-40A
0
Rel-12
CA_1A-7A-42A
0
Rel-12
CA_1A-7A-46A
0
Rel-13
CA_1A-8A-20A
0
Rel-10
CA_1A-8A-28A
0
Rel-10
CA_1A-11A-28A
0
Rel-10
CA_1A-20A-28A
0
Rel-10
CA_1A-20A-42A
0
Rel-12
CA_1A-21A-28A
0
Rel-10
CA_1A-28A-42A
0
Rel-12
CA_1A-28A-46A
0
Rel-13
CA_1A-41A-42A2
0
Rel-12
CA_2A-5A-66A
0
Rel-10
CA_2A-7A-66A
0
Rel-10
CA_2A-12A-66A
0, 1
Rel-10
CA_2A-13A-66A
0
Rel-10
CA_2A-29A-66A
Rel-10
CA_2A-30A-66A
0
Rel-10
CA_2A-46A-66A
0
Rel-13
CA_2A-48A-66A
0
Rel-10
CA_3A-5A-7A
0
Rel-10
CA_3A-5A-40A
1
Rel-12
CA_3A-5A-41A
0
Rel-12
CA_3A-7A-8A
2
Rel-10
CA_3A-7A-26A
0
Rel-10
CA_3A-7A-32A
0
Rel-10
CA_3A-7A-40A
0
Rel-12
CA_3A-7A-42A
0
Rel-12
CA_3A-8A-11A
0
Rel-10
CA_3A-8A-20A
0
Rel-10
CA_3A-8A-28A
0
Rel-10
CA_3A-11A-28A
0
Rel-10
CA_3A-19A-21A
0
Rel-10
CA_3A-20A-28A
0
Rel-11
CA_3A-20A-32A4
0
Rel-10
CA_3A-20A-42A
0
Rel-12
CA_3A-21A-28A
0
Rel-10
CA_3A-21A-42A
0
Rel-12
CA_3A-28A-41A
0
Rel-12
CA_3A-28A-42A
0
Rel-12
CA_5A-7A-46A
0
Rel-13
CA_5A-12A-66A
0
Rel-10
CA_5A-30A-66A
0
Rel-10
CA_5A-40A-41A
0
Rel-12
CA_7A-20A-28A
0
Rel-11
CA_7A-20A-32A
0
Rel-10
CA_7A-20A-42A
0
Rel-12
CA_8A-11A-28A
0
Rel-10
CA_8A-28A-41A
0
Rel-12
CA_12A-30A-66A
0
Rel-10
CA_21A-28A-42A
0
Rel-12
CA_28A-40A-41A
0
Rel-12
CA_28A-41A-42A5
0
Rel-12
CA_28A-41A-46A
0
Rel-13
CA_29A-30A-66A
0
Rel-10
Note 1: UL carrier shall be supported in each of the 3 bands being aggregated unless otherwise specified.
Note 2: UL carrier is only supported on Band 1 or Band 42 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
Note 3: UL carrier is only supported on Band 1 or Band 3 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
Note 4: UL carrier is only supported on Band 3 or Band 20 not Band 32 because Band 32 is SDL band.
Note 5: For CA_28A-41A-42A, only non-simultaneous Rx/Tx on Band 41 and Band 42 is supported.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-03-03
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 3 Down Link (DL) / 3 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-03-03/36714-03-03-e00.zip
|
The present document is a technical report for 3DL/3UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 3DL/3UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 3DL/3UL inter-band carrier aggregation combinations
CA combination
REL independent from
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-04-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 4 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-04-01/36714-04-01-e00.zip
|
The present document is a technical report for 4DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 4DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 4DL/1UL inter-band carrier aggregation combinations
CA combination
REL-independent from
CA_4DL_1A-1A-3C_1UL_BCS0
Rel-11
CA_4DL_1A-1A-3A-5A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-5A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-5A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-5A-41A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7C_1UL_BCS1
Rel-11
CA_4DL_1A-3C-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-20A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-28A_1UL_BCS1
Rel-12
CA_4DL_1A-3A-7A-40A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-7A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-3A-8A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-8A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-8A-11A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-8A-20A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-19A-21A_1UL_BCS0
Rel-10
CA_4DL_1A-3A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-21A-28A_1UL_BCS0
Rel-10
CA_4DL_1A-3A-21A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-1A-3A-28A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-28A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-28A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-40C_1UL_BCS0
Rel-12
CA_4DL_1A-3C-40A_1UL_BCS0
Rel-12
CA_4DL_1A-5A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-5A-7A-46A_1UL_BCS0
Rel-13
CA_4DL_1A-5A-46C_1UL_BCS0
Rel-13
CA_4DL_1A-7A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_1A-7A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-20A-32A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-46C_1UL_BCS0
Rel-13
CA_4DL_1A-21A-28A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_1A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_1A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_1A-46D_1UL_BCS0
Rel-13
CA_4DL_1A-46D_1UL_BCS1
Rel-13
CA_4DL_2A-2A-5A-30A_BCS0
Rel-11
CA_4DL_2A-2A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-5A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-12A-30A_BCS0
Rel-11
CA_4DL_2A-2A-12A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-13A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-29A-30A_1UL_BCS0
Rel-12
CA_4DL_2A-2A-30A-66A_BCS0
Rel-11
CA_4DL_2A-2A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-2A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-4A-5B_1UL_BCS0
Rel-11
CA_4DL_2A-4A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_2A-4A-7C_1UL_BCS0
Rel-11
CA_4DL_2A-4A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-4A-12B_1UL_BCS0
Rel-11
CA_4DL_2A-5A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-12A-66A_BCS0
Rel-11
CA_4DL_2A-5B-30A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-48A-48A_1UL_BCS0
Rel-14
CA_4DL_2A-5A-48C_1UL_BCS0
Rel-14
CA_4DL_2A-5A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-5A-30A-66A_BCS0
Rel-11
CA_4DL_2A-5A-66A-66A_BCS0
Rel-11
CA_4DL_2A-5A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-5B-66A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-66C_1UL_BCS0
Rel-11
CA_4DL_2C-5B_1UL_BCS0
Rel-11
CA_4DL_2A-12A-30A-66A_BCS0
Rel-11
CA_4DL_2A-12A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-12A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-12B-66A_BCS0
Rel-11
CA_4DL_2A-13A-48A-48A_1UL_BCS0
Rel-14
CA_4DL_2A-13A-48C_1UL_BCS0
Rel-14
CA_4DL_2A-13A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-13A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-13A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-13A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-30A-66A-66A_BCS0
Rel-11
CA_4DL_2A-46A-46C _1UL_BCS0
Rel-13
CA_4DL_2A-46D_1UL_BCS0
Rel-13
CA_4DL_2A-46C-66A_1UL_BCS0
Rel-13
CA_4DL_2A-46A-46A-66A_1UL_BCS0
Rel-13
CA_4DL_2A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_2A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_2A-48D _1UL_BCS0
Rel-14
CA_4DL_2A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-66D_1UL_BCS0
Rel-11
CA_4DL_3C-7C_1UL_BCS1
Rel-11
CA_4DL_3A-3A-7A-8A_1UL_BCS0
Rel-11
CA_4DL_3A-3A-7A-8A_1UL_BCS1
Rel-11
CA_4DL_3A-3A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_3A-3A-7A-7A_1UL_BCS1
Rel-11
CA_4DL_3A-5A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_3A-5A-40A-40A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-7A-8A _1UL_BCS0
Rel-11
CA_4DL_3A-7A-7A-8A _1UL_BCS1
Rel-11
CA_4DL_3A-7A-8A-20A_1UL_BCS0
Rel-12
CA_4DL_3A-7C-20A_1UL_BCS0
Rel-11
CA_4DL_3C-7A-20A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-20A-32A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-40C_1UL_BCS0
Rel-12
CA_4DL_3A-19A-21A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-21A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-28A-41C_1UL_BCS0
Rel-12
CA_4DL_3A-28A-41A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-40D_1UL_BCS0
Rel-12
CA_4DL_3C-40C_1UL_BCS0
Rel-12
CA_4DL_3C-41C_1UL_BCS0
Rel-12
CA_4DL_3A-41D_1UL_BCS0
Rel-12
CA_4DL_3A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_3A-46D_1UL_BCS0
Rel-13
CA_4DL_3A-46D_1UL_BCS1
Rel-13
CA_4DL_4A-4A-5B_1UL_BCS0
Rel-11
CA_4DL_4A-4A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_4A-4A-12B_1UL_BCS0
Rel-11
CA_4DL_4A-5A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_4A-5A-12B_1UL_BCS0
Rel-11
CA_4DL_4A-5B-30A_1UL_BCS0
Rel-11
CA_4DL_4A-46A-46C_1UL_BCS0
Rel-13
CA_4DL_4A-46D_1UL_BCS0
Rel-13
CA_4DL_5A-7A-46C_1UL_BCS0
Rel-13
CA_4DL_5A-30A-66A-66A_BCS0
Rel-11
CA_4DL_5B-30A-66A_BCS0
Rel-11
CA_4DL_5A-46D_1UL_BCS0
Rel-13
CA_4DL_5A-46D_1UL_BCS1
Rel-13
CA_4DL_5A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_5A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_5A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_5A-48D _1UL_BCS0
Rel-14
CA_4DL_5A-5A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_5A-5A-66B_1UL_BCS0
Rel-11
CA_4DL_5A-5A-66C_1UL_BCS0
Rel-11
CA_4DL_5B-66A-66A_1UL_BCS0
Rel-11
CA_4DL_5B-66B_1UL_BCS0
Rel-11
CA_4DL_5B-66C_1UL_BCS0
Rel-11
CA_4DL_5A-66D_1UL_BCS0
Rel-11
CA_4DL_5A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_5A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_7A-46D_1UL_BCS0
Rel-13
CA_4DL_7A-46D_1UL_BCS1
Rel-13
CA_4DL_7C-46C_1UL_BCS0
Rel-13
CA_4DL_8B-39C_1UL_BCS0
Rel-12
CA_4DL_8A-41D_1UL_BCS0
Rel-12
CA_4DL_8B-41C_1UL_BCS0
Rel-12
CA_4DL_8B-46C_1UL_BCS0
Rel-13
CA_4DL_8A-46D_1UL_BCS0
Rel-13
CA_4DL_11A-46D_1UL_BCS0
Rel-13
CA_4DL_12A-30A-66A-66A_1UL_BCS0
Rel-12
CA_4DL_12B-66A-66A_BCS0
Rel-11
CA_4DL_13A-46D_1UL_BCS0
Rel-13
CA_4DL_13A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_13A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_13A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_13A-48D _1UL_BCS0
Rel-14
CA_4DL_13A-66D_1UL_BCS0
Rel-11
CA_4DL_13A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_13A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_19A-46D_1UL_BCS0
Rel-13
CA_4DL_21A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_21A-46D_1UL_BCS0
Rel-13
CA_4DL_28A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_28A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_28A-46D_1UL_BCS0
Rel-13
CA_4DL_29A-66A-66A-70A_1UL_BCS0
Rel-11
CA_4DL_29A-66C-70A_1UL_BCS0
Rel-10
CA_4DL_29A-66A-70C_1UL_BCS0
Rel-10
CA_4DL_39A-40D_1UL_BCS0
Rel-11
CA_4DL_39C-40C_1UL_BCS0
Rel-11
CA_4DL_39A-42D_1UL_BCS0
Rel-11
CA_4DL_39C-42C_1UL_BCS0
Rel-11
CA_4DL_39C-46C_1UL_BCS0
Rel-13
CA_4DL_39A-46D_1UL_BCS0
Rel-13
CA_4DL_40C-42C_1UL_BCS0
Rel-11
CA_4DL_40C-46C_1UL_BCS0
Rel-13
CA_4DL_40A-46D_1UL_BCS0
Rel-13
CA_4DL_40D-46A_1UL_BCS0
Rel-13
CA_4DL_40A-46D_1UL_BCS1
Rel-13
CA_4DL_41A-42D_1UL_BCS0
Rel-11
CA_4DL_41D-42A_1UL_BCS0
Rel-11
CA_4DL_41C-46C_1UL_BCS0
Rel-13
CA_4DL_41A-46D_1UL_BCS0
Rel-13
CA_4DL_41D-46A_1UL_BCS0
Rel-13
CA_4DL_46A-46C-66A_1UL_BCS0
Rel-13
CA_4DL_46D-66A_1UL_BCS0
Rel-13
CA_4DL_48D-66A _1UL_BCS0
Rel-14
CA_4DL_48A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_66A-66A-70C_1UL_BCS0
Rel-11
CA_4DL_66C-70C_1UL_BCS0
Rel-10
Note 1: UL carrier shall be supported in each of the 4 bands being aggregated unless otherwise specified.
Note 2: UL carrier is only supported on Band 1 or Band 42 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-05-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 5 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-05-01/36714-05-01-e10.zip
|
The present document is a technical report for 5DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 5DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 5DL/1UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_1A-3A-5A-7A-7A
12
CA_1A-3A-7A-40C
12
CA_1A-3C-7C
12
CA_1A-3A-7A-20A-28A
12
CA_1A-3A-7A-20A-42A
12
CA_1A-3A-7A-7A-26A
12
CA_1A-3A-21A-42C
12
CA_1A-3A-28A-42C
12
CA_1A-3C-40C
12
CA_1A-5A-46D
13
CA_1A-5A-7A-46C
13
CA_1A-7A-46D
13
CA_1A-21A-28A-42C
12
CA_1A-41C-42C
12
CA_1A-46E
13
CA_2A-2A-5A-12A-66A
12
CA_2A-5B-30A-66A
12
CA_2A-2A-5A-30A-66A
12
CA_2A-5A-30A-66A-66A
12
CA_2A-2A-5A-66C
12
CA_2A-2A-5A-66B
12
CA_2A-2A-5A-66A-66A
12
CA_2A-2A-12A-30A-66A
12
CA_2A-2A-12B-66A
12
CA_2A-2A-66D
12
CA_2A-2A-66A-66C
12
CA_2A-2A-66A-66B
12
CA_2A-4A-5B-30A
12
CA_2C-5B-30A
12
CA_2A-5B-66C
12
CA_2A-5B-66B
12
CA_2A-5A-66D
12
CA_2A-12B-66A-66A
12
CA_2A-13A-66D
12
CA_2A-13A-66A-66C
12
CA_2A-13A-66A-66B
12
CA_2A-46A-46D
13
CA_2A-46D-66A
13
CA_2A-46A-46C-66A
13
CA_3A-3A-7A-7A-8A
12
CA_3A-28A-40D
12
CA_3A-28A-41A-42C
12
CA_3A-28A-41C-42A
12
CA_3A-40E
12
CA_3C-41D
12
CA_3A-41C-42C
12
CA_3A-46E
13
CA_4A-4A_5B_ 30A
12
CA_4A-46A-46D
13
CA_5A-46E
13
CA_5A-5A-66D
12
CA_5A-5A-66A-66C
12
CA_5A-5A-66A-66B
12
CA_5A-7A-46D
13
CA_5B-66A-66C
12
CA_5B-66A-66B
12
CA_7A-46E
13
CA_7C-46D
13
CA_8B-41D
12
CA_8B-46D
13
CA_8A-46E
13
CA_11A-46E
13
CA_13A-46E
13
CA_19A-46E
13
CA_21A-46E
13
CA_28A-41C-42C
12
CA_28A-46E
13
CA_39A-40E
12
CA_39C-40D
12
CA_39C-41D
12
CA_39A-42E
12
CA_39C-42D
12
CA_39C-46D
13
CA_39A-46E
13
CA_40C-46D
13
CA_40A-46E
13
CA_40D-46C
13
CA_41C-42D
12
CA_41D-42C
12
CA_41A-46E
13
CA_41C-46D
13
CA_41D-46C
13
CA_46E-66A
13
CA_46A-46D-66A
13
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.741
|
Study on further enhancements to Coordinated Multi-Point (CoMP) operation for LTE
|
TR
|
14.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.741/36741-e00.zip
|
The present document is related to the technical report for the study item “Study on Further enhancements to Coordinated Multi-Point Operation” [2]. The purpose of this TR is to help TSG RAN WG1 to understand the performance benefit of the enhancements related to coordinated multi-point schemes.
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 information and draw a conclusion on way forward.
This document will be kept up-to-date via CRs in the future.
|
36.743
|
Enhanced Multimedia Broadcast/Multicast (eMBMS) enhancements for LTE
|
TR
|
0.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.743/36743-010.zip
|
This Technical Report summarizes the findings related to the following objectives of [2]:
• Support for standalone carrier with all DL subframes dedicated to MBSFN transmission and self-contained eMBMS signaling including information of SIB13, SIB15, SIB16. (RAN2)
• Support for multi-carrier eMBMS/unicast operation involving reception from one or more eMBMS cells that may be non-collocated and asynchronous with one or more cells that are simultaneously used for unicast. (RAN4, RAN2)
• Solutions where a UE can receive the TV transport service without being authenticated (RAN1, RAN2, RAN3)
|
36.744
|
Citizens Broadband Radio Service (CBRS) 3.5 GHz band for LTE in the United States
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.744/36744-e00.zip
|
The present document is a technical report for the CBRS (Citizens Broadband Radio Service) 3.5GHz E-UTRA TDD band (3550-3700MHz) for operations in the United States.
|
36.745
|
Feasibility study on global application of LTE Band 11 and of LTE Band 21 User Equipments (UEs)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.745/36745-e00.zip
|
The present document is to evaluate possible methods and conditions for existing Band 11 and Band 21 UEs to comply with a new satellite protection requirement defined by ITU-R.
|
36.747
|
Enhanced CRS and 4Rx SU-MIMO Interference Mitigation Performance Requirements for LTE
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.747/36747-e00.zip
|
The objective of this report is to investigate feasibility and specify requirements for 1) CRS-IM receivers for the generic scenarios with different number of CRS APs (2, 4) and different number of UE receive antennas and 2) SU-MIMO IM receivers for UEs equipped with 4 receive antennas. The work item [2] has the following detailed objectives:
- Investigate feasibility and specify requirements for the CRS-IM receivers for the generic scenarios with different number of CRS APs (2, 4) and different number of UE receive antennas for synchronous networks:
- Stage 1: Investigate performance benefits and feasibility of using CRS-IM receivers:
- Identify target scenarios including deployment scenarios, interference models, and others
- Reuse Rel-12 NAICS and Rel-13 CRS-IM WIs assumptions as the starting point
- Evaluate the CRS-IM performance benefits
- Identify reference CRS-IM receiver structure assumptions including at least number of cancelled cell(s), and IM algorithm.
- The tradeoff between complexity and performance should be analyzed in order to define reference receivers.
- Stage 2: Specify UE demodulation and CSI reporting performance requirements to verify practical CRS-IM operation for the identified scenarios based on the outcome of Stage 1.
- The work should be done under the following assumptions:
- The following scenarios are prioritized:
- 2 RX antennas UEs with 4 CRS APs in the serving and interference cell(s)
- 2 RX antennas UEs with a mix of 2 and 4 CRS APs in the serving and interference cell(s)
- 4 RX antennas UEs with 2 and 4 CRS APs in the serving and interference cell(s)
- CRS-IM can be used for different downlink physical channels:
- First priority: PDSCH (both CRS- and DMRS-based transmission modes)
- Second priority: DL control channels including PDCCH, PCFICH, PHICH and EPDCCH
- Non-colliding CRS scenarios are primarily considered.
- Colliding CRS scenarios are not precluded.
- Homogeneous deployment scenarios are primarily considered
- Heterogeneous deployment scenarios are not precluded.
- Single carrier case.
- Reference PDSCH receiver structure: LMMSE-IRC with CRS-IM.
- Investigate feasibility and specify requirements for the enhanced SU-MIMO inter-stream interference mitigation (SU-MIMO IM) receivers for the scenarios with 4 receive antennas UEs
- Stage 1: Investigate performance benefits and feasibility of using SU-MIMO IM receivers for the scenarios with 4 receive antennas UEs.
- Investigate and agree on target scenarios including layer number for spatial multiplexing, MCS, propagation conditions and others for performance evaluation
- Reuse the assumptions for Rel-12 SU-MIMO IM (Type-C receiver) and Rel-13 4Rx MIMO performance requirements as starting point.
- SU-MIMO scenarios
- rank 2/3/4 SU-MIMO is considered
- The maximum number of layers (e.g. rank3/4) should be determined based on feasibility study (e.g. operating SNR), realistic Tx EVM assumption and the study on performance gains, reference receiver complexity and testability, etc.
- Strive to reuse agreed Tx EVM for 4Rx in Rel-13 if the related agreement can be reached
- Consider 2 and 4 CRS APs scenarios
- Channel correlations
- Focus on the Medium, Medium A and High antenna correlation models
- Modulation order: up to 256QAM
- The considered modulation orders should be decided based on feasibility study (e.g. operating SNR), realistic Tx EVM assumption, performance gains, reference receiver complexity and testability, etc.
- Strive to reuse agreed Tx EVM for 4Rx in Rel-13 if the related agreement can be reached.
- Identify the reference receiver structure for SU-MIMO IM evaluation
- R-ML is considered in high priority
- Evaluate the performance of enhanced SU-MIMO IM receivers.
- Stage 2: Specify UE demodulation performance requirements to verify enhanced SU-MIMO receivers for the UEs equipped with 4 RX antennas
- Reference receiver structure and other test parameters are based on the outcome of Stage 1.
- Single carrier case.
|
36.749
|
Evolved Universal Terrestrial Radio Access (E-UTRA); New AWS Band for LTE
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.749/36749-e00.zip
|
The present document a technical report for the AWS 3/4 band for LTE work item. The band is specified as 15+25 MHz (1 695 – 1 710 MHz / 1 995 – 2 020 MHz) with two duplex spacings.
|
36.750
|
Study on Voice and Video Enhancement for LTE
|
TR
|
14.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.750/36750-e10.zip
|
The present document captures the findings of the study on voice and video enhancement for LTE.
|
36.752
|
Study of Narrow-Band Internet of Things (NB-IoT) Radio Frequency (RF) requirement to co-existence with Code Division Multiple Access (CDMA)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.752/36752-e00.zip
|
The present document summarizes the studies of NB-IoT RF requirement for coexistence with CDMA.
|
36.785
|
Vehicle to Vehicle (V2V) services based on LTE sidelink; User Equipment (UE) radio transmission and reception
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.785/36785-e00.zip
|
The present document is the Technical Report on TR on V2V Services based on LTE sidelink.
The purpose of the present document is to study the radio requirements on V2V services based on LTE sidelink as part of the Rel-14 work item. The normative requirements resulting from the present document will be addressed in the applicable release 14 Technical Specifications (TS).
|
36.786
|
Vehicle-to-Everything (V2X) services based on LTE; User Equipment (UE) radio transmission and reception
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.786/36786-e00.zip
|
The present document is the Technical Report on TR on V2X Services based on LTE sidelink.
The purpose of the present document is to study the radio requirements and adjacent channel coexistence with high power up to 33dBm on V2X services based on LTE sidelink as part of the Rel-14 work item. The normative requirements resulting from the present document will be addressed in the applicable release 14 Technical Specifications (TS).
|
36.858
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE 2.6 GHz FDD SDL band (2570-2620 MHz)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.858/36858-e00.zip
|
The present document is a technical report for the LTE 2,6 GHz FDD supplemental downlink (SDL) band covering 2 570-2 620 MHz. It is intended to be specified for E-UTRA for operations in Region 1. The band is to be used in CA for E-UTRA. The LTE CA combination of Band 3+ FDD SDL Band 2 570-2 620 MHz was selected. All the CA related aspects are reported in 2DL/1UL CA basket TR 36.714-02-01 [3].
|
36.881
|
Study on latency reduction techniques for LTE
|
TR
|
14.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.881/36881-e00.zip
|
This document is related to the technical report for the study item “Study on latency reduction techniques for LTE” [2]. The purpose of this TR is to capture the findings from TSG RAN WG2 and WG1 according to their respective objectives, and to draw a conclusion on way forward.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.885
|
Study on LTE-based V2X services
|
TR
|
14.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.885/36885-e00.zip
|
The present document contains the results and findings from the study item, “Feasibility Study on LTE-based V2X Services” [2]. The purpose of this TR is to document the identified LTE enhancements and corresponding evaluations for LTE-based V2X services defined in [3] as follows:
- V2V (vehicle-to-vehicle): covering LTE-based communication between vehicles.
- V2P (vehicle-to-pedestrian): covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger).
- V2I/N (vehicle-to-infrastructure/network): covering LTE-based communication between a vehicle and a roadside unit/network. A roadside unit (RSU) is a stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications. Note: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that combines V2X application logic with the functionality of an eNB (referred to as eNB-type RSU) or UE (referred to as UE-type RSU).
This document addresses LTE-based V2X both with and without LTE network coverage, and covers both the operating scenario where the carrier(s) is/are dedicated to LTE-based V2X services (subject to regional regulation and operator policy including the possibility of being shared by multiple operators) and the operating scenario where the carrier(s) is/are licensed spectrum and also used for normal LTE operation.
This technical report contains the evaluation methodology for LTE-based V2V, V2I/N and V2P services to compare the performance of different technical options.
This document identifies necessary enhancements to LTE for support of PC5 transport for V2V services.
This document captures identification and evaluation of Uu transport for V2V and PC5/Uu transport for V2I/N and V2P services.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.886
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Band 41 High Power UE (HPUE)
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.886/36886-e10.zip
|
The scope of the present document is to evaluate the feasibility of increasing UL TX power in Band 41 from 23dBm +/-2dB (Power Class 3) to 26dBm +/-2dB (Power Class 2) as well as discuss impacts (if any) to other 3GPP bands and regulatory requirements.
|
36.896
|
Study on Flexible eNB-ID and Cell-ID in E-UTRAN
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.896/36896-e00.zip
|
The present document is related to the technical report of the study item "Study on Flexible eNB-ID and Cell-ID in E-UTRAN " (RP-160534 [2]).
This activity involves the Radio Access work area of the 3GPP studies and has impacts on the 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.898
|
Network Assistance for Network Synchronization
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.898/36898-e00.zip
|
The present document captures the results of the study item on Network Assistance for Network Synchronization in LTE in RP-151084 [2]. It identifies the existing LTE functions that may need network based synchronization and their synchronization-related requirements, and reviews and compares techniques for enhancement of RAN functionality.
|
37.805
|
Study on HSPA and LTE Joint Operation
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.805/37805-e00.zip
|
The present document captures the results of Study on HSPA and LTE Joint Operation in RP-160571 [2]. It identifies possible solutions to support concurrent transmission of CS in UMTS and PS in LTE and evaluates the impacts on network architecture and interface.
|
37.871
|
E-UTRA, UTRA and GSM/EDGE; Multi-Band Base Station testing with three or more bands
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.871/37871-e00.zip
|
The present document is a technical report of the Multi-Band Base Station testing with three or more bands work item which was approved at TSG RAN #70 [2]. The objective of the present document is to provide specification support for Multi-Band Base Station testing with three or more bands.
The present document provides motivation, requirements and a list of recommended changes to the specifications.
|
38.801
|
Study on new radio access technology: Radio access architecture and interfaces
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.801/38801-e00.zip
|
The present document covers the Radio Access Architecture and Interface aspects of the study item “New Radio Access Technology” [1]. The purpose of this TR is to record the discussion and agreements that arise in the specification of the “New Radio Access Technology” from an Access Architecture and Interface specification point of view.
|
38.802
|
Study on new radio access technology Physical layer aspects
|
TR
|
14.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.802/38802-e20.zip
|
This document is related to the technical report for physical layer aspect of the study item “Study on New Radio Access Technology” [2]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, 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.
This document is intended to gather all information in order to compare the solutions and gains vs. complexity, and draw a conclusion on way forward.
This document will be kept up-to-date via CRs in the future.
|
38.803
|
Study on new radio access technology: Radio Frequency (RF) and co-existence aspects
|
TR
|
14.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.803/38803-e40.zip
|
The present document covers the RF and co-existence aspects of the study item “New Radio Access Technology” [1].
|
38.804
|
Study on new radio access technology Radio interface protocol aspects
|
TR
|
14.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.804/38804-e00.zip
|
The present document covers the Radio Interface Protocol aspects of the study item “New Radio Access Technology” [1]. This document is intended to gather the agreements for which normative work will take place after completing this study item. In limited cases, major options and reasons of decision are described.
|
38.805
|
Study on new radio access technology; 60 GHz unlicensed spectrum
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.805/38805-e00.zip
|
The present document contains the results and findings from the study item, “Study on New Radio Access Technology” [2].
This technical report documents the existing regulatory requirements for unlicensed spectrum deployment in the 60 GHz bands.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
44.118
|
Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode
|
TS
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-e00.zip
| |
45.871
|
Study on Multiple Input Multiple Output (MIMO) for GSM/EDGE downlink
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.871/45871-e00.zip
|
The present document contains investigations carried out and during the 3GPP study item on MIMO for GSM/EDGE Downlink.
The following items are covered in this study report:
- Objectives for the study
- Overview of MIMO for Downlink concept
- Conceptual design of several functional blocks of this solution
- Performance evaluations related to envisaged functional blocks belonging to MIMO for Downlink
- Compatibility analysis
|
22.234
|
Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking
|
TS
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.234/22234-d10.zip
|
This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
Maintenance of the I-WLAN feature is discontinued as of Release 12. 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.
|
22.806
|
Study on application-specific congestion control for data communication
|
TR
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.806/22806-d10.zip
|
The present document provides a study on Application specific Congestion control for Data Communication (ACDC). This Study investigates the following aspects:
- Identify the use cases and potential requirements to allow/restrict the communication initiation of particular applications defined by operator, subject to regional regulations;
- Gap analysis with existing access control mechanisms.
|
22.807
|
Study on enhancements for infrastructure-based data communication between devices
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.807/22807-d00.zip
|
More and more devices are becoming connected. These connected devices can be MTC devices such as smart meters, but increasingly all kinds of consumer electronic devices (e.g. photo cameras, navigation devices, e-books, hifi equipment, TVs) are connected. Where Machine-Type Communication is generally client server based, many consumer electronic devices also communicate with other consumer electronic devices. For example a photo camera can communicate with a printer, or a media server can communicate with hi-fi equipment. It may be of interest for the cellular industry to support infrastructure based discovery and communications between connected devices, i.e. without the need for intermediate network servers.
In this context, the objective of the present document is to study:
• Potential enhancements to support secure discovery of Ues of interest
• Potential enhancements to support secure optimized end-to-end data communication between Ues via the 3GPP infrastructure
• Potential enhancements derived from user requirements for identification in communication between Ues
• Potential interactions of data communication between devices with LIPA and SIPTO
Ues may represent functions/capabilities provided by non-3GPP devices in order to support interworking. However, discovery of, or end-to-end data communication with, non-3GPP devices themselves is out of scope.
Potential enhancements will be studied through the definition of use cases. From these use cases, potential requirements are identified. For potential requirements identified, if any, it will be determined what is the best way to approach normative specification.
|
22.810
|
Study of enhanced call information presentation
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.810/22810-d00.zip
|
The present document will consider use cases and identify potential requirements for enhancing the calling information presentation. This will include:
- Type of contents shared in calling information presentation, e.g. number, name, portrait, signature, etc.
- Use cases for both calling party and called party.
- Interaction with MMTel services, CAT, and CRS service.
- Interoperability with other network.
|
22.828
|
Study on co-ordinated Packet data network GateWay (PGW) Change for Selected IP Traffic Offload (CSIPTO)
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.828/22828-d00.zip
|
The present document considers use cases and identifies potential requirements for network consideration of the following items regarding the change of local PGW in use for SIPTO:
a) end-user experience and preferences; and
b) UE's knowledge of ongoing IP flow types.
|
22.852
|
Study on Radio Access Network (RAN) sharing enhancements
|
TR
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.852/22852-d10.zip
| |
22.853
|
Study on Service Exposure and Enablement Support (SEES) requirements
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.853/22853-d00.zip
|
The present document identifies potential requirements for the network information and capability that the 3GPP network could exposed to the 3rd party applications and the MNOs could get the benefits from such the 3rd party applications.
The present document identifies if existing capabilities (e.g. MOSAP, OMA, GSMA oneAPI, MTC IWF) already satisfy the use cases. Potential additional requirements are formulated if enhancements to existing capabilities or new capabilities are needed.
|
22.897
|
Study on isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.897/22897-d00.zip
| |
22.934
|
Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.934/22934-d00.zip
|
This document studies the feasibility of interworking between 3GPP systems and Wireless Local Area Networks (WLANs). This document identifies and describes:
- Scenarios for 3GPP - WLAN Interworking
- 3GPP - WLAN interworking service requirements
- Guidelines for standardisation of 3GPP-WLAN interworking
The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
It is beyond the scope of 3GPP to develop new system functionalities for WLANs that are not interworking with any 3GPP system functionality.
|
22.935
|
Feasibility study on Location Services (LCS) for Wireless Local Area Network (WLAN) interworking
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.935/22935-d00.zip
|
The 3GPP has developed and continues to develop Location Services (LCS) requirements and standards for GSM and UMTS. To further the advancement of LCS within the 3GPP, LCS requirements and standards may be extended for 3GPP WLAN interworking to support the same location-based services that have been deployed today for GSM and UMTS. LCS with 3GPP WLAN Interworking system is considered to enlarge the area of location services.
The purpose of the feasibility study is to study a generic interworking functionality for LCS between 3GPP system and WLAN systems (e.g. IEEE 802.11 family, HIPERLAN/2, …). Specifically, the feasibility study aims to:
- Study the LCS requirements for 3GPP WLAN Interworking scenarios.
- Study the different possible LCS architectures for interworking.
Also, the feasibility study will:
- Assess the service requirements for support of LCS over I-WLAN
- Define the MMI aspects, i.e., the minimum set of functions to support LCS when the choice of access system by the user and/or terminal for when both access systems is available.
- Assess the charging requirements and architecture impacts. In particular, consider whether or not WLAN charging for LCS should be integrated with the architecture for UMTS charging for LCS.
- Assess the security requirements, given the prerequisite that a) the security level of the UMTS platform itself is not impacted, b) the security level provided to users in the WLAN mode is comparable to the one of UMTS.
|
22.937
|
Requirements for service continuity between mobile and Wireless Local Area Network (WLAN) networks
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.937/22937-d00.zip
|
The present document develops the use cases and requirements for service continuity between a 3GPP network and another network, which can be:
- a TISPAN NGN with an IMS, accessed by a WLAN.
- an ISP accessed via a WLAN
Each access network has its own separate security system and the NOs have a commercial agreement for roaming and handover.
The present document considers use cases whereby:
Editors Note: Text to be added when use cases are agreed
The present document also examines the requirements and implications of:
- service aspects: maintaining service quality and service continuity, while roaming between a 3GPP PLMN and an independently-owned WLAN;
- security aspects: while roaming between a 3GPP PLMN and a WLAN, in particular when networks may be independently authenticated.
- UICC aspects, including NAA types, personalisation and ownership.
The present document is related to ongoing standardisation efforts in the following areas:
- where the WLAN is an I-WLAN , requirements for which are described in [3];
- methods for selecting the 3GPP or the non-3GPP access network, requirements for which are described in [2].
|
23.179
|
Functional architecture and information flows to support mission critical communication services; Stage 2
|
TS
|
13.5.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.179/23179-d50.zip
|
This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service including the common services core architecture for identity management, group management, and configuration management required to support the MCPTT voice service. Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.179 [2].
The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [9]. Certain MCPTT functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats.
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered, however, for roaming only EPC-level roaming and IMS-level roaming are considered i.e. partner MCPTT system based roaming (also known as "migration") is out of scope.
|
23.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; System description
|
TS
|
13.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-d10.zip
|
This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
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.
|
23.327
|
Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems
|
TS
|
13.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-d10.zip
|
This document specifies the stage 2 system description for providing mobility between 3GPP Wireless Local Area Network Interworking (I‑WLAN) and 3GPP Systems. The I-WLAN feature defined in TS 23.234 [2] has been discontinued since Release 13 and it is removed from this specification.
|
23.704
|
Study on Circuit Switched (CS) / Packet Switched (PS) coordination in shared network; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.704/23704-d00.zip
|
The present document investigates relevant scenarios and possible solutions to enhance the CS/PS Coordination in a shared UTRAN/GERAN network as currently specified in TS 23.251 [2].
Within this technical report relevant mobility scenarios shall be investigated and it shall be evaluated per scenario if any issues with CS/PS Coordination can be expected. The investigation shall be done for non-supporting UEs and for any UE in shared networks where no Multiple PLMN list is broadcasted. Solutions to solve found issues shall be evaluated and agreed for subsequent normative specification.
The scenarios that need to be handled will at least include:
- CS handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- PS Handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- Redirection;
- Cell reselection;
- CSFB;
- rSRVCC and SRVCC;
- PLMN selection at handover based on UE capability;
- Registration to PS domain in a shared network after CS only registration has been performed.
|
23.705
|
Study on system enhancements for user plane congestion management
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.705/23705-d00.zip
|
The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document.
|
23.706
|
Study on enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.706/23706-d00.zip
|
This document studies enhancements to the IMS architecture and stage 2 procedures in order to support the requirements defined by SA1 as part of eWebRTCi (Enhancements to WEBRTC interoperability).
The output of this work will not require changes to existing WebRTC enabled web browsers.
|
23.707
|
Architecture enhancements for dedicated core networks; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.707/23707-d00.zip
|
An operator may choose to deploy one (or more) dedicated core networks within a PLMN with each core network dedicated for specific type(s) of subscriber. The present document studies and evaluates architectural enhancements required to support dedicated core networks. The specific dedicated core network that serves a UE is selected based on subscription information and operator configuration, without requiring the UEs to be modified.
The technical report covers both assignment of dedicated core network nodes and maintaining the association during mobility. Roaming and network sharing aspects of dedicated core network, and impacts on procedures such as CSFB, SRVCC and rSRVCC will be studied.
Dedicated core networks may be in the PS domain or CS domain or both.
|
23.708
|
Architecture enhancements for service capability exposure
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.708/23708-d00.zip
|
The present document studies and evaluates architecture enhancements for a service capability exposure framework wherein 3GPP system provided service capabilities are exposed via one or more standardized APIs, e.g. the OMA-API(s). As part of this work it will be identified how the APIs and the 3GPP system functionality act together to expose 3GPP service capabilities. The definition of APIs is out of scope of this work item.
The present document will also define the architectural enhancements for new service capabilities and services (based on the Stage 1 normative requirements) that are exposed via the service capability exposure framework.
|
23.709
|
Study on optimizations to support high latency communications; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.709/23709-d00.zip
|
This document captures the study result of possible system enhancements to support applications that communicate with devices that are not reachable for a long period over the 3GPP IP connectivity and being able to support large number of such devices in the system without negatively affecting the system performance.
In addressing the above, the following problem is studied:
- Downlink access for devices that are not reachable for a long period and the problems associated with such devices (e.g. packet discard when the UE sleeps, frequent retransmissions, load on the CN network, waste of radio resources and UE power when the network unnecessarily conveys retransmit packets, etc.). This study may propose and evaluate enhancements to the 3GPP system. Depending on conclusions, the study may also propose 3GPP enablers to be used by the service layer e.g. defined by other SDOs for downlink access to devices that are not reachable for a long period.
Different application layer protocols used within the M2M ecosystem have different requirements and characteristics with respect to acceptable end-to-end delay, round trip time, persistence in retransmissions, etc. The result of this study may include general recommendations for application layers how to use the 3GPP accesses for better application performance and optimal core and radio network efficiency thereof.
|
23.712
|
Study on warning status reporting
|
TR
|
13.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.712/23712-d00.zip
|
The present document investigates possible enhancements to the Warning Status Reporting mechanisms specified up to release 12 in 3GPP TS 23.041 [2].
The study will cover:
- identification of requirements for Warning Status reporting;
- identification and evaluation of alternatives for Warning Status reporting;
- analysis on their potential interactions with the existing mechanisms; and
- recommendations on the alternatives.
The result of this study will be used to identify the changes possibly required in the 3GPP specifications to support enhanced Warning Status reporting mechanisms.
|
23.713
|
Study on extended architecture support for proximity-based services
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.713/23713-d00.zip
|
The scope of this Technical Report is to study and evaluate the possible architecture enhancements to the Proximity-based Services (ProSe) system defined in TS 23.303 [3], based on the relevant Stage 1 requirements defined in TS 22.278 [4] and TS 22.115 [5].
The present Technical Report documents the analysis and general principles agreed regarding these objectives, and collects the solution details developed based on these agreements, in order to progress them to the relevant specifications.
|
23.718
|
Architecture enhancement for flexible mobile service steering
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.718/23718-d00.zip
|
The present document studies and evaluates architectural enhancements required for 3GPP systems to provide flexible mobile service steering policies as per the service requirements defined in TS 22.101 [2], clause 30.
NOTE: Service enablers supported within the (S)Gi-LAN and the routing of traffic between those service enablers are not in the scope. The scope of the work is restricted to providing policies for traffic steering through interfaces defined by 3GPP.
|
23.720
|
Study on architecture enhancements for Cellular Internet of Things (CIoT)
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.720/23720-d00.zip
|
The present document studies and evaluates the architecture enhancement to support ultra-low complexity, power constrained, and low data-rate 'Internet of Things' devices.
The study will consider architecture enhancements/simplifications in the following areas:
- Support of highly efficient handling of frequent and infrequent small data transmissions (e.g. based on the traffic model in TR 45.820 [4]) with minimised overhead for system signalling without compromising e.g. security.
- Support of power consumption optimisations and/or using existing ones that have been developed for EPS or GPRS.
- Assessing simplification of Mobility Management and Session Management procedures.
- Support of paging optimisations for UEs requiring coverage enhancements.
The present document will also consider system architecture alternatives to address the points above.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.