|
|
| 36.213 | 1447 | - | A | 18.2.0 | Rel-18 | Rel-16 corrections to higher-layers parameters for Additional MTC Enhancements for LTE and Additional enhancements for NB-IoT |
R1-2409323
| agreed | RAN1#118-bis | Motorola Mobility |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.213 | 1446 | - | F | 18.2.0 | Rel-18 | Corrections to higher-layers parameters for IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
R1-2409322
| agreed | RAN1#118-bis | Motorola Mobility |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.213 | 1445 | - | A | 17.6.0 | Rel-17 | Rel-16 corrections to higher-layers parameters for Additional MTC Enhancements for LTE and Additional enhancements for NB-IoT |
R1-2409321
| agreed | RAN1#118-bis | Motorola Mobility |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.213 | 1444 | - | F | 16.10.0 | Rel-16 | Corrections to higher-layers parameters for Additional MTC Enhancements for LTE and Additional enhancements for NB-IoT |
R1-2409320
| agreed | RAN1#118-bis | Motorola Mobility |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.213 | 1443 | - | F | 18.1.0 | Rel-18 | Corrections to IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
R1-2401921
| agreed | RAN1#116 | Motorola Mobility |
RP-240524
| approved | RAN#103 | RAN1 | 18.2.0 | IoT_NTN_enh-Core |
|
|
|
| 36.213 | 1442 | - | F | 18.0.0 | Rel-18 | Corrections to IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
R1-2312762
| agreed | RAN1#115 | Motorola Mobility |
RP-233715
| approved | RAN#102 | RAN1 | 18.1.0 | IoT_NTN_enh-Core |
|
|
|
| 36.213 | 1441 | - | A | 18.0.0 | Rel-18 | Correction on Koffset during random access procedure |
R1-2312491
| agreed | RAN1#115 | Qualcomm Incorp... |
RP-233725
| approved | RAN#102 | RAN1 | 18.1.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1440 | - | F | 17.5.0 | Rel-17 | Correction on Koffset during random access procedure |
R1-2312490
| agreed | RAN1#115 | Qualcomm Incorp... |
RP-233725
| approved | RAN#102 | RAN1 | 17.6.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1439 | 1 | A | 18.0.0 | Rel-18 | CR on HARQ timing for CEMode B |
R1-2310691
| agreed | RAN1#114-bis | Lenovo, Ericsso... |
RP-233724
| approved | RAN#102 | RAN1 | 18.1.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1439 | - | A | 18.0.0 | Rel-18 | CR on HARQ timing for CEMode B |
R1-2310655
| revised | RAN1#114-bis | Lenovo, Ericsso... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1438 | 1 | A | 17.5.0 | Rel-17 | CR on HARQ timing for CEMode B |
R1-2310690
| agreed | RAN1#114-bis | Lenovo, Ericsso... |
RP-233724
| approved | RAN#102 | RAN1 | 17.6.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1438 | - | A | 17.5.0 | Rel-17 | CR on HARQ timing for CEMode B |
R1-2310654
| revised | RAN1#114-bis | Lenovo, Ericsso... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1437 | - | F | 16.9.0 | Rel-16 | CR on HARQ timing for CEMode B |
R1-2310653
| agreed | RAN1#114-bis | Lenovo, Ericsso... |
RP-233724
| approved | RAN#102 | RAN1 | 16.10.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1436 | - | B | 17.5.0 | Rel-18 | Introduction of IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
R1-2308693
| agreed | RAN1#114 | Motorola Mobility |
RP-232475
| approved | RAN#101 | RAN1 | 18.0.0 | IoT_NTN_enh-Core |
|
|
|
| 36.213 | 1435 | 1 | F | 17.4.0 | Rel-17 | CR on corrections to eMTC support for IoT NTN in TDD |
R1-2302181
| agreed | RAN1#112 | Moderator (Sony... |
RP-230448
| approved | RAN#99 | RAN1 | 17.5.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1435 | - | F | 17.4.0 | Rel-17 | CR on corrections to eMTC support for NTN |
R1-2302018
| revised | RAN1#112 | Moderator (Sony) |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1434 | - | F | 17.3.0 | Rel-17 | Correction on repetition number acquisition for NPDSCH and NPUSCH with 16-QAM |
R1-2212977
| agreed | RAN1#111 | Moderator (Huaw... |
RP-222860
| approved | RAN#98-e | RAN1 | 17.4.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1433 | - | F | 17.3.0 | Rel-17 | Editorial corrections to NB-IoT/eMTC support for Non-Terrestrial Networks |
R1-2210794
| agreed | RAN1#110-bis-e | Motorola Mobility |
RP-222861
| approved | RAN#98-e | RAN1 | 17.4.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1432 | - | F | 17.3.0 | Rel-17 | CR on UE pre-compensation in segment |
R1-2210562
| withdrawn | RAN1#110-bis-e | Moderator (MediaTek) |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1431 | - | F | 17.3.0 | Rel-17 | DRAFT CR Clarification on the no acquisition of the repetition number via DCI for 16-QAM transmissions in NB-IoT |
R1-2210072
| not pursued | RAN1#110-bis-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1430 | - | F | 17.3.0 | Rel-17 | DRAFT CR Missing Koffset in FDD HARQ-ACK reporting procedure |
R1-2210070
| not pursued | RAN1#110-bis-e | Ericsson |
| | | | | IoT_NTN_enh |
|
|
|
| 36.213 | 1429 | - | A | 16.8.0 | Rel-16 | CR on the CSI periodic reporting for dormant SCell state in Rel16 |
R1-2208256
| agreed | RAN1#110 | Moderator (Samsung) |
RP-222420
| approved | RAN#97-e | RAN1 | 16.9.0 | LTE_euCA-Core |
|
|
|
| 36.213 | 1428 | - | F | 15.15.0 | Rel-15 | CR on the CSI periodic reporting for dormant SCell state in Rel15 |
R1-2208255
| agreed | RAN1#110 | Moderator (Samsung) |
RP-222420
| approved | RAN#97-e | RAN1 | 15.16.0 | LTE_euCA-Core |
|
|
|
| 36.213 | 1427 | - | F | 17.2.0 | Rel-17 | Clarification on TBS range of QPSK for NUPSCH |
R1-2208251
| agreed | RAN1#110 | Moderator (Huaw... |
RP-222408
| approved | RAN#97-e | RAN1 | 17.3.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1426 | 1 | F | 17.2.0 | Rel-17 | CR on FDD HARQ-ACK reporting procedure |
R1-2208237
| agreed | RAN1#110 | Moderator (MediaTek) |
RP-222409
| approved | RAN#97-e | RAN1 | 17.3.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1426 | - | F | 17.2.0 | Rel-17 | CR on FDD HARQ-ACK reporting procedure |
R1-2208223
| revised | RAN1#110 | Moderator (MediaTek) |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1425 | - | F | 17.2.0 | Rel-17 | Correction on determination of TBS for NPDSCH |
R1-2208177
| agreed | RAN1#110 | ASUSTeK |
RP-222416
| approved | RAN#97-e | RAN1 | 17.3.0 | NB_IOTenh-Core,... |
|
|
|
| 36.213 | 1424 | 1 | F | 17.2.0 | Rel-17 | CR on UE pre-compensation in segment |
R1-2208238
| agreed | RAN1#110 | Moderator (MediaTek) |
RP-222409
| approved | RAN#97-e | RAN1 | 17.3.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1424 | - | F | 17.2.0 | Rel-17 | CR on UE pre-compensation in segment |
R1-2208176
| revised | RAN1#110 | Moderator (MediaTek) |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1423 | - | F | 17.2.0 | Rel-17 | Missing DCI formats when mapping ACKNACK resource offset field |
R1-2208087
| agreed | RAN1#110 | Ericsson |
RP-222416
| approved | RAN#97-e | RAN1 | 17.3.0 | LTE_MTCe2_L1-Co... |
|
|
|
| 36.213 | 1422 | - | D | 17.2.0 | Rel-17 | DRAFT CR Misssing DCI formats when mapping ACKNACK resource offset field |
R1-2207575
| not pursued | RAN1#110 | Ericsson |
| | | | | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1421 | - | F | 17.2.0 | Rel-17 | DRAFT CR on timing relationship enhancements for IoT NTN |
R1-2207569
| not pursued | RAN1#110 | Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.213 | 1420 | - | F | 17.1.0 | Rel-17 | Corrections to Additional Enhancements for NB-IoT and LTE-MTC |
R1-2205666
| agreed | RAN1#109-e | Motorola Mobility |
RP-221608
| approved | RAN#96 | RAN1 | 17.2.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1419 | - | F | 17.1.0 | Rel-17 | Corrections to NB-IoT/eMTC support for Non-Terrestrial Networks |
R1-2205665
| agreed | RAN1#109-e | Motorola Mobility |
RP-221609
| approved | RAN#96 | RAN1 | 17.2.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1418 | - | F | 17.0.0 | Rel-17 | Corrections to Additional Enhancements for NB-IoT and LTE-MTC |
R1-2202974
| agreed | RAN1#108-e | Motorola Mobility |
RP-220258
| approved | RAN#95-e | RAN1 | 17.1.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1417 | - | F | 17.0.0 | Rel-17 | Corrections to NB-IoT/eMTC support for Non-Terrestrial Networks |
R1-2202973
| agreed | RAN1#108-e | Motorola Mobility |
RP-220260
| approved | RAN#95-e | RAN1 | 17.1.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1416 | - | F | 17.0.0 | Rel-17 | Clarification on PDSCH scheduling delay for 14-HARQ processes |
R1-2202888
| not pursued | RAN1#108-e | Moderator (ZTE)... |
| | | | | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1415 | - | F | 17.0.0 | Rel-17 | Clarification on the support of 16-QAM for NB-IoT in TS 36.213 |
R1-2202281
| not pursued | RAN1#108-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1414 | - | B | 16.7.1 | Rel-17 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s14-sxx |
R1-2112913
| agreed | RAN1#107-e | Motorola Mobility |
RP-212976
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1413 | - | B | 16.7.1 | Rel-17 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s10-s13 |
R1-2112912
| agreed | RAN1#107-e | Motorola Mobility |
RP-212976
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1412 | - | B | 16.7.1 | Rel-17 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s08-s09 |
R1-2112911
| agreed | RAN1#107-e | Motorola Mobility |
RP-212976
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1411 | - | B | 16.7.1 | Rel-17 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s06-s07 |
R1-2112910
| agreed | RAN1#107-e | Motorola Mobility |
RP-212976
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1410 | - | B | 16.7.1 | Rel-17 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s00-s05 |
R1-2112909
| agreed | RAN1#107-e | Motorola Mobility |
RP-212976
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.213 | 1409 | - | B | 16.7.1 | Rel-17 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s14-xx |
R1-2112908
| agreed | RAN1#107-e | Motorola Mobility |
RP-212974
| approved | RAN#94-e | RAN1 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1408 | - | B | 16.7.1 | Rel-17 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s10-s13 |
R1-2112907
| agreed | RAN1#107-e | Motorola Mobility |
RP-212974
| approved | RAN#94-e | RAN1 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1407 | - | B | 16.7.1 | Rel-17 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s06-07 |
R1-2112906
| agreed | RAN1#107-e | Motorola Mobility |
RP-212974
| approved | RAN#94-e | RAN1 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
|
| 36.213 | 1406 | - | B | 16.7.1 | Rel-17 | Introduction of New bands and bandwidth allocation for LTE based 5G terrestrial broadcast in 36.213 s10-s13 |
R1-2112905
| agreed | RAN1#107-e | Motorola Mobility |
RP-212975
| approved | RAN#94-e | RAN1 | 17.0.0 | LTE_terr_bcast_... |
|
|
|
| 36.213 | 1405 | - | F | 16.7.1 | Rel-16 | Clarification on HARQ bundling for LTE-M MTB scheduling in FDD |
R1-2112713
| agreed | RAN1#107-e | Moderator (ZTE)... |
RP-212963
| approved | RAN#94-e | RAN1 | 16.8.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1404 | - | A | 16.7.1 | Rel-16 | Clarification on NPDSCH and NPDCCH starting position for TDD NB-IoT |
R1-2112366
| not pursued | RAN1#107-e | Ericsson |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1403 | - | F | 15.15.0 | Rel-15 | Clarification on NPDSCH and NPDCCH starting position for TDD NB-IoT |
R1-2112365
| not pursued | RAN1#107-e | Ericsson |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1402 | - | A | 16.6.0 | Rel-16 | Clarification on the deployment mode indicator for NB-IoT |
R1-2108652
| agreed | RAN1#106-e | Moderator (Eric... |
RP-211849
| approved | RAN#93-e | RAN1 | 16.7.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1401 | - | F | 15.14.0 | Rel-15 | Clarification on the deployment mode indicator for NB-IoT |
R1-2108651
| agreed | RAN1#106-e | Moderator (Eric... |
RP-211849
| approved | RAN#93-e | RAN1 | 15.15.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1400 | - | F | 16.5.0 | Rel-16 | Alignment CR on RRC parameter name for single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA |
R1-2106378
| agreed | RAN1#105-e | Lenovo, Motorol... |
RP-211239
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1399 | - | A | 16.5.0 | Rel-16 | Alignment CR on RRC parameter names for EN-DC/NE-DC Coexistence (mirrored to Rel-16) |
R1-2106377
| agreed | RAN1#105-e | Lenovo, Motorol... |
RP-211233
| approved | RAN#92-e | RAN1 | 16.6.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1398 | - | F | 15.13.0 | Rel-15 | Alignment CR on RRC parameter names for EN-DC/NE-DC Coexistence |
R1-2106376
| agreed | RAN1#105-e | Lenovo, Motorol... |
RP-211233
| approved | RAN#92-e | RAN1 | 15.14.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1397 | - | F | 16.5.0 | Rel-16 | Clarification on UE procedure for uplink MTB scheduling in TDD |
R1-2106306
| agreed | RAN1#105-e | Moderator (Eric... |
RP-211241
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1396 | - | F | 16.5.0 | Rel-16 | Correction on PUCCH transmit power control for LTE-M |
R1-2104035
| agreed | RAN1#104-bis-e | Moderator (Eric... |
RP-211241
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1395 | - | F | 16.5.0 | Rel-16 | Correction on subcarrier indication for PUR |
R1-2104016
| agreed | RAN1#104-bis-e | Moderator (Huaw... |
RP-211242
| approved | RAN#92-e | RAN1 | 16.6.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1394 | - | F | 16.5.0 | Rel-16 | Correction on multi-TB scheduling for NB-IoT |
R1-2103998
| agreed | RAN1#104-bis-e | Moderator (Huaw... |
RP-211242
| approved | RAN#92-e | RAN1 | 16.6.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1393 | - | F | 16.5.0 | Rel-16 | Correction on additional SRS symbols |
R1-2103934
| agreed | RAN1#104-bis-e | Huawei, HiSilicon |
RP-211244
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1392 | - | A | 16.5.0 | Rel-16 | Correction on PDSCH dropping for multicast in special subframe |
R1-2103922
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1391 | - | A | 15.13.0 | Rel-15 | Correction on PDSCH dropping for multicast in special subframe |
R1-2103921
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 15.14.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1390 | - | F | 14.16.0 | Rel-14 | Correction on PDSCH dropping for multicast in special subframe |
R1-2103920
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 14.17.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1389 | - | A | 16.5.0 | Rel-16 | Correction on MPDCCH assignment procedure |
R1-2103919
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 16.6.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1388 | - | A | 15.13.0 | Rel-15 | Correction on MPDCCH assignment procedure |
R1-2103918
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 15.14.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1387 | - | F | 14.16.0 | Rel-14 | Correction on MPDCCH assignment procedure |
R1-2103917
| agreed | RAN1#104-bis-e | ZTE |
RP-211245
| approved | RAN#92-e | RAN1 | 14.17.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1386 | - | A | 16.5.0 | Rel-16 | Clarification on the UE transmit power for the 2-of-3 subcarrier allocation in sub-PRB |
R1-2103730
| not pursued | RAN1#104-bis-e | Ericsson |
| | | | | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1385 | - | F | 15.13.0 | Rel-15 | Clarification on the UE transmit power for the 2-of-3 subcarrier allocation in sub-PRB |
R1-2103729
| not pursued | RAN1#104-bis-e | Ericsson |
| | | | | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1384 | - | F | 16.4.0 | Rel-16 | PUR correction on parameter name for DL carrier |
R1-2102212
| agreed | RAN1#104-e | Moderator (Huaw... |
RP-210057
| approved | RAN#91-e | RAN1 | 16.5.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1383 | - | F | 16.4.0 | Rel-16 | Correction on transmission scheme for NPDSCH configured by PUR-RNTI |
R1-2102210
| agreed | RAN1#104-e | Moderator (Huaw... |
RP-210057
| approved | RAN#91-e | RAN1 | 16.5.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1382 | - | F | 16.4.0 | Rel-16 | Correction on multicast gap in multi-TB scheduling in LTE-MTC |
R1-2102203
| agreed | RAN1#104-e | Moderator (Eric... |
RP-210056
| approved | RAN#91-e | RAN1 | 16.5.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1381 | - | F | 16.4.0 | Rel-16 | Correction on HARQ process number for SPS validation when multi-TB is configured |
R1-2102157
| agreed | RAN1#104-e | Moderator (Eric... |
RP-210056
| approved | RAN#91-e | RAN1 | 16.5.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1380 | - | F | 16.4.0 | Rel-16 | Correction on determination of number of scheduled TB for SC-MTCH |
R1-2102065
| agreed | RAN1#104-e | Moderator (ZTE)... |
RP-210057
| approved | RAN#91-e | RAN1 | 16.5.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1379 | 1 | F | 16.4.0 | Rel-16 | PUR correction on PUSCH Repetition Adjustment |
R1-2102109
| agreed | RAN1#104-e | Moderator (Sier... |
RP-210056
| approved | RAN#91-e | RAN1 | 16.5.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1379 | - | F | 16.4.0 | Rel-16 | PUR correction on PUSCH Repetition Adjustment |
R1-2102038
| revised | RAN1#104-e | Moderator (Sier... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1378 | - | A | 16.4.0 | Rel-16 | Clarification on power control for NB-IoT |
R1-2101982
| agreed | RAN1#104-e | ZTE, Ericsson |
RP-210063
| approved | RAN#91-e | RAN1 | 16.5.0 | NB_IOT-Core, TEI15 |
|
|
|
| 36.213 | 1377 | - | F | 15.12.0 | Rel-15 | Clarification on power control for NB-IoT |
R1-2101981
| agreed | RAN1#104-e | ZTE, Ericsson |
RP-210063
| approved | RAN#91-e | RAN1 | 15.13.0 | NB_IOT-Core, TEI15 |
|
|
|
| 36.213 | 1376 | - | A | 16.4.0 | Rel-16 | Correction on spectral efficiency of 1024QAM |
R1-2101944
| agreed | RAN1#104-e | Huawei, HiSilicon |
RP-210060
| approved | RAN#91-e | RAN1 | 16.5.0 | LTE_1024QAM_DL-Core |
|
|
|
| 36.213 | 1375 | - | F | 15.12.0 | Rel-15 | Correction on spectral efficiency of 1024QAM |
R1-2101943
| agreed | RAN1#104-e | Huawei, HiSilicon |
RP-210060
| approved | RAN#91-e | RAN1 | 15.13.0 | LTE_1024QAM_DL-Core |
|
|
|
| 36.213 | 1374 | - | F | 16.3.0 | Rel-16 | Flexible bandwidth for MBMS |
| | | |
RP-202412
| postponed | RAN#90-e | EBU | | LTE_terr_bcast-Core |
|
|
|
| 36.213 | 1373 | - | F | 16.3.0 | Rel-16 | Alignment of terminology for Rel-16 Additional MTC Enhancements for LTE |
R1-2009764
| agreed | RAN1#103-e | Lenovo, Motorol... |
RP-202391
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1372 | - | F | 16.3.0 | Rel-16 | 36.213 CR on Single UL Tx for EN-DC |
R1-2009634
| agreed | RAN1#103-e | Moderator (Noki... |
RP-202389
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1371 | - | F | 16.3.0 | Rel-16 | Corrections on PUR-RNTI for NB-IoT |
R1-2009620
| agreed | RAN1#103-e | Moderator (Huaw... |
RP-202392
| approved | RAN#90-e | RAN1 | 16.4.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1370 | - | F | 16.3.0 | Rel-16 | Corrections on UE-specific search space by PUR-RNTI |
R1-2009618
| agreed | RAN1#103-e | Moderator (Huaw... |
RP-202392
| approved | RAN#90-e | RAN1 | 16.4.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1369 | - | F | 16.3.0 | Rel-16 | Correction on TPC command for multi-TB scheduling in LTE-MTC |
R1-2009614
| agreed | RAN1#103-e | Moderator (Eric... |
RP-202391
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1368 | 1 | F | 16.3.0 | Rel-16 | Corrections for multi-TB early termination |
R1-2009840
| agreed | RAN1#103-e | Moderator (Eric... |
RP-202391
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1368 | - | F | 16.3.0 | Rel-16 | Corrections for multi-TB early termination |
R1-2009612
| revised | RAN1#103-e | Moderator (Eric... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1367 | - | F | 16.3.0 | Rel-16 | Power sharing for LTE DAPS |
R1-2009528
| agreed | RAN1#103-e | Moderator (Qual... |
RP-202399
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_feMob-Core |
|
|
|
| 36.213 | 1366 | - | F | 16.3.0 | Rel-16 | Correction on HARQ process ID assumption for multi-TB |
R1-2009467
| agreed | RAN1#103-e | Moderator (ZTE) |
RP-202392
| approved | RAN#90-e | RAN1 | 16.4.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1365 | - | F | 16.3.0 | Rel-16 | PUR configuration of transmission mode |
R1-2009443
| agreed | RAN1#103-e | Moderator (Sier... |
RP-202391
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1364 | - | A | 16.3.0 | Rel-16 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.213 |
R1-2009441
| agreed | RAN1#103-e | Huawei, HiSilicon |
RP-202400
| approved | RAN#90-e | RAN1 | 16.4.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1363 | - | F | 15.11.0 | Rel-15 | Corrections on preamble format indicator presence in NPDCCH order in TS 36.213 |
R1-2009440
| agreed | RAN1#103-e | Huawei, HiSilicon |
RP-202400
| approved | RAN#90-e | RAN1 | 15.12.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1362 | - | A | 16.3.0 | Rel-16 | Clarification on the subcarrier allocation for sub-PRB in CE Mode B |
R1-2009437
| agreed | RAN1#103-e | Ericsson |
RP-202396
| approved | RAN#90-e | RAN1 | 16.4.0 | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1361 | - | F | 15.11.0 | Rel-15 | Clarification on the subcarrier allocation for sub-PRB in CE Mode B |
R1-2009436
| agreed | RAN1#103-e | Ericsson |
RP-202396
| approved | RAN#90-e | RAN1 | 15.12.0 | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1360 | - | F | 16.2.0 | Rel-16 | Correction on PUR-RNTI for NB-IoT for NB-IoT in 36.213 |
R1-2007409
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201816
| approved | RAN#89-e | RAN1 | 16.3.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1359 | - | F | 16.2.0 | Rel-16 | Correction on terms and higher layer parameters for NB-IoT in 36.213 |
R1-2007407
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201816
| approved | RAN#89-e | RAN1 | 16.3.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1358 | - | F | 16.2.0 | Rel-16 | Correction on SRS carrier switching |
R1-2007317
| withdrawn | RAN1#102-e | CATT |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.213 | 1357 | - | F | 15.10.0 | Rel-15 | Correction on SRS carrier switching |
R1-2007316
| withdrawn | RAN1#102-e | CATT |
| | | | | NR_newRAT-Core |
|
|
|
| 36.213 | 1356 | - | F | 16.2.0 | Rel-16 | Missing 'else' in RV determination in UL multi-TB scheduling in LTE-MTC |
R1-2007309
| agreed | RAN1#102-e | Moderator (Ericsson) |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1355 | - | F | 16.2.0 | Rel-16 | Number of HARQ processes in multi-TB scheduling in CE mode B in TDD in LTE-MTC |
R1-2007307
| agreed | RAN1#102-e | Moderator (Ericsson) |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1354 | - | F | 16.2.0 | Rel-16 | Clarifications for PUR Repetition Adjustment |
R1-2007300
| agreed | RAN1#102-e | Moderator (Sier... |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1353 | - | F | 16.2.0 | Rel-16 | Add PUR allocation procedures to UL resource allocation type 5 |
R1-2007299
| agreed | RAN1#102-e | Moderator (Sier... |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1352 | - | F | 16.2.0 | Rel-16 | Corrections on PUR collision handling |
R1-2007298
| agreed | RAN1#102-e | Moderator (Sier... |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1351 | - | F | 16.2.0 | Rel-16 | Clarifications for the PUR UE-specific search space |
R1-2007297
| agreed | RAN1#102-e | Moderator (Sier... |
RP-201815
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1350 | - | F | 16.2.0 | Rel-16 | Correction on higher layer parameters for additional SRS in 36.213 |
R1-2007279
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201817
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1349 | - | F | 16.2.0 | Rel-16 | Correction on configuration of multiTB-Gap |
R1-2007271
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201816
| approved | RAN#89-e | RAN1 | 16.3.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1348 | - | F | 16.2.0 | Rel-16 | Corrections on PUR collision handling |
R1-2007212
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201816
| approved | RAN#89-e | RAN1 | 16.3.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1347 | - | F | 16.2.0 | Rel-16 | Corrections on L1 adjustment on the NPUSCH repetition number |
R1-2007211
| agreed | RAN1#102-e | Moderator (Huawei) |
RP-201816
| approved | RAN#89-e | RAN1 | 16.3.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1346 | - | A | 16.2.0 | Rel-16 | Correction on SPDCCH monitoring of an MBSFN subframe |
R1-2007167
| agreed | RAN1#102-e | Huawei, HiSilic... |
RP-201823
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1345 | - | F | 15.10.0 | Rel-15 | Correction on SPDCCH monitoring of an MBSFN subframe |
R1-2007166
| agreed | RAN1#102-e | Huawei, HiSilic... |
RP-201823
| approved | RAN#89-e | RAN1 | 15.11.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1344 | - | A | 16.2.0 | Rel-16 | Correction on CFI related parameter names alignment between TS 36.331 and TS 36.213 |
R1-2007165
| agreed | RAN1#102-e | Motorola Mobili... |
RP-201822
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_HRLLC-Core |
|
|
|
| 36.213 | 1343 | - | F | 15.10.0 | Rel-15 | Correction on CFI related parameter names alignment between TS 36.331 and TS 36.213 |
R1-2007164
| agreed | RAN1#102-e | Motorola Mobili... |
RP-201822
| approved | RAN#89-e | RAN1 | 15.11.0 | LTE_HRLLC-Core |
|
|
|
| 36.213 | 1342 | - | A | 16.2.0 | Rel-16 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 |
R1-2007131
| agreed | RAN1#102-e | Sharp |
RP-201819
| approved | RAN#89-e | RAN1 | 16.3.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1341 | - | A | 15.10.0 | Rel-15 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 |
R1-2007130
| agreed | RAN1#102-e | Sharp |
RP-201819
| approved | RAN#89-e | RAN1 | 15.11.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1340 | - | F | 14.15.0 | Rel-14 | Correction on conditions for selecting resources when the number of HARQ transmissions is two in sidelink transmission mode 4 |
R1-2007129
| agreed | RAN1#102-e | Sharp |
RP-201819
| approved | RAN#89-e | RAN1 | 14.16.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1339 | - | F | 16.1.0 | Rel-16 | Corrections to single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA |
R1-2005182
| agreed | RAN1#101-e | Motorola Mobility |
RP-200696
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1338 | 1 | F | 16.1.0 | Rel-16 | Corrections to DL MIMO efficiency enhancements for LTE |
R1-2005190
| agreed | RAN1#101-e | Motorola Mobility |
RP-200700
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1338 | - | F | 16.1.0 | Rel-16 | Corrections to DL MIMO efficiency enhancements for LTE |
R1-2005181
| revised | RAN1#101-e | Motorola Mobility |
| | | | | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1337 | - | F | 16.1.0 | Rel-16 | Corrections to Additional MTC Enhancements for LTE |
R1-2005180
| agreed | RAN1#101-e | Motorola Mobility |
RP-200698
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1336 | 1 | F | 16.1.0 | Rel-16 | Corrections to LTE-based 5G terrestrial broadcast |
R1-2005189
| agreed | RAN1#101-e | Motorola Mobility |
RP-200701
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_terr_bcast-Core |
|
|
|
| 36.213 | 1336 | - | F | 16.1.0 | Rel-16 | Corrections to LTE-based 5G terrestrial broadcast |
R1-2005179
| revised | RAN1#101-e | Motorola Mobility |
| | | | | LTE_terr_bcast-Core |
|
|
|
| 36.213 | 1335 | - | F | 16.1.0 | Rel-16 | Corrections to Additional enhancements for NB-IoT |
R1-2005178
| agreed | RAN1#101-e | Motorola Mobility |
RP-200699
| approved | RAN#88-e | RAN1 | 16.2.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1334 | - | F | 16.1.0 | Rel-16 | Corrections to DL MIMO efficiency enhancements for LTE |
R1-2003158
| merged | RAN1#100-bis-e | Motorola Mobility |
| | | | | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1333 | - | F | 16.1.0 | Rel-16 | Corrections to Additional MTC Enhancements for LTE |
R1-2003157
| merged | RAN1#100-bis-e | Motorola Mobility |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1332 | - | F | 16.1.0 | Rel-16 | Corrections to LTE-based 5G terrestrial broadcast |
R1-2003156
| merged | RAN1#100-bis-e | Motorola Mobility |
| | | | | LTE_terr_bcast-Core |
|
|
|
| 36.213 | 1331 | - | F | 16.1.0 | Rel-16 | Corrections to Additional enhancements for NB-IoT |
R1-2003155
| merged | RAN1#100-bis-e | Motorola Mobility |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1330 | - | A | 16.1.0 | Rel-16 | Correction on NPDCCH monitoring for NB-IoT |
R1-2002959
| agreed | RAN1#100-bis-e | Huawei, HiSilicon |
RP-200704
| approved | RAN#88-e | RAN1 | 16.2.0 | NB_IOTenh-Core |
|
|
|
| 36.213 | 1329 | - | A | 15.9.0 | Rel-15 | Correction on NPDCCH monitoring for NB-IoT |
R1-2002958
| agreed | RAN1#100-bis-e | Huawei, HiSilicon |
RP-200704
| approved | RAN#88-e | RAN1 | 15.10.0 | NB_IOTenh-Core |
|
|
|
| 36.213 | 1328 | - | F | 14.14.0 | Rel-14 | Correction on NPDCCH monitoring for NB-IoT |
R1-2002957
| agreed | RAN1#100-bis-e | Huawei, HiSilicon |
RP-200704
| approved | RAN#88-e | RAN1 | 14.15.0 | NB_IOTenh-Core |
|
|
|
| 36.213 | 1327 | - | A | 16.1.0 | Rel-16 | CR on excluding TDD special subframes for MWUS maximum and actual duration |
R1-2002921
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200681
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1326 | - | F | 15.9.0 | Rel-15 | CR on excluding TDD special subframes for MWUS maximum and actual duration |
R1-2002920
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200681
| approved | RAN#88-e | RAN1 | 15.10.0 | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1325 | - | A | 16.1.0 | Rel-16 | Correction on Msg3 NPUSCH retransmission for NB-IoT EDT |
R1-2002835
| agreed | RAN1#100-bis-e | Huawei, HiSilicon |
RP-200684
| approved | RAN#88-e | RAN1 | 16.2.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1324 | - | F | 15.9.0 | Rel-15 | Correction on Msg3 NPUSCH retransmission for NB-IoT EDT |
R1-2002834
| agreed | RAN1#100-bis-e | Huawei, HiSilicon |
RP-200684
| approved | RAN#88-e | RAN1 | 15.10.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1323 | - | A | 16.1.0 | Rel-16 | Clarification on PUCCH collision for HARQ-ACK bundling |
R1-2002778
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1322 | - | A | 15.9.0 | Rel-15 | Clarification on PUCCH collision for HARQ-ACK bundling |
R1-2002777
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 15.10.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1321 | - | A | 16.1.0 | Rel-16 | Clarification on set of values for HARQ delay |
R1-2002776
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 16.2.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1320 | - | A | 15.9.0 | Rel-15 | Clarification on set of values for HARQ delay |
R1-2002775
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 15.10.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1319 | - | A | 16.1.0 | Rel-16 | Correction on PUSCH and PDSCH scheduling with CSS |
R1-2002767
| agreed | RAN1#100-bis-e | Nokia, Nokia Sh... |
RP-200683
| approved | RAN#88-e | RAN1 | 16.2.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1318 | - | F | 15.9.0 | Rel-15 | Correction on PUSCH and PDSCH scheduling with CSS |
R1-2002766
| agreed | RAN1#100-bis-e | Nokia, Nokia Sh... |
RP-200683
| approved | RAN#88-e | RAN1 | 15.10.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1317 | - | F | 14.14.0 | Rel-14 | Clarification on PUCCH collision for HARQ-ACK bundling |
R1-2002172
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 14.15.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1316 | 1 | F | 14.14.0 | Rel-14 | Clarification on set of values for HARQ delay |
R1-2002773
| not pursued | RAN1#100-bis-e | Qualcomm Incorp... |
| | | | | LTE_feMTC-Core |
|
|
|
| 36.213 | 1316 | - | F | 14.14.0 | Rel-14 | Clarification on set of values for HARQ delay |
R1-2002171
| agreed | RAN1#100-bis-e | Qualcomm Incorp... |
RP-200682
| approved | RAN#88-e | RAN1 | 14.15.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1315 | - | F | 16.0.0 | Rel-16 | Corrections to DL MIMO efficiency enhancements for LTE |
R1-2001436
| agreed | RAN1#100-e | Motorola Mobility |
RP-200198
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1314 | - | F | 16.0.0 | Rel-16 | Corrections to single Tx switched uplink solution for EN-DC feature of Rel-16 MR DC/CA |
R1-2001435
| agreed | RAN1#100-e | Motorola Mobility |
RP-200194
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1313 | - | F | 16.0.0 | Rel-16 | Corrections to Additional enhancements for NB-IoT |
R1-2001434
| agreed | RAN1#100-e | Motorola Mobility |
RP-200197
| approved | RAN#87-e | RAN1 | 16.1.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1312 | - | F | 16.0.0 | Rel-16 | Corrections to Additional MTC Enhancements for LTE |
R1-2001433
| agreed | RAN1#100-e | Motorola Mobility |
RP-200196
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1311 | - | A | 16.0.0 | Rel-16 | Clarification on MPDCCH monitoring during UL gaps |
R1-2001381
| agreed | RAN1#100-e | ZTE, Sanechips |
RP-200180
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1310 | - | A | 15.8.0 | Rel-15 | Clarification on MPDCCH monitoring during UL gaps |
R1-2001380
| agreed | RAN1#100-e | ZTE, Sanechips |
RP-200180
| approved | RAN#87-e | RAN1 | 15.9.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1309 | - | A | 14.13.0 | Rel-14 | Clarification on MPDCCH monitoring during UL gaps |
R1-2001379
| agreed | RAN1#100-e | ZTE, Sanechips |
RP-200180
| approved | RAN#87-e | RAN1 | 14.14.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1308 | - | F | 13.15.0 | Rel-13 | Clarification on MPDCCH monitoring during UL gaps |
R1-2001378
| agreed | RAN1#100-e | ZTE, Sanechips |
RP-200180
| approved | RAN#87-e | RAN1 | 13.16.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1307 | - | A | 16.0.0 | Rel-16 | Correction on Msg3 NPUSCH for NB-IoT EDT |
R1-2001336
| agreed | RAN1#100-e | Huawei, HiSilicon |
RP-200182
| approved | RAN#87-e | RAN1 | 16.1.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1306 | - | A | 16.0.0 | Rel-16 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs |
R1-2001332
| agreed | RAN1#100-e | Huawei, HiSilicon |
RP-200179
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1305 | - | A | 15.8.0 | Rel-15 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs |
R1-2001331
| agreed | RAN1#100-e | Huawei, HiSilicon |
RP-200179
| approved | RAN#87-e | RAN1 | 15.9.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1304 | - | F | 14.13.0 | Rel-14 | Corrections on the indication value for the transport blocks in a bundle for HD-FDD eMTC UEs |
R1-2001330
| agreed | RAN1#100-e | Huawei, HiSilicon |
RP-200179
| approved | RAN#87-e | RAN1 | 14.14.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1303 | - | A | 16.0.0 | Rel-16 | Correction on priority value in LTE V2X |
R1-2001329
| agreed | RAN1#100-e | Sharp |
RP-200201
| approved | RAN#87-e | RAN1 | 16.1.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1302 | - | F | 15.8.0 | Rel-15 | Correction on Msg3 NPUSCH for NB-IoT EDT |
R1-2001326
| agreed | RAN1#100-e | Huawei, HiSilicon |
RP-200182
| approved | RAN#87-e | RAN1 | 15.9.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1301 | - | A | 15.8.0 | Rel-15 | Correction on priority value in LTE V2X |
R1-2001325
| agreed | RAN1#100-e | Sharp |
RP-200201
| approved | RAN#87-e | RAN1 | 15.9.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1300 | - | F | 14.13.0 | Rel-14 | Correction on priority value in LTE V2X |
R1-2001224
| agreed | RAN1#100-e | Sharp |
RP-200201
| approved | RAN#87-e | RAN1 | 14.14.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1299 | - | B | 15.7.0 | Rel-16 | Introduction of of Rel-16 MR DC/CA features in 36.213 s10-13 |
R1-1913691
| agreed | RAN1#99 | Motorola Mobility |
RP-192645
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1298 | - | B | 15.7.0 | Rel-16 | Introduction of of Rel-16 MR DC/CA features in 36.213 s08-09 |
R1-1913690
| agreed | RAN1#99 | Motorola Mobility |
RP-192645
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1297 | - | B | 15.7.0 | Rel-16 | Introduction of of Rel-16 MR DC/CA features in 36.213 s06-07 |
R1-1913689
| agreed | RAN1#99 | Motorola Mobility |
RP-192645
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1296 | - | B | 15.7.0 | Rel-16 | Introduction of of Rel-16 MR DC/CA features in 36.213 s00-05 |
R1-1913688
| agreed | RAN1#99 | Motorola Mobility |
RP-192645
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_NR_DC_CA_en... |
|
|
|
| 36.213 | 1295 | - | B | 15.7.0 | Rel-16 | Introduction of Additional MTC Enhancements for LTE in 36.213 s10-s13 |
R1-1913684
| agreed | RAN1#99 | Motorola Mobility |
RP-192647
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1294 | - | B | 15.7.0 | Rel-16 | Introduction of LTE-based 5G terrestrial broadcast |
R1-1913624
| agreed | RAN1#99 | Motorola Mobility |
RP-192650
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_terr_bcast-Core |
|
|
|
| 36.213 | 1293 | - | B | 15.7.0 | Rel-16 | Introduction of configured PRG size for TM9 and TM10 in 36.213 |
R1-1913623
| agreed | RAN1#99 | Motorola Mobility |
RP-192651
| approved | RAN#86 | RAN1 | 16.0.0 | TEI16 |
|
|
|
| 36.213 | 1292 | - | B | 15.7.0 | Rel-16 | Introduction of DL MIMO efficiency enhancements for LTE |
R1-1913621
| agreed | RAN1#99 | Motorola Mobility |
RP-192649
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.213 | 1291 | - | B | 15.7.0 | Rel-16 | Introduction of Additional enhancements for NB-IoT |
R1-1913618
| agreed | RAN1#99 | Motorola Mobility |
RP-192648
| approved | RAN#86 | RAN1 | 16.0.0 | NB_IOTenh3-Core |
|
|
|
| 36.213 | 1290 | - | B | 15.7.0 | Rel-16 | Introduction of Additional MTC Enhancements for LTE in 36.213 s14-sxx |
R1-1913615
| agreed | RAN1#99 | Motorola Mobility |
RP-192647
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1289 | - | B | 15.7.0 | Rel-16 | Introduction of Additional MTC Enhancements for LTE in 36.213 s08-s09 |
R1-1913614
| agreed | RAN1#99 | Motorola Mobility |
RP-192647
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1288 | - | B | 15.7.0 | Rel-16 | Introduction of Additional MTC Enhancements for LTE in 36.213 s06-s07 |
R1-1913613
| agreed | RAN1#99 | Motorola Mobility |
RP-192647
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1287 | - | B | 15.7.0 | Rel-16 | Introduction of Additional MTC Enhancements for LTE in 36.213 s00-s05 |
R1-1913612
| agreed | RAN1#99 | Motorola Mobility |
RP-192647
| approved | RAN#86 | RAN1 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.213 | 1286 | - | F | 15.7.0 | Rel-15 | Correction on TPC accumulation reset for short TTI |
R1-1913415
| agreed | RAN1#99 | LG Electronics |
RP-192630
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1285 | - | A | 15.7.0 | Rel-15 | Clarification for PUCCH resource determination with HARQ-ACK bundling |
R1-1913411
| agreed | RAN1#99 | Qualcomm Incorp... |
RP-192619
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1284 | - | F | 14.12.0 | Rel-14 | Clarification for PUCCH resource determination with HARQ-ACK bundling |
R1-1913410
| agreed | RAN1#99 | Qualcomm Incorp... |
RP-192619
| approved | RAN#86 | RAN1 | 14.13.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1283 | - | F | 15.7.0 | Rel-15 | Correction to 64-QAM TBS determination for eMTC |
R1-1913409
| agreed | RAN1#99 | Qualcomm Incorp... |
RP-192618
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_eMTC4-Core |
|
|
|
| 36.213 | 1282 | - | F | 15.7.0 | Rel-15 | Correction on PUSCH scheduling with CSS for Case 1 HARQ timing |
R1-1913357
| agreed | RAN1#99 | Huawei, HiSilicon |
RP-192622
| approved | RAN#86 | RAN1 | 15.8.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1281 | - | F | 15.7.0 | Rel-15 | NPDCCH start position for special subframe |
R1-1913339
| agreed | RAN1#99 | Huawei, HiSilicon |
RP-192633
| approved | RAN#86 | RAN1 | 15.8.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1280 | - | F | 15.7.0 | Rel-15 | Correction on SPDCCH monitoring for TS 36.213 |
R1-1911396
| agreed | RAN1#98-Bis | Samsung |
RP-192630
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1279 | - | F | 15.7.0 | Rel-15 | Correction on antenna switching parameter in UE sounding procedure in 36.213 |
R1-1911367
| agreed | RAN1#98-Bis | Huawei, HiSilicon |
RP-192621
| approved | RAN#86 | RAN1 | 15.8.0 | TEI15 |
|
|
|
| 36.213 | 1278 | - | A | 15.7.0 | Rel-15 | Correction to HARQ-ACK delay |
R1-1911366
| agreed | RAN1#98-Bis | Qualcomm Incorp... |
RP-192619
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1277 | - | F | 14.12.0 | Rel-14 | Correction to HARQ-ACK delay |
R1-1911365
| agreed | RAN1#98-Bis | Qualcomm Incorp... |
RP-192619
| approved | RAN#86 | RAN1 | 14.13.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1276 | - | A | 15.7.0 | Rel-15 | Correction on repetition number of MPDCCH with HARQ-ACK bundling |
R1-1911364
| agreed | RAN1#98-Bis | Huawei, HiSilicon |
RP-192619
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1275 | - | F | 14.12.0 | Rel-14 | Correction on repetition number of MPDCCH with HARQ-ACK bundling |
R1-1911363
| agreed | RAN1#98-Bis | Huawei, HiSilicon |
RP-192619
| approved | RAN#86 | RAN1 | 14.13.0 | LTE_feMTC-Core |
|
|
|
| 36.213 | 1274 | - | A | 15.7.0 | Rel-15 | Clarification to postponing in subframes that are not BL/CE subframes |
R1-1910736
| agreed | RAN1#98-Bis | Qualcomm Incorp... |
RP-192620
| approved | RAN#86 | RAN1 | 15.8.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1273 | - | A | 14.12.0 | Rel-14 | Clarification to postponing in subframes that are not BL/CE subframes |
R1-1910711
| agreed | RAN1#98-Bis | Qualcomm Incorp... |
RP-192620
| approved | RAN#86 | RAN1 | 14.13.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1272 | - | F | 13.14.0 | Rel-13 | Clarification to postponing in subframes that are not BL/CE subframes |
R1-1910708
| agreed | RAN1#98-Bis | Qualcomm Incorp... |
RP-192620
| approved | RAN#86 | RAN1 | 13.15.0 | LTE_MTCe2_L1-Core |
|
|
|
| 36.213 | 1271 | - | F | 15.6.0 | Rel-15 | Correction on calculation of Multiple Entry PHR for EN-DC and NE-DC |
R1-1909838
| agreed | RAN1#98 | Huawei, HiSilicon |
RP-191938
| approved | RAN#85 | RAN1 | 15.7.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1270 | - | A | 15.6.0 | Rel-15 | Correction on UE procedure for transmitting PSCCH in mode 3 |
R1-1909724
| agreed | RAN1#98 | Sharp |
RP-191947
| approved | RAN#85 | RAN1 | 15.7.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1269 | - | F | 14.11.0 | Rel-14 | Correction on UE procedure for transmitting PSCCH in mode 3 |
R1-1909723
| agreed | RAN1#98 | Sharp |
RP-191947
| approved | RAN#85 | RAN1 | 14.12.0 | LTE_V2X-Core |
|
|
|
| 36.213 | 1268 | - | F | 15.6.0 | Rel-15 | Correction on high layer parameters related to EDT and SR |
R1-1909640
| agreed | RAN1#98 | ZTE, China Sout... |
RP-191936
| approved | RAN#85 | RAN1 | 15.7.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1267 | 1 | F | 15.6.0 | Rel-15 | Correction on higher layer parameter configuring short TTI length in 36.213 |
R1-1909902
| agreed | RAN1#98 | Huawei |
RP-191945
| approved | RAN#85 | RAN1 | 15.7.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1267 | - | F | 15.6.0 | Rel-15 | Correction on higher layer parameter configuring short TTI length in 36.213 |
R1-1909628
| revised | RAN1#98 | Huawei |
| | | | | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1266 | - | A | 15.6.0 | Rel-15 | Support of MPDCCH in CRS-less ssp10 |
R1-1909598
| agreed | RAN1#98 | Qualcomm Incorp... |
RP-191935
| approved | RAN#85 | RAN1 | 15.7.0 | LTE_UL_CAP_enh-Core |
|
|
|
| 36.213 | 1265 | - | F | 14.11.0 | Rel-14 | Support of MPDCCH in CRS-less ssp10 |
R1-1909597
| agreed | RAN1#98 | Qualcomm Incorp... |
RP-191935
| approved | RAN#85 | RAN1 | 14.12.0 | LTE_UL_CAP_enh-Core |
|
|
|
| 36.213 | 1264 | - | F | 15.6.0 | Rel-15 | TBS scaling with configuration of different modulation orders |
R1-1909592
| agreed | RAN1#98 | Qualcomm Incorp... |
RP-191945
| approved | RAN#85 | RAN1 | 15.7.0 | LTE_sTTIandPT-Core |
|
|
|
| 36.213 | 1263 | - | F | 15.6.0 | Rel-15 | Correction on maximum number of HARQ processes for Case 1 HARQ timing |
R1-1909574
| agreed | RAN1#98 | Huawei, HiSilicon |
RP-191938
| approved | RAN#85 | RAN1 | 15.7.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1262 | - | F | 15.5.0 | Rel-15 | Correction on calculation of Multiple Entry PHR for EN-DC and NE-DC |
R1-1907626
| agreed | RAN1#97 | Huawei, HiSilicon |
RP-191279
| approved | RAN#84 | RAN1 | 15.6.0 | NR_newRAT-Core |
|
|
|
| 36.213 | 1261 | - | F | 15.5.0 | Rel-15 | Correction on timing relationship for UE configured with EDT |
R1-1907616
| agreed | RAN1#97 | ZTE |
RP-191269
| approved | RAN#84 | RAN1 | 15.6.0 | NB_IOTenh2-Core |
|
|
|
| 36.213 | 1260 | - | A | 15.5.0 | Rel-15 | Clarification on Class A periodic CSI reporting using PUCCH |
R1-1907606
| agreed | RAN1#97 | Ericsson |
RP-191276
| approved | RAN#84 | RAN1 | 15.6.0 | LTE_EBF_FDMIMO-Core |
|
|
|
| 36.213 | 1259 | - | A | 14.10.0 | Rel-14 | Clarification on Class A periodic CSI reporting using PUCCH |
R1-1907605
| agreed | RAN1#97 | Ericsson |
RP-191276
| approved | RAN#84 | RAN1 | 14.11.0 | LTE_EBF_FDMIMO-Core |
|