|
| 29.303 | 0128 | 1 | B | 16.2.0 | Rel-16 | DNS-based Service Discovery for W1AP |
C4-203422
| postponed | CT4#98-e | Orange |
| | | | | LTE_NR_arch_evo_enh |
|
|
| 29.303 | 0128 | - | B | 16.2.0 | Rel-16 | DNS-based Service Discovery for W1AP |
C4-203409
| revised | CT4#98-e | Orange |
| | | | | LTE_NR_arch_evo_enh |
|
|
| 36.401 | 0090 | 8 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-222576
| agreed | RAN3#115-e | Ericsson, Huawe... |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 7 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-221586
| revised | RAN3#115-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 6 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-221173
| endorsed | RAN3#114-bis-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 5 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-220017
| revised | RAN3#114-bis-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 4 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-214636
| revised | RAN3#114-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 3 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-214487
| revised | RAN3#113-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 2 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-213167
| revised | RAN3#113-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | 1 | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-212859
| revised | RAN3#112-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0090 | - | B | 16.0.0 | Rel-17 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-212835
| revised | RAN3#112-e | Ericsson, Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 36.401 | 0089 | - | B | 16.0.0 | Rel-17 | CR to 36.401 on the introduction of eNB CP-UP separation |
R3-212024
| | RAN3#112-e | Huawei, China Unicom |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0096 | 1 | F | 17.6.0 | Rel-17 | Correction on Bearer Context Status Change |
R3-237761
| agreed | RAN3#122 | Huawei, China U... |
RP-233852
| approved | RAN#102 | RAN3 | 17.7.0 | LTE_NR_arch_evo... |
|
|
| 37.483 | 0096 | - | F | 17.6.0 | Rel-18 | Correction on Bearer Context Status Change |
R3-237728
| revised | RAN3#122 | Huawei, China U... |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0091 | 2 | F | 18.2.0 | Rel-18 | PDCP version information over the E1 interface |
R3-244608
| noted | RAN3#125 | Samsung |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0091 | 1 | F | 18.1.0 | Rel-18 | PDCP version information over the E1 interface |
R3-243757
| revised | RAN3#124 | Samsung |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0091 | - | F | 17.6.0 | Rel-17 | PDCP version information over the E1 interface |
R3-237548
| revised | RAN3#122 | Samsung |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0060 | 2 | F | 17.4.0 | Rel-17 | Correction of RAT type in Data Usage Report List for Rel-17 |
R3-232599
| agreed | RAN3#120 | Huawei, Deutsch... |
RP-231068
| approved | RAN#100 | RAN3 | 17.5.0 | LTE_NR_arch_evo... |
|
|
| 37.483 | 0060 | 1 | F | 17.4.0 | Rel-17 | Correction of RAT type in Data Usage Report List for Rel-17 |
R3-231988
| revised | RAN3#119-bis-e | Huawei, Deutsch... |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0060 | - | F | 17.4.0 | Rel-17 | Correction of RAT type in Data Usage Report List for Rel-17 |
R3-231668
| revised | RAN3#119-bis-e | Huawei, Deutsch... |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0047 | - | A | 17.2.0 | Rel-17 | Restriction of NIA0 algorithm in gNB-CU-UP |
R3-226506
| withdrawn | RAN3#118 | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 37.483 | 0005 | 1 | F | 17.0.0 | Rel-17 | Correction on enhanced eNB architecture evolution |
R3-223772
| agreed | RAN3#116-e | Huawei |
RP-221140
| approved | RAN#96 | RAN3 | 17.1.0 | LTE_NR_arch_evo... |
|
|
| 37.483 | 0005 | - | F | 17.0.0 | Rel-17 | Correction on enhanced eNB architecture evolution |
R3-223238
| revised | RAN3#116-e | Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0186 | - | B | 16.7.0 | Rel-17 | Use of node ID in eNB |
R3-215090
| withdrawn | RAN3#114-e | Huawei, Telecom... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0185 | - | B | 16.7.0 | Rel-17 | Correction on enhanced eNB architecture evolution |
R3-215089
| withdrawn | RAN3#114-e | Huawei, Telecom... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 7 | B | 16.8.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-222574
| agreed | RAN3#115-e | Ericsson, Huawe... |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 6 | B | 16.8.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-221536
| revised | RAN3#115-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 5 | B | 16.8.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-220043
| endorsed | RAN3#114-bis-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 4 | B | 16.7.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-216240
| revised | RAN3#114-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 3 | B | 16.7.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-214623
| revised | RAN3#114-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 2 | B | 16.6.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-213168
| revised | RAN3#113-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | 1 | B | 16.5.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-212860
| revised | RAN3#112-e | Ericsson, Huawe... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0178 | - | B | 16.5.0 | Rel-17 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-212836
| revised | RAN3#112-e | Ericsson, Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.401 | 0177 | - | B | 16.5.0 | Rel-17 | CR to 38.401 on the introduction of ng-eNB CP-UP separation |
R3-212023
| | RAN3#112-e | Huawei, CMCC, C... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | 5 | B | 16.3.0 | Rel-17 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-222575
| agreed | RAN3#115-e | Ericsson |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | 4 | B | 16.3.0 | Rel-17 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-221514
| revised | RAN3#115-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | 3 | B | 16.3.0 | Rel-17 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-220016
| endorsed | RAN3#114-bis-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | 2 | B | 16.3.0 | Rel-17 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution |
R3-214632
| revised | RAN3#114-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | 1 | B | 16.3.0 | Rel-17 | Transport of UP data - Introduction of E-UTRA PDCP in NR UP protocol |
R3-214347
| revised | RAN3#113-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.425 | 0124 | - | B | 16.3.0 | Rel-17 | Transport of UP data - Introduction of E-UTRA PDCP in NR UP protocol |
R3-213877
| revised | RAN3#113-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0054 | 3 | F | 16.4.0 | Rel-17 | E1 TS 38.460 specification transfer to TS 37.480 |
R3-222747
| agreed | RAN3#115-e | Nokia, Nokia Sh... |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.460 | 0054 | 2 | F | 16.4.0 | Rel-17 | E1 TS 38.460 specification transfer to TS 37.480 |
R3-221636
| revised | RAN3#115-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0054 | 1 | F | 16.4.0 | Rel-17 | E1 TS 38.460 specification transfer to TS 37.480 |
R3-221108
| endorsed | RAN3#114-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0054 | - | D | 16.4.0 | Rel-17 | E1 TS 38.460 specification transfer to TS 37.480 |
R3-220852
| revised | RAN3#114-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 7 | B | 16.4.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-220044
| endorsed | RAN3#114-bis-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 6 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-216241
| revised | RAN3#114-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 5 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-214637
| revised | RAN3#114-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 4 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-214488
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 3 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-213176
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 2 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-212938
| revised | RAN3#112-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | 1 | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-212885
| revised | RAN3#112-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0050 | - | B | 16.3.0 | Rel-17 | Further discussions on logical entities and corresponding definitions |
R3-212825
| revised | RAN3#112-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0046 | 1 | B | 16.3.0 | Rel-17 | General principles for eNB CP-UP separation |
R3-212196
| | RAN3#112-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.460 | 0046 | - | B | 16.2.0 | Rel-17 | General principles for eNB CP-UP separation |
R3-210756
| revised | RAN3#111-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.461 | 0003 | 3 | F | 16.0.0 | Rel-17 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series |
R3-222716
| agreed | RAN3#115-e | Intel Corporation |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.461 | 0003 | 2 | F | 16.0.0 | Rel-17 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series |
R3-221638
| revised | RAN3#115-e | Intel Corporation |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.461 | 0003 | 1 | F | 16.0.0 | Rel-17 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series |
R3-221116
| endorsed | RAN3#114-bis-e | Intel Corporation |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.461 | 0003 | - | F | 16.0.0 | Rel-17 | Transfer of Rel-17 E1 interface specification from 38.46x series to 37.48x series |
R3-220843
| revised | RAN3#114-bis-e | Intel Corporation |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0018 | 3 | F | 16.1.0 | Rel-17 | Transfer of E1 interface specification from 38-series to 37-series |
R3-222734
| agreed | RAN3#115-e | Huawei |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.462 | 0018 | 2 | F | 16.1.0 | Rel-17 | Transfer of E1 interface specification from 38-series to 37-series |
R3-221637
| revised | RAN3#115-e | Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0018 | 1 | F | 16.1.0 | Rel-17 | Transfer of E1 interface specification from 38-series to 37-series |
R3-221109
| endorsed | RAN3#114-bis-e | Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0018 | - | F | 16.1.0 | Rel-17 | Transfer of E1 interface specification from 38-series to 37-series |
R3-220918
| revised | RAN3#114-bis-e | Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | 5 | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-220018
| endorsed | RAN3#114-bis-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | 4 | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-214638
| revised | RAN3#114-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | 3 | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-214489
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | 2 | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-213166
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | 1 | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-212827
| revised | RAN3#112-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0017 | - | B | 16.1.0 | Rel-17 | CR to 38.462 on the introduction of new interface |
R3-212026
| revised | RAN3#112-e | Huawei |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0016 | 1 | B | 16.1.0 | Rel-17 | E1 Signaling Transport for eNB CP-UP separation |
R3-212197
| | RAN3#112-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.462 | 0016 | - | B | 16.1.0 | Rel-17 | E1 Signaling Transport for eNB CP-UP separation |
R3-210757
| revised | RAN3#111-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0665 | 2 | F | 16.8.0 | Rel-17 | E1AP specification transfer to TS 37.483 |
R3-221639
| agreed | RAN3#115-e | Ericsson |
RP-220217
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_arch_evo... |
|
|
| 38.463 | 0665 | 1 | F | 16.8.0 | Rel-17 | E1AP specification transfer to TS 37.483 |
R3-221118
| endorsed | RAN3#114-bis-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0665 | - | D | 16.8.0 | Rel-17 | E1AP specification transfer to TS 37.483 |
R3-220635
| revised | RAN3#114-bis-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0606 | 5 | B | 16.8.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-220019
| endorsed | RAN3#114-bis-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0606 | 4 | B | 16.7.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-214639
| revised | RAN3#114-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0606 | 3 | B | 16.6.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-214490
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0606 | 2 | B | 16.6.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-213165
| revised | RAN3#113-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo_enh |
|
|
| 38.463 | 0606 | 1 | B | 16.5.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-212826
| revised | RAN3#112-e | Huawei, Ericsson |
| | | | | LTE_NR_arch_evo_enh |
|
|
| 38.463 | 0606 | - | B | 16.5.0 | Rel-17 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB |
R3-212528
| revised | RAN3#112-e | Huawei |
| | | | | LTE_NR_arch_evo_enh |
|
|
| 38.463 | 0578 | 1 | B | 16.5.0 | Rel-17 | E1 changes needed for eNB CP-UP separation |
R3-212198
| | RAN3#112-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|
|
| 38.463 | 0578 | - | B | 16.4.0 | Rel-17 | E1 changes needed for eNB CP-UP separation |
R3-210759
| revised | RAN3#111-e | Ericsson |
| | | | | LTE_NR_arch_evo... |
|