hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.1.1.1 Channel bandwidths per operating band for CA | Table 7.2.1.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_1A-41A
1
Yes
Yes
Yes
Yes
41
Yes
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.1.1.2 Co-existence studies for CA_1-41 | Table 7.2.1.1.2-1gives the intermodulation products for band 1 + band 41 CA with 2 DLs. For the IMD analysis the maximum transmission as defined in table 7.2.1.1.1-1 is considered. None of the harmonics of one band fall into the receive band of the other. The intermodulation products generated by two operating bands do not impact the own receiver since TDD BS cannot transmit and receive simultaneously in a single band.
It can be seen in the table that 2nd order IMD products may fall into BS receive band 31. The 3rd order IMD products may fall into BS receive bands of 1, 3, 4, 7, 9, 10, 23, 24, 30, 33, 34, 36, 37, 38, 39, 40 and 41. However, when the impact of maximum bandwidth is considered, the 3rd order IMD products do not fall into the BS receive of Band 1, 23, 30, 33, 34, 36, 37, 39, 40.
It should be noted that Bands 4, 7, 10, 24, 31 and 38 are not intended for use in the same geographical area as Band 1 and Band 41. This leaves bands 3, 9 and 41 to consider for IMD products.
Currently Bands 3, and 9 are used in the same geographical area as Bands 1 and 41. It is recommended that Bands 1 and 41 BS transmitters do not share the same antenna with Band 3 or 9 BS receivers so that the antenna PIM will not cause Band 3 or 9 BS receiver desensitization. A TDD BS cannot transmit and receive simultaneously in a single band so the own B41 receiver is protected. However, it is not recommended that different band 41 operators share the same antenna as a Band 1 transmitter unless the operation is synchronized.
Table 7.2.1.1.2-1: 2DLs B1 + B41 harmonics and IMD products frequency limits
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
2110
2170
2496
2690
2nd order harmonics frequency range (MHz)
4220
4340
4992
5380
3rd order harmonics frequency range (MHz)
6330
6510
7488
8070
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
|f2_low + f1_low|
|f2_high + f1_high|
IMD frequency limits (MHz)
326
580
4606
4860
3rd order IMD products
|f2_high – 2*f1_low|
|f2_low – 2*f1_high|
|2*f2_low – f1_high|
|2*f2_high – f1_low|
IMD frequency limits (MHz)
1530
1844
2822
3270
3rd order IMD products
|2*f1_low + f2_low|
|2*f1_high + f2_high|
|2*f2_low + f1_low|
|2*f2_high + f1_high|
IMD frequency limits (MHz)
6716
7030
7102
7550
3rd order IMD products
|f1_low – f2_high + f2_low|
|f1_high + f2_high – f2_low|
|f2_low – f1_high + f1_low|
|f2_high + f1_high – f1_low|
IMD frequency limits (MHz)
1916
2364
2436
2750
3rd order IMD products (with maximum channel bandwidth)
|f1_low – max BW f2|
|f1_high + max BW f2|
|f2_low – max BW f1|
|f2_high + max BW f1|
IMD frequency limits (MHz)
2090
2190
2476
2710
Table 7.2.1.1.2-2 analyzes the impact of harmonic products for band 1+ band 41 CA with band 1 as UL. We can conclude that none of UL harmonic products fall into the own and any other receive bands.
Table 7.2.1.1.2-2: Impact of UL harmonic interference
UE UL carriers
f1_low
f1_high
UL frequency (MHz)
1920
1980
2nd order harmonics frequency range (MHz)
3840 to 3960
3rd order harmonics frequency range (MHz)
5760 to 5940
NOTE: Only Band 1 is utilized as UL in the WI.
7.2.1.1.3 ∆TIB and ∆RIB values
For two simultaneous DLs and only one UL, TIB,c and RIB values are shown in tables below.
Table 7.2.1.1.3-2: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_1A-41A
1
0.5
41
0.5
Table 7.2.1.1.3-3: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_1A-41A
1
0
41
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.2 LTE Advanced Carrier Aggregation of Band 1 and Band 42 | Table 7.2.2-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_1-42
1
1920 MHz
–
1980 MHz
5, 10, 15, 20
2110 MHz
–
2170 MHz
5, 10, 15, 20
FDD
42
3400 MHz
–
3600 MHz
5, 10,15, 20
3400 MHz
–
3600 MHz
5, 10, 15, 20
TDD |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.2.1 List of specific combination issues | |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.2.1.1 Channel bandwidths per operating band for CA | Table 7.2.2.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregated bandwidth
[MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_1A-42A
1
Yes
Yes
Yes
Yes
40
0
42
Yes
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.2.1.2 Co-existence studies for CA_1-42 | The harmonic frequencies do not fall into the frequency ranges of both bands as observed in table 7.2.2.1.2-1. Therefore we can conclude that there is no issue on harmonic interference.
Table 7.2.2.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
1
1920
1980
2110
2170
3840
3960
5760
5940
4220
4340
6330
6510
42
3400
3600
3400
3600
6800
7200
10200
10800
6800
7200
10200
10800
Table 7.2.2.1.2-2 shows the second and third order DL harmonics and intermodulation products when two simultaneous DLs are active in Band 1 and Band 42.
Table 7.2.2.1.2-2: Band 1 and Band 42 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
2110
2170
3400
3600
2nd order harmonics frequency range (MHz)
4220
4340
6800
7200
3rd order harmonics frequency range (MHz)
6330
6510
10200
10800
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1230
1490
5510
5770
3rd order IMD products
(2*f1_low – f2_high)
(2*f1_high – f2_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
620
940
4630
5090
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
7620
7940
8910
9370
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
1910
2370
3340
3660
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
2090
2190
3380
3620
It can be seen from table 7.2.2.1.2-1 that some 2nd IMD products caused by BS supporting carrier aggregation of Band 1 and Band 42 fall into the BS receive band of Bands 11 and 21, while some 3rd IMD products fall into the BS receive band of Bands 1, 5, 6, 8, 12, 13, 14, 17, 18 , 19, 20, 22, 23, 25, 26, 27, 28, 30, 33, 34, 36, 37, 39, 40, 42, 43 and 44. Note that the calculation in table 7.2.2.1.2-1 (except the last row) assumes the BS transmits the whole 60 MHz DL frequency of Band 1 and the whole 200 MHz DL frequency of Band 42. However even if the BS only transmits up to 20 MHz DL in Band 1 and up to 20 MHz DL in Band 42 as stated in Table 7.2.2.1.1-1, the 3rd IMD products may still fall into the BS receive band of the Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 20, 22, 26, 27, 28, 42, 43 and 44 as shown in the last row in table 7.2.2.1.2-1.
It should be noted that Bands 12, 13, 14, 17 is not intended for use in the same geographical area as Band 1 and Band 22 is not intended for use in the same geographical area as Band 42. Consequently, the focus here will be on the harmonics and IMD products falling into Bands 5, 6, 8, 18, 19, 20, 26, 27, 28, 42, 43 and 44.
TDD BS does not transmit and receive simultaneously, so the BS’s own band 42 receiver and other synchronized band 42 receivers would not be interfered. With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 5, 6, 8, 18, 19, 20, 26, 27, 28 or unsynchronized 44 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization,
Therefore, it is recommended that Bands 1 and 42 BS transmitters should not share the same antenna with Band 5, 6, 8, 18, 19, 20, 26, 27, 28, unsynchronized 42, unsynchronized 43 or unsynchronized 44 BS receiver, unless the antenna path meets very stringent 3rd order PIM specification so that the PIM will not cause Band 5, 6, 8, 18, 19, 20, 26, 27, 28, unsynchronized 42, unsynchronized 43 or unsynchronized 44 BS receiver desensitization.
7.2.2.1.3 ∆TIB and ∆RIB values
Following relaxations are allowed for the UE which supports inter-band carrier aggregation of Band 1 and Band 42.
Table 7.2.2.1.3-1: IB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_1A-42A
1
0.3
42
[0.8]
Table 7.2.2.1.3-2: RIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB,c [dB]
CA_1A-42A
1
0
42
[0.5] |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.3 LTE Advanced Carrier Aggregation of Band 3 and Band 40 | Table 7.2.3-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-40
3
1710 MHz
–
1785 MHz
5, 10, 15, 20
(Note 1)
1805 MHz
–
1880 MHz
5, 10, 15, 20
FDD
40
2300 MHz
–
2400 MHz
10, 15, 20
(Note 1)
2300 MHz
–
2400 MHz
10, 15, 20
TDD
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.3.1 List of specific combination issues | |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.3.1.1 Channel bandwidths per operating band for CA | Table 7.2.3.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-40A
3
Yes
Yes
Yes
Yes
40
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.3.1.2 Co-existence studies for CA_3-40 | Table 7.2.3.1.2-1 summarizes frequency ranges where harmonics occur due to Band 3 or Band 40 for both UL and DL. It can be seen that the harmonic frequencies of Band 3 and Band 40 in DL are away from the BS receive bands of interest in the UL. For the UE aspect, the UL harmonic frequencies of Band 3 and Band 40 does not locate within the UE receive bands of interest in the DL. Therefore we can conclude that there is no issue on harmonic interference.
Table 7.2.3.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
3
1710
1785
1805
1880
3420
3570
5130
5355
3610
3760
5415
5640
40
2300
2400
2300
2400
4600
4800
6900
7200
4600
4800
6900
7200
The 2nd DL harmonics of Band 3 carriers may fall into the BS receive band of Bands 43.
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 3 and Band 40 DL carriers can be calculated as shown in table 4 below:
Table 7.2.3.1.2-2: Band 3 and Band 40 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
1805
1880
2300
2400
2nd order harmonics frequency range (MHz)
3610
3760
4600
4800
3rd order harmonics frequency range (MHz)
5415
5640
6900
7200
2nd order IMD products
(f2-low – f1-high)
(f2-high – f1-low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
420
595
4105
4280
3rd order IMD products
(2*f1_low –f2_high)
(2*f1_high –f2_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
1210
1460
2720
2995
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
5910
6160
6405
6680
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
1705
1980
2225
2475
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
1785
1900
2280
2420
It can be seen from Table 7.2.3.1.2-2 that the 2nd order IMD products may fall into the BS receive band of Band 31. The 3rd IMD products caused by BS supporting carrier aggregation of Band 3 and Band 40 may fall into the BS receive bands of Band 1, 2, 3, 4, 9, 10, 11, 21, 25, 30, 33, 35, 36, 37, 39, and 40. However, when the impact of maximum bandwidth is considered, the 3rd order IMD products do not fall into the BS receive of Band 1, 3, 4, 9, 10, 33, 36, and 37.
It should be noted that Bands 2, 4, 9, 10, 11, 21, 25, 30, 31, and 35 are not intended for use in the same geographical area as Band 3 and 40. Consequently, the focus here will be on the harmonics and IMD products falling into Bands 39, and 40.
TDD BS does not transmit and receive simultaneously, so the BS’s own band 40 receiver and other synchronized band 40 receivers would not be interfered. With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is noted that the harmonics and IMD interference generated in common signal paths within Band 39, if unsynchronized with band 40 may not be well below the receiver noise floor eliminating the possibility of receiver desensitization. Operating band 39 together with band 3 and 40 CA it is either recommended to synchronize bands 39 and 40 carriers or to have at least one of the three carrier signals using separate feeders.
7.2.3.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 7.2.3.1.3-1, and in table 7.2.3.1.3-2:
Table 7.2.3.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3A-40A
3
FFS
40
FFS
Table 7.2.3.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3A-40A
3
FFS
40
FFS |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.4 LTE Advanced Carrier Aggregation of Band 8 and Band 40 | Table 7.2.4-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_8-40
8
880 MHz
–
915 MHz
5, 10
(Note 1)
925 MHz
–
960 MHz
5, 10
FDD
40
2300 MHz
–
2400 MHz
10, 15, 20
(Note 1)
2300 MHz
–
2400 MHz
10, 15, 20
TDD
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.4.1 List of specific combination issues | |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.4.1.1 Channel bandwidths per operating band for CA | Table 7.2.4.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_8A-40A
8
Yes
Yes
40
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.4.1.2 Co-existence studies for CA_8-40 | Table 7.2.4.1.2-1 summarizes frequency ranges where harmonics occur due to Band 8 or Band 40 for both UL and DL. It can be seen that the harmonic frequencies of Band 8 and Band 40 in DL are away from the BS receive bands of interest in the UL. For the UE aspect, the UL harmonic frequencies of Band 8 and Band 40 does not locate within the UE receive bands of interest in the DL. Therefore we can conclude that there is no issue on harmonic interference.
Table 7.2.4.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
8
880
915
925
960
1760
1830
2640
2745
1850
1920
2775
2880
40
2300
2400
2300
2400
4600
4800
6900
7200
4600
4800
6900
7200
The 2nd DL harmonics of Band 8 carriers may fall into the BS receive band of Bands 2, 25, 33, 35, 37, and 39.
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 8 and Band 40 DL carriers can be calculated as shown in table 7.2.4.1.2-2 below:
Table 7.2.4.1.2-2: Band 8 and Band 40 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
925
960
2300
2400
2nd order harmonics frequency range (MHz)
1850
1920
4600
4800
3rd order harmonics frequency range (MHz)
2775
2880
6900
7200
2nd order IMD products
(f2-low – f1-high)
(f2-high – f1-low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1340
1475
3225
3360
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
380
550
3640
3875
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
4150
4320
5525
5760
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
825
1060
2265
2435
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
905
980
2290
2410
It can be seen from Table 4 that the 2nd order IMD products will fall into the BS receive bands of Band 11 and 21. The 3rd IMD products caused by BS supporting carrier aggregation of Band 8 and Band 40 may fall into the BS receive bands of Band 5, 6, 8, 18, 19, 20, 26, 30, 31, 40, and 43. However, when the impact of maximum bandwidth is considered, the 3rd order IMD products do not fall into the BS receive of Band 5, 18, 19, 20, and 26.
It should be noted that Bands 2, 6, 11, 18, 19, 21, 25, 30, and 31 are not intended for use in the same geographical area as Band 8 and 40. Consequently, the focus here will be on the harmonics and IMD products falling into Bands 8, 33, 35, 37, 39, 40 and 43.
TDD BS does not transmit and receive simultaneously, so the BS’s own band 40 receiver and other synchronized band 40 receivers would not be interfered. With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it recommended that the harmonics and IMD interference generated within the Bands 8, 33, 35, 37, 39, 43, and unsynchronized Band 40 generated in common signal paths is carefully considered. (E.g. by separating band Tx path from the other bands in the feeder system).
7.2.4.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 7.2.4.1.3-1, and in table 7.2.4.1.3-2:
Table 7.2.4.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_8A-40A
8
0.3
40
0.3
Table 7.2.4.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_8A-40A
8
0
40
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.5 LTE Advanced Carrier Aggregation of Band 3 and Band 42 (1 UL) | Table 7.2.5-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-42
3
1710 MHz
–
1785 MHz
5, 10, 15, 20
1805 MHz
–
1880 MHz
5, 10, 15, 20
FDD
42
3400 MHz
–
3600 MHz
5, 10,15, 20
3400 MHz
–
3600 MHz
5, 10, 15, 20
TDD
7.2.5.1 List of specific combination issues
7.2.5.1.1 Channel bandwidths per operating band for CA
Table 7.2.5.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregated bandwidth
[MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-42A
3
Yes
Yes
Yes
Yes
40
0
42
Yes
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.5.1.2 Co-existence studies for CA_3-42 | As shown in Table 7.2.5.1.2-1, second harmonics of Band 3 UL and DL fall into frequency ranges of Band 42 and 43 respectively.
Table 7.2.5.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
3
1710
1785
1805
1880
3420
3570
5130
5355
3610
3760
5415
5640
42
3400
3600
3400
3600
6800
7200
10200
10800
6800
7200
10200
10800
Table 7.2.5.1.2-2 shows the second and third order DL harmonics and intermodulation products when two simultaneous DLs are active in Band 3 and Band 42.
Table 7.2.5.1.2-2: Band 3 and Band 42 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
1805
1880
3400
3600
2nd order harmonics frequency range (MHz)
3610
3760
6800
7200
3rd order harmonics frequency range (MHz)
5415
5640
10200
10800
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1520
1795
5205
5480
3rd order IMD products
(2*f1_low – f2_high)
(2*f1_high – f2_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
10
360
4920
5395
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
7010
7360
8605
9080
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
1605
2080
3325
3675
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
1785
1900
3380
3620
It can be seen from table 7.2.5.1.2-1 that some 2nd IMD products caused by BS supporting carrier aggregation of Band 3 and Band 42 fall into the BS receive band of Bands 3, 4, 9, 10, 24 and 43, while some 3rd IMD products fall into the BS receive band of Bands 1, 2, 3, 4, 9, 10, 22, 23, 24, 25, 33, 34, 35, 36, 37, 39, 42 and 43. Note that the calculation in table 6.5.2.1.2-1 (except the last row) assumes the BS transmits the whole 20 MHz DL frequency of Band 3 and the whole 200 MHz DL frequency of Band 42. However even if the BS only transmits up to 20 MHz DL in Band 3 and up to 20 MHz DL in Band 42 as stated in Table 7.2.5.1.1-1, the 3rd IMD products may still fall into the BS receive band of the Bands 22, 42, 43 as shown in the last row in table 7.2.5.1.2-1.
7.2.5.1.3 ∆TIB and ∆RIB values
Following relaxations are allowed for the UE which supports inter-band carrier aggregation of Band 3 and Band 42. These relaxations are derived from the assumption that harmonic trap filter for Band 3 is not considered. The relaxations based on the implement of harmonic trap filter are FFS.
Table 7.2.5.1.3-1: IB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3A-42A
3
0.3
42
[0.8]
Table 7.2.5.1.3-2: RIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB,c [dB]
CA_3A-42A
3
0
42
[0.5]
7.2.6 LTE Advanced Carrier Aggregation of Band 26 and Band 41
Table 7.2.6-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA operating Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
UE transmit / BS receive
Channel BW MHz
UE receive / BS transmit
Channel BW MHz
FUL_low – FUL_high
FDL_low – FDL_high
CA_26-41
26
814 MHz
–
849 MHz
5,10,15,20
859 MHz
–
894 MHz
5,10,15,20
FDD
41
2496 MHz
–
2690 MHz
5,10,15,20
2496 MHz
–
2690 MHz
5,10,15,20
TDD |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.6.1 List of specific combination issues | <Text will be added.> |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.6.1.1 Channel bandwidths per operating band for CA | Table 7.2.6.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregated bandwidth
[MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_26A-41A
26
Yes
Yes
Yes
35
0
41
Yes
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.6.1.2 Co-existence studies for CA_26-41 | Table 7.2.6.1.2-1gives the intermodulation products for Band 26 + Band 41 CA with 2 DLs. For the IMD analysis the maximum transmission as defined in table 7.2.6.1.1-1 is considered. It can be seen from the table that the 2nd harmonics of BS transmitting in Band 26 may fall into the BS receive band of Bands 3, 4, 9 and 10 and the 3rd harmonics of BS transmitting in Band 26 may fall into the BS receive band of Bands 38 and 41, while the 2nd IMD products caused by BS supporting CA of Band 26 and Band 41 may fall into the BS receive band of Band 3, 4, 9, 10, 22, 24 and 42, and the 3rd IMD products may fall into the BS receive band of Bands 5, 6, 8, 12, 13, 14, 17, 18, 19, 20, 26, 27, 28, 38, 41 and 44. Note that Bands 7, 8, 20 and 38 are not intended for use in the same geographical area as Bands 26 and 41. Therefore, sharing antenna for CA operation between Band 26 and Band 41 is not recommended. In addition, when one deploys CA_26-41 operation in certain region, these co-existence studies should be taken into account because harmonics and IMDs could fall into twenty bands in total.
Table 7.2.6.1.2-1: 2DLs B26 + B41 harmonics and IMD products frequency limits
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
859
894
2496
2690
2nd order harmonics frequency range (MHz)
1718
1788
4992
5380
3rd order harmonics frequency range (MHz)
2577
2682
7488
8070
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
|f2_low + f1_low|
|f2_high + f1_high|
IMD frequency limits (MHz)
1602
1831
3355
3584
3rd order IMD products
|f2_high – 2*f1_low|
|f2_low – 2*f1_high|
|2*f2_low – f1_high|
|2*f2_high – f1_low|
IMD frequency limits (MHz)
708
972
4098
4521
3rd order IMD products
|2*f1_low + f2_low|
|2*f1_high + f2_high|
|2*f2_low + f1_low|
|2*f2_high + f1_high|
IMD frequency limits (MHz)
4214
4478
5851
6274
3rd order IMD products
|f1_low – f2_high + f2_low|
|f1_high + f2_high – f2_low|
|f2_low – f1_high + f1_low|
|f2_high + f1_high – f1_low|
IMD frequency limits (MHz)
665
1088
2461
2725
3rd order IMD products (with maximum channel bandwidth)
|f1_low – max BW f2|
|f1_high + max BW f2|
|f2_low – max BW f1|
|f2_high + max BW f1|
IMD frequency limits (MHz)
839
914
2486
2700 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.6.1.2.1 B26 UE receiver harmonic mixing problem | This CA combination is associated with an undesired property that the B41 UL carrier can align with 3rd order harmonic of B26 DL carrier, as shown in Table 7.2.6.1.2.1-1, which could potentially cause B26 desensitization problem if simultaneous Tx/Rx would be operated, due to the known harmonic mixing problem in typical receiver design.
Table 7.2.6.1.2.1-1 B26 DL and B41 UL harmonic relation
B26 DL
B26 DL x3
B41
Range (MHz)
859 - 894
2577 - 2682
2496 – 2690
Using the commonly adopted L/H band UE reference architecture, as shown in Figure 7.2.6.1.2.1-1, the B41 UL power at B26 LNA input is estimated to be around -33 dBm. Considering that a typical receiver path (excluding off-chip filters) 3rd order harmonic rejection performance would not be better than 20 dB (which includes 9-dB rejection from switching mixer and less than 10 dB from matching selectivity), the desensitization level is expected to be more than 50 dB which can virtually nullify the receiver function. On the other hand, if a transceiver could provide up to 20-dB 3rd order harmonic rejection, to avoid self-desensitization, the isolation from B41 PA output to B26 LNA input shall still be better than 100 dB, which likely cannot be achieved even with additional bandpass filters cascaded before LNA.
Figure 7.2.6.1.2.1-1 UE reference architecture for self-desensitization analysis
Although adding bandpass filters can help reduce desensitization level, it will also introduce additional insertion loss to B26 receiver, yet the MSD is expected to be still higher than 20 dB due to finite PCB isolation. Therefore, it is suggested network to avoid simultaneous Tx/Rx operation when the B41 UL and B26 DL 3rd harmonic alignment condition occurs.
7.2.6.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 7.2.6.1.3-1, and in table 7.2.6.1.3-2:
Table 7.2.6.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_26A-41A
26
0.3
41
0.3
Table 7.2.6.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_26A-41A
26
0
41
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.7 LTE-Advanced Carrier Aggregation of Band 3 and Band 38 (1 UL) | Table 7.2.7-1: Inter-band CA
E-UTRA CA Band
E-UTRA Band
Uplink (UL) operating band
Downlink (DL) operating band
Duplex Mode
BS receive / UE transmit
BS transmit / UE receive
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-38
3
1710 MHz
–
1785 MHz
1805 MHz
–
1880 MHz
FDD
38
2570 MHz
–
2620 MHz
2570 MHz
–
2620 MHz
7.2.7.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.7.1.1 Channel bandwidths per operating band for CA | Table 7.2.7.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-38A
3
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.7.1.2 UE cCo-existence studies for 1UL/2DL | Table 7.2.7.1.2-1 presents the harmonic analysis for UE with single uplink. There are no harmonic frequency products interfering own downlink bands but Band 3 second harmonic will fall into band 42 frequency range.
Table 7.2.7.1.2-1: 1UL B3 + B38 harmonic products
UE UL carriers
f1_low
f1_high
f2_low
f2_high
UL frequency (MHz)
1710
1785
2570
2620
2nd order harmonics frequency range (MHz)
3420 to 3570
5140 to 5240
3rd order harmonics frequency range (MHz)
5130 to 5355
7710 to 7860
Table 7.2.7.1.2-2 shows the second and third order DL harmonics and intermodulation products when two simultaneous DLs are active in Band 3 and Band 38.
Table 7.2.7.1.2-2: Band 3 and Band 38 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
1805
1880
2570
2620
2nd order harmonics frequency range (MHz)
3610
3760
5140
5240
3rd order harmonics frequency range (MHz)
5415
5640
7710
7860
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
690
815
4375
4500
3rd order IMD products
(2*f1_low – f2_high)
(2*f1_high – f2_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
990
1190
3260
3435
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
6180
6380
6945
7120
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
1755
1930
2495
2695
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
1785
1900
2550
2640
It can be seen from table 7.2.7.1.2-2 that 2nd harmonics caused by BS supporting carrier aggregation of Band 3 and Band 38 may fall into the BS receive band of Bands 43, while none 3rd harmonic will fall into the BS receive band of currently defined 3GPP Bands.
It can be seen from table 7.2.7.1.2-2 that 2nd IMD products caused by BS supporting carrier aggregation of Band 3 and Band 38 may fall into the BS receive band of Bands 12-14, 17, 26-28 and 44, while 3rd IMD products may fall into the BS receive band of Bands 2, 7, 22, 25, 35, 38, 39, 41 and 42 (assuming BS transmits up to 20 MHz DL in Band 3 and up to 20 MHz DL in Band 38).
As BS cannot transmit and receive in Band 38 at the same time, the 3rd IMD products problem in receive band of Band 38 is not an issue.
7.2.7.1.3 ∆TIB and ∆RIB values
The reported additional IL (Insertion Loss) values, based on implementation/simulation data, under ETC (Extreme Temperature Conditions) for combining band 3 and band 38, for each of the Tx and Rx paths, are shown in Table 7.2.7 .1.3-1.
Table 7.2.7.1.3-1: IL values for band 3+38 diplexer and quadplexers (under ETC)
E-UTRA bands
Vendor A IL (dB)
Vendor B IL (dB)
3 Tx
0.5
0.6
3 Rx
0.5
0.6
38 Tx/Rx
0.5
0.7
For the reported additional IL values, the corresponding average additional IL values for the Tx and the Rx are shown in Table 7.2.7.1.3-2:
Table 7.2.7.1.3-2: Average Tx and Rx IL for combining band 3 and band 38 (under ETC)
Inter-band CA Configuration
E-UTRA Band
Tx IL [dB]
Rx IL [dB]
3
0.55
0.55
38
0.6
For two simultaneous DLs and one UL the TIB,c and RIB values are shown in Table 7.2.7.1.3-3 and in Table 7.2.7.1.3-4:
Table 7.2.7.1.3-3: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3A-38A
3
[FFS]0.5
38
[FFS]0.5
Table 7.2.7.1.3-4: ΔRIB,c
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3A-38A
3
[FFS]0
38
[FFS]0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.8 LTE Advanced Carrier Aggregation of Band 19 and Band 42 (1 UL) | Table 7.2.8-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_19-42
19
830 MHz
–
845 MHz
5, 10, 15
875 MHz
–
890 MHz
5, 10, 15
FDD
42
3400 MHz
–
3600 MHz
5, 10,15, 20
3400 MHz
–
3600 MHz
5, 10, 15, 20
TDD
7.2.8.1 List of specific combination issues
7.2.8.1.1 Channel bandwidths per operating band for CA
Table 7.2.8.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregated bandwidth
[MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_19A-42A
19
Yes
Yes
Yes
35
0
42
Yes
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.8.1.2 Co-existence studies for CA_19-42 | The harmonic frequencies do not fall into the frequency ranges of both bands as observed in table 7.2.8.1.2-1. Therefore we can conclude that there is no issue on harmonic interference.
Table 7.2.8.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
19
830
845
875
890
1660
1690
2490
2535
1750
1780
2625
2670
42
3400
3600
3400
3600
6800
7200
10200
10800
6800
7200
10200
10800
Table 7.2.8.1.2-1 shows the second and third order DL harmonics and intermodulation products when two simultaneous DLs are active in Band 19 and Band 42.It can be seen from table 7.2.8.1.2-1 that some 2nd harmonic products of Band 19 fall into the BS receive band of Bands 3, 4, 9 and 10, while some 3rd harmonic products fall into the BS receive band of Bands 41.
Table 7.2.8.1.2-2: Band 19 and Band 42 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
875
890
3400
3600
2nd order harmonics frequency range (MHz)
1750
1780
6800
7200
3rd order harmonics frequency range (MHz)
2625
2670
10200
10800
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
|f2_low + f1_low|
|f2_high + f1_high|
IMD frequency limits (MHz)
2510
2725
4275
4490
3rd order IMD products
|2*f1_high – f2_low|
|2*f1_low – f2_high|
|2*f2_low – f1_high|
|2*f2_high – f1_low|
IMD frequency limits (MHz)
1620
1850
5910
6325
3rd order IMD products
|2*f1_low + f2_low|
|2*f1_high + f2_high|
|2*f2_low + f1_low|
|2*f2_high + f1_high|
IMD frequency limits (MHz)
5150
5380
7675
8090
3rd order IMD products
|f1_low – f2_high + f2_low|
|f1_high + f2_high – f2_low|
|f2_low – f1_high + f1_low|
|f2_high + f1_high – f1_low|
IMD frequency limits (MHz)
675
1090
3385
3615
3rd order IMD products (with maximum channel bandwidth)
|f1_low – f2_BWmax|
|f1_high + f2_BWmax|
|f2_low – f1_BWmax|
|f2_high + f1_BWmax|
IMD frequency limits (MHz)
855
910
3385
3615
It can be seen from table 7.2.8.1.2-2 that some 2nd IMD products caused by BS supporting carrier aggregation of Band 19 and Band 42 fall into the BS receive band of Bands 7, 38 and 41, while some 3rd IMD products fall into the BS receive band of Bands 3, 4, 5, 6, 8, 9, 10, 12, 13, 14, 17, 18, 19, 20, 22, 24, 26, 27, 28, 42, 43 and 44. Note that the calculation in table 7.2.8.1.2-2 (except the last row) assumes the BS transmits the whole 15 MHz DL frequency of Band 19 and the whole 200 MHz DL frequency of Band 42. However even if the BS only transmits up to 15 MHz DL in Band 19 and up to 20 MHz DL in Band 42 as stated in Table 7.2.8.1.1-1, the 3rd IMD products may still fall into the BS receive band of the Bands 3, 4, 8, 9, 10, 20, 22, 24, 42, 43 as shown in the last row in table 7.2.8.1.2-2.
It should be noted that Bands 4, 7, 10, 20 and 24 are not intended for use in the same geographical area as Band 19 and Band 22 is not intended for use in the same geographical area as Band 42. Consequently, the focus is on the IMD products falling into Bands 3, 8, 9, 38, 41, 42 and 43, where receiver desensitization might be an issue.
TDD BS does not transmit and receive simultaneously, so the BS’s own band 42 receiver and other synchronized band 42 receivers would not be interfered. Therefore, it is recommended that Bands 19 and 42 BS transmitters should not share the same antenna with Band 3, 8, 9 or unsynchronized Band 38, 41, 43 BS receivers, unless the antenna path meets very stringent 3rd order PIM specification so that the PIM will not cause Band 3, 8, 9 or unsynchronized 38, 41, 43 BS receivers desensitization.
7.2.8.1.3 ∆TIB and ∆RIB values
Following relaxations are allowed for the UE which supports inter-band carrier aggregation of Band 19 and Band 42.
Table 7.2.8.1.3-1: IB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_19A-42A
19
0.3
42
[0.8]
Table 7.2.8.1.3-2: RIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB,c [dB]
CA_19A-42A
19
0
42
[0.5]
Annex A:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2012-10
RAN4#64bis
R4-125796
Rel-12 Inter-band Carrier Aggregation Technical Report skeleton
N/A
0.1.0
2012-11
RAN4#65
R4-126715
The following TPs have been implemented:
R4-125219, “TP for TR ab.cde (inter-band CA) on IMD study of B38 + B39”
R4-125246, “TP for TR36.8XX(Rel-12) : LTE-A Inter-band Carrier Aggregation of Band 1 and Band 8”
R4-125401, “TP for CA band combination B3+19”
Editorial updates by the rapporteur:
• Version number changed
• Removed the word “non-contiguous”
Minor table reference corrections
0.1.0
0.2.0
2013-01
RAN4#66
R4-130546
The following TPs have been implemented:
R4-126098, “TP for TR 36.8xx (Inter-Band CA Rel-12): LTE_CA_B3_B26 Core Requirements“
R4-126251, “TP for TR36.8xx (Release12): LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 28 (1UL)”
R4-126107, “Harmonics and intermodulation products generated by the BS supporting LTE-A CA of Band 2 and Band 4”
R4-126407, “Interband CA B2+B4 UE issues”
Editorial updates by the rapporteur:
• TR number updated to 36.851.
• Version number changed
• Added a table to the Scope clause that lists all Rel-12 inter-band carrier aggregation combinations
• LTE_CA_B38_B39 have been removed from the report
• LTE_CA_B1_B7 text from TS 36.850 have been included in this report
• Added missing reference [4]
• Changed the order of subclause 6.1,1, 6.1.2 and 6.1.3 (UID Order)
• Minor editorial corrections
0.2.0
0.3.0
2013-04
RAN4#66bis
R4-131374
The following TPs have been implemented:
R4-130196, “TP for TR36.851: CA_1A-26A UE/BS RF aspects”
R4-130883, “TP for TR36.851 (Rel-12) : ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 3 and Band 19”
R4-130033, “TP for TR 36.851: Quadplexer insertion loss data for aggregating band 1”
R4-130727, “Additional IL for Band 1 + Band 7 combination”
R4-130885, “TP for TR 36.851 on IMD study of inter-band CA B39 + B41”
R4-130889 : “TP for TR 36.851 on UE issues for B39+B41”
R4-130558, “TP 36.851: modified classes of inter-band combinations (up to 2 UL)”
Editorial updates by the rapporteur:
• Version number changed
• Title modified and aligned with TR 36.850
• Table 1-1 updated with 3 new work items
• Values in Table 6.3.3.1.3-2 replaced by “[FFS]”
Minor editorial corrections
0.3.0
0.4.0
2013-05
RAN4#67
R4-132863
The following TPs have been implemented:
R4-130993, “TP for TR36.851 (Release 12): ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 2 and Band 13 (1UL)”
R4-131197, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products for Band Combination (2 + 12)”
R4-131200, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products for Band Combination (3 + 26)”
R4-131201, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (23 + 29)”
R4-131210, “CA_2A-4A addition on 20 MHz channel bandwidth”
R4-131249, “CA_B2_B12: Core requirement considerations and text proposal”
R4-131292, “TP for 36.851 Rel-12: Additional insertion loss data for CA_2-4”
R4-131925, “TP for TR 36.851 (Inter-Band CA Rel-12): LTE_CA_B8_B26 Operating Bands”
R4-131926, “TP for TR 36.851 (Inter-Band CA Rel-12): LTE_CA_B19_B21 Core Requirements”
R4-131985, “TP for TR 36.851 (Inter-Band CA Rel-12): LTE_CA_B23_B29 Core Requirements”
Editorial updates by the rapporteur:
• Version number changed
• Renumbering of sub-clause numbers 6.1.1-6.1.5
• Minor editorial corrections
0.4.0
0.5.0
2013-08
RAN4#68
R4-133849
The following TPs have been implemented:
R4-132189, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (2 + 13)”
R4-132190, “Corrections on Coexistence Studies of Harmonics and Intermodulation Products for Band Combination (3 + 26)”
R4-131054, “Update on harmonics and intermodulation products generated by the BS supporting LTE-A CA of Band 2 and Band 4”
Editorial updates by the rapporteur:
• Version number changed
• Minor editorial corrections
0.5.0
0.6.0
2013-10
RAN4#68bis
R4-134922
The following TPs have been implemented:
R4-133147, “TP for TR 36.851: Supported E-UTRA bandwidths per CA configuration for inter-band CA”
R4-133371, “TP for TR36.851 (Release 12): ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 2 and Band 5 (1UL)”
R4-133370, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (2 + 5)”
R4-133475, “TP for TR36.851 (Release 12): ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 2 and Band 12 (1UL)”
R4-133644, “TP for TR36.851: CA_1A-26A specifications”
R4-134414, “Revised TP for TR36.851: CA_1A-18A specifications”
R4-134416, “CA_B12_B25: Core requirement considerations and text proposal”
Editorial updates by the rapporteur:
• Version number changed
• Table 1-1 updated with 3 new work items
• Minor editorial corrections
0.6.0
0.7.0
2013-11
RAN4#69
R4-135966
The following TPs have been implemented:
R4-134704, “TP for TR36.851 (Release 12): TIB and RIB values of LTE-A Inter-band Carrier Aggregation of Band 5 and Band 25 (1UL)”
R4-134819, “TP for TR36.851: TIB and RIB values of LTE CA of Band 5&7”
R4-134820, “TP for TR36.851: Co-existence studies for CA_7-28”
R4-134821, “TP for TR36.851: TIB and RIB values of LTE CA of Band 7&28”
R4-135699,” TP for TR36.851: Co-existence studies for CA5-7”
R4-134706, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (5 + 25)”
R4-134597, “Text proposal for LTE-A inter-band CA B12+B25 (2DL/1UL)”
R4-134667, “TP for TR36.851 (Rel-12) : IMD and Harmonics Issues on LTE-A Inter-band Carrier Aggregation of Band 1 and Band 11”
R4-134668, “TP for TR36.851 (Rel-12) : IMD and Harmonics Issues on R4-134668, LTE-A Inter-band Carrier Aggregation of Band 8 and Band 11”
Editorial updates by the rapporteur:
• Version number changed
• Table 1-1 updated with 4 new work items
Minor editorial corrections
0.7.0
0.8.0
2014-02
RAN4#70
R4-140843
The following TPs have been implemented:
R4-137031, “TP on UE requirement structure for TDD inter-band CA_B39_B41”
R4-136063, “TP for TR36.851 (Release 12): ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 5 and Band 30 (1UL)”
R4-134714, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (5 + 30))”
R4-134709, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (2 + 30)”
R4-136066, “TP for TR36.851 (Release 12): ∆TIB and ∆RIB values of LTE-A Inter-band Carrier Aggregation of Band 29 and Band 30 (1UL)”
R4-134716, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (29 + 30)”
R4-134713, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (4 + 30)”
Editorial updates by the rapporteur:
Version number changed
Added headings to sub-clause 6.1.16 and 6.1.18
Clause numbering in 6.1.2 corrected
Minor editorial corrections
0.8.0
0.9.0
2014-03
RAN4#70-Bis
R4-141475
The following TPs have been implemented:
R4-140018, “R4-69AH-0077: TP to 36.851 on 1+20 Harmonic and IMD analysis (CA_1-3-20 leading and CA_1-7-20)”
R4-141045, “R4-69AH-0100: TP to 36.851 on 7+8 Harmonic and IMD analysis (CA_7-8-20)”
R4-140079, “TP for TR36.851: Operating Bands for LTE_CA_B8_B27”
R4-140450, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (1 + 28)”
R4-140475, “Text Proposal on Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (12 + 30)”
R4-140476, “TP for TR36.851 (Release 12): TIB and RIB values of LTE-A Inter-band Carrier Aggregation of Band 12 and Band 30 (1UL)”
R4-140585, “TP for TR36.851 (Rel-12) : Insertion loss value proposal of CA 1+11”
R4-140587, “TP for TR36.851 (Rel-12) : Insertion loss value proposal of CA 8+11”
R4-140913, “TP 36.851 v0.9.0: additional bandwidth combination set for CA_2A-4A”
R4-140970, “TP for TR 36.851: DeltaTIB and DeltaRIB values for LTE-A Inter-band Carrier Aggregation of Band 4 and Band 27 (1UL)”
R4-141181, “TP for TR 36.851: B1+B5 Harmonic and IMD analysis for 3DLs CA_1A_5A_7A band combination UE”
R4-141183, “Text Proposal on Coexistence Studies of Harmonics and intermodulation products analysis supporting LTE-A CA of Band 1 and Band 3”
R4-141185, “TP for TR 36.851: Harmonics and Intermod analysis for LTE-A Inter-band Carrier Aggregation of Band 4 and Band 27 (1UL)”
R4-141232, “TP for TR 36.851: Rib values for CA_39A-41A”
R4-141256, “TP for TR36.851: LTE_CA_B3_B27”
Editorial updates by the rapporteur:
Version number changed
Updated scope table with new band combinations
Split the scope table to separate 3 band CA combinations
Added headings for missing sub-clauses in TPs
Clause numbering corrected
Minor editorial corrections
0.9.0
0.10.0
2014-05
RAN4#71
R4- 143471
The following TPs have been implemented:
R4-141322, "TP for TR 36.851: Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 20"
R4-141324, "TP for TR 36.851: Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 20"
R4-141339, "TP for TR36.851: Operating bands and CA configurations on LTE Advanced Carrier Aggregation of Band Combination (1+42)"
R4-141403, "TP for TR36.851: Editorial corrections for CA 1+8"
R4-141475, "TR 36.851 V0.10.0: Rel-12 Inter-band Carrier Aggregation"
R4-141525, "TP for TR 36.851: Correction of Harmonics and Intermod analysis for LTE-A Inter-band Carrier Aggregation of Band 4 and Band 27 (1UL)"
R4-141755, "TP for TR 36.851: Coexistence Studies of Harmonics and intermodulation products analysis supporting LTE-A CA of Band 8 and Band 27"
R4-141879, "TP for TR 36.851: Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (1 + 18)"
R4-141902, "TP for TR 36.851: Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (18 + 28)"
R4-141943, "TP for TR 36.851: Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (4 + 12)"
R4-142018, "TP for TR 36.851: Skeleton for TDD-FDD CA"
R4-142203, "Bulk Corrections for Harmonics and Intermod anlaysis in TR 36.851"
R4-142455, "TP for TR 36.851: Channel bandwidth for CA B41+B42"
R4-142456, "TP for TR 36.851: B41+B42 Harmonic and IMD analysis"
R4-142457, "TP to TR 36.851: Harmonics/IMD analysis and channel bandwidths for CA_7A-22A"
R4-142482, "Text Proposal for TR 36.851: BS harmonics and intermodulation analysis for TDD-FDD CA B1+B41 combination (CA_1A-41A)"
R4-142483, "TP for TR36.851: Co-existence study on LTE Advanced Carrier Aggregation of Band Combination (1+42)"
R4-142484, "TP for TR36.851: Harmonics and intermodulation product analysis supporting LTE-Advanced CA of Band 3 and Band 40"
R4-142485, "TP for TR36.851: Harmonics and intermodulation product analysis supporting LTE-Advanced CA of Band 8 and Band 40"
R4-142548, "TP for TR 36.851: LTE_CA_B5_B13 introduction"
R4-142549, "TP for TR36.851: TIB and RIB proposal for CA 1+11"
R4-142553, "Simulation results on UE for Band18+Band28 CA"
Editorial updates by the rapporteur:
Version number changed
Updated scope table with new band combinations
Added another table to capture TDD FDD band combinations
Added headings for missing sub-clauses in TPs
Clause numbering corrected
Other minor editorial corrections
0.10.0
0.11.0
2014-08
RAN4#72
R4-144851
The following TPs have been implemented:
R4-143148, "TP for TR36.851: Insertion Loss for TDD-FDD CA of Band 8 and Band 40" (KT).
Editorial updates by the rapporteur:
Version number changed
Other minor editorial corrections
0.11.0
0.12.0
2014-10
RAN4#72-BIS
R4-146316
The following TPs have been implemented:
R4-144239, "TP 36.851: additional bandwidth combination set for CA_2A-4A" (T-Mobile USA).
R4-144283, "TP for TR36.851 (Rel-12): Updated TIB and RIB proposal for CA 8+11" (SoftBank Mobile).
R4-144648, "TP for TR36.851: UE RF requirements for CA_B26-B41" (KDDI).
R4-144978, "TP for 36.851: UE requirements for fallback modes of 3DL combinations with Band 30" (Ericsson).
R4-145007, "TP for TR 37.851: Fallback modes for 3DL CA Band 1+3+20" (Ericsson).
R4-145089, "TP 36.851: additional bandwidth combination set for CA_4A-12A" (T-Mobile USA).
R4-145454, "TP for TR36.851: UE relaxation requirements for CA_B18-B28" (KDDI).
R4-145455, "TP for TR36.851: TIB and RIB for CA_B18-B28" (KDDI).
R4-145496, "TP for TR36.851: On Coexistence Studies of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (26 + 41)" (KDDI).
R4-145565, "TP for 36.851: Delta Tib and Delta Rib for inter-band CA B41+B42" (Huawei).
R4-145058, "TP for the addition of 3MHz bandwidth for Band 12, in the B2+B12 CA combination" (U.S. Cellular).
RP-141245, “TP for 36.851: B1+B3 CA remaining specs” (China Unicom)
RP-141638, “TP for TR 36.851: Band 1 and Band 7 UE Tx and Rx relaxations” (LGUplus, Qualcomm Incorporated, LG Electronics, Nokia Corporation, Intel Corporation, MediaTek)
Editorial updates by the rapporteur:
Version number changed
Updated scope table with new band combinations
Added headings for missing sub-clauses in TPs
Clause numbering corrected
Updated Annex
Other minor editorial corrections
0.12.0
0.13.0
2014-11
RAN4#73
R4-147550
The following TPs have been implemented:
R4-145707, "TP for TR 36.851: TDD-FDD CA for B1+B41" (China Telecom).
R4-145821, "TP for TR36.851: DTIB and DRIB for CA_B1_B28" (KDDI).
R4-145822, "TP for TR36.851: UE RF requirements for CA_B26_B41" (KDDI).
R4-145913, "TP for TR36.851 on LTE Advanced Carrier Aggregation of Band Combination (1+42)" (NTT DOCOMO, INC.).
R4-146162, "TP for TR 36.851: Corrections of Harmonics and Intermodulation Products caused by LTE Advanced Carrier Aggregation of Band Combination (5 + 13)" (Alcatel-Lucent, Intel Corporation, Verizon).
R4-146173, "TP for TR 36.851: Updates of Harmonics and Intermodulation Products caused by LTE Advanc Carrier Aggregation of Band Combination (26 + 41)" (Alcatel-Lucent, KDDI).
R4-146383, "TP to 36.851: additional bandwidth combination set for CA_2A-5A" (Ericsson).
R4-146734, "TP for TR36.851: UE RF requirements for CA_3A-38A" (Nokia Corporation).
R4-146735, "TP for Rel-13 2DL TR 36.8xx: LTE_CA_B5_B13" (Intel Corporation, Verizon ).
R4-146766, "TP for TR36.851 on LTE Advanced Carrier Aggregation of Band Combination (3+42)" (NTT DOCOMO, INC.).
Editorial updates by the rapporteur:
Version number changed
Updated scope table with new band combinations
Added headings for missing sub-clauses in TPs
Clause numbering corrected
Updated Annex
Other minor editorial corrections
0.13.0
0.14.0
2014-12
RAN#66
RP-142015
The following TPs have been implemented:
R4-146933, "TP to TR36.851 on BS harmonics and IMD analysis for CA of Band 3 and Band 38" (Nokia Networks).
R4-147578, "TP for Rel-12 2DL TR 36.851: TDD-FDD CA for B1+B41 combination (CA_1A-41A)" (Ericsson, KDDI).
R4-147676, "TP for TR36.851: UE Low-band receiver harmonic mixing problem for CA_B26_B41" (MediaTek Inc.).
R4-148005, "TP for TR 36.851: coexistence studies and UE requirements for CA_7-12" (Ericsson).
R4-148010, "TP for TR36.851 LTE Advanced Carrier Aggregation of Band Combination (19+42)" (NTT DOCOMO, INC.).
R4-148015, "TP for TR36.851: MSD proposal on CA_B1_B28" (KDDI).
R4-148101, "Band 7+8 reference sensitivity and TP to 36.851" (Vodafone).
Editorial updates by the rapporteur:
Version number changed
Updated scope table with new band combinations
Added headings for missing sub-clauses in TPs
Clause numbering corrected
Updated Annex
Other minor editorial corrections
0.14.0
1.0.0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 7.2.7.1.2 Co-existence studies for 1UL/2DL | Table 7.2.7.1.2-1 presents the harmonic analysis for UE with single uplink. There are no harmonic frequency products interfering own downlink bands but Band 3 second harmonic will fall into band 42 frequency range.
Table 7.2.7.1.2-1: 1UL B3 + B38 harmonic products
UE UL carriers
f1_low
f1_high
f2_low
f2_high
UL frequency (MHz)
1710
1785
2570
2620
2nd order harmonics frequency range (MHz)
3420 to 3570
5140 to 5240
3rd order harmonics frequency range (MHz)
5130 to 5355
7710 to 7860
Table 7.2.7.1.2-2 shows the second and third order DL harmonics and intermodulation products when two simultaneous DLs are active in Band 3 and Band 38.
Table 7.2.7.1.2-2: Band 3 and Band 38 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
1805
1880
2570
2620
2nd order harmonics frequency range (MHz)
3610
3760
5140
5240
3rd order harmonics frequency range (MHz)
5415
5640
7710
7860
2nd order IMD products
|f2_low – f1_high|
|f2_high – f1_low|
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
690
815
4375
4500
3rd order IMD products
(2*f1_low – f2_high)
(2*f1_high – f2_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
990
1190
3260
3435
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
6180
6380
6945
7120
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
1755
1930
2495
2695
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
1785
1900
2550
2640
It can be seen from table 7.2.7.1.2-2 that 2nd harmonics caused by BS supporting carrier aggregation of Band 3 and Band 38 may fall into the BS receive band of Bands 43, while none 3rd harmonic will fall into the BS receive band of currently defined 3GPP Bands.
It can be seen from table 7.2.7.1.2-2 that 2nd IMD products caused by BS supporting carrier aggregation of Band 3 and Band 38 may fall into the BS receive band of Bands 12-14, 17, 26-28 and 44, while 3rd IMD products may fall into the BS receive band of Bands 2, 7, 22, 25, 35, 38, 39, 41 and 42 (assuming BS transmits up to 20 MHz DL in Band 3 and up to 20 MHz DL in Band 38).
As BS cannot transmit and receive in Band 38 at the same time, the 3rd IMD products problem in receive band of Band 38 is not an issue.
7.2.7.1.3 ∆TIB and ∆RIB values
The reported additional IL (Insertion Loss) values, based on implementation/simulation data, under ETC (Extreme Temperature Conditions) for combining band 3 and band 38, for each of the Tx and Rx paths, are shown in Table 7.2.7 .1.3-1.
Table 7.2.7.1.3-1: IL values for band 3+38 diplexer and quadplexers (under ETC)
E-UTRA bands
Vendor A IL (dB)
Vendor B IL (dB)
3 Tx
0.5
0.6
3 Rx
0.5
0.6
38 Tx/Rx
0.5
0.7
For the reported additional IL values, the corresponding average additional IL values for the Tx and the Rx are shown in Table 7.2.7.1.3-2:
Table 7.2.7.1.3-2: Average Tx and Rx IL for combining band 3 and band 38 (under ETC)
Inter-band CA Configuration
E-UTRA Band
Tx IL [dB]
Rx IL [dB]
3
0.55
0.55
38
0.6
For two simultaneous DLs and one UL the TIB,c and RIB values are shown in Table 7.2.7.1.3-3 and in Table 7.2.7.1.3-4:
Table 7.2.7.1.3-3: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3A-38A
3
0.5
38
0.5
Table 7.2.7.1.3-4: ΔRIB,c
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3A-38A
3
0
38
0 |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 1 Scope | The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] http://www.3gpp.org/ftp/Information/WORK_PLAN/
[2] http://www.3gpp.org/ftp/Information/WI_Sheet/ |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3 Feature: Operations, Administration, Maintenance & Provisioning (OAM8) UID_340063 | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3.1 BB: Network Infrastructure Management | Technical Specification Group Services and System Aspects TSGS#36(07)0296
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID Telecom Management Methodology - Unique_ID 35051
Document for: Approval
Agenda Item: 10.4x (OAM8) - OAM&P Rel 8
3GPP TSG-SA5 (Telecom Management) S5-070672
Meeting #52, Xián, CHINA, 02 - 06 April 2007 revision of S5-050287
Work Item Description
Title:
Telecom Management Methodology UID_35051
Acronym: OAM8
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P 8 (Operations, Administration, Maintenance & Provisioning), Feature: OAM8
3 Justification
Telecom Management capabilities and functions evolve continuously because for example, new functions are added to manage new kind of nodes introduced into the network, more efficient functions and capabilities are introduced, new technologies are added, old technologies are not longer used. There is a constant need to enhance and further develop the methodology for the evolved Telecom Management area.
To spread the way of working for Telecom Management, the methodology developed by 3GPP is promoted outside 3GPP. The use of the same or similar methodology to develop management capabilities for the various networks would facilitate the integration of these systems and networks where telecom is a part of. Therefore there are some dependencies on external bodies, e.g. 3GPP2, ITU-T and ETSI that are using a methodology that is common to 3GPP. The needs from these external bodies have to be taken into account.
Requirements methodology is developed jointly with ITU-T and ETSI. That work needs to be finished.
IS methodology is being developed jointly with ITU-T and ETSI. Also this work needs to be finished.
SS methodology needs to be developed jointly with ITU-T and ETSI.
The methodology for XML technology was started in Rel-7 and needs to be completed.
In Rel-7 the SOAP technology was introduced. The methodology for how to use it needs to be developed, so that the same problems do not occur as for XML.
It is still not clear how vendor specific extensions shall be done for XML.
4 Objective
To complete the joint methodology for Requirements and IS together with ITU-T and ETSI.
To develop a joint methodology for SS together with ITU-T and ETSI.
To finish the started methodology for XML.
To develop a methodology for SOAP.
To develop a methodology for vendor specific extensions for XML.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None
9 Impacts
Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
Don't know
X |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 10 Expected Output and Time scale (to be updated at each plenary) | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.275
MMTel Charging
SA5
SA#41 Sep 2008
SA#43 Mar 2009
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.298
Add MMTel ASN.1 structure
Update Section 5.2.3 subsystem level CDR definitions with supplementary service data type
SA#43 Mar 2009
32.299
Add MMTel AVPs and descriptions
Define supplementary service AVPs, AVP codes, value types and flag rules. Provide detailed description for supplementary service AVPs
SA#43 Mar 2009
11 Work item rapporteur(s)
GARDELLA, Maryse (Alcatel-Lucent)
12 Work item leadership
SA5
13 Supporting Companies
Alcatel-Lucent, Verizon Wireless, Nortel, Motorola
14 Classification of the WI (if known)
Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
X
Work Task (go to 14c) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14c The WI is a Work Task: parent Building Block | UID_390010 EPC Data Definitions |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
No
X
X
X
X
X
Don't know |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 1 3GPP Work Area | Radio Access
X
Core Network
Services
2 Linked work items
OAM&P 8 (Operations, Administration, Maintenance & Provisioning), Feature: OAM8
3 Justification
Circuit is a logic link between two exchange network nodes which bear the user data such as voice, e.g. 64K slot of one 2M E1. Traffic route represents the route via which bearer flow to a specific destination.
To learn the detailed circuit connection relationship between network nodes and traffic route configuration status of the CN CS, bearer transport network related NRM need to be defined, such as circuit, traffic route, etc.
4 Objective
Define Bearer Transport Network (BTN) related NRM applicable to CN CS of UMTS.
Add BTN relative NRM definition of the CN CS to 32.63x Configuration Management (CM); Core network resources IRP.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14a The WI is a Feature: List of building blocks under this feature | (list of Work Items identified as building blocks) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14b The WI is a Building Block: parent Feature | UID_370059 IMS Multimedia Telephony and Supplementary Services (Acronym: IMSTSS) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 1 3GPP Work Area * | X
Radio Access
X
Core Network
Services |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2 Classification of WI and linked work items | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2.0 Primary classification * | This work item is a … *
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
X
Work Task (go to 2.4) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2.1 Study Item | Related Work Item(s) (if any]
Unique ID
Title
Nature of relationship
Go to §3. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2.2 Feature | Related Study Item or Feature (if any) *
Unique ID
Title
Nature of relationship
Go to §3. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 2.3 Building Block | Parent Feature (or Study Item)
Unique ID
Title
TS
340064
OAM Network Infrastructure Management (OAM8-NIM)
This work item is … *
Stage 1 (go to 2.3.1)
Stage 2 (go to 2.3.2)
Stage 3 (go to 2.3.3)
Test spec (go to 2.3.4)
Other (go to 2.3.5)
2.3.1 Stage 1
Source of external requirements (if any) *
Organization
Document
Remarks
Go to §3.
2.3.2 Stage 2 *
Corresponding stage 1 work item
Unique ID
Title
TS
Other source of stage 1 information
TS or CR(s)
Clause
Remarks
If no identified source of stage 1 information, justify: *
Go to §3.
2.3.3 Stage 3 *
Corresponding stage 2 work item (if any)
Unique ID
Title
TS
Else, corresponding stage 1 work item
Unique ID
Title
TS
Other justification
TS or CR(s)
Or external document
Clause
Remarks
If no identified source of stage 2 information, justify: *
Go to §3.
2.3.4 Test spec *
Related Work Item(s)
Unique ID
Title
TS
Go to §3.
2.3.5 Other *
Related Work Item(s)
Unique ID
Title
Nature of relationship
TS / TR
Go to §3.
2.4 Work task *
Parent Building Block
Unique ID
Title
TS |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3 Justification * | The XML definitions for the IRPs below were not specified in Rel-8. These definitions are required for implementation of a Rel-8 Notification Log IRP. It is not possible to log the notifications generated by Rel-8 implementations of these IRPs. Furthermore, these XML definitions are needed in the specification of SOAP Solution Sets for these IRPs. Without these XML definitions it will not be possible to complete the Rel-9 WI “IRP SOAP Solution Sets continuation from Rel-8 (OAM9) (UID_440065)”. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 4 Objective * | The objective is to create the missing specifications listed below. These specifications are needed to support a Rel-8 Notification Log implementation. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 5 Service Aspects | None. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 6 MMI-Aspects | None. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 7 Charging Aspects | None. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 8 Security Aspects | None. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 9 Impacts * | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
X
No
X
X
X
Don't know |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 10 Expected Output and Time scale * | New specifications *
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TS 32.125
“Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); ”
SA5
SA#46
SA#46
TS 32.355
“Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP)”
SA5
SA#46
SA#46
TS 32.505
“Telecommunication management; Self-Configuration of Network Elements Integration Reference Point (IRP)”
SA5
SA#46
SA#46
TS 32.535
“Telecommunication management; Software management Integration Reference Point (IRP)”
SA5
SA#46
SA#46
Note that this is related also to the Rel-9 WID “Management of software entities residing in Network Elements UID_420031” which will need 32.535 to create 32.537 as proposed in that WID.
Affected existing specifications *
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
TS 32.150
Add XML file format definition into IRP concepts (today it only includes RS, IS, SS), as agreed in S5-093318
Telecommunication management; Integration Reference Point (IRP) Concept and definitions
TS 32.153
Add XML template and XML definition and usage guidelines, as agreed in S5-093318
Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines
TS 32.335
Add missing XML namespaces to tables and import in schema.
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); eXtensible Markup Language (XML) solution definitions
11 Work item rapporteur(s) *
Shuqiang Huang (ZTE), [email protected]
Work item leadership *
SA5
13 Supporting Individual Members *
Supporting IM name
Ericsson
Nokia Siemens Networks
Huawei
ZTE |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3.2 BB: Performance Management | Technical Specification Group Services and System Aspects TSGS#36(07)0301
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID IP bearer network Performance measurement definitions - Unique_ID 35061
Document for: Approval
Agenda Item: 10.4x (OAM8) - OAM&P Rel 8
3GPP TSG-SA5 (Telecom Management) S5-071047
Meeting SA5#53, 07 - 11 May 2007, Sophia Antipolis, FRANCE revision of S5-050297
Work Item Description
Title:
IP bearer network Performance measurement definition UID_35061
Acronym: OAM8
Is this Work Item a "Study Item"? (Yes / No): No.
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P 8 (Operations, Administration, Maintenance & Provisioning), Feature: OAM8
3 Justification
Standardising performance measurements can bring a unified criterion for operators to evaluate the performance of networks provided by different vendors. With the evolution of RAN and All-IP Networks, it is very important to measure the performance of IP network between any two among RNCs, SGSNs, GGSNs, MGWs and MSC Servers. At present, 3GPP does not have performance measurements for it . Hence, it is necessary for us to look into ways to define these measurements.
This WT proposes to widen the scope of TS 32.32x TestIRP to include 3GPP support of IP network performance measurements either by reference to existing measurements from other standards bodies or by initiating an effort in those standards bodies to include the counters that we would identify in this WT. IP performance mainly deals with the time delay, jitter, packet loss etc between any two NEs.
Some of the IP network performance measurements methods have been defined in other standard bodies, such as IETF, so their work can be used as reference.
4 Objective
Include support of Performance Measurement Counters for IP bearer network in TS 32.32x Test IRP either by reference to existing measurements from other standards bodies (ITU-T, IETF) or by initiating an effort in those standards bodies to include the counters that we would identify in this WT.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3.3 BB: Trace Management | This BB has been created in the 3GPP Work Plan in order to host the CT1 Work Task
UID_11067 Service Level Tracing in IMS (OAM8-Trace) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3.4 OAM&P Studies (OAM8-Study) UID_340067 | Technical Specification Group Services and System Aspects TSGS#36(07)0307
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID Study of Element Operations Systems Function (EOSF) definition - Unique_ID 35065
Document for: Approval
Agenda Item: 11.28 (OAM-Study) - OAM&P Studies
3GPP TSG-SA5 (Telecom Management) S5-071048
Meeting SA5#53, 7-11 May 2007, Sophia Antipolis, France
Work Item Description
Title:
Study of Element Operations Systems Function (EOSF) definition UID_35065
Acronym: OAM-Study
Is this Work Item a "Study Item"? (Yes / No): Yes
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P Rel-8 Studies (OAM-Study), UID_340067
3 Justification
In the Logical Layered Architecture (LLA) of TMN, Network OSFs (N-OSF) are concerned with the management function on network level, and Element OSFs (E-OSF) with the management function on network element level. These two logical layers respectively play the role of network management function.
The Element Management System developed by vendors may mainly cover network management functions described in E-OSF and or N-OSF.
3GPP TS 32.101 also state that the Element Manager (EM) has two aspects of function, element management and sub-network management. However, 3GPP 32.xxx series does not provide a clear definition for Element OSF which can help operators and vendors clarify what are required and can be used as a guide when they deploy network.
It is necessary to state that EM provided by vendor is an entity, which implement E-OSF logical functions and may or may not implement N-OSF functions and even more. The Network Management System (NMS) may or may not direct access to NE and implement part of E-OSF. This scenario (i.e. whether NMS implement or not any E-OSF and whether EM implement any N-OSF or not ) is outside the 3GPP standardization scope. The mapping rule between physical entities (e.g. EMS, NMS) and logical function entities (e.g. E-OSF and N-OSF) is outside of this WID scope.
The definition of E-OSF specification has to be based on the network operating and maintaining experience and consider the potential application environment of UMTS network. Up to now the existing specification from 3GPP may not enough as a guideline for the products. More E-OSF detail function definition is necessary to be defined in a TR as a reference for operator and vendor.
4 Objective
The intention of this TR is to identify and define what will be needed in the E-OSFs. The intention of this TR is not to define new requirements for the eventual standardization of new Interface IRP and/or NRM IRP and/or System Context.
This WI proposes to define the E-OSFs including the following main aspects.
-Define functional scope of Element OSF (E-OSF)
-Define functional requirement of Elements OSF (E-OSF)
-Define the usage (use case) of the result of this WID.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 4 Feature: Charging Management small Enhancements (CH8) UID_350016 | Technical Specification Group Services and System Aspects TSGS#35(07)0077
Meeting #35, 12 - 15 March 2007, Lemesos, Cyprus
Source: SA5 (Telecom Management)
Title: R8 WID Online charging correlation
Document for: Approval
Agenda Item: 13 Proposed New WIDs (not part of an existing feature)
3GPP TSG-SA5 (Telecom Management) S5-070315
Meeting SA5#51, 22 - 26 Jan 2007, Seville, ES
Work Item Description
Title
Online charging correlation UID_350038
Acronym: CH8
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
Charging Management small Enhancements (CH8) (Unique_ID 350016)
3 Justification
3GPP Technical Specification 32.240 (Charging architecture and principles) provides the possibility to aggregate and correlate charging information produced by different domains (e.g. IMS, PS) and different sources (e.g. x-CSCF, GGSN, etc.). This intra-domain and inter-domain correlation is specified for the offline charging method. However, such functionality is not offered for online charging. The Online Charging System (OCS) which performs event/session based charging, credit control and rating features collects charging events at the bearer level, the IMS level and at the service level. On the one hand, by controlling the network and application usage separately, the OCS is not able to apply special charging handling to one charging level against the other (e.g. zero rate bearer usage when an IMS session is active). On the other hand, when multiple services are rendered simultaneously to the subscriber, the OCS is not able to perform service bundling of these services.
As such correlation functionality needs to be defined for online charging.
4 Objective
As per the above justification, it is required to update the charging specifications as follows:
• Update the OCS internal architecture to combine the EBCF (Event Based Charging Function) and SBCF (Session Based charging Function) into a single OCF (Online Charging Function) that performs both event and session based charging. This allows to optimize the handling of correlation.
• Introduce a correlation function within the OCS as part of the above OCF which would be implement the service logic for correlation
• Introduce a context monitoring function that defines a context related to the multiple sessions/services activated by a user simultaneously
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
This is a charging work item.
8 Security Aspects
None |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14c The WI is a Work Task: parent | Feature UID_370059 IMS Multimedia Telephony and Supplementary Services (Acronym: IMSTSS)
BB: UID_370062 IMS Multimedia Telephony Service (Acronym: IMS-MMTel) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 11 Work item rapporteurs | Gavin WONG, Vodafone (gavin.wong (at) vodafone.com) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 12 Work item leadership | SA5 |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 13 Supporting Companies | Vodafone, Alcatel-Lucent, Ericsson, Huawei, Nokia Siemens Networks, Orange |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14 Classification of the WI (if known) | Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
X
Work Task (go to 14c) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 5 Feature: 3G Long Term Evolution - Evolved Packet System RAN part UID_20068 | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 5.1 BB: E-UTRAN Data Definitions UID_390001 | Technical Specification Group Services and System Aspects TSGS#37(07)0617
Meeting #37, 17 - 20 September 2007, Riga, LATVIA
Source: SA5 (Telecom Management)
Title: WID on Subscriber and Equipment Trace for eUTRAN and EPC (OAM8) - OAM&P Rel 8
Document for: Approval
Agenda Item: 10.22 (OAM8) - OAM&P Rel 8
3GPP TSG-SA5 (Telecom Management) S5-071346
Meeting SA5#54, 25 - 29 June 2007, Orlando, FL USA
Work Item Description
Title
Subscriber and Equipment Trace for eUTRAN and EPC UID_370001
Acronym: E-UTRAN-OAM
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
• LTE
• SAE
3 Justification
The use cases for the existing Subscriber and Equipment trace are valid also for eUTRAN and EPC. Therefore shall the existing Subscriber and Equipment Trace function and the Trace IRP be upgraded to include eUTRAN and EPC.
4 Objective
Include the eUTRAN and EPC nodes and interfaces in the Subscriber and Equipment Trace function and the Trace IRP.
Also the new requirements from TR 32.816 (Study on Management of LTE and SAE) are to be included.
• Work is needed in RAN3, CT1, CT4
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
Not known |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 6 Feature: 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects) UID_320005 | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 6.1 BB: EPC Data Definitions UID_390010 | Technical Specification Group Services and System Aspects TSGS#38(07)0737
Meeting #38, 03 - 06 December 2007, Cancun, MEXICO
Source: SA5 (Telecom Management)
Title: New WID on EPC NRM IRP
Document for: Approval
Agenda Item: 10.21 (SAES) - 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects)
3GPP TSG-SA5 (Telecom Management) S5-071964
Meeting SA5#56, 22 - 26 Oct 2007, Guangzhou, CHINA
Work Item Description
Title
EPC Network Resource Model (NRM) Integration Reference Point (IRP) UID_380037
Acronym: EPC-OAM
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
UID_320005 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects)
UID_340036 Study of Management for LTE and SAE (draft TR 32.816) under OAM8-Studies
UID_340063 OAM&P 8 (Operations, Administration, Maintenance & Provisioning) - OAM8
3 Justification
The Evolved Packet Core (EPC) is defined by 3GPP with different Network Elements from the UTMS Core Network.
The Network Resource Model (NRM) of the UTMS Core Network is not applicable to EPC.
The Evolved Packet Core (EPC) system needs to be managed. 3GPP network management paradigm necessitates the standardization of the representations of various managed resources. The standardization of the EPC system managed resources is captured in the so-called EPC Network Resource Model (NRM).
The EPC architecture and capabilities evolve from those defined for UTMS Core Network. The management of the EPC system should also evolve from that for managing the UTMS Core Network. In particular, the NRM for EPC should align and resemble those specified for the Core managed network resources.
The alignment of EPC NRM with Core NRM will have the following benefits:
• The system architecture of EPC evolves from Core network and the existing Core network NRM is proven in operation. Therefore, the alignment will result in a specification that has a higher chance of being bug free when compared to a “brand new” designed specification.
• It will minimise both the standardisation and product development efforts and maintenance efforts (i.e. the cost and time for development including testing and reduction of training cost when the management paradigms for EPC and Core network remained similar);
• It will shorten the time to market for EPC systems;
• It will facilitate a seamless coexistence with Core network management systems.
4 Objective
Define EPC NRM using the same principles as for the UMTS Core network NRM. The definition will be captured in a new NRM IRP called EPC NRM IRP. The defined NRM should have identical characteristics as those defined for other NRMs such as UMTS Core network NRM.
For example: the DN of its instances uses the same name convention as all instances whose IOCs are defined in various NRM IRPs.
For example: Its IOCs will integrate, in identical manner as other NRM such as those defined in UMTS/GSM NRM IRP, with the IOCs defined in Generic NRM IRP.
For example: operations and notifications defined in various Interface IRPs that work with existing instances of various NRM IRPs must work, without change, with the new instances of EPC.
Similar to existing 3GPP NRM IRPs such as UTRAN and Core Network NRM IRP, the proposed new EPC NRM IRP focuses only on the representation of the network resources in question.
This NRM IRP does not deal with the applications or usage of the IOCs.
The objective of this work item is to define the NRM for EPC, e.g.: MME, HSS, Serving GW, PDN GW
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
Not known. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 6.2 BB: EPC Charging | Technical Specification Group Services and System Aspects TSGS#38(07)0736
Meeting #38, 03 - 06 December 2007, Cancun, MEXICO
Source: SA5 (Telecom Management)
Title: New WID on EPC Charging
Document for: Approval
Agenda Item: 10.21 (SAES) - 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects)
3GPP TSG-SA5 (Telecom Management) S5-072005
Meeting SA5#56, 22 - 26 October 2007, Guangzhou, CHINA
Work Item Description
Title
Evolved Packet Core (EPC) Charging UID_380038
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
UID_320005 3GPP System Architecture Evolution Specification - Evolved Packet System (non RAN aspects)
3 Justification
The Evolved 3GPP System needs reliable and efficient charging solutions. As the Evolved 3GPP System is an evolvement of UMTS, also the charging solutions for the Evolved 3GPP System should evolve from UMTS. Following the recommendations of the Study on Charging Aspects of 3GPP System Evolution a re-use of the existing UMTS charging standard solutions will have the following benefits:
• It is proven in operation;
• It will minimise both the standardisation and product development efforts (i.e. the cost and time);
• It provides a base, on which more functionality can be developed;
• It will shorten the time to market for Evolved 3GPP systems;
• It will facilitate a seamless coexistence with UMTS charging systems.
• It will also consider non-3GPP access;
• It will enable an easy migration for the Operator to the new solution.
4 Objective
This work item proposes to introduce Charging for the EPC Architecture by following the recommendations given in TR 32.820.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
This work item will cover Charging for EPC.
8 Security Aspects
Further investigation needed. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 7 Feature: IMS Multimedia Telephony and Supplementary Services UID_370059 | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 7.1 BB: AoC support in IMS Charging | Technical Specification Group Services and System Aspects TSGS#38(07)0739
Meeting #38, 03 - 06 December 2007, Cancun, MEXICO
Source: SA5 (Telecom Management)
Title: New WID on Advice of Charge (AoC) support in IMS Charging
Document for: Approval
Agenda Item: 10.26 (CH8) - Charging Management small Enhancements
3GPP TSG-SA5 (Telecom Management) S5-072012
Meeting SA5#56, 22 - 26 October 2007, Guangzhou, CHINA
Work Item Description
Title
Advice of Charge (AoC) support in IMS Charging UID_380042
The AoC service is standardized in 3GPP and available for CS and PS networks based on Charge Advice Information (CAI).
TISPAN introduced AoC based on Tariff Information according to ITU recommendations and ETSI specifications.
It is becoming available in 3G IMS networks. The usage of AoC in IMS based networks should be defined in 3GPP.
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
• UID_370059 IMS Multimedia Telephony and Supplementary Services (Acronym: IMSTSS)
3 Justification
AoC is currently listed in the charging requirements for 3GPP in TS 22.115.
The high level description on AoC Information and Charging levels is in TS 22.086 and TS 23.086. AoC is based on the Charge Advise Information (CAI) defined in TS 22.024.
The support of subscribed AoC in CAMEL for CS and PS networks is specified in TS 23.078.
The requirement for AoC support in TISPAN is handled in WID02037 and considers the SIP transfer of charging information in WID 3113.
The transport of tariff information, the evaluation and the advice to the mobile subscriber is not described in IMS.
4 Objective
This work item proposes to introduce AoC in 3GPP IMS Charging and is limited to support AoC information on the corresponding charging interfaces as well as in the OCS.
A new specification will be created with definitions for AoC and description of AoC in IMS Charging. This description will contain the AoC Information for charging purposes.
The determination for SIP transport of tariff information will follow the requirements from TS 22.273.
The mechanism for the tariff change and the support of the tariff format will adhere on the existing 3GPP principles.
Additions, e.g. for different use case or simplifications is For Further Study.
5 Service Aspects
The AoC service provision and information transfer should be made available as a SIP based IMS services. The transfer of tariff information is outside the scope of this WID but is For Further Study in other 3GPP groups.
6 MMI-Aspects
The presentation of the AoC information at the UE/ME is outside the scope of this WID and shall be considered in other 3GPP groups.
7 Charging Aspects
This is a Charging Work Item
8 Security Aspects
Further investigation needed |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 7.2 BB: IMS Multimedia Telephony Service UID_370062 | Technical Specification Group Services and System Aspects TSGS#38(07)0749
Meeting #38, 03 - 06 December 2007, Cancun, MEXICO
Source: SA5 (Telecom Management)
Title: New WID on Multimedia Telephony Service and Supplementary Services (MMTel) Charging
Document for: Approval
Agenda Item: 10.26 (CH8) - Charging Management small Enhancements
3GPP TSG-SA5 (Telecom Management) S5-072014
Meeting SA5#56, 22 - 26 Oct 2007, Guangzhou, CHINA
Work Item Description
Title:
Multimedia Telephony Service and Supplementary Services (MMTel) Charging UID_380041
Supplementary services are a critical part of IMS. The current IMS charging specifications do not fully support supplementary services and associated charging records. This work proposal recommends adding MMTel charging
Is this Work Item a "Study Item"? (Yes / No): No
1 3GPP Work Area
Radio Access
X
Core Network
Services
2 Linked work items
Feature UID_370059 IMS Multimedia Telephony and Supplementary Services (Acronym: IMSTSS)
BB: UID_370062 IMS Multimedia Telephony Service (Acronym: IMS-MMTel)
3 Justification
The current 3GPP IMS charging documents do not fully cover MMTel supplementary services. The supplementary services are important to network operators since majority of voice calls involves supplementary services, such as call forwarding, call waiting, conference call, etc. Thus, supplementary service charging should be included in IMS session charging.
4 Objective
This work item proposes to introduce MMTel charging in 3GPP IMS. A new specification will be created with definitions for multimedia telephony service charging in IMS. Also this work item will enhance existing SA5 TS 32.298 and TS 32.299 by adding MMTel supplementary services AVPs from Telephone Application Server and corresponding charging fields in the charging data records.
NOTE : MMtel online charging was initially part of this Work Item. It is proposed to handle MMTel online charging in a separate Work Item.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
This is a charging Work Item
8 Security Aspects
None |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 8 Feature: UTRA HNB UID_390033 | |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 8.1 BB: 3G Home NodeB OAM&P (type 1 definition) (HNB-3G_OAM) UID_420037 | Technical Specification Group Services and System Aspects TSGS#42(08)0708
Meeting #42, 8 - 11 December 2008,
Athens, Greece
3GPP TSG-SA5 (Telecom Management) S5-082488
Meeting SA5#62, 17~21 November 2008, Miami, USA
Source: Huawei Technologies, Nokia Siemens Network, Ericsson
Title: New WT-level WID on 3G Home NodeB OAM&P (Interface Type 1 Management)
Document for: Approval
Agenda Item: 6.2
Parent Building Block
Unique ID
Title
TS
UID_380065
Home NodeB / eNodeB
HomeNB |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 3 Justification | In order to complement the work done in RAN, it’s SA5 responsibility to provide corresponding OAM solution for 3G Home NodeB. SA5 will need to standardize management services that are specific to Home NodeB because of the following Home NodeB characteristics:
• The quantity of Home NodeB is likely to be large
• There may be many Home NodeB vendors
• Home NodeB may be purchased easily by end users in market
• The location of Home NodeB could be in a private residence which may not be accessible for frequent on-site maintenance
SA5 has studied Home NodeB OAM and SON aspects for some time. The management differences between Home NodeB and macro NodeB are listed in TR32.821. The requirements for managing Home NodeB have been provided in the TR32.821 and the consequences on the management interface for Home NodeB are also described.
Based on the study in SA5, it was agreed the interface type 1 and type 2 shown in the following diagram are to be standardized for Home NodeB OAM&P. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 4 Objective | This work Item is to define corresponding OAM solution for 3G Home NodeB on interface type 1 management. The workitem will include (but not necessarily limited to):
4.1 Management on Standard Interfaces type 1 for 3G Home NodeB:
• Investigate what management standardization work are needed for management of 3G Home NodeB over interface type 1.
• Define the standardization work mentioned above for 3G Home NodeB management over interface type 1.
4.2 This WI shall include:
• Stage 1 Requirements specified in TS 32.XX1
◦ Configuration Management (CM)
◦ Fault Management
◦ Performance Management
◦ Security aspects of OAM
◦ Note: Input for this TS is derived from TS25.467, TR32.821, SA5 contributions & Specification
• Stage 2 specified in TS 32.XX2
◦ Architecture for HNB Management (derived from TS25.467, TR32.821, SA5 contributions & Specification) for CM, FM and PM
◦ Object Classes for
▪ Configuration Management (CM) for
• HNB Access Network
• Core Network (related to HNB)
• Transport Network (related to HNB)
▪ Fault Management
▪ Performance Management
◦ Stage 2 for contents definition for CM, FM, PM & Logging
◦ Note: Input for this TS is derived from TS25.467, TR32.821, bbf2008 851 00 (BBF contribution), SA5 contributions & Specification
• The HNB to ACS procedure flow document TS 32.xx3
◦ OAM Procedural flows for HNB Discovery, registration, config updates
◦ OAM Procedural flows for FM
◦ OAM Procedural flows for PM
◦ Note: Input for this TS is derived from TS25.467, TR32.821, SA5 contributions & Specification
• Stage 3 specified in TS 32.XX4
◦ Data Format for CM, FM & PM (specified or referenced if required by stage-2)
4.3 The standardization work for management on interface type 2 will not be covered in this workitem. |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 10 Expected Output and Time scale | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.581
Home NodeB OAM&P concepts and requirements(for interface type1)
SA5
SA#43 Mar 2009
SA#43 Mar 2009
32.582
Home NodeB OAM&P Stage2(for interface type1)
SA5
SA#43 Mar 2009
SA#43 Mar 2009
32.583
HNB to ACS procedure flow
SA5
SA#43 Mar 2009
SA#43 Mar 2009
32.584
Home NodeB OAM&P Stage3(for interface type1)
SA5
SA#44 Mar 2009
SA#44 Mar 2009
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item rapporteur(s)
Huawei Technologies.([email protected])
12 Work item leadership
SA5
13 Supporting Individual Members
Supporting IM name
Huawei Technologies.
Nokia Siemens Networks
Ericsson
Vodafone
T-Mobile
Telefonica
Alcatel-Lucent
IPAccess
China Mobile
Telecom Italia
Airvana
Motorola
ZTE
Qualcomm
Samsung
14 Classification of the WI (if known)
Study Item (no further information required)
Feature (go to 14a)
X
Building Block (go to 14b)
Work Task (go to 14c) |
75b0bc4f802ad76b9632a25b25224d00 | 30.818 | 14b The WI is a Building Block: parent | Feature UID_390033 UTRA HNB (Acronym: HNB)
Annex A:
List of SA5 Release 8 specifications
Type
Number
Title
rapporteur
TR
30.818
Project scheduling and open issues for SA5, Release 8
ZOICAS, Adrian
TS
32.121
Advanced alarming on Itf-N Integration Reference Point (IRP); Requirements
SUERBAUM, Clemens
TS
32.122
Advanced alarming on Itf-N Integration Reference Point (IRP); Information Service (IS)
SUERBAUM, Clemens
TS
32.123
Advanced alarming on Itf-N Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
SUERBAUM, Clemens
TS
32.153
IRP technology specific template
TOVINGER, Thomas
TS
32.154
Backward and Forward Compatibility (BFC); Concept and definitions
TOVINGER, Thomas
TS
32.155
Requirements template
TOVINGER, Thomas
TS
32.274
Charging management; Short Message Service (SMS) charging
WONG, Gavin
TS
32.275
Charging management; MultiMedia Telephony (MMTel) charging
GARDELLA, Maryse
TS
32.280
Charging management; Advice of Charge (AoC) service
GÖRMER, Gerald
TS
32.410
Telecommunication management; Key Performance Indicators (KPI) for UMTS and GSM
LIANG, Shuangchun
TS
32.450
Key Performance Indicators (KPI) for E-UMTS: Definitions
HÜBINETTE, Ulf
TS
32.451
Key Performance Indicators (KPI) for E-UMTS: Requirements
HÜBINETTE, Ulf
TS
32.500
Self-Organizing Networks (SON); Concepts and requirements
GOMPAKIS, Panagiotis
TS
32.501
Self-Organizing Networks (SON); Self-establishment of eNodeBs; Concepts and requirements
SUERBAUM, Clemens
TS
32.502
Self-Organizing Networks (SON); Self-establishment of eNodeBs; Stage 2
SUERBAUM, Clemens
TS
32.511
Self-Organizing Networks (SON); Automatic Neighbour Relation (ANR) management; Concepts and requirements
TSE, Edwin
TS
32.521
Self-Organizing Networks (SON); Self-optimization and self-healing; Concepts and requirements
WANG, Xuelong
TS
32.531
Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements
TS
32.532
Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS)
TS
32.533
Telecommunication management; Software management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TS
32.537
Telecommunication management; Software management Integration Reference Point (IRP); SOAP Solution Set (SS)
TS
32.581
Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Concepts and requirements for Type 1 interface HNB to HNB Management System (HMS)
Zou Lan
TS
32.582
Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HNB to HNB Management System (HMS)
SUDARSAN, Padma
TS
32.583
Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HNB to HNB Management System (HMS)
Malviya, Manish
TS
32.584
Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS)
ANDRIANOV, Anatoly
TS
32.751
EPC NRM IRP Requirements
LOU, Min
TS
32.752
EPC NRM IRP Information Service
WANG, Xuelong
TS
32.753
EPC NRM IRP CORBA Solution Set
LOU, Min
TS
32.755
EPC NRM IRP Bulk CM XML file format definition
WANG, Xuelong
TS
32.761
E-UTRAN NRM IRP Requirements
ELMDAHL, Per
TS
32.762
E-UTRAN NRM IRP Information Service
ELMDAHL, Per
TS
32.763
E-UTRAN NRM IRP CORBA Solution Set
ELMDAHL, Per
TS
32.765
E-UTRAN NRM IRP Bulk CM XML file format definition
ELMDAHL, Per
TR
32.808
Study of Common Profile Storage (CPS) Framework of User Data for network services and management
ABA, Istvan
TR
32.816
Study on management of Long Term Evolution (LTE) and System Architecture Evolution (SAE)
PETERSEN, Robert
TR
32.818
Study on 3GPP SA5 / MTOSI XML harmonization
DUGUAY, Jean
TR
32.819
Telecommunications management; Element management layer - Operation System Function (E-OSF) definition
YANG, Li
TR
32.820
Charging management; 3GPP System Architecture Evolution (SAE): Charging aspects
GÖRMER, Gerald
Annex B:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-09
SA#49
SP-100524
--
--
Presentation to SA for Information and Approval
---
1.0.0
2010-10
--
--
--
--
Publication
1.0.0
8.0.0 |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 1 Scope | This document studies the security architecture, i.e. the security features and the security mechanisms for inter-access mobility between 3GPP access system and non-3GPP access systems. For the general architecture for inter-access mobility cf. TR 23.882. This report is meant to provide more detail on the security aspects of inter-access mobility.
The scope should be extended to the mobility between two non-3GPP access systems, which interwork with 3GPP core entities. An example would be the mobility between two WLAN access systems providing 3GPP IP access.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.402 [14]. This TR may therefore be useful to better understand the basis on which decisions in TS 33.402 [14] were taken, and which alternatives were under discussion. However, none of the text in this TR shall be quoted as reflecting 3GPP’s position in any way. Rather, 3GPP’s position on security for non-3GPP access to EPS is reflected in the normative text in TS 33.402 [14]. Information in the TR may be inaccurate and outdated. One example of outdated text can be found in clauses 4.1 and 4.2 on alternatives for authentication protocols. The choices of authentication protocols finally made by 3GPP can be found in TS 33.401 [13] and TS 33.402 [14] respectively. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 23.882: "3rd Generation Partnership Project; 3GPP System Architecture Evolution: Report on Technical Options and Conclusions".
[2] 3GPP TS 33.234: "3rd Generation Partnership Project; Wireless Local Area Network (WLAN) interworking security".
[3] 3GPP TS 29.061: "3rd Generation Partnership Project; Technical Specification Group Core Network; Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[4] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[5] “IKEv2 Mobility and Multihoming Protocol (MOBIKE)”, draft-ietf-mobike-protocol-03.txt, Sep 2005.
[6] RFC 3957 “Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4”.
[7] "NETLMM protocol", draft-giaretta-netlmm-dt-protocol-00.txt, June 2006.
[8] RFC 4285 “Authentication Protocol for Mobile IPv6”.
[9] “Mobile IPv6 Bootstrapping for the Authentication Option Protocol”, draft-devarapalli-mip6-authprotocol-bootstrap-03.txt, September 2007.
[10] “Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction”, draft-ietf-dime-mip6-split-05.txt, September 2007.
[11] “Proxy Mobile IPv6”, draft-ietf-netlmm-proxymip6-06.txt, September 2007.
[12] RFC4832 “Security threats of network based mobility management”.
[13] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security Architecture".
[14] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non- 3GPP accesses". |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 3 Definitions, symbols and abbreviations | |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 3.1 Definitions | For the purposes of the present document, the following apply:
Access network: one of following access network: GPRS IP access, WLAN 3GPP IP access, WLAN Direct IP access LTE, WiMax, etc.
Data origin authentication: The corroboration that the source of data received is as claimed.
WLAN 3GPP IP Access: Access to an IP network via the 3GPP system.
WLAN Direct IP Access: Access to an IP network is direct from the WLAN AN.
3GPP - WLAN Interworking: Used generically to refer to interworking between the 3GPP system and the WLAN family of standards.
Trusted Access: A non-3GPP IP Access Network is defined as a “trusted non-3GPP IP Access Network” if the 3GPP EPC system chooses to trust such non-3GPP IP access network. The 3GPP EPC system may choose to trust the non-3GPP IP access network operated by the same or different operators, e.g. based on business agreements. Specific security mechanisms may be in place between the trusted non-3GPP IP Access Network and the 3GPP EPC to avoid security threats. The decision whether a specific non-3GPP IP Access Network is trusted or untrusted is up to the 3GPP EPC operator, and is not based on the specific link-layer technology adopted by the non-3GPP IP Access Network.
Source access system: in handover situations, this is the access system, from which the UE is handed over.
Target access system: in handover situations, this is the access system, to which the UE is handed over. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
Gi Reference point between GPRS and an external packet data network
Wi Reference point is similar to the Gi reference point, applies to WLAN 3GPP IP Access
Wm Reference point is located between 3GPP AAA Server and Packet Data Gateway respectively between 3GPP AAA Proxy and Packet Data Gateway
Wu Reference point is located between the WLAN UE and the PDG. It represents the WLAN UE-initiated tunnel between the WLAN UE and the PDG
Gi+/Wi+ Mobile IP signalling and bearer plane between the Gateway (i.e. GGSN or PDG) and the MIP HA; |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
AAA Authentication Authorisation Accounting
AN Access network
APN Access Point Name
BSF Bootstrapping Function
DS-MIPv6 Dual stack MIP
FA Foreign Agent
GBA Generic Bootstrapping Architecture
GGSN Gateway GPRS Support Node
HA Home agency
HN Home network
IP Internet Protocol
IPSec IP Security protocol
I-WAN Interworking Wireless Local Area Network
MIP IP mobility
MOBIKE IKEv2 Mobility and Multihoming Protocol
MS Mobile Station
MN Mobile Node
NAI Network Access Identifier
NAT Network Address Translation
NAF Network Application Function
NETLMM Network-based localized mobility management
PDG Packet Data Gateway
PDP Packet Data Protocol
RFC Request For Comments
RRQ MIPv4 Registration Request
RRP MIPv4 Registration Response
SAE System Architecture Evolution
SGSN Serving GPRS Support Node
SPI Security Parameter Index
URI Uniform Resource Identifier
USIM UMTS subscriber identity module
UE User Equipment |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 4 Authentication protocols across access systems | Editor’s note: it will be decided later if this section is needed in the final report.
It is assumed that an SAE user has a USIM which is used as user credential in authentication.
Authentication protocols are assumed to be run between the UE and an authentication server in the home network. It is likely there will always be a 3G AAA server to terminate authentication protocols in SAE, but this is still to be decided by SA2 (i.e. it is still to be decided whether always AAA protocols, e.g. DIAMETER, will be used to carry authentication data, or whether MAP may still be used). When AKA is used then the 3G AAA server will interface with a 3G Authentication Centre.
Even for one user, the type of authentication protocol depends on the type of access network. E.g. for I-WLAN EAP-AKA may be used, whereas for UTRAN UMTS AKA will be used. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 4.1 UMTS AKA | UMTS AKA will be used across UTRAN. It is still to be decided by SA3 whether UMTS AKA or EAP-AKA will be used over LTE. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 4.2 EAP-AKA | EAP-AKA may be used across I-WLAN and for WiMAX. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 4.3 Others | |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 5 Establishment of security contexts in the target access system | Each type of access system may require there own security contexts, which may need to be available to protect the access network. An example is an MSK key in a WLAN access system using an EAP method for authentication and key agreement. The MSK is then used to derive further keys.
An example of an access system more complex than WLAN and requiring more security contexts to be set up is WiMAX. WiMAX does not only need keys for the protection of the link layer, but e.g. also keys to protect Mobile IP signalling of the WiMAX-internal Mobile IP (CMIP or PMIP) layer providing WiMAX-internal mobility, which is different from the SAE Mobile IP layer providing mobility between access systems, of which at least one is non-3GPP.
There may also be access systems, which do not require any security context, e.g. a DSL-based access system relying on physical security.
The establishment of these security contexts in the access system may be done in two ways:
with the support of SAE;
without the support of SAE. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 5.1 Establishment of security contexts with the support of SAE | In this case, the credentials the UE shares with the 3G AAA server are used to establish security contexts in the access system. An example of this case is I-WLAN Direct IP access, where the SIM or USIM are used to establish MSK required to protect the WLAN link layer. Another example is likely WiMAX: the WiMAX Forum is currently working on solutions for 3G-WiMAX interworking, which would allow to bootstrap WiMAX-internal security contexts from a key derived from a run of EAP-AKA between the UE and the 3G AAA server. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 5.2 Establishment of security contexts without the support of SAE | In this case, credentials other than those available in 3G networks are used to establish security contexts in the non-3GPP access system. An example of this case is WiMAX when WiMAX-specific credentials are used to set up IP connectivity across WiMAX. SAE plays no role in this set up, so the establishment of these security contexts is out of scope of SAE.
It is assumed that the SAE user always uses a USIM on UICC to perform mutual authentication and establish security contexts with the Home Network.
It is to be decided by SA3 whether a UE-PDG tunnel is required. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 6 Establishment of IPsec tunnel between UE and PDG across the target non-3GPP access system (if required) | One of the two variants of the S2 interface in the SAE architecture, cf. TR 23.882, allows to connect an access system to the evolved SAE packet core via an IPsec tunnel between the UE and a PDG. WLAN 3GPP IP access is an example of the use of such a tunnel, but WLAN is not the only access system which may be connected in this way. This section deals with the roaming of a UE between an access system (old) to another access system (new), for the case that at least the target access system requires such a UE-PDG tunnel.
The level of security achieved in certain deployments of non-3GPP IP access networks though internal security mechanisms (including confidentiality, integrity protection, protection of signalling, key management, etc) of some such non-3GPP IP access networks may be trusted by the 3GPP Evolved Packet Core (EPC) operator. In such case, no additional security mechanisms (e.g. IPSec tunnels from the UE to the EPC) are required. in the sense that the non-3GPP IP access network can interwork with the 3GPP EPC without relying on an IPsec tunnel to the UE. Such non-3GPP IP access networks are referred to here as "trusted non-3GPP IP access networks". The decision whether a specific non-3GPP IP access network is trusted or untrusted is up to the 3GPP EPC operator and is not based on the specific link-layer technology adopted by the non-3GPP IP access network.
If the non-3GPP IP access network is trusted (i.e. based on business, roaming and interconnection agreements), the need for a PDG functionality to connect the non-3GPP IP access to the EPC is FFS. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 6.1 The source access system has a UE-PDG tunnel | An example of this case is mobility between two I-WLAN 3GPP IP access systems. The problem to be solved is to retain the IPsec tunnel even when the IP address of the UE changes due to mobility.
There are two cases here: the PDG remains the same or the PDG changes.
If PDG remains the same, the existing IPsec tunnel could be maintained. In order to achieve this, a mechanism proposed in TR 23.882, Annex E, is MOBIKE. For MOBIKE to work, it is required that the PDG remains the same while the UE moves.
If the PDG changes, then it is not a matter of maintaining the IPSec tunnel, but creating a new one with the target PDG. In such case, the focus becomes the mechanisms on the S2 interface, not what happens between the new PDG and the UE.
Another possible solution to retain the IPsec tunnel when the PDG remains fixed would be the use of an IP mobility mechanism (e.g. Mobile IP). The Mobile IP Home Agent would have to be e.g. located between the PDG and the UE, but close to the PDG, ensuring that the outer IP address of the IPsec tunnel remains constant, even while the UE moves and acquires a new local IP address. The adoption of MIP for mobility is FFS.
If the PDG changes, then it is not a matter of maintaining the IPSec tunnel, but creating a new one with the target PDG. In such case, in addition, to the establishment of the new IPsec tunnel, the mobility of the PDG has to be handled by the S2 interface. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 6.2 The source access system does not have a UE-PDG tunnel | An example of this case is mobility between a 3GPP access system, such as LTE or UTRAN, and an I-WLAN 3GPP IP access system. The problem to be solved is to set up the IPsec tunnel in the target system in an efficient way.
Neither MOBIKE nor an additional layer of Mobile IP will help here. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7 Security for IP based mobility | There may be several layers of Mobile IP being used in a complete SAE system, including access networks. E.g. there is a WiMAX-internal Mobile IP layer. The considerations in this section are concerned with the outermost such layer, where the related Home Agent 3GPP HA resides in the 3G network. It is still to be decided if the HA is located in the SAE anchor, cf. architecture in section 4. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.1 General requirement | Major security threats related to IP mobility, when the procedures are not properly secured, are:
- IP address ownership needs to be verified else redirection attacks will happen
- Traffic sent to a target redirected elsewhere
- Attacker can blackhole traffic to a victim
- Attacker can insert itself on-path as a Man-in-the-Middle
- Redirecting traffic for someone to a victim
- Leads to (D)DoS (distributed denial of service) 3rd party bombing
- Consequently charging can be confused
- (D)Dos attack on mobility anchor
Key handling principle for inter-3GPP HO:
Before handover from EUTRAN to non-3GPP IP access network and/or from non-3GPP IP access network to EUTRAN, UE and EPS core network use the present key and the same key derivation function to derive the new key, which is to be used after handover.
(From S3-070732)
Some of the main problems that need to be considered when defining secuity context transfer optimizations for non-3GPP/3GPP handovers are:
• Security (avoiding negative impact on LTE/UMTS security)
• User privacy related to identity management
• AAA architecure misaligmnent between 3GPP and non-3GPP accesses
• Difficulty of defining a unique reference point for (secure) inter-access security context transfer.
• Possible standardization impact outside 3GPP (IETF, IEEE).
These shall be taken into account when looking at optimizations for handovers between 3GPP and non-3GPP accesses.
There are different kinds of make-before-break solutions using pre-authentication. This pre-authentication could take place either at the time of hand-over preparation, or (for e.g. single-radio terminals) the authentication could (perhaps) be prepared at the initial attach. It is an agreed working assumption that solutions based on pre-authentication should be the focus of the SA3 study for authentication optimizations for handovers between 3GPP and non-3GPP accesses |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.2 Host based Mobility | |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.2.1 Security associations used with Mobile IP | Figure 1 gives an overview of the MIP security associations which need to be present irrespective of the version of Mobile IP used. More security associations may be required for certain versions of Mobile IP. E.g. for Mobile IP v4 with a Foreign Agent, security associations between MN and FA, and FA and HA are needed.
Figure 1: Overview of the security architecture for MIP
The needed security associations are:
- A security association between the UE and 3GPP AAA. It is assumed that the 3GPP AAA in HPLMN is in charge of user authentication and authorization. This security association is based on a long-term secret.
- A security association between the UE and 3GPP MIP HA. This security association is established dynamically.
- A security association between 3GPP MIP HA and 3GPP AAA server in the same network. Typically, this security association is static. NDS/IP could be used when proxy AAA is used in roaming case. See TS 33.210 for more detail information [4]. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.2.2 Security protocols used with Mobile IP | 1. The security association between the MN and 3GPP AAA is used for (mutual) authentication. In our context, the authentication protocol may be e.g. EAP-AKA. This protocol is independent of Mobile IP, but keys derived from a run of this protocol may be used for Mobile IP purposes.
2. The security association between the MN and 3GPP MIP HA is used for MIP signalling integrity protection. The protocols used depend on the version of Mobile IP. To give examples:
MIPv4: Home agent and mobile nodes shall be able to perform message authentication according to RFC 3344. MN-HA key agreed between HA and MN during MIP authentication is used to compute the digest in the Mobile-Home Authentication Extension according to RFC3344. The Mobile-Home Authentication Extension is used to provide integrity of signalling between Mobile Node and Home Agent. HMAC-MD5 shall be used as authentication algorithm with a key size 128 bit. HA will compute the UDP payload (RRQ or RRP data), all prior extensions, the type, length and SPI of the extension with MN-HA key in MIP Req-resp. MN uses with HMAC-MD5 to verify the received message from HA.
For MIPv4 with a foreign agent, more security associations are needed, as mentioned in the previous subsection. RFC3344 can also be used for these. The foreign agent shall be able to support message authentication using HMAC-MD5 and key size of 128 bits, with a key distribution mechanism (FFS).
MIPv6: IPsec is specified as the means of securing signalling messages between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6) in RFC3776. RFC4285 proposes an alternate method for securing MIPv6 signalling messages between Mobile Nodes and Home Agents. The alternate method consists of a MIPv6-specific mobility message authentication option that can be added to MIPv6 signalling messages.
The alternate method is entirely based on shared secrets and does not use IPsec.
3. The security association between 3GPP MIP HA and 3GPP AAA server in the same network is used to securely transport the MN-HA keys from AAA server to MIP HA. It may not be needed if the interface between AAA server and HA is secured by other means.
Home agent and mobile nodes may perform message authentication whenever it is needed. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3 Bootstrapping of Mobile IP parameters | |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3.1 General | It would be undesirable for SAE if the UE had to obtain security credentials to be used specifically for Mobile IP signalling security. Rather, the security associations required for Mobile IP should be able to be derived from security credentials already available. In the case of SAE, this means that it should be possible to derive the security associations required for Mobile IP from the USIM.
Authentication between the MN and the network shall be performed as. A subscriber, who wants to use MIP, will have its subscriber profile located in the 3GPP AAA in the Home Network. The subscriber profile will contain information on the subscriber that may not be revealed to an external partner, At MIP registration , during a change of location between different access networks by matching the request with the subscriber profile, if the subscriber is allowed to continue with the request or not. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3.2 RFC3957 used in conjunction with GBA | NOTE: this subsection applies only to MIPv4.
MN-HA key generation & distribution based on RFC 3957. This method uses pre-shared secret between MS and AAA server to establish a shared secret between MS and HA and / or MS and FA.
Figure 2: MN-HA key generation & distribution
1. During initial MIPv4 registration, MS includes a new extension (called the MN-HA Key Generation Nonce Request extension [RFC 3957]) in RRQ to request for a nonce from HAAA. The RRQ also contains the MS’s credential in the MN-AAA authenticator extension.
2. FA sends DIAMETER/RADIUS Access-Request to HAAA to authenticate the MS credential.
3. If the MS is authenticated successfully, the HAAA returns DIAMETER/RADIUS Access-Accept.
4. FA forwards the RRQ to the HA.
NOTE: If co-located care-of address mode is used, then RRQ message will be sent from MS to HA directly without FA in above picture
5. HA sends DIAMETER/RADIUS Access-Request to HAAA. In case of Roaming, the message will send through VAAA to HAAA. The DIAMETER/RADIUS Access-Request contains the MN-HA SPI attribute to request for a MN-HA key to HAAA that the MN-HA key needs to be derived. The HA may include the MS credential in the DIAMETER/RADIUS Access-Request.
Editor’s note: it’s FFS if it’s possible for a HA in the visited network.
6. HAAA selects a nonce and derives the MN-HA key from the MN-AAA shared secret, MS’s NAI, and the nonce.
7. HAAA returns DIAMETER/RADIUS Access-Accept that contains the MN-HA key and the nonce.
8. The HA sends RRP with a new extension (called the Generalized MN-HA Key Generation Nonce Reply Extension [RFC 3957]) carrying the key generation nonce, and the MN-HA authenticator computed from the MN-HA key. The new extension must precede the MN-HA authenticator. (FA forwards the RRP to the MS)
9. The MS derives the MN-HA key and uses it to verify the MN-HA authenticator in the RRP.
One possible way is to use GBA in conjunction with RFC 3957. In this case HAAA is associated with NAF.
Figure 3: Using GBA to derive and distribute MN-HA Keys (HAAA as NAF)
Generic Bootstrapping Architecture (GBA) allows bootstrapping of shared secrets between a UE/MN and the home network (Bootstrapping Service Function, BSF), which can then be used to derive further shared secrets to be used between MS and a Network Application Function(NAF).
Two options for using GBA in the inter access mobility authentication are considered:
- using GBA to derive the MN-HA Keys, in which case the HA is used as NAF and.
- using GBA to provision MN-AAA Keys, in which case HAAA is used as a NAF.
Figure 5 shows how GBA could be used to derive and distribute MN-HA Keys when HAAA as NAF, i.e. HAAA is associated with a Network Application Function (NAF).
1. The MN performs a bootstrapping procedure with the BSF and generates a (master) shared secret, Ks. Bootstrapping procedure is performed between the UE/MS and the BSF (which is located in the home network). During bootstrapping, mutual authentication is performed between the MS and the home network, and a bootstrapping key, Ks, will be generated by both the UE/MS and the BSF. Associated with the Ks include a Bootstrapping Transaction Identifier (B-TID) and a lifetime of the Ks.
NOTE: This procedure is only needed during initial registration (and it can be done before the MIP registration). It is not repeated at every HO (Handover). The only time it needs to be repeated is when the key is about to expire. But even in this case, the GAA procedure is done “offline”—i.e. the next MIP registration does not need to wait for GAA procedure to complete.
2. MN can then start MIP related signalling with the HA, which in turn contacts the HAAA.
3. HA then contacts to HAAA using Diameter/ RADIUS. Note: in the baseline document only RADIUS message is shown in the figure and the text. However, both Diameter and RADIUS can be used.
4. The HAAA, acting as a NAF, does not have the MN-AAA key, as the MN-AAA key is supposed to be generated by the BSF using Ks and other inputs to a KDF (key derivation function). Therefore, the HAAA will contact the BSF and fetch the MN-AAA key (Ks_(ext/int)_NAF of the HAAA) needed to authenticate the MN.
5. MN-HA keys are then derived from the MN-AAA Key using RFC 3957.
NOTE: If foreign agents (FA) are used, then foreign agent use Diameter/RADIUS to communication with HAAA.
Editor’s note: it needs to check how to send the B-TID in MIP registration message. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3.3 Use GBA to generate MN-HA key | NOTE: This subsection applies to MIPv4and MIPv6.
In this alternative authentication method, HA is associated with NAF.
Home Agent (HA) is associated with a NAF, and Ks_(ext/int)_NAF would be used as MN-HA key: the MN performs a bootstrapping procedure with the BSF and generates a (master) shared secret, Ks. After that, the MN can start MIP related signalling with the HA, which in turn contacts the BSF to fetch MN-HA key.
Figure 4: Overview of GBA operations
1. Bootstrapping procedure is performed between the UE/MS and the BSF (which is located in the home network). During bootstrapping, mutual authentication is performed between the MS and the home network, and a bootstrapping key, Ks, will be generated by both the UE/MS and the BSF. Associated with the Ks include a Bootstrapping Transaction Identifier (B-TID) and a lifetime of the Ks.
NOTE: This procedure is only needed during initial registration (and it can be done before the MIP registration). It is not repeated at every HO (Handover). The only time it needs to be repeated is when the key is about to expire. But even in this case, the GAA procedure is done “offline”—i.e. the next MIP registration does not need to wait for GAA procedure to complete.
2. Once bootstrapping is completed, UE/MS can make use of the bootstrapped security association with a network application server, called the Network Application Function (NAF). To do so, the UE/MS communicates with the NAF. The UE/MS conveys to the NAF the B-TID.
3. The UE/MS derives the application specific session keys Ks_(ext/int)_NAF using a pre-defined key derivation function (KDF), with Ks, identifier of the NAF (NAF_Id), as well as other information as input. Upon receiving the request from UE/MS in step 2, the NAF contacts the BSF over the Zn to request the Ks_(ext/int)_NAF. The NAF provides the B-TID received from the UE/MS, and provides its own identity (NAF_Id). The BSF derives the Ks_(ext/int)_NAF in the same way as the UE/MS, and returns the derived key to the NAF. The Ks_(ext/int)_NAF can then be used as the shared secret between the MS and the NAF for any further security operations.
NOTE: If foreign agents (FA) are used, then foreign agent implements GAA NAF to get the MN-FA key. |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3.4 Use partial GBA to derive MN-HA Keys | NOTE: This subsection applies to MIPv4 and MIPv6.
GBA was designed for a situation where a UE wants to securely access potentially many application servers (NAFs), while having to be authenticated to the home network (and consume authentication vectors) in the Ub protocol run only once. Furthermore, the NAFs the UE wants to access may and need not be known at the time of the Ub protocol run. These requirements do not apply to MIP bootstrapping: the number of MIP servers with which the UE needs to share a key is limited to one, namely the Home AAA or Home Agent (when no Foreign Agent is used), and two, when an FA is used (or three, when two FAs are involved in a handover situation). In addition, the addresses of HA and FA cannot be chosen by the UE any time later, but are assigned by the home network (HA) and the visited network (FA), respectively. Therefore, the full functionality of GBA may not be needed.
A disadvantage of the use of GBA for MIP bootstrapping is that the HA, and, if applicable, the FA, need to support NAF functionality. An off-the-shelf HA or FA does not do that.
Editor’s note: the intention of this GBA extension is a subset of GBA and should not be a problem.
We consider two cases below. For both cases, the following is assumed:
- a UE has to run the Ub protocol with the BSF before starting MIP registration.
- the BSF is integrated with the AAA server (as in the current baseline document).
- the AAA server distributes keys to HA and FA using standard AAA procedures (for MIPv4: RFC4004: DIAMETER Mobile IPv4 application, and for MIPv6: draft-ietf-dime-mip6-split-03), and does not use the Zn interface.
- the distributed keys are used with the Mobile IPv4 and Mobile IPv6 authentication mechanisms defined in RFC 3344 and RFC 4285 respectively
Editor’s note: it’s FFS whether RADIUS extension also needs to be supported.
With these assumptions, HA and FA can be off-the-shelf, and need not be GBA-aware. The Ua and the Zn interfaces are not needed.
Case 1: HA and FA addresses and/or names are acquired by the UE independently of the Ub protocol run
In this case, the BSF and the UE derive keys Ks_(ext/int)_NAF to be shared between UE and HA, and UE and FA, respectively, as specified in TS 33.220.
Editor’s note: no change to Ub in Case 1.
Case 2: The HA address and/or name is acquired by the UE as part of the Ub protocol run
In this case, the BSF can send the FQDN, and possibly also the IP address, of the HA to the UE in a new element in the XML body of the “200OK” message, which is the last message in the Ub protocol run. This provides an alternative to SAE HA address assignment. Note that it may not be obvious for all access systems how to let the UE acquire the SAE HA address.
Editor’s note: the Ub interface will be affected in Case 2.
The FA address needs to be acquired by the UE locally.
The use of partial GBA for MIP bootstrapping is captured in Figure 5.
Figure 5: Partial GBA for MIP bootstrapping |
f1b0a2c921a1d71d732d8ab589640b1a | 33.922 | 7.3.5 Using IKEv2 | Authentication between the MN and the network and IPsec SA setup between the MN and the HA for MIPv6 shall be performed using IKEv2 as defined in the IETF draft [draft-ietf-mip6-bootstrapping-split-02.txt]. In SAE, the home agent communicates with the AAA server to perform mutual authentication. The IKEv2 authentication is performed using EAP-AKA.
Figure 6: MN-Network authentication and MN-HA IPsec SA setup for MIPv6
Editor’s note 1: adding relatively heavy protocol of IKEv2 should be considered to be for further study if cost efficiency is in appropriate level.
Editor’s note 2: this is only one of multiple different options.
Editor’s note 3: both I-WLAN scenarios 2 and 3 should be studied
(From S3-070820)
The first procedure that must be performed by the MN is the discovery of the HA address, which in case of EPS is the IP address of the PDN GW.
As soon as the Mobile Node has discovered the PDN GW address, it establishes an IPsec Security Association with the Home Agent itself through IKEv2. The detailed description of this procedure is provided in RFC4877. The IKEv2 Mobile Node to Home Agent authentication is performed using Extensible Authentication Protocol (EAP).
When the Mobile Node runs IKEv2 with its Home Agent, it shall request an IPv6 Home Address through the Configuration Payload in the IKE_AUTH exchange by including an INTERNAL_IP6_ADDRESS attribute. When the Home Agent processes the message, it allocates a HoA and sends it a CFG_REPLY message. The IPv6 Home Address allocation through IKEv2 allows to bind the Home Address with the IPsec security association so that the MN can only send Binding Updates for its own Home Address and not for other MN’s Home Addresses.
Figure 7 provides the flow for the initial DS-MIPv6 bootstrapping.
Figure 7: DS-MIPv6 bootstrapping based on IKEv2
1) The UE discovers the PDN GW address based on the procedure specified in 23.401.
2) The UE starts an IKEv2 exchange with the PDN GW. The first part of this exchange is an IKE_SA_INIT exchange.
3) The UE indicates that EAP is used for IKEv2 authentication and an EAP exchange is performed. EAP is carried over IKEv2 between the UE and the PDN GW and over the AAA protocol between the PDN GW and the AAA server.
4) During the IKEv2 exchange, the PDN GW allocates an IPv6 Home Address and send it to the UE in a IKEv2 Configuration Payload.
5) As a result of the previous steps, an IPsec SA is established to protect DS-MIPv6 signalling.
6) The UE sends the MIP Binding Update message to the PDN GW.
7) The PDN GW processes the binding update. The PDN GW sends the MIP Binding Ack to the UE.
8) As a result of the above steps a MIPv6 tunnel is established and the UE can start using its home address at the application level. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.