id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
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.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-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-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-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.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.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.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.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.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.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.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.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.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.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.
|
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.
|
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.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
| |
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.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.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.
|
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.703
|
Study on architecture enhancements to support Proximity-based Services (ProSe)
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.703/23703-c00.zip
|
The present document is limited to the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Proximity-based Services (ProSe) based on the relevant Stage 1 requirements as defined in TS 22.278 [3] and TS 22.115 [4].
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.303 [26].The text of the present document was not updated to align with normative specifications.
|
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.800
|
Study on Application Based Charging (ABC); Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.800/23800-c00.zip
|
This Technical Report defines key issues and studies PCEF/TDF charging solutions for the network usage of services and applications when TDF performs application detection and control. Both online and offline charging aspects will be considered. The work will be based on the Rel‑11 Policy and charging control architecture, including the specification for application detection and control and the corresponding TDF functionality definition, as defined in TS 23.203 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces will be identified.
The agreed solutions will be evaluated for subsequent normative specification.
|
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.
|
23.843
|
Study on Core Network Overload (CNO) solutions
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.843/23843-c00.zip
|
The present document investigates core network signalling overload scenarios and potential general handling solutions, in particular:
1. Identify and document events that have occurred and caused network disturbances due to signalling overload. In addition, identify and document scenarios that have high probability of occurrence in the 3GPP network, which may result in signalling overload for core network entities. Such scenarios/events may include HLR/HSS overload by RNC restart, denial of service attacks, and misbehaving/3GPP-non-compliant mobiles causing unpredictable system response;
2. Analyse the criticality of the scenarios and determine whether it is required to take actions for the identified scenarios;
3. Study ways to mitigate and/or eliminate the impact on the core network from signalling overload scenarios that are identified to be critical.
The information provided about the HSS/HLR overload will serve as a starting basis for the study. All currently deployed 3GPP networks should be covered in the study, including LTE
The study should avoid overlap with other parallel activities within 3GPP, and work in close cooperation with the specific WG needs to be maintained.
During the study, if potential security threats such as denial of service attack scenarios are identified, SA WG3 must then be informed to take appropriate measures.
|
23.844
|
Feasibility study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.844/23844-c00.zip
|
This study focuses on the enhancement of IMS to support Peer-to-Peer Content Distribution Services in respect of GPRS, EPC and other underlying access network technologies but not intend to modify GPRS or EPC for P2P mechanism.
The objectives are to study IMS based Peer-to-Peer Content Distribution Services on the architectural level with the following aspects:
- Creating solutions in order to fulfil the use cases and requirements as defined by SA WG1 while avoiding duplicate work in other SDOs, such as IETF [e.g., PPSP, P2PSIP, ALTO, and DECADE], and re-using their work. The solutions should:
- Apply the same IMS user management/registration procedure as other IMS services;
- Be able to provide the UE with the appropriate AS to obtain the addresses of other Peers, from which the UE can retrieve the requested content;
- Re-use ISC interface for service triggering;
- Be able to select qualified User Peers among available UEs according to the policies preconfigured in the network.
- Elaborate alternative solutions, which support the following network access technologies:
- Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);
- Fixed access only (e.g. xDSL, LAN);
- Fixed and mobile convergence scenarios.
- Evaluate possible impacts and improvements on network when IMS based Peer-to-Peer Content Distribution Services are deployed, such as the interactions that are needed to adapt the peer-to-peer overlay properties to the configuration and the resources of the network.
- Identify QoS, mobility, charging and security related requirements in the case of Peer-to-Peer Content Distribution Services on IMS.
The assessment on alternative solutions and the final conclusion of this study should not only take TR 22.906 [2] into consideration but also comply with the related normative work in SA WG1.
|
23.852
|
Study on S2a Mobility based on GPRS Tunnelling Protocol (GTP) and Wireless Local Area Network (WLAN) access to the Enhanced Packet Core (EPC) network (SaMOG); Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.852/23852-c00.zip
|
This Study item is to study:
1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a.
2. Supporting WLAN access to EPC through S2a via mechanisms:
2.1 with no impact to the UE;
2.2 with impact to the UE.
Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI).
|
23.853
|
Operator Policies for IP Interface Selection (OPIIS)
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.853/23853-c00.zip
|
This Technical Report describes solutions that define:
- operator policies for selecting an IP interface in the UE for routing of IP flows among a choice of available interfaces in both 3GPP and non-3GPP accesses;
- system architecture for distribution of these policies to the UE.
Editor's note: The working assumption is that the ANDSF architecture is used for distribution of the operator policies defined in this TR.
The solutions described in this TR shall clarify how the operator policies defined in this TR relate with the ANDSF policies.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to select a solution and include it in the relevant technical specifications.
|
23.859
|
Local IP access (LIPA) mobility and Selected IP Traffic Offload (SIPTO) at the local network
|
TR
|
12.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.859/23859-c01.zip
|
This Technical Report describes the solutions to implement the architectural aspects based on the requirements from TS 22.220 [3], clauses 5.7 and 5.9, and TS 22.101 [2], clause 4.3.5, for LIPA and SIPTO at the local network.
This includes:
- the support of mobility for LIPA between the H(e)NBs located in the local IP network;
- functionality to support Selected IP Traffic Offload requirements at the local network, including mobility.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to include the solutions in the relevant technical specifications.
|
23.862
|
Evolved Packet Core (EPC) enhancements to support interworking with data application providers; Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.862/23862-c00.zip
|
This Technical Report describes solutions for interworking between mobile operators and data application providers. The solutions developed will describe a framework for authentication, authorization, policy and charging for various interworking scenarios.
Solutions developed as part of this work item will cover the following different relationships between mobile operators and data application providers for both roaming and non-roaming cases when
- mobile operator owns all the application layer entities;
- mobile operator does not own all the application layer entities.
The technical report will investigate charging, policy and group addressing capabilities for interworking between mobile operators and data application providers. Updates to 3GPP functions and interfaces will be specified for solutions based on IMS and/or EPC.
On-going work for authentication and other aspects in other 3GPP work items will not be duplicated. It will be investigated whether changes to 3GPP specifications are needed and if so which ones. The work item will focus on impacts to IMS and EPC.
|
23.863
|
Support of Short Message Service (SMS) in IP Multimedia Subsystem (IMS) without Mobile Station International ISDN Number (MSISDN); Stage 2
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.863/23863-c00.zip
|
This Technical Report is to specify architecture enhancement toward SMS submit/delivery mechanism in IMS to allow IMS registered UE to:
- Receive and send SMS without requiring an MSISDN associated as part of their IMS subscription record in HSS and
- any possible enhancements towards the related storing and forwarding mechanism if the UE is out of reach.
There are three potential aspects for these IMS UEs without MSISDN that need to be investigated:
1) Server - IMS UE communication via SMS (e.g. for M2M).
2) IMS UE to IMS UE communication via SMS for person to person communications. Both UEs do not have MSISDN.
3) SMS Interworking between IMS UE without MSISDN and traditional UE (e.g. CS) with MSISDN.
Normative specification work (if needed or feasible) for each of these areas can be started independently.
|
23.865
|
Study on Wireless Local Area Network (WLAN) network selection for 3GPP terminals; Stage 2
|
TR
|
12.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.865/23865-c10.zip
|
This Technical Report describes enhancements to solutions for WLAN network selection. The solutions are based on architectures as specified in TS 23.402 [9] and will take into account Hotspot 2.0 specifications developed by the WFA. 3GPP operator's policies for WLAN network selection will be provisioned on 3GPP terminals via pre-configuration or using the ANDSF server for their delivery. The scope of the technical report will be as follows:
1. Evaluate existing 3GPP WLAN PLMN and access network selection procedures for 3GPP terminals which use Hotspot 2.0 procedures and provisioned network operator policy (e.g. mechanisms based on WLAN and ANDSF) for any needed changes to current specifications. This may require enhancements to the ANDSF framework. The established 3GPP PLMN network selection (according to TS 23.122) shall not be impacted. The work must ensure there are no conflicts between existing 3GPP PLMN network selection and the 3GPP WLAN PLMN access network selection procedures defined by this WID.
2. Ensure that the content in the Management Object related to 3GPP operator policy provisioning for WLAN network selection procedures and the operator policy provisioning in WFA MO for WLAN network selection are consistent.
3. Identify solutions to resolve potential conflicts between policies provided by non-3GPP providers via Hotspot 2.0 mechanisms and policies provided by 3GPP operators using ANDSF.
This work applies to non-seamless WLAN offload as well as to trusted and untrusted WLAN access to EPC with/without seamless offload. It will be investigated whether changes to 3GPP specifications are needed and if so which ones.
|
23.866
|
Study on system improvements for energy efficiency
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.866/23866-c00.zip
|
The present document is for investigating deployment aspects that relate to energy efficiency, including potential system enhancements that support energy efficient deployments. System enhancements may be anticipated in the area of functions that have major influence on deployment like functions that support pools of CN nodes or functions that enable multiple CN nodes to serve the same or overlapping areas. The initial focus is on PS domain. This study should avoid any overlap with the work by RAN/CT/SA5 by taking into account the work that has been and is going on in these WGs. Proposals have to be well justified to be considered in this document.
|
23.887
|
Study on Machine-Type Communications (MTC) and other mobile data applications communications enhancements
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.887/23887-c00.zip
|
The present document studies and evaluates architectural enhancements for Machine-Type and other mobile data applications Communications.
Specifically, the following system improvements are considered:
- Small Data Transmission (SDT) which includes the following aspects:
- SDT as per the service requirements (TS 22.368, clause 7.2.5); and
- Efficient handling of frequent SDT as per the service requirement (TS 22.101, clause 4.3.1).
- Triggering enhancements which includes the following aspects:
- Device triggering enhancements including T5 based device trigger and other triggering efficiency optimizations.
- Monitoring enhancements which includes the following aspect:
- Monitoring as per the service requirements (TS 22.368, clause 7.2.8).
- UE Power optimizations which includes the following aspects:
- Optimizations to prevent battery drain (that may come from e.g. frequent changes between idle and connected mode or too long periods in connected mode); and
- Lower UE power consumption as per the service requirements (TS 22.368, clause 7.1.1).
- Group based features which include the following aspects:
- Fulfil the group based policing requirements (TS 22.368 clause 7.2.14.2);
- Fulfil the group based addressing requirements (TS 22.368 clause 7.2.14.3); and
- Fulfil the group based charging requirements (TS 22.368 clause 7.1.5).
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services as provided by the 3GPP system and the related optimizations are considered in this study.
The present document analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
|
23.890
|
Optimized offloading to Wireless Local Area Network (WLAN) in 3GPP Radio Access Technology (RAT) mobility
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.890/23890-c00.zip
|
This technical report describes key issues and solutions for optimized offloading of traffic to WLAN access when PS mobility between 3GPP RAT takes place. The technical report analyzes the user and service impact due to mobility between 3GPP RATs. The technical report analyzes the key issues and solutions in order to identify whether current mechanisms documented in SA2 specifications are sufficient, identify potential inefficiencies, and identify whether additional solutions are needed to address the key issues.
The technical report also describes proposed extensions to ANDSF in order to enable policy differentiation for 3GPP RATs (e.g. E-UTRAN versus UTRAN, GERAN versus UTRAN) with respect to WLAN, in order to enable a UE to distinguish preferences of WLAN with respect to specific 3GPP RATs upon acquiring connectivity (e.g. PDN creation in a 3GPP RAT or WLAN, or establishing NSWO connectivity) or upon mobility.
|
23.897
|
Feasibility study on IP Multimedia Subsystem (IMS) business trunking for Internet Protocol Private Branch Exchange (IP-PBX) in Static Mode of Operation
|
TR
|
12.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.897/23897-c00.zip
|
During the production of the 3GPP Release 7 specifications it was recognized that the IP Multimedia Subsystem was suitable for serving both mobile and fixed installations and a number of specifications developed by ETSI TISPAN were therefore embedded in the 3GPP specifications to form the Common IMS. Among other aspects, Common IMS requires that the IMS is able to connect with Next Generation Corporate Networks (NGCN), also known as IP-PBXs (see ETSI TS 181 019 [3]).
Managing the connection to IP-PBXs which do not use registration procedures when connecting to the IMS and operate in a static mode that is to enable the IMS to receive and send traffic to an IP-PBX, is realized by means of configuration within the network. The static mode of operation can be used in 2 scenarios, peering based business trunking and subscription based business trunking. The static mode of operation for both of the above mentioned scenarios can be studied in this TR.
It was however observed that the number of implementations of IP-PBXs that are operated in a static mode (e.g. based on the SIPConnect specifications recently released by the SIP Forum) increases.
The purpose of this study is to enable the IMS to manage connections to a large number of IP-PBXs that are operated in a static mode, with minimized configuration in the network.
|
24.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3
|
TS
|
12.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.234/24234-c20.zip
|
The present document specifies the network selection, including authentication and access authorization using authentication, authorization and accounting (AAA) procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification the network includes the WLAN and 3GPP network.
Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology specific protocols, however this signalling is transparent to the WLAN.
Tunnel management procedures are defined to be independent of the underlying WLAN access technology and as such can be reused independently of the underlying technology.
The present document specifies procedures within I-WLAN necessary in order for IMS emergency calls to be supported when I-WLAN is used as the underlying access network. These involve both network selection as well as tunnel management procedures.
WLAN Network Selection supersedes I-WLAN for UE WLAN selection as specified in 3GPP TS 24.302 [28] from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
24.235
|
3GPP System to Wireless Local Area Network (WLAN) interworking Management Object (MO)
|
TS
|
12.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.235/24235-c10.zip
|
This document defines the 3GPP System to Wireless Local Area Network interworking Management Object (MO) for I-WLAN PLMN selection as specified in 3GPP TS 24.234 [3]. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD_DM-V1_2 [2].
The 3GPP System to Wireless Local Area Network interworking Management Object consists of relevant parameters that can be managed for WLAN UE as specified in 3GPP TS 24.234 [3].
The Access Network Discovery and Selection Function MO as specified in 3GPP TS 24.312 [13] supercedes the Wireless Local Area Network interworking MO for I-WLAN PLMN selection from Rel-12 onwards.
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
24.327
|
Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN) and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3
|
TS
|
12.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.327/24327-c00.zip
|
This document specifies the signalling procedures for handling the mobility of a UE between 3GPP Wireless Local Area Network Interworking (I-WLAN) and GPRS systems.
The present document is applicable to the User Equipment (UE) and the network nodes supporting mobility between 3GPP I-WLAN and GPRS systems.
In addition, the present document specifies the procedures used between the UE and the network nodes for the attach and the detach cases. It also specifies how the UE performs handover when moving from 3GPP I-WLAN to GPRS systems and vice-versa.
This document is based on DSMIPv6 procedures specified in 3GPP TS 24.303 [3] and will specify additional details specific to the 3GPP I-WLAN and GPRS systems in the context of mobility.
|
24.802
|
Study on Indication of Network to Network Interface (NNI) routeing scenarios in Session Initiation Protocol (SIP) requests in the IP Multimedia Subsystem (IMS)
|
TR
|
12.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.802/24802-c10.zip
|
The present document provides a study of the IMS impacts for providing a solution for determination of Inter‑IMS Network to Network Interface (II-NNI) traversal scenario type. The document describes and analyses different II‑NNI traversal scenarios. The present document describes requirements and investigates the implementation options to fulfil requirements for determination of II-NNI traversal scenario type.
Examples of scenarios to study are:
- the visited to home scenario;
- the home to visited scenario;
- the loopback scenario;
- the invocation of MRB/MRF in visited network from an AS in home network scenario; and
- a request sent from the home network on the originating side to the home network on the terminating side.
The present document includes the study of the existing protocol mechanism and new protocol mechanism for further evaluation what is needed to identify a particular II-NNI traversal scenario type.
The study also considers existing deployments.
The present document analyses and evaluates different solutions.
|
24.803
|
Study on telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3
|
TR
|
12.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.803/24803-c00.zip
|
The present document contains the study on Telepresence using IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), Session Description Protocol (SDP) and other protocols of controlling multiple streams for Telepresence based on service requirements.
The study aims, within the defined CT1 work areas, at:
- analysing IMS session procedures and signalling between the UE and core network for Telepresence creation, establishment with media negotiation and configuration, session modification and termination, with the incorporation of new protocol (i.e. CLUE as under developing in IETF);
- investigating impacts for presentation in Telepresence and floor control in IMS;
- analysing similar impacts to allow legacy devices interworked with Telepresence using IMS; and
- studying potential enhancements and extensions to facilitate these procedures.
This study will identify specification areas, if any, that lie within the scope of other 3GPP working groups, and seek input from those 3GPP working groups to define that related specification work.
|
25.700
|
Study on Further Enhanced Uplink (EUL) enhancements
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.700/25700-c00.zip
|
In the past few years, a considerable increase in number of users as well as offered traffic per user has been experienced in HSPA networks, both in the downlink and in the uplink.
In response to this, several features have been standardized in 3GPP. These include multi-carrier HSPA, downlink and uplink CELL_FACH state enhancements, and introduction of downlink and uplink MIMO. However, much of the focus has been on improving downlink performance and further enhancements are needed for the uplink to handle increasing traffic load as well as new traffic types.
|
25.701
|
Study on scalable UMTS Frequency Division Duplex (FDD) bandwidth
|
TR
|
12.2.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.701/25701-c20.zip
|
The present document is the result of the study item "Scalable UMTS FDD Bandwidth".
This study identifies target scenarios and investigates candidate solutions by considering benefits and technical complexity. The detailed objectives are described in RP-130221 [3].
|
25.702
|
Study on Dedicated Channel (DCH) enhancements for UMTS
|
TR
|
12.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.702/25702-c10.zip
|
The present document captures design options, evaluation results and analysis from the study item on "DCH enhancements for UMTS" described in [2].
The work under this study intends to capture the merits and feasibility of DCH Enhancements in terms of the reduction in the average required power per user on the downlink and the average RoT consumed on the uplink. An evaluation of the increase in UE data throughput in a mixed voice-data traffic scenario when DCH enhancements were applied is also conducted.
The following enhancements are considered in the study:
• DL Physical Layer Enhancements
◦ DL DPCCH Slot Format Optimization
◦ DL DPDCH Frame Early Termination
◦ DL ACK Indicator design for UL FET
◦ DPCH Time Domain Multiplexing
◦ Reduced power control rate schemes
◦ Node B DTX/UE DRX Mechanisms
• UL Physical Layer Enhancements
◦ UL DPCCH Slot Format Optimization
◦ UL Frame Early Termination
◦ UL ACK Indication for DL Frame Early Termination
◦ DTCH/DCCH time compression
◦ Reduced power control rate schemes
◦ UE DTX/Node B DRX mechanisms
Additionally, the following aspects are also investigated:
• UE Power Consumption Efficiency
• Impact on Network implementation
• Impact on UE implementation
• Impact on specifications
|
25.703
|
Universal Terrestrial Radio Access (E-UTRA); Study on Home Node B (HNB) emergency warning area
|
TR
|
12.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.703/25703-c00.zip
|
The present document captures the result of the Study on HNB Emergency Warning Area for UTRA (RP-131258 [2]).
|
25.704
|
Study on enhanced broadcast of system information
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.704/25704-c00.zip
|
The present document captures the studies for [2] about the need to introduce mechanisms in UMTS to provide additional broadcast capacity, considering:
- the currently existing deployments and their future evolutions,
- the broadcast load expected from different releases, including Rel-11 and estimate for Rel-12,
- the impact on system performance and end-user experience in case of increased system information scheduling latency.
|
25.800
|
Technical Report on UMTS Heterogeneous Networks
|
TR
|
12.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.800/25800-c10.zip
|
The present document captures evaluation results and analysis from the study item on "UMTS Heterogeneous Networks" described in [2].
|
26.235
|
Packet switched conversational multimedia applications; Default codecs
|
TS
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.235/26235-c00.zip
|
The present document introduces the set of default codecs for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communication are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document is applicable, but not limited, to services such as PS video telephony and Push to talk over Cellular (PoC) as well as Combined CS and IMS services (CSI). For Multimedia Telepphony Service for IMS (MTSI), all media handling, including codecs, is defined in TS 26.114 [50]. This specification does not apply for MTSI.
The applicability of this specification to GERAN is FFS.
|
26.236
|
Packet switched conversational multimedia applications; Transport protocols
|
TS
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.236/26236-c00.zip
|
The present document introduces the required protocols for packet switched conversational multimedia applications within 3GPP IP Multimedia Subsystem. Visual and sound communications are specifically addressed. The intended applications are assumed to require low-delay, real-time functionality.
The present document describes the required protocol related elements for 3G PS multimedia terminal:
• required SDP signalling regarding the media type bit rate, packet size, packet transport frequency;
• usage of RTP payload for media types;
• bandwidth adaptation;
• QoS negotiation.
The present document is applicable, but not limited, to packet switched video telephony. All media handling, including codecs, for Multimedia Telephony Service for IMS (MTSI) service is defined in [35]. This specification does not apply to MTSI.
The applicability of the present document to GERAN is FFS.
|
26.827
|
IP Multimedia Subsystem (IMS) based streaming and download delivery enhancements
|
TR
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.827/26827-c00.zip
|
The objectives of the Work Item on IMS-based Streaming and Download Delivery Enhancements (IMS_SDE) include:
- Identify use cases and recommended requirements based on Release 10/11 functionality included in the PSS and MBMS specifications to be addressed for IMS-based streaming and download enhancements, and document the adopted use cases.
- Develop procedures towards enabling the IMS-based extensions of the identified use cases in TS 26.237.
The present document is written in a form that the recommendations made and assumptions stated are directed to authors and contributors to Technical Specifications being affected as a result of the study presented here.
|
26.848
|
Multimedia Broadcast/Multicast Service (MBMS); Enhanced MBMS operation
|
TR
|
12.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.848/26848-c00.zip
|
The present document covers the MBMS enhancement aspects, including MBMS Over The Air (OTA) efficiency, MBMS for datacasting and real-time content, and generic signalling of DASH transport over broadcast, multicast and unicast.
|
26.849
|
Multimedia Broadcast/Multicast Service (MBMS) improvements; MBMS operation on demand
|
TR
|
12.1.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.849/26849-c10.zip
|
The present document covers:
- Use cases on the dynamically establishment of MBMS User Services to offload unicast delivery of certain contents, either real-time or non-real-time based, which reach a certain traffic volume due to the popularity of those contents.
- Use cases for terminating a previously established MBMS User Service due to subsequently decrease in its consumption.
- Recommended requirements on the BM-SC and UE to support on-demand MBMS.
- Gap analyses in the existing TR 26.346 specification for supporting the recommended requirements for MooD operation.
- High-level MBMS and unicast network architecture in the context of MooD.
- Message sequence diagrams illustrating examples of MooD operation.
- Description of solution frameworks that enable MooD operation, including configuration data, necessary interaction between BM-SC and UE to activate or trigger the MBMS client for reception of newly-established MBMS User Service, and the reporting of ongoing consumption of the MBMS service to enable measurement of ongoing demand for that service.
|
28.820
|
Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Operation Model (FNOM) Umbrella Operation Model (UOM)
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.820/28820-c00.zip
|
The present document is the result of the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules.
Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original, for comparison with the corresponding TMF version.
Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report.
As a result of the analysis of the requirements for the harmonization of the 3GPP and TM Forum Information Models in the context of FMC basic use cases were developed 3GPP TR 32.833 [1], TM Forum TR 166 [2]. These use cases led to the recognition that it would be necessary to define common operation model elements applicable for wire-line and wireless networks. The present document defines these common model elements.
To be noted:
- The Umbrella Operation Model (UOM) described in the present document provides the set of interfaces/operations etc. that have been agreed for convergence to strengthen consistency of representation and semantics of network management operations in the fixed and mobile environments.
- The UOM is necessary but not sufficient for implementation.
- The UOM cannot be used directly for implementation. Implementation classes must be derived from those in the UOM by Inheritance or some other appropriate mechanism.
- Classes derived from those in the UOM (e.g. for the fixed environment) may use different names from those used in the UOM.
|
29.806
|
Study on IP Multimedia Subsystem (IMS) Proxy Call Session Control Function (P-CSCF) restoration procedures
|
TR
|
12.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.806/29806-c10.zip
|
The present document analyses existing P-CSCF restoration mechanism limitations and drawbacks, as defined by 3GPP TS 23.380 [2] and 3GPP TS 24.229 [3], and proposes alternative solutions that could minimize such limitations.
Expected output from this document is a proposal of an enhanced P-CSCF restoration mechanism.
|
29.807
|
Study on General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTP-C) overload control mechanisms
|
TR
|
12.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.807/29807-c00.zip
|
The present document investigates various aspects related to the support of the GTP-C signalling based load / overload control solution as specified in 3GPP TS 23.401 [2] and TS 23.060 [3], as also concluded in TR 23.843 [4], with the main focus on:
• Definition of "Load Control" and "Overload Control" related information with enough precision to guarantee a common multi-vendor interpretation of this information allowing inter-operability between various GTP-C nodes;
• Mechanisms to address various "Notes", which are targeted to the stage 3, specified in clause 8.2.5, clause 8.2.6 & clause 10.2 of the 3GPP TR 23.843 v1.0.0 [4].
This technical report addresses the following aspects related to the "GTP-C signalling based load and overload control" feature in detail:
- Investigation and study of the following aspects related to the "Load Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Load Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of "Load Control Information" in GTP-C messages.
- Potential enhancements to the existing node selection algorithm to take information received from "Load Control Information" into account.
- Investigation and study of the following aspects related to the "Overload Control Information" to fulfill the normative requirements or to produce recommendations.
- Definition of the "Overload Control Information" by evaluating various parameters which can be exchanged under this information.
- Inclusion of the "Overload Control Information" in GTP-C messages.
- Message throttling algorithms and message prioritization when congestion mitigation is applied.
- Propagation of the MME/SGSN identity to the PGW to ensure that the overload mitigation is always applied to the currently serving MME/SGSN.
- Potential interactions with the existing overload control mechanisms when the overload factor is received within the "Overload Control Information".
- Investigation and study of the following the other deployment related aspects to fulfill the normative requirements or to produce recommendations.
- Applicability of this feature to 3GPP and non-3GPP based GTP-C interfaces.
- Methods to discover the support of this feature by the peer node in the network.
- Supporting the feature across the PLMN boundary.
- Issues within the network with partial support of this feature.
- Overload mitigation policies when this feature support is not enabled in the network.
|
29.809
|
Study on Diameter overload control mechanisms
|
TR
|
12.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.809/29809-c00.zip
|
The present document investigates possible enhancements of the Diameter base protocol (IETF RFC 6733 [2] and existing Diameter applications to support overload control mechanisms in 3GPP core networks.
This work is based on the results of the feasibility study on Core Network Overload available in 3GPP TR 23.843 [3] and the related work done in the IETF Diameter Maintenance and Extensions (DiME) working group.
This study will cover:
- Identification of the set of requirements for an improved overload control mechanism over Diameter based signaling interfaces used in 3GPP core networks.
- Identification, evaluation and selection of candidate solutions for overload control mechanisms, including:
- Mechanisms to detect overload situations e.g. notification of Diameter end-point signaling load;
- Mechanisms to exchange overload control policies between Diameter end-points;
- Details on the expected behaviour of 3GPP core network nodes supporting the defined overload control mechanism (Diameter end-points and Diameter agent);
- Evaluation of the impacts of the proposed solution(s) on existing Diameter-based Technical Specifications and Diameter based signalling networks (internal operator networks, inter-operator network (e.g. IPX).
- Recommendations on the solutions to select depending of the applicability context (interfaces, application, network, etc.)
The results of this study will contribute to the work done within the IETF DiME working group on Diameter overload control, through official liaison statement from 3GPP or company-driven individual contributions, which includes:
- Provide feedback from 3GPP on the requirements for Diameter overload control mechanisms defined in IETF Draft draft-ietf-dime-overload-reqs-06 [4]);
- Contribute to the specification of the IETF standard mechanism for overload control over Diameter.
The results of this study will be used to identify the changes required in the 3GPP specifications to support overload control mechanisms over Diameter-based 3GPP interfaces and applications.
|
29.817
|
Study on eXtensible Markup Language (XML) based access of the Application Function (AF) to the Policy and Charging Rules Function (PCRF)
|
TR
|
12.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.817/29817-c10.zip
|
The Technical Report describes solutions for an XML based protocol (e.g. SOAP, Restful HTTP, etc.) between the AF and the PCRF for the case of non IMS applications. The scope of this work is to provide an XML based equivalent to the Diameter based signalling that is presently specified in 3GPP TS 29.214 [5].
This study covers the following alternatives:
- XML based protocol between AF and PCRF;
- Adding a new protocol converter (as a stand-alone entity) between PCRF and AF
Investigate a suitable transport protocol for XML, charging issues in case of 3rd party SPs, security issues.
Roaming in both home routed and local break out and signalling routing aspects (e.g. DRA handling and others aspects) has also been included.
Necessary changes to 3GPP specifications are identified.
|
29.828
|
Study on extended IP Multimedia Subsystem (IMS) media plane security features and Transmission Control Protocol (TCP) related Network Address Translation (NAT) traversal support; IMS H.248 profiles aspects
|
TR
|
12.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.828/29828-c10.zip
|
The present document investigates the IMS H.248 profiles requirements and procedures to support the stage 2 requirements specified in 3GPP TS 33.328 [2] for Extended IMS media plane security features.
This includes in particular the following aspects:
1. Provide end-to access edge protection of session based messaging (MSRP) traffic using TLS and certificates fingerprints exchanged over SDP;
2. Provide end-to-end protection of session based messaging (MSRP) traffic using TLS;
3. Provide end-to access edge protection of BFCP based traffic, using TLS and certificates fingerprints exchanged over SDP;
4. Provide optional support of TLS protection of BFCP and MSRP based traffic at the Conference Server.
5. Analyse requirements and procedures for end-to-end TCP bearer connection control and related NAT traversal support.
NOTE: this aspect is not specific to media security and may result in normative work via another work item.
6. Provide support of TCP-based IP transport connections for TLS security sessions, which includes possible NAT traversal support during the TCP connection establishment phase, possible correlations between the establishment (and release) events of TCP connections with TLS session establishment (and release).
7. Provide end-to access edge protection of T.38 fax using DTLS.
This study will cover:
- Identification of the key issues and the main design considerations that should drive the definition of stage 2 requirements and procedures for the Iq, Ix and Mp profiles;
- Identification of the requirements and procedures for the Iq, Ix and Mp profiles for support of end-to-access edge and end-to-end media security for session-based messaging (MSRP [6]) and conferencing (BFCP [16]);
- Identification of the requirements and procedures for the Iq profile for support of end-to-access edge media security for T.38 fax over UDPTL/UDP transport;
- Identification of the ITU-T H.248 extensions necessary to fulfil the 3GPP requirements and identification of potential missing gaps that should be taken into account by ITU-T Q3/16;
- Conclusions and Recommendations for the normative work.
The results of this study will be used to identify the changes required in the 3GPP specifications to support Extended IMS media plane security.
|
29.854
|
Study on shared data update for multiple subscribers
|
TR
|
12.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.854/29854-c20.zip
|
The present document analyses the use cases for the need of update of subscription data shared by multiple subscribers, the existing mechanisms in 3GPP networks which is or may be used for shared data update, possible solutions and impact on the existing interfaces and relevant elements.
The recommendation of the document is used to decide whether it is required to standardize any solution, and which is the final preferred solution if further standardization is needed.
|
32.830
|
Telecommunication management; Study on version handling over Itf-N
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.830/32830-c00.zip
|
The scope of the study is to:
• Document current version handling capabilities in SA5 OAM specifications (clause 5)
• Identify and agree on the use cases and requirements (clause 6) for a coherent approach for version handling capabilities for SA5 OAM specifications
• Identify solution(s) with pros and cons to support the identified requirements (clause 7). The solutions may require enhancement or modification of rules in the IRP methodology as well as enhancements of existing or addition of new IRP specifications, utilizing SOA capabilities where appropriate. This includes:
1. The identification of entities that require version control (clause 7.1)
2. The protocol(s) by which the entity version can be discovered and registered (clause 7.2)
• Recommend a solution (clause 8).
Note: "Version handling" in the context of this study addresses what kind of support for version information that is available over the Itf-N interface, i.e. what the IRPManager can "see" regarding which versions of the 3GPP specifications that are supported by the IRPAgent, for which object instances etc.
|
32.835
|
Telecommunication management; Study of heterogeneous networks management
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.835/32835-c00.zip
|
The present document investigates and makes recommendations on how management information can be selected by the manager over Itf-N for heterogeneous networks (see TR 21.905 [1]) nodes that are owned, deployed and maintained by the operator.
The nodes that are owned, deployed or maintained by residential users are out of scope of the present document, such as Home NodeBs, Home eNodeBs.
|
32.836
|
Telecommunication management; Study on Network Management (NM) centralized Coverage and Capacity Optimization (CCO) Self-Organizing Networks (SON) function
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.836/32836-c00.zip
|
The present document summarizes the result of the study on "Enhanced Network Management (NM) centralized Coverage and Capacity Optimization".
A CCO function that resides outside the NM is out of the scope for this study.
|
32.841
|
Telecommunication management; Study on Wireless Local Area Network (WLAN) management
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.841/32841-c00.zip
| |
32.844
|
Study of charging support of Proximity-based Services (ProSe) direct communication for public safety use
|
TR
|
12.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.844/32844-c00.zip
|
The present document contains the outcome of the study on the charging architecture for the one-to-many "ProSe Direct Communication for ProSe-enabled Public Safety UEs".
The study covers the "ProSe Direct Communication for Public Safety use" as specified in TS 23.303 [238], in order to meet the charging requirements specified in TS 22.115 [101].
The present document makes recommendations for the following aspects of ProSe Direct Communication for Public Safety use:
- charging requirements and principles;
- charging architecture and charging scenarios, with the support of delayed reporting;
- charging interfaces; and
- recommendations to CT1 on UE reporting configuration and usage information elements.
|
32.851
|
Telecommunication management; Study on Operations, Administration and Maintenance (OAM) aspects of Network Sharing
|
TR
|
12.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.851/32851-c20.zip
|
The present document is aimed at addressing the operational implications of network sharing.
There are a wide variety of deployment scenarios for network sharing.
Scenarios identified in 3GPP TS 23.251 [3] and TR 22.951 [2] are taken into consideration to identify OAM impacts.
3GPP TS 23.251 "Network sharing; Architecture and functional description" specifies the stage 2 descriptions which are also considered to address OAM aspects.
NGCOR defined RAN sharing requirements are taken into account as input for this study.
|
32.859
|
Telecommunication management; Study on Alarm Management
|
TR
|
12.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.859/32859-c10.zip
|
The scope of the present document is to study how to improve the quality of alarms and enhance usability of alarm systems.
|
33.804
|
Single Sign On (SSO) application security for Common IP Multimedia Subsystem (IMS) based on Session Initiation Protocol (SIP) Digest
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.804/33804-c00.zip
|
The objective of this study item is to provide reference material for IMS based non-UICC based Single Sign On (SSO) to applications. This study item targets to re-use the SIP Digest Credentials for SSO to applications by re-using Common IMS and existing security elements. The study should describe needed extension to enable a re-use of SIP Digest credentials in Common IMS for providing security between a terminal and an application server. The study aims to maximise the commonalities of the SSO_APS with the currently defined application security approaches in 3GPP while efficiently satisfying the needs of Common IMS deployments using SIP Digest.
The Technical Report targets to bring forth approaches with a security level for access to applications using SSO_APS that is at least as good as that provided by SIP Digest for Common IMS. This Technical Report is intended to be used where the usage of UICC is not possible in a UICC-less environment. If the usage of UICC is possible, then it is expected to used, but that is outside the scope of the present study.
The scope of this Technical Report (Study Item Code SSO_APS) is restricted to environments where the storage of credentials on a UICC is not mandated.
|
33.805
|
Study on security assurance methodology for 3GPP network products
|
TR
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.805/33805-c00.zip
|
The present document studies methodologies for specifying network product security assurance and hardening requirements, with associated test cases when feasible, of 3GPP network products. Network product security assurance and hardening refers to protection against unwanted access to a 3GPP network product, its Operating System, and main running Application(s). The suitability of industry standard methodologies and the potential need for collaboration with bodies such as GSMA, CCRA, ISO and ITU will be assessed. The study will also consider regulatory aspects and the potential need for security certification. The suitability of the candidate methodologies will be assessed with reference to real world examples.
Part of the scope of this work is to conclude which 3GPP network products, if not all, would be subject to 3GPP network product security assurance and hardening requirements. There is likely to be a long list with the result that prioritisation will be required. LTE network product classes will be the first priority. The work will also study exactly what should constitute a 3GPP network product in the context of this study e.g. whether it should be an individual 3GPP functional entity, a group of 3GPP functional entities or some other realisation.
The study will also include assessing the extent to which individual 3GPP network products need to be hardened beyond a common baseline and should take into consideration network vs. environment.
|
33.823
|
Security for usage of Generic Bootstrapping Architecture (GBA) with a User Equipment (UE) browser
|
TR
|
12.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.823/33823-c20.zip
|
This work in this Technical Report has the following scope:
- Study the potential threats for different GBA credentials use scenarios via a web browser. These new use scenarios (e.g. using HTML forms, using Javascript, using widgets) are not covered by current specifications.
The scope of this Technical Report will cover the following:
- Study, identify and specify any protection mechanism that maybe additionally required for the GBA credentials;
- Study, identify and potentially specify usage control for GBA credentials;
- Study, identify and potentially specify access control mechanism for GBA module;
- Study, identify and potentially specify the usage of web based GBA as an extension on the current protocol mechanisms used on Ua reference point (e.g. new Ua protocol identifier);
- Identify and outline how GBA can be used with HTML Forms and Javascript securely (e.g. describing GBA - web specific common practices and examples).
This Technical Report will collect the potential specification improvements, which are then at a later stage of work transferred to the appropriate Technical Specifications. The potential improvements for access control to GBA credentials and potential Ua protocol impacts will then be documented in TS 33.220 [2]. The threat analysis, common security implementation practices and examples may build a new chapter 5 in TS 33.222 [3].
Relation to GBA variants defined in other documents: Web based GBA aims at defining web enhancements for the use of HTML forms with GBA. It is a new variant for the Ua interface and does not affect the Ub interface, as opposed to the GBA variants defined in TS 33.220. Web based GBA is orthogonal to these other GBA variants and can be used with any of them.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.