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
|
|---|---|---|---|---|---|---|
38.475
|
NG-RAN; F1 interface user plane protocol
|
TS
|
0.3.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.475/38475-030.zip
|
The present document specifies the F1 user plane protocol being used over the F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN.
|
25.807
|
Low output powers for general purpose Frequency Division Duplex (FDD) Base Station (BS)
|
TR
|
6.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.807/25807-600.zip
| |
26.932
|
Study on User Equipment (UE) characteristics and performance for video telephony
|
TR
|
0.3.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.932/26932-030.zip
|
[The present document reports the study on video UE characteristics and performance for video telephony.
It identifies some of the UE characteristics that impact the video telephony quality of experience beyond those related to the acoustic performance already specified for speech.
For these characteristics that are specific to video and video call, the document investigates the technical metrics that can be used to assess their performance level. It is also discusses the related possible requirements or objectives that could be specified to achieve the minimum quality of experience expected for the 3GPP video telephony services.
This Technical Report finally studies how these performance requirements/objectives can be verified and the suitable test methodologies are proposed and described where needed.]
|
29.387
|
V2X Control Function to V2X Application Server aspects (V2); Stage 3
|
TS
|
0.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.387/29387-010.zip
|
This document defines the stage 3 specification of V2 reference point between the V2X Control Function and V2X Application Server.
The V2 reference point and related stage 2 procedures are defined in 3GPP TS 23.285 [2].
|
25.902
|
Iub/Iur congestion control
|
TR
|
7.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.902/25902-710.zip
| |
33.899
|
Study on the security aspects of the next generation system
|
TR
|
1.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.899/33899-130.zip
|
NOTE: TR 33.899 is a collection of proposed security requirements, and solutions that were collected during the study of the next generation architecture. The study item was stopped in August 2017. The content of TR 33.899 reflects the state of the work when the study item was stopped. Proposed requirements and solutions are not fully evaluated.
In the scope of this TR are the threats, potential requirements and solutions for the security of next generation mobile networks.
The work will include:
- Collection, analysis and further investigation of potential security threats and requirements for the next generation systems, based on the service, architectural and radio related requirements for the next generation mobile networks.
- Investigation of the security architecture and access security.
The complete or partial conclusions of this study will form the basis for the normative work and/or for any further study.
The security threats and requirements, and the security architecture may additionally include standalone security topics. These topics may not be covered by the security work described above but they shall not be in conflict with service, architectural or radio related requirements for next generation mobile networks. It is part of the study to determine whether such topics need to be dealt with, and, if so, what they are.
|
23.717
|
Enabling Transcoder Free Operation During SRVCC (PS to CS)
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.717/23717-100.zip
|
Editor's note: This clause will define the scope of the Stage 2.
This TR describes various alternatives to enhance the SRVCC procedures to enable Transcoder free operation (TrFO) where possible and ensure that the proper CS radio resources are reserved for optimal RAN codec.
|
26.879
|
Mission Critical Push To Talk (MCPTT); Media, codecs and Multimedia Broadcast/Multicast Service (MBMS) enhancements for MCPTT over LTE
|
TR
|
13.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.879/26879-d00.zip
|
The present document covers the enhancement required to support MCPTT.
|
32.837
|
Gap analysis between 3GPP SA5 specifications and Next Generation Mobile Networks (NGMN) Next Generation Operations Requirements (NGCOR)
|
TR
|
0.13.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.837/32837-0d0.zip
|
The present document makes a gap analysis between the Next Generation Mobile Networks (NGMN) Alliance's "Next Generation Converged Operations Requirements (NGCOR) Requirements" [2] as compared to 3GPPRelease 13 OAM Technical Specifications, and provides recommendation towards NGCOR compliance including suggestions for further 3GPP specification enhancements.
This document addresses the compliance information corresponding to the publication of NGCOR phase II, "NGCOR NEXT GENERATION CONVERGED OPERATIONS REQUIREMENTS" V1.4 [22].
|
33.806
|
Pilot development of Security Assurance Specification for MME Network Product class for 3GPP network product classes
|
TR
|
0.9.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.806/33806-090.zip
|
The present document …
|
33.895
|
Study on Security aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms
|
TR
|
1.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.895/33895-100.zip
|
The present study investigates the security aspects of the service requirements specified by SA1 in TS 22.101 [11] clause 26, on the integration of SSO frameworks with 3GPP networks for various operator authentication configurations (e.g. configurations using GBA or not using GBA).
In particular, this study evaluates existing interworking solutions between SSO frameworks and 3GPP authentication mechanisms against the SA1 service requirements. The study is not limited to evaluation of existing interworking solutions and new interworking solutions may be developed as appropriate.
The study covers the security requirements to enable the operator to become the preferred SSO Identity Provider by allowing the usage of credentials on the UE for SSO services, as well as ways for the 3GPP operator to leverage its trust framework and its reliable and robust secure credential handling infra-structure to provide SSO service based on operator-controlled credentials.
|
36.833-1-08
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 8
|
TR
|
0.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-08/36833-1-08-040.zip
|
The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 8 which was initially approved at TSG RAN #67 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
45.876
|
Uplink Multi-User MIMO
|
TR
|
0.2.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.876/45876-020.zip
|
The present document details the output of the 3GPP study item on UL MU-MIMO [2]. It is intended to gather information in order to draw a conclusion on the UL MU-MIMO technology based on the link level and system level evaluations.
The following items are covered in this document:
• Objectives for the study.
• Concept description.
• Performance evaluations.
• Complexity analysis.
|
22.817
|
Study on UICC/USIM enhancements
|
TR
|
0.4.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.817/22817-041.zip
|
The present report identifies use cases and potential requirements for new USIM services with a focus on:
- Instances where the USIM is used inside terminals with specialised functionalities (e.g. radio modems, 3G Notebook terminals);
- Possible enhancements to facilitate USIM-UICC support for new services;
• Possible enhancements to facilitate an improved user experience when interacting with the UE; and
- Evolution from the USAT towards multimedia USIM toolkit support.
The present report covers only use cases and services that cannot be fully implemented and easily realised using the existing standards, but instead require some enhancement of the present UICC/USIM requirements. Alternative technical solutions (i.e. non USIM-based solutions) are also introduced and referenced for use cases in order to provide a more complete picture of how they might best be realised.
|
23.896
|
Technical Report on Support for fixed broadband access networks convergence
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.896/23896-c00.zip
|
Editor's note: This clause will describe the scope of the feasibility study for P4C.
This Technical Report addresses stage 2 study for the Evolved Packet System (EPS) to facilitate policy and charging control in the fixed broadband access network in the convergent scenario where a single operator is deploying both the fixed broadband access network and the Evolved Packet Core (EPC).
The scope of this TR is to consider the convergent scenario where the PCRF controls directly the network element(s) in the fixed broadband access without the mediation of a different policy server, such as the BPCF defined in TS 23.139 [20].
The work in this TR takes the fixed broadband accesses as specified by BroadBand Forum as a reference. This does not preclude the applicability of the solutions described in this TR to other types of fixed broadband accesses.
This TR will address policy and charging control for:
- Traffic to/from fixed devices connected to the fixed broadband access network (e.g. PC, IPTV Set top Box).
- Traffic exchanged by 3GPP UEs connected via WLAN or H(e)NB when both the fixed broadband access network and the EPC are under the control of the EPS operator.
The work is organized in the building blocks and this TR address the Building block listed below, for an outline of the content of each building block refers to clause 4:
- BB1: Policy and Charging Control for supporting traffic from fixed terminals and NSWO traffic from 3GPP UEs in fixed broadband access networks (P4C-F).
- BB3: Policy and Charging Control for 3GPP UEs connected to fixed broadband access network via S2b and S2c reference points for EPC routed traffic (P4C-S2bc).
- BB4: Policy and Charging Control for EPC routed traffic over fixed broadband access networks of 3GPP UEs connected via H(e)NB in convergent scenarios (P4C-HeNB).
- BB5: Policy and Charging Control for supporting Layer 2 traffic in fixed broadband access network (P4C-FL2).
- BB6: Policy and Charging Control for 3GPP UEs connected to fixed broadband forum access networks as Trusted network in Convergence scenario (P4C-TC).
NOTE: The Building Block 2 P4C-TI is addressed in TR 23.839 [28].
|
28.601
|
Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.601/28601-c00.zip
|
The present document describes the Network Resource Model (NRM) Integration Reference Point (IRP) requirements for Interworking WLAN (IWLAN). According to the structure of IWLAN defined in 3GPP TS 23.234 [6], the present document is focusing on the definition of NRM IRP requirements on the 3GPP part (e.g. WAG, PDG, 3GPP AAA, etc).
|
28.602
|
Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.602/28602-c00.zip
|
The present document is an Integration Reference Point (IRP) named "Core Network (CN) and non-3GPP access interworking system Network Resource Model IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management (CM) information to one or several 'IRPManagers' (typically Network Managers) concerning interworking network resources.
According to the structure of IWLAN defined in 3GPP TS 23.234 [5], several nodes are defined in 3GPP (e.g. WAG, PDG, 3GPP AAA, etc). The present document is focusing on the definition of NRM IRP IOCs for management support.
It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines I-WLAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which Interface IRP that is applicable is outside the scope of the present document.
The present document supports the Federated Network Information Model (FNIM) concept described in 3GPP TS 32.107 [16] in that the relevant Information Object Classes (IOCs) defined in the present document are directly or indirectly inherited from those specified in the Umbrella Information Model (UIM) of 3GPP TS 28.620 [17].
|
28.606
|
Telecommunication management; Core Network (CN) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
12.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.606/28606-c10.zip
|
The present document is part of an Integration Reference Point (IRP) named Core Network (CN) and non-3GPP access Interworking System Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Core Network (CN) and non-3GPP access Interworking System resources. The Core Network (CN) and non-3GPP access Interworking System NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Core Network (CN) and non-3GPP access Interworking System NRM IRP.
This Solution Set specification is related to 3GPP TS 28.602 V12. 0.X [4].
|
32.839
|
Management Specification Tooling Environment
|
TR
|
0.1.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.839/32839-011.zip
|
As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed [1], [2]. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. This document defines these common model elements.
To be noted:
- The Umbrella Operation Model (UOM) described in this document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile environments.
- The UOM is necessary but not sufficient for implementation.
- The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism.
- Classes derived from those in the UOM (e.g. for the fixed environment) may use different names from those used in the UOM.
|
33.268
|
Security aspects of Public Warning System (PWS)
|
TS
|
0.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.268/33268-001.zip
|
This clause shall start on a new page.
The present document …
|
36.832
|
LTE in the 1670-1675MHz Band for the United States
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.832/36832-100.zip
|
The present document constitutes the output of the initial evaluation phase for the work item “LTE RAN Enhancements for Diverse Data Applications” (LTE_eDDA). The document captures agreements and descriptions related to the evaluation methodology used, descriptions of enhancement proposals and their evaluation results, and conclusions and recommendations for further work within the scope of the LTE_eDDA work item.
|
36.833
|
Intra-band Non-contiguous CA for Band 4 for LTE
|
TR
|
0.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833/36833-020.zip
|
This clause shall start on a new page.
The present document is the technical report for the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 4 work item, which was approved at TSG RAN #56 [2].
|
36.834
|
LTE Advanced intra-band contiguous Carrier Aggregation in Band 3
|
TR
|
0.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.834/36834-030.zip
|
The present document is a technical report of the work item for LTE-Advanced Intra-band Contiguous Carrier Aggregation in Band 3 which was approved at TSG RAN #57 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.838
|
Intra-band contiguous CA in Band 27 for LTE
|
TR
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.838/36838-001.zip
|
The present document is a technical report of the work item for LTE Advanced Contiguous Carrier Aggregation in Band 27 which was initially approved at TSG RAN #58 [2]. A revised WID was approved at TSG RAN #59 [3]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.841
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Intra-band non-contiguous Carrier Aggregation (CA) for band 25 for LTE
|
TR
|
12.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.841/36841-c00.zip
|
The present document is a technical report of the LTE Advanced Intra-band Non-contiguous Carrier Aggregation in Band 25 work item which was approved at TSG RAN #53 [2]. The objective of this work item is to provide specification support for intra-band non-contiguous carrier aggregation in LTE FDD Band 25.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.851
|
Inter-band carrier aggregation
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.851/36851-100.zip
|
The present document is a technical report for Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B1_B7
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 7
A3
LTE_CA_B2_B4
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 4
A4
LTE_CA_B23_B29
LTE Advanced inter-band Carrier Aggregation of Band 23 and Band 29
A1
LTE_CA_B3_B26
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 26
A1
LTE_CA_B3_B19
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 19
A1
LTE_CA_B1_B8
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 8
A1
LTE_CA_B3_B28
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 28
A1
LTE_CA_B1_B26
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 26
A1
LTE_CA_B39_B41
LTE Advanced inter-band Carrier Aggregation of Band 39 and Band 41
A3
LTE_CA_B2_B12
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 12
A1
LTE_CA_B2_B13
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 13
A1
LTE_CA_B19_B21
LTE Advanced inter-band Carrier Aggregation of Band 19 and Band 21
A5
LTE_CA_B12_B25
LTE Advanced inter-band Carrier Aggregation of Band 12 and Band 25
A1
LTE_CA_B2_B5
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
LTE_CA_B1_B18
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B7_B28
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 28
A1
LTE_CA_B5_B25
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 25
A1
LTE_CA_B1_B11
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 11
A5
LTE_CA_B8_B11
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 11
A5
LTE_CA_B5_B7
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 7
A1
LTE_CA_B1_B3
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 3
A3
LTE_CA_B1_B28
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 28
A2
LTE_CA_B4_B27
LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 27
A1
LTE_CA_B3_B27
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 27
A1
LTE_CA_B8_B27
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 27
A3
LTE_CA_B3_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B7_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B41_B42
LTE Advanced inter-band Carrier Aggregation of Band 41 and Band 42
A5
LTE_CA_B5_B13
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 13
A3
LTE_CA_B7_B22
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 22
A5
LTE_CA_B2_B5_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
The scope of the report has been further extended [6] to cover the 2 DL fallback modes for the 3 DL Carrier Aggregation combinations with single UL configuration. These 3 DL/1UL combinations are listed in table 1-2. In addition, the report also covers the LTE TDD-FDD joint operation including Carrier Aggregation combinations [7], captured in Table 1-3.
Table 1-2: Release 12 inter-band carrier aggregation combinations (3 DL/1UL)
WI code
WI title
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 5 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 29 and Band 30
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B1_B18_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 18 and Band 28
LTE_CA_3DL_FB_BW
Additional bandwidth combinations for LTE Advanced inter-band Carrier Aggregation to support 3DL fallback
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
Table 1-3: Release 12 inter-band carrier aggregation combinations (LTE TDD-FDD joint operation)
WI code
WI title
Class
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 41)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 42)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 40)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 8 and Band 40)
A1
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 42)
A2
LTE_CA_B26_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 26, Band 41 and Band 41
-
LTE_CA_B3_B38
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 38
A3
LTE_CA_B19_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 19, Band 42 and Band 42
A1
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.853
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced; LTE-Advanced 3 Band Carrier Aggregation (CA) (3DL/1UL)
|
TR
|
2.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.853/36853-220.zip
|
The present document is a technical report for 3DL Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address 3DL Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 3DL inter-band carrier aggregation combinations
WI code
WI title
LTE_CA_B2_B2_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 2 and Band 1
LTE_CA_B2_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 4 and Band 13
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 30
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 29 and Band 30
LTE_CA_B4_B4_B13
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 4, Band 4 and Band 13
LTE_CA_B4_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 30
LTE_CA_B4_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 30
LTE_CA_B4_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 29 and Band 30
LTE_CA_B1_B3_B8
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 8
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B4_B5
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 5
LTE_CA_B2_B4_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 12
LTE_CA_B2_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 5 and Band 12
LTE_CA_B2_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 12
LTE_CA_B3_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 20
LTE_CA_B3_B8_B27
LTE Advanced 3 band Carrier Aggregation (3DL/1UL) for Band 3, Band 8 and Band 27
LTE_CA_B4_B5_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 5 and Band 12
LTE_CA_B4_B12_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 12 and Band 12
LTE_CA_B1_B3_B5
LTE Advanced 3 Band Carrier Aggregation(3DL/1UL) for Band 1, Band 3 and Band 5
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B3_B7_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 7 and Band 7
LTE_CA_B3_B3_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 3 and Band 7
LTE_CA_B1_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 42 and Band 42
LTE_CA_B3_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 3, Band 42 and Band 42
LTE_CA_B1_B3_B19
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 19
LTE_CA_B2_B4_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 4 and Band 29
LTE_CA_B4_B4_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 4 and Band 7
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
LTE_CA_B39_B39_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 39 and Band 41
LTE_CA_B39_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 39, Band 41 and Band 41
LTE_CA_B2_B2_B29
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2 and Band 29
LTE_CA_B1_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 41, and Band 41
LTE_CA_B2_B2_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 2, and Band 12
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.905
|
Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test points for User Equipment (UE) radio transmission and reception conformance test cases
|
TR
|
0.0.2
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.905/37905-002.zip
|
The present document specifies and contains the derivation of Test Points for RF test cases, thereby 3GPP TSG RAN WG5 will have a way of storing the input contributions provided. The test cases are described in TS36.521-1[2].
The test cases which have been analysed to determine Test Points are included as .zip files.
The present document is applicable from Release 10 up to the release indicated on the front page of the present Terminal conformance specifications.
|
25.901
|
Network Assisted Cell Change (NACC) from UTRAN to GERAN; Network side aspects
|
TR
|
6.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.901/25901-610.zip
| |
26.951
|
Enhancements to Multimedia (EMM); EMM, DDE and IPME Aspects
|
TR
|
2.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.951/26951-200.zip
|
The present document contains the results of the work items EMM , EMM-DDE and EMM-IPME as approved in SA in SP-120025. This document does not include the results from the EMM-EFEC work item.
|
28.101
|
Management of Converged Networks; Requirements
|
TS
|
0.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.101/28101-000.zip
|
The present document is part of a TS family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
TS 32.xy1 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Requirements
TS 32.xy2 Fixed Mobile Convergent (FMC) Network Management; FMC Architecture and Model; Stage 2
In a fixed mobile convergent (FMC) network, the services offered to end users need resources from networks of different technologies.
NM standards of different technologies are the responsibilities of various standardization organizations (SDOs) and organizations. Various SDO/organizations may have defined different network management (NM) protocols to manage their respective network resources. Their managed resource models are mostly different from one another. Different parts of the large FMC network may be managed by different organizations.
The key challenge of FMC NM is the production of a set of specifications whose implementations would
a) Reduce FMC operators’ CAPEX and OPEX and
b) Facilitate OSS (playing the role of IRPManager) to integrate the various NM services consumed into the so-called “end-to-end” view of the FMC network under management.
Since network resource models are designed and maintained by different SDO/organizations and the provision of the “end-to-end” view requires defined relations among network resource models, this set of specifications would include:
1. Model architecture, called Federated Network Model (FNM), identifying various network resource models and their relations among each other;
2. The governance of each network resource model and the working procedures among SDO/organizations (that are designers and maintainers of the network resource model) involved.
The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for item 1 and item 2 above.
This clause shall start on a new page.
The present document …
|
28.102
|
Management of Converged Networks; Stage 2
|
TS
|
0.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.102/28102-000.zip
|
FFS
|
28.401
|
Telecommunication management; Performance Management (PM); Performance measurements for Core Network (CN) and non-3GPP access Interworking System
|
TS
|
0.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.401/28401-020.zip
|
The present document describes the measurements for CN and non-3GPP interworking system.
TS 32.401 [3] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a interworking system. Only measurement types that are specific to interworking system are defined within the present documents. Vendor specific measurement types used in interworking system are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to WAG, PDG and so on);
- Header 2: Measurement function (e.g. FFS);
- Header 3: Measurements.
|
30.007
|
Guideline on WI/SI for new Operating Bands
|
TR
|
0.2.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.007/30007-020.zip
|
The present document a technical report for the <Work item name> work item.
The Scope of the TR should be kept short. Details of the Work Item objective should be given in the Background section (Clause 4).
|
33.914
|
Single Sign On (SSO) application security for common IP Multimedia Subsystem (IMS) based on SIP Digest
|
TR
|
2.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.914/33914-200.zip
|
The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated.
|
36.416
|
Mobile Relay for E-UTRA
|
TS
|
0.0.2
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.416/36416-002.zip
|
The present document is the technical report for the study item on Mobile Relay for E-UTRA [1], which was approved at TSG RAN#53. The objective of the SI is to first identify the scenario(s) and requirements then identify the key properties of mobile relays and assess the benefits of mobile relays over existing solutions in fast-moving environments.
|
36.827
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced carrier aggregation band 41
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.827/36827-b00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 41 work item which was approved at TSG RAN #52 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 41.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
25.463
|
UTRAN Iuant interface: Remote Electrical Tilting (RET) antennas Application Part (RETAP) signalling
|
TS
|
6.7.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.463/25463-670.zip
| |
36.831
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced Carrier Aggregation (CA) in band 7
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.831/36831-b00.zip
|
The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 7 which was approved at TSG RAN #53 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
23.823
|
Intra Domain Connection of RAN Nodes to Multiple CN Nodes
|
TR
|
2.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.823/23823-200.zip
|
This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications.
|
22.913
|
Location Services (LCS) support in Evolved Packet Core (EPC) for non-3GPP accesses
|
TR
|
1.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.913/22913-100.zip
|
This Technical Report (TR) presents the results of the Study on LCS support for non-3GPP accesses.
One main concept of EPC is to support a variety of different access systems (existing and future) ensuring mobility and service continuity between these access systems. In that perspective, the LCS support for non 3GPP accesses should be also taken into account. However, historically, TS 22.071 has been applicable only to 3GPP accesses and any new requirements for non 3GPP accesses have not been discussed yet.
Therefore we need to consider how to support LCS in EPC for non 3GPP accesses, e.g. 3GPP2 and WiMAX. Supporting LCS in EPC for non 3GPP access does not necessarily mean that all positioning methods available in various kinds of non 3GPP accesses should be supported in EPC or inventing new positioning methods for other accesses. However, how to realize the presentation of location information in EPC when users are connected in non 3GPP accesses should be at least taken into account. In addition, the service scenarios should be discussed whether new service requirements are needed for the users camping on non 3GPP accesses through EPC.
This work will examine whether requirements in TS 22.071 would be applicable for non 3GPP accesses and specify new service requirements for the users connected to non 3GPP accesses through EPC.
Consideration will be given, but not limited, to the following:
• High level requirements of LCS support for non 3GPP accesses;
• Location information provided to the LCS client for non 3GPP accesses;
• QoS requirements of LCS support for non 3GPP accesses.
• Priority between different LCS services for non 3GPP accesses.
• Privacy requirements of LCS support for non 3GPP accesses.
• Periodic location report of LCS services for non 3GPP accesses.
• Impact on the LCS client and the LCS server to support LCS services for non 3GPP accesses
|
23.848
|
Study on enhancements to IP Multimedia Subsystem (IMS) border functions for interconnection of IMS based services
|
TR
|
0.9.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.848/23848-090.zip
|
The objective of this document is to analyse and identify enhancements needed in the current 3GPP IMS interconnection architecture driven by the needs that new business models/service delivery scenarios impose at the interconnection points of the IMS operators.
The present document will covers network to network interconnection as main objective and addresses the issues related to both control and user plane functionalities including:
- signalling treatment,
- numbering/naming/addressing,
- IP interworking,
- policy management,
- e2e QoS,
- transcoding,
- security,
- charging.
The purpose of this document is to formulate architectural solutions for the enhanced functionalities identified to cover all IMS operator’s needs in this widespread environment. These solutions should be applicable for an IMS operator in a common IMS environment (i.e. regardless the access being used) as well as for direct and indirect interconnection paradigms. Finally, the best solution/s should be agreed and impacted normative work in 3GPP identified to update current 3GPP specifications with the output of this work.
|
23.884
|
Local Call Local Switching, Feasibility Study
|
TR
|
0.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.884/23884-010.zip
|
The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of potential correlation information between the two legs of the call to be sent to the BSS (e.g. in case of MSC pooling)
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications.
|
29.875
|
Interworking Proxy between GTP based and PMIP based interfaces
|
TR
|
1.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.875/29875-120.zip
|
The present document is to evaluate the feasibility of introduction of an Interworking Proxy (IWP) between GTP-based S8 and, PMIP-based S8 and S9 interfaces as described in 3GPP TS23.402 [2] Annex A. This evaluation will be based on the study of various concrete interworking deployment scenarios for which an IWP may be used. For each scenario, it will be analysed how the IWP fulfils the specific interworking requirements and performs the mapping of procedures and the corresponding parameter handling. The U-plane Interworking will also be analysed for each scenario.
The present document will study the mechanism for the interworking scenarios, e.g. IWP selection, message binding.
|
33.837
|
Study of mechanisms for Protection against Unsolicited Communication for IMS (PUCI)
|
TR
|
2.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.837/33837-201.zip
|
The scope of this report is to develop solutions to protect mobile subscribers from receiving unsolicited communication over IMS and to analyze these solutions in respect of their requirements and impacts on standardized interfaces.
This activity will take into account the study done in TISPAN TR 187 009 on “Feasibility study of prevention of unsolicited communications in the NGN”. This work will also be coordinated with ongoing activity in other SDOs (e.g. TISPAN, IETF and OMA). It is preferred that a common solution can be defined for protection against UC in both IMS and NGN deployments.
|
25.463
|
UTRAN Iuant interface: Remote Electrical Tilting (RET) antennas Application Part (RETAP) signalling
|
TS
|
7.5.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.463/25463-750.zip
| |
36.571-2
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; UE positioning in E-UTRA; Part 2: Protocol conformance
|
TS
|
1.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.571-2/36571-2-100.zip
|
The present document specifies the protocol conformance testing for the 3rd Generation E-UTRAN User Equipment (UE) supporting UE positioning.
This is the second part of a multi-part test specification. The following information can be found in this part:
- the overall protocol conformance test structure;
- the protocol conformance test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The Implementation Conformance Statement (ICS) pro-forma could be found in the 3rd part of the present document.
The present document is valid for UE implemented according to 3GPP Release 9.
|
36.571-5
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; UE positioning in E-UTRA; Part 5: UE positioning test scenarios and assistance data
|
TS
|
1.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.571-5/36571-5-100.zip
|
The present document specifies the test scenarios and assistance data required for the conformance test for FDD or TDD mode of UTRA and E-UTRA for the User Equipment (UE) that supports one or more of the defined positioning methods. For UTRA these are Assisted Global Positioning System (A-GPS) and Assisted Global Navigation Satellite System (A-GNSS). For E-UTRA these are A-GNSS, Observed Time Difference of Arrival (OTDOA) and Enhanced Cell ID (ECID).
|
22.258
|
Service requirements for an All-IP Network (AIPN); Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.258/22258-800.zip
|
The present document describes the service requirements for the All-IP Network (AIPN) including service requirements for Evolved UTRA and UTRAN. Where appropriate, references are made to service requirements within other 3GPP specifications that are applicable to the AIPN.
|
22.812
|
Study into network selection requirements for non-3GPP access
|
TR
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.812/22812-800.zip
|
The present document considers the network selection procedures requirements for non-3GPP access types. The network selection principles covered include both automatic and manual selection. Also considered is the operator management of network preferences for non-3GPP access types and how the device accesses networks offered through non-3GPP access.
Non-3GPP access includes any method by which the UE is connected either to a core network or to a server other than by using the radio bearers standardised by 3GPP. Examples are: BlueTooth, WLAN and fixed (wired connections).
UEs considered in this study are UEs able to connect to a non-3GPP network in addition to its 3GPP capabilities (i.e. dual mode, multi-mode UEs).
This work in this TR is applicable to GSM and UMTS and there are no additional considerations of EPS (Evolved Packet System).
Roaming and handover conditions between 3GPP and non-3GPP networks is not under the scope of this document and will not be treated here. They may be referred to, however, for the consistency of use cases and access description consistency.
Connection to a 3GPP operator's core network by WLAN is out of scope where this is I-WLAN. This is covered in [2].
Use of the Generic Access Network is out of scope.
Considerations of tariffing are out of scope.
|
22.984
|
Unauthenticated Packet Switched (PS) emergency calls
|
TR
|
0.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.984/22984-030.zip
|
The present document gives an overview of the problems related to Unauthenticated PS based Emergency Calls (UAPSEC) and provides information on this topic in comparison to the existing unauthenticated CS based emergency call.
Major areas of work the document takes into account are security aspects, architectural aspects and signalling aspects. It also considers the case where the subscriber has got a PS subscription but no subscription to IMS services.
The document explains on the differences between the scenarios that allowed unauthenticated CS emergency calls without encountering too big problems and the scenarios that make Unauthenticated PS based Emergency Calls different in this respect.
It elaborates on these new scenarios, for example on the Distributed Denial of Service Attacks (DDOS) scenario.
|
23.822
|
Framework for Gq' / Rx harmonization
|
TR
|
0.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.822/23822-030.zip
|
This document provides information that will be used to align the Rx and Gq' reference points. The document analyses several options and recommends options for alignment, taking the architectural and protocol aspects into account.
|
23.827
|
Feasibility study of mobility between 3GPP-WLAN interworking and 3GPP systems
|
TR
|
0.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.827/23827-040.zip
|
This TR studies and defines the appropriate solutions for supporting mobility and roaming between 3GPP-WLAN Interworking system and 3GPP Systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user’s perceived quality on the services at a change of the access network (between I-WLAN and 3GPP Access Systems). The solutions should impose minimum changes to the 3GPP PS core network and the terminals as well as the WLAN access.
Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included.
|
23.937
|
Feasbility study of mobility between 3GPP-WLAN interworking and 3GPP systems
|
TR
|
0.0.2
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.937/23937-002.zip
|
This TR studies and defines the appropriate solutions for supporting mobility and roaming between 3GPP-WLAN Interworking system and 3GPP Systems so that ongoing 3GPP PS based services can be maintained with minimal impact on the end-user’s perceived quality on the services at a change of the access network (between I-WLAN and 3GPP Access Systems). The solutions should impose minimum changes to the 3GPP PS core network and the terminals as well as the WLAN access.
Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included.
|
23.982
|
IP Multimedia System (IMS) centralized services
|
TR
|
0.3.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.982/23982-031.zip
|
This document contains the results of the feasibility study into the architectural requirements and alternatives for the delivery of consistent services to the user mainly via IMS centralized services regardless of the attached access type; e.g. CS domain access or IP-CAN. Considerations include overall requirements, architectural requirements, alternative architectures and evaluation of potential architectural solutions.
The study considers how to access IMS-based multimedia telephony services while still allowing innovative services. It includes investigation into call/session establishment via CS domain access and IP-CAN and for calls/sessions transferred across CS domain access and IP-CAN, including the interactions with domain selection. It provides consideration for the handling of the multiple medias that are enabled by the multimedia telephony communication service. The solution should be applicable for terminals with VCC capabilities and for non-VCC capable terminals. Impact on legacy terminals with the same subscription (e.g. SIM swapping) should be studied.
The second objective of the study is an investigation into the means to support and the need of the evolution of a network towards the IMS centralized services architecture. The assumption for this evolution is that some networks may not immediately migrate all services to the IMS centralized services architecture. In addition, given that some calls may not be rerouted to IMS during the migratory period, the study shall also investigate how to ensure that equivalent services are implemented in IMS and CS.
|
24.293
|
ICS Protocol over USSD bearer
|
TS
|
0.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.293/24293-020.zip
|
The present document describes the I1 interface between IMS Centralized Services (ICS) UE and Service Centralization and Continuity (SCC) Application Server (AS).
This specification defines a new application layer protocol over I1 interface, specifies the interaction between the ICS UE and the SCC AS including session control procedures and supplementary services control procedures.
For the current version of the specification the application layer protocol is run over Unstructured Supplementary Service Data (USSD) transport, however the application layer protocol is not restricted to USSD transport.
The overall ICS architecture is specified in 3GPP TS 23.292 [3].
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the IMS centralized services.
|
25.822
|
UMTS 700 MHz Work Item Technical Report
|
TR
|
1.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.822/25822-100.zip
|
The present document is a technical report of the UMTS 700 MHz work item, which was approved to establish in TSG RAN#35. The purpose of the work item is to provide UMTS specification support for UTRA/FDD in the new band allocations on pairing
• 698-716 MHz UL with 728-746 MHz DL and
• 746-768 MHz DL with 776-798 MHz UL.
UMTS 700 MHz work item is covering also E-UTRA aspects, especially narrower BW options 1.4 MHz and 3.0 MHz. Because E-UTRA work is still ongoing, changes for new specifications will be covered under E-UTRA work item.
In addition to schedule and status of the work item, the report includes a description of the motivation of requirements and specification recommendations.
|
25.825
|
Dual-cell High Speed Downlink Packet Access (HSDPA) operation
|
TR
|
1.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.825/25825-100.zip
|
The present document is intended to capture findings produced in the context of the Feasibility Study on Dual-Cell HSDPA operation [1].
The work under this study item aims at assessing the feasibility, benefits and complexity of combining network radio resources (i.e. cells) to achieve enhanced user experience and enhanced user experience consistency. The assessment focuses on scenarios with the following constraints:
• The dual cell operation only applies to downlink HS-DSCH.
• The two cells belong to the same Node-B and are on different carriers.
• The two cells do not use MIMO to serve UEs configured for dual cell operation.
• Primary priority: The two cells operate on adjacent carrier frequencies in the same frequency band. Other allocations can be considered with lower priority
In order to characterize benefits of Dual-Cell HSDPA operation, possible enhancements of performance throughout the cell and in particular in the outer area of the cell coverage are evaluated considering:
• UE receiver impairments caused by the implementation of dual-cell operation,
• Node B scheduler architecture (per carrier or joint scheduler),
• Load balancing when coupled with joint scheduling vs. per carrier scheduling.
Furthermore, impacts on implementation and complexity within the UTRA and UE, impacts systems operation (e.g. UL controlchannel coverage and operation of legacy UE), and impacts on the core specifications due to introducing Dual-Cell HSDPA operation are identified.
|
25.828
|
UMTS 2300 TDD Work Item Technical Report
|
TR
|
0.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.828/25828-030.zip
|
This document is the technical report of the UMTS 2300MHz WI which was approved in TSG RAN meeting #38 [1].
The purpose of this TR is to summarize a study of radio requirements for UTRA TDD－1.28Mcps TDD in the 2300MHz Band:
• 2300-2400 MHz: Up-link and Down-link (UE transmit and receive, Node B transmit and receive)
|
29.612
|
TISPAN; Interworking; Trunking Gateway Control Procedures for interworking between NGN and external CS networks
|
TS
|
1.1.3
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.612/29612-113.zip
|
The present document defines the control procedures for trunk gateways when PSTN/ISDN emulation and PSTN/ISDN simulation services in an NGN Network require interworking with ETSI PSTN/ISDN services in a ISUP network. Interworking with BICC networks is not included in the scope of TISPAN R1.
Existing profiles will be evaluated, in order to determine if they can be re-used, with possible modifications, or if a completely new profile is to be defined.
|
29.624
|
TISPAN; H.248 Profile for controlling Trunking Media Gateways; Protocol specification
|
TS
|
1.1.6
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.624/29624-116.zip
|
The present document defines the profile of the Gateway Control Protocol (ITU-T Recommendation H.248.1 [3]), for controlling Trunking Media Gateways (TMGW) for both the PSTN/ISDN Emulation and IMS Core Subsytems. Thus the scope of this Profile is a subset of the 3GPP profile for the Mn interface defined in TS 129 332 [2].
|
29.803
|
3GPP System Architecture Evolution (SAE): CT WG4 aspects
|
TR
|
0.9.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.803/29803-090.zip
|
The present document discusses and describes procedures and protocols from CT4 aspects of Evolved Packet System (EPS) towards a higher-data-rate, lower-latency, packet-optimized system that supports multiple access technologies.
These CT4 aspects include selection and study of protocols and procedures that will be used in the evolved system (e.g. within evolved packet core network, between EPC and current GPRS core network, between EPC and HSS/AAA, and between 3GPP and non-3GPP access), and describes impacts and required enhancements for related network protocols, including GTP and IETF protocols based on stage2 architecture requirements.
In addition, the present document also includes description of the new identities and addressing schemes required by Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Evolved Packet System (EPS), and in particular functional requirements and protocols for enhancing existing capabilities for EPS/E-UTRAN, e.g. MBMS and network sharing.
The present document is used as a place holder for CT4 EPS materials to be moved to appropriate 3GPP technical specifications when the TR is sufficiently stable.
|
30.818
|
Telecommunication management; Project scheduling and open issues for SA5, Release 8
|
TR
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.818/30818-800.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
|
33.178
|
Security aspects of early IP Multimedia Subsystem (IMS)
|
TS
|
1.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.178/33178-100.zip
|
The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain.
|
33.922
|
Security aspects for inter-access mobility between non 3GPP and 3GPP access network
|
TS
|
2.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.922/33922-200.zip
|
This document studies the security architecture, i.e. the security features and the security mechanisms for inter-access mobility between 3GPP access system and non-3GPP access systems. For the general architecture for inter-access mobility cf. TR 23.882. This report is meant to provide more detail on the security aspects of inter-access mobility.
The scope should be extended to the mobility between two non-3GPP access systems, which interwork with 3GPP core entities. An example would be the mobility between two WLAN access systems providing 3GPP IP access.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.402 [14]. This TR may therefore be useful to better understand the basis on which decisions in TS 33.402 [14] were taken, and which alternatives were under discussion. However, none of the text in this TR shall be quoted as reflecting 3GPP’s position in any way. Rather, 3GPP’s position on security for non-3GPP access to EPS is reflected in the normative text in TS 33.402 [14]. Information in the TR may be inaccurate and outdated. One example of outdated text can be found in clauses 4.1 and 4.2 on alternatives for authentication protocols. The choices of authentication protocols finally made by 3GPP can be found in TS 33.401 [13] and TS 33.402 [14] respectively.
|
36.801
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Measurement Requirements
|
TR
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.801/36801-001.zip
|
The present document should identify the required UE and BS measurements for E-UTRA, e.g. for mobility, positioning, and traffic. It should also identify the requirements, i.e. the measurements interval, the reporting accuracy, granularity and performance requirements. Furthermore it should also identify the constraints, content and size of neighbour cell lists, e.g. multi mode multi RAT operation, provisioning of measurement occurances need for parallel measurements, i.e. mobility and positioning. The purpose of this TR is to provide specification support for RAN WG1,2,3,4.
This document is intended to gather the agreements rather than comparing different solutions.
NOTE: This document is a living document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.803
|
Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception
|
TR
|
1.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.803/36803-110.zip
|
The purpose of this TR is to summarize the study of radio requirements for the User Equipment (UE) radio transmission and reception as part of the work item on Evolved Universal Terrestrial Radio Access (E-UTRA).
|
36.804
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception
|
TR
|
1.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.804/36804-120.zip
|
The present document summarizes the studies of radio requirements for the Base Station (BS) radio transmission and reception as part of the work item on Evolved Universal Terrestrial Radio Access (E-UTRA).
|
23.803
|
Evolution of policy control and charging
|
TR
|
7.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.803/23803-700.zip
|
The present document intends to study the following items:
1) Complete harmonization and merger of the policy control and flow based charging architecture and procedures;
2) Possible architectures and solutions for adding end-user subscription differentiation and general policy control aspects to the policy- and charging control;
3) Alternative solutions for binding bearers to services (provided today by the authorization token). This includes studying solutions for the network to control bearer usage by service flows.
Editors Note: The document may also study the impact on policy control and flow based charging architecture based on the conclusion and approved recommendations of the E2E QoS Work Item in a Release 7 context if deemed feasible.
|
23.805
|
Selective disabling of User Equipment (UE) capabilities; Report on technical options and conclusions
|
TR
|
0.3.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.805/23805-031.zip
|
The present document presents an assessment of different service architecture implementations for the new Selective Disabling of UE Capabilities specified in TS 22.011, Section 4.5.
For each service architecture the document provides:
• A detailed description of the architecture
• An assessment of the architecture against the SA1 requirements described in TS 22.011, Section 4.5.
• An assessment of the architecture’s strengths and weaknesses
The document provides a conclusion identifying the preferred service architecture of the SA2 TSG.
|
23.807
|
Feasibility study for enhancement of radio performance for Voice over IP Multimedia Subsystem (VoIMS); Report on technical options and conclusions
|
TR
|
0.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.807/23807-030.zip
|
The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain.
Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC.
Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data.
Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR.
|
23.808
|
Supporting Globally Routable User Agent URI in IMS; Report and conclusions
|
TR
|
1.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.808/23808-101.zip
|
The present document is a temporary container for the architectural impacts on IM CN subsystem for supporting GRUU. The contents of this report when stable will be the base for CRs to 3GPP Technical Specifications e.g. TS 23.228 [2].
GRUU is a URI, the creation and use of which is defined in an IETF specification draft-ietf-sip-gruu-0 [1] in order to route SIP messages to a specific SIP User Agent (UA) instance. The support of GRUU in IMS is to enable routing of SIP messages to a specific instance of a registered public user identity even when a single public user id is registered from multiple UEs.
|
23.809
|
One Tunnel solution for Optimisation of Packet Data Traffic
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.809/23809-100.zip
|
The present document is a temporary container for a stage-2 like description of an architecture that uses direct tunnelling of user plane data between the RNC and the GGSN, which is known as One Tunnel approach. The content of this report when stable will be moved into 3GPP Technical Specification TS 23.060 [1].
This report will further develop the One Tunnel approach described in TR 23.873 [2] and identify what changes are needed to PS core and potentially to UTRAN functionalities and protocols to support the One Tunnel functionality. This include the investigation of the functions added after Rel‑4 up to Rel‑6 (e.g. Iu-flex, Network sharing, MBMS, etc) and either verify that they are not affected or address any conflicts between these functions and the One Tunnel function.
The resulting system architecture shall be fully interoperable with pre-Rel‑7 nodes and it should retain the existing network capabilities, or those that cannot be delivered need to be clearly documented.
|
23.817
|
Feasibility study on enhancement of radio performances for Voice over IMS (VoIMS); Report on Technical options and conclusions
|
TR
|
0.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.817/23817-010.zip
|
The present document describes architecture changes for Voice over IMS service to allow enhancement of radio performances in RAN. This work focuses on the PS domain with the assumption that voice services are supported in this domain.
Two radio optimization methods have been identified to provide radio optimisation for VoIMS: Unequal Error Protection (UEP) and Header Removal (HR). With the information currently available in RNC, RNC cannot use these optimisation methods. More study is then needed to describe which additional information are needed by RNC and how these information can be provided to RNC.
Radio optimisations for the SIP signalling are out of the scope of this TR. The study will focus on the bearer optimisation for user data.
Radio optimisations with no architecture impact outside the UTRAN are out of the scope of this TR.
|
23.818
|
Optimisations and Enhancements for Realtime IMS Communication
|
TR
|
0.10.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.818/23818-0a0.zip
|
The scope of the technical report is to capture the results of a study into the optimisations and enhancements of the system for mass market real-time communication (IMS multimedia telephony).
The objective is to provide a study into optimisations and enhancements for the support realtime services based on IMS with regards to the following aspects:
- Analysis of IMS session establishment procedures (e.g. signalling flows, bearer establishment) in order to reduce call establishment time for multimedia telephony to obtain the same, or at least similar, characteristics as exists for CS telephony;
- Analysis of impacts of any non call related IMS signalling (e.g. due to Presence) on the efficiency and service aspects of active real time communication sessions and the establishment of such sessions;
- Analysis into mechanisms to inform the IMS of loss of the signalling bearer transport through the IP-CAN;
- Analysis and identification of architecture and information flow impacts due to the dynamic allocation of users to Application Servers, including analysing any potential impacts at initial registration, session establishment and provision of user data in the HSS;
- Identification of any stage 2 impacts in order to support multimedia telephony services;
- Efficient interworking with other VoIP networks, e.g. regarding call establishment time and simplified call flows.
The study is intended to provide conclusions on the above aspects with respect to future normative specification work.
|
23.819
|
Terminating session handling
|
TR
|
1.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.819/23819-130.zip
|
3GPP has specified how to combine CS call and IMS Sessions but has not yet addressed the interworking between e.g. a pure IMS voice/video session and a combination of a CS call and an IMS session.
The present document studies how to handle terminating real-time sessions and calls taking into account different domains (CS, IMS) and different UE capabilities (CSI, IMS VoIP, etc.).
|
23.836
|
Quality of Service (QoS) and policy aspects of 3GPP - Wirless Local Area Network (WLAN) interworking
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.836/23836-100.zip
|
Some 3GPP PS based services (e.g. VoIP over IMS, PS streaming, etc) require strict QoS provisioning. In order to support such services over I-WLAN, QoS Provisioning in 3GPP-WLAN Interworking is required.
IEEE 802.11 WLAN standards are currently not supporting QoS mechanisms, therefore QoS provisioning was not considered in Rel-6 work for 3GPP-WLAN Interworking. As IEEE is currently finalizing QoS amendments to 802.11 WLAN standards, QoS-related aspects of the 3GPP-WLAN architecture should be studied.
In the context of end-to-end QoS provisioning being studied in TR 23.802, provisioning of QoS within I-WLAN as an IP-CAN is important. It shall be defined if and how QoS provisioning in I-WLAN can interact with the end-to-end QoS framework.
Flow based charging and service/subscription based policy control are studied in TR 23.803 as generic features to support the access to PS based services from different IP-CANs. In order to leverage the generic charging and service/subscription based policy control within I-WLAN as another IP-CAN, the Gateway element in case of 3GPP-WLAN Interworking has to provide the needed functionalities, e.g. for Policy Enforcement.
The followings are objectives of the document.
- investigate the necessity and reliability of the applicable QoS mechanism between the WLAN UE and PDG, and the possible impacts to the 3GPP-WLAN interworking entities;
- ensure that the architecture for 3GPP/WLAN Interworking defined by TS 23.234 is supported by the following QoS-related mechanisms being developed in 3GPP:
a. E2E QoS architecture being studied in TR 23.802;
b. Policy and charging evolution capabilities being studied in TR 23.803.
|
23.837
|
Location Services (LCS) architecture for 3GPP system - Wireless Local Area Network (WLAN) interworking
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.837/23837-100.zip
|
The present document investigates solutions for providing LCS over 3GPP WLAN interworking architecture. The architectural requirements and different possible LCS architectures to provide the location services over I-WLAN are analyzed. The procedures to obtain the location information of a WLAN UE attached to I-WLAN network are also studied. The LCS aspects for I-WLAN as IP-CAN in the IMS Emergency call, i.e., the emergency location information handling for I-WLAN are described in this TR.
|
25.812
|
Requirements for evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN)
|
TR
|
0.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.812/25812-000.zip
|
This document is related to the technical report for the study item “Evolved UTRA and UTRAN” [1]. The objective of the study item is to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data-rate, low-latency and packet-optimized radio access technology.
This document provides guidance and collects requirements which an evolved UTRA and UTRAN system should meet.
|
25.819
|
7.68 Mcps TDD option: Layer 2 and 3 protocol aspects
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.819/25819-100.zip
|
The present document identifies RAN2 the specifications impacted by the introduction of 7.68 Mcps TDD. It describes the various options for implementing the 7.68 Mcps TDD option in specifications and presents a brief description of the decisions and changes agreed.
|
25.904
|
Improved support of gaming over HSDPA/EDCH
|
TR
|
0.0.2
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.904/25904-002.zip
|
This document is related to the technical report for physical layer aspect of the study item “Evolved UTRA and UTRAN” [1]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, along with the complexity evaluation of each technique.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information in order to compare the solutions and gains vs. complexity, and draw a conclusion on way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
The purpose of this TR is to help 3GPP TSG RAN WG2 define, describe and improve the support for gaming using HSDPA/HSUPA (HS-DSCH/E-DCH), focusing on minimizing delay and the service interruption time in case of handover. The latency of radio, core network, and terminals should be included in this TR with evaluations of the various complexity issues affecting both real time gaming (such as RT Shooting and RT auto racing) and less than real time gaming (such as chess and other less demanding gaming). Inclusion of 2 way RT gaming plus 2 way synchronized voice should also be included in this TR. All evaluations shall include complexity analysis and any end-user complexities and relevant issues.
The activity involved in this TR involves both Radio Access and has impacts that include Radio Access Network and Mobile Equipment.
This TR is intended to work in conjunction with other WI’s that are currently employed in reducing the latency of the radio network.
The conclusion of this work item shall be CR’s that will be presented to RAN WG2 and other WG’s
|
30.301
|
3.84 Mcps TDD enhanced uplink: RAN WG2 Stage 2 decisions
|
TR
|
0.2.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.301/30301-020.zip
|
This document is a Technical Report which captures the Stage 2 decisions on the support of 3.84 Mcps TDD Enhanced Uplink in UTRA.
|
32.807
|
Telecommunication management; Project scheduling and open issues for SA5, Release 7
|
TR
|
0.0.3
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.807/32807-003.zip
|
The purpose of this document is to contain the updated Work Item Descriptions (WIDs) and capture status of all TSG SA WG5 work items of the current 3GPP Release in order for the group to get an overview of current ongoing work.
This TR is used as a mean to provide input to the complete 3GPP work plan that is handled by MCC.
|
33.801
|
Access security review
|
TR
|
1.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.801/33801-100.zip
| |
33.802
|
Feasibility study on IMS security extensions
|
TR
|
0.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.802/33802-020.zip
|
Editor’s Note: The current version of this document represents the state of discussion in 3GPP SA3 after meetings #39 and #40. It consists of a compilation of input documents to SA3 #39 and SA3 #40. The annexes describe solutions proposed for signalling protection for fixed broadband access to IMS. They are based on input documents to SA3 #39 and SA3 #40 (S3-050402, S3-050539, S3-050571). Section 5 (Analysis) represents the contents of the analysis contributions discussed (S3-050333, S3-050372, S3-050427, S3-050570). The current text in section 5 is not endorsed by SA3 at this point of time.
The scope of the present document is to study security requirements and solutions related fixed broadband access to IMS. Both solutions for ETSI TISPAN NGN R1 and ETSI TISPAN NGN R2 need to be studied. Based on this document, solutions to meet the fixed broadband access security needs are to be specified in TS 33.203 within the time frame of NGN R1 and NGN R2.
|
43.935
|
Feasibility study of enhanced support for video telephony service over GERAN via the A interface
|
TR
|
0.4.0
|
G1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.935/43935-040.zip
|
The present document provides an overview of the possible enhancements to the circuit switched vide telephony service in GERAN.
|
50.099
|
GERAN project plan and open issues
|
TR
|
0.55.0
|
GP
|
https://www.3gpp.org/ftp/Specs/archive/50_series/50.099/50099-005500.zip
| |
22.976
|
Study on PS domain services and capabilities
|
TR
|
2.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.976/22976-200.zip
|
This Technical Report provides background information, motivations, descriptions of service drivers, and concepts regarding general service requirements and service features of Release 2000, consisting of an evolved Release 99, and IP multimedia services.
The evolved Release 99 and the first phase of IP multimedia services of 3GPP Release 2000 are described in this TR provide the basis for the detailed Stage 1 specification work. The IP multimedia services will be developed in a phased approach and a longer term vision is presented in the report.
The focus of the TR is:
• Support and evolution of 3GPP Release 99
• High level vision of multimedia services
• Examination of potential service drivers
• New and evolved service capabilities and end user benefits
• Evaluation of what does and does not need to be standardised
• Release a Feature List of global interest and potential service candidates
• Case study of realisation of some services (e.g. CFU)
This TR has been created to ease the development of 3GPP Release 2000, and this document can be used to guide 3GPP in the creation of new specifications and CRs to existing specifications for the realisation of mobile communications services based on the Release 2000 specifications.
|
23.241
|
3GPP Generic User Profile (GUP); Stage 2; Data Description Method (DDM)
|
TS
|
6.1.0
|
N4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.241/23241-610.zip
|
The present document is the Stage Two description for the Data Description Method (DDM) and the Datatype Definition Method (DtDM) of the 3GPP Generic User Profile.
The present document specifies the method for describing the logical structure of the data description, Generic User Profile, Profile Components, methods for describing Datatypes and other constructs for use in 3GPP. The GUP data description method is designed to coexist with other data description technologies.
The document includes:
• DDM and DtDM features and definition;
• Process and procedures for administration of GUP/DDM and 3GPP TS 24.241 [12].
|
23.801
|
Potential mechanisms for Circuit Switched (CS) domain video and voice service improvements
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.801/23801-100.zip
|
This TR studies different mechanisms which might permit 3GPP based systems to rapidly enhance their customers Circuit Switched Videotelephony experience.
Many operators regard circuit video services as a key part of UMTS. However there is a strong desire to have an effective and user friendly method of switching between voice and video services when the user desires and/or when radio conditions change and video mode is no longer available. There are several situations where swapping between video and voice calls is needed.
Within the TR, different mechanisms are described along with their characteristics. A comparison of the pros and cons of the different mechanisms is included.
|
23.825
|
Overall architecture aspects of IP flow based bearer level charging; Stage 2
|
TR
|
1.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.825/23825-140.zip
|
The present document identifies the overall architecture aspects of IP flow based bearer level charging.
It is expected that the content of this TR will act as a basis for:
- Change requests against the architecture specifications [5] of SA2, clarifying the architecture implications of IP flow based bearer charging
- Change requests against the Charging Principles specification [3] of SA5, which contains the charging architecture and mechanisms.
|
23.835
|
Study into applicability of Galileo in Location Services (LCS)
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.835/23835-100.zip
|
Based on the March 2003 GALILEO system definition, in the present document, as proposed in [1]:
• the potential benefits of using Galileo (alone or combined with GPS) on service performance: in particular the availability improvements for in urban/indoor environment are highlighted.
• the expected complexity differential between 3GPP mobiles utilizing A-GPS and those that might utilize a combination of A-GPS plus “Assisted GALILEO” is described.
• the changes that might be needed to 3GPP standards to support “assisted Galileo” in addition or in combination with the currently specified assisted GPS are identified
• from the 3GPP community point of view, the desirable characteristics of GALILEO that would minimize the impact to 3GPP mobiles when introducing the extension of A-GPS techniques to GALILEO are proposed.
These informations will allow 3GPP to decide whether or not to initialise 3GPP standard changes to introduce GALILEO. The final 3GPP standard modifications should be reassessed against the final GALILEO definition.
|
23.864
|
Commonality and interoperability between IP Multimedia System (IMS) core networks
|
TR
|
0.6.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.864/23864-060.zip
|
The present document defines the key architectural items that are the building blocks for achieving commonality and interoperability between IMSs that possibly use different IP Connectivity Networks. Specific IP-connectivity access network technologies and their details are not within the scope of the present document.It is expected that one solution will be developped and finetuned for each of these architectural items. The present Technical Report serves as a placeholder for the solutions under development. When the solution reaches maturity, Change Requests against the relevant Technical Specifications will be raised.
|
23.876
|
Push architecture
|
TR
|
0.5.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.876/23876-050.zip
|
This technical report defines methods for supporting push services by 3GPP bearers. The mechanisms defined apply to existing bearers for the 3GPP Packet Switched Domain (PS domain), Circuit-Switched Domain (CS Domain), and the IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast Multicast Service, and Wireless LAN. This technical report addresses the requirements for supported push services as defined in 3GPP TS 22.174 Push Service; Service aspects (Stage 1). Any necessary changes identified during this work will be introduced by means of CRs to the appropriate specifications.
Definition of push functions that apply to push application servers is outside the scope of this work. The definition of push functions that are best implemented in push application servers such as a Push Proxy and Push Initiator will be undertaken by other standards bodies and industry forums.
|
23.881
|
Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.881/23881-100.zip
|
The present document studies study interworking and migration scenarios related to IPv4 based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4 based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6.
|
23.899
|
Combining Circuit Switched (CS) bearers with IP Multimeida Subsystem (IMS)
|
TR
|
1.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.899/23899-120.zip
|
The present document investigates architectural requirements and architectural alternatives for using existing CS bearers in association with an IM session. The document considers overall requirements, architectural requirements, considerations for evaluation of potential architectural solutions and proposed alternative architectures.
The Feasibility Study covers different solutions for offering existing IMS simultaneous services (real-time media + non-real-time media) also in GERAN, where conversational PS spectrum efficiency is too low.
The target is to seek for an architectural solution that is completely transparent for the end-user, and is easily interoperable with existing IMS services&networks that don’t use this solution.
The solutions studied within the Feasibility Study are not necessarily restricted by existing service requirements. However, if an alternative is chosen to be included in specifications, it must be cross-checked with existing service requirements.
|
23.934
|
3GPP system to Wireless Local Area Network (WLAN) interworking; Functional and architectural definition
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.934/23934-100.zip
|
Editor’s note : Identify and analyse possible system architectures for allowing WLAN based radio networks to Interwork with 3GPP based systems.
|
23.964
|
Commonality and interoperability between IP Multimedia System (IMS) core networks
|
TR
|
0.3.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.964/23964-031.zip
|
The present document defines the key architectural items that are the building blocks for achieving commonality and interoperability between IMS core networks that possibly use different IP Connectivity Networks. Specific IP-connectivity access network technologies and their details are not within the scope of the present document.It is expected that one solution will be developped and finetuned for each of these architectural items. The present Technical Report serves as a placeholder for the solutions under development. When the solution reaches maturity, Change Requests against the relevant Technical Specifications will be raised.
|
24.241
|
3GPP Generic User Profile (GUP) Common objects; Stage 3
|
TS
|
0.5.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.241/24241-050.zip
|
This specification serves as a vessel for storing and listing new DatatypesProfiles, Generic User Profile Component Groups, Profile Components, Datatypes,Fragments, and other constructs for use in 3GPP applications within various specifications, thereby serving as a means to manage the process of adding new entities of these typesDatatypes, Generic User Profile Fragments, and other constructs
The present document defines the stage three description to the 3GPP Generic User Profile (GUP) Common Objects. This document serves as a vessel to manage the process for addition of new Datatypes, Generic User Profile Group Components Fragments, Common Profile Components, and other constructs for use in 3GPP applications within various specifications.
3GPP GUP architecture, storage, distribution, ownership, etc are included in [11] and [12].
[…]
|
25.802
|
Remote control of electrical tilting antennas
|
TR
|
6.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.802/25802-600.zip
|
The present document is for the Release 6 work item "Remote Control of Electrical Tilting Antennas" (see [1]).
The objectives of this work item are the specification of a standardised open interface to enable local RET antenna-controlling functionality situated in the Node B to allow the RET antenna system being provided by a third party vendor and to enable the control of the antenna from the Network Manager, so that the operator is able to control the RET antenna remotely and consistently across the network.
The purpose of the present document is to record the required changes of the specifications and to gather all information in order to trace the history and the status of the Work Task in RAN WG3. It is not intended to replace contributions and Change Requests, but only to list conclusions and make reference to agreed contributions and CRs. When a solution for the remote control of electrical tilting antennas is sufficiently stable, the needed CRs can be issued.
Therefore, this document identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.