TDoc | Title | Source |
---|---|---|
R2-2409501 | Agenda for RAN2#128 | Chairman |
TDoc | Title | Source |
---|---|---|
R2-2409502 | RAN2#127bis Meeting Report | MCC |
TDoc | Title | Source |
---|---|---|
R2-2409503 | RAN2 Handbook | MCC |
R2-2409711 | Reply LS on RAN3 vs RAN2 Basketball Match | RAN2 |
R2-2409712 | Report on RAN2 Basketball team | OPPO |
R2-2410130 | Clarification on providing impact analysis in CR coversheet | Lenovo |
R2-2410464 | Discussion on CR coversheet update | Ericsson |
R2-2411233 | Correction on conditional PSCell addition or change failure | R3 (CATT, CMCC, ZTE, Nokia, Nokia Shanghai Bell) |
R2-2411234 | Correction on AI/ML Terminology | R3 (Nokia, Ericsson, ZTE, Huawei) |
R2-2411235 | OAM Requirements on Energy Cost index | R3 (Nokia, Jio, Telecom Italia, Ericsson, ZTE, Samsung, NEC, Huawei, Deutsche Telekom) |
R2-2411236 | Correction of IAB F1-C transfer in NR-DC | R3 (ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung) |
R2-2411237 | Correction of IAB F1-C transfer in NR-DC | R3 (ZTE Corporation, Ericsson, Lenovo, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, CATT, Samsung) |
R2-2411238 | Stage 2 correction for AI/ML for NG-RAN | R3 (Ericsson, Huawei, Nokia, InterDigital, ZTE, NEC, Deutsche Telekom) |
R2-2411239 | QoE measurement handling in idle mode | R3 (CATT, Ericsson, ZTE, Xiaomi) |
R2-2411240 | Correction to area-specific SRS activation | R3 (CATT, ZTE, Ericsson, China Telecom, Nokia, Samsung, Qualcomm Incorporated, Xiaomi, Huawei) |
R2-2411241 | Coarse UE Location Information Reporting from MME to eNB for NB-IoT UEs | R3 (Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CATT) |
R2-2411242 | Corrections to Stage-2 for XR awareness | R3 (Ericsson, Qualcomm Inc., Nokia, Nokia Shanghai Bell, Huawei, Samsung, ZTE, China Telecom, Xiaomi, CATT, CMCC, Lenovo) |
R2-2411243 | Stage-2 updates for intra-SN S-CPAC with MN involvement | R3 (Ericsson, Nokia, CATT, LG Electronics, Huawei, ZTE, Samsung) |
TDoc | Title | Source |
---|---|---|
R2-2410559 | Addition of reference to 38.304 for Qoffsettemp handling | Nokia |
R2-2410560 | Addition of reference to 38.304 for Qoffsettemp handling | Nokia |
R2-2410561 | Addition of reference to 38.304 for Qoffsettemp handling | Nokia |
R2-2410562 | Addition of reference to 38.304 for Qoffsettemp handling | Nokia |
R2-2411015 | Addition of reference to 38.304 for Qoffsettemp handling | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2409946 | Correction to NR Beam Reporting in LTE RRC | Apple, ZTE Corporation |
R2-2410891 | Correction to NR Beam Reporting in LTE RRC | Apple, ZTE Corporation |
R2-2411016 | Correction to NR Beam Reporting in LTE RRC | Apple, ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409878 | Minor Corrections on TS36.331 | vivo |
R2-2409879 | Minor Corrections on TS36.331 | vivo |
R2-2409880 | Minor Corrections on TS36.331 | vivo |
R2-2410026 | Correction on SI Reception in IoT-NTN | vivo |
R2-2410027 | Correction on SI Reception in IoT-NTN | vivo |
R2-2410547 | Alignment of highProrityAccess cause in RRC Establishment and Resume | Peraton Labs |
R2-2411017 | Correction on SI Reception in RRC CONNECTED | vivo |
R2-2411018 | Correction on SI Reception in RRC CONNECTED | vivo |
R2-2411019 | Correction on SI Reception in RRC CONNECTED | vivo |
R2-2411035 | Alignment of highProrityAccess cause in RRC Establishment and Resume | Peraton Labs, CISA ECD, AT&T, Nokia (Rapporteur), Verizon |
R2-2411204 | Correction on SI Reception in RRC CONNECTED | vivo |
TDoc | Title | Source |
---|---|---|
R2-2410232 | Correction on broadcast of assistance data-r15 | Huawei, HiSilicon |
R2-2410233 | Correction on broadcast of assistance data-r16 | Huawei, HiSilicon |
R2-2410234 | Correction on broadcast of assistance data-r17 | Huawei, HiSilicon |
R2-2410235 | Correction on broadcast of assistance data-r18 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2409814 | Maximum number of configured CCs | Nokia, Nokia Shanghai Bell |
R2-2409815 | Maximum number of configured CCs | Nokia, Nokia Shanghai Bell |
R2-2409816 | Maximum number of configured CCs | Nokia, Nokia Shanghai Bell |
R2-2409817 | Maximum number of configured CCs | Nokia, Nokia Shanghai Bell |
R2-2410451 | Clarification on support of BFD-BFR on PSCell | Ericsson |
R2-2410452 | Clarification on support of BFD-BFR on PSCell | Ericsson |
R2-2410453 | Clarification on support of BFD-BFR on PSCell | Ericsson |
R2-2410454 | Clarification on support of BFD-BFR on PSCell | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2410419 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410420 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410421 | Gap requirement for CSI-RS based measurements and inter-RAT measurements (R18) | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410431 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410900 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410901 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
R2-2410902 | Gap requirement for CSI-RS based measurements and inter-RAT measurements | Huawei, HiSilicon, ZTE Corporation, Ericsson, Samsung, CATT, Apple, Nokia, Nokia Shanghai Bell, LG Electronics Inc., OPPO |
TDoc | Title | Source |
---|---|---|
R2-2409997 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
R2-2409998 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
R2-2411224 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
R2-2411225 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409552 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
R2-2409553 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
R2-2409554 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
R2-2411086 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
R2-2411087 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
R2-2411088 | Correction to available UL-SCH resources in SR triggering | Samsung (Rapporteur), Ericsson, Spreadtrum |
TDoc | Title | Source |
---|---|---|
R2-2410563 | Correction on deprioritisationTimer | Nokia, MediaTek Inc., LG Electronics Inc. |
R2-2410564 | Correction on deprioritisationTimer | Nokia, MediaTek Inc., LG Electronics Inc. |
R2-2410565 | Correction on deprioritisationTimer | Nokia |
R2-2410566 | Correction on deprioritisationTimer | Nokia |
R2-2411020 | Correction on deprioritisationTimer | Nokia |
R2-2411039 | Correction on deprioritisationTimer | Nokia, MediaTek Inc., LG Electronics Inc., Qualcomm Inc., ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409642 | Correction on IE SRS-CarrierSwitching | CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, CMCC, Ericsson |
R2-2409643 | Correction on IE SRS-CarrierSwitching | CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, Ericsson |
R2-2409644 | Correction on IE SRS-CarrierSwitching | CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, Ericsson |
R2-2409645 | Correction on IE SRS-CarrierSwitching | CATT, Vivo, China Telecom, China Unicom, Nokia, ZTE Corporation, Ericsson |
R2-2410058 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2410059 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2410060 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2410203 | Correction to missing NR-DC parameters branches | Ericsson |
R2-2410204 | Correction to missing NR-DC parameters branches | Ericsson |
R2-2410205 | Correction to missing NR-DC parameters branches | Ericsson |
R2-2410829 | Corrections on parallelTx capabilities for inter-band and intra-band | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2410830 | Corrections on parallelTx capabilities for inter-band and intra-band | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2410831 | Corrections on parallelTx capabilities for inter-band and intra-band | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2410832 | Corrections on parallelTx capabilities for inter-band and intra-band | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2410885 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2410886 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2410887 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411021 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411022 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411023 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411101 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411102 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
R2-2411103 | Correction to Relaxed measurement | LG Electronics, Nokia, Samsung, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409928 | Correction on SI request in RRC_CONNECTED | LG Electronics Inc. |
R2-2409929 | Correction on SI request in RRC_CONNECTED | LG Electronics Inc. |
R2-2409930 | Correction on SI request in RRC_CONNECTED | LG Electronics Inc. |
R2-2410074 | Correction on protection of RRC messages | ZTE Corporation, Sanechips |
R2-2410075 | Correction on protection of RRC messages | ZTE Corporation, Sanechips |
R2-2410076 | Correction on protection of RRC messages | ZTE Corporation, Sanechips |
R2-2410356 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2410357 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2410358 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2410359 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2410746 | Correction to PNI-NPN identity | Huawei, HiSilicon, CATT |
R2-2410747 | Correction to PNI-NPN identity | Huawei, HiSilicon, CATT |
R2-2410748 | Correction to PNI-NPN identity | Huawei, HiSilicon, CATT |
R2-2411024 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2411025 | Corrections on smtc configuration | ZTE Corporation, Sanechips |
R2-2411026 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
R2-2411027 | Corrections to smtc configuration | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2410052 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2410053 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2410054 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2410666 | Correction to maximum data rate calculation | Nokia |
R2-2410667 | Correction to maximum data rate calculation | Nokia |
R2-2410668 | Correction to maximum data rate calculation | Nokia |
R2-2410669 | Correction to maximum data rate calculation | Nokia |
R2-2411028 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2411029 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2411030 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
R2-2411259 | Clarification on inter-band handover enhancements capabilities | Qualcomm Inc., OPPO |
TDoc | Title | Source |
---|---|---|
R2-2409684 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2409685 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2409686 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2410077 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
R2-2410078 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
R2-2410079 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
R2-2410931 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2410932 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2410933 | RRC correction on sl-X-Overhead field description of SL-ResourcePool | Philips International B.V. |
R2-2410934 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
R2-2410935 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
R2-2410936 | Correction on intra-UE prioritization | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2409562 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
R2-2409563 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
R2-2409564 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
R2-2410906 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
R2-2410907 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
R2-2410908 | Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409714 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2410024 | Correction on NavIC L5 almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2410025 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2410236 | Corection to high accuracy extended uncerntainty in QoS-r16 | Huawei, HiSilicon |
R2-2410237 | Correction to high accuracy extended uncertainty in LCS QoS | Huawei, HiSilicon |
R2-2410238 | Correction to high accuracy extended uncertainty in LCS QoS | Huawei, HiSilicon |
R2-2410817 | Correction to high accuracy extended uncertainty in LCS QoS | Huawei, HiSilicon |
R2-2410821 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410822 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410823 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410824 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410869 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410873 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2410982 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2410983 | Correction on NavIC L5 almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2410984 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2411062 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson, MediaTek Inc. |
R2-2411063 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson, MediaTek Inc. |
R2-2411064 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson, MediaTek Inc. |
R2-2411065 | Presence of ValueTag and ExpirationTime when posSIBs are segmented | Ericsson |
R2-2411186 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2411187 | Correction on NavIC L5 almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2411188 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater, UTC-ModelSet2, and GNSS-SystemTime. | Reliance Jio, MediaTek, Ericsson, Qualcomm Incorporated, CEWiT |
R2-2411206 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater and GNSS-SystemTime. | Reliance Jio, CEWiT, MediaTek, Ericsson, Qualcomm, CATT, Nokia |
R2-2411207 | Correction on NavIC L5 almanac set IE, and field descriptions under KlobucharModelParamater and GNSS-SystemTime | Reliance Jio, CEWiT, MediaTek, Ericsson, Qualcomm, CATT, Nokia |
R2-2411208 | Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater and GNSS-SystemTime. | Reliance Jio, CEWiT, MediaTek, Ericsson, Qualcomm, CATT, Nokia |
TDoc | Title | Source |
---|---|---|
R2-2410874 | Discussion on RAN1 LS on waveform determination for PUSCH scheduled by fallbackRAR UL grant and MsgA PUSCH | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409515 | LS on waveform determination for PUSCH scheduled by fallbackRAR UL grant and MsgA PUSCH (R1-2409301; contact: CATT) | RAN1 |
R2-2409602 | Contact company’s input on RAN1 LS in R2-2409515 | CATT |
R2-2409603 | CR on the usage of msg3-transmitPrecoder | CATT |
R2-2409604 | CR on the usage of msg3-transmitPrecoder | CATT |
R2-2410937 | Co-configuration of IUC scheme-2 and random selection | OPPO |
R2-2411031 | LS response on waveform determination for PUSCH scheduled by fallbackRAR UL grant and MsgA PUSCH | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409600 | Correction on location based measurements in NR NTN | CATT, Nokia, Nokia Shanghai Bell |
R2-2409601 | Correction on location based measurements in NR NTN | CATT, Nokia, Nokia Shanghai Bell |
R2-2409806 | Clarification on MII usage | Samsung, Nokia |
R2-2409807 | Clarification on MII usage | Samsung, Nokia |
TDoc | Title | Source |
---|---|---|
R2-2409999 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
R2-2410131 | Miscellaneous corrections on stage 2 description of QMC | Lenovo |
R2-2410807 | Correction on TDD support in NTN | Huawei, HiSilicon |
R2-2410808 | Correction on TDD support in NTN | Huawei, HiSilicon |
R2-2410818 | Discussion on RAN1 LS on waveform determination | LG Electronics Inc. |
R2-2411032 | Miscellaneous corrections on stage 2 description of QMC | Lenovo |
R2-2411226 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409609 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409610 | Correction on PHR for mTRP PUSCH repetition (R17) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409611 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409612 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409613 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409614 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2409698 | Corrections to validity of configured uplink grant for SDT | Samsung, LG Electronics, Sony |
R2-2409804 | Correction on HARQ process | Samsung, Ericsson, Nokia, LG Electronics Inc., Qualcomm Incorporated, Apple, ZTE, CATT |
R2-2409805 | Correction on HARQ process | Samsung, Ericsson, Nokia, LG Electronics Inc., Qualcomm Incorporated, Apple, ZTE, CATT |
R2-2410455 | Correction on use of recommended of IAB-MT beam indication | Ericsson, Samsung |
R2-2410456 | Correction on use of recommended of IAB-MT beam indication | Ericsson, Samsung |
R2-2411068 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411069 | Correction on PHR for mTRP PUSCH repetition (R17) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411070 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411071 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411072 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411073 | Correction on PHR for mTRP PUSCH repetition (R18) | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411095 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411096 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411097 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411098 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411099 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
R2-2411100 | Correction on PHR for mTRP PUSCH repetition | LG Electronics Inc., MediaTek Inc., CATT, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409605 | Discussion on remaining issues for one-shot HARQ Feedback in NR NTN | CATT |
R2-2409699 | Corrections to validity of configured uplink grant for SDT | Samsung, LG Electronics, Sony |
R2-2409832 | Correction on the field name of candidate beam list in BFR MAC CE | Samsung |
R2-2409833 | Correction on the field name of candidate beam list in BFR MAC CE | Samsung |
R2-2410195 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2410196 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2410511 | PHR for serving cells configured with multiple TRP PUSCH repetition in NR-DC | Huawei, HiSilicon |
R2-2410512 | PHR for serving cells configured with multiple TRP PUSCH repetition in NR-DC | Huawei, HiSilicon |
R2-2410720 | Correction on drx HARQ RTT timer in NTN | LG Electronics Inc. |
R2-2410722 | Correction on drx HARQ RTT timer in NTN | LG Electronics Inc. |
R2-2410879 | NTN DRX Timer Handling and URLLC One-Shot HARQ Feedback | Sharp |
R2-2411089 | Correction on the field name of candidate beam list in BFR MAC CE | Samsung |
R2-2411090 | Correction on the field name of candidate beam list in BFR MAC CE | Samsung |
R2-2411091 | PHR for serving cells configured with multiple TRP PUSCH repetition in NR-DC | Huawei, HiSilicon |
R2-2411092 | PHR for serving cells configured with multiple TRP PUSCH repetition in NR-DC | Huawei, HiSilicon |
R2-2411117 | Report of [AT128][006][UP] NTN and one shot feedback (CATT) | CATT |
R2-2411118 | Correction on HARQ-RTT-TimerDL-NTN in NR NTN | CATT, LG Electronics Inc., Sharp |
R2-2411119 | Correction on HARQ-RTT-TimerDL-NTN in NR NTN | CATT, LG Electronics Inc., Sharp |
R2-2411173 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2411174 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2411214 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2411215 | CR on TCI state indication of CORESET#0 | OPPO |
R2-2411216 | CR on TCI state indication of CORESET#0 | OPPO, ZTE |
R2-2411217 | CR on TCI state indication of CORESET#0 | OPPO, ZTE |
TDoc | Title | Source |
---|---|---|
R2-2409932 | Clarification of MeasurementTimingConfiguration use | Vodafone,Ericsson,Nokia |
TDoc | Title | Source |
---|---|---|
R2-2409808 | Clarification on determining about to start sessions | Samsung, Nokia |
R2-2409809 | Clarification on determining about to start sessions | Samsung, Nokia |
R2-2409914 | Correction to unified TCI signalling | MediaTek Inc. |
R2-2409915 | Correction to unified TCI signalling | MediaTek Inc. |
R2-2409919 | Correction on UE behavior of setting failedPSCellId | NTTDOCOMO, INC. |
R2-2409920 | Correction on UE behavior of setting failedPSCellId | NTTDOCOMO, INC. |
R2-2410360 | Corrections on measurement gap configuration | ZTE Corporation, Sanechips |
R2-2410361 | Corrections on measurement gap configuration | ZTE Corporation, Sanechips |
R2-2410417 | Corrections to NR NTN (R17) | Huawei, HiSilicon, CMCC, Sequans Communications |
R2-2410418 | Corrections to NR NTN (R18) | Huawei, HiSilicon, CMCC, Sequans Communications |
R2-2410533 | Correction for CFRA configuration due to PRACH partitioning | Huawei, HiSilicon, ZTE Corporation, Ericsson, Mediatek |
R2-2410534 | Correction for CFRA configuration due to PRACH partitioning | Huawei, HiSilicon, ZTE Corporation, Ericsson, Mediatek |
R2-2410650 | Correction on IE perRAInfoList for SCGFailureInformation | Huawei, HiSilicon |
R2-2410651 | Correction on IE perRAInfoList for SCGFailureInformation | Huawei, HiSilicon |
R2-2410835 | Correction on UE capabilities for TCI state indication | Huawei, HiSilicon |
R2-2410836 | Correction on UE capabilities for TCI state indication | Huawei, HiSilicon |
R2-2410837 | Correction on UE capabilities for TCI state indication | Huawei, HiSilicon |
R2-2410838 | Correction on UE capabilities for TCI state indication | Huawei, HiSilicon |
R2-2410893 | Clarification of MeasurementTimingConfiguration use | Vodafone,Ericsson,Nokia |
R2-2410909 | Correction on UE capabilities for TCI state indication | Huawei, HiSilicon |
R2-2410917 | Corrections on measurement gap configuration | ZTE Corporation, Sanechips |
R2-2411037 | Corrections on measurement gap configuration | ZTE Corporation, Sanechips |
R2-2411038 | Corrections on measurement gap configuration | ZTE Corporation, Sanechips |
R2-2411264 | Correction for CFRA configuration due to PRACH partitioning | Huawei, HiSilicon, ZTE Corporation, Ericsson, Mediatek |
TDoc | Title | Source |
---|---|---|
R2-2409662 | Correction of field description si-broadcastStatus and posSI-broadcast status to reflect maxSI message (Rel-17) | Xiaomi, Ericsson, LG electronics, Philips International B.V., Qualcomm Incorporated, ZTE Corporation |
R2-2409663 | Correction of field description si-broadcastStatus and posSI-broadcast status to reflect maxSI message (Rel-18) | Xiaomi, Ericsson, LG electronics, Philips International B.V., Qualcomm Incorporated, ZTE Corporation |
R2-2409664 | Clarification for IDC solutions of logged MDT (Rel-17) | Xiaomi, CMCC |
R2-2409665 | Clarification for IDC solutions of logged MDT (Rel-18) | Xiaomi, CMCC |
R2-2409775 | Correction on the pre-condition for conditional reconfiguration for CPA | vivo |
R2-2409776 | Correction on the pre-condition for conditional reconfiguration for CPA, S-CPAC and LTM configuration | vivo |
R2-2409781 | Corrections on UL polarization parameters in NR NTN | CATT |
R2-2409782 | Corrections on UL polarization parameters in NR NTN | CATT |
R2-2410028 | Correction on NTN in FR1-NTN Bands | vivo |
R2-2410029 | Correction on NTN in FR1-NTN Bands | vivo |
R2-2410043 | Correction on handling successHO-Config during full configuration | Samsung, Ericsson |
R2-2410157 | Correction for RA resource information in RA-report | Sharp, Ericsson, Lenovo |
R2-2410162 | Correction for RA resource information in RA-report | Sharp, Ericsson, Lenovo |
R2-2410253 | Maximum number of SI messages | Nokia, Nokia Shanghai Bell |
R2-2410362 | Corrections to NTN SMTC configuration | ZTE Corporation, Sanechips |
R2-2410363 | Corrections to NTN SMTC configuration | ZTE Corporation, Sanechips |
R2-2410767 | Correction on PSCell mobility history information | Samsung, ZTE Corporation, Sanechips, Ericsson |
R2-2410775 | Correction on PSCell mobility history information | Samsung, ZTE Corporation, Sanechips, Ericsson |
R2-2410923 | Clarification for IDC solutions of logged MDT (Rel-18) | Xiaomi, CMCC |
R2-2411012 | Correction on PSCell mobility history information | Samsung, ZTE Corporation, Sanechips, Ericsson, Nokia |
R2-2411013 | Correction on PSCell mobility history information | Samsung, ZTE Corporation, Sanechips, Ericsson, Nokia |
R2-2411033 | Correction of maxSI messages [SI-SCHEDULING] | Xiaomi |
R2-2411034 | Correction of maxSI messages [SI-SCHEDULING] | Xiaomi |
R2-2411254 | Correction for RA resource information in RA-report | Sharp, Ericsson, Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2409749 | Network signalling of maximum number of UL segments - RRC processing delay | Qualcomm Incorporated |
R2-2409750 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2409751 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2409752 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2409753 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2409862 | RRC processing time for NW signalled UL segments | Samsung |
R2-2409992 | Mandatory support of Enhanced channel raster by RedCap UE | Ericsson |
R2-2409993 | Mandatory support of Enhanced channel raster by (e)RedCap UE | Ericsson |
R2-2410030 | Correction on Capability Reporting in FR1-NTN Bands | vivo |
R2-2410031 | Correction on Capability Reporting in FR1-NTN Bands | vivo |
R2-2410348 | Discussion on segmented UE capability | Huawei, HiSilicon |
R2-2410905 | Mandatory support of Enhanced channel raster by (e)RedCap UE | Ericsson |
R2-2410961 | Correction on Capability Reporting in FR1-NTN | vivo |
R2-2410970 | Correction on Capability Reporting in FR1-NTN | vivo |
R2-2411040 | Mandatory support of Enhanced channel raster by (e)RedCap UE | Ericsson |
R2-2411228 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
R2-2411229 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
R2-2411230 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
R2-2411231 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
R2-2411247 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2411248 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2411249 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2411250 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Qualcomm Incorporated |
R2-2411252 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
R2-2411253 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2410557 | Correction on emergency call back when eDRX is configured in RRC_INACTIVE | Nokia |
R2-2410558 | Correction on emergency call back when eDRX is configured in RRC_INACTIVE | Nokia |
R2-2410772 | On eDRX Operation with Emergency Services | ZTE Corporation |
R2-2411041 | LS on emergency services and eDRX | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409757 | Miscellaneous CR for Rel-17 SL relay | Huawei, HiSilicon, Philips International B.V., OPPO |
R2-2409758 | Miscellaneous CR for Rel-17 SL relay | Huawei, HiSilicon, Philips International B.V., OPPO |
R2-2409850 | Clarification on the L2 U2N Remote UE Measurement | CATT |
R2-2409851 | Clarification on the L2 U2N Remote UE Measurement | CATT |
R2-2410903 | Corrections on the L2 U2N Remote UE measurement | CATT |
R2-2410904 | Corrections on the L2 U2N Remote UE measurement | CATT |
TDoc | Title | Source |
---|---|---|
R2-2410579 | RRC correction on SidelinkUEInformationNR for NR sidelink relay communication transmission | Philips International B.V., NEC |
R2-2410580 | RRC correction on SidelinkUEInformationNR for NR sidelink relay communication transmission | Philips International B.V., NEC |
TDoc | Title | Source |
---|---|---|
R2-2410220 | Correction to MAC for R17 POS | Huawei, HiSilicon |
R2-2410221 | Correction to MAC for R17 POS | Huawei, HiSilicon |
R2-2411255 | Correction to MAC for R17 POS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2409565 | Correction on spatial relation info in SP SRS activation deactivation MAC CE (R17) | ZTE Corporation, Ericsson |
R2-2409566 | Correction on spatial relation info in SP SRS activation deactivation MAC CE (R18) | ZTE Corporation, Ericsson |
R2-2409607 | Correction on spatial relation info in SRS configuration (R17) | ZTE Corporation, Ericsson |
R2-2409608 | Correction on spatial relation info in SRS configuration (R18) | ZTE Corporation, Ericsson |
R2-2409628 | Corrections on the NOTE in the description of dl-PRS-MeasRRC-Inactive | CATT |
R2-2409629 | Corrections on the NOTE in the description of dl-PRS-MeasRRC-Inactive | CATT |
R2-2410222 | Correction to PRS priority subset for DL-AoD-r17 | Huawei, HiSilicon |
R2-2410223 | Correction to PRS priority subset for DL-AoD-r18 | Huawei, HiSilicon |
R2-2410825 | Correction of SRS type for TA alignment | Ericsson |
R2-2410826 | Correction of SRS type for TA alignment | Ericsson |
R2-2410985 | Correction on spatial relation info in SP SRS activation deactivation MAC CE (R17) | ZTE Corporation, Ericsson |
R2-2410986 | Correction on spatial relation info in SP SRS activation deactivation MAC CE (R18) | ZTE Corporation, Ericsson |
R2-2410987 | Correction on spatial relation info in SRS configuration (R17) | ZTE Corporation, Ericsson, Qualcomm, CATT, Samsung, vivo, Nokia, Xiaomi |
R2-2410988 | Correction on spatial relation info in SRS configuration (R18) | ZTE Corporation, Ericsson, Qualcomm, CATT, Samsung, vivo, Nokia, Xiaomi |
R2-2411169 | [AT128][402][POS] Spatial relation info source for positioning in RRC_INACTIVE (ZTE) | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409743 | Misc RRC corrections for SL enhancements | Huawei, HiSilicon |
R2-2409744 | Misc RRC corrections for SL enhancements | Huawei, HiSilicon |
R2-2410126 | Correction to random resource selection for sidelink | Ericsson |
R2-2410127 | Correction to random resource selection for sidelink | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409509 | Reply LS on IUC Scheme-2 and Random Selection (R1-2409174; contact: OPPO) | RAN1 |
R2-2409551 | Discussion on R1 LS Reply (R1-2409174) | OPPO |
R2-2409961 | Correction on SL DRX procedure | Apple |
R2-2409962 | Correction on SL DRX procedure | Apple |
R2-2410070 | Correction on SL DRX parameters | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410071 | Correction on SL DRX parameters | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410080 | Correction on unit of SL DRX timer | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410081 | Correction on unit of SL DRX timer | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410128 | Correction to MAC on resource selection | Ericsson |
R2-2410129 | Correction to MAC on resource selection | Ericsson |
R2-2410171 | Clarification on terminologies for SL IUC | ASUSTeK |
R2-2410172 | Clarification on terminologies for SL IUC | ASUSTeK |
R2-2410711 | Correction on IUC | LG Electronics Inc. |
R2-2410712 | Correction on IUC | LG Electronics Inc. |
R2-2410938 | Co-configuration of IUC scheme-2 and random selection | OPPO |
R2-2410939 | Correction on unit of SL DRX timer | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410940 | Correction on unit of SL DRX timer | ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson, Nokia, ASUSTeK, Apple, OPPO, LG |
R2-2410941 | Clarification on terminologies for SL IUC | ASUSTeK |
R2-2410942 | Clarification on terminologies for SL IUC | ASUSTeK |
R2-2410950 | Correction on IUC | LG |
R2-2411131 | Correction on IUC | LG |
R2-2411139 | Co-configuration of IUC scheme-2 and random selection | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2409646 | Miscellaneous corrections for Rel-18 SON/MDT | CATT, Samsung, Ericsson |
R2-2409810 | Correction for stored SDUs handling when a t-Reordering expires | Samsung |
R2-2409811 | Clarifications on DPC field in PHR MAC CE | Samsung |
R2-2410226 | Rapporteur CR for MT-SDT and CG-SDT enhancement [CG-SDTenh] | Huawei, HiSilicon |
R2-2410262 | Correction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson, ZTE |
R2-2410307 | Correction on QoE measurements release at successful handover from LTE/5GC to NR | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2410349 | Corrections on capabilities for eRedCap | Huawei, HiSilicon, LG Electronics Inc., Intel Corporation |
R2-2410368 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2410369 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2410396 | stage 2 Correction on additional buffer size table | NEC, Nokia (Rapporteur) |
R2-2410424 | Correction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson, ZTE |
R2-2410532 | Clarification for UE capability on UL traffic information | Huawei, HiSilicon |
R2-2410585 | Correction on the idc-TDM-AssistanceConfig | Huawei, HiSilicon, Xiaomi, Nokia, Intel Corporation, Ericsson, Apple, Samsung |
R2-2410615 | Paging clarification for MBS | SHARP Corporation |
R2-2410652 | Miscellaneous corrections on R18 SONMDT for 36.331 | Huawei, HiSilicon |
R2-2410653 | Correction on priority-based QoE measurements in TS 38.300 | Huawei, HiSilicon, China Unicom, Nokia, Ericsson, ZTE, Apple |
R2-2410698 | Miscellaneous corrections on R18 SONMDT for 36.331 | Huawei, HiSilicon |
R2-2410773 | Correction to the musim-AffectedBandsList and musim-AvoidedBandsList | ZTE Corporation |
R2-2410811 | Rapporteur correction on multicast MCCH | Huawei, HiSilicon, Samsung, CATT |
R2-2410812 | Correction on multicast reception in RRC_INACTIVE upon paging | Huawei, HiSilicon, Nokia, CATT, Ericsson, Samsung, Apple, ZTE |
R2-2410859 | Stage 2 correction on additional buffer size table | NEC, Nokia (Rapporteur) |
R2-2410896 | Rapporteur correction on multicast MCCH | Huawei, HiSilicon, Samsung, CATT |
R2-2410899 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2410910 | Correction to the musim-AffectedBandsList and musim-AvoidedBandsList | ZTE Corporation |
R2-2410919 | Correction on QoE measurements release at successful handover from LTE/5GC to NR | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2410920 | Correction of Enhancement on NR QoE management and optimizations for diverse services | Ericsson, ZTE |
R2-2411080 | Correction on the idc-TDM-AssistanceConfig | Huawei, HiSilicon, Xiaomi, Nokia, Intel Corporation, Ericsson, Apple, Samsung |
R2-2411081 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2411082 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2411083 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2411084 | Guidelines on implementing FRx/xDD differentiation in per UE capability | Huawei, HiSilicon |
R2-2411161 | Correction on priority-based QoE measurements in TS 38.300 | Huawei, HiSilicon, China Unicom, Nokia, Ericsson, ZTE, Apple |
TDoc | Title | Source |
---|---|---|
R2-2409506 | LS on higher layer parameters for DCI format 2_3 (R1-2407534; contact: CATT) | RAN1 |
R2-2409507 | LS on Rel-18 RAN1 UE features list for NR after RAN1#118bis (R1-2409045; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2409917 | Miscellaneous updates and Introduction of DPC UE capabilities for Rel-18 WIs | Intel Corporation |
R2-2409918 | Miscellaneous updates and Introduction of DPC UE capabilities for Rel-18 WIs | Intel Corporation |
R2-2410894 | Miscellaneous updates for Rel-18 WIs | Intel Corporation |
R2-2410895 | Miscellaneous updates for Rel-18 WIs | Intel Corporation |
R2-2411245 | Miscellaneous updates for Rel-18 WIs | Intel Corporation |
R2-2411246 | Miscellaneous updates for Rel-18 WIs | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2410225 | Rapporteur MAC CR for RACH-less HO and LTM [RACH-lessHO] | Huawei, HiSilicon, Qualcomm |
R2-2410415 | Correction on RACH-less handover procedure in TS38.321 [RACH-lessHO] | CATT, Samsung, InterDigital |
R2-2410745 | Correction on RACH-less handover fallback [RACH-lessHO] | Huawei, HiSilicon, Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2410855 | Correction on RACH-less handover fallback [RACH-lessHO] | Huawei, HiSilicon, Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2411093 | Correction on RACH-less handover fallback [RACH-lessHO] | Huawei, HiSilicon, Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2411178 | Correction on RACH-less handover procedure in TS38.321 [RACH-lessHO] | CATT, Samsung, InterDigital, Ericsson, Qualcomm Incorporated, LG Electronics Inc., Huawei, HiSilicon, vivo |
TDoc | Title | Source |
---|---|---|
R2-2410726 | Clarification on NCR-MT Mandatory features | |
R2-2410809 | Correction on the NCR-MT capability | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2410207 | Correction on Band Selection and Cell Barring for Aerial UEs | Ericsson |
R2-2411120 | Correction on Band Selection and Cell Barring for Aerial UEs | Ericsson |
R2-2411202 | Correction on Band Selection and Cell Barring for Aerial UEs | Ericsson, Samsung, Qualcomm Inc., Nokia |
TDoc | Title | Source |
---|---|---|
R2-2409545 | Correction on MT-SDT Capability for NR-NTN Case | vivo, ZTE Corporation, Sanechips, Huawei, HiSilicon, Ericsson |
R2-2410227 | Correction to RRC for CG-SDT enhancement [CG-SDTenh] | Huawei, HiSilicon |
R2-2411223 | Correction to RRC for CG-SDT enhancement [CG-SDTenh] | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2409813 | Miscellaneous corrections on BAP for IAB | Huawei, HiSilicon (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2410611 | Clarification on the definition of eRedCap UEs | Ericsson, Sequans Communications |
TDoc | Title | Source |
---|---|---|
R2-2409513 | LS on the time period for R18 preamble repetition (R1-2409262; contct: Huawei) | RAN1 |
R2-2410447 | Discussion on RAN1 LS on time period in Msg1 repetition | ZTE Corporation |
R2-2410543 | Discussion on RAN1 LS on time period | Ericsson |
R2-2410617 | Discussion on LS from RAN1 on the time period for R18 preamble repetition | Huawei, HiSilicon |
R2-2410819 | Discussion on RAN1 LS on the time period for R18 preamble repetition | LG Electronics Inc. |
R2-2411167 | Summary of [AT128][008][CE] Response LS to RAN1 (Huawei) | Huawei |
R2-2411168 | Reply LS on the time period for R18 preamble repetition | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409693 | Measurements on the carrier of SSB-less SCell | NEC |
R2-2410169 | Miscellaneous corrections for NES | ZTE Corporation, Sanechips |
R2-2410259 | SSBLess handling | Nokia |
R2-2410301 | Network energy savings for NR rapporteur RRC CR | Huawei, HiSilicon |
R2-2410531 | Cell DRX MPS exemption in RA | Peraton Labs |
R2-2411094 | Network energy savings for NR rapporteur RRC CR | Huawei, HiSilicon |
R2-2411104 | Miscellaneous corrections for NES | ZTE Corporation, Sanechips |
R2-2411209 | Cell DRX MPS exemption in RA | Peraton Labs, CISA ECD, AT&T, Verizon, FirstNet, Qualcomm, ZTE |
R2-2411260 | Miscellaneous corrections for NES | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2409647 | Corrections on SPR configuration release and logging PSCell identity | CATT |
R2-2409648 | Corrections on RA Report retrieval | CATT |
R2-2409986 | NR-U related RA information in SCGFailureInformation | Nokia |
R2-2410045 | Correction on Inter-RAT SHR | Samsung |
R2-2410057 | Correction on logging RSSI measurements in RLF report and SHR | Samsung |
R2-2411011 | Correction on logging RSSI measurements in RLF report and SHR | Samsung |
R2-2411014 | NR-U related RA information in SCGFailureInformation | Nokia |
R2-2411036 | Correction on logging PSCell identity | CATT |
R2-2411165 | Correction in the optionality of NR-U related information | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2409994 | Clarification of UE capability restrictions in MUSIM | Ericsson, Samsung, Xiaomi, LG Electronics Inc., Vivo |
R2-2410350 | Corrections for MUSIM in 38.300 | Huawei, HiSilicon, Samsung, vivo |
R2-2411105 | Clarification of UE capability restrictions in MUSIM | Ericsson, Huawei, HiSilicon, Samsung, Xiaomi, LG Electronics Inc., Vivo |
TDoc | Title | Source |
---|---|---|
R2-2409510 | LS on TDD UL/DL Configuration for Two TA (R1-2409179; contact: Ericsson) | RAN1 |
R2-2409715 | Correction on simultaneousU-TCI-UpdateListx | CATT, Ericsson |
R2-2410173 | Discussion on supporting 8Tx in MAC specification | ASUSTeK |
R2-2410174 | Correction on supporting 8Tx in MAC specification | ASUSTeK |
R2-2410175 | Correction on PHR for MIMO | ASUSTeK |
R2-2410397 | On LS on TDD UL/DL Configuration for Two TA | Ericsson |
R2-2410528 | Correction on PHR for MIMO STx2P multi-panel scheme | Samsung, LG, Huawei, CATT, Ericsson |
R2-2410624 | Harmonization of 8Tx in MAC specification | ZTE Corporation |
R2-2410625 | Clarification to 38.321 on R17 PHR MAC CE for mTRP PUSCH Repetition | ZTE Corporation |
R2-2410951 | Report of [AT128][201][MIMOevo] Proposals/CRs for PHR | Samsung |
R2-2410952 | Report of [AT127bis][202][MIMOevo] Discuss on the modelling and review the MAC CR for 8Tx 2TB if the modelling is agreeable (ASUSTeK, ZTE) | ASUSTeK, ZTE |
R2-2410953 | [Draft] LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP | CATT |
R2-2410954 | Correction on TDD UL/DL Configuration for Two TA | Ericsson |
R2-2411076 | Harmonization of 8Tx in MAC specification | ZTE Corporation |
R2-2411220 | LS on UL 8Tx | Samsung |
R2-2411244 | LS on differentiation of sDCI mTRP, mDCI mTRP and sTRP | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409599 | Correction on Group Paging Handling | CATT, CBN |
R2-2409756 | Misc correction on NR MBS enhancement | ZTE Corporation, Sanechips |
R2-2409939 | Clarification on group paging procedure | Samsung |
R2-2410254 | Multicast reception after reselection to cell with MCCH | Nokia, Samsung, Ericsson, ZTE |
R2-2410630 | Correction on applying of PTM configuration in Paging procedure | SHARP Corporation |
R2-2410876 | Correction on Group Paging Handling | CATT, CBN, China Broadnet |
R2-2411004 | Multicast reception after reselection to cell with MCCH | Nokia, Samsung, Ericsson, ZTE |
R2-2411005 | Correction on Group Paging Handling | CATT, CBN, China Broadnet |
R2-2411008 | Clarification on group paging procedure | Samsung, Ericsson, Huawei, HiSilicon, ZTE, Nokia |
R2-2411009 | Multicast reception after reselection to cell with MCCH | Nokia, Samsung, Ericsson, ZTE |
R2-2411258 | Multicast reception after reselection to cell with MCCH | Nokia, Samsung, Ericsson, ZTE |
TDoc | Title | Source |
---|---|---|
R2-2410654 | Correction on UE behaviours when reporting SRB is modified | Huawei, HiSilicon |
R2-2410659 | Miscellaneous correction on QoE measurement | Samsung |
R2-2411003 | Miscellaneous correction on QoE measurement | Samsung |
R2-2411006 | Report of [AT128][503][QoE] QoE reporting SRB change issue | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2409852 | Further Discussion on the SN Gap Report | CATT |
R2-2410249 | Correction to multi-PUSCH configured grant | Huawei, HiSilicon, Qualcomm, Apple, vivo, Nokia, Nokia Shanghai Bell |
R2-2410729 | Correction for Delay Critical Indication from PDCP to RLC | Samsung, LG Electronics Inc., Nokia, Huawei, HiSilicon, Ericsson |
R2-2411067 | Correction on DSR cancellation | CMCC |
R2-2411106 | Correction to multi-PUSCH configured grant | Huawei, HiSilicon, Qualcomm, Apple, vivo, Nokia, Nokia Shanghai Bell |
R2-2411107 | Correction for Delay Critical Indication from PDCP to RLC | Samsung, LG Electronics Inc., Nokia, Huawei, HiSilicon, Ericsson, Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2409777 | Coexistence of (e)RedCap UEs and LTM and other MAC corrections | vivo |
R2-2409923 | Clarification on LTM capabilities | |
R2-2410000 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
R2-2410116 | Correction on UE receiver features | China Telecom |
R2-2410219 | Correction to co-existence of multi-PUSCH CG and CG-SDTenh [CG-SDTenh] | Huawei, HiSilicon |
R2-2410446 | On supporting LTM for (e)RedCap UEs | ZTE Corporation |
R2-2410457 | Coexistence of NCR and CPAC with (e)RedCap | Ericsson, ZTE Corporation |
R2-2410458 | Coexistence of LTM with RedCap | Ericsson |
R2-2410516 | Correction to LTM MAC CE based CFRA with MSG1 repetition | Huawei, HiSilicon |
R2-2410696 | Transmit operation of SR and SN gap report | Nokia, Nokia Shanghai Bell |
R2-2410758 | Clarification on SIBs validity | Google Korea LLC |
R2-2410820 | Correction to co-existence of multi-PUSCH CG and CG-SDTenh [CG-SDTenh] | Huawei, HiSIlicon |
R2-2411203 | Correction on UE receiver features | China Telecom |
R2-2411212 | Correction to LTM MAC CE based CFRA with MSG1 repetition | Huawei, HiSilicon |
R2-2411227 | Miscellaneous non-controversial corrections Set XXIII | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409567 | Correction on assistance data transfer in SL positioning for stage-2 | ZTE Corporation |
R2-2409618 | Corrections of location time stamp, RSTD and RTOA report | CATT |
R2-2409683 | RRC correction on NR sidelink positioning | Philips International B.V., Ericsson |
R2-2409916 | Miscellaneous corrections to SLPP specification | Intel Corporation |
R2-2410214 | Rapporteur CR to MAC spec for R18 Positioning | Huawei, HiSilicon, ASUSTek |
R2-2410215 | Rapporteur CR to IDLE mode procedure for R18 Positioning | Huawei, HiSilicon, Phillips |
R2-2410217 | Correction on SLPP | Huawei, HiSilicon |
R2-2410494 | Miscellaneous RRC Positioning Correction | Ericsson |
R2-2410495 | Correction of misplaced else condition of SL Positioning clause | Ericsson |
R2-2410644 | Clarification on the maximum number of other UEs in sidelink positioning | vivo |
R2-2410989 | Correction on assistance data transfer in SL positioning for stage-2 | ZTE Corporation |
R2-2410990 | Corrections of location time stamp, RSTD and RTOA report | CATT |
R2-2410991 | Miscellaneous corrections to SLPP specification | Intel Corporation |
R2-2410992 | Rapporteur CR to IDLE mode procedure for R18 Positioning | Huawei, HiSilicon, Phillips |
R2-2410993 | Clarification on the maximum number of other UEs in sidelink positioning | vivo |
R2-2410994 | Correction on SLPP | Huawei, HiSilicon |
R2-2411061 | Miscellaneous RRC Positioning Correction | Ericsson |
R2-2411079 | Correction on SLPP | Huawei, HiSilicon |
R2-2411112 | Rapporteur CR to IDLE mode procedure for R18 Positioning | Huawei, HiSilicon, Phillips |
R2-2411126 | Summary of email discussion [AT128][404] | Huawei, HiSilicon |
R2-2411127 | Rapporteur CR to MAC spec for R18 Positioning | Huawei, HiSilicon, ASUSTek |
R2-2411181 | Rapporteur CR to MAC spec for R18 Positioning | Huawei, HiSilicon, ASUSTek |
TDoc | Title | Source |
---|---|---|
R2-2409508 | Reply LS on CSI-RS and SRS for spatial relation (R1-2409097; contact: ZTE) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2410497 | Miscellaneous corrections for Positioning | Ericsson |
R2-2411171 | Miscellaneous corrections for Positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409568 | Correction on tx timestamp request in SL-RTT | ZTE Corporation |
R2-2409826 | Clarification on SLPP session ID existence in SLPP messages between target UE and LMF | vivo |
R2-2410132 | Corrections on capabilities for FG R1 41-1-19a and 41-1-19b in IE CommonSL-PRS-MethodsIEsProvideCapabilities | Lenovo |
R2-2410218 | Discussion on the issues in GAD in SLPP | Huawei, HiSilicon |
R2-2410995 | Correction on tx timestamp request in SL-RTT | ZTE Corporation |
R2-2411121 | Corrections on capabilities for FG R1 41-1-19a and 41-1-19b in IE CommonSL-PRS-MethodsIEsProvideCapabilities | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2409619 | Correction of nr-DL-PRS-RSCPD-ReportingRRC-Inactive in NR-DL-TDOA-MeasurementCapability | CATT |
R2-2410401 | Correction for the UE capability on PosSRS-BWA-RRC-Inactive | Xiaomi |
R2-2410402 | Correction for the UE capability on PosSRS-BWA-RRC-Inactive | Xiaomi |
R2-2411122 | Correction of NR-DL-TDOA-MeasurementCapability and NR-Multi-RTT-MeasurementCapability | CATT |
R2-2411123 | Correction for the UE capability on posSRS-BWA-RRC-Inactive | Xiaomi, Lenovo |
R2-2411124 | Correction for the UE capability on posSRS-BWA-RRC-Inactive | Xiaomi, Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2409569 | Correction on the dedicated pool interest frequency request in SUI | ZTE Corporation |
R2-2409620 | Clarification on the activation mechanism of srs-PosConfigOrActivationReq | CATT, Ericsson |
R2-2409639 | Correction on NW restriction for dedicated SL-PRS resource pool | vivo, Ericsson |
R2-2409656 | Correction for UE indicating its preference TX/RX frequencies for sidelink positioning in SUI | vivo |
R2-2410216 | Correction for positioning SRS CA in RRC_INACTIVE | Huawei, HiSilicon, Ericsson, Samsung |
R2-2410224 | Correction to sidelinkUEInformation for SL POS | Huawei, HiSilicon |
R2-2410498 | Sidelink RRC Positioning Correction | Ericsson, vivo |
R2-2410584 | RRC correction on NR sidelink positioning | Philips International B.V. |
R2-2411129 | Correction for positioning SRS CA in RRC_INACTIVE | Huawei, HiSilicon, Ericsson, Samsung |
R2-2411130 | Correction for UE indicating its preference TX/RX frequencies for sidelink positioning in SUI | vivo |
R2-2411170 | Sidelink RRC Positioning Correction | Ericsson, vivo, ZTE Corporation |
R2-2411172 | RRC correction on NR sidelink positioning | Philips International B.V. |
R2-2411189 | Correction for positioning SRS CA in RRC_INACTIVE | Huawei, HiSilicon, Ericsson, Samsung |
R2-2411251 | LS on co-existence of SL-CA and SL PRS transmission/reception for Dedicated SL-PRS resource pool | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2410176 | Correction on prioritization between SR and SL-PRS transmission | ASUSTeK |
TDoc | Title | Source |
---|---|---|
R2-2410133 | Correction on the capability description for posSRS-BWA-RRC-Inactive-r18 (FG R1 41-4-8) | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2409936 | Misc state 2 corrections for LTM mobility | Vodafone, Ericsson, Nokia, ZTE |
R2-2410459 | Misc RRC corrections for feMob | Ericsson |
R2-2410514 | Miscellaneous corrections for LTM | Huawei, HiSilicon |
R2-2410801 | Corrections for mobility enhancements in stage-2 | ZTE Corporation, Ericsson |
R2-2410924 | Miscellaneous corrections for LTM | Huawei, HiSilicon |
R2-2410925 | Misc Stage-2 corrections for LTM mobility | Vodafone, Ericsson, Nokia, ZTE |
R2-2410926 | Correction for mobility enhancements in stage-2 | ZTE Corporation, Ericsson |
R2-2411257 | Correction for mobility enhancements in stage-2 | ZTE Corporation, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409900 | Corrections on remaining LTM RRC issues | MediaTek Inc. |
R2-2409922 | Clarification on conditional, DAPS and LTM candidate configurations | |
R2-2410018 | Correction on the field description of ltm-UE-MeasuredTA-ID | CATT |
R2-2410019 | Correction on the field description of ltm-NoResetID | CATT |
R2-2410055 | Clarification on inter-band LTM capabilities | Qualcomm Inc., OPPO |
R2-2410063 | Remaining issues on L2 reset for LTM | NEC |
R2-2410117 | Correction on LTM UE capability based on the LS from RAN1 | MediaTek Inc. |
R2-2410442 | Miscellaneous Rel-18 LTM Aspects and Corrections | Nokia |
R2-2410449 | Stage 2 TP for simultaneous execution of CHO and SCG LTM | Lenovo |
R2-2410460 | Issues on capabilities for LTM | Ericsson |
R2-2410461 | Remaining issues on LTM | Ericsson |
R2-2410462 | Summary of RRC proposals for feMob | Ericsson |
R2-2410513 | LTM UE capabilities for inter-frequency L1 measurements | Huawei, HiSilicon |
R2-2410515 | Further MAC corrections | Huawei, HiSilicon |
R2-2410517 | MAC CR rapporteur summary | Huawei, HiSilicon |
R2-2410628 | Clarification to 38.321 on RACH Initiation for RACH based LTM | ZTE Corporation |
R2-2410707 | Miscellaneous corrections for SCPAC | Nokia |
R2-2410737 | Restrictions on simultaneous conditional, DAPS and LTM candidate configurations | |
R2-2410802 | Correction for mobility enhancements in stage-2 | ZTE Corporation, Ericsson |
R2-2410921 | Summary of [AT128][101][MOB] | Ericsson |
R2-2410922 | Misc RRC corrections for feMob | Ericsson |
R2-2410947 | [Draft] LS on LTM UE capabilities for cross-band operation | Qualcomm |
R2-2410948 | Scope of interFreqL1-MeasConfig-r18 | Huawei, HiSilicon |
R2-2410949 | Scope of interFreqL1-MeasConfig-r18 | Huawei, HiSilicon |
R2-2411135 | LS on LTM UE capabilities for cross-band operation | RAN2 |
R2-2411137 | Misc RRC corrections for feMob | Ericsson |
R2-2411219 | LS on LTM UE capabilities for cross-band operation | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409589 | Corrections on location based measurements and need code for IoT NTN | CATT |
R2-2410056 | Applicability of optional UE Capabilities for NB-IoT | Qualcomm Inc. |
R2-2410422 | Miscellaneous corrections to TS 36.331 for IoT NTN | Huawei, HiSilicon |
R2-2410488 | Corrections on distance-based measurements during T-service for IoT NTN | Samsung |
R2-2410810 | Correction on measurement | Huawei, HiSilicon |
R2-2410860 | Corrections on distance-based measurements during T-Service for IoT NTN | Samsung |
R2-2410867 | IoT NTN UE capabilities correction for GNSS and HARQ enhancements | Ericsson |
R2-2410884 | IoT NTN Stage 2 correction to eMTC CHO | Ericsson (Rapporteur) |
R2-2410962 | Correction on measurement | Huawei, HiSilicon, Apple |
R2-2410963 | Corrections on location based measurements and need code for IoT NTN | CATT |
R2-2411113 | Applicability of optional UE Capabilities for NB-IoT | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R2-2409518 | Reply LS on UE Location Information for NB-IoT NTN (R3-245819; contact: Nokia) | RAN3 |
TDoc | Title | Source |
---|---|---|
R2-2409543 | Correction on UE Location Information Reporting in IoT-NTN | vivo, Ericsson, Nokia, Nokia Shanghai Bell |
R2-2409590 | Corrections on the reference of satellite ID | Huawei, HiSilicon, Apple |
R2-2409947 | UE feature for SIB33(-NB) reception in RRC_IDLE state in a TN cell | Apple, Qualcomm Incorporated, Samsung, Huawei, HiSilicon, Ericsson, CATT, MediaTek Inc. |
R2-2410308 | Correction on SIB33(-NB) for IoT NTN | Nokia, Nokia Shanghai Bell |
R2-2410480 | Clarification on TN-NTN mobility for IoT NTN | ZTE Corporation, Sanechips |
R2-2410481 | Various corrections for IoT NTN Rel-18 | Samsung |
R2-2410857 | Scope and uniqueness of satelliteId | Nordic Semiconductor, Samsung |
R2-2410866 | Correction to satellite ID in system infromation | Ericsson, Samsung |
R2-2410892 | Scope and uniqueness of satelliteId | Nordic Semiconductor, Samsung |
R2-2410964 | Correction on SIB33(-NB) for IoT NTN | Nokia, Nokia Shanghai Bell, Samsung |
R2-2410965 | UE feature for SIB33(-NB) reception in RRC_IDLE state in a TN cell | Apple, Qualcomm Incorporated, Samsung, Huawei, HiSilicon, Ericsson, CATT, MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2410541 | Miscellaneous corrections to NR NTN | Samsung |
R2-2410966 | Miscellaneous corrections to NR NTN | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2409505 | LS on FR2-NTN inclusion to specifications (R1-2407406; contact: vivo) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2409544 | Correction on NTN in FR2 bands | vivo, ZTE Corporation, Sanechips |
R2-2409606 | Correction on coexistence between CHO and satellite switching with re-synchronization | CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2409948 | UE feature for SIB19 reception in RRC_IDLE/RRC_INACTIVE state in a TN cell | Apple, Qualcomm Incorporated, Samsung, Huawei, HiSilicon, CATT, MediaTek Inc. |
R2-2410364 | Miscellaneous corrections on NTN in FR2 bands | ZTE Corporation, Vivo, Sanechips |
R2-2410438 | Various Corrections and Open Points for Rel-18 NTN | Nokia, Nokia Shanghai Bell |
R2-2410527 | Discussion on some corrections | Samsung |
R2-2410642 | Correction on RACH-less HO in NR-NTN | vivo, Samsung, Nokia, Nokia Shanghai Bell, THALES, Huawei, HiSilicon, CATT |
R2-2410750 | Remaining issues on SMTC | Huawei, HiSilicon |
R2-2410865 | Clarification of reference location within the MO for NR NTN Rel-18 | Ericsson |
R2-2410878 | Remaining open issues of satellite switch with resync | Sequans Communications |
R2-2410967 | Draft LS on RACH-less HO in NTN | Nokia |
R2-2410971 | Report of [AT128][301][NR NTN] SMTC issues | Huawei |
R2-2410973 | Draft LS soft satellite switch with resync | Huawei |
R2-2410977 | Miscellaneous corrections on NTN in FR2 bands | ZTE Corporation, vivo, Sanechips |
R2-2410978 | LS on soft satellite switch with resync | RAN2 |
R2-2410979 | Clarification on the UE feature for cell reselection from TN to NTN | Apple, Qualcomm Incorporated, Samsung, Huawei, HiSilicon, CATT, MediaTek Inc. |
R2-2410980 | Correction on coexistence between CHO and satellite switching with re-synchronization | CATT, Nokia, Nokia Shanghai Bell, Ericsson |
R2-2411191 | LS on inter-gNB RACH-less HO in NTN | RAN2 |
R2-2411192 | [Draft] LS on UE Capabilities for FR2-NTN | vivo |
R2-2411193 | Clarification on the UE feature for cell reselection from TN to NTN | Apple, Qualcomm Incorporated, Samsung, Huawei, HiSilicon, CATT, MediaTek Inc. |
R2-2411195 | LS on UE Capabilities for FR2-NTN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409631 | Corrections on security for L2 U2U relay | vivo |
R2-2409682 | RRC correction on NR SL U2U relay operation | Philips International B.V. |
R2-2409735 | Clarification for ul-DataSplitThreshold setting in multi-path relay | OPPO |
R2-2409759 | Miscellaneous CR for Rel-18 SL relay enhancement | Huawei, HiSilicon |
R2-2409760 | Correction to error handling for U2U operation | Huawei, HiSilicon |
R2-2410918 | Corrections on security for L2 U2U relay | vivo |
R2-2411185 | Miscellaneous and editorial changes for NR sidelink relay enhancement | LG Electronics, ZTE Corporation, Sanechips, Philips International B.V. |
TDoc | Title | Source |
---|---|---|
R2-2410197 | U2U Relays, Local ID Assignment | Ericsson |
R2-2411000 | U2U Relays, Local ID Assignment | Ericsson |
R2-2411176 | U2U Relays, Local ID Assignment | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409853 | Clarification on the Terminology of Peer UE | CATT |
R2-2409960 | Corrections on RRC SRAP configuration for L2 U2U | Apple, ZTE |
R2-2410614 | Corrections for U2U relay measurements | ZTE Corporation, Sanechips, Huawei, Hisilicon, OPPO, CATT, Apple |
R2-2410996 | Corrections on the Terminology of Peer UE | CATT |
R2-2410997 | Corrections on RRC SRAP configuration for L2 U2U | Apple, ZTE |
R2-2410998 | Corrections for U2U relay measurements | ZTE Corporation, Sanechips, Huawei, Hisilicon, OPPO, CATT, Apple |
R2-2411182 | Corrections on the Terminology of Peer UE | CATT, ZTE, Huawei |
R2-2411183 | Corrections on RRC SRAP configuration for L2 U2U | Apple, ZTE |
TDoc | Title | Source |
---|---|---|
R2-2410586 | RLC correction for multi-path relay with N3C | Huawei, HiSilicon |
R2-2410999 | RLC correction for multi-path relay with N3C | Huawei, HiSilicon |
R2-2411166 | CR to TS 38.323 Extension of N3C number | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2409549 | Co-configuration of random/partial-sensing resource selection and Co-Ex | OPPO |
R2-2409729 | TP for SL enhancemen in TS 38.321 | NEC Corporation |
R2-2410721 | Correction on Co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics Inc. |
R2-2410723 | Correction on MCSt | LG |
R2-2410724 | MAC correction for resource selection of MCSt | LG |
R2-2410727 | Correction on Co-channel coexistence for LTE sidelink and NR sidelink | LG Electronics Inc. |
R2-2411115 | Correction on Co-channel coexistence for LTE sidelink and NR sidelink | LG |
R2-2411140 | Correction on carrier selection for SL evolution | NEC |
R2-2411162 | Correction on carrier selection for SL evolution | NEC |
TDoc | Title | Source |
---|---|---|
R2-2410001 | Correction on carrier selection for SL evolution | Huawei, HiSilicon, LG Electronics Inc., Apple, Nokia |
R2-2410072 | Correction on carrier selection for IUC | ZTE Corporation, Sanechips, Ericsson, Apple, Nokia |
R2-2410073 | Correction on MCSt | ZTE Corporation, Sanechips |
R2-2410147 | discussion on remaining issue of resource selection for MCSt | Ericsson |
R2-2410177 | Correction on SL IUC timer for SL CA | ASUSTeK |
R2-2410583 | RRC correction on SidelinkUEInformationNR for NR sidelink transmission | Philips International B.V., NEC |
R2-2410612 | Stage 2 Corrections on MCSt | InterDigital Inc, Apple |
R2-2410714 | MAC corrections on Release-18 Sidelink evolution | LG |
R2-2410943 | Stage 2 Corrections on MCSt | InterDigital Inc, Apple |
R2-2410944 | Correction on carrier selection for SL evolution | Huawei, HiSilicon, LG Electronics Inc., Apple, Nokia |
R2-2410945 | Discussion on MCSt | ZTE Corporation, Sanechips |
R2-2410946 | Correction to MCSt for sidelink | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2410536 | Correction for cell barring for 2Rx XR UE [2Rx_XR_Device] | Huawei, HiSilicon, Xiaomi, Ericsson, LGE, ZTE Corporation |
R2-2410833 | Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] | Huawei, HiSilicon |
R2-2410834 | Introduction of new capability for intra-band EN-DC channel spacing [Intra-Band_EN-DC_Channelspacing] | Huawei, HiSilicon |
R2-2411075 | Correction for cell barring for 2Rx XR UE [2Rx_XR_Device] | Huawei, HiSilicon, Xiaomi, Ericsson, LGE, ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409747 | Clarifications on cell barring behaviour | Qualcomm Incorporated, Huawei, ZTE, Ericsson, LG Electronics Inc., Nokia, Samsung, Vivo |
R2-2409748 | Clarifications on cell barring behaviour | Qualcomm Incorporated, Huawei, ZTE, Ericsson, LG Electronics Inc., Nokia, Samsung, Vivo |
R2-2410192 | Enhancement to measurement report | OPPO |
R2-2410206 | Correction on the 2RxXR and Aerial UEs [2Rx_XR_Device] | Ericsson, Samsung, Qualcomm Inc. |
R2-2410463 | Correction on reporting the best cell change [meas_report_enh] | Ericsson |
R2-2410535 | Correction for Paging monitoring during SDT [CG-SDT-Enh] | Huawei, HiSilicon, LG Electronics Inc., ZTE Corporation, Sanechips, MediaTek Inc. |
R2-2410537 | Corrections on the conditional presence of barring exemption for emergency call [EM_Call_Exemption] | Huawei, HiSilicon |
R2-2411108 | Correction for Paging monitoring during SDT [CG-SDT-Enh] | Huawei, HiSilicon, LG Electronics Inc., ZTE Corporation, Sanechips, MediaTek Inc. |
R2-2411109 | Clarifications on cell barring behaviour [2Rx_XR_Device] [EM_Call_Exemption] | Qualcomm Incorporated, Huawei, ZTE, Ericsson, LG Electronics Inc., Nokia, Samsung, Vivo |
R2-2411110 | Clarifications on cell barring behaviour [2Rx_XR_Device] [EM_Call_Exemption] | Qualcomm Incorporated, Huawei, ZTE, Ericsson, LG Electronics Inc., Nokia, Samsung, Vivo |
TDoc | Title | Source |
---|---|---|
R2-2410041 | Correction on SPR content determination | |
R2-2410487 | Clarification on SCS of Timing Advance Report MAC CE for ATG | Samsung, Qualcomm Inc., Huawei, HiSilicon, CMCC, CATT |
R2-2410664 | Supporting R17 early implementation of R18 measurement gap enhancements | Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, BT Plc., Telecom Italia, CATT, Samsung |
R2-2410851 | Correction on UE capability for multi-carrier enhancements | NTT DOCOMO, INC., Huawei, HiSilicon |
R2-2410852 | Correction on UE capability for multi-carrier enhancements | NTT DOCOMO, INC., Huawei, HiSilicon |
R2-2410872 | Clarification on SCS for Timing Advance Report MAC CE for ATG | Samsung, Qualcomm Inc., Huawei, HiSilicon, CMCC, CATT |
R2-2410897 | Correction on UE capability for multi-carrier enhancements | NTT DOCOMO, INC., Huawei, HiSilicon |
R2-2410898 | Correction on UE capability for multi-carrier enhancements | NTT DOCOMO, INC., Huawei, HiSilicon |
R2-2411074 | Correction on UE capability for multi-carrier enhancements | NTT DOCOMO, INC., Huawei, HiSilicon |
R2-2411111 | Clarification on SCS for Timing Advance Report MAC CE for ATG | Samsung, Qualcomm Inc., Huawei, HiSilicon, CMCC, CATT |
R2-2411261 | Clarification on SCS for Timing Advance Report MAC CE for ATG | Samsung, Qualcomm Inc., Huawei, HiSilicon, CMCC, CATT |
TDoc | Title | Source |
---|---|---|
R2-2409523 | LS on Rel-19 NR channel BW less than 5MHz for FR1 (R4-2417119; contact: Intel) | RAN4 |
R2-2409654 | Discussion on UE capability on less than 5MHz (LS R4-2417119) | CATT |
R2-2409778 | Correction on UE capability on ncd-SSB-BWP-Wor-r18 | vivo, Qualcomm Incorporated, Guangdong Genius |
R2-2410148 | Correction on HST FR2 | Ericsson |
R2-2410260 | Less than 5Mhz and carrier configuration | Nokia |
R2-2410302 | Clarification of offsetThresholdTA-r18 for NR ATG | Huawei, HiSilicon, CATT, Nokia, Nokia Shanghai Bell, LG Electronics Inc. |
R2-2410486 | Correction on SCS applied for TAR offset threshold for ATG | Samsung, ZTE, Qualcomm Inc., Ericsson |
R2-2410665 | Supporting R17 early implementation of R18 measurement gap enhancements | Nokia, Nokia Shanghai Bell, Ericsson, ZTE Corporation, BT Plc., Telecom Italia, CATT, Samsung |
R2-2410749 | Simultaneous reception of EUTRAN data and NR SSB with different numerology | Huawei, HiSilicon |
R2-2410768 | Report of [Post127bis][011][less5MHz] 331 CR (ZTE) | ZTE Corporation |
R2-2410769 | Correction on the Less than 5M Bandwidth | ZTE Corporation, vivo |
R2-2410803 | Alternative solution for clarification on the unit of offsetThresholdTA-r18 for ATG | ZTE Corporation |
R2-2410839 | Correction on BWP operation without bandwidth restriction | Huawei, HiSilicon, ZTE Corporation, Ericsson |
R2-2411153 | Correction on UE capability on ncd-SSB-BWP-Wor-r18 | vivo, Qualcomm Incorporated, Guangdong Genius |
R2-2411163 | Correction on the Less than 5M Bandwidth | ZTE Corporation, vivo |
R2-2411164 | Correction on the Less than 5M Bandwidth | ZTE Corporation |
R2-2411180 | Clarification on the unit of offsetThresholdTA-r18 for ATG | ZTE Corporation |
R2-2411210 | Capability on measurement gap enhancements | Huawei, HiSilicon |
R2-2411211 | Capability on measurement gap enhancements | Huawei, HiSilicon |
R2-2411262 | Clarification on the unit of offsetThresholdTA-r18 for ATG | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2410845 | Correction on applicable BWP for multi-cell scheduling | NTT DOCOMO, INC., Nokia, Samsung, Huawei |
R2-2410848 | Discussion on applicable BWP for Multi-cell scheduling | NTT DOCOMO, INC., Nokia, Samsung |
R2-2411256 | Correction on applicable BWP for multi-cell scheduling | NTT DOCOMO, INC., Nokia, Samsung, Huawei |
TDoc | Title | Source |
---|---|---|
R2-2410496 | Introduction of LCS User Plane | Ericsson, Intel Corporation, Huawei, HiSilicon, ZTE Corporation, vivo, Qualcomm Incorporated, Samsung, CATT |
R2-2411066 | Introduction of LCS User Plane | Ericsson, Intel Corporation, Huawei, HiSilicon, ZTE Corporation, vivo, Qualcomm Incorporated, Samsung, CATT |
TDoc | Title | Source |
---|---|---|
R2-2409527 | Reply LS on AIML data collection (S2-2411191; contact: InterDigital) | SA2 |
R2-2409531 | LS on AI/ML Model transfer/delivery to UE (S5-246292; contact: NEC) | SA5 |
R2-2409532 | Reply LS on AIML Data Collection (S5-246299; contact Nokia) | SA5 |
R2-2411077 | Reply LS on AIML data collection (S3-245138; contact: Samsung) | SA3 |
R2-2411177 | Reply LS on AIML data collection (R3-247801; contact: ZTE) | RAN3 |
TDoc | Title | Source |
---|---|---|
R2-2409546 | LCM for UE-sided model for Beam Management use case | OPPO |
R2-2409704 | Discussion on LCM for UE-sided model for Beam Management | vivo |
R2-2409716 | Discussion on LCM for UE-sided model for BM use case | CATT |
R2-2409727 | Discussion on LCM for UE sided model | NEC Corporation |
R2-2409736 | LCM for UE-sided model for BM | LG Electronics |
R2-2409831 | Discussion on LCM for UE-sided model for beam management | Samsung |
R2-2409834 | Discussion on LCM for UE-sided Model for Beam Management Use Case | Fujitsu |
R2-2409864 | Discussion on LCM for UE-sided model for BM | Xiaomi |
R2-2409870 | Further Discussion on LCM for UE-side Model | MediaTek Inc. |
R2-2409908 | On LCM for UE-sided Models for Beam Management | Qualcomm Incorporated |
R2-2409943 | Remaining issues on LCM procedure of UE-sided model for AI/ML based beam management | Apple |
R2-2410040 | Discussion on LCM for UE-sided model for BM | |
R2-2410101 | LCM for UE-sided model for BM | China Telecom |
R2-2410142 | Discussion on LCM for UE-sided model for Beam Management | Spreadtrum, UNISOC |
R2-2410276 | LCM for UE sided model in beam management | Lenovo |
R2-2410342 | Discussion on LCM for UE-sided model for BM | CMCC |
R2-2410450 | On LCM for UE-sided model for Beam Management Use Case | SHARP Corporation |
R2-2410492 | Discussion on LCM for UE-sided model for Beam Management use case | Huawei, HiSilicon |
R2-2410550 | LCM for UE-sided model for Beam Management use case | InterDigital |
R2-2410554 | Discussion on UE-sided model for Beam Management | Jio |
R2-2410578 | LCM for UE-side models for beam management | Ericsson |
R2-2410581 | LCM for UE-side model (beam management) | Futurewei Technologies |
R2-2410592 | LCM for UE-side Beam Management | Nokia Corporation |
R2-2410604 | Considerations on LCM for UE-sided model in Beam Management use case | Kyocera |
R2-2410626 | On LCM for UE-sided model for Beam Management | ZTE Corporation |
R2-2410751 | Discussion on LCM for UE-sided model for beam management use case | TCL |
TDoc | Title | Source |
---|---|---|
R2-2409570 | Discussion on LCM for positioning use case | ZTE Corporation |
R2-2409705 | Discussion on RAN2 issues of AI/ML enhanced positioning | vivo |
R2-2409717 | Consideration on LCM for Positioning use case | CATT |
R2-2409791 | LCM for Positioning use case | NEC |
R2-2409824 | Discussion on LCM for POS use case | Samsung |
R2-2409835 | Discussion on LCM for Positioning Use Case | Fujitsu |
R2-2409907 | Association of measurements and ground truth labels for positioning use-cases | Fraunhofer IIS, Fraunhofer HHI |
R2-2409944 | Further discussion on LCM procedure of AI/ML based positioning | Apple |
R2-2410277 | LCM for AIML based positioning with UE-sided model | Lenovo |
R2-2410475 | LCM for positioning use case | Qualcomm Incorporated |
R2-2410499 | LCM For Positioning | Ericsson |
R2-2410502 | LCM for Positioning use case | Interdigital Inc. |
R2-2410553 | LCM for positioning use case | Nokia |
R2-2410637 | Discussion on the LCM for AI positioning | Xiaomi |
R2-2410658 | Discussion on LCM for Positioning use case | Huawei, HiSilicon |
R2-2410673 | Discussion on LCM for positioning | CMCC |
R2-2410778 | Discussion on Functionality-based LCM for Positioning Use Case | CEWiT |
TDoc | Title | Source |
---|---|---|
R2-2409547 | Data Collection for Network Side BM Model Training | OPPO |
R2-2409548 | Data Collection for Positioning Model Training | OPPO |
R2-2409653 | Consideration on NW side data collection | CATT |
R2-2409706 | Discussion on NW side data collection | vivo |
R2-2409737 | NW side data collection | LG Electronics |
R2-2409830 | Disuccsion on NW side data collection | Samsung |
R2-2409836 | Discussion on NW side Data Collection | Fujitsu |
R2-2409865 | Discussion on NW side data collection | Xiaomi |
R2-2409881 | Further Discussion on Data collection for Network Side Model Training | MediaTek Inc. |
R2-2409905 | AIML PHY NW-side data collection | NEC |
R2-2409909 | On Network Side Data Collection | Qualcomm Incorporated |
R2-2409945 | Remaining issues on NW-sided data collection | Apple |
R2-2410069 | Discussion on NW-side Data Collection | SHARP Corporation |
R2-2410102 | Discussion on NW-side data collection for AI/ML based beam management | China Telecom |
R2-2410143 | Discussion on NW-side data collection | Spreadtrum, UNISOC |
R2-2410278 | Data Collection for NW-sided model training | Lenovo |
R2-2410343 | Discussion on NW side data collection | CMCC |
R2-2410425 | Data Collection for Training of NW-side ML Models | Nokia |
R2-2410489 | Some aspects for NW side data collection | Sony |
R2-2410503 | NW side data collection | Interdigital Inc. |
R2-2410538 | Discussion on NW-sided data collection for training | Huawei, HiSilicon |
R2-2410582 | NW-side data collection | Futurewei Technologies |
R2-2410627 | Further Considerations on NW side data collection | ZTE Corporation |
R2-2410846 | NW-side data collection for beam management and positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2410504 | Summary of [POST127bis][020][AI PHY] Reply LS to SA2_SA5 (InterDigital_Nokia) | Interdigital Inc., Nokia |
R2-2410505 | [Draft] Reply LS to SA2 on AIML data collection, | Interdigital |
R2-2410506 | [Draft] Reply LS to SA5 on AIML data collection | Nokia |
R2-2411114 | Reply LS to SA5 on AIML data collection | RAN2 |
R2-2411116 | [Draft] Reply LS to SA2 on AIML data collection | Interdigital |
R2-2411151 | [Draft] Reply LS to SA2 on AIML data collection | Interdigital |
R2-2411152 | Reply LS to SA2 on AIML data collection | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2410103 | Discussion on model transfer/delivery | China Telecom |
R2-2410344 | Discussion on AIML model transfer delivery | CMCC, NTT Docomo, China Unicom, CATT, Apple |
R2-2410529 | Operators views on the AI_ML model delivery options | BT plc, Turkcell |
R2-2410601 | Requirements for Model Transfer/Delivery | T-Mobile USA Inc., Nokia |
R2-2410853 | Operators views on the AI_ML model delivery options | BT plc, Turkcell, Deutsche Telekom |
TDoc | Title | Source |
---|---|---|
R2-2409511 | Reply LS to RAN2 on data block sizes for Ambient IoT (R1-2409250; contact: MediaTek) | RAN1 |
R2-2409526 | LS on security aspects of Ambient IoT (S2-2411049; contact: OPPO) | SA2 |
R2-2409812 | TP for TR 38.769 update | Huawei, CMCC, T-Mobile USA |
R2-2411078 | Reply LS on security aspects of Ambient IoT (S3-245139; contact: OPPO) | SA3 |
R2-2411213 | TP for the A-IoT conclusion | Huawei, HiSilicon |
R2-2411221 | TP for TR 38.769 update | Huawei, CMCC, T-Mobile USA |
R2-2411222 | LS on RAN2 outcome of Ambient IoT study | RAN2 |
R2-2411263 | LS on RAN2 outcome of Ambient IoT study | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409621 | Discussion on the Functionality Aspects for Ambient IoT | CATT |
R2-2409702 | Ambient IoT coverage, energy, TB size, and all sorts of other things | MediaTek Inc. |
R2-2409703 | Ambient IoT ID management and implications for energy status indication | MediaTek Inc. |
R2-2409707 | Discussion on functionality aspects for Ambient IoT | vivo |
R2-2409783 | A-IoT functionality | ZTE Corporation, Sanechips |
R2-2409837 | Discussions on Functionality Aspect of Ambient IoT | Fujitsu |
R2-2409897 | A-IoT functionalities | Huawei, HiSilicon |
R2-2409963 | Functional Aspects of Ambient IoT | Apple |
R2-2410002 | Functionality for Ambient IOT | InterDigital |
R2-2410016 | Discussion on A-IOT functionality aspects | Xiaomi |
R2-2410096 | Discussion on functionality for Ambient IoT | China Telecom |
R2-2410124 | Discussion on AIoT functionalities | OPPO |
R2-2410134 | Considerations on functionality aspects for Ambient IoT | Lenovo |
R2-2410137 | Discussion on the functionalities required for Ambient IoT | Spreadtrum, UNISOC |
R2-2410193 | Functionality aspects for A-IoT | Ericsson |
R2-2410300 | Discussion on Ambient IoT segmentation functionality | Panasonic |
R2-2410311 | Remaining issues on study of AIoT functionalities | NTT DOCOMO, INC. |
R2-2410353 | Ambient-IoT Functionality Aspects | NEC |
R2-2410370 | A-IoT functionalities | ETRI |
R2-2410374 | Considerations on functionality aspects for Ambient IoT | Sony |
R2-2410416 | Lean Inventory procedure/counting of devices | VODAFONE |
R2-2410423 | Functionality aspects of AIoT | Nokia France |
R2-2410477 | Views on Functionality Aspects of Ambient IoT | Qualcomm Incorporated |
R2-2410493 | Discussion on remaining aspects of AS ID | Continental Automotive |
R2-2410572 | Discussions on Energy Status Indication for Ambient IoT | Futurewei |
R2-2410573 | Further discussions on AS ID for Ambient IoT devices | Futurewei |
R2-2410594 | Discussion on functionality aspects of ambient IoT | LG Electronics Inc. |
R2-2410603 | Use cases for one-bit energy status report in AIoT | SHARP Corporation |
R2-2410620 | Discussion on functionality for ambient IoT | Google Ireland Limited |
R2-2410646 | Remaining issues of functionalities for Ambient IoT | Kyocera |
R2-2410672 | Discussion on functionality for A-IoT | CMCC |
R2-2410679 | Discussion on functionality aspects for A-IoT | HONOR |
R2-2410753 | Discussions on functionalities required for AIoT | Samsung |
R2-2411232 | Assistance information from CN to the reader | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409578 | Discussion on A-IOT paging procedure | Xiaomi |
R2-2409583 | Discussion on A-IOT paging procedure | Xiaomi |
R2-2409622 | Discussion on Paging for Ambient IoT | CATT |
R2-2409687 | Remaining issues of AIoT Paging | ZTE Corporation, Sanechips |
R2-2409708 | Discussion on AIoT Paging | vivo |
R2-2409739 | Discussion on ambient IoT paging | LG Electronics Inc. |
R2-2409838 | Discussions on AIoT paging | Fujitsu |
R2-2409884 | Discussion on Paging for A-IoT | Transsion Holdings |
R2-2409892 | Discussion on paging procedure for Ambient IoT | OPPO |
R2-2409898 | A-IoT paging | Huawei, HiSilicon |
R2-2409964 | Discussion on Ambient IoT Paging | Apple |
R2-2410003 | Paging Related Aspects for Ambient IOT | InterDigital |
R2-2410068 | New and retransmitted A-IoT paging indication and device behaviors | Sharp |
R2-2410125 | Ambient-IoT Paging | NEC |
R2-2410140 | Discussion on paging procedure of AIoT | Spreadtrum, UNISOC |
R2-2410178 | Discussion on Ambient IoT paging message with multiple IDs | ASUSTeK |
R2-2410264 | Discussion on paging procedure for Ambient IoT | Lenovo |
R2-2410295 | Discussion on A-IoT paging | Panasonic |
R2-2410312 | Discussion on RA type indication in AIoT paging | NTT DOCOMO, INC. |
R2-2410334 | Discussion on A-IoT paging | CMCC |
R2-2410375 | Considerations on paging for Ambient IoT | Sony |
R2-2410404 | Paging procedures for Ambient IoT | Nokia |
R2-2410551 | Ambient IoT Paging | Qualcomm Incorporated |
R2-2410575 | Further discussions on Ambient IoT paging | Futurewei |
R2-2410605 | Discussion on DL messages for Ambient IoT UEs | Ericsson |
R2-2410616 | Ambient IoT device paging | TCL |
R2-2410645 | Remaining issues of A-IoT paging for Ambient IoT | Kyocera |
R2-2410680 | Discussion on A-IoT Paging | HONOR |
R2-2410693 | Further discussions on Ambient IoT Paging | China Telecom |
R2-2410754 | Discussion on A-IoT paging | Samsung |
R2-2410766 | Discussion on paging procedure for ambient IoT | Google Ireland Limited |
R2-2410779 | Discussion on A-IOT paging procedure | CEWiT |
TDoc | Title | Source |
---|---|---|
R2-2409577 | Discussion on access procedure for ambient IOT | Xiaomi |
R2-2409582 | Discussion on access procedure for ambient IOT | Xiaomi |
R2-2409623 | Discussion on the Random Access for Ambient IoT | CATT |
R2-2409700 | Device support of ambient IoT random access procedures | MediaTek Inc. |
R2-2409709 | Random Access Procedure for AIoT Device | vivo |
R2-2409738 | Discussion on random access aspects for Ambient IoT | LG Electronics Inc. |
R2-2409784 | Unified random-access procedure for A-IoT | ZTE Corporation, Sanechips |
R2-2409792 | Random Access for Ambient IoT device | NEC |
R2-2409839 | Discussions on AIoT Random Access | Fujitsu |
R2-2409885 | Discussion on Random Access for A-IoT | Transsion Holdings |
R2-2409890 | Discussion on D2R failure/success indication in A-IoT | SHARP Corporation |
R2-2409895 | random access for AIoT | OPPO |
R2-2409965 | Discussion on Random Access for Ambient IoT | Apple |
R2-2410004 | Random Access Procedure for Ambient IOT | InterDigital |
R2-2410097 | Random access procedure for A-IoT | China Telecom |
R2-2410138 | Discussion on random access of Ambient IoT | Spreadtrum, UNISOC |
R2-2410152 | Discussion on UL multiple access | Ericsson |
R2-2410261 | Study the A-IoT Random Access Procedure | Tejas Network Limited |
R2-2410265 | Discussion on random access for Ambient IoT | Lenovo |
R2-2410313 | Remaining issues on study of AIoT random access | NTT DOCOMO, INC. |
R2-2410315 | Further discussion on ambient IoT random access | CMCC |
R2-2410351 | A-IoT random access procedure | Huawei, HiSilicon |
R2-2410376 | Considerations on random access aspects for Ambient IoT | Sony |
R2-2410403 | CBRA type down-selection | Vodafone, Huawei, CMCC, Telit Communications S.p.A., CATT, Nokia |
R2-2410414 | Open issues on random access for AIoT | Nokia |
R2-2410476 | Views on Random Access Aspects of Ambient IoT | Qualcomm Incorporated |
R2-2410576 | Issues with previous agreement on Msg2 in 2-step CBRA | Futurewei |
R2-2410593 | Discussion on Ambient IoT random access | KT Corp. |
R2-2410629 | Discussion on random access for ambient IoT | Google Ireland Limited |
R2-2410681 | Discussion on A-IoT random access | HONOR |
R2-2410719 | Further discussion on Ambient IoT random access | Samsung |
R2-2410780 | Discussion on random access for Ambient IoT | CEWiT |
R2-2410868 | Handling of Msg2 for 2step CBRA | Philips International B.V. |
R2-2410890 | A-IoT Random Access - failure/success feedback indication for following D2R data | Wiliot Ltd. |
TDoc | Title | Source |
---|---|---|
R2-2409624 | Discussion on Topology 2 for Ambient IoT | CATT |
R2-2409688 | Remaining issues of AIoT TP2 | ZTE Corporation, Sanechips |
R2-2409701 | Ambient IoT resource allocation for topology 2 | MediaTek Inc. |
R2-2409710 | Discussion on Topology 2 related aspects | vivo |
R2-2409742 | Considerations on TP2 related aspects between BS and UE reader | Xiaomi |
R2-2409840 | Discussions on topology 2 related aspects | Fujitsu |
R2-2409894 | Discussion on topology 2 for Ambient IOT | OPPO |
R2-2409899 | A-IoT Topology 2 aspects | Huawei, HiSilicon |
R2-2409966 | Remaining open issues in Topology 2 | Apple |
R2-2410005 | Topology 2 for Ambient IOT | InterDigital |
R2-2410083 | Validity of resources and reader behavior in Topology 2 | NEC |
R2-2410098 | Discussion on Topology 2 related aspects for Ambient IoT | China Telecom |
R2-2410141 | Discussion on Topology 2 issues | Spreadtrum, UNISOC |
R2-2410151 | On Topology 2 | Ericsson |
R2-2410179 | Consideration on information and scenario in Topology 2 | ASUSTeK |
R2-2410251 | Discussion on topology 2 for A-IoT | KT Corp. |
R2-2410266 | Considerations on Topology 2 for Ambient IoT | Lenovo |
R2-2410335 | Discussions on topology 2 for A-IoT | CMCC |
R2-2410371 | Discussion on ‘temporary out of connection’ in Topology 2 | ETRI |
R2-2410467 | RAN2 Aspects for AIoT Operation in Topology 2 | Nokia |
R2-2410552 | Further aspects of Topology 2 | Qualcomm Incorporated |
R2-2410595 | Discussion on topology 2 considerations of ambient IoT | LG Electronics Inc. |
R2-2410647 | Remaining issues on Topology 2 aspects of Ambient IoT | Kyocera |
R2-2410682 | Consideration on resource configuration for Topology 2 | HONOR |
R2-2410755 | Discussion on A-IoT Topology 2 | Samsung |
R2-2410760 | Considerations on Topology 2 for Ambient IoT | TCL |
R2-2410805 | Discussion on Topology 2 related aspects | Fraunhofer HHI, Fraunhofer IIS |
R2-2411179 | Conclusion of [AT128][016][AIoT] Resource validity (Interdigital) | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2410186 | Text proposal of 38.744 | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2410037 | Discussion on cluster based RRM measurement prediction | BJTU |
R2-2410744 | AI-ML based Inter-frequency measurement prediction | Rakuten Mobile, Inc |
R2-2410774 | Simulation results for RRM measurement prediction | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2409651 | Simulation results of RRM Measurement Prediction | CATT, Turkcell |
R2-2409667 | Updated simulation results for RRM measurement prediction | vivo |
R2-2409823 | Discussion on the simulation results for RRM measurement prediction | Samsung |
R2-2409866 | Discussion on RRM prediction simulation result | Xiaomi |
R2-2409868 | Simulation Results for AIML RRM Prediction and Remaining Issues | MediaTek Inc. |
R2-2409971 | Cluster-based approach, UE-sided vs. network-sided models, etc. | Apple |
R2-2410020 | Simulation results on the RRM measurement prediction and discussions | NTT DOCOMO, INC. |
R2-2410144 | Simulation results on RRM measurement prediction | Spreadtrum, UNISOC, BUPT |
R2-2410187 | Discussion on simulation result of RRM measurement prediction | OPPO |
R2-2410339 | Simulation results for RRM measurement prediction | CMCC |
R2-2410474 | Simulation results for temporal, inter-frequency and spatial domain RRM measurement predictions | Ericsson |
R2-2410507 | Simulation results for RRM measurement predictions | Interdigital Inc. |
R2-2410539 | Simulation results for RRM measurement prediction | Huawei, HiSilicon |
R2-2410678 | Simulation and evaluation of RRM measurement prediction | Indian Institute of Tech (M), IIT Kanpur |
R2-2410781 | Simulation results for RRM Measurement Prediction | CEWiT |
R2-2410796 | On the RRM measurement prediction aspects | Nokia |
R2-2410799 | Evaluation on RRM measurement prediction | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2410568 | Discussion on measurement event prediction | Jio |
TDoc | Title | Source |
---|---|---|
R2-2410759 | AI-ML based RLF/HO failure prediction | Rakuten Mobile, Inc |
TDoc | Title | Source |
---|---|---|
R2-2409652 | Discussion on generalization for RRM prediction | CATT, Turkcell |
R2-2409668 | Discussion on generalization study for RRM prediction | vivo |
R2-2409795 | Simulation assumption for Measurement event prediction | NEC |
R2-2409829 | Discussion on Generalization Issues for AI/ML Mobility | Samsung |
R2-2409867 | Simulation assumptions on event/RLF/SLS and model generalization | Xiaomi |
R2-2409869 | Simulation Assumptions of SLS, measurement event prediction, RLF prediction and generalzatiion study | MediaTek Inc. |
R2-2409972 | Model generalization, RLF evaluation assumptions, etc. | Apple |
R2-2409991 | Simulation assumptions and methodology for Measurement Event prediction, RLF prediction, and SLS | Qualcomm Incorporated |
R2-2410023 | Discussions on evaluation methodology of AI/ML for mobility | NTT DOCOMO, INC. |
R2-2410084 | Other aspects for RRM measurement prediction | Lenovo |
R2-2410188 | Discussion on generalization study of AI mobility | OPPO |
R2-2410190 | Summary of [POST127bis][022][AI mobility] Simulation Assumptions (OPPO) | Hangzhou Mengyuxiang |
R2-2410263 | Discussion on generalization aspects | Ericsson |
R2-2410345 | Discussion on other aspects of simulation assumption | CMCC |
R2-2410508 | Generalization of AIML models for RRM measurement prediction | Interdigital Inc. |
R2-2410522 | Discussion on RRM measurement predictions and prediction-based mobility events | Sharp |
R2-2410540 | Discussion on simulation assumptions and generalization | Huawei, HiSilicon |
R2-2410697 | Discussion on simulation assumptions for RLF prediction | KDDI Corporation |
R2-2410797 | On the remaining simulation assumptions and model generalization aspects | Nokia, Nokia Shanghai Bell |
R2-2410800 | Discussion on generalization aspects and simulation assumption | ZTE Corporation |
R2-2411175 | Summary of [AT128][017][AI mob]Simulation assumptions (OPPO) | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2409718 | LP-WUS in RRC_IDLE/INACTIVE | CATT |
R2-2409761 | Discussion on LP-WUS WUR in RRC_IDLE INACTIVE | vivo |
R2-2409871 | General considerations on the procedure for RRC_IDLE_INACTIVE | Xiaomi Communications |
R2-2409902 | LP-WUS in RRC_IDLE INACTIVE | NEC |
R2-2409921 | Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE | Huawei, HiSilicon |
R2-2409924 | LP-WUS operation in RRC_IDLE and RRC_INACTIVE | LG Electronics Inc. |
R2-2409949 | Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE | Apple |
R2-2409989 | On LR and MR operating frequencies and the answer to RAN1 LS | VODAFONE,VIVO, Deutsche Telekom |
R2-2409990 | DRAFT Reply LS to R2-2409157/R1-2407559 | VODAFONE Group Plc |
R2-2410085 | LP-WUS in Idle and Inactive | Ericsson |
R2-2410119 | Discussion on LP-WUS procedure and configuration | OPPO |
R2-2410166 | Procedure and configuration of LP-WUS for IDLE and INACTIVE mode | ZTE Corporation, Sanechips |
R2-2410377 | RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode | Sony |
R2-2410412 | Discussion on IDLE/INACTIVE procedures for LP-WUS | Tejas Network Limited |
R2-2410509 | Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes | InterDigital, Inc. |
R2-2410555 | LP-WUS in IDLE and INACTIVE | Nokia |
R2-2410606 | Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode | Samsung |
R2-2410632 | Discussion on LP-WUS in RRC_IDLE and RRC_INACTIVE | Sharp |
R2-2410670 | Further considerations on LP-WUS operation in IDLE INACTIVE mode | CMCC |
R2-2410683 | Discussion on LP-WUS in RRC_IDLE/INACTIVE | HONOR |
R2-2410730 | LP-WUS operation in IDLE/Inactive state | Qualcomm Incorporated |
R2-2410798 | Procedure and Configuration of LP-WUS in RRC Idle/ Inactive | Lenovo |
R2-2410841 | Discussion on LP-WUS for IDLE/INACTIVE state | NTT DOCOMO, INC. |
R2-2410858 | On LP-WUS paging monitoring considerations | Nordic Semiconductor |
R2-2410955 | Summary of email discussion [AT128][205] on not support LP-WUS reception on all the bands supported by the UE | Vodafone |
R2-2410956 | DRAFT Reply LS to R2-2409157/R1-2407559 | Vodafone |
R2-2410957 | Reply LS to R2-2407921/ R1-2407559 | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409592 | Further discussion on the criteria for RRM measurement relaxation and offloading | Huawei, HiSilicon |
R2-2409719 | RRM Relaxation and Offloading in RRC_IDLE/INACTIVE | CATT |
R2-2409762 | Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | vivo |
R2-2409872 | Discussion on RRM measurement relaxation for RRC_IDLE_INACTIVE | Xiaomi Communications |
R2-2409903 | LP-WUS measurement relaxation and offloading | NEC |
R2-2409925 | RRM relaxation and RRM offloading | LG Electronics Inc. |
R2-2409950 | RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | Apple |
R2-2410086 | LP-WUS and RRM measurements | Ericsson |
R2-2410120 | Discussion on RRM measurement in RRC IDLE and INACTIVE | OPPO |
R2-2410167 | RRM measurement relaxation and offloading in RRC_IDLE and RRC_INACTIVE mode | ZTE Corporation, Sanechips |
R2-2410273 | RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | Lenovo |
R2-2410341 | Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE | CMCC |
R2-2410378 | Discussion on RRM aspects for LP-WUS/WUR | Sony |
R2-2410510 | Discussion on RRM measurement relaxation and offloading | InterDigital, Inc. |
R2-2410556 | RRM measurement relaxation in RRC_IDLE/INACTIVE | Nokia |
R2-2410607 | RRM measurement relaxation and offloading in RRC Idle Inactive Mode | Samsung |
R2-2410633 | Discussion on RRM measurement relaxation and offloading | Sharp |
R2-2410694 | RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE | China Telecom |
R2-2410732 | LP-WUS RRM measurement relaxation and offloading | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2409588 | Discussing on LP-WUS monitoring in Connected mode | Xiaomi |
R2-2409713 | LP-WUS operation for RRC_CONNECTED Mode | LG Electronics Inc. |
R2-2409720 | Analysis on LP-WUS for RRC_CONNECTED Mode | CATT |
R2-2409763 | Discussion on LP-WUS WUR in RRC_Connected | vivo |
R2-2409883 | LP-WUS in RRC_CONNECTED | Nokia, Nokia Shanghai Bell |
R2-2409904 | LP-WUS in RRC_CONNECTED | NEC |
R2-2409951 | Procedures for LP-WUS in RRC_CONNECTED | Apple |
R2-2410087 | LP-WUS in Connected | Ericsson |
R2-2410099 | LP-WUS in CONNECTED mode | China Telecom |
R2-2410121 | Discussion on LP-WUS in RRC_CONNECTED | OPPO |
R2-2410168 | Procedures for LP-WUS in RRC_CONNECTED | ZTE Corporation, Sanechips |
R2-2410319 | Discussion on LP-WUS operation in CONNECTED mode | CMCC |
R2-2410352 | Discussion on LP-WUS for RRC_CONNECTED mode | Huawei, HiSilicon |
R2-2410379 | Considerations on LP-WUS/WUR in RRC Connected mode | Sony |
R2-2410405 | LP-WUS in CONNECTED mode | InterDigital |
R2-2410413 | Discussion on CONNECTED mode procedures for LP-WUS | Tejas Network Limited |
R2-2410608 | Procedures for LP-WUS in RRC Connected Mode | Samsung |
R2-2410634 | Discussion on LP-WUS in RRC_CONNECTED | Sharp |
R2-2410731 | LP-WUS operation in CONNECTED state | Qualcomm Incorporated |
R2-2410814 | LP-WUS in RRC Connected Mode | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2409520 | LS on SSB adaptation (R4-2416911; contact: Apple) | RAN4 |
R2-2409521 | LS on SSB relation in On-demand SSB and SSB adaptation on Scell (R4-2416913; contact: Ericsson) | RAN4 |
TDoc | Title | Source |
---|---|---|
R2-2409550 | Discussion on On-Demand SSB | OPPO |
R2-2409596 | Consideration on on-demand SSB SCell operation | CATT |
R2-2409696 | On-demand SSB SCell Operation | Samsung |
R2-2409926 | On-demand SSB SCell operation | LG Electronics Inc. |
R2-2409940 | Discussion on on-demand SSB for SCell | Apple |
R2-2410014 | Discussion on on-demand SSB SCell operation | Sharp |
R2-2410015 | Discussion on on-demand SSB | Xiaomi |
R2-2410061 | Further discussion on On-demand SSB for SCell | NEC |
R2-2410145 | Discussion on on-demand SSB SCell operation | Fujitsu |
R2-2410163 | On-demand SSB SCell operation in connected mode | ZTE Corporation, Sanechips |
R2-2410255 | On demand SSB handling | Nokia, Nokia Shanghai Bell |
R2-2410284 | Issues on the procedure of on-demand SSB SCell operation | Lenovo |
R2-2410320 | Discussion on On demand SSB for Scell | CMCC |
R2-2410380 | On-demand SSB Scell operation discussion | Sony |
R2-2410398 | Discussion on on-demand SSB for NES | Ericsson |
R2-2410426 | Discussion on On-demand SSB SCell Operation | Qualcomm Incorporated |
R2-2410432 | Discussion on on-demand SSB SCell operation for NES | Huawei, HiSilicon |
R2-2410472 | On demand SSB transmission for SCell | InterDigital |
R2-2410600 | Discussion on on-demand SSB SCell operation | NTT DOCOMO INC. |
R2-2410788 | Remaining issues of on-demand SSB SCell operation | vivo |
R2-2410849 | Discussion on OD-SSB | Rakuten Mobile, Inc |
TDoc | Title | Source |
---|---|---|
R2-2409575 | Discussion on on-demand SIB1 | Xiaomi |
R2-2409580 | Discussion on on-demand SIB1 | Xiaomi |
R2-2409597 | Consideration on on-demand SIB1 | CATT |
R2-2409695 | On-demand SIB1 | Samsung |
R2-2409820 | Discussion on the issues for OD-SIB1 | Google Ireland Limited |
R2-2409927 | On-demand transmission of SIB1 | LG Electronics Inc. |
R2-2409941 | Discussion on on-demand SIB1 | Apple |
R2-2410009 | Discussion on On-demand SIB1 WUS provisioning, UE behaviour, and barring | NEC Telecom MODUS Ltd. |
R2-2410042 | Discussion on Ondemand-SIB1 | KDDI Corporation |
R2-2410100 | Discussion on OD-SIB1 | China Telecom |
R2-2410146 | Discussion on on-demand SIB1 procedure for NES | Fujitsu |
R2-2410164 | Remaining issues of on-demand SIB1 in idle and inactive mode | ZTE Corporation, Sanechips |
R2-2410170 | On-demand SIB1 for Idle/Inactive mode UEs | III |
R2-2410239 | Consideration on on-demand SIB1 | OPPO |
R2-2410256 | On demand SIB1 handling | Nokia, Nokia Shanghai Bell |
R2-2410303 | Discussion on on-demand SIB1 operation for NES | Huawei, HiSilicon |
R2-2410321 | Discussion on on-demand SIB1 | CMCC |
R2-2410381 | WUS configuration details for on-demand SIB1 | Sony |
R2-2410391 | Cell barring in on-demand SIB1 cells | Sony |
R2-2410400 | Discussion on on-demand SIB1 for NES | Ericsson |
R2-2410411 | Barring and SIB1-less case 2 | Vodafone, Deutsche Telekom, Xiaomi |
R2-2410427 | Discussion on On-demand SIB1 | Qualcomm Incorporated |
R2-2410469 | Case 2 and remaining essential issues | Lenovo |
R2-2410470 | On-demand SIB1 request and reception | InterDigital |
R2-2410602 | Discussion on on-demand SIB1 | NTT DOCOMO INC. |
R2-2410738 | Discussion on on-demand SIB1 for NES | Rakuten Mobile, Inc |
R2-2410776 | Discussion on On-demand SIB1 for NES | Fraunhofer IIS, Fraunhofer HHI |
R2-2410789 | Discussion on on-demand SIB1 for RRC IDLE and INACTIVE UE | vivo |
R2-2410842 | Considerations on OD-SIB1 feature | Deutsche Telekom, Vodafone, Lenovo, Fraunhofer IIS |
TDoc | Title | Source |
---|---|---|
R2-2409576 | Discussion on common signal adaptation | Xiaomi |
R2-2409581 | Discussion on common signal adaptation | Xiaomi |
R2-2409598 | Adaptation of Common signal channel transmissions | CATT |
R2-2409679 | Discussion on adaptation of common signal/channel transmissions | OPPO |
R2-2409692 | Discussion on common signal and channel adaptation | LG Electronics Inc. |
R2-2409697 | Adaptation of common signal channel transmissions | Samsung |
R2-2409841 | Adaptation of common signal or channel | Fujitsu |
R2-2409942 | Discussion on common signal transmission adaptation | Apple |
R2-2410010 | PRACH and paging adaptation for NES | NEC Telecom MODUS Ltd. |
R2-2410165 | Consideration on common signal/channel transmissions | ZTE Corporation, Sanechips |
R2-2410257 | Common signal aspects of NES WI | Nokia, Nokia Shanghai Bell |
R2-2410285 | Discussion on the adaptation transmissions for NES operation | Lenovo |
R2-2410322 | Discussion on SSB adaptation | CMCC |
R2-2410428 | Discussion on Adaptation of Common Signal/Channel Transmissions | Qualcomm Incorporated |
R2-2410433 | Discussion on adaptation of common signals/channels transmissions | Huawei, HiSilicon |
R2-2410471 | Time domain adaptation of common signalling and channels | InterDigital |
R2-2410610 | Adaptation of common signal/channel transmissions for NES | Ericsson |
R2-2410741 | Adaptation of paging signal/channel transmissions | III |
R2-2410743 | Discussion on RACH adaptation | SHARP Corporation |
R2-2410790 | Discussion on adaptation of common signal transmissions | vivo |
R2-2410930 | Summary of [111] | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2409514 | LS on the support of semi-persistent CSI-RS resource for LTM candidate cells (R1-2409283; contact: Fujitsu) | RAN1 |
R2-2409534 | Reply LS on security handling for inter-CU LTM in non-DC cases (S3-244316; contact: Samsung) | SA3 |
R2-2409535 | Reply LS on security key update of inter-CU SCG LTM (S3-244317; contact: Xiaomi) | SA3 |
R2-2409979 | Introduction of NR mobility enhancements Phase 4 in TS 38.300 | Apple |
R2-2410112 | Introduction of NR mobility enhancements Phase 4 in TS 37.340 | China Telecom |
R2-2410927 | Introduction of NR mobility enhancements Phase 4 in TS 38.300 | Apple |
R2-2410928 | Introduction of NR mobility enhancements Phase 4 in TS 37.340 | China Telecom |
TDoc | Title | Source |
---|---|---|
R2-2409593 | Discussion on Inter-CU LTM | CATT |
R2-2409616 | Discussion on remaining issues of inter-CU LTM | LG Electronics Inc. |
R2-2409764 | Discussion on inter-CU LTM | vivo |
R2-2409863 | Discussion on Inter CU LTM | Lekha Wireless Solutions |
R2-2409873 | Discussion on open issues for inter-CU LTM | OPPO |
R2-2409886 | Further discussion on remaining issues of inter-CU LTM cell switch | Transsion Holdings |
R2-2409973 | Important issues in Inter-CU LTM | Apple |
R2-2409980 | Important issues in Inter-CU LTM | Apple |
R2-2410012 | Further Discussion on inter -CU LTM | ETRI |
R2-2410021 | Discussion on inter-CU LTM | Xiaomi |
R2-2410035 | Discussion on inter-CU LTM in non-DC and DC cases | Fujitsu |
R2-2410113 | Discussion on inter-CU LTM | China Telecom |
R2-2410118 | Leftover issues on Inter-CU LTM | MediaTek Inc. |
R2-2410228 | Discussion on reference configuration for inter-CU LTM | ITRI |
R2-2410242 | Discussion on inter-CU LTM | NEC |
R2-2410279 | Remaining issues for Inter-CU LTM | Lenovo |
R2-2410323 | Discussion on Inter-CU LTM | CMCC |
R2-2410382 | LTM for Inter-CU | Sony |
R2-2410443 | Dsicussion on Inter-CU LTM | ZTE Corporation |
R2-2410466 | On remaining issues for Inter-CU LTM | Nokia |
R2-2410518 | Inter-CU LTM | Huawei, HiSilicon |
R2-2410530 | Security handling for Inter-CU LTM | Qualcomm Incorporated |
R2-2410544 | Security handling and DC aspects for inter-CU LTM | Ericsson |
R2-2410598 | Discussion on Inter-CU LTM | InterDigital, Inc. |
R2-2410660 | Potential issue on coexistence of inter-MN LTM and intra-SN LTM | Kyocera |
R2-2410690 | Further discussion on inter-CU LTM | HONOR |
R2-2410703 | Discussion on issues for supporting inter-CU LTM | Sharp |
R2-2410742 | Discussion on Inter-CU LTM | Rakuten Mobile, Inc |
R2-2410752 | Further Considerations to Support Inter-CU LTM | Samsung |
R2-2410763 | LTM in DC scenarios | Rakuten Mobile, Inc |
R2-2410856 | Discussion on inter-CU LTM | DENSO CORPORATION |
R2-2411132 | [Draft] Reply LS on security handling for inter-CU LTM in non-DC cases | CATT |
R2-2411133 | [AT128][116][MOB] Inter-CU LTM (ZTE) | ZTE Corporation |
R2-2411136 | Reply LS on security handling for inter-CU LTM in non-DC cases | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409594 | L1 event triggered measurement reporting | CATT |
R2-2409630 | Event LTM triggered measurement report | LG Electronics Inc. |
R2-2409657 | Discussion on event triggered L1 MR | MediaTek Inc. |
R2-2409659 | Remaining issues of L1 event triggered measurement reporting | Xiaomi |
R2-2409765 | Discussion on LTM measurement event evaluation and reporting | vivo |
R2-2409802 | Event triggered L1 measurement reporting for LTM. | Interdigital, Inc. |
R2-2409842 | Discussions on event triggered L1 measurement reporting | Fujitsu |
R2-2409874 | Open issues for event triggered L1 measurement reporting | OPPO |
R2-2409887 | Discussion on L1 event triggered measurement reporting | Transsion Holdings |
R2-2409952 | LTM event triggered measurement reporting | Apple |
R2-2409987 | L1 event-triggered measurement reporting for LTM | Qualcomm Incorporated |
R2-2410062 | Further details of L1 event triggered measurement reporting | NEC |
R2-2410114 | Discussion on L1 event triggered measurement reporting | China Telecom |
R2-2410153 | Discussion on L1 event-triggered measurement reporting | Huawei, HiSilicon |
R2-2410180 | Discussion on L1 measurement reporting for LTM | ASUSTeK |
R2-2410244 | Discussion on event triggered L1 report | Huawei, HiSilicon |
R2-2410280 | Event based L1 measurement report | Lenovo |
R2-2410306 | L1 measurement event configuration and reporting | Panasonic |
R2-2410340 | Discussion on L1 event triggered measurement reporting | CMCC |
R2-2410399 | Discussion on L1 event triggered measurement reporting | Rakuten Mobile, Inc |
R2-2410441 | On L1 Measurement Reporting Enhancements for Rel-19 LTM | Nokia |
R2-2410444 | Discussion on L1 event triggered measurement reporting | ZTE Corporation |
R2-2410545 | Event definition and MAC CE content for L1 event-triggered measurements | Ericsson |
R2-2410567 | Discussion on L1 event triggered measurement | Jio |
R2-2410571 | Open issues for L1 event triggered measurement reporting | Fraunhofer HHI, Fraunhofer IIS |
R2-2410621 | Support of Event Triggered L1 Measurement Report | Samsung |
R2-2410648 | Details of event-triggered L1 measurement reporting for LTM | Kyocera |
R2-2410663 | Discussion on LTM measurement reporting configuration | Baicells |
R2-2410688 | Discussion on measurement event evaluation and report | HONOR |
R2-2410702 | L1 event triggered measurement reporting | Sharp |
R2-2410708 | Discussion on L1 event triggered measurement reporting | KDDI Corporation |
R2-2410710 | Discussion on event triggered L1 measurement reporting | ITL |
R2-2410888 | Support of Event Triggered L1 Measurement Report | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2409595 | Discussion on Conditional Intra-CU LTM | CATT |
R2-2409617 | Discussion on conditional LTM | LG Electronics Inc. |
R2-2409658 | Further discussion on Conditional LTM | MediaTek Inc. |
R2-2409766 | Discussion on conditional LTM | vivo |
R2-2409803 | Conditional LTM. | Interdigital, Inc. |
R2-2409843 | Discussion on conditional Intra-CU LTM | Fujitsu |
R2-2409875 | Discussion on conditional LTM | OPPO |
R2-2409888 | Further discussion on supporting intra-CU conditional LTM | Transsion Holdings |
R2-2409953 | Conditional Intra-CU LTM Topics | Apple |
R2-2409988 | Conditional intra-CU LTM | Qualcomm Incorporated |
R2-2410013 | Discussion on conditional intra-CU LTM | ETRI |
R2-2410022 | Discussion on conditional LTM | Xiaomi |
R2-2410044 | Discussion on Conditional Intra CU LTM | Lekha Wireless Solutions |
R2-2410064 | Discussion on conditional intra-CU LTM | NEC |
R2-2410115 | Discussion on conditional intra-CU LTM | China Telecom |
R2-2410136 | Discussion on conditional intra-CU LTM | Spreadtrum, UNISOC |
R2-2410230 | Discussion on early TA acquisition for conditional intra-CU LTM | ITRI |
R2-2410252 | Discussion on Conditional LTM | KT Corp. |
R2-2410324 | Discussion on Conditional LTM | CMCC |
R2-2410389 | Conditional Intra-CU LTM | Sony |
R2-2410445 | Discussion on conditional intra-CU LTM | ZTE Corporation |
R2-2410448 | Conditional LTM Scenarios and remaining points | Lenovo |
R2-2410465 | Discussion on conditional intra-CU LTM | Panasonic |
R2-2410519 | Intra-CU conditional LTM | Huawei, HiSilicon |
R2-2410546 | Further considerations for conditional LTM | Ericsson |
R2-2410622 | Support of Conditional Intra-CU LTM | Samsung |
R2-2410661 | Discussion on Conditional Intra-CU LTM | Kyocera |
R2-2410689 | Discussion on conditional LTM | HONOR |
R2-2410695 | Discussion on Conditional intra-CU LTM | NTT DOCOMO, INC. |
R2-2410701 | Discussion on conditional LTM | Sharp |
R2-2410709 | Discussion on Conditional LTM | ITL |
R2-2410782 | Discussion on Conditional LTM | CEWiT |
R2-2410795 | On conditional LTM | Nokia |
R2-2410889 | Support of Conditional Intra-CU LTM | Samsung |
R2-2411134 | RAN2 agreements on Inter-CU LTM and Conditional LTM | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409517 | Reply LS on multi-modality awareness at RAN (R3-245682; contact: Nokia) | RAN3 |
R2-2409525 | Reply LS on Application-Layer FEC Awareness at RAN (S2-2410999; contact: Qualcomm) | SA2 |
R2-2409533 | LS for PDU Set Information Marking Support without QoS parameters (S2-2411253; contact: vivo) | SA2 |
R2-2409560 | Reply LS on Application-Layer FEC Awareness at RAN | Qualcomm Incorporated |
R2-2409767 | Discussion on SA2 LSs on XRM and FEC | vivo |
R2-2409818 | Rapporteur Inputs | Nokia, Qualcomm (Rapporteurs) |
R2-2410491 | Discussion on LS from SA2 on PDU Set information | Sony |
R2-2411001 | Reply LS to SA2 on PDU set | RAN2 |
R2-2411201 | LS Reply on multi-modality awareness (S4-242223; contact: Huawei) | SA4 |
TDoc | Title | Source |
---|---|---|
R2-2409555 | Discussion on measurement gap cancelation | Qualcomm Incorporated |
R2-2409722 | Discussion on RRM measurement gaps/restrictions related enhancements | Hanbat National University |
R2-2409734 | Discussion on Measurement Gap enhancements | OPPO |
R2-2409768 | Discussion on RRM measurement gaps enhancements | vivo |
R2-2409785 | Measurement gap skipping for XR | ZTE Corporation, Sanechips |
R2-2409825 | Discussion on RRM measurement gaps enhancements of XR traffic | Xiaomi Communications |
R2-2409844 | Discussions on measurement gap related enhancements | Fujitsu |
R2-2409854 | Consideration on Enabling TX RX for XR during RRM Measurements | CATT |
R2-2409912 | Discussion on MG enhancement for XR | LG Electronics Inc. |
R2-2409955 | Views on Enhancements Relating to RRM Measurement Gaps | Apple |
R2-2410082 | Impacts on DSR and DRX from MG skipping | NEC |
R2-2410089 | RAN2 Issues on Gap Enhancements | Sharp |
R2-2410095 | Enabling TX/RX for XR during measurement gaps/restrictions | Lenovo |
R2-2410154 | Discussion on RRM enhancements for XR | Huawei, HiSilicon |
R2-2410198 | RRM Measurement Gap/Restrictions | Ericsson |
R2-2410209 | RRM measurement gaps/restrictions related enhancements | Nokia, Nokia Shanghai Bell |
R2-2410245 | Discussion on RRM enhancements for XR | Huawei, HiSilicon |
R2-2410338 | RRC-based MG skipping solution | CMCC, Qualcomm, Google |
R2-2410387 | Discussion on enabling TX/RX for XR during RRM measurements | Sony |
R2-2410406 | RRM measurement gap related enhancements for XR | InterDigital |
R2-2410577 | RRM Measurement Gaps/Restrictions related enhancements for XR | Google Ireland Limited |
R2-2410718 | Discussion on RRM measurement gaps/restrictions enhancements for Rel-19 XR | Samsung |
R2-2410740 | Discussion on XR RRM measurement gaps/restrictions related enhancements | III |
R2-2410761 | Discussion on RRM measurement for XR enhancements | Hanbat National University |
R2-2410783 | Discussion on RRM Measurement Gaps/Restrictions Enhancements | Meta |
TDoc | Title | Source |
---|---|---|
R2-2410390 | UL scheduling enhancements for Multi-modal traffic flows | Sony |
TDoc | Title | Source |
---|---|---|
R2-2409556 | Discussion on LCP enhancements | Qualcomm Incorporated |
R2-2409677 | Discussion on LCP enhancements for XR | OPPO |
R2-2409769 | Remaining issues on LCP enhancements for XR | vivo |
R2-2409786 | LCP enhancements for XR | ZTE Corporation, Sanechips |
R2-2409790 | Discussion on Logical channel priority | CANON Research Centre France |
R2-2409828 | Discussion on LCP enhancements of XR traffic | Xiaomi Communications |
R2-2409845 | Discussions on enhancements for LCH priority-adjusted data | Fujitsu |
R2-2409855 | Consideration on LCP Enhancement | CATT |
R2-2409910 | Discussion on LCP enhancement for XR | LG Electronics Inc. |
R2-2409956 | On Priority Switching during LCP Procedure | Apple |
R2-2410038 | Discussion on how to apply additional priority for delay-aware LCP | TCL |
R2-2410090 | Details of LCP Enhancements | Sharp |
R2-2410094 | Enhanced Logical channel prioritization for XR | Lenovo |
R2-2410194 | Considerations on LCP enhancements for XR | NEC Corporation |
R2-2410208 | Discussion on LCP enhancements for XR | DENSO CORPORATION |
R2-2410210 | LCP Enhancements for XR | Nokia, Nokia Shanghai Bell |
R2-2410316 | Consideration on fairness in delay-aware LCP for XR | CMCC, Qualcomm Incorporated |
R2-2410373 | Discussion on additional priority based LCP enhancements in XR | Huawei, HiSilicon |
R2-2410407 | LCP enhancements for XR | InterDigital |
R2-2410435 | Discussion on Leftover Issues for Additional LCH Priority | China Telecom |
R2-2410500 | LCP enhancements | Ericsson |
R2-2410692 | Remaining issue for LCP enhancement | MediaTek Inc. |
R2-2410784 | Discussion on LCP Enhancements for XR | Meta |
R2-2410844 | Further Discussion on additional LCP handling | ETRI |
R2-2410850 | LCP enhancements for Rel-19 XR – outstanding issues | Samsung R&D Institute UK |
TDoc | Title | Source |
---|---|---|
R2-2409557 | Discussion on DSR enhancements | Qualcomm Incorporated |
R2-2409678 | Discussion on DSR enhancements for XR | OPPO |
R2-2409770 | Remaining issues on DSR enhancements for XR | vivo |
R2-2409787 | DSR enhancements for XR | ZTE Corporation, Sanechips |
R2-2409797 | Discussion on Delay status report | CANON Research Centre France |
R2-2409827 | Discussion on DSR enhancements of XR traffic | Xiaomi Communications |
R2-2409846 | Discussions on DSR enhancements | Fujitsu |
R2-2409856 | Consideration on DSR Enhancement | CATT |
R2-2409911 | Discussion on DSR enhancement for XR | LG Electronics Inc. |
R2-2409957 | Views on DSR Enhancements | Apple |
R2-2410091 | Details of DSR Enhancements | Sharp |
R2-2410189 | Considerations on DSR enhancements for XR | NEC Corporation |
R2-2410211 | DSR Enhancements for XR | Nokia, Nokia Shanghai Bell |
R2-2410212 | Discussion on DSR enhancements for XR | DENSO CORPORATION |
R2-2410229 | Discussion on enhanced DSR for XR | ITRI |
R2-2410286 | Enhanced delay status reporting for XR | Lenovo |
R2-2410317 | Further consideratio on DSR enhancment | CMCC |
R2-2410372 | Discussion on DSR enhancements in XR | Huawei, HiSilicon |
R2-2410408 | DSR enhancements for UL scheduling | InterDigital |
R2-2410436 | Discussion on Leftover Issues for DSR Enhancement | China Telecom |
R2-2410501 | DSR enhancements | Ericsson |
R2-2410684 | Discussion on DSR enhancements | HONOR |
R2-2410717 | DSR enhancements for Rel-19 XR | Samsung |
R2-2410728 | Further discussion on DSR enhancement | TCL |
R2-2410762 | Discussion on XR DSR enhancements | III |
R2-2410785 | Discussion on DSR Enhancements for XR | Meta |
R2-2410843 | Further Discussion on DSR enhancements | ETRI |
TDoc | Title | Source |
---|---|---|
R2-2409558 | Discussion on RLC enhancements | Qualcomm Incorporated |
R2-2409561 | Discussion on AL-FEC awareness at RAN | Qualcomm Incorporated, China Telecom, Huawei, HiSilicon, Lenovo, Nokia, Nokia Shanghai Bell, Xiaomi |
R2-2409636 | RLC AM retransmission enhancements | Xiaomi |
R2-2409733 | Discussion on RLC re-transmission related enhancements | OPPO |
R2-2409740 | Further details of RLC enhancements for XR | LG Electronics Inc. |
R2-2409771 | Discussion on RLC enhancement for XR | vivo |
R2-2409788 | RLC enhancements for XR | ZTE Corporation, Sanechips |
R2-2409798 | Discussion on RLC AM Enhancements | CANON Research Centre France |
R2-2409819 | RLC enhancements | Nokia |
R2-2409847 | Discussions on RLC enhancements | Fujitsu |
R2-2409857 | Consideration on XR-specific RLC Enhancement | CATT |
R2-2409882 | RLC Enhancements for XR | Samsung |
R2-2409958 | Discussions on Fast RLC Retransmission | Apple |
R2-2410036 | Discussion on Reply LS to SA2 on Application-Layer FEC Awareness | TCL |
R2-2410092 | Issues on RLC Enhancements | Sharp |
R2-2410135 | Discussion on timely RLC retransmission(s) | Spreadtrum, UNISOC |
R2-2410155 | Discussion on RLC AM enhancements | Huawei, HiSilicon |
R2-2410199 | More Discussions on RLC AM Enhancements | Ericsson |
R2-2410246 | Discussion on RLC AM enhancements | Huawei, HiSilicon |
R2-2410287 | AM RLC enhancement | Lenovo |
R2-2410337 | Discussion on the RLC enhancements for XR and RAN2 impacts on the SA2 LS | CMCC |
R2-2410383 | RLC AM enhancements | Sony |
R2-2410393 | RLC AM enhancement | NEC |
R2-2410409 | Discussion on RLC enhancements | InterDigital |
R2-2410437 | Discussion on RLC AM Enhancements | China Telecom |
R2-2410685 | Discussion on RLC enhancements | HONOR |
R2-2410777 | RLC AM enhancements with small packet delay budget | MediaTek Inc. |
R2-2410786 | Discussion on RLC AM Enhancements for XR | Meta |
R2-2411002 | Reply LS on Application-Layer FEC Awareness at RAN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409559 | Discussion on XR rate control | Qualcomm Incorporated |
R2-2409637 | XR rate control | Xiaomi |
R2-2409741 | Rate control signaling for XR | LG Electronics Inc. |
R2-2409772 | Discussion on XR rate control | vivo |
R2-2409789 | Data rate control for XR applications | ZTE Corporation, Sanechips |
R2-2409858 | Discussion on XR Rate Control | CATT |
R2-2409901 | XR Rate Control | Lenovo |
R2-2409959 | Views on MAC Signalling for XR Rate Control | Apple |
R2-2410039 | XR rate control | Nokia, Nokia Shanghai Bell |
R2-2410093 | XR Rate Control Enhancements | Sharp |
R2-2410156 | Discussion on XR rate control | Huawei, HiSilicon |
R2-2410191 | Uplink rate control for XR | NEC Corporation |
R2-2410200 | More on XR Rate Control | Ericsson |
R2-2410240 | Discussion on XR rate control | OPPO |
R2-2410247 | Discussion on XR rate control | Huawei, HiSilicon |
R2-2410318 | Further consideration on XR rate control | CMCC |
R2-2410410 | Discussion on UL congestion signaling | InterDigital |
R2-2410490 | Recommended bit rate based XR rate control | Sony |
R2-2410686 | Discussion on XR rate control | HONOR |
R2-2410716 | Discussion on UL rate control for Rel-19 XR | Samsung |
R2-2410739 | Discussion on Rate Control for XR | China Telecom |
R2-2410787 | Discussion on RAN Awareness and UL Rate Control for XR | Meta |
R2-2410877 | Uplink congestion control signalling | MediaTek Inc. |
R2-2411218 | LS on XR UL bit rate control | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409512 | Reply LS on common TA in a regenerative payload scenario (R1-2409258; contact: CMCC) | RAN1 |
R2-2409519 | LS on Supporting MBS broadcast service for NR NTN (R3-245844; contact: Xiaomi) | RAN3 |
R2-2409522 | Reply LS on common TA in a regenerative payload scenario (R4-2416920; contact: CMCC) | RAN4 |
R2-2409536 | Introduction of LTE TN to NR NTN Mobility UE Capability | vivo |
R2-2409669 | Introduction of LTE TN to NR NTN IDLE mode mobility | CATT |
R2-2409938 | Introduction of stage 2 for LTE to NR NTN idle mode mobility | Samsung |
R2-2410861 | Running RRC CR for NR NTN phase 3 | Ericsson |
R2-2410968 | Introduction of LTE TN to NR NTN IDLE mode mobility | CATT |
R2-2410969 | Introduction of stage 2 for LTE to NR NTN idle mode mobility | Samsung |
R2-2410972 | Draft reply on Supporting MBS broadcast service for NR NTN | Xiaomi |
R2-2411196 | Reply on Supporting MBS broadcast service for NR NTN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409666 | Discussion on downlink coverage enhancements | LG Electronics Inc. |
R2-2409671 | Further discussion on downlink coverage enhancements | CATT |
R2-2409821 | Discussion on the DL coverage enhancement at system level | Google Ireland Limited |
R2-2409848 | Discussions on cell DTX during satellite dynamic power sharing | Fujitsu |
R2-2409978 | DL coverage enhancement in NTN | Apple |
R2-2410048 | Discussion on cell DTX | Qualcomm Incorporated |
R2-2410066 | Discussion on DL coverage enhancement | Xiaomi |
R2-2410107 | NR NTN coverage enhancement | China Telecom |
R2-2410122 | Discussion on DL coverage enhancement for NTN | OPPO |
R2-2410213 | Discussion on NTN downlink coverage enhancement | Nokia |
R2-2410267 | Cell barring and reselection for NTN DL-CE | Lenovo |
R2-2410293 | Consideration on downlink coverage enhancement | NEC Corporation |
R2-2410365 | Consideration on downlink coverage enhancements | ZTE Corporation, Sanechips |
R2-2410386 | SMTC impacts due to NTN downlink coverage enhancements | Sony |
R2-2410525 | Discussion on Downlink Coverage Enhancement | Samsung |
R2-2410549 | Downlink coverage enhancement for NTN | InterDigital |
R2-2410671 | RAN2 Impact on DL coverage enhancements | CMCC |
R2-2410677 | NTN DL coverage enhancements | NERCDTV |
R2-2410691 | Discussions on downlink coverage enhancement | HONOR |
R2-2410699 | Discussion on Downlink Coverage Enhancements | Sharp |
R2-2410715 | Discussion on downlink coverage enhancements in NR NTN | ETRI, Korea University |
R2-2410804 | Downlink coverage enhancement SMTC impacts | Sequans Communications |
R2-2410806 | Downlink coverage enhancement access control | Sequans Communications |
R2-2410870 | Discussion on RAN2 Aspects for system-level Downlink Coverage enhancements | THALES |
R2-2410881 | DL coverage enhancements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2410067 | Discussion on uplink capacity enhancement | Xiaomi |
R2-2410330 | Discussion on uplink capacity/throughput enhancement for NR NTN | CMCC |
R2-2410367 | Consideration on NTN miscellaneous issues | ZTE Corporation, Sanechips |
R2-2410434 | Discussion on Uplink Capacity Enhancements | Huawei, HiSilicon, Turkcell |
TDoc | Title | Source |
---|---|---|
R2-2409537 | Further Discussion on MBS Broadcast Service Area Provision | vivo |
R2-2409538 | Discussion on MBS Broadcast Service Continuity in NTN | vivo |
R2-2409615 | Discussion on support of broadcast service in NTN | LG Electronics France |
R2-2409670 | Further discussion on support of broadcast service in NR NTN | CATT, CBN |
R2-2409849 | Discussions on supporting broadcast intended to serve partial cell | Fujitsu |
R2-2409893 | Discussion on providing MBS service area in NTN network | OPPO |
R2-2409977 | Intended broadcast service area provision over NTN | Apple |
R2-2410011 | Discussion on intended service area signalling | NEC |
R2-2410046 | Signaling of MBS broadcast service area information | Qualcomm Incorporated |
R2-2410108 | Broadcast service area information in NR NTN | China Telecom |
R2-2410231 | Discussions on configuration of intended service areas | ITRI |
R2-2410268 | NTN broadcast service area indication and service continuity | Lenovo |
R2-2410331 | Considerations on broadcast service for NR NTN | CMCC |
R2-2410366 | Consideration on broadcast service enhancements | ZTE Corporation, Sanechips |
R2-2410440 | On the Open Points for Supporting MBS in Rel-19 NR NTN | Nokia, Nokia Shanghai Bell |
R2-2410521 | Discussion on MBS broadcast over NTN | Huawei, HiSilicon, Turkcell |
R2-2410526 | Discussion on MBS Broadcast Service Intended Area | Samsung |
R2-2410597 | Support for broadcast service in non-terrestrial networks | InterDigital, Inc. |
R2-2410638 | Discussion on the reply LS to RAN3 on supporting MBS broadcast service for NR NTN | Xiaomi |
R2-2410639 | Discussion on the support of broadcast service | Xiaomi |
R2-2410662 | Further Discussion on Support of MBS Broadcasting over NTN | TCL |
R2-2410700 | Discussion on UE behaviours within intended service area | Sharp |
R2-2410713 | Discussion on the support of broadcast service in NR-NTN | ETRI |
R2-2410764 | Further considerations on intended broadcast service area provision | Continental Automotive |
R2-2410862 | Support for broadcast services in NR NTN | Ericsson |
R2-2410871 | Discussion on MBS Broadcast service area signaling | THALES |
TDoc | Title | Source |
---|---|---|
R2-2409981 | Regenerative payload for NTN for NR Ph3 | TOYOTA Info Technology Center |
R2-2410123 | Discussion on satellite switch with resynch for regenerative payload | OPPO |
R2-2410269 | UE location verification in NTN regenerative architecture | Lenovo |
R2-2410384 | Satellite switch with re-sync in regenerative payload | Sony |
R2-2410590 | Discussion on regenerative payload | Huawei, HiSilicon, Turkcell |
R2-2410649 | Discussion on regenerative payload | Fujitsu Limited |
R2-2410880 | Regenerative payload | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409539 | Discussion on Redirection from E-UTRA TN to NR-NTN | vivo |
R2-2409672 | Discussion on remaing issue for LTE TN to NR NTN IDLE mode mobility | CATT |
R2-2409982 | Improvements_to_LTE-TN-to-NTN_mobility | PANASONIC |
R2-2410047 | Frequency priorities and redirection from LTE to NR NTN | Qualcomm Incorporated |
R2-2410109 | Remaining issue for NTN mobility redirection | China Telecom |
R2-2410394 | Clarification on NR Satellite Info Provision | NEC |
R2-2410439 | On LTE TN to NR NTN reselection using redirection in Release message | Nokia, Nokia Shanghai Bell |
R2-2410485 | Further issues on E-UTRAN to NR NTN idle mode mobility | Samsung |
R2-2410640 | Discussion on the NR NTN frequency configured by the RRC connection release message | Xiaomi |
TDoc | Title | Source |
---|---|---|
R2-2409524 | Reply LS on Support of Regenerative-based Satellite Access (S2-2410918; contact: Qualcomm) | SA2 |
R2-2409529 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions (S2-2411250; contact: Sateliot) | SA2 |
R2-2409530 | Reply LS on FS_5GSAT_Ph3_ARCH conclusions (s3i240703; contact: Tridea Works) | SA3-LI |
R2-2410813 | RRC Runing CR for IoT NTN | Huawei, HiSilicon |
R2-2410883 | Draft Introduction of IoT NTN phase 3 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409540 | Further Discussion on S&F Operation | vivo |
R2-2409585 | Discussion on Store and Forward operation | Xiaomi |
R2-2409674 | Discussion on RAN2 impacts due to the satellite ID list from MME in S&F operation | CATT |
R2-2409676 | Considerations on S&F operation from device perspective | Telit Communications S.p.A., Novamint, Sateliot, Thales |
R2-2409689 | Further consideration on S&F operation in IoT NTN | ZTE Corporation, Sanechips |
R2-2409799 | Support of Store and Forward. | Interdigital, Inc. |
R2-2409822 | Discussion on the S&F operation indication | Google Ireland Limited |
R2-2409876 | Discussion on Store & Forward satellite operation | OPPO |
R2-2409889 | Discussion on support of Store&Forward | Transsion Holdings |
R2-2409935 | Discussion on Store & Forward operation | DENSO CORPORATION |
R2-2409976 | Support of S&F operation in IoT NTN | Apple |
R2-2410049 | Discussion on S&F mode operation | Qualcomm Incorporated |
R2-2410110 | Further discussion of IoT NTN Store & Forward | China Telecom |
R2-2410181 | Discussion on assistance information for S&F | ASUSTeK |
R2-2410270 | Further considerations on S&F operation | Lenovo |
R2-2410314 | Discussion on Support of Store & Forward | TOYOTA Info Technology Center |
R2-2410346 | Discussion on IoT NTN Store and Forward | CMCC |
R2-2410395 | Radio Interface Aspect of S&F | NEC |
R2-2410468 | Radio Interface Impacts of SF operation | Nokia, Nokia Shanghai Bell |
R2-2410482 | Discussion on Store and Forward operation | Samsung |
R2-2410591 | Further consideration on Store and Forward | Huawei, HiSilicon, Turkcell |
R2-2410596 | Considerations on multi-satellite for S&F Satellite operation | NOVAMINT, Sateliot, Thales |
R2-2410599 | Suspend/resume procedure for Store and Forward satellite operation | SHARP Corporation |
R2-2410636 | RAN2 impact on S&F mode | MediaTek Inc. |
R2-2410687 | Discussion on the Store and Forward satellite operation | HONOR |
R2-2410765 | Further considerations on S&F operations | Continental Automotive |
R2-2410854 | Support of Store & Forward | Sequans Communications |
R2-2410863 | Support for store and forward in IoT NTN | Ericsson |
R2-2410974 | Report of [AT128][304][R19 IoT NTN] Satellite IDs for S&F | CATT |
R2-2410975 | Draft LS on Satellite IDs for S&F | CATT |
R2-2411197 | LS on Satellite IDs for store-and-forward operation | RAN2 |
R2-2411205 | Draft] LS on MME-configured satellite list for store and forward operation | CATT |
TDoc | Title | Source |
---|---|---|
R2-2409541 | Discussion on CB-Msg3 Mechanism | vivo |
R2-2409586 | Discussion on uplink capacity enhancements for IoT NTN | Xiaomi |
R2-2409591 | Discussion on the RAN2 solutions for uplink capacity enhancement | Huawei, HiSilicon |
R2-2409673 | Further consideration on UL capacity enhancements | CATT |
R2-2409690 | Further consideration on UL capacity enhancements in IoT NTN | ZTE Corporation, Sanechips |
R2-2409800 | EDT/PUR enhancements. | Interdigital, Inc. |
R2-2409877 | Discussion on CB-msg3 EDT and msg4 enhancement | OPPO |
R2-2409937 | Further considerations on retransmission and finite buffer for DSA | NTU |
R2-2409975 | Uplink capacity enhancement in IoT NTN | Apple |
R2-2410050 | CB-Msg3 and Msg4 enhancements | Qualcomm Incorporated |
R2-2410111 | Contention-based Msg3-EDT in IoT NTN | China Telecom |
R2-2410271 | EDT for uplink capacity enhancement in NTN | Lenovo |
R2-2410291 | Consideration on UL capacity enhancement for IoT-NTN | NEC Corporation |
R2-2410296 | Discussion on the use of an implicit pointer for locating DSA replicas for EDT of CB-Msg3 | DLR, ESA |
R2-2410309 | Further discussion on UL capacity enhancement for IoT NTN | Nokia, Nokia Shanghai Bell |
R2-2410332 | Considerations on uplink capacity enhancement for IoT-NTN | CMCC |
R2-2410347 | Discussion on Uplink Capacity Enhancement | TOYOTA Info Technology Center |
R2-2410483 | Procedures for contention-based Msg3 | Samsung |
R2-2410641 | Discussion on enhanced EDT | MediaTek Inc. |
R2-2410725 | Discussion on EDT Enhancements for IOT NTN | Skylo Technologies |
R2-2410875 | Implicit pointer for locating DSA replicas for EDT of CB-Msg3 | DLR, ESA, Inmarsat, Viasat |
R2-2410882 | UL capacity enhancements for IoT NTN | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409542 | Further Discussion on PWS Support for NB-IoT | vivo |
R2-2409587 | PWS support for NB-IoT over NTN | Xiaomi |
R2-2409675 | Support of PWS for NB-IoT NTN UE | CATT |
R2-2409691 | Further consideration on PWS support for NB-IoT over NTN | ZTE Corporation, Sanechips |
R2-2409801 | Support of PWS. | Interdigital, Inc. |
R2-2409896 | Discussion on supporting PWS in IOT-NTN network | OPPO |
R2-2410051 | Discussion on PWS in NB-IoT NTN | Qualcomm Incorporated |
R2-2410272 | PWS broadcast support for NB-IoT in NTN | Lenovo |
R2-2410289 | Discussion on PWS for NB-IoT | |
R2-2410292 | Consideration on PWS broadcast for NB-IoT | NEC Corporation |
R2-2410304 | Further considerations on PWS support for NB-IoT | Huawei, HiSilicon, Turkcell |
R2-2410310 | Further discussion on support of PWS | Nokia, Nokia Shanghai Bell |
R2-2410333 | Support of PWS messages for NB-IoT | CMCC |
R2-2410484 | Impact of PWS signalling for NB-IoT | Samsung |
R2-2410643 | Discussion on supporting PWS for NB-IoT | MediaTek Inc. |
R2-2410864 | Support for PWS in NB-IoT NTN | Ericsson |
R2-2410976 | Draft LS on PWS reception in RRC_CONNECTED | InterDigital |
R2-2411194 | LS on PWS support in RRC_CONNECTED for NB-IoT NTN | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409635 | MRO enhancements for Rel-18 mobility features | Samsung |
R2-2409650 | Discussion on MRO Enhancements for Rel-18 Mobility | CATT |
R2-2409754 | Further considerations on MRO | ZTE Corporation, Sanechips |
R2-2409779 | MRO for MOB DCCA | LG Electronics |
R2-2409780 | MRO for MOB LTM | LG Electronics |
R2-2409933 | Discussion on MRO enhancement for LTM | China Unicom |
R2-2409934 | Discussion on MRO enhancement for CHO with candidate SCGs | China Unicom |
R2-2409970 | SON for LTM | Apple |
R2-2409983 | MRO for CHO with candidate SCG | Nokia |
R2-2409984 | MRO for LTM | Nokia |
R2-2410065 | MRO for Rel-18 mobility | NEC |
R2-2410182 | Discussion on random access report for LTM | ASUSTeK |
R2-2410274 | Discussion on MRO for R18 mobility | Lenovo |
R2-2410328 | MRO enhancements for CHO with candidate SCGs | CMCC |
R2-2410329 | MRO enhancements for LTM | CMCC |
R2-2410473 | SON support for MRO | Ericsson |
R2-2410635 | SON enhancement for CHO with candidate SCG | SHARP Corporation |
R2-2410656 | Discussion on MRO enhancements for Rel-18 mobility | Huawei, HiSilicon |
R2-2410733 | MRO enhancement for SON and MDT | Qualcomm Incorporated |
R2-2410757 | Configuring UE based TA acquisition for LTM | Rakuten Mobile, Inc |
R2-2410815 | MRO for Rel-18 mobility features | vivo |
TDoc | Title | Source |
---|---|---|
R2-2409649 | Considerations on R18 leftovers for SDT | CATT |
R2-2409655 | Reporting failure cause for SDT | Samsung |
R2-2409755 | Consideration on RAN3 agreed RA report content | ZTE Corporation, Sanechips |
R2-2410275 | Discussion on RACH optimization for SDT | Lenovo |
R2-2410657 | Discussion on support of the Rel-18 leftovers | Huawei, HiSilicon |
R2-2410816 | RACH optimization for SDT | vivo |
R2-2410847 | On Rel.18 leftovers | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2409571 | Discussion on random access procedure in SBFD | ZTE Corporation |
R2-2409579 | Discussion on RACH in SBFD | Xiaomi |
R2-2409584 | Discussion on RACH in SBFD | Xiaomi |
R2-2409625 | Consideration on Random Access in SBFD symbols | CATT |
R2-2409680 | SBFD RACH configuration for initial random access | Charter Communications, Inc |
R2-2409745 | Impacts on the random access by the evolution of duplex operation | Huawei, HiSilicon |
R2-2409794 | Random Access for SBFD Operation | NEC |
R2-2409913 | Discussion on Random Access in SBFD | LG Electronics Inc. |
R2-2409974 | Detailed design for RACH in SBFD | Apple |
R2-2409995 | SBFD RA aspects | Ericsson |
R2-2410088 | RA Aspects for SBFD | Sharp |
R2-2410241 | Random Access Operation of SBFD | Nokia Corporation |
R2-2410336 | Discussion on random access in SBFD | CMCC |
R2-2410385 | Random access for SBFD Operation | Sony |
R2-2410478 | Views on random access for SBFD | Qualcomm Incorporated |
R2-2410574 | Random Access in Sub-Band Full Duplex | Google Ireland Limited |
R2-2410609 | Random access in SBFD | Samsung |
R2-2410791 | Discussion on random access procedure in SBFD | vivo |
R2-2410794 | Discussion on random access in SBFD | Fujitsu Limited |
TDoc | Title | Source |
---|---|---|
R2-2409572 | Discussion on CLI measurement in SBFD | ZTE Corporation |
R2-2409626 | Discussion on other aspects for SBFD | CATT |
R2-2409638 | Other aspects of SBFD | Xiaomi |
R2-2409681 | SBFD-aware UE capability indication | Charter Communications, Inc |
R2-2409746 | Other impacts by the evolution of duplex operation | Huawei, HiSilicon |
R2-2409793 | Selection of SBFD Cell | NEC |
R2-2409996 | Non-RA aspects for subband full duplex (SBFD) operation | Ericsson |
R2-2410258 | Other aspects of SBFD | Nokia |
R2-2410479 | Other aspects of SBFD | Qualcomm Incorporated |
R2-2410623 | Support of Cross Link Interference in SBFD | Samsung |
R2-2410792 | Discussion on other aspects in SBFD | vivo |
TDoc | Title | Source |
---|---|---|
R2-2410325 | Work Plan for Rel-19 on NR MIMO Phase 5 | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2409640 | Consideration on Asymmetric DL sTRP/UL mTRP | LG Electronics Inc. |
R2-2409661 | Discussion on asymmetric DL sTRP and UL mTRP | Xiaomi |
R2-2409721 | Discussion on RRC and MAC Impacts for Asymmetric DL sTRP/UL mTRP | CATT |
R2-2409773 | Discussion on MAC CE impact for asymmetric DL sTRP/UL mTRP scenarios | vivo |
R2-2409954 | RAN2 Impacts for Rel-19 NR MIMO | Apple |
R2-2410248 | RAN2 Aspects of Asymmetric DL sTRP/UL mTRP | Nokia Corporation |
R2-2410294 | Asymmetric DL/UL mTRP user plane impact from MIMO ph. 5 | Ericsson |
R2-2410326 | Discussion on asymmetric DL sTRP and UL mTRP | CMCC |
R2-2410388 | Enhancement for Asymmetric DL sTRP/UL mTRP | Sony |
R2-2410429 | Discussion on UL only mTRP | Qualcomm Incorporated |
R2-2410520 | Discussion on Asymmetric DL sTRP/UL mTRP | Huawei, HiSilicon |
R2-2410523 | Discussion on Asymmetric DL sTRP/UL mTRP | Samsung |
R2-2410770 | Consideration on the PL Offset MAC CE for R19 MIMO | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409641 | Impact from UEI beam reporting | LG Electronics Inc. |
R2-2409660 | Discussion on the modelling of the UE-initiated beam report | Xiaomi |
R2-2409774 | Discussion on UE-initiated/event-driven beam management | vivo |
R2-2409891 | Discussion on UE-initiated/event-driven beam management | SHARP Corporation |
R2-2410202 | Impacts from other NR MIMO Phase 5 objectives | Ericsson |
R2-2410250 | RAN2 Aspects of the NR MIMO | Nokia Corporation |
R2-2410327 | Discussion on UE-initiated/event-driven beam management | CMCC |
R2-2410355 | Discussion on MAC CE impact of Rel-19 MIMO | NEC |
R2-2410430 | Discussion on UE initiated beam reporting | Qualcomm Incorporated |
R2-2410524 | Discussion on UE-initiated Beam Reporting and CSI enhancement | Samsung |
R2-2410618 | Enhancements for UE-initiated/event-driven beam management | Huawei, HiSilicon |
R2-2410771 | Consideration on the UEIBM for R19 MIMO | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2409632 | Discussion on topology and intermediate relay UE (re)selection | vivo |
R2-2409728 | Discussion on multi-hop U2N relay discovery and relay selection | NEC Corporation |
R2-2409730 | Discovery and relay (re)selection for multi-hop U2N relay | OPPO |
R2-2409859 | Discussion on Multi-hop Discovery and (Re)selection | CATT |
R2-2409906 | Discussion on relay discovery and (re)selection for NR sidelink multi-hop relay | TOYOTA InfoTechnology Center |
R2-2409967 | Relay discovery and selection for Multi-hop UE-to-NW Relay | Apple |
R2-2410007 | Discovery and Relay (Re)Selection for Multi-hop U2N Relays | InterDigital |
R2-2410032 | Discussion on multi-hop Relay discovery and (re)selection | ZTE Corporation, Sanechips |
R2-2410104 | Multi-hop relay discovery and reselection | China Telecom |
R2-2410150 | discussion on discovery and relay (re)selection | Ericsson |
R2-2410183 | Remaining issues on multi-hop U2N Relay Discovery message forwarding | ASUSTeK |
R2-2410281 | Relay (re)selection in Multi-hop relay | Lenovo |
R2-2410288 | Relay discovery aspects for multi-hop relay | Nokia |
R2-2410298 | Discussion on the discovery and relay (re)selection for multi-hop U2N relay | LG Electronics Inc. |
R2-2410305 | Report of [POST127][401][Relay] MH relay discovery and (re)selection | LG Electronics Inc. |
R2-2410392 | Multi-hop relay selection/re-selection | Sony |
R2-2410570 | Discovery and (re)selection under multihop relay | Kyocera |
R2-2410587 | Relay discovery and (re)selection for multi-hop Relay | Huawei, HiSilicon |
R2-2410619 | Relay discovery and (re)selection | TCL |
R2-2410704 | discussion on Relay discovery and (re)selection for multi-hop relay | Sharp |
R2-2410734 | Discovery and Relay (re)selection for multi-hop U2N relay | Qualcomm Incorporated |
R2-2410827 | Considerations on relay discovery and (re)selection | Samsung |
R2-2410840 | Relay discovery and (re)selection | TCL |
R2-2410981 | Report of [POST127][401][Relay] MH relay discovery and (re)selection | LG Electronics Inc. |
R2-2411125 | LS to SA2 on relay discovery announcement | ZTE Corporation, Sanechips |
R2-2411184 | LS to SA2 on relay discovery announcement | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2409633 | Discussion on CP and SRAP impact for Approach 1 | vivo |
R2-2409732 | Control plane procedures of multi-hop U2N relay | OPPO |
R2-2409796 | CP and SRAP for Multi-hop Relay | NEC |
R2-2409860 | Discussion on the Control Plane Procedures | CATT |
R2-2409968 | Discussion on End-to-End Connection Setup Approaches for Multi-hop UE-to-NW Relay | Apple |
R2-2409969 | Discussion on SRAP for Multi-hop Layer-2 U2N Relay | Apple |
R2-2410006 | Report of [Post127][402][Relay] Multi-hop relay control plane | InterDigital |
R2-2410008 | Control Plane Aspects for Multi-hop U2N Relays | InterDigital |
R2-2410033 | Discussion on control plane procedures for multi-hop SL relay | ZTE Corporation, Sanechips |
R2-2410105 | Discussion on control plane aspects for NR sidelink multi-hop relay | China Telecom |
R2-2410139 | Discussion on control plane and QoS handling for NR sidelink multi-hop relay | Spreadtrum, UNISOC |
R2-2410149 | discussion on control plane procedure | Ericsson |
R2-2410184 | Remaining issues on SRB0 message forwarding in multi-hop U2N Relay | ASUSTeK |
R2-2410282 | Control plane in Multi-hop relay | Lenovo |
R2-2410290 | SRAP impacts on MH relay | Nokia |
R2-2410297 | Discussion on the control plane procedure for multi-hop U2N relay | LG Electronics Inc. |
R2-2410569 | Control Plane under multihop L2 U2N relaying | Kyocera |
R2-2410588 | Control plane procedures for multi-hop relay | Huawei, HiSilicon |
R2-2410631 | On approach 1 | Nokia |
R2-2410705 | discussion on C-plane procedure for multi-hop relay | Sharp |
R2-2410735 | Control procedure for multi-hop L2 based U2N relay | Qualcomm Incorporated |
R2-2410756 | Consideration on CP and UP issues for multi-hop SL relay | Samsung |
R2-2411128 | Way forward on SL multi-hop relay | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2409634 | Discussion on Service continuity for multi-hop relay | vivo |
R2-2409731 | Service continuity of multi-hop U2N relay | OPPO |
R2-2409861 | Intra-gNB Service Continuity for Multi-hop U2N Relay | CATT |
R2-2410034 | Discussion on service continuity for multi-hop SL relay | ZTE Corporation, Sanechips |
R2-2410106 | Discussion on service continuity for multi-hop relay | China Telecom |
R2-2410185 | Discussion on measurement report for multi-hop U2N Relay | ASUSTeK |
R2-2410201 | Service Continuity for Multi-Hop Relays | Ericsson |
R2-2410283 | Service continuity for Multi-hop system | Lenovo |
R2-2410299 | Discussion on service continuity for multi-hop U2N relay | LG Electronics Inc. |
R2-2410354 | Considerations on Service Continuity of Multi-hop Relay | NEC |
R2-2410589 | Discussion on service continuity for Multi-hop Relay | Huawei, HiSilicon |
R2-2410706 | discussion on service continuity for multi-hop relay | Sharp |
R2-2410736 | Consideration on multi-hop U2N relay service continuity | Qualcomm Incorporated |
R2-2410828 | Initial considerations on service continuity | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2409516 | Reply LS on Support of UE move between CAG cell of 5G Femto and CSG cell (R3-244830; contact: Ericsson) | RAN3 |
R2-2409528 | Reply LS on Clarification regarding definition of 5G NR femto ownership (S2-2411241; contact: LGE) | SA2 |
TDoc | Title | Source |
---|---|---|
R2-2409573 | Introduction of NavIC in A-GNSS positioning | ZTE Corporation |
R2-2409723 | Discussion on Introduction of NavIC L1 SPS support to A-GNSS positioning | Reliance Jio, CEWiT |
R2-2409724 | Introduction of NavIC L1 SPS A-GNSS in LTE Stage 2 specification | Reliance Jio, CEWiT, Ericsson, Huawei |
R2-2409725 | Introduction of NavIC L1 SPS A-GNSS in NR Stage 2 specification | Reliance Jio, CEWiT, Ericsson, Huawei |
R2-2409726 | Introduction of NavIC L1 SPS A-GNSS in LPP | Reliance Jio, ISRO, CEWiT, MediaTek, Ericsson |
R2-2410161 | Discussion on the support of NavIC L1 SPS | Huawei, HiSilicon |
R2-2410243 | A-GNSS support for NavIC L1 SPS | NEC |
TDoc | Title | Source |
---|---|---|
R2-2409574 | Introduction of BDS B2b in A-GNSS positioning | ZTE Corporation |
R2-2409627 | Introduction of B2b signal in BDS system in A-GNSS | CATT, CAICT, Ericsson, Huawei, HiSilicon |
R2-2410158 | Introduction of BDS B2b in A-GNSS for TS 36305 | Huawei, HiSilicon, CAICT, CATT, Ericsson |
R2-2410159 | Introduction of BDS B2b in A-GNSS for TS 38305 | Huawei, HiSilicon, CAICT, CATT, Ericsson |
R2-2410160 | Discussion on the remaining issues for BDS B2b | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2409694 | Work plan for WID: introduction of IoT-NTN TDD mode | Iridium Satellite LLC |
TDoc | Title | Source |
---|---|---|
R2-2409504 | LS on the potential impact on RAN2 specifications due to supporting ProSe in NPN (C1-245500; contact: Nokia) | CT1 |
R2-2409931 | Enhancement for resolving throughput degradation during handover | China Unicom, Huawei, HiSilicon, Sony, Turkcell, NTT Docomo, Meta |
R2-2409985 | Support of ProSe in NPN (CT1 LS R2-2409504/C1-245500) | Nokia |
R2-2410017 | Discussion on support of NPN for ProSe | ZTE Corporation, Sanechips |
R2-2410542 | Quality Indication in Msg3 for SDT | Ericsson |
R2-2410548 | Terminating Non-MPS Subscribed UE Handling | Peraton Labs |
R2-2410613 | PDCP SN Gap reporting at mobility | Nokia |
R2-2410655 | Discussion on the issue of ANR reporting of HSDN cells [ANR_HSDN] | Huawei, HiSilicon, CMCC, China Unicom, China Telecom, CATT, \tNTT DoCoMo |
R2-2410674 | Discussion on UE aggregation enhancement | CMCC, ZTE, Media Tek Inc., vivo, CATT |
R2-2410675 | Corrections to TS 38.331 on SL Relay enhancement | CMCC, Media Tek Inc., CATT |
R2-2410676 | Corrections to TS 38.300 on SL Relay enhancement | CMCC, Media Tek Inc., CATT |
R2-2410793 | Inclusion of the NB-IoT satellite information in E-UTRAN | Google, Samsung, MediaTek Inc. |
R2-2411085 | Inclusion of the NB-IoT satellite information in E-UTRAN | Google, Samsung, MediaTek Inc.,Inmarsat, Viasat, Thales, Nordic Semiconductor |
TDoc | Title | Source |
---|---|---|
R2-2410911 | Report from session on V2X/SL, R19 NES and MOB | Vice Chairman (Samsung) |
TDoc | Title | Source |
---|---|---|
R2-2410912 | Rel-18 MIMO and MUSIM, Rel-19 MIMO, LPWUS, and SBFD | Vice Chairman (CATT) |
TDoc | Title | Source |
---|---|---|
R2-2410913 | Report from session on NR NTN and IoT NTN | Session chair (ZTE) |
TDoc | Title | Source |
---|---|---|
R2-2410914 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
TDoc | Title | Source |
---|---|---|
R2-2410915 | Report from session on R18 MBS, R18 QoE and R19 XR | Session chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R2-2410916 | Report from session on maintenance and SON/MDT | Session chair (Ericsson) |