|
|
| 36.321 | 1588 | 1 | F | 18.2.0 | Rel-18 | Miscellaneous MAC correction for IoT NTN |
R2-2407620
| agreed | RAN2#127 | MediaTek |
RP-242237
| approved | RAN#105 | RAN2 | 18.3.0 | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1588 | - | F | 18.2.0 | Rel-18 | Miscellaneous MAC correction for IoT NTN |
R2-2406938
| revised | RAN2#127 | MediaTek |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1587 | - | F | 18.2.0 | Rel-18 | Clarification of note on UL and DL parallel scheduling for NB-IoT |
R2-2406642
| | RAN2#127 | Qualcomm Incorp... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1586 | - | F | 18.1.0 | Rel-18 | IoT NTN MAC corrections |
R2-2405454
| | RAN2#126 | Ericsson |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1585 | 3 | F | 18.1.0 | Rel-18 | Corrections on UE behaviour on DRX for IoT NTN |
R2-2405759
| agreed | RAN2#126 | MediaTek |
RP-241556
| approved | RAN#104 | RAN2 | 18.2.0 | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1585 | 2 | F | 18.1.0 | Rel-18 | Corrections on UE behaviour on DRX for IoT NTN |
R2-2404954
| revised | RAN2#126 | MediaTek |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1585 | 1 | F | 18.1.0 | Rel-18 | Corrections on UE behaviour on DRX for IoT NTN |
R2-2404007
| revised | RAN2#125-bis | MediaTek |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1585 | - | F | 18.1.0 | Rel-18 | Corrections on UE behaviour on DRX for IoT NTN |
R2-2403221
| revised | RAN2#125-bis | MediaTek |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1584 | - | F | 18.1.0 | Rel-18 | MAC corrections to IoT NTN |
R2-2402384
| withdrawn | RAN2#125-bis | ZTE Corporation... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1583 | - | F | 18.0.0 | Rel-18 | Corrections to IoT NTN |
R2-2401596
| agreed | RAN2#125 | MediaTek |
RP-240660
| approved | RAN#103 | RAN2 | 18.1.0 | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1582 | 1 | F | 18.0.0 | Rel-18 | Correction on GNSS validity duration reporting |
R2-2401515
| | RAN2#125 | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1582 | - | F | 18.0.0 | Rel-18 | Correction on GNSS validity duration reporting |
R2-2401459
| revised | RAN2#125 | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1581 | - | F | 18.0.0 | Rel-18 | Correction to 36.321 on GNSS validity duration reporting |
R2-2401129
| noted | RAN2#125 | Nokia, Nokia Sh... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1580 | 1 | B | 17.6.0 | Rel-18 | Introduction of further enhancements for IoT-NTN |
R2-2314015
| agreed | RAN2#124 | MediaTek |
RP-233891
| approved | RAN#102 | RAN2 | 18.0.0 | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1580 | - | F | 17.6.0 | Rel-18 | Introduction of further enhancements for IoT-NTN |
R2-2313781
| revised | RAN2#124 | MediaTek |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.321 | 1579 | - | F | 17.6.0 | Rel-17 | Correction on the Koffset handling during RRC connection re-establishment |
R2-2313485
| not pursued | RAN2#124 | Google Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1578 | - | F | 17.6.0 | Rel-17 | Correction on Koffset when receiving dedicated SIB31 |
R2-2313357
| not pursued | RAN2#124 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1577 | - | A | 17.6.0 | Rel-17 | Correction on drx-InactivityTimer definition for NB-IoT UE |
R2-2312710
| agreed | RAN2#124 | Nokia, Nokia Sh... |
RP-233886
| approved | RAN#102 | RAN2 | 17.7.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1576 | - | F | 16.8.0 | Rel-16 | Correction on drx-InactivityTimer definition for NB-IoT UE |
R2-2312709
| agreed | RAN2#124 | Nokia, Nokia Sh... |
RP-233886
| approved | RAN#102 | RAN2 | 16.9.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1575 | 1 | A | 17.6.0 | Rel-17 | Correction on the UL HARQ RTT timer length |
R2-2313713
| agreed | RAN2#124 | MediaTek |
RP-233886
| approved | RAN#102 | RAN2 | 17.7.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1575 | - | A | 17.6.0 | Rel-17 | Correction on the UL HARQ RTT timer length |
R2-2312118
| revised | RAN2#124 | MediaTek Inc. |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1574 | 1 | F | 16.8.0 | Rel-16 | Correction on the UL HARQ RTT timer length |
R2-2313712
| agreed | RAN2#124 | MediaTek |
RP-233886
| approved | RAN#102 | RAN2 | 16.9.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1574 | - | F | 16.8.0 | Rel-16 | Correction on the UL HARQ RTT timer length |
R2-2312117
| revised | RAN2#124 | MediaTek Inc. |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1573 | 2 | F | 17.6.0 | Rel-17 | Correction to 36.321 on Koffset handling during MAC reset |
R2-2313787
| agreed | RAN2#124 | Huawei, Ericsso... |
RP-233887
| approved | RAN#102 | RAN2 | 17.7.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1573 | 1 | F | 17.6.0 | Rel-17 | Correction to 36.321 on Koffset handling during MAC reset |
R2-2313550
| revised | RAN2#124 | Huawei, Ericsso... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1573 | - | F | 17.6.0 | Rel-17 | Correction to 36.321 on Koffset handling during handover |
R2-2311597
| endorsed | RAN2#123-bis | Huawei, Ericsso... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1572 | - | A | 17.6.0 | Rel-17 | Correction on the UL HARQ RTT timer length |
R2-2309779
| not pursued | RAN2#123-bis | MediaTek Inc., Apple |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1571 | - | F | 16.8.0 | Rel-16 | Correction on the UL HARQ RTT timer length |
R2-2309778
| not pursued | RAN2#123-bis | MediaTek Inc., Apple |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1570 | 3 | F | 16.8.0 | Rel-16 | Correction on drx-InactivityTimer for NB-IOT UE |
R2-2313863
| agreed | RAN2#124 | Xiaomi, Ericsson |
RP-233886
| approved | RAN#102 | RAN2 | 16.9.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1570 | 2 | F | 16.8.0 | Rel-16 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2311540
| revised | RAN2#123-bis | Xiaomi |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1570 | 1 | F | 16.8.0 | Rel-16 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2311408
| revised | RAN2#123-bis | Xiaomi |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1570 | - | F | 16.8.0 | Rel-16 | MAC correction on drx-InactivityTimer for eMTC UE |
R2-2309764
| revised | RAN2#123-bis | Xiaomi |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1569 | 3 | A | 17.6.0 | Rel-17 | Correction on drx-InactivityTimer for NB-IOT UE |
R2-2313864
| agreed | RAN2#124 | Xiaomi, Ericsson |
RP-233886
| approved | RAN#102 | RAN2 | 17.7.0 | NB_IOTenh3-Core |
|
|
|
| 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 | 1567 | 2 | F | 17.5.0 | Rel-17 | Miscellaneous MAC corrections for IoT NTN |
R2-2308995
| agreed | RAN2#123 | MediaTek Inc., ... |
RP-232568
| approved | RAN#101 | RAN2 | 17.6.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1567 | 1 | F | 17.5.0 | Rel-17 | Corrections on the HARQ RTT timer for IoT NTN |
R2-2308986
| revised | RAN2#123 | MediaTek |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1567 | - | F | 17.5.0 | Rel-17 | Corrections on the HARQ RTT timer for IoT NTN |
R2-2307324
| revised | RAN2#123 | MediaTek |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1566 | - | F | 17.4.0 | Rel-17 | Correction on UL operation upon validity timer expiry in IoT NTN |
R2-2304763
| not pursued | RAN2#122 | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1565 | 2 | F | 17.4.0 | Rel-17 | Clarification on UL operation upon validity timer expiry for IoT NTN |
R2-2305409
| agreed | RAN2#122 | Nokia, Nokia Sh... |
RP-231417
| approved | RAN#100 | RAN2 | 17.5.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1565 | 1 | F | 17.4.0 | Rel-17 | Clarification on UL operation upon validity timer expiry for IoT NTN |
R2-2304267
| revised | RAN2#121-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1565 | - | F | 17.4.0 | Rel-17 | Corrections on MAC procedure upon validity timer expiry for IoT NTN |
R2-2303980
| revised | RAN2#121-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1564 | - | C | 17.4.0 | Rel-18 | Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN |
R2-2302675
| withdrawn | RAN2#121-bis-e | MediaTek Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1563 | - | F | 17.3.0 | Rel-17 | Correction for IoT NTN |
R2-2301878
| agreed | RAN2#121 | Ericsson |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1562 | 1 | F | 17.3.0 | Rel-17 | Clarification on the generation of TA reporting for IoT NTN |
R2-2301987
| agreed | RAN2#121 | ZTE Corporation... |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1562 | - | F | 17.3.0 | Rel-17 | Clarification on the generation of TA reporting for IoT NTN |
R2-2301051
| revised | RAN2#121 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1561 | 1 | F | 17.3.0 | Rel-17 | Correction on figure clarifying HARQ RTT timer |
R2-2301986
| agreed | RAN2#121 | Qualcomm Inc. |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1561 | - | F | 17.3.0 | Rel-17 | Correction on figure clarifying HARQ RTT timer |
R2-2300888
| revised | RAN2#121 | Qualcomm Incorp... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1560 | 3 | F | 17.4.0 | Rel-17 | MAC correction on TDD support for IoT NTN |
R2-2304762
| agreed | RAN2#122 | OPPO |
RP-231417
| approved | RAN#100 | RAN2 | 17.5.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1560 | 2 | F | 17.4.0 | Rel-17 | MAC correction on TDD support for IoT NTN |
R2-2302530
| revised | RAN2#121-bis-e | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1560 | 1 | F | 17.4.0 | Rel-17 | MAC correction on TDD support for IoT NTN |
R2-232467
| | RAN2#121-bis-e | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1560 | - | F | 17.3.0 | Rel-17 | MAC correction on TDD support for IoT NTN |
R2-2300358
| revised | RAN2#121 | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1559 | - | F | 17.3.0 | Rel-17 | Misc corrections on MAC for IoT NTN |
R2-2300258
| agreed | RAN2#121 | MediaTek Inc |
RP-230696
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1558 | 1 | F | 17.2.0 | Rel-17 | Correction for IoT NTN |
R2-2213030
| merged | RAN2#120 | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1558 | - | F | 17.2.0 | Rel-17 | Correction for IoT NTN |
R2-2212942
| revised | RAN2#120 | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1557 | - | F | 17.2.0 | Rel-17 | Start of DL HARQ RTT timer for eMTC in NTN |
R2-2211577
| | RAN2#120 | Qualcomm Incorp... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1556 | 2 | F | 17.2.0 | Rel-17 | Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
R2-2213364
| agreed | RAN2#120 | MediaTek |
RP-223409
| approved | RAN#98-e | RAN2 | 17.3.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1556 | 1 | F | 17.2.0 | Rel-17 | Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
R2-2213016
| revised | RAN2#120 | MediaTek |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1556 | - | F | 17.2.0 | Rel-17 | Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
R2-2211287
| revised | RAN2#120 | Mediatek Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1555 | - | F | 17.2.0 | Rel-17 | Correction on UE-eNB RTT |
R2-2211286
| | RAN2#120 | Mediatek Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1554 | - | F | 17.2.0 | Rel-17 | MAC corrections for Rel-17 IoT NTN |
R2-2211019
| endorsed | RAN2#119-bis-e | MediaTek Inc. |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1553 | - | F | 17.2.0 | Rel-17 | Correction to (UL) HARQ RTT Timer for eMTC in NTNs |
R2-2210755
| | RAN2#119-bis-e | Ericsson |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1552 | - | F | 17.2.0 | Rel-17 | Correction on HARQ RTT timer with Koffset |
R2-2210699
| | RAN2#119-bis-e | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1551 | - | F | 17.2.0 | Rel-17 | Clarifications for IoT NTN MAC CEs |
R2-2210697
| merged | RAN2#119-bis-e | Samsung R&D Ins... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1550 | - | F | 17.2.0 | Rel-17 | Correction on UE-eNB RTT calculation |
R2-2210571
| | RAN2#119-bis-e | MediaTek Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1549 | - | F | 17.2.0 | Rel-17 | DRX correction for IoT NTN |
R2-2210094
| merged | RAN2#119-bis-e | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1548 | - | F | 17.2.0 | Rel-17 | Correction on UE-eNB RTT calculation |
R2-2209441
| withdrawn | RAN2#119-bis-e | MediaTek Inc. |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1547 | - | F | 17.1.0 | Rel-17 | Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
R2-2209041
| agreed | RAN2#119-e | MediaTek |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1546 | - | F | 17.1.0 | Rel-17 | Correction on TA Reporting Triggering Condition for IoT NTN in TS 36.321 |
R2-2208387
| | RAN2#119-e | CATT |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1545 | - | F | 17.1.0 | Rel-17 | 36321CR_Corrections for RTToffset in HARQ RTT timers |
R2-2207817
| merged | RAN2#119-e | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1544 | - | F | 17.1.0 | Rel-17 | Clarification on the expiry of the contention resolution timer. |
R2-2207351
| | RAN2#119-e | Qualcomm Incorp... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1543 | - | F | 17.1.0 | Rel-17 | Clarification on PDCCH-based HARQ feedback |
R2-2207349
| | RAN2#119-e | Qualcomm Incorp... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1542 | - | F | 17.1.0 | Rel-17 | Correction on the definition of deltaPDCCH in (UL) HARQ RTT Timer for NB-IoT NTN |
R2-2207064
| merged | RAN2#119-e | OPPO |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1541 | - | F | 17.0.0 | Rel-17 | Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
R2-2206794
| agreed | RAN2#118-e | MediaTek |
RP-221737
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1540 | 1 | A | 17.0.0 | Rel-17 | Correction on calculating number of TBs for multi-TB scheduling |
R2-2206323
| agreed | RAN2#118-e | Oy LM Ericsson AB |
RP-221712
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1540 | - | A | 17.0.0 | Rel-17 | Correction on calculating number of TBs for multi-TB scheduling |
R2-2205879
| revised | RAN2#118-e | Oy LM Ericsson AB |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1539 | 1 | F | 16.7.0 | Rel-16 | Correction on calculating number of TBs for multi-TB scheduling |
R2-2206322
| agreed | RAN2#118-e | Oy LM Ericsson AB |
RP-221712
| approved | RAN#96 | RAN2 | 16.8.0 | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1539 | - | F | 16.7.0 | Rel-16 | Correction on calculating number of TBs for multi-TB scheduling |
R2-2205877
| revised | RAN2#118-e | Oy LM Ericsson AB |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1538 | - | F | 17.0.0 | Rel-17 | 36.321 corrections for IoT NTN |
R2-2205724
| noted | RAN2#118-e | Nokia, Nokia Sh... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1537 | 3 | B | 16.6.0 | Rel-17 | Introducing Non-Terrestrial Network in NB-IoT and eMTC |
| | | |
RP-220983
| approved | RAN#95-e | MediaTek | 17.0.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1537 | 2 | B | 16.6.0 | Rel-17 | Introducing Non-Terrestrial Network in NB-IoT and eMTC |
| | | |
RP-220852
| revised | RAN#95-e | MediaTek | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.321 | 1537 | 1 | B | 16.6.0 | Rel-17 | Introducing Non-Terrestrial Network in NB-IoT and eMTC |
R2-2204260
| agreed | RAN2#117-e | MediaTek |
RP-220509
| revised | RAN#95-e | RAN2 | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.321 | 1537 | - | B | 16.6.0 | Rel-17 | Introducing Non-Terrestrial Network in NB-IoT and eMTC |
R2-2203685
| revised | RAN2#117-e | MediaTek |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 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.321 | 1535 | 1 | F | 16.6.0 | Rel-16 | Introduction of carrier specific NRSRP thresholds for NPRACH resource selection |
R2-2203585
| agreed | RAN2#117-e | CMCC, ZTE Corpo... |
RP-220472
| approved | RAN#95-e | RAN2 | 16.7.0 | NB_IOTenh-Core,... |
|
|
|
| 36.321 | 1535 | - | F | 16.6.0 | Rel-16 | Solution for random access issue on multiCarrier in NB-IoT |
R2-2203856
| revised | RAN2#117-e | CMCC |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1534 | - | F | 16.6.0 | Rel-16 | Correction to pur-ResponseWindowTimer and removal of pur-ResponseWindowSize |
R2-2203724
| agreed | RAN2#117-e | Qualcomm Incorp... |
RP-220473
| approved | RAN#95-e | RAN2 | 16.7.0 | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1533 | - | F | 16.6.0 | Rel-17 | Correction to pur-ResponseWindowTimer and removal of pur-ResponseWindowSize |
R2-2203723
| withdrawn | RAN2#117-e | Qualcomm Incorp... |
| | | | | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1532 | - | A | 16.6.0 | Rel-16 | Clarification on CDRX and two HARQ interaction for NB-IoT |
R2-2203496
| | RAN2#117-e | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1531 | - | A | 15.11.0 | Rel-15 | Clarification on CDRX and two HARQ interaction for NB-IoT |
R2-2203495
| | RAN2#117-e | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1530 | - | F | 14.13.0 | Rel-14 | Clarification on CDRX and two HARQ interaction for NB-IoT |
R2-2203486
| | RAN2#117-e | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1529 | - | A | 16.6.0 | Rel-16 | Correction to DRX active time after a Scheduling Request or a SPS BSR has been sent in NB-IoT |
R2-2203215
| | RAN2#117-e | Huawei, HiSilicon |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1528 | - | F | 15.11.0 | Rel-15 | Correction to DRX active time after a Scheduling Request or a SPS BSR has been sent in NB-IoT |
R2-2203214
| | RAN2#117-e | Huawei, HiSilicon |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1527 | - | F | 16.6.0 | Rel-16 | Miscelleneous CR on 36.321 |
R2-2110160
| withdrawn | RAN2#116-e | LG Electronics ... |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1526 | - | F | 16.5.0 | Rel-16 | Correction on UL/SL prioritization |
R2-2107186
| agreed | RAN2#115-e | OPPO, Apple |
RP-212441
| approved | RAN#93-e | RAN2 | 16.6.0 | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1525 | - | F | 16.4.0 | Rel-16 | CR on LCP of the source MAC entity |
R2-2106301
| agreed | RAN2#114-e | Samsung |
RP-211473
| approved | RAN#92-e | RAN2 | 16.5.0 | NR_Mob_enh-Core |
|
|
|
| 36.321 | 1524 | 1 | F | 16.4.0 | Rel-16 | MAC clarifications for PUR |
R2-2106606
| agreed | RAN2#114-e | ZTE Corporation... |
RP-211479
| approved | RAN#92-e | RAN2 | 16.5.0 | LTE_eMTC5-Core,... |
|
|
|
| 36.321 | 1524 | - | F | 16.4.0 | Rel-16 | MAC clarifications for PUR |
R2-2106277
| revised | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.321 | 1523 | - | F | 16.4.0 | Rel-16 | Correction on UL-SL prioritization |
R2-2104834
| not pursued | RAN2#114-e | OPPO, Apple |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1522 | - | F | 16.4.0 | Rel-16 | CR on LCP of the source MAC entity |
R2-2103292
| endorsed | RAN2#113-bis-e | Samsung |
| | | | | NR_Mob_enh-Core |
|
|
|
| 36.321 | 1521 | 1 | F | 16.3.0 | Rel-16 | Recommended bit rate query handling at MAC Reset |
R2-2101984
| agreed | RAN2#113-e | Ericsson |
RP-210700
| approved | RAN#91-e | RAN2 | 16.4.0 | LTE_VoLTE_ViLTE... |
|
|
|
| 36.321 | 1521 | - | F | 16.3.0 | Rel-16 | Recommended bit rate query handling at MAC Reset |
R2-2101445
| revised | RAN2#113-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1520 | - | F | 15.11.0 | Rel-15 | Recommended bit rate query handling at MAC Reset |
R2-2101444
| not pursued | RAN2#113-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1519 | - | F | 14.13.0 | Rel-14 | Recommended bit rate query handling at MAC Reset |
R2-2101443
| not pursued | RAN2#113-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1518 | 1 | F | 16.3.0 | Rel-16 | Clarification on TA validation for PUR |
R2-2102160
| agreed | RAN2#113-e | Huawei, HiSilic... |
RP-210698
| approved | RAN#91-e | RAN2 | 16.4.0 | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1518 | - | F | 16.3.0 | Rel-16 | Clarification on the (N)RSRP reference for TA validation for PUR |
R2-2101035
| revised | RAN2#113-e | Huawei, HiSilicon |
| | | | | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1517 | 1 | F | 16.3.0 | Rel-16 | PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling |
R2-2102069
| agreed | RAN2#113-e | Qualcomm Inc. |
RP-210698
| approved | RAN#91-e | RAN2 | 16.4.0 | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1517 | - | F | 16.3.0 | Rel-16 | PDCCH-based HARQ-ACK for a specific HARQ process with multi-TB scheduling |
R2-2100735
| revised | RAN2#113-e | Qualcomm Incorp... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1516 | 1 | F | 16.2.0 | Rel-16 | Corrections to UL/SL Prioritization for 5G V2X with NR Sidelink |
R2-2010965
| agreed | RAN2#112-e | LG Electronics Inc. |
RP-202769
| approved | RAN#90-e | RAN2 | 16.3.0 | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1516 | - | F | 16.2.0 | Rel-16 | Corrections to UL/SL Prioritization for 5G V2X with NR Sidelink |
R2-2010957
| revised | RAN2#112-e | LG Electronics Inc. |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1515 | - | F | 16.2.0 | Rel-16 | Recommended bit rate query handling at MAC Reset |
R2-2010155
| postponed | RAN2#112-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1514 | - | F | 15.10.0 | Rel-15 | Recommended bit rate query handling at MAC Reset |
R2-2010154
| postponed | RAN2#112-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1513 | - | F | 14.13.0 | Rel-14 | Recommended bit rate query handling at MAC Reset |
R2-2010153
| postponed | RAN2#112-e | Ericsson |
| | | | | LTE_VoLTE_ViLTE_enh |
|
|
|
| 36.321 | 1512 | 2 | A | 16.2.0 | Rel-16 | Correction on lch-CellRestriction |
R2-2011251
| agreed | RAN2#112-e | Samsung |
RP-202780
| approved | RAN#90-e | RAN2 | 16.3.0 | LTE_HRLLC-Core,... |
|
|
|
| 36.321 | 1512 | 1 | F | 16.2.0 | Rel-16 | Correction on lch-CellRestriction |
R2-2011081
| revised | RAN2#112-e | Samsung |
| | | | | TEI16, LTE_HRLL... |
|
|
|
| 36.321 | 1512 | - | F | 16.2.0 | Rel-16 | Correction on lch-CellRestriction |
R2-2009572
| revised | RAN2#112-e | Samsung |
| | | | | TEI16, LTE_HRLL... |
|
|
|
| 36.321 | 1511 | 1 | F | 15.10.0 | Rel-15 | Correction on lch-CellRestriction |
R2-2011080
| agreed | RAN2#112-e | Samsung |
RP-202780
| approved | RAN#90-e | RAN2 | 15.11.0 | TEI15, LTE_HRLL... |
|
|
|
| 36.321 | 1511 | - | F | 15.10.0 | Rel-15 | Correction on lch-CellRestriction |
R2-2009571
| revised | RAN2#112-e | Samsung |
| | | | | TEI15, LTE_HRLL... |
|
|
|
| 36.321 | 1510 | - | A | 16.2.0 | Rel-16 | Corrections on MAC reset regarding SL BSR cancellation |
R2-2009216
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_D2D_Prox-Core |
|
|
|
| 36.321 | 1509 | - | A | 15.10.0 | Rel-15 | Corrections on MAC reset regarding SL BSR cancellation |
R2-2009215
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_D2D_Prox-Core |
|
|
|
| 36.321 | 1508 | - | A | 14.13.0 | Rel-14 | Corrections on MAC reset regarding SL BSR cancellation |
R2-2009214
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_D2D_Prox-Core |
|
|
|
| 36.321 | 1507 | - | A | 13.9.0 | Rel-13 | Corrections on MAC reset regarding SL BSR cancellation |
R2-2009213
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_D2D_Prox-Core |
|
|
|
| 36.321 | 1506 | - | F | 12.10.0 | Rel-12 | Corrections on MAC reset regarding SL BSR cancellation |
R2-2009181
| not pursued | RAN2#112-e | Ericsson |
| | | | | LTE_D2D_Prox-Core |
|
|
|
| 36.321 | 1505 | - | F | 16.2.0 | Rel-16 | CR for TS 36.321 for NR V2X on miscellaneous issues |
R2-2009052
| | RAN2#112-e | ZTE Corporation... |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1504 | - | F | 16.2.0 | Rel-16 | 36321_Correction of prioritization between SL and UL |
R2-2008798
| | RAN2#112-e | OPPO |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1503 | 2 | F | 16.1.0 | Rel-16 | MAC corrections for PUR |
R2-2008314
| agreed | RAN2#111-e | ZTE Corporation... |
RP-201928
| approved | RAN#89-e | RAN2 | 16.2.0 | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1503 | 1 | F | 16.1.0 | Rel-16 | CR for HARQ feedback for PUR response |
R2-2008308
| revised | RAN2#111-e | ZTE Corporation... |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1503 | - | F | 16.1.0 | Rel-16 | CR for HARQ feedback for PUR response |
R2-2007987
| revised | RAN2#111-e | ZTE Corporation... |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1502 | - | A | 16.1.0 | Rel-16 | Correction on PDU generation for UL spatial multiplexing – Option 2 |
R2-2007724
| not pursued | RAN2#111-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1501 | - | A | 16.1.0 | Rel-16 | Correction on PDU generation for UL spatial multiplexing – Option 1 |
R2-2007723
| agreed | RAN2#111-e | ASUSTeK |
RP-201935
| approved | RAN#89-e | RAN2 | 16.2.0 | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1500 | - | A | 15.9.0 | Rel-15 | Correction on PDU generation for UL spatial multiplexing – Option 2 |
R2-2007722
| not pursued | RAN2#111-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1499 | - | A | 15.9.0 | Rel-15 | Correction on PDU generation for UL spatial multiplexing – Option 1 |
R2-2007721
| agreed | RAN2#111-e | ASUSTeK |
RP-201935
| approved | RAN#89-e | RAN2 | 15.10.0 | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1498 | - | F | 14.12.0 | Rel-14 | Correction on PDU generation for UL spatial multiplexing – Option 2 |
R2-2007720
| not pursued | RAN2#111-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1497 | - | F | 14.12.0 | Rel-14 | Correction on PDU generation for UL spatial multiplexing – Option 1 |
R2-2007719
| agreed | RAN2#111-e | ASUSTeK |
RP-201935
| approved | RAN#89-e | RAN2 | 14.13.0 | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1496 | - | F | 16.1.0 | Rel-16 | MAC CR for PHR reporting format for LTE DAPS handover |
R2-2007692
| not pursued | RAN2#111-e | Qualcomm Inc, H... |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1495 | 1 | F | 16.1.0 | Rel-16 | Editorial changes |
R2-2008165
| agreed | RAN2#111-e | Ericsson |
RP-201928
| approved | RAN#89-e | RAN2 | 16.2.0 | LTE_eMTC5-Core,... |
|
|
|
| 36.321 | 1495 | - | F | 16.1.0 | Rel-16 | Editorial changes |
R2-2007655
| revised | RAN2#111-e | Ericsson |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.321 | 1494 | - | F | 16.1.0 | Rel-16 | Correction to discard of PUR-RNTI |
R2-2007365
| | RAN2#111-e | Ericsson |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.321 | 1493 | - | F | 16.1.0 | Rel-16 | Prioritization between UL Uu and SL when priorities are not configured |
R2-2007288
| | RAN2#111-e | Ericsson |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1492 | - | A | 16.1.0 | Rel-16 | correction on the UE behaviour on dormant state |
R2-2007218
| not pursued | RAN2#111-e | vivo |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.321 | 1491 | - | F | 15.9.0 | Rel-15 | correction on the UE behaviour on dormant state |
R2-2007217
| not pursued | RAN2#111-e | vivo |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.321 | 1490 | - | F | 16.1.0 | Rel-16 | Other corrections on 36321 for PUR |
R2-2006849
| merged | RAN2#111-e | ZTE Corporation... |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1489 | - | F | 16.1.0 | Rel-16 | Correction on discarding PUR-RNTI |
R2-2006848
| | RAN2#111-e | ZTE Corporation... |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1488 | - | A | 16.1.0 | Rel-16 | Corrections to data inactivity monitoring considering SL logical channels |
R2-2006778
| | RAN2#111-e | Samsung Electro... |
| | | | | LTE_eV2X-Core |
|
|
|
| 36.321 | 1487 | - | F | 15.9.0 | Rel-15 | Corrections to data inactivity monitoring considering SL logical channels |
R2-2006777
| noted | RAN2#111-e | Samsung Electro... |
| | | | | LTE_eV2X-Core |
|
|
|
| 36.321 | 1486 | - | D | 16.1.0 | Rel-16 | CR on TS 36.321 for UL-SL prioritization issues for NR V2X |
R2-2006741
| | RAN2#111-e | ZTE Corporation... |
| | | | | 5G_V2X_NRSL-Core |
|
|
|
| 36.321 | 1485 | 3 | F | 16.1.0 | Rel-16 | Corrections to 5G V2X with NR Sidelink |
R2-2008631
| agreed | RAN2#111-e | LG Electronics |
RP-201927
| approved | RAN#89-e | RAN2 | 16.2.0 | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1485 | 2 | F | 16.1.0 | Rel-16 | Corrections to 5G V2X with NR Sidelink |
R2-2008334
| revised | RAN2#111-e | LG Electronics |
| | | | | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1485 | 1 | F | 16.1.0 | Rel-16 | Corrections to 5G V2X with NR Sidelink |
R2-2008110
| revised | RAN2#111-e | LG Electronics |
| | | | | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1485 | - | F | 16.1.0 | Rel-16 | Corrections to 5G V2X with NR Sidelink |
R2-2006706
| revised | RAN2#111-e | LG Electronics ... |
| | | | | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1484 | - | F | 16.0.0 | Rel-16 | Corrections to 5G V2X with NR Sidelink |
R2-2005971
| agreed | RAN2#110-e | LG Electronics Inc. |
RP-201176
| approved | RAN#88-e | RAN2 | 16.1.0 | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1483 | 1 | A | 16.0.0 | Rel-16 | Clarification for dedicated SR with HARQ-ACK |
R2-2005941
| agreed | RAN2#110-e | ZTE Corporation... |
RP-201168
| approved | RAN#88-e | RAN2 | 16.1.0 | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1483 | - | A | 16.0.0 | Rel-16 | Clarification for dedicated SR with HARQ-ACK |
R2-2005590
| revised | RAN2#110-e | ZTE Corporation... |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1482 | - | A | 16.0.0 | Rel-16 | Correction on PDU generation for UL spatial multiplexing |
R2-2005554
| postponed | RAN2#110-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1481 | - | A | 15.8.0 | Rel-15 | Correction on PDU generation for UL spatial multiplexing |
R2-2005553
| postponed | RAN2#110-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1480 | - | F | 14.12.0 | Rel-14 | Correction on PDU generation for UL spatial multiplexing |
R2-2005552
| postponed | RAN2#110-e | ASUSTeK |
| | | | | LTE_LATRED_L2-C... |
|
|
|
| 36.321 | 1479 | 1 | A | 16.0.0 | Rel-16 | Clarification on PHR report for power class 14dBm UE |
R2-2005944
| agreed | RAN2#110-e | Huawei, HiSilicon |
RP-201168
| approved | RAN#88-e | RAN2 | 16.1.0 | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1479 | - | A | 16.0.0 | Rel-16 | Clarification on PHR report for power class 14dBm UE |
R2-2005027
| revised | RAN2#110-e | Huawei, HiSilicon |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1478 | 1 | F | 15.8.0 | Rel-15 | Clarification on PHR report for power class 14dBm UE |
R2-2005943
| agreed | RAN2#110-e | Huawei, HiSilicon |
RP-201168
| approved | RAN#88-e | RAN2 | 15.9.0 | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1478 | - | F | 15.8.0 | Rel-15 | Clarification on PHR report for power class 14dBm UE |
R2-2005026
| revised | RAN2#110-e | Huawei, HiSilicon |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1477 | - | A | 15.8.0 | Rel-15 | Allow sending Rel-14 AS RAI when no UL grant |
R2-2004828
| | RAN2#110-e | MediaTek Inc. |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1476 | - | F | 14.12.0 | Rel-14 | Allow sending Rel-14 AS RAI when no UL grant |
R2-2004819
| withdrawn | RAN2#110-e | MediaTek Inc. |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1475 | - | F | 14.12.0 | Rel-14 | Allow sending Rel-14 AS RAI when no UL grant |
R2-2004816
| | RAN2#110-e | MediaTek Inc. |
| | | | | NB_IOTenh-Core |
|
|
|
| 36.321 | 1474 | 1 | B | 16.0.0 | Rel-16 | CR on 36.321 for even further mobility enhancement in E-UTRAN |
R2-2005761
| agreed | RAN2#110-e | vivo |
RP-201195
| approved | RAN#88-e | RAN2 | 16.1.0 | LTE_feMob-Core |
|
|
|
| 36.321 | 1474 | - | B | 16.0.0 | Rel-16 | CR on 36.321 for LTE feMob |
R2-2004644
| | RAN2#110-e | vivo |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1473 | 2 | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 eMTC |
R2-2005826
| agreed | RAN2#110-e | Ericsson |
RP-201193
| approved | RAN#88-e | RAN2 | 16.1.0 | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1473 | 1 | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 eMTC |
R2-2004628
| revised | RAN2#110-e | Ericsson |
| | | | | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1473 | - | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 eMTC |
R2-2003922
| revised | RAN2#109-bis-e | Ericsson |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1472 | 2 | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 NB-IoT |
R2-2005924
| agreed | RAN2#110-e | Ericsson |
RP-201193
| approved | RAN#88-e | RAN2 | 16.1.0 | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1472 | 1 | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 NB-IoT |
R2-2004631
| revised | RAN2#110-e | Ericsson |
| | | | | NB_IOTenh3-Core... |
|
|
|
| 36.321 | 1472 | - | F | 16.0.0 | Rel-16 | Corrections to MAC for Rel-16 NB-IoT |
R2-2004043
| not treated | RAN2#109-bis-e | Ericsson |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1471 | 1 | F | 14.12.0 | Rel-14 | Correction on Uu and PC5 prioritization |
R2-2005572
| | RAN2#110-e | ASUSTeK |
| | | | | LTE_V2X-Core |
|
|
|
| 36.321 | 1471 | - | F | 14.12.0 | Rel-14 | Correction on Uu and PC5 prioritization |
R2-2003642
| not treated | RAN2#109-bis-e | ASUSTeK |
| | | | | LTE_V2X-Core |
|
|
|
| 36.321 | 1470 | 1 | A | 15.8.0 | Rel-15 | Correction on Uu and PC5 prioritization |
R2-2005573
| merged | RAN2#110-e | ASUSTeK |
| | | | | LTE_eV2X-Core |
|
|
|
| 36.321 | 1470 | - | A | 15.8.0 | Rel-15 | Correction on Uu and PC5 prioritization |
R2-2003641
| not treated | RAN2#109-bis-e | ASUSTeK |
| | | | | LTE_eV2X-Core |
|
|
|
| 36.321 | 1469 | 2 | F | 15.8.0 | Rel-15 | Clarification for dedicated SR with HARQ-ACK |
R2-2005940
| agreed | RAN2#110-e | ZTE Corporation... |
RP-201168
| approved | RAN#88-e | RAN2 | 15.9.0 | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1469 | 1 | F | 15.8.0 | Rel-15 | Clarification for dedicated SR with HARQ-ACK |
R2-2005588
| revised | RAN2#110-e | ZTE Corporation... |
| | | | | NB_IOTenh2-Core |
|
|
|
| 36.321 | 1469 | - | F | 15.8.0 | Rel-15 | Optimisation on trigger for dedicated SR with HARQ-ACK |
R2-2003254
| not treated | RAN2#109-bis-e | ZTE Corporation... |
| | | | | LTE_eMTC4-Core |
|
|
|
| 36.321 | 1468 | 1 | F | 16.0.0 | Rel-16 | CR on 36.321 for LTE feMob |
R2-2003856
| revised | RAN2#109-bis-e | vivo |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1468 | - | F | 16.0.0 | Rel-16 | CR on 36.321 for LTE feMob |
R2-2002868
| revised | RAN2#109-bis-e | vivo |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1467 | 1 | B | 15.8.0 | Rel-16 | Introduction of 5G V2X with NR Sidelink |
R2-2002342
| agreed | RAN2#109-e | LG Electronics Inc. |
RP-200346
| approved | RAN#87-e | RAN2 | 16.0.0 | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1467 | - | B | 15.8.0 | Rel-16 | [Running CR] Introduction of 5G V2X with NR Sidelink |
R2-2001970
| revised | RAN2#109-e | LG Electronics Inc. |
| | | | | 5G_V2X_NRSL |
|
|
|
| 36.321 | 1466 | 1 | B | 15.8.0 | Rel-16 | Introduction of additional enhancements for NB-IoT |
R2-2001787
| agreed | RAN2#109-e | Ericsson |
RP-200361
| approved | RAN#87-e | RAN2 | 16.0.0 | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1466 | - | B | 15.8.0 | Rel-16 | Running CR on 36.321 for NB-IoT |
R2-2000983
| revised | RAN2#109-e | Ericsson |
| | | | | NB_IOTenh3-Core |
|
|
|
| 36.321 | 1465 | 1 | B | 15.8.0 | Rel-16 | Introduction of further enhancements for eMTC |
R2-2001872
| agreed | RAN2#109-e | Ericsson |
RP-200360
| approved | RAN#87-e | RAN2 | 16.0.0 | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1465 | - | B | 15.8.0 | Rel-16 | Running CR on 36.321 for eMTC |
R2-2000976
| revised | RAN2#109-e | Ericsson |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.321 | 1464 | 1 | B | 15.8.0 | Rel-16 | Recommended Bit Rate/Query for FLUS and MTSI |
R2-2002178
| agreed | RAN2#109-e | Qualcomm Incorp... |
RP-200359
| approved | RAN#87-e | RAN2 | 16.0.0 | E_FLUS |
|
|
|
| 36.321 | 1464 | - | B | 15.8.0 | Rel-16 | Recommended Bit Rate/Query for FLUS and MTSI |
R2-2000439
| revised | RAN2#109-e | Qualcomm Incorp... |
| | | | | E_FLUS |
|
|
|
| 36.321 | 1463 | 2 | B | 15.8.0 | Rel-16 | Introducation of even further mobility enhancement in E-UTRAN |
R2-2001769
| agreed | RAN2#109-e | vivo |
RP-200364
| approved | RAN#87-e | RAN2 | 16.0.0 | LTE_feMob-Core |
|
|
|
| 36.321 | 1463 | 1 | B | 15.8.0 | Rel-16 | [Running 36.321 CR for LTE feMob] |
R2-2001755
| revised | RAN2#109-e | vivo (rapporteur) |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1463 | - | B | 15.8.0 | Rel-16 | Running 36.321 CR for LTE feMob |
R2-2000371
| revised | RAN2#109-e | vivo (rapporteur) |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1462 | - | F | 15.7.0 | Rel-15 | Correction to PHR in dual connectivity |
R2-1916398
| agreed | RAN2#108 | Qualcomm Inc, N... |
RP-192935
| approved | RAN#86 | RAN2 | 15.8.0 | NR_newRAT-Core |
|
|
|
| 36.321 | 1461 | 3 | B | 15.8.0 | Rel-16 | Introduction of Power headroom reporting for Additional SRS |
R2-2001741
| agreed | RAN2#109-e | Ericsson |
RP-200362
| approved | RAN#87-e | RAN2 | 16.0.0 | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.321 | 1461 | 2 | B | 15.8.0 | Rel-16 | Introduction of Power headroom reporting for Additional SRS |
R2-2001721
| revised | RAN2#109-e | Ericsson |
| | | | | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.321 | 1461 | 1 | B | 15.8.0 | Rel-16 | Introduction of Power headroom reporting for Additional SRS |
R2-2001079
| revised | RAN2#109-e | Ericsson |
| | | | | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.321 | 1461 | - | B | 15.7.0 | Rel-16 | Introduction of Additional SRS |
R2-1915644
| revised | RAN2#108 | Ericsson |
| | | | | LTE_DL_MIMO_EE-Core |
|
|
|
| 36.321 | 1460 | - | B | 15.7.0 | Rel-16 | Running 36.321 CR for LTE feMob |
R2-1914695
| endorsed | RAN2#108 | vivo (rapporteur) |
| | | | | LTE_feMob-Core |
|
|
|
| 36.321 | 1459 | 2 | F | 15.7.0 | Rel-15 | Clarification of PDCCH monitoring when not fully aligned with PDCCH periods |
R2-1916439
| agreed | RAN2#108 | NTT DOCOMO INC. |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | NB_IOT-Core, TEI15 |
|