| TDoc | Title | Source |
|---|---|---|
| R2-2503301 | Agenda for RAN2#130 | Chairman |
| TDoc | Title | Source |
|---|---|---|
| R2-2503302 | RAN2#129bis Meeting Report | MCC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503303 | RAN2 Handbook | MCC |
| R2-2503703 | On specification file formats and workflows | Apple |
| R2-2504187 | Further aspects on improvements to specification handling | Ericsson |
| R2-2504415 | Report of [POST129bis][002][ASN.1 review] Process improvements | Nokia |
| R2-2504448 | Markdown for CRs – Gaps and Possible Solutions | Samsung |
| R2-2504670 | ASN.1 review plan | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503472 | Clarification on Inter-RAT Cell Selection for NB-IoT | vivo |
| R2-2503473 | Clarification on Inter-RAT Cell Selection for NB-IoT | vivo |
| R2-2503474 | Clarification on Inter-RAT Cell Selection for NB-IoT | vivo |
| R2-2503939 | Correction to NeedForGap capability | Huawei, HiSilicon |
| R2-2503940 | Correction to NeedForGap capability | Huawei, HiSilicon |
| R2-2503941 | Correction to NeedForGap capability (R18) | Huawei, HiSilicon |
| R2-2503982 | Correction to NeedForGap capability | Huawei, HiSilicon |
| R2-2504017 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504018 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504019 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504020 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504021 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504022 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504023 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504024 | Introducing UE capability for A4 A5 ReportOnLeave | ZTE Corporation, Sanechips, Qualcomm Incorporated, Samsung, MediaTek Inc, Xiaomi, Huawei, HiSilicon |
| R2-2504322 | Correction on MBMS Interest Indication | Samsung |
| R2-2504323 | Correction on MBMS Interest Indication | Samsung |
| R2-2504324 | Correction on MBMS Interest Indication | Samsung |
| R2-2504325 | Correction on MBMS Interest Indication | Samsung |
| R2-2504326 | Correction on MBMS Interest Indication | Samsung |
| R2-2504332 | Correction to explicit indication of epoch in SIB31 | Nordic Semiconductor ASA, Qualcomm, Mediatek Inc., Ericsson |
| R2-2504333 | Correction to explicit indication of epoch in SIB31 | Nordic Semiconductor ASA, Qualcomm, Mediatek Inc., Ericsson |
| R2-2504335 | Clarification to NTN SI message accumulation over SI-windows | Nordic Semiconductor ASA |
| R2-2504336 | Clarification to NTN SI message accumulation over SI-windows | Nordic Semiconductor ASA |
| R2-2504337 | Clarification to NTN SI message accumulation over SI-windows | Nordic Semiconductor ASA |
| R2-2504451 | Miscellaneous non-controversial corrections | Samsung |
| R2-2504452 | Miscellaneous non-controversial corrections | Samsung |
| R2-2504453 | Miscellaneous non-controversial corrections | Samsung |
| R2-2504553 | Miscellaneous non-controversial corrections | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503307 | Reply LS on segmented UE capabilities (C4-251474; contact: Ericsson) | CT4 |
| R2-2503315 | LS on Handling of UE Radio Capability for Paging (R3-252276; contact: Ericsson) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R2-2503946 | Corrections on DCP | Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2503947 | Corrections on DCP | Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2503948 | Corrections on DCP | Huawei, HiSilicon, Nokia (Rapporteur) |
| TDoc | Title | Source |
|---|---|---|
| R2-2503648 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| R2-2503649 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| R2-2503650 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| R2-2503769 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| R2-2503770 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| R2-2503771 | Clarification on the power ramping indicated to PHY | OPPO, Qualcomm Incorporated, Huawei, MediaTek Inc, LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R2-2504105 | Correction to delivery of SIB segments by dedicated signalling in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2504106 | Correction to delivery of SIB segments by dedicated signalling in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2504107 | Correction to delivery of SIB segments by dedicated signalling in RRC_CONNECTED | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R2-2503630 | Correction to Immediate MDT measurements | Nokia |
| R2-2503631 | Correction to Immediate MDT measurements | Nokia |
| R2-2503632 | Correction to Immediate MDT measurements | Nokia |
| R2-2503993 | Correction to nrofCandidates-CI for DCI format 2_4 | Huawei, HiSilicon |
| R2-2503994 | Correction to nrofCandidates-CI for DCI format 2_4 | Huawei, HiSilicon |
| R2-2503995 | Correction to nrofCandidates-CI for DCI format 2_4 | Huawei, HiSilicon |
| R2-2504086 | Correction on timeUntilReconnection in RLF report | ZTE Corporation, Xiaomi, Sanechips |
| R2-2504163 | Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 | Apple, Huawei, HiSilicon, xiaomi, Samsung |
| R2-2504164 | Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 | Apple, Huawei, HiSilicon, xiaomi, Samsung |
| R2-2504165 | Type clarification for interBandMRDC-WithOverlapDL-Bands-r16 | Apple, Huawei, HiSilicon, xiaomi, Samsung |
| R2-2504195 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504196 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504197 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504198 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504199 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504200 | Correction to pdsch-256QAM-FR1 for IAB-MT | Nokia |
| R2-2504250 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504251 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504252 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504253 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504582 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504583 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504584 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504585 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504586 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504587 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504588 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504589 | Correction on SRS capability reporting | Huawei, HiSilicon, Ericsson, OPPO |
| R2-2504680 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504681 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504682 | Correction on number of NZP CSI-RS resources | Ericsson |
| R2-2504683 | Correction on number of NZP CSI-RS resources | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503854 | Corrections on Spatial Relation Info list and sizeExt list for PUCCH | ZTE, Samsung, Qualcomm, CATT, MediaTek |
| R2-2503855 | Corrections on Spatial Relation Info list and sizeExt list for PUCCH | ZTE, Samsung, Qualcomm, CATT, MediaTek |
| R2-2503856 | Corrections on Spatial Relation Info list and sizeExt list for PUCCH | ZTE, Samsung, Qualcomm, CATT, MediaTek |
| R2-2504257 | PUCCH SpatialRelationInfo Lists | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503595 | Clarifications on band combination specific power class | Qualcomm Incorporated |
| R2-2503596 | Clarifications on band combination specific power class | Qualcomm Incorporated |
| R2-2503597 | Clarifications on band combination specific power class | Qualcomm Incorporated |
| R2-2504190 | Correction to scellWithoutSSB | Ericsson |
| R2-2504191 | Correction to scellWithoutSSB | Ericsson |
| R2-2504192 | Correction to scellWithoutSSB | Ericsson |
| R2-2504193 | Correction to scellWithoutSSB | Ericsson |
| R2-2504590 | Correction on pdcp-DuplicationSRB for NR-DC | Huawei, HiSilicon |
| R2-2504591 | Correction on pdcp-DuplicationSRB for NR-DC | Huawei, HiSilicon |
| R2-2504592 | Correction on pdcp-DuplicationSRB for NR-DC | Huawei, HiSilicon |
| R2-2504593 | Correction on pdcp-DuplicationSRB for NR-DC | Huawei, HiSilicon |
| R2-2504624 | Clarification on the maxMIMO-LayersForMulti-DCI-mTRP-r16 | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2504661 | Removal of PWS support in NR NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503318 | Reply LS on emergency call back and paging (R3-252402; contact: ZTE) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R2-2504508 | Correction on cell type specific cell reselection prioritisation [NR_HSDN] | Huawei, HiSilicon, Nokia, Qualcomm, CMCC, Xiaomi, CATT, Apple, NTT DOCOMO, INC., Ericsson |
| R2-2504509 | Correction on cell type specific cell reselection prioritisation [NR_HSDN] | Huawei, HiSilicon, Nokia, Qualcomm, CMCC, Xiaomi, CATT, Apple, NTT DOCOMO, INC., Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2504228 | Correction on M6 definition for NR MDT | Huawei, HiSilicon |
| R2-2504229 | Correction on M6 definition for NR MDT | Huawei, HiSilicon |
| R2-2504520 | Clarification on redirection and cell reselection to NR NTN | CATT, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2504521 | Clarification on redirection and cell reselection to NR NTN | CATT, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R2-2503723 | Correction of egress Uu RLC channel determination for L2 U2N Relay UE | Apple |
| R2-2503724 | Correction of egress Uu RLC channel determination for L2 U2N Relay UE | Apple |
| R2-2503852 | Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE | ZTE Corporation, Samsung, Qualcomm, Nokia, China Telecom, MediaTek |
| R2-2503853 | Correction on PUCCH spatial relation Activation/Deactivation for multiple TRP PUCCH repetition MAC CE | ZTE Corporation, Samsung, Qualcomm, Nokia, China Telecom, MediaTek |
| R2-2504141 | Correction on SR for mTRP BFR | Huawei, HiSilicon |
| R2-2504142 | Correction on SR for mTRP BFR | Huawei, HiSilicon |
| R2-2504314 | Corrections on P-CSI report in NTN | Qualcomm Incorporated |
| R2-2504428 | MAC correction on Release-17 Sidelink enhancement | LG Electronics Inc. |
| R2-2504430 | Correction on IAB related MAC CEs | ZTE Corporation, Samsung, Sanechips |
| R2-2504431 | Correction on IAB related MAC CEs | ZTE Corporation, Samsung, Sanechips |
| R2-2504432 | MAC correction on Release-17 Sidelink enhancement | LG Electronics Inc. |
| R2-2504605 | Discussion on DCP and CSI report | Beijing Xiaomi Mobile Software |
| R2-2504607 | Clarification on not support DCP for NTN | Xiaomi |
| R2-2504611 | Clarification on not support DCP for NTN | Xiaomi |
| R2-2504612 | Clarification on the ambiguity of symbol n | Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R2-2503456 | Usage of msg3-transmitPrecoder | CATT, Huawei, HiSilicon |
| R2-2503457 | Usage of msg3-transmitPrecoder | CATT, Huawei, HiSilicon |
| R2-2503887 | Slot aggregation configuration with multi-PUSCH | Nokia |
| R2-2503888 | Slot aggregation configuration with multi-PUSCH | Nokia |
| R2-2503933 | Correction to ul-GapFR2-r17 | Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell, Ericsson, MediaTek Inc. |
| R2-2503934 | Correction to ul-GapFR2-r17 | Huawei, HiSilicon, Apple, Nokia, Nokia Shanghai Bell, Ericsson, MediaTek Inc. |
| R2-2504015 | Correction on SCS and CP configuration in RedCap-specific initial BWP | ZTE Corporation, Sanechips, Vivo, Ericsson, MediaTek Inc, Qualcomm Incorporated, OPPO, Samsung |
| R2-2504016 | Correction on SCS and CP configuration in RedCap-specific initial BWP | ZTE Corporation, Sanechips, Vivo, Ericsson, MediaTek Inc, Qualcomm Incorporated, OPPO, Samsung |
| R2-2504083 | Corrections to location-based measurement | ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2504084 | Corrections to location-based measurement initiation | ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2504085 | Corrections to location-based measurement initiation | ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2504087 | Correction on timeUntilReconnection in RLF report | ZTE Corporation, Xiaomi, Sanechips |
| R2-2504088 | Correction on timeUntilReconnection in RLF report | ZTE Corporation, Xiaomi, Sanechips |
| R2-2504648 | Correction on SCS and CP configuration in RedCap-specific initial BWP | ZTE Corporation, Sanechips, Vivo, Ericsson, MediaTek Inc, Qualcomm Incorporated, OPPO, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503576 | Correction on SHR determination procedure | CATT |
| R2-2503577 | Correction on SHR determination procedure | CATT |
| R2-2504001 | Discussion on rsrp-ThresholdSSB-r17 in TS 38.331 | Huawei, HiSilicon, Qualcomm, MediaTek, ZTE, Xiaomi, Vivo |
| R2-2504025 | Discussion on eDRX operation with emergency PDU session | ZTE Corporation |
| R2-2504026 | [draft] Reply LS on emergency call back and paging | ZTE Corporation |
| R2-2504203 | Corrections on measurement with (cond)EventD1/D2/T1 | Samsung |
| R2-2504204 | Corrections on measurement with (cond)EventD1/T1 | Samsung |
| R2-2504205 | Corrections on measurement with (cond)EventD1/D2/T1 | Samsung |
| R2-2504456 | Discussion on rsrp-ThresholdSSB-r17 in TS 38.331 | Huawei, HiSilicon, Qualcomm, MediaTek, ZTE, Xiaomi, Vivo, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503937 | Capability for SMTC adjustment in RRC_IDLE and RRC_INACTIVE | Huawei, HiSilicon, CMCC, Qualcomm Incorporated. |
| R2-2503938 | Capability for SMTC adjustment in RRC_IDLE and RRC_INACTIVE | Huawei, HiSilicon, CMCC, Qualcomm Incorporated. |
| R2-2504315 | Clarification on support of DCP in NTN | Qualcomm Inc. |
| R2-2504316 | Clarification on support of DCP in NTN | Qualcomm Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2504266 | Discussion on emergency services and eDRX | Nokia, Huawei, HiSilicon |
| R2-2504267 | (e)DRX usage clarification for UEs with emergency PDU Sessions | Nokia, Huawei, HiSilicon |
| R2-2504268 | (e)DRX usage clarification for UEs with emergency PDU Sessions | Nokia, Huawei, HiSilicon |
| R2-2504287 | eDRX and emergency PDU session | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2504302 | Correction for GNSS periodic AD request | Ericsson |
| R2-2504303 | Correction for GNSS periodic AD request | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503443 | Miscellaneous non-controversial rapporteur corrections | Xiaomi |
| R2-2503976 | Removal of editor’s note for nr-PDCCH-OverlapLTE-CRS-RE-r18 (FG R1 52-1) | Lenovo, Ericsson |
| R2-2503977 | Corrections on eDSS capability descriptions | Lenovo, Ericsson |
| R2-2503978 | Corrections on Multicarrier enhancements capability descriptions | Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R2-2503377 | Correction on condition-based IUC for shared SL-PRS resource pool | vivo, Ericsson |
| R2-2503378 | Correction on NW restriction for dedicated SL-PRS resource pool | vivo, Ericsson |
| R2-2503408 | Handling of the default SRB configuration upon LTM execution | CATT |
| R2-2503498 | Corrections on the descriptions of nr-PeriodicOrOneShotTimeWindow and nr-StartSFN-TimeWindow | CATT, Qualcomm Incorporated |
| R2-2503505 | Correction for cell barring for NES CellDTX-DRX UEs | Huawei, HiSilicon |
| R2-2503611 | Updating references to TS 28.558 from TS 28.552 | Nokia |
| R2-2503628 | Correction on UE capability for L1-RSRP measurement in LTM | vivo, Ericsson, Xiaomi, ZTE Corporation |
| R2-2503629 | Correction on the maximum number of SSB rsources for L1 measurement without gaps in LTM | vivo, Ericsson, Xiaomi, ZTE Corporation |
| R2-2503685 | Correction on RACH-less HO Use Case [RACH-lessHO] | vivo, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, ZTE Corporation, Sanechips, Huawei, HiSilicon, Lenovo, THALES |
| R2-2503718 | Correction on MCSt Restriction for Resource Selection | Apple |
| R2-2503719 | Correction to PC5 RLC Channel Release | Apple, ASUSTek |
| R2-2503774 | Missing rate of change direction of azimuth/elevation for relative velocity | Xiaomi, Qualcomm, CATT, Huawei, MediaTek Inc., Ericsson |
| R2-2503841 | Rapporteur MAC CR for RACH-less HO and LTM [RACH-lessHO] | Huawei, HiSilicon, CATT, Nokia, Samsung, Qualcomm |
| R2-2503842 | Correction to UE capability for retx-less CG | Huawei, HiSIlicon, Apple, Futurewei, Qualcomm |
| R2-2503843 | Correction to RRC for retx-less CG | Huawei, HiSIlicon, Apple, Futurewei, Qualcomm |
| R2-2503935 | Clarification on ssb-TimeOffset | Huawei, HiSilicon |
| R2-2503949 | Correction on UE capability for SIB17bis | Huawei, HiSilicon |
| R2-2503992 | Adding enabledDefaultBeamForMultiCellScheduling | Huawei, HiSilicon, NTT DOCOMO INC., Samsung, Ericsson |
| R2-2504008 | Correction on sidelink RRC specification | ZTE Corporation, Sanechips, Ericsson |
| R2-2504009 | Correction on sidelink relay RRC specification | ZTE Corporation, Sanechips |
| R2-2504050 | Clarification on capability for inter-frequency configuration for less than 5MHz | Huawei, HiSilicon, Xiaomi, Samsung, Qualcomm Incorporated |
| R2-2504067 | Correction on SIB33 reception in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2504076 | Correction on timeSinceSHR in SHR report | ZTE Corporation, Sanechips |
| R2-2504089 | Corrections to location-based measurement | ZTE Corporation, Ericsson, CATT, Sanechips |
| R2-2504122 | Capability Coordination for LTM | Ericsson, Nokia |
| R2-2504127 | Capability coordination for LTM | Ericsson, Nokia |
| R2-2504143 | Handling of PUCCH resources for L1 LTM reports at TAT expiry | Huawei, HiSilicon |
| R2-2504166 | Type clarification for intraBandNR-CA-non-collocated-r18 | Apple, Huawei, HiSilicon, xiaomi, Samsung |
| R2-2504217 | Correction to Rel-18 NR NTN CHO with only location/time-based trigger | Samsung |
| R2-2504220 | Correction to Rel-18 NR NTN CHO with only location/time-based trigger | Samsung |
| R2-2504227 | Correction on SON for NPN in TS 38.300 | Huawei, HiSilicon, CATT, Samsung, ZTE, CMCC |
| R2-2504254 | Miscellaneous non-controversial corrections Set XXV | Ericsson |
| R2-2504425 | MAC correction on Release-18 Sidelink evolution | LG Electronics Inc. |
| R2-2504455 | Correction on logging intendedSIBs | Samsung |
| R2-2504480 | Correction on supporting 8Tx in MAC specification | ASUSTeK, Samsung, ZTE, Ericsson |
| R2-2504501 | Correction on supporting 8Tx in MAC specification | ASUSTeK, Samsung, ZTE, Ericsson |
| R2-2504534 | Corrections on eEMR/IMR and LTM L2 Reset/UE-based TA measurement | Samsung, Ericsson |
| R2-2504549 | Corrections on eEMR/IMR and LTM L2 Reset/UE-based TA measurement | Samsung, Ericsson |
| R2-2504567 | Corrections on eEMR/IMR and LTM L2 Reset/UE-based TA measurement | Samsung, Ericsson |
| R2-2504650 | Correction on NTN in FR2-NTN bands | vivo, ZTE Corporation, Ericsson, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2504551 | Possible RAN1 impact on RACH-less HO in TN | NEC |
| TDoc | Title | Source |
|---|---|---|
| R2-2504072 | Correction on NCR-MT capability | Huawei, HiSilicon |
| R2-2504615 | Correction on NCR-Fwd functionality | Samsung, Nokia (Rapporteur) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504074 | Correction on the definition of waypoint location | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R2-2503760 | Way forward of servingCellMO for SSB-less Scell | ZTE Corporation, Sanechips, Ericsson, Nokia |
| R2-2503761 | Correction on servingCellMO configuration - 38.331 | ZTE Corporation, Sanechips, Ericsson, Nokia |
| R2-2503762 | Correction on servingCellMO configuration - 38.306 | ZTE Corporation, Sanechips, Ericsson, Nokia |
| R2-2503936 | Discussion on servingCellMO for SSB-less Scell | Huawei, HiSilicon, Apple, Samsung, Qualcomm Incorporated, MediaTek Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2503575 | Corrections on SPR configuration | CATT, Ericsson |
| R2-2504292 | Correction on ra-InformationCommon logging in RLF-Report SHR and SPR | Ericsson |
| R2-2504293 | Corrections on PCell information in SPR | Ericsson |
| R2-2504515 | Correction for setting choCandidate in SHR | Sharp |
| R2-2504517 | Correction for setting choCandidate in SHR | Sharp |
| R2-2504535 | Correction on areaConfiguration | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503950 | Corrections for MUSIM gap | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R2-2503740 | Corrections on simultaneousU-TCI-UpdateListx and RACH-ConfigTwoTA | CATT |
| R2-2504213 | Correction on PHR for STx2P multi-panel scheme | Samsung |
| R2-2504258 | Correction to epre-Ratio field description | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503979 | Clean-up corrections on stage 2 description of QMC | Lenovo, Nokia, Nokia Shanghai Bell, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2504597 | Discussion on DSR cancellation | Ericsson, Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R2-2504133 | Further Thoughts on IDC issue between GNSS and NTN UL | Nokia, Nokia Shanghai Bell |
| R2-2504206 | Corrections on measurement with (cond)EventD1/D2/T1 | Samsung |
| R2-2504313 | Clarification on reference point for hard satellite switch with resynchronization | Qualcomm Incorporated, Huawei |
| R2-2504339 | Clarification on reference point for hard satellite switch with resynchronization | Qualcomm Incorporated, Huawei |
| R2-2504660 | Removal of PWS support in NR NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2504095 | Various corrections on connected mode RRM for IoT NTN | Samsung |
| R2-2504657 | In-band operation for NB-IoT | Ericsson |
| R2-2504658 | Introduction of the inband operation for NTN IoT in NR NTN | Ericsson, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503996 | Correction to PDCP duplication description for L2 MP using SL relay or N3C indirect path | Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2504002 | Correction to PDCP duplication description for L2 MP using SL relay or N3C indirect path | Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2504346 | U2U Relays, Peer Remote UE Control Plane Procedures | Ericsson |
| R2-2504481 | Correction on terminology of local ID pair list | ASUSTeK, Huawei, HiSilicon |
| R2-2504482 | Correction on terminology of local ID pair list | ASUSTeK, Huawei, HiSilicon |
| R2-2504483 | Additional description of AM RLC entity for supporting L2 U2U Relay | ASUSTeK |
| R2-2504484 | Correction to end-to-end sidelink DRB Release | ASUSTeK, Apple |
| R2-2504548 | Further discussion on the prerequisite of Rel-17/18 SL relay capability | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503332 | Reply LS to RAN2 on AdditionalSpectrumEmission (R4-2505217; contact: ZTE) | RAN4 |
| R2-2503722 | Dummy sl-PowerClassUnlicensed capability | Apple |
| R2-2504433 | Correction on MCSt for resource selection | LG, Ericsson |
| R2-2504438 | Correction on TX carrier (re-)selection | LG Electronics Inc. |
| R2-2504458 | Discussion on implementation of AdditionalSpectrumEmission | ZTE Corporation, Sanechips |
| R2-2504539 | Correction on SL-U Power Class Capability | Apple, OPPO |
| TDoc | Title | Source |
|---|---|---|
| R2-2503497 | Corrections on RRC connection resume procedure initiated by activation or configuration of positioning SRS | CATT, Samsung, Ericsson, vivo |
| R2-2503517 | Correction to TA validation for SRS transmission in RRC_INACTIVE | Ofinno |
| R2-2503784 | Clarification on UE behavior when multiple positioning methods are requested for UE-based positioning | LG Electronics Inc, Qualcomm Incorporated |
| R2-2503872 | Correction on SRS hopping in positioning | ZTE Corporation, Ericsson, CATT, Samsung, vivo, Xiaomi, Qualcomm, Lenovo |
| R2-2503873 | Correction on SL positioning DCI format | ZTE Corporation |
| R2-2504103 | Correction on UE capabilities in SL positioning | Huawei, HiSilicon |
| R2-2504104 | Correction on the periodic AD of NR integrity service alert | Huawei, HiSilicon, Ericsson, vivo |
| R2-2504304 | RRC Sidelink Positioning Correction | Ericsson, vivo, Huawei, Xiaomi |
| R2-2504305 | Sidelink Positioning, LPHAP, Carrier aggregation and frequency hopping correction | Ericsson |
| R2-2504340 | RRC Sidelink Positioning Correction | Ericsson, vivo, Huawei, Xiaomi |
| R2-2504485 | Correction on sl-PRS-ResourcePoolID for SL-PRS CG | ASUSTeK, Ericsson, Huawei, HiSilicon, Samsung |
| R2-2504486 | Correction regarding SL-PRS Resource Request MAC CE | ASUSTeK |
| R2-2504502 | Correction on sl-PRS-ResourcePoolID for SL-PRS CG | ASUSTeK, Ericsson, Huawei, HiSilicon, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503325 | Reply LS to RAN2 on granularity definition of pdcch-RACH-AffectedBandsList-r18 (R4-2504940; contact: MediaTek) | RAN4 |
| R2-2503471 | Clarification on source band definition and UE reporting unsupported target band in pdcch-RACH-AffectedBandsList-r18 | MediaTek Inc. |
| R2-2503738 | Correction to LTM cell switch failure handling | |
| R2-2503743 | Data loss issue on fast LTM recovery | Fujitsu |
| R2-2504123 | Clarification of pdcch-RACH-AffectedBandsList-r18 and related capabilities | Ericsson |
| R2-2504124 | Summary of proposals for feMob | Ericsson |
| R2-2504136 | Corrections to Rel-18 LTM (interruptions during RACH and LTM Recovery to the source cell) | Nokia |
| R2-2504144 | Handling of radio and RLC bearers in LTM with NR-DC | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R2-2503359 | Introduction of NB-IoT NTN in-band operation with NR NTN | vivo |
| R2-2504139 | RAN2 Impacts for NR NB-IoT-NTN | Nokia , Nokia Shanghai Bells |
| TDoc | Title | Source |
|---|---|---|
| R2-2503383 | Corrections on Rel-18 Multi-carrier enhancements | Lenovo Information Technology |
| R2-2504073 | Correction on the field descriptions of less than 5Mhz | Huawei, HiSilicon |
| R2-2504167 | Type clarification for UE requirements associated with nonCollocatedTypeMRDC and nonCollocatedTypeNR-CA | Apple, Huawei, HiSilicon, xiaomi, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503304 | Reply LS on UE usage of the RAT restrictions (C1-252546; contact: Apple) | CT1 |
| R2-2503308 | LS on updated Rel-19 RAN1 UE features lists for NR after RAN1#120bis (R1-2502979; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2503309 | LS on initial Rel-19 RAN1 UE features lists for LTE after RAN1#120bis (R1-2502982; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2503314 | LS on Rel-19 higher layers parameters list Post RAN1#120bis (R1-2503154; contact: Ericsson) | RAN1 |
| R2-2503324 | LS on UE capability signalling for NTN less than 5MHz (R4-2504712; contact: ZTE, Xiaomi) | RAN4 |
| R2-2503326 | LS on Rx BSF optimization for NR RRM Ph5 (R4-2504962; contact: CICT Mobile) | RAN4 |
| R2-2503327 | LS of RAN4 RRM agreements on LB CA via switching (R4-2504956; contact: Apple) | RAN4 |
| R2-2503329 | LS on simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD combinations (R4-2505123; contact: Huawei) | RAN4 |
| R2-2503330 | LS on introduction of new UE capabilities for FR2 MPR improvement (R4-2505144; contact: Samsung, Qualcomm) | RAN4 |
| R2-2503331 | LS to RAN2 on Type 4 for non-collocated deployment (R4-2505161; contact: Samsung) | RAN4 |
| R2-2503334 | LS on DL MIMO layers capabilities for 6Rx UEs (R4-2505225; contact: Intel) | RAN4 |
| R2-2503442 | Discussion on R19 ASN.1 review | Xiaomi |
| R2-2503444 | Running UE capability CR on 38.306 for Rel-19 R1 R4 feature lists, including [TN32HARQ], [Pos_SRSHop], [SRTrig_SSSGSwitch] and [Simul_SRSCS] | Xiaomi |
| R2-2503445 | Running UE capability CR on 38.331 for Rel-19 R1 R4 feature lists, including [TN32HARQ], [Pos_SRSHop], [SRTrig_SSSGSwitch] and [Simul_SRSCS] | Xiaomi |
| R2-2503728 | Discussion on CT1 Reply LS (C1-252546) on RAT restrictions | Apple, OPPO, Huawei, HiSilicon, Samsung |
| R2-2503729 | Restriction on RAT utilization | Apple, Vodafone, InterDigital, Ericsson, Nokia, OPPO, Samsung |
| R2-2503730 | Restriction on RAT utilization | Apple, Vodafone, InterDigital, Ericsson, Nokia, OPPO, Samsung |
| R2-2503731 | [Draft] Reply LS on UE usage of the RAT restrictions | Apple |
| R2-2504148 | Practical aspects of R19 ASN.1 review | Huawei, HiSilicon |
| R2-2504668 | Introduction of UE capability signalling for NTN less than 5MHz | Xiaomi |
| R2-2504669 | Introduce UE capability signalling for NTN less than 5MHz | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2503322 | LS reply on AI/ML Positioning Case 3b (R3-252485; contact: Ericsson) | RAN3 |
| R2-2503342 | Reply LS on per-UE UE performance metrics (S5-252056; contact: NEC, Intel, Ericsson) | SA5 |
| R2-2503398 | Introduction of AI for Air interface feature in 38300 | vivo(Rapporteur) |
| R2-2503587 | 38.305 running CR for AIML Positioning | CATT |
| R2-2503713 | Running MAC CR for AI/ML for Air Interface | Apple (Rapporteur) |
| R2-2504128 | Summary of [POST129bis][015][AI PHY] 37.355 Running CR | Qualcomm Incorporated (Rapporteur) |
| R2-2504129 | Running CR for AI/ML Positioning Accuracy Enhancements | Qualcomm Incorporated (Rapporteur) |
| R2-2504130 | LPP open issues for feature "AI/ML for NR air interface" | Qualcomm Incorporated (Rapporteur) |
| R2-2504238 | Running 37.320 CR for AIML PHY | Huawei, HiSilicon |
| R2-2504349 | Draft RRC running CR for AIML PHY | Ericsson |
| R2-2504350 | RRC open issues AIML PHY | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503394 | Leftover Issue Discussion on LCM for UE-sided model for BM use case | OPPO |
| R2-2503399 | Discussion on LCM for UE-sided model for Beam Management | vivo |
| R2-2503449 | Discussion on open issues of AI/ML air LCM | Xiaomi |
| R2-2503537 | Discussion on LCM for UE sided model | NEC Corporation (ARIB) |
| R2-2503539 | Discussion on LCM for UE-sided model for beam management | Samsung |
| R2-2503546 | Discussion on LCM for UE-sided Model for Beam Management Use Case | Fujitsu |
| R2-2503561 | Remaining issues on LCM for UE-sided model for BM | LG Electronics |
| R2-2503588 | Discussion on LCM for UE-sided model for BM use case | CATT |
| R2-2503666 | LCM for UE-sided model for BM | China Telecom |
| R2-2503714 | Remaining issues on LCM procedure of UE-sided model for AI/ML based beam management | Apple |
| R2-2503734 | Discussion on applicability reporting | KT Corp. |
| R2-2503775 | Further Discussion on LCM of UE-sided Model for AI BM | MediaTek Inc. |
| R2-2503848 | Continuous Discussion On LCM for UE-sided model | ZTE Corporation |
| R2-2503918 | Left issues related to applicability report for AIML based BM | Lenovo |
| R2-2503966 | Discussion on LCM for UE-sided model for Beam Management | Spreadtrum, UNISOC |
| R2-2504041 | Further discussion on LCM for UE-sided model for BM | Transsion Holdings |
| R2-2504051 | Discussion on LCM for UE side model for Beam Management | Sony |
| R2-2504114 | Applicability report and Inference for UE-sided model for Beam Management and CSI prediction | Huawei, HiSilicon |
| R2-2504156 | On Explicit Reporting of Functionality Inapplicability | SHARP Corporation |
| R2-2504157 | Considerations for Functionality Activation and Reporting | SHARP Corporation |
| R2-2504214 | Discussion on LCM for UE-Side Model for Beam Management Use Case | Futurewei Technologies |
| R2-2504239 | Discussion on training data collection for UE-sided model for BM and CSI prediction | Huawei, HiSilicon |
| R2-2504309 | Remaining open issues: LCM for UE-sided model for BM use case | InterDigital |
| R2-2504353 | Open Issues on LCM for UE-sided Models for Beam Management and CSI Prediction | Qualcomm Incorporated |
| R2-2504376 | Discussion on LCM for UE-sided model for BM | CMCC |
| R2-2504413 | LCM for UE-side Beam Management | Nokia |
| R2-2504414 | On Enhancements for NW Involvement in UE-side DC for BM | Nokia, T-Mobile USA Inc., Ericsson, BT plc, Verizon, Deutsche Telekom AG |
| R2-2504462 | LCM for UE-side models for beam management | HONOR |
| R2-2504487 | Discussion on Remaining RRC open issues on LCM for UE-side models | ASUSTeK |
| R2-2504554 | Discussions on LCM on UE-side model for Beam Management | NTT DOCOMO, INC. |
| R2-2504636 | LCM for UE-side models for beam management | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503380 | Association of measurements and ground truth labels for positioning use-cases | Fraunhofer IIS, Fraunhofer HHI |
| R2-2503384 | LCM for Positioning use case | NEC |
| R2-2503397 | Leftover Issue Discussion on LCM for Positioning use case | OPPO |
| R2-2503400 | Discussion on open issues of AI/ML enhanced positioning Case 1 | vivo |
| R2-2503403 | Discussion on consistency between training and inference for AI POS | vivo, Qualcomm Incorporated, ZTE Corporation, Sanechips, Lenovo, Ericsson, CATT, OPPO, Fraunhofer IIS, Fraunhofer HHI, CEWiT |
| R2-2503450 | Discussion on AI/ML positioning case 1 | Xiaomi |
| R2-2503464 | Discussion on Applicability Reporting | Continental Automotive |
| R2-2503547 | Discussion on LCM for Positioning Use Case | Fujitsu |
| R2-2503589 | Issues to address for AIML Positioning stage-2 | CATT |
| R2-2503667 | Discussion on performance monitoring for positioning case 1 | China Telecom |
| R2-2503715 | Remaining issues on LCM procedure of AI/ML based positioning | Apple |
| R2-2503800 | Discussion on error causes for AI/ML positioning | LG Electronics Inc. |
| R2-2503801 | Discussion on Functionality-based LCM for Positioning Use Case | CEWiT |
| R2-2503876 | Discussion on LCM for positioning use case | ZTE Corporation |
| R2-2503919 | LCM for AIML based positioning | Lenovo |
| R2-2503985 | Discussion on LCM for POS use case | Samsung |
| R2-2504102 | LCM for Positioning use case | Nokia |
| R2-2504158 | Discussion on remaining issues for "AI/ML Positioning Case 1" | Qualcomm Incorporated |
| R2-2504240 | Discussion on LPP open issues for Case 1 | Huawei, HiSilicon |
| R2-2504307 | Remaining issue for LCM For Positioning | Ericsson |
| R2-2504310 | Remaining open issues: LCM for Positioning use case | InterDigital |
| R2-2504440 | Discussion on LCM for positioning | CMCC |
| R2-2504463 | Discussion on LCM for Positioning Use Case | HONOR |
| TDoc | Title | Source |
|---|---|---|
| R2-2503395 | Leftover Issue Discussion on NW side data collection | OPPO |
| R2-2503401 | Discussion on NW side data collection | vivo |
| R2-2503526 | User consent for NW-side data collection | NTT DOCOMO, Apple, vivo, Xiaomi |
| R2-2503538 | Discussion on NW side data collection | Samsung |
| R2-2503548 | Discussion on NW side Data Collection | Fujitsu |
| R2-2503562 | Remaining issues on NW side Data Collection | LG Electronics |
| R2-2503571 | Discussion on NW-side data collection | NEC |
| R2-2503590 | Consideration on NW side data collection | CATT |
| R2-2503637 | Discussion on NW side data collection | Xiaomi |
| R2-2503670 | Discussion on NW side data collection | China Telecom |
| R2-2503691 | NW side data collection | Interdigital Inc. |
| R2-2503716 | Remaining issues on NW-sided data collection | Apple |
| R2-2503776 | Further Discussion on Network-Side Data Collection | MediaTek Inc. |
| R2-2503826 | Discussion on NW-side Data Collection | Sharp |
| R2-2503849 | Discussion on NW side data collection framework | ZTE Corporation, Apple, MediaTek, OPPO, Samsung, Lenovo, Xiaomi, CMCC, China Telecom, vivo, NTT DOCOCMO |
| R2-2503851 | Considerations on remaining issues on NW Side Data Collection | ZTE Corporation |
| R2-2503920 | NW side data collection for AI based beam management | Lenovo |
| R2-2503921 | NW side data collection for AI based positioning | Lenovo |
| R2-2503928 | Discussion on NW-side Data Collection for BM | |
| R2-2503967 | Discussion on NW side data collection | Spreadtrum, UNISOC |
| R2-2504101 | Data Collection for Training of NW-side AI/ML Models | Nokia |
| R2-2504111 | Discussion on NW-sided data collection for training | Huawei, HiSilicon |
| R2-2504219 | Discussion on Data Collection for NW-side Model Training | Futurewei Technologies |
| R2-2504354 | Open Issues on Network Side Data Collection | Qualcomm Incorporated |
| R2-2504377 | Discussion on time info for NW side data collection | CMCC |
| R2-2504416 | Remaining Issues on NW side data collection | Kyocera |
| R2-2504464 | Discussion on NW side data collection | HONOR |
| R2-2504488 | Discussion on Remaining RRC open issues for NW-sided data collection | ASUSTeK |
| R2-2504637 | NW-side data collection for beam management and positioning | Ericsson |
| R2-2504644 | Discussion on NW-side data collection framework | Ericsson, Nokia, Huawei, T-Mobile USA, BT Plc. |
| R2-2504651 | Further discussion on NW-Side AI/ML Data Logging Framework | Rakuten Mobile, Inc |
| TDoc | Title | Source |
|---|---|---|
| R2-2503385 | Analysis of solutions for UE side model data collection | NEC |
| R2-2503396 | Discussion on UE side data collection | OPPO |
| R2-2503402 | Discussion on UE side data collection | vivo |
| R2-2503451 | Discussion on RAN impact of UE-side data collection | Xiaomi |
| R2-2503549 | Discussion on Data Collection via UP Tunnel for UE-sided model | Fujitsu |
| R2-2503591 | Consideration on UE side data collection | CATT |
| R2-2503692 | UE side data collection | Interdigital Inc. |
| R2-2503717 | Further discussion on UE-side data collection | Apple |
| R2-2503736 | Discussion on UE-side data collection | LG Electronics Inc. |
| R2-2503739 | Discussion on LCM for UE-sided model | KT Corp. |
| R2-2503777 | Discussion on the Necessity of Non-Standardized Data | Mediatek Inc.,Nokia,Qualcomm Incorporated,Xiaomi,InterDigital Inc. |
| R2-2503850 | Further Considerations on UE Side Data Collection | ZTE Corporation |
| R2-2504226 | Discussion on Data Collection for UE-side Model Training | Futurewei Technologies |
| R2-2504241 | Discussion on UE-sided data collection for training | Huawei, HiSilicon, OPPO, ZTE, NTT DoCoMo, China Unicom, CMCC, China Telecom, Apple, vivo |
| R2-2504355 | On UE Side Data Collection | Qualcomm Incorporated |
| R2-2504378 | Discussion on UE side data collection | CMCC,China Telecom |
| R2-2504614 | Remaining issues on UE-side data collection | Ericsson |
| R2-2504628 | UE side data collection | Samsung R&D Institute UK |
| R2-2504663 | Discussion on UE-sided data collection for AIML Training | Rakuten Mobile, Inc |
| TDoc | Title | Source |
|---|---|---|
| R2-2504379 | Discussion on AIML model transfer delivery | CMCC,China Telecom,CATT,ZTE,Apple,Samsung,Xiaomi |
| R2-2504616 | Discussion on model transfer/delivery | NTT DOCOMO, INC. |
| R2-2504635 | Operators views for the AI_ML model delivery options | BT Plc, Turkcell, T-Mobile, Deutsche Telekom, Orange |
| R2-2504641 | Operators views for the AI_ML model delivery options | BT Plc, Turkcell, T-Mobile, Deutsche Telekom, Orange |
| TDoc | Title | Source |
|---|---|---|
| R2-2503321 | LS on Ambient IoT further progress of RAN3 (R3-252481; contact: Huawei) | RAN3 |
| R2-2503337 | LS on the removal of service type information (S2-2504294; contact: InterDigital) | SA2 |
| R2-2503338 | LS on AIoT device identifier length (S2-2504296; contact: Huawei) | SA2 |
| R2-2503997 | A-IoT MAC running CR | Huawei, HiSilicon |
| R2-2503998 | Remaining A-IoT MAC open issues | Huawei, HiSilicon |
| R2-2504398 | 38.300 running CR for Ambient IoT | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503343 | Open issues on A-IoT paging | Futurewei |
| R2-2503370 | Discussion on A-IoT Paging | LG Electronics Inc. |
| R2-2503404 | Discussion on AIoT Paging | vivo |
| R2-2503419 | Discussion on Paging for Ambient IoT | CATT |
| R2-2503480 | Device behavior for parallel service requests (Joint paper: Option B - no further standard effort, issue 1-1) | Xiaomi, Huawei, CMCC, Spreadtrum, CATT, Apple, China Telecom, Transsion Holdings, vivo, InterDigital, Philips International B.V., Qualcomm Incorporated, NTT DOCOMO, INC. |
| R2-2503481 | Remaining open issues on A-IOT paging procedure | Xiaomi |
| R2-2503489 | AIoT paging aspects | Nokia |
| R2-2503518 | Discussion on issues 1-1 and 1-3 | Ofinno |
| R2-2503550 | Discussions on AIoT paging | Fujitsu |
| R2-2503610 | Ambient-IoT Paging | NEC |
| R2-2503641 | On remaining issues on A-IoT Paging | NTT DOCOMO, INC. |
| R2-2503720 | Discussion on Ambient IoT Paging | Apple |
| R2-2503789 | Discussion on Paging Procedure for Ambient IoT | China Telecom |
| R2-2503864 | Discussion on A-IoT paging | Panasonic |
| R2-2503871 | Discussion on A-IoT paging message format | Tejas Network Limited |
| R2-2503903 | Discussion on paging procedure for Ambient IoT | Lenovo |
| R2-2503963 | Discussion on A-IoT paging | Spreadtrum, UNISOC |
| R2-2503990 | A-IoT paging | Huawei, HiSilicon |
| R2-2504042 | Discussion on Paging for A-IoT | Transsion Holdings |
| R2-2504052 | Considerations on paging for Ambient IoT | Sony |
| R2-2504112 | Details of option A for overall A-IoT MAC procedure (Issue 1-1) | ZTE Corporation, Sanechips, Continental Automotive, Tejas Networks, Nokia, Ofinno, Samsung, Fujitsu, Kyocera, Sony, ETRI, III, Ericsson, Nordic Semiconductor ASA |
| R2-2504150 | Paging Aspects for Ambient IOT | InterDigital |
| R2-2504177 | AIoT Paging: Handling a New Service Request | Philips International B.V. |
| R2-2504215 | Ambient IoT paging message format | MediaTek Inc. |
| R2-2504261 | Remaining aspects of Ambient IoT Paging | Qualcomm Incorporated |
| R2-2504348 | Discussion on A-IoT paging | Fraunhofer HHI, Fraunhofer IIS |
| R2-2504396 | Discussion on A-IoT paging | CMCC |
| R2-2504407 | Discussion on A-IoT paging | KT Corp. |
| R2-2504426 | Discussion on DL messages for Ambient IoT UEs | Ericsson |
| R2-2504465 | Discussion on A-IoT paging | HONOR |
| R2-2504489 | Discussion on Ambient IoT paging message design | ASUSTeK |
| R2-2504532 | Discussion on A-IoT paging | ITL |
| R2-2504543 | Discussions on AIoT paging | Samsung |
| R2-2504572 | Discussion on paging procedure for Ambient-IoT | III |
| R2-2504573 | Discussion on paging procedure for Ambient IoT | OPPO |
| R2-2504580 | A-IoT Paging | CEWiT |
| R2-2504638 | Open issues for A-IoT paging | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2503344 | Open issues on A-IoT random access | Futurewei |
| R2-2503405 | Random Access Procedure for AIoT Device | vivo |
| R2-2503420 | Discussion on the Random Access for A-IoT | CATT |
| R2-2503482 | Remaining open issues on access procedure for A-IOT | Xiaomi |
| R2-2503519 | Discussion of issues 2-4, 2-6, 2-11, 1-4 and a new issue | Ofinno |
| R2-2503527 | Discussion on random access aspects of Ambient IoT | KT Corp. |
| R2-2503551 | Discussions on AIoT Random Access | Fujitsu |
| R2-2503642 | On remaining issues on A-IoT Random Access | NTT DOCOMO, INC. |
| R2-2503664 | Further discussions on A-IoT random access | China Telecom |
| R2-2503721 | Discussion on Random Access for Ambient IoT | Apple |
| R2-2503751 | Discussion on random access for A-IoT | OPPO |
| R2-2503825 | Open issues on random access for Ambient IoT devices | NEC Corporation |
| R2-2503863 | Open issues on random access for AIoT | Nokia |
| R2-2503868 | Discussion on Msg1 transmission for random access | ETRI |
| R2-2503879 | Discussion on A-IoT message format for CBRA and CFRA | Tejas Network Limited |
| R2-2503890 | Discussion on A-IoT random access procedure | Panasonic |
| R2-2503904 | Discussion on random access for Ambient IoT | Lenovo |
| R2-2503952 | A-IoT random access procedure | Huawei, HiSilicon |
| R2-2503960 | Discussion on A-IoT random access | Spreadtrum, UNISOC |
| R2-2503969 | Open issues for A-IoT random access | ZTE Corporation, Sanechips |
| R2-2504062 | Considerations on RACH msg 2 configuration | Sony |
| R2-2504151 | Random Access Procedure for Ambient IOT | InterDigital |
| R2-2504159 | Discussion on UL multiple access | Ericsson |
| R2-2504221 | Views on Random Access Aspects of Ambient IoT | Qualcomm Incorporated |
| R2-2504372 | Further consideration on A-IoT random access | CMCC |
| R2-2504454 | Discussion on random access aspects for Ambient IoT | LG Electronics Inc. |
| R2-2504466 | Discussion on A-IoT random access | HONOR |
| R2-2504490 | Discussion on Ambient IoT random access | ASUSTeK |
| R2-2504536 | Discussion on A-IoT random access | Samsung |
| R2-2504581 | A-IoT Random Access | CEWiT |
| TDoc | Title | Source |
|---|---|---|
| R2-2503345 | Open issues on A-IoT data transmission and other aspects | Futurewei |
| R2-2503406 | AIoT Data Transmission | vivo |
| R2-2503421 | Discussion on the A-IoT Data Transmission | CATT |
| R2-2503483 | Remaining open issues on Data transmission | Xiaomi |
| R2-2503520 | Discussion of new issue: success/failure of D2R message(s) | Ofinno |
| R2-2503552 | Discussions on Data Transmission and Other General Aspects | Fujitsu |
| R2-2503601 | A-IoT Data Transmission | Ericsson |
| R2-2503643 | On remaining issues on A-IoT Data Transmission | NTT DOCOMO, INC. |
| R2-2503665 | A-IoT data transmission | China Telecom |
| R2-2503704 | Remaining issues in data transmission | Apple |
| R2-2503750 | Discussion on AIoT data transmission related functionalities | OPPO |
| R2-2503779 | Ambient-IoT Data transmission | NEC |
| R2-2503870 | Discussion on addressing issue for AS ID assignment and segment retransmission | Panasonic |
| R2-2503886 | AIoT data transmission aspects | Nokia |
| R2-2503961 | Discussion on A-IoT data transmission | Spreadtrum, UNISOC |
| R2-2503970 | Open issues for data transmission and MAC formats | ZTE Corporation, Sanechips |
| R2-2503980 | Discussion on A-IoT data transmission and other general aspects | Lenovo |
| R2-2503991 | A-IoT data transmission | Huawei, HiSilicon |
| R2-2504053 | Considerations on segmentation | Sony |
| R2-2504152 | Remaining Aspects on Data Transmission | InterDigital |
| R2-2504216 | Ambient IoT MAC PDU formats | Mediatek Inc. |
| R2-2504222 | Data Transmission and Other General Aspects of Ambient IoT | Qualcomm Incorporated |
| R2-2504439 | Discussion on data transmission for A-IoT | CMCC |
| R2-2504467 | Discussion on Data Transmission for Ambient IoT | HONOR |
| R2-2504491 | Discussion on the assistance information from device | ASUSTeK |
| R2-2504503 | Discussion on A-IoT data transmission | LG Electronics Inc. |
| R2-2504544 | Discussion on A-IoT data transmission | Samsung |
| R2-2504577 | Discussion on A-IoT data segmentation and transmission | III |
| TDoc | Title | Source |
|---|---|---|
| R2-2503541 | Text proposal of TR 38.744 | OPPO |
| R2-2503542 | Draft text porposal to capture simulation results | OPPO |
| R2-2503778 | Report of [POST129bis][020][AI Mob] Sim. Results Figures (Mediatek) | MediaTek Inc. |
| R2-2503780 | Support of Spatial Domain Prediction for AI Mobility | MediaTek Inc., vivo, CATT, Qualcomm Incorporated, Nokia, Huawei, HiSilicon, Ericsson, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503371 | Discussion on functionality management | vivo |
| R2-2503514 | AI/ML for mobility Configuration and Functionality management | Qualcomm Incorporated |
| R2-2503534 | Discussions on functionality management | NTT DOCOMO, INC. |
| R2-2503543 | Discussion on functionality management for UE sided model | OPPO |
| R2-2503572 | Discussion on AIML mobility functionality management | NEC |
| R2-2503592 | Functionality management of AIML mobility | CATT, Turkcell |
| R2-2503638 | Discussion on inference solution and functionality management for UE sided model | Xiaomi |
| R2-2503656 | Discussion on Inference Reporting for AI/ML-based Mobility | Sharp |
| R2-2503686 | Functionality Management for AI/ML Mobility | Lenovo |
| R2-2503693 | Functionality management for UE sided model for RRM measurement prediction | Interdigital Inc. |
| R2-2503705 | On functionality of UE-sided AI/ML mobility | Apple |
| R2-2503782 | Discussion on Functionality Management for AI Mobility | MediaTek Inc. |
| R2-2503964 | Discussion on Functionality management for AI mobility | Spreadtrum, UNISOC |
| R2-2503983 | Discussion on functionality management for UE-side model | Samsung |
| R2-2504108 | Discussion on functionality management for UE sided model | Huawei, HiSilicon |
| R2-2504131 | Inference and report configuration of UE sided model | Ericsson |
| R2-2504284 | Functionality management for AI mobility | Nokia, Nokia Shanghai Bell |
| R2-2504441 | Discussion on functionality management for UE sided model | CMCC |
| R2-2504459 | Discussion on functionality management for AI mob | ZTE Corporation |
| R2-2504492 | Discussion on functionality management for AIML Mobility | ASUSTeK |
| R2-2504552 | Discussion on measurement report and configuration for UE sided model | KDDI Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503372 | Configuration and report of inference input to network sided model | vivo |
| R2-2503466 | Discussion on AIML mobility Configuration and Report of Inference input to network sided model | NEC |
| R2-2503515 | Configuration and reporting for inference for network-side model | Qualcomm Incorporated |
| R2-2503639 | Discussion on configuration and report for NW sided model | Xiaomi |
| R2-2503687 | Configuration and Report of Inference Input to NW-sided model | Lenovo |
| R2-2503706 | On NW-sided AI/ML mobility | Apple |
| R2-2503984 | Discussion on configuration and report of inference input for NW-side model | Samsung |
| R2-2504109 | Discussion on NW-sided model support | Huawei, HiSilicon |
| R2-2504460 | Discussion on configuration and report of inference input to network sided model | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503373 | Discussion on data collection | vivo |
| R2-2503535 | Discussions on data collection | NTT DOCOMO, INC. |
| R2-2503545 | Discussion on data collection | OPPO |
| R2-2503593 | Discussion on data collection for AIML mobility | CATT, Turkcell |
| R2-2503640 | Discussion on data collection | Xiaomi |
| R2-2503694 | Data collection for RRM measurement prediction | Interdigital Inc. |
| R2-2503707 | On data collection for AI/ML mobility | Apple |
| R2-2504132 | Data collection for network sided and UE sided models | Ericsson |
| R2-2504286 | Considerations on data collection | Nokia |
| R2-2504380 | Discussion on data collection for AI Mob | CMCC |
| R2-2504461 | Discussion on data collection for AI mob | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503465 | Discussion on AIML mobility Performance monitoring | NEC |
| R2-2503516 | Performance monitoring of AI/ML for Mobility | Qualcomm Incorporated |
| R2-2503536 | Discussions on performance monitoring | NTT DOCOMO, INC. |
| R2-2503544 | Discussion on performance monitoring | OPPO |
| R2-2503594 | Discussion on performance monitoring | CATT, Turkcell |
| R2-2503688 | Support of Model Monitoring for AI/ML Mobility | Lenovo |
| R2-2503695 | Performance Monitoring for AI/ML Mobility | Interdigital Inc. |
| R2-2503783 | Discussion on Performance Monitoring for AI Mobility | MediaTek Inc. |
| R2-2503965 | Discussion on Performance monitoring for AI mobility | Spreadtrum, UNISOC |
| R2-2504110 | Discussion on performance monitoring | Huawei, HiSilicon |
| R2-2504285 | Discussion on performance monitoring | Nokia |
| R2-2504297 | Discussion on performance monitoring | Ericsson |
| R2-2504361 | Discussion on Performance Monitoring for AI/ML Mobility | Samsung |
| R2-2504381 | Discussion on performance monitoring for AI Mob | CMCC |
| R2-2504575 | Performance monitoring | TURKCELL |
| TDoc | Title | Source |
|---|---|---|
| R2-2503313 | LS on the RRM measurement metrics for OFDM-based LP-WUR (R1-2503103; contact: Apple) | RAN1 |
| R2-2503612 | RRC Running CR for LP-WUS WUR | vivo (Rapporteur) |
| R2-2503657 | 38.304 Running CR for LP-WUS | CATT |
| R2-2503658 | Summary of [Post129bis][208][LPWUS] Running CR for 38.304 (CATT) | CATT |
| R2-2503758 | Summary of [Post129bis][206] Remaining issue of LP-WUS in MR-DC | ZTE Corporation, Sanechips |
| R2-2503759 | Running 37.340 CR for LP-WUS | ZTE Corporation, Sanechips |
| R2-2503765 | Discussion summary and list of RRC open issue for LP-WUS WUR | vivo |
| R2-2503807 | Running MAC CR for LP-WUS | Apple (Rapporteur) |
| R2-2503808 | Report of [Post129bis][210][LPWUS] Running CR for TS 38.321 (Apple) | Apple (Rapporteur) |
| R2-2503899 | Summary of [Post129bis][218][LPWUS] UE Capabilities (Huawei) | Huawei, HiSilicon |
| R2-2504578 | Introduction of Low-Power Wake-Up Signal and Receiver for NR | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503568 | Discussion on LP-WUS in RRC_IDLE INACTIVE | NEC |
| R2-2503603 | Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode | Samsung |
| R2-2503613 | Discussion on LP-WUS WUR in RRC_IDLE INACTIVE | vivo |
| R2-2503651 | Remaining issues on LP-WUS paging monitoring | Xiaomi Communications |
| R2-2503659 | Remaining issues on LP-WUS in IDLE and INACTIVE | CATT |
| R2-2503763 | Procedure and configuration of LP-WUS for IDLE and INACTIVE mode | ZTE Corporation, Sanechips |
| R2-2503790 | Discussion on LP-WUS in RRC_IDLE and INACTIVE | China Telecom |
| R2-2503809 | Remaining issues of LP-WUS in RRC_IDLE/INACTIVE | Apple |
| R2-2503837 | Remaining issues on LP-WUS in RRC IDLE or INACTIVE | LG Electronics Inc. |
| R2-2503867 | Open issues on LP-WUS in IDLE/INACTIVE mode | Tejas Network Limited |
| R2-2503881 | Discussion on LP-WUS in RRC_IDLE and RRC_INACTIVE | Sharp |
| R2-2503900 | Further discussion on the LP-WUS in RRC_IDLE/INACTIVE mode | Huawei, HiSilicon |
| R2-2503953 | Discussion on prioritizing the frequencies supporting LP-WUS | Huawei, HiSilicon, vivo, CMCC, CATT, Nokia, Samsung, LG Electronics Inc., Apple, Ericsson, OPPO, Sharp, NEC |
| R2-2504003 | Discussion on LP-WUS procedure and configuration | OPPO |
| R2-2504264 | LP-WUS in IDLE and INACTIVE | Nokia |
| R2-2504288 | LP-WUS in Idle and Inactive | Ericsson |
| R2-2504363 | Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes | InterDigital, Inc. |
| R2-2504404 | Further Consideration on LP-WUS operation in IDLE/INACTIVE | CMCC |
| R2-2504468 | Discussion on LP-WUS in RRC_IDLE/INACTIVE | HONOR |
| R2-2504555 | Open issues on LP-WUS operation in IDLE/Inactive state | Qualcomm Incorporated |
| R2-2504603 | Procedure and Configuration of LP-WUS in RRC Idle/ Inactive | Lenovo |
| R2-2504643 | Discussion on the LP-WUS deactivation with RRC dedicated message | NTT DOCOMO INC.. |
| R2-2504677 | Discussion on LP-WUS procedure and configuration | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R2-2503569 | Discussion on LP-WUS RRM | NEC |
| R2-2503604 | RRM measurement relaxation and offloading in RRC Idle Inactive Mode | Samsung |
| R2-2503614 | Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | vivo |
| R2-2503652 | Remaining issues on RRM measurement relaxation for RRC_IDLE_INACTIVE | Xiaomi Communications |
| R2-2503660 | RRM Relaxation and Offloading in RRC_IDLE/INACTIVE | CATT |
| R2-2503791 | Discussion on RRM measurement relaxation and offloading in RRC_IDLE and INACTIVE | China Telecom |
| R2-2503810 | Remaining issues of LP-WUS RRM Measurement | Apple |
| R2-2503838 | Remaining issues on measurement offloading and relaxation | LG Electronics Inc. |
| R2-2503882 | Discussion on RRM measurement relaxation and offloading | Sharp |
| R2-2503902 | RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | Lenovo |
| R2-2504004 | Discussion on RRM measurement in RRC IDLE and INACTIVE | OPPO |
| R2-2504066 | Further discussion on the criteria for RRM measurement relaxation and offloading | Huawei, HiSilicon |
| R2-2504265 | RRM measurement relaxation in RRC_IDLE/INACTIVE | Nokia |
| R2-2504289 | LP-WUS and RRM measurements | Ericsson |
| R2-2504364 | Discussion on RRM measurement relaxation and offloading | InterDigital, Inc. |
| R2-2504365 | Discussion on neighboring cell measurement with LR | InterDigital, Ericsson, Nokia, Sony, Vodafone, KT, Turkcell |
| R2-2504403 | Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE | CMCC |
| R2-2504557 | LP-WUS RRM measurement relaxation and offloading | Qualcomm Incorporated |
| R2-2504565 | RRM measurement relaxation and offloading in RRC IDLEINACTIVE for LP-WUS/WUR | Panasonic |
| R2-2504623 | Remaining issues for LP-WUS RRM | ZTE Corporation, Sanechips |
| R2-2504678 | Discussion on RRM measurement in RRC IDLE and INACTIVE | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R2-2503349 | Discussing on LP-WUS monitoring in Connected mode | Xiaomi |
| R2-2503570 | Discussion on LP-WUS in RRC_CONNECTED | NEC |
| R2-2503605 | Procedures for LP-WUS in RRC Connected Mode | Samsung |
| R2-2503615 | Discussion on LP-WUS WUR in RRC_Connected | vivo |
| R2-2503661 | Analysis on LP-WUS for RRC_CONNECTED | CATT |
| R2-2503764 | Procedures for LP-WUS in RRC_CONNECTED | ZTE Corporation, Sanechips |
| R2-2503811 | Remaining issues of LP-WUS in RRC_CONNECTED | Apple |
| R2-2503819 | Remainng issues on LP-WUS in RRC_CONNECTED | LG Electronics Inc. |
| R2-2503833 | LP-WUS in CONNECTED mode | InterDigital |
| R2-2503869 | Open issues on LP-WUS operation in CONNECTED mode | Tejas Network Limited |
| R2-2503954 | Further discussion on LP-WUS for RRC_CONNECTED mode | Huawei, HiSilicon |
| R2-2504005 | Discussion on support of dual DRX group with LP-WUS in RRC_CONNECTED | OPPO |
| R2-2504290 | LP-WUS in Connected | Ericsson |
| R2-2504291 | LP-WUS and secondary DRX | Ericsson, Huawei, HiSilicon, NEC, LGE, Apple, InterDigital, CATT |
| R2-2504385 | Discussion on LP-WUS operation in CONNECTED mode | CMCC |
| R2-2504469 | Discussion on LP-WUS in RRC_CONNECTED | HONOR |
| R2-2504514 | LP-WUS in RRC_CONNECTED | Nokia, Nokia Shanghai Bell |
| R2-2504556 | Open issues on LP-WUS operation in CONNECTED state | Qualcomm Incorporated |
| R2-2504601 | LP-WUS in RRC Connected Mode | Lenovo |
| R2-2504679 | Discussion on support of dual DRX group with LP-WUS in RRC_CONNECTED | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R2-2503305 | Reply LS on paging enhancement in R19 NES (C1-252548; contact: Huawei) | CT1 |
| R2-2503312 | LS on DCI-based PRACH adaptation (R1-2503086; contact: Ericsson) | RAN1 |
| R2-2503319 | Reply LS on energy saving indication from CN to RAN (R3-252404; contact: Huawei) | RAN3 |
| R2-2503504 | Introduction of Network Energy Savings Enhancements running CR | Huawei, HiSilicon |
| R2-2503607 | Running RRC CR for enhancements for network energy efficiency | Ericsson |
| R2-2503608 | Report of [POST129b][111][NES] (Ericsson) | Ericsson |
| R2-2503708 | Running 38.304 CR for network energy saving | Apple (Rapporteur) |
| R2-2503709 | Summary report of [POST129b][113][NES] 38.304 CR (Apple) | Apple (Rapporteur) |
| R2-2503752 | Summary of [POST129b][121] Initial discussion on UE capabilities in NES | ZTE Corporation, Sanechips |
| R2-2503753 | Draft 38.331 CR for NES UE capability | ZTE Corporation, Sanechips |
| R2-2503754 | Draft 38.306 CR for NES UE capability | ZTE Corporation, Sanechips |
| R2-2504281 | Summary of Comments to 38.321 CR for NES | InterDigital |
| R2-2504282 | Running 38.321 CR for network energy saving | InterDigital |
| TDoc | Title | Source |
|---|---|---|
| R2-2503376 | Discussion on On-Demand SSB | OPPO |
| R2-2503392 | On-demand SSB SCell Operation | Samsung |
| R2-2503407 | Remaining issues on OD-SSB SCell operation | LG Electronics France |
| R2-2503414 | Consideration on on-demand SSB SCell operation | CATT |
| R2-2503573 | Discussion on on-demand SSB | Xiaomi |
| R2-2503609 | Discussion on on-demand SSB for NES | Ericsson |
| R2-2503710 | Remaining issues on on-demand SSB for Scell | Apple |
| R2-2503755 | Remaining issues of on-demand SSB SCell operation | ZTE Corporation, Sanechips |
| R2-2503805 | Remaining issues on on-demand SSB SCell operation | Fujitsu |
| R2-2503824 | Remaining issues of OD-SSB | Rakuten Mobile, Inc |
| R2-2503827 | Discussion on on-demand SSB SCell operation | Sharp |
| R2-2503893 | On demand SSB handling | Nokia, Nokia Shanghai Bell |
| R2-2503916 | Issues on the procedure of on-demand SSB SCell operation | Lenovo |
| R2-2503944 | Discussion on on-demand SSB SCell operation for NES | Huawei, HiSilicon |
| R2-2503988 | Remaining issues on On-demand SSB for SCell | NEC |
| R2-2504036 | Remaining issues of on-demand SSB SCell operation | vivo |
| R2-2504061 | Remaining details on OD-SSB MAC CE | Sony |
| R2-2504242 | Discussion on On-demand SSB SCell Operation | Qualcomm Incorporated |
| R2-2504280 | On demand SSB transmission for SCell | InterDigital |
| R2-2504386 | Discussion on On-demand SSB for Scell | CMCC |
| R2-2504417 | On-demand SSB SCell operation | Panasonic |
| R2-2504418 | Discussion on on-demand SSB SCell operation | NTT DOCOMO, INC. |
| R2-2504540 | Discussion on On-demand SSB | KDDI Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503351 | Discussion on on-demand SIB1 | Xiaomi |
| R2-2503391 | On-demand SIB1 | Samsung |
| R2-2503415 | Consideration on on-demand SIB1 | CATT |
| R2-2503467 | Remaining issues for On-demand SIB1 request and UE behaviour | NEC |
| R2-2503485 | Providing Cell Reselection Assistance information | Lenovo |
| R2-2503502 | Discussion on remaining issues of on-demand SIB1 operation for NES | Huawei, HiSilicon |
| R2-2503636 | Discussion on on-demand SIB1 for NES | Ericsson |
| R2-2503711 | Remaining issues on on-demand SIB1 | Apple |
| R2-2503756 | Remaining issues of on-demand SIB1 | ZTE Corporation, Sanechips |
| R2-2503797 | Open issues in the running CRs for OD-SIB1 | |
| R2-2503806 | Remaining issues on on-demand SIB1 procedure | Fujitsu |
| R2-2503823 | Remaining issues of OD-SIB1 | Rakuten Mobile, Inc |
| R2-2503839 | Remaining issues on OD-SIB1 operation | LG Electronics Inc. |
| R2-2503894 | On demand SIB1 handling | Nokia, Nokia Shanghai Bell |
| R2-2503955 | Discussion on SIBxx validity check during T311 | ITRI, Acer Incorporated |
| R2-2503999 | Consideration on on-demand SIB1 | OPPO |
| R2-2504037 | Remaining issues on OD-SIB1 | vivo |
| R2-2504054 | Remaining details for on-demand SIB1 | Sony |
| R2-2504243 | Discussion on On-demand SIB1 | Qualcomm Incorporated |
| R2-2504278 | On-demand SIB1 request and reception | InterDigital |
| R2-2504387 | Discussion on On-demand SIB1 | CMCC |
| R2-2504419 | Discussion on on-demand SIB1 | NTT DOCOMO, INC. |
| R2-2504470 | Discussion on on-demand SIB1 | HONOR |
| R2-2504493 | Broadcasting status for OD-SIB1 request | ASUSTeK |
| R2-2504533 | Discussion on On-demand SIB1 | KDDI Corporation |
| R2-2504538 | Discussion on Ondemand-SIB1 | KDDI Corporation (TTC) |
| R2-2504604 | Reducing On-demand SIB1 overhead | Fraunhofer IIS, Fraunhofer HHI |
| R2-2504606 | Remaining issues on OD-SIB1 Request | SHARP Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503374 | Summary of [POST129bis][122][NES] CFRA Applicability (OPPO) | OPPO |
| R2-2503393 | Adaptation of common signal channel transmissions | Samsung |
| R2-2503416 | Adaptation of Common signal channel transmissions | CATT |
| R2-2503454 | Discussion on adaptation of common signal channel transmission | OPPO |
| R2-2503468 | Discussion on Adaptation of common signal channel transmissions | NEC |
| R2-2503553 | Adaptation of common signal or channel | Fujitsu |
| R2-2503574 | Discussion on PRACH adaptation | Xiaomi |
| R2-2503712 | Remaining issues on common signal transmission adaptation | Apple |
| R2-2503757 | Remaining issues of common signal/channel adaption | ZTE Corporation, Sanechips |
| R2-2503828 | Discussion on PRACH adaptation | Sharp |
| R2-2503895 | Adaptation of common signals | Nokia, Nokia Shanghai Bell |
| R2-2503945 | Discussion on adaptation of common signals/channels transmissions | Huawei, HiSilicon |
| R2-2503968 | Issue for additional PRACH resources with multiple initial BWPs | Spreadtrum, UNISOC |
| R2-2504038 | Discussion on adaptation of common signal transmissions | vivo |
| R2-2504055 | RA-RNTI issue and RACH adaptations | Sony |
| R2-2504244 | Discussion on Adaptation of Common Signal/Channel Transmissions | Qualcomm Incorporated |
| R2-2504279 | Time domain adaptation of common signalling and channels | InterDigital |
| R2-2504388 | Discussion on Common signalling adaptation | CMCC |
| R2-2504420 | Discussion on adaptation of common signal and channel | NTT DOCOMO, INC. |
| R2-2504427 | Adaptation of common signal/channel transmissions for NES | Ericsson |
| R2-2504429 | [DRAFT] Reply LS on DCI-based PRACH adaptation | Ericsson |
| R2-2504471 | Discussion on adaptation of common signal/channel transmissions | HONOR |
| R2-2504494 | Discussion on PRACH adaptation | ASUSTeK |
| R2-2504579 | Remaining issues on common signal and channel transmissions adaptation | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2503310 | Reply LS on number of beam measurements in the measurement report MAC CE (R1-2503077; contact: Fujitsu) | RAN1 |
| R2-2503311 | LS on the support of semi-persistent CSI-RS resource for LTM CSI acquisition for candidate cells (R1-2503079; contact: Fujitsu) | RAN1 |
| R2-2503320 | Reply LS for Reply LS on security handling for inter-CU LTM in non-DC cases (R3-252449; contact: CATT) | RAN3 |
| R2-2503412 | Draft 306 running CR for UE capability for Mob Ph4 | CATT |
| R2-2503413 | Draft 331 running CR for UE capability for Mob Ph4 | CATT |
| R2-2503616 | Running MAC CR for Mob Ph4 | vivo (Rapporteur) |
| R2-2503679 | Introduction of NR mobility enhancements Phase 4 in TS 37.340 | China Telecom |
| R2-2503680 | List of 37.340 open issues for R19 mobility | China Telecom |
| R2-2503732 | Introduction of NR mobility enhancements Phase 4 in TS 38.300 | Apple |
| R2-2503733 | Report of [POST129b][119][Mob] Stage-2 CR 38.300 (Apple) | Apple |
| R2-2503766 | Discussion summary and list of MAC open issue for Mob Ph4 | vivo |
| R2-2503785 | Introduction of event-triggered meas report for RRC spec | Huawei, HiSilicon |
| R2-2503786 | Summary of [POST128][116][MOB] RRC running CR (Huawei) | Huawei, HiSilicon |
| R2-2504125 | Running RRC CR for inter-CU LTM and CLTM | Ericsson |
| R2-2504126 | RRC open issues list for mobility | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503381 | Some issues for Inter-CU LTM | Lenovo Information Technology |
| R2-2503409 | Discussion on Inter-CU LTM | CATT |
| R2-2503479 | Fast recovery for inter-CU LTM | MediaTek Inc. |
| R2-2503486 | Discussion on open issues for inter-CU LTM | OPPO |
| R2-2503532 | Remaining issues of inter-CU LTM | Xiaomi |
| R2-2503617 | Discussion on inter-CU LTM | vivo |
| R2-2503681 | Discussion on remaining issues of inter-CU LTM | China Telecom |
| R2-2503744 | Discussion on issues for supporting inter-CU LTM | Sharp |
| R2-2503747 | Discussion on inter-CU LTM | Fujitsu |
| R2-2503804 | Discussion on inter-CU LTM | Qualcomm Incorporated |
| R2-2503822 | Discussion on inter-CU LTM | NEC |
| R2-2503858 | Inter-CU LTM and Fast Recovery | Ericsson |
| R2-2503898 | Discussion on inter-CU LTM | DENSO CORPORATION |
| R2-2504027 | Discussion on inter-CU LTM | ZTE Corporation |
| R2-2504043 | Discussion LTM fast recover of inter-CU LTM cell switch | Transsion Holdings |
| R2-2504048 | Remaining issues on inter-CU LTM | LG Electronics Inc. |
| R2-2504137 | Further remaining issues for Inter-CU LTM | Nokia |
| R2-2504145 | Inter-CU LTM | Huawei, HiSilicon |
| R2-2504168 | Remaining issues in Inter-CU LTM | Apple |
| R2-2504194 | Discussion on Inter-CU LTM fast recovery | InterDigital Washington DC |
| R2-2504262 | Discussion on open issues of inter-CU LTM | Ofinno |
| R2-2504330 | Remaining issues of Inter-CU LTM | Rakuten Mobile, Inc |
| R2-2504389 | Discussion on Inter-CU LTM | CMCC |
| R2-2504423 | Remaining open issues on inter-CU LTM | ETRI |
| R2-2504516 | Discussion on inter-CU LTM | NTT DOCOMO, INC. |
| R2-2504542 | Further Considerations to Support Inter-CU LTM | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503410 | L1 event triggered measurement reporting | CATT |
| R2-2503435 | Remaining issues of L1 event triggered measurement reporting | Xiaomi |
| R2-2503469 | Remaining issues on event triggered L1 MR | MediaTek Inc. |
| R2-2503484 | Discussion on L1 measurement | Lenovo |
| R2-2503487 | Open issues for L1 event triggered measurement reporting | OPPO |
| R2-2503554 | Discussions on L1 event triggered measurement reporting | Fujitsu |
| R2-2503618 | Discussion on LTM measurement event evaluation and reporting | vivo |
| R2-2503682 | Discussion on remaining issues of L1 event triggered measurement reporting | China Telecom |
| R2-2503745 | Discussion on issues for supporting L1 event triggered measurement reporting | Sharp |
| R2-2503772 | Discussion on L1 event triggered measurement reporting | Baicells Technologies Co. Ltd |
| R2-2503802 | Discussion on event triggered L1 measurement reporting for LTM | Qualcomm Incorporated |
| R2-2503812 | Remaining issues of LTM measurement | Apple |
| R2-2503859 | Discussion on L1 event-based measurements | Ericsson |
| R2-2503861 | Discussion on truncated L1 measurement reporting | Panasonic |
| R2-2503989 | Remaining issues on MR MAC CE | NEC |
| R2-2504028 | Discussion on L1 event triggered measurement reporting | ZTE Corporation |
| R2-2504044 | Discussion on L1 event triggered measurement reporting | Transsion Holdings |
| R2-2504115 | Discussion on L1 event-triggered measurement reporting | Huawei, HiSilicon |
| R2-2504120 | Discussion on the support of mTRP in event-triggered LTM | Huawei, HiSilicon, Nokia, NTT Docomo, OPPO, ZTE |
| R2-2504135 | Final Details on L1 Measurement Reporting Enhancements for Rel-19 LTM | Nokia |
| R2-2504181 | LCP for LTM measurement report MAC CE | Interdigital, Inc. |
| R2-2504263 | Discussion on L1 event triggered measurement report | Ofinno |
| R2-2504331 | Remaining issues of L1 event triggered measurement reporting | Rakuten Mobile, Inc |
| R2-2504402 | Discussion on L1 event triggered measurement reporting | CMCC |
| R2-2504408 | Remaining issues of event-triggered L1 measurement reporting for LTM | Kyocera |
| R2-2504422 | Discussion on L1 event triggered measurement reporting for LTM | KDDI Corporation |
| R2-2504445 | Remaining Issues of L1 Event Triggered Measurement Report | Samsung |
| R2-2504472 | Discussion on measurement event evaluation and report | HONOR |
| R2-2504495 | Discussion on event-triggered L1 MR MAC CE | ASUSTeK |
| R2-2504610 | Discussion on LTM event-triggered measurement reporting | Fraunhofer HHI, Fraunhofer IIS |
| R2-2504639 | Resolving MAC open issues for LTM event triggered MR | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2503382 | CLTM Scenarios and remaining points | Lenovo Information Technology |
| R2-2503411 | Discussion on Conditional Intra-CU LTM | CATT |
| R2-2503455 | Discussion on Conditional Intra CU LTM | Lekha Wireless Solutions |
| R2-2503470 | Further discussion on conditional LTM | MediaTek Inc. |
| R2-2503488 | Open issues for conditional LTM | OPPO |
| R2-2503533 | Discussion on conditional LTM | Xiaomi |
| R2-2503555 | Discussion on conditional Intra-CU LTM | Fujitsu |
| R2-2503619 | Discussion on conditional LTM | vivo |
| R2-2503683 | Discussion on remaining issues of CLTM | China Telecom |
| R2-2503746 | Discussion on issues for supporting conditional LTM | Sharp |
| R2-2503773 | Discussion on Conditional intra-CU LTM remaining issues | Baicells Technologies Co. Ltd |
| R2-2503803 | Discussion on intra-CU conditional LTM | Qualcomm Incorporated |
| R2-2503813 | Remaining issues of conditional LTM | Apple |
| R2-2503860 | Open issues for Conditional LTM | Ericsson |
| R2-2503931 | Remaining Open issues for CLTM | NEC |
| R2-2503956 | Discussion on conditional LTM | ITRI |
| R2-2504029 | Discussion on conditional intra-CU LTM | ZTE Corporation |
| R2-2504045 | Discussion on remaining issues of conditional intra-CU LTM | Transsion Holdings |
| R2-2504049 | Remaining issues on CLTM | LG Electronics Inc. |
| R2-2504146 | Intra-CU conditional LTM | Huawei, HiSilicon |
| R2-2504182 | Conditional LTM. | Interdigital, Inc. |
| R2-2504269 | Discussion on open issues of CLTM | Ofinno |
| R2-2504283 | Discussion on conditional LTM | Nokia |
| R2-2504329 | Remaining issues of Conditional LTM | Rakuten Mobile, Inc |
| R2-2504390 | Discussion on conditional LTM | CMCC |
| R2-2504412 | Remaining issue of Conditional intra-CU LTM | Kyocera |
| R2-2504424 | Remaining open issues on conditional LTM | ETRI |
| R2-2504446 | Remaining Issues of Conditional Intra-CU LTM | Samsung |
| R2-2504473 | Discussion on conditional LTM | HONOR |
| R2-2504496 | Discussion on TA handling for C-LTM | ASUSTeK |
| R2-2504531 | Discussion on Conditional intra-CU LTM | ITL |
| TDoc | Title | Source |
|---|---|---|
| R2-2503323 | Reply LS on uplink rate control (R3-252491; contact: Meta) | RAN3 |
| R2-2503328 | Reply LS on UE assistance information (R4-2504972; contact: Nokia) | RAN4 |
| R2-2503336 | LS reply on uplink rate control (S2-2504252; contact: vivo) | SA2 |
| R2-2503339 | LS on the accuracy of PDU Set size and data burst size indication (S4-250736; contact: Qualcomm) | SA4 |
| R2-2503340 | LS on Indicating Time to the Next Data Burst (TTNB) (S4-250737; contact: Qualcomm) | SA4 |
| R2-2503360 | Introduction to R19 XR enhancements | Qualcomm Incorporated |
| R2-2503361 | List of open issues in MAC | Qualcomm Incorporated |
| R2-2503362 | Draft reply LS to SA4 on accuracy of PDU Set size and data burst size | Qualcomm Incorporated |
| R2-2503363 | Draft reply LS to SA4 on accuracy of TTNB | Qualcomm Incorporated |
| R2-2503436 | Draft 38.306 CR for Rel-19 XR UE capabilities | Xiaomi |
| R2-2503437 | Draft 38.331 CR for Rel-19 XR UE capabilities | Xiaomi |
| R2-2503438 | Open issues of Rel-19 XR UE capabilities | Xiaomi |
| R2-2503563 | Rapporteur Inputs | Nokia, Qualcomm (Rapporteurs) |
| R2-2503564 | Draft Stage 2 CR for XR | Nokia (Rapporteur) |
| R2-2503565 | Stage 2 Open Issues | Nokia (Rapporteur) |
| R2-2503620 | RLC running CR for R19 XR | vivo |
| R2-2503696 | PDCP running CR for R19 XR | LG Electronics Inc. (Rapporteur) |
| R2-2503697 | Discussion of [POST129bis][504][XR] PDCP running CR | LG Electronics Inc. (Rapporteur) |
| R2-2503767 | Discussion summary and list of RLC open issue for R19 XR | vivo |
| R2-2503787 | Running RRC CR for R19 XR | Huawei, HiSilicon |
| R2-2503788 | Summary of [POST129bis][503][XR] RRC running CR (Huawei) | Huawei, HiSilicon |
| R2-2504609 | Discussion on SA2 LS on UL rate control | vivo |
| R2-2504649 | Draft LS to SA2 on gNB PDU Set based handling without QoS parameters | Futurewei |
| TDoc | Title | Source |
|---|---|---|
| R2-2503364 | Discussion on measurement gap enhancements | Qualcomm Incorporated |
| R2-2503425 | Discussion on RRM Measurement Gaps Restrictions Related Enhancements | CATT |
| R2-2503494 | Discussion on Measurement Gap enhancements | OPPO |
| R2-2503508 | UAI and Measurement Gap Enhancements | Sharp |
| R2-2503521 | RRM Measurement Gaps Enhancements for XR | Ofinno |
| R2-2503621 | Discussion on RRM measurement gaps enhancements | vivo |
| R2-2503653 | Discussion on RRM measurement gaps enhancements of XR traffic | Xiaomi Communications |
| R2-2503792 | Discussion on RRM measurement gaps/restrictions related enhancements | China Telecom |
| R2-2503892 | Enabling TX/RX for XR during measurement gaps/restrictions | Lenovo |
| R2-2503971 | Measurement gap enhancements for XR | ZTE Corporation, Sanechips |
| R2-2504121 | Discussion on UAI for MG skipping | Huawei, HiSilicon |
| R2-2504341 | Discussion on UE Assistance Information (UAI) for Measurement Gaps | Ericsson |
| R2-2504409 | RRM measurement gaps/restrictions related enhancements | Nokia, Nokia Shanghai Bell |
| R2-2504436 | Discussion on UAI for Measurement Gap Enhancements | Samsung |
| R2-2504442 | Discussion on RAN4 LS on UE assistance information | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503365 | Discussion on LCP enhancements | Qualcomm Incorporated |
| R2-2503426 | Consideration on LCP Enhancement | CATT |
| R2-2503452 | Discussion on LCH priority adjustment for XR | OPPO |
| R2-2503475 | Remaining issues on LCP enhancement for XR | LG Electronics Inc. |
| R2-2503509 | Open Issues on LCP Enhancements | Sharp |
| R2-2503522 | LCP Enhancements for XR | Ofinno |
| R2-2503622 | Discussion on Bj adjustments for LCH priority-adjusted data transmission | vivo |
| R2-2503654 | Discussion on LCP enhancements of XR traffic | Xiaomi Communications |
| R2-2503690 | TP for using additional LCP priority for SR priority determination | Huawei, HiSilicon, ZTE Corporation, Samsung, Sharp, NEC, CATT |
| R2-2503698 | Discussions on Delay-based LCP Enhancements | Apple |
| R2-2503793 | Discussion on Remaining Issues of LCP Enhancements | China Telecom |
| R2-2503883 | Remaining issues on LCP enhancements | NEC |
| R2-2503891 | Open issues on Intra-UE prioritization/LCP enhancements | Lenovo |
| R2-2503957 | Discussion on enhanced LCP for XR | ITRI |
| R2-2503972 | LCP enhancements for XR | ZTE Corporation, Sanechips |
| R2-2504308 | Remaining open issues on LCP in XR | Huawei, HiSilicon |
| R2-2504373 | Further consideration on LCP enhancement for XR | CMCC |
| R2-2504410 | LCP Enhancements for XR | Nokia, Nokia Shanghai Bell |
| R2-2504537 | discussion on LCP enhancements for XR | ETRI |
| R2-2504596 | Discussion on Bj enhancement | Ericsson, InterDigital, LG Electronics, Fujitsu |
| R2-2504608 | Discussion on LCP enhancement | Ericsson |
| R2-2504619 | Finalising LCP design for XR Ph3 | Samsung R&D Institute UK |
| TDoc | Title | Source |
|---|---|---|
| R2-2503366 | Discussion on DSR enhancements | Qualcomm Incorporated |
| R2-2503427 | Consideration on DSR Enhancement | CATT |
| R2-2503453 | Discussion on DSR enhancements for XR | OPPO |
| R2-2503476 | Remaining issues on DSR enhancement for XR | LG Electronics Inc. |
| R2-2503510 | Open issues on DSR Enhancements | Sharp |
| R2-2503556 | Discussions on DSR enhancements | Fujitsu |
| R2-2503623 | Remaining issues on DSR enhancements for XR | vivo |
| R2-2503655 | Discussion on DSR enhancements of XR traffic | Xiaomi Communications |
| R2-2503699 | On Data Volume Calculations for Rel-19 DSR | Apple |
| R2-2503794 | Discussion on Remaining Issues of DSR Enhancements | China Telecom |
| R2-2503834 | DSR enhancements for UL scheduling | InterDigital |
| R2-2503885 | Remaining issues on DSR enhancements | NEC |
| R2-2503912 | Enhanced delay status reporting for XR | Lenovo |
| R2-2503973 | DSR enhancements for XR | ZTE Corporation, Sanechips |
| R2-2504113 | Remaining open issues on DSR enhancements in XR | Huawei, HiSilicon |
| R2-2504374 | Further consideration on DSR enhancement for XR | CMCC |
| R2-2504411 | DSR Enhancements for XR | Nokia, Nokia Shanghai Bell |
| R2-2504435 | Remaining Issues on DSR enhancements in Rel-19 XR | Samsung |
| R2-2504474 | Discussion on DSR enhancements | HONOR |
| R2-2504518 | Discussion on DSR enhancements for XR | DENSO CORPORATION |
| R2-2504574 | Discussion on XR DSR enhancements | III |
| R2-2504598 | Discussion on DSR enhancements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503367 | Discussion on RLC enhancements | Qualcomm Incorporated |
| R2-2503428 | Further consideration on XR-specific RLC Enhancement | CATT |
| R2-2503439 | RLC AM retransmission enhancements | Xiaomi |
| R2-2503493 | Discussion on RLC re-transmission related enhancements | OPPO |
| R2-2503507 | Discussion on RLC Enhancements for XR | Samsung |
| R2-2503511 | Open Issues on RLC Enhancements | Sharp |
| R2-2503557 | Discussions on RLC enhancements | Fujitsu |
| R2-2503566 | RLC enhancements | Nokia, Nokia Shanghai Bell |
| R2-2503600 | Considerations on open issues for RLC enhancements | KDDI Corporation (TTC) |
| R2-2503624 | Discussion on RLC remaining issues for XR | vivo |
| R2-2503635 | Discussion on RLC AM Enhancements | CANON Research Centre France |
| R2-2503700 | Views on Avoidance of Unnecessary RLC Retransmissions | Apple |
| R2-2503701 | Discussions on Fast RLC Retransmission | Apple |
| R2-2503795 | Discussion on Remaining Issues of RLC AM Enhancements | China Telecom |
| R2-2503818 | Details on XR RLC autonomous retransmission | Quectel |
| R2-2503830 | Remaining open issues on RLC enhancements for XR | LG Electronics Inc. |
| R2-2503835 | Discussion on RLC enhancements | InterDigital |
| R2-2503913 | AM RLC enhancement | Lenovo |
| R2-2503974 | RLC enhancements for XR | ZTE Corporation, Sanechips |
| R2-2504032 | Remaining issues on RLC AM enhancement | NEC |
| R2-2504056 | Timely retransmissions for RLC AM | Sony, Canon |
| R2-2504118 | Discussion on RLC AM enhancements | Huawei, HiSilicon |
| R2-2504342 | Discussion on UE Capabilities for Unnecessary Retransmission Avoidance | Ericsson, Qualcomm Incorporated, ZTE Corporation, MediaTek Inc., Xiaomi |
| R2-2504401 | Discussion on the left issue of RLC enhancements | CMCC |
| R2-2504475 | Discussion on RLC enhancements | HONOR |
| R2-2504519 | Discussion on RLC enhancements | DENSO CORPORATION |
| R2-2504666 | RLC enhancements | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R2-2503368 | Discussion on XR rate control | Qualcomm Incorporated, MediaTek Inc. |
| R2-2503429 | Discussion on XR Rate Control | CATT |
| R2-2503440 | XR rate control | Xiaomi |
| R2-2503512 | Open Issues on Rate Control | Sharp |
| R2-2503523 | XR Rate Control | Ofinno |
| R2-2503558 | Discussions on XR rate control | Fujitsu |
| R2-2503625 | Discussion on remaining issues of XR rate control | vivo |
| R2-2503702 | Views on Remaining Issues of XR Uplink Rate Control | Apple |
| R2-2503796 | Discussion on Remaining Issues of XR Rate Control | China Telecom |
| R2-2503831 | Remaining open issues on rate control signaling for XR | LG Electronics Inc. |
| R2-2503836 | Discussion on UL congestion signaling | InterDigital |
| R2-2503889 | Uplink rate control for XR | NEC |
| R2-2503975 | XR Rate control details | ZTE Corporation, Sanechips |
| R2-2504000 | Discussion on XR Rate Control | OPPO |
| R2-2504119 | Discussion on XR rate control | Huawei, HiSilicon |
| R2-2504343 | More Views on XR Rate Control | Ericsson |
| R2-2504375 | Further consideration on XR rate control and query | CMCC |
| R2-2504434 | Discussion on UL rate control for Rel-19 XR | Samsung |
| R2-2504457 | Closing the Loop on XR Rate Control | Nokia, Nokia Shanghai Bell |
| R2-2504476 | Discussion on XR rate control | HONOR |
| R2-2504599 | XR Rate Control | Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R2-2503358 | Introduction of LTE TN to NR NTN Mobility UE Capability | vivo |
| R2-2503463 | Introduction of LTE TN to NR NTN IDLE mode mobility | CATT |
| R2-2504077 | Running 38.304 CR for NR NTN | ZTE Corporation, Sanechips |
| R2-2504078 | Remaining 304 open issues for NR NTN | ZTE Corporation, Sanechips |
| R2-2504096 | Introduction of stage 2 for LTE TN to NR NTN idle mode mobility | Samsung |
| R2-2504170 | Open issues of Rel-19 NR NTN UE capabilities | Apple |
| R2-2504171 | Draft CR for Rel-19 NR NTN UE capabilities | Apple |
| R2-2504530 | Introduction of LTE TN to NR NTN IDLE mode mobility | CATT |
| R2-2504629 | Stage 2 Running CR for NR NTN phase 3 | THALES |
| R2-2504630 | Discussion on NTN MBS broadcast description in Stage 2 CR | THALES |
| R2-2504632 | Discussion to align NR NTN k-Mac with IoT NTN TDD k-Mac | THALES |
| R2-2504656 | Running RRC CR for NR NTN phase 3 | Ericsson |
| R2-2504659 | Remaining RRC open issues for NR NTN Rel-19 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503352 | Further Discussion on DL Coverage in NTN | vivo |
| R2-2503458 | Discussion on downlink coverage enhancements | CATT |
| R2-2503459 | Discussion on the need of cell (re)selection enhancement for DL CE | CATT |
| R2-2503495 | Discussion on DL coverage enhancement | Xiaomi |
| R2-2503559 | Discussions on downlink coverage enhancement | Fujitsu |
| R2-2503671 | The consideration of location based SMTC in NR NTN | China Telecom |
| R2-2503884 | Discussion on NR NTN downlink coverage enhancements | DENSO CORPORATION |
| R2-2503905 | Further considerations on NR NTN DL-CE | Lenovo |
| R2-2503926 | Discussion on NTN downlink coverage enhancement | Nokia, Nokia Shanghai Bell |
| R2-2503943 | Discussion on DL coverage enhancements | Huawei, HiSilicon, Turkcell |
| R2-2503958 | Discussions on the assistance information for supporting location-based SMTC selection | ITRI |
| R2-2504006 | Discussion on DL coverage enhancement for NTN | OPPO |
| R2-2504010 | Remaining issues on DL CE in NR NTN | ETRI |
| R2-2504035 | Details on SMTC enhancement | NEC |
| R2-2504057 | SMTC impacts due to NTN downlink coverage enhancements | Sony |
| R2-2504079 | Consideration on downlink coverage enhancements | ZTE Corporation, Sanechips |
| R2-2504172 | DL coverage enhancement in NTN | Apple |
| R2-2504178 | Downlink coverage enhancement for NTN | InterDigital Washington DC |
| R2-2504207 | Open issues on Downlink Coverage Enhancement | Samsung |
| R2-2504312 | Discussion on beam hopping with multiple SMTC offsets | Qualcomm Incorporated |
| R2-2504357 | Discussion on Downlink Coverage Enhancements | Sharp |
| R2-2504400 | Analysis on DL coverage enhancements due to extended SSB periodicity | CMCC |
| R2-2504506 | Further consideration on downlink coverage enhancements | NERCDTV |
| R2-2504571 | Discussion on Downlink Coverage Enhancements | CSCN, Huawei, HiSilicon, ZTE corporation, Sanechips, CATT |
| R2-2504595 | Discussion on downlink coverage enhancement | LG Electronics Inc. |
| R2-2504653 | DL coverage enhancements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2504080 | Consideration on uplink capacity enhancements | ZTE Corporation, Sanechips |
| R2-2504183 | Discussion on Uplink Capacity/Throughput Enhancement for NTN | InterDigital Washington DC |
| R2-2504276 | Discussion on Uplink Capacity Enhancements | Huawei, HiSilicon, Turkcell |
| R2-2504352 | On RAN2 aspects for Uplink OCC | Samsung |
| R2-2504391 | Discussion on uplink capacity/throughput enhancement for NR NTN | CMCC |
| R2-2504511 | Discussion on UL Capacity and Throughput Enhancement | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R2-2503353 | Remaining Issues on MBS Broadcast Provision in NTN | vivo |
| R2-2503460 | Further discussion on support of broadcast service in NR NTN | CATT |
| R2-2503560 | Discussions on supporting broadcast service | Fujitsu |
| R2-2503672 | The signaling design of service area for PWS | China Telecom |
| R2-2503748 | Remaining issues on the support of broadcast service in NTN | ETRI |
| R2-2503749 | Discussion on providing MBS service area in NTN network | OPPO |
| R2-2503906 | Some remaining issues for MBS broadcast in NR NTN | Lenovo |
| R2-2503907 | Further considerations on ETWS support in NR NTN | Lenovo |
| R2-2504063 | Discussion on the remaining issues for the intended service area | Xiaomi |
| R2-2504081 | Consideration on broadcast service ehancements | ZTE Corporation, Sanechips |
| R2-2504134 | Open issues for MBS in Rel-19 NR NTN | Nokia, Nokia Shanghai Bell |
| R2-2504147 | Discussion on MBS broadcast over NTN | Huawei, HiSilicon, Turkcell |
| R2-2504173 | Discussion on broadcast service continuity over NTN | Apple, Lenovo, ZTE Corporation, Sanechips, Samsung, Huawei, HiSilicon |
| R2-2504201 | Remaining issues for MBS service continuity over NTN | Continental Automotive |
| R2-2504208 | Open issues on Broadcast service area | Samsung |
| R2-2504311 | MBS broadcast service continuity | Qualcomm Incorporated |
| R2-2504356 | Remaining issues on intended service area | Sharp |
| R2-2504392 | Considerations on broadcast service for NR NTN | CMCC |
| R2-2504421 | Discussion on Supporting of MBS Broadcast Service | TCL |
| R2-2504477 | Discussion on the support of broadcast service | HONOR |
| R2-2504529 | Discussion on support for broadcast service in NTN | LG Electronics Inc. |
| R2-2504652 | Support for broadcast services in NR NTN | Ericsson |
| R2-2504662 | MBS signalling details in NR NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503986 | Regenerative payload for NTN for NR Ph3 | TOYOTA ITC |
| R2-2504033 | Stage 2 updates for regenerative payload | NEC |
| R2-2504058 | Satellite switch with re-sync in regenerative payload | Sony |
| R2-2504064 | Discussion on the t-service for the regenerative payload | Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R2-2503673 | NTN mobility redirection signalling design | China Telecom |
| R2-2504007 | Discussion on dedicated priority via RRCConnectionRelease | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R2-2503306 | Reply LS on maximum warning message size (C4-251432; contact: CICT Mobile) | CT4 |
| R2-2504068 | RRC Running CR for IoT NTN | Huawei, HiSilicon |
| R2-2504069 | RRC open issue list for IoT NTN | Huawei, HiSilicon |
| R2-2504140 | Remaining Open Issues for idle mode operation for IoT-NTN (TS 36.304) | Nokia,Nokia Shanghai Bells |
| R2-2504149 | Running CR for TS36.304 for IoT-NTN | Nokia Solutions & Networks (I) |
| R2-2504321 | UE capability Running CR for Rel-19 IoT NTN | Qualcomm Inc. |
| R2-2504525 | MAC Running CR for Rel-19 IoT NTN | MediaTek Inc. |
| R2-2504526 | Remaining MAC open issues in IoT NTN | MediaTek Inc. |
| R2-2504631 | Discussion to align IoT NTN k-Mac with IoT NTN TDD k-Mac | THALES |
| R2-2504646 | Draft Introduction of IoT NTN phase 3 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503346 | Discussion on Store and Forward operation | Xiaomi |
| R2-2503354 | Further Discussion on S&F Operation | vivo |
| R2-2503496 | Remaining S&F Open Issues | PANASONIC |
| R2-2503499 | Remaining issues for S&F operation in IoT NTN | ZTE Corporation, Sanechips |
| R2-2503528 | Discussion on Store & Forward satellite operation | OPPO |
| R2-2503598 | Discussion on Store & Forward satellite operation | TCL |
| R2-2503674 | Remaining issues for IoT NTN S&F | China Telecom |
| R2-2503768 | Discussion on Store & Forward operation | DENSO CORPORATION |
| R2-2503798 | Open issues on the S&F mode transition time | |
| R2-2503908 | Mode transition time for S&F operation | Lenovo |
| R2-2504034 | Remaining issues on S&F | NEC |
| R2-2504046 | Discussion on support of Store&Forward | Transsion Holdings |
| R2-2504090 | Open issues on Store and Forward operation | Samsung |
| R2-2504097 | Discussion on Paging and Mode Switching | Toyota ITC |
| R2-2504138 | On RAN2 aspects of SF Operation | Nokia , Nokia Shanghai Bells |
| R2-2504174 | Support of S&F operation in IoT NTN | Apple |
| R2-2504179 | Store and Forward open issues | Interdigital, Inc. |
| R2-2504202 | Further considerations on S&F operations | Continental Automotive |
| R2-2504277 | Further consideration on Store and Forward | Huawei, HiSilicon, Turkcell |
| R2-2504317 | Switching of S&F mode | Qualcomm Incorporated |
| R2-2504351 | CIoT UP solution for Store & Forward satellite operation | SHARP Corporation |
| R2-2504366 | Discussion on RAN2 impacts due to MME-configured satellite list | CATT, Google, Sateliot, Thales |
| R2-2504367 | Discussion on IoT NTN Store and Forward | CMCC |
| R2-2504478 | Discussion on the Store and Forward satellite operation | HONOR |
| R2-2504497 | Discussion on time information for S&F | ASUSTeK |
| R2-2504527 | RAN2 impact on S&F mode | MediaTek Inc. |
| R2-2504550 | Remaining issues on Store and Forward satellite operation | ETRI, Korea University |
| R2-2504617 | Discussion on “S&F Monitoring List” and “S&F Wait Timer” and potential RAN2 impacts | Sateliot, Thales, Novamint |
| R2-2504654 | Support for store and forward in IoT NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503347 | Discussion on uplink capacity enhancements for IoT NTN | Xiaomi |
| R2-2503355 | Further Discussion on CB-msg3-EDT Mechanism | vivo |
| R2-2503461 | Discussion on open issues for CB-Msg3 EDT | CATT |
| R2-2503478 | Further discussion on CB-Msg3 and Msg-4 enhancement | NTU |
| R2-2503500 | Remaining issues for CB-msg3-EDT in IoT NTN | ZTE Corporation, Sanechips |
| R2-2503529 | Discussion on CB-msg3 EDT and msg4 enhancement | OPPO |
| R2-2503599 | Discussion on UL Capability Enhancement for IOT NTN | TCL |
| R2-2503662 | Further discussion on UL capacity enhancement for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2503675 | Discussion of UL capacity in IoT NTN | China Telecom |
| R2-2503880 | Discussion on UL Capacity Enhancement for IoT-NTN | NEC |
| R2-2503909 | EDT for uplink capacity enhancement in NTN | Lenovo |
| R2-2503959 | Remaining issues on CB-msg3-EDT | Spreadtrum, UNISOC |
| R2-2504047 | Discussion on uplink capacity enhancement | Transsion Holdings |
| R2-2504065 | Further consideration on UL capacity enhancement | Huawei, HiSilicon, Turkcell |
| R2-2504091 | On procedures and open issues for CB-Msg3-EDT | Samsung |
| R2-2504098 | Discussion on Diversity Slotted ALOHA Randomization | Toyota ITC |
| R2-2504175 | Uplink capacity enhancement in IoT NTN | Apple |
| R2-2504180 | CB-EDT | Interdigital, Inc. |
| R2-2504318 | CB-Msg3-EDT and Msg4 multicast | Qualcomm Incorporated |
| R2-2504338 | IoT-NTN uplink capacity enhancement | Nordic Semiconductor ASA |
| R2-2504393 | Further discussion on uplink capacity enhancement for IoT-NTN | CMCC |
| R2-2504479 | Discussion on UL capacity enhancement | HONOR |
| R2-2504528 | Discussion on CB-Msg3 procedure | MediaTek Inc. |
| R2-2504645 | UL capacity enhancements for IoT NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503348 | PWS support for NB-IoT over NTN | Xiaomi |
| R2-2503356 | Remaining Issues on PWS Support for NB-IoT | vivo |
| R2-2503501 | Remaining issues for PWS support in IoT NTN | ZTE Corporation, Sanechips |
| R2-2503503 | Remaining issues on PWS support for NB-IoT | Huawei, HiSilicon, Turkcell |
| R2-2503530 | Discussion on PWS for NB-IoT | OPPO |
| R2-2503663 | Remaining issues on support of PWS for NB-IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2503676 | The PWS related consideration of NB-IoT NTN | China Telecom |
| R2-2503799 | Open issues on the support for PWS in NB-IoT | |
| R2-2503910 | Further considerations on PWS broadcast support in IoT NTN | Lenovo |
| R2-2504092 | Acceptable cell camping for NB-IoT | Samsung, Iridium, Vivo, Thales |
| R2-2504319 | Discussion on PWS in NB-IoT NTN | Qualcomm Incorporated |
| R2-2504362 | Remaining issue on support of PWS for NB-IoT NTN UE | CATT |
| R2-2504394 | Support of PWS messages for NB-IoT | CMCC |
| R2-2504655 | Enhancements to support PWS in NB-IoT NTN | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503317 | LS on SONMDT for NTN (R3-252382; contact: CMCC) | RAN3 |
| R2-2503581 | Views on R19 SONMDT UE capabilities | CATT |
| R2-2503582 | Introduction of SONMDT UE Capabilities | CATT |
| R2-2503583 | Introduction of SONMDT UE Capabilities | CATT |
| R2-2503584 | Introduction of SONMDT UE Capabilities | CATT |
| R2-2504234 | Running 36.331 CR for R19 SONMDT | Huawei, HiSilicon |
| R2-2504235 | Open issue list for running 36.331 CR for R19 SONMDT | Huawei, HiSilicon |
| R2-2504295 | Running CR for SONMDT features | Ericsson |
| R2-2504296 | Open Issues for NR RRC SONMDT features | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503417 | Discussion on Rel-19 SONMDT open issues | Xiaomi |
| R2-2503585 | MRO Enhancements for Rel-18 Mobility | CATT |
| R2-2503633 | MRO for LTM and near failure handling for CHO with candidate SCGs | Nokia |
| R2-2503914 | Discussion on MRO enhancements for LTM | Lenovo |
| R2-2503932 | MRO enhancement for LTM | NEC |
| R2-2504224 | Remaining issues for MRO enhancements | Samsung |
| R2-2504236 | Discussion on MRO for mobility | Huawei, HiSilicon |
| R2-2504270 | Discussion on MRO for LTM | Ofinno |
| R2-2504399 | MRO enhancements for CHO with candidate SCGs | CMCC |
| R2-2504498 | Discussion on random access report for LTM | ASUSTeK |
| R2-2504512 | Discussion on SON enhancement for R18 mobility features | SHARP Corporation |
| R2-2504558 | MRO enhancements for mobility | Qualcomm Incorporated |
| R2-2504568 | Remaining MRO issues for MOB | LG Electronics Inc. |
| R2-2504613 | Further considerations on MRO for LTM and CHO with candidate SCG | Ericsson |
| R2-2504618 | Discussion on open issue about CHO with candidate SCGs | vivo |
| R2-2504621 | Remaining issues for Rel-19 MRO | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2503418 | Discussion on other aspects of Rel-19 SONMDT | Xiaomi |
| R2-2503586 | MHI Enhancement for SCG Activation and Deactivation | CATT |
| R2-2503634 | SON/MDT enhancements for network slicing, MHI and NTN | Nokia |
| R2-2503669 | MRO for intra-NTN mobility | China Telecom |
| R2-2503915 | Discussion on MRO for intra-NTN mobility | Lenovo |
| R2-2504237 | Discussion on SONMDT for others | Huawei, HiSilicon |
| R2-2504247 | Discussion on NTN, slicing and other open issues | Samsung |
| R2-2504294 | Discussion on SON-MDT enhancements for Slicing and NTN | Ericsson |
| R2-2504443 | Discussion on SON/MDT for Slicing and NTN | CMCC |
| R2-2504513 | SON enhancements for R18 leftovers | SHARP Corporation |
| R2-2504559 | UE capabilitie for SON and MDT | Qualcomm Incorporated |
| R2-2504569 | NTN Logging for Unchanged PCI Mobility | LG Electronics Inc. |
| R2-2504622 | Remaining other issues for Rel-19 SON MDT | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2503422 | Introduction of SBFD in TS 38300 (Running CR) | CATT |
| R2-2503862 | RRC running CR for Evolution of NR duplex operation (SBFD) | Huawei, HiSilicon |
| R2-2503866 | Remaining RRC open issues in feature SBFD | Huawei, HiSilicon |
| R2-2504437 | Remaining MAC open issues for Rel-19 SBFD | Samsung |
| R2-2504444 | MAC running CR for Evolution of NR duplex operation: SBFD | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R2-2503379 | Impacts on the random access by the evolution of duplex operation | Huawei, HiSilicon |
| R2-2503386 | Random Access for SBFD | NEC |
| R2-2503423 | Random Access in SBFD symbols | CATT |
| R2-2503434 | Discussion on RACH in SBFD | Xiaomi |
| R2-2503477 | Remaining issues on Random Access procedure for SBFD | LG Electronics Inc. |
| R2-2503513 | Open Issues on SBFD Random Access | Sharp |
| R2-2503606 | Random access in SBFD | Samsung |
| R2-2503646 | Remaining issues of SBFD RACH procedure | OPPO |
| R2-2503840 | Random Access Operation of SBFD | Nokia Corporation |
| R2-2503874 | Discussion on random access procedure in SBFD | ZTE Corporation |
| R2-2504039 | Remaining issues on RACH procedure in SBFD | vivo |
| R2-2504059 | Remaining issues for Random Access in SBFD Operation | Sony |
| R2-2504169 | Remaining issues for RACH in SBFD | Apple |
| R2-2504223 | Views on random access for SBFD | Qualcomm Incorporated |
| R2-2504255 | SBFD RA remaining aspects | Ericsson |
| R2-2504327 | Discussion on RACH aspect in SBFD | InterDigital, Inc. |
| R2-2504397 | Discussion on random access in SBFD | CMCC |
| R2-2504602 | Random Access in SBFD | Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R2-2503424 | Discussion on other aspects of SBFD | CATT |
| R2-2503441 | Other aspects of SBFD | Xiaomi |
| R2-2503647 | Discussion on the SBFD related issues | OPPO |
| R2-2503875 | Discussion on L3 measurements in SBFD | ZTE Corporation |
| R2-2503896 | Other aspects of SBFD | Nokia |
| R2-2504040 | SBFD other aspects | vivo |
| R2-2504225 | Other aspects of SBFD | Qualcomm Incorporated |
| R2-2504256 | CSI-RS measurements in SBFD | Ericsson |
| R2-2504328 | Discussion on resource configuration aspect in SBFD | InterDigital, Inc. |
| R2-2504447 | Other Aspects of SBFD | Samsung |
| R2-2504640 | Other aspects about the evolution of duplex operation | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R2-2504184 | Running CR for MIMO Phase 5 | Ericsson |
| R2-2504185 | Open issues for MIMO on 38.331 | Ericsson |
| R2-2504209 | Introduction of MIMO | Samsung |
| R2-2504210 | Report of MAC open issues for MIMO | Samsung |
| R2-2504370 | Work Plan for Rel-19 on NR MIMO Phase 5 | CMCC, Samsung, MediaTek |
| R2-2504371 | Running CR for Rel-19 MIMO Phase 5 | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503388 | RACH Procedure for Asymmetric DL sTRP/ UL mTRP | NEC |
| R2-2503524 | Enhancements for Asymmetric DL sTRP and UL mTRP | Ofinno |
| R2-2503626 | Discussion on open issues for asymmetric DL sTRPUL mTRP | vivo |
| R2-2503644 | Remaining issues of asymmetric DL sTRP and UL mTRP | OPPO |
| R2-2503735 | Discussion on asymmetric UL mTRP in LTM cell switch | SHARP Corporation |
| R2-2503741 | Discussion on Asymmetric DL sTRP UL mTRP | CATT |
| R2-2503820 | Consideration on Asymmetric DL sTRP/UL mTRP | LG Electronics Inc. |
| R2-2503857 | Discussion on asymmetric DL sTRP/UL mTRP | Nokia Corporation |
| R2-2503917 | Discussion on PL offset | Lenovo |
| R2-2504031 | Asymmetric DL/UL mTRP user plane impact from MIMO ph. 5 | Ericsson |
| R2-2504100 | Discussion on remaining issues on Asymmetric DL sTRP/UL mTRP | Huawei, HiSilicon |
| R2-2504211 | Open issues on Asymmetric DL sTRP/UL mTRP | Samsung |
| R2-2504245 | Discussion on UL only mTRP | Qualcomm Incorporated |
| R2-2504248 | Discussion on asymmetric DL sTRP/UL mTRP | China Telecom Corporation Ltd. |
| R2-2504368 | Discussion on Asymmetric DL sTRP/UL mTRP | CMCC |
| R2-2504625 | Consideration on the Remaining Issues of Asymmetric TRP | ZTE Corporation |
| R2-2504665 | Discussion on Asymmetric DL sTRP/UL mTRP | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503525 | Enhancements for UE-initiated/event-driven beam management | Ofinno |
| R2-2503627 | Discussion on MAC and RRC open issues for UEI BMR | vivo |
| R2-2503645 | Clarification on the UL skipping for event-triggered beam reporting | OPPO |
| R2-2503737 | Discussion on overlapping rule for mode-A beam report in PUSCH | SHARP Corporation |
| R2-2503742 | Discussion on UE-initiated Beam Reporting | CATT |
| R2-2503821 | Discussion on UEI beam reporting impact | LG Electronics Inc. |
| R2-2503865 | RAN2 Aspects of the NR MIMO | Nokia Corporation |
| R2-2504099 | Discussion on remaining issues of UE-initiated/event-driven beam management | Huawei, HiSilicon |
| R2-2504186 | Impacts from UE-initiated/event-driven beam management | Ericsson |
| R2-2504212 | Open issues on UE-initiated Reporting and RRC parameters | Samsung |
| R2-2504246 | Discussion on UE Initiated Beam Report | Qualcomm Incorporated |
| R2-2504249 | Discussion on UE Initiated Beam Report | China Telecom Corporation Ltd. |
| R2-2504369 | Discussion on other issues of NR MIMO Phase 5 | CMCC |
| R2-2504499 | Discussion on RRC impacts for UEI Beam Reporting Mode B | ASUSTeK |
| R2-2504500 | Discussion on MAC impacts for UEI Beam Reporting Mode B | ASUSTeK |
| R2-2504626 | Consideration on the Remaining Issues of UEIBM | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503430 | Introduction of Service Continuity for MH Sidelink Relay in 38331 | CATT |
| R2-2503815 | Multihop terminology | LG Electronics Inc. |
| R2-2504153 | Draft Running CR for 38.321 | InterDigital |
| R2-2504162 | Introduction of multi-hop U2N relay in TS 38.323 | Ericsson |
| R2-2504218 | Introduction of multi-hop U2N relay in TS 38.304 | Mediatek Inc. |
| R2-2504271 | Introduction of NR sidelink multi-hop relay in TS 38.331 | Huawei, HiSilicon |
| R2-2504272 | Open issues for Multi hop Sidelink Relay in TS 38.331 | Huawei, HiSilicon, CATT |
| R2-2504504 | Introduction of NR sidelink multi-hop relay in TS 38.351 | OPPO |
| R2-2504505 | SRAP open issues for NR sidelink multi-hop relay | OPPO |
| R2-2504545 | Discussion on Capabilities of Multi-hop SL relay | Samsung |
| R2-2504634 | introduction of multi-hop U2N SL Relay in 38.300 | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2503431 | Discussion on Multi-hop Discovery and (Re)selection | CATT |
| R2-2503490 | Discovery and relay (re)selection for multi-hop U2N relay | OPPO |
| R2-2503540 | Discussion on multi-hop U2N relay discovery and relay selection | NEC Corporation (ARIB) |
| R2-2503668 | Discussion on multi-hop relay reselection | China Telecom |
| R2-2503725 | Relay discovery and selection for Multi-hop UE-to-NW Relay | Apple |
| R2-2503901 | Discussion on discovery and relay reselection for multi-hop U2N relay | LG Electronics Inc. |
| R2-2503922 | Relay (re)selection in Multi-hop relay | Lenovo |
| R2-2503962 | Discussion on notification message | Spreadtrum, UNISOC |
| R2-2504012 | Discussion on Relay discovery and (re)selection | ZTE Corporation, Sanechips |
| R2-2504060 | Multi-hop relay selection/re-selection | Sony |
| R2-2504154 | Discovery and Relay (Re)Selection for Multi-hop U2N Relays | InterDigital |
| R2-2504161 | Discussion on relay discovery and relay (re)selection | Ericsson |
| R2-2504259 | Relay (re)selection under multihop relay | Kyocera |
| R2-2504273 | Relay discovery and (re)selection for multi-hop Relay | Huawei, HiSilicon |
| R2-2504358 | discussion on Relay discovery and (re)selection for multi-hop relay | Sharp |
| R2-2504522 | Discussion on remaining issues on intermediate relay UE (re)selection and discovery | vivo |
| R2-2504546 | Considerations on relay discovery and (re)selection | Samsung |
| R2-2504560 | Discussion on notification when the intermediate relay UE performs relay reselection | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R2-2503387 | Remaining issues for Control Plane Procedures | NEC |
| R2-2503432 | Discussion on the Control Plane Procedures | CATT |
| R2-2503492 | Control plane procedures of multi-hop U2N relay | OPPO |
| R2-2503677 | Discussion on control plane aspects for NR sidelink multi-hop relay | China Telecom |
| R2-2503726 | Fast & Parallel RRC Establishment for Multi-hop U2N relaying and TP | Apple, FirstNet, Ericsson, AT&T, Kyocera, Philips, NEC |
| R2-2503727 | Discussion on SRAP and Control Plane for Multi-hop Layer-2 U2N Relay | Apple |
| R2-2503923 | Control plane in Multi-hop relay | Lenovo |
| R2-2503925 | Discussion on the control plane procedure for multi-hop U2N relay | LG Electronics Inc. |
| R2-2503929 | Control plane and SRAP for multi-hop relay | Nokia |
| R2-2504011 | Discussion on control plane procedures for multi-hop SL Relay | ZTE Corporation, Sanechips |
| R2-2504014 | Report of [Post129bis][412][Relay] FFS issues on system information | ZTE Corporation, Sanechips |
| R2-2504155 | Open Issues on SI and Paging for Multi-Hop U2N Relays | InterDigital |
| R2-2504160 | Discussion on control plane procedures | Ericsson |
| R2-2504274 | Control plane procedures for multi-hop relay | Huawei, HiSilicon |
| R2-2504359 | discussion on C-plane procedure for multi-hop relay | Sharp |
| R2-2504406 | Discussion on control plane procedure for SL relay | KT Corp. |
| R2-2504523 | Discussion on remaining issues on paging | vivo |
| R2-2504547 | Discussions on fast RRC connection setup for multi-hop SL relay | Samsung, Nokia |
| R2-2504561 | Open issue for control plane | Qualcomm Incorporated |
| R2-2504642 | SRAP design for R19 multi-hop SL relaying and remaining Control Plane issues | Samsung R&D Institute UK |
| R2-2504647 | Parallel RRC setup for multi-hop U2N relay | OPPO, vivo, Qualcomm, Huawei, CATT, MediaTek Inc., KT Corp., China Telecom, ASUSTek, Sharp |
| R2-2504667 | Discussion on the control plane procedure for multi-hop U2N relay (update) | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R2-2503433 | Intra-gNB Service Continuity for Multi-hop U2N Relay | CATT |
| R2-2503491 | Service continuity of multi-hop U2N relay | OPPO |
| R2-2503678 | Discussion on service continuity for multi-hop relay | China Telecom |
| R2-2503781 | Considerations on Service Continuity of Multi-hop Relay | NEC |
| R2-2503924 | Service continuity for Multi-hop system | Lenovo |
| R2-2503927 | Discussion on service continuity for multi-hop U2N relay | LG Electronics Inc. |
| R2-2503930 | Discussion on service continuity for multi-hop relay | Nokia |
| R2-2504013 | Discussion on Service continuity | ZTE Corporation, Sanechips |
| R2-2504275 | Discussion on service continuity for Multi-hop Relay | Huawei, HiSilicon |
| R2-2504344 | Service Continuity for Multi-Hop Relays | Ericsson |
| R2-2504360 | discussion on service continuity for multi-hop relay | Sharp |
| R2-2504524 | Discussion on service continuity for scenario C and D | vivo |
| R2-2504562 | Service continuity discussion | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R2-2503316 | Reply LS on NR Femto node shared by PLMN and PNI-NPN (R3-252337; contact: LGE) | RAN3 |
| R2-2503335 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) (S2-2504110; contact: Qualcomm) | SA2 |
| TDoc | Title | Source |
|---|---|---|
| R2-2504116 | Remaining issues for NAVIC L1 SPS | Huawei, HiSilicon |
| R2-2504298 | Introduction of NavIC L1 SPS A-GNSS in NR Stage 2 specification | Ericsson, Reliance Jio, CEWiT, Huawei |
| R2-2504299 | Introduction of NavIC L1 SPS A-GNSS in LTE Stage 2 specification | Ericsson, Reliance Jio, CEWiT, Huawei |
| R2-2504300 | Introduction of NavIC L1 SPS A-GNSS in LPP | Ericsson, Reliance Jio, ISRO, MediaTek, CEWiT |
| R2-2504301 | Report of [POST129][401][POS] NavIC L1 CR update (Ericsson) | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R2-2503350 | Discussion on support of IoT-NTN TDD mode | Xiaomi |
| R2-2503357 | Further Discussion on IoT-NTN TDD mode | vivo |
| R2-2503389 | SI transmission of IoT-NTN TDD mode | NEC |
| R2-2503462 | Discussion on support of NB-IoT NTN TDD | CATT |
| R2-2503531 | Discussion on IoT NTN TDD mode | OPPO |
| R2-2503689 | IoT-NTN TDD mode SI scheduling and UE procedures | Iridium Satellite LLC |
| R2-2503911 | DL and UL impacts of TDD pattern in IoT NTN | Lenovo |
| R2-2503987 | Discussion on NTN IoT-NTN TDD mode | TOYOTA ITC |
| R2-2504070 | Discussion on RAN2 impacts of IoT-NTN TDD | Huawei, HiSilicon |
| R2-2504082 | Consideration on IoT-NTN TDD mode | ZTE Corporation, Sanechips |
| R2-2504093 | On RAN2 aspects for IoT NTN TDD | Samsung |
| R2-2504320 | Discussion on new NB-IoT NTN TDD mode | Qualcomm Incorporated |
| R2-2504334 | On SI scheduling, postponing impacts, and early implementation of the IoT-NTN TDD mode | Nordic Semiconductor ASA |
| R2-2504395 | Support of IoT-NTN TDD mode | CMCC |
| R2-2504510 | Further discussion on support of TDD mode for IoT-NTN | Nokia, Nokia Shanghai Bell |
| R2-2504633 | Discussion on support of IoT-NTN TDD mode | THALES |
| TDoc | Title | Source |
|---|---|---|
| R2-2503390 | Configuration to support LTE-based 5G Broadcast | NEC |
| R2-2503506 | Configuration and scheduling aspects for LTE-based 5G Broadcast Phase 2 | Samsung |
| R2-2504075 | Discussion on time-frequency interleavers for MBMS | Huawei, HiSilicon |
| R2-2504260 | RAN2 impacts to support time-frequency interleavers for LTE-based 5G Broadcast Phase 2 | Qualcomm Incorporated, EBU |
| R2-2504620 | Discussion on TFI for 5G Broadcast | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R2-2504071 | ETWS geo-fencing for eMTC NTN and for TN | Huawei, HiSilicon, China Southern Power Grid, Turkcell |
| R2-2504347 | NR-NTN to NB-IoT NTN inter-RAT mobility | EchoStar, Boost Mobile, Terrestar, Qualcomm, TTP |
| TDoc | Title | Source |
|---|---|---|
| R2-2503844 | Introduction of control parameters for on-demand posSIB request_RRC [OdPosSIB-Req] | Huawei, HiSilicon, Ericsson |
| R2-2503845 | Introduction of control parameters for on-demand posSIB request_UEcapa [OdPosSIB-Req] | Huawei, HiSilicon, Ericsson |
| R2-2503846 | Introduction of control parameters for on-demand posSIB request_stage2 [OdPosSIB-Req] | Huawei, HiSilicon, Ericsson |
| R2-2503847 | Introduction of control parameters for on-demand posSIB request_POSstage2 [OdPosSIB-Req] | Huawei, HiSilicon, Ericsson |
| R2-2504230 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] | Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2504231 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] | Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2504232 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] | Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2504233 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] | Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, NTT DoCoMo, Samsung |
| R2-2504382 | Corrections to TS 38.300 on multi-path relay enhancement [N3C_M_Relay] | CMCC,ZTE, MediaTek, vivo, Huawei, CATT, Nokia, Nokia Shanghai Bell, Xiaomi, Spreadtrum, UNISOC |
| R2-2504383 | Corrections to TS 38.331 on multi-path relay enhancement [N3C_M_Relay] | CMCC,ZTE, MediaTek, vivo, Huawei, CATT, Nokia, Nokia Shanghai Bell, Xiaomi, Spreadtrum, UNISOC |
| R2-2504384 | Corrections to TS 38.306 on multi-path relay enhancement [N3C_M_Relay] | CMCC,ZTE, MediaTek, vivo, Huawei, CATT, Nokia, Nokia Shanghai Bell, Xiaomi, Spreadtrum, UNISOC |
| TDoc | Title | Source |
|---|---|---|
| R2-2503333 | LS on UL Tx switching for TEI19 (R4-2505221; contact: MediaTek) | RAN4 |
| R2-2503369 | Introduction of LTE TN to NB-IoT NTN Mobility UE Capability | vivo, Samsung, Google, THALES, MediaTek Inc. |
| R2-2503829 | 36331CR for the inclusion of NB-IoT satellite information in E-UTRAN | Google, Samsung, vivo, THALES, MediaTek Inc. |
| R2-2503832 | 36300CR for the inclusion of NB-IoT satellite information in E-UTRAN | Google, Samsung, vivo, THALES, MediaTek Inc. |
| R2-2503877 | Introduction of UE capability for SRS frequency hopping for non-RedCap UE in 37355 [Pos_SRSHop] | ZTE Corporation |
| R2-2503878 | Introduction on the SRS frequency hopping for non-RedCap UE in 38331 [Pos_SRSHop] | ZTE Corporation, Ericsson |
| R2-2503981 | Discussion on implementing FGs for TEI19 feature Pos_SRSHop | Lenovo |
| R2-2504094 | Redirection from TN to IoT NTN and NR NTN | Samsung, Google |
| R2-2504306 | UE request for equalIntegerAmbiguityLevel assistance data [GNSS-EqualIntegerAmbiguity] | Ericsson, Huawei, CATT, Samsung, ZTE Corporation, Nokia, AT&T, Deutsche Telekom |
| R2-2504345 | Scheduling Request (SR) to Random Access (RA) Fallback Enhancements | Ericsson |
| R2-2504405 | Introducing PDCCH CCE Usage based on statistical MIMO layer for L2M [PDCCH_Usage] | CMCC, Huawei, Ericsson, ZTE, CATT |
| R2-2504507 | Discussion and TP for band specific capability for paging [Per_Band_Paging_Cap] | Huawei, HiSilicon, Nokia, Ericsson |
| R2-2504541 | Leftover issue on ANR reporting of HSDN cells in INM | Samsung |
| R2-2504576 | Support early CSI acquisition for L3 Handover | Huawei, HiSilicon, China Unicom, Sony, Turkcell, NTT Docomo INC., Meta, Ericsson, Reliance Jio, Vodafone, ZTE Corporation, British Telecom, Deutsche Telekom, Vivo, LG Electronics Inc. |
| R2-2504600 | Discussion on UE capability change | Nokia |
| R2-2504664 | Introducing PDCCH CCE Usage for L2M [PDCCH_Usage] | CMCC, Huawei, Ericsson, ZTE, CATT |
| TDoc | Title | Source |
|---|---|---|
| R2-2503375 | Discussion on R4 LS on UE Architecture Type-4a/4b | OPPO |
| R2-2503446 | Discussion on DL MIMO layer capability for 6Rx UE | Xiaomi, Intel Corporation, Oppo, Ericsson, Nokia, Qualcomm Incorporated, ZTE, Sanechips, CATT, T-mobile USA, CHTTL |
| R2-2503447 | Introduction of 6 DL MIMO layer | Xiaomi, Intel Corporation, Oppo, Ericsson, Nokia, Qualcomm Incorporated, ZTE, Sanechips, CATT, T-mobile USA, CHTTL |
| R2-2503448 | Introduction of 6 DL MIMO layer | Xiaomi, Intel Corporation, Oppo, Ericsson, Nokia, Qualcomm Incorporated, ZTE, Sanechips, CATT, T-mobile USA, CHTTL |
| R2-2503579 | Consideration on CSSF optimization | CATT |
| R2-2503580 | Discussion on Rx BSF optimization for NR RRM Ph5 | CATT |
| R2-2503814 | RAN2 impact on CSSF optimization | Apple, Ericsson |
| R2-2503816 | iscussion on singling design for Non-collocated feature | KDDI Corporation, Samsung |
| R2-2503817 | Discussion on singling design for Non-collocated feature | KDDI Corporation, Samsung |
| R2-2503897 | Reduced Beam Sweeping Factor | Nokia |
| R2-2503942 | Discussion on CSSF optimization and Rx BSF optimization for NR RRM ph5 | Huawei, HiSilicon |
| R2-2503951 | Discussion on simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD combinations | Huawei, HiSilicon |
| R2-2504030 | Discussion on Rx BSF optimization | ZTE Corporation |
| R2-2504176 | Discussion on Type 4 requirements for intra-band non-collocated ENDC/NR SA | Apple |
| R2-2504188 | Simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD | Ericsson |
| R2-2504189 | Additional aspects on Type 4 for non-collocated deployment | Ericsson |
| R2-2504449 | Introduction of new UE capabilities for FR2 MPR improvement | Samsung |
| R2-2504450 | Introduction of new UE capabilities for FR2 MPR improvement | Samsung |
| R2-2504563 | draftCR 38.331 signalling support for intra-band non-collocated NR-CA EN-DC | KDDI Corporation |
| R2-2504564 | Introduction of signaling support for intra-band non-collocated EN-DC/NR-CA deployment Phase 2: new receiver type(s) | KDDI |
| R2-2504566 | signalling support for intra-band non-collocated NR-CA EN-DC | KDDI Corporation |
| R2-2504594 | Discussion on 6 DL MIMO layers | Huawei, HiSilicon, MediaTek Inc., Samsung, Apple |
| R2-2504627 | Consideration on the Type 4 UE for Non-collocated Deployment | ZTE Corporation |
| TDoc | Title | Source |
|---|---|---|
| R2-2503341 | LS on RTP retransmission (S4-250739; contact: Nokia) | SA4 |
| R2-2503567 | RTP Retransmissions for XR | Nokia, Nokia Shanghai Bell |
| R2-2503578 | Views on LS on RTP retransmission (S4-250739) | CATT |
| R2-2503602 | Running RRC CR for Rel-19 Multi-carrier enhancements | Lenovo Information Technology |
| R2-2503684 | Introduction of number of UEs in RRC_INACTIVE state with data transmission | China Telecom, Huawei, HiSilicon, ZTE Corporation, Sanechips, CATT, Ericsson |
| R2-2504117 | Discussion on LS S4-250739 for RTP retransmission | Huawei, HiSilicon |
| R2-2504570 | RAT restrictions for ECRAT | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R2-2504671 | Report from session on V2X/SL, R19 NES and MOB | Vice Chairman (Samsung) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504672 | Rel-18 MIMO, Rel-19 MIMO, LPWUS, and SBFD | Vice Chairman (CATT) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504673 | Report from session on NR NTN and IoT NTN | Session chair (ZTE) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504674 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504675 | Report from session on R19 XR and LTE Broadcast | Session chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R2-2504676 | Report from session on maintenance and SON/MDT | Session chair (Ericsson) |