|
| 36.101 | 5895 | - | F | 17.7.0 | Rel-17 | CR on cleanup for Rel-17 NPDSCH requirements with 16QAM in TS 36.101 |
R4-2219518
| agreed | RAN4#105 | Huawei, HiSilicon |
RP-223308
| approved | RAN#98-e | RAN4 | 17.8.0 | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5880 | - | B | 17.6.0 | Rel-17 | Big CR for TS 36.101 for Rel-17 NB-IoT and eMTC UE performance requirements |
R4-2214656
| agreed | RAN4#104-e | Ericsson |
RP-222029
| approved | RAN#97-e | RAN4 | 17.7.0 | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5879 | 1 | B | 17.6.0 | Rel-17 | CR: Introduction of eMTC PDSCH requirmeents with 14 HARQ processes |
R4-2214548
| endorsed | RAN4#104-e | Huawei,HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5879 | - | B | 17.6.0 | Rel-17 | CR: Introduction of eMTC PDSCH requirmeents with 14 HARQ processes |
R4-2213801
| revised | RAN4#104-e | Huawei,HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5835 | 1 | B | 17.3.0 | Rel-17 | CR IBE mask and MPR for NB-IoT 16-QAM |
R4-2119952
| agreed | RAN4#101-e | Nokia, Nokia Sh... |
RP-212843
| approved | RAN#94-e | RAN4 | 17.4.0 | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5835 | - | B | 17.3.0 | Rel-17 | CR IBE mask and MPR for NB-IoT 16-QAM |
R4-2117192
| revised | RAN4#101-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5811 | - | B | 17.2.0 | Rel-17 | CR on NB-IoT IBE mask to allow 16-QAM |
R4-2114002
| endorsed | RAN4#100-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.101 | 5750 | - | B | 17.1.0 | Rel-17 | EVM limit in NB-IoT IBE mask |
R4-2108978
| postponed | RAN4#99-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4969 | - | A | 18.0.0 | Rel-18 | Correction CR on NPUSCH format1 demodulation requirements for TS 36.104 |
R4-2302615
| agreed | RAN4#106 | Samsung |
RP-230512
| approved | RAN#99 | RAN4 | 18.1.0 | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4968 | - | F | 17.8.0 | Rel-17 | Correction CR on NPUSCH format1 demodulation requirements for TS 36.104 |
R4-2302612
| agreed | RAN4#106 | Samsung |
RP-230512
| approved | RAN#99 | RAN4 | 17.9.0 | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4962 | - | F | 17.7.0 | Rel-17 | CR on cleanup for Rel-17 NPUSCH format 1 requirements with 16QAM in TS 36.104 |
R4-2219519
| merged | RAN4#105 | Huawei, HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4961 | - | F | 17.7.0 | Rel-17 | CR on NPUSCH format1 demodulation requirement for TS 36.104 |
R4-2219023
| agreed | RAN4#105 | Samsung |
RP-223308
| approved | RAN#98-e | RAN4 | 17.8.0 | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4960 | - | B | 17.6.0 | Rel-17 | Big CR for TS 36.104 for Rel-17 NB-IoT BS performance requirements |
R4-2214657
| agreed | RAN4#104-e | Huawei, HiSilicon |
RP-222029
| approved | RAN#97-e | RAN4 | 17.7.0 | NB_IOTenh4_LTE_... |
|
|
| 36.104 | 4949 | - | B | 17.4.0 | Rel-17 | CR to TS16104 Addition of NB-IoT 16QAM |
R4-2204077
| agreed | RAN4#102-e | Huawei, HiSilic... |
RP-220351
| approved | RAN#95-e | RAN4 | 17.5.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7295 | - | F | 18.4.0 | Rel-18 | (NB_IOTenh4_LTE_eMTC6-Core) CR on maintenance for Rel-18 NB-IoT (Cat F) |
R4-2401313
| agreed | RAN4#110 | Huawei, HiSilicon |
RP-240557
| approved | RAN#103 | RAN4 | 18.5.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7294 | - | F | 17.12.0 | Rel-17 | (NB_IOTenh4_LTE_eMTC6-Core) CR on maintenance for Rel-17 NB-IoT (Cat F) |
R4-2401312
| agreed | RAN4#110 | Huawei, HiSilicon |
RP-240557
| approved | RAN#103 | RAN4 | 17.13.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7274 | - | A | 18.3.1 | Rel-18 | [NB_IOTenh4_LTE_eMTC6-Core] CR on 36.133 Fixing capability description for NB-IoT neighbor cell measurements in connected mode |
R4-2320756
| agreed | RAN4#109 | Nokia, Nokia Sh... |
RP-233344
| approved | RAN#102 | RAN4 | 18.4.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7273 | 1 | F | 17.11.2 | Rel-17 | [NB_IOTenh4_LTE_eMTC6-Core] CR on 36.133 Fixing capability description for NB-IoT neighbor cell measurements in connected mode |
R4-2321542
| agreed | RAN4#109 | Nokia, Nokia Sh... |
RP-233344
| approved | RAN#102 | RAN4 | 17.12.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7273 | - | F | 17.11.2 | Rel-17 | [NB_IOTenh4_LTE_eMTC6-Core] CR on 36.133 Fixing capability description for NB-IoT neighbor cell measurements in connected mode |
R4-2320755
| revised | RAN4#109 | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7233 | - | A | 18.2.0 | Rel-18 | [NB_IOTenh4_LTE_eMTC6-Core] CR on maintenance of neighbour cell measurement for NB-IoT R18 |
R4-2312406
| agreed | RAN4#108 | Huawei, HiSilicon |
RP-232488
| approved | RAN#101 | RAN4 | 18.3.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7232 | 1 | F | 17.10.0 | Rel-17 | [NB_IOTenh4_LTE_eMTC6-Core] CR on maintenance of neighbour cell measurement for NB-IoT R17 |
R4-2314436
| agreed | RAN4#108 | Huawei, HiSilicon |
RP-232488
| approved | RAN#101 | RAN4 | 17.11.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7232 | - | F | 17.10.0 | Rel-17 | [NB_IOTenh4_LTE_eMTC6-Core] CR on maintenance of neighbour cell measurement for NB-IoT R17 |
R4-2312405
| revised | RAN4#108 | Huawei, HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7180 | - | F | 17.6.0 | Rel-17 | Big CR for 36.133 maintenance (Rel-17) |
R4-2215211
| agreed | RAN4#104-e | MCC, Ericsson |
RP-222026
| approved | RAN#97-e | RAN4 | 17.7.0 | TEI14, NR_newRA... |
|
|
| 36.133 | 7175 | - | B | 17.6.0 | Rel-17 | Big CR for NB_IOTenh4_LTE_eMTC6_RRM (Rel-17) |
R4-2213565
| agreed | RAN4#104-e | MCC, Huawei |
RP-222029
| approved | RAN#97-e | RAN4 | 17.7.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7173 | - | F | 17.6.0 | Rel-17 | CR on maintenance of neighbour cell measurement for NB-IoT |
R4-2212965
| agreed | RAN4#104-e | Huawei, HiSilicon |
RP-222029
| approved | RAN#97-e | RAN4 | 17.7.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7156 | 1 | F | 17.5.0 | Rel-17 | CR on maintenance for NB-IoT R17 |
R4-2211124
| agreed | RAN4#103-e | Huawei, Hisilicon |
RP-221678
| approved | RAN#96 | RAN4 | 17.6.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7156 | - | F | 17.5.0 | Rel-17 | CR on maintenance for NB-IoT R17 |
R4-2208953
| revised | RAN4#103-e | Huawei, Hisilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7137 | 1 | B | 17.4.0 | Rel-17 | Big CR of RRM requirements for Rel-17 NB-IoT and eMTC |
R4-2207083
| agreed | RAN4#102-e | Huawei, Hisilicon |
RP-220351
| approved | RAN#95-e | RAN4 | 17.5.0 | NB_IOTenh4_LTE_... |
|
|
| 36.133 | 7137 | - | B | 17.4.0 | Rel-17 | Big CR of RRM requirements for Rel-17 NB-IoT and eMTC |
R4-2204884
| revised | RAN4#102-e | Huawei, Hisilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.141 | 1344 | - | F | 17.7.0 | Rel-17 | CR 36.141 on Finalization of NPUSCH format 1 16QAM test requirement |
R4-2219991
| agreed | RAN4#105 | Nokia, Nokia Sh... |
RP-223308
| approved | RAN#98-e | RAN4 | 17.8.0 | NB_IOTenh4_LTE_... |
|
|
| 36.141 | 1339 | - | F | 17.7.0 | Rel-17 | CR on cleanup for Rel-17 NPUSCH format 1 requirements with 16QAM in TS 36.141 |
R4-2219520
| merged | RAN4#105 | Huawei, HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.141 | 1338 | - | B | 17.6.0 | Rel-17 | Big CR for TS 36.141 for Rel-17 NB-IoT BS conformance testing |
R4-2214658
| agreed | RAN4#104-e | Huawei, HiSilicon |
RP-222029
| approved | RAN#97-e | RAN4 | 17.7.0 | NB_IOTenh4_LTE_... |
|
|
| 36.141 | 1324 | - | B | 17.4.0 | Rel-17 | CR to TS16141 Addition of NB-IoT 16QAM |
R4-2204078
| agreed | RAN4#102-e | Huawei, HiSilic... |
RP-220351
| approved | RAN#95-e | RAN4 | 17.5.0 | NB_IOTenh4_LTE_... |
|
|
| 36.211 | 0570 | - | F | 17.2.0 | Rel-17 | DRAFT CR Clarification on the mapping to physical resources for 16-QAM in NB-IoT |
R1-2207573
| not pursued | RAN1#110 | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.211 | 0569 | - | F | 17.1.0 | Rel-17 | Correction to additional enhancements for NB-IoT and eMTC |
R1-2205664
| agreed | RAN1#109-e | Ericsson |
RP-221608
| approved | RAN#96 | RAN1 | 17.2.0 | NB_IOTenh4_LTE_... |
|
|
| 36.211 | 0567 | - | F | 17.0.0 | Rel-17 | Correction to additional enhancements for NB-IoT and eMTC |
R1-2202971
| agreed | RAN1#108-e | Ericsson |
RP-220258
| approved | RAN#95-e | RAN1 | 17.1.0 | NB_IOTenh4_LTE_... |
|
|
| 36.211 | 0565 | - | D | 17.0.0 | Rel-17 | Correction of parameter name for 14-HARQ processes |
R1-2202889
| not pursued | RAN1#108-e | Moderator (ZTE)... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.211 | 0562 | - | B | 16.7.0 | Rel-17 | Introduction of additional enhancements for NB-IoT and LTE-MTC |
R1-2112923
| agreed | RAN1#107-e | Ericsson |
RP-212974
| approved | RAN#94-e | RAN1 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.212 | 0373 | - | F | 17.0.0 | Rel-17 | Correction to additional enhancements for NB-IoT and LTE-MTC |
R1-2202972
| agreed | RAN1#108-e | FUTUREWEI |
RP-220258
| approved | RAN#95-e | RAN1 | 17.1.0 | NB_IOTenh4_LTE_... |
|
|
| 36.212 | 0372 | - | F | 17.0.0 | Rel-17 | Clarification on the support of 16-QAM for NB-IoT in TS 36.212 |
R1-2202280
| not pursued | RAN1#108-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.212 | 0371 | - | B | 16.6.0 | Rel-17 | Introduction of Rel-17 NB-IoT and eMTC features |
R1-2112958
| agreed | RAN1#107-e | FUTUREWEI |
RP-212974
| approved | RAN#94-e | RAN1 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 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 | 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 | 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 | 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 | 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 | 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 | 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.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.302 | 1211 | 1 | B | 16.1.0 | Rel-17 | Introduction of Rel-17 enhancements for NB-IoT and eMTC |
R2-2203580
| agreed | RAN2#117-e | Huawei, HiSilicon |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.302 | 1211 | - | B | 16.1.0 | Rel-17 | Introduction of Rel-17 enhancements for NB-IoT and eMTC |
R2-2203217
| revised | RAN2#117-e | Huawei, HiSilicon |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0860 | 1 | F | 17.3.0 | Rel-17 | Small corrections on coverage-based paging |
R2-2302011
| agreed | RAN2#121 | ZTE Corporation... |
RP-230688
| approved | RAN#99 | RAN2 | 17.4.0 | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0860 | - | F | 17.3.0 | Rel-17 | Small corrections on coverage-based paging |
R2-2301310
| revised | RAN2#121 | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0852 | - | F | 17.1.0 | Rel-17 | Introduction of value infinity for coverage based paging carrier hysteresis timer |
R2-2208305
| not pursued | RAN2#119-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0850 | 1 | F | 17.0.0 | Rel-17 | Correction to coverage based paging |
R2-2206861
| agreed | RAN2#118-e | Nokia, Nokia Sh... |
RP-221757
| approved | RAN#96 | RAN2 | 17.1.0 | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0850 | - | F | 17.0.0 | Rel-17 | Correction to coverage based paging |
R2-2206272
| revised | RAN2#118-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0848 | - | F | 17.0.0 | Rel-17 | RILZ312, Z313, Z316 CEL-based paging |
R2-2205878
| merged | RAN2#118-e | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0844 | 2 | B | 16.6.0 | Rel-17 | Introduction of Enhancements for NB-IoT/eMTC |
R2-2204255
| agreed | RAN2#117-e | Nokia |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0844 | 1 | B | 16.6.0 | Rel-17 | Introduction of Enhancements for NB-IoT/eMTC |
R2-2203581
| revised | RAN2#117-e | Nokia |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.304 | 0844 | - | B | 16.6.0 | Rel-17 | Introduction of Enhancements for NB-IoT/eMTC |
R2-2203756
| revised | RAN2#117-e | Nokia |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.306 | 1865 | - | F | 17.2.0 | Rel-17 | Correction to npusch-16QAM-r17 |
R2-2212961
| agreed | RAN2#120 | Qualcomm Incorp... |
RP-223409
| approved | RAN#98-e | RAN2 | 17.3.0 | NB_IOTenh4_LTE_... |
|
|
| 36.306 | 1841 | 1 | B | 16.7.0 | Rel-17 | Introduction of additional enhancements for NB-IoT and eMTC |
R2-2203578
| agreed | RAN2#117-e | ZTE Corporation... |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.306 | 1841 | - | B | 16.7.0 | Rel-17 | 36306 running CR for NB-IoT eMTC |
R2-2202743
| revised | RAN2#117-e | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.321 | 1569 | 2 | F | 17.6.0 | Rel-17 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2311541
| revised | RAN2#123-bis | Xiaomi |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.321 | 1569 | 1 | F | 17.6.0 | Rel-17 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2311407
| revised | RAN2#123-bis | Xiaomi |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.321 | 1569 | - | F | 17.6.0 | Rel-17 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2309763
| revised | RAN2#123-bis | Xiaomi |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.321 | 1568 | - | F | 17.5.0 | Rel-17 | MAC correction on drx-InactivityTimer for eMTC and NB-IOT UE |
R2-2307514
| postponed | RAN2#123 | Xiaomi |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.321 | 1536 | - | B | 16.6.0 | Rel-17 | Introduction of Rel-17 enhancements for NB-IoT and eMTC |
R2-2203583
| agreed | RAN2#117-e | Ericsson |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 5003 | - | F | 17.8.0 | Rel-17 | Clarification of CQI report enabling in RRCEarlyDataRequest-NB message |
R2-2402815
| | RAN2#125-bis | Qualcomm Incorp... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4903 | - | F | 17.3.0 | Rel-17 | CR to 36.331 on NPUSCH-ConfigDedicated-NB-v1700 |
R2-2300845
| agreed | RAN2#121 | Huawei, HiSilic... |
RP-230688
| approved | RAN#99 | RAN2 | 17.4.0 | NB_IOTenh4_LTE_eMTC6 |
|
|
| 36.331 | 4880 | 1 | F | 17.2.0 | Rel-17 | Add a new field for indicating access stratum release |
R2-2212790
| | RAN2#120 | Google Inc. |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4880 | - | F | 17.2.0 | Rel-17 | Add a new field for access stratum release |
R2-2210704
| revised | RAN2#119-bis-e | Google Inc. |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4866 | 1 | F | 17.1.0 | Rel-17 | Correction on npusch-MCS field description |
R2-2209098
| agreed | RAN2#119-e | ZTE Corporation... |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4866 | - | F | 17.1.0 | Rel-17 | 36331_(R17)_Correction on npusch-MCS field description |
R2-2208597
| revised | RAN2#119-e | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4857 | - | F | 17.1.0 | Rel-17 | Introduction of value infinity for coverage based paging carrier hysteresis timer |
R2-2208304
| not pursued | RAN2#119-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4803 | 1 | F | 17.0.0 | Rel-17 | Corrections to R17 NB-IoT/eMTC Enhancements |
R2-2206271
| agreed | RAN2#118-e | Qualcomm Incorp... |
RP-221757
| approved | RAN#96 | RAN2 | 17.1.0 | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4803 | - | F | 17.0.0 | Rel-17 | Corrections based on ASN.1 review of R17 NB-IoT/eMTC Enhancements |
R2-2205564
| revised | RAN2#118-e | Qualcomm Incorp... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4789 | - | F | 17.0.0 | Rel-17 | RILZ312, Z313, Z316, Z317, Z318 CEL-based paging |
R2-2205162
| noted | RAN2#118-e | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4788 | - | F | 17.0.0 | Rel-17 | Clarification on NPUSCH repetition number for PUR with 16QAM |
R2-2205149
| not pursued | RAN2#118-e | ZTE Corporation... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4760 | 1 | B | 16.7.0 | Rel-17 | Introduction of NB-IoT/eMTC Enhancements |
R2-2203577
| agreed | RAN2#117-e | Qualcomm Incorp... |
RP-220507
| approved | RAN#95-e | RAN2 | 17.0.0 | NB_IOTenh4_LTE_... |
|
|
| 36.331 | 4760 | - | B | 16.7.0 | Rel-17 | Introduction of NB-IoT/eMTC Enhancements |
R2-2202427
| revised | RAN2#117-e | Qualcomm Incorp... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1898 | - | A | 17.1.0 | Rel-17 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation |
R3-224806
| revised | RAN3#117-e | Ericsson, Vodaf... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1883 | - | F | 17.0.0 | Rel-17 | Correction of Cell Identifier and Coverage Enhancement Level |
R3-223356
| noted | RAN3#116-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1834 | - | B | 16.7.0 | Rel-17 | Support of Carrier Selection based on coverage level |
R3-214784
| | RAN3#114-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1829 | - | B | 16.6.0 | Rel-17 | Support of CE based carrier selection |
R3-213978
| noted | RAN3#113-e | Huawei |
| | | | | NB_IOTenh4_LTE_eMTC6 |
|
|
| 36.413 | 1823 | - | B | 16.6.0 | Rel-17 | Support of Carrier Selection based on coverage level |
R3-213454
| noted | RAN3#113-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1813 | - | B | 16.5.0 | Rel-17 | Support of Additional enhancements for NB-IoT and LTE-MTC |
R3-211918
| | RAN3#112-e | Huawei |
| | | | | NB_IOTenh4_LTE_eMTC6 |
|
|
| 36.413 | 1812 | - | B | 16.5.0 | Rel-17 | Support of Carrier Selection based on coverage level |
R3-211650
| | RAN3#112-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1810 | - | B | 16.5.0 | Rel-17 | 36.413 (Rel-17) Introduction of paging carrier information for Option 2 |
R3-211590
| | RAN3#112-e | ZTE |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1809 | 1 | B | 16.6.0 | Rel-17 | 36.413 (Rel-17) Introduction of CEL based paging carrier selection |
R3-213245
| noted | RAN3#113-e | ZTE |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 36.413 | 1809 | - | B | 16.5.0 | Rel-17 | 36.413 (Rel-17) Introduction of CEL based paging carrier selection for Option 1 |
R3-211589
| revised | RAN3#112-e | ZTE |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.306 | 0826 | - | F | 17.2.0 | Rel-17 | Correction to npusch-16QAM-r17 |
R2-2211292
| withdrawn | RAN2#120 | Qualcomm Incorp... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0875 | - | A | 17.1.0 | Rel-17 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation |
R3-224808
| revised | RAN3#117-e | Ericsson, Vodaf... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0799 | - | F | 17.0.0 | Rel-17 | Correction of Paging Assistance Data for CE Capable UE |
R3-223355
| noted | RAN3#116-e | Ericsson |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0753 | - | B | 16.8.0 | Rel-17 | Support of Carrier Selection based on coverage level |
R3-221811
| | RAN3#115-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0720 | - | B | 16.8.0 | Rel-17 | Support of Carrier Selection based on coverage level |
R3-220196
| | RAN3#114-bis-e | Nokia, Nokia Sh... |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0673 | - | B | 16.7.0 | Rel-17 | Support of CE based carrier selection |
R3-215005
| | RAN3#114-e | Huawei |
| | | | | NB_IOTenh4_LTE_eMTC6 |
|
|
| 38.413 | 0630 | - | B | 16.6.0 | Rel-17 | Support of CE based carrier selection |
R3-213576
| noted | RAN3#113-e | Huawei |
| | | | | NB_IOTenh4_LTE_eMTC6 |
|
|
| 38.413 | 0621 | 2 | B | 16.8.0 | Rel-17 | BLCR to TS38.413 for introduction of CEL based paging carrier selection |
R3-220226
| | RAN3#114-bis-e | ZTE |
| | | | | NB_IOTenh4_LTE_eMTC6 |
|
|
| 38.413 | 0621 | 1 | B | 16.7.0 | Rel-17 | Introduction of CEL based paging carrier selection |
R3-214739
| revised | RAN3#114-e | ZTE |
| | | | | NB_IOTenh4_LTE_... |
|
|
| 38.413 | 0621 | - | B | 16.6.0 | Rel-17 | 38.413 (Rel-17) Introduction of CEL based paging carrier selection |
R3-213246
| revised | RAN3#113-e | ZTE |
| | | | | NB_IOTenh4_LTE_... |
|