TDoc | Title | Source |
---|---|---|
R2-2104700 | Agenda for RAN2#114-e | Chairman |
TDoc | Title | Source |
---|---|---|
R2-2104701 | RAN2#113bis-e Meeting Report | MCC |
R2-2106641 | RAN2#113bis-e Meeting Report | MCC |
TDoc | Title | Source |
---|---|---|
R2-2106469 | 3GPP TSG RAN WG2 Handbook (05/2021) | Chairman |
R2-2106565 | Correction of MRO in stage 2 | R3 (Samsung, CMCC, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility) |
R2-2106566 | Correction on LTE aerial feature | R3 (Ericsson, Qualcomm Incorporated) |
R2-2106567 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | R3 (Qualcomm Incorporated, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics, Huawei) |
R2-2106568 | 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario | R3 (Intel Corporation, Samsung, LGE) |
R2-2106569 | 37.340 correction for CHO early data forwarding in MN to eNB/gNB Change scenario | R3 (Intel Corporation, Samsung, LGE) |
R2-2106570 | Addition of sidelink MR-DC resource coordination | R3 (Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation, Huawei) |
R2-2106571 | No partial success in the SN initiated SN Modification procedure for EN-DC | R3 (Ericsson, NTT DOCOMO, INC., ZTE, Nokia, Nokia Shanghai Bell, Huawei) |
R2-2106572 | No partial success in the SN initiated SN Modification procedure for EN-DC | R3 (Ericsson, NTT DOCOMO, INC., ZTE, Nokia, Nokia Shanghai Bell, Huawei) |
R2-2106573 | Correction on NRPPa transaction types | R3 (Huawei, CMCC) |
R2-2106574 | R15CR37.340 for SCG release | R3 (ZTE, Ericsson) |
R2-2106575 | R16CR37.340 for SCG release | R3 (ZTE, Ericsson) |
R2-2106614 | Reserved for breakout session | MCC |
R2-2106629 | Correction on NRPPa transaction types | R3 (Huawei, CMCC) |
TDoc | Title | Source |
---|---|---|
R2-2106454 | Stealth Pirating Attack by RACH Rebroadcast Overwriting (SPARROW) (FSAG Doc 93_009) | GSMA |
TDoc | Title | Source |
---|---|---|
R2-2104793 | Corrections on the acquisition of a posSI message | CATT |
R2-2104794 | Corrections on the acquisition of a posSI message | CATT |
R2-2104800 | Corrections on the acquisition of a posSI message by BL UE or UE in CE | CATT |
R2-2104801 | Corrections on the acquisition of a posSI message by BL UE or UE in CE | CATT |
R2-2105209 | Corrections to Positioning SI message scheduling for eMTC and NB-IoT | Lenovo, Motorola Mobility |
R2-2105210 | Corrections to Positioning SI message scheduling for eMTC and NB-IoT | Lenovo, Motorola Mobility |
R2-2105211 | Positioning SI message scheduling for eMTC | Lenovo, Motorola Mobility |
R2-2106405 | Clarification on endTransaction field | Samsung |
R2-2106410 | Clarification on endTransaction field | Samsung |
R2-2106579 | Report from email discussion [AT114-e][610][POS] Agenda item 4.4 on LTE positioning Rel-15 and earlier (Lenovo) | Lenovo |
R2-2106592 | Corrections to Positioning SI message scheduling for eMTC and NB-IoT | Lenovo, Motorola Mobility |
R2-2106593 | Corrections to Positioning SI message scheduling for eMTC and NB-IoT | Lenovo, Motorola Mobility |
TDoc | Title | Source |
---|---|---|
R2-2106137 | Correction on category dependency for DL Category 13 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2106142 | Correction on integrity verification failure | Samsung |
R2-2106143 | Correction on integrity verification failure | Samsung |
R2-2106288 | Correction on T325 | Google Inc. |
R2-2106292 | Correction on T325 | Google Inc. |
R2-2106317 | Minor changes collected by Rapporteur for Rel-15 | Samsung |
R2-2106318 | Minor changes collected by Rapporteur for Rel-16 | Samsung |
R2-2106497 | Correction on T325 | Google Inc. |
R2-2106498 | Correction on T325 | Google Inc. |
R2-2106499 | Minor changes collected by Rapporteur for Rel-15 | Samsung |
R2-2106500 | Minor changes collected by Rapporteur for Rel-16 | Samsung |
R2-2106510 | Minor changes collected by Rapporteur for Rel-16 | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2106639 | Offline 001 on Rel-15 Stage 2 Corrections | Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2105001 | Removing ambiguous legacy and normal terms from handover descriptions | Nokia, Nokia Shanghai Bell |
R2-2105002 | Removing ambiguous legacy and normal terms from handover descriptions | Nokia, Nokia Shanghai Bell |
R2-2105763 | Clarification to data forwarding upon SN change | Ericsson |
R2-2105783 | Clarification to data forwarding upon SN change | Ericsson |
R2-2106170 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (Rapporteur), Ericsson |
R2-2106174 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (Rapporteur), Ericsson |
R2-2106628 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (Rapporteur), Ericsson |
R2-2106790 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (Rapporteur), Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104733 | LS on Handover terminology (S5-211324; contact: Ericsson) | SA5 |
TDoc | Title | Source |
---|---|---|
R2-2106194 | Correction on PSCell change without security key change | Huawei, HiSilicon |
R2-2106195 | Correction on PSCell change without security key change | Huawei, HiSilicon |
R2-2106685 | Correction on PSCell change without security key change and data forwarding upon SN change with full configuration | Huawei, HiSilicon, Ericsson |
R2-2106686 | Correction on PSCell change without security key change and data forwarding upon SN change with full configuration, | Huawei, HiSilicon, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2106642 | Report of [AT114-e][002][NR15] User Plane | NEC |
TDoc | Title | Source |
---|---|---|
R2-2105747 | Correction on MAC behavior for suspended radio bearers for Rel-15 | Huawei, HiSilicon |
R2-2105748 | Correction on MAC behavior for suspended radio bearers for Rel-16 | Huawei, HiSilicon |
R2-2105849 | Correction to 38.321 on the term of the handover in handling of MAC CE | ZTE, Sanechips |
R2-2105850 | Correction to 38.321 on the term of the handover in handling of MAC CE | ZTE, Sanechips |
R2-2106286 | Clarification on not monitoring PDCCH for SCell when the SCell is deactivated | ZTE Corporation, Sanechips |
R2-2106455 | Correction on BSR calculation for suspended radio bearers | MediaTek |
R2-2106456 | Correction on BSR calculation for suspended radio bearers | MediaTek |
TDoc | Title | Source |
---|---|---|
R2-2105264 | RRC connection re-establishment | Nokia, Nokia Shanghai Bell, , Sequans Communications |
R2-2105315 | Correction on suspended AM DRB in PDCP re-establishment | NEC, LG Electronics |
R2-2105316 | Correction on suspended AM DRB in PDCP re-establishment | NEC, LG Electronics |
R2-2105469 | Clarification on the change of PDU session ID | Samsung |
R2-2105470 | Clarification on the change of PDU session ID | Samsung |
R2-2105555 | RRC connection re-establishment | Nokia, Ericsson, Nokia Shanghai Bell, Sequans Communications |
R2-2105556 | RRC connection re-establishment | Nokia, Ericsson, Nokia Shanghai Bell, Sequans Communications |
R2-2105743 | On change of PDU session ID for an established DRB | Huawei, HiSilicon |
R2-2105746 | Clarification on PDCP suspend and suspended DRB | Huawei, HiSilicon |
R2-2105761 | Change of PDU Session ID | Ericsson |
R2-2106302 | Clarification on suspended AM DRB | Samsung Electronics Polska |
R2-2106319 | Clarification on suspended AM DRB | Samsung Electronics Polska |
R2-2106699 | Correction on suspended AM DRB in PDCP re-establishment | NEC, LG Electronics, Nokia, Ericsson, Nokia Shanghai Bell, Sequans Communications |
R2-2106700 | Correction on suspended AM DRB in PDCP re-establishment | NEC, LG Electronics, Nokia, Ericsson, Nokia Shanghai Bell, Sequans Communications |
TDoc | Title | Source |
---|---|---|
R2-2106801 | Offline 006 on Rel-15 Connection Control III | Qualcomm (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2105106 | Clarification on CGI reporting | Apple |
R2-2105107 | Clarification on CGI reporting | Apple |
R2-2105148 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
R2-2105149 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
R2-2105150 | CR on RRC processing delay | ZTE Corporation, Sanechips |
R2-2105151 | CR on RRC processing delay | ZTE Corporation, Sanechips |
R2-2105152 | CR on RRC processing delay | ZTE Corporation, Sanechips |
R2-2105153 | CR on RRC processing delay | ZTE Corporation, Sanechips |
R2-2105175 | CR on the supportedBandwidthCombinationSet-R15 | ZTE Corporation, Sanechips |
R2-2105176 | CR on the supportedBandwidthCombinationSet-R16 | ZTE Corporation, Sanechips |
R2-2105180 | CR on the 35M/45M supporting-R15 | ZTE Corporation, Sanechips |
R2-2105181 | CR on the 35M/45M supporting-R16 | ZTE Corporation, Sanechips |
R2-2105204 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
R2-2105205 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
R2-2105459 | Clarification on SCellFrequencies | Nokia, Nokia Shanghai Bell |
R2-2105462 | Clarification on SCellFrequencies | Nokia, Nokia Shanghai Bell |
R2-2105647 | Introduction of DL scheduling slot offset capabilities in UERadioPagingInformation | Ericsson |
R2-2105648 | Introduction of DL scheduling slot offset capabilities in UERadioPagingInformation | Ericsson |
R2-2105931 | Clarification of CSI measurement configuration | Ericsson |
R2-2105937 | Clarification of CSI measurement configuration | Ericsson |
R2-2105938 | Miscellaneous non-controversial corrections Set X | Ericsson |
R2-2105939 | Miscellaneous non-controversial corrections Set X | Ericsson |
R2-2105980 | Correction to the use of simultaneous CSI-RS resources | Ericsson, Nokia |
R2-2105981 | Correction to the use of simultaneous CSI-RS resources | Ericsson, Nokia |
R2-2106020 | Clarification of mcg-RB-config field description | Ericsson |
R2-2106021 | Clarification of mcg-RB-config field description | Ericsson |
R2-2106180 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
R2-2106181 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
R2-2106300 | Correction on T325 | Google Inc. |
R2-2106308 | Correction on T325 | Google Inc. |
R2-2106325 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
R2-2106327 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
R2-2106390 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
R2-2106391 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
R2-2106632 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
R2-2106643 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
R2-2106644 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
R2-2106668 | Correction on T325 | Google Inc. |
R2-2106669 | Correction on T325 | Google Inc. |
R2-2106691 | CR on the 35M45M supporting-R15 | ZTE Corporation, Sanechips |
R2-2106692 | CR on the 35M45M supporting-R16 | ZTE Corporation, Sanechips |
R2-2106715 | Miscellaneous non-controversial corrections Set X | Ericsson |
R2-2106716 | Miscellaneous non-controversial corrections Set X | Ericsson |
R2-2106719 | [AT114-e][003][NR15] CP IPA and Miscellaneous CRs | Ericsson |
R2-2106727 | Clarification on SCellIndex and servCellIndex | NTT DOCOMO, INC. |
R2-2106728 | Clarification on SCellIndex and servCellIndex | NTT DOCOMO, INC. |
R2-2106791 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2106800 | [AT114-e][007][NR15] Connection Control IV (ZTE) | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104827 | CR on default configuration | OPPO |
R2-2104828 | CR on default configuration | OPPO |
R2-2104905 | Correction on CSI-RS configuration | vivo |
R2-2104906 | Correction on CSI-RS configuration | vivo |
R2-2104919 | Handling of common configuration | Qualcomm Incorporated |
R2-2105089 | Clarification on the Timing Reference of PSCell SMTC Configuration | Apple, Xiaomi, ZTE Corporation, Sanechips, Samsung, CATT, Ericsson, OPPO |
R2-2105090 | Clarification on NR HO without SCG Configuration Change | Apple |
R2-2105091 | Clarification on NR HO without SCG Configuration Change | Apple |
R2-2105092 | DRAFT LS on the NR HO without SCG Configuration Change | Apple |
R2-2105174 | Discussion on the Common Configuration in the Dedicated Signaling | ZTE Corporation, Sanechips |
R2-2105323 | Correction on CrossCarrierSchedulingConfig Introduced by Two PUCCH Group | CATT |
R2-2105324 | Correction on CrossCarrierSchedulingConfig Introduced by Two PUCCH Group | CATT |
R2-2105392 | Correction on firstActiveDownlinkBWP-Id | ZTE Corporation, Sanechips, Ericsson |
R2-2105403 | Correction on firstActiveDownlinkBWP-Id(R16) | ZTE Corporation, Sanechips, Ericsson |
R2-2105404 | Correction on aperiodicSRS-Resource | ZTE Corporation, Sanechips |
R2-2105405 | Correction on aperiodicSRS-Resource(R16) | ZTE Corporation, Sanechips |
R2-2105503 | Further clarification on random access problem | ZTE Corporation, Sanechips |
R2-2105582 | Discussion on abortion of resume procedure | Huawei, HiSilicon |
R2-2105583 | Clarification on the abortion of RRC connection resume | Huawei, HiSilicon |
R2-2105584 | Clarification on the abortion of RRC connection resume | Huawei, HiSilicon |
R2-2105649 | Clarification for an ongoing establishment and resume procedure | Ericsson |
R2-2105650 | Clarification for an ongoing establishment and resume procedure | Ericsson |
R2-2105767 | RRC processing time for Scell modification | Ericsson, Nokia, Nokia Shanghai Bell |
R2-2105768 | Clarification on NR-DC procedures | Ericsson |
R2-2105769 | Summary of [Post113bis-e][060][NR15] RLC bearer handling with Full Configuration | Ericsson, Mediatek Inc. |
R2-2105933 | Configuration of common fields in dedicated signalling | Ericsson |
R2-2105946 | Abortion of RRC connection resume procedure by upper layers | Ericsson |
R2-2105947 | Abortion of RRC connection resume procedure by upper layers | Ericsson |
R2-2105948 | Abortion of RRC connection resume procedure by upper layers | Ericsson |
R2-2105949 | Abortion of RRC connection resume procedure by upper layers | Ericsson |
R2-2105950 | Correction for RRC Resume latency requirements | Huawei, HiSilicon |
R2-2105951 | Correction for RRC Resume latency requirements | Huawei, HiSilicon |
R2-2106077 | Correction on flow remapping to an added DRB | Sequans Communications |
R2-2106079 | Correction on flow remapping to an added DRB | Sequans Communications |
R2-2106135 | Clarification on NR HO without SCG Configuration Change | Apple |
R2-2106178 | OverheatingIndicationProhibitTimer for SCG in (NG)EN-DC | Qualcomm Incorporated |
R2-2106179 | OverheatingIndicationProhibitTimer for SCG in (NG)EN-DC | Qualcomm Incorporated |
R2-2106182 | Clarification on the frequency deprioritisation | Huawei, HiSilicon, China Unicom |
R2-2106183 | Clarification on the frequency deprioritisation | Huawei, HiSilicon, China Unicom |
R2-2106188 | Clarification on releasing of BWP | Huawei, HiSilicon |
R2-2106189 | Clarification on releasing of BWP | Huawei, HiSilicon |
R2-2106190 | Correction on SCG failure reporting procedure | Huawei, HiSilicon |
R2-2106191 | Correction on SCG failure reporting procedure | Huawei, HiSilicon |
R2-2106192 | Clarification of initiation of RRC resume procedure | Huawei, HiSilicon |
R2-2106193 | Clarification of initiation of RRC resume procedure | Huawei, HiSilicon |
R2-2106264 | Correction on A-CSI trigger state configuration | vivo |
R2-2106265 | Correction on A-CSI trigger state configuration | vivo |
R2-2106267 | Clarification of recurrence in RateMatchPattern | Qualcomm Incorporated |
R2-2106270 | Clarification of recurrence in RateMatchPattern | Qualcomm Incorporated |
R2-2106304 | RLC re-establishment upon full configuration | Huawei, HiSilicon |
R2-2106305 | RLC re-establishment upon full configuration | Huawei, HiSilicon |
R2-2106329 | Clarification on RLC bearer handling in full configuration | MediaTek Inc., Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Vivo, Huawei, HiSilicon, ZTE Corporation, Apple |
R2-2106330 | Clarification on RLC bearer handling in full Configuration | MediaTek Inc., Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Vivo, Huawei, HiSilicon, ZTE Corporation, Apple |
R2-2106377 | CR on random access problem of MCG | ZTE Corporation, Sanechips |
R2-2106378 | CR on random access problem of MCG | ZTE Corporation, Sanechips |
R2-2106414 | Clarification on leftover issues for NR-DC | Huawei, HiSilicon |
R2-2106415 | Correction on PSCell SMTC timing reference in NR-DC | Huawei, HiSilicon |
R2-2106416 | Correction on PSCell SMTC timing reference in NR-DC | Huawei, HiSilicon |
R2-2106451 | Discussion on the Common Configuration in the Dedicated Signaling | ZTE Corporation, Sanechips |
R2-2106460 | Correction on firstActiveDownlinkBWP-Id | ZTE Corporation, Sanechips, Ericsson, Nokia |
R2-2106461 | Correction on firstActiveDownlinkBWP-Id | ZTE Corporation, Sanechips, Ericsson, Nokia |
R2-2106697 | Correction on flow remapping to an added DRB | Sequans Communications, Nokia, Nokia Shanghai Bell |
R2-2106698 | Correction on flow remapping to an added DRB | Sequans Communications, Nokia, Nokia Shanghai Bell |
R2-2106708 | RLC and PDCP Re-establishment upon RRC resume/reestablishment | Huawei, HiSilicon, Ericsson, Intel, ZTE, Nokia, Nokia Shanghai Bell |
R2-2106709 | RLC and PDCP Re-establishment upon RRC resume/reestablishment | Huawei, HiSilicon, Ericsson, Intel, ZTE, Nokia, Nokia Shanghai Bell |
R2-2106731 | Report of offline discussion: [AT114-e][004][NR15] Connection Control I (Huawei) | Huawei, HiSilicon |
R2-2106732 | Abortion of RRC connection resume handling | Huawei, HiSilicon |
R2-2106733 | Abortion of RRC connection resume handling | Huawei, HiSilicon |
R2-2106737 | Clarification on RLC bearer handling in full configuration | MediaTek Inc., Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Vivo, Huawei, HiSilicon, ZTE Corporation, Apple, Intel |
R2-2106738 | Clarification on RLC bearer handling in full configuration | MediaTek Inc., Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Vivo, Huawei, HiSilicon, ZTE Corporation, Apple, Intel |
R2-2106754 | Clarification on the Timing Reference of PSCell SMTC Configuration | Apple, Xiaomi, ZTE Corporation, Sanechips, Samsung, CATT, Ericsson, OPPO, Nokia |
R2-2106755 | Summary of [AT114-e][005][NR15] Connection Control II (Apple) | Apple |
R2-2106778 | Correction on A-CSI trigger state configuration | vivo |
R2-2106779 | Correction on A-CSI trigger state configuration | vivo |
TDoc | Title | Source |
---|---|---|
R2-2105154 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips, Samsung, NEC, Nokia, Ericsson, CATT |
R2-2105388 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips, Samsung, NEC, Nokia, Ericsson, CATT |
R2-2105463 | Further discussion on full and delta configuration signalling for inter-MN handover without SN change | Nokia Italy |
R2-2105468 | Further discussion on full and delta configuration signalling for inter-MN handover without SN change | Nokia, Nokia Shanghai Bell, Ericson |
R2-2105940 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation |
R2-2105945 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation |
R2-2106186 | Correction on full configuration during SN change | Huawei, HiSilicon |
R2-2106187 | Correction on full configuration during SN change | Huawei, HiSilicon |
R2-2106216 | Clarification on RRC fullconfig for SN modification | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Fujitsu, ZTE Corporation, Sanechips, Huawei, HiSilicon |
R2-2106269 | Clarification on RRC fullconfig for SN modification | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Fujitsu, ZTE Corporation, Sanechips, Huawei, HiSilicon |
R2-2106306 | Support of full configuration for inter-MN handover without SN change | Huawei, HiSilicon |
R2-2106331 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips, Samsung, NEC, Nokia, Ericsson, CATT |
R2-2106332 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips, Samsung, NEC, Nokia, Ericsson, CATT |
R2-2106663 | Summary of [AT114-e][008][NR15] Inter-Node Signalling (Nokia) | Nokia |
R2-2106682 | LS on inter-MN handover without SN change | RAN2 |
R2-2106717 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation, NEC |
R2-2106718 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation, NEC |
R2-2106780 | Clarification on RRC full config for PSCell change | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Fujitsu, ZTE Corporation, Sanechips, Huawei, HiSilicon, NEC |
R2-2106781 | Clarification on RRC full config for PSCell change | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Fujitsu, ZTE Corporation, Sanechips, Huawei, HiSilicon, NEC |
R2-2106782 | Clarification on RRC full config for PSCell change | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Intel, Samsung, Fujitsu, ZTE Corporation, Sanechips, NEC |
R2-2106783 | Clarification on RRC full config for PSCell change | NTT DOCOMO INC., Ericsson, Nokia, Nokia Shanghai Bell, Intel, Samsung, Fujitsu, ZTE Corporation, Sanechips, NEC |
R2-2106788 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation, NEC |
R2-2106789 | Clean-up of INM procedure text | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, NTT DOCOMO, INC, ZTE Corporation, NEC |
R2-2106792 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips, Samsung, NEC, Nokia, Ericsson, CATT |
TDoc | Title | Source |
---|---|---|
R2-2104952 | Discussion on RMSI reception based on non-zero search space | OPPO, CMCC |
R2-2104953 | 38331 R15 RMSI reception based on non-zero search space-option 1 | OPPO |
R2-2104954 | 38331 R16 RMSI reception based on non-zero search space-option 1 | OPPO |
R2-2104955 | 38331 R15 RMSI reception based on non-zero search space-option 2 | OPPO |
R2-2104956 | 38331 R16 RMSI reception based on non-zero search space-option 2 | OPPO |
R2-2105367 | Clarification of cell Identity for SIB validity | vivo |
R2-2105368 | Clarification of cell Identity for SIB validity | vivo |
R2-2106688 | Report of [AT114-e][009][NR15] System Information (OPPO) | OPPO |
R2-2106689 | LS on RMSI reception based on non-zero search space | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2105993 | Clarification on RRC full configuration of SgNB | Huawei, HiSilicon |
R2-2105994 | Clarification on RRC full config for SN modification | Huawei, HiSilicon |
R2-2105995 | Clarification on RRC full config for SN modification | Huawei, HiSilicon |
R2-2106734 | Abortion of RRC connection resume handling | Huawei, HiSilicon |
R2-2106735 | Abortion of RRC connection resume handling | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2105066 | Left issue on fallback BC | OPPO |
R2-2105169 | CR on the Intra-band and Inter-band EN-DC Capabilities - R15 | ZTE Corporation, Sanechips |
R2-2105170 | CR on the Intra-band and Inter-band EN-DC Capabilities - R16 | ZTE Corporation, Sanechips |
R2-2105171 | Further Discussion on the BCS with Different Supported Bandwidths | ZTE Corporation, Sanechips |
R2-2105172 | CR on the fallback Band Combination Removing-R15 | ZTE Corporation, Sanechips |
R2-2105173 | CR on the fallback Band Combination Removing-R16 | ZTE Corporation, Sanechips |
R2-2105182 | CR on the Intra-band and Inter-band EN-DC Capabilities - R15 | ZTE Corporation, Sanechips |
R2-2105183 | CR on the Intra-band and Inter-band EN-DC Capabilities - R16 | ZTE Corporation, Sanechips |
R2-2105188 | Clarification on IMS video over split bearer in (NG)EN-DC | Google Inc. |
R2-2105189 | Clarification on IMS video over split bearer in (NG)EN-DC | Google Inc. |
R2-2105190 | Clarification on IMS video over split bearer in NR-DC and NE-DC | Google Inc. |
R2-2105191 | Clarification on IMS video over split bearer in NR-DC and NE-DC | Google Inc. |
R2-2105406 | Discussion on multipleCORESET | ZTE Corporation, Sanechips |
R2-2105407 | Correction on multipleCORESET | ZTE Corporation, Sanechips |
R2-2105408 | Correction on multipleCORESET(R16) | ZTE Corporation, Sanechips |
R2-2105629 | Discussion on IMS video capabilities | Google Inc. |
R2-2105640 | Indication of unsupported capabilities for IMS video | Google Inc. |
R2-2105641 | Indication of unsupported capabilities for IMS video | Google Inc. |
R2-2105644 | Indication of unsupported capabilities for IMS video | Google Inc. |
R2-2105677 | Introduction of capabilities for IMS video | Google Inc. |
R2-2105679 | Introduction of capabilities for IMS video | Google Inc. |
R2-2105737 | Introduction of capabilities for IMS video | Google Inc. |
R2-2105794 | Introduction of capabilities for IMS video | Google Inc. |
R2-2105941 | BCS fallback behaviour | Ericsson |
R2-2105983 | Allowed bandwidth in BWP configuration | Ericsson |
R2-2105984 | Use of CA-Parameters extensions for NR-DC | Ericsson |
R2-2106119 | Discussion on BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106120 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106121 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106122 | Introduction of indication for BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106123 | Introduction of indication for BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106124 | Further clarification on supportedNumberTAG | Huawei, HiSilicon, Apple |
R2-2106125 | Further clarification on supportedNumberTAG | Huawei, HiSilicon, Apple |
R2-2106126 | Clarification on pdcch-MonitoringAnyOccasions | Huawei, HiSilicon |
R2-2106127 | Clarification on pdcch-MonitoringAnyOccasions | Huawei, HiSilicon |
R2-2106128 | Clarification on the simultaneousRxTxInterBandCA capability in NR-DC | Huawei, HiSilicon |
R2-2106129 | Clarification on the simultaneousRxTxInterBandCA capability in NR-DC | Huawei, HiSilicon |
R2-2106130 | Discussion on contiguous and non-contiguous for intra-band EN-DC | Huawei, HiSilicon |
R2-2106360 | CR on the fallback Band Combination Removing-R15 | ZTE Corporation, Sanechips |
R2-2106393 | Clarification on maximum number of TCI-state for PDSCH | MediaTek Inc. |
R2-2106394 | Clarification on maximum number of TCI-state for PDSCH | MediaTek Inc. |
R2-2106660 | Discussion on IMS video capabilities | Google Inc. |
R2-2106710 | Summary of offline 011 Rel-15 UE caps II | Ericsson |
R2-2106711 | Correction to ca-ParametersNR-ForDC | Ericsson, Intel |
R2-2106712 | Correction to ca-ParametersNR-ForDC | Ericsson, Intel |
R2-2106720 | CR on the fallback Band Combination Removing-R15 | ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated, Ericsson |
R2-2106721 | CR on the fallback Band Combination Removing-R16 | ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated, Ericsson |
R2-2106739 | Clarification on maximum number of TCI-state for PDSCH | MediaTek Inc. |
R2-2106740 | Clarification on maximum number of TCI-state for PDSCH | MediaTek Inc. |
R2-2106741 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106742 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
R2-2106743 | Further clarification on supportedNumberTAG | Huawei, HiSilicon, Apple |
R2-2106744 | Further clarification on supportedNumberTAG | Huawei, HiSilicon, Apple |
R2-2106760 | Summary of [AT114-e][010][NR15] UE cap I - BCS for fallback BC (Huawei) | Huawei, HiSilicon |
R2-2106769 | CR on the Fallback Band Combination Removing-R15 | ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2106770 | CR on the Fallback Band Combination Removing-R16 | ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2104907 | Discussion on paging DRX cycle determination for inactive mode | vivo |
R2-2105744 | Correction on PO determination for UE in inactive state-38.304 | ZTE corporation, Sanechips, Ericsson |
R2-2105745 | Correction on PO determination for UE in inactive state-38.306 | ZTE corporation, Sanechips, Ericsson |
R2-2105751 | Discussion on PO determination for UE in inactive state | ZTE corporation, Sanechips, Ericsson |
R2-2105752 | Correction on PO determination for UE in inactive state-38.331 | ZTE corporation, Sanechips, Ericsson |
R2-2105753 | Correction on PO determination for UE in inactive state-36.331 | ZTE corporation, Sanechips, Ericsson |
R2-2105754 | Correction on PO determination for UE in inactive state-36.304 | ZTE corporation, Sanechips, Ericsson |
R2-2105755 | Correction on PO determination for UE in inactive state-36.306 | ZTE corporation, Sanechips, Ericsson |
R2-2106196 | Discussion on PO misalignment for INACTVIE and IDLE states | Huawei, HiSilicon |
R2-2106771 | Report of [AT114-e] [013] [NR15] Idle Inactive mode (ZTE) | ZTE corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2105052 | Correction to E-CID-R15 | Huawei, HiSilicon |
R2-2105053 | Correction to E-CID-R16 | Huawei, HiSilicon |
R2-2106406 | Clarification on endTransaction field | Samsung |
R2-2106411 | Clarification on endTransaction field | Samsung |
R2-2106580 | [AT114-e][611][POS] Agenda Item 5.5 on NR Rel-15 positioning (Huawei) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2106640 | Offline 014 on Rel-16 Stage 2 Corrections | Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2105474 | Clarification on IP packet type in DedicatedInfoF1c | Nokia, Nokia Shanghai Bell |
R2-2105859 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT | ZTE Corporation (Rapporteur) |
R2-2105891 | Addition of size limitation for SRVCC | Ericsson |
R2-2105905 | Addition of size limitation for SRVCC | Ericsson, Nokia (Rapporteur) |
R2-2106389 | Updated description of multi-TRP | Nokia (rapporteur) |
R2-2106459 | Missing IAB SA mode for QoS description | Samsung |
R2-2106610 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT | ZTE Corporation (Rapporteur) |
R2-2106635 | Missing IAB SA mode for QoS description | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2104714 | LS on maximum size change of switchTriggerToAddModList-r16 and switchTriggerToReleaseList-r16, and update to TS 38.300 (R1-2104094; contact: Lenovo) | RAN1 |
R2-2105185 | Correction on descriptions of PDCCH features | Huawei, HiSilicon |
R2-2105187 | Correction on PDCP duplication for a radio bearer | Huawei, HiSilicon |
R2-2105267 | Miscellaneous Corrections | Nokia (Rapporteur), Apple, Ericsson, Nokia Shanghai Bell |
R2-2105356 | Corrections on stage-2 description for IAB | vivo |
R2-2105892 | Removing incorrect SRVCC limitation | Ericsson, Nokia |
R2-2105955 | Description of PDCCH features introduced for NR-U | Lenovo, Motorola Mobility, Ericsson |
R2-2106655 | Miscellaneous Corrections | Nokia (Rapporteur), Apple, Ericsson, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2106176 | Overheating assistance configuration for SCG in EN-DC | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2105762 | Correction on MAC handling of uplink grants within a bundle | CATT |
R2-2105785 | Clarification on which uplink grants participate to the intra-UE prioritization procedure | CATT, Samsung, Ericsson |
R2-2105932 | Corrections on BSR/PHR content handling | ZTE Corporation, Sanechips |
R2-2106206 | Miscellaneous corrections on BAP transmitting operation and default routing | Huawei, HiSilicon |
R2-2106309 | PDCP miscellaneous corrections | LG Electronics Inc. (PDCP rapporteur) |
R2-2106630 | PDCP miscellaneous corrections | LG Electronics Inc. (PDCP rapporteur) |
R2-2106658 | Summary of [AT114-e][015][NR16] User Plane IPA CRs (CATT) | CATT (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2104724 | LS on SCell activation requirements for NR-U (R4-2105699; contact: Nokia) | RAN4 |
R2-2104759 | Remaining issues on overlapped PUSCH and UCI with UL skipping | vivo |
R2-2104864 | MAC behaviour for overlapped UCI(s), SR and PUSCH with equal L1 priority | Huawei, HiSilicon |
R2-2104895 | On UCI multiplexing visibility from MAC | CATT |
R2-2104896 | Correction on UL skipping with lch-basedPrioritization | CATT |
R2-2105065 | Correction on handling rule for CG-CG conflict | vivo |
R2-2105067 | CR for secondary DRX group | OPPO |
R2-2105068 | Clarification on reporting multiplexed CSI on PUCCH | OPPO |
R2-2105112 | UL skipping and intra-UE prioritization | Apple |
R2-2105113 | Discussion of UCI multiplexing and overlapped SR/PUSCH | Apple |
R2-2105230 | Draft reply LS to RAN1 on overlapped data and SR are of equal L1 priority | vivo |
R2-2105231 | Analysis on SCell activation/deactivation requirements for NR-U | Huawei, HiSilicon |
R2-2105232 | Clarification on secondary DRX group | Samsung |
R2-2105564 | Consideration on the UCI multiplexing | OPPO |
R2-2105673 | On Intra-UE prioritization and UL skipping | Ericsson |
R2-2105749 | Clarification on MAC PDU assembly with eLCID | Huawei, HiSilicon |
R2-2105780 | UL Skipping Condition for LCH-basedPrioritization | Samsung |
R2-2105781 | Discussion on overlapped data and SR with equal PHY priority | Samsung |
R2-2105851 | Correction to 38.321 on msga-TransMax selection for 2-step RACH | ZTE Corporation, Sanechips |
R2-2105852 | Correction to 38.321 on PUSCH Skipping coupled with intra-UE multiplexing | ZTE, Sanechips |
R2-2105853 | Correction to 38.321 on UCI multiplexing for priorization handling | ZTE, Sanechips |
R2-2105854 | Consideration on interaction between L1 and L2 in MAC spec | ZTE, Sanechips |
R2-2105865 | Clarification on prioritization of retransmission over initial transmission for HARQ PID selection in NR-U | Nokia, Nokia Shanghai Bell |
R2-2105866 | Interaction between MAC and PHY for UCI Multiplexing Issues | Nokia, Nokia Shanghai Bell |
R2-2106031 | Clarification to transmission of padding and padding BSR with eLCID in IAB | Ericsson, Apple |
R2-2106321 | CR for not transmitting only padding and padding BSR with eLCID | Samsung, Nokia, Nokia Shanghai Bell, Qualcomm, LG, ZTE, MediaTek, Intel |
R2-2106442 | Discussion on whether to ignore an UL grant overlapped with UCI | MediaTek Inc. |
R2-2106694 | [AT114-e][018][NR16] MAC III (Nokia) | Nokia (Rapporteur) |
R2-2106713 | Report of [AT114-e][017][NR16] MAC I - UL Skipping | Apple |
R2-2106746 | Reply LS on overlapped data and SR with equal L1 priority | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2105357 | Corrections on BAP Control PDU operations | vivo |
R2-2105875 | Handling of erroneous data at BAP layer | Samsung Electronics GmbH |
R2-2106027 | Corrections to the handling of unknown, unforeseen, and erroneous protocol data | Ericsson, AT&T |
R2-2106028 | Handling of Unknown and Reserved Values in the BAP Header | Ericsson, AT&T |
R2-2106218 | Correction on BAP handling for the hybrid release IAB deployment | Huawei (Rapporteur), HiSilicon |
R2-2106219 | Discussion on extension principles for mixed deployment of IAB node in different releases | Huawei, HiSilicon |
R2-2106763 | Summary of [AT114-e][019][NR16] BAP (Ericsson) | Ericsson |
R2-2106764 | Corrections to the handling of unknown, unforeseen, and erroneous protocol data | Ericsson, AT&T, Samsung, Huawei, Nokia |
TDoc | Title | Source |
---|---|---|
R2-2104788 | Corrections to UE action upon SIB1 reception | Samsung Electronics Co., Ltd |
R2-2104839 | Correction on Capability of two PUCCH transmission | OPPO |
R2-2104887 | Miscellaneous corrections to Rel-16 UE capabilities | Intel Corporation |
R2-2104890 | UE Feature list for NR Rel-16 | Intel Corporation |
R2-2104904 | Correction on repetition for L1-SINR | vivo |
R2-2105104 | SSB-ToMeasure for NR-U | Apple, Fujitsu, xiaomi, LG Electronics |
R2-2105105 | Inter-RAT RRM measurement on NR-U | Apple, Fujitsu, xiaomi, LG Electronics |
R2-2105144 | Correction on T321 for autonomous gap based E-UTRAN CGI reporting | ZTE Corporation, Sanechips |
R2-2105184 | Correction on failureType in FailureReportSCG-EUTRA and scgFailureInfoEUTRA | Huawei, HiSilicon, Ericsson |
R2-2105372 | Correction on freqMonitorLocations | ASUSTeK |
R2-2105393 | Correction on description of ssb-PositionsInBurst in ServingCellConfigCommonSIB | Fujitsu |
R2-2105417 | Correction on description of subCarrierSpacing in BWP | Fujitsu,Samsung |
R2-2105422 | Correction on RNA configuration for UE in SNPN access mode | Samsung |
R2-2105527 | CR on the missing definition of "Available SNPN" in TS 38.304 | Huawei, HiSilicon |
R2-2105602 | IAB LTE changes | Samsung |
R2-2105605 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
R2-2105624 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
R2-2105732 | Clarifications on the TRP definition for positioning | Xiaomi Communications |
R2-2106207 | Miscellaenous corrections on BH RLC channel management for IAB-MT | Huawei, HiSilicon |
R2-2106208 | Miscellaneous corrections on F1 over LTE for IAB | Huawei, HiSilicon, Samsung |
R2-2106284 | Correction on releasing referenceTimePreferenceReporting and sl-AssistanceConfigNR | Google Inc. |
R2-2106448 | CR on the configuration restriction on DCI format 0_2/1_2 for unlicensed band (Option 1) | OPPO, Samsung, Xiaomi, ZTE, Apple, Intel |
R2-2106563 | Correction on Capability of two PUCCH transmission | OPPO |
R2-2106609 | Clarifications on the TRP definition for positioning | Xiaomi Communications |
R2-2106647 | Miscellaneous corrections to Rel-16 UE capabilities | Intel Corporation |
R2-2106648 | UE Feature list for NR Rel-16 | Intel Corporation |
R2-2106651 | [Offline-020][NR16] Control Plane IPA CRs and UE caps (Intel) | Intel |
R2-2106657 | Clarifications on the TRP definition for positioning | Xiaomi Communications |
R2-2106667 | Correction on releasing referenceTimePreferenceReporting and sl-AssistanceConfigNR | Google Inc. |
R2-2106670 | Corrections to the UE action upon SIB1 reception | Samsung Electronics |
R2-2106672 | Correction on T321 for autonomous gap based CGI reporting in LTE | ZTE Corporation, Sanechips |
R2-2106701 | UE Feature list for NR Rel-16 [Rel16FeatureList] | Intel Corporation |
R2-2106714 | Inter-RAT RRM measurement on NR-U | Apple, Fujitsu, xiaomi, LG Electronics |
R2-2106723 | Correction on description of subCarrierSpacing in BWP | Fujitsu, Samsung |
R2-2106756 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
R2-2106793 | Miscellaneous corrections to Rel-16 UE capabilities | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104920 | Correction on reportSlotOffsetList | Qualcomm Incorporated |
R2-2105179 | Miscellaneous Corrections to the SNPN | ZTE Corporation, Sanechips, Samsung |
R2-2105186 | Correction on switchTriggerToAddModList-r16 and switchTriggerToReleaseList-r16 | Huawei, HiSilicon |
R2-2105516 | Correction on T310 and T312 | ITRI |
R2-2105896 | Extending number of cells for search space switching trigger configuration | Ericsson |
R2-2105925 | Correction on description of msg1-SubcarrierSpacing in RACH-ConfigCommon | ZTE Corporation, Sanechips |
R2-2105926 | Correction on description of ssb-PositionsInBurst in ServingCellConfigCommon | ZTE Corporation, Sanechips |
R2-2106627 | Correction on description of msg1-SubcarrierSpacing in RACH-ConfigCommon | ZTE Corporation, Sanechips |
R2-2106722 | Miscellaneous Corrections to the SNPN | ZTE Corporation, Sanechips, Samsung |
R2-2106757 | Correction on description of msg1-SubcarrierSpacing in RACH-ConfigCommon | ZTE Corporation, Sanechips |
R2-2106758 | Extending number of cells for search space switching trigger configuration | Ericsson |
R2-2106759 | Capability bit for extending search space switching trigger configuration | Ericsson |
R2-2106765 | Report for offline discussion [AT114-e][021][NR16] RRC I (ZTE) | ZTE Corporation (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2105421 | Discussion on CGI reporting for NPN-only cell | Samsung Electronics Co., Ltd |
R2-2106281 | Discussion on CGI report for NPN-only cell | Huawei, CMCC, China Telecom, HiSilicon |
R2-2106706 | CR on CGI reporting for NPN-only cell | Huawei, Samsung, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2105964 | Discussion on SI start offset requirements | Ericsson, Verizon |
R2-2105965 | Correction of SI Scheduling | Ericsson, Verizon |
R2-2106665 | Correction of posSI Scheduling | Ericsson, Verizon |
TDoc | Title | Source |
---|---|---|
R2-2105394 | Introduction of ssb-PositionQCL-Common and ssb-PositionQCL in inter-node messages | Fujitsu |
TDoc | Title | Source |
---|---|---|
R2-2104717 | Reply LS on half-duplex operation (R1-2104122; contact: Huawei) | RAN1 |
R2-2104985 | Corrections to directional collision handling in half-duplex operation | Nokia, Nokia Shanghai Bell |
R2-2104986 | Corrections to directional collision handling in half-duplex operation | Nokia, Nokia Shanghai Bell |
R2-2104987 | Restrictions in the number of HARQ processes | Nokia, Nokia Shanghai Bell |
R2-2105069 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2105358 | Miscellaneous corrections on IAB | vivo |
R2-2105423 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2105425 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2105427 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2105645 | Resolving ambiguity in use of BAP routing ID | Samsung Electronics GmbH |
R2-2105712 | Draft Reply LS on half-duplex operation | Huawei, HiSilicon |
R2-2105713 | CR on half-duplex operation | Huawei, HiSilicon, CATT |
R2-2105714 | CR on half-duplex operation | Huawei, HiSilicon, CATT |
R2-2106115 | Extension of candidateBeamRSList set to "release" | MediaTek Inc., Intel Corporation |
R2-2106116 | Handling of candidateBeamRSListExt-v1610 set to “release” (option 1) | MediaTek Inc., Intel Corporation |
R2-2106117 | Handling of candidateBeamRSListExt-v1610 set to “release” (option 2) | MediaTek Inc., Intel Corporation |
R2-2106118 | Handling of candidateBeamRSListExt-v1610 set to “release” (option 3) | MediaTek Inc., Intel Corporation |
R2-2106177 | Overheating assistance configuration for SCG in NR-DC | Qualcomm Incorporated |
R2-2106338 | Redirection with high priority access | ZTE corporation, Sanechips |
R2-2106339 | Redirection with high priority access-38.331 | ZTE corporation, Sanechips |
R2-2106340 | Redirection with high priority access-38.306 | ZTE corporation, Sanechips |
R2-2106341 | Redirection with high priority access-36.331 | ZTE corporation, Sanechips |
R2-2106342 | Redirection with high priority access-36.306 | ZTE corporation, Sanechips |
R2-2106382 | Redirection with high priority access-36.331 | ZTE corporation, Sanechips |
R2-2106383 | Redirection with high priority access-36.306 | ZTE corporation, Sanechips |
R2-2106518 | Corrections to directional collision handling in half-duplex operation | Nokia, Nokia Shanghai Bell |
R2-2106519 | Corrections to directional collision handling in half-duplex operation | Nokia, Nokia Shanghai Bell |
R2-2106704 | Corrections to directional collision handling in half-duplex operation | Nokia, Nokia Shanghai Bell |
R2-2106736 | Report of e-mail discussion [AT114-e][022][NR16] RRC II (MediaTek) | MediaTek |
R2-2106747 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106748 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106749 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106750 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106774 | Miscellaneous corrections on IAB | vivo |
R2-2106796 | Redirection with MPS Indication [Redirect_MPS_I] | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106797 | Redirection with MPS Indication [Redirect_MPS_I] | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106798 | Redirection with MPS Indication [Redirect_MPS_I] | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
R2-2106799 | Redirection with MPS Indication [Redirect_MPS_I] | Perspecta Labs, CISA ECD, T-Mobile US, Ericsson, Qualcomm, NTT DoCoMo, AT&T, Verizon |
TDoc | Title | Source |
---|---|---|
R2-2106464 | Discussion on compatibility issue on failure type for NR SCG failure | CATT |
TDoc | Title | Source |
---|---|---|
R2-2104716 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104bis-e (R1-2104121; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2104722 | LS on introduction of new frequency separation classes (R4-2104402; contact: Nokia) | RAN4 |
R2-2104727 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2105855; contact: CMCC) | RAN4 |
R2-2104829 | Left issue on two PUCCH capability | OPPO |
R2-2104884 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2104885 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2104916 | CR on 38.306 for the capability of supporting txDiversity | vivo |
R2-2104917 | CR on 38.331 for the capability of supporting txDiversity | vivo |
R2-2105063 | Corrections on the Shared Spectrum Channel Access Parameters | CATT |
R2-2105094 | Introduction of the intra-NR and inter-RAT HST Capabilities | Apple, OPPO, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2105095 | Introduction of the intra-NR and inter-RAT HST Capabilities and Configuration | Apple, OPPO, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2105177 | CR on the Updated RAN1/4 Features -38306 | ZTE Corporation, Sanechips |
R2-2105178 | CR on the Updated RAN1/4 Features -38331 | ZTE Corporation, Sanechips |
R2-2105247 | Adding 400 Mhz and 600 MHz frequency separation classes | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2105359 | Capability of supporting one-octet eLCID in IAB | vivo |
R2-2105360 | Capability of supporting one-octet eLCID in IAB - Option A | vivo |
R2-2105361 | Capability of supporting one-octet eLCID in IAB - Option B | vivo |
R2-2105362 | Capability of supporting one-octet eLCID in IAB - Option B | vivo |
R2-2105711 | Discussion on signalling design for TxD capability | Huawei, HiSilicon |
R2-2105715 | Discussion on introduction of new frequency separation classes | Huawei, HiSilicon |
R2-2105716 | CR on introduction of new frequency separation classes | Huawei, HiSilicon |
R2-2105717 | CR on introduction of new frequency separation classes | Huawei, HiSilicon |
R2-2106316 | Correction on TPMI group signaling for UL full power transmission | Samsung |
R2-2106649 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2106650 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2106652 | [Offline-023][NR16] UE capabilities (Intel) | Intel |
R2-2106681 | LS response on two PUCCH capability | RAN2 |
R2-2106702 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2106703 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2106752 | Introduction of the intra-NR and inter-RAT HST Capabilities | Apple, OPPO, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2106753 | Introduction of the intra-NR and inter-RAT HST Capabilities and Configuration | Apple, OPPO, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2106794 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
R2-2106795 | Release-16 UE capabilities based on RAN1 and RAN4 feature lists | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2105651 | Clarification for IFRI handling | Ericsson |
R2-2106209 | Correction for TS38.304 on power class for cell selection of IAB | Huawei, HiSilicon |
R2-2106210 | Correction for TS36.304 on power class for cell selection of IAB | Huawei, HiSilicon |
R2-2106275 | Clarification of Cell Barring when SIB1 is missing | Qualcomm Incorporated |
R2-2106291 | Correction of IFRI-related conditions | LG Electronics, Samsung |
R2-2106294 | Discussion on IFRI-related condition | LG Electronics, Samgsung |
R2-2106421 | Discussion on IFRI-related condition | LG Electronics, Samsung |
R2-2106671 | [AT114-e][024][NR16] Idle Inactive (QC) | Qualcomm Incorporated |
R2-2106724 | Correction for TS38.304 on power class for cell selection of IAB | Huawei, HiSilicon |
R2-2106725 | Correction for TS36.304 on power class for cell selection of IAB | Huawei, HiSilicon |
R2-2106726 | LS to RAN4 on power class and P-max for IAB-MT cell selection | RAN2 |
R2-2106785 | Correction of IFRI-related conditions | LG Electronics, Samsung, Ericsson, Apple |
R2-2106786 | Correction of IFRI-related conditions | LG Electronics, Samsung, Ericsson, Apple |
TDoc | Title | Source |
---|---|---|
R2-2104711 | LS on the configuration of search spaces for scheduling SL transmissions (R1-2104063; contact: Ericsson) | RAN1 |
R2-2105587 | Clarification on LTE DAPS and sidelink on 36.300 | Huawei, HiSilicon |
R2-2105770 | Handling of new features and NBC changes in sidelink | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104830 | Left issue on sync configuration | OPPO |
R2-2104840 | Correction on V2X UE capability | OPPO |
R2-2105043 | Correction on parameters of SL configured grant | OPPO |
R2-2105081 | Correction on TS 38.331 from the latest RAN1 decisions | ZTE Corporation, Sanechips |
R2-2105082 | Discussion on MCS table configuration | ZTE Corporation, Sanechips |
R2-2105298 | Correction on security handling for SL-SRB1 | CATT |
R2-2105300 | Correction on SS config for scheduling SL | CATT |
R2-2105301 | Miscellaneous corrections on TS38.331 | CATT |
R2-2105346 | Discussion on SL-SRB1 integrity check failure handling | vivo |
R2-2105347 | CR on SL-SRB1 integrity check failure handling | vivo |
R2-2105348 | Draft LS on SL-SRB1 integrity check failure handling | vivo |
R2-2105349 | Clarification on priority of LTE PSSS SSSS PSBCH | vivo |
R2-2105520 | Addition of total L2 buffer size and RLC RTT for NR SL | Huawei, HiSilicon |
R2-2105585 | Correction on TS 38.331 from the latest RAN1 decisions | Huawei, HiSilicon |
R2-2105588 | Miscellaneous corrections on TS 36.331 for NR V2X | Huawei, HiSilicon |
R2-2105589 | Miscellaneous corrections on TS 38.331 for NR V2X | Huawei, HiSilicon |
R2-2105590 | Miscellaneous corrections on TS 38.331 for NR V2X (Rapporteur CR) | Huawei, HiSilicon |
R2-2105591 | Miscellaneous corrections on TS 36.331 for NR V2X (Rapporteur CR) | Huawei, HiSilicon |
R2-2105592 | Clarification on dci-FormatsSL | Huawei, HiSilicon |
R2-2105643 | Correction of Sidelink Configured Grant Type 1 Usage During Handover | Nokia, Nokia Shanghai Bell, Samsung Electronics |
R2-2105771 | Configuration of search spaces for scheduling SL transmissions | Ericsson |
R2-2105772 | Handling of sidelink configured grant during handover | Ericsson |
R2-2105913 | Correction on sidelink configuration | ZTE Corporation, Sanechips |
R2-2106564 | Correction on V2X UE capability | OPPO |
R2-2106608 | Addition of total L2 buffer size and RLC RTT for NR SL | Huawei, HiSilicon |
R2-2106611 | Corrections on TS 38.331 from the latest RAN1 decisions | Huawei, HiSilicon |
R2-2106612 | Miscellaneous corrections on TS 38.331 for NR V2X | Huawei, HiSilicon |
R2-2106613 | Miscellaneous corrections on TS 36.331 for NR V2X | Huawei, HiSilicon |
R2-2106615 | Clarification on SL-SRB1 integrity check failure handling | vivo |
R2-2106616 | Summary on SL-SRB1 integrity check failure handling | vivo (Rapporteur) |
R2-2106617 | Correction of Sidelink Configured Grant Type 1 Usage During Handover | Nokia, Nokia Shanghai Bell, Samsung Electronics, Ericsson |
R2-2106618 | Configuration of search spaces for scheduling SL transmissions | Ericsson |
R2-2106619 | Clarification on priority of LTE PSSS/SSSS/PSBCH | vivo |
R2-2106624 | [Draft] LS on SL-SRB1 integrity check failure handling | vivo |
R2-2106633 | Correction of Sidelink Configured Grant Type 1 Usage During Handover | Nokia, Nokia Shanghai Bell, Samsung Electronics, Ericsson |
R2-2106636 | Summary of CP corrections in AI 6.2.2 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104831 | Left issue on PUCCH reporting | OPPO |
R2-2104832 | Left issue on maxTransNum | OPPO |
R2-2104833 | Correction on UL-SL prioritization | OPPO, Apple |
R2-2104834 | Correction on UL-SL prioritization | OPPO, Apple |
R2-2105042 | Correction of SL configured grant | OPPO (Rapporteur) |
R2-2105080 | Correction on SR procedur for sidelink BSR | ZTE Corporation, Sanechips |
R2-2105126 | Correction on the usage of sl-ReselectAfter | Apple, OPPO, Huawei, HiSilicon, Qualcomm Incorporated |
R2-2105276 | Correction on condition of setting the resource reservation interval for mode 2 | SHARP Corporation |
R2-2105299 | Correction on security handling for SL-SRB1 | CATT |
R2-2105350 | Remaining issues on sl-MaxTransNum configuration and UE behaviour | vivo |
R2-2105497 | Correction of PQFI terminology in SDAP | Ericsson |
R2-2105586 | Corrections on MCS selection | Huawei, HiSilicon |
R2-2105599 | Clarification on setting the cast type indicator | Huawei, HiSilicon |
R2-2105633 | Handling of the retransmission TB without an associated SL process | Huawei, HiSilicon |
R2-2106213 | Review Report on MAC CRs in AI 6.2.3 | LG Electronics Inc. |
R2-2106490 | Correction on TS 38.321 for mode 2 UE performing re-evaluation check | OPPO |
R2-2106620 | Miscellaneous MAC corrections | LG Electronics Inc. |
R2-2106621 | Correction on mode 2 UE performing re-evaluation check | OPPO |
R2-2106622 | [Draft] LS on resource reselection trigger sl-reselectAfter | Apple |
R2-2106625 | LS on resource reselection trigger sl-reselectAfter | RAN2 |
R2-2106626 | Handling of the retransmission TB without an associated SL process | Huawei, HiSilicon, vivo, Apple, CATT, Intel |
R2-2106638 | Miscellaneous MAC corrections | LG Electronics Inc. |
R2-2106693 | Handling of the retransmission TB without an associated SL process | Huawei, HiSilicon, Vivo, Apple, CATT, Intel |
TDoc | Title | Source |
---|---|---|
R2-2105044 | Correction to 5G support for NB-IOT positioning | Huawei, HiSilicon |
R2-2105048 | Correction to NR stage2 spec for MO-LR | Huawei, HiSilicon |
R2-2105055 | Correction to NRPPa PDU transfer for uplink positioning | Huawei, HiSilicon |
R2-2105967 | Addition of missing parameters for the SRS spatial information | Ericsson |
R2-2106599 | [AT114-e][616][POS] Stage2 Positioning CRs (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104795 | Corrections on the descriptions of SRS-Config | CATT |
R2-2105975 | Correction for the positioning SI offset and clarification on mapping of posSIB to SI | Ericsson, Apple |
TDoc | Title | Source |
---|---|---|
R2-2104796 | Miscellaneous corrections on the field description | CATT, Ericsson, ZTE |
R2-2104842 | 37.355 Draft CR on timestamp reference in NR positioning measurement report | vivo |
R2-2105045 | Correction to the need code for downlink LPP message | Huawei, HiSilicon, Lenovo |
R2-2105046 | Correction to the need code for downlink LPP message-R16 | Huawei, HiSilicon, Lenovo |
R2-2105049 | Correction to PRS configuration | Huawei, HiSilicon |
R2-2105050 | Correction to the uplink LPP message | Huawei, HiSilicon |
R2-2105051 | Correction to DL-PRS capability | Huawei, HiSilicon |
R2-2105054 | Correction to PRS-only TP | Huawei, HiSilicon |
R2-2105056 | Correction to NR-ARFCN of the TRP | Huawei, HiSilicon |
R2-2105962 | Clarification on UE Signaling and measurements of DL-PRS for multiple Positioning Frequency Layers | Ericsson |
R2-2105963 | Correction of Expected RSTD to reflect Optional Presence for Broadcast | Ericsson, Fraunhofer IIS, Fraunhofer HHI |
R2-2105976 | LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap | Ericsson |
R2-2106407 | Clarification on endTransaction field | Samsung |
R2-2106412 | Clarification on endTransaction field | Samsung |
R2-2106465 | Summary for LPP Corrections for Positioning | Ericsson |
R2-2106582 | Correction to DL-PRS capability | Huawei, HiSilicon |
R2-2106584 | [AT114-e][614][POS] Remaining issues on LPP (Ericsson) | Ericsson |
R2-2106589 | Correction to NR-ARFCN of the TRP | Huawei, HiSilicon |
R2-2106591 | Description on timestamp reference in NR positioning measurement report | vivo, Ericsson |
R2-2106631 | Correction to NR-ARFCN of the TRP | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104797 | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | CATT |
R2-2104798 | Corrections on the UE capability of indication on supporting the extension of Positioning SRSresourceID | CATT |
R2-2104799 | Corrections on the UE capability of indication on supporting the extension of Positioning SRSresourceID | CATT |
R2-2105966 | View on Correction for SP Positioning SRS Activation and \tDeactivation MAC CE | Ericsson |
R2-2106583 | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | CATT |
R2-2106585 | Report of [AT114-e][615][POS] UE capability for SRS activation MAC CE (CATT) | CATT |
R2-2106597 | Corrections on the UE capability of indication on supporting the extension of SRS resourceID | CATT |
R2-2106598 | Corrections on the UE capability of indication on supporting the extension of SRSresourceID | CATT |
TDoc | Title | Source |
---|---|---|
R2-2105004 | Transmissions to the source that continue upon DAPS UL switching | Nokia, Nokia Shanghai Bell |
R2-2105016 | Transmission of InDeviceCoexistence, UEAssistanceInformation, MBMSInterestIndication, or SidelinkUEInformation after conditional handover | MediaTek Inc., Ericsson |
R2-2105017 | Transmission of UEAssistanceInformation or SidelinkUEInformationNR after conditional handover | MediaTek Inc., Ericsson, Sharp, LG Electronics, Qualcomm Incorporated |
R2-2105206 | Full configuration for CHO | Google Inc. |
R2-2105500 | CR on T312 handling in DAPS HO | ZTE Corporation, Sanechips |
R2-2105501 | Miscellaneous corrections to 37.340 on mobility enhancement | ZTE Corporation (Rapporteur), Sanechips, Ericsson |
R2-2105502 | CR on configuration release in DAPS HO | ZTE Corporation, Sanechips |
R2-2105608 | Clarification on RLF detection of source PCell | Huawei, HiSilicon |
R2-2105609 | Clarification on RLF detection of source PCell | Huawei, HiSilicon |
R2-2106290 | CR on LCP of the source MAC entity | Samsung |
R2-2106301 | CR on LCP of the source MAC entity | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2105003 | 38.331 CR: Even further revised inability to comply with conditional reconfiguration | Nokia, Nokia Shanghai Bell |
R2-2105325 | 36.331 Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
R2-2105326 | 38.331 Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
R2-2105888 | Conditional reconfigurations and DAPS handover | Ericsson |
R2-2105889 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
R2-2105890 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
R2-2105901 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
R2-2105903 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
R2-2106063 | Clarification regarding inability to comply with conditional reconfiguration | Samsung Telecommunications |
R2-2106153 | Discussion on CHO and SCG configuration | Huawei, HiSilicon |
R2-2106154 | Discussion on MAC reset for CHO | Huawei, HiSilicon |
R2-2106491 | Summary of [AT114-e][210][MOB] LTE/NR mobility corrections (Huawei) | Huawei |
R2-2106494 | 36.331 Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
R2-2106495 | 38.331 Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
R2-2106496 | Clarification regarding inability to comply with conditional reconfiguration | Samsung Telecommunications |
R2-2106508 | Clarification on non-coexistence of CHO and DAPS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104934 | Reconfiguration during DAPS HO | Ericsson, Nokia (Rapporteur) |
R2-2104935 | Reconfiguration during DAPS HO | Ericsson, Nokia (Rapporteur) |
R2-2105005 | Transmissions to the source that continue upon DAPS UL switching in LTE | Nokia, Nokia Shanghai Bell |
R2-2105207 | Correction to DAPS handover | Google Inc. |
R2-2105208 | Correction to DAPS handover | Google Inc. |
R2-2105504 | CR on non-DAPS DRB handling | ZTE Corporation, Sanechips |
R2-2105505 | CR on non-DAPS DRB handling | ZTE Corporation, Sanechips |
R2-2105606 | Clarification on non-coexistence of CHO+DAPS | Huawei, HiSilicon, China Telecom |
R2-2105607 | Correction on reference signal reconfiguration for RLM | Huawei, HiSilicon |
R2-2106138 | Clarification on UE configuration at DAPS fallback | Samsung |
R2-2106139 | Clarification on UE configuration at DAPS fallback | Samsung |
R2-2106141 | Correction on headerCompression field for DAPS DRB | Samsung |
R2-2106509 | Miscellaneous corrections to DAPS handover | Huawei, HiSilicon, Samsung |
R2-2106679 | Miscellaneous corrections to DAPS handover | Ericsson, Nokia (Rapporteur) |
R2-2106680 | Miscellaneous corrections to DAPS handover | Ericsson, Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2105145 | CR on SCG suspend in EN-DC | ZTE Corporation, Sanechips |
R2-2105146 | CR on SCG release in EN-DC | ZTE Corporation, Sanechips |
R2-2105147 | CR on SCG release in EN-DC | ZTE Corporation, Sanechips |
R2-2106018 | Misc corrections for Rel-16 DCCA | Ericsson |
R2-2106019 | Misc corrections for Rel-16 DCCA | Ericsson |
R2-2106333 | Clarification on NR SCG configuration within RRC Resume | MediaTek Inc. |
R2-2106506 | Misc corrections for Rel-16 DCCA | Ericsson |
R2-2106507 | Clarification on NR SCG configuration within RRC Resume | MediaTek Inc., Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2105057 | Corrections on the capability of eutra-IdleInactiveMeasurements | CATT |
R2-2105058 | Corrections on the capability of direct SCG SCell activation | CATT |
R2-2106492 | Summary of [AT114-e][220][DCCA] Miscellaneous DCCA corrections (Ericsson) | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104708 | Further Reply LS on power control for NR-DC (R1-2104018; contact: Apple, vivo) | RAN1 |
R2-2104723 | Reply LS on Introduction of Cell Grouping UE capability for NR-DC (R4-2105333; contact: Qualcomm) | RAN4 |
R2-2104918 | NR-DC cell grouping UE capability signalling | Qualcomm Incorporated |
R2-2104957 | Clarification reconfigurationWithSync IE reception due to fast MCG recovery | OPPO |
R2-2105025 | Cell grouping for NR-DC | Intel Corporation |
R2-2105141 | Options for future-proof NR-DC cell-grouping signaling | Apple Inc |
R2-2105322 | Correction on pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup 38 331 | CATT |
R2-2105665 | Summary of of [Post113bis-e][222][R16 DCCA] Cell grouping for NR-DC (Nokia) | Nokia, Nokia Shanghai Bell |
R2-2105666 | Draft LS to RAN4 on NR DC cell grouping | Nokia, Nokia Shanghai Bell |
R2-2105667 | NR DC Cell Grouping | Nokia, Nokia Shanghai Bell |
R2-2106017 | Cell grouping for NR-DC | Ericsson |
R2-2106022 | Correction on field condition for MCG recovery | Ericsson |
R2-2106062 | UE NR-DC cell grouping capability, future extensibility | Samsung Telecommunications |
R2-2106065 | Clarification on coordination of UE measurement capabilities for CHO and MDT in MRDC | Samsung Telecommunications |
R2-2106162 | Clarification on intra-FR2 NR-DC power control | Huawei, HiSilicon |
R2-2106262 | Furthur discussion on FR2 NR-DC power control | vivo |
R2-2106263 | Correction on FR2 NR-DC power control parameter | vivo, MediaTek Inc |
R2-2106337 | Views on NR-DC cell grouping UE capability | SoftBank Corp. |
R2-2106493 | Summary of [AT114-e][221][ DCCA] Cell grouping CR | Ericsson |
R2-2106512 | Introduction of NR-DC Cell Group capability filtering | Ericsson |
R2-2106513 | Introduction of NR-DC Cell Group capability filtering | Ericsson |
R2-2106514 | Introduction of NR-DC Cell Group capability filtering | Ericsson |
R2-2106515 | NR-DC Cell Group capability filtering | Ericsson |
R2-2106555 | NR-DC Cell Group capability filtering | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2105996 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
R2-2106007 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
R2-2106458 | Merged Corrections to TS 37.320 | CMCC, Nokia |
R2-2106634 | Merged Corrections to TS 37.320 | CMCC, Nokia |
TDoc | Title | Source |
---|---|---|
R2-2104734 | LS Reply on QoS Monitoring for URLLC (S5-211350; contact: Intel) | SA5 |
R2-2105327 | Corrections on accessibility measurements | vivo |
R2-2105328 | Correction on the support for RACH Optimization solutions | vivo |
R2-2106005 | [Draft] Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
R2-2106064 | Inter-node aspects of measurements for MDT in MRDC | Samsung Telecommunications |
TDoc | Title | Source |
---|---|---|
R2-2105329 | Corrections on the range of PER and the description of D2.1 | vivo |
R2-2105998 | On corrections to packet loss rate measurements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2105108 | Clarification on RA reporting | Apple, Samsung, Ericsson |
R2-2105330 | Correction on the mandatory presence of ra-InformationCommon | vivo |
R2-2105424 | On duplicated RPLMN checking for availability indicator in logged measurements | Samsung Electronics Co., Ltd |
R2-2105426 | On duplicated RPLMN checking for availability indicator in logged measurements | Samsung Electronics Co., Ltd |
R2-2105436 | On duplicated RPLMN checking for availability indicator in logged measurements | Samsung Electronics Co., Ltd |
R2-2105841 | Correction to 38331 on CEF report trigger | ZTE Corporation, Sanechips |
R2-2105842 | Correction to 36331 on RLF report | ZTE Corporation, Sanechips |
R2-2105843 | Correction to 36331 on T330 | ZTE Corporation, Sanechips |
R2-2105997 | On WLAN-BT configuration in reportConfigInterRAT in LTE | Ericsson, Huawei |
R2-2106000 | On the lack of PLMN identity check in case of OutOfCoverage event triggered logging | Ericsson |
R2-2106001 | On OutOfCoverage event related measurement logging | Ericsson |
R2-2106002 | On User Consent related aspects | Ericsson |
R2-2106003 | On WLAN-BT configuration in reportConfigInterRAT | Ericsson, Huawei |
R2-2106006 | Configuration of location information for CEF reporting | Ericsson, NTT Docomo |
R2-2106038 | Handling of user contest for location reporting in SONMDT | QUALCOMM Incorporated, Apple |
R2-2106149 | Correction on the release of obtainCommonLocation | Huawei, HiSilicon, Samsung |
R2-2106150 | Discussion on CEF report | Huawei, HiSilicon, Apple, Qualcomm Incorporated |
R2-2106151 | Discussion on the user consent for trace reporting | Huawei, HiSilicon |
R2-2106173 | Configuration of location information for CEF reporting | NTT DOCOMO INC. Ericsson |
R2-2106772 | SON-MDT Changes agreed in RAN2#114 meeting | Ericsson, Huawei |
R2-2106773 | SON-MDT Changes agreed in RAN2#114 meeting | Ericsson, Huawei |
TDoc | Title | Source |
---|---|---|
R2-2104709 | Reply LS on timing of neighbor cell RSS-based measurements (R1-2104033; contact: Qualcomm) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2106285 | Discussion on paging resources determination for eMTC | ZTE Corporation, Sanechips |
R2-2106307 | Clarification on paging DRX cycle | ZTE Corporation, Sanechips |
R2-2106313 | 36304_(R16)_Correction on paging resources determination-Alt1 | ZTE Corporation, Sanechips |
R2-2106320 | 36304_(R16)_Correction on paging resources determination-Alt2 | ZTE Corporation, Sanechips |
R2-2106322 | 36300_(R16)_Clarification on paging in RRC_INACTIVE | ZTE Corporation, Sanechips |
R2-2106326 | draft LS to RAN3 to clarify paging DRX cycle | ZTE Corporation, Sanechips |
R2-2106546 | Report of [AT114-e][401][eMTC R16] Paging DRX cycle (ZTE) | ZTE (email discussion rapporteur) |
R2-2106548 | Report of [Post114-e][401][eMTC R16] Paging DRX cycle in RRC_INACTIVE (ZTE) | ZTE (email discussion rapporteur) |
R2-2106549 | Clarifications on paging DRX cycle | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2106705 | Clarifications on paging DRX cycle | ZTE Corporation, Sanechips, Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2105922 | Clarify systemInfoUnchanged-BR also transmitted in RSS | Qualcomm Incorporated |
R2-2106547 | Report of [AT114-e][402][eMTC R16] systemInfoUnchanged-BR in RSS (Qualcomm) | Qualcomm |
R2-2106550 | Clarify systemInfoUnchanged-BR also transmitted in RSS | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2106214 | Add ack-NACK-NumRepetitions for PUR-Config-NB | ZTE Corporation, Sanechips |
R2-2106277 | MAC clarifications for PUR | ZTE Corporation, Sanechips, MediaTek Inc. |
R2-2106604 | Report of [AT114-e][303][NBIOT/eMTC R16] PUR Corrections (ZTE) | ZTE (email discussion rapporteur) |
R2-2106605 | Add ack-NACK-NumRepetitions for PUR-Config-NB | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2106606 | MAC clarifications for PUR | ZTE Corporation, Sanechips, MediaTek Inc., Qualcomm Incorporated, vivo |
TDoc | Title | Source |
---|---|---|
R2-2105473 | Clarification to Fallback band combination definition | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2105047 | Correction to LTE stage2 spec for MO-LR | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104710 | LS on G-RNTI and G-CS-RNTI for MBS (R1-2104045; contact: CMCC) | RAN1 |
R2-2104758 | Discussion on Multicast Session Activation | CATT, CBN |
R2-2104820 | draft LS about deployment scenarios of NR Broadcast | ZTE, Sanechips |
R2-2104821 | NR Broadcast deployment scenarios | ZTE, Sanechips |
R2-2104875 | Group notification and RACH congestion | Intel Corporation |
R2-2104940 | Group notification and unicast paging for MBS activation | OPPO |
R2-2104947 | MCCH based Group Notification | MediaTek Inc. |
R2-2105008 | Discussion on the remaining issues with MBS group notification | Futurewei |
R2-2105015 | NR Multicast and Broadcast Radio Bearer Architecture aspects | Qualcomm Inc |
R2-2105018 | NR Multicast group paging aspects | Qualcomm Inc |
R2-2105099 | Access Control for the MBS Service Reception | Apple |
R2-2105284 | Consideration on Group Notification | vivo |
R2-2105365 | Discussion on two delivery modes for NR MBS | CHENGDU TD TECH LTD. |
R2-2105513 | Group notification for Delivery mode 1 in NR MBS | Kyocera |
R2-2105550 | Discussion on MBS session activation/reactivation | Spreadtrum Communications |
R2-2105577 | Support of group notification | Huawei, CBN, HiSilicon |
R2-2105655 | Open issues multicast | Ericsson |
R2-2105669 | MBS group notification | Nokia, Nokia Shanghai Bell |
R2-2105726 | Discussion on MBS support on MRDC | Xiaomi Communications |
R2-2105727 | MBS impacts on PDCP | Xiaomi Communications |
R2-2105730 | Discussion on the MBS paging for delivery mode 1 | Xiaomi Communications |
R2-2105756 | Architecture aspects for NR MBS | Ericsson |
R2-2106009 | Protocol Architecture of MRB with Dynamic PTM/PTP Switch | Futurewei |
R2-2106238 | Discussion on MBS L2 Structure | cmcc |
R2-2106248 | 38.300 Running CR for MBS in NR | CMCC |
R2-2106282 | Multicast and Broadcast transport channels | Huawei, CBN, HiSilicon |
R2-2106417 | Discussion on overall architecture of MBS traffic delivery | LG Electronics Deutschland |
R2-2106554 | 38.300 Running CR for MBS in NR | CMCC, Huawei |
R2-2106687 | Reply LS on G-RNTI and G-CS-RNTI for MBS | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104754 | Reliability Improvement for PTM Transmission | CATT |
R2-2104822 | Consideration on MBS reliability guarantee | ZTE, Sanechips |
R2-2104948 | Reliability Mechanism for MBS | MediaTek Inc. |
R2-2104969 | Discussion on HARQ process for MBS data reception | Asia Pacific Telecom, FGI |
R2-2105020 | NR Multicast PTM bearer RLC AM mode operation | Qualcomm Inc, FirstNet,UIC, Kyocera, AT&T |
R2-2105028 | ARQ of PTM with Logical Channel Aggregation | Futurewei |
R2-2105096 | Discussion on the MBS transmission reliabilty | Apple |
R2-2105265 | MBS Reliability | Nokia, Nokia Shanghai Bell |
R2-2105370 | Discussion on reliability for RRC_CONNECTED state | CHENGDU TD TECH LTD. |
R2-2105373 | UE stay in RRC_CONNECTED when no MBS data ongoing | ASUSTeK |
R2-2105514 | Consideration of possible solutions for L2 reliability in NR MBS | Kyocera |
R2-2105596 | PTP_PTM dynamic switch | NEC |
R2-2105757 | Reliability for MBS | Ericsson |
R2-2105764 | Discussion on MRB Architecture | Samsung |
R2-2105795 | Way forward on UP architecture for MBS | InterDigital Inc., ZTE, Sanechips, MediaTek Inc., Huawei, HiSilicon, Ericsson, LG Electronics Inc., Samsung Telecommunications, Fujitsu, Sharp, CATT, CBN, Spreadtrum Communications, Xiaomi Communications, Asia Pacific Telecom co. Ltd., OPPO, Lenovo, Motor |
R2-2105832 | Issues on MBS reliability | Lenovo, Motorola Mobility |
R2-2106008 | L2 ARQ of PTM Transmission with Dynamic PTM/PTP Switch | Futurewei, Qualcomm Inc., Intel, UIC, Kyocera |
R2-2106112 | On RLC mode for PTM transmission | SHARP Corporation |
R2-2106113 | Support of PDCP status reporting for PTM-PTP switching | SHARP Corporation |
R2-2106205 | Activation/Deactivation of PTM | Sharp |
R2-2106239 | Discussion on MBS UP remaining issues | cmcc |
R2-2106334 | MBS L2 architecture for PTP-PTM switching | Intel Corporation |
R2-2106356 | Activation and Deactivation of PTM/PTP leg | Convida Wireless |
R2-2106365 | PTM Reliability Considerations | Convida Wireless |
R2-2106419 | [Pre114-e][001][MBS] Summary 8.1.2.1 MBS Connected mode Reliability (LGE) | LG Electronics Inc. |
R2-2106423 | Discussion on MBS Reliability | LG Electronics Deutschland |
TDoc | Title | Source |
---|---|---|
R2-2105680 | MRB and DRB configuration | Sony |
TDoc | Title | Source |
---|---|---|
R2-2104755 | Open Issues on Mobility with Service Continuity | CATT, CBN |
R2-2104823 | Lossless handover support for NR MBS | ZTE, Sanechips |
R2-2104939 | Service continuity for MBS | OPPO |
R2-2104949 | Mobility and Service continuity for NR Multicast | MediaTek Inc. |
R2-2104995 | Considerations on Mobility and Service Continuity | Samsung |
R2-2105009 | Handling MBS during UE mobility | Futurewei |
R2-2105019 | NR Multicast Broadcast mobility enhancements with service continuity | Qualcomm Inc |
R2-2105097 | Mobility with MBS service continuity | Apple |
R2-2105285 | PTP PTM switch and service continuity | vivo |
R2-2105286 | Service Continuity for Connected UE | vivo |
R2-2105386 | Discussion on mobility with service continuity for NR MBS | CHENGDU TD TECH LTD. |
R2-2105551 | Discussion on service continuity during mobility | Spreadtrum Communications |
R2-2105579 | Service continuity during inter-cell mobility | Huawei, CBN, HiSilicon |
R2-2105796 | PTM/PTP mode switching | InterDigital |
R2-2105833 | Connected Mode Mobility with Service Continuity | Lenovo, Motorola Mobility |
R2-2106240 | Discussion on Mobility with Service Continuity | cmcc |
R2-2106335 | MBS service continuity in mobility | Intel Corporation |
R2-2106345 | Group notification for multicast session | LG Electronics Inc. |
R2-2106352 | MBS Mobility with Service Continuity | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2104756 | Discussion on Group Scheduling | CATT |
R2-2104824 | Discussion on Group scheduling for NR MBS | ZTE, Sanechips |
R2-2104876 | MBS MAC layer and Group scheduling aspects | Intel Corporation |
R2-2104938 | Discussion on group based scheduling for MBS | OPPO |
R2-2104950 | RAN2 aspects of Group Scheduling for NR MBS | MediaTek Inc. |
R2-2104951 | L1 HARQ operation for PTM transmission | MediaTek Inc. |
R2-2104993 | Considerations on Multiplexing & Scheduling Aspects | Samsung |
R2-2105098 | MBS reception in CONNECTED state | Apple |
R2-2105266 | Miscellaneous Aspects of MBS Provisioning | Nokia, Nokia Shanghai Bell |
R2-2105287 | Group Scheduling for MBS | vivo |
R2-2105310 | Dynamic PTM and PTP switching | Shanghai Jiao Tong University |
R2-2105311 | Group Scheduling for NR MBS | Shanghai Jiao Tong University |
R2-2105313 | Deactivation of MBS reception | Shanghai Jiao Tong University |
R2-2105512 | Consideration of dynamic PTM - PTP switching with service continuity for NR MBS | Kyocera |
R2-2105572 | RAN2 aspects of group scheduling | TCL Communication Ltd. |
R2-2105573 | Dynamic PTM PTP Switch | TCL Communication Ltd. |
R2-2105654 | Open issues group scheduling | Ericsson |
R2-2105681 | MBS BWP UE capability and MBS resources | Sony |
R2-2105765 | SDAP/PDCP/RLC Aspects for MBS | Samsung |
R2-2105834 | MBS Group Scheduling Aspects | Lenovo, Motorola Mobility |
R2-2106241 | Discussion on group scheduling for MBS | cmcc |
R2-2106283 | RAN2 aspects of group scheduling | Huawei, CBN, HiSilicon |
R2-2106422 | Discussion on RAN2 aspects of group scheduling and DRX | LG Electronics Deutschland |
R2-2106483 | [Pre114-e][002][MBS] Summary on MBS scheduling | vivo |
TDoc | Title | Source |
---|---|---|
R2-2104757 | Further Discussion on delivery mode 2 | CATT, CBN |
R2-2104825 | Idle and Inactive mode UEs support of NR MBS | ZTE, Sanechips |
R2-2104936 | Discussion on beam sweeping transmission for delivery mode 2 | OPPO |
R2-2104937 | Discussion on MBS interesting indication and service continuity for delivery mode 2 | OPPO |
R2-2104984 | On NR MBS operation in Idle/Inactive mode | Samsung |
R2-2105007 | MCCH Configuration and messaging in MBS delivery mode 2 | Futurewei |
R2-2105013 | NR MBS control signalling aspects for UEs in different RRC states | Qualcomm Inc |
R2-2105288 | Open Issues for Delivery mode 2 | vivo |
R2-2105366 | Performance improvement for delivery mode 2 | TD TECH LTD. |
R2-2105387 | Discussion on delivery mode 2 for NR MBS | CHENGDU TD TECH LTD. |
R2-2105439 | Discussion on Multicast Control Channel Scheduling Configurations for Delivery Mode 2 | TCL Communication Ltd. |
R2-2105511 | Control plane aspects for delivery mode 2 in NR MBS | Kyocera |
R2-2105552 | Discussion issues on delivery mode2 | Spreadtrum Communications |
R2-2105578 | MBS support for delivery mode 2 | Huawei, CBN, HiSilicon |
R2-2105653 | Open issues broadcast | Ericsson |
R2-2105668 | MCCH design details | Nokia, Nokia Shanghai Bell |
R2-2105728 | Service continuity for delivery mode 2 | Xiaomi Communications |
R2-2105729 | Remaining issues of MCCH and MCCH change notification | Xiaomi Communications |
R2-2105835 | Discussion on Idle and Inactive mode UEs | Lenovo, Motorola Mobility |
R2-2105914 | MBS support for RRC_IDLE/INACTIVE | Intel Corporation |
R2-2106114 | L2 architecture for delivery mode 2 | SHARP Corporation |
R2-2106242 | Discussion on delivery mode 2 remaining issues | cmcc |
R2-2106350 | MBS in IDLE/INACTIVE | LG Electronics Inc. |
R2-2106357 | On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
R2-2106361 | NR MBS Configuration Information | Convida Wireless |
R2-2106544 | LS on update for MCCH design | RAN2 |
R2-2106730 | Report of offline discussion: [AT114-e][039][MBS] MCCH and MCCH change notification (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2105062 | TS 37.340 CR for CPA and inter-SN CPC | CATT |
R2-2105986 | Making progress on further MRDC enhancements | Huawei, HiSilicon |
R2-2106505 | [AT114-e][230][R17 DCCA] Making progress (Huawei) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2105279 | Discussion on deactivation of SCG | China Telecom Corporation Ltd. |
R2-2105453 | UE initiated SCG deactivation | NTT DOCOMO INC. |
R2-2105797 | Activation and Deactivation of SCG | InterDigital |
R2-2106039 | Comparison of SCG deactivation solutions | Convida Wireless |
R2-2106106 | Deactivation of SCG | LG Electronics |
R2-2106140 | DC power sharing for deactivated SCG | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2104941 | Summary of AI 8.2.2.2 UE measurements and reporting in deactivated SCG | OPPO |
R2-2104942 | UE measurements and reporting in deactivated SCG | OPPO |
R2-2104944 | Considerations on Considerations on UE measurements and reporting in deactivated SCG | KDDI Corporation |
R2-2105011 | RRM and RLM/RLF handling for deactivated SCG | Futurewei |
R2-2105059 | UE Behavior in Deactivated SCG | CATT |
R2-2105064 | Mobility for deactivated SCG | NTT DOCOMO INC. |
R2-2105139 | TA Maintenance and other UE actions in SCG deactivated state | Apple Inc |
R2-2105158 | Discussion on UE behaviour when SCG is deactivated | ZTE Corporation, Sanechips |
R2-2105441 | UE behaviour in deactivated SCG | NTT DOCOMO INC. |
R2-2105628 | UE behavior when SCG is deactivated | vivo |
R2-2105791 | Further considerations on SCG deactivation | NEC |
R2-2105798 | Measurements and maintenance of UL synch with a deactivated SCG | InterDigital |
R2-2105829 | UE behaviour in deactivated SCG | Lenovo, Motorola Mobility |
R2-2105987 | UE behaviour while the SCG is deactivated | Huawei, HiSilicon |
R2-2106023 | Efficient SCG (de)activation | Ericsson |
R2-2106107 | UE Measurement Aspects in SCG Deactivation | LG Electronics |
R2-2106287 | Discussion for UE behaviour in deactivated SCG | SHARP Corporation |
R2-2106336 | UE behavior during SCG deactivation | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2105010 | Discussion on random access in SCG fast activation | Futurewei |
R2-2105140 | UE initiation of SCG re-activation request | Apple Inc |
R2-2105440 | Activation of deactivated SCG | NTT DOCOMO INC. |
R2-2105548 | Discussion on UE behaviour when SCG is deactivated | Spreadtrum Communications |
R2-2106058 | Remaining aspects concerning SCG activation procedure | Samsung Telecommunications |
R2-2106108 | Activation of SCG | LG Electronics |
R2-2106258 | Discussions on activation of deactivated SCG | CMCC |
R2-2106312 | Discussion on SCG activation | SHARP Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104943 | Discussion on TRS activation for fast SCell activation | OPPO |
R2-2106259 | Considerations for fast MCG link recovery with deactivated SCG | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2104996 | SN-initiated Conditional PSCell Change – clarifications | Nokia, Nokia Shanghai Bell |
R2-2104997 | On CPAC Procedures and Further Functionalities | Nokia, Nokia Shanghai Bell |
R2-2104998 | Discussion on RAN3 LS on CPAC | Nokia, Nokia Shanghai Bell |
R2-2105012 | Discussion on the procedure of SN initiated CPC | Futurewei |
R2-2105060 | Discussion on the remaining issues for SN initiated inter-SN CPC | CATT |
R2-2105061 | Discussion on the inter-node message design | CATT |
R2-2105202 | Remaining issues for source SN configuration update | China Telecommunication |
R2-2105260 | CPAC procedures from network perspective | Qualcomm Incorporated |
R2-2105506 | Further consideration on CPAC | ZTE Corporation, Sanechips |
R2-2105519 | Procedures in CPAC and conventional PSCell change | ITRI |
R2-2105792 | Signaling aspects for SN-initiated CPC | NEC |
R2-2105830 | Discussion on CPAC procedures | Lenovo, Motorola Mobility |
R2-2105897 | Conditional PSCell Addition Change | Ericsson |
R2-2105988 | Inter-node message design (with draft reply LS to RAN3) | Huawei, HiSilicon |
R2-2105989 | Source SN configuration update at or after SN-initiated CPC | Huawei, HiSilicon |
R2-2106059 | CPAC stage 2 flow, progressing remaining issues | Samsung Telecommunications |
R2-2106436 | Source SN configuration update at or after SN-initiated CPC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104914 | Discussion on the configuration of CPAC | vivo |
R2-2105111 | Details in conditional PSCell change and addition | Apple |
R2-2105261 | CPAC procedures from UE perspective | Qualcomm Incorporated |
R2-2105507 | Further discussion on CPAC | ZTE Corporation, Sanechips |
R2-2105898 | UE procedures and signalling for CPAC | Ericsson |
R2-2105990 | Uu RRC message design in CPAC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2104915 | Discussion on CAPC simultaneous with CHO | vivo |
R2-2105262 | Other CPAC aspects | Qualcomm Incorporated |
R2-2105444 | Failure handling of Conditional PSCell Addition | DENSO CORPORATION |
R2-2105518 | SCG RLF recovery in case CPC is configured | ITRI |
R2-2105799 | Coexistence of CHO and CPC | InterDigital, Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips |
R2-2105831 | Miscellaneous issues on CPAC | Lenovo, Motorola Mobility |
R2-2106260 | Combination of CPAC and CHO | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2104764 | Paging Collision Avoidance | OPPO |
R2-2104970 | Paging collision avoidance for MUSIM device | Asia Pacific Telecom, FGI |
R2-2104991 | On Paging Collision Avoidance Solution | Samsung |
R2-2105075 | Definition and solution for paging collision, RRC Inactive, SI change | Lenovo, Motorola Mobility |
R2-2105084 | MUSIM Page Collision Avoidance | Apple |
R2-2105164 | Consideration on the Paging Collision | ZTE Corporation, Sanechips |
R2-2105194 | Further Consideration on Paging Collision Avoidance | CATT |
R2-2105227 | RAN Impacts for paging collision avoidance solutions for Multi-SIM | Nokia, Nokia Shanghai Bells |
R2-2105258 | Options for paging collision avoidance | Qualcomm Incorporated |
R2-2105269 | Paging Collision avoidance | vivo |
R2-2105374 | UE indication of paging collision for Multi-SIM | ASUSTeK |
R2-2105682 | Discussion on paging collision avoidance in Multi-SIM | Sony |
R2-2105899 | Paging Collision Avoidance for Multi-SIM | Charter Communications, Inc |
R2-2105917 | Paging Collision Avoidance Open Issues | Huawei, HiSilicon |
R2-2105978 | Paging collision avoidance | Ericsson |
R2-2106101 | 36.304 change for SA2 agreed NAS based IMSI offset signaling in EPS | Intel Corporation |
R2-2106102 | 5G-S-TMSI re-assignment is “enough” for paging collision avoidance in 5GS | Intel Corporation |
R2-2106109 | Considerations on Paging Collision | LG Electronics |
R2-2106343 | Paging collision avoidance for MUSIM device | MediaTek Inc. |
R2-2106398 | Discussion of the paging collision problem in 5GS | Xiaomi Communications |
R2-2106502 | Summary of [240][MUSIM] UE assistance information of paging collision (vivo) | vivo |
R2-2106517 | Reply LS on UE assistance information for paging collision avoidance | RAN2 |
R2-2106751 | [DRAFT] Reply LS on UE assistance information for paging collision avoidance | vivo |
TDoc | Title | Source |
---|---|---|
R2-2104765 | UE Notification on Network Switching for Multi-SIM | OPPO |
R2-2105085 | MUSIM Network Switching | Apple |
R2-2105086 | MUSIM Band Conflict and RRC Processing Delay Requirements | Apple |
R2-2105165 | Consideration on the Switching Notification Procedure | ZTE Corporation, Sanechips |
R2-2105195 | Further Consideration on Network Switching | CATT |
R2-2105196 | Analysis on UE switching without leaving RRC_CONNECTED state | China Telecommunications |
R2-2105201 | Network switching consideration of Multi-SIM | China Telecommunication |
R2-2105226 | Scenarios and Requirements for switching notification procedure | Nokia, Nokia Shanghai Bells |
R2-2105257 | Network switching procedures for Multi-SIM | Qualcomm Incorporated |
R2-2105270 | Open Issues on Switching Notification | vivo |
R2-2105375 | MUSIM Release Assistance Info for network switching | ASUSTeK |
R2-2105437 | Open issues on network switching for Multi-USIM devices | Samsung Electronics Co., Ltd |
R2-2105442 | Signalling design on short time switching procedure | DENSO CORPORATION |
R2-2105445 | Procedures for MSIM UE notification on network switching | Futurewei Technologies |
R2-2105449 | UE notification procedure for short time switching | NEC |
R2-2105450 | Open issues on network switching procedures | DENSO CORPORATION |
R2-2105683 | Discussion on Busy Indication in Inactive State | Sony |
R2-2105684 | Discussion on Leaving in MultiSIM | Sony |
R2-2105719 | On coordinated switch from NW for MUSIM device | Huawei, HiSilicon |
R2-2105823 | Switching notification and busy indication | Lenovo, Motorola Mobility |
R2-2105900 | Network Switching Solutions for Multi-SIM | Charter Communications, Inc |
R2-2105977 | Discussion on switching mechanisms for a Multi-USIM device | Ericsson |
R2-2106110 | Considerations on SIM Swithcing | LG Electronics |
R2-2106212 | RRC based Switching Notification for leaving RRC_CONNECTED | Sharp |
R2-2106215 | RNAU Handling in MUSIM | Sharp |
R2-2106351 | Network switching behavior for MUSIM device | MediaTek Inc. |
R2-2106399 | Discussion of the UE notification on network switching for multi-SIM | Xiaomi Communications |
R2-2106503 | Summary of [241][MUSIM] LS to SA2/CT1 on network switching for leaving RRC_CONNECTED (Qualcomm) | Qualcomm Incorporated |
R2-2106504 | LS on Network Switching for MUSIM | RAN2 |
R2-2106695 | [AT114-e][241][MUSIM] LS to SA2/CT1 on network switching | Qualcomm Incorporated |
R2-2106696 | [Draft] LS on Network Switching for MUSIM | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2104766 | Paging with Service Indication | OPPO |
R2-2105163 | Further analysis on introduction of paging cause | China Telecommunications |
R2-2105166 | Consideration on the Service Indication | ZTE Corporation, Sanechips |
R2-2105228 | On Service type indication in Paging for EPS And RAN impacts of NAS-BUSY-Indication for RRC-INACTIVE | Nokia, Nokia Shanghai Bells |
R2-2105259 | Paging Prioritization for MUSIM | Qualcomm Incorporated |
R2-2105271 | Including Paging Cause in Paging Message | vivo |
R2-2105420 | Discussion on support of paging cause for Multi-USIM devices | Samsung Electronics Co., Ltd |
R2-2105451 | Discussion on paging service indication for MUSIM | Futurewei Technologies |
R2-2105541 | Discussion on the transmission of paging cause | Spreadtrum Communications |
R2-2105542 | Supporting of Paging Cause Solution detection | Spreadtrum Communications |
R2-2105921 | Discussion on the paging with service indication | Huawei, HiSilicon |
R2-2105979 | Introduction of a Paging cause indication | Ericsson |
R2-2106103 | Solution analysis for supporting Multi-SIM paging cause | Intel Corporation |
R2-2106111 | Support of Paging Cause | LG Electronics |
R2-2106353 | Paging with service indication | MediaTek Inc. |
R2-2106401 | Detailed methods of the paging cause support for MUSIM | Xiaomi Communications |
TDoc | Title | Source |
---|---|---|
R2-2104858 | Updated Rel-17 IAB Workplan | Qualcomm Incorporated, Samsung (WI rapporteurs) |
R2-2105121 | UE L2 Re-ordering Buffer Size Concerns with eIAB Topologies | Apple |
TDoc | Title | Source |
---|---|---|
R2-2104778 | Enhancement of multi-hop latency and congestion mitigation | CATT |
R2-2104860 | Fairness and multi-hop latency in IAB topology | Qualcomm Incorporated |
R2-2104877 | IAB topology-wide fairness, latency and congestion enhancement | Intel Corporation |
R2-2104975 | Discussion on fairness, multi-hop latency and congestion mitigation | ZTE, Sanechips |
R2-2105122 | Latency mitigation in eIAB networks using timing and PDB information | Apple |
R2-2105272 | Discussion on multi-hop latency and LCG extension issues | vivo |
R2-2105395 | Consideration on multi-hop latency in IAB | Fujitsu |
R2-2105452 | Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation | Futurewei Technologies |
R2-2105509 | Possible solutions for topology-wide fairness, multi-hop latency and congestion mitigation in eIAB | Kyocera |
R2-2105517 | An elaboration of required PDB for multi-hop latency | ITRI |
R2-2105685 | Link quality report and number of hops information to improve topology-wide fairness and latency | Sony |
R2-2105686 | Local reouting and cost factor to mitigate congestion | Sony |
R2-2105800 | Timing information for latency enforcement in multi-hop IAB | Interdigital |
R2-2105801 | Latency enforcement, fairness and congestion mitigation in multi-hop IAB | InterDigital |
R2-2105845 | Fairness, latency and congestion – solutions to identified issues | Samsung Electronics GmbH |
R2-2105846 | Enhancements to LCG space and BSR triggering including pre-emptive BSR | Samsung Electronics GmbH |
R2-2105876 | Fairness, latency, congestion | Nokia, Nokia Shanghai Bell |
R2-2106032 | On Topology-wide Fairness, Multi-hop Latency, and Congestion in IAB Network | Ericsson |
R2-2106221 | Enhancements for topology-wide fairness, multi-hop latency and congestion mitigation | Huawei, HiSilicon |
R2-2106303 | Discussion on local rerouting based on HbH flow control indication | ETRI |
R2-2106366 | Discussion on identified issues for topology-wide fairness, multi-hop latency and congestion mitigation | LG Electronics Inc. |
R2-2106372 | Discussion on FFS for local re-routing, LCG extension, and CP-UP separation | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104779 | Inter-donor Topology Adaptation | CATT |
R2-2104780 | CHO and DAPS-like | CATT |
R2-2104781 | RLF Indication and Local Rerouting | CATT |
R2-2104859 | Inter-topology BAP routing | Qualcomm Incorporated |
R2-2104861 | Enhancements to local rerouting and RLF indication in IAB | Qualcomm Incorporated |
R2-2104878 | Intra-donor CHO enhancement for IAB | Intel Corporation |
R2-2104879 | dual-parent IAB-node topology adaptation enhancement | Intel Corporation |
R2-2104880 | RLF indication enhancement and DAPS for single connected IAB-node | Intel Corporation |
R2-2104972 | Discussion on RLF indication and local re-routing | ZTE, Sanechips |
R2-2104973 | Discussion on CP-UP separation and topology redundancy | ZTE, Sanechips |
R2-2104974 | Discussion on CHO and DAPS support in IAB | ZTE, Sanechips |
R2-2105123 | Migration and RLF handling in eIAB Networks | Apple |
R2-2105273 | Discussion on DAPS-like solution and CHO triggers | vivo |
R2-2105274 | Miscellaneous issues on topology adaptation | vivo |
R2-2105275 | On BAP routing of intra-CU local rerouting and inter-donor DC | vivo |
R2-2105376 | Handling Type-2 & Type-3 RLF indication | ASUSTeK |
R2-2105396 | Conditional HO for RLF recovery | Fujitsu |
R2-2105397 | Discussion on the inter-donor topology redundancy | Fujitsu |
R2-2105398 | Discussion on local rerouting | Fujitsu |
R2-2105454 | RAN2 impacts of Rel.17 IAB topology adaptation enhancements | Futurewei Technologies |
R2-2105481 | Multi-parent options | Nokia, Nokia Shanghai Bell |
R2-2105482 | Re-routing ehnancements and RLF indications in IAB | Nokia, Nokia Shanghai Bell |
R2-2105483 | Inter-donor-DU rerouting | Nokia, Nokia Shanghai Bell |
R2-2105510 | Details of topology adaptation enhancements for eIAB | Kyocera |
R2-2105594 | DAPS-like handover and NR DC for IAB | NEC |
R2-2105595 | CHO for IAB | NEC |
R2-2105687 | Topology adaptation enhancements in IAB | Sony |
R2-2105688 | Dual-protocol-stack solution in IAB | Sony |
R2-2105782 | Topology adaptation enhancements | Samsung Electronics GmbH |
R2-2105784 | New triggers for local rerouting | Samsung Electronics GmbH |
R2-2105802 | CHO triggering in IAB | InterDigital |
R2-2105803 | DAPS support in IAB | InterDigital |
R2-2105815 | Discussion on IAB packet rerouting | Lenovo, Motorola Mobility |
R2-2105816 | CHO in IAB system | Lenovo, Motorola Mobility |
R2-2105848 | Discussion on inter-donor DU local re-routing | CANON Research Centre France |
R2-2105861 | Discussion on Inter-donor topology redundancy | CANON Research Centre France |
R2-2105864 | Discussion on RLF indication and local rerouting enhancements | CANON Research Centre France |
R2-2106029 | On IAB Inter-donor Topology Adaptation | Ericsson |
R2-2106030 | On CHO and DAPS for IAB | Ericsson |
R2-2106033 | Remaining Issues Related to CP/UP Separation in IAB Network | Ericsson |
R2-2106278 | Inter-donor-DU rerouting and local rerouting for R17-IAB | Huawei, HiSilicon |
R2-2106279 | Running CR of TS 38.340 for eIAB | Huawei, HiSilicon |
R2-2106280 | Inter-donor topology routing, F1 over NR access link and CHO | Huawei, HiSilicon |
R2-2106298 | CHO and DAPS-like Solution for eIAB | LG Electronics |
R2-2106299 | Resolving issues on BH RLF | LG Electronics |
R2-2106485 | [Pre114-e][003][eIAB] Summary of 8.4.3: Topology Adaptation Enhancements (Nokia) | Nokia |
R2-2106707 | LS on Topology Adaptation enhancements | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104720 | LS on gNB-based propagation delay compensation (R3-211136; contact: Nokia) | RAN3 |
R2-2105867 | Text Proposal of Stage-2 Running CR for Rel-17 IIoT/URLLC Enhancement | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2104729 | LS on Time Synchronization assistance parameters (S2-2103023; contact: Nokia) | SA2 |
R2-2104886 | Pre-compensation at the gNB for RTT and TA based PDC | Intel Corporation |
R2-2104898 | Design for Time Synchronization in Rel-17 | CATT |
R2-2104901 | Propagation Delay Compensation for TSN | Qualcomm Incorporated |
R2-2105255 | Discussion on the Time synchronisation assistance parameters | Huawei, HiSilicon |
R2-2105289 | Discussion on the propagation delay compensation | vivo |
R2-2105307 | Further discussion on time synchronization and PDC | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2105565 | Consideration on the support of time synchronization enhancement | OPPO |
R2-2105672 | On propagation delay compensation | MediaTek Inc. |
R2-2105674 | Determining per Uu Interface Time Sync Error Budget | Ericsson |
R2-2105723 | Discussion on the time synchronization error budget in RAN | Xiaomi Communications |
R2-2105766 | Synchronization and Error Budget | Samsung |
R2-2105825 | Discussion on enabling UE side propagation delay compensation | Lenovo, Motorola Mobility |
R2-2105844 | Propagation Delay Compensation Signaling | CANON Research Centre France |
R2-2105868 | Time Synchronization Signalling Analysis | Nokia, Nokia Shanghai Bell |
R2-2105871 | [Draft] Reply LS on Time Synchronization assistance parameters | Nokia, Nokia Shanghai Bell |
R2-2106249 | Support of time synchronization for TSN based on RAN1 progress | CMCC |
R2-2106323 | Discussion on Propagation Delay Compensation (PDC) | III |
R2-2106324 | Timing synchronization for UE in RRC_INACTIVE state and RRC_IDLE state | TCL Communication Ltd. |
R2-2106433 | Discussion on enhancements for support of time synchronization | LG Electronics Deutschland |
R2-2106557 | [DRAFT] Reply LS on Time Synchronization assistance parameters | Nokia |
R2-2106560 | Reply LS on Time Synchronization assistance parameters | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104899 | Autonomous retransmission on a different CG configuration | CATT |
R2-2104902 | CG Harmonization for Unlicensed Controlled Environment | Qualcomm Incorporated |
R2-2105256 | Remaining issues about uplink enhancements for URLLC in UCE | Huawei, HiSilicon |
R2-2105290 | Remaining issues of harmonizing UL CG enhancements in NR-U and IIoT | vivo |
R2-2105456 | Further details on enhancements for URLLC in UCE | Lenovo, Motorola Mobility |
R2-2105566 | Consideration on URLLC over NR-U | OPPO |
R2-2105675 | Harmonizing UL CG enhancements in NR-U and URLLC | Ericsson |
R2-2105676 | RAN enhancements based on new QoS related parameters | Ericsson |
R2-2105689 | Prioritization of UL transmissions in unlicensed URLLC | Sony |
R2-2105724 | Remaining issues of CG harmonization | Xiaomi Communications |
R2-2105789 | Configured grant mode switching for IIoT/URLLC in unlicensed controlled environments | III |
R2-2105856 | Further Consideration On the URLLC transmission in UCE | ZTE, Sanechips |
R2-2105872 | Remaining Issues on Configured Grant for IIoT in NR-U | Nokia, Nokia Shanghai Bell |
R2-2105952 | Uplink enhancements for URLLC in unlicensed controlled environments | Intel Corporation |
R2-2106226 | Discussion on the remaining issue for uplink enhancements for URLLC in UCE | CMCC |
R2-2106381 | Remaining Issue of Harmonization of CG Transmission | Samsung |
R2-2106395 | Summary of [POST113bis-e][505][R17 IIoT] URLLC in UCE | LG Electronics Inc. |
R2-2106396 | Summary of [POST113bis-e][505][R17 IIoT] URLLC in UCE | LG Electronics Inc. |
R2-2106400 | URLLC on UCE | LG Electronics Inc. |
R2-2106556 | Summary of [POST113bis-e][505][R17 IIoT] URLLC in UCE | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104897 | Summary of Email Discussion 506 – R17 IIOT QoS | CATT |
R2-2104900 | Comparison of the solutions for Survival Time | CATT |
R2-2104903 | RAN Enhancement to support new QoS | Qualcomm Incorporated |
R2-2104980 | Topics on new QoS handling | Fujitsu |
R2-2105114 | Reliability enhancements for CG/SPS | Apple |
R2-2105115 | Further considerations on survival time for new QoS | Apple |
R2-2105312 | Further discussion on enhanced QoS | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2105419 | Further discussion on RAN enhancements based on Survival Time | III |
R2-2105457 | Discussion on the mechanism to guarantee the survival time | Lenovo, Motorola Mobility |
R2-2105567 | Consideration on RAN enhancement based on new QoS | OPPO |
R2-2105604 | Entering and operating in the Survival Time state | Samsung Electronics GmbH |
R2-2105615 | Entering and operating in the Survival Time state | Samsung Electronics GmbH |
R2-2105638 | Entering and operating in the Survival Time state | Samsung Electronics GmbH |
R2-2105725 | Clarification on the survival time | Xiaomi Communications |
R2-2105873 | RAN Enhancement for New QoS Parameters | Nokia, Nokia Shanghai Bell |
R2-2105954 | Discussion on the roles played in the survival time operation | Futurewei Technologies |
R2-2106041 | Discussion on multi-level PERs for survival time handling | Huawei, HiSilicon |
R2-2106044 | Enhancements based on new QoS requirements | InterDigital |
R2-2106066 | RAN2 Enhancements to Support Survival Time | Intel Corporation |
R2-2106227 | Discussion on the RAN support for new QoS parameters | CMCC |
R2-2106328 | Discussion of RAN enhancements based on new QoS | TCL Communication Ltd. |
R2-2106397 | Enhancement for survival time | LG Electronics Inc. |
R2-2106413 | RAN enhancements based on new QoS related parameters | Oy LM Ericsson AB |
R2-2106558 | Summary of [502][URLLC/IIoT] QoS for IIoT (CATT) | CATT |
TDoc | Title | Source |
---|---|---|
R2-2104707 | Reply LS on uplink timing alignment for small data transmissions (R1-2104012; contact: Lenovo) | RAN1 |
R2-2105032 | Runnning MAC CR for small data | Huawei, HiSilicon |
R2-2105639 | Discussion on the spec modeling for Small Data | Huawei, HiSilicon, ZTE Corporation |
R2-2105847 | Discussion on the spec modeling for Small Data | Huawei, HiSilicon, ZTE corporation, Sanechips |
R2-2105877 | Stage-2 running CR Introduction of SDT | Nokia, Nokia Shanghai Bell |
R2-2105927 | RRC Running CR for SDT | ZTE Corporation (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2104760 | Further Discussion on User Plane Aspect for Small Data Transmission | vivo |
R2-2104770 | Discussion on common user plane issues of SDT | OPPO |
R2-2104784 | User Plane Common Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
R2-2104964 | Handling of fallback during a SDT procedure | Asia Pacific Telecom, FGI |
R2-2105280 | Consideration on UP common aspects of SDT | CATT |
R2-2105447 | User plane aspects of SDT | NEC |
R2-2105455 | UP common issues for Small Data Transmissions | Lenovo, Motorola Mobility |
R2-2105597 | Consideration on overall SDT procedure | LG Electronics Inc. |
R2-2105690 | Some aspects of User Plane for SDT in NR | Sony |
R2-2105760 | Common aspects for SDT | Ericsson |
R2-2106043 | User plane aspects of small data transmission | InterDigital |
R2-2106254 | Remaining issues on SDT procedure | CMCC |
R2-2106310 | Remaining untreated proposals from [AT113bis-e][501] UP SDT open issues | LG Electronics Inc. (Rapporteur) |
R2-2106311 | Remaining UP issues in SDT | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104761 | Discussion on RRC-Controlled Small Data Transmission | vivo |
R2-2104771 | Discussion on common control plane issues of SDT | OPPO |
R2-2104785 | Control Plane Common Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
R2-2104881 | Failure and successful handling for an SDT session | Intel Corporation |
R2-2104882 | CP-SDT remaining open issues | Intel Corporation |
R2-2104981 | Handling of T319-like timer | Fujitsu |
R2-2104982 | RAN paging reception and response during SDT | Fujitsu |
R2-2105100 | Power Saving for SDT | Apple |
R2-2105101 | Control plane aspects on the SDT procedure | Apple |
R2-2105102 | Subsequent data transmission for SDT | Apple |
R2-2105281 | Consideration on CP issues | CATT |
R2-2105377 | Beam management in SDT | ASUSTeK |
R2-2105448 | Control plane aspects of SDT | NEC |
R2-2105575 | Control plane common aspects for SDT | Huawei, HiSilicon |
R2-2105691 | Discussion on subsequent SDT in NR, timer handling, and support for SRB1/2 | Sony |
R2-2105720 | Discussion on the support of the RRC-less SDT | Xiaomi Communications, Intel Corporation, ASUSTeK, Fujitsu, MediaTek, Apple, Spreadtrum Communications |
R2-2105721 | Technical details of the RRC-less SDT | Xiaomi Communications, ASUSTeK, Fujitsu, Spreadtrum Communications |
R2-2105810 | Consideration on CP issues for small data transmission | Lenovo, Motorola Mobility |
R2-2105885 | Discussion on open issues of SDT | Qualcomm Incorporated |
R2-2105911 | SDT control plane aspects | Nokia, Nokia Shanghai Bell |
R2-2105928 | Control plane common aspects of SDT | ZTE Corporation, Sanechips |
R2-2106040 | SDT cell re-selection | Convida Wireless |
R2-2106050 | SDT CP and configuration aspects | InterDigital |
R2-2106051 | Untreated proposal from [Post113-e][503] | InterDigital |
R2-2106132 | Discussion on CP aspects of SDT | China Telecomunication Corp. |
R2-2106217 | Beam selection and indication for subsequent SDT | ETRI |
R2-2106255 | Handling of non-SDT data arriving | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2104762 | Report of [Post113bis-e][507][SDT] Resource Configuration Aspects | vivo |
R2-2104763 | Supporting Small Data Transmission via RA Procedure | vivo |
R2-2104772 | Discussion on RACH-based SDT | OPPO |
R2-2104786 | Details of RACH bsaed Small Data Transmission | Samsung Electronics Co., Ltd |
R2-2104883 | RA-SDT remaining open issues | Intel Corporation |
R2-2104965 | PDCCH monitoring in RA-based SDT procedure | Asia Pacific Telecom, FGI |
R2-2105378 | Discussion on PDCCH monitoring for RA-SDT | ASUSTeK |
R2-2105549 | Discussion on RACH-based SDT | Spreadtrum Communications |
R2-2105574 | Small data transmission with RA-based schemes | Huawei, HiSilicon |
R2-2105692 | Discussion on context fetch and anchor relocation | Sony |
R2-2105693 | RACH-based SDT in NR | Sony |
R2-2105758 | RACH based SDT | Ericsson |
R2-2105878 | Details of RACH specific schemes | Nokia, Nokia Shanghai Bell |
R2-2105886 | Discussion on open issues for RACH based SDT | Qualcomm Incorporated |
R2-2105929 | Open issues for RACH based SDT | ZTE Corporation, Sanechips |
R2-2106131 | Considerations on Open issues in RA-SDT | China Telecomunication Corp. |
R2-2106256 | Anchor relocation and context fetch | CMCC |
R2-2106443 | Report of [Post113bis-e][507][SDT] Resource Configuration Aspects | vivo |
R2-2106559 | [Draft] Reply LS to RAN1 on physical layer aspects of small data transmis-sion | vivo |
R2-2106561 | Reply LS to RAN1 on physical layer aspects of small data transmission | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104787 | Details of Configured Grant based Small Data Transmission | Samsung Electronics Co., Ltd |
R2-2104968 | Beam selection and failure handling for CG-SDT | Asia Pacific Telecom, FGI |
R2-2104983 | PDCCH monitoring after SDT-TAT expiry | Fujitsu |
R2-2105031 | Remaining untreated proposals from [POST113-e][504][SDT] CG Open Issues | Huawei, HiSilicon |
R2-2105282 | Analysis and views on CG-SDT | CATT |
R2-2105379 | Beam selection for CG-SDT | ASUSTeK |
R2-2105465 | Aspects specific to CG based SDT | Nokia, Nokia Shanghai Bell |
R2-2105576 | Small data transmission with CG-based scheme | Huawei, HiSilicon |
R2-2105598 | Discussion on CG-SDT open issues | LG Electronics Inc. |
R2-2105694 | CG-based SDT in NR | Sony |
R2-2105722 | Remaining issues of CG SDT | Xiaomi Communications |
R2-2105759 | Details of CG based SDT | Ericsson |
R2-2105811 | Consideration on CG based small data transmission | Lenovo, Motorola Mobility |
R2-2105887 | Discussion on open issues for CG based SDT | Qualcomm Incorporated |
R2-2105930 | Open issues for CG based SDT | ZTE Corporation, Sanechips |
R2-2106012 | Discussion on CG-SDT Request by UE | NEC Telecom MODUS Ltd. |
R2-2106042 | CG-based SDT selection and configuration | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2104837 | Work planning for R17 SL relay | OPPO, CMCC |
R2-2104945 | Running CR on Introduction of Rel-17 Sidelink Relay | MediaTek Inc. |
R2-2106562 | Running CR on Introduction of Rel-17 Sidelink Relay | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104736 | Remaining issues on relay discovery | Qualcomm Incorporated |
R2-2104746 | Leftover Issues on Sidelink Discovery | CATT |
R2-2104869 | Discovery Procedure for sidelink relay | InterDigital |
R2-2104892 | Discussion on remaining issues of NR sidelink relay discovery | OPPO |
R2-2104958 | Remaining issues on Relay discovery procedure | vivo |
R2-2104976 | Discussion on Relay discovery in Sidelink Relay | ZTE, Sanechips |
R2-2105022 | Open aspects on relay discovery | Intel Corporation |
R2-2105342 | Remaining issues for SL relay discovery | Samsung |
R2-2105390 | Discovery resources for sidelink relaying | Kyocera |
R2-2105491 | Left issues for SL discovery | Ericsson |
R2-2105535 | Discussion on Ralay discovery | Spreadtrum Communications |
R2-2105740 | Remaining issues on discovery for sidelink relay | Huawei, HiSilicon |
R2-2105742 | Use of Pre-configuration and collocated neighbour cell carrier | Beijing Xiaomi Mobile Software |
R2-2105807 | Relay Discovery for L2 and L3 relay | Lenovo, Motorola Mobility |
R2-2106266 | Left issues for relay discovery message transmission | LG Electronics Inc. |
R2-2106435 | Consideration on remaining issues of NR sidelink relay discovery | China Telecommunications |
R2-2106437 | Remaining issues on Relay Discovery | MediaTek Inc. |
R2-2106457 | [Pre114-e][602][Relay] Summary on agenda item 8.7.2 on relay discovery (OPPO) | OPPO |
R2-2106586 | Offline discussion 617 | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2104737 | Remaining issues on relay (re)selection | Qualcomm Incorporated |
R2-2104745 | Remaining issues on relay (re)selection | Qualcomm Incorporated |
R2-2104747 | Remain Issues on Relay (Re)selection | CATT |
R2-2104870 | Relay selection and reselection | InterDigital |
R2-2104889 | Open aspects of Relay (re)selection | Intel Corporation |
R2-2104893 | Discussion on remaining issues of NR sidelink relay (re)selection | OPPO |
R2-2104959 | Remaining issues on Relay (re)selection | vivo |
R2-2104971 | Remaining Open Issues on Relay (re-)selection | Fraunhofer HHI, Fraunhofer IIS |
R2-2104977 | Discussion on Relay selection in Sidelink Relay | ZTE, Sanechips |
R2-2105127 | Discussion on remaining issues of relay (re)selection and discovery | Apple |
R2-2105238 | Discussion on some relay (re)selection issues | Nokia, Nokia Shanghai Bell |
R2-2105492 | Aspects for SL relay selection and reselection | Ericsson |
R2-2105496 | [Post113bis-e][602][Relay] Definition of relay load criterion (Ericsson] | Ericsson |
R2-2105515 | Discussion on sidelink relay reselection | SHARP Corporation |
R2-2105536 | Discussion on Ralay selection and reselection | Spreadtrum Communications |
R2-2105695 | Relay (re)selection | Sony |
R2-2105750 | Remote UE use of Relay UE Load Indication | Beijing Xiaomi Mobile Software |
R2-2105790 | Remaining PDB in UE-to-NW and UE-to-UE Relay | Nokia, Nokia Shanghai Bell |
R2-2105808 | Relay (re)selection for L2 and L3 relay | Lenovo, Motorola Mobility |
R2-2106011 | View on definition of relay load criterion | Continental Automotive GmbH |
R2-2106160 | Remaining issues on relay selection and reselection | Huawei, HiSilicon |
R2-2106203 | Use of relay load as a Relay (re)selection criterion | MediaTek Inc. |
R2-2106251 | Remaining issues on AS criteria for relay selection | CMCC |
R2-2106268 | AS layer criteria for relay selection and reselection | LG Electronics Inc. |
R2-2106271 | left L2/L3 common issues for relay selection and reselection | LG Electronics Inc. |
R2-2106344 | Other remaining issues on (re)selection | MediaTek Inc. |
R2-2106470 | [Pre114-e][603][Relay] Summary on agenda item 8.7.3 on relay (re)selection (CATT) | CATT |
R2-2106587 | [AT114-e][618][Relay] Remaining issues on (re)selection | CATT |
TDoc | Title | Source |
---|---|---|
R2-2104742 | Further discussion adaptation layer of L2 U2N relay | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2104738 | Further discussion on control plane procedures of L2 U2N relay | Qualcomm Incorporated |
R2-2104748 | Control Plane Procedures of L2 Relay | CATT |
R2-2104838 | Left issues on RRC procedure for L2 U2N Relay | OPPO |
R2-2104871 | Control Plane Procedures for L2 UE to NW Relays | InterDigital |
R2-2104888 | Control plane procedures for L2N relaying | Intel Corporation |
R2-2104946 | Stage 2 level procedure for Connection Establishment | MediaTek Inc. |
R2-2104960 | Further Discussion on L2 Control Plane Procedures | vivo |
R2-2104978 | Consideration on the control plane procedure of SL relay | ZTE, Sanechips |
R2-2105030 | Open Issues in L2 Relay Control Plane Procedures | Futurewei |
R2-2105074 | Monitoring Paging by a U2N Relay | Lenovo, Motorola Mobility |
R2-2105076 | SI acquisition, CN Registration and RNAU | Lenovo, Motorola Mobility |
R2-2105128 | Discussion on Unified Access Control in Relay UE | Apple |
R2-2105129 | Discussion on RNA Update procedures in L2 UE-to-NW Relay | Apple |
R2-2105130 | Discussion on QoS mechanism for Layer 2 UE-to-NW relay | Apple |
R2-2105343 | On-demand SI request for Remote UE | Samsung |
R2-2105380 | Discussion on on-demand SI acquisition procedure for U2N Relay | ASUSTeK |
R2-2105391 | RRC state transitions and RLF handling in L2 relaying | Kyocera |
R2-2105486 | Connection control on L2 relay | Xiaomi communications |
R2-2105537 | Discussion on control plane procedures for L2 U2N relay | Spreadtrum Communications |
R2-2105678 | Various configuration and QoS management aspects of L2 relaying | Samsung Electronics GmbH |
R2-2105696 | L2 relay control plane procedures | Sony |
R2-2105739 | SIB Handling in Sidelink UE-to-Nwk Relay | Nokia, Nokia Shanghai Bell |
R2-2105773 | Discussion on control plane procedures for L2 sidelink relay | Ericsson |
R2-2105960 | Paging and SI deliveries for L2 relay | ETRI |
R2-2106054 | Discussion on Uu adaptation layer in L2 UE-to-NW relay | Nokia, Nokia Shanghai Bell |
R2-2106161 | Discussion on the CP procedures for L2 Relay | Huawei, HiSilicon |
R2-2106252 | Discussion on control plane procedure | CMCC |
R2-2106273 | L2 relay specific topics related to the control plane procedures | LG Electronics Inc. |
R2-2106293 | Discussion on establishment cause value of relay UE | Xiaomi, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility, Vivo, Apple, ZTE |
R2-2106450 | Discussion on RNA Update procedures in L2 UE-to-NW Relay | Apple |
R2-2106463 | Summary on agenda item 8.7.4.1 on L2 relay control plane | vivo |
R2-2106520 | LS on establishment/resume cause value and UAC on L2 SL Relay | RAN2 |
R2-2106577 | Summary on agenda item 8.7.4.1 on L2 relay control plane | vivo (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2104739 | Service continuity of L2 U2N relay | Qualcomm Incorporated |
R2-2104749 | Service Continuity for L2 U2N Relay | CATT |
R2-2104872 | Service Continuity for L2 UE to NW Relays | InterDigital |
R2-2104891 | Service Continuity support for L2 U2N Relaying | Intel Corporation |
R2-2104894 | Discussion on service continuity in NR sidelink relay | OPPO |
R2-2104961 | Service continuity and Adaptation Layer for L2 SL Relay | vivo |
R2-2104979 | Discussion on the service continuity of SL relay | ZTE, Sanechips |
R2-2105029 | Open Issues in Switches between Direct and Indirect Paths | Futurewei |
R2-2105344 | Service continuity support for SL remote UE | Samsung |
R2-2105741 | Discussion on service continuity and adaptation layer for L2 UE to NW Relay | Huawei, HiSilicon |
R2-2105774 | Discussion on service continuity for L2 sidelink relay | Ericsson |
R2-2106253 | Service continuity for L2 relay | CMCC |
R2-2106481 | [Pre114-e][605][Relay] Summary on agenda item 8.7.4.2 on L2 relay service continuity (Samsung) | Samsung |
R2-2106578 | Report of [AT114-e][605][Relay] Summary on AI 8.7.4.2 on L2 relay service continuity | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2104743 | Draft LS to SA2 on slice grouping and slice priority | Qualcomm Incorporated |
R2-2104744 | Discussion on SMBR enforcement | Qualcomm Incorporated |
R2-2105239 | Discussion on Uplink SMBR enforcement | Nokia, Nokia Shanghai Bell |
R2-2105942 | SMBR enforcement in RAN | Ericsson |
R2-2106155 | Discussion on SMBR enforcement | Huawei, HiSilicon |
R2-2106223 | Discussion on SMBR enforcement in RAN | CMCC |
R2-2106373 | UL SMBR enforcement | Samsung |
R2-2106374 | UL SMBR enforcement | Samsung |
R2-2106418 | SMBR enforcement in RAN | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104740 | Further discussion on slice specific cell reselection | Qualcomm Incorporated |
R2-2104782 | Considerations on slice based cell reselection | Beijing Xiaomi Software Tech |
R2-2104791 | Discussion on slice aware cell reselection | ZTE corporation, Sanechips |
R2-2104873 | Frequency prioritization for slice specific cell (re)selection | Intel Corporation |
R2-2105109 | Discussion on slice based cell reselection | Apple |
R2-2105203 | Discussion on frequency priority for inter-frequency cell reselection | China Telecommunication |
R2-2105212 | Further discussion on slice-based cell reselection | Lenovo, Motorola Mobility |
R2-2105240 | Slice specific cell reselection | Nokia, Nokia Shanghai Bell |
R2-2105331 | Discussion on slice-based reselection | vivo |
R2-2105438 | Discussion on slice based cell reselection | Samsung Electronics Co., Ltd |
R2-2105533 | Discussion on slice based cell reselection | Spreadtrum Communications |
R2-2105568 | Consideration on slice-specific cell reselection | OPPO |
R2-2105630 | Cell (re)selection for RAN slicing | FGI |
R2-2105631 | Cell (re)selection for RAN slicing | Asia Pacific Telecom, FGI |
R2-2105697 | Slice based Cell Reselection and intended slice | Sony |
R2-2105738 | Considerations on contents of slice related cell selection info | KDDI Corporation |
R2-2105880 | Discussion on slice aware cell reselection | LG Electronics UK |
R2-2105943 | Cell re-selection enhancements for slicing | Ericsson |
R2-2106013 | Slice-based cell/frequency prioritization | NEC Telecom MODUS Ltd. |
R2-2106087 | Consideration on slice-based cell reselection | SHARP Corporation |
R2-2106156 | Discussion on slice based cell reselection under network control | Huawei, HiSilicon |
R2-2106175 | Discussion on Slice-based Cell Reselection | CATT |
R2-2106224 | Discussion on slice based cell reselection | CMCC |
R2-2106501 | Summary of [AT114-e][250][Slicing] Usage of slice priorities for cell reselection (Lenovo) | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2104741 | Further discussion on slice specific RACH | Qualcomm Incorporated |
R2-2104789 | Considerations on slice based RACH configuration | Beijing Xiaomi Software Tech |
R2-2104792 | Slice specific RACH resources and RACH prioritization | ZTE corporation, Sanechips |
R2-2104874 | Further considerations of slice based RACH | Intel Corporation |
R2-2105110 | Discussion on slice based RACH | Apple |
R2-2105213 | Further discussion on slice-based PRACH configuration | Lenovo, Motorola Mobility |
R2-2105332 | Discussion on slice-based RACH configuration | vivo |
R2-2105345 | Slice specific RACH configuration | Samsung |
R2-2105475 | Slice-specific RACH prioritisation | Nokia, Nokia Shanghai Bell |
R2-2105534 | Consideration on slice based RACH configuration | Spreadtrum Communications |
R2-2105569 | Consideration on slice-specific RACH | OPPO |
R2-2105944 | RACH for RAN slicing enhancement | Ericsson |
R2-2106014 | RAN Slicing remaining RACH issues | NEC Telecom MODUS Ltd. |
R2-2106157 | Discussion on slice based RACH configuration | Huawei, HiSilicon |
R2-2106184 | Analysis on slice based RACH configuration | CATT |
R2-2106225 | Discussion on slice based RACH configuration | CMCC |
R2-2106375 | Discussion on slice-specific RACH operation | LG electronics |
TDoc | Title | Source |
---|---|---|
R2-2104773 | Paging subgroup assignment | Qualcomm Incorporated |
R2-2104783 | Paging Enhancements_UE Grouping | Samsung Electronics Co., Ltd |
R2-2104807 | Discussion on grouping-based paging | OPPO |
R2-2104909 | UE sub-grouping for paging enhancement | vivo |
R2-2105021 | Further considerations of network assigned subgrouping | Intel Corporation |
R2-2105087 | NR UE Power Save IDLE/INACTIVE Paging Grouping Schemes | Apple |
R2-2105283 | UE subgrouping schemes with paging enhancement | CATT |
R2-2105293 | UE Paging Subgroup Assignment for Power Saving | MediaTek Inc. |
R2-2105295 | Discussion on idle_inactive_mode UE power saving | Xiaomi Communications |
R2-2105411 | Details on paging subgrouping determination and indication | Nokia, Nokia Shanghai Bell |
R2-2105656 | Grouping methods for Paging | Ericsson |
R2-2105718 | Discussion on the control node for UE grouping | Huawei, HiSilicon |
R2-2105736 | PEI monitoring in NR: CN and System level impacts | VODAFONE Group Plc |
R2-2105809 | Consideration on Idle/inactive-mode UE power saving | Lenovo, Motorola Mobility |
R2-2105855 | Further Consideration on UE Grouping | ZTE, Sanechips |
R2-2105956 | Discussion on UE grouping control entity | Futurewei Technologies |
R2-2106257 | Considerations on paging subgrouping | CMCC |
R2-2106349 | UE subgrouping for paging enhancement | LG Electronics Inc. |
R2-2106552 | LS on Paging Subgrouping | RAN2 |
R2-2106666 | Report of [AT114-e][025][ePowSav] Subgrouping network architecture | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2105088 | NR UE Power Save TRS/CSI-RS Signaling for IDLE/INACTIVE UEs | Apple |
TDoc | Title | Source |
---|---|---|
R2-2104703 | LS to ITU-T on extraterritorial use of MCC+MNC for satellite networks (C1-212539; contact: Qualcomm) | CT1 |
R2-2104806 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
R2-2104962 | NTN Stage2 running CR 38.300 | THALES |
R2-2104963 | NR-NTN-solutions work plan | THALES |
R2-2105953 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
R2-2106049 | Stage 3 NTN running CR for 38.321 - RAN2#114 | InterDigital |
R2-2106539 | NTN Stage2 running CR 38.300 | THALES |
R2-2106540 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
R2-2106541 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
R2-2106542 | Stage-3 running CR for TS 38.321 for Rel-17 NTN | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2106048 | MAC open issues in NTN - RAN2#114 | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2104812 | Discussion on RACH in NTN | OPPO |
R2-2104966 | Discussion on UE-specific TA report | Asia Pacific Telecom, FGI |
R2-2105118 | On reporting UE specific TA pre-compensation during RACH in NTN | Apple |
R2-2105199 | Discussion of RACH in NTN | China Telecommunication |
R2-2105381 | Discussion on LCH-based RA type selection | ASUSTeK |
R2-2105382 | BSR over 2-step RA | ASUSTeK |
R2-2105412 | On RACH aspects for NTN | Nokia, Nokia Shanghai Bell |
R2-2105817 | Considerations on new criteria for RA type selection | Lenovo, Motorola Mobility |
R2-2106015 | NTN Remaining RACH issues | NEC Telecom MODUS Ltd. |
R2-2106090 | Reporting information about UE specific TA pre-compensation | Ericsson. Apple |
R2-2106197 | Discussion on RACH and TA report aspects | LG Electronics Inc. |
R2-2106362 | Discussion On TA report | Xiaomi, Saumsung, Qualcomm Incorporated, Asia Pacific Telecom, Huawei, HiSilicon, OPPO, Lenovo, Motorola Mobility |
R2-2106385 | NTN MAC enhancements | Convida Wireless |
TDoc | Title | Source |
---|---|---|
R2-2104813 | Discussion on UL HARQ operation in NTN | OPPO |
R2-2104850 | About HARQ for NTN | THALES |
R2-2104851 | Discussion on HARQ Aspects and UL Scheduling Enhancement in NTN | CATT |
R2-2104967 | HARQ retransmission schemes in NTN | Asia Pacific Telecom, FGI |
R2-2105119 | Other MAC aspects for NR NTN | Apple |
R2-2105249 | Round trip delay offset for configured grant timers | MediaTek Inc. |
R2-2105250 | On disabling uplink HARQ retransmission and associated LCP impacts | MediaTek Inc. |
R2-2105413 | On LCP and DRX impact for NTN | Nokia, Nokia Shanghai Bell |
R2-2105414 | Discussion on UL scheduling enhancements for NTN | Nokia, Nokia Shanghai Bell |
R2-2105431 | LCP restriction for an UL HARQ process | Qualcomm Incorporated, Xiaomi, Huawei, HiSilicon, Samsung |
R2-2105488 | DRX impact of disabling HARQ feedback | PANASONIC R&D Center Germany |
R2-2105489 | DRX impact of disabling HARQ feedback | PANASONIC R&D Center Germany |
R2-2105490 | DRX impact of disabling HARQ feedback | PANASONIC R&D Center Germany |
R2-2105498 | Co-existence issue of BSR over CG and BSR over 2-step RACH | PANASONIC R&D Center Germany |
R2-2105528 | LCP enhancement for NTN | Spreadtrum Communications |
R2-2105529 | Discussion on extending of SR-prohibitTimer | Spreadtrum Communications |
R2-2105612 | Discussion on remaining MAC issues in NTN | Huawei, HiSilicon |
R2-2105698 | Other MAC enhancements in NTN | Sony |
R2-2105836 | Considerations on LCP in NTN | ZTE Corporation, Sanechips |
R2-2106047 | UL HARQ RTT timer in NTN | InterDigital, MediaTek, Samsung |
R2-2106068 | Remaining Issues on HARQ Stalling, RNTI Capacity, UL Scheduling, LCP, and UL HARQ Behaviors for an NTN | Samsung Research America |
R2-2106089 | On DRX, LCP, timing, HARQ, SR/BSR, and CG and SPS | Ericsson |
R2-2106201 | Discussion on other MAC aspects | LG Electronics Inc. |
R2-2106245 | Left Issues for HARQ operation in NTN | CMCC |
R2-2106444 | UL HARQ RTT timer in NTN | InterDigital, MediaTek, Samsung, ZTE |
R2-2106488 | [Pre114-e][103][NTN] Summary 8.10.2.2 - Other MAC aspects | InterDigital |
R2-2106523 | Report of [AT114-e][103][NTN] Other MAC aspects: Phase 2 | InterDigital |
R2-2106532 | Report of [AT114-e][103][NTN] Other MAC aspects: Phase 2 | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2104731 | LS on PDB for new 5QI (S2-2103552; contact: Ericsson) | SA2 |
R2-2104814 | Discussion on PDB for new 5QI | OPPO |
R2-2105837 | Considerations on RLC/PDCP aspects | ZTE Corporation, Sanechips |
R2-2106016 | RLC and PDCP timers extension | NEC Telecom MODUS Ltd. |
R2-2106055 | On RLC t-Reassembly for NTN | Sequans Communications |
R2-2106088 | On RLC and PDCP for NTNs | Ericsson |
R2-2106091 | DRAFT Reply LS on PDB for new 5QI | Ericsson |
R2-2106524 | DRAFT Reply LS on PDB for new 5QI | Ericsson |
R2-2106533 | Reply LS on PDB for new 5QI | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104826 | Signalling Solution for Feeder Link Switching of NTN | VODAFONE Group Plc |
R2-2104852 | Discussion on TAC update in NTN | CATT |
R2-2105117 | Satellite cell ID mapping to earth fixed locations for efficient cell selection and cell reselection in NTN | Apple |
R2-2105252 | On Soft-switch based Tracking Area Updates in NR-NTN | MediaTek Inc. |
R2-2105432 | Hard and soft TAC update timing | Qualcomm Incorporated |
R2-2105530 | Discussion on TAC updating in NTN | Spreadtrum Communications |
R2-2105571 | Discussion on TAC aspects for NTN | Beijing Xiaomi Electronics |
R2-2105610 | Discussion on decoupled cell ID | Huawei, HiSilicon |
R2-2105611 | Discussion on remaining issues on soft TAU | Huawei, HiSilicon |
R2-2106069 | Tracking Area Management using Virtual Tracking Areas in an NTN | Samsung Research America, Apple, Rakuten Mobile |
R2-2106070 | Enhancements for the Soft TAC Update for Earth-moving Beams in an NTN | Samsung Research America |
R2-2106525 | Report on [Offline 107] TAC update | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2104805 | Report of [POST113bis-e][101][NTN] cell reselection | ZTE corporation, Sanechips |
R2-2104815 | Discussion on idle/inactive mode procedures in NTN | OPPO |
R2-2104857 | Leftover issues on IDLE and inactive mode | CATT |
R2-2105116 | Way forward for NTN Ephemeris Discussions for pre-compensation, idle mode and connected mode procedures | Apple |
R2-2105251 | On Cell-Reselection in NR-NTN | MediaTek Inc. |
R2-2105487 | Discussion on IDLE issues | Xiaomi communications |
R2-2105531 | Issue on cell selection and reselection in NTN | Spreadtrum Communications |
R2-2105699 | Idle mode enhancement in NTN | Sony |
R2-2105786 | Cell reselection based on time and location condition | LG Electronics Inc. |
R2-2105818 | Considerations on ephemeris provision for NTN | Lenovo, Motorola Mobility |
R2-2106171 | NTN Idle/Inactive mode cell re-selection | ITL |
R2-2106231 | Discussion on GNSS tracking for cell (re)selection and ephemeris division&provision | CMCC |
R2-2106387 | NTN type and scenario indication | Convida Wireless |
R2-2106392 | NTN Cell (re)selection enhancements | Convida Wireless |
TDoc | Title | Source |
---|---|---|
R2-2104816 | Discussion on mobility management for connected mode UE in NTN | OPPO |
R2-2104853 | Discussion on connected mode in NTN | CATT |
R2-2104999 | Further thoughts on connected mode mobility in NTN | Nokia, Nokia Shanghai Bell |
R2-2105000 | Further views on SMTC configurations for NTN | Nokia, Nokia Shanghai Bell |
R2-2105006 | Service continuity between NTN and TN | Hughes/EchoStar, Thales, BT Plc, Turkcell, Vodafone, ESA, Inmarsat |
R2-2105120 | On connected mode issues for NR NTN | Apple |
R2-2105253 | Mobility for NTN-TN scenarios | MediaTek Inc. |
R2-2105383 | Location-based measurement report | ASUSTeK |
R2-2105384 | Discussion on measurement event triggering in NTN | ASUSTeK |
R2-2105389 | Discussion on UE feedback based SMTC and GAPS measurement configuration | Rakuten Mobile, Inc |
R2-2105433 | Open issues in CHO | Qualcomm Incorporated |
R2-2105434 | SMTC and MG enhancements | Qualcomm Incorporated |
R2-2105460 | Discussion on connected mode aspects for NTN | Xiaomi Communications |
R2-2105613 | Discussion on remaining issues for CHO in NTN | Huawei, HiSilicon |
R2-2105614 | Discussion on service continuity between NTN and TN | Huawei, HiSilicon |
R2-2105700 | Signaling storm during HOs and Timer based trigger details | Sony |
R2-2105701 | Cell coverage spillage over multiple countries issue in NTN | Sony |
R2-2105702 | SMTC enhancement in NTN | Sony |
R2-2105787 | Further considerations on NTN CHO | LG Electronics Inc. |
R2-2105819 | UE assistance for measurement gap and SMTC configuration in NTN | Lenovo, Motorola Mobility |
R2-2105820 | NTN specific CHO trigger condition | Lenovo, Motorola Mobility |
R2-2105923 | Further consideration on CHO in NTN | ZTE corporation, Sanechips |
R2-2105936 | Connected mode aspects for NTN | Ericsson |
R2-2106024 | Further discussion on CHO in NTN | NEC Telecom MODUS Ltd. |
R2-2106045 | Location-based CHO in NTN | InterDigital |
R2-2106046 | Time-based CHO for soft feeder-link switch | InterDigital |
R2-2106071 | Handover Enhancements and Power-saving Neighbor Search for an NTN | Samsung Research America |
R2-2106232 | SMTC and measurement Gap configuration for NTN | CMCC |
R2-2106233 | Signaling issues resolution for connected mobility | CMCC |
R2-2106234 | Discussion on NTN-TN mobility | CMCC |
R2-2106347 | Measurement window enhancements for NTN cell | LG Electronics Inc. |
R2-2106386 | SMTC and MG configuration for NTN | Convida Wireless |
R2-2106388 | NTN ANR enhancements | Convida Wireless |
R2-2106489 | Feature summary for 8.10.3.3 | Ericsson |
R2-2106526 | Feature summary for 8.10.3.3 | Ericsson |
R2-2106534 | [Offline 104] CHO aspects and service continuity - second round | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104730 | Reply to LS on UE location aspects in NTN (S2-2103550; contact: Thales) | SA2 |
R2-2104854 | Discussion on reply LSs on UE location aspects in NTN | CATT |
R2-2105435 | UE positioning methods for NTN | Qualcomm Incorporated |
R2-2105558 | Discussion on location service for NTN | Xiaomi |
R2-2105924 | Understanding on the UE location aspects in NTN | ZTE corporation, Sanechips |
R2-2105935 | NTN location reporting aspects | Ericsson |
R2-2106072 | Area Management in an NTN | Samsung Research America and Thales |
R2-2106527 | [AT114-e][108][NTN] UE location aspects (CATT) | CATT |
R2-2106535 | [Offline 108] UE locacation aspects - second round | CATT |
R2-2106538 | draft New LS on UE location aspects in NTN | CATT |
R2-2106543 | New LS on UE location aspects in NTN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104713 | LS on DL-AoD angle calculation enhancement (R1-2104089; contact: Ericsson) | RAN1 |
R2-2104921 | Clarification on work scope of Rel-17 positioning enhancement | Intel Corporation |
R2-2106092 | Clarification on work scope of Rel-17 positioning enhancement | Intel Corporation |
R2-2106096 | Support of angle calculation enhancement for DL-AoD | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104844 | Enhancement for positioning latency | vivo |
R2-2104845 | Discuss Scheduling Location in Advance to reduce Latency | vivo |
R2-2104922 | Scheduled location time based latency reduction | Intel Corporation |
R2-2105037 | Discussion on positioning latency | Huawei, HiSilicon |
R2-2105142 | Discussion on scheduled location time for latency reduction | CATT |
R2-2105219 | Discussion on positioning latency | Huawei, HiSilicon |
R2-2105302 | Discussion on Enhancements for Latency Reduction | InterDigital, Inc. |
R2-2105523 | Further consideration of positioning latency enhancments | OPPO |
R2-2105557 | Discussion on UE capability regarding positioning latency | BEIJING SAMSUNG TELECOM R&D |
R2-2105560 | Positioning enhancements on latency reduction | Xiaomi |
R2-2105600 | Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
R2-2105968 | For latency reduction Need of QoS info in gNB and positioning capability \tstorage | Ericsson |
R2-2105973 | draft LS to different groups | Ericsson |
R2-2106082 | Scheduling Location in Advance to Reduce Latency | Qualcomm Incorporated |
R2-2106093 | Scheduled location time based latency reduction | Intel Corporation |
R2-2106261 | Discussion on latency reduction for positioning | CMCC |
R2-2106367 | Latency reduction via configured grant for positioning | Samsung Electronics |
R2-2106368 | Discussion on the scheduled location time | Samsung Electronics |
R2-2106376 | posSI request enhancement for latency reduction | Samsung R&D Institute UK |
R2-2106426 | Discussion on positioning latency reduction | ZTE Corporation, Sanechips |
R2-2106449 | Summary of AI 8.11.2 Latency enhancements | CATT |
TDoc | Title | Source |
---|---|---|
R2-2104802 | Positioning for UEs in RRC_INACTIVE state | CATT |
R2-2104846 | Discussion on open issues of positioning support in RRC_INACTIVE state | vivo |
R2-2104847 | Discussion on UL positioning support in RRC_INACTIVE state | vivo |
R2-2104923 | Support of Positioning in RRC_INACTIVE | Intel Corporation, Apple, OPPO, Xiaomi, InterDigital Inc., Spreadtrum, CATT, Huawei, HiSilicon, ZTE, vivo, Convida Wireless, Nokia |
R2-2105034 | Discussion on positioning in RRC INACTIVE state | Huawei, HiSilicon |
R2-2105041 | Draft LS to SA2 on INACTIVE positioning | Huawei, HiSilicon |
R2-2105216 | Discussion on positioning in RRC INACTIVE state | Huawei, HiSilicon |
R2-2105222 | Draft LS to SA2 on INACTIVE positioning | Huawei, HiSilicon |
R2-2105303 | Discussion on Positioning in RRC INACTIVE state | InterDigital, Inc. |
R2-2105304 | Discussion on Positioning Information reporting using SDT | InterDigital, Inc. |
R2-2105339 | Supporting positioning in RRC_INACTIVE state | OPPO |
R2-2105340 | Discussion on UL Positioning methods in RRC_INACTIVE state | OPPO |
R2-2105546 | Discussion on positioning in RRC_INACTIVE state | Spreadtrum Communications |
R2-2105561 | Discussion on positioning for UEs in RRC Inactive | Xiaomi |
R2-2105601 | On Positioning in RRC_INACTIVE state | Lenovo, Motorola Mobility |
R2-2105703 | Considerations on positioning RRC Inactive | Sony |
R2-2105710 | Considerations on Assistance data for positioning in RRC_INACTIVE mode. | Fraunhofer IIS; Fraunhofer HHI |
R2-2105971 | On Maximizing benefits of SDT | Ericsson |
R2-2106083 | Positioning of UEs in RRC Inactive State | Qualcomm Incorporated |
R2-2106094 | Support of Positioning in RRC_INACTIVE | Intel Corporation |
R2-2106104 | Support of UL and RAT independent positioning in RRC_INACTIVE | Intel Corporation |
R2-2106369 | Support of positioning result reporting in Inactive state | Samsung Electronics |
R2-2106408 | Discussion on UL positioning support in RRC_INACTIVE state | vivo |
R2-2106409 | Discussion on open issues of positioning support in RRC_INACTIVE state | vivo |
R2-2106429 | Discussion on DL INACTIVE positioning | ZTE Corporation, Sanechips |
R2-2106430 | Discussion on MG for INACTIVE positioning | ZTE Corporation, Sanechips |
R2-2106434 | Support of Positioning in RRC_INACTIVE | Intel Corporation, Apple, OPPO, Xiaomi, InterDigital Inc., Spreadtrum, CATT, Huawei, HiSilicon, ZTE, vivo, Convida Wireless, Nokia |
R2-2106447 | Summary of AI 8.11.3 for INACTIVE POS | Huawei, HiSilicon |
R2-2106551 | LS to RAN1 on UL positioning in RRC_INACTIVE | RAN2 |
R2-2106576 | Summary of AI 8.11.3 for INACTIVE POS | Huawei, HiSilicon |
R2-2106588 | [AT114-e][620][POS] RRC state exposure for positioning (Huawei) | Huawei, HiSilicon |
R2-2106590 | Summary of [AT114-e][621][POS] LS to RAN1 on UL positioning in RRC_INACTIVE (Intel) | Intel |
TDoc | Title | Source |
---|---|---|
R2-2104803 | Further discussion on on-demand PRS | CATT |
R2-2104848 | Discuss on-demand PRS | vivo |
R2-2104924 | Support of on-demand PRS request | Intel Corporation |
R2-2105035 | Discussion on on-demand PRS | Huawei, HiSilicon |
R2-2105040 | Stage-2 TP for on-demand PRS | Huawei, HiSilicon |
R2-2105134 | Discussion on UE-initiated on-demand PRS | Apple |
R2-2105217 | Discussion on on-demand PRS | Huawei, HiSilicon |
R2-2105221 | Stage-2 TP for on-demand PRS | Huawei, HiSilicon |
R2-2105305 | Discussion on procedures for On-demand PRS for DL-based positioning | InterDigital, Inc. |
R2-2105306 | Discussion on procedure for On-demand PRS for DL+UL based positioning | InterDigital, Inc. |
R2-2105338 | Discussion on on-demand DL-PRS | OPPO |
R2-2105547 | Discussion on on-demand PRS | Spreadtrum Communications |
R2-2105562 | Positioning enhancement to on-demand DL PRS | Xiaomi |
R2-2105603 | On-Demand DL-PRS Support | Lenovo, Motorola Mobility |
R2-2105704 | Considerations on positioning PRS On-demand | Sony |
R2-2105734 | On-demand PRS | Fraunhofer IIS, Fraunhofer HHI |
R2-2105969 | On demand PRS | Ericsson |
R2-2106084 | On-Demand DL-PRS | Qualcomm Incorporated |
R2-2106095 | Support of on-demand PRS request | Intel Corporation |
R2-2106354 | UE feedback for on-demand PRS | Nokia, Nokia Shanghai Bell |
R2-2106355 | Pre-configuration and initiation of on-demand PRS associated with QoS/radio conditions | Nokia, Nokia Shanghai Bell |
R2-2106370 | Support of on-demand DL PRS for positioning efficiency | Samsung Electronics |
R2-2106379 | On-demand DL PRS transmission and reception | Convida Wireless |
R2-2106424 | Discussion on restriction of on demand PRS | ZTE Corporation, Sanechips |
R2-2106425 | Discussion on on demand PRS | ZTE Corporation, Sanechips |
R2-2106467 | Summary on agenda item 8.11.4 on on-demand PRS | Qualcomm Incorporated |
R2-2106594 | LS on On-demand PRS | RAN2 |
R2-2106595 | LS to RAN1 on parameters for on-demand PRS | RAN2 |
R2-2106607 | LS to RAN1 on parameters for on-demand PRS | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104843 | Discussion on methodologies for network-assisted and UE-assisted integrity | vivo |
R2-2105036 | Discussion on network-assisted and UE-assisted integrity | Huawei, HiSilicon |
R2-2105218 | Discussion on network-assisted and UE-assisted integrity | Huawei, HiSilicon |
R2-2105308 | Discussion on procedures and signalling for GNSS positioning integrity | InterDigital, Inc. |
R2-2105524 | Discussion on supporting positioning integrity in RAN | OPPO |
R2-2105563 | Discussion on signalling and procedures for GNSS positioning integrity | Xiaomi |
R2-2105735 | UE-aided detection of threat to GNSS systems and assistance data signaling | Fraunhofer IIS; Fraunhofer HHI; Ericsson |
R2-2105874 | Positioning Integrity Support in LPP | Nokia, Nokia Shanghai Bell |
R2-2105970 | On GNSS Integrity | Ericsson |
R2-2105985 | Guiding framework on integrity concepts for A-GNSS positioning | ESA |
R2-2106085 | Considerations on GNSS positioning integrity support | Qualcomm Incorporated |
R2-2106105 | Proposals on GNSS integrity assistance information | Swift Navigation |
R2-2106371 | Consideration on the signalling design for Positioning Integrity | Samsung Electronics |
R2-2106427 | Discussion on positioning integrity transportation | ZTE Corporation, Sanechips |
R2-2106428 | Discussion on positioning integrity data calculation and LS to RTCM | ZTE Corporation, Sanechips |
R2-2106445 | Positioning Integrity Support in LPP | Nokia, Nokia Shanghai Bell |
R2-2106453 | [Pre114-e][609][POS] Summary on agenda item 8.11.5 on GNSS integrity (Nokia) | Nokia |
R2-2106596 | LS to RTCM on GNSS integrity assistance data | RAN2 |
R2-2106600 | Email discussion on LS to RTCM for GNSS integrity | ESA |
TDoc | Title | Source |
---|---|---|
R2-2105143 | Introduction of B2a signal in BDS system in A-GNSS | CATT, CAICT |
R2-2105972 | Impacts of NavIC in NR RRC | Ericsson |
R2-2106581 | [AT114-e][613][POS] Rel-17 A-GNSS enhancements(CATT/Ericsson) | CATT, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104804 | Discussion on LS on DL-AoD angle calculation enhancement | CATT |
R2-2104849 | Discussion on DL-AoD angle calculation enhancement | vivo |
R2-2104925 | Support of angle calculation enhancement for DL-AoD | Intel Corporation |
R2-2105038 | Discussion on positioning enhancement | Huawei, HiSilicon |
R2-2105220 | Discussion on positioning enhancement | Huawei, HiSilicon |
R2-2105309 | Discussion on Positioning during Mobility in RRC INACTIVE | InterDigital, Inc. |
R2-2105974 | On High Accuracy Aspects | Ericsson |
R2-2106086 | Signalling and Procedures for supporting Reference Location Devices | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2104702 | Reply LS on Unified Access Control (UAC) for RedCap (C1-212395; contact: vivo) | CT1 |
R2-2105233 | Revised WI work plan for RedCap | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104774 | Definition and constrained use of RedCap UEs | Qualcomm Incorporated |
R2-2104808 | Discussion on constraining of reduced capabilities | OPPO |
R2-2104910 | UE type definition and constraining for RedCap UEs | vivo, Guangdong Genius |
R2-2104927 | RedCap UE capability and constraining of reduced capabilities | Intel Corporation |
R2-2105136 | Resolution on some basic mandatory capabilities for RedCap UEs for faster product development | Apple Inc |
R2-2105160 | Define and Constrain Reduced Capability for RedCap | ZTE Corporation, Sanechips |
R2-2105234 | Definition of RedCap UE and first look on capability signaling | Ericsson |
R2-2105319 | On Redcap UE capabilities and type | CATT |
R2-2105471 | Capability for RedCap UEs and its early indication | Samsung |
R2-2105539 | Discussion on L2 buffer size reduction for Redcap UE | Spreadtrum Communications |
R2-2105634 | Definition of RedCap UE type and reduced capabilities | Huawei, HiSilicon |
R2-2105882 | How to prevent RedCap UEs from using capabilities not intended for RedCap Ues | LG Electronics UK |
R2-2105910 | On RedCap UE capabilities | Nokia, Nokia Shanghai Bell |
R2-2106053 | Constraint of RedCap UE to intended use cases | InterDigital |
R2-2106098 | RedCap UE capability and constraining of reduced capabilities | Intel Corporation |
R2-2106230 | Discussion on the definition and constraining of reduced capabilities | CMCC |
R2-2106276 | The capability and the constrain of RedCap UE | China Telecommunications |
R2-2106462 | Summary 8.12.2.1 - Definition of RedCap UE and reduced capabilities (Intel) | Intel Corporation (UK) Ltd |
R2-2106521 | Summary of [AT114-e][105][RedCap] Definition of RedCap UE and reduced capabilities (Intel) | Intel Corporation |
R2-2106528 | [Offline 105] Definition of RedCap UE and reduced capabilities - second round | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104775 | Access and camping restrictions for RedCap UEs | Qualcomm Incorporated |
R2-2104777 | Discussion on early identification and SI indication | CAICT |
R2-2104790 | NR-REDCAP identification and SI indication | THALES |
R2-2104809 | Discussion on RedCap UE’s access control | OPPO |
R2-2104911 | Identification and access restrictions for RedCap UEs | vivo, Guangdong Genius |
R2-2104928 | Early identification and camping restrictions for RedCap UE | Intel Corporation |
R2-2105014 | Methods for barring and for capability reporting | Sierra Wireless, S.A. |
R2-2105071 | Discussion on UAC for Redcap devices | Xiaomi Communications |
R2-2105072 | Discussion on Identification and UE access restrictions for Redcap devices | Xiaomi Communications |
R2-2105137 | Power-saving aspects from cell access and camping of RedCap UEs | Apple Inc |
R2-2105161 | Identification and Access Restriction for RedCap | ZTE Corporation, Sanechips |
R2-2105235 | Early indication & access restriction for RedCap UEs | Ericsson |
R2-2105320 | Early Identification and camping restrictions for Redcap UEs | CATT |
R2-2105399 | Camping restrictions of RedCap UE | Fujitsu |
R2-2105443 | Camping restriction and cell selection criterion | DENSO CORPORATION |
R2-2105472 | Access control for RedCap UEs | Samsung |
R2-2105540 | Discussion on early indication design for Redcap UE | Spreadtrum Communications |
R2-2105635 | Identification and access restriction of RedCap UE | Huawei, HiSilicon |
R2-2105793 | Early identification and SI indication | NEC |
R2-2105814 | Cell barring for REDCAP UEs | Lenovo, Motorola Mobility |
R2-2105879 | Access for REDCAP UE | Nokia, Nokia Shanghai Bell |
R2-2105883 | Identification and access restrictions of RedCap Ues | LG Electronics UK |
R2-2105957 | Discussion on access and camping restrictions for RedCap UEs | Futurewei Technologies |
R2-2106052 | Identification and restriction of RedCap UE | InterDigital |
R2-2106099 | Early identification and camping restrictions for RedCap UE | Intel Corporation |
R2-2106243 | Access control for RedCap UEs | cmcc |
R2-2106244 | Discussion on early identification | cmcc |
R2-2106274 | Early identification and camping restrictions of RedCap UE | China Telecommunications |
R2-2106487 | [Pre114-e][106][RedCap] Summary 8.12.2.2 - Identification and access restrictions | Huawei, HiSilicon |
R2-2106522 | Summary of [AT114-e][106][RedCap] Identification and access restrictions | Huawei, HiSilicon |
R2-2106529 | [Offline 106] Identification and access restrictions - second round | Huawei, HiSilicon |
R2-2106536 | LS on the coordination between gNBs on the supporting of RedCap Ues | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104810 | Discussion on eDRX for RedCap UEs | OPPO |
R2-2104912 | Discussion on eDRX for RedCap UEs | vivo, Guangdong Genius |
R2-2104929 | Leftover issues for eDRX | Intel Corporation |
R2-2105070 | Discussion on e-DRX for Redcap Devices | Xiaomi Communications |
R2-2105135 | RedCap UE power-saving with 2.56 DRX cycle | Apple Inc, FaceBook Inc, MediaTek Inc |
R2-2105162 | On eDRX for RedCap | ZTE Corporation, Sanechips |
R2-2105236 | PTW configuration and minimum cycle length for eDRX | Ericsson |
R2-2105321 | Discussion on eDRX for NR RRC Inactive and Idle | CATT |
R2-2105464 | Open issues on eDRX cycles | DENSO CORPORATION |
R2-2105636 | eDRX for RedCap UE | Huawei, HiSilicon |
R2-2105671 | Remaining issues for eDRX | MediaTek Inc. |
R2-2105813 | Consideration on eDRX for RedCap UE | Lenovo, Motorola Mobility |
R2-2105869 | eDRX for REDCAP | Nokia, Nokia Shanghai Bell |
R2-2105881 | Support for eDRXs for RRC Inactive and Idle | LG Electronics UK |
R2-2106100 | Leftover issues for eDRX | Intel Corporation |
R2-2106530 | Summary of [AT114-e][110][REDCAP] eDRX aspects (Ericsson) | Ericsson |
R2-2106537 | LS on lower bound for eDRX cycle length | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104776 | RRM measurement relaxations for stationary UEs | Qualcomm Incorporated |
R2-2104811 | Discussion on RRM relax for RedCap UEs | OPPO |
R2-2104913 | RRM relaxation for neighboring cell for RedCap UEs | vivo, Guangdong Genius |
R2-2104926 | RRM measurement relaxation criteria for RedCap devices | Intel Corporation |
R2-2105138 | Confined Mobility impact on RRM Relaxation | Apple Inc |
R2-2105159 | RRM relaxation for RedCap UEs | ZTE Corporation, Sanechips |
R2-2105229 | RRM Relaxation for RedCap UE | NTT DOCOMO INC. |
R2-2105237 | Triggering conditions for Rel-17 RRM relaxation | Ericsson |
R2-2105246 | RRM Relaxation | Ericsson |
R2-2105296 | Discussion on RRM relaxations for RedCap UE | Xiaomi Communications |
R2-2105418 | Summary of [Post103bis-e][102][REDCAP] RRM relaxations (Qualcomm) | Qualcomm Wireless GmbH |
R2-2105521 | RRM relaxation in RRC_CONNECTED for RedCap UEs | SHARP Corporation |
R2-2105637 | RRM measurement relaxation for RedCap UE | Huawei, HiSilicon |
R2-2105705 | Redcap relaxed measurements and number of beams | Sony |
R2-2105706 | RedCap Relaxed measurements, stationary definition | Sony |
R2-2105788 | RRM relaxation for stationary RedCap Ues | LG Electronics Inc. |
R2-2105812 | RRM relaxation for stationary UE with reduced capability | Lenovo, Motorola Mobility |
R2-2105909 | On RRM relaxations for REDCAP | Nokia, Nokia Shanghai Bell |
R2-2105959 | Discussion on R17 stationarity criterion and not-at-cell-edge criterion for RedCap UEs | Futurewei Technologies |
R2-2106097 | RRM measurement relaxation criteria for RedCap devices | Intel Corporation |
R2-2106229 | Discussion on the RRM relaxation for RedCap Ues | CMCC |
R2-2106272 | RRM relaxation of RedCap UE | China Telecommunications |
R2-2106403 | RRM relaxation criteria in RRC_Idle/Inactive | Samsung |
R2-2106404 | RRM relaxation criteria in RRC_Connected | Samsung |
R2-2106531 | [Offline 111] RRM relaxation criteria in idle/inactive | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2104930 | Further Discussion on CHO and DAPS Aspects | CATT |
R2-2105197 | Further discussion on SON of CHO | China Telecommunication |
R2-2105198 | Views on the left issues related to SON of DAPS | China Telecommunication |
R2-2105333 | Discussion on CHO and DAPS enhancements | vivo |
R2-2105446 | Discussion on signalling aspects of successful handover report | NEC |
R2-2105476 | Further clarifications on MRO | Nokia, Nokia Shanghai Bell |
R2-2105522 | Further consideration of SON of HO related aspects | OPPO |
R2-2105804 | SON Enhancements for CHO | Lenovo, Motorola Mobility |
R2-2105805 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility |
R2-2105806 | SON Enhancement for NR-U | Lenovo, Motorola Mobility |
R2-2105838 | Remaining issues on HO related SON aspects | ZTE Corporation, Sanechips |
R2-2105862 | Discussion on handover related SON aspects | Huawei, HiSilicon |
R2-2106010 | HO related SON changes | QUALCOMM Incorporated |
R2-2106025 | Handover-related SON aspects | Ericsson |
R2-2106060 | Remaining handover SON aspects, also covering multiple events | Samsung Telecommunications |
R2-2106134 | Discussion on RLF report for DAPS | SHARP |
R2-2106136 | Successful HO report in DAPS | SHARP |
R2-2106235 | SON Enhancement for CHO, DAPS and Successful HO Report | CMCC |
R2-2106384 | Further considerations on HO related SON issues | LG Electronics Deutschland |
R2-2106484 | [Pre114-e][801][SON/MDT] Summary on agenda item 8.13.2.1 Handover related SON aspects (Ericsson) | Ericsson |
R2-2106637 | Summary of AI 8.13.2.1 Handover related SON aspects | Ericsson |
R2-2106690 | [Offline 801][SON/MDT] Handover related SON aspects (Ericsson) | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104931 | Further Discussion on RACH Report for 2-step RACH | CATT |
R2-2105334 | Discussion on signalling and content of 2-stepRA report | vivo |
R2-2105466 | Discussion on 2-step RACH reporting in SON | OPPO |
R2-2105477 | Remaining Issues and New Aspects in 2-step NR UE Report | Nokia, Nokia Shanghai Bell |
R2-2105839 | Remaining issues on RA related enhancements | ZTE Corporation, Sanechips |
R2-2105863 | Discussion on 2 step RA related SON aspects | Huawei, HiSilicon |
R2-2106026 | 2-Step RA information for SON purposes | Ericsson |
R2-2106036 | On logging of on-demand SI information | QUALCOMM Incorporated |
R2-2106133 | Discussion on RA information for 2-step RA | SHARP |
R2-2106236 | SON Enhancement for 2-step RA | CMCC |
R2-2106480 | Summary on agenda item 8.13.2.2 2-step ?RA related SON aspects | CATT |
TDoc | Title | Source |
---|---|---|
R2-2106185 | SON Enhancements for 2SRA, Successful HO Report and Others | Samsung |
R2-2106237 | Further consideration on UL-DL coverage mismatch | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2104932 | Consideration on MDT Enhancements for On-demand SI | CATT |
R2-2105335 | Discussion on Logged MDT configuration | vivo |
R2-2105478 | Logged MDT and other enhancements | Nokia, Nokia Shanghai Bell |
R2-2105616 | Consideration of enhancements for logged MDT | OPPO |
R2-2105625 | Consideration of enhancements for logged MDT | OPPO |
R2-2105840 | Remaining issues on logged MDT | ZTE Corporation, Sanechips |
R2-2105884 | Discussion on FFS issues | LG Electronics UK |
R2-2106004 | On logged MDT related enhancements | Ericsson |
R2-2106037 | Logged measurement Enhancements | QUALCOMM Incorporated |
R2-2106057 | R17 Logged MDT issues (on overwrite, IRAT/ MR-DC, logging non camping freqs, IDC and OSI) | Samsung Telecommunications |
R2-2106152 | Discussion on logged MDT enhancements | Huawei, HiSilicon |
R2-2106482 | Summary on agenda item 8.13.3.2 Logged MDT enhancements | Huawei |
R2-2106678 | Summary of [AT114e][802][SON/MDT] Reporting on demand SI ?related information (CATT)? | CATT |
TDoc | Title | Source |
---|---|---|
R2-2105895 | Running RRC CR for QoE measurements | Ericsson |
R2-2106683 | Running RRC CR for QoE measurements | Ericsson |
R2-2106684 | Running stage-2 CR for QoE measurements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104994 | QoE confiugration and reporting | Qualcomm Incorporated |
R2-2105214 | Further discussion on QoE measurement collection in NR standalone | Lenovo, Motorola Mobility |
R2-2105336 | Discussion on QoE measurement configuration | vivo |
R2-2105479 | QoE configuration and general ascpects | Nokia, Nokia Shanghai Bell |
R2-2105526 | Discussion on QoE measurement collection in NR | OPPO |
R2-2105580 | Discussion on QoE measurement configuration and reporting | Huawei, HiSilicon |
R2-2105893 | Configuration and reporting of QoE measurements | Ericsson |
R2-2106061 | Harmonised general framework for QoE measurements | Samsung Telecommunications |
R2-2106167 | Discussion on NR QoE configuration | CATT |
R2-2106220 | Further discussion on configuration and reporting | CMCC |
R2-2106348 | QoE measurement configuration | LG Electronics Inc. |
R2-2106402 | Issues for NR QoE measurement | Samsung |
R2-2106432 | Discussion on NR QoE configuration | ZTE Corporation, Sanechips |
R2-2106653 | Configuration Reporting General | Qualcomm |
R2-2106654 | QoE configuration and reporting related issues | Qualcomm |
R2-2106776 | QoE configuration and reporting related issues | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104992 | QoE pause and resume handling | Qualcomm Incorporated |
R2-2105215 | QoE report handling during RAN overload | Lenovo, Motorola Mobility |
R2-2105337 | Discussion on start and stop of QoE measurement | vivo |
R2-2105525 | Discussion on QoE measurement pausing and resuming | OPPO |
R2-2105581 | QoE measurement handling at RAN overload | Huawei, HiSilicon |
R2-2105646 | Discussion on NR QoE | China Unicom |
R2-2105894 | Pause and resume of QoE measurements | Ericsson |
R2-2105920 | QoE reporting control | Nokia, Nokia Shanghai Bell |
R2-2106159 | Discussion on QoE collection start and stop | CATT |
R2-2106222 | Further discussion on start and stop | CMCC |
R2-2106346 | Stop and start for QoE measurement reporting | LG Electronics Inc. |
R2-2106431 | Discussion on pause/resume NR QoE reporting | ZTE Corporation, Sanechips |
R2-2106661 | Report from email discussion [AT114-e][027][QoE] Start and Stop (Lenovo) | Lenovo |
R2-2106761 | Report from email discussion [AT114-e][027][QoE] Start and Stop (Lenovo) | Lenovo |
R2-2106762 | Draft LS on QoE report handling at QoE pause | Lenovo |
R2-2106775 | LS on QoE report handling at QoE pause | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104750 | Leftover Issues on DRX for Sidelink Unicast | CATT |
R2-2104751 | DRX Design for Sidelink Groupcast and Broadcast | CATT |
R2-2104752 | [AT113bis-e][707][V2X/SL] Uu DRX Impact to Support SL | CATT |
R2-2104769 | Discussion on network involvement for SL related DRX | OPPO |
R2-2104835 | Discussion on DRX configuration and DRX timers | OPPO |
R2-2104836 | Left issues on SL DRX RTT timer | OPPO, Intel, Xiaomi communications |
R2-2104841 | Summary of [POST113-e][704] TX UE centric or RX UE centric DRX configuration determination (OPPO) | OPPO |
R2-2104865 | Reviised Summary of [POST113-e][703][V2X/SL] Details of Timer (InterDigital) | InterDigital |
R2-2104866 | Open Issues on SL DRX | InterDigital |
R2-2104867 | On TX Centric vs RX Centric Approaches for DRX Configuration Determination | InterDigital, Apple, Huawei |
R2-2105023 | Further discussion on SL DRX operation | Intel Corporation |
R2-2105024 | On DRX wake-up time alignment | Intel Corporation |
R2-2105073 | DRX Configuration for UC BC GC and its interaction with Sensing | Lenovo, Motorola Mobility |
R2-2105077 | Discussion on SL DRX configuration | ZTE Corporation, Sanechips |
R2-2105078 | Discussion on SL DRX timer | ZTE Corporation, Sanechips |
R2-2105083 | Consideration on the sidelink DRX for unicast | Huawei, HiSilicon |
R2-2105131 | Discussion on RX-centric and Tx-centric in SL unicast DRX | Apple, InterDigtal Inc. |
R2-2105132 | Discussion on remaining issues of SL DRX | Apple |
R2-2105248 | NR SL DRX | Fraunhofer IIS, Fraunhofer HHI |
R2-2105277 | Discussion on co-existence with UEs not supporting SL DRX | SHARP Corporation |
R2-2105278 | Discussion on SL DRX inactivity timer | SHARP Corporation |
R2-2105297 | Further discussion on Sidelink DRX | LG Electronics France |
R2-2105351 | SL DRX Configuration Impact on RAN1 and RAN2 | vivo |
R2-2105352 | Left issues on SL DRX | vivo |
R2-2105385 | Discussion on active time regarding Sidelink DRX | ASUSTeK |
R2-2105400 | Discussion on HARQ RTT and Retransmission Timer for SL DRX | Fujitsu |
R2-2105401 | Alignment of sidelink DRX active time | Fujitsu |
R2-2105458 | Coordination between Uu DRX and SL DRX | Lenovo, Motorola Mobility |
R2-2105480 | Discussion on sidelink DRX configuration | Xiaomi communications |
R2-2105484 | DRX alignment between TX and RX UE | Xiaomi communications |
R2-2105493 | Remaining aspects of SL DRX | Ericsson |
R2-2105495 | summary offline 706 | Ericsson |
R2-2105532 | Remaining issues on DRX Timers for SL | Spreadtrum Communications |
R2-2105553 | Consideration on sidelink DRX for broadcast and groupcast | Huawei, HiSilicon |
R2-2105593 | Discussion on SL communication impact on Uu DRX | Huawei, HiSilicon |
R2-2105707 | Proposals for Sidelink DRX | Sony |
R2-2105733 | Geolocation for Sidelink DRX | Nokia, Nokia Shanghai Bell, Fujitsu, Fraunhofer IIS, Fraunhofer HHI |
R2-2105902 | Discussion on Directional SL DRX for Unicast | Qualcomm Finland RFFE Oy |
R2-2105904 | Discussion on SL DRX configuration for Groupcast & Broadcast | Qualcomm Finland RFFE Oy |
R2-2105906 | Discussion on SL DRX Timers and Others | Qualcomm Finland RFFE Oy |
R2-2105912 | [AT113bis-e][708][V2X/SL] DRX configuration for SL CG and BG | ZTE |
R2-2105958 | Further Issues on Sidelink Traffic Pattern for SL DRX Configuration | Nokia, Nokia Shanghai Bell |
R2-2106056 | On the deciding entity of SL DRX configuration | Nokia, Nokia Shanghai Bell |
R2-2106073 | Coordination between DL DRX and SL DRX | Samsung Research America |
R2-2106074 | SL DRX operation for groupcast/broadcast | Samsung Research America |
R2-2106172 | SL DRX enabled UE Mode 2 operation | ITL |
R2-2106202 | Remaining issues in which UE decides sidelink DRX configurations | LGE, InterDigital, Huawei, ASUSTeK, Apple |
R2-2106204 | Consideration on SL DRX operation | LG Electronics Inc. |
R2-2106363 | SL DRX Granularity Considerations | Convida Wireless |
R2-2106364 | SL DRX Configuration: TX Centric or RX Centric | Convida Wireless |
R2-2106438 | On detailed SL DRX model | MediaTek Inc. |
R2-2106439 | On SL DRX timer operation | MediaTek Inc. |
R2-2106623 | LS on time gap information in SCI | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104868 | Resource Allocation for eSL | InterDigital |
R2-2105079 | Discussion on inter-UE coordination | ZTE Corporation, Sanechips |
R2-2105133 | Discussion on resource allocation enhacenmens | Apple |
R2-2105353 | Discussion on inter-UE coordination for sidelink mode2 | vivo |
R2-2105402 | Dual-mode Configuration and Selection for NR Sidelink | Fujitsu |
R2-2105467 | Power efficient resource allocation and Inter-UE coordination | LG Electronics France |
R2-2105485 | Resource allocation enhancement impact in RAN2 | Xiaomi communications |
R2-2105499 | Inter-UE Coordination for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
R2-2105508 | Power Reduction for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
R2-2105538 | Discussion on resource allocation enhancement for NR sidelink | Spreadtrum Communications |
R2-2105708 | Discusison on Sidelink sensing | Sony |
R2-2105775 | General principles for resource allocation enhacements for SL mode 2 | Ericsson |
R2-2105824 | Discussion on sidelink resource allocation enhancements | Lenovo, Motorola Mobility |
R2-2106067 | Resource Allocation Enhancements for Reduced Power Consumption and Enhanced Reliability | Intel Corporation |
R2-2106075 | Resource allocation enhancements | Samsung Research America |
R2-2106358 | On Resource Allocation Mode 2 Enhancement for NR Sidelink | Convida Wireless |
R2-2106440 | Transmission of assistance information for Mode 2 enhancement | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104753 | Impacts of SL DRX on Other Procedures | CATT |
R2-2105494 | Interaction between partial sensing and DRX | Ericsson |
R2-2106441 | On SL sync search optimization | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2104704 | LS on limited service availability of an SNPN (C1-212601; contact: Nokia) | CT1 |
R2-2104728 | Reply LS on support of PWS over SNPN (S2-2102963; contact: Qualcomm) | SA2 |
R2-2105241 | RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN | Nokia, China Telecom (Rapporteurs) |
R2-2105242 | Draft Stage 2 CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
R2-2105243 | Proposed reply for LS on limited service availability of an SNPN (C1-21212601/R2-2104704) | Nokia, Nokia Shanghai Bell |
R2-2106553 | Draft Stage 2 CR: Non-Public Network enhancements | Nokia, Nokia Shanghai Bell |
R2-2106766 | [DRAFT] Reply LS on limited service availability of an SNPN | Nokia |
R2-2106777 | Reply LS on limited service availability of an SNPN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104767 | Support SNPN with subscription or credentials by a separate entity | OPPO |
R2-2105125 | Additional considerations for access of SNPN with credentials from a different entity | Apple |
R2-2105167 | Consideration on the Separate Entity Supporting | ZTE Corporation, Sanechips |
R2-2105192 | Further Consideration on Subscription or Credentials by CH | CATT |
R2-2105200 | Consideration on GIN related issues | China Telecommunication |
R2-2105244 | Discussion on GINs from RAN2 perspective | Nokia, Nokia Shanghai Bell |
R2-2105291 | Remaining issues on supporting SNPN with subscription or credentials by a separate entity | vivo |
R2-2105409 | SNPN access with different entity credentials | Qualcomm Incorporated |
R2-2105570 | Accessing SNPN with credentials owned by a credentials holder | Huawei, HiSilicon |
R2-2105632 | Cell (re)selection for Rel-17 NPN enhancements | Asia Pacific Telecom, FGI |
R2-2105670 | RAN2 impact to support SNPN with credentials by a separate entity | MediaTek Inc. |
R2-2105915 | Support of credentials owned by third party entities in SNPN | Intel Corporation |
R2-2106034 | SNPN access using external credentials | Ericsson |
R2-2106199 | On Supporting Visited SNPN with Credentials | Samsung |
R2-2106246 | Left Issues on Supporting SNPN with Credentials by a Separate Entity | CMCC |
R2-2106296 | Resolving issues for access with external CH | LG Electronics |
R2-2106659 | SNPN and subscription or credentials by a separate entity | China Telecom |
TDoc | Title | Source |
---|---|---|
R2-2104768 | Support UE onboarding and provisioning for NPN | OPPO |
R2-2105124 | Additional considerations for UE on-boarding and provisioning for NPN | Apple |
R2-2105168 | Consideration on the Onboarding and Provisioning for NPN | ZTE Corporation, Sanechips |
R2-2105193 | Further Discussion on UE Onboarding and Provisioning for NPN | CATT |
R2-2105245 | Onboarding related considerations | Nokia, Nokia Shanghai Bell |
R2-2105292 | Remaining issues on supporting UE onboarding and provisioning for NPN | vivo |
R2-2105410 | UE onboarding and provisioning | Qualcomm Incorporated |
R2-2105554 | UE onboarding and remote provisioning for SNPN | Huawei, HiSilicon |
R2-2105709 | Discuss the need of UAC for UE on-boarding | Sony |
R2-2105916 | Support UE Onboarding and provisioning for NPN | Intel Corporation |
R2-2106035 | UE onboarding | Ericsson |
R2-2106200 | On Supporting Onboarding SNPN | Samsung |
R2-2106228 | Discussion the left issues to support UE on-boarding and remote provisioning | CMCC |
R2-2106297 | Resolving issues for UE onboarding and provisioning for NPN | LG Electronics |
R2-2106545 | LS on Group IDs for Network selection (GINs) | RAN2 |
R2-2106662 | UE onboarding and provisioning for NPN | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104712 | LS on TCI states indication for PDCCH (R1-2104064; contact: Intel) | RAN1 |
R2-2104719 | LS on Timing Assumption for Inter-Cell DL Measurement (R1-2104142; contact: Samsung) | RAN1 |
R2-2106645 | Report of [AT114-e][035][feMIMO] TCI states indication for PDCCH | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2104908 | Discussion on L1 L2-Centric Inter-Cell Mobility | vivo |
R2-2104988 | Multi-cell support for multi-TRPand L1 mobility | Nokia, Nokia Shanghai Bell |
R2-2105026 | Further aspects on L1/L2-Centric Inter-Cell Mobility | Intel Corporation |
R2-2105027 | Enhanced MAC CE for PDCCH in multi-TRP deployment | Intel Corporation |
R2-2105033 | Discussion on L1/2 centric mobility | OPPO |
R2-2105103 | L1/L2-centric inter-cell mobility | Apple |
R2-2105294 | Procedures of L1L2-Centric Inter-Cell Mobility | MediaTek Inc. |
R2-2105341 | Discussion on RAN2 specification impacts of TRP-specific BFR | OPPO |
R2-2105354 | L1/L2 Mobility Overview | Qualcomm Incorporated |
R2-2105355 | Responses to RAN1 LS for L1/L2 Mobility | Qualcomm Incorporated |
R2-2105617 | On Scenarios for L1 L2 mobility ?for FeMIMO | CATT |
R2-2105618 | Discussions on L1 L2 mobility for FeMIMO without serving cell change | CATT |
R2-2105619 | On Scenarios for L1 L2 mobility ?for FeMIMO | CATT |
R2-2105620 | Discussions on L1 L2 mobility for FeMIMO without serving cell change | CATT |
R2-2105621 | On Scenarios for L1 L2 mobility for FeMIMO | CATT |
R2-2105622 | Discussions on L1 L2 mobility for FeMIMO without serving cell change | CATT |
R2-2105731 | Enhanced TCI State Indication for UE-specific PDCCH MAC CE | Xiaomi Communications |
R2-2105826 | Discussion on the support of inter-cell multi-TRP operation | Lenovo, Motorola Mobility |
R2-2105827 | Discussion on the support of L1/L2 centric inter-cell mobility | Lenovo, Motorola Mobility |
R2-2105857 | Consideration on the L1L2 centric mobility | ZTE, Sanechips |
R2-2105858 | Consideration on the enhanced TCI state indication MAC CE for PDCCH | ZTE, Sanechips |
R2-2105870 | Beam failure with mTRP | Nokia, Nokia Shanghai Bell |
R2-2105907 | On the LS about Activating two TCI states with a MAC CE | Ericsson |
R2-2105991 | L1/L2 centric-mobility: Multi-TRP | Huawei, HiSilicon |
R2-2105992 | Handover-like mechanism for L1/L2-centric inter-cell mobility | Huawei, HiSilicon |
R2-2105999 | On L1/L2 centric inter-cell mobility | Ericsson |
R2-2106295 | Potential RAN2 work for feMIMO | LG Electronics |
R2-2106314 | Summary of email discussion [Post113bis-e][061][feMIMO] InterCell mTRP and L1/L2 mobility (Samsung) | Samsung |
R2-2106315 | DRAFT LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
R2-2106664 | [AT114-e][036][feMIMO] InterCell mTRP and L1/L2 mobility (Samsung) | Samsung |
R2-2106768 | [DRAFT] LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
R2-2106787 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2104715 | LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (R1-2104117; contact: Qualcomm) | RAN1 |
R2-2104718 | Reply LS on Rel-17 uplink Tx switching (R1-2104137; contact: China Telecom) | RAN1 |
R2-2104721 | LS on Rel-17 Tx switching enhancements (R4-2103234; contact: China Telecom) | RAN4 |
R2-2104726 | LS on RACH procedure for HO with PSCell (R4-2105830; contact: Ericsson) | RAN4 |
R2-2104732 | Reply LS to SA2 on UE Data Collection (S4-210644; contact: Qualcomm) | SA4 |
R2-2104735 | LS on network sharing with multiple SSBs in a carrier (S5-212403; contact: ZTE) | SA5 |
R2-2104933 | RACH partitioning for Rel-17 features | Ericsson |
R2-2104989 | RACH procedure for HO with PSCell | Nokia, Nokia Shanghai Bell |
R2-2104990 | Reply LS on RACH procedure for HO with PSCell | Nokia, Nokia Shanghai Bell |
R2-2105093 | Clarification on RACH Procedure for HO with PSCell | Apple |
R2-2105155 | Discussion on RACH procedure for HO with PSCell | ZTE Corporation, Sanechips |
R2-2105156 | Consideration on Rel-17 UL Tx switching capability | ZTE Corporation, Sanechips |
R2-2105157 | Draft LS on Rel-17 UL Tx switching capability | ZTE Corporation, Sanechips |
R2-2105623 | Rel-17 Tx switching enhancements | vivo |
R2-2105626 | 38.331 CR on Rel-17 Tx switching enhancements | vivo |
R2-2105627 | 38.306 CR on Rel-17 Tx switching enhancements | vivo |
R2-2105652 | PWS segmentation area | Ericsson |
R2-2105776 | [Draft] Reply LS on RACH procedure for HO with PSCell | Ericsson |
R2-2105777 | RACH procedure for HO with PSCell | Ericsson |
R2-2105778 | Clarification on RACH procedure for HO with PSCell | Ericsson |
R2-2105779 | Clarification on RACH procedure for HO with PSCell | Ericsson |
R2-2105961 | NR positioning support for TA-based positioning in E-CID | Ericsson |
R2-2105982 | UE capabilities for UL Tx switching enhancement | Ericsson |
R2-2106081 | RAN2 Datapath impact from >52GHz | Apple Inc |
R2-2106163 | RAN2 impact to support R17 UL Tx switching enhancement | Huawei, HiSilicon, China Telecom, CATT |
R2-2106164 | Draft CR to TS38.331 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
R2-2106165 | Draft CR to TS38.306 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
R2-2106166 | Discussion on RAN4 LS on RACH procedure for HO with PSCell | Huawei, HiSilicon |
R2-2106446 | RAN2 Datapath impact from >52GHz | Apple Inc |
R2-2106452 | SDT RACH resource configuration and coordination with other WIs (REDCAP, Coverage-ext, RAN-Slicing) | ZTE Corporation, Sanechips |
R2-2106646 | RAN2 Datapath impact from >52GHz | Apple Inc |
R2-2106656 | Summary of [AT114-e][031][NR17] UL TX Switching (Huawei) | Huawei, HiSilicon |
R2-2106673 | Summary of [AT114-e][030][NR17] RACH for HO with PSCell | Ericsson |
R2-2106674 | Reply LS on RACH procedure for HO with PSCell | RAN2 |
R2-2106675 | Clarification on RACH procedure for HO with PSCell | Ericsson |
R2-2106676 | Clarification on RACH procedure for HO with PSCell | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2104706 | LS on Agreements Related to Support of a maximum DL TBS of 1736 bits as a Rel-17 optional UE capability (R1-2103942; contact: Sony) | RAN1 |
R2-2104725 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state (R4-2105800; contact: Huawei) | RAN4 |
R2-2106602 | RAN2 agreements for Rel-17 NB-IoT and LTE-MTC | Document Rapporteur (Ericsson) |
TDoc | Title | Source |
---|---|---|
R2-2105224 | Analysis on connected mode signalling procedure changes for Re-establishment time reduction | Nokia, Nokia Shanghai Bells |
R2-2105314 | Remaining issues for measurement in connected mode | ZTE Corporation, Sanechips |
R2-2105543 | Discussion on the remaining issue of reestablishment-time-reduction | Spreadtrum Communications |
R2-2105657 | Triggering RLF cell selection before T3010 expiry | Huawei, HiSilicon |
R2-2105661 | Report of email discussion [351] NB-IoT RLF measurements (Huawei) | Huawei |
R2-2105828 | Neighbor cell measurements triggering before RLF | Lenovo, Motorola Mobility |
R2-2105918 | Consideration on neighbour cell measurement in RRC connected state | Qualcomm Incorporated |
R2-2106080 | Discussion on connected mode measurement in NB-IoT | Ericsson |
R2-2106289 | Measurement before radio link failure | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2105225 | Further analysis on paging carrier selection options | Nokia, Nokia Shanghai Bells |
R2-2105317 | Further discussion on CEL-based paging carrier selection | ZTE Corporation, Sanechips |
R2-2105544 | Further discussion on enhanced paging carrier selection and NPRACH carrier selection | Spreadtrum Communications |
R2-2105642 | Simplified Static solution | THALES |
R2-2105658 | Clarification on Paging carrier selection | Huawei, HiSilicon |
R2-2105659 | Guildelines for the design of coverage based paging carrier selection | Huawei, HiSilicon |
R2-2105919 | Considerations on the two paging carrier selection schemes | Qualcomm Incorporated |
R2-2106076 | Analysis of Rmax based solution and carrier-based solution | Ericsson |
R2-2106198 | Carrier selection enhancement | MediaTek Inc. |
R2-2106380 | Network configuration for paging carrier selection | Nokia Solutions & Networks (I) |
R2-2106466 | Summary of NB-IoT AI 9.1.3 carrier selection based on coverage level | Ericsson |
R2-2106601 | [AT114-e][301][NBIOT/eMTC R17] NB-IoT Carrier Selection (Ericsson) | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2105318 | Further discussion on 16QAM for NB-IoT | ZTE Corporation, Sanechips |
R2-2105363 | Further discussion on 14 HARQ and DL TBS of 1736bits for eMTC | ZTE Corporation, Sanechips |
R2-2105660 | Support of DL TBS of 1736 bits for HD-FDD Cat. M1 Ues | Huawei, HiSilicon |
R2-2106078 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
R2-2106158 | Total L2 Buffer Size for NB-IoT and LTE-M UEs | Ericsson |
R2-2106603 | Report of [AT114-e][302][NBIOT/eMTC R17] NB-IoT/eMTC Other (ZTE) | ZTE (email discussion rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2104817 | Discussion on essential features of IoT over NTN | OPPO |
R2-2104855 | Further Consideration on PSM for IoT NTN | CATT |
R2-2105364 | Further discussion on essential parts of IoT NTN | ZTE Corporation |
R2-2105415 | Further discussion on essential parts for IoT-NTN functionality for Rel-17 | Nokia, Nokia Shanghai Bell |
R2-2105428 | Essential features for SI TR | Qualcomm Incorporated |
R2-2105664 | Discussion on essential parts for IOT NTN | Huawei, HiSilicon |
R2-2106168 | Essential functionality in IoT NTN | Ericsson |
R2-2106359 | Essential Functionality related to power saving & mobility | Beijing Xiaomi Mobile Software |
R2-2106468 | [Pre114-e][004][IoT NTN] Summary Essential Parts (Huawei) | Huawei |
R2-2106677 | [AT114-e][032][IoT NTN] TR recommendations essential parts | R2 Chairman (Mediatek) |
R2-2106745 | TP for TR 36.763 capturing RAN2 #114-e agreements | Eutelsat S.A., MediaTek |
R2-2106767 | [AT114-e][032][IoT NTN] TR recommendations essential parts | R2 Chairman (Mediatek) |
R2-2106784 | TP for TR 36.763 capturing RAN2 #114-e agreements | Eutelsat S.A., MediaTek |
TDoc | Title | Source |
---|---|---|
R2-2104818 | Discussion on impact of repetition transmission for IoT over NTN | OPPO |
R2-2104819 | Discussion on other open issues for IoT over NTN | OPPO |
R2-2104862 | Mobile-Termination with non-continuous coverage in NTN | Gatehouse, Sateliot |
R2-2104863 | On satellite pass predictions for UE wake-up management under discontinuous coverage | Sateliot, Gatehouse |
R2-2105369 | Specific issues of IoT NTN | ZTE Corporation, Sanechips |
R2-2105416 | Discussion on open issues not covered by NR NTN | Nokia, Nokia Shanghai Bell |
R2-2105429 | Recovery of synchronization in RRC_CONNECTED | Qualcomm Incorporated |
R2-2105559 | Discussion on open issues and essential enhancements for IoT-NTN | XIaomi |
R2-2105663 | Discussion on mobility enhancement for IoT NTN | Huawei, HiSilicon |
R2-2105821 | Considerations on power saving for idle mode in discontinuous coverage | Lenovo, Motorola Mobility |
R2-2105822 | Considerations on RLF and re-establishment for IoT NTN | Lenovo, Motorola Mobility |
R2-2105860 | Mobile-Termination with non-continuous coverage in NTN | Gatehouse, Sateliot, ESA |
R2-2105908 | On satellite pass predictions for UE wake-up management under discontinuous coverage | Sateliot, Gatehouse, ESA |
R2-2106211 | Discontinuous coverage, SIB acquisition during cell reselection and extended DRX cycles in IoT NTN | Ericsson |
R2-2106420 | Mobile-Termination with non-continuous coverage in NTN | Gatehouse, Sateliot, Thales, ESA |
R2-2106479 | [Pre114-e][005][IoT NTN] Summary 9.2.2 Open issues not covered by NR NTN | MediaTek |
TDoc | Title | Source |
---|---|---|
R2-2104856 | Discussion on RLF mechanism of IOT over NTN | CATT |
R2-2105223 | On Paging Capacity Evaluation for IoT-NTN | Nokia, Nokia Shanghai Bells |
R2-2105254 | On Discontinuous coverage in IoT-NTN | MediaTek Inc. |
R2-2105371 | Paging capacity evaluation for IoT NTN | ZTE Corporation, Sanechips |
R2-2105430 | Enhancement to SIB acquisition | Qualcomm Incorporated |
R2-2105461 | Connected mode related issues in IoT NTN | Xiaomi Communications |
R2-2105545 | Discussion on the issue of mobility for IoT over NTN | Spreadtrum Communications |
R2-2105662 | Paging evaluation for NTN IOT | Huawei, HiSilicon |
R2-2106169 | Connection density evaluation for IoT NTN devices | Ericsson |
R2-2106247 | RLF-based NB-IoT mobility in IoT-NTN | CMCC |
R2-2106250 | Discussion on TA Update for IoT-NTN | CMCC |
R2-2106486 | [Pre114-e][006][IoT NTN] Summary of 9.2.3 Other Open Issues (Ericsson) | Ericsson |
R2-2106729 | On Paging Capacity Evaluation for IoT-NTN | Nokia, Nokia Shanghai Bells |
TDoc | Title | Source |
---|---|---|
R2-2104705 | User location identification from Carrier Aggregation secondary cell activation messages (FSAG Doc 88_009) | GSMA |
R2-2105039 | Draft LS on SLIC attack | Huawei, HiSilicon |
R2-2105263 | [Draft] LS reply on Stealthy Location Identification Attack | vivo |
R2-2105268 | Discussion on Stealthy Location Identification Attack. | vivo |
R2-2106144 | Discussion on event triggered logged MDT for LTE | Huawei, HiSilicon |
R2-2106145 | CR to 36.306 on event triggered logged MDT for LTE | Huawei, HiSilicon |
R2-2106146 | CR to 36.331 on event triggered logged MDT for LTE | Huawei, HiSilicon |
R2-2106147 | CR to 37.320 on event triggered logged MDT for LTE | Huawei, HiSilicon |
R2-2106148 | CR to 36.304 on event triggered logged MDT for LTE | Huawei, HiSilicon |
R2-2106511 | [DRAFT] LS to SA3 on SLIC | vivo |
R2-2106516 | LS to SA3 on SLIC | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2105934 | On the use of the term exclude-list | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2106471 | Report from session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing | Vice Chairman (Nokia) |
TDoc | Title | Source |
---|---|---|
R2-2106472 | Report from Break-Out Session on R17 NTN and RedCap | Vice Chairman (ZTE) |
TDoc | Title | Source |
---|---|---|
R2-2106473 | Report eMTC breakout session | Session chair (Ericsson) |
TDoc | Title | Source |
---|---|---|
R2-2106474 | Report for Rel-17 Small data and URLLC/IIoT | Session chair (InterDigital) |
TDoc | Title | Source |
---|---|---|
R2-2106475 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
TDoc | Title | Source |
---|---|---|
R2-2106476 | Report from SOM/MDT session | Session chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R2-2106477 | Report NB-IoT breakout session | Session chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R2-2106478 | Report from session on LTE V2X and NR SL | Session chair (Samsung) |