|
|
| 36.133 | 6908 | 1 | B | 16.5.0 | Rel-16 | Applicability of 2-step RA and 4-step RA in RRM requirements in 36.133 |
R4-2008640
| agreed | RAN4#95-e | Ericsson |
RP-200969
| approved | RAN#88-e | RAN4 | 16.6.0 | NR_2step_RACH-Core |
|
|
|
| 36.133 | 6908 | - | B | 16.5.0 | Rel-16 | Applicability of 2-step RA and 4-step RA in RRM requirements in 36.133 |
R4-2008002
| revised | RAN4#95-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 37.340 | 0261 | 3 | F | 16.5.0 | Rel-16 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT |
R2-2106610
| agreed | RAN2#114-e | ZTE Corporation... |
RP-211471
| approved | RAN#92-e | RAN2 | 16.6.0 | LTE_NR_DC_CA_en... |
|
|
|
| 37.340 | 0261 | 2 | F | 16.5.0 | Rel-16 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT |
R2-2105859
| revised | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 37.340 | 0261 | 1 | F | 16.5.0 | Rel-16 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT, IAB |
R2-2104611
| revised | RAN2#113-bis-e | ZTE Corporation... |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 37.340 | 0261 | - | F | 16.5.0 | Rel-16 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT, IAB |
R2-2104015
| revised | RAN2#113-bis-e | ZTE Corporation... |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 38.104 | 0455 | - | A | 18.0.0 | Rel-18 | CR to 38.104: BS Conformance, FRC numbering alignment between BS specs |
R4-2301780
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.104 | 0454 | - | F | 17.8.0 | Rel-17 | CR to 38.104: BS Conformance, FRC numbering alignment between BS specs |
R4-2301779
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.104 | 0453 | - | F | 16.14.0 | Rel-16 | CR to 38.104: BS Conformance, FRC numbering alignment between BS specs |
R4-2301778
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0275 | - | A | 17.0.0 | Rel-17 | CR on correction 2-step RACH performance requirements for FR2 in 38.104 (Rel-17) |
R4-2101303
| agreed | RAN4#98-e | Huawei, HiSilic... |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0274 | 1 | F | 16.6.0 | Rel-16 | CR on correction 2-step RACH performance requirements for FR2 in 38.104 (Rel-16) |
R4-2103959
| agreed | RAN4#98-e | Huawei, HiSilic... |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0274 | - | F | 16.6.0 | Rel-16 | CR on correction 2-step RACH performance requirements for FR2 in 38.104 (Rel-16) |
R4-2101302
| revised | RAN4#98-e | Huawei, HiSilic... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0248 | 1 | B | 16.5.0 | Rel-16 | CR on BS demodulation requirements for 2-step RACH for FR2 |
R4-2017636
| agreed | RAN4#97-e | Huawei, HiSilicon |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0248 | - | B | 16.5.0 | Rel-16 | CR on BS demodulation requirements for 2-step RACH for FR2 |
R4-2015612
| revised | RAN4#97-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0245 | 2 | B | 16.5.0 | Rel-16 | CR to TS 38.104 BS demodulation requirements for 2-step RACH |
R4-2017666
| agreed | RAN4#97-e | ZTE Wistron Tel... |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0245 | 1 | B | 16.5.0 | Rel-16 | CR to TS 38.104 BS demodulation requirements for 2-step RACH |
R4-2017635
| revised | RAN4#97-e | ZTE Wistron Tel... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.104 | 0245 | - | B | 16.5.0 | Rel-16 | Draft CR to TS 38.104 BS demodulation requirements for 2-step RACH |
R4-2015177
| not pursued | RAN4#97-e | ZTE Wistron Tel... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 2281 | - | F | 17.4.0 | Rel-17 | Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 3 (Rel-17) |
R4-2207538
| agreed | RAN4#102-e | MCC, OPPO |
RP-220339
| approved | RAN#95-e | RAN4 | 17.5.0 | NR_Mob_enh-Perf... |
|
|
|
| 38.133 | 2280 | - | F | 16.10.0 | Rel-16 | Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 3 (Rel-16) |
R4-2207143
| agreed | RAN4#102-e | MCC, OPPO |
RP-220339
| approved | RAN#95-e | RAN4 | 16.11.0 | NR_Mob_enh-Perf... |
|
|
|
| 38.133 | 2244 | - | A | 17.3.0 | Rel-17 | Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 1 (Rel-17) |
R4-2120431
| agreed | RAN4#101-e | MCC, Nokia, Nok... |
RP-212847
| approved | RAN#94-e | RAN4 | 17.4.0 | NR_eMIMO, NR_Mo... |
|
|
|
| 38.133 | 2243 | - | F | 16.9.0 | Rel-16 | Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 1 (Rel-16) |
R4-2120430
| agreed | RAN4#101-e | MCC, Nokia, Nok... |
RP-212847
| approved | RAN#94-e | RAN4 | 16.10.0 | NR_eMIMO, NR_Mo... |
|
|
|
| 38.133 | 2233 | - | A | 17.3.0 | Rel-17 | Rel-17 Cat-A CR to RMC CORESET reference channel for test cases A.5.3.2.2.y |
R4-2119575
| endorsed | RAN4#101-e | Qualcomm Incorp... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 2232 | 1 | F | 16.9.0 | Rel-16 | Rel-16 Cat-F CR to RMC CORESET reference channel for test cases A.5.3.2.2.y |
R4-2120409
| endorsed | RAN4#101-e | Qualcomm Incorp... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 2232 | - | F | 16.9.0 | Rel-16 | Rel-16 Cat-F CR to RMC CORESET reference channel for test cases A.5.3.2.2.y |
R4-2119574
| revised | RAN4#101-e | Qualcomm Incorp... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1882 | - | A | 17.1.0 | Rel-17 | Correction on the power of the first preamble for 2-step RACH |
R4-2109272
| agreed | RAN4#99-e | Nokia, Nokia Sh... |
RP-211104
| approved | RAN#92-e | TSG WG RAN4 | 17.2.0 | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1881 | - | F | 16.7.0 | Rel-16 | Correction on the power of the first preamble for 2-step RACH |
R4-2109271
| agreed | RAN4#99-e | Nokia, Nokia Sh... |
RP-211104
| approved | RAN#92-e | TSG WG RAN4 | 16.8.0 | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1705 | - | A | 17.0.0 | Rel-17 | 2-step RACH RRM performance requirements corrections |
R4-2102278
| withdrawn | RAN4#98-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1704 | - | F | 16.6.0 | Rel-16 | 2-step RACH RRM performance requirements corrections |
R4-2102277
| withdrawn | RAN4#98-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1502 | - | A | 17.0.0 | Rel-17 | 2-step RACH RRM performance requirements corrections |
R4-2100581
| agreed | RAN4#98-e | Nokia, Nokia Sh... |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1501 | - | F | 16.6.0 | Rel-16 | 2-step RACH RRM performance requirements corrections |
R4-2100580
| agreed | RAN4#98-e | Nokia, Nokia Sh... |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1435 | - | A | 17.0.0 | Rel-17 | [CR] Applicability rule for 2-step RA (Cat A) |
R4-2100116
| withdrawn | RAN4#98-e | ZTE Corporation |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 1434 | - | F | 16.6.0 | Rel-16 | [CR] Applicability rule for 2-step RA |
R4-2100115
| merged | RAN4#98-e | ZTE Corporation |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 1214 | 1 | F | 16.5.0 | Rel-16 | CR Maintenance 2-step RACH RRM requirements |
R4-2017255
| agreed | RAN4#97-e | Nokia, Nokia Sh... |
RP-202431
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Core |
|
|
|
| 38.133 | 1214 | - | F | 16.5.0 | Rel-16 | CR Maintenance 2-step RACH RRM requirements |
R4-2014935
| revised | RAN4#97-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 1213 | 1 | B | 16.5.0 | Rel-16 | Big CR on 2-step RA type RRM performance requirements |
R4-2017253
| agreed | RAN4#97-e | Nokia, Nokia Sh... |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 1213 | - | B | 16.5.0 | Rel-16 | Big CR on 2-step RA type RRM performance requirements |
R4-2014933
| revised | RAN4#97-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.133 | 0924 | 1 | F | 16.4.0 | Rel-16 | Maintenance CR for 2-step RA |
R4-2012184
| agreed | RAN4#96-e | ZTE Corporation |
RP-201489
| approved | RAN#89-e | ETSI MCC | 16.5.0 | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0924 | - | F | 16.4.0 | Rel-16 | Maintenance CR for 2-step RA |
R4-2009686
| revised | RAN4#96-e | ZTE Corporation |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0871 | 1 | B | 16.3.0 | Rel-16 | Applicability of 2-step RA and 4-step RA in RRM requirements in 38.133 |
R4-2008639
| agreed | RAN4#95-e | Ericsson |
RP-200969
| approved | RAN#88-e | RAN4 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0871 | - | B | 16.3.0 | Rel-16 | Applicability of 2-step RA and 4-step RA in RRM requirements in 38.133 |
R4-2008001
| revised | RAN4#95-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0743 | 1 | B | 16.3.0 | Rel-16 | CR to 38.133 on UE transmit timing requirements for 2-step RACH |
R4-2008638
| agreed | RAN4#95-e | ZTE |
RP-200969
| approved | RAN#88-e | RAN4 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0743 | - | B | 16.3.0 | Rel-16 | CR to 38.133 on UE transmit timing requirements for 2-step RACH |
R4-2007653
| revised | RAN4#95-e | ZTE |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0678 | 1 | B | 16.3.0 | Rel-16 | CR to TS 38.133: introducing 2-step RACH core requirements |
R4-2008637
| agreed | RAN4#95-e | Nokia, Nokia Sh... |
RP-200969
| approved | RAN#88-e | RAN4 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.133 | 0678 | - | B | 16.3.0 | Rel-16 | CR to TS 38.133: introducing 2-step RACH core requirements |
R4-2006601
| revised | RAN4#95-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.141-1 | 0315 | - | A | 18.0.0 | Rel-18 | CR to 38.141-1: BS Conformance, FRC numbering alignment between BS specs |
R4-2301783
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.141-1 | 0314 | - | F | 17.8.0 | Rel-17 | CR to 38.141-1: BS Conformance, FRC numbering alignment between BS specs |
R4-2301782
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.141-1 | 0313 | - | F | 16.14.0 | Rel-16 | CR to 38.141-1: BS Conformance, FRC numbering alignment between BS specs |
R4-2301781
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0312 | - | A | 18.0.0 | Rel-18 | CR to 38.141-1: BS Demod Step size correction on 2-Step RACH (8.2.9) |
R4-2301758
| agreed | RAN4#106 | Keysight Techno... |
RP-230501
| approved | RAN#99 | RAN4 | 18.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0311 | - | A | 17.8.0 | Rel-17 | CR to 38.141-1: BS Demod Step size correction on 2-Step RACH (8.2.9) |
R4-2301757
| agreed | RAN4#106 | Keysight Techno... |
RP-230501
| approved | RAN#99 | RAN4 | 17.9.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0310 | - | F | 16.14.0 | Rel-16 | CR to 38.141-1: BS Demod Step size correction on 2-Step RACH R16 (8.2.9) |
R4-2301756
| agreed | RAN4#106 | Keysight Techno... |
RP-230501
| approved | RAN#99 | RAN4 | 16.15.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0257 | - | A | 17.3.0 | Rel-17 | Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT A) |
R4-2120818
| agreed | RAN4#101-e | MCC, Huawei |
RP-212847
| approved | RAN#94-e | RAN4 | 17.4.0 | NR_newRAT-Perf,... |
|
|
|
| 38.141-1 | 0256 | - | F | 16.9.0 | Rel-16 | Big CR for TS 38.141-1 Maintenance Demod part (Rel-16, CAT F) |
R4-2120817
| agreed | RAN4#101-e | MCC, Huawei |
RP-212847
| approved | RAN#94-e | RAN4 | 16.10.0 | NR_newRAT-Perf,... |
|
|
|
| 38.141-1 | 0204 | - | A | 17.0.0 | Rel-17 | Corrections on 2-step RACH demodulation requirements |
R4-2102280
| withdrawn | RAN4#98-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0203 | - | F | 16.6.0 | Rel-16 | Corrections on 2-step RACH demodulation requirements |
R4-2102279
| withdrawn | RAN4#98-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0186 | - | A | 17.0.0 | Rel-17 | CR on update applicability rule for 2-step RACH in 38.141-1 (Rel-17) |
R4-2101305
| agreed | RAN4#98-e | Huawei, HiSilicon |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0185 | 1 | F | 16.6.0 | Rel-16 | CR on update applicability rule for 2-step RACH in 38.141-1 (Rel-16) |
R4-2103871
| agreed | RAN4#98-e | Huawei, HiSilicon |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0185 | - | F | 16.6.0 | Rel-16 | CR on update applicability rule for 2-step RACH in 38.141-1 (Rel-16) |
R4-2101304
| revised | RAN4#98-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0177 | - | A | 17.0.0 | Rel-17 | Corrections on 2-step RACH demodulation requirements |
R4-2100583
| agreed | RAN4#98-e | Nokia, Nokia Sh... |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0176 | 1 | F | 16.6.0 | Rel-16 | Corrections on 2-step RACH demodulation requirements |
R4-2103869
| agreed | RAN4#98-e | Nokia, Nokia Sh... |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0176 | - | F | 16.6.0 | Rel-16 | Corrections on 2-step RACH demodulation requirements |
R4-2100582
| revised | RAN4#98-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0167 | 1 | B | 16.5.0 | Rel-16 | CR to 38.141-1 Introduction of test procedure and requirements for 2-step RACH |
R4-2017667
| agreed | RAN4#97-e | Ericsson |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0167 | - | B | 16.5.0 | Rel-16 | CR to 38.141-1 Introduction of test procedure and requirements for 2-step RACH |
R4-2017654
| revised | RAN4#97-e | Ericsson |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0154 | 1 | B | 16.5.0 | Rel-16 | Introduction of 2-step RACH FRC tables in 38.141-1 |
R4-2017637
| agreed | RAN4#97-e | Nokia, Nokia Sh... |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-1 | 0154 | - | B | 16.5.0 | Rel-16 | Introduction of 2-step RACH FRC tables in 38.141-1 |
R4-2014939
| revised | RAN4#97-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0461 | - | A | 18.0.0 | Rel-18 | CR to 38.141-2: BS Conformance, FRC numbering alignment between BS specs |
R4-2301786
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.141-2 | 0460 | - | F | 17.8.0 | Rel-17 | CR to 38.141-2: BS Conformance, FRC numbering alignment between BS specs |
R4-2301785
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-P... |
|
|
|
| 38.141-2 | 0459 | - | F | 16.14.0 | Rel-16 | CR to 38.141-2: BS Conformance, FRC numbering alignment between BS specs |
R4-2301784
| merged | RAN4#106 | Keysight Techno... |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0376 | - | A | 17.3.0 | Rel-17 | Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT A) |
R4-2120824
| agreed | RAN4#101-e | MCC, Intel |
RP-212850
| approved | RAN#94-e | RAN4 | 17.4.0 | NR_2step_RACH-P... |
|
|
|
| 38.141-2 | 0375 | - | F | 16.9.0 | Rel-16 | Big CR for TS 38.141-2 Maintenance Demod part (Rel-16, CAT F) |
R4-2120823
| agreed | RAN4#101-e | MCC, Intel |
RP-212850
| approved | RAN#94-e | RAN4 | 16.10.0 | NR_2step_RACH-P... |
|
|
|
| 38.141-2 | 0283 | - | A | 17.0.0 | Rel-17 | CR on update applicability rule for 2-step RACH in 38.141-2 (Rel-17) |
R4-2101307
| agreed | RAN4#98-e | Huawei, HiSilicon |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0282 | 1 | F | 16.6.0 | Rel-16 | CR on update applicability rule for 2-step RACH in 38.141-2 (Rel-16) |
R4-2103872
| agreed | RAN4#98-e | Huawei, HiSilicon |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0282 | - | F | 16.6.0 | Rel-16 | CR on update applicability rule for 2-step RACH in 38.141-2 (Rel-16) |
R4-2101306
| revised | RAN4#98-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0272 | - | A | 17.0.0 | Rel-17 | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
R4-2100932
| agreed | RAN4#98-e | Samsung |
RP-210073
| approved | RAN#91-e | RAN4 | 17.1.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0271 | 1 | F | 16.6.0 | Rel-16 | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
R4-2103870
| agreed | RAN4#98-e | Samsung |
RP-210073
| approved | RAN#91-e | RAN4 | 16.7.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0271 | - | F | 16.6.0 | Rel-16 | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
R4-2100931
| revised | RAN4#98-e | Samsung |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0258 | - | B | 16.5.0 | Rel-16 | CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
R4-2017653
| agreed | RAN4#97-e | Samsung |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0233 | 1 | B | 16.5.0 | Rel-16 | Introduction of test procedure and requirement for 2-step RACH |
R4-2017638
| withdrawn | RAN4#97-e | Ericsson |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0233 | - | B | 16.5.0 | Rel-16 | Introduction of test procedure and requirement for 2-step RACH |
R4-2015022
| not pursued | RAN4#97-e | Ericsson |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0231 | 1 | B | 16.5.0 | Rel-16 | CR to TS 38.141-2: BS demodulation requirements for 2-step RACH (Annex) |
R4-2017633
| agreed | RAN4#97-e | Intel Corporation |
RP-202415
| approved | RAN#90-e | RAN4 | 16.6.0 | NR_2step_RACH-Perf |
|
|
|
| 38.141-2 | 0231 | - | B | 16.5.0 | Rel-16 | CR to TS 38.141-2: BS demodulation requirements for 2-step RACH (Annex) |
R4-2014561
| revised | RAN4#97-e | Intel Corporation |
| | | | | NR_2step_RACH-Perf |
|
|
|
| 38.202 | 0009 | - | B | 15.5.0 | Rel-16 | Introduction of two-step RACH |
R1-1913625
| agreed | RAN1#99 | Qualcomm |
RP-192635
| approved | RAN#86 | RAN1 | 16.0.0 | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0071 | 1 | F | 16.5.0 | Rel-16 | Alignment of notation |
R1-2106347
| agreed | RAN1#105-e | Ericsson |
RP-211243
| approved | RAN#92-e | RAN1 | 16.6.0 | NR_unlic-Core, ... |
|
|
|
| 38.211 | 0071 | - | F | 16.5.0 | Rel-16 | Alignment of notation |
R1-2104123
| agreed | RAN1#104-bis-e | Ericsson |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.211 | 0068 | - | F | 16.4.0 | Rel-16 | Alignment of notation |
R1-2102232
| agreed | RAN1#104-e | Ericsson |
RP-210059
| approved | RAN#91-e | RAN1 | 16.5.0 | NR_eMIMO-Core, ... |
|
|
|
| 38.211 | 0064 | - | F | 16.3.0 | Rel-16 | Alignment CR for TS 38.211 |
R1-2009751
| agreed | RAN1#103-e | Ericsson |
RP-202398
| approved | RAN#90-e | RAN1 | 16.4.0 | NR_2step_RACH-C... |
|
|
|
| 38.211 | 0053 | - | F | 16.3.0 | Rel-16 | CR on the determination of DMRS sequences in 38.211 |
R1-2009445
| agreed | RAN1#103-e | Moderator (ZTE) |
RP-202380
| approved | RAN#90-e | RAN1 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0047 | - | F | 16.2.0 | Rel-16 | CR on 2-step RACH for 38.211 |
R1-2007236
| agreed | RAN1#102-e | Moderator (ZTE) |
RP-201804
| approved | RAN#89-e | RAN1 | 16.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0043 | 1 | F | 16.1.0 | Rel-16 | Corrections to two-step RACH |
R1-2005125
| agreed | RAN1#101-e | Ericsson |
RP-200686
| approved | RAN#88-e | RAN1 | 16.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0043 | - | F | 16.1.0 | Rel-16 | Corrections to two-step RACH |
R1-2003165
| revised | RAN1#100-bis-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0035 | - | F | 16.0.0 | Rel-16 | Corrections to two-step RACH |
R1-2001468
| agreed | RAN1#100-e | Ericsson |
RP-200184
| approved | RAN#87-e | RAN1 | 16.1.0 | NR_2step_RACH-Core |
|
|
|
| 38.211 | 0023 | - | B | 15.7.0 | Rel-16 | Introduction of two-step RACH |
R1-1913626
| agreed | RAN1#99 | Ericsson |
RP-192635
| approved | RAN#86 | RAN1 | 16.0.0 | NR_2step_RACH-Core |
|
|
|
| 38.212 | 0031 | - | B | 15.7.0 | Rel-16 | Introduction of two-step RACH |
R1-1913692
| agreed | RAN1#99 | Huawei |
RP-192635
| approved | RAN#86 | RAN1 | 16.0.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0537 | - | A | 18.0.0 | Rel-18 | Clarification of HARQ-ACK for MsgB PDSCH |
R1-2310685
| agreed | RAN1#114-bis | Moderator (CATT... |
RP-233727
| approved | RAN#102 | RAN1 | 18.1.0 | NR_2step_RACH-C... |
|
|
|
| 38.213 | 0536 | - | F | 17.7.0 | Rel-17 | Clarification of HARQ-ACK for MsgB PDSCH |
R1-2310684
| agreed | RAN1#114-bis | Moderator (CATT... |
RP-233727
| approved | RAN#102 | RAN1 | 17.8.0 | NR_2step_RACH-C... |
|
|
|
| 38.213 | 0483 | - | F | 17.5.0 | Rel-17 | Rel-17 editorial corrections for TS 38.213 |
R1-2304285
| agreed | RAN1#112-bis-e | Samsung |
RP-231226
| approved | RAN#100 | RAN1 | 17.6.0 | NR_FeMIMO-Core,... |
|
|
|
| 38.213 | 0464 | - | F | 16.13.0 | Rel-16 | Corrections on Channel Structure for 2-step RACH in Rel-16 |
R1-2303664
| not pursued | RAN1#112-bis-e | NEC Corporation |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0305 | - | A | 17.1.0 | Rel-17 | Correction on Rel-16 SRS power control with 2-step RACH |
R1-2205275
| agreed | RAN1#109-e | Moderator (Medi... |
RP-221619
| approved | RAN#96 | RAN1 | 17.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0304 | - | F | 16.9.0 | Rel-16 | Correction on Rel-16 SRS power control with 2-step RACH |
R1-2205274
| agreed | RAN1#109-e | Moderator (Medi... |
RP-221619
| approved | RAN#96 | RAN1 | 16.10.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0289 | - | A | 17.0.0 | Rel-17 | Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) |
R1-2202945
| agreed | RAN1#108-e | Samsung |
RP-220249
| approved | RAN#95-e | RAN1 | 17.1.0 | NR_2step_RACH-C... |
|
|
|
| 38.213 | 0288 | - | F | 16.8.0 | Rel-16 | Rel-16 editorial corrections for TS 38.213 |
R1-2202944
| agreed | RAN1#108-e | Samsung |
RP-220249
| approved | RAN#95-e | RAN1 | 16.9.0 | NR_2step_RACH-C... |
|
|
|
| 38.213 | 0267 | 1 | F | 16.7.0 | Rel-16 | Rel-16 editorial corrections for TS 38.213 |
R1-2112870
| agreed | RAN1#107-e | Samsung |
RP-212964
| approved | RAN#94-e | RAN1 | 16.8.0 | 5G_V2X_NRSL-Cor... |
|
|
|
| 38.213 | 0267 | - | F | 16.7.0 | Rel-16 | Rel-16 editorial corrections for TS 38.213 |
R1-2112865
| revised | RAN1#107-e | Samsung |
| | | | | 5G_V2X_NRSL-Cor... |
|
|
|
| 38.213 | 0184 | - | F | 16.4.0 | Rel-16 | CR on transmission timing adjustment procedure in 38.213 |
R1-2101965
| agreed | RAN1#104-e | Moderator (ZTE)... |
RP-210048
| approved | RAN#91-e | RAN1 | 16.5.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0176 | - | F | 16.3.0 | Rel-16 | Alignment CR for TS 38.213 |
R1-2009742
| agreed | RAN1#103-e | Samsung |
RP-202398
| approved | RAN#90-e | RAN1 | 16.4.0 | NR_2step_RACH-C... |
|
|
|
| 38.213 | 0147 | - | F | 16.3.0 | Rel-16 | CR on 2-step RACH for 38.213 |
R1-2009446
| agreed | RAN1#103-e | Moderator (ZTE) |
RP-202380
| approved | RAN#90-e | RAN1 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0127 | - | F | 16.2.0 | Rel-16 | CR on 2-step RACH for 38.213 |
R1-2007237
| agreed | RAN1#102-e | Moderator (ZTE) |
RP-201804
| approved | RAN#89-e | RAN1 | 16.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0112 | 1 | F | 16.1.0 | Rel-16 | Corrections on two-step RACH |
R1-2005148
| agreed | RAN1#101-e | Samsung |
RP-200686
| approved | RAN#88-e | RAN1 | 16.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0112 | - | F | 16.1.0 | Rel-16 | Corrections on two-step RACH |
R1-2003184
| revised | RAN1#100-bis-e | Samsung |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0085 | - | F | 16.0.0 | Rel-16 | Corrections on two-step RACH |
R1-2001450
| agreed | RAN1#100-e | Samsung |
RP-200184
| approved | RAN#87-e | RAN1 | 16.1.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0070 | 1 | B | 15.7.0 | Rel-16 | Introduction of two-step RACH in NR |
| | | |
RP-193121
| approved | RAN#86 | Samsung | 16.0.0 | NR_2step_RACH-Core |
|
|
|
| 38.213 | 0070 | - | B | 15.7.0 | Rel-16 | Introduction of two-step RACH |
R1-1913627
| agreed | RAN1#99 | Samsung |
RP-192635
| revised | RAN#86 | RAN1 | | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0317 | - | A | 17.2.0 | Rel-17 | Correction on parallel transmission of MsgA and other channels in TS 38.214 |
R1-2208103
| agreed | RAN1#110 | Moderator (ZTE) |
RP-222419
| approved | RAN#97-e | RAN1 | 17.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0306 | - | F | 16.10.0 | Rel-16 | Correction on parallel transmission of MsgA and other channels in TS 38.214 |
R1-2208037
| agreed | RAN1#110 | Moderator (ZTE) |
RP-222419
| approved | RAN#97-e | RAN1 | 16.11.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0215 | - | F | 16.6.0 | Rel-16 | Rel-16 editorial corrections for TS 38.214 |
R1-2108596
| agreed | RAN1#106-e | Nokia, Nokia Sh... |
RP-211850
| approved | RAN#93-e | RAN1 | 16.7.0 | 5G_V2X_NRSL-Cor... |
|
|
|
| 38.214 | 0157 | - | F | 16.4.0 | Rel-16 | CR on DMRS configuration for MsgA in 38.214 |
R1-2101964
| agreed | RAN1#104-e | Moderator (ZTE)... |
RP-210048
| approved | RAN#91-e | RAN1 | 16.5.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0154 | - | F | 16.3.0 | Rel-16 | Alignment of RRC parameter names for 38.214 |
R1-2009778
| agreed | RAN1#103-e | Nokia, Nokia Sh... |
RP-202398
| approved | RAN#90-e | RAN1 | 16.4.0 | NR_2step_RACH-C... |
|
|
|
| 38.214 | 0117 | - | F | 16.2.0 | Rel-16 | CR on 2-step RACH for 38.214 |
R1-2007238
| agreed | RAN1#102-e | Moderator (ZTE) |
RP-201804
| approved | RAN#89-e | RAN1 | 16.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0086 | 1 | F | 16.1.0 | Rel-16 | Correction of two-step RACH |
R1-2005153
| agreed | RAN1#101-e | Nokia, Nokia Sh... |
RP-200686
| approved | RAN#88-e | RAN1 | 16.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0086 | - | F | 16.1.0 | Rel-16 | Correction of two-step RACH |
R1-2003139
| revised | RAN1#100-bis-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0075 | - | F | 16.0.0 | Rel-16 | Corrections on two-step RACH after RAN1#100-e |
R1-2001448
| agreed | RAN1#100-e | Nokia |
RP-200184
| approved | RAN#87-e | RAN1 | 16.1.0 | NR_2step_RACH-Core |
|
|
|
| 38.214 | 0050 | - | B | 15.7.0 | Rel-16 | Introduction of two-step RACH |
R1-1913628
| agreed | RAN1#99 | Nokia |
RP-192635
| approved | RAN#86 | RAN1 | 16.0.0 | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0705 | - | A | 17.5.0 | Rel-17 | Stage2 correction on UE Identities |
R2-2308743
| agreed | RAN2#123 | Huawei, Nokia (... |
RP-232566
| approved | RAN#101 | RAN2 | 17.6.0 | NR_2step_RACH-C... |
|
|
|
| 38.300 | 0704 | - | F | 16.13.0 | Rel-16 | Stage2 correction on UE Identities |
R2-2308742
| agreed | RAN2#123 | Huawei, Nokia (... |
RP-232566
| approved | RAN#101 | RAN2 | 16.14.0 | NR_2step_RACH-C... |
|
|
|
| 38.300 | 0395 | - | F | 16.7.0 | Rel-16 | Correction to 38300 on 2step CFRA configuration |
R2-2110732
| not pursued | RAN2#116-e | ZTE Corporation... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0343 | - | F | 16.4.0 | Rel-16 | Correction on uplink transmission allowed without TA |
R2-2101813
| agreed | RAN2#113-e | Huawei, HiSilic... |
RP-210689
| approved | RAN#91-e | RAN2 | 16.5.0 | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0259 | - | F | 16.2.0 | Rel-16 | Missing RACH Figure |
R2-2006817
| agreed | RAN2#111-e | Nokia (Rapporte... |
RP-201928
| approved | RAN#89-e | RAN2 | 16.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0233 | - | F | 16.1.0 | Rel-16 | 4-step RA type description |
R2-2004879
| withdrawn | RAN2#110-e | Nokia (rapporte... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0214 | 1 | F | 16.1.0 | Rel-16 | 4-step RA type figure description |
R2-2004882
| agreed | RAN2#110-e | Nokia (rapporte... |
RP-201173
| approved | RAN#88-e | RAN2 | 16.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0214 | - | F | 16.1.0 | Rel-16 | 4-step RA type description |
R2-2003009
| revised | RAN2#109-bis-e | Nokia (rapporte... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0197 | 1 | B | 16.0.0 | Rel-16 | Introduction of 2-step RACH |
R2-2002348
| agreed | RAN2#109-e | Nokia (rapporte... |
RP-200342
| approved | RAN#87-e | RAN2 | 16.1.0 | NR_2step_RACH-Core |
|
|
|
| 38.300 | 0197 | - | B | 16.0.0 | Rel-16 | Stage-2 running CR for 2-step RACH |
R2-2000942
| revised | RAN2#109-e | Nokia (rapporte... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.306 | 1039 | 1 | A | 18.0.0 | Rel-18 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r18) |
R2-2401521
| postponed | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 1039 | - | A | 18.0.0 | Rel-18 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r18) |
R2-2401028
| revised | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 1038 | 1 | A | 17.7.0 | Rel-17 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r17) |
R2-2401520
| postponed | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 1038 | - | A | 17.7.0 | Rel-17 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r17) |
R2-2401027
| revised | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 1037 | 1 | F | 16.15.0 | Rel-16 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16 (r16) |
R2-2401519
| postponed | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 1037 | - | F | 16.15.0 | Rel-16 | Clarification on the parallelTxMsgA-SRS-PUCCH-PUSCH-r16(r16) |
R2-2401026
| revised | RAN2#125 | ZTE Corporation... |
| | | | | NR_2step_RACH |
|
|
|
| 38.306 | 0422 | 1 | B | 16.2.0 | Rel-16 | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
R2-2010851
| agreed | RAN2#112-e | Intel Corporation |
RP-202778
| approved | RAN#90-e | RAN2 | 16.3.0 | NR_UE_pow_sav-C... |
|
|
|
| 38.306 | 0422 | - | B | 16.2.0 | Rel-16 | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
R2-2009278
| revised | RAN2#112-e | Intel Corporation |
| | | | | NR_UE_pow_sav-C... |
|
|
|
| 38.306 | 0370 | 2 | B | 16.1.0 | Rel-16 | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 corrections |
R2-2008638
| agreed | RAN2#111-e | Intel Corporati... |
RP-201932
| approved | RAN#89-e | RAN2 | 16.2.0 | TEI16, NR_CLI_R... |
|
|
|
| 38.306 | 0370 | 1 | B | 16.1.0 | Rel-16 | Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
R2-2008119
| revised | RAN2#111-e | Intel Corporati... |
| | | | | TEI16, NR_CLI_R... |
|
|
|
| 38.306 | 0370 | - | B | 16.1.0 | Rel-16 | Rel-16 UE capabilities based on RAN1 and RAN4 feature lists and RAN2 corrections |
R2-2006938
| revised | RAN2#111-e | Intel Corporati... |
| | | | | NR_UE_pow_sav, ... |
|
|
|
| 38.306 | 0364 | - | F | 16.1.0 | Rel-16 | Clarification on 2-step RACH capability |
R2-2006577
| merged | RAN2#111-e | vivo |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.306 | 0349 | - | B | 16.0.0 | Rel-16 | Clarification for 4-step RACH CSI-RS capability |
R2-2006034
| merged | RAN2#110-e | ZTE Corporation... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.306 | 0329 | 2 | B | 16.0.0 | Rel-16 | Release-16 UE capabilities based on RAN1, RAN4 feature lists and RAN2 |
| | | |
RP-201217
| approved | RAN#88-e | NTT DOCOMO, INC... | 16.1.0 | NR_UE_pow_sav, ... |
|
|
|
| 38.306 | 0329 | 1 | B | 16.0.0 | Rel-16 | Release-16 UE capabilities for RAN1 and RAN4 feature list |
R2-2005818
| agreed | RAN2#110-e | Intel Corporati... |
| | | | | NR_UE_pow_sav, ... |
|
|
|
| 38.306 | 0329 | - | B | 16.0.0 | Rel-16 | Release-16 UE capabilities for RAN1 and RAN4 feature list |
R2-2005314
| revised | RAN2#110-e | Intel Corporati... |
| | | | | NR_UE_pow_sav, ... |
|
|
|
| 38.321 | 1663 | - | F | 17.6.0 | Rel-17 | MAC correction related to PDCCH monitoring-r17 |
R2-2309617
| | RAN2#123-bis | Huawei, HiSilicon |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 1662 | - | F | 16.13.0 | Rel-16 | MAC correction related to PDCCH monitoring-r16 |
R2-2309616
| postponed | RAN2#123-bis | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1516 | - | A | 17.3.0 | Rel-17 | NRU and 2Step RA Corrections on Rel-17 MAC |
R2-2300493
| | RAN2#121 | vivo |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.321 | 1515 | - | F | 16.11.0 | Rel-16 | NRU and 2Step RA Corrections on Rel-16 MAC |
R2-2300490
| | RAN2#121 | vivo |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.321 | 1376 | - | A | 17.1.0 | Rel-17 | Correction on RA Resource Selection in Rel-17 |
R2-2208263
| not pursued | RAN2#119-e | vivo |
| | | | | NR_newRAT-Core,... |
|
|
|
| 38.321 | 1375 | - | F | 16.9.0 | Rel-16 | Correction on RA Resource Selection in Rel-16 |
R2-2208261
| not pursued | RAN2#119-e | vivo |
| | | | | NR_newRAT-Core,... |
|
|
|
| 38.321 | 1350 | - | A | 17.1.0 | Rel-17 | Clarification on the matching TB size for 2-step RA |
R2-2207899
| not pursued | RAN2#119-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1349 | - | F | 16.9.0 | Rel-16 | Clarification on the matching TB size for 2-step RA |
R2-2207898
| not pursued | RAN2#119-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1178 | - | F | 16.6.0 | Rel-16 | Correction to MsgA and Msg3 retransmission overlapping with another bundle retransmission |
R2-2111231
| not pursued | RAN2#116-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 1172 | - | F | 16.6.0 | Rel-16 | Correction on downlink pathloss reference for 2-step RACH |
R2-2110763
| not pursued | RAN2#116-e | Qualcomm Incorp... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1153 | - | F | 16.5.0 | Rel-16 | Correction to MsgA grant overlapping with another UL grant for a HARQ process |
R2-2108603
| postponed | RAN2#115-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1112 | - | F | 16.4.0 | Rel-16 | Correction to 38.321 on msga-TransMax selection for 2-step RACH |
R2-2105851
| agreed | RAN2#114-e | ZTE Corporation... |
RP-211471
| approved | RAN#92-e | RAN2 | 16.5.0 | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1089 | - | F | 16.4.0 | Rel-16 | Correction to RA-RNTI generation for 2-step RA |
R2-2103534
| not pursued | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1055 | - | F | 16.3.0 | Rel-16 | Conditions to stop an ongoing RA procedure |
R2-2101857
| not pursued | RAN2#113-e | Asia Pacific Te... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1054 | - | F | 16.3.0 | Rel-16 | Conditions to stop an ongoing RA procedure |
R2-2101838
| withdrawn | RAN2#113-e | Asia Pacific Te... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1037 | 2 | F | 16.3.0 | Rel-16 | Correction on available UL-SCH resource |
R2-2102513
| agreed | RAN2#113-e | LG Electronics Inc. |
RP-210689
| approved | RAN#91-e | RAN2 | 16.4.0 | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1037 | 1 | F | 16.3.0 | Rel-16 | Correction on available UL-SCH resource |
R2-2102079
| revised | RAN2#113-e | LG Electronics Inc. |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1037 | - | F | 16.3.0 | Rel-16 | 38321 CR Correction on available UL-SCH resource |
R2-2101512
| revised | RAN2#113-e | LG Electronics Inc. |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1016 | - | F | 16.3.0 | Rel-16 | Correction on UL-SCH resource in 2-step RA procedure |
R2-2100350
| not pursued | RAN2#113-e | vivo |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 1015 | - | F | 16.3.0 | Rel-16 | Correction on Usage of RA-RNTI in 2-step RA procedure |
R2-2100349
| not pursued | RAN2#113-e | vivo |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0982 | 1 | F | 16.2.1 | Rel-16 | Correction on DELTA_PREAMBLE and parameters for 2-step RA |
R2-2011005
| agreed | RAN2#112-e | Huawei, HiSilic... |
RP-202771
| approved | RAN#90-e | RAN2 | 16.3.0 | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0982 | - | F | 16.2.1 | Rel-16 | Correction on DELTA_PREAMBLE for 2-step RA |
R2-2010405
| revised | RAN2#112-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0981 | 1 | F | 16.3.0 | Rel-16 | Correction on BSR for two-step RA |
R2-2101811
| not pursued | RAN2#113-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0981 | - | F | 16.2.1 | Rel-16 | Correction on BSR for two-step RA |
R2-2010402
| revised | RAN2#112-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0953 | - | F | 16.2.1 | Rel-16 | 2-step RA parameter corrections |
R2-2009969
| | RAN2#112-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0943 | - | F | 16.2.1 | Rel-16 | Clarification on the PRACH occasion frequency domain index |
R2-2009794
| not pursued | RAN2#112-e | Nokia, Nokia Sh... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0841 | - | F | 16.1.0 | Rel-16 | Correction to description of MAC subheader for msgB |
R2-2007825
| not pursued | RAN2#111-e | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0769 | 2 | F | 16.1.0 | Rel-16 | Miscellaneous corrections |
R2-2008450
| agreed | RAN2#111-e | Samsung, LG Ele... |
RP-201932
| approved | RAN#89-e | RAN2 | 16.2.0 | TEI16, LTE_NR_D... |
|
|
|
| 38.321 | 0769 | 1 | F | 16.1.0 | Rel-16 | Miscellaneous corrections |
R2-2007717
| revised | RAN2#111-e | Samsung |
| | | | | TEI16, LTE_NR_D... |
|
|
|
| 38.321 | 0769 | - | F | 16.1.0 | Rel-16 | Miscellaneous corrections |
R2-2006659
| revised | RAN2#111-e | Samsung |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 38.321 | 0725 | - | F | 16.0.0 | Rel-16 | Correction of Handling of invalid POs for MsgA transmissions |
R2-2003362
| not treated | RAN2#109-bis-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0722 | - | F | 16.0.0 | Rel-16 | Change LCID to eLCID for Absolute Timing Advance Command |
R2-2003357
| not treated | RAN2#109-bis-e | Ericsson |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.321 | 0714 | 5 | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2006323
| agreed | RAN2#110-e | ZTE (CR editor)... |
RP-201172
| approved | RAN#88-e | RAN2 | 16.1.0 | NR_unlic-Core, ... |
|
|
|
| 38.321 | 0714 | 4 | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2006027
| revised | RAN2#110-e | ZTE (CR editor)... |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.321 | 0714 | 3 | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2006019
| revised | RAN2#110-e | ZTE (CR editor)... |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.321 | 0714 | 2 | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2004617
| revised | RAN2#110-e | ZTE (CR editor)... |
| | | | | NR_unlic-Core, ... |
|
|
|
| 38.321 | 0714 | 1 | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2003962
| revised | RAN2#109-bis-e | ZTE (CR editor)... |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 0714 | - | F | 16.0.0 | Rel-16 | Updates to MAC spec for 2-step RACH |
R2-2002965
| revised | RAN2#109-bis-e | ZTE (CR editor)... |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 0692 | 3 | B | 15.8.0 | Rel-16 | Introduction of 2-step RACH in 38.321 |
R2-2002413
| agreed | RAN2#109-e | ZTE Corporation... |
RP-200342
| approved | RAN#87-e | RAN2 | 16.0.0 | NR_2step_RACH-C... |
|
|
|
| 38.321 | 0692 | 2 | B | 15.8.0 | Rel-16 | Introduction of 2-step RACH in 38.321 |
R2-2002379
| revised | RAN2#109-e | ZTE Corporation... |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 0692 | 1 | B | 15.8.0 | Rel-16 | Running MAC CR for 2-step RACH |
R2-2002202
| revised | RAN2#109-e | ZTE Corporation... |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.321 | 0692 | - | B | 15.8.0 | Rel-16 | Running MAC CR for 2-step RACH |
R2-2000997
| revised | RAN2#109-e | ZTE Corporation... |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.331 | 4308 | - | F | 17.6.0 | Rel-17 | Correction on the msgB-ResponseWindow configuration-r17 |
R2-2309619
| | RAN2#123-bis | Huawei, HiSilicon |
| | | | | NR_2step_RACH-C... |
|
|
|
| 38.331 | 4307 | - | F | 16.14.0 | Rel-16 | Correction on the msgB-ResponseWindow configuration-r16 |
R2-2309618
| postponed | RAN2#123-bis | Huawei, HiSilicon |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.331 | 3467 | - | F | 17.1.0 | Rel-17 | MsgA PUSCH resource release upon T304 expiry for SCG |
R2-2208983
| agreed | RAN2#119-e | Samsung |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_2step_RACH-C... |
|
|
|
| 38.331 | 3424 | 1 | A | 17.1.0 | Rel-17 | Correction for PUSCH-PowerControl field descriptions for 2-step RACH |
R2-2209076
| agreed | RAN2#119-e | MediaTek Inc. |
RP-222519
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_2step_RACH-Core |
|
|
|
| 38.331 | 3424 | - | A | 17.1.0 | Rel-17 | Correction for field description on PUSCH |
R2-2208476
| revised | RAN2#119-e | MediaTek Beijin... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.331 | 3423 | 1 | F | 16.9.0 | Rel-16 | Correction for PUSCH-PowerControl field descriptions for 2-step RACH |
R2-2209075
| agreed | RAN2#119-e | MediaTek Inc. |
RP-222519
| approved | RAN#97-e | RAN2 | 16.10.0 | NR_2step_RACH-Core |
|
|
|
| 38.331 | 3423 | - | F | 16.9.0 | Rel-16 | Correction for field description on PUSCH |
R2-2208474
| revised | RAN2#119-e | MediaTek Beijin... |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.331 | 2814 | 1 | F | 16.6.0 | Rel-16 | Correction on msgA-SubcarrierSpacing |
R2-2111622
| agreed | RAN2#116-e | vivo, Samsung |
RP-213343
| approved | RAN#94-e | RAN2 | 16.7.0 | NR_2step_RACH-Core |
|
|
|
| 38.331 | 2814 | - | F | 16.6.0 | Rel-16 | Correction on msgA-SubcarrierSpacing |
R2-2109445
| revised | RAN2#116-e | vivo, Samsung |
| | | | | NR_2step_RACH-Core |
|
|
|
| 38.331 | 2760 | - | F | 16.5.0 | Rel-16 | Correction to 38.331 on the field description of msgA-TransMax |
R2-2108268
| agreed | RAN2#115-e | ZTE Corporation... |
RP-212442
| approved | RAN#93-e | RAN2 | 16.6.0 | NR_2step_RACH-Core |
|
|
|
| 38.331 | 2728 | 1 | F | 16.5.0 | Rel-16 | Correction to description of p0-AlphaSets |
R2-2109071
| agreed | RAN2#115-e | ZTE Corporation... |
RP-212442
| approved | RAN#93-e | RAN2 | 16.6.0 | NR_2step_RACH-Core |
|