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
|
|---|---|---|---|---|---|---|
33.885
|
Study on security aspects for LTE support of Vehicle-to-Everything (V2X) services
|
TR
|
14.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.885/33885-e10.zip
|
The present document contains a study of the security aspects of V2X services and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.185 [2]. Potential stage 2 solutions for V2X Services are being studied in TR 23.785[3].
|
36.714-00-00
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for x Down Link (DL) / y Up Link (UL) including contiguous and non-contiguous spectrum
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-00-00/36714-00-00-e00.zip
|
The present document is a technical report for Intra-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address Intra-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 intra-band carrier aggregation combinations
CA combination
REL independent from
CA_2DL_1A-1A_1UL_BCS0
Rel-11
CA_2DL_1C_1UL_BCS1
Rel-11
CA_2DL_3B_1UL_BCS0
Rel-10
CA_2DL_3A-3A_1UL_BCS2
Rel-11
CA_2DL_3A-3A_1UL_BCS3
Rel-11
CA_2DL_5B_2UL_BCS0
Rel-11
CA_2DL_5B_1UL_BCS1
Rel-11
CA_2DL_5A_5A_1UL_BCS1
Rel-11
CA_2DL_7A-7A_2UL_7A-7A_BCS1
Rel-11
CA_2DL_7A-7A_1UL_BCS2
Rel-11
CA_2DL_7A-7A_1UL_BCS3
Rel-11
CA_2DL_7A-7A_2UL_7A-7A_BCS3
Rel-11
CA_2DL_12A-12A_1UL_BCS0
Rel-11
CA_3DL_40D_1UL_BCS1
Rel-11
CA_3DL_40D_3UL_BCS0
Rel-12
CA_4DL_40E_1UL_BCS0
Rel-11
CA_2DL_40A-40A_1UL_BCS1
Rel-11
CA_3DL_40A-40C_1UL_BCS0
Rel-11
CA_4DL_40C-40C_1UL_BCS0
Rel-11
CA_3DL_41D_3UL_BCS0
Rel-12
CA_3DL_41A-41C_2UL_41C_BCS0
Rel-11
CA_4DL_41E_2UL_41C_BCS0
Rel-11
CA_5DL_41C-41D_2UL_41C_BCS0
Rel-12
CA_2DL_42C_2UL_BCS1
Rel-11
CA_3DL_42D_2UL_BCS1
Rel-11
CA_5DL_42F_1UL_BCS0
Rel-11
CA_5DL_42F_2UL_BCS0
Rel-11
CA_2DL_43C_1UL_BCS0
Rel-11
CA_2DL_46C_0UL_BCS0
Rel-13
CA_2DL_46C_0UL_BCS1
Rel-13
CA_3DL_46D_0UL_BCS0
Rel-13
CA_3DL_46D_0UL_BCS1
Rel-13
CA_4DL_46E_0UL_BCS0
Rel-13
CA_4DL_46E_0UL_BCS1
Rel-13
CA_2DL_46A-46A_0UL_BCS0
Rel-13
CA_3DL_46A-46C_0UL_BCS0
Rel-13
CA_4DL_46A-46D_0UL_BCS0
Rel-13
CA_2DL_48A-48A_1UL_BCS0
Rel-11
CA_2DL_48C_1UL_BCS0
Rel-11
CA_3DL_48A-48C_1UL_BCS0
Rel-11
CA_3DL_48D_1UL_BCS0
Rel-11
CA_4DL_48A-48D_1UL_BCS0
Rel-11
CA_5DL_48A-48E_1UL_BCS0
Rel-11
CA_4DL_48C-48C_1UL_BCS0
Rel-11
CA_4DL_48E_1UL_BCS0
Rel-11
CA_5DL_48C-48D_1UL_BCS0
Rel-11
CA_5DL_48F_1UL_BCS0
Rel-11
CA_3DL_66D_1UL_BCS0
Rel-10
CA_3DL_66A-66B_1UL_BCS0
Rel-11
CA_3DL_66A-66C_1UL_BCS0
Rel-11
CA_2DL_66A-66A_2UL_66A-66A_BCS0
Rel-13
CA_2DL_66B_2UL_66B_BCS0
Rel-13
CA_2DL_66C_2UL_66C_BCS0
Rel-13
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-00-02
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced intra-band Carrier Aggregation (CA) Rel-14 for x Down Link (DL) / y Up Link (UL) with x=3, 4, 5
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-00-02/36714-00-02-e10.zip
|
The present document is a technical report for LTE Advanced 2ULs and xDLs Carrier Aggregation with x=3,4,5 under Rel-14 time frame. The purpose is to gather the relevant background information and studies in order to address 2ULs and xDLs Carrier Aggregation requirements.
This TR covers relevant background information and studies core & performance requirements for the Rel-14 band combinations in Table 1-1, 1-10 and 1-11.
Table 1-1: 3DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3C
CA_1A-3A or
CA_3C
1
Yes
Yes
Yes
Yes
60
0
3
See CA_3C BCS0 in Table 1-6
CA_1A-3A-7A
CA_1A-3A or CA_1A-7A or CA_3A-7A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
CA_1A-3A-21A
CA_1A-3A or
CA_1A-21A or
CA_3A-21A
1
Yes
Yes
Yes
Yes
55
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_1A-3A-28A
CA_1A-3A, CA_1A-28A, CA_3A-28A
1
Yes
Yes
Yes
Yes
50
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
CA_1A-3A-40A
CA_1A-3A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-3A-42A
CA_1A-3A or
CA_1A-42A or
CA_3A-42A
1
Yes
Yes
Yes
Yes
60
0
3
Yes
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-5A-40A
CA_1A-5A
1
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
40
Yes
Yes
Yes
CA_1A-5A-46A
CA_1A-5A
1
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
46
Yes
CA_1A-7A-7A
CA_1A-7A
1
Yes
Yes
Yes
Yes
60
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-7A-8A
CA_1A-7A or CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
7
Yes
Yes
Yes
8
Yes
Yes
CA_1A-7A-46A
CA_1A-7A
1
Yes
Yes
Yes
Yes
60
0
7
Yes
Yes
Yes
46
Yes
CA_1A-8A-40A
CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-19A-42A
CA_1A-19A or
CA_1A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
55
0
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-21A-28A
CA_1A-21A, CA_1A-28A, CA_21A-28A
1
Yes
Yes
Yes
Yes
45
0
21
Yes
Yes
Yes
28
Yes
Yes
CA_1A-21A-42A
CA_1A-21A or
CA_1A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
55
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-28A-42A
CA_1A-28A, CA_1A-42A, CA_28A-42A
1
Yes
Yes
Yes
Yes
50
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-42C
CA_1A-42A
1
Yes
Yes
Yes
Yes
60
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_2A-4A-5A
CA_2A-4A
2
Yes
Yes
Yes
Yes
50
0
4
Yes
Yes
Yes
Yes
5
Yes
Yes
CA_2A-4A-7A
.CA_2A-4A
2
Yes
Yes
Yes
Yes
60
0
4
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
Yes
CA_2A-4A-29A
CA_2A-4A
2
Yes
Yes
Yes
Yes
50
0
4
Yes
Yes
Yes
Yes
29
Yes
Yes
CA_2A-12A-30A
CA_2A-12A
2
Yes
Yes
Yes
Yes
40
0
12
Yes
Yes
30
Yes
Yes
CA_2A-12B
CA_2A-12A
2
Yes
Yes
Yes
Yes
35
0
CA_12B
See CA_12B BCS0 in Table 1-2
CA_3A-3A-8A
CA_3A-8A
CA_3A-3A
See CA_3A-3A BCS0 in Table 1-5
50
0
8
Yes
Yes
CA_3A-3A
See CA_3A-3A BCS1 in Table 1-5
40
1
8
Yes
Yes
CA_3A-5A-7A
CA_3A-5A or
CA_3A-7A or
CA_5A-7A
3
Yes
Yes
Yes
50
0
5
Yes
Yes
7
Yes
Yes
Yes
CA_3A-5A-40A
CA_3A-5A
3
Yes
Yes
Yes
Yes
50
0
5
Yes
Yes
40
Yes
Yes
Yes
CA_3A-7A-7A
CA_3A-7A
3
Yes
Yes
Yes
Yes
60
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_3A-7A-8A
CA_3A-7A or CA_3A-8A or CA_7A-8A
3
Yes
Yes
Yes
40
0
7
Yes
Yes
8
Yes
Yes
3
Yes
Yes
Yes
Yes
50
1
7
Yes
Yes
Yes
8
Yes
Yes
CA_3C-8A
CA_3A-8A or
CA-3C
3
See CA_3C BCS0 in Table 1-6
50
0
8
Yes
Yes
Yes
CA_3A-8A-40A
CA_3A-8A
3
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_3A-19A-21A
CA_3A-19A or
CA_3A-21A or
CA_19A-21A
3
Yes
Yes
Yes
Yes
50
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_3A-19A-42A
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
3
Yes
Yes
Yes
Yes
55
0
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-21A-28A
CA_3A-21A, CA_3A-28A, CA_21A-28A
3
Yes
Yes
Yes
Yes
45
0
21
Yes
Yes
Yes
28
Yes
Yes
CA_3A-21A-42A
CA_3A-21A or
CA_3A-42A or
CA_21A-42A
3
Yes
Yes
Yes
Yes
55
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-28A-42A
CA_3A-28A, CA_3A-42A, CA_28A-42A
3
Yes
Yes
Yes
Yes
50
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_3A-41A-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
60
0
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_3A-42C
CA_3A-42A, CA_42C
3
Yes
Yes
Yes
Yes
60
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_4A-12A-30A
CA_4A-12A
4
Yes
Yes
Yes
Yes
40
0
12
Yes
Yes
30
Yes
Yes
CA_4A-12B
CA_4A-12A
4
Yes
Yes
Yes
Yes
35
0
CA_12B
See CA_12B BCS0 in Table 1-2
CA_5A-7A-7A
CA_5A-7A
5
Yes
Yes
50
0
7
See CA_7A-7A BCS3 in Table 1-9
CA_5A-7A-46A
CA_5A-7A
5
Yes
Yes
50
0
7
Yes
Yes
Yes
46
Yes
CA_7C-28A
CA_7C or CA_7A-28A
7
See CA_7C BCS2 in Table 1-3
60
0
28
Yes
Yes
Yes
CA_19A-21A-42A
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
19
Yes
Yes
Yes
50
0
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_19A-42C
CA_19A-42A
19
Yes
Yes
Yes
55
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_21A-42C
CA_21A-42A
21
Yes
Yes
Yes
55
0
CA_42C
See CA_42C BCS0 in Table 1-4
CA_21A-28A-42A
CA_21A-28A, CA_21A-42A, CA_28A-42A
21
Yes
Yes
Yes
45
0
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_28A-41A-42A
CA_41A-42A
28
Yes
Yes
50
0
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_28A-42C
CA_28A-42A, CA_42C
28
Yes
Yes
50
0
42
See CA_42C BCS0 in Table 1-4
CA_41A-42C
CA_41A-42A or CA_42C
41
Yes
Yes
Yes
60
0
42
See CA_42C BCS1 in Table 1-4
CA_41C-42A
CA_41A-42A or CA_41C
41
See CA_41C BCS0 in Table 1-7
60
0
42
Yes
Yes
Yes
CA_xA-yA-zA
CA_xA-yA or
CA_yA-zA or
CA_xA-zA
X
Up to 60
0
Y
Z
Table 1-2: E-UTRA CA_12B configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_12B
5
5, 10
15
0
Table 1-3: E-UTRA CA_7C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Uplink CA configurations
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_7C
CA_7C
15
15
40
0
20
20
10
20
40
1
15
15, 20
20
10, 15, 20
15
10, 15
40
2
20
15, 20
Table 1-4: E-UTRA CA_42C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_42C
5, 10, 15, 20
20
40
0
20
5, 10, 15
10, 15, 20
20
40
1
20
10, 15
Table 1-5: E-UTRA CA_3A-3A configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRACA configuration
Uplink CA configurations (NOTE 1)
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
CA_3A-3A
-
5, 10, 15, 20
5, 10, 15, 20
40
0
5, 10
5, 10, 15, 20
30
1
Table 1-6: E-UTRA CA_3C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_3C
5, 10, 15
20
40
0
20
5, 10, 15, 20
Table 1-7: E-UTRA CA_41C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_41C
10
20
40
0
15
15, 20
20
10, 15, 20
Table 1-8: E-UTRA CA_46C configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Allowed channel bandwidths for carrier [MHz]
Allowed channel bandwidths for carrier [MHz]
CA_46C
20
20
40
0
Table 1-9: E-UTRA CA_7A-7A configurations and bandwidth combination sets defined for intra-band CA
E-UTRA CA configuration / Bandwidth combination set
E-UTRACA configuration
Uplink CA configurations (NOTE 1)
Component carriers in order of increasing carrier frequency
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
Channel bandwidths for carrier [MHz]
CA_7A-7A
-
5
15
40
0
10
10, 15
15
15, 20
20
20
5, 10, 15, 20
5, 10, 15, 20
40
1
5, 10, 15, 20
5, 10
30
2
10, 15, 20
10, 15, 20
40
3
Table 1-10: 4DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3A-5A-7A
CA_1A-3A or
CA_1A-5A or
CA_1A-7A or
CA_3A-5A or
CA_3A-7A or
CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
5
Yes
Yes
7
Yes
Yes
Yes
CA_1A-3A-7A-7A
CA_1A-3A or CA_1A-7A or CA_3A-7A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-3A-8A-40A
CA_1A-3A,
CA_1A-8A,
CA_3A-8A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
8
Yes
Yes
Yes
40
Yes
Yes
Yes
Yes
CA_1A-3A-5A-40A
CA_1A-3A,
CA_1A-5A,
CA_3A-5A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
5
Yes
Yes
40
Yes
Yes
Yes
CA_1A-3A-7A-8A
CA_1A-3A,
CA_1A-7A,
CA_1A-8A, CA_3A-7A, CA_3A-8A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
8
Yes
Yes
CA_1A-3C-8A
CA_1A-3A or
CA_1A-8A or
CA_3A-8A or
CA_3C
1
Yes
Yes
Yes
Yes
70
0
3
See CA_3C BCS0 in Table 1-6
8
Yes
Yes
Yes
CA_1A-3A-19A-21A
CA_1A-3A,
CA_1A-19A,
CA_1A-21A,
CA_3A-19A,
CA_3A-21A,
CA_19A-21A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
21
Yes
Yes
Yes
CA_1A-3A-19A-42A
CA_1A-3A or
CA_1A-19A or
CA_1A-42A or
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
75
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-21A-28A
CA_1A-3A,
CA_1A-21A,
CA_1A-28A,
CA_3A-21A,
CA_3A-28A,
CA_21A-28A
1
Yes
Yes
Yes
Yes
65
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
28
Yes
Yes
CA_1A-3A-21A-42A
CA_1A-3A,
CA_1A-21A,
CA_1A-42A,
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
1
Yes
Yes
Yes
Yes
75
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-28A-42A
CA_1A-3A,
CA_1A-28A,
CA_1A-42A,
CA_3A-28A,
CA_3A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-3A-42C
CA_1A-3A or
CA_1A-42A or
CA_3A-42A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-5A-7A-7A
CA_1A-5A or CA_1A-7A or CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-5A-7A-46A
CA_1A-5A or
CA_1A-7A or
CA_5A-7A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
7
Yes
Yes
Yes
46
Yes
CA_1A-5A-46C
CA_1A-5A
1
Yes
Yes
Yes
Yes
70
0
5
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_1A-7A-46C
CA_1A-7A
1
Yes
Yes
Yes
Yes
80
0
7
Yes
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_1A-19A-21A-42A
CA_1A-19A or
CA_1A-21A or
CA_1A-42A or
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
70
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-19A-42C
CA_1A-19A or
CA_1A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
75
0
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-21A-28A-42A
CA_1A-21A,
CA_1A-28A,
CA_1A-42A,
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
65
0
21
Yes
Yes
Yes
28
Yes
Yes
42
Yes
Yes
Yes
Yes
CA_1A-21A-42C
CA_1A-21A or
CA_1A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
75
0
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-28A-42C
CA_1A-28A,
CA_1A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_2A-4A-5A-29A
CA_2A-4A
2
Yes
Yes
Yes
Yes
60
0
4
Yes
Yes
Yes
Yes
5
Yes
Yes
29
Yes
Yes
CA_2A-4A-7A-7A
CA_2A-4A
2
Yes
Yes
Yes
Yes
80
0
4
Yes
Yes
Yes
Yes
7
See the CA_7A-7A BCS1 in Table 1-9
CA_3A-5A-7A-7A
CA_3A-5A or CA_3A-7A or CA_5A-7A
3
Yes
Yes
Yes
70
0
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_3C-7C
CA_3A-7A
3
See CA_3C Bandwidth Combination Set 0 in Table 1-6
80
0
7
See CA_7C Bandwidth Combination Set 2 in Table 1-3
3
See CA_3C Bandwidth Combination Set 0 in Table 1-6
80
1
7
See CA_7C Bandwidth Combination Set 1 in Table 1-3
CA_3A-7C-28A
CA_3A-7A,
CA_7C,
CA_7A-28A
3
Yes
Yes
Yes
80
0
7
See CA_7C Bandwidth Combination Set 2 in Table 1-3
28
Yes
Yes
Yes
CA_3A-19A-42C
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
3
Yes
Yes
Yes
Yes
75
0
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_3A-21A-42C
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
3
Yes
Yes
Yes
Yes
75
0
21
Yes
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_3A-28A-41A-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
41
Yes
Yes
Yes
42
Yes
Yes
Yes
CA_3A-28A-42C
CA_3A-28A,
CA_3A-42A,
CA_28A-42A,
CA_42C
3
Yes
Yes
Yes
Yes
70
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_3A-41A-42C
CA_42C, CA_41A-42A
3
Yes
Yes
Yes
Yes
80
0
41
Yes
Yes
Yes
42
See CA_42C Bandwidth combination set 0 in Table 1-4
CA_3A-41C-42A
CA_41A-42A
3
Yes
Yes
Yes
Yes
80
0
41
See CA_41C Bandwidth combination set 0 in Table 1-7
42
Yes
Yes
Yes
CA_5A-7A-46C
CA_5A-7A
5
Yes
Yes
70
0
7
Yes
Yes
Yes
46
See the CA_46C BCS0 in Table 1-8
CA_19A-21A-42C
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
19
Yes
Yes
Yes
70
0
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_21A-28A-42C
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
21
Yes
Yes
Yes
65
0
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_28A-41A-42C
CA_42C, CA_41A-42A
28
Yes
Yes
70
0
41
Yes
Yes
Yes
42
See CA_42C Bandwidth combination set 0 in Table 1-4
CA_28A-41C-42A
CA_41A-42A
28
Yes
Yes
70
0
41
See CA_41C Bandwidth combination set 0 in Table 1-7
42
Yes
Yes
Yes
CA_41C-42C
CA_41A-42A or CA_42C or CA_41C
41
See CA_41C BCS0 in Table 1-7
80
0
42
See CA_42C BCS1 in Table 1-4
CA_wA-xA-yA-zA
CA_wA-xA,
CA_wA-yA,
CA_wA-zA,
CA_xA-yA,
CA_xA-zA,
CA_yA-zA
W
Up to 80
X
Y
Z
Table 1-11: 5DL/2UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA Configuration
Uplink CA configurations
E-UTRA Bands
1.4
MHz
3
MHz
5
MHz
10
MHz
15
MHz
20
MHz
Maximum aggregated bandwidth
[MHz]
Bandwidth combination set
CA_1A-3A-5A-7A-7A
CA_1A-3A or CA_1A-5A or CA_1A-7A or CA_3A-5A or CA_3A-7A or CA_5A-7A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
5
Yes
Yes
7
See CA_7A-7A BCS3 in Table 1-9
CA_1A-3A-19A-42C
CA_1A-3A or
CA_1A-19A or
CA_1A-42A or
CA_3A-19A or
CA_3A-42A or
CA_19A-42A
1
Yes
Yes
Yes
Yes
95
0
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-3A-21A-42C
CA_1A-3A,
CA_1A-21A,
CA_1A-42A,
CA_3A-21A,
CA_3A-42A,
CA_21A-42A
1
Yes
Yes
Yes
Yes
95
0
3
Yes
Yes
Yes
Yes
21
Yes
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_1A-3A-28A-42C
CA_1A-3A,
CA_1A-28A,
CA_1A-42A,
CA_3A-28A,
CA_3A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
Yes
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_1A-19A-21A-42C
CA_1A-19A or
CA_1A-21A or
CA_1A-42A or
CA_19A-21A or
CA_19A-42A or
CA_21A-42A
1
Yes
Yes
Yes
Yes
90
0
19
Yes
Yes
Yes
21
Yes
Yes
Yes
42
See CA_42C Bandwidth Combination Set 0 in Table 1-4
CA_1A-21A-28A-42C
CA_1A-21A,
CA_1A-28A,
CA_1A-42A,
CA_21A-28A,
CA_21A-42A,
CA_28A-42A
1
Yes
Yes
Yes
Yes
85
0
21
Yes
Yes
Yes
28
Yes
Yes
42
See CA_42C BCS0 in Table 1-4
CA_vA-wA-xA-yA-zA
CA_vA-wA or
CA_vA-xA or
CA_vA-yA or
CA_vA-zA or
CA_wA-xA or
CA_wA-yA or
CA_wA-zA or
CA_xA-yA or
CA_xA-zA or
CA_yA-zA
V
Up to 100
0
W
X
Y
Z
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-02-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-02-01/36714-02-01-e00.zip
|
The present document is a technical report for 2DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 2DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 2DL/1UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_1A-3A
10
CA_1A-32A
10
CA_1A-38A
12
CA_1A-41A
12
CA_1A-46A
13
CA_2A-48A
14
CA_2A-66A
10
CA_3A-11A
10
CA_3A-21A
10
CA_3A-28A
10
CA_3A-32A
10
CA_3A-40A
12
CA_3A-41A
12
CA_3A-46A
13
CA_3A-5A
10
CA_3A-69A
10
CA_5A-28A
10
CA_5A-41A
12
CA_5A-46A
13
CA_5A-46A
13
CA_5A-48A
14
CA_5A-66A
10
CA_7A-26A
10
CA_7A-32A
10
CA_7A-46A
13
CA_7A-66A
10
CA_7A-8A
10
CA_8A-28A
10
CA_8A-39A
12
CA_8A-41A
12
CA_8A-46A
13
CA_8A-46A
13
CA_11A-28A
10
CA_11A-41A
12
CA_11A-42A
12
CA_11A-46A
13
CA_12A-66A
10
CA_13A-46A
13
CA_13A-48A
14
CA_13A-66A
10
CA_19A-46A
13
CA_20A-32A
10
CA_20A-28A
10
CA_21A-28A
10
CA_21A-46A
13
CA_26A-46A
13
CA_28A-41A
12
CA_28A-46A
13
CA_29A-66A
10
CA_29A-70A
10
CA_30A-66A
10
CA_39A-40A
10
CA_39A-42A
10
CA_39A-46A
13
CA_40A-41A
10
CA_40A-42A
10
CA_40A-46A
13
CA_40A-46A
13
CA_41A-46A
13
CA_46A-66A
13
CA_46A-70A
13
CA_48A-66A
14
CA_66A-70A
10
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
Feasibility study on LTE Advanced Carrier Aggregation for Band 3 and Band 39 [FS_LTE_CA_B3_B39] input is also in this TR in chapter 7.
|
36.714-02-02
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 2 Down Link (DL) / 2 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-02-02/36714-02-02-e00.zip
|
The present document is a technical report for 2DL/2UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 2DL/2UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 2DL/2UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_3A-41A
Rel-12
CA_8A-41A
Rel-12
CA_3A-42A
Rel-12
CA_19A-42A
Rel-12
CA_21A-42A
Rel-12
CA_2A-7A
Rel-11
CA_7A-8A
Rel-11
CA_8A-39A
Rel-12
CA_41A-42A
Rel-12
CA_3A-21A
Rel-11
CA_28A-42A
Rel-12
CA_3A-28A
Rel-11
CA_21A-28A
Rel-11
CA_5A-66A
Rel-11
CA_2A-66A
Rel-11
CA_12A-30A
Rel-11
CA_2A-30A
Rel-11
CA_5A-30A
Rel-11
CA_2A-66A
Rel-11
CA_2A-66A
Rel-11
CA_12A-66A
Rel-11
CA_30A-66A
Rel-11
CA_3A-40A
Rel-12
CA_5A-40A
Rel-12
CA_1A-46A
Rel-14
CA_41A-46A
Rel-14
CA_42A-46A
Rel-14
CA_2A-46A
Rel-14
CA_3A-46A
Rel-14
CA_7A-46A
Rel-14
CA_46A-66A
Rel-14
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-03-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 3 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-03-01/36714-03-01-e00.zip
|
The present document is a technical report for 3DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 3DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 3DL/1UL inter-band carrier aggregation combinations
CA combination
BCS
REL independent from
CA_1A-1A-3A
0
Rel-11
CA_1A-3A-3A
0
Rel-11
CA_1A-1A-5A
0
Rel-11
CA_1A-1A-28A
0
Rel-11
CA_1C-3A
0
Rel-10
CA_1A-7A-7A
0
Rel-11
CA_1A-7C
1
Rel-10
CA_1A-40C
0
Rel-12
CA_1A-46C
0, 1
Rel-13
CA_2A-5B
0
Rel-10
CA_2A-7A-7A
0
Rel-11
CA_2A-7C
0
Rel-10
CA_2A-12A-12A
0
Rel-11
CA_2A-2A-30A
0
Rel-11
CA_2A-46C
0
Rel-13
CA_2A-48C
0
Rel-10
CA_2A-48A-48A
0
Rel-11
CA_2A-46A-46A
0
Rel-13
CA_2A-66B
0
Rel-10
CA_2A-66C
0
Rel-10
CA_2A-2A-66A
0
Rel-11
CA_2A-66A-66A
0
Rel-11
CA_3A-3A-7A
0, 1
Rel-11
CA_3A-7A-7A
0, 1
Rel-11
CA_3C-8A
0
Rel-10
CA_3C-20A
0
Rel-10
CA_3A-3A-20A
0
Rel-11
CA_3A-40A-40A
0
Rel-12
CA_3C-40A
0
Rel-12
CA_3A-3A-41A
0
Rel-11
CA_3C-41A
0
Rel-12
CA_3A-46C
0, 1
Rel-13
CA_4A-5B
0
Rel-10
CA_4A-7A-7A
0
Rel-11
CA_4A-7C
0
Rel-10
CA_4A-12A-12A
0
Rel-11
CA_4A-46C
0
Rel-13
CA_4A-46A-46A
0
Rel-13
CA_5A-7C
0
Rel-10
CA_5A-7A-7A
0
Rel-11
CA_5A-12A-12A
0
Rel-11
CA_5B-30A
0
Rel-10
CA_5A-5A-40A
0
Rel-11
CA_5A-40A-40A
0
Rel-12
CA_5A-46C
0, 1
Rel-13
CA_5A-66B
0
Rel-10
CA_5A-66C
0
Rel-10
CA_5B-66A
0
Rel-10
CA_5A-5A-66A
0
Rel-11
CA_5A-66A-66A
0
Rel-11
CA_7A-7A-8A
0, 1
Rel-11
CA_7A-7A-26A
0
Rel-11
CA_7A-46C
0
Rel-13
CA_7C-46A
0
Rel-10
CA_8A-39C
0
Rel-12
CA_8B-39A
0
Rel-12
CA_8B-41A
0
Rel-12
CA_8A-46C
0
Rel-13
CA_8B-46A
0
Rel-13
CA_11A-41C
0
Rel-12
CA_11A-42C
0
Rel-12
CA_11A-46C
0
Rel-13
CA_12A-66C
0
Rel-10
CA_12A-66A-66A
0
Rel-11
CA_12B-66A
0
Rel-10
CA_13A-46C
0
Rel-13
CA_13A-66B
0
Rel-10
CA_13A-66C
0
Rel-10
CA_13A-66A-66A
0
Rel-11
CA_19A-46C
0
Rel-13
CA_21A-46C
0
Rel-13
CA_28A-46C
0
Rel-13
CA_29A-46A-46A
0
Rel-13
CA_29A-66C
0
Rel-13
CA_29A-66A-66A
0
Rel-11
CA_30A-66A-66A
0
Rel-11
CA_39A-40C
0
Rel-10
CA_39C-40A
0
Rel-10
CA_39A-42C
0
Rel-10
CA_39C-42A
0
Rel-10
CA_39A-46C
0
Rel-13
CA_39C-46A
0
Rel-13
CA_40A-42C
0
Rel-12
CA_40C-42A
0
Rel-12
CA_40A-46C
0,1
Rel-13
CA_40C-46A
0
Rel-13
CA_41C-46A
0
Rel-13
CA_41A-46C
0
Rel-13
CA_46A-66C
0
Rel-13
CA_46C-66A
0
Rel-13
CA_46A-46A-66A
0
Rel-13
CA_46A-66A-66A
0
Rel-13
CA_48A-48A-66A
0
Rel-11
CA_48C-66A
0
Rel-10
CA_1A-3A-11A
0
Rel-10
CA_1A-3A-21A
0
Rel-10
CA_1A-3A-26A
1
Rel-10
CA_1A-3A-38A
0
Rel-12
CA_1A-3A-41A3
0
Rel-12
CA_1A-5A-41A
0
Rel-12
CA_1A-5A-46A
0
Rel-13
CA_1A-7A-20A
1
Rel-10
CA_1A-7A-26A
0
Rel-10
CA_1A-7A-28A
2
Rel-10
CA_1A-7A-40A
0
Rel-12
CA_1A-7A-42A
0
Rel-12
CA_1A-7A-46A
0
Rel-13
CA_1A-8A-20A
0
Rel-10
CA_1A-8A-28A
0
Rel-10
CA_1A-11A-28A
0
Rel-10
CA_1A-20A-28A
0
Rel-10
CA_1A-20A-42A
0
Rel-12
CA_1A-21A-28A
0
Rel-10
CA_1A-28A-42A
0
Rel-12
CA_1A-28A-46A
0
Rel-13
CA_1A-41A-42A2
0
Rel-12
CA_2A-5A-66A
0
Rel-10
CA_2A-7A-66A
0
Rel-10
CA_2A-12A-66A
0, 1
Rel-10
CA_2A-13A-66A
0
Rel-10
CA_2A-29A-66A
Rel-10
CA_2A-30A-66A
0
Rel-10
CA_2A-46A-66A
0
Rel-13
CA_2A-48A-66A
0
Rel-10
CA_3A-5A-7A
0
Rel-10
CA_3A-5A-40A
1
Rel-12
CA_3A-5A-41A
0
Rel-12
CA_3A-7A-8A
2
Rel-10
CA_3A-7A-26A
0
Rel-10
CA_3A-7A-32A
0
Rel-10
CA_3A-7A-40A
0
Rel-12
CA_3A-7A-42A
0
Rel-12
CA_3A-8A-11A
0
Rel-10
CA_3A-8A-20A
0
Rel-10
CA_3A-8A-28A
0
Rel-10
CA_3A-11A-28A
0
Rel-10
CA_3A-19A-21A
0
Rel-10
CA_3A-20A-28A
0
Rel-11
CA_3A-20A-32A4
0
Rel-10
CA_3A-20A-42A
0
Rel-12
CA_3A-21A-28A
0
Rel-10
CA_3A-21A-42A
0
Rel-12
CA_3A-28A-41A
0
Rel-12
CA_3A-28A-42A
0
Rel-12
CA_5A-7A-46A
0
Rel-13
CA_5A-12A-66A
0
Rel-10
CA_5A-30A-66A
0
Rel-10
CA_5A-40A-41A
0
Rel-12
CA_7A-20A-28A
0
Rel-11
CA_7A-20A-32A
0
Rel-10
CA_7A-20A-42A
0
Rel-12
CA_8A-11A-28A
0
Rel-10
CA_8A-28A-41A
0
Rel-12
CA_12A-30A-66A
0
Rel-10
CA_21A-28A-42A
0
Rel-12
CA_28A-40A-41A
0
Rel-12
CA_28A-41A-42A5
0
Rel-12
CA_28A-41A-46A
0
Rel-13
CA_29A-30A-66A
0
Rel-10
Note 1: UL carrier shall be supported in each of the 3 bands being aggregated unless otherwise specified.
Note 2: UL carrier is only supported on Band 1 or Band 42 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
Note 3: UL carrier is only supported on Band 1 or Band 3 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
Note 4: UL carrier is only supported on Band 3 or Band 20 not Band 32 because Band 32 is SDL band.
Note 5: For CA_28A-41A-42A, only non-simultaneous Rx/Tx on Band 41 and Band 42 is supported.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-03-03
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 3 Down Link (DL) / 3 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-03-03/36714-03-03-e00.zip
|
The present document is a technical report for 3DL/3UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 3DL/3UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 3DL/3UL inter-band carrier aggregation combinations
CA combination
REL independent from
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-04-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 4 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-04-01/36714-04-01-e00.zip
|
The present document is a technical report for 4DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 4DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 4DL/1UL inter-band carrier aggregation combinations
CA combination
REL-independent from
CA_4DL_1A-1A-3C_1UL_BCS0
Rel-11
CA_4DL_1A-1A-3A-5A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-5A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-5A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-5A-41A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7C_1UL_BCS1
Rel-11
CA_4DL_1A-3C-7A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-20A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-7A-28A_1UL_BCS1
Rel-12
CA_4DL_1A-3A-7A-40A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-7A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-3A-8A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-8A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-8A-11A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-8A-20A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-19A-21A_1UL_BCS0
Rel-10
CA_4DL_1A-3A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-21A-28A_1UL_BCS0
Rel-10
CA_4DL_1A-3A-21A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-1A-3A-28A_1UL_BCS0
Rel-11
CA_4DL_1A-3C-28A_1UL_BCS0
Rel-11
CA_4DL_1A-3A-28A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-3A-40C_1UL_BCS0
Rel-12
CA_4DL_1A-3C-40A_1UL_BCS0
Rel-12
CA_4DL_1A-5A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_1A-5A-7A-46A_1UL_BCS0
Rel-13
CA_4DL_1A-5A-46C_1UL_BCS0
Rel-13
CA_4DL_1A-7A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_1A-7A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-20A-32A_1UL_BCS0
Rel-12
CA_4DL_1A-7A-46C_1UL_BCS0
Rel-13
CA_4DL_1A-21A-28A-42A_1UL_BCS0
Rel-12
CA_4DL_1A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_1A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_1A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_1A-46D_1UL_BCS0
Rel-13
CA_4DL_1A-46D_1UL_BCS1
Rel-13
CA_4DL_2A-2A-5A-30A_BCS0
Rel-11
CA_4DL_2A-2A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-5A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-12A-30A_BCS0
Rel-11
CA_4DL_2A-2A-12A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-13A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-29A-30A_1UL_BCS0
Rel-12
CA_4DL_2A-2A-30A-66A_BCS0
Rel-11
CA_4DL_2A-2A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-2A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-2A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-4A-5B_1UL_BCS0
Rel-11
CA_4DL_2A-4A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_2A-4A-7C_1UL_BCS0
Rel-11
CA_4DL_2A-4A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-4A-12B_1UL_BCS0
Rel-11
CA_4DL_2A-5A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-12A-66A_BCS0
Rel-11
CA_4DL_2A-5B-30A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-48A-48A_1UL_BCS0
Rel-14
CA_4DL_2A-5A-48C_1UL_BCS0
Rel-14
CA_4DL_2A-5A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-5A-30A-66A_BCS0
Rel-11
CA_4DL_2A-5A-66A-66A_BCS0
Rel-11
CA_4DL_2A-5A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-5B-66A_1UL_BCS0
Rel-11
CA_4DL_2A-5A-66C_1UL_BCS0
Rel-11
CA_4DL_2C-5B_1UL_BCS0
Rel-11
CA_4DL_2A-12A-30A-66A_BCS0
Rel-11
CA_4DL_2A-12A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-12A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-12B-66A_BCS0
Rel-11
CA_4DL_2A-13A-48A-48A_1UL_BCS0
Rel-14
CA_4DL_2A-13A-48C_1UL_BCS0
Rel-14
CA_4DL_2A-13A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-13A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_2A-13A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-13A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-30A-66A-66A_BCS0
Rel-11
CA_4DL_2A-46A-46C _1UL_BCS0
Rel-13
CA_4DL_2A-46D_1UL_BCS0
Rel-13
CA_4DL_2A-46C-66A_1UL_BCS0
Rel-13
CA_4DL_2A-46A-46A-66A_1UL_BCS0
Rel-13
CA_4DL_2A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_2A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_2A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_2A-48D _1UL_BCS0
Rel-14
CA_4DL_2A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_2A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_2A-66D_1UL_BCS0
Rel-11
CA_4DL_3C-7C_1UL_BCS1
Rel-11
CA_4DL_3A-3A-7A-8A_1UL_BCS0
Rel-11
CA_4DL_3A-3A-7A-8A_1UL_BCS1
Rel-11
CA_4DL_3A-3A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_3A-3A-7A-7A_1UL_BCS1
Rel-11
CA_4DL_3A-5A-7A-7A_1UL_BCS0
Rel-11
CA_4DL_3A-5A-40A-40A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-7A-8A _1UL_BCS0
Rel-11
CA_4DL_3A-7A-7A-8A _1UL_BCS1
Rel-11
CA_4DL_3A-7A-8A-20A_1UL_BCS0
Rel-12
CA_4DL_3A-7C-20A_1UL_BCS0
Rel-11
CA_4DL_3C-7A-20A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-20A-28A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-20A-32A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-20A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-7A-7A-26A_1UL_BCS0
Rel-11
CA_4DL_3A-7A-40C_1UL_BCS0
Rel-12
CA_4DL_3A-19A-21A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-21A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-28A-41C_1UL_BCS0
Rel-12
CA_4DL_3A-28A-41A-42A_1UL_BCS0
Rel-12
CA_4DL_3A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-40D_1UL_BCS0
Rel-12
CA_4DL_3C-40C_1UL_BCS0
Rel-12
CA_4DL_3C-41C_1UL_BCS0
Rel-12
CA_4DL_3A-41D_1UL_BCS0
Rel-12
CA_4DL_3A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_3A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_3A-46D_1UL_BCS0
Rel-13
CA_4DL_3A-46D_1UL_BCS1
Rel-13
CA_4DL_4A-4A-5B_1UL_BCS0
Rel-11
CA_4DL_4A-4A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_4A-4A-12B_1UL_BCS0
Rel-11
CA_4DL_4A-5A-12A-12A_1UL_BCS0
Rel-11
CA_4DL_4A-5A-12B_1UL_BCS0
Rel-11
CA_4DL_4A-5B-30A_1UL_BCS0
Rel-11
CA_4DL_4A-46A-46C_1UL_BCS0
Rel-13
CA_4DL_4A-46D_1UL_BCS0
Rel-13
CA_4DL_5A-7A-46C_1UL_BCS0
Rel-13
CA_4DL_5A-30A-66A-66A_BCS0
Rel-11
CA_4DL_5B-30A-66A_BCS0
Rel-11
CA_4DL_5A-46D_1UL_BCS0
Rel-13
CA_4DL_5A-46D_1UL_BCS1
Rel-13
CA_4DL_5A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_5A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_5A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_5A-48D _1UL_BCS0
Rel-14
CA_4DL_5A-5A-66A-66A_1UL_BCS0
Rel-11
CA_4DL_5A-5A-66B_1UL_BCS0
Rel-11
CA_4DL_5A-5A-66C_1UL_BCS0
Rel-11
CA_4DL_5B-66A-66A_1UL_BCS0
Rel-11
CA_4DL_5B-66B_1UL_BCS0
Rel-11
CA_4DL_5B-66C_1UL_BCS0
Rel-11
CA_4DL_5A-66D_1UL_BCS0
Rel-11
CA_4DL_5A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_5A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_7A-46D_1UL_BCS0
Rel-13
CA_4DL_7A-46D_1UL_BCS1
Rel-13
CA_4DL_7C-46C_1UL_BCS0
Rel-13
CA_4DL_8B-39C_1UL_BCS0
Rel-12
CA_4DL_8A-41D_1UL_BCS0
Rel-12
CA_4DL_8B-41C_1UL_BCS0
Rel-12
CA_4DL_8B-46C_1UL_BCS0
Rel-13
CA_4DL_8A-46D_1UL_BCS0
Rel-13
CA_4DL_11A-46D_1UL_BCS0
Rel-13
CA_4DL_12A-30A-66A-66A_1UL_BCS0
Rel-12
CA_4DL_12B-66A-66A_BCS0
Rel-11
CA_4DL_13A-46D_1UL_BCS0
Rel-13
CA_4DL_13A-48A-48C _1UL_BCS0
Rel-14
CA_4DL_13A-48A-48A-66A_1UL_BCS0
Rel-14
CA_4DL_13A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_13A-48D _1UL_BCS0
Rel-14
CA_4DL_13A-66D_1UL_BCS0
Rel-11
CA_4DL_13A-66A-66C_1UL_BCS0
Rel-11
CA_4DL_13A-66A-66B_1UL_BCS0
Rel-11
CA_4DL_19A-46D_1UL_BCS0
Rel-13
CA_4DL_21A-28A-42C_1UL_BCS0
Rel-12
CA_4DL_21A-46D_1UL_BCS0
Rel-13
CA_4DL_28A-41A-42C_1UL_BCS0
Rel-12
CA_4DL_28A-41C-42A_1UL_BCS0
Rel-12
CA_4DL_28A-46D_1UL_BCS0
Rel-13
CA_4DL_29A-66A-66A-70A_1UL_BCS0
Rel-11
CA_4DL_29A-66C-70A_1UL_BCS0
Rel-10
CA_4DL_29A-66A-70C_1UL_BCS0
Rel-10
CA_4DL_39A-40D_1UL_BCS0
Rel-11
CA_4DL_39C-40C_1UL_BCS0
Rel-11
CA_4DL_39A-42D_1UL_BCS0
Rel-11
CA_4DL_39C-42C_1UL_BCS0
Rel-11
CA_4DL_39C-46C_1UL_BCS0
Rel-13
CA_4DL_39A-46D_1UL_BCS0
Rel-13
CA_4DL_40C-42C_1UL_BCS0
Rel-11
CA_4DL_40C-46C_1UL_BCS0
Rel-13
CA_4DL_40A-46D_1UL_BCS0
Rel-13
CA_4DL_40D-46A_1UL_BCS0
Rel-13
CA_4DL_40A-46D_1UL_BCS1
Rel-13
CA_4DL_41A-42D_1UL_BCS0
Rel-11
CA_4DL_41D-42A_1UL_BCS0
Rel-11
CA_4DL_41C-46C_1UL_BCS0
Rel-13
CA_4DL_41A-46D_1UL_BCS0
Rel-13
CA_4DL_41D-46A_1UL_BCS0
Rel-13
CA_4DL_46A-46C-66A_1UL_BCS0
Rel-13
CA_4DL_46D-66A_1UL_BCS0
Rel-13
CA_4DL_48D-66A _1UL_BCS0
Rel-14
CA_4DL_48A-48C-66A_1UL_BCS0
Rel-14
CA_4DL_66A-66A-70C_1UL_BCS0
Rel-11
CA_4DL_66C-70C_1UL_BCS0
Rel-10
Note 1: UL carrier shall be supported in each of the 4 bands being aggregated unless otherwise specified.
Note 2: UL carrier is only supported on Band 1 or Band 42 not Band 41 because the fall back mode 1UL/2DL CA_1A-41A has the limitation that UL carrier is only supported on Band 1.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.714-05-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced inter-band Carrier Aggregation (CA) Rel-14 for 5 Down Link (DL) / 1 Up Link (UL)
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.714-05-01/36714-05-01-e10.zip
|
The present document is a technical report for 5DL/1UL Inter-band Carrier Aggregation under Rel-14 time frame according to the New CA WI approach in Release 14 [1]. The purpose is to gather the relevant background information and studies in order to address 5DL/1UL Inter-band Carrier Aggregation requirements for the Rel-14 band combinations in Table 1-1.
Table 1-1: Release 14 5DL/1UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_1A-3A-5A-7A-7A
12
CA_1A-3A-7A-40C
12
CA_1A-3C-7C
12
CA_1A-3A-7A-20A-28A
12
CA_1A-3A-7A-20A-42A
12
CA_1A-3A-7A-7A-26A
12
CA_1A-3A-21A-42C
12
CA_1A-3A-28A-42C
12
CA_1A-3C-40C
12
CA_1A-5A-46D
13
CA_1A-5A-7A-46C
13
CA_1A-7A-46D
13
CA_1A-21A-28A-42C
12
CA_1A-41C-42C
12
CA_1A-46E
13
CA_2A-2A-5A-12A-66A
12
CA_2A-5B-30A-66A
12
CA_2A-2A-5A-30A-66A
12
CA_2A-5A-30A-66A-66A
12
CA_2A-2A-5A-66C
12
CA_2A-2A-5A-66B
12
CA_2A-2A-5A-66A-66A
12
CA_2A-2A-12A-30A-66A
12
CA_2A-2A-12B-66A
12
CA_2A-2A-66D
12
CA_2A-2A-66A-66C
12
CA_2A-2A-66A-66B
12
CA_2A-4A-5B-30A
12
CA_2C-5B-30A
12
CA_2A-5B-66C
12
CA_2A-5B-66B
12
CA_2A-5A-66D
12
CA_2A-12B-66A-66A
12
CA_2A-13A-66D
12
CA_2A-13A-66A-66C
12
CA_2A-13A-66A-66B
12
CA_2A-46A-46D
13
CA_2A-46D-66A
13
CA_2A-46A-46C-66A
13
CA_3A-3A-7A-7A-8A
12
CA_3A-28A-40D
12
CA_3A-28A-41A-42C
12
CA_3A-28A-41C-42A
12
CA_3A-40E
12
CA_3C-41D
12
CA_3A-41C-42C
12
CA_3A-46E
13
CA_4A-4A_5B_ 30A
12
CA_4A-46A-46D
13
CA_5A-46E
13
CA_5A-5A-66D
12
CA_5A-5A-66A-66C
12
CA_5A-5A-66A-66B
12
CA_5A-7A-46D
13
CA_5B-66A-66C
12
CA_5B-66A-66B
12
CA_7A-46E
13
CA_7C-46D
13
CA_8B-41D
12
CA_8B-46D
13
CA_8A-46E
13
CA_11A-46E
13
CA_13A-46E
13
CA_19A-46E
13
CA_21A-46E
13
CA_28A-41C-42C
12
CA_28A-46E
13
CA_39A-40E
12
CA_39C-40D
12
CA_39C-41D
12
CA_39A-42E
12
CA_39C-42D
12
CA_39C-46D
13
CA_39A-46E
13
CA_40C-46D
13
CA_40A-46E
13
CA_40D-46C
13
CA_41C-42D
12
CA_41D-42C
12
CA_41A-46E
13
CA_41C-46D
13
CA_41D-46C
13
CA_46E-66A
13
CA_46A-46D-66A
13
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.741
|
Study on further enhancements to Coordinated Multi-Point (CoMP) operation for LTE
|
TR
|
14.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.741/36741-e00.zip
|
The present document is related to the technical report for the study item “Study on Further enhancements to Coordinated Multi-Point Operation” [2]. The purpose of this TR is to help TSG RAN WG1 to understand the performance benefit of the enhancements related to coordinated multi-point schemes.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information and draw a conclusion on way forward.
This document will be kept up-to-date via CRs in the future.
|
36.743
|
Enhanced Multimedia Broadcast/Multicast (eMBMS) enhancements for LTE
|
TR
|
0.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.743/36743-010.zip
|
This Technical Report summarizes the findings related to the following objectives of [2]:
• Support for standalone carrier with all DL subframes dedicated to MBSFN transmission and self-contained eMBMS signaling including information of SIB13, SIB15, SIB16. (RAN2)
• Support for multi-carrier eMBMS/unicast operation involving reception from one or more eMBMS cells that may be non-collocated and asynchronous with one or more cells that are simultaneously used for unicast. (RAN4, RAN2)
• Solutions where a UE can receive the TV transport service without being authenticated (RAN1, RAN2, RAN3)
|
36.744
|
Citizens Broadband Radio Service (CBRS) 3.5 GHz band for LTE in the United States
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.744/36744-e00.zip
|
The present document is a technical report for the CBRS (Citizens Broadband Radio Service) 3.5GHz E-UTRA TDD band (3550-3700MHz) for operations in the United States.
|
36.745
|
Feasibility study on global application of LTE Band 11 and of LTE Band 21 User Equipments (UEs)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.745/36745-e00.zip
|
The present document is to evaluate possible methods and conditions for existing Band 11 and Band 21 UEs to comply with a new satellite protection requirement defined by ITU-R.
|
36.747
|
Enhanced CRS and 4Rx SU-MIMO Interference Mitigation Performance Requirements for LTE
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.747/36747-e00.zip
|
The objective of this report is to investigate feasibility and specify requirements for 1) CRS-IM receivers for the generic scenarios with different number of CRS APs (2, 4) and different number of UE receive antennas and 2) SU-MIMO IM receivers for UEs equipped with 4 receive antennas. The work item [2] has the following detailed objectives:
- Investigate feasibility and specify requirements for the CRS-IM receivers for the generic scenarios with different number of CRS APs (2, 4) and different number of UE receive antennas for synchronous networks:
- Stage 1: Investigate performance benefits and feasibility of using CRS-IM receivers:
- Identify target scenarios including deployment scenarios, interference models, and others
- Reuse Rel-12 NAICS and Rel-13 CRS-IM WIs assumptions as the starting point
- Evaluate the CRS-IM performance benefits
- Identify reference CRS-IM receiver structure assumptions including at least number of cancelled cell(s), and IM algorithm.
- The tradeoff between complexity and performance should be analyzed in order to define reference receivers.
- Stage 2: Specify UE demodulation and CSI reporting performance requirements to verify practical CRS-IM operation for the identified scenarios based on the outcome of Stage 1.
- The work should be done under the following assumptions:
- The following scenarios are prioritized:
- 2 RX antennas UEs with 4 CRS APs in the serving and interference cell(s)
- 2 RX antennas UEs with a mix of 2 and 4 CRS APs in the serving and interference cell(s)
- 4 RX antennas UEs with 2 and 4 CRS APs in the serving and interference cell(s)
- CRS-IM can be used for different downlink physical channels:
- First priority: PDSCH (both CRS- and DMRS-based transmission modes)
- Second priority: DL control channels including PDCCH, PCFICH, PHICH and EPDCCH
- Non-colliding CRS scenarios are primarily considered.
- Colliding CRS scenarios are not precluded.
- Homogeneous deployment scenarios are primarily considered
- Heterogeneous deployment scenarios are not precluded.
- Single carrier case.
- Reference PDSCH receiver structure: LMMSE-IRC with CRS-IM.
- Investigate feasibility and specify requirements for the enhanced SU-MIMO inter-stream interference mitigation (SU-MIMO IM) receivers for the scenarios with 4 receive antennas UEs
- Stage 1: Investigate performance benefits and feasibility of using SU-MIMO IM receivers for the scenarios with 4 receive antennas UEs.
- Investigate and agree on target scenarios including layer number for spatial multiplexing, MCS, propagation conditions and others for performance evaluation
- Reuse the assumptions for Rel-12 SU-MIMO IM (Type-C receiver) and Rel-13 4Rx MIMO performance requirements as starting point.
- SU-MIMO scenarios
- rank 2/3/4 SU-MIMO is considered
- The maximum number of layers (e.g. rank3/4) should be determined based on feasibility study (e.g. operating SNR), realistic Tx EVM assumption and the study on performance gains, reference receiver complexity and testability, etc.
- Strive to reuse agreed Tx EVM for 4Rx in Rel-13 if the related agreement can be reached
- Consider 2 and 4 CRS APs scenarios
- Channel correlations
- Focus on the Medium, Medium A and High antenna correlation models
- Modulation order: up to 256QAM
- The considered modulation orders should be decided based on feasibility study (e.g. operating SNR), realistic Tx EVM assumption, performance gains, reference receiver complexity and testability, etc.
- Strive to reuse agreed Tx EVM for 4Rx in Rel-13 if the related agreement can be reached.
- Identify the reference receiver structure for SU-MIMO IM evaluation
- R-ML is considered in high priority
- Evaluate the performance of enhanced SU-MIMO IM receivers.
- Stage 2: Specify UE demodulation performance requirements to verify enhanced SU-MIMO receivers for the UEs equipped with 4 RX antennas
- Reference receiver structure and other test parameters are based on the outcome of Stage 1.
- Single carrier case.
|
36.749
|
Evolved Universal Terrestrial Radio Access (E-UTRA); New AWS Band for LTE
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.749/36749-e00.zip
|
The present document a technical report for the AWS 3/4 band for LTE work item. The band is specified as 15+25 MHz (1 695 – 1 710 MHz / 1 995 – 2 020 MHz) with two duplex spacings.
|
36.750
|
Study on Voice and Video Enhancement for LTE
|
TR
|
14.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.750/36750-e10.zip
|
The present document captures the findings of the study on voice and video enhancement for LTE.
|
36.752
|
Study of Narrow-Band Internet of Things (NB-IoT) Radio Frequency (RF) requirement to co-existence with Code Division Multiple Access (CDMA)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.752/36752-e00.zip
|
The present document summarizes the studies of NB-IoT RF requirement for coexistence with CDMA.
|
36.785
|
Vehicle to Vehicle (V2V) services based on LTE sidelink; User Equipment (UE) radio transmission and reception
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.785/36785-e00.zip
|
The present document is the Technical Report on TR on V2V Services based on LTE sidelink.
The purpose of the present document is to study the radio requirements on V2V services based on LTE sidelink as part of the Rel-14 work item. The normative requirements resulting from the present document will be addressed in the applicable release 14 Technical Specifications (TS).
|
36.786
|
Vehicle-to-Everything (V2X) services based on LTE; User Equipment (UE) radio transmission and reception
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.786/36786-e00.zip
|
The present document is the Technical Report on TR on V2X Services based on LTE sidelink.
The purpose of the present document is to study the radio requirements and adjacent channel coexistence with high power up to 33dBm on V2X services based on LTE sidelink as part of the Rel-14 work item. The normative requirements resulting from the present document will be addressed in the applicable release 14 Technical Specifications (TS).
|
36.858
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE 2.6 GHz FDD SDL band (2570-2620 MHz)
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.858/36858-e00.zip
|
The present document is a technical report for the LTE 2,6 GHz FDD supplemental downlink (SDL) band covering 2 570-2 620 MHz. It is intended to be specified for E-UTRA for operations in Region 1. The band is to be used in CA for E-UTRA. The LTE CA combination of Band 3+ FDD SDL Band 2 570-2 620 MHz was selected. All the CA related aspects are reported in 2DL/1UL CA basket TR 36.714-02-01 [3].
|
36.881
|
Study on latency reduction techniques for LTE
|
TR
|
14.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.881/36881-e00.zip
|
This document is related to the technical report for the study item “Study on latency reduction techniques for LTE” [2]. The purpose of this TR is to capture the findings from TSG RAN WG2 and WG1 according to their respective objectives, and to draw a conclusion on way forward.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.885
|
Study on LTE-based V2X services
|
TR
|
14.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.885/36885-e00.zip
|
The present document contains the results and findings from the study item, “Feasibility Study on LTE-based V2X Services” [2]. The purpose of this TR is to document the identified LTE enhancements and corresponding evaluations for LTE-based V2X services defined in [3] as follows:
- V2V (vehicle-to-vehicle): covering LTE-based communication between vehicles.
- V2P (vehicle-to-pedestrian): covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger).
- V2I/N (vehicle-to-infrastructure/network): covering LTE-based communication between a vehicle and a roadside unit/network. A roadside unit (RSU) is a stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications. Note: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that combines V2X application logic with the functionality of an eNB (referred to as eNB-type RSU) or UE (referred to as UE-type RSU).
This document addresses LTE-based V2X both with and without LTE network coverage, and covers both the operating scenario where the carrier(s) is/are dedicated to LTE-based V2X services (subject to regional regulation and operator policy including the possibility of being shared by multiple operators) and the operating scenario where the carrier(s) is/are licensed spectrum and also used for normal LTE operation.
This technical report contains the evaluation methodology for LTE-based V2V, V2I/N and V2P services to compare the performance of different technical options.
This document identifies necessary enhancements to LTE for support of PC5 transport for V2V services.
This document captures identification and evaluation of Uu transport for V2V and PC5/Uu transport for V2I/N and V2P services.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.886
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Band 41 High Power UE (HPUE)
|
TR
|
14.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.886/36886-e10.zip
|
The scope of the present document is to evaluate the feasibility of increasing UL TX power in Band 41 from 23dBm +/-2dB (Power Class 3) to 26dBm +/-2dB (Power Class 2) as well as discuss impacts (if any) to other 3GPP bands and regulatory requirements.
|
36.896
|
Study on Flexible eNB-ID and Cell-ID in E-UTRAN
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.896/36896-e00.zip
|
The present document is related to the technical report of the study item "Study on Flexible eNB-ID and Cell-ID in E-UTRAN " (RP-160534 [2]).
This activity involves the Radio Access work area of the 3GPP studies and has impacts on the Access Network of the 3GPP systems.
The present document gathers all technical outcome of the study item, and draws a conclusion on the way forward.
|
36.898
|
Network Assistance for Network Synchronization
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.898/36898-e00.zip
|
The present document captures the results of the study item on Network Assistance for Network Synchronization in LTE in RP-151084 [2]. It identifies the existing LTE functions that may need network based synchronization and their synchronization-related requirements, and reviews and compares techniques for enhancement of RAN functionality.
|
37.805
|
Study on HSPA and LTE Joint Operation
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.805/37805-e00.zip
|
The present document captures the results of Study on HSPA and LTE Joint Operation in RP-160571 [2]. It identifies possible solutions to support concurrent transmission of CS in UMTS and PS in LTE and evaluates the impacts on network architecture and interface.
|
37.871
|
E-UTRA, UTRA and GSM/EDGE; Multi-Band Base Station testing with three or more bands
|
TR
|
14.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.871/37871-e00.zip
|
The present document is a technical report of the Multi-Band Base Station testing with three or more bands work item which was approved at TSG RAN #70 [2]. The objective of the present document is to provide specification support for Multi-Band Base Station testing with three or more bands.
The present document provides motivation, requirements and a list of recommended changes to the specifications.
|
38.801
|
Study on new radio access technology: Radio access architecture and interfaces
|
TR
|
14.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.801/38801-e00.zip
|
The present document covers the Radio Access Architecture and Interface aspects of the study item “New Radio Access Technology” [1]. The purpose of this TR is to record the discussion and agreements that arise in the specification of the “New Radio Access Technology” from an Access Architecture and Interface specification point of view.
|
38.802
|
Study on new radio access technology Physical layer aspects
|
TR
|
14.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.802/38802-e20.zip
|
This document is related to the technical report for physical layer aspect of the study item “Study on New Radio Access Technology” [2]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, along with the complexity evaluation of each technique.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information in order to compare the solutions and gains vs. complexity, and draw a conclusion on way forward.
This document will be kept up-to-date via CRs in the future.
|
38.803
|
Study on new radio access technology: Radio Frequency (RF) and co-existence aspects
|
TR
|
14.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.803/38803-e40.zip
|
The present document covers the RF and co-existence aspects of the study item “New Radio Access Technology” [1].
|
38.804
|
Study on new radio access technology Radio interface protocol aspects
|
TR
|
14.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.804/38804-e00.zip
|
The present document covers the Radio Interface Protocol aspects of the study item “New Radio Access Technology” [1]. This document is intended to gather the agreements for which normative work will take place after completing this study item. In limited cases, major options and reasons of decision are described.
|
38.805
|
Study on new radio access technology; 60 GHz unlicensed spectrum
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.805/38805-e00.zip
|
The present document contains the results and findings from the study item, “Study on New Radio Access Technology” [2].
This technical report documents the existing regulatory requirements for unlicensed spectrum deployment in the 60 GHz bands.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
44.118
|
Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol; Iu mode
|
TS
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.118/44118-e00.zip
| |
45.871
|
Study on Multiple Input Multiple Output (MIMO) for GSM/EDGE downlink
|
TR
|
14.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.871/45871-e00.zip
|
The present document contains investigations carried out and during the 3GPP study item on MIMO for GSM/EDGE Downlink.
The following items are covered in this study report:
- Objectives for the study
- Overview of MIMO for Downlink concept
- Conceptual design of several functional blocks of this solution
- Performance evaluations related to envisaged functional blocks belonging to MIMO for Downlink
- Compatibility analysis
|
22.234
|
Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking
|
TS
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.234/22234-d10.zip
|
This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
Maintenance of the I-WLAN feature is discontinued as of Release 12. No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
22.806
|
Study on application-specific congestion control for data communication
|
TR
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.806/22806-d10.zip
|
The present document provides a study on Application specific Congestion control for Data Communication (ACDC). This Study investigates the following aspects:
- Identify the use cases and potential requirements to allow/restrict the communication initiation of particular applications defined by operator, subject to regional regulations;
- Gap analysis with existing access control mechanisms.
|
22.807
|
Study on enhancements for infrastructure-based data communication between devices
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.807/22807-d00.zip
|
More and more devices are becoming connected. These connected devices can be MTC devices such as smart meters, but increasingly all kinds of consumer electronic devices (e.g. photo cameras, navigation devices, e-books, hifi equipment, TVs) are connected. Where Machine-Type Communication is generally client server based, many consumer electronic devices also communicate with other consumer electronic devices. For example a photo camera can communicate with a printer, or a media server can communicate with hi-fi equipment. It may be of interest for the cellular industry to support infrastructure based discovery and communications between connected devices, i.e. without the need for intermediate network servers.
In this context, the objective of the present document is to study:
• Potential enhancements to support secure discovery of Ues of interest
• Potential enhancements to support secure optimized end-to-end data communication between Ues via the 3GPP infrastructure
• Potential enhancements derived from user requirements for identification in communication between Ues
• Potential interactions of data communication between devices with LIPA and SIPTO
Ues may represent functions/capabilities provided by non-3GPP devices in order to support interworking. However, discovery of, or end-to-end data communication with, non-3GPP devices themselves is out of scope.
Potential enhancements will be studied through the definition of use cases. From these use cases, potential requirements are identified. For potential requirements identified, if any, it will be determined what is the best way to approach normative specification.
|
22.810
|
Study of enhanced call information presentation
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.810/22810-d00.zip
|
The present document will consider use cases and identify potential requirements for enhancing the calling information presentation. This will include:
- Type of contents shared in calling information presentation, e.g. number, name, portrait, signature, etc.
- Use cases for both calling party and called party.
- Interaction with MMTel services, CAT, and CRS service.
- Interoperability with other network.
|
22.828
|
Study on co-ordinated Packet data network GateWay (PGW) Change for Selected IP Traffic Offload (CSIPTO)
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.828/22828-d00.zip
|
The present document considers use cases and identifies potential requirements for network consideration of the following items regarding the change of local PGW in use for SIPTO:
a) end-user experience and preferences; and
b) UE's knowledge of ongoing IP flow types.
|
22.852
|
Study on Radio Access Network (RAN) sharing enhancements
|
TR
|
13.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.852/22852-d10.zip
| |
22.853
|
Study on Service Exposure and Enablement Support (SEES) requirements
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.853/22853-d00.zip
|
The present document identifies potential requirements for the network information and capability that the 3GPP network could exposed to the 3rd party applications and the MNOs could get the benefits from such the 3rd party applications.
The present document identifies if existing capabilities (e.g. MOSAP, OMA, GSMA oneAPI, MTC IWF) already satisfy the use cases. Potential additional requirements are formulated if enhancements to existing capabilities or new capabilities are needed.
|
22.897
|
Study on isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.897/22897-d00.zip
| |
22.934
|
Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.934/22934-d00.zip
|
This document studies the feasibility of interworking between 3GPP systems and Wireless Local Area Networks (WLANs). This document identifies and describes:
- Scenarios for 3GPP - WLAN Interworking
- 3GPP - WLAN interworking service requirements
- Guidelines for standardisation of 3GPP-WLAN interworking
The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
It is beyond the scope of 3GPP to develop new system functionalities for WLANs that are not interworking with any 3GPP system functionality.
|
22.935
|
Feasibility study on Location Services (LCS) for Wireless Local Area Network (WLAN) interworking
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.935/22935-d00.zip
|
The 3GPP has developed and continues to develop Location Services (LCS) requirements and standards for GSM and UMTS. To further the advancement of LCS within the 3GPP, LCS requirements and standards may be extended for 3GPP WLAN interworking to support the same location-based services that have been deployed today for GSM and UMTS. LCS with 3GPP WLAN Interworking system is considered to enlarge the area of location services.
The purpose of the feasibility study is to study a generic interworking functionality for LCS between 3GPP system and WLAN systems (e.g. IEEE 802.11 family, HIPERLAN/2, …). Specifically, the feasibility study aims to:
- Study the LCS requirements for 3GPP WLAN Interworking scenarios.
- Study the different possible LCS architectures for interworking.
Also, the feasibility study will:
- Assess the service requirements for support of LCS over I-WLAN
- Define the MMI aspects, i.e., the minimum set of functions to support LCS when the choice of access system by the user and/or terminal for when both access systems is available.
- Assess the charging requirements and architecture impacts. In particular, consider whether or not WLAN charging for LCS should be integrated with the architecture for UMTS charging for LCS.
- Assess the security requirements, given the prerequisite that a) the security level of the UMTS platform itself is not impacted, b) the security level provided to users in the WLAN mode is comparable to the one of UMTS.
|
22.937
|
Requirements for service continuity between mobile and Wireless Local Area Network (WLAN) networks
|
TR
|
13.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.937/22937-d00.zip
|
The present document develops the use cases and requirements for service continuity between a 3GPP network and another network, which can be:
- a TISPAN NGN with an IMS, accessed by a WLAN.
- an ISP accessed via a WLAN
Each access network has its own separate security system and the NOs have a commercial agreement for roaming and handover.
The present document considers use cases whereby:
Editors Note: Text to be added when use cases are agreed
The present document also examines the requirements and implications of:
- service aspects: maintaining service quality and service continuity, while roaming between a 3GPP PLMN and an independently-owned WLAN;
- security aspects: while roaming between a 3GPP PLMN and a WLAN, in particular when networks may be independently authenticated.
- UICC aspects, including NAA types, personalisation and ownership.
The present document is related to ongoing standardisation efforts in the following areas:
- where the WLAN is an I-WLAN , requirements for which are described in [3];
- methods for selecting the 3GPP or the non-3GPP access network, requirements for which are described in [2].
|
23.179
|
Functional architecture and information flows to support mission critical communication services; Stage 2
|
TS
|
13.5.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.179/23179-d50.zip
|
This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service including the common services core architecture for identity management, group management, and configuration management required to support the MCPTT voice service. Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The corresponding service requirements are defined in 3GPP TS 22.179 [2].
The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [9]. Certain MCPTT functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access.
The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats.
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered, however, for roaming only EPC-level roaming and IMS-level roaming are considered i.e. partner MCPTT system based roaming (also known as "migration") is out of scope.
|
23.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; System description
|
TS
|
13.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-d10.zip
|
This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications.
|
23.327
|
Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems
|
TS
|
13.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-d10.zip
|
This document specifies the stage 2 system description for providing mobility between 3GPP Wireless Local Area Network Interworking (I‑WLAN) and 3GPP Systems. The I-WLAN feature defined in TS 23.234 [2] has been discontinued since Release 13 and it is removed from this specification.
|
23.704
|
Study on Circuit Switched (CS) / Packet Switched (PS) coordination in shared network; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.704/23704-d00.zip
|
The present document investigates relevant scenarios and possible solutions to enhance the CS/PS Coordination in a shared UTRAN/GERAN network as currently specified in TS 23.251 [2].
Within this technical report relevant mobility scenarios shall be investigated and it shall be evaluated per scenario if any issues with CS/PS Coordination can be expected. The investigation shall be done for non-supporting UEs and for any UE in shared networks where no Multiple PLMN list is broadcasted. Solutions to solve found issues shall be evaluated and agreed for subsequent normative specification.
The scenarios that need to be handled will at least include:
- CS handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- PS Handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- Redirection;
- Cell reselection;
- CSFB;
- rSRVCC and SRVCC;
- PLMN selection at handover based on UE capability;
- Registration to PS domain in a shared network after CS only registration has been performed.
|
23.705
|
Study on system enhancements for user plane congestion management
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.705/23705-d00.zip
|
The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document.
|
23.706
|
Study on enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.706/23706-d00.zip
|
This document studies enhancements to the IMS architecture and stage 2 procedures in order to support the requirements defined by SA1 as part of eWebRTCi (Enhancements to WEBRTC interoperability).
The output of this work will not require changes to existing WebRTC enabled web browsers.
|
23.707
|
Architecture enhancements for dedicated core networks; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.707/23707-d00.zip
|
An operator may choose to deploy one (or more) dedicated core networks within a PLMN with each core network dedicated for specific type(s) of subscriber. The present document studies and evaluates architectural enhancements required to support dedicated core networks. The specific dedicated core network that serves a UE is selected based on subscription information and operator configuration, without requiring the UEs to be modified.
The technical report covers both assignment of dedicated core network nodes and maintaining the association during mobility. Roaming and network sharing aspects of dedicated core network, and impacts on procedures such as CSFB, SRVCC and rSRVCC will be studied.
Dedicated core networks may be in the PS domain or CS domain or both.
|
23.708
|
Architecture enhancements for service capability exposure
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.708/23708-d00.zip
|
The present document studies and evaluates architecture enhancements for a service capability exposure framework wherein 3GPP system provided service capabilities are exposed via one or more standardized APIs, e.g. the OMA-API(s). As part of this work it will be identified how the APIs and the 3GPP system functionality act together to expose 3GPP service capabilities. The definition of APIs is out of scope of this work item.
The present document will also define the architectural enhancements for new service capabilities and services (based on the Stage 1 normative requirements) that are exposed via the service capability exposure framework.
|
23.709
|
Study on optimizations to support high latency communications; Stage 2
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.709/23709-d00.zip
|
This document captures the study result of possible system enhancements to support applications that communicate with devices that are not reachable for a long period over the 3GPP IP connectivity and being able to support large number of such devices in the system without negatively affecting the system performance.
In addressing the above, the following problem is studied:
- Downlink access for devices that are not reachable for a long period and the problems associated with such devices (e.g. packet discard when the UE sleeps, frequent retransmissions, load on the CN network, waste of radio resources and UE power when the network unnecessarily conveys retransmit packets, etc.). This study may propose and evaluate enhancements to the 3GPP system. Depending on conclusions, the study may also propose 3GPP enablers to be used by the service layer e.g. defined by other SDOs for downlink access to devices that are not reachable for a long period.
Different application layer protocols used within the M2M ecosystem have different requirements and characteristics with respect to acceptable end-to-end delay, round trip time, persistence in retransmissions, etc. The result of this study may include general recommendations for application layers how to use the 3GPP accesses for better application performance and optimal core and radio network efficiency thereof.
|
23.712
|
Study on warning status reporting
|
TR
|
13.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.712/23712-d00.zip
|
The present document investigates possible enhancements to the Warning Status Reporting mechanisms specified up to release 12 in 3GPP TS 23.041 [2].
The study will cover:
- identification of requirements for Warning Status reporting;
- identification and evaluation of alternatives for Warning Status reporting;
- analysis on their potential interactions with the existing mechanisms; and
- recommendations on the alternatives.
The result of this study will be used to identify the changes possibly required in the 3GPP specifications to support enhanced Warning Status reporting mechanisms.
|
23.713
|
Study on extended architecture support for proximity-based services
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.713/23713-d00.zip
|
The scope of this Technical Report is to study and evaluate the possible architecture enhancements to the Proximity-based Services (ProSe) system defined in TS 23.303 [3], based on the relevant Stage 1 requirements defined in TS 22.278 [4] and TS 22.115 [5].
The present Technical Report documents the analysis and general principles agreed regarding these objectives, and collects the solution details developed based on these agreements, in order to progress them to the relevant specifications.
|
23.718
|
Architecture enhancement for flexible mobile service steering
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.718/23718-d00.zip
|
The present document studies and evaluates architectural enhancements required for 3GPP systems to provide flexible mobile service steering policies as per the service requirements defined in TS 22.101 [2], clause 30.
NOTE: Service enablers supported within the (S)Gi-LAN and the routing of traffic between those service enablers are not in the scope. The scope of the work is restricted to providing policies for traffic steering through interfaces defined by 3GPP.
|
23.720
|
Study on architecture enhancements for Cellular Internet of Things (CIoT)
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.720/23720-d00.zip
|
The present document studies and evaluates the architecture enhancement to support ultra-low complexity, power constrained, and low data-rate 'Internet of Things' devices.
The study will consider architecture enhancements/simplifications in the following areas:
- Support of highly efficient handling of frequent and infrequent small data transmissions (e.g. based on the traffic model in TR 45.820 [4]) with minimised overhead for system signalling without compromising e.g. security.
- Support of power consumption optimisations and/or using existing ones that have been developed for EPS or GPRS.
- Assessing simplification of Mobility Management and Session Management procedures.
- Support of paging optimisations for UEs requiring coverage enhancements.
The present document will also consider system architecture alternatives to address the points above.
|
23.741
|
Study on enhancements to Multimedia Broadcast/Multicast Service (MBMS) for LTE
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.741/23741-d00.zip
|
The objective of this Technical Report is to study and specify potential modifications to the MBMS/GCSE_LTE architectures and/or procedures as specified in TS 23.246 [2] and TS 23.468 [3] to enable the following improvements and enhancements:
1. to allow the establishment of MBMS bearers using target area information, as distinct from using an MBMS Service Area;
2. to MBMS congestion handling;
3. if seen to be needed, to possible MBMS roaming scenarios;
4. as required by the MCPTT application work.
|
23.769
|
Group based enhancements
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.769/23769-d00.zip
|
The present document studies and evaluates architectural enhancements required for Group based features which include the following aspects:
- Fulfil the general group based requirements (TS 22.368 [2] clause 7.2.14.1)
- Fulfil the group based policing requirements (TS 22.368 [2] clause 7.2.14.2)
- Fulfil the group based addressing requirements (TS 22.368 [2] clause 7.2.14.3)
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study.
|
23.770
|
Study on system impacts of extended Discontinuous Reception (DRX) cycle for power consumption optimization
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.770/23770-d00.zip
|
The present document studies the core network and NAS impacts in UE of extending DRX cycle for both idle mode and connected mode, solutions in the core network to support it, and interactions between GERAN/RAN and Core Network. Also, basic assumptions may be done for each solution on GERAN/RAN aspects of extending DRX cycle.
The main goal is to identify which open issues remained from the Rel‑12 study for extended Idle and Connected mode DRX as described in TR 23.887 [4] (as documented in clause 7.1.3.1 and 7.1.3.6 of TR 23.887), document potential solutions and conclude on which feasible solutions would be adopted in core network (pending work in RAN regarding extension of DRX cycle).
No connected mode mobility enhancements for extended C-DRX are considered in this work, i.e., if a UE using extended C-DRX moves to a different cell, current connected mode mobility procedures apply.
|
23.771
|
Study on system impacts of IP Multimedia Subsystem (IMS) emergency sessions over Wireless Local Area Network (WLAN)
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.771/23771-d00.zip
|
The present document studies the mechanisms needed to support IMS Emergency sessions over WLAN (both in the Trusted -S2a - and in the untrusted -S2b- cases)
The study is split up into 2 phases corresponding to 2 SID (FS_SEW1 and FS_SEW2).
Topics to be studied in phase 1 (FS_SEW1) are:
- Providing access to EPC over WLAN in order to support an emergency session only in case of "Valid" UEs as in the case 1 in clause 4.3.12.1 of TS 23.401 [3]: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session.
- Providing Location information (in particular for untrusted WLAN). Only existing location determination mechanisms are considered i.e. location determination mechanisms that should not require standard effort. No location accuracy requirements are considered in phase 1.
Phase 1(FS_SEW1) will not consider solutions that imply specification activities in other SDO(s).
Topics to be studied in phase 2 (FS_SEW2) correspond to all the features not covered by phase 1, e.g.:
- Support of other cases for the access to EPC over WLAN (e.g. the UE is authenticated but is in a location where it is restricted from regular service, or is unauthenticated or has no USIM).
- Roaming cases (user not in his / her home country).
- Support of session continuity of emergency sessions at inter-access mobility.
- TWAN access.
|
23.772
|
Enhanced Circuit Switched (CS) fallback
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.772/23772-100.zip
|
Editor's note: This clause will describe the work scope of the work item.
The present document studies enhancements for CSFB in the interest of shortening the call setup time. Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
There shall be no UE impact.
Normative specifications may be developed based on the conclusions of the present document.
|
23.779
|
Study on application architecture to support Mission Critical Push To Talk over LTE (MCPTT) services
|
TR
|
13.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.779/23779-d00.zip
|
This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for the Mission Critical Push To Talk over LTE (MCPTT) application. This TR will identify the architecture needed to support MCPTT services based on the Stage 1 requirements, including TS 22.179 [2]. This Technical Report depends on functionality specified in 3GPP specifications.
|
23.789
|
Monitoring Enhancements
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.789/23789-d00.zip
|
The present document studies and evaluates architectural enhancements required for 3GPP systems to provide monitoring service capability as per the service requirements defined in TS 22.368 [2], clause 7.2.8 and TS 22.101 [10], clause 29.2.
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study.
|
23.797
|
Study on architecture enhancements to support isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.797/23797-d00.zip
|
This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Isolated E-UTRAN operation for public safety based on the Stage 1 requirements in TS 22.346 [3].
|
23.858
|
Usage Monitoring Control PCC Enhancement
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-d00.zip
|
The scope of this technical report is to capture the results of a study that investigates if enhancements to the existing policy control architecture are needed in the area of usage monitoring control. The goals of the study are to derive possible requirements and architecture enhancements for:
1. Monitoring of service (s) / application (s) in more than one usage monitoring group;
2. Disabling a service (s) / application (s) from the existing usage monitoring group of services/group of applications;
3. Excluding the usage of a particular service (s) / application (s) from the accumulated usage for the IP-CAN session/TDF session;
4. Usage control for a subscriber group, e.g. the members of a family or a company subscriber, or a group of devices belonging to subscribers that share the same usage allowance threshold.
In addition, study the different proposed solutions for effective time based usage monitoring and how associated start and end of usage is defined.
|
23.861
|
Network based IP flow mobility
|
TR
|
13.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.861/23861-d00.zip
|
Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel‑13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel‑10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel‑13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel‑13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel‑13 consider the following aspects:
- The support of a PDN Connection active over multiple accesses simultaneously.
- The association of one or multiple IP flows belonging to a PDN connection to an access system.
- The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
- The triggers for IP flow mobility in the UE and the network.
- UE-initiated and network-initiated NBIFOM.
- The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used.
|
24.381
|
Mission Critical Push To Talk (MCPTT) group management; Protocol specification
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.381/24381-d40.zip
|
The present document specifies the group management protocols needed to support Mission Critical Push To Talk (MCPTT). Group management applies only when the UE operates on the network.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the group management client (GMC) functionality, to application server supporting the group management server (GMS) functionality, and to application server supporting the MCPTT server functionality.
|
24.382
|
Mission Critical Push To Talk (MCPTT) identity management; Protocol specification
|
TS
|
13.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.382/24382-d30.zip
|
This document specifies the identity management and authentication protocols needed to support Mission Critical Push To Talk (MCPTT). Identity management applies only to on-network operation.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
This document is applicable to User Equipment (UE) supporting the identity management client functionality, and to application servers supporting the identity management server functionality.
|
24.383
|
Mission Critical Push To Talk (MCPTT) Management Object (MO)
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.383/24383-d40.zip
|
The present document defines a number of Mission Critical Push To Talk (MCPTT) Management Objects (MO) that are configured for the MCPTT UE for the operation of the MCPTT Service. The management objects are compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA OMA-ERELD_DM-V1_2 [2].
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting on-line, off-line or both on-line and off-line configuration of the configuration management client.
The present document is applicable to an MCPTT UE supporting off-line configuration of the group management client.
The parameters defined by the management objects in the present document are configured in the MCPTT UE using on-line configuration over the CSC-4 reference point and using off-line configuration over the CSC-11 and CSC-12 reference points. Other specifications define how these parameters are used in the operation of MCPTT, and whether they are applicable to on-network operation or off-network operation, or both:
- 3GPP TS 24.379 [7]
- 3GPP TS 24.380 [8]
- 3GPP TS 24.381 [9]
- 3GPP TS 24.382 [11]
- 3GPP TS 24.384 [12]
The common network operation means both on-network operation and off-network operation in the present document.
The following management objects are defined in the present document:
- MCPTT UE configuration MO
- MCPTT user profile MO
- MCPTT group configuration MO
- MCPTT service configuration MO
- MCPTT UE initial configuration MO
The MOs listed above define repositories of data in the ME.
|
24.384
|
Mission Critical Push To Talk (MCPTT) configuration management; Protocol specification
|
TS
|
13.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.384/24384-d40.zip
|
The present document specifies the configuration management documents and protocols needed to support Mission Critical Push To Talk (MCPTT) online configuration over the CSC-4 and CSC-5 reference points and the procedures to support Mission Critical Push To Talk (MCPTT) offline configuration over the CSC-11and CSC-12 reference points. Configuration management documents defined in the present document includes:
MCPTT UE initial configuration document;
MCPTT UE configuration document;
MCPTT user profile configuration document; and
MCPTT service configuration document.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting the configuration management client functionality, to application server supporting the configuration management server functionality, and to application server supporting the MCPTT server functionality.
|
25.705
|
Study on Small data transmission enhancements for UMTS
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.705/25705-d00.zip
|
The study on small data transmissions enhancements for UMTS has as a target to investigate and provide solutions in the areas of coverage, signalling optimization, support of massive deployment of devices, and power savings taking into consideration minimizing the impact on the physical layer, legacy terminals, and networks [2].
|
25.706
|
Technical Report on Downlink Enhancements for UMTS
|
TR
|
13.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.706/25706-d00.zip
|
WCDMA currently serves as the dominant mobile broadband technique. The number of connections for WCDMA users and the average user date rate have continued to increase in the past years and will further increase in the coming years, which requires WCDMA to evolve further from both uplink and downlink perspective.
|
25.756
|
RAN sharing enhancements for UMTS
|
TR
|
13.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.756/25756-d00.zip
|
This document captures the results of the study item on RAN Sharing Enhancements for UMTS in RP-142284 [2]. It identifies the existing functions for UTRAN RAN Sharing, the use cases and requirements for enhancements, and reviews and compares scenarios and techniques for enhancement of RAN functionality.
|
25.766
|
Study on Network-Assisted Interference Cancellation and Suppression for UMTS
|
TR
|
13.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.766/25766-d10.zip
|
The study on network-assisted interference cancellation and suppression for UMTS has as a target to investigate the potential solutions in the areas of mechanisms for offloading, CQI mismatch issue, and signaling of parameters for UEs with NAICS capability and enhanced techniques , including considerations to minimize the impact on physical layer and legacy terminals and networks. [2].
|
28.821
|
Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.821/28821-d00.zip
|
The present document is the result of the Multi-SDO JWG on Model Alignment which 3GPP TSG SA WG5 (SA5) has developed jointly with TMF and NGMN, and which does not fully follow the 3GPP templates and drafting rules.
Therefore 3GPP SA5 has desired to keep the present document as similar as possible to the original in ([9]), for comparison with the corresponding TMF version.
Thus 3GPP SA5 has done only the strictly necessary changes from the 3GPP drafting rules perspective in order to publish the present document as a 3GPP Technical Report. One of these type of changes is due to the fact that it is not allowed to use "shall" in an informative TR. However, in order to preserve the original intention of "must" and "shall" in the original JWG document and distinguish it from other places where "should" has been used (in case it is decided in the future to transform the TR into a TS), the use of "shall" is marked in italics font as "shall".
The JWG on Model Alignment work has chosen UML to capture behaviour of systems/entities under management.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of JWG Model Alignment work. This paper documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by JWG Model Alignment work. Collectively, this set of notations and model elements is called the FMC (developed by the Converged Management of Fixed/Mobile Networks project) Model Repertoire.
JWG Model Alignment specifications shall employ the UML notation and model elements of this repertoire. In the course of the JWG Model Alignment work, JWG Model Alignment group may modify (add, delete, modify) UML notation and model elements of this repertoire when necessary.
|
29.810
|
Study on Diameter load control mechanisms
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.810/29810-d00.zip
|
The present document investigates possible enhancements of the Diameter base protocol (IETF RFC 6733 [2]) and existing Diameter applications to support load control mechanisms in 3GPP core networks.
This work is based on the related work done in the IETF Diameter Maintenance and Extensions (DiME) working group. The Diameter overload control work and specifications done in IETF (e.g. IETF RFC 7068 [3] and IETF RFC 7683 [4]) and 3GPP will be taken into account.
This study covers:
- the identification of the set of requirements for load information exchange over Diameter based signalling interfaces used in 3GPP core networks, compared to those already expressed in IETF RFC 7068 [3] and any other requirements specified by the DiME working group;
- the evaluation of the IETF solution for load information exchange and applicability to 3GPP;
- possible enhancements specific to 3GPP;
- the identification of the 3GPP interfaces as possible candidates for the support of the load information exchange.
The results of this study will contribute to and rely on the work done within the IETF DiME working group on Diameter load control. Objective is to use the solution(s) that will be defined for Diameter load control by IETF DiME for 3GPP Diameter based networks and to avoid 3GPP specific enhancements.
Depending on this study outputs, normative work may be required to support load control mechanisms over Diameter-based 3GPP interfaces and applications.
|
29.811
|
Study on EPC signalling improvements for race scenarios
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.811/29811-d00.zip
|
The present document analyses various EPC race conditions scenarios and scenarios with hanging session or bearer contexts in EPC nodes, and assesses whether to improve the existing protocols and/or specifications for effective handling of these scenarios. The specification updates, if needed, may consist in EPC (GTP-C, PMIP and/or Diameter) signalling improvements, recommendations on how to minimize the occurrences of the issues, and/or clarifications on how the EPC nodes should behave in these scenarios.
|
29.812
|
Study on SCC AS Restoration
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.812/29812-d00.zip
|
The present document contains a detailed description of the SCC AS restoration procedure to be used in the eSRVCC network specially. The purpose of the SCC AS restoration procedure, as described in the present document, is to ensure that the originating or terminating session is continued or resumed as soon as possible when some the SCC AS in the SCC AS pool is out of service. The document defines the SCC AS failure scenarios, possible solutions and solution analysis. For the related procedure and functionality of S-CSCF, SCC AS, ATCF and HSS in the IMS and eSRVCC environment, it is based on the requirement in 3GPP related specifications
As the introduction of eSRVCC, the SCC AS shall exchange eSRVCC related parameters with ATCF and HSS during initial registration and re-registration procedures as described in 3GPP TS 24.237 [2], which is different from all other ASs.
i) ATCF reports its ATCF-Management-URI and ATCF-Path-URI towards the SCC AS, and the SCC AS stores it for later routing of MESSAGE.
ii) SCC AS shall send MESSAGE to ATCF with its own ATU-STI based on ATCF-Management-URI received, in order to ensure the routing of eSRVCC procedure triggered by ATCF later.
iii) SCC AS shall also update the received ATCF-Path-URI of ATCF towards HSS, HSS forwards it to MME, and stores it for subscriber downloading to SCC AS later.
The present document analysis SCC AS failure implications in eSRVCC network, it studies possible solutions and determines whether any should be standardize.
|
29.813
|
Study on S6a/S6d Shared Data Update
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.813/29813-d00.zip
|
The present document analyses the scenarios where permanent subscription data that are shared by multiple subscribers (e.g. MTC UEs) are modified by administration means in the HSS. Existing mechanisms in 3GPP networks to convey the change of subscription data to relevant MMEs/SGSNs and their drawbacks are outlined and possible solutions avoiding such drawbacks are discussed.
The recommendation of the document is used to decide whether it is required to standardize any solution, and which is the final preferred solution if further standardization is needed.
|
29.819
|
Study on impacts of the Diameter Base Protocol specification update.
|
TR
|
13.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.819/29819-d00.zip
|
The IETF RFC 3588 [2] specifying the Diameter base protocol has been obsoleted by the IETF RFC 6733 [3]. This new version of the IETF RFC is not a new version of the Diameter base protocol but a specification update intended to fix issues discovered after early implementations of the protocol.
The aim of the Technical Report is to:
- appraise the differences between the IETF RFC 6733 [3] and the IETF RFC 3588 [2];
- analyze the possible impacts on the 3GPP specifications relying on the Diameter base protocol and then;
- provide guidelines regarding a general update of the normative reference for Diameter base protocol.
|
29.826
|
P-CSCF restoration enhancements for WLAN
|
TR
|
13.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.826/29826-d10.zip
|
The present document analyses P-CSCF restoration enhancements for WLAN. After reviewing existing P-CSCF restoration with their limitations, it defines the objectives to fulfil and proposes solutions addressing trusted WLAN using S2a interface and untrusted WLAN using S2b interface. The enhancements refer to and complement the HSS based and PCRF based solutions for 3GPP accesses specified in Rel12 and described in 3GPP TS 23.380 [2].
|
31.829
|
Conformance requirements for IP Multimedia Services Identity Module (ISIM) application test specification
|
TR
|
13.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.829/31829-d00.zip
|
The present document objective is to develop a technical report listing the conformance requirements extracted from TS 31.103. This technical report will then be a basis for a gap analysis of test coverage and the subsequent development of test cases to verify the conformance of Terminals with features for the ISIM application.
The conformance requirements should allow:
• Ensuring that content of the ISIM when available is read and used by the ME
• Reusing of existing test specifications in 3GPP
• Providing recommendations when necessary to fulfil the test purpose
|
32.151
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
|
TS
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-d00.zip
|
The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series.
|
32.152
|
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
|
TS
|
13.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-d20.zip
|
3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.
|
32.842
|
Telecommunication management; Study on network management of virtualized networks
|
TR
|
13.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.842/32842-d10.zip
|
The present document studies the network management of virtualized 3GPP specified core networks based on the architectural framework in ETSI GS NFV-MAN 001 [2]. It studies the network management of mobile networks that include virtualized core networks functions.
It also identifies the potential impacts on the existing 3GPP management architecture and to propose potential solutions for the network management of fully virtualized networks and mixed networks.
The objectives of this study are:
- Study the use cases and concepts for the network management of virtualized networks, which are applicable to 3GPP, taking into account the relevant use cases from ETSI.
- Analyse and classify the network management scenarios when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when all instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in fully virtualized networks).
- Analyse and classify the network management scenarios when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks).
- Identify the requirements for potential solutions for the network management of virtualized networks when some instances of 3GPP-defined network elements in a subsystem/domain are virtualized according to the architectural framework in ETSI GS NFV-MAN 001 [2] (i.e. in mixed networks). Study whether or not a single management system for mixed networks is required.
- Identify the potential impacts on the existing 3GPP Management reference model.
- Analyse the existing 3GPP Management reference model, interfaces, protocols and procedures to determine what can be re-used, adapted or extended and whether new IRPs are needed for network management of virtualized networks.
- Propose enhancements or extensions to the 3GPP Management reference model, if an impact is foreseen.
- If needed, solution(s) for a single management system for mixed networks should be studied.
- Provide recommendations for the standardization of the network management of fully virtualized networks and mixed networks, based on the result of the analysis and the potentially identified impacts, enhancements or extensions.
|
32.843
|
Telecommunication management; Charging management; Study on Inter-Public-Land-Mobile-Network (PLMN) Packet Switched (PS) domain online charging
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.843/32843-d00.zip
|
The present document studies PS domain Online Charging in a roaming context, when the Gateway node implementing the IP access to the PDN for data traffic, pertains to the VPLMN, whereas the Online Charging System (OCS) pertains to the HPLMN.
The study will focus, in a first phase, on high level scenarios for Flow Based Charging, relying on defined TS 23.203 [207] PCC roaming architectures with Gy crossing PLMNs, in order to investigate the following aspects:
- Information availability in both PLMNs
- Inter-PLMN connection mechanisms for Diameter messages
- Impacts on Inter-operator charging
- Whether a "proxy OCS" is needed
The two following configurations will be addressed:
- Gy between OCS residing in HPLMN and PCEF located in PGW VPLMN, for Local Breakout Roaming configuration defined by TS 23.401 [208] and TS 23.203 [207].
- Gy between OCS residing in HPLMN and PCEF located in IP-Edge fixed broadband access owned by a Convergent fixed-mobile VPLMN, for Non Seamless WLAN Offload (NSWO) 3GPP UEs traffic defined by annex S of TS 23.203 [207].
During this first phase, the study will also investigate a basic set of Online Charging features and parameters, to be used in an inter-PLMN situation.
Based on conclusions and recommendations for the first phase, the second phase of the study will address the inter-PLMN Gyn Reference Point for the support of Application Based Charging.
|
32.849
|
Study on Charging aspects of Roaming End-to-end scenarios with VoLTE IMS and interconnecting networks
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.849/32849-d00.zip
|
The objective of this study item is to document missing elements and information with regard to the roaming architecture for Voice over IMS with Local Breakout.
The present document collects and evaluates end-to-end roaming scenarios under different aspects of charging. The main scenarios presented will include mobile originating calls with and without the use of the loopback mechanism and mobile terminating call scenarios.
It will analyse operator requirements in consideration of the roaming scenarios and the existing Charging specifications
The conclusions are presented in a further clause with assumptions made and proposed further proceedings on that issues.
|
32.861
|
Telecommunication management; Study on application and partitioning of Interface N (Itf-N)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.861/32861-d00.zip
|
The present document examines IRP requirements selected from existing IRPs' requirement and identifies one or more subsets of these requirements. It also studies the grouping of IRP functionality to recommend which functionality is needed in a network management context to satisfy every given subset of requirements.
|
32.863
|
Telecommunication management; Fixed Mobile Convergence (FMC) metadefinitions for measurements and Key Performance Indicators (KPIs)
|
TR
|
13.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.863/32863-d00.zip
|
The present document defines the metadata for Performance Management (PM) performance measurements (KPIs/counters). The definition would enforce consistency in description/definition of all standardized performance measurements (counters/KPIs) by various SDOs and organizations (or Multi-SDO) involved in the Management of Converged Networks [6]. This consistency would facilitate encoding and decoding of performance measurements (counters/KPIs) exchanged (via management protocols) and/or stored in (database or files).
The metadata related to PM operations/notifications is not part of this PM measurement metadata.
The present document takes into account the recommendations from the Fixed Mobile Convergence (FMC) model repertoire [2] developed by the Multi-SDO JWG on Model Alignment.
|
33.179
|
Security of Mission Critical Push To Talk (MCPTT) over LTE
|
TS
|
13.12.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.179/33179-dc0.zip
|
The present document specifies the security architecture, procedures and information flows needed to protect the mission critical push to talk (MCPTT) service. The architecture includes mechanisms for authentication, protection of MCPTT signalling and protection of MCPTT media. Security for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified.
The functional architecture for MCPTT is defined in 3GPP TS 23.179 [2], the corresponding service requirements are defined in 3GPP TS 22.179 [3].
The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. As the security model is based on the public safety environment, some security features may not be applicable to MCPTT for commercial purposes.
|
33.832
|
Study on IMS Enhanced Spoofed Call Prevention and Detection
|
TR
|
0.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.832/33832-030.zip
|
The present document evaluates the IETF STIR working group active drafts for use in 3GPP networks for spoofed call detection and make recommendations on what aspects of IETF STIR active drafts should be incorporated into 3GPP IMS security specifications.
Additionally 3GPP technology specific aspects not considered or addressed in the IETF STIR Working Group will be identified and studied such as service interactions and deployment scenarios including (but not limited to):
• * Roaming
• * Business line trunking/PBX
• * CS to IMS transition scenarios
|
33.833
|
Study on security issues to support Proximity Services (ProSe)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.833/33833-d00.zip
|
The present document contains a study of the security aspects of Proximity Services (ProSe) and an evaluation of possible technical solutions needed to support such services. The Stage 1 requirements for these services are defined in TS 22.278 [2] and TS 22.115 [3]. These requirements include a list of general requirements on ProSe Security, Authorization and Privacy (TS 22.278 [2] clause 9.4), which are taken into consideration when developing the security key issues, security requirements and security solutions in the present document.
Different possible Stage 2 solutions for Proximity Services are studied in TR 23.703 [4].
Normative provisions/requirements are included in the present specification solely for the purposes of studying solutions and are not to be considered as implying normative requirements on 3GPP entities.
NOTE: Lawful Interception (LI) aspects are not covered in this document.
|
33.860
|
Study on Enhanced General Packet Radio Service (EGPRS) access security enhancements with relation to cellular Internet of Things (IoT)
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.860/33860-d10.zip
|
The present document contains a study of the EGPRS access security in relation to cellular IoT, and an evaluation of possible technical security enhancements needed to support such services. Different possible deployment scenarios for Cellular IoT, and related stage 2 solutions are being studied in TR 45.820 [2].
The scope of this study is limited to investigate the feasibility of improving the access security aspects of Gb mode. In more detail, the scope includes:
1) Investigate potential security threats, such as man in the middle attacks.
2) Investigate potential security enhancements between the UE and SGSN to mitigate said threats.
3) Define what security procedures and security algorithms that are recommended to be used by for Cellular IoT devices in Gb mode. This may be procedures and algorithms already specified in earlier 3GPP releases or it could be new procedures and algorithms being introduced as part of this feasibility study.
4) The potential security enhancements as part of this study item should aim at minimising the impacts to the GPRS core network.
|
33.872
|
Study on security enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS)
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.872/33872-d00.zip
|
The present document contains a study on security issues following the potential modifications of the IMS architecture and stage 2 procedures as required by the support of eWebRTCi (Enhancements to WEBRTC interoperability).
In particular, the present document focuses on:
• Support for end to end WebRTC security, subject to regulatory constraints, that avoids conversion between WebRTC and IMS security protocols , including the feasibility of end to end security aspects
• Third-party WebRTC access in the case where the 3rd party allocates IMS identities from a block where the associated subscription corresponds to a class of users supported by the WebRTC environment (e.g., enterprise associates) rather than a single end user
|
33.879
|
Study on security enhancements for Mission Critical Push To Talk (MCPTT) over LTE
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.879/33879-d10.zip
|
The present document contains a study of the security aspects of the Mission-Critical Push-To-Talk (MCPTT) service and its interaction with the network. This includes an analysis of the threats to the service, the security requirements to mitigate those threats and an evaluation of possible technical solutions designed to meet the security requirements of the service.
The Stage 1 requirements for the service are defined in TS 22.179 [2]. An evaluation of Stage 2 architectural solutions for MCPTT is performed in TR 23.779 [3] and TS 23.179 [10]. This study will include consideration of relevant 3GPP specifications, particularly for ProSe (TS 33.303 [4], TS 23.303 [5]) and GCSE (TS 23.468 [6]).
The focus of the present document is to support public-safety use cases of MCPTT. Commercial scenarios are not specifically considered and some features may not be applicable to them.
|
33.889
|
Study on security aspects of Machine-Type Communications (MTC) architecture and feature enhancements
|
TR
|
13.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.889/33889-d00.zip
|
The present document captures requirements, solution alternatives, evaluations and conclusions for the SA2-led Rel-13 Features:
• GROUPE (Group based Enhancements) [4],
• MONTE (Monitoring Enhancements) [5] and
• AESE (Architecture Enhancements for Service Capability Exposure [3].
The present document captures the conclusions of the study on security and privacy implications for the requirements identified in Stage 1 and Stage 2 specifications for the above mentioned Rel-13 MTC features.
Based on the outcome of the present document, any new normative text will be incorporated in TS 33.187 [2] and/or suitable existing SA3 specifications.
Editor’s Note: SA3 is supposed to work only on security solutions for architectural solutions that are covered in SA2 Rel-13 TRs TR 23.769[4], TR 23.789[5], TR 23.708 [3].
|
33.897
|
Study on isolated E-UTRAN operation for public safety; Security aspects
|
TR
|
13.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.897/33897-d10.zip
|
The present document contains the results of a Stage 2 study and evaluation of possible 3GPP security solutions in support of Isolated E-UTRAN Operation for Public Safety (IOPS). The solutions are based on the Stage 1 requirements in 3GPP TS 22.346 [2], the architectural enhancements to support IOPS presented in the Stage 2 study report 3GPP TR 23.797 [3] and resulting informative Annex K in 3GPP TS 23.401 [10]. For the current release of specification the solution in 3GPP TS 23.401 [10] is based on a Local EPC with no backhaul.
The present document identifies key issues, security threats, deduces security requirements and presents proposed security solutions for IOPS.
Throughout this Technical Report the terms 'IOPS network' and 'Isolated E-UTRAN' are used synonymously.
|
36.789
|
Multi-node tests for Licence-Assisted Access (LAA)
|
TR
|
13.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.789/36789-d00.zip
|
The present document describes the multi-node tests for Rel-13 LAA BSs and other wireless systems operating in unlicensed spectrum. In particular, the report documents how to conduct multi-node tests involving two Rel-13 LAA BSs or one Rel-13 LAA BS and one other wireless system, e.g. IEEE 802.11 system to make sure that the two systems can coexist in the same unlicensed spectrum. This document aims to provide an evaluation methodology for multi-node coexistence between Rel-13 LAA BSs and other wireless systems.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.