id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.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.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.770
|
Study on system impacts of extended Discontinuous Reception (DRX) cycle for power consumption optimization
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.770/23770-d00.zip
|
The present document studies the core network and NAS impacts in UE of extending DRX cycle for both idle mode and connected mode, solutions in the core network to support it, and interactions between GERAN/RAN and Core Network. Also, basic assumptions may be done for each solution on GERAN/RAN aspects of extending DRX cycle.
The main goal is to identify which open issues remained from the Rel‑12 study for extended Idle and Connected mode DRX as described in TR 23.887 [4] (as documented in clause 7.1.3.1 and 7.1.3.6 of TR 23.887), document potential solutions and conclude on which feasible solutions would be adopted in core network (pending work in RAN regarding extension of DRX cycle).
No connected mode mobility enhancements for extended C-DRX are considered in this work, i.e., if a UE using extended C-DRX moves to a different cell, current connected mode mobility procedures apply.
|
23.771
|
Study on system impacts of IP Multimedia Subsystem (IMS) emergency sessions over Wireless Local Area Network (WLAN)
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.771/23771-d00.zip
|
The present document studies the mechanisms needed to support IMS Emergency sessions over WLAN (both in the Trusted -S2a - and in the untrusted -S2b- cases)
The study is split up into 2 phases corresponding to 2 SID (FS_SEW1 and FS_SEW2).
Topics to be studied in phase 1 (FS_SEW1) are:
- Providing access to EPC over WLAN in order to support an emergency session only in case of "Valid" UEs as in the case 1 in clause 4.3.12.1 of TS 23.401 [3]: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session.
- Providing Location information (in particular for untrusted WLAN). Only existing location determination mechanisms are considered i.e. location determination mechanisms that should not require standard effort. No location accuracy requirements are considered in phase 1.
Phase 1(FS_SEW1) will not consider solutions that imply specification activities in other SDO(s).
Topics to be studied in phase 2 (FS_SEW2) correspond to all the features not covered by phase 1, e.g.:
- Support of other cases for the access to EPC over WLAN (e.g. the UE is authenticated but is in a location where it is restricted from regular service, or is unauthenticated or has no USIM).
- Roaming cases (user not in his / her home country).
- Support of session continuity of emergency sessions at inter-access mobility.
- TWAN access.
|
23.797
|
Study on architecture enhancements to support isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.797/23797-d00.zip
|
This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Isolated E-UTRAN operation for public safety based on the Stage 1 requirements in TS 22.346 [3].
|
23.779
|
Study on application architecture to support Mission Critical Push To Talk over LTE (MCPTT) services
|
TR
|
13.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.779/23779-d00.zip
|
This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for the Mission Critical Push To Talk over LTE (MCPTT) application. This TR will identify the architecture needed to support MCPTT services based on the Stage 1 requirements, including TS 22.179 [2]. This Technical Report depends on functionality specified in 3GPP specifications.
|
23.861
|
Network based IP flow mobility
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.861/23861-d00.zip
|
Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel‑13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel‑10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel‑13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel‑13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel‑13 consider the following aspects:
- The support of a PDN Connection active over multiple accesses simultaneously.
- The association of one or multiple IP flows belonging to a PDN connection to an access system.
- The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
- The triggers for IP flow mobility in the UE and the network.
- UE-initiated and network-initiated NBIFOM.
- The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used.
|
23.789
|
Monitoring Enhancements
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.789/23789-d00.zip
|
The present document studies and evaluates architectural enhancements required for 3GPP systems to provide monitoring service capability as per the service requirements defined in TS 22.368 [2], clause 7.2.8 and TS 22.101 [10], clause 29.2.
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study.
|
23.772
|
Enhanced Circuit Switched (CS) fallback
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.772/23772-100.zip
|
Editor's note: This clause will describe the work scope of the work item.
The present document studies enhancements for CSFB in the interest of shortening the call setup time. Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
There shall be no UE impact.
Normative specifications may be developed based on the conclusions of the present document.
|
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.
|
23.741
|
Study on enhancements to Multimedia Broadcast/Multicast Service (MBMS) for LTE
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.741/23741-d00.zip
|
The objective of this Technical Report is to study and specify potential modifications to the MBMS/GCSE_LTE architectures and/or procedures as specified in TS 23.246 [2] and TS 23.468 [3] to enable the following improvements and enhancements:
1. to allow the establishment of MBMS bearers using target area information, as distinct from using an MBMS Service Area;
2. to MBMS congestion handling;
3. if seen to be needed, to possible MBMS roaming scenarios;
4. as required by the MCPTT application work.
|
23.858
|
Usage Monitoring Control PCC Enhancement
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-d00.zip
|
The scope of this technical report is to capture the results of a study that investigates if enhancements to the existing policy control architecture are needed in the area of usage monitoring control. The goals of the study are to derive possible requirements and architecture enhancements for:
1. Monitoring of service (s) / application (s) in more than one usage monitoring group;
2. Disabling a service (s) / application (s) from the existing usage monitoring group of services/group of applications;
3. Excluding the usage of a particular service (s) / application (s) from the accumulated usage for the IP-CAN session/TDF session;
4. Usage control for a subscriber group, e.g. the members of a family or a company subscriber, or a group of devices belonging to subscribers that share the same usage allowance threshold.
In addition, study the different proposed solutions for effective time based usage monitoring and how associated start and end of usage is defined.
|
23.769
|
Group based enhancements
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.769/23769-d00.zip
|
The present document studies and evaluates architectural enhancements required for Group based features which include the following aspects:
- Fulfil the general group based requirements (TS 22.368 [2] clause 7.2.14.1)
- Fulfil the group based policing requirements (TS 22.368 [2] clause 7.2.14.2)
- Fulfil the group based addressing requirements (TS 22.368 [2] clause 7.2.14.3)
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study.
|
24.381
|
Mission Critical Push To Talk (MCPTT) group management; Protocol specification
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.381/24381-d40.zip
|
The present document specifies the group management protocols needed to support Mission Critical Push To Talk (MCPTT). Group management applies only when the UE operates on the network.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the group management client (GMC) functionality, to application server supporting the group management server (GMS) functionality, and to application server supporting the MCPTT server functionality.
|
24.383
|
Mission Critical Push To Talk (MCPTT) Management Object (MO)
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.383/24383-d40.zip
|
The present document defines a number of Mission Critical Push To Talk (MCPTT) Management Objects (MO) that are configured for the MCPTT UE for the operation of the MCPTT Service. The management objects are compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA OMA-ERELD_DM-V1_2 [2].
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting on-line, off-line or both on-line and off-line configuration of the configuration management client.
The present document is applicable to an MCPTT UE supporting off-line configuration of the group management client.
The parameters defined by the management objects in the present document are configured in the MCPTT UE using on-line configuration over the CSC-4 reference point and using off-line configuration over the CSC-11 and CSC-12 reference points. Other specifications define how these parameters are used in the operation of MCPTT, and whether they are applicable to on-network operation or off-network operation, or both:
- 3GPP TS 24.379 [7]
- 3GPP TS 24.380 [8]
- 3GPP TS 24.381 [9]
- 3GPP TS 24.382 [11]
- 3GPP TS 24.384 [12]
The common network operation means both on-network operation and off-network operation in the present document.
The following management objects are defined in the present document:
- MCPTT UE configuration MO
- MCPTT user profile MO
- MCPTT group configuration MO
- MCPTT service configuration MO
- MCPTT UE initial configuration MO
The MOs listed above define repositories of data in the ME.
|
24.382
|
Mission Critical Push To Talk (MCPTT) identity management; Protocol specification
|
TS
|
13.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.382/24382-d30.zip
|
This document specifies the identity management and authentication protocols needed to support Mission Critical Push To Talk (MCPTT). Identity management applies only to on-network operation.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
This document is applicable to User Equipment (UE) supporting the identity management client functionality, and to application servers supporting the identity management server functionality.
|
24.384
|
Mission Critical Push To Talk (MCPTT) configuration management; Protocol specification
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.384/24384-d40.zip
|
The present document specifies the configuration management documents and protocols needed to support Mission Critical Push To Talk (MCPTT) online configuration over the CSC-4 and CSC-5 reference points and the procedures to support Mission Critical Push To Talk (MCPTT) offline configuration over the CSC-11and CSC-12 reference points. Configuration management documents defined in the present document includes:
MCPTT UE initial configuration document;
MCPTT UE configuration document;
MCPTT user profile configuration document; and
MCPTT service configuration document.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting the configuration management client functionality, to application server supporting the configuration management server functionality, and to application server supporting the MCPTT server functionality.
|
25.705
|
Study on Small data transmission enhancements for UMTS
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.705/25705-d00.zip
|
The study on small data transmissions enhancements for UMTS has as a target to investigate and provide solutions in the areas of coverage, signalling optimization, support of massive deployment of devices, and power savings taking into consideration minimizing the impact on the physical layer, legacy terminals, and networks [2].
|
25.756
|
RAN sharing enhancements for UMTS
|
TR
|
13.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.756/25756-d00.zip
|
This document captures the results of the study item on RAN Sharing Enhancements for UMTS in RP-142284 [2]. It identifies the existing functions for UTRAN RAN Sharing, the use cases and requirements for enhancements, and reviews and compares scenarios and techniques for enhancement of RAN functionality.
|
25.706
|
Technical Report on Downlink Enhancements for UMTS
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.706/25706-d00.zip
|
WCDMA currently serves as the dominant mobile broadband technique. The number of connections for WCDMA users and the average user date rate have continued to increase in the past years and will further increase in the coming years, which requires WCDMA to evolve further from both uplink and downlink perspective.
|
25.766
|
Study on Network-Assisted Interference Cancellation and Suppression for UMTS
|
TR
|
13.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.766/25766-d10.zip
|
The study on network-assisted interference cancellation and suppression for UMTS has as a target to investigate the potential solutions in the areas of mechanisms for offloading, CQI mismatch issue, and signaling of parameters for UEs with NAICS capability and enhanced techniques , including considerations to minimize the impact on physical layer and legacy terminals and networks. [2].
|
28.821
|
Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.821/28821-d00.zip
|
The present document is the result of the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules.
Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original in ([9]), for comparison with the corresponding TMF version.
Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report. One of these type of changes is due to the fact that it is not allowed to use "shall" in an informative TR. However, in order to preserve the original intention of "must" and "shall" in the original JWG document and distinguish it from other places where "should" has been used (in case it is decided in the future to transform the TR into a TS), the use of "shall" is marked in italics font as "shall".
The JWG on Model Alignment work has chosen UML to capture behaviour of systems/entities under management.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of JWG Model Alignment work. This paper documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by JWG Model Alignment work. Collectively, this set of notations and model elements is called the FMC (developed by the Converged Management of Fixed/Mobile Networks project) Model Repertoire.
JWG Model Alignment specifications shall employ the UML notation and model elements of this repertoire. In the course of the JWG Model Alignment work, JWG Model Alignment group may modify (add, delete, modify) UML notation and model elements of this repertoire when necessary.
|
29.810
|
Study on Diameter load control mechanisms
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.810/29810-d00.zip
|
The present document investigates possible enhancements of the Diameter base protocol (IETF RFC 6733 [2]) and existing Diameter applications to support load control mechanisms in 3GPP core networks.
This work is based on the related work done in the IETF Diameter Maintenance and Extensions (DiME) working group. The Diameter overload control work and specifications done in IETF (e.g. IETF RFC 7068 [3] and IETF RFC 7683 [4]) and 3GPP will be taken into account.
This study covers:
- the identification of the set of requirements for load information exchange over Diameter based signalling interfaces used in 3GPP core networks, compared to those already expressed in IETF RFC 7068 [3] and any other requirements specified by the DiME working group;
- the evaluation of the IETF solution for load information exchange and applicability to 3GPP;
- possible enhancements specific to 3GPP;
- the identification of the 3GPP interfaces as possible candidates for the support of the load information exchange.
The results of this study will contribute to and rely on the work done within the IETF DiME working group on Diameter load control. Objective is to use the solution(s) that will be defined for Diameter load control by IETF DiME for 3GPP Diameter based networks and to avoid 3GPP specific enhancements.
Depending on this study outputs, normative work may be required to support load control mechanisms over Diameter-based 3GPP interfaces and applications.
|
29.812
|
Study on SCC AS Restoration
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.812/29812-d00.zip
|
The present document contains a detailed description of the SCC AS restoration procedure to be used in the eSRVCC network specially. The purpose of the SCC AS restoration procedure, as described in the present document, is to ensure that the originating or terminating session is continued or resumed as soon as possible when some the SCC AS in the SCC AS pool is out of service. The document defines the SCC AS failure scenarios, possible solutions and solution analysis. For the related procedure and functionality of S-CSCF, SCC AS, ATCF and HSS in the IMS and eSRVCC environment, it is based on the requirement in 3GPP related specifications
As the introduction of eSRVCC, the SCC AS shall exchange eSRVCC related parameters with ATCF and HSS during initial registration and re-registration procedures as described in 3GPP TS 24.237 [2], which is different from all other ASs.
i) ATCF reports its ATCF-Management-URI and ATCF-Path-URI towards the SCC AS, and the SCC AS stores it for later routing of MESSAGE.
ii) SCC AS shall send MESSAGE to ATCF with its own ATU-STI based on ATCF-Management-URI received, in order to ensure the routing of eSRVCC procedure triggered by ATCF later.
iii) SCC AS shall also update the received ATCF-Path-URI of ATCF towards HSS, HSS forwards it to MME, and stores it for subscriber downloading to SCC AS later.
The present document analysis SCC AS failure implications in eSRVCC network, it studies possible solutions and determines whether any should be standardize.
|
29.819
|
Study on impacts of the Diameter Base Protocol specification update.
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.819/29819-d00.zip
|
The IETF RFC 3588 [2] specifying the Diameter base protocol has been obsoleted by the IETF RFC 6733 [3]. This new version of the IETF RFC is not a new version of the Diameter base protocol but a specification update intended to fix issues discovered after early implementations of the protocol.
The aim of the Technical Report is to:
- appraise the differences between the IETF RFC 6733 [3] and the IETF RFC 3588 [2];
- analyze the possible impacts on the 3GPP specifications relying on the Diameter base protocol and then;
- provide guidelines regarding a general update of the normative reference for Diameter base protocol.
|
29.811
|
Study on EPC signalling improvements for race scenarios
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.811/29811-d00.zip
|
The present document analyses various EPC race conditions scenarios and scenarios with hanging session or bearer contexts in EPC nodes, and assesses whether to improve the existing protocols and/or specifications for effective handling of these scenarios. The specification updates, if needed, may consist in EPC (GTP-C, PMIP and/or Diameter) signalling improvements, recommendations on how to minimize the occurrences of the issues, and/or clarifications on how the EPC nodes should behave in these scenarios.
|
29.813
|
Study on S6a/S6d Shared Data Update
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.813/29813-d00.zip
|
The present document analyses the scenarios where permanent subscription data that are shared by multiple subscribers (e.g. MTC UEs) are modified by administration means in the HSS. Existing mechanisms in 3GPP networks to convey the change of subscription data to relevant MMEs/SGSNs and their drawbacks are outlined and possible solutions avoiding such drawbacks are discussed.
The recommendation of the document is used to decide whether it is required to standardize any solution, and which is the final preferred solution if further standardization is needed.
|
29.826
|
P-CSCF restoration enhancements for WLAN
|
TR
|
13.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.826/29826-d10.zip
|
The present document analyses P-CSCF restoration enhancements for WLAN. After reviewing existing P-CSCF restoration with their limitations, it defines the objectives to fulfil and proposes solutions addressing trusted WLAN using S2a interface and untrusted WLAN using S2b interface. The enhancements refer to and complement the HSS based and PCRF based solutions for 3GPP accesses specified in Rel12 and described in 3GPP TS 23.380 [2].
|
31.829
|
Conformance requirements for IP Multimedia Services Identity Module (ISIM) application test specification
|
TR
|
13.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.829/31829-d00.zip
|
The present document objective is to develop a technical report listing the conformance requirements extracted from TS 31.103. This technical report will then be a basis for a gap analysis of test coverage and the subsequent development of test cases to verify the conformance of Terminals with features for the ISIM application.
The conformance requirements should allow:
• Ensuring that content of the ISIM when available is read and used by the ME
• Reusing of existing test specifications in 3GPP
• Providing recommendations when necessary to fulfil the test purpose
|
32.151
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
|
TS
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-d00.zip
|
The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series.
|
32.152
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
|
TS
|
13.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-d20.zip
|
3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
|
32.842
|
Telecommunication management; Study on network management of virtualized networks
|
TR
|
13.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.842/32842-d10.zip
|
The present document studies the network management of virtualized 3GPP specified core networks based on the architectural framework in ETSI GS NFV-MAN 001 [2]. It studies the network management of mobile networks that include virtualized core networks functions.
It also identifies the potential impacts on the existing 3GPP management architecture and to propose potential solutions for the network management of fully virtualized networks and mixed networks.
The objectives of this study are:
- Study the use cases and concepts for the network management of virtualized networks, which are applicable to 3GPP, taking into account the relevant use cases from ETSI.
- Analyse and classify the network management scenarios when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Analyse and classify the network management scenarios when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks). Study whether or not a single management system for mixed networks is required.
- Identify the potential impacts on the existing 3GPP Management reference model.
- Analyse the existing 3GPP Management reference model, interfaces, protocols and procedures to determine what can be re-used, adapted or extended and whether new IRPs are needed for network management of virtualized networks.
- Propose enhancements or extensions to the 3GPP Management reference model, if an impact is foreseen.
- If needed, solution(s) for a single management system for mixed networks should be studied.
- Provide recommendations for the standardization of the network management of fully virtualized networks and mixed networks, based on the result of the analysis and the potentially identified impacts, enhancements or extensions.
|
32.849
|
Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-d00.zip
|
The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues.
|
32.861
|
Telecommunication management; Study on application and partitioning of Interface N (Itf-N)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.861/32861-d00.zip
|
The present document examines IRP requirements selected from existing IRPs' requirement and identifies one or more subsets of these requirements. It also studies the grouping of IRP functionality to recommend which functionality is needed in a network management context to satisfy every given subset of requirements.
|
32.843
|
Telecommunication management; Charging management; Study on Inter-Public-Land-Mobile-Network (PLMN) Packet Switched (PS) domain online charging
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.843/32843-d00.zip
|
The present document studies PS domain Online Charging in a roaming context, when the Gateway node implementing the IP access to the PDN for data traffic, pertains to the VPLMN, whereas the Online Charging System (OCS) pertains to the HPLMN.
The study will focus, in a first phase, on high level scenarios for Flow Based Charging, relying on defined TS 23.203 [207] PCC roaming architectures with Gy crossing PLMNs, in order to investigate the following aspects:
- Information availability in both PLMNs
- Inter-PLMN connection mechanisms for Diameter messages
- Impacts on Inter-operator charging
- Whether a "proxy OCS" is needed
The two following configurations will be addressed:
- Gy between OCS residing in HPLMN and PCEF located in PGW VPLMN, for Local Breakout Roaming configuration defined by TS 23.401 [208] and TS 23.203 [207].
- Gy between OCS residing in HPLMN and PCEF located in IP-Edge fixed broadband access owned by a Convergent fixed-mobile VPLMN, for Non Seamless WLAN Offload (NSWO) 3GPP UEs traffic defined by annex S of TS 23.203 [207].
During this first phase, the study will also investigate a basic set of Online Charging features and parameters, to be used in an inter-PLMN situation.
Based on conclusions and recommendations for the first phase, the second phase of the study will address the inter-PLMN Gyn Reference Point for the support of Application Based Charging.
|
32.863
|
Telecommunication management; Fixed Mobile Convergence (FMC) metadefinitions for measurements and Key Performance Indicators (KPIs)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.863/32863-d00.zip
|
The present document defines the metadata for Performance Management (PM) performance measurements (KPIs/counters). The definition would enforce consistency in description/definition of all standardized performance measurements (counters/KPIs) by various SDOs and organizations (or Multi-SDO) involved in the Management of Converged Networks [6]. This consistency would facilitate encoding and decoding of performance measurements (counters/KPIs) exchanged (via management protocols) and/or stored in (database or files).
The metadata related to PM operations/notifications is not part of this PM measurement metadata.
The present document takes into account the recommendations from the Fixed Mobile Convergence (FMC) model repertoire [2] developed by the Multi-SDO JWG on Model Alignment.
|
33.179
|
Security of Mission Critical Push To Talk (MCPTT) over LTE
|
TS
|
13.12.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.179/33179-dc0.zip
|
The present document specifies the security architecture, procedures and information flows needed to protect the mission critical push to talk (MCPTT) service. The architecture includes mechanisms for authentication, protection of MCPTT signalling and protection of MCPTT media. Security for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The functional architecture for MCPTT is defined in 3GPP TS 23.179 [2], the corresponding service requirements are defined in 3GPP TS 22.179 [3].
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. As the security model is based on the public safety environment, some security features may not be applicable to MCPTT for commercial purposes.
|
33.832
|
Study on IMS Enhanced Spoofed Call Prevention and Detection
|
TR
|
0.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.832/33832-030.zip
|
The present document evaluates the IETF STIR working group active drafts for use in 3GPP networks for spoofed call detection and make recommendations on what aspects of IETF STIR active drafts should be incorporated into 3GPP IMS security specifications.
Additionally 3GPP technology specific aspects not considered or addressed in the IETF STIR Working Group will be identified and studied such as service interactions and deployment scenarios including (but not limited to):
• * Roaming
• * Business line trunking/PBX
• * CS to IMS transition scenarios
|
33.860
|
Study on Enhanced General Packet Radio Service (EGPRS) access security enhancements with relation to cellular Internet of Things (IoT)
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.860/33860-d10.zip
|
The present document contains a study of the EGPRS access security in relation to cellular IoT, and an evaluation of possible technical security enhancements needed to support such services. Different possible deployment scenarios for Cellular IoT, and related stage 2 solutions are being studied in TR 45.820 [2].
The scope of this study is limited to investigate the feasibility of improving the access security aspects of Gb mode. In more detail, the scope includes:
1) Investigate potential security threats, such as man in the middle attacks.
2) Investigate potential security enhancements between the UE and SGSN to mitigate said threats.
3) Define what security procedures and security algorithms that are recommended to be used by for Cellular IoT devices in Gb mode. This may be procedures and algorithms already specified in earlier 3GPP releases or it could be new procedures and algorithms being introduced as part of this feasibility study.
4) The potential security enhancements as part of this study item should aim at minimising the impacts to the GPRS core network.
|
33.872
|
Study on security enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.872/33872-d00.zip
|
The present document contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).
In particular, the present document focuses on:
• Support for end to end WebRTC security, subject to regulatory constraints, that avoids conversion between WebRTC and IMS security protocols , including the feasibility of end to end security aspects
• Third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block where the associated subscription corresponds to a class of users supported by the WebRTC environment (e.g., enterprise associates) rather than a single end user
|
33.833
|
Study on security issues to support Proximity Services (ProSe)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-d00.zip
|
The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document.
|
33.897
|
Study on isolated E-UTRAN operation for public safety; Security aspects
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.897/33897-d10.zip
|
The present document contains the results of a Stage 2 study and evaluation of possible 3GPP security solutions in support of Isolated E-UTRAN Operation for Public Safety (IOPS). The solutions are based on the Stage 1 requirements in 3GPP TS 22.346 [2], the architectural enhancements to support IOPS presented in the Stage 2 study report 3GPP TR 23.797 [3] and resulting informative Annex K in 3GPP TS 23.401 [10]. For the current release of specification the solution in 3GPP TS 23.401 [10] is based on a Local EPC with no backhaul.
The present document identifies key issues, security threats, deduces security requirements and presents proposed security solutions for IOPS.
Throughout this Technical Report the terms 'IOPS network' and 'Isolated E-UTRAN' are used synonymously.
|
33.879
|
Study on security enhancements for Mission Critical Push To Talk (MCPTT) over LTE
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.879/33879-d10.zip
|
The present document contains a study of the security aspects of the Mission-Critical Push-To-Talk (MCPTT) service and its interaction with the network. This includes an analysis of the threats to the service, the security requirements to mitigate those threats and an evaluation of possible technical solutions designed to meet the security requirements of the service.
The Stage 1 requirements for the service are defined in TS 22.179 [2]. An evaluation of Stage 2 architectural solutions for MCPTT is performed in TR 23.779 [3] and TS 23.179 [10]. This study will include consideration of relevant 3GPP specifications, particularly for ProSe (TS 33.303 [4], TS 23.303 [5]) and GCSE (TS 23.468 [6]).
The focus of the present document is to support public-safety use cases of MCPTT. Commercial scenarios are not specifically considered and some features may not be applicable to them.
|
33.889
|
Study on security aspects of Machine-Type Communications (MTC) architecture and feature enhancements
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.889/33889-d00.zip
|
The present document captures requirements, solution alternatives, evaluations and conclusions for the SA2-led Rel-13 Features:
• GROUPE (Group based Enhancements) [4],
• MONTE (Monitoring Enhancements) [5] and
• AESE (Architecture Enhancements for Service Capability Exposure [3].
The present document captures the conclusions of the study on security and privacy implications for the requirements identified in Stage 1 and Stage 2 specifications for the above mentioned Rel-13 MTC features.
Based on the outcome of the present document, any new normative text will be incorporated in TS 33.187 [2] and/or suitable existing SA3 specifications.
Editor’s Note: SA3 is supposed to work only on security solutions for architectural solutions that are covered in SA2 Rel-13 TRs TR 23.769[4], TR 23.789[5], TR 23.708 [3].
|
36.789
|
Multi-node tests for Licence-Assisted Access (LAA)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.789/36789-d00.zip
|
The present document describes the multi-node tests for Rel-13 LAA BSs and other wireless systems operating in unlicensed spectrum. In particular, the report documents how to conduct multi-node tests involving two Rel-13 LAA BSs or one Rel-13 LAA BS and one other wireless system, e.g. IEEE 802.11 system to make sure that the two systems can coexist in the same unlicensed spectrum. This document aims to provide an evaluation methodology for multi-node coexistence between Rel-13 LAA BSs and other wireless systems.
|
36.825
|
Feasibility study on possible additional configuration for LTE TDD
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.825/36825-d00.zip
|
The objective of the study is to evaluate issues related to the potential introduction of the following additional configuration(s) for LTE TDD; 10:0:0 and 9:1:0 (DL:Sp:UL). This includes:
- Identify the scenario(s), frequency band(s), and use cases(s) of the possible additional TDD configuration(s)
- Coexistence with adjacent standalone LTE TDD operations in the same band
- To be compared with the coexistence between intra-band adjacent LTE TDD operations using different UL/DL configurations
- Evaluation of the potential benefits and drawbacks of the additional TDD configuration(s) and possible solutions to mitigate the potential drawbacks
- Any other relevant ecosystem aspect(s)
- Compare the option of using 10:0:0 and/or 9:1:0 TDD configuration for a TDD spectrum against the alternative of converting the TDD spectrum to FDD supplemental DL spectrum
NOTE: The study shall not provide any recommendation on next steps / future normative work.
|
36.833-6-42
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 42 for 3 downlinks (3DL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-6-42/36833-6-42-d00.zip
|
The present document is a technical report of the work item for LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 42 for 3 downlinks (3DL), which was approved at TSG RAN #67 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-8-41
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band non-contiguous Carrier Aggregation (CA) in Band 41 for 4 downlinks (4DL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-8-41/36833-8-41-d00.zip
|
The present document is a technical report of the LTE Advanced intra-band non-contiguous Carrier Aggregation in Band 41 for 4 DL work item which was approved at TSG RAN #66 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE TDD Band 41 for 4DL.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.844
|
Study on expansion of LTE in the 1670-1675 MHz Band for the United States to include 1670-1680 MHz Band
|
TR
|
13.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.844/36844-d20.zip
|
The present document is a technical report for “Expansion of LTE_FDD_1670_US to include 1670-1680 MHz Band for LTE in the US” study item, which was approved at 3GPP TSG RAN#59 [2]. The ID assigned to the study item is FS_LTE_FDD_1670_US. The objective of this study item is to facilitate and harmonize the characteristics and efficient use of 1670-1680MHz DL duplexed with band 24 UL for LTE FDD deployment in US. In addition to the schedule and status of the study items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.849
|
Study on Advanced Wireless Services (AWS) extension band for LTE
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.849/36849-d00.zip
|
The present document is a technical report for the study item on the extension of the AWS Band for LTE approved at TSG RAN#64. The objective of the study item is to evaluate the technical feasibility of different band plans as shown in the study item description.
|
36.852-13
|
LTE Advanced inter-band Carrier Aggregation (CA) (2DL/1UL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.852-13/36852-13-d00.zip
|
The present document is a technical report for Inter-band Carrier Aggregation for 2DL/1UL under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation (2DL/1UL) requirements for the Rel-13 band combinations in table 1-1.
Table 1-1: Release 13 inter-band carrier aggregation combinations (2DL/1UL)
WI/SI code
WI title
Class
LTE_CA_B2_B28
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 28
A1
LTE_CA_B3_B31
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 31
A2
LTE_CA_B4_B28
LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 28
A2
LTE_CA_B7_B22
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 22
A5
LTE_CA_B19_B28
LTE Advanced inter-band Carrier Aggregation of Band 19 and Band 28
A3
LTE_CA_B20_B31
LTE Advanced inter-band Carrier Aggregation of Band 20 and Band 31
A3
LTE_CA_B25_B26
LTE Advanced inter-band Carrier Aggregation of Band 25 and Band 26
A1
LTE_CA_B5_B7_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 7
A1
LTE_CA_700EU_B20
European 700 Supplemental Downlink band (738-758 MHz) in E-UTRA and LTE Carrier Aggregation (2DL/1UL) with Band 20
A3
FS_LTE_CA_B20_B28
Study on LTE Advanced inter-band Carrier Aggregation of Band 20 and Band 28
A3
LTE_CA_B4_B12_BWset2
Additional bandwidth combination set 2 for LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 12
A2
LTE_CA_B2_B12_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 12
A1
The scope of the report also covers the 2 DL fallback modes for the 3 DL Carrier Aggregation combinations with single UL configuration [2]. These 3 DL/1UL combinations (with 2 DL fallback modes) are listed in table 1-2. In addition, the report also covers the LTE TDD-FDD joint operation including Carrier Aggregation combinations [3], captured in Table 1-3. In addition, the report also covers the 2 DL fallback modes for the 4 DL Carrier Aggregation combinations with single UL configuration. These 4 DL/1UL combinations (with 2 DL fallback modes) are listed in table 1-4.
Table 1-2: Release 13 inter-band carrier aggregation combinations (3 DL/1UL)
WI code
WI title
LTE_CA_B2_B5_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 5 and Band 29
LTE_CA_B38_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 38, Band 40 and Band 40
LTE_CA_B3_B7_B28
LTE Advanced 3 Band Carrier Aggregation (3DL) of Band 3, Band 7 and Band 28
LTE_CA_B1_B8_B28
LTE Advanced 3 band Carrier Aggregation (3DL/1UL) of Band 1, Band 8 and Band 28
LTE_CA_B3_B20_B32
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 20 and Band 32
LTE_CA_B4_B4_B7_BWset
Additional bandwidth combination set for LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 4, Band 4 and Band 7
Table 1-3: Release 13 inter-band carrier aggregation combinations (LTE TDD-FDD joint operation)
WI code
WI title
Class
LTE_CA_B1_B40
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 40
-
LTE_CA_B3_B40
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 40
A3
LTE_CA_B21_B42
LTE Advanced inter-band Carrier Aggregation of Band 21 and Band 42
A5
LTE_CA_B7_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 7, Band 40 and Band 40
-
LTE_CA_B5_B40
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 40
-
LTE_CA_B20_B40
LTE Advanced inter-band Carrier Aggregation of Band 20 and Band 40
-
LTE_CA_B3_B38
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 38
-
LTE_CA_B3_B41
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 41
-
LTE_CA_28A-40C
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 28, Band 40 and Band 40
-
LTE_CA_28A-41C
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 28, Band 41 and Band 41
-
LTE_CA_28A-42C
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 28, Band 42 and Band 42
-
LTE_CA_B7_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 7, Band 42 and Band 42
-
LTE_CA_B20_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 20, Band 42 and Band 42
-
LTE_CA_B5_B38
LTE Advanced inter-band Carrier Aggregation for Band 5 and Band 38
-
LTE_CA_B7_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 42 and Band 42
-
LTE_LAA-Core
Licensed-Assisted Access to Unlicensed Spectrum
A4
LTE_LAA-Core
Licensed-Assisted Access to Unlicensed Spectrum
A2
LTE_CA_B3_B8_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 3, Band 8 and Band 40
LTE_CA_B2_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 7 and Band 12
Table 1-4: Release 13 inter-band carrier aggregation combinations (4DL/1UL)
WI code
WI title
LTE_CA_B4_B5_B12_B12
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 4, Band 5, Band 12 and Band 12
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.853-13
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced 3 Band Carrier Aggregation (CA) (3DL/1UL)
|
TR
|
13.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.853-13/36853-13-d10.zip
|
The present document is a technical report for 3DL Inter-band Carrier Aggregation under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements.
The present document covers relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements for the Rel-13 band combinations in Table 1-1, Table 1-2 and Table 1-3.
Table 1-1: Release 13 3DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_B3_B3_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 8
LTE_CA_B38_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 38, Band 40 and Band 40
LTE_CA_B1_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 41 and Band 41
LTE_CA_B8_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 8, Band 41 and Band 41
LTE_CA_B26_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 26, Band 41 and Band 41
LTE_CA_B7_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 40 and Band 40
LTE_CA_B1_B7_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 28
LTE_CA_B1_B3_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 7
LTE_CA_B2_B2_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2 and Band 12
LTE_CA_B1_B3_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 28
LTE_CA_B3_B7_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 28
LTE_CA_B3_B7_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 7
LTE_CA_B7_B7_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 7 and Band 28
LTE_CA_B3_B7_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 8
LTE_CA_B1_B3_B3
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 3
LTE_CA_B1_B8_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 8 and Band 28
LTE_CA_B2_B5_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 29
LTE_CA_B3_B3_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 5
LTE_CA_B3_B8_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 8 and Band 28
LTE_CA_B3_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 40 and Band 40
LTE_CA_B8_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 8, Band 42 and Band 42
LTE_CA_B21_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 21, Band 42 and Band 42
LTE_CA_B41_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 41, Band 42 and Band 42
LTE_CA_B1_B3_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 42
LTE_CA_B1_B19_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 19 and Band 42
LTE_CA_B1_B21_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 21 and Band 42
LTE_CA_B3_B19_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 19 and Band 42
LTE_CA_B7_B20_B38
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 20 and Band 38
LTE_CA_B19_B21_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 19, Band 21 and Band 42
LTE_CA_B1_B19_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 19 and Band 28
LTE_CA_B1_B3_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 40
LTE_CA_B1_B8_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 8 and Band 40
LTE_CA_B3_B8_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 8 and Band 40
LTE_CA_B28_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 28, Band 40 and Band 40
LTE_CA_B1_B8_B11
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 8 and Band 11
LTE_CA_B3_B7_B38
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 38
LTE_CA_B3_B20_B32
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 20 and Band 32
LTE_CA_B7_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 42 and Band 42
LTE_CA_B20_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 20, Band 42 and Band 42
LTE_CA_B28_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 28, Band 41 and Band 41
LTE_CA_B28_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 28, Band 42 and Band 42
LTE_CA_B1_B11_B18
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 11 and Band 18
LTE_CA_B4_B4_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 7
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
LTE_CA_B3_B28_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 28 and Band 40
LTE_CA_B3_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 41 and Band 41
LTE_CA_B3_B41_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 41 and Band 42
LTE_CA_B5_B40_B40
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 5, Band 40 and Band 40
LTE_LAA-Core
Licensed-Assisted Access to Unlicensed Spectrum
LTE_CA_B2_B4_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 7
LTE_CA_B2_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 7 and Band 12
The present document also covers the 4DL fallback modes for the 4DL Carrier Aggregation combinations with single UL configuration. These 4DL/1UL combinations are listed in Table 1-2.
Table 1-2: Release 13 inter-band carrier aggregation combinations (4DL/1UL)
WI code
WI title
LTE_CA_B2_B2_B4_B4
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 4 and Band 4
LTE_CA_B2_B4_B12_B30
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 12 and Band 30
LTE_CA_B2_B2_B5_B30
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 5 and Band 30
LTE_CA_B2_B2_B12_B30
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 12 and Band 30
LTE_CA_B1_B3_B7_B8
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 1, Band 3, Band 7 and Band 8
LTE_CA_B2_B2_B29_B30
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 29 and Band 30
LTE_CA_B4_B4_B5_B29
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 4, Band 4, Band 5 and Band 29
LTE_CA_B1_B3_B5_B40
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 1, Band 3, Band 5 and Band 40
LTE_CA_B41_B41_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 41, Band 41, Band 42 and Band 42
LTE_CA_B4_B4_B29_B30
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 4, Band 4, Band 29 and Band 30
The present document also covers the 5DL fallback modes for the 5DL Carrier Aggregation combinations with single UL configuration. These 5DL/1UL combinations are listed in Table 1-3.
Table 1-3: Release 13 inter-band carrier aggregation combinations (5DL/1UL)
WI code
WI title
LTE_CA_B1_B3_B7_B7_B28
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) of Band 1, Band 3, Band 7, Band 7 and Band 28
LTE_CA_B3_B3_B7_B7_B28
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) of Band 3, Band 3, Band 7, Band 7 and Band 28
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.854-13
|
LTE Advanced 4 Band Carrier Aggregation (CA) (4DL/1UL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.854-13/36854-13-d00.zip
|
The present document is a technical report for 4DL Inter-band Carrier Aggregation under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address 4DL Inter-band Carrier Aggregation requirements.
The present document covers relevant background information and studies in order to address 4DL Inter-band Carrier Aggregation requirements for the Rel-13 band combinations in Table 1-1.
The present document is divided in two different parts:
- General part: this part covers BS and UE specific which is band combination independent.
- Specific band combination part: this part covers each band combination and its specific issues independently from each other (i.e. one subclause is defined per band combination).
Table 1-1: Release 13 4DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_1A-3A-7A-8A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 1, Band 3, Band 7 and Band 8
LTE_CA_2A_2A_4A_4A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 2, Band 2, Band 4 and Band 4
LTE_CA_2A_2A_4A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 2, Band 2, Band 4 and Band 12
LTE_CA_2A-2A-5A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 5 and Band 30
LTE_CA_2A-2A-12A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 12 and Band 30
LTE_CA_2A-2A-29A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 29 and Band 30
LTE_CA_2A-4A-4A-12A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 2, Band 4, Band 4 and Band 12
LTE_CA_2A-4A-12A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 12 and Band 30
LTE_CA_2A-4A-29A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 29 and Band 30
LTE_CA_2A-4A-5A-30A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 5 and Band 30
LTE_CA_25A-41A-41A-41A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 25, Band 41, Band 41 and Band 41
LTE_CA_2A-4A-5A-29A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 5 and Band 29
LTE_CA_B1_B3_B19_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 1, Band 3, Band 19 and Band 42
LTE_CA_B1_B3_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 1, Band 3, Band 42 and Band 42
LTE_CA_B1_B19_B21_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 1, Band 19, Band 21 and Band 42
LTE_CA_B1_B19_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 1, Band 19, Band 42 and Band 42
LTE_CA_B1_B21_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 1, Band 21, Band 42 and Band 42
LTE_CA_B3_B19_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 3, Band 19, Band 42 and Band 42
LTE_CA_B19_B21_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) for Band 19, Band 21, Band 42 and Band 42
LTE_CA_B41_B41_B42_B42
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 41, Band 41, Band 42 and Band 42
LTE_CA_2A_2A_4A_5A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 4 and Band 5
LTE_CA_2A_2A_5A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 5 and Band 12
LTE_CA_2A_2A_12A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 2, Band 12 and Band 12
LTE_CA_2A_4A_5A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 5 and Band 12
LTE_CA_2A_4A_12A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 5, Band 12 and Band 12
LTE_CA_2A_5A_12A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 5, Band 12 and Band 12
LTE_CA_4A_4A_5A_12A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 4, Band 4, Band 5 and Band 12
LTE_CA_2A_4A_4A_5A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 4 and Band 5
LTE_CA_B39_B41_B41_B41
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 39, Band 41, Band 41 and Band 41
LTE_CA_B39_B39_B41_B41
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 39, Band 39, Band 41 and Band 41
LTE_CA_B1_B3_B5_B40
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 1, Band 3, Band 8 and Band 40
LTE_CA_B3_B28_B40_B40
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 3, Band 28, Band 40 and Band 40
LTE_CA_B28_B40_B40_B40
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 28, Band 40, Band 40 and Band 40
LTE_CA_B3_B7_B7_B28
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 3, Band 7, Band 7 and Band 28
CA_2A-4A-12B
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 2, Band 4, Band 12 and Band 12
CA_4A-4A-12B
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 4, Band 4, Band 12 and Band 12
CA_4A-5A-12B
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 4, Band 5, Band 12 and Band 12
CA_1A-3A-7A-8A
LTE Advanced 4 Band Carrier Aggregation (4DL/1UL) of Band 1, Band 3, Band 7 and Band 8
CA_4A_4A_5A_30A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 4, Band 4, Band 5 and Band 30
CA_4A_4A_12A_30A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 4, Band 4, Band 12 and Band 30
CA_4A_4A_29A_30A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 4, Band 4, Band 29 and Band 30
CA_1A-3A-5A-40A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 1, Band 3, Band 5 and Band 40
CA_1A-3A-8A-40A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 1, Band 3, Band 8 and Band 40
CA_1A-3A-7A-28A
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) of Band 1, Band 3, Band 7, Band 7 and Band 28
CA_3C-7A-28A
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) of Band 3, Band 3, Band 7, Band 7 and Band 28
LTE_LAA-Core
Licensed-Assisted Access to Unlicensed Spectrum
CA_2A-4A-7A-12A
LTE Advanced 4 Band Carrier Aggregation (4DL) of Band 2, Band 4, Band 7 and Band 12
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.855
|
Feasibility of positioning enhancements for E-UTRA
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.855/36855-d00.zip
|
Positioning mechanisms were specified in 3GPP as a key feature for E-UTRA networks since Release 9, e.g. OTDOA, E-CID etc. They are not only used in helping meet regulatory requirements, but also utilized with increasing importance to enable all kinds of location based applications.
The proliferation of heterogeneous network deployments brings some challenges also in the area of efficient terminal positioning and calls for the study of enhanced mechanisms and positioning performance requirements.
The addition of multiple nodes in heterogeneous networks can improve the position accuracy remarkably if the specificities of such deployments are taken into account in the positioning mechanisms. Some examples include the support of several transmission points with identical cell IDs and improved support for positioning in carrier aggregation.
Furthermore, the accuracy of current positioning mechanisms and in particular OTDOA and E-CID based on UE Rx-Tx time difference measurement is only defined for limited scenarios:
• Limited channel bandwidth for the cells to be measured (reference and neighbour cells)
• Tests defined assuming single Tx antenna. Practical network might have Tx diversity on antenna port 6 which is used for RSTD measurements
It is desirable to study the possibility of enhanced accuracy for other practical deployment scenarios.
The present document is the Technical Report for the Study Item on positioning enhancements for E-UTRA.
|
36.857-13
|
LTE Advanced 5 Band Carrier Aggregation (CA) (5DL/1UL)
|
TR
|
13.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.857-13/36857-13-d10.zip
|
The present document is a technical report for 5DL Inter-band Carrier Aggregation under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address 5DL Inter-band Carrier Aggregation requirements.
The present document covers relevant background information and studies in order to address 5DL Inter-band Carrier Aggregation requirements for the Rel-13 band combinations in Table 1-1.
Table 1-1: Release 13 5DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_B1_B3_B19_B42_B42
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) for Band 1, Band 3, Band 19, Band 42 and Band 42
LTE_CA_B1_B19_B21_B42_B42
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) for Band 1, Band 19, Band 21, Band 42 and Band 42
LTE_CA_B1_B3_B7_B7_B28
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) for Band 1, Band 3, Band 7, Band 7 and Band 28
LTE_CA_B3_B3_B7_B7_B28
LTE Advanced 5 Band Carrier Aggregation (5DL/1UL) for Band 3, Band 3, Band 7, Band 7 and Band 28
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.859
|
Study on Downlink Multiuser Superposition Transmission (MUST) for LTE
|
TR
|
13.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.859/36859-d00.zip
|
The present document captures the results and findings of the study item “Study on Downlink Multiuser Superposition Transmission” [2][3]. The purpose of this TR is to document the identified LTE enhancements to enable downlink multiuser superposition transmission and corresponding evaluation results in the target deployment scenarios.
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 defines evaluation methodology and target deployment scenarios for the study on downlink multiuser superposition transmission.
This document identifies LTE enhancements and potential specification impacts to enable downlink multiuser superposition transmission.
This document contains an assessment of feasibility and performance of the identified LTE enhancements to enable downlink multiuser superposition transmission.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.860-13
|
LTE-Advanced dual uplink inter-band Carrier Aggregation (CA)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.860-13/36860-13-d00.zip
|
The present document is a technical report for LTE Advanced Dual Uplink Inter-band Carrier Aggregation under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Uplink Inter-band Carrier Aggregation requirements.
|
36.861
|
Technical Report for Study Item: Study on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.861/36861-d00.zip
|
The present document contains the result of the Study item on LTE FDD in the bands 1980-2010 MHz and 2170-2200 MHz, which has been approved in RP-121420 [5] at TSG RAN#57, Sep 2012.
The objective of this study is to facilitate and harmonize the efficient use of these bands for terrestrial IMT, especially LTE, for Korea and other applicable countries in Region 3.
|
36.862
|
Technical Report for 2 GHz Band in Region 1
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.862/36862-d00.zip
|
The present document is work item technical report for 2 GHz LTE Band in Region 1, which was approved at TSG RAN #64 [2]. The present document provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.867
|
Study on LTE DL 4 Rx antenna ports
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.867/36867-d00.zip
|
The present document is the Technical Report for the Study Item to identify the scope and WI objectives for LTE DL 4 Rx AP in Rel-13.
|
36.869
|
Advanced Wireless Services (AWS) extension band for LTE
|
TR
|
13.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.869/36869-d10.zip
|
The present document a technical report for the AWS extension band for LTE work item. The band is specified as 70+90 MHz (1710 - 1780 MHz / 2110 - 2200 MHz) with fixed duplex spacing. Intra-band DL CA is also included as part of the WI.
|
36.833-5-42
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 42 for 3 downlinks (3DL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-5-42/36833-5-42-d00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 42 for 3DL WI which was approved at TSG RAN #65 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 42 for 3DL.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.833-7-42
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 42 for 4 downlinks (4DL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-7-42/36833-7-42-d00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 42 for 4DL WI which was approved at TSG RAN #67 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 42 for 4DL.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.802
|
Evolved Universal Terrestrial Radio Access (E-UTRA); NB-IOT; Technical Report for BS and UE radio transmission and reception
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.802/36802-d00.zip
|
The present document summarizes the studies of radio requirements for BS and UE radio transmission and reception as part of the work item on Narrowband Internet of Things (NB-IoT).
|
36.870
|
Study on new Advanced Wireless Services (AWS)-3/4 Band for LTE
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.870/36870-d00.zip
|
The purpose of the present document is to study the feasibility of specifying two duplex spacings for a new asymmetrical LTE Band (1695-1710 MHz UL & 1995-2020 MHz DL) in order to provide deployment flexibility in protecting primary Federal and non-Federal Meteorological Satellite (MetSat) receiver sites and addressing market license variations.
|
36.875
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Extension of dual connectivity in E-UTRAN
|
TR
|
13.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.875/36875-d10.zip
|
The present document provides descriptions of requirements and solutions with regards to extension of dual connectivity in Rel-13.
|
36.876
|
Study on further enhancements of small cell high layer aspects for LTE
|
TR
|
13.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.876/36876-d00.zip
|
The present document is related to the technical report of the study item "Study on further enhancement of small Cell high layer aspects for LTE" (RP-142283 [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.882
|
Study on regulatory aspects for flexible duplex for E-UTRAN
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.882/36882-d00.zip
|
The objectives of this study are:
Identify and document potential regional/band-specific regulatory possibilities/constraints for the use cases of utilizing UL spectrum for transmission from the network to UEs, including aspects such as Tx power levels, modulation schemes, type of transmitting nodes, etc.
|
36.883
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Introducing UL 64QAM
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.883/36883-d00.zip
|
The present document is the Technical Report for the work Item on UE core requirements for uplink 64 QAM in LTE.
|
36.879-13
|
LTE Advanced 3DL/2UL inter-band Carrier Aggregation (CA)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.879-13/36879-13-d00.zip
|
The present document is a technical report for LTE Advanced 2ULs and 3DLs Carrier Aggregation under Rel-13 time frame. The purpose is to gather the relevant background information and studies in order to address 2Uls and 3DLs Carrier Aggregation requirements.
This TR covers relevant background information and studies core & performance requirements for the Rel-13 band combinations in Table 1-1 and Table 1-2.
Table 1-1: Release 13 2ULs and 3DLs inter-band carrier aggregation combinations
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
CA_1A-3A,
CA_1A-5A,
CA_3A-5A
1
Yes
Yes
Yes
Yes
50
0
3
Yes
Yes
Yes
Yes
5
Yes
Yes
1
Yes
Yes
40
1
3
Yes
Yes
Yes
Yes
5
Yes
Yes
CA_1A-3A-8A
CA_1A-3A,
CA_1A-8A,
CA_3A-8A
1
Yes
Yes
Yes
Yes
50
0
3
Yes
Yes
Yes
Yes
8
Yes
Yes
Yes
1
Yes
Yes
40
1
3
Yes
Yes
Yes
Yes
8
Yes
Yes
Yes
1
Yes
Yes
Yes
40
2
3
Yes
Yes
Yes
8
Yes
Yes
Yes
CA_1A-3A-19A
CA_1A-3A,
CA_3A-19A,
CA_1A-19A
1
Yes
Yes
Yes
Yes
55
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
CA_1A-5A-7A
CA_1A-7A,
CA_5A-7A,
CA_1A-5A
1
Yes
Yes
40
0
5
Yes
Yes
7
Yes
Yes
Yes
1
Yes
Yes
Yes
Yes
50
1
5
Yes
Yes
7
Yes
Yes
Yes
CA_1A-18A-28A
CA_1A-18A
CA_18A-28A
CA_1A-28A
1
Yes
Yes
Yes
Yes
45
0
18
Yes
Yes
Yes
28
Yes
Yes
1
Yes
Yes
Yes
Yes
40
1
18
Yes
Yes
28
Yes
Yes
CA_1A-19A-21A
CA_1A-19A,
CA_1A-21A,
CA_19A-21A
1
Yes
Yes
Yes
Yes
50
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_2A-4A-12A
CA_2A-4A,
CA_4A-12A
2
Yes
Yes
Yes
Yes
50
0
4
Yes
Yes
Yes
Yes
12
Yes
Yes
CA_2A-5A-13A
CA_2A-13A
2
Yes
Yes
Yes
Yes
40
0
5
Yes
Yes
13
Yes
CA_3A-7A-20A
CA_3A-7A
CA_3A-20A
CA_7A-20A
3
Yes
Yes
Yes
Yes
60
0
7
Yes
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_3A-7A-28A
CA_3A-7A
CA_7A-28A
3
Yes
Yes
Yes
Yes
60
0
7
Yes
Yes
Yes
Yes
28
Yes
Yes
Yes
Yes
CA_4A-5A-13A
CA_4A-13A
4
Yes
Yes
Yes
Yes
40
0
5
Yes
Yes
13
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: Release 13 2ULs and 3DLs mixed intra/inter band carrier aggregation combinations
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations (NOTE 4)
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_3A-7C
CA_3A-7A
CA_7C
3
Yes
Yes
Yes
Yes
60
0
7
See CA_7C Bandwidth combination set 1 in table 5.6A.1-1 [3]
CA_3C-7A
CA_3A-7A
CA_3C
3
See CA_3C Bandwidth Combination Set 0 in table 5.6A.1-1 [3]
60
0
7
Yes
Yes
Yes
Yes
CA_25A_41C
CA_41C
25
Yes
Yes
Yes
Yes
60
0
41
See CA_41C Bandwidth Combination Set 1 in Table 5.6A.1-1 [3]
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.880
|
Study on further enhancements of Minimization of Drive Tests (MDT) for E-UTRAN
|
TR
|
13.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.880/36880-d00.zip
|
The objective of the study is to investigate technical solutions for MDT enhancements, limited to aspects that can be observed at access stratum. In particular the following:
- Enhanced QoS Verification Use Case:
Study MDT measurements and procedures capabilities to support better understanding of the QoS and its limiting factors for MMTEL voice and video traffic, including:
Study necessary MDT measurements and procedures capabilities for assessing the performance of MMTEL voice and video, e.g. delay, packet loss rate of PDCP layer.
Study necessary MDT measurements and procedures capabilities for mobility performance of MMTEL voice and video (e.g. add tags to the existing RLF report in order to derive the particular MMTEL voice and video traffic failures).
Study necessary MDT measurements and procedures capabilities for identifying hotspot areas of MMTEL voice and video.
- Enhanced Coverage Optimization Use Case:
Consider provision of additional feedback from UE handling diverse capabilities that impact MDT measurement results (e.g. new type of assistance information such as IDC, etc) and analyze what benefit such information could achieve.
The present document provides descriptions and possible solutions of use cases and analysis of these solutions.
|
36.878
|
Study on performance enhancements for high speed scenario in LTE
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.878/36878-d00.zip
|
In some countries, several vehicles move with the speed over than 300km/h, e.g., Japan Tohoku Shinkansen (320km/h), German ICE (330km/h), AGV Italo (400km/h), and Shanghai Maglev (430km/h). With the increase of high speed moving environment, the demand of using mobiles in such an environment in E-UTRA is growing larger. Therefore, it is important to guarantee the performance under such environment in E-UTRA.
However, in the current 3GPP specifications, since the maximum speed guaranteed in BS performance is up to 350km/h, it would be challenging to keep up with the speed of vehicles moving around 400km/h. In addition, since the speed guaranteed in BS demodulation, UE demodulation, and UE RRM specifications are different, even though the speed up to 350km/h is guaranteed in BS specification, the same speed cannot also be ensured in UE demodulation and UE RRM specification as well. Given the fact above, it is essential to comprehensively revisit and enhance the existing requirements to ensure the system performance under high speed environment in E-UTRA.
In addition, due to different commercial network deployment scenarios of operators and surrounding environments (downtown/suburban or mountain areas), there may exist some issues/scenarios that the current specified requirements may not be able to cover and to guarantee the solid performance. Therefore, it would be worth investigating potential issues/scenarios and identifying some new requirements to ensure them from various aspects where the current requirements are missing now.
The present document is the Technical Report for the Study Item on performance enhancements for high speed scenario in LTE.
|
36.884
|
Performance requirements of MMSE-IRC receiver for LTE BS
|
TR
|
13.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.884/36884-d10.zip
|
The present document should fulfil the following objectives:
- Phase I:
- Identify target deployment scenarios and agree on relevant network parameters. Both homogeneous deployment (macro cell only) and heterogeneous deployment (co-channel between macro cell and low power node) should be considered.
- Conduct system-level simulation to determine the inter-cell interference modelling methodology and other side conditions needed for link-level simulation, and link-level simulation to evaluate gain of MMSE-IRC over baseline receiver (MMSE receiver)
- Phase II:
- LTE BS MMSE-IRC receiver is assumed as the reference receiver structure for specifying the requirements.
- Demodulation RS based MMSE-IRC receiver can be considered as baseline, and practical and realizable implementation should be taken into account.
- Specify the enhanced demodulation performance requirements for verification of BS receiver's ability on inter-cell interference suppression.
- For PUSCH, specify enhanced demodulation performance requirements based on the reference receiver.
- For PUCCH, with lower priority, determine whether to specify enhanced demodulation performance requirements based on the reference receiver.
- Specify the enhanced conformance test requirements.
Note: The enhanced demodulation performance requirements only apply to the base station capable of MMSE-IRC receiver.
|
36.889
|
Feasibility Study on Licensed-Assisted Access to Unlicensed Spectrum
|
TR
|
13.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.889/36889-d00.zip
|
The present document contains the results and findings from the study item, “Study on Licensed-Assisted Access Using LTE” [2]. The purpose of this TR is to document the identified LTE enhancements and corresponding evaluations for a single global solution framework for licensed-assisted access to unlicensed spectrum. Dual connectivity and standalone access to unlicensed spectrum are not part of the study. Therefore, for LAA operation, a carrier in an unlicensed band cannot be configured as a PCell/PSCell in this Rel-13 study.
This document addresses evaluation methodology and possible scenarios for LTE deployments, focusing on LTE Carrier Aggregation configurations.
This technical report documents the existing regulatory requirements for unlicensed spectrum deployment in the 5GHz bands.
This document identifies and defines design targets for coexistence with other unlicensed spectrum deployments, including fairness with respect to Wi-Fi and other LAA services.
This document identifies and captures coexistence evaluations of physical layer options and enhancements to LTE and, if necessary, LTE RAN protocols to meet the requirements and targets for unlicensed spectrum deployments.
This document contains an assessment of the feasibility of base station and terminal operation of 5GHz band (based on regulatory limits) in conjunction with relevant licensed frequency bands.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.890
|
Study on Support of single-cell point-to-multipoint transmission in LTE
|
TR
|
13.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.890/36890-d00.zip
|
The present document constitutes the output of the study item "Support of Single-cell PTM transmission in LTE" [2]. This document is intended to capture the possible solutions identified during the study and the conclusions and recommendations for further work.
|
36.895
|
Evolved Universal Terrestrial Radio Access (E-UTRA); European 700 supplemental downlink band (738-758 MHz) in E-UTRA
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.895/36895-d00.zip
|
The present document is a technical report for the European 700 Supplemental Downlink (SDL) for 738-758 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 20 + European 700SDL is selected.
|
36.897
|
Study on Elevation Beamforming/Full-Dimension (FD) MIMO for LTE
|
TR
|
13.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.897/36897-d00.zip
|
The present document is related to the technical report of the study item “Study on Elevation Beamforming/Full-Dimension (FD) MIMO for LTE” [2]. The purpose of this TR is to help TSG RAN WG1 to understand the performance benefit of standard enhancements targeting two-dimensional antenna array operation with 8 or more transceiver units (TXRUs) per transmission point.
This study item is the follow-up to TR 36.873 and it will take into account the findings on 3D channel model in TR36.873 [3]
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 is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.899-13
|
LTE Advanced inter-band Carrier Aggregation (CA) (3DL/3UL)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.899-13/36899-13-d00.zip
|
The present document is a technical report for work items of LTE Advanced inter-band Carrier Aggregation (3DL/3UL) of Band 39 and B41 which were approved at TSG RAN #69 [3] and [4]. The present document provides the relevant background information and studies in order to address mixed intra-band contiguous and inter band Carrier Aggregation(3DL/3UL) requirements.
|
36.892
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Introduction of 1447-1467MHz Band for TD-LTE in China
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.892/36892-d00.zip
|
The present document is a technical report for the work item of introduction of 1447-1467MHz Band for TD-LTE in China, which was approved at TSG RAN#68. The objective of this work item is to specify technical requirements for deploying LTE TDD operation in the new band.
|
36.893
|
Evolved Universal Terrestrial Radio Access (E-UTRA); 700MHz band for Arab Region
|
TR
|
13.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.893/36893-d10.zip
|
The present document is a technical report for the 700MHz E-UTRA FDD band for Arab region work item.
|
36.894
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on measurement gap enhancement for LTE
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.894/36894-d00.zip
|
The present document is the technical report for the Study Item on measurement gap enhancement in LTE.
The current measurement gap configuration and the corresponding RRC signalling were first introduced in Rel.8 back in 2008. Since then, some fundamental evolutions in LTE have been realized. These include numerous new technologies (e.g. carrier aggregation, FeICIC, CoMP, dual-connectivity, etc.), new network topologies (e.g. Heterogeneous Network with small cells) and increased number of deployed bands and frequencies.
The main challenges of the existing measurement gap and the motivations for the further enhancement can be summarized in the following four aspects:
- Network impact and UE scheduling opportunity
- Up to 15% of DL/UL resources are restricted from reception and transmission due to the existing measurement gap configuration
- Multiple Rx chains equipped in CA capable UE can potentially provide extra degrees of freedom to do the measurement more efficiently, but they are not fully utilized at the moment.
- Challenges with multiple Rx chains and single chip RF-IC implementation
- UE can only be configured with single measurement gap pattern even equipped with multiple Rx chains
- This significantly limits network and UE's flexibility to balance the measurement delay, power consumption and spectrum efficiency, which can benefit from multiple RF chains.
- Harmonic interference and/or synthesizer operations due to one Rx chain can result in the interruption on the other Rx chains
- The scenarios where involving synthesizer operating include, but not limited to, radio turned on/off, inter-frequency measurement, SCell activation/deactivation and/or SCell measurements.
- The existing measurement gap pattern is inefficient to handle the Inter-RF chain interference issue. This unnecessarily imposes significant implementation restriction.
- UE power consumption and mobility
- The potential benefit has been recognized to save UE power consumption by differentiating the measurement requirements for the different frequency layers, e.g. coverage, offloading, etc. However, it is not easy to be realized based on the existing measurement gap configuration.
- The mobility performance can be considerably improved with measurement gap enhancement by reducing the measurement delay of coverage layers.
- With the ever-increasing number of deployed bands and frequencies, the existing inter-frequency/inter-RAT measurement mechanism faces even more challenges to meet the performance requirements.
- Limitations of the existing measurement gap pattern are identified in various technical areas
- No enhancement has been made even though the importance of measurement gap enhancement has been well recognized.
- The measurement gap related discussions are diverse and spread over quite a few topics.
- It is desirable to address different measurement gap related issue in a single SI and the eventual enhancement and design should be versatile enough to serve different purposes.
All in all, the effectiveness of new technologies and new network topologies evolved since Rel.8 not only greatly relies on the measurement accuracy and reporting delay, but also on the measurement efficiency and the associated power consumption at UE. All these issues motivate some effort to further investigate the measurement gap enhancement. It is desirable to design an all-weathered and future-proofed inter-frequency/inter-RAT measurement solution by jointly considering all aspects, including but not limited to delay, power consumption, flexibility and network performance.
|
36.978
|
Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) antenna test function definition for two-stage Multiple Input Multiple Output (MIMO) Over The Air (OTA) test method
|
TR
|
13.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.978/36978-d20.zip
|
The present document contains the findings of the Study Item (FS_LTE_MIMO_OTA_ATF) to describe the antenna test function for the two-stage MIMO OTA test method.
|
37.842
|
Evolved Universal Terrestrial Radio Access (E-UTRA) and Universal Terrestrial Radio Access (UTRA; Radio Frequency (RF) requirement background for Active Antenna System (AAS) Base Station (BS)
|
TR
|
13.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.842/37842-d30.zip
|
The present document is the Technical Report for the Work Item on Base Station (BS) Radio Frequency (RF) requirements for Active Antenna System (AAS), which was approved at TSG RAN#59. The present document captures the background and the decisions on the specification of RF requirements that are applicable to AAS BS.
|
37.870
|
Study on Multi-RAT joint coordination
|
TR
|
13.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.870/37870-d00.zip
|
The present document provides descriptions and possible solutions of use cases for the multi-RAT joint operation, and also provides analysis of these solutions. Considerations with regards to requested functionality in scope of other 3GPP groups, if any, may be captured in this document as well.
|
37.857
|
Study on indoor positioning enhancements for UTRA and LTE
|
TR
|
13.1.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.857/37857-d10.zip
|
The present document captures the findings of the study item "Study on Indoor Positioning Enhancements for UTRA and LTE" [1]. The purpose of the present document is to help TSG RAN WG1 and WG4 to properly model and evaluate the performance of new and existing indoor positioning techniques using 3D indoor channel models.
|
43.869
|
GERAN Study on power saving for MTC devices
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.869/43869-d00.zip
|
The present document contains the results from the feasibility study on power saving for Machine Type Communication (MTC) devices in GERAN.
The study should cover the following aspects:
- Identification of use cases and traffic models that the study should target.
- Identification of a set of attributes to be used for identifying specific use case scenarios of prime interest.
- Identification of candidate GERAN enhancements to reduce the energy consumption of MTC devices for use case scenarios of prime interest.
- Energy consumption evaluation of the identified candidate GERAN enhancements for scenarios of prime interest.
|
45.820
|
Cellular system support for ultra-low complexity and low throughput Internet of Things (CIoT)
|
TR
|
13.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.820/45820-d10.zip
|
The present document contains the outcomes of the 3GPP study item on, 'Cellular System Support for Ultra Low Complexity and Low Throughput Internet of Things'.
The following are covered by the study:
- Objectives of the study.
- Evaluation methodology.
- Summary of physical layer aspects and higher layer aspects for different candidate techniques proposed during the study to fulfil the objectives.
- Common assumptions used in the evaluation of candidate techniques.
- Evaluation of network architecture aspects. Link level and system level performance evaluations based on the objectives and evaluation methodology.
|
51.010-1
|
Mobile Station (MS) conformance specification; Part 1: Conformance specification
|
TS
|
13.14.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-1/51010-1-de0.zip
|
The present document describes the technical characteristics and methods of test for Mobile Stations (MS), for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 400 MHz, 700 MHz, 810 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz band (GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, R-GSM 900, ER-GSM 900, GSM 900, DCS 1 800 and PCS 1 900), standardized by ETSI Special Mobile Group (SMG).
The present document is valid for MS implemented according to GSM Phase2 or Phase2+ R96, or R97, or R98, or R99 or 3GPP Release 4 or 3GPP Release 5 or 3GPP Release 6, 3GPP Release 7, 3GPP Release 8, 3GPP Release 9, 3GPP Release 10, 3GPP Release 11 or 3GPP Release 12.
A subset of the tests is referenced in the GSM Common Technical Regulations (CTRs) and is used for regulatory conformance testing according to the EEC procedures for Telecommunications Terminal Equipment (TTE) type approval (EC Directive 91/263/EEC; also known as the "Terminal Directive" or "Second Phase Directive"). The remaining tests can be used to verify conformance with the GSM core technical specifications for those requirements that are not considered "essential" in the sense of the EC Directive 91/263/EEC (Article 4).
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
It applies to the public land mobile radio service in the GSM systems named above, using constant envelope modulation and operating on radio frequencies in the frequency bands listed above respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
The present document is part of the GSM-series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related ETSs or ENs, nor is it created to provide full understanding of (or parts of) GSM systems. The present document lists the requirements, and provides the methods of test for testing a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications or GSM related ETSs or ENs. Clause 2 provides a complete list of the GSM technical specifications, GSM related ETSs, ENs, and ETRs, on which this conformance test specifications is based.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
If there is a difference between this conformance document, and any other GSM technical specification or GSM related ETS or EN, or 3GPP TS, then the other GSM technical specification or GSM related ETS or EN or 3GPP TS shall prevail.
|
51.010-2
|
Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification
|
TS
|
13.16.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-2/51010-2-dg0.zip
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Global System for Mobile Stations (MSs), operating in the 450 MHz, 480 MHz, 700 MHz, 750 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz frequency band (GSM 400, GSM 700, GSM 750, GSM 850, R-GSM 900, ER-GSM 900, GSM 900, DCS 1 800 and PCS 1 900) within the European digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [3] and ETS 300 406 [1].
The present document is valid for MS implemented according to GSM Phase2 or Phase2+ R96, or R97, or R98, or R99 or 3GPP Release 4 or 3GPP Release 5 or 3GPP Release 6 or 3GPP Release 7 or 3GPP Release 8, 3GPP Release 9 or 3GPP Release 10 or 3GPP Release 11 or 3GPP Release 12.
|
22.801
|
Study on non-MTC mobile data applications impacts
|
TR
|
12.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.801/22801-c00.zip
|
To make the network better suited for mobile data applications, the aim/scope of this study is to:
• Capture real world data / analysis.
• Identify services scenarios / use cases for mobile data applications.
• Identify potential problems / issues caused by different mobile data applications.
• Identify potential service and operational requirements for possible enhancements to the system.
|
22.805
|
Feasibility study on user plane congestion management
|
TR
|
12.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.805/22805-c10.zip
|
This TR considers scenarios and use cases where high usage levels lead to user plane traffic congestion in the RAN, and proposes requirements for handling user plane traffic when RAN congestion occurs. The aim is to make efficient use of available resources to increase the potential number of active users while maintaining the user experience.
Scenarios that will be considered include handling of user plane traffic when RAN congestion occurs based on:
• the subscription of the user;
• the type of application;
• the type of content.
|
22.888
|
Study on enhancements for Machine-Type Communications (MTC)
|
TR
|
12.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.888/22888-c00.zip
|
Objective of this work item is to study additional requirements, use cases and functionality beyond that specified by the Release 10 NIMTC work item on the following aspects:
• network improvements for MTC Device to MTC Device communications via one or more PLMNs.
Note: direct-mode communication between devices is out of scope.
• possible improvements for MTC Devices that act as a gateway for 'capillary networks' of other devices.
Note: capillary networks themselves are out of scope of 3GPP.
• network improvements for groups of MTC Devices that are co-located with other MTC Devices.
• improvements on network selection mechanisms and steering of roaming for MTC devices.
• possible enhancements to IMS to support MTC.
• possible improvements for location tracking of MTC Devices.
• service requirements on communications between PLMN and the MTC User/MTC Server (e.g. how the MTC User can set event to be monitored with MTC Monitoring).
• possible service requirements to optimize MTC Devices.
• possible New MTC Features to further improve the network for MTC.
For each of the aspects above, the Study will need to identify what kind of (if any) impacts there are on 3GPP standards.
|
22.896
|
Study on continuity of data sessions to local networks
|
TR
|
12.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.896/22896-c00.zip
|
The present document studies use cases and potential requirements for Continuity of Data Sessions of a UE to Local Networks.
Local IP Access (LIPA) signifies the capability of a UE to obtain access to a local residential/enterprise IP network (subsequently called a local network) that is connected to one or more H(e)NBs and to communicate with entities in the local network through Data Sessions. Basic functionality for Local IP Access (LIPA) has been specified in 3GPP
Rel-10.
The current study item investigates extending LIPA functionality to allow access to the local network when a UE is under coverage of the macro network and provide related mobility support.
|
22.895
|
Study on service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms
|
TR
|
12.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.895/22895-c00.zip
|
The Single Sign-On (SSO) framework integration with 3GPP network resource and services intends to execute a comprehensive set of use cases and service requirements to serve various operator authentication configurations.
The scope of the Single Sign-On (SSO) integration study is to:
- provide service and deployment scenarios for 3GPP operators adopting an integrated approach to SSO, including web, person-to-person and M2M service scenarios;
- provide transparent identification and seamless authentication to Application Services on behalf of the user;
- support a comprehensive set of use cases of integration of different Identity and SSO frameworks (e.g OpenID) for various operator authentication configurations;
- define use cases and provide service requirements for Operators sharing controlled user credentials with Affiliated Application Service Providers;
- define use cases and service requirements associated with ensuring that the intended user is making use of the associated SSO capability (including the case when the UE has been stolen or lost);
- realize the Identity Provider role within the 3GPP network ecosystem and its influence among outside internet web service providers; and
- provide an enhanced user experience with secure, reliable access and authentication to Affiliated Application Services.
|
22.803
|
Feasibility study for Proximity Services (ProSe)
|
TR
|
12.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.803/22803-c20.zip
| |
23.701
|
Study on Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.701/23701-c00.zip
|
The present document contains a study on the potential modifications of the IMS architecture and stage 2 procedures as required by the support of Web Real Time Communication (WebRTC) clients access to IMS.
For this purpose the present document addresses (non exhaustive list):
- Architectural impacts for the support of different kinds of clients (operator / Third party) in different scenarios.
- The architecture (including the support of WebRTC clients access to IMS for clients on a 3GPP UE that are roaming at access level) for following scenarios:
- when 3GPP or non-3GPP access is used (common IMS).
- when the UE is not roaming at access level or when home-routed access is used (these scenarios have priority for the work).
- evaluate/study whether IMS roaming architecture is used in case of 3GPP LBO.
- Media plane aspects e.g.:
- architectural impacts related to the use of specific codecs: the study addresses transcoding aspects but also the case where the use of 3GPP codecs is possible from the UE.
NOTE: How a WebRTC client / the browser can access to 3GPP codecs on the UE is out of the SA WG2 study scope.
- architectural impacts related to media plane security interworking.
- Authentication and Control plane security related aspects.
- Charging.
- PCC aspects.
- Usage of the 3GPP Packet Core Network to support WebRTC clients access to IMS.
For example the following points had been studied: the PDN connection / PDP context to be used by WebRTC traffic especially in roaming cases and the QoS control, e.g. how a WebRTC client can use the QoS supported / delivered by the 3GPP Packet Core.
|
23.768
|
Study on architecture enhancements to support Group Communication System Enablers for LTE (GCSE_LTE)
|
TR
|
12.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.768/23768-c10.zip
|
The present document captures the results of the study and evaluation of possible solutions for architectural enhancements to support Group Communication System Enablers for LTE (GCSE_LTE). The Stage 1 requirements for GCSE_LTE are defined in TS 22.468 [3].
Specifically, GCSE_LTE covers the following aspects:
- Group Communication (GC) among entitled group members via E-UTRAN;
- Group Communication (GC) among entitled group members using E-UTRAN and members of the same group using ProSe communication paths via a ProSe UE-to-Network Relay;
- The relationship between ProSe and GCSE for GCs.
The functional descriptions of "ProSe communication paths via ProSe UE-to-Network Relay" and "ProSe GCs" have been defined in TR 23.703 [4].
|
23.839
|
Study on support of Broadband Forum (BBF) access Interworking
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-c00.zip
|
Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 [3] and TS 23.203 [4].
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.