|
|
| 36.101 | 6011 | - | A | 18.2.0 | Rel-18 | CR for TS 36.101 [LTE_CA_R16_2BDL_2BUL] Addition of missing CA operating bands (R18_CAT A) |
R4-2312598
| agreed | RAN4#108 | ZTE Corporation |
RP-232486
| approved | RAN#101 | RAN4 | 18.3.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 6010 | - | A | 17.10.0 | Rel-17 | CR for TS 36.101 [LTE_CA_R16_2BDL_2BUL] Addition of missing CA operating bands (R17_CAT A) |
R4-2312597
| agreed | RAN4#108 | ZTE Corporation |
RP-232486
| approved | RAN#101 | RAN4 | 17.11.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 6009 | 1 | F | 16.17.0 | Rel-16 | CR for TS 36.101 [LTE_CA_R16_2BDL_2BUL] Addition of missing CA operating bands |
R4-2314870
| agreed | RAN4#108 | ZTE Corporation |
RP-232486
| approved | RAN#101 | RAN4 | 16.18.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 6009 | - | F | 16.17.0 | Rel-16 | CR for TS 36.101 [LTE_CA_R16_2BDL_2BUL] Addition of missing CA operating bands |
R4-2312596
| revised | RAN4#108 | ZTE Corporation |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5857 | - | A | 17.4.0 | Rel-17 | Big CR for TS 36.101 Maintenance (Rel-17) |
R4-2206625
| agreed | RAN4#102-e | MCC, Xiaomi |
RP-220330
| approved | RAN#95-e | RAN4 | 17.5.0 | TEI14, LTE_CA_R... |
|
|
|
| 36.101 | 5856 | - | F | 16.12.0 | Rel-16 | Big CR for TS 36.101 Maintenance (Rel-16) |
R4-2206624
| agreed | RAN4#102-e | MCC, Xiaomi |
RP-220330
| approved | RAN#95-e | RAN4 | 16.13.0 | TEI14, LTE_CA_R... |
|
|
|
| 36.101 | 5646 | - | B | 16.5.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-2008234
| agreed | RAN4#95-e | Huawei, HiSilicon |
RP-201060
| approved | RAN#88-e | RAN4 | 16.6.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5606 | - | B | 16.5.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-2004824
| | RAN4#94-bis-e | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5586 | - | B | 16.3.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1915364
| withdrawn | RAN4#93 | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5549 | - | B | 16.3.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1912522
| withdrawn | RAN4#92-Bis | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5529 | - | B | 16.2.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1909905
| agreed | RAN4#92 | Huawei, HiSilicon |
RP-192042
| approved | RAN#85 | RAN4 | 16.3.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5458 | - | B | 16.1.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1905674
| agreed | RAN4#91 | Huawei, HiSilicon |
RP-191255
| approved | RAN#84 | RAN4 | 16.2.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5444 | - | B | 16.1.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1904516
| agreed | RAN4#90-Bis | Huawei, HiSilicon |
RP-191255
| approved | RAN#84 | RAN4 | 16.2.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5387 | - | B | 16.0.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 bands UL into Rel-16 TS 36.101 |
R4-1901366
| withdrawn | RAN4#90 | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5297 | - | B | 15.4.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 band into Rel-16 TS 36.101 |
R4-1815770
| agreed | RAN4#89 | Huawei, HiSilicon |
RP-182375
| approved | RAN#82 | RAN4 | 16.0.0 | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5255 | - | B | 15.4.0 | Rel-16 | Introduction of completed LTE CA for 2 bands DL with 2 band into Rel-16 TS 36.101 |
R4-1814263
| agreed | RAN4#88-Bis | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|
|
|
| 36.101 | 5191 | - | B | 15.3.0 | Rel-15 | Introduction of completed R16 2DL/2UL band combinations to TS 36.101 |
R4-1811271
| withdrawn | RAN4#88 | Huawei, HiSilicon |
| | | | | LTE_CA_R16_2BDL... |
|