|
|
| 36.300 | 1439 | - | D | 19.0.0 | Rel-19 | Clarification on inter-freq neighbor cell meas for IOT NTN TDD |
R2-2508131
| | RAN2#132 | Iridium Satelli... |
| | | | | IoT_NTN_TDD-Core |
|
|
|
| 36.300 | 1438 | - | B | 19.0.0 | Rel-19 | Introduction of TN to IoT NTN redirection [IoT-TN-NTN-redir] |
R2-2507921
| endorsed | RAN2#131bis | Samsung, Google... |
| | | | | TEI19 |
|
|
|
| 36.300 | 1437 | 2 | B | 19.0.0 | Rel-19 | Introduction of MINT in EPS |
R2-2507937
| endorsed | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.300 | 1437 | 1 | B | 19.0.0 | Rel-19 | Introduction of MINT in EPS |
R2-2507738
| revised | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.300 | 1437 | - | B | 19.0.0 | Rel-19 | CR to 36.300 Introduction of MINT in EPS |
R2-2507572
| revised | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.300 | 1436 | 1 | F | 19.0.0 | Rel-19 | Introducing CAS Muting [5GB_CASMuting] |
R2-2507811
| endorsed | RAN2#131bis | ZTE Corporation... |
| | | | | TEI19 |
|
|
|
| 36.300 | 1436 | - | F | 19.0.0 | Rel-19 | 5G Broadcast CAS Muting in stage 2 spec [5GB_CASMuting] |
R2-2507237
| revised | RAN2#131bis | ZTE Corporation... |
| | | | | TEI19 |
|
|
|
| 36.300 | 1435 | - | B | 18.5.0 | Rel-19 | Addition of SON enhancements |
R2-2506600
| agreed | RAN2#131 | R3 (Lenovo, Eri... |
RP-252783
| approved | RAN#109 | RAN2 | 19.0.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.300 | 1434 | - | A | 18.5.0 | Rel-18 | Clarification on BL CE UE in RRC_INACTIVE |
R2-2506509
| agreed | RAN2#131 | R3 (Ericsson, N... |
RP-252767
| approved | RAN#109 | RAN2 | 18.6.0 | NB_IOTenh4_LTE_eMTC6 |
|
|
|
| 36.300 | 1433 | - | F | 17.10.0 | Rel-17 | Clarification on BL CE UE in RRC_INACTIVE |
R2-2506508
| agreed | RAN2#131 | R3 (Ericsson, N... |
RP-252767
| approved | RAN#109 | RAN2 | 17.11.0 | NB_IOTenh4_LTE_eMTC6 |
|
|
|
| 36.300 | 1432 | - | B | 18.5.0 | Rel-19 | Restriction on RAT utilization |
R2-2506403
| agreed | RAN2#131 | Apple, Vodafone... |
RP-252868
| approved | RAN#109 | RAN2 | 19.0.0 | ECRATU |
|
|
|
| 36.300 | 1432 | - | B | 18.5.0 | Rel-19 | Restriction on RAT utilization |
R2-2506403
| agreed | RAN2#131 | Apple, Vodafone... |
RP-252816
| reissued | RAN#109 | R2 | 19.0.0 | ECRATU |
|
|
|
| 36.300 | 1431 | 1 | B | 18.5.0 | Rel-19 | Introduction of MINT in EPS |
R2-2506830
| not pursued | RAN2#131bis | Google |
| | | | | TEI19 |
|
|
|
| 36.300 | 1431 | - | B | 18.5.0 | Rel-19 | Introduction of MINT in EPS |
R2-2506194
| revised | RAN2#131 | Google |
| | | | | TEI19 |
|
|
|
| 36.300 | 1430 | 2 | F | 18.5.0 | Rel-18 | Clarification of satellite identifiers |
R2-2506295
| agreed | RAN2#131 | THALES, Samsung... |
RP-252769
| approved | RAN#109 | RAN2 | 18.6.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1430 | 1 | F | 18.5.0 | Rel-18 | Clarification of satellite identifiers |
R2-2506276
| revised | RAN2#131 | THALES, Samsung... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1430 | - | F | 18.5.0 | Rel-18 | Clarification of satellite identifiers |
R2-2506172
| revised | RAN2#131 | THALES, Samsung... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1429 | - | B | 18.5.0 | Rel-19 | SatSwitchwithReSync support for NB-IoT NTN |
R2-2505934
| | RAN2#131 | Skylo Technolog... |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.300 | 1428 | 1 | B | 18.5.0 | Rel-19 | Introduction of LTE-based 5G Broadcast Phase 2 |
R2-2506347
| agreed | RAN2#131 | ZTE Corporation... |
RP-252794
| approved | RAN#109 | RAN2 | 19.0.0 | LTE_terr_bcast_... |
|
|
|
| 36.300 | 1428 | - | B | 18.5.0 | Rel-19 | Introduction of LTE-based 5G Broadcast Phase 2 |
R2-2505799
| revised | RAN2#131 | ZTE Corporation... |
| | | | | LTE_terr_bcast_... |
|
|
|
| 36.300 | 1427 | - | B | 18.5.0 | Rel-19 | Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] |
R2-2505368
| agreed | RAN2#131 | Google, Samsung... |
RP-252796
| approved | RAN#109 | RAN2 | 19.0.0 | TEI19 |
|
|
|
| 36.300 | 1426 | 1 | B | 18.5.0 | Rel-19 | Introduction of IoT NTN TDD mode |
R2-2506497
| agreed | RAN2#131 | Iridium Satelli... |
RP-252795
| approved | RAN#109 | RAN2 | 19.0.0 | IoT_NTN_TDD-Core |
|
|
|
| 36.300 | 1426 | - | B | 18.5.0 | Rel-19 | Stage 2 CR for Introduction of IoT NTN TDD mode |
R2-2505256
| revised | RAN2#131 | Iridium Satelli... |
| | | | | IoT_NTN_TDD-Core |
|
|
|
| 36.300 | 1425 | 1 | B | 18.5.0 | Rel-19 | Introduction of IoT NTN phase 3 |
R2-2506494
| agreed | RAN2#131 | Ericsson |
RP-252792
| approved | RAN#109 | RAN2 | 19.0.0 | IoT_NTN_Ph3-Core |
|
|
|
| 36.300 | 1425 | - | B | 18.5.0 | Rel-19 | Introduction of IoT NTN phase 3 |
R2-2505145
| revised | RAN2#131 | Ericsson |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.300 | 1424 | 1 | A | 18.4.0 | Rel-18 | Remove the PWS support for IoT NTN |
R2-2504989
| agreed | RAN2#130 | R3 (Qualcomm In... |
RP-251693
| not pursued | RAN#108 | RAN2 | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1424 | - | A | 18.4.0 | Rel-18 | Remove the PWS support for IoT NTN |
R2-2504948
| revised | RAN2#130 | R3 (Qualcomm In... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1423 | 1 | F | 17.9.0 | Rel-17 | Remove the PWS support for IoT NTN |
R2-2504988
| agreed | RAN2#130 | R3 (Nokia, Noki... |
RP-251693
| not pursued | RAN#108 | RAN2 | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1423 | - | F | 17.9.0 | Rel-17 | Remove the PWS support for IoT NTN |
R2-2504947
| revised | RAN2#130 | R3 (Nokia, Noki... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1422 | - | F | 18.4.0 | Rel-18 | Clarification on data transmission for EDT |
R2-2504942
| agreed | RAN2#130 | R3 (ZTE Corpora... |
RP-251697
| approved | RAN#108 | RAN2 | 18.5.0 | NB_IOTenh3-Core... |
|
|
|
| 36.300 | 1421 | - | B | 18.4.0 | Rel-18 | Introduction of NB-IoT NTN in-band operation with NR NTN |
R2-2503359
| not pursued | RAN2#130 | vivo |
| | | | | TEI18 |
|
|
|
| 36.300 | 1420 | 2 | B | 18.4.0 | Rel-18 | Introduction of the inband operation for NTN IoT in NR NTN [NTNNBIoT_inbandNTNNR] |
R2-2504789
| agreed | RAN2#130 | Ericsson, Samsu... |
RP-251696
| approved | RAN#108 | RAN2 | 18.5.0 | TEI18 |
|
|
|
| 36.300 | 1420 | 1 | C | 18.4.0 | Rel-18 | Introduction of the inband operation for NTN IoT in NR NTN |
R2-2504782
| revised | RAN2#130 | Ericsson, Samsung |
| | | | | TEI18 |
|
|
|
| 36.300 | 1420 | - | C | 18.4.0 | Rel-18 | Introduction of the inband operation for NTN IoT in NR NTN |
R2-2504658
| revised | RAN2#130 | Ericsson, Samsung |
| | | | | IoT_NTN_enh-Cor... |
|
|
|
| 36.300 | 1419 | 1 | A | 18.4.0 | Rel-18 | Clarification on redirection and cell reselection to NR NTN |
R2-2504766
| agreed | RAN2#130 | CATT, Nokia, No... |
RP-251692
| approved | RAN#108 | RAN2 | 18.5.0 | NR_NTN_solution... |
|
|
|
| 36.300 | 1419 | - | A | 18.4.0 | Rel-18 | Clarification on redirection and cell reselection to NR NTN |
R2-2504521
| revised | RAN2#130 | CATT, Nokia, No... |
| | | | | NR_NTN_solution... |
|
|
|
| 36.300 | 1418 | 1 | F | 17.9.0 | Rel-17 | Clarification on redirection and cell reselection to NR NTN |
R2-2504765
| agreed | RAN2#130 | CATT, Nokia, No... |
RP-251692
| approved | RAN#108 | RAN2 | 17.10.0 | NR_NTN_solution... |
|
|
|
| 36.300 | 1418 | - | F | 17.9.0 | Rel-17 | Clarification on redirection and cell reselection to NR NTN |
R2-2504520
| revised | RAN2#130 | CATT, Nokia, No... |
| | | | | NR_NTN_solution... |
|
|
|
| 36.300 | 1417 | 2 | F | 18.4.0 | Rel-18 | Corrections to location-based measurement |
R2-2504089
| agreed | RAN2#130 | ZTE Corporation... |
RP-251696
| approved | RAN#108 | RAN2 | 18.5.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1417 | 1 | F | 18.4.0 | Rel-18 | Corrections to location-based measurement |
R2-2503062
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1417 | - | F | 18.4.0 | Rel-18 | Corrections to location-based measurement |
R2-2502522
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1416 | - | F | 17.9.0 | Rel-17 | Definition of NTN Cell |
R2-2500598
| not pursued | RAN2#129 | Apple |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1415 | - | F | 18.3.0 | Rel-18 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT UEs |
R2-2411241
| agreed | RAN2#128 | R3 (Qualcomm, E... |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1414 | 1 | F | 18.3.0 | Rel-18 | Correction on measurement |
R2-2410962
| agreed | RAN2#128 | Huawei, HiSilic... |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1414 | - | F | 18.3.0 | Rel-18 | Correction on measurement |
R2-2410810
| revised | RAN2#128 | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1413 | 1 | F | 18.3.0 | Rel-18 | Alignment of highProrityAccess cause in RRC Establishment and Resume |
R2-2411035
| agreed | RAN2#128 | Peraton Labs, C... |
RP-243221
| approved | RAN#106 | RAN2 | 18.4.0 | NR_newRAT-Core |
|
|
|
| 36.300 | 1413 | - | F | 18.3.0 | Rel-18 | Alignment of highProrityAccess cause in RRC Establishment and Resume |
R2-2410547
| revised | RAN2#128 | Peraton Labs |
| | | | | NR_newRAT-Core |
|
|
|
| 36.300 | 1412 | 7 | B | 18.5.0 | Rel-19 | Introduction of for LTE TN to NR NTN idle mode mobility |
R2-2506553
| agreed | RAN2#131 | Samsung |
RP-252793
| approved | RAN#109 | RAN2 | 19.0.0 | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 6 | B | 18.5.0 | Rel-19 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
R2-2506137
| revised | RAN2#131 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 5 | B | 18.5.0 | Rel-19 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
R2-2505147
| withdrawn | RAN2#131 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 4 | B | 18.4.0 | Rel-19 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
R2-2504096
| revised | RAN2#130 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 3 | B | 18.4.0 | Rel-19 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
R2-2501416
| revised | RAN2#129 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 2 | B | 18.4.0 | Rel-19 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility |
R2-2501284
| revised | RAN2#129 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | 1 | B | 18.3.0 | Rel-19 | Introduction of stage 2 for LTE to NR NTN idle mode mobility |
R2-2410969
| revised | RAN2#128 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1412 | - | B | 18.3.0 | Rel-19 | Introduction of stage 2 for LTE to NR NTN idle mode mobility |
R2-2409938
| revised | RAN2#128 | Samsung |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.300 | 1411 | - | F | 18.3.0 | Rel-18 | Corrections on the reference of satellite ID |
R2-2409590
| merged | RAN2#128 | Huawei, HiSilic... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1410 | - | F | 18.3.0 | Rel-18 | Correction on UE Location Information Reporting in IoT-NTN |
R2-2409543
| agreed | RAN2#128 | vivo, Ericsson,... |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1409 | 1 | F | 18.3.0 | Rel-18 | IoT NTN Stage 2 correction to eMTC CHO |
R2-2410884
| agreed | RAN2#128 | Ericsson (Rappo... |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1409 | - | F | 18.3.0 | Rel-18 | IoT NTN Stage 2 correction |
R2-2409178
| revised | RAN2#127-bis | Ericsson (Rappo... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1408 | - | F | 18.3.0 | Rel-18 | Correction on UE Location Information Reporting in IoT-NTN |
R2-2408011
| postponed | RAN2#127-bis | vivo, Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1407 | 2 | F | 18.3.0 | Rel-18 | Corrections on CHO and measurement |
R2-2409241
| endorsed | RAN2#127-bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1407 | 1 | F | 18.3.0 | Rel-18 | Corrections on CHO and measurement |
R2-2409236
| revised | RAN2#127-bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1407 | - | F | 18.3.0 | Rel-18 | Corrections on CHO and measurement |
R2-2408010
| revised | RAN2#127-bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1406 | 1 | F | 17.8.0 | Rel-17 | Clarification on UE/BS requirements for LTE based 5G terrestrial broadcast |
| | | |
RP-242383
| approved | RAN#105 | Qualcomm Incorp... | 17.9.0 | LTE_terr_bcast_... |
|
|
|
| 36.300 | 1406 | - | F | 17.8.0 | Rel-17 | Clarification on UE/BS requirements for LTE based 5G terrestrial broadcast |
| | | |
RP-242092
| revised | RAN#105 | Qualcomm Incorp... | | LTE_terr_bcast_... |
|
|
|
| 36.300 | 1405 | 1 | F | 18.2.0 | Rel-18 | Correction for IoT NTN neighbour cell measurements and TN to NTN mobility |
R2-2407868
| agreed | RAN2#127 | Ericsson, Samsung |
RP-242237
| approved | RAN#105 | RAN2 | 18.3.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1405 | - | F | 18.2.0 | Rel-18 | Correction for IoT NTN neighbour cell measurements and TN to NTN mobility |
R2-2407626
| revised | RAN2#127 | Ericsson, Samsung |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1404 | - | F | 18.1.0 | Rel-18 | Correction on Inter-system MRO |
R2-2406064
| agreed | RAN2#126 | R3 (Samsung, No... |
RP-241544
| approved | RAN#104 | RAN2 | 18.2.0 | NR_SON_MDT-Core... |
|
|
|
| 36.300 | 1403 | - | A | 18.1.0 | Rel-18 | IoT NTN Kmac corrections |
R2-2405802
| agreed | RAN2#126 | Ericsson |
RP-241553
| approved | RAN#104 | RAN2 | 18.2.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1402 | 1 | F | 17.7.0 | Rel-17 | IoT NTN Kmac correction |
R2-2405801
| agreed | RAN2#126 | Ericsson |
RP-241553
| approved | RAN#104 | RAN2 | 17.8.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1402 | - | F | 17.7.0 | Rel-17 | IoT NTN Kmac correction |
R2-2405452
| revised | RAN2#126 | Ericsson |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1401 | 2 | F | 18.1.0 | Rel-18 | IoT NTN measurement corrections |
R2-2405752
| agreed | RAN2#126 | Ericsson, Huawei |
RP-241556
| approved | RAN#104 | RAN2 | 18.2.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1401 | 1 | F | 18.1.0 | Rel-18 | IoT NTN Kmac and measurment corrections |
R2-2405453
| revised | RAN2#126 | Ericsson, Huawei |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1401 | - | F | 18.1.0 | Rel-18 | IoT NTN corrections to stage 2 |
R2-2403776
| revised | RAN2#125-bis | Ericsson, Huawei |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1400 | - | F | 18.1.0 | Rel-18 | Correction to Stage 2 on IoT NTN |
R2-2402772
| noted | RAN2#125-bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1399 | - | F | 18.0.0 | Rel-18 | Correction of timer-based conditional handover for IoT NTN |
R2-2402004
| agreed | RAN2#125 | R3 (Huawei, Nok... |
RP-240660
| approved | RAN#103 | RAN2 | 18.1.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1398 | - | B | 18.0.0 | Rel-18 | 2Rx Non-RedCap XR device access |
R2-2401964
| not pursued | RAN2#125 | Apple, Verizon,... |
| | | | | TEI18 |
|
|
|
| 36.300 | 1397 | 1 | F | 18.0.0 | Rel-18 | Correction to Stage 2 on IoT NTN |
R2-2401514
| noted | RAN2#125 | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1397 | - | F | 18.0.0 | Rel-18 | Correction to Stage 2 on IoT NTN |
R2-2401461
| revised | RAN2#125 | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1396 | 1 | F | 18.0.0 | Rel-18 | Corrections to stage 2 for IoT NTN |
R2-2401600
| agreed | RAN2#125 | Ericsson, Huawe... |
RP-240660
| approved | RAN#103 | RAN2 | 18.1.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1396 | - | F | 18.0.0 | Rel-18 | R18 IoT NTN corrections to stage 2 |
R2-2401402
| revised | RAN2#125 | Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1395 | 1 | F | 18.0.0 | Rel-18 | Corrections to Enhanced LTE Support for Uncrewed Aerial Vehicles. |
R2-2401871
| | RAN2#125 | Nokia, Nokia Sh... |
| | | | | LTE_UAV_enh |
|
|
|
| 36.300 | 1395 | - | F | 18.0.0 | Rel-18 | Corrections to Enhanced LTE Support for Uncrewed Aerial Vehicles. |
R2-2400673
| agreed | RAN2#125 | Nokia, Nokia Sh... |
RP-240661
| approved | RAN#103 | RAN2 | 18.1.0 | LTE_UAV_enh |
|
|
|
| 36.300 | 1394 | - | F | 18.0.0 | Rel-18 | Handover for Reduced Capability |
R2-2400473
| agreed | RAN2#125 | Nokia (Rapporte... |
RP-240698
| approved | RAN#103 | RAN2 | 18.1.0 | NR_redcap-Core,... |
|
|
|
| 36.300 | 1393 | - | F | 17.6.0 | Rel-17 | Handover for Reduced Capability |
R2-2400471
| agreed | RAN2#125 | Nokia (Rapporte... |
RP-240656
| approved | RAN#103 | RAN2 | 17.7.0 | NR_redcap-Core |
|
|
|
| 36.300 | 1392 | - | B | 17.5.0 | Rel-18 | IoT NTN enhancements |
R2-2314003
| merged | RAN2#124 | R3 (ZTE, Huawei... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1391 | - | B | 17.5.0 | Rel-18 | Addition of SON features enhancement |
R2-2313986
| agreed | RAN2#124 | R3 (Lenovo, Nok... |
RP-233909
| approved | RAN#102 | RAN2 | 18.0.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.300 | 1390 | - | F | 17.5.0 | Rel-17 | Introduction of new attributes “Resource Coordination Only” in ANR |
R2-2313975
| agreed | RAN2#124 | R3 (Ericsson, Z... |
RP-233889
| approved | RAN#102 | RAN2 | 17.6.0 | TEI17 |
|
|
|
| 36.300 | 1389 | - | B | 17.5.0 | Rel-18 | Introduction of Enhanced LTE Support for Uncrewed Aerial Vehicles |
R2-2313056
| agreed | RAN2#124 | Nokia, Nokia Sh... |
RP-233892
| approved | RAN#102 | RAN2 | 18.0.0 | LTE_UAV_enh |
|
|
|
| 36.300 | 1388 | - | F | 17.5.0 | Rel-17 | Correction to 36.300 on Koffset handling during handover |
R2-2311311
| | RAN2#123-bis | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1387 | 2 | B | 17.5.0 | Rel-18 | Introduction of IoT NTN enhancements |
R2-2313779
| agreed | RAN2#124 | Ericsson |
RP-233891
| approved | RAN#102 | RAN2 | 18.0.0 | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1387 | 1 | B | 17.5.0 | Rel-18 | Introduction of IoT NTN enhancements |
R2-2313301
| revised | RAN2#124 | Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1387 | - | B | 17.5.0 | Rel-18 | Introduction of IoT NTN enhancements |
R2-2311244
| revised | RAN2#123-bis | Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.300 | 1386 | - | F | 17.5.0 | Rel-17 | Correction to GNSS acquisition description for IoT NTN |
R2-2308538
| not pursued | RAN2#123 | Ericsson |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1385 | 2 | F | 17.4.0 | Rel-17 | Correction on handover procedure completion |
R2-2306570
| agreed | RAN2#122 | vivo, Nokia (ra... |
RP-231412
| approved | RAN#100 | RAN2 | 17.5.0 | LTE-L23, TEI17 |
|
|
|
| 36.300 | 1385 | 1 | F | 17.4.0 | Rel-17 | Correction on handover procedure completion |
R2-2306562
| revised | RAN2#122 | vivo, Nokia (ra... |
| | | | | LTE-L23 |
|
|
|
| 36.300 | 1385 | - | F | 8.12.0 | Rel-8 | Correction on handover procedure completion |
R2-2304943
| revised | RAN2#122 | vivo, Nokia (ra... |
| | | | | LTE-L23 |
|
|
|
| 36.300 | 1384 | 2 | F | 17.4.0 | Rel-17 | Miscellaneous Stage 2 corrections for IoT NTN |
R2-2306928
| agreed | RAN2#122 | Huawei, HiSilicon |
RP-231417
| approved | RAN#100 | RAN2 | 17.5.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1384 | 1 | F | 17.4.0 | Rel-18 | Miscellaneous Stage 2 corrections for IoT NTN |
R2-2306649
| revised | RAN2#122 | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1384 | - | F | 17.4.0 | Rel-18 | Miscellaneous Stage 2 corrections for IoT NTN |
R2-2304810
| revised | RAN2#122 | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1383 | 2 | F | 17.4.0 | Rel-17 | Correction for R17 IoT NTN |
R2-2306261
| agreed | RAN2#122 | Ericsson, OPPO,... |
RP-231417
| approved | RAN#100 | RAN2 | 17.5.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1383 | 1 | F | 17.4.0 | Rel-17 | Correction for R17 IoT NTN |
R2-2304260
| revised | RAN2#121-bis-e | Ericsson, OPPO,... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1383 | - | F | 17.4.0 | Rel-17 | Correction for R17 IoT NTN |
R2-2303832
| revised | RAN2#121-bis-e | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1382 | - | F | 17.4.0 | Rel-17 | Stage-2 Corrections for Supporting Emergency Calls in IoT NTN |
R2-2302677
| not pursued | RAN2#121-bis-e | MediaTek Inc |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1381 | 2 | F | 17.3.0 | Rel-17 | Correction related to AS deactivation due to discontinuous coverage |
R2-2301976
| agreed | RAN2#121 | Deutsche Teleko... |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1381 | 1 | F | 17.3.0 | Rel-17 | Correction related to AS deactivation due to discontinuous coverage |
R2-2301863
| revised | RAN2#121 | Deutsche Teleko... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1381 | - | F | 17.3.0 | Rel-17 | Correction related to AS deactivation due to discontinuous coverage |
R2-2301380
| revised | RAN2#121 | Deutsche Teleko... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1380 | - | F | 17.3.0 | Rel-17 | CR to 36.300 on neighbour cell measurements |
R2-2301158
| not pursued | RAN2#121 | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1379 | - | F | 17.3.0 | Rel-17 | Clarification on coexistence of DAPS and CPA |
R2-2300857
| not pursued | RAN2#121 | CATT, Nokia (Ra... |
| | | | | LTE_NR_DC_enh2-Core |
|
|
|
| 36.300 | 1378 | - | F | 17.3.0 | Rel-17 | Stage-2 correction on TDD support for IoT NTN |
R2-2300357
| agreed | RAN2#121 | OPPO |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1377 | 1 | F | 17.3.0 | Rel-17 | IoT-NTN Stage-2 correction |
R2-2301963
| agreed | RAN2#121 | OPPO |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1377 | - | F | 17.3.0 | Rel-17 | IoT-NTN Stage-2 correction |
R2-2300167
| revised | RAN2#121 | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1376 | - | F | 17.2.0 | Rel-17 | Correction to IoT NTN about constructing the Mapped Cell ID |
R2-2213182
| agreed | RAN2#120 | R3 (CATT, Erics... |
RP-223409
| approved | RAN#98-e | RAN2 | 17.3.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1375 | 2 | F | 17.2.0 | Rel-17 | IoT NTN corrections |
R2-2213365
| agreed | RAN2#120 | Ericsson |
RP-223409
| approved | RAN#98-e | RAN2 | 17.3.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1375 | 1 | F | 17.2.0 | Rel-17 | IoT NTN corrections |
R2-2213035
| revised | RAN2#120 | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1375 | - | F | 17.2.0 | Rel-17 | IoT NTN corrections |
R2-2213015
| revised | RAN2#120 | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1374 | - | F | 17.2.0 | Rel-17 | Removal of FFS from LTE Relay description |
R2-2211364
| agreed | RAN2#120 | Nokia (rapporte... |
RP-223414
| approved | RAN#98-e | RAN2 | 17.3.0 | TEI17, LTE_Rela... |
|
|
|
| 36.300 | 1373 | 1 | A | 17.2.0 | Rel-17 | Correction on measurement reporting for interference detection in UAV |
R2-2213208
| agreed | RAN2#120 | Samsung Electro... |
RP-223405
| approved | RAN#98-e | RAN2 | 17.3.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1373 | - | A | 17.2.0 | Rel-17 | Correction on measurement reporting for interference detection in UAV |
R2-2211189
| revised | RAN2#120 | Samsung Electro... |
| | | | | LTE_Aerial-Core |
|
|
|
| 36.300 | 1372 | 1 | A | 16.8.0 | Rel-16 | Correction on measurement reporting for interference detection in UAV |
R2-2213207
| agreed | RAN2#120 | Samsung Electro... |
RP-223405
| approved | RAN#98-e | RAN2 | 16.9.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1372 | - | A | 16.8.0 | Rel-16 | Correction on measurement reporting for interference detection in UAV |
R2-2211188
| revised | RAN2#120 | Samsung Electro... |
| | | | | LTE_Aerial-Core |
|
|
|
| 36.300 | 1371 | 1 | F | 15.13.0 | Rel-15 | Correction on measurement reporting for interference detection in UAV |
R2-2213206
| agreed | RAN2#120 | Samsung Electro... |
RP-223405
| approved | RAN#98-e | RAN2 | 15.14.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1371 | - | F | 15.13.0 | Rel-15 | Correction on measurement reporting for interference detection in UAV |
R2-2211187
| revised | RAN2#120 | Samsung Electro... |
| | | | | LTE_Aerial-Core |
|
|
|
| 36.300 | 1370 | - | F | 17.2.0 | Rel-17 | Correction on user consent for UE coarse location request |
R2-2209661
| | RAN2#119-bis-e | Huawei, HiSilicon |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1369 | 1 | F | 17.1.0 | Rel-17 | Correction to IoT-NTN stage 2 correction description |
R2-2209262
| agreed | RAN2#119-e | Ericsson |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1369 | - | F | 17.1.0 | Rel-17 | Correction to IoT-NTN stage 2 correction description |
R2-2208762
| revised | RAN2#119-e | Ericsson |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.300 | 1368 | 1 | F | 17.0.0 | Rel-17 | Correction on R17 SON MDT for TS36.300 |
R2-2206854
| agreed | RAN2#118-e | R3 (ZTE,China U... |
RP-221733
| approved | RAN#96 | RAN2 | 17.1.0 | NR_ENDC_SON_MDT_enh |
|
|
|
| 36.300 | 1368 | - | F | 17.0.0 | Rel-17 | Correction on R17 SON MDT for TS36.300 |
R2-2206772
| revised | RAN2#118-e | R3 (ZTE,China U... |
| | | | | NR_ENDC_SON_MDT_enh |
|
|
|
| 36.300 | 1367 | - | F | 17.0.0 | Rel-17 | Clarifications for NB-IOT UE |
R2-2206737
| merged | RAN2#118-e | R3 (Nokia, Noki... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1366 | 1 | F | 17.0.0 | Rel-17 | RACH optimisation in EN-DC secondary cell |
R2-2206855
| agreed | RAN2#118-e | R3 (Nokia, Noki... |
RP-221733
| approved | RAN#96 | RAN2 | 17.1.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.300 | 1366 | - | F | 17.0.0 | Rel-17 | RACH optimisation in EN-DC secondary cell |
R2-2206734
| revised | RAN2#118-e | R3 (Nokia, Noki... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.300 | 1365 | - | F | 17.0.0 | Rel-17 | Stage 2 Correction on NB-IoT and eMTC Support for NTN |
R2-2206731
| merged | RAN2#118-e | R3 (ZTE) |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1364 | 2 | F | 17.0.0 | Rel-17 | IoT NTN Stage 2 Corrections |
R2-2206876
| agreed | RAN2#118-e | Ericsson, Eutelsat |
RP-221737
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1364 | 1 | F | 17.0.0 | Rel-17 | IoT NTN Stage 2 Corrections |
R2-2206777
| revised | RAN2#118-e | Ericsson, Eutelsat |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1364 | - | F | 17.0.0 | Rel-17 | IoT NTN Stage 2 Corrections |
R2-2206629
| revised | RAN2#118-e | Ericsson, Eutelsat |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1363 | 2 | B | 17.0.0 | Rel-17 | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
R2-2206874
| agreed | RAN2#118-e | Ericsson, Veriz... |
RP-221738
| approved | RAN#96 | RAN2 | 17.1.0 | TEI17 |
|
|
|
| 36.300 | 1363 | 1 | B | 17.0.0 | Rel-17 | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
R2-2206718
| revised | RAN2#118-e | Ericsson, Veriz... |
| | | | | TEI17 |
|
|
|
| 36.300 | 1363 | - | B | 17.0.0 | Rel-17 | Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] |
R2-2206544
| revised | RAN2#118-e | Ericsson, Veriz... |
| | | | | TEI17 |
|
|
|
| 36.300 | 1362 | - | B | 16.7.0 | Rel-17 | BLCR to 36.300_Addition of SON features enhancement |
R2-2204169
| agreed | RAN2#117-e | R3 (Lenovo, Mot... |
RP-220839
| approved | RAN#95-e | RAN2 | 17.0.0 | NR_ENDC_SON_MDT_enh |
|
|
|
| 36.300 | 1361 | - | B | 16.7.0 | Rel-17 | NB-IoT/eMTC support for Non-Terrestrial Networks |
R2-2204167
| | RAN2#117-e | R3 (ZTE, CATT, ... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1360 | - | B | 16.7.0 | Rel-17 | Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast |
R2-2203699
| agreed | RAN2#117-e | Qualcomm Inc. |
RP-220508
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_terr_bcast_... |
|
|
|
| 36.300 | 1359 | 1 | C | 16.7.0 | Rel-17 | UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps] |
R2-2204213
| agreed | RAN2#117-e | R3 (Ericsson, Q... |
RP-220510
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17 |
|
|
|
| 36.300 | 1359 | - | C | 16.7.0 | Rel-17 | UE Security Capabilities signaling in E-UTRAN [UE_Sec_Caps] |
R2-2204156
| revised | RAN2#117-e | R3 (Ericsson, Q... |
| | | | | TEI17 |
|
|
|
| 36.300 | 1358 | - | A | 16.7.0 | Rel-16 | Clarification of RSRP measurement triggering for number of cells for UAVs |
R2-2203659
| agreed | RAN2#117-e | Ericsson, Samsu... |
RP-220472
| approved | RAN#95-e | RAN2 | 16.8.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1357 | - | F | 15.12.0 | Rel-15 | Clarification of RSRP measurement triggering for number of cells for UAVs |
R2-2203658
| agreed | RAN2#117-e | Ericsson, Samsu... |
RP-220472
| approved | RAN#95-e | RAN2 | 15.13.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1356 | 2 | B | 16.7.0 | Rel-17 | Introduction of IoT NTN Stage 2 |
R2-2204266
| agreed | RAN2#117-e | Ericsson, Eutelsat |
RP-220509
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1356 | 1 | B | 16.7.0 | Rel-17 | Introduction of IoT NTN Stage 2 |
R2-2204232
| revised | RAN2#117-e | Ericsson, Eutelsat |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1356 | - | B | 16.7.0 | Rel-17 | IoT NTN Stage 2 CR |
R2-2203455
| revised | RAN2#117-e | Ericsson, Eutelsat |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.300 | 1355 | - | B | 16.7.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2203437
| agreed | RAN2#117-e | Ericsson |
RP-220488
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.300 | 1354 | 1 | B | 16.7.0 | Rel-17 | Introduction of Rel-17 enhancements for NB-IoT and eMTC |
R2-2203579
| agreed | RAN2#117-e | Huawei, HiSilicon |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.300 | 1354 | - | B | 16.7.0 | Rel-17 | Introduction of Rel-17 enhancements for NB-IoT and eMTC |
R2-2203216
| revised | RAN2#117-e | Huawei, HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
|
| 36.300 | 1353 | 1 | B | 16.7.0 | Rel-17 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
R2-2203821
| agreed | RAN2#117-e | Huawei, HiSilic... |
RP-220495
| approved | RAN#95-e | RAN2 | 17.0.0 | UPIP_SEC_LTE-RA... |
|
|
|
| 36.300 | 1353 | - | B | 16.7.0 | Rel-17 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
R2-2202719
| revised | RAN2#117-e | Huawei, HiSilic... |
| | | | | UPIP_SEC_LTE |
|
|
|
| 36.300 | 1352 | 1 | B | 16.7.0 | Rel-17 | Introduction of MINT [MINT] |
R2-2203866
| agreed | RAN2#117-e | Ericsson, Lenov... |
RP-220837
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17 |
|
|
|
| 36.300 | 1352 | - | B | 16.7.0 | Rel-17 | Introduction of MINT |
R2-2202256
| revised | RAN2#117-e | Ericsson, Lenov... |
| | | | | TEI17 |
|
|
|
| 36.300 | 1351 | - | B | 16.6.0 | Rel-17 | [gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report |
R2-2110838
| | RAN2#116-e | Ericsson, Veriz... |
| | | | | TEI17 |
|
|
|
| 36.300 | 1350 | 1 | F | 16.6.0 | Rel-16 | Miscellaneous corrections |
R2-2111317
| agreed | RAN2#116-e | Nokia (rapporte... |
RP-213342
| approved | RAN#94-e | RAN2 | 16.7.0 | LTE_1024QAM_DL-... |
|
|
|
| 36.300 | 1350 | - | F | 16.6.0 | Rel-16 | Miscellaneous corrections |
R2-2110805
| revised | RAN2#116-e | Nokia (rapporte... |
| | | | | LTE_feMTC-Core,... |
|
|
|
| 36.300 | 1349 | 1 | B | 16.6.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2111438
| endorsed | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.300 | 1349 | - | B | 16.6.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2110789
| revised | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.300 | 1348 | - | F | 16.6.0 | Rel-16 | Correction to NB-IoT measurements |
R2-2110471
| merged | RAN2#116-e | Huawei, HiSilicon |
| | | | | NB_IOT-Core, TEI16 |
|
|
|
| 36.300 | 1347 | - | F | 16.5.0 | Rel-16 | 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario |
R2-2106568
| agreed | RAN2#114-e | R3 (Intel Corpo... |
RP-211479
| approved | RAN#92-e | RAN2 | 16.6.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1346 | 1 | F | 16.5.0 | Rel-16 | Correction on LTE aerial feature |
| | | |
RP-211344
| approved | RAN#92-e | Ericsson, Qualc... | 16.6.0 | LTE_Aerial-Core |
|
|
|
| 36.300 | 1346 | - | F | 16.5.0 | Rel-16 | Correction on LTE aerial feature |
R2-2106566
| | RAN2#114-e | R3 (Ericsson, Q... |
| | | | | LTE_Aerial-Core |
|
|
|
| 36.300 | 1345 | - | F | 16.5.0 | Rel-16 | 36300_(R16)_Clarification on paging in RRC_INACTIVE |
R2-2106322
| | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1344 | - | F | 16.5.0 | Rel-16 | Removing incorrect SRVCC limitation |
R2-2105892
| not pursued | RAN2#114-e | Ericsson, Nokia |
| | | | | SRVCC_NR_to_UMTS |
|
|
|
| 36.300 | 1343 | - | F | 16.5.0 | Rel-16 | CR on non-DAPS DRB handling |
R2-2105505
| not pursued | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1342 | - | F | 16.5.0 | Rel-16 | Transmissions to the source that continue upon DAPS UL switching in LTE |
R2-2105005
| merged | RAN2#114-e | Nokia, Nokia Sh... |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1341 | 1 | F | 16.5.0 | Rel-16 | Miscellaneous corrections to DAPS handover |
R2-2106679
| agreed | RAN2#114-e | Ericsson, Nokia... |
RP-211479
| approved | RAN#92-e | RAN2 | 16.6.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1341 | - | F | 16.5.0 | Rel-16 | Reconfiguration during DAPS HO |
R2-2104934
| revised | RAN2#114-e | Ericsson, Nokia... |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1340 | - | F | 16.5.0 | Rel-16 | Reconfiguration during DAPS HO |
R2-2104571
| | RAN2#113-bis-e | Ericsson |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1339 | 1 | F | 16.5.0 | Rel-16 | Clarification on RLF detection of source PCell |
R2-2105608
| agreed | RAN2#114-e | Huawei, HiSilicon |
RP-211479
| approved | RAN#92-e | RAN2 | 16.6.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1339 | - | F | 16.5.0 | Rel-16 | Clarification on RLF detection of source Pcell |
R2-2104337
| revised | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1338 | 1 | F | 16.5.0 | Rel-16 | Clarification on LTE DAPS and sidelink on 36.300 |
R2-2105587
| agreed | RAN2#114-e | Huawei, HiSilicon |
RP-211470
| approved | RAN#92-e | RAN2 | 16.6.0 | 5G_V2X_NRSL-Core |
|
|
|
| 36.300 | 1338 | - | F | 16.5.0 | Rel-16 | Clarification on LTE DAPS and sidelink on 36.300 |
R2-2104107
| revised | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.300 | 1337 | - | F | 16.5.0 | Rel-17 | Correction on handover terminology |
R2-2104011
| not pursued | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | TEI17 |
|
|
|
| 36.300 | 1336 | 1 | F | 16.5.0 | Rel-16 | Removing ambiguous legacy and normal terms from handover descriptions |
R2-2105002
| agreed | RAN2#114-e | Nokia, Nokia Sh... |
RP-211473
| approved | RAN#92-e | RAN2 | 16.6.0 | NR_Mob_enh-Core |
|
|
|
| 36.300 | 1336 | - | F | 16.5.0 | Rel-17 | 36.300 CR: removing ambiguous HO naming |
R2-2103338
| revised | RAN2#113-bis-e | Nokia, Nokia Sh... |
| | | | | E_HOO |
|
|
|
| 36.300 | 1335 | - | F | 16.4.0 | Rel-16 | Non-support of CHO/CPC with LTE/5GC |
R2-2101978
| agreed | RAN2#113-e | Ericsson |
RP-210698
| approved | RAN#91-e | RAN2 | 16.5.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1334 | - | F | 16.4.0 | Rel-16 | Clarification on manufacturer based UE capability ID |
R2-2101029
| not pursued | RAN2#113-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.300 | 1333 | 3 | D | 16.7.0 | Rel-17 | Inclusive Language Review for TS 36.300 |
R2-2203788
| agreed | RAN2#117-e | Nokia (Rapporteur) |
RP-220506
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17 |
|
|
|
| 36.300 | 1333 | 2 | D | 16.7.0 | Rel-17 | Inclusive Language Review for TS 36.300 |
R2-2203270
| revised | RAN2#117-e | Nokia (rapporteur) |
| | | | | TEI17 |
|
|
|
| 36.300 | 1333 | 1 | D | 16.4.0 | Rel-17 | Inclusive language in 36.300 |
R2-2101989
| revised | RAN2#113-e | Nokia (Rappporteur) |
| | | | | TEI17 |
|
|
|
| 36.300 | 1333 | - | D | 16.4.0 | Rel-17 | Inclusive language in 36.300 |
R2-2100956
| revised | RAN2#113-e | Nokia (Rappporteur) |
| | | | | TEI17 |
|
|
|
| 36.300 | 1332 | - | F | 16.3.0 | Rel-16 | Correction on immediate suspension |
R2-2010828
| agreed | RAN2#112-e | R3 (Huawei, Nok... |
RP-202779
| approved | RAN#90-e | RAN2 | 16.4.0 | LTE_eMTC5-Core,... |
|
|
|
| 36.300 | 1331 | - | F | 16.3.0 | Rel-16 | Correction for LTE CHO and Full Configuration |
R2-2010822
| agreed | RAN2#112-e | R3 (Intel Corpo... |
RP-202782
| approved | RAN#90-e | RAN2 | 16.4.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1330 | - | F | 16.3.0 | Rel-16 | MobEnh Stage-2 corrections |
R2-2010716
| agreed | RAN2#112-e | Nokia (rapporte... |
RP-202782
| approved | RAN#90-e | RAN2 | 16.4.0 | LTE_feMob-Core |
|
|
|
| 36.300 | 1329 | - | F | 16.3.0 | Rel-16 | Clarifications on DAPS and conditional handover for LTE-5GC |
R2-2010507
| merged | RAN2#112-e | Ericsson |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1328 | - | C | 16.3.0 | Rel-16 | Support for eDRX cyle beyond 10.24s in RRC_INACTIVE |
R2-2010497
| not pursued | RAN2#112-e | LG Electronics UK |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.300 | 1327 | - | F | 16.3.0 | Rel-16 | Correction for the definition of DAPS handover (36.300) |
R2-2010207
| not pursued | RAN2#112-e | SHARP Corporation |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1326 | - | F | 16.3.0 | Rel-16 | Correction on TS 36.300 for CHO |
R2-2010188
| not pursued | RAN2#112-e | Huawei, HiSilicon |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1325 | - | F | 16.3.0 | Rel-16 | Misc corrections for Rel-16 DCCA |
R2-2010021
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.300 | 1324 | 1 | F | 16.3.0 | Rel-16 | Miscellaneous Stage-2 corrections |
R2-2010713
| agreed | RAN2#112-e | Nokia (rapporte... |
RP-202788
| approved | RAN#90-e | RAN2 | 16.4.0 | NB_IOTenh2-Core... |
|
|
|
| 36.300 | 1324 | - | F | 16.3.0 | Rel-16 | Miscellaneous Stage-2 corrections |
R2-2009802
| revised | RAN2#112-e | Nokia (rapporte... |
| | | | | NB_IOTenh2-Core... |
|
|
|
| 36.300 | 1323 | 1 | F | 15.11.0 | Rel-15 | Miscellaneous Stage-2 corrections |
R2-2010712
| agreed | RAN2#112-e | Nokia (rapporte... |
RP-202788
| approved | RAN#90-e | RAN2 | 15.12.0 | NB_IOTenh2-Core... |
|
|
|
| 36.300 | 1323 | - | F | 15.11.0 | Rel-15 | Miscellaneous Stage-2 corrections |
R2-2009801
| revised | RAN2#112-e | Nokia (rapporte... |
| | | | | NB_IOTenh2-Core... |
|
|
|
| 36.300 | 1322 | 1 | F | 16.3.0 | Rel-16 | CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 kHz and 2.5 kHz |
R2-2010758
| agreed | RAN2#112-e | Qualcomm Incorp... |
RP-202780
| approved | RAN#90-e | RAN2 | 16.4.0 | LTE_terr_bcast-Core |
|
|
|
| 36.300 | 1322 | - | F | 16.3.0 | Rel-16 | CP length and reference signal for MBSFN with sub-carrier spacing of 0.375 KkHz and 2.5 kKHz |
R2-2009446
| revised | RAN2#112-e | Qualcomm Inc |
| | | | | LTE_terr_bcast-Core |
|
|
|
| 36.300 | 1321 | - | F | 16.3.0 | Rel-16 | Clarification on CHO in LTE-DC |
R2-2009386
| merged | RAN2#112-e | ZTE Corporation... |
| | | | | LTE_feMob-Core |
|
|
|
| 36.300 | 1320 | 1 | F | 16.3.0 | Rel-16 | Clarification on no support of CA or DC with DAPS |
R2-2010747
| agreed | RAN2#112-e | ZTE Corporation... |
RP-202782
| approved | RAN#90-e | RAN2 | 16.4.0 | LTE_feMob-Core |
|