| 2 |
Approval of Agenda |
|
| R1-2302255 |
Draft Agenda of RAN1#112bis-e meeting |
RAN1 Chair |
| R1-2302258 |
RAN1#112bis-e Meeting Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2302259 |
RAN1#112bis-e Meeting Management |
RAN1 Chair |
| R1-2302296 |
Towards Rel-18 Completion in RAN1 |
RAN1 Chair |
| 3 |
Highlights from RAN plenary |
|
| R1-2302257 |
Highlights from RAN#99 |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2302256 |
Report of RAN1#112 meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2302260 |
Reply LS on FS_5MBS_Ph2 progress |
RAN3, Huawei |
| R1-2302261 |
LS on Approaches during execution for inter-DU LTM |
RAN3, Ericsson |
| R1-2302262 |
Reply LS on interference modelling |
RAN4, CATT |
| R1-2302263 |
LS reply on RACH-less handover in NTN |
RAN4, OPPO |
| R1-2302264 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
RAN4, CATT |
| R1-2302265 |
Reply LS on UE power limitation for STxMP in FR2 |
RAN4, vivo |
| R1-2302266 |
LS on Rel-18 Multi-carrier enhancement for NR |
RAN4, China Telecom |
| R1-2302267 |
LS on the UE SRS IL imbalance issue |
RAN4, Huawei |
| R1-2302268 |
LS on clarification on impact of SRS antenna switching for TDD-FDD band combinations |
RAN4, Huawei |
| R1-2302269 |
Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 |
RAN4, Qualcomm |
| R1-2302270 |
Reply LS on enhancements to realize increasing UE power high limit for CA and DC |
RAN4, NTT DOCOMO INC |
| R1-2302271 |
LS on co-channel coexistence |
RAN4, Huawei |
| R1-2302272 |
LS on updated Rel-17 RAN4 feature list for NR |
RAN4, CMCC |
| R1-2302273 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN4, CATT |
| R1-2302274 |
Reply LS on Latency impact for NTN verified UE location |
SA1, Xiaomi |
| R1-2302275 |
Reply LS on transmission bandwidths for NR on dedicated spectrum less than 5 MHz |
RAN, Nokia |
| R1-2302276 |
Reply LS on spectrum less than 5 MHz |
RAN, Nokia |
| R1-2302277 |
Reply LS on msg1/msgA transmission channel access control |
RAN2, Qualcomm |
| R1-2302278 |
LS to RAN1 on SL resource (re)selection |
RAN2, Lenovo |
| R1-2302279 |
Reply LS on cast types for IUC scheme 1 |
RAN2, Apple |
| R1-2302280 |
LS on Comparison of SL-RSRP and SD-RSRP measurements |
RAN2, Nokia |
| R1-2302281 |
Reply LS on RAN dependency for Ranging & Sidelink Positioning |
RAN2, Xiaomi |
| R1-2302282 |
LS on error source distributions |
RAN2, CATT |
| R1-2302283 |
LS on LBT and SL resource (re)selection |
RAN2, Nokia |
| R1-2302284 |
LS on RAN2 agreement for sidelink CAPC |
RAN2, OPPO |
| R1-2302285 |
Reply LS on Pemax,c of S-SSB transmission |
RAN2, vivo |
| R1-2302286 |
Reply LS to SA2 on satellite access for PRUs |
RAN2, CATT |
| R1-2302287 |
Reply LS to RAN1 on LP-WUR architectures |
RAN4, vivo |
| R1-2302288 |
LS on 3GPP work on Energy Efficiency |
SA5, Huawei |
| R1-2302386 |
Discussion on UL Tx switching across 3 or 4 bands in Rel-18 |
Huawei, HiSilicon |
| R1-2302444 |
Draft reply LS to RAN2 on SL resource (re)selection |
vivo |
| R1-2302445 |
Draft reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
vivo |
| R1-2302446 |
Draft LS reply on Rel-18 Multi-carrier enhancement for NR |
vivo |
| R1-2302447 |
Draft Reply LS to RAN2 on RAN dependency for Ranging & Sidelink Positioning |
vivo |
| R1-2302448 |
Draft Reply LS on error source distributions |
vivo |
| R1-2302449 |
Discussion on RAN4 LS for low-power wake-up receiver architectures |
vivo |
| R1-2302450 |
Draft reply LS to RAN4 on low-power wake-up receiver architectures |
vivo |
| R1-2302451 |
Discussion on impact of SRS antenna switching for TDD-FDD band combinations |
vivo |
| R1-2302452 |
Discussion the UE SRS IL imbalance issue |
vivo |
| R1-2302525 |
Discussion on comparison of SL-RSRP and SD-RSRP measurements |
OPPO |
| R1-2302526 |
Draft reply LS on comparison of SL-RSRP and SD-RSRP measurements |
OPPO |
| R1-2302527 |
Draft reply LS to RAN2 on RAN dependency for Ranging & Sidelink Positioning |
OPPO |
| R1-2302638 |
Discussion on RAN4 reply LS on LP-WUR architecture in R1-2302287(R4-230712) |
CATT |
| R1-2302639 |
Discussion on RAN4 LS on Rel-18 Multi-carrier enhancement for NR |
CATT |
| R1-2302640 |
Discussion on RAN2 LS on RAN dependency for Ranging & Sidelink Positioning |
CATT |
| R1-2302641 |
Draft reply LS on RAN dependency for Ranging & Sidelink Positioning |
CATT |
| R1-2302642 |
Discussion on RAN2 LS on error source distributions |
CATT |
| R1-2302643 |
Draft reply LS on error source distributions |
CATT |
| R1-2302644 |
Draft reply LS on LBT and SL resource (re)selection |
CATT, GOHIGH |
| R1-2302645 |
Discussion on LS on SL resource (re)selection trigger |
CATT, GOHIGH |
| R1-2302754 |
[Draft] Reply LS on Rel-18 Multi-carrier enhancement for NR |
ZTE |
| R1-2302772 |
Discussion on LS on error source distributions |
OPPO |
| R1-2302773 |
Discussion on the LS from RAN2 on RAN dependency for Ranging & Sidelink Positioning |
OPPO |
| R1-2302777 |
Discussions on reply LS on Rel-18 multi-carrier enhancement |
Intel Corporation |
| R1-2302778 |
Discussions on reply LS on Rel-18 NR SL Relay |
Intel Corporation |
| R1-2302779 |
Discussions on reply LS on LP-WUR architectures |
Intel Corporation |
| R1-2302824 |
Discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements |
InterDigital, Inc. |
| R1-2302921 |
Discussion on LS on comparison of SL-RSRP and SD-RSRP measurements |
LG Electronics |
| R1-2302940 |
Discussion on reply LS on LP-WUR architecture |
ZTE, Sanechips |
| R1-2302941 |
[Draft] Reply LS on LP-WUR architecture |
ZTE, Sanechips |
| R1-2302955 |
[Draft] Reply LS on Rel-18 Multi-carrier enhancement for NR |
xiaomi |
| R1-2303095 |
Draft Reply LS on clarification on impact of SRS antenna switching for TDD-FDD band combinations |
Samsung |
| R1-2303096 |
Draft reply LS on error source distributions |
Samsung |
| R1-2303097 |
Draft reply LS on SL positioning QoS parameters |
Samsung |
| R1-2303098 |
Discussion on SL positioning QoS parameters |
Samsung |
| R1-2303165 |
Discussion of RAN4 LS on Rel-18 Multi-carrier enhancement for NR |
Spreadtrum Communications |
| R1-2303270 |
Discussion on RAN4 LS on the UE SRS IL imbalance issue |
Nokia, Nokia Shanghai Bell |
| R1-2303271 |
Draft Reply LS on error source distributions |
ZTE |
| R1-2303272 |
Discussion on error source distributions for integrity |
ZTE |
| R1-2303273 |
Draft Reply LS on RAN dependency for Ranging & Sidelink Positioning |
ZTE |
| R1-2303319 |
[Draft] Reply LS on SL resource (re)selection |
Ericsson |
| R1-2303320 |
Discussion on Reply LS on SL resource (re)selection |
Ericsson |
| R1-2303321 |
[Draft] Reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
Ericsson |
| R1-2303322 |
Discussion on Reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
Ericsson |
| R1-2303370 |
Discussion on RAN2 LS on SL resource (re)selection |
MediaTek Inc. |
| R1-2303371 |
Discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements |
MediaTek Inc. |
| R1-2303395 |
Draft reply LS to RAN2 on SL resource (re)selection |
ZTE, Sanechips |
| R1-2303396 |
Draft reply LS on comparison of SL-RSRP and SD-RSRP measurements |
ZTE, Sanechips |
| R1-2303397 |
About LS on LBT and SL resource (re)selection |
ZTE, Sanechips |
| R1-2303441 |
Draft Reply LS to RAN2 on error source distributions |
InterDigital, Inc. |
| R1-2303442 |
Discussion on LS reply regarding error source distributions |
InterDigital, Inc. |
| R1-2303457 |
Discussions on reply LS on SRS IL imbalance |
Intel Corporation |
| R1-2303461 |
Draft reply LS to RAN4 on LP-WUR architectures |
Apple |
| R1-2303462 |
Draft reply LS to RAN4 on Rel-18 multi-carrier enhancements for NR |
Apple |
| R1-2303463 |
Discussion on RAN4 LS on Co-channel Coexistence |
Apple |
| R1-2303464 |
Draft Reply LS to RAN4 on Co-channel Coexistence |
Apple |
| R1-2303465 |
Discussion on RAN2 LS on Comparison of SL-RSRP and SD-RSRP Measurements |
Apple |
| R1-2303466 |
Draft Reply LS to RAN2 on Comparison of SL-RSRP and SD-RSRP Measurements |
Apple |
| R1-2303520 |
DRAFT Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 |
Nokia, Nokia Shanghai Bell |
| R1-2303544 |
Discussion on draft reply LS on error source distributions |
Ericsson |
| R1-2303557 |
Draft Reply to RAN2 LS on SL resource (re)selection |
Qualcomm Incorporated |
| R1-2303558 |
Clarification on SRS antenna switching |
Qualcomm Incorporated |
| R1-2303559 |
Draft Reply to RAN2 LS on Comparison of SL-RSRP and SD-RSRP measurements |
Qualcomm Incorporated |
| R1-2303560 |
Draft Reply to RAN4 LS on NR support for dedicated spectrum less than 5 MHz for FR1 |
Qualcomm Incorporated |
| R1-2303561 |
Draft Reply to LS on RAN dependency for Ranging & Sidelink Positioning |
Qualcomm Incorporated |
| R1-2303562 |
Draft Reply to LS on RAN4 LS on Multi-Carrier enhancement for NR |
Qualcomm Incorporated |
| R1-2303563 |
Draft reply to RAN 4 LS on the UE SRS IL imbalance issue |
Qualcomm Incorporated |
| R1-2303629 |
Discussion on RAN4 LS for multi-carrier enhancement |
OPPO |
| R1-2303645 |
Draft Reply LS on RAN dependency for Ranging & Sidelink Positioning |
xiaomi |
| R1-2303646 |
Draft reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
xiaomi |
| R1-2303657 |
Discussion on RAN4 LS on the UE SRS IL imbalance issue |
ZTE |
| R1-2303689 |
Discussion on reply LS on Multi-carrier enhancement for NR |
NTT DOCOMO, INC. |
| R1-2303754 |
Discussion on RAN4 reply LS for LP-WUR architectures |
Ericsson |
| R1-2303799 |
Draft Reply LS on 3GPP work on energy efficiency |
Huawei, HiSilicon |
| R1-2303800 |
Discussion on SL positioning QoS parameters |
Huawei, HiSilicon |
| R1-2303845 |
Discussion on RAN4 LS on dedicated spectrum less than 5 MHz |
ZTE |
| R1-2303846 |
[Draft] Reply LS to RAN4 on dedicated spectrum less than 5MHz |
ZTE |
| R1-2303853 |
Discussion of RAN4 LS on LP-WUR architecture |
Huawei, HiSilicon |
| R1-2303855 |
Discussion on RAN2 LS on SL resource (re)selection |
Huawei, HiSilicon |
| R1-2303856 |
Draft reply LS on UL Tx switching across 3 or 4 bands in Rel-18 |
Huawei, HiSilicon |
| R1-2303857 |
Discussion on RAN2 LS on Comparison of SL-RSRP and SD-RSRP measurements |
Huawei, HiSilicon |
| R1-2303859 |
Discussion on error source distributions |
Huawei, HiSilicon |
| R1-2303860 |
Discussion on the UE SRS IL imbalance issue |
Huawei, HiSilicon |
| R1-2303861 |
Discussion on SRS antenna switching for TDD-FDD band combinations |
Huawei, HiSilicon |
| R1-2303866 |
Discussion on RAN4 LS on co-channel coexistence |
Huawei, HiSilicon |
| R1-2303867 |
Draft reply LS on co-channel coexistence |
Huawei, HiSilicon |
| R1-2303873 |
Discussion of RAN2 LS on Comparison of SL-RSRP and SD-RSRP measurements R1-2302280(R2-2302234) |
Nokia, Nokia Shanghai Bell |
| R1-2303874 |
[Draft] Reply LS on Comparison of SL-RSRP and SD-RSRP measurements |
Nokia, Nokia Shanghai Bell |
| R1-2304137 |
[112bis-e-LS-03] FL summary of email discussion on reply LS for Rel-18 Tx switching |
Moderator (China Telecom) |
| R1-2304219 |
Reply LS on Rel-18 Multi-carrier enhancement for NR |
RAN1, China Telecom |
| R1-2304245 |
Summary on impact of SRS antenna switching for TDD-FDD band combinations |
Moderator (Huawei) |
| R1-2304284 |
Summary of email discussion [112bis-e-LS-04] |
Moderator (Huawei) |
| 7.1 |
Maintenance on NR Releases 15-16 |
|
| R1-2302453 |
Discussion on contention window adjustment procedures |
vivo |
| R1-2302454 |
Draft Rel-16 CR on TS 37.213 on contention window adjustment procedures |
vivo |
| R1-2302455 |
Draft Rel-17 mirror CR on TS 37.213 on contention window adjustment procedures |
vivo |
| R1-2302528 |
Correction to CWS adjustment for channels without explicit HARQ feedback |
OPPO |
| R1-2302646 |
Correction on PUCCH resource determination in Rel-16 |
CATT |
| R1-2302647 |
Editorial corrections in TS 38.213 in Rel-16 |
CATT |
| R1-2302648 |
Correction on impact of DAPS handover in Rel-16 |
CATT |
| R1-2302649 |
Correction on impact of DAPS handover in Rel-17 |
CATT |
| R1-2302677 |
Correction on NFI definition for Type-2 HARQ-ACK codebook in Rel-16 |
CATT |
| R1-2302678 |
Correction on NFI definition for Type-2 HARQ-ACK codebook in Rel-17 |
CATT |
| R1-2302679 |
Editorial corrections in TS 38.213 in Rel-17 |
CATT |
| R1-2302768 |
Draft CR on TBS determination of a PUSCH retransmission with initial PUSCH scheduled by RAR UL grant for CFRA |
Ericsson |
| R1-2302956 |
Correction on indication period for RLM for DRX mode in TS 38.213 |
xiaomi |
| R1-2303099 |
Draft CR for default value of PDSCH-to-HARQ_feedback in Rel-16 |
Samsung |
| R1-2303100 |
Draft CR for default value of PDSCH-to-HARQ_feedback in Rel-17 |
Samsung |
| R1-2303101 |
Correction on HARQ-ACK codebook for SPS PDSCH receptions |
Samsung |
| R1-2303102 |
Discussion on Type-1 HARQ-ACK codebook with a new RRC parameter indicating receiving up to one PDSCH per slot |
Samsung |
| R1-2303171 |
Clarification to the switching gap location of the UL Tx Switching |
Nokia, Nokia Shanghai Bell |
| R1-2303287 |
Correction on the mapping of PDSCH-to-HARQ_feedback timing indicator field values in Rel-16 |
CATT |
| R1-2303289 |
Correction on the mapping of PDSCH-to-HARQ_feedback timing indicator field values in Rel-17 |
CATT |
| R1-2303564 |
Discussion on Type1 HARQ-ACK CB issue with more than one PDSCH per slot |
Qualcomm Incorporated |
| R1-2303664 |
Corrections on Channel Structure for 2-step RACH in Rel-16 |
NEC Corporation |
| R1-2303755 |
Power scaling of SCell PRACH for UL CA |
Ericsson |
| R1-2303756 |
Draft CR for 38.213 on correction to SCell PRACH power scaling for UL CA |
Ericsson |
| R1-2303802 |
Discussion on the multiplexing between SR/SPS A/N and CSI |
Huawei, HiSilicon |
| R1-2304023 |
Summary of [112bis-e-AI7.1-03] on PUCCH resource determination |
Moderator (CATT) |
| R1-2304024 |
Summary of [112bis-e-AI7.1-04] on DAPS handover |
Moderator (CATT) |
| R1-2304025 |
Summary of [112bis-e-AI7.1-05] on NFI definition |
Moderator (CATT) |
| R1-2304026 |
Summary of [112bis-e-AI7.1-12] on mapping of PDSCH-to-HARQ_feedback field |
Moderator (CATT) |
| R1-2304068 |
Summary for [112bis-e-AI7.1-08] NR Rel-15/16 maintenance on default value of PDSCH-to-HARQ_feedback |
Moderator (Samsung) |
| R1-2304071 |
Correction on the mapping of PDSCH-to-HARQ_feedback timing indicator field values in Rel-16 |
Moderator (CATT), Huawei, HiSilicon, ZTE, Sanechips, Ericsson |
| R1-2304072 |
Correction on the mapping of PDSCH-to-HARQ_feedback timing indicator field values in Rel-17 |
Moderator (CATT), Huawei, HiSilicon, ZTE, Sanechips, Ericsson |
| R1-2304109 |
Summary of [112bis-e-AI7.1-02] NR Rel-15/16 maintenance on CWS adjustment for channels without explicit HARQ |
Moderator (OPPO) |
| R1-2304117 |
Summary of [112bis-e-AI7.1-09] NR Rel-15/16 maintenance on HARQ-ACK codebook for SPS PDSCH receptions |
Moderator (Samsung) |
| R1-2304127 |
Clarification of HARQ-ACK transmission for the 1st SPS PDSCH |
Moderator (CATT) |
| R1-2304128 |
Clarification of HARQ-ACK transmission for the 1st SPS PDSCH |
Moderator (CATT) |
| R1-2304129 |
Clarification of HARQ-ACK transmission for the 1st SPS PDSCH |
Moderator (CATT), Samsung, Ericsson, Huawei, HiSilicon |
| R1-2304130 |
Clarification of HARQ-ACK transmission for the 1st SPS PDSCH |
Moderator (CATT), Samsung, Ericsson, Huawei, HiSilicon |
| R1-2304131 |
Correction on impact of DAPS handover in Rel-16 |
Moderator (CATT) |
| R1-2304132 |
Correction on impact of DAPS handover in Rel-17 |
Moderator (CATT) |
| R1-2304133 |
Correction on impact of DAPS handover in Rel-16 |
Moderator (CATT), Samsung, Ericsson |
| R1-2304134 |
Correction on impact of DAPS handover in Rel-17 |
Moderator (CATT), Samsung, Ericsson |
| R1-2304149 |
Summary of Email discussion on [112bis-e-AI7.1-01] |
Moderator (vivo) |
| R1-2304153 |
Summary of email discussions [112bis-e-AI7.1-10] NR Rel-15/16 maintenance on Type1 HARQ-ACK CB issue with more than one PDSCH per slot |
Moderator (Qualcomm) |
| R1-2304154 |
[Draft] LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 |
Moderator (Qualcomm) |
| R1-2304155 |
[Draft] CR on Type1 HARQ-ACK CB issue with more than one PDSCH per slot |
Moderator (Qualcomm), Samsung |
| R1-2304156 |
LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 |
RAN1, Qualcomm |
| R1-2304157 |
CR on Type1 HARQ-ACK CB issue with more than one PDSCH per slot |
Moderator (Qualcomm), Samsung |
| R1-2304179 |
Summary on email discussion [112bis-e-AI7.1-06] NR Rel-15/16 maintenance on TBS determination of a PUSCH retransmission |
Moderator (Ericsson) |
| R1-2304180 |
Clarification to the switching gap location of the UL Tx Switching |
Moderator (Nokia), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, NTT DOCOMO, Samsung, vivo |
| R1-2304181 |
Clarification to the switching gap location of the UL Tx Switching |
Moderator (Nokia), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, NTT DOCOMO, Samsung, vivo |
| R1-2304185 |
Moderator summary: Maintenance on switching gap location of UL Tx Switching (R1-2303171) |
Moderator (Nokia) |
| R1-2304186 |
Summary of [112bis-e-AI7.1-07] On indication period for RLM for DRX mode |
Moderator (xiaomi) |
| R1-2304187 |
Summary of Corrections on Channel Structure for 2-step RACH |
Moderator (NEC) |
| R1-2304188 |
Summary of Email discussion [112bis-e-AI7.1-14] |
Moderator (Ericsson) |
| R1-2304189 |
Summary of [112bis-e-AI7.1-15] NR Rel-15/16 maintenance on multiplexing between SR/SPS A/N and CSI |
Moderator (HiSilicon) |
| R1-2304228 |
CR on TBS determination of a PUSCH retransmission with initial PUSCH scheduled by RAR UL grant |
Moderator (Ericsson), Ericsson, Samsung, CATT, Huawei, HiSilicon, vivo, ZTE, MediaTek |
| R1-2304229 |
CR on TBS determination of a PUSCH retransmission with initial PUSCH scheduled by RAR UL grant |
Moderator (Ericsson), Ericsson, Samsung, CATT, Huawei, HiSilicon, vivo, ZTE, MediaTek |
| R1-2304246 |
Summary on [112bis-e-AI7.1-16] |
Moderator (Huawei) |
| 7.2 |
Maintenance on NR Release 17 |
|
| R1-2302297 |
Maintenance issues for Rel-17 NR RedCap |
Ericsson |
| R1-2302343 |
Draft CR on PDCCH validation for multicast SPS |
Huawei, HiSilicon, CBN |
| R1-2302344 |
Remaining issues for Rel-17 MBS UE features. |
Huawei, HiSilicon |
| R1-2302395 |
Correction on URLLC/IIoT functionalities of DCI formats 1_1 and 1_2 |
Nokia, Nokia Shanghai Bell |
| R1-2302425 |
Draft CR on UE capability name alignment of AP SRS without data and without CSI in TS 38.214 |
ZTE |
| R1-2302443 |
Correction on multiplexing of different PHY priorities in 38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2302456 |
Correction on mixed R16 SSSG switching and R17 PDCCH monitoring adaptation |
vivo |
| R1-2302457 |
Clarification on missing field descriptions of SCI 2-C |
vivo,CATT,GOHIGH |
| R1-2302458 |
Draft editorial CR on RRC signaling for SPS HARQ-ACK for MBS |
vivo |
| R1-2302459 |
Correction on multiplexing NACK-only, CSI and SR in a PUCCH |
vivo |
| R1-2302460 |
Discussion on overlapping of NACK-only,SR and other PUCCH/PUSCH |
vivo |
| R1-2302461 |
Draft CR on overlapping among NACK-only, SR and other PUCCH/PUSCH |
vivo |
| R1-2302462 |
Draft CR on not applying disabled HARQ-ACK to multicast SPS PDSCH activation/deactivation |
vivo |
| R1-2302463 |
Draft CR on intra-UE multiplexing for MBS |
vivo |
| R1-2302464 |
Draft CR on HARQ-ACK multiplexing on PUSCH with different priority |
vivo |
| R1-2302465 |
Correction for SDT operation the in separate initial BWP for RedCap |
vivo |
| R1-2302466 |
Discussions on the support of LBT type switching in the shared COT in FR2-2 |
vivo |
| R1-2302467 |
Correction on the LBT Type switching in the shared COT |
vivo |
| R1-2302468 |
Correction on the indication of short control signal |
vivo |
| R1-2302529 |
Discussion on remaining issue for LBT upgrade within gNB COT |
OPPO |
| R1-2302530 |
Draft CR on resolving issue for LBT upgrade within gNB COT |
OPPO |
| R1-2302531 |
Correction on the antenna switching capability indication for more than 4 Rx |
OPPO |
| R1-2302650 |
Discussion on PRACH/PUSCH/PUCCH occasion validation |
CATT |
| R1-2302651 |
Correction on collision handling between valid PRACH occasion and NCD-SSB in Rel-17 |
CATT |
| R1-2302652 |
Correction on resource exclusion behavior with non-preferred resource set |
CATT, GOHIGH,Qualcomm, vivo,Nokia, Nokia Shanghai Bell |
| R1-2302653 |
Correction on the time gap between PSFCH and corresponding SCI format 1-A |
CATT, GOHIGH |
| R1-2302654 |
Correction on HARQ-ACK multiplexing on PUSCH with different priority |
CATT |
| R1-2302655 |
Correction on the applicable subcarrier spacings of Type-3 HARQ-ACK codebook |
CATT |
| R1-2302656 |
Clarification of configurations of serving cells and HARQ processes for enhanced Type-3 HARQ-ACK codebook |
CATT |
| R1-2302657 |
Correction on UCI multiplexing with different priorities |
CATT |
| R1-2302658 |
Draft CR on the condition of not providing Type-1 HARQ-ACK codebook |
CATT, CBN |
| R1-2302659 |
Draft CR on not applying enabled/disabled HARQ-ACK feedback to multicast SPS activation/deactivation |
CATT |
| R1-2302660 |
Draft CR on PDCCH validation for multicast SPS |
CATT |
| R1-2302661 |
Draft CR on transmission power of DCI format 4_0 |
CATT, CBN |
| R1-2302662 |
Draft CR on a set of row indexes R of TDRA tables for Type-1 HARQ-ACK codebook multiplexing of unicast and multicast |
CATT |
| R1-2302663 |
Discussion on restriction for a slot timing value indicated by DCI format 1_0 when multicast is configured |
CATT, CBN |
| R1-2302664 |
Draft CR on restriction for a slot timing value indicated by DCI format 1_0 when multicast is configured |
CATT, CBN |
| R1-2302665 |
Discussion on Type-1/2/3 HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast |
CATT, CBN |
| R1-2302666 |
Draft CR on Type-1/2/3 HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast |
CATT, CBN |
| R1-2302667 |
Draft CR for Type-2 HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast |
CATT |
| R1-2302668 |
Draft CR for Type-3 HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast |
CATT |
| R1-2302669 |
Draft CR on pdsch-AggregationFactor for multicast SPS |
CATT, CBN |
| R1-2302670 |
Draft CR on editorial correction of pdsch-TimeDomainAllocationListForMultiPDSCH |
CATT |
| R1-2302671 |
Draft CR on alignment of the condition on R_Tgeneration and candidate PDSCH reception determination |
CATT |
| R1-2302672 |
Discussion on R_Tgeneration and candidate PDSCH reception determination for the features extending NR operation to 71 GHz |
CATT |
| R1-2302673 |
Discussion on 32 HARQ process in PDSCH-HARQ-ACK-EnhType3 configuration for the features extending NR operation to 71 GHz |
CATT |
| R1-2302674 |
Discussion on LBT update upon detection of DCI format 2_0 for FR2-2 |
CATT |
| R1-2302675 |
Draft CR on LBT update upon detection of DCI format 2_0 for FR2-2 |
CATT |
| R1-2302733 |
Draft CR on the power control for SRS resource set for noncodebook |
Lenovo |
| R1-2302734 |
Draft CR on UL-TCI-State configuration in TS38.214 |
Lenovo |
| R1-2302742 |
Alignment of terminology |
Ericsson LM |
| R1-2302744 |
Draft CR on editorial correction on Common TA parameters |
THALES |
| R1-2302753 |
Draft CR on editorial correction on epoch time |
THALES |
| R1-2302755 |
Remaining issues for MBS UE feature |
ZTE |
| R1-2302766 |
Draft CR on UCI multiplexing for SR and NACK-only PUCCH for MBS |
ZTE |
| R1-2302832 |
Discussion on LBT type update upon detection of DCI format 2-0 for FR2-2 |
ZTE, Sanechips |
| R1-2302833 |
Draft CR on LBT type update upon detection of DCI format 2-0 for FR2-2 in TS 37.213 |
ZTE, Sanechips |
| R1-2302888 |
Support of joint SPS multicast release |
Nokia, Nokia Shanghai Bell |
| R1-2302889 |
Draft CR on Multicast Deactivation Release |
Nokia, Nokia Shanghai Bell |
| R1-2302929 |
Moderator Summary #1 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2302930 |
Moderator Summary #2 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2302938 |
Correction on SRS transmission outside initial UL BWP |
Nokia, Nokia Shanghai Bell |
| R1-2302939 |
Discussion on SRS for positioning outside of initial BWP |
Nokia, Nokia Shanghai Bell |
| R1-2302942 |
Discussion on RedCap remaining issues |
ZTE, Sanechips |
| R1-2302957 |
Corrections on simultaneous reception during SDT procedure |
xiaomi |
| R1-2302958 |
Discussion on RedCap SDT operation |
xiaomi |
| R1-2303003 |
Draft CR 38.211: Alignment of Common TA parameter names to 38.331 |
Ericsson |
| R1-2303004 |
Correction of aperiodic SRS triggering without data and CSI |
Nokia, Nokia Shanghai Bell |
| R1-2303037 |
UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI |
Xiaomi EV Technology |
| R1-2303042 |
Draft CR on Action Delay for DCI based unified TCI Indication for NTN |
Google |
| R1-2303043 |
Discussion on Action Delay for DCI based unified TCI Indication for NTN |
Google |
| R1-2303058 |
Clarification on Preserve for periodic based partial sensing |
Sharp |
| R1-2303059 |
Clarification on candidate slots for aperiodic transmission in partial sensing |
Sharp |
| R1-2303060 |
Clarification on pre-emption for non-preferred resource set |
Sharp |
| R1-2303093 |
Discussion on LBT type upgrade within a gNB COT |
Nokia, Nokia Shanghai Bell |
| R1-2303094 |
Correction on LBT Type determination within a gNB COT |
Nokia, Nokia Shanghai Bell |
| R1-2303103 |
Correction on timer expiration for SSSG switching |
Samsung |
| R1-2303104 |
Discussion on BWP operations in FR2-2 |
Samsung |
| R1-2303105 |
Draft CR on BWP switching with CBG-based transmission in FR2-2 |
Samsung |
| R1-2303106 |
Correction on the PDSCH reception restriction when a UE supports FDMed unicast and multicast PDSCH receptions |
Samsung |
| R1-2303107 |
Correction on HARQ-ACK codebook for multicast SPS PDSCH receptions |
Samsung |
| R1-2303108 |
Discussion on PUCCH power control for multiplexing HARQ-ACK of different priorities |
Samsung |
| R1-2303109 |
Correction on Intra-UE multiplexing of HARQ-ACK of different priorities |
Samsung |
| R1-2303172 |
Maintenance of Rel-17 RedCap |
NEC |
| R1-2303210 |
Discussion on RedCap remaining issues |
CMCC |
| R1-2303211 |
Draft CR on collision handling between PRACH and NCD-SSB |
CMCC |
| R1-2303212 |
Discussion on multi-TRP operation for MBS |
CMCC |
| R1-2303213 |
Draft CR on PDCCH validation for single multicast SPS |
CMCC |
| R1-2303214 |
Draft CR on joint SPS release via multicast DCI |
CMCC |
| R1-2303215 |
Draft CR on FDMed PDSCH reception |
CMCC |
| R1-2303274 |
Draft CR for PRS reduced sample in 38.214 |
ZTE |
| R1-2303275 |
Draft CR for Positioning Measurement Gap Activation Request in 38.214 |
ZTE |
| R1-2303291 |
Correction on redundancy version for CG-SDT in TS 38.213 |
ZTE, vivo, Samsung, Intel |
| R1-2303317 |
Draft CR on HARQ-ACK feedback for multicast SPS activation/deactivation |
Lenovo |
| R1-2303318 |
Draft CR on multicast HARQ-ACK information in a Type-3 HARQ-ACK codebook |
Lenovo |
| R1-2303347 |
On UL resource validation with SSB |
MediaTek Inc. |
| R1-2303348 |
Draft CR for 38.213 on UL resource validation with SSB |
MediaTek Inc. |
| R1-2303363 |
On the relation between SUL indicator and pusch-Config/pucch-Config for DCI 0_0 |
MediaTek Inc. |
| R1-2303364 |
[R17] Draft 38.212 CR on SUL indicator and pusch-Config/pucch-Config for DCI 0_0 |
MediaTek Inc. |
| R1-2303365 |
On rate match pattern periodicity |
MediaTek Inc. |
| R1-2303366 |
Draft CR for 38.214 on rate match pattern periodicity |
MediaTek Inc. |
| R1-2303384 |
Draft CR on the parameters for multicast |
ZTE |
| R1-2303385 |
Draft CR on FDMed PDSCH reception |
ZTE |
| R1-2303386 |
Draft CR on feedback mode for SPS for MBS |
ZTE |
| R1-2303387 |
Draft CR on the generation of the Type1 HARQ-ACK codebook for MBS |
ZTE |
| R1-2303388 |
Draft CR on HARQ-ACK multiplexed in PUSCH for MBS |
ZTE |
| R1-2303389 |
Draft CR on PUCCH resource determination for MBS |
ZTE |
| R1-2303390 |
Draft CR on intra-UE multiplexing for MBS |
ZTE |
| R1-2303391 |
Draft CR on intra-UE multiplexing with NACK-only PUCCH |
ZTE |
| R1-2303392 |
Draft CR on the Type-3 codebook for MBS |
ZTE |
| R1-2303394 |
RedCap support of SDT |
Nokia, Nokia Shanghai Bell |
| R1-2303398 |
Correction on sidelink power control procedure in TS 38.213 |
ZTE, Sanechips |
| R1-2303399 |
Correction on the description of slot index in TS38.213 |
ZTE, Sanechips |
| R1-2303422 |
Draft CR on LBT type determination within a COT for FR2-2 in TS 37.213 |
LG Electronics |
| R1-2303423 |
Draft CR on multicast HARQ-ACK |
LG Electronics |
| R1-2303424 |
Draft CR on sps-ConfigDeactivationStateList |
LG Electronics |
| R1-2303515 |
Correction on default beam and configuration for HST-SFN |
Google |
| R1-2303545 |
Draft CR to 38.213 for NACK only mode 2 configuration with multiple G-RNTI |
Ericsson |
| R1-2303546 |
Draft CR to 38.213 for PTM retransmissions of SPS multicast |
Ericsson |
| R1-2303547 |
Draft CR to 38.213 for HARQ for SPS activation and release |
Ericsson |
| R1-2303548 |
Draft CR to 38.214 on DCI for enable/disable HARQ for MBS |
Ericsson |
| R1-2303549 |
Maintenance on NR Multicast and Broadcast Services |
Ericsson |
| R1-2303565 |
Clarification on A-CSI-RS triggering offset |
Qualcomm Incorporated |
| R1-2303566 |
Maintenance for channel access for FR2-2 |
Qualcomm Incorporated |
| R1-2303567 |
Clarification on CBG based Type 3 HARQ-ACK codebook including HARQ-ACK processes with different max number of CBGs |
Qualcomm Incorporated |
| R1-2303568 |
Remaining issues for Rel-17 MBS maintenance |
Qualcomm Incorporated |
| R1-2303569 |
Draft CR on feedback for multicast SPS release |
Qualcomm Incorporated |
| R1-2303570 |
Draft CR on feedback for first PDSCH after multicast SPS activation |
Qualcomm Incorporated |
| R1-2303571 |
Draft CR for MBS without mTRP |
Qualcomm Incorporated |
| R1-2303572 |
Discussion on Rel-17 UE features |
Qualcomm Incorporated |
| R1-2303631 |
Correction on multicast second HARQ-ACK reporting mode |
MediaTek Inc. |
| R1-2303632 |
Correction on multicast SPS PDCCH validation |
MediaTek Inc. |
| R1-2303633 |
Correction on PUCCH resource determination for multiplexing multicast first and second HARQ-ACK reporting mode |
MediaTek Inc. |
| R1-2303634 |
Correction on PUCCH resource determination for multiplexing unicast and multicast HARQ-ACK |
MediaTek Inc. |
| R1-2303635 |
Correction on PUCCH resource determination for NACK-only mode 1 with one bit HARQ-ACK |
MediaTek Inc. |
| R1-2303636 |
Correction on PUCCH resource determination for the multicast first HARQ-ACK reporting mode |
MediaTek Inc. |
| R1-2303637 |
Correction on HARQ-ACK for multicast SPS |
MediaTek Inc. |
| R1-2303688 |
Correction on n1PUCCH-AN for multicast HARQ-ACK multiplexing case |
MediaTek Inc. |
| R1-2303690 |
Discussion on remaining issues for RedCap UE |
NTT DOCOMO, INC. |
| R1-2303691 |
Discussion on value range mismatch of p0 for SRS/PUCCH in Rel-17 unified TCI framework |
NTT DOCOMO, INC. |
| R1-2303692 |
Draft CR on value range mismatch of p0 for PUCCH in Rel-17 unified TCI framework |
NTT DOCOMO, INC. |
| R1-2303693 |
Discussion on remaining issues for joint channel estimation |
NTT DOCOMO, INC. |
| R1-2303694 |
Draft CR on half-duplex consideration for SL re-evaluation/pre-emption check |
NTT DOCOMO, INC. |
| R1-2303695 |
Draft CR to support NACK-only feedback with multiple G-RNTIs |
NTT DOCOMO, INC. |
| R1-2303696 |
Draft CR on HARQ feedback for the initial SPS PDSCH |
NTT DOCOMO, INC. |
| R1-2303792 |
Remaining issues for Rel-17 MBS |
Huawei, HiSilicon, CBN |
| R1-2303793 |
Draft CR on disabling HARQ-ACK for multicast SPS |
Huawei, HiSilicon, CBN |
| R1-2303794 |
Corrections to timeline for CSI feedback in TS38.214 |
Huawei, HiSilicon |
| R1-2303795 |
Corrections to spatial domain filter determination for directional LBT in TS38.214 |
Huawei, HiSilicon |
| R1-2303796 |
Corrections to UL LBT Type 1 upgrade within gNB COT in TS37.213 |
Huawei, HiSilicon |
| R1-2303797 |
Correction on description of random resource selection in TS 38.214 |
Huawei, HiSilicon |
| R1-2303798 |
Correction on UE-A is the destination UE of a TB transmitted by UE-B in TS 38.214 |
Huawei, HiSilicon |
| R1-2303801 |
Draft CR on Type-1 HARQ-ACK codebook for multicast |
Huawei, HiSilicon, CBN |
| R1-2303811 |
Correction on Rel-17 PDCCH skipping |
ZTE, Sanechips |
| R1-2303816 |
Discussion on TBoMS regarding multi-PUSCH |
ASUSTeK |
| R1-2303817 |
Discussion on MBS SPS activation |
ASUSTeK |
| R1-2303824 |
Corrections on IUC parameter for determing preferred resource set in TS38.214 |
Sharp |
| R1-2303829 |
Draft CR on channel access procedure upon detection of a common DCI for FR2-2 |
WILUS Inc. |
| R1-2303843 |
Corrections on RRC parameter name for DMRS bundling in TS38.213 |
Sharp |
| R1-2303844 |
Corrections on RRC parameter name for DMRS bundling in TS38.214 |
Sharp |
| R1-2303852 |
Correction on adding PUCCH-sSCell for the BWP operation |
Huawei, HiSilicon |
| R1-2303854 |
Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 |
Huawei, HiSilicon |
| R1-2303868 |
Correction on availability indication in eIAB |
Ericsson |
| R1-2303869 |
Discussion on reference SCS for availability indication in eIAB |
Ericsson |
| R1-2303870 |
Correction on reference SCS for availability indication in eIAB |
Ericsson |
| R1-2303871 |
Correction on RRC parameters in eIAB |
Ericsson |
| R1-2303876 |
Draft CR on HARQ-ACK for SPS release |
Huawei, HiSilicon |
| R1-2303877 |
Draft CR on PUCCH resource for multicast SPS |
Huawei, HiSilicon |
| R1-2303878 |
Draft CR on joint release for multicast SPS |
Huawei, HiSilicon |
| R1-2303879 |
Draft CR on FDM multiplexing unicast and multicast |
Huawei, HiSilicon |
| R1-2303880 |
Draft CR on PUCCH resources for multicast HARQ-ACK |
Huawei, HiSilicon |
| R1-2303887 |
FL Summary for Rel-17 Maintenance on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2303928 |
FL summary #1 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2303929 |
FL summary #2 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2303930 |
FL summary #3 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2303931 |
FL summary #4 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2303932 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2303939 |
FL summary of Rel-17 FR2-2 maintenance (RS and timeline) |
Moderator (vivo) |
| R1-2303948 |
Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2303949 |
Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2303977 |
Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 0) |
Moderator (Intel Corporation) |
| R1-2303987 |
Summary#1 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2304027 |
Moderator summary #1 on Maintenance of Rel-17 URLLC & IIoT maintenance (intra-UE multiplexing) |
Moderator (CATT) |
| R1-2304037 |
Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| R1-2304058 |
Summary of [112bis-e-R17-Others-01] Email discussion on other Rel-17 maintenance |
Moderator (MediaTek Inc.) |
| R1-2304059 |
Moderator Summary#0 of Maintenance on Rel-17 SRS |
Moderator (ZTE) |
| R1-2304061 |
Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2304062 |
Corrections to timeline for CSI feedback in TS38.214 |
Moderator (vivo), Huawei, HiSilicon |
| R1-2304063 |
Moderator Summary #3 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2304064 |
Moderator Summary #4 for AI 7.2: Maintenance on NR Sidelink enhancement |
Moderator (LG Electronics) |
| R1-2304078 |
FL Summary #2: Rel-17 NR NTN maintenance |
Moderator (Thales) |
| R1-2304079 |
Moderator summary of [112bis-e-R17-URLLC-01] Rel-17 URLLC & IIoT maintenance (HARQ-ACK) |
Moderator (Nokia) |
| R1-2304080 |
Corrections on Type 3 HARQ-ACK codebook |
Moderator (Nokia), CATT, Qualcomm |
| R1-2304084 |
FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2304085 |
FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2304086 |
Draft CR on condition for not providing Type-1 CB |
Moderator (Huawei) |
| R1-2304087 |
Draft CR on Type-1 HARQ-ACK codebook for multicast |
Moderator (Huawei) |
| R1-2304088 |
Draft CR on referred PUCCH resources for multiplexing HARQ-ACK |
Moderator (Huawei) |
| R1-2304089 |
Draft CR on HARQ-ACK for SPS release |
Moderator (Huawei) |
| R1-2304096 |
Draft CR on enhanced type-3 HARQ-ACK codebook |
Moderator (LG Electronics), CATT |
| R1-2304097 |
CR on enhanced type-3 HARQ-ACK codebook |
Moderator (LG Electronics), CATT |
| R1-2304098 |
DRAFT LS to RAN2 on scheduling and HARQ issues for FR2-2 |
Moderator (LG Electronics) |
| R1-2304099 |
LS to RAN2 on scheduling and HARQ issues for FR2-2 |
RAN1, LG Electronics |
| R1-2304107 |
Draft CR on FDMed PDSCH reception |
Moderator (CMCC), Huawei, HiSilicon, Samsung, ZTE |
| R1-2304111 |
Moderator Summary #0 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2304112 |
Corrections on Type-3 HARQ-ACK codebook |
Moderator (Nokia), CATT, Qualcomm, Samsung |
| R1-2304113 |
Updated RAN1 UE features list for Rel-17 NR after RAN1 #112bis-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2304114 |
Draft LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112bis-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2304115 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112bis-e |
RAN1, (AT&T, NTT DOCOMO, INC.) |
| R1-2304116 |
Clarification for half-duplex consideration in partial sensing based re-evaluation/pre-emption checking |
Moderator (LG Electronics) |
| R1-2304124 |
Correction on default beam and configuration for HST-SFN |
Moderator (Intel Corporation) |
| R1-2304136 |
[112bis-e-R17-CovEnh-01] FL summary of maintenance issues for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2304138 |
CR on antenna switching capability indication for more than 4 Rx antenna |
Moderator (ZTE), OPPO, Samsung |
| R1-2304139 |
Moderator Summary#1 of Maintenance on Rel-17 SRS |
Moderator (ZTE) |
| R1-2304142 |
Correction on redundancy version for CG-SDT in TS 38.213 |
Moderator (ZTE), vivo, Samsung, Intel, New H3C, xiaomi |
| R1-2304143 |
Draft CR on value range mismatch of p0 for SRS in Rel-17 unified TCI framework |
Moderator (ZTE), NTT DOCOMO, INC., Ericsson, ZTE |
| R1-2304158 |
Summary on Rel-17 SDT |
Moderator (ZTE) |
| R1-2304159 |
Session notes for 7.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) |
Ad-Hoc Chair (Huawei) |
| R1-2304160 |
Session notes for 7.2 (Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC) |
Ad-hoc Chair (CMCC) |
| R1-2304161 |
Session notes for 7.2 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) |
Ad-Hoc Chair (Huawei) |
| R1-2304162 |
Session notes for 7.2 (Maintenance on NR Positioning Enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2304163 |
Session notes for 7.2 (Maintenance on Support of Reduced Capability NR Devices) |
Ad-hoc Chair (CMCC) |
| R1-2304164 |
Session notes for 7.2 (Maintenance on UE Power Saving Enhancements) |
Ad-hoc Chair (CMCC) |
| R1-2304165 |
Session notes for 7.2 (NR coverage enhancement) |
Ad-hoc Chair (CMCC) |
| R1-2304166 |
Session notes for 7.2 (Maintenance on NR Sidelink enhancement) |
Ad-Hoc Chair (Huawei) |
| R1-2304167 |
Session notes for 7.2 (Maintenance on NR Multicast and Broadcast Services) |
Ad-Hoc Chair (Huawei) |
| R1-2304184 |
Draft CR on SPS release via multicast DCI |
Moderator (CMCC) |
| R1-2304198 |
Correction on the indication of short control signal |
Moderator (Nokia), vivo, NTT DOCOMO, INC., Huawei, HiSilicon, ZTE, Sanechips |
| R1-2304199 |
Corrections to spatial domain filter determination for directional LBT in TS38.214 |
Moderator (Nokia), Huawei, HiSilicon, NTT DOCOMO, INC. |
| R1-2304200 |
Summary of [112bis-e-R17-FR2_2-02] Email discussion on Rel-17 FR2_2 maintenance for other channel access mechanism issues |
Moderator (Nokia) |
| R1-2304208 |
Draft CR on the HARQ-ACK CB for multicast SPS repetition |
Moderator (Huawei) |
| R1-2304209 |
Draft CR on Type-1 HARQ-ACK CB on PUSCH |
Moderator (Huawei) |
| R1-2304230 |
CR on value range mismatch of p0 for SRS in Rel-17 unified TCI framework |
Moderator (ZTE), NTT DOCOMO, INC., Ericsson, ZTE, Samsung |
| R1-2304231 |
Clarification for half-duplex consideration in partial sensing based re-evaluation/pre-emption checking |
Moderator (LG Electronics), NTT DOCOMO, vivo |
| R1-2304232 |
Correction on default beam and configuration for HST-SFN |
Moderator (Intel Corporation), Google, Samsung |
| R1-2304236 |
CR on SFN configuration for HST-SFN |
Moderator (Intel Corporation) |
| R1-2304237 |
Draft CR on SFN configuration for HST-SFN |
Moderator (Intel Corporation) |
| R1-2304254 |
Correction on RRC parameters in eIAB |
Moderator (Qualcomm), Ericsson, Samsung |
| R1-2304255 |
Correction on SFN configuration for HST-SFN |
Moderator (Intel Corporation), Google, Samsung, Ericsson, ZTE |
| R1-2304256 |
Correction on reference SCS for availability indication in eIAB |
Moderator (Qualcomm), Ericsson, Samsung |
| R1-2304259 |
Summary for maintenance on UE power saving enhancements |
Moderator (MediaTek) |
| R1-2304260 |
Summary #1 of [112bis-e-R17-IAB-01] |
Moderator (Qualcomm) |
| R1-2304267 |
Clarifications of CG/RA-SDT operation for RedCap Ues |
Moderator (Ericsson) |
| R1-2304268 |
Clarification of RA-SDT operation for RedCap UEs in TDD |
Moderator (Ericsson) |
| R1-2304271 |
CR on condition for not providing Type-1 CB |
Moderator (Huawei), CATT, Samsung |
| R1-2304272 |
CR on Type-1 HARQ-ACK codebook for multicast |
Moderator (Huawei), CATT |
| R1-2304273 |
CR on HARQ-ACK for SPS release |
Moderator (Huawei), Qualcomm, Samsung, Lenovo, vivo, MediaTek |
| R1-2304280 |
CR on SPS release via multicast DCI |
Moderator (CMCC) |
| R1-2304281 |
Clarification of RA-SDT operation for RedCap UEs in TDD |
Moderator (Ericsson), vivo, xiaomi, Qualcomm, Ericsson |
| R1-2304283 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| R1-2304285 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2304286 |
Email discussion on issue CA-1 of channel access of Rel.17 FR2-2 |
Moderator (Qualcomm) |
| R1-2304289 |
Alignment of parameter names |
Ericsson |
| R1-2304290 |
Correction on contention window adjustments |
Ericsson |
| 9.1.1.1 |
Unified TCI framework extension for multi-TRP |
|
| R1-2302299 |
Unified TCI Enhancements for MTRP |
InterDigital, Inc. |
| R1-2302311 |
Unified TCI framework extension for multi-TRP |
FUTUREWEI |
| R1-2302370 |
Discussion on unified TCI framework extension for multi-TRP |
Huawei, HiSilicon |
| R1-2302396 |
Unified TCI framework extension for multi-TRP |
Panasonic |
| R1-2302411 |
Unified TCI framework extension for multi-TRP |
Ericsson |
| R1-2302416 |
Enhancements on unified TCI framework extension for multi-TRP |
ZTE |
| R1-2302469 |
Further discussion on unified TCI framework extension for multi-TRP |
vivo |
| R1-2302532 |
Unified TCI framework extension for multi-TRP |
OPPO |
| R1-2302585 |
Discussion on unified TCI framework extension for multi-TRP |
Spreadtrum Communications |
| R1-2302635 |
Multi-TRP enhancements for the unified TCI framework |
Fraunhofer IIS |
| R1-2302680 |
Further discussion on unified TCI framework extension for multi-TRP operation |
CATT |
| R1-2302723 |
Discussion of unified TCI framework for multi-TRP |
Lenovo |
| R1-2302780 |
Unified TCI Framework for Multi-TRP |
Intel Corporation |
| R1-2302900 |
Discussion on unified TCI framework extension for multi-TRP |
Fujitsu |
| R1-2302959 |
Unified TCI framework extension for multi-TRP |
xiaomi |
| R1-2303005 |
Unified TCI framework extension for multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2303068 |
Unified TCI framework extension for multi-TRP/panel |
LG Electronics |
| R1-2303110 |
Views on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2303178 |
Unified TCI framework extension for multi-TRP |
Sharp |
| R1-2303216 |
Discussion on unified TCI framework extension for multi-TRP |
CMCC |
| R1-2303300 |
Discussion on Unified TCI framework extension for multi-TRP |
CEWiT |
| R1-2303359 |
Unified TCI framework extension for multi-TRP |
MediaTek Inc. |
| R1-2303372 |
Discussion on unified TCI framework extension for multi-TRP |
Transsion Holdings |
| R1-2303393 |
Discussion on unified TCI framework extension for multi-TRP operation |
TCL Communication Ltd. |
| R1-2303405 |
Discussion on unified TCI framework extension for multi-TRP |
FGI |
| R1-2303467 |
Unified TCI framework extension for multi-TRP |
Apple |
| R1-2303516 |
Discussion on unified TCI framework extension for multi-TRP |
Google |
| R1-2303573 |
Extension of unified TCI framework for mTRP |
Qualcomm Incorporated |
| R1-2303665 |
Discussion on unified TCI framework extension for multi-TRP |
NEC |
| R1-2303697 |
Discussion on unified TCI framework extension for multi-TRP |
NTT DOCOMO, INC. |
| R1-2303778 |
Discussion on unified TCI framework extension for multi-TRP |
ITRI |
| R1-2303805 |
Discussion on unified TCI framework extension for M-TRP operation |
Hyundai Motor Company |
| R1-2303806 |
Summary of pre-meeting offline discussion on extension of unified TCI framework |
Moderator (MediaTek Inc.) |
| R1-2303807 |
Moderator summary on extension of unified TCI framework (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2303812 |
Moderator summary on extension of unified TCI framework (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2303814 |
Moderator summary on extension of unified TCI framework (Round 2) |
Moderator (MediaTek Inc.) |
| R1-2304235 |
Moderator summary on extension of unified TCI framework (Final) |
Moderator (MediaTek Inc.) |
| 9.1.1.2 |
Two TAs for multi-DCI |
|
| R1-2302300 |
Enhanced mTRP Operation with Multiple TA |
InterDigital, Inc. |
| R1-2302312 |
Enhancements to support two TAs for multi-DCI |
FUTUREWEI |
| R1-2302371 |
Study on TA enhancement for UL M-TRP transmssion |
Huawei, HiSilicon |
| R1-2302412 |
Two TAs for multi-DCI |
Ericsson |
| R1-2302417 |
TA enhancement for multi-DCI |
ZTE |
| R1-2302470 |
Further discussion on two TAs for multi-DCI-based multi-TRP operation |
vivo |
| R1-2302533 |
Two TAs for multi-DCI based multi-TRP operation |
OPPO |
| R1-2302586 |
Discussion on two TAs for multi-DCI based multi-TRP |
Spreadtrum Communications |
| R1-2302681 |
Discussion on two TAs for UL multi-DCI for multi-TRP operation |
CATT |
| R1-2302724 |
Discussion of two TAs for multi-DCI UL transmission |
Lenovo |
| R1-2302781 |
On two TAs for multi-DCI |
Intel Corporation |
| R1-2302960 |
Discussion on two TAs for multi-TRP operation |
xiaomi |
| R1-2303006 |
Two TAs for UL multi-DCI multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2303040 |
Discussion on two TAs for multi-DCI based on multi-TRP operation |
TCL Communication Ltd. |
| R1-2303069 |
Two TAs for multi-TRP/panel |
LG Electronics |
| R1-2303111 |
Views on two TAs for m-DCI |
Samsung |
| R1-2303179 |
Two TAs for multi-DCI |
Sharp |
| R1-2303217 |
Discussion on two TAs for multi-DCI |
CMCC |
| R1-2303360 |
UL Tx Timing Management for MTRP Operation |
MediaTek Inc. |
| R1-2303373 |
Discussion on two TAs for multi-DCI based multi-TRP operation |
Transsion Holdings |
| R1-2303468 |
Views on two TAs for multi-DCI Uplink Transmissions |
Apple |
| R1-2303517 |
Discussion on two TAs for multi-DCI |
Google |
| R1-2303574 |
Supporting two TAs for multi-DCI based mTRP |
Qualcomm Incorporated |
| R1-2303666 |
Discussion on two TAs for multi-DCI |
NEC |
| R1-2303698 |
Discussion on two TAs for multi-DCI |
NTT DOCOMO, INC. |
| R1-2304055 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| 9.1.2 |
CSI enhancement |
|
| R1-2302301 |
Further Details on CSI for CJT and Medium/High UE Velocities |
InterDigital, Inc. |
| R1-2302372 |
CSI enhancement for coherent JT and mobility |
Huawei, HiSilicon |
| R1-2302418 |
CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2302471 |
Further discussion on CSI enhancement for high-medium UE velocities and coherent JT |
vivo |
| R1-2302534 |
CSI enhancement for high/medium UE velocities and coherent JT |
OPPO |
| R1-2302587 |
Discussion on CSI enhancement for high/medium UE velocities and coherent JT |
Spreadtrum Communications |
| R1-2302636 |
CSI enhancements for medium UE velocities and coherent JT |
Fraunhofer IIS |
| R1-2302682 |
Discussion on CSI enhancement for high/medium UE velocities and coherent JT |
CATT |
| R1-2302725 |
Discussion of CSI enhancement for high speed UE and coherent JT |
Lenovo |
| R1-2302782 |
On CSI enhancements |
Intel Corporation |
| R1-2302839 |
Views on CSI enhancement for high/medium UE velocities and CJT |
Sony |
| R1-2302901 |
Discussion on Rel-18 MIMO CSI enhancement |
Fujitsu |
| R1-2302961 |
CSI enhancement for high/medium UE velocities and CJT |
Xiaomi |
| R1-2303007 |
CSI enhancement for high/medium UE velocities and CJT |
Nokia, Nokia Shanghai Bell |
| R1-2303044 |
On CSI Enhancement |
Google |
| R1-2303070 |
Potential CSI enhancement for high/medium UE velocities and coherent JT |
LG Electronics |
| R1-2303084 |
Discussion on CSI enhancement |
Mavenir |
| R1-2303112 |
Moderator summary on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2303113 |
Summary of OFFLINE discussion on Rel-18 MIMO CSI |
Moderator (Samsung) |
| R1-2303114 |
Views on CSI enhancements |
Samsung |
| R1-2303191 |
CSI enhancement |
Sharp |
| R1-2303218 |
Discussion on CSI enhancement for high/medium UE velocities and CJT |
CMCC |
| R1-2303328 |
CSI Enhancements |
MediaTek Inc. |
| R1-2303469 |
Views on Rel-18 MIMO CSI enhancement |
Apple |
| R1-2303575 |
CSI enhancements for medium UE velocities and Coherent-JT |
Qualcomm Incorporated |
| R1-2303650 |
Views on CSI Enhancements for CJT |
AT&T |
| R1-2303677 |
Discussion on CSI enhancement |
NEC |
| R1-2303699 |
Discussion on CSI enhancement |
NTT DOCOMO, INC. |
| R1-2303783 |
On CSI enhancements for Rel-18 NR MIMO evolution |
Ericsson |
| R1-2303893 |
CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2303901 |
Views on CSI enhancements |
Samsung |
| R1-2304022 |
Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 |
Moderator (Samsung) |
| R1-2304065 |
Moderator Summary#3 on Rel-18 CSI enhancements: Round 2 |
Moderator (Samsung) |
| R1-2304066 |
Views on CSI enhancements |
Samsung |
| R1-2304122 |
Moderator Summary#4 on Rel-18 CSI enhancements: Round 3 |
Moderator (Samsung) |
| 9.1.3.1 |
Increased number of orthogonal DMRS ports |
|
| R1-2302302 |
Remaining Details on DMRS Enhancements |
InterDigital, Inc. |
| R1-2302313 |
On increasing the number of orthogonal DM-RS ports for MU-MIMO |
FUTUREWEI |
| R1-2302373 |
Discussion on DMRS enhancements in Rel-18 |
Huawei, HiSilicon |
| R1-2302419 |
DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO |
ZTE, China Telecom |
| R1-2302428 |
Discussions on increased number of orthogonal DMRS ports |
New H3C Technologies Co., Ltd. |
| R1-2302472 |
Further discussion on DMRS enhancements |
vivo |
| R1-2302535 |
DMRS enhancement for Rel-18 MIMO |
OPPO |
| R1-2302588 |
Discussion on increased number of orthogonal DMRS ports |
Spreadtrum Communications |
| R1-2302634 |
On increased number of orthogonal DMRS ports |
Fraunhofer IIS |
| R1-2302683 |
DMRS enhancements in Rel-18 |
CATT |
| R1-2302726 |
Discussion of increased number of orthogonal DMRS ports |
Lenovo |
| R1-2302767 |
On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO |
Ericsson |
| R1-2302783 |
DMRS Enhancements for Rel-18 NR |
Intel Corporation |
| R1-2302962 |
Discussion on DMRS enhancement |
Xiaomi |
| R1-2303008 |
Rel-18 UL and DL DMRS Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303045 |
On DMRS Enhancement |
Google |
| R1-2303071 |
Increased number of orthogonal DMRS ports |
LG Electronics |
| R1-2303115 |
Views on DMRS enhancements |
Samsung |
| R1-2303180 |
Increased number of orthogonal DMRS ports |
Sharp |
| R1-2303219 |
Discussion on increased number of orthogonal DMRS ports |
CMCC |
| R1-2303329 |
Increased number of orthogonal DMRS ports |
MediaTek Inc. |
| R1-2303470 |
Views on supporting increased number of orthogonal DMRS ports |
Apple |
| R1-2303576 |
Design for increased number of orthogonal DMRS ports |
Qualcomm Incorporated |
| R1-2303678 |
Discussion on increased number of orthogonal DMRS ports |
NEC |
| R1-2303700 |
Discussion on DMRS enhancements |
NTT DOCOMO, INC. |
| R1-2303884 |
FL summary#1 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2303885 |
FL summary#2 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2303886 |
FL summary#3 on DMRS |
Moderator (NTT DOCOMO) |
| 9.1.3.2 |
SRS enhancement targeting TDD CJT and 8 TX operation |
|
| R1-2302303 |
Enhancements on SRS for CJT and 8TX UEs |
InterDigital, Inc. |
| R1-2302314 |
SRS enhancements for TDD CJT and 8TX operation |
FUTUREWEI |
| R1-2302374 |
Discussion on SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 |
Huawei, HiSilicon |
| R1-2302420 |
SRS enhancement targeting TDD CJT and 8 TX operation |
ZTE |
| R1-2302473 |
Further discussion on SRS enhancements |
vivo |
| R1-2302536 |
SRS enhancement targeting TDD CJT and 8 TX operation |
OPPO |
| R1-2302580 |
Discussions on SRS enhancement in Rel-18 |
New H3C Technologies Co., Ltd. |
| R1-2302589 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
Spreadtrum Communications |
| R1-2302684 |
Discussion on Rel-18 SRS enhancement |
CATT |
| R1-2302727 |
Discussion of SRS enhancement |
Lenovo |
| R1-2302776 |
On SRS enhancements targeting TDD CJT and 8 TX operation |
Oy LM Ericsson AB |
| R1-2302784 |
Discussion on SRS enhancement in Rel-18 |
Intel Corporation |
| R1-2302963 |
Discussion on SRS enhancements |
Xiaomi |
| R1-2303009 |
SRS enhancement for TDD CJT and 8Tx operation |
Nokia, Nokia Shanghai Bell |
| R1-2303046 |
On SRS Enhancement |
Google |
| R1-2303072 |
SRS enhancement targeting TDD CJT and 8 TX operation |
LG Electronics |
| R1-2303116 |
Views on SRS enhancements |
Samsung |
| R1-2303170 |
Views on SRS enhancement targeting TDD CJT and 8 TX operation |
KDDI Corporation |
| R1-2303181 |
SRS enhancement targeting TDD CJT and 8 TX operation |
Sharp |
| R1-2303192 |
Discussion on SRS enhancement targeting TDD CJT |
ETRI |
| R1-2303220 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
CMCC |
| R1-2303471 |
Views on Rel-18 MIMO SRS enhancement |
Apple |
| R1-2303577 |
SRS enhancement for TDD CJT and 8 Tx operation |
Qualcomm Incorporated |
| R1-2303679 |
Discussion on SRS enhancement |
NEC |
| R1-2303701 |
Discussion on SRS enhancement |
NTT DOCOMO, INC. |
| R1-2304010 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2304011 |
FL Summary #2 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2304012 |
FL Summary #3 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2304013 |
FL Summary #4 on SRS enhancements |
Moderator (FUTUREWEI) |
| 9.1.4.1 |
UL precoding indication for multi-panel transmission |
|
| R1-2302304 |
Discussion on Multi-panel Uplink Transmission |
InterDigital, Inc. |
| R1-2302375 |
Discussion on UL precoding indication for multi-panel transmission |
Huawei, HiSilicon |
| R1-2302397 |
UL Precoding for Multi-panel Transmission |
Panasonic |
| R1-2302421 |
Enhancements on UL precoding indication for multi-panel transmission |
ZTE |
| R1-2302474 |
Further discussion on UL precoding indication for multi-panel transmission |
vivo |
| R1-2302537 |
Discussion on UL precoding indication for multi-panel transmission |
OPPO |
| R1-2302590 |
Discussion on UL precoding indication for multi-panel transmission |
Spreadtrum Communications |
| R1-2302685 |
Further discussion on enhancements on UL precoding indication for multi-panel transmission |
CATT |
| R1-2302728 |
UL precoding indication for multi-panel transmission |
Lenovo |
| R1-2302775 |
UL precoding indication for multi-panel transmission |
Oy LM Ericsson AB |
| R1-2302785 |
UL precoding indication for multi-panel transmission |
Intel Corporation |
| R1-2302902 |
Discussion on UL precoding indication for multi-panel transmission |
Fujitsu |
| R1-2302964 |
Enhancements on multi-panel uplink transmission |
Xiaomi |
| R1-2303010 |
Precoder Indication for Multi-Panel UL Transmission |
Nokia, Nokia Shanghai Bell |
| R1-2303047 |
On Simultaneous Multi-Panel Transmission |
Google |
| R1-2303066 |
Views on UL multi-panel transmission |
Sharp |
| R1-2303073 |
UL precoding indication for multi-panel transmission |
LG Electronics |
| R1-2303117 |
Views on UL precoding indication for STxMP |
Samsung |
| R1-2303221 |
Discussion on UL precoding indication for multi-panel transmission |
CMCC |
| R1-2303361 |
Simultaneous transmission across multiple UE panels |
MediaTek Inc. |
| R1-2303406 |
Discussion on simultaneous transmission on multiple panels |
FGI |
| R1-2303472 |
Views on UL precoding indication for multi-panel simultaneous PUSCH transmissions |
Apple |
| R1-2303578 |
Simultaneous multi-panel transmission |
Qualcomm Incorporated |
| R1-2303667 |
Discussion on UL precoding indication for multi-panel transmission |
NEC |
| R1-2303702 |
Discussion on multi-panel transmission |
NTT DOCOMO, INC. |
| R1-2303818 |
Discussion on UCI multiplexing regarding STxMP |
ASUSTeK |
| R1-2303906 |
Summary #1 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2303907 |
Summary #2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2303908 |
Summary #3 on Rel-18 STxMP |
Moderator (OPPO) |
| 9.1.4.2 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
|
| R1-2302305 |
Further Discussion on 8TX UE Operations |
InterDigital, Inc. |
| R1-2302306 |
FL Summary SRI/TPMI Enhancements; Preparatory |
Moderator (InterDigital, Inc.) |
| R1-2302307 |
FL Summary SRI/TPMI Enhancements; First Round |
Moderator (InterDigital, Inc.) |
| R1-2302308 |
FL Summary SRI/TPMI Enhancements; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2302309 |
FL Summary SRI/TPMI Enhancements; Third Round |
Moderator (InterDigital, Inc.) |
| R1-2302310 |
Recommended Direction on SRITPMI Enhancements for RAN1#113 |
Moderator (InterDigital, Inc.) |
| R1-2302376 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Huawei, HiSilicon |
| R1-2302422 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
ZTE |
| R1-2302475 |
Further discussion on enabling 8 TX UL transmission |
vivo |
| R1-2302538 |
SRI TPMI enhancement for 8 TX UL transmission |
OPPO |
| R1-2302591 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Spreadtrum Communications |
| R1-2302686 |
Discussion on SRI/TPMI enhancement for 8TX UL transmission |
CATT |
| R1-2302729 |
SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| R1-2302786 |
Discussion on enhancement for 8Tx UL transmission |
Intel Corporation |
| R1-2302840 |
Considerations on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Sony |
| R1-2302965 |
Enhancements on 8Tx uplink transmission |
Xiaomi |
| R1-2303011 |
UL enhancements for enabling 8Tx UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2303048 |
On SRI/TPMI Indication for 8Tx Transmission |
Google |
| R1-2303067 |
Views on 8 TX UL transmission |
Sharp |
| R1-2303074 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
LG Electronics |
| R1-2303118 |
Views on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2303222 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
CMCC |
| R1-2303330 |
SRI/TPMI enhancement for enabling 8 Tx UL transmission |
MediaTek Inc. |
| R1-2303407 |
Discussion on SRI/TPMI Enhancements for 8 TX UL Transmission |
FGI |
| R1-2303420 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
KDDI Corporation |
| R1-2303473 |
Views on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Apple |
| R1-2303579 |
Enhancements for 8 Tx UL transmissions |
Qualcomm Incorporated |
| R1-2303660 |
SRI/TPMI Enhancement for Enabling 8 TX UL Transmission |
Ericsson |
| R1-2303680 |
Discussion on SRI/TPMI enhancement |
NEC |
| R1-2303703 |
Discussion on 8 TX UL transmission |
NTT DOCOMO, INC. |
| R1-2303891 |
Further discussion on enabling 8 TX UL transmission |
vivo |
| R1-2303902 |
Views on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2303954 |
SRI/TPMI Enhancement for Enabling 8 TX UL Transmission |
Ericsson |
| 9.2 |
Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface |
|
| R1-2303580 |
Technical report for Rel-18 SI on AI and ML for NR air interface |
Qualcomm Incorporated |
| R1-2304148 |
TR38.843 v0.1.0: Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface |
Rapporteur (Qualcomm) |
| R1-2304168 |
Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) |
Ad-hoc Chair (CMCC) |
| 9.2.1 |
General aspects of AI/ML framework |
|
| R1-2302318 |
Discussion on common AI/ML characteristics and operations |
FUTUREWEI |
| R1-2302357 |
Discussion on general aspects of AI/ML framework |
Huawei, HiSilicon |
| R1-2302436 |
Discussion on general aspects of common AI PHY framework |
ZTE |
| R1-2302476 |
Discussions on AI/ML framework |
vivo |
| R1-2302539 |
On general aspects of AI/ML framework |
OPPO |
| R1-2302592 |
Discussion on general aspects of AIML framework |
Spreadtrum Communications |
| R1-2302627 |
Further discussion on the general aspects of ML for Air-interface |
Nokia, Nokia Shanghai Bell |
| R1-2302694 |
Discussion on AI/ML framework for NR air interface |
CATT |
| R1-2302789 |
General aspects of AI/ML framework for NR air interface |
Intel Corporation |
| R1-2302821 |
Discussion on general aspects of AI/ML framework |
InterDigital, Inc. |
| R1-2302841 |
Considerations on common AI/ML framework |
Sony |
| R1-2302877 |
Discussion on general aspects of AIML framework |
Ericsson |
| R1-2302903 |
Discussion on general aspects of AI/ML framework |
Fujitsu |
| R1-2302974 |
Views on the general aspects of AI/ML framework |
xiaomi |
| R1-2303041 |
Discussion on general aspects of AI/ML framework |
Panasonic |
| R1-2303049 |
On General Aspects of AI/ML Framework |
Google |
| R1-2303075 |
General aspects on AI/ML framework |
LG Electronics |
| R1-2303119 |
General aspects of AI ML framework and evaluation methodogy |
Samsung |
| R1-2303182 |
Considerations on general aspects on AI-ML framework |
CAICT |
| R1-2303193 |
Discussion on general aspects of AI/ML framework for NR air interface |
ETRI |
| R1-2303223 |
Discussion on general aspects of AI/ML framework |
CMCC |
| R1-2303335 |
Discussion on general aspects of AI/ML LCM |
MediaTek Inc. |
| R1-2303412 |
General aspects of AI/ML framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303434 |
General aspects of AI and ML framework for NR air interface |
NVIDIA |
| R1-2303474 |
Discussion on general aspect of AI/ML framework |
Apple |
| R1-2303523 |
General aspects of AI/ML framework |
Lenovo |
| R1-2303581 |
General aspects of AI/ML framework |
Qualcomm Incorporated |
| R1-2303630 |
Discussion on general aspects of AI/ML framework |
KDDI Corporation |
| R1-2303648 |
Discussion on AI/ML framework |
Rakuten Mobile, Inc |
| R1-2303649 |
General Aspects of AI/ML framework |
AT&T |
| R1-2303668 |
Discussion on general aspects of AI ML framework |
NEC |
| R1-2303704 |
Discussion on general aspects of AI/ML framework |
NTT DOCOMO, INC. |
| R1-2303809 |
Discussions on Common Aspects of AI/ML Framework |
TCL Communication Ltd. |
| R1-2304049 |
Summary#1 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2304050 |
Summary#2 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2304051 |
Summary#3 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2304052 |
Summary#4 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2304053 |
Summary#5 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2304054 |
Final summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| 9.2.2.1 |
Evaluation on AI/ML for CSI feedback enhancement |
|
| R1-2302319 |
Discussion and evaluation of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2302358 |
Evaluation on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2302437 |
Evaluation on AI CSI feedback enhancement |
ZTE |
| R1-2302477 |
Evaluation on AI/ML for CSI feedback enhancement |
vivo |
| R1-2302540 |
Evaluation methodology and results on AI/ML for CSI feedback enhancement |
OPPO |
| R1-2302593 |
Discussion on evaluation on AIML for CSI feedback enhancement |
Spreadtrum Communications, BUPT |
| R1-2302628 |
Evaluation of ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2302637 |
Evaluation of AI/ML based methods for CSI feedback enhancement |
Fraunhofer IIS |
| R1-2302695 |
Evaluation on AI/ML-based CSI feedback enhancement |
CATT |
| R1-2302790 |
Evaluation for CSI feedback enhancements |
Intel Corporation |
| R1-2302822 |
Evaluation on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2302904 |
Evaluation on AI/ML for CSI feedback enhancement |
Fujitsu |
| R1-2302918 |
Evaluations of AI-CSI |
Ericsson |
| R1-2302975 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
xiaomi |
| R1-2303050 |
On Evaluation of AI/ML based CSI |
Google |
| R1-2303076 |
Evaluation on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2303087 |
Evaluation on AI for CSI feedback enhancement |
Mavenir |
| R1-2303120 |
Evaluation on AI ML for CSI feedback enhancement |
Samsung |
| R1-2303174 |
Evaluation of AI and ML for CSI feedback enhancement |
RAN1, Comba |
| R1-2303183 |
Some discussions on evaluation on AI-ML for CSI feedback |
CAICT |
| R1-2303194 |
Evaluation on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2303224 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2303336 |
Evaluation on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2303435 |
Evaluation of AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2303475 |
Evaluation for AI/ML based CSI feedback enhancement |
Apple |
| R1-2303524 |
Evaluation on AI/ML for CSI feedback |
Lenovo |
| R1-2303582 |
Evaluation on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2303654 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2303705 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2303776 |
Evaluation on AI/ML for CSI feedback enhancement |
Indian Institute of Tech (H) |
| R1-2303849 |
Evaluation on AI/ML for CSI feedback enhancement |
IIT Kanpur |
| R1-2303988 |
Summary#1 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2303989 |
Summary#2 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2303990 |
Summary#3 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2303991 |
Summary#4 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2303992 |
Summary#5 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2303993 |
Summary#6 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| R1-2304247 |
Summary#7 for [112bis-e-R18-AIML-02] |
Moderator (Huawei) |
| 9.2.2.2 |
Other aspects on AI/ML for CSI feedback enhancement |
|
| R1-2302320 |
Discussion on other aspects of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2302359 |
Discussion on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2302438 |
Discussion on other aspects for AI CSI feedback enhancement |
ZTE |
| R1-2302478 |
Other aspects on AI/ML for CSI feedback enhancement |
vivo |
| R1-2302541 |
On sub use cases and other aspects of AI/ML for CSI feedback enhancement |
OPPO |
| R1-2302594 |
Discussion on other aspects on AIML for CSI feedback |
Spreadtrum Communications |
| R1-2302629 |
Other aspects on ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2302696 |
Discussion on AI/ML-based CSI feedback enhancement |
CATT |
| R1-2302750 |
Discussion on AI/ML for CSI feedback enhancement |
NEC |
| R1-2302791 |
On other aspects on AI/ML for CSI feedback |
Intel Corporation |
| R1-2302823 |
Discussion on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2302842 |
Considerations on CSI measurement enhancements via AI/ML |
Sony |
| R1-2302905 |
Views on specification impact for CSI feedback enhancement |
Fujitsu |
| R1-2302919 |
Discussion on AI-CSI |
Ericsson |
| R1-2302976 |
Discussion on specification impact for CSI feedback based on AI/ML |
Xiaomi |
| R1-2303026 |
Discussion on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2303038 |
Discussion on AI/ML for CSI feedback enhancement |
Panasonic |
| R1-2303051 |
On Enhancement of AI/ML based CSI |
Google |
| R1-2303077 |
Other aspects on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2303121 |
Discussion on potential specification impact for CSI feedback enhancement |
Samsung |
| R1-2303184 |
Discussions on AI-ML for CSI feedback |
CAICT |
| R1-2303195 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2303225 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2303337 |
Other aspects on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2303436 |
AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2303476 |
Discussion on other aspects of AI/ML for CSI enhancement |
Apple |
| R1-2303525 |
Further aspects of AI/ML for CSI feedback |
Lenovo |
| R1-2303583 |
Other aspects on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2303655 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2303706 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2303810 |
Discussions on CSI measurement enhancement for AI/ML communication |
TCL Communication Ltd. |
| R1-2303979 |
Summary #1 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2303980 |
Summary #2 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2303981 |
Summary #3 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2303982 |
Summary #4 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2303983 |
Summary #5 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| 9.2.3.1 |
Evaluation on AI/ML for beam management |
|
| R1-2302321 |
Discussion and evaluation of AI/ML for beam management |
FUTUREWEI |
| R1-2302360 |
Evaluation on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2302439 |
Evaluation on AI beam management |
ZTE |
| R1-2302479 |
Evaluation on AI/ML for beam management |
vivo |
| R1-2302542 |
Evaluation methodology and results on AI/ML for beam management |
OPPO |
| R1-2302595 |
Evaluation on AI/ML for beam management |
Spreadtrum Communications |
| R1-2302630 |
Evaluation of ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2302697 |
Evaluation on AI/ML-based beam management |
CATT |
| R1-2302792 |
Evaluations for AI/ML beam management |
Intel Corporation |
| R1-2302825 |
Discussion for evaluation on AI/ML for beam management |
InterDigital, Inc. |
| R1-2302878 |
Evaluation of AIML for beam management |
Ericsson |
| R1-2302906 |
Evaluation on AI/ML for beam management |
Fujitsu |
| R1-2302977 |
Evaluation on AI/ML for beam management |
xiaomi |
| R1-2303052 |
On Evaluation of AI/ML based Beam Management |
Google |
| R1-2303078 |
Evaluation on AI/ML for beam management |
LG Electronics |
| R1-2303122 |
Evaluation on AI ML for Beam management |
Samsung |
| R1-2303185 |
Some discussions on evaluation on AI-ML for Beam management |
CAICT |
| R1-2303226 |
Discussion on evaluation on AI/ML for beam management |
CMCC |
| R1-2303301 |
Evaluation on AI/ML for beam management |
CEWiT |
| R1-2303338 |
Evaluation on AI/ML for beam management |
MediaTek Inc. |
| R1-2303437 |
Evaluation of AI and ML for beam management |
NVIDIA |
| R1-2303477 |
Evaluation for AI/ML based beam management enhancements |
Apple |
| R1-2303526 |
Evaluation on AI/ML for beam management |
Lenovo |
| R1-2303584 |
Evaluation on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2303707 |
Discussion on evaluation on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2303994 |
Feature lead summary #0 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2303995 |
Feature lead summary #1 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2303996 |
Feature lead summary #2 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2303997 |
Feature lead summary #3 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| 9.2.3.2 |
Other aspects on AI/ML for beam management |
|
| R1-2302322 |
Discussion on other aspects of AI/ML for beam management |
FUTUREWEI |
| R1-2302361 |
Discussion on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2302432 |
Discussion on other aspects of AI/ML beam management |
New H3C Technologies Co., Ltd. |
| R1-2302440 |
Discussion on other aspects for AI beam management |
ZTE |
| R1-2302480 |
Other aspects on AI/ML for beam management |
vivo |
| R1-2302543 |
Other aspects of AI/ML for beam management |
OPPO |
| R1-2302596 |
Other aspects on AI/ML for beam management |
Spreadtrum Communications |
| R1-2302631 |
Other aspects on ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2302698 |
Discussion on AI/ML-based beam management |
CATT |
| R1-2302793 |
Other aspects on AI/ML for beam management |
Intel Corporation |
| R1-2302826 |
Discussion for other aspects on AI/ML for beam management |
InterDigital, Inc. |
| R1-2302843 |
Consideration on AI/ML for beam management |
Sony |
| R1-2302868 |
Discussion on AI/ML for beam management |
Panasonic |
| R1-2302883 |
Discussion on AI/ML for beam management |
Ericsson |
| R1-2302907 |
Discussion for specification impacts on AI/ML for beam management |
Fujitsu |
| R1-2302978 |
Potential specification impact on AI/ML for beam management |
xiaomi |
| R1-2303053 |
On Enhancement of AI/ML based Beam Management |
Google |
| R1-2303079 |
Other aspects on AI/ML for beam management |
LG Electronics |
| R1-2303123 |
Discussion on potential specification impact for beam management |
Samsung |
| R1-2303186 |
Discussions on AI-ML for Beam management |
CAICT |
| R1-2303196 |
Discussion on other aspects on AI/ML for beam management |
ETRI |
| R1-2303227 |
Discussion on other aspects on AI/ML for beam management |
CMCC |
| R1-2303339 |
Other aspects on AI/ML for beam management |
MediaTek Inc. |
| R1-2303438 |
AI and ML for beam management |
NVIDIA |
| R1-2303478 |
Discussion on other aspects of AI/ML for beam management enhancement |
Apple |
| R1-2303527 |
Further aspects of AI/ML for beam management |
Lenovo |
| R1-2303585 |
Other aspects on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2303669 |
Discussion on AI/ML for beam management |
NEC |
| R1-2303708 |
Discussion on other aspects on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2303966 |
Summary#1 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2303967 |
Summary#2 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2303968 |
Summary#3 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2303969 |
Summary#4 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2303970 |
Summary#5 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| 9.2.4.1 |
Evaluation on AI/ML for positioning accuracy enhancement |
|
| R1-2302335 |
Evaluation of AI/ML for Positioning Accuracy Enhancement |
Ericsson |
| R1-2302362 |
Evaluation on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2302441 |
Evaluation on AI positioning enhancement |
ZTE |
| R1-2302481 |
Evaluation on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2302544 |
Evaluation methodology and results on AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2302632 |
Evaluation of ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2302699 |
Evaluation on AI/ML-based positioning enhancement |
CATT |
| R1-2302908 |
Discussions on evaluation results of AIML positioning accuracy enhancement |
Fujitsu |
| R1-2302979 |
Evaluation on AI/ML for positioning accuracy enhancement |
xiaomi |
| R1-2303054 |
On Evaluation of AI/ML based Positioning |
Google |
| R1-2303080 |
Evaluation on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2303124 |
Evaluation on AI ML for Positioning |
Samsung |
| R1-2303187 |
Some discussions on evaluation on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2303228 |
Discussion on evaluation on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2303340 |
Evaluation of AIML for Positioning Accuracy Enhancement |
MediaTek Inc. |
| R1-2303439 |
Evaluation of AI and ML for positioning enhancement |
NVIDIA |
| R1-2303450 |
Evaluation on AI/ML for positioning accuracy enhancement |
InterDigital, Inc. |
| R1-2303479 |
Evaluation on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2303528 |
Discussion on AI/ML Positioning Evaluations |
Lenovo |
| R1-2303586 |
Evaluation on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2303926 |
Evaluation on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2304016 |
Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304017 |
Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304018 |
Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304019 |
Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304103 |
Summary #5 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304104 |
Summary #6 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304105 |
Summary #7 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2304106 |
Final Summary of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| 9.2.4.2 |
Other aspects on AI/ML for positioning accuracy enhancement |
|
| R1-2302336 |
Other Aspects of AI/ML Based Positioning Enhancement |
Ericsson |
| R1-2302363 |
Discussion on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2302442 |
Discussion on other aspects for AI positioning enhancement |
ZTE |
| R1-2302482 |
Other aspects on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2302545 |
On sub use cases and other aspects of AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2302597 |
Discussion on other aspects on AIML for positioning accuracy enhancement |
Spreadtrum Communications |
| R1-2302633 |
Other aspects on ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2302700 |
Discussion on AI/ML-based positioning enhancement |
CATT |
| R1-2302739 |
Other aspects on AI-ML for positioning accuracy enhancement |
Baicells |
| R1-2302844 |
Discussions on AI-ML for positioning accuracy enhancement |
Sony |
| R1-2302909 |
Discussions on specification impacts for AIML positioning accuracy enhancement |
Fujitsu |
| R1-2302980 |
Views on the other aspects of AI/ML-based positioning accuracy enhancement |
xiaomi |
| R1-2303055 |
On Enhancement of AI/ML based Positioning |
Google |
| R1-2303081 |
Other aspects on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2303125 |
Discussion on potential specification impact for Positioning |
Samsung |
| R1-2303188 |
Discussions on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2303229 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2303341 |
Other Aspects on AI ML Based Positioning Enhancement |
MediaTek Inc. |
| R1-2303413 |
On potential AI/ML solutions for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303440 |
AI and ML for positioning enhancement |
NVIDIA |
| R1-2303451 |
Designs and potential specification impacts of AIML for positioning |
InterDigital, Inc. |
| R1-2303480 |
On Other aspects on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2303529 |
AI/ML Positioning use cases and associated Impacts |
Lenovo |
| R1-2303587 |
Other aspects on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2303675 |
Discussion on AI/ML for positioning accuracy enhancement |
NEC |
| R1-2303709 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
NTT DOCOMO, INC. |
| R1-2303940 |
FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2304056 |
FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2304102 |
FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2304177 |
FL summary #4 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| 9.3 |
Study on evolution of NR duplex operation |
|
| R1-2303230 |
TR 38.858 v0.3.0 for study on evolution of NR duplex operation |
CMCC |
| R1-2303231 |
Updated summary on SLS calibration results for NR duplex evolution |
CMCC |
| R1-2303639 |
TP on SBFD for TR 38.858 |
CATT, CMCC, Samsung |
| R1-2304212 |
Summary on SLS calibration results for NR duplex evolution |
Moderator (CMCC) |
| 9.3.1 |
Evaluation on NR duplex evolution |
|
| R1-2302347 |
Discussion on evaluation and methodologies on evolution of NR duplex operation |
Huawei, HiSilicon |
| R1-2302427 |
Discussion for Evaluation on NR duplex evolution |
New H3C Technologies Co., Ltd. |
| R1-2302483 |
Evaluation on NR duplex evolution |
vivo |
| R1-2302521 |
Discussion on evaluation on NR duplex evolution |
InterDigital, Inc. |
| R1-2302546 |
Discussion on evaluation on NR duplex evolution |
OPPO |
| R1-2302598 |
Discussion on evaluation on NR duplex evolution |
Spreadtrum Communications, BUPT, New H3C |
| R1-2302701 |
Discussion on evaluation on NR duplex evolution |
CATT |
| R1-2302735 |
Discussion on evaluation of NR duplex evolution |
MediaTek Inc. |
| R1-2302756 |
SBFD Prototype and Preliminary Simulation Results |
ZTE |
| R1-2302769 |
Evaluation on NR duplex evolution |
Ericsson |
| R1-2302794 |
Evaluation of NR Duplex Enhancements |
Intel Corporation |
| R1-2302981 |
Discussion on evaluation on NR duplex evolution |
xiaomi |
| R1-2303015 |
On the evaluation methodology for NR duplexing enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303126 |
Discussion on evaluation for NR duplex evolution |
Samsung |
| R1-2303232 |
Evaluation on NR duplex evolution |
CMCC |
| R1-2303261 |
Discussion on evaluation on NR duplex evolution |
Panasonic |
| R1-2303302 |
Calibration analysis for SBFD |
CEWiT |
| R1-2303458 |
Evaluation on NR duplex evolution |
Sharp |
| R1-2303481 |
On evaluations for NR duplex evolution |
Apple |
| R1-2303588 |
On Deployment scenarios and evaluation Methodology for NR duplex evolution |
Qualcomm Incorporated |
| R1-2303710 |
Discussion on evaluation on NR duplex evolution |
NTT DOCOMO, INC. |
| R1-2303741 |
Study on Evaluation for NR duplex evolution |
LG Electronics |
| R1-2303773 |
Coupling loss for SBFD system level simulation calibration |
Korea Testing Laboratory |
| R1-2303892 |
SBFD Prototype and Preliminary Simulation Results |
ZTE |
| R1-2303945 |
Summary#1 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2303946 |
Summary#2 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2303947 |
Summary#3 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2303986 |
Discussion on evaluation on NR duplex evolution |
OPPO |
| R1-2304101 |
Evaluation of NR Duplex Enhancements |
Intel Corporation |
| R1-2304182 |
Draft LS on BS noise figure model for duplex evolution |
Moderator (CMCC) |
| R1-2304183 |
LS on BS noise figure model for duplex evolution |
RAN1, CMCC |
| 9.3.2 |
Subband non-overlapping full duplex |
|
| R1-2302348 |
Discussion on potential enhancement on subband non-overlapping full duplex |
Huawei, HiSilicon |
| R1-2302407 |
Discussion on subband non-overlapping full duplex |
TCL Communication Ltd. |
| R1-2302426 |
Discussion for subband non-overlapping full duplex |
New H3C Technologies Co., Ltd. |
| R1-2302484 |
Discussion on subband non-overlapping full duplex |
vivo |
| R1-2302522 |
Discussion on subband non-overlapping full duplex |
InterDigital, Inc. |
| R1-2302547 |
Discussion on subband non-overlapping full duplex |
OPPO |
| R1-2302599 |
Discussion on subband non-overlapping full duplex |
Spreadtrum Communications |
| R1-2302702 |
Discussion on subband non-overlapping full duplex |
CATT |
| R1-2302736 |
Discussion on subband non-overlapping full duplex for NR |
MediaTek Inc. |
| R1-2302746 |
Discussion on subband non-overlapping full duplex |
NEC |
| R1-2302757 |
Discussion of subband non-overlapping full duplex |
ZTE |
| R1-2302770 |
Subband non-overlapping full duplex |
Ericsson |
| R1-2302795 |
On SBFD operation in NR systems |
Intel Corporation |
| R1-2302845 |
Considerations on Subband Full Duplex TDD operations |
Sony |
| R1-2302910 |
Discussion on subband non-overlapping full duplex |
Fujitsu |
| R1-2302982 |
Discussion on subband non-overlapping full duplex |
xiaomi |
| R1-2303016 |
On subband non-overlapping full duplex for NR |
Nokia, Nokia Shanghai Bell |
| R1-2303127 |
On SBFD for NR duplex evolution |
Samsung |
| R1-2303197 |
Discussion on subband non-overlapping full duplex enhancements |
ETRI |
| R1-2303233 |
Discussion on subband non-overlapping full duplex |
CMCC |
| R1-2303262 |
Discussion on subband non-overlapping full duplex |
Panasonic |
| R1-2303303 |
Discussion on subband non-overlapping full duplex |
CEWiT |
| R1-2303408 |
Discussion on subband non-overlapping full duplex |
FGI |
| R1-2303459 |
Discussion on subband non-overlapping full duplex |
Sharp |
| R1-2303482 |
Views on subband non-overlapping full duplex |
Apple |
| R1-2303530 |
Subband non-overlapping full duplex |
Lenovo |
| R1-2303589 |
Feasibility and techniques for Subband non-overlapping full duplex |
Qualcomm Incorporated |
| R1-2303711 |
Discussion on subband non-overlapping full duplex |
NTT DOCOMO, INC. |
| R1-2303742 |
Study on Subband non-overlapping full duplex |
LG Electronics |
| R1-2303779 |
Discussion on sub-band non-overlapping full duplex |
ITRI |
| R1-2303825 |
Details of subband non-overlapping full duplex |
ASUSTEK COMPUTER (SHANGHAI) |
| R1-2303830 |
Discussion on subband non-overlapping full duplex |
WILUS Inc. |
| R1-2304028 |
Summary #1 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2304029 |
Summary #2 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2304030 |
Summary #3 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2304031 |
Summary #4 of subband non-overlapping full duplex |
Moderator (CATT) |
| 9.3.3 |
Potential enhancements on dynamic/flexible TDD |
|
| R1-2302349 |
Study on potential enhancements on dynamic/flexible TDD |
Huawei, HiSilicon |
| R1-2302408 |
Potential enhancement on dynamic/flexible TDD |
TCL Communication Ltd. |
| R1-2302430 |
Discussion on potential enhancement on dynamic/flexible TDD |
New H3C Technologies Co., Ltd. |
| R1-2302485 |
Potential enhancements on dynamic/flexible TDD |
vivo |
| R1-2302523 |
Discussion on potential enhancements on dynamic/flexible TDD |
InterDigital, Inc. |
| R1-2302548 |
Discussion on potential enhancements on dynamic/flexible TDD |
OPPO |
| R1-2302600 |
Discussion on potential enhancements on dynamic/flexible TDD |
Spreadtrum Communications |
| R1-2302703 |
Discussion on potential enhancements on dynamic/flexible TDD |
CATT |
| R1-2302737 |
Discussion on potential enhancements for dynamic/flexible TDD |
MediaTek Inc. |
| R1-2302745 |
Views on enhancements of dynamic/flexible TDD |
NEC |
| R1-2302758 |
Discussion of enhancements on dynamic/flexible TDD |
ZTE, China Telecom |
| R1-2302771 |
Potential enhancements on dynamic/flexible TDD |
Ericsson |
| R1-2302796 |
On potential enhancements for dynamic/flexible TDD operations |
Intel Corporation |
| R1-2302846 |
Considerations on Flexible/Dynamic TDD |
Sony |
| R1-2302983 |
Discussion on potential enhancements on dynamic/flexible TDD |
xiaomi |
| R1-2303017 |
Dynamic TDD enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303088 |
Potential enhancements on dynamic/flexible TDD |
Lenovo |
| R1-2303128 |
Dynamic and flexible TDD for NR duplex evolution |
Samsung |
| R1-2303167 |
Discussion on potential enhancements on dynamic/flexible TDD |
Panasonic |
| R1-2303234 |
Discussion on potential enhancements on flexible/dynamic TDD |
CMCC |
| R1-2303304 |
Discussion on enhancements on dynamic/flexible TDD |
CEWiT |
| R1-2303483 |
Views on potential enhancements on dynamic TDD |
Apple |
| R1-2303590 |
On potential enhancements on dynamic/flexible TDD |
Qualcomm Incorporated |
| R1-2303712 |
Discussion on potential enhancements on dynamic/flexible TDD |
NTT DOCOMO, INC. |
| R1-2303743 |
Study on Potential enhancements on dynamic/flexible TDD |
LG Electronics |
| R1-2303831 |
Discussion on potential enhancements on dynamic/flexible TDD |
WILUS Inc. |
| R1-2304032 |
Summary #1 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2304033 |
Summary #2 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2304034 |
Summary #3 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2304035 |
Summary #4 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| 9.4 |
NR sidelink evolution |
|
| R1-2304074 |
Summary#1 - [112bis-e-R18-SL-05] Email discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements in R1-2302280 |
Moderator (Nokia) |
| R1-2304075 |
Summary#2 - [112bis-e-R18-SL-05] Email discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements in R1-2302280 |
Moderator (Nokia) |
| R1-2304169 |
Session notes for 9.4 (NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| R1-2304210 |
Draft Reply LS on comparison of SL-RSRP and SD-RSRP measurements |
Moderator (Nokia) |
| R1-2304211 |
Reply LS on comparison of SL-RSRP and SD-RSRP measurements |
RAN1, Nokia |
| 9.4.1.1 |
Channel access mechanism |
|
| R1-2302289 |
On Channel Access Mechanism for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2302324 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2302353 |
Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2302486 |
Channel access mechanism for sidelink on unlicensed spectrum |
vivo |
| R1-2302519 |
Sidelink channel access mechanisms |
National Spectrum Consortium |
| R1-2302549 |
On channel access mechanism and resource allocation for SL-U |
OPPO |
| R1-2302601 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2302704 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2302797 |
On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2302847 |
Discussion on channel access mechanism for SL-unlicensed |
Sony |
| R1-2302911 |
Discussion on channel access mechanism for SL-U |
Fujitsu |
| R1-2302922 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2302951 |
Sidelink channel access on unlicensed spectrum |
InterDigital, Inc. |
| R1-2302984 |
Discussion on channel access mechanism for sidelink-unlicensed |
xiaomi |
| R1-2303002 |
SL-U Channel Access Mechanism Clarifications |
CableLabs |
| R1-2303129 |
On channel access mehanism for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2303168 |
Sidelink channel access on unlicensed spectrum |
Panasonic |
| R1-2303189 |
Considerations on channel access mechanism of SL-U |
CAICT |
| R1-2303198 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
ETRI |
| R1-2303235 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CMCC |
| R1-2303313 |
Channel access mechanism for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2303323 |
Channel access mechanism for SL-U |
Ericsson |
| R1-2303367 |
Discussion on channel access mechanism |
MediaTek Inc. |
| R1-2303374 |
Discussion of channel access mechanism for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2303400 |
Discussion on channel access mechanism for SL-U |
ZTE, Sanechips |
| R1-2303484 |
Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum |
Apple |
| R1-2303521 |
Discussion on Channel Access Mechanisms |
Johns Hopkins University APL |
| R1-2303535 |
NR Sidelink Unlicensed Channel Access Mechanisms |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2303591 |
Channel Access Mechanism for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2303686 |
Channel Access of Sidelink on Unlicensed Spectrum |
NEC |
| R1-2303713 |
Discussion on channel access mechanism in SL-U |
NTT DOCOMO, INC. |
| R1-2303768 |
Discussion on channel access mechanism for NR sidelink evolution |
Sharp |
| R1-2303819 |
Channel Access Mechanism for SL-U |
ITL |
| R1-2303832 |
Discussion on channel access mechanism for SL-U |
WILUS Inc. |
| R1-2303971 |
FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2303972 |
FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2303973 |
FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2303974 |
FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2303975 |
FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2304145 |
[DRAFT] LS on PSFCH and S-SSB transmissions over non-contiguous RB sets |
Moderator (OPPO) |
| R1-2304218 |
LS on PSFCH and S-SSB transmissions over non-contiguous RB sets |
RAN1, OPPO |
| R1-2304257 |
LS on MCSt resource (re-)selection |
RAN1, OPPO |
| 9.4.1.2 |
Physical channel design framework |
|
| R1-2302290 |
On Physical Channel Design Framework for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2302325 |
Discussion on physical channel design for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2302354 |
Physical channel design for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2302487 |
Physical channel design framework for sidelink on unlicensed spectrum |
vivo |
| R1-2302520 |
Sidelink Physical Channel Design Considerations |
National Spectrum Consortium |
| R1-2302550 |
On PHY channel designs and procedures for SL-U |
OPPO |
| R1-2302602 |
Discussion on Physical channel design for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2302705 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2302798 |
On the Physical Layer Enhancements for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2302848 |
Discussion on physical channel design framework for SL-unlicensed |
Sony |
| R1-2302923 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2302952 |
SL U physical layer design framework |
InterDigital, Inc. |
| R1-2302985 |
Discussion on physical channel design for sidelink-unlicensed |
xiaomi |
| R1-2303130 |
On physical channel design framework for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2303169 |
Physical channel design for sidelink on unlicensed spectrum |
Panasonic |
| R1-2303199 |
Discussion on physical channel design framework for SL-U |
ETRI |
| R1-2303236 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CMCC |
| R1-2303314 |
Physical layer design framework for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2303324 |
PHY channel design framework for SL-U |
Ericsson |
| R1-2303368 |
Discussion on physical channel design framework |
MediaTek Inc. |
| R1-2303375 |
Discussion of physical channel design for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2303401 |
Discussion on physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2303485 |
On Sidelink Physical Channel Design Framework for Unlicensed Spectrum |
Apple |
| R1-2303539 |
NR Sidelink Unlicensed Physical Channel Design |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2303592 |
Physical Channel Design for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2303670 |
Discussion on physical channel design framework |
NEC |
| R1-2303714 |
Discussion on channel design framework in SL-U |
NTT DOCOMO, INC. |
| R1-2303769 |
Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum |
Sharp |
| R1-2303820 |
Physical Channel Design framework for SL-U |
ITL |
| R1-2303833 |
Discussion on PHY channel design framework for SL-U |
WILUS Inc. |
| R1-2303918 |
FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2303919 |
FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2303920 |
FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| 9.4.2 |
Co-channel coexistence for LTE sidelink and NR sidelink |
|
| R1-2302291 |
On Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2302355 |
Co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R1-2302488 |
Co-channel coexistence for LTE sidelink and NR sidelink |
vivo |
| R1-2302551 |
Remaining details on dynamic resource sharing |
OPPO |
| R1-2302581 |
Dynamic co-channel coexistence for LTE sidelink and NR sidelink |
TOYOTA Info Technology Center |
| R1-2302603 |
Discussion on Co-channel coexistence for LTE sidelink and NR sidelink |
Spreadtrum Communications |
| R1-2302706 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CATT, GOHIGH |
| R1-2302799 |
On the Co-channel Coexistence between LTE and NR Sidelink |
Intel Corporation |
| R1-2302849 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sony |
| R1-2302872 |
Discussion on Sidelink Co-channel Coexistence |
Panasonic |
| R1-2302924 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
LG Electronics |
| R1-2302931 |
FL Summary #1 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2302932 |
FL Summary #2 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2302933 |
FL Summary #3 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2302953 |
Co-channel coexistence for LTE sidelink and NR sidelink |
InterDigital, Inc. |
| R1-2302986 |
Discussion on co-channel coexistence for LTE and NR Sidelink |
xiaomi |
| R1-2303131 |
On co-channel coexistence for LTE sidelink and NR sidelink |
Samsung |
| R1-2303200 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ETRI |
| R1-2303237 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CMCC |
| R1-2303315 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Lenovo |
| R1-2303325 |
Co-channel coexistence between LTE sidelink and NR sidelink |
Ericsson |
| R1-2303376 |
Discussion of co-channel coexistence for LTE sidelink and NR sidelink |
Transsion Holdings |
| R1-2303402 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ZTE, Sanechips |
| R1-2303486 |
On Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Apple |
| R1-2303540 |
Discussion on Co-Channel Coexistence for LTE and NR Sidelink |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2303593 |
Co-channel Coexistence Between LTE SL and NR SL |
Qualcomm Incorporated |
| R1-2303687 |
Co-existence between LTE and NR sidelink |
NEC |
| R1-2303715 |
Discussion on co-channel coexistence of LTE-SL and NR-SL |
NTT DOCOMO, INC. |
| R1-2303770 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sharp |
| R1-2303787 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ASUSTeK |
| R1-2303791 |
Co-channel coexistence for LTE sidelink and NR sidelink |
Continental Automotive |
| R1-2303834 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
WILUS Inc. |
| R1-2303848 |
On sidelink co-channel coexistence issues |
Mitsubishi Electric RCE |
| R1-2303976 |
Co-channel Coexistence Between LTE SL and NR SL |
Qualcomm Incorporated |
| R1-2304110 |
FL Summary #4 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2304178 |
FL Summary #5 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| 9.4.3 |
Enhanced sidelink operation on FR2 licensed spectrum |
|
| R1-2302292 |
On Beam Management for Sidelink in FR2 |
Nokia, Nokia Shanghai Bell |
| R1-2302356 |
Enhanced sidelink operation on FR2 licensed spectrum |
Huawei, HiSilicon |
| R1-2302489 |
Enhanced sidelink operation on FR2 licensed spectrum |
vivo |
| R1-2302552 |
On sidelink beam management in FR2 |
OPPO |
| R1-2302582 |
Discussion on sidelink beam management on FR2 licensed spectrum |
TOYOTA Info Technology Center |
| R1-2302604 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
Spreadtrum Communications |
| R1-2302707 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
CATT |
| R1-2302800 |
On Sidelink Operation in FR2 Licensed Spectrum |
Intel Corporation |
| R1-2302850 |
Discussion on sidelink beam management on FR2 licensed spectrum |
Sony |
| R1-2302925 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
LG Electronics |
| R1-2302954 |
On enhanced SL FR2 operation |
InterDigital, Inc. |
| R1-2302987 |
Discussion on SL beam management in FR2 licensed spectrum |
xiaomi |
| R1-2303132 |
On enhanced SL Operation in FR2 |
Samsung |
| R1-2303238 |
Discussion on sidelink enhancements on FR2 licensed spectrum |
CMCC |
| R1-2303305 |
Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation |
CEWiT |
| R1-2303316 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
Lenovo |
| R1-2303326 |
Study aspects for sidelink in FR2 licensed spectrum |
Ericsson |
| R1-2303369 |
Discussion on SL operation on FR2 |
MediaTek Inc. |
| R1-2303377 |
Discussion of sidelink operation on FR2 |
Transsion Holdings |
| R1-2303403 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
ZTE, Sanechips |
| R1-2303487 |
On Sidelink Operation on FR2 |
Apple |
| R1-2303522 |
Discussion on Enhanced Sidelink Operation on FR2 Licensed Spectrum |
Johns Hopkins University APL |
| R1-2303541 |
NR Sidelink Operation in FR2 |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2303594 |
Enhanced sidelink operation on FR2 licensed spectrum |
Qualcomm Incorporated |
| R1-2303671 |
Discussion on sidelink operation on FR2 licensed spectrum |
NEC |
| R1-2303716 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
NTT DOCOMO, INC. |
| R1-2303771 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
Sharp |
| R1-2303835 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
WILUS Inc. |
| R1-2303881 |
Enhanced sidelink operation on FR2 licensed spectrum |
vivo |
| R1-2303903 |
FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2303904 |
FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2303905 |
FL summary #3 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| 9.5 |
Expanded and Improved NR Positioning |
|
| R1-2304100 |
Moderator summary on LS reply for error source distributions (R1-2302282) |
Moderator (InterDigital, Inc.) |
| R1-2304146 |
[Draft] Reply LS to RAN2 on error source distributions |
Moderator (InterDigital, Inc.) |
| R1-2304147 |
Reply LS to RAN2 on error source distributions |
RAN1, InterDigital, Inc. |
| R1-2304170 |
Session notes for 9.5 (Study on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2304243 |
RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| 9.5.1 |
Sidelink positioning |
|
| R1-2304092 |
Moderator summary on discussion of RAN2 LS in R1-2302281 on RAN dependency for Ranging & Sidelink Positioning |
Moderator (xiaomi) |
| R1-2304152 |
Reply LS on RAN dependency for Ranging & Sidelink Positioning |
RAN1, xiaomi |
| 9.5.1.1 |
SL positioning reference signal |
|
| R1-2302293 |
Design of SL positioning reference signal SL-PRS |
Nokia, Nokia Shanghai Bell |
| R1-2302326 |
Discussion on SL positioning reference signal |
FUTUREWEI |
| R1-2302377 |
Design on SL-PRS and power control |
Huawei, HiSilicon |
| R1-2302388 |
On sidelink positioning reference signal transmission coordination |
Continental Automotive |
| R1-2302490 |
Discussion on SL positioning reference signal |
vivo |
| R1-2302553 |
Discussion on SL positioning reference signal |
OPPO |
| R1-2302583 |
Discussion on SL positioning reference signal |
TOYOTA Info Technology Center |
| R1-2302605 |
Discussion on SL positioning reference signal |
Spreadtrum Communications |
| R1-2302708 |
Further discussion on SL positioning reference signal |
CATT, GOHIGH |
| R1-2302801 |
On SL Positioning Reference Signals |
Intel Corporation |
| R1-2302851 |
Discussion on SL positioning reference signal |
Sony |
| R1-2302874 |
Discussion on Sidelink Positioning Reference Signal |
Panasonic |
| R1-2302926 |
Discussion on SL positioning reference signal |
LG Electronics |
| R1-2302988 |
Discussion on sidelink positioning reference signal |
xiaomi |
| R1-2303027 |
Discussion on SL positioning reference signal |
China Telecom |
| R1-2303063 |
SL positioning reference signal |
Sharp |
| R1-2303133 |
On SL Positioning Reference Signal |
Samsung |
| R1-2303239 |
Discussion on SL positioning reference signal |
CMCC |
| R1-2303263 |
Discussion on SL PRS Aspects |
Lenovo |
| R1-2303276 |
Discussion on SL positioning reference signal |
ZTE |
| R1-2303306 |
Discussion on SL positioning reference signal design |
CEWiT |
| R1-2303414 |
Design considerations on SL positioning reference signal |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303443 |
SL-PRS design and power control for SL-PRS |
InterDigital, Inc. |
| R1-2303488 |
On SL positioning reference signal |
Apple |
| R1-2303550 |
SL positioning reference signal design |
Ericsson |
| R1-2303595 |
Reference Signal Design for SL Positioning |
Qualcomm Incorporated |
| R1-2303683 |
Discussion on SL positioning reference signal |
NEC |
| R1-2303784 |
Discussion on sidelink positioning reference signal |
ASUSTeK |
| R1-2303837 |
Reference signal design for sidelink positioning |
MediaTek (Chengdu) Inc. |
| R1-2303963 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2303964 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2303965 |
FL summary #3 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2304242 |
FL summary #4 on SL positioning reference signal |
Moderator (Intel Corporation) |
| 9.5.1.2 |
Measurements and reporting for SL positioning |
|
| R1-2302294 |
On measurements and reporting for SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2302327 |
Discussion on measurements and reporting for SL positioning |
FUTUREWEI |
| R1-2302378 |
Discussion on SL positioning measurement and reporting |
Huawei, HiSilicon |
| R1-2302491 |
Discussion on measurements and reporting for SL positioning |
vivo |
| R1-2302554 |
Discussion on measurements and reporting for SL positioning |
OPPO |
| R1-2302606 |
Discussion on measurements and reporting for SL positioning |
Spreadtrum Communications |
| R1-2302709 |
Further discussion on measurements and reporting for SL positioning |
CATT, GOHIGH |
| R1-2302802 |
Measurements and reporting for SL positioning |
Intel Corporation |
| R1-2302852 |
On Measurements and reporting for SL positioning |
Sony |
| R1-2302927 |
Discussion on measurements and reporting for SL positioning |
LG Electronics |
| R1-2302989 |
Discussion on measurements and reporting for SL positioning |
xiaomi |
| R1-2303064 |
Measurements and reporting for SL positioning |
Sharp |
| R1-2303134 |
On Measurements and Reporting for SL Positioning |
Samsung |
| R1-2303240 |
Discussion on measurements and reporting for SL positioning |
CMCC |
| R1-2303264 |
Discussion on SL Positioning Measurement and Reporting |
Lenovo |
| R1-2303277 |
Discussion on SL positioning measurements and reporting |
ZTE |
| R1-2303307 |
View on SL positioning measurements, measurements and reporting for SL positioning |
CEWiT |
| R1-2303415 |
Measurements and reporting for SL positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303444 |
Measurement and reporting for SL positioning |
InterDigital, Inc. |
| R1-2303489 |
On Measurements and reporting for SL positioning |
Apple |
| R1-2303551 |
Measurements and reporting for SL positioning |
Ericsson |
| R1-2303596 |
Measurements and Reporting for SL Positioning |
Qualcomm Incorporated |
| R1-2303775 |
Solution for Carrier Phase based RTT Positioning |
Locaila |
| R1-2303842 |
Measurement and reporting design for sidelink positioning |
MediaTek (Chengdu) Inc. |
| R1-2303956 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2303957 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2303958 |
Summary #3 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2304240 |
Summary #4 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| 9.5.1.3 |
Resource allocation for SL positioning reference signal |
|
| R1-2302295 |
On resource allocation for SL positioning reference signal |
Nokia, Nokia Shanghai Bell |
| R1-2302328 |
Discussion on resource allocation for SL PRS |
FUTUREWEI |
| R1-2302379 |
Discussion on SL-PRS resource allocation |
Huawei, HiSilicon |
| R1-2302387 |
Considerations on resource allocation for sidelink positioning reference signal |
Continental Automotive |
| R1-2302492 |
Discussion on resource allocation for SL positioning reference signal |
vivo |
| R1-2302555 |
Discussion on resource allocation for SL positioning reference signal |
OPPO |
| R1-2302584 |
Discussion on resource allocation for SL positioning reference signal |
TOYOTA Info Technology Center |
| R1-2302607 |
Discussion on resource allocation for SL positioning reference signal |
Spreadtrum Communications |
| R1-2302710 |
Further discussion on resource allocation for SL positioning reference signal |
CATT, GOHIGH |
| R1-2302803 |
On resource allocation for SL positioning |
Intel Corporation |
| R1-2302853 |
Discussion on resource allocation for SL positioning reference signal |
Sony |
| R1-2302875 |
Discussion on Resource Allocation for SL-PRS |
Panasonic |
| R1-2302928 |
Discussion on resource allocation for SL positioning reference signal |
LG Electronics |
| R1-2302990 |
Discussion on resource allocation for SL positioning reference signal |
xiaomi |
| R1-2303028 |
Discussion on SL positioning reference signal resource allocation |
China Telecom |
| R1-2303065 |
Resource allocation for SL positioning reference signal |
Sharp |
| R1-2303135 |
On Resource Allocation for SL Positioning Reference Signal |
Samsung |
| R1-2303241 |
Discussion on resource allocation for SL positioning reference signal |
CMCC |
| R1-2303265 |
Discussion on SL Positioning Resource Allocation |
Lenovo |
| R1-2303278 |
Discussion on resource allocation for SL positioning reference signal |
ZTE |
| R1-2303308 |
Discussion on SL positioning resource allocation for SL positioning reference signal |
CEWiT |
| R1-2303416 |
Considerations on SL-PRS resource allocation |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303445 |
Resource allocation for SL positioning reference signal |
InterDigital, Inc. |
| R1-2303490 |
On Resource allocation for SL positioning reference signal |
Apple |
| R1-2303552 |
Resource allocation for SL positioning reference signal |
Ericsson |
| R1-2303597 |
Resource Allocation for SL-PRS |
Qualcomm Incorporated |
| R1-2303684 |
Discussion on resource allocation for SL positioning reference signal |
NEC |
| R1-2303786 |
Discussion on resource allocation for SL PRS |
ASUSTeK |
| R1-2303823 |
Considerations on resource allocation for SL positioning reference signal |
ITL |
| R1-2303838 |
Resource allocation for SL-PRS |
MediaTek (Chengdu) Inc. |
| R1-2303978 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2304067 |
Moderator Summary #2 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2304140 |
Moderator Summary #3 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2304233 |
Moderator Summary #4 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| 9.5.2 |
NR DL and UL carrier phase positioning |
|
| R1-2302380 |
Measurement and reporting for NR carrier phase positioning |
Huawei, HiSilicon |
| R1-2302493 |
Discussion on carrier phase positioning |
vivo |
| R1-2302524 |
Discussions on Carrier Phase Measurement for NR Positioning |
BUPT |
| R1-2302556 |
Discussions on NR carrier phase positioning |
OPPO |
| R1-2302608 |
Discussion on NR DL and UL carrier phase positioning |
Spreadtrum Communications |
| R1-2302711 |
Further discussion on NR DL and UL carrier phase positioning |
CATT |
| R1-2302804 |
On DL and UL carrier phase positioning |
Intel Corporation |
| R1-2302934 |
Views on NR DL and UL carrier phase positioning |
Nokia, Nokia Shanghai Bell |
| R1-2302991 |
NR DL and UL carrier phase positioning |
xiaomi |
| R1-2303136 |
On NR DL and UL Carrier Phase Positioning |
Samsung |
| R1-2303242 |
Discussion on DL/UL carrier phase positioning |
CMCC |
| R1-2303266 |
DL & UL Carrier Phase Positioning Discussion |
Lenovo |
| R1-2303279 |
Discussion on carrier phase positioning |
ZTE |
| R1-2303417 |
NR carrier phase measurements for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303446 |
Discussion on positioning based on NR carrier phase measurement |
InterDigital, Inc. |
| R1-2303491 |
On NR DL and UL carrier phase positioning |
Apple |
| R1-2303553 |
NR DL and UL carrier phase positioning |
Ericsson |
| R1-2303598 |
NR Carrier Phase Positioning |
Qualcomm Incorporated |
| R1-2303717 |
Discussion on NR DL and UL carrier phase positioning |
NTT DOCOMO, INC. |
| R1-2303744 |
Discussion on carrier phase positioning in NR |
LG Electronics |
| R1-2303774 |
Discussion on integer number resolution |
Locaila |
| R1-2303821 |
Discussion on NR UL and DL carrier phase positioning |
IIT Kanpur, CEWiT |
| R1-2303841 |
Solutions for carrier phase positioning |
MediaTek (Chengdu) Inc. |
| R1-2303882 |
NR carrier phase measurements for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303888 |
FL Summary #1 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2303889 |
FL Summary #2 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2303890 |
FL Summary #3 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2303944 |
Discussion on carrier phase positioning in NR |
LG Electronics |
| 9.5.3 |
LPHAP (Low Power High Accuracy Positioning) |
|
| R1-2302330 |
On enhancements for Rel-18 NR LPHAP |
FUTUREWEI |
| R1-2302381 |
Physical layer aspects of LPHAP |
Huawei, HiSilicon |
| R1-2302431 |
Discussion on Low Power High Accuracy Positioning |
Quectel |
| R1-2302494 |
Discussion on low power high accuracy positioning |
vivo |
| R1-2302557 |
Discussion on low power high accuracy positioning |
OPPO |
| R1-2302609 |
Discussion on LPHAP (Low Power High Accuracy Positioning) |
Spreadtrum Communications |
| R1-2302712 |
Further discussion on Low Power High Accuracy Positioning |
CATT |
| R1-2302805 |
On support of LPHAP |
Intel Corporation |
| R1-2302854 |
Discussion on Low Power High Accuracy Positioning |
Sony |
| R1-2302935 |
Views on LPHAP |
Nokia, Nokia Shanghai Bell |
| R1-2302992 |
Discussion on Low Power High Accuracy Positioning |
xiaomi |
| R1-2303137 |
On Low Power High Accuracy Positioning |
Samsung |
| R1-2303243 |
Discussion on low power high accuracy positioning |
CMCC |
| R1-2303280 |
Discussion on low power high accuracy positioning |
ZTE |
| R1-2303447 |
Discussions on Low Power High Accuracy Positioning (LPHAP) techniques |
InterDigital, Inc. |
| R1-2303492 |
On Low Power High Accuracy Positioning |
Apple |
| R1-2303554 |
On Low Power High Accuracy Positioning |
Ericsson |
| R1-2303599 |
Discussion on LPHAP Positioning |
Qualcomm Incorporated |
| R1-2303676 |
Discussion on Low Power High Accuracy Positioning |
NEC |
| R1-2303718 |
Discussion on Low Power High Accuracy Positioning |
NTT DOCOMO, INC. |
| R1-2303745 |
Discussion on LPHAP in idle/inactive state |
LG Electronics |
| R1-2304000 |
Summary #1 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2304001 |
Summary #2 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2304002 |
Summary #3 for low power high accuracy positioning |
Moderator (CMCC) |
| 9.5.4 |
Bandwidth aggregation for positioning measurements |
|
| R1-2302382 |
Discussion on PRS/SRS BW aggregation |
Huawei, HiSilicon |
| R1-2302495 |
Discussion on bandwidth aggregation for positioning measurements |
vivo |
| R1-2302558 |
Discussion on bandwidth aggregation for positioning measurement |
OPPO |
| R1-2302610 |
Discussion on bandwidth aggregation for positioning measurements |
Spreadtrum Communications |
| R1-2302713 |
Further discussion on bandwidth aggregation for positioning measurements |
CATT |
| R1-2302806 |
On bandwidth aggregation for positioning measurements |
Intel Corporation |
| R1-2302936 |
Views on Bandwidth aggregation for positioning measurements |
Nokia, Nokia Shanghai Bell |
| R1-2302993 |
Bandwidth aggregation for positioning measurement |
Xiaomi |
| R1-2303138 |
On Bandwidth Aggregation for Positioning Measurements |
Samsung |
| R1-2303201 |
Bandwidth aggregation for positioning measurements |
ETRI |
| R1-2303244 |
Discussion on BW aggregation for positioning measurements |
CMCC |
| R1-2303267 |
PRS/SRS Bandwidth Aggregation Aspects |
Lenovo |
| R1-2303281 |
Discussion on BW aggregation for positioning |
ZTE |
| R1-2303285 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2303286 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2303448 |
Bandwidth aggregation for positioning measurements |
InterDigital, Inc. |
| R1-2303493 |
On Bandwidth aggregation for positioning measurements |
Apple |
| R1-2303555 |
Bandwidth aggregation for positioning measurements |
Ericsson |
| R1-2303600 |
Discussion on Bandwidth aggregation for Positioning |
Qualcomm Incorporated |
| R1-2303719 |
Discussion on bandwidth aggregation for positioning measurements |
NTT DOCOMO, INC. |
| R1-2303746 |
Discussion on Bandwidth aggregation for positioning measurements |
LG Electronics |
| R1-2303839 |
PRS/SRS aggregation for positioning measurement |
MediaTek (Chengdu) Inc. |
| R1-2303927 |
Discussion on Bandwidth aggregation for Positioning |
Qualcomm Incorporated |
| R1-2304081 |
[Draft] LS on measurement definitions for positioning with bandwidth aggregation |
Moderator (ZTE) |
| R1-2304082 |
LS on measurement definitions for positioning with bandwidth aggregation |
RAN1, ZTE |
| R1-2304083 |
Summary #3 for BW aggregation positioning |
Moderator (ZTE) |
| 9.5.5 |
Positioning for RedCap UEs |
|
| R1-2302329 |
On positioning for RedCap UEs in Rel-18 |
FUTUREWEI |
| R1-2302383 |
Discussion on positioning for RedCap UEs |
Huawei, HiSilicon |
| R1-2302496 |
Discussion on positioning for RedCap UEs |
vivo |
| R1-2302559 |
Discussion on positioning for RedCap UEs |
OPPO |
| R1-2302611 |
Discussion on positioning for RedCap Ues |
Spreadtrum Communications |
| R1-2302714 |
Further discussion on positioning for RedCap UEs |
CATT |
| R1-2302807 |
Positioning for RedCap UEs |
Intel Corporation |
| R1-2302855 |
Discussion on positioning for RedCap UEs |
Sony |
| R1-2302937 |
Views on Positioning for RedCap UEs |
Nokia, Nokia Shanghai Bell |
| R1-2303139 |
On Positioning for RedCap UEs |
Samsung |
| R1-2303245 |
Discussion on RedCap UE positioning |
CMCC |
| R1-2303268 |
RedCap Positioning |
Lenovo |
| R1-2303282 |
Discussion on Positioning for RedCap UEs |
ZTE |
| R1-2303449 |
Positioning for RedCap UEs |
InterDigital, Inc. |
| R1-2303494 |
On Positioning for RedCap UEs |
Apple |
| R1-2303556 |
Positioning for RedCap Ues |
Ericsson |
| R1-2303601 |
Positioning for Reduced Capabilities UEs |
Qualcomm Incorporated |
| R1-2303674 |
Discussion on positioning support for RedCap UEs |
NEC |
| R1-2303720 |
Discussion on positioning for RedCap UEs |
NTT DOCOMO, INC. |
| R1-2303747 |
Discussion on positioning support for RedCap UEs |
LG Electronics |
| R1-2303822 |
Discussion on NR positioning for RedCap |
IIT Kanpur, CEWiT |
| R1-2303840 |
Positioning for RedCap UEs |
MediaTek (Chengdu) Inc. |
| R1-2304004 |
Feature Lead Summary #1 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2304005 |
Feature Lead Summary #2 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2304006 |
Feature Lead Summary #3 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2304007 |
Feature Lead Summary #4 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2304253 |
Feature Lead Summary #5 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| 9.6 |
Enhanced support of reduced capability NR device |
|
| R1-2303938 |
RAN1 agreements for Rel-18 NR RedCap |
Rapporteur (Ericsson) |
| R1-2304171 |
Session notes for 9.6 (Study on further NR RedCap (reduced capability) UE complexity reduction) |
Ad-hoc Chair (CMCC) |
| 9.6.1 |
UE complexity reduction |
|
| R1-2302298 |
Further RedCap UE complexity reduction |
Ericsson |
| R1-2302323 |
Discussion on R18 RedCap complexity |
FUTUREWEI |
| R1-2302342 |
Discussion on potential solutions to further reduce UE complexity |
Huawei, HiSilicon |
| R1-2302497 |
Discussion on further UE complexity reduction |
vivo |
| R1-2302560 |
Further consideration on reduced UE complexity |
OPPO |
| R1-2302612 |
Discussion on enhanced support of RedCap devices |
Spreadtrum Communications |
| R1-2302715 |
Discussion on further complexity reduction for Rel-18 RedCap UE |
CATT |
| R1-2302808 |
Complexity reduction for eRedCap UE |
Intel Corporation |
| R1-2302887 |
RedCap UE Complexity Reduction |
Nokia, Nokia Shanghai Bell |
| R1-2302943 |
Discussion on further UE complexity reduction |
ZTE, Sanechips |
| R1-2302994 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2303029 |
Discussion on further complexity reduction for eRedCap UEs |
China Telecom |
| R1-2303062 |
Discussion on UE complexity reduction |
Sharp |
| R1-2303089 |
UE complexity reduction |
Lenovo |
| R1-2303140 |
Further UE complexity reduction for eRedCap |
Samsung |
| R1-2303173 |
Discussion on Rel-18 RedCap UE |
NEC |
| R1-2303246 |
Discussion on further reduced UE complexity |
CMCC |
| R1-2303349 |
On eRedCap complexity reduction |
MediaTek Inc. |
| R1-2303378 |
Discussion on UE complexity reduction |
Transsion Holdings |
| R1-2303425 |
Discussion on further UE complexity reduction for eRedCap |
LG Electronics |
| R1-2303452 |
Considerations for further UE complexity reduction |
Sierra Wireless. S.A. |
| R1-2303495 |
Further RedCap UE complexity reduction |
Apple |
| R1-2303536 |
On further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2303602 |
UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2303638 |
UE complexity reduction for eRedCap |
Panasonic |
| R1-2303656 |
Discussion on UE complexity reduction |
DENSO CORPORATION |
| R1-2303721 |
Discussion on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2303836 |
UE complexity reduction for eRedCap |
Sony |
| R1-2303847 |
Considerations for Rel-18 eRedCap UE complexity reduction |
Sequans Communications |
| R1-2303883 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2303898 |
UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2303899 |
Discussion on Rel-18 RedCap UE |
NEC |
| R1-2303909 |
On eRedCap UE complexity reduction |
MediaTek Inc. |
| R1-2303933 |
FL summary #1 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2303934 |
FL summary #2 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2303935 |
FL summary #3 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2303936 |
FL summary #4 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2303937 |
FL summary #5 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2304258 |
[Draft] LS on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
Moderator (Ericsson) |
| R1-2304261 |
FL summary #6 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2304262 |
LS on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
RAN1, Ericsson |
| 9.7.1 |
Techniques in spatial and power domains |
|
| R1-2302333 |
Spatial and Power Adaptations for Network Energy Savings |
FUTUREWEI |
| R1-2302337 |
CSI enhancements for network energy saving |
Huawei, HiSilicon |
| R1-2302389 |
Spatial and power domain adaptation for network energy saving |
Panasonic |
| R1-2302393 |
Techniques in spatial and power domains |
Nokia, Nokia Shanghai Bell |
| R1-2302498 |
Discussions on NES techniques in spatial and power domain |
vivo |
| R1-2302561 |
Discussion on techniques in spatial and power domains |
OPPO |
| R1-2302613 |
Discussion on NES techniques in spatial and power domains |
Spreadtrum Communications |
| R1-2302716 |
Network Energy Saving techniques in spatial and power domain |
CATT |
| R1-2302751 |
Discussion on network energy saving techniques in spatial and power domains |
NEC |
| R1-2302809 |
Discussion on NWES techniques in spatial and power domain |
Intel Corporation |
| R1-2302912 |
Discussion on NW energy saving techniques in spatial and power domains |
Fujitsu |
| R1-2302944 |
Discussion on NES techniques in spatial and power domains |
ZTE, Sanechips |
| R1-2302995 |
Discussion on techniques in spatial and power domains |
Xiaomi |
| R1-2303024 |
Discussion on techniques in spatial and power domains |
InterDigital, Inc. |
| R1-2303030 |
Discussion on spatial/power domain adaptation for network energy saving |
China Telecom |
| R1-2303056 |
Network Energy Saving in Spatial and Power Domain |
Google |
| R1-2303141 |
Techniques in spatial and power domains |
Samsung |
| R1-2303202 |
Network energy saving techniques in spatial and power domains |
ETRI |
| R1-2303247 |
Discussion on network energy saving techniques in spatial and power domains |
CMCC |
| R1-2303309 |
Discussion on spatial and power adaptations for network energy savings |
CEWiT |
| R1-2303344 |
On NW energy saving techniques in spatial and power domains |
MediaTek Inc. |
| R1-2303379 |
Discussion of NES techniques in spatial domain and power domain |
Transsion Holdings |
| R1-2303426 |
Discussion on NES techniques in spatial and power domains |
LG Electronics |
| R1-2303496 |
Discussion on spatial and power domain enhancements to support network energy saving |
Apple |
| R1-2303531 |
Network energy saving techniques in spatial and power domains |
Lenovo |
| R1-2303603 |
Techniques in spatial and power domains |
Qualcomm Incorporated |
| R1-2303651 |
Network energy savings techniques in spatial and power domains |
AT&T |
| R1-2303722 |
Discussion on spatial and power domain enhancements for NW energy savings |
NTT DOCOMO, INC. |
| R1-2303757 |
NW energy saving techniques in spatial and power domains |
Ericsson |
| R1-2303780 |
Discussion on techniques in spatial and power domains |
ITRI |
| R1-2303813 |
Spatial Domain Adaptation for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303850 |
Discussion on spatial domain adaptation for NES |
KT Corp. |
| R1-2303910 |
Discussions on NES techniques in spatial and power domain |
vivo |
| R1-2303913 |
FL summary#1 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2303914 |
FL summary#2 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2303915 |
FL summary#3 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2303916 |
FL summary#4 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2303917 |
FL summary#5 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2303955 |
CSI enhancements for network energy saving |
Huawei, HiSilicon |
| R1-2303985 |
Discussion on NES techniques in spatial and power domains |
ZTE, Sanechips |
| R1-2304270 |
Final FL summary for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| 9.7.2 |
Enhancements on cell DTX/DRX mechanism |
|
| R1-2302334 |
Cell DTX/DRX for NES |
FUTUREWEI |
| R1-2302338 |
Cell DTX/DRX mechanism for network energy saving |
Huawei, HiSilicon |
| R1-2302390 |
Cell DTX/DRX enhancement for network energy saving |
Panasonic |
| R1-2302394 |
Enhancements on cell DTX/DRX mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2302499 |
Discussions on enhancements on cell DTX/DRX mechanism |
vivo |
| R1-2302562 |
Discussion on enhancements on cell DTX/DRX mechanism |
OPPO |
| R1-2302614 |
Discussion on enhancements on cell DTXDRX mechanism |
Spreadtrum Communications |
| R1-2302717 |
DTX/DRX for network Energy Saving |
CATT |
| R1-2302747 |
Cell DTX/DRX Configuration for Network Energy Saving |
NEC |
| R1-2302810 |
Discussion on enhancements on cell DTX/DRX mechanism |
Intel Corporation |
| R1-2302913 |
Discussion on cell DTX/DRX mechanism |
Fujitsu |
| R1-2302945 |
Discussion on cell DTX/DRX |
ZTE, Sanechips |
| R1-2302996 |
Discussions on cell DTX-DRX for network energy saving |
xiaomi |
| R1-2303025 |
Discussion on enhancements on cell DTX/DRX mechanism |
InterDigital, Inc. |
| R1-2303031 |
Discussion on mechanism of cell DTX/DRX for network energy saving |
China Telecom |
| R1-2303057 |
Network Energy Saving on Cell DTX and DRX |
Google |
| R1-2303142 |
Enhancements on cell DTX/DRX mechanism |
Samsung |
| R1-2303203 |
Enhancements on cell DTX/DRX mechanism |
ETRI |
| R1-2303248 |
Discussion on cell DTX DRX enhancements |
CMCC |
| R1-2303310 |
Discussion on cell DTX/DRX mechanism for network energy saving |
CEWiT |
| R1-2303345 |
On NW energy saving enhancements for cell DTX/DRX mechanism |
MediaTek Inc. |
| R1-2303380 |
Discussion on Enhancement on cell DTX DRX mechanism |
Transsion Holdings |
| R1-2303427 |
Discussion on cell DTX/DRX mechanism |
LG Electronics |
| R1-2303497 |
Discussion on cell DTX/DRX mechanisms |
Apple |
| R1-2303532 |
Enhancements on cell DTX/DRX mechanism |
Lenovo |
| R1-2303604 |
Enhancements on cell DTX and DRX mechanism |
Qualcomm Incorporated |
| R1-2303647 |
Discussion on cell DTX/DRX mechanism |
Rakuten Mobile, Inc |
| R1-2303723 |
Discussion on enhancements on Cell DTX/DRX mechanism |
NTT DOCOMO, INC. |
| R1-2303758 |
RAN1 aspects of cell DTX/DRX |
Ericsson |
| R1-2303781 |
Discussion on potential enhancements on cell DTX/DRX mechanism for NR |
ITRI |
| R1-2303815 |
RAN1 Considerations for Cell DTX and DRX |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2303895 |
Summary of issues for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2303896 |
Discussion summary #1 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2304014 |
Discussion summary #2 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2304015 |
Discussion summary #3 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2304119 |
Discussion summary #4 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2304120 |
Discussion summary #5 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2304239 |
Discussion summary #6 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| 9.8 |
XR Enhancements for NR |
|
| R1-2302398 |
PDCCH monitoring resumption after UL NACK |
Ericsson |
| R1-2302500 |
Draft CR on PDCCH monitoring resumption after NACK |
vivo, MediaTek, Google, Qualcomm, Panasonic, Meta, Ericsson, China Unicom, Huawei, HiSilicon, Xiaomi, Apple, China Telecom |
| R1-2302676 |
PDCCH Skipping interaction with HARQ |
CATT |
| R1-2302946 |
Discussion on PDCCH monitoring resumption after reporting NACK |
ZTE, Sanechips |
| R1-2303312 |
Draft CR for Introducing PDCCH monitoring resumption after UL NACK |
Nokia, Nokia Shanghai Bell |
| R1-2303826 |
Work Plan for Rel-18 WI on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL) |
| R1-2304041 |
Moderator Summary#1 - PDCCH monitoring resume after UL NACK |
Moderator (Ericsson) |
| R1-2304042 |
Moderator Summary#2 - PDCCH monitoring resume after UL NACK |
Moderator (Ericsson) |
| R1-2304043 |
Moderator Summary#3 - PDCCH monitoring resume after UL NACK |
Moderator (Ericsson) |
| 9.8.1 |
XR-specific capacity enhancements |
|
| R1-2302317 |
XR-specific capacity enhancements |
FUTUREWEI |
| R1-2302346 |
Discussion on CG enhancements for XR capacity |
Huawei, HiSilicon |
| R1-2302399 |
Capacity Enhancements for XR |
Ericsson |
| R1-2302429 |
Discussions on XR-specific capacity enhancements |
New H3C Technologies Co., Ltd. |
| R1-2302501 |
Discussion on XR specific capacity enhancements |
vivo |
| R1-2302563 |
Discussion on XR specific capacity enhancements |
OPPO |
| R1-2302615 |
Discussion on XR-specific capacity enhancements |
Spreadtrum Communications |
| R1-2302718 |
Design of Multiple CG Occasions |
CATT |
| R1-2302811 |
Discussion on XR specific capacity enhancement techniques |
Intel Corporation |
| R1-2302836 |
XR-specific capacity enhancements techniques |
TCL Communication Ltd. |
| R1-2302856 |
Discussion on XR-specific capacity enhancements |
Sony |
| R1-2302879 |
On XR-specific capacity enhancements techniques |
Google Inc. |
| R1-2302893 |
Discussion on XR capacity enhancement techniques |
Panasonic |
| R1-2302947 |
Discussion on XR specific capacity enhancements |
ZTE, Sanechips |
| R1-2302997 |
Discussion on XR-specific capacity enhancements |
xiaomi |
| R1-2303023 |
Discussion on XR-specific capacity enhancements |
InterDigital, Inc. |
| R1-2303143 |
Capacity improvements for XR |
Samsung |
| R1-2303190 |
Discussion on XR specific capacity enhancements |
CAICT |
| R1-2303249 |
Discussion on XR-specific capacity enhancements |
CMCC |
| R1-2303311 |
XR-specific capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303356 |
On XR capacity enhancements |
MediaTek Inc. |
| R1-2303409 |
Discussion on XR-specific capacity enhancements |
FGI |
| R1-2303428 |
Discussion on XR-specific capacity enhancements |
LG Electronics |
| R1-2303460 |
Remaining issues on XR-specific capacity enhancements |
Sharp |
| R1-2303498 |
XR-specific capacity enhancements |
Apple |
| R1-2303533 |
XR-related CG Enhancements |
Lenovo |
| R1-2303605 |
Capacity Enhancement Techniques for XR |
Qualcomm Incorporated |
| R1-2303672 |
Discussion on XR-specific capacity enhancements |
NEC |
| R1-2303724 |
Discussion on XR-specific capacity enhancements |
NTT DOCOMO, INC. |
| R1-2303827 |
Discussion on XR-specific capacity enhancements |
DENSO CORPORATION |
| R1-2304044 |
Moderator Summary#1 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2304045 |
Moderator Summary#2 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2304046 |
Moderator Summary#3 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2304047 |
Moderator Summary#4 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2304048 |
Moderator Summary#5 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| 9.9 |
NTN (Non-Terrestrial Networks) enhancements |
|
| R1-2302406 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R1-2304172 |
Session notes for 9.9 (NTN (Non-Terrestrial Networks) enhancements) |
Ad-Hoc Chair (Huawei) |
| 9.9.1 |
Coverage enhancement for NR NTN |
|
| R1-2302364 |
Discussion on coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2302433 |
Further considerations on coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2302502 |
Discussions on remaining issues of coverage enhancements in NR NTN |
vivo |
| R1-2302564 |
Discussion on coverage enhancement for NR NTN |
OPPO |
| R1-2302616 |
Discussion on coverage enhancements for NTN |
Spreadtrum Communications |
| R1-2302719 |
Further discussion on UL coverage enhancement for NR NTN |
CATT |
| R1-2302738 |
Discussion on coverage enhancement for NR NTN |
Baicells |
| R1-2302748 |
Coverage enhancement for NR NTN |
NEC |
| R1-2302812 |
On coverage enhancement for NR NTN |
Intel Corporation |
| R1-2302857 |
On coverage enhancement for NR NTN |
Sony |
| R1-2302998 |
Discussion on coverage enhancement for NR-NTN |
xiaomi |
| R1-2303014 |
On coverage enhancements for NR NTN |
Ericsson |
| R1-2303032 |
Discussion on coverage enhancement for NR NTN |
China Telecom |
| R1-2303144 |
On coverage enhancement for NR NTN |
Samsung |
| R1-2303204 |
Discussion on coverage enhancement for NR NTN |
ETRI |
| R1-2303250 |
Discussion on coverage enhancement for NR NTN |
CMCC |
| R1-2303294 |
Discussion on coverage enhancement for NTN |
ZTE |
| R1-2303351 |
UL coverage enhancements |
MediaTek Inc. |
| R1-2303499 |
On Coverage Enhancement for NR NTN |
Apple |
| R1-2303534 |
Coverage enhancements for NR NTN |
Lenovo |
| R1-2303606 |
Coverage enhancements for NR NTN |
Qualcomm Incorporated |
| R1-2303625 |
Discussion on coverage enhancement for NR-NTN |
Panasonic |
| R1-2303643 |
Views on Coverage enhancement for NR NTN |
Sharp |
| R1-2303725 |
Discussion on coverage enhancement for NR NTN |
NTT DOCOMO, INC. |
| R1-2303748 |
Discussion on coverage enhancement for NR NTN |
LG Electronics |
| R1-2303950 |
Summary #1 on 9.9.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2303951 |
Summary #2 on 9.9.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2303952 |
Summary #3 on 9.9.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2303953 |
Summary #4 on 9.9.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2304093 |
[Draft] LS on PUSCH DMRS bundling for NR NTN coverage enhancement |
Moderator (NTT DOCOMO, INC.) |
| R1-2304094 |
LS on PUSCH DMRS bundling for NR NTN coverage enhancement |
RAN1, NTT DOCOMO, INC. |
| R1-2304244 |
Summary EOM on 9.9.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2304252 |
[Draft] LS on higher layer signaling in Msg3 PUSCH for PUCCH repetition for Msg4 HARQ-ACK |
Moderator (NTT DOCOMO, INC.) |
| 9.9.2 |
Network verified UE location for NR NTN |
|
| R1-2302365 |
Discussion on network-verified UE location for NR NTN |
Huawei, HiSilicon |
| R1-2302401 |
Discussion on network verified UE location in NR NTN |
THALES |
| R1-2302402 |
FL Summary #1: Network verified UE location for NR NTN |
THALES |
| R1-2302403 |
FL Summary #2: Network verified UE location for NR NTN |
THALES |
| R1-2302404 |
FL Summary #3: Network verified UE location for NR NTN |
THALES |
| R1-2302405 |
FL Summary #4: Network verified UE location for NR NTN |
THALES |
| R1-2302434 |
Further discussion on aspects related to network verified UE location for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2302503 |
Discussions on remaining issues of UE location verification in NR NTN |
vivo |
| R1-2302565 |
Discussion on network verified UE location for NR NTN |
OPPO |
| R1-2302720 |
Further discussion on Network verified UE location for NR NTN |
CATT |
| R1-2302813 |
On network verified UE location for NR NTN |
Intel Corporation |
| R1-2302858 |
On network verified UE location for NR NTN |
Sony |
| R1-2302894 |
Discussion on Network-verified UE location for NR-NTN |
PANASONIC |
| R1-2302999 |
Discussion on the network verified location for NR-NTN |
xiaomi |
| R1-2303145 |
Network verified UE location for NR NTN |
Samsung |
| R1-2303205 |
Discussion on Network verified UE location for NR NTN |
ETRI |
| R1-2303269 |
NTN NW verified UE location |
Lenovo |
| R1-2303295 |
Discussion on network verified UE location for NR NTN |
ZTE |
| R1-2303352 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2303433 |
On Network verified UE location in NR NTN |
Ericsson Limited |
| R1-2303500 |
On Network Verified UE Location |
Apple |
| R1-2303607 |
Network verified UE location for NR NTN |
Qualcomm Incorporated |
| R1-2303659 |
Discussion on Network Verified UE Location for NR NTN |
TCL Communication Ltd. |
| R1-2303726 |
Discussion on Network verified UE location for NR NTN |
NTT DOCOMO, INC. |
| R1-2303749 |
Discussion on network verified UE location for NR NTN |
LG Electronics |
| R1-2303772 |
Network verified UE location for Rel-18 NR NTN |
Sharp |
| 9.9.3 |
Disabling of HARQ feedback for IoT NTN |
|
| R1-2302366 |
Discussion on disabling of HARQ feedback for IoT NTN |
Huawei, HiSilicon |
| R1-2302566 |
Discussion on disabling of HARQ feedback for IoT NTN |
OPPO |
| R1-2302617 |
Discussion on disabling of HARQ feedback for IoT NTN |
Spreadtrum Communications |
| R1-2302721 |
Discussion on remaining issues of disabling of HARQ feedback for IoT NTN |
CATT |
| R1-2302837 |
Disabling of HARQ feedback for NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2302859 |
Discussion on disabling of HARQ feedback for IoT-NTN |
Sony |
| R1-2303000 |
Discussion on the HARQ operation for IoT NTN |
xiaomi |
| R1-2303020 |
On disabling HARQ feedback for IoT NTN |
Ericsson |
| R1-2303146 |
Disabling of HARQ feedback for IoT NTN |
Samsung |
| R1-2303175 |
Disabling of HARQ feedback for IoT NTN |
Nordic Semiconductor ASA |
| R1-2303251 |
Discussion on disabling of HARQ feedback for IoT NTN |
CMCC |
| R1-2303296 |
Discussion on disabling of HARQ feedback for IoT-NTN |
ZTE |
| R1-2303357 |
Disabling of HARQ for IoT NTN |
MediaTek Inc. |
| R1-2303419 |
On disabling HARQ feedback for IoT-NTN |
Mavenir |
| R1-2303501 |
On HARQ Feedback Disabling for IoT NTN |
Apple |
| R1-2303542 |
Disabling of HARQ feedback for IoT NTN |
InterDigital, Inc. |
| R1-2303608 |
Disabling HARQ Feedback for IoT-NTN |
Qualcomm Incorporated |
| R1-2303627 |
Disabling of HARQ feedback for IoT NTN |
Lenovo |
| R1-2303642 |
Views on Disabling of HARQ feedback for IoT NTN |
Sharp |
| R1-2303685 |
Disabling of HARQ feedback for IoT NTN |
NEC |
| R1-2303998 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2303999 |
FLS#2 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| 9.9.4 |
Improved GNSS operations for IoT NTN |
|
| R1-2302367 |
Discussion on improved GNSS operations for IoT NTN |
Huawei, HiSilicon |
| R1-2302567 |
Discussion on improved GNSS operations for IoT NTN |
OPPO |
| R1-2302618 |
Discussion on improved GNSS operations for IoT NTN |
Spreadtrum Communications |
| R1-2302722 |
Discussion on remaining issues of improved GNSS operations for IoT NTN |
CATT |
| R1-2302749 |
On Improved GNSS Operations for IoT NTN |
NEC |
| R1-2302838 |
Enhancements for long connections in NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2303001 |
Discussion on the improved GNSS operation for IoT NTN |
xiaomi |
| R1-2303147 |
Improved GNSS operations for IoT NTN |
Samsung |
| R1-2303176 |
Improved GNSS operations for IoT NTN |
Nordic Semiconductor ASA |
| R1-2303252 |
Discussion on improved GNSS operations for IoT NTN |
CMCC |
| R1-2303297 |
Discussion on improved GNSS operation for IoT-NTN |
ZTE |
| R1-2303358 |
Improved GNSS operations for IoT NTN |
MediaTek Inc. |
| R1-2303432 |
On improved GNSS operation in IoT NTN |
Ericsson Limited |
| R1-2303502 |
On improved GNSS operations for IoT NTN |
Apple |
| R1-2303543 |
Improved GNSS operations for IoT NTN |
InterDigital, Inc. |
| R1-2303609 |
Improved GNSS Operations for IoT-NTN |
Qualcomm Incorporated |
| R1-2303628 |
Improved GNSS operations for IoT NTN |
Lenovo |
| R1-2303911 |
Feature lead summary#1 of AI 9.9.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2303912 |
Feature lead summary#2 of AI 9.9.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2304073 |
Feature lead summary#3 of AI 9.9.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2304125 |
[Draft] LS on GNSS position fix during inactive state of Connected DRX for improved GNSS operations |
Moderator (MediaTek) |
| R1-2304126 |
LS on GNSS position fix during inactive state of Connected DRX for improved GNSS operations |
RAN1, MediaTek |
| 9.10 |
Further NR mobility enhancements |
|
| R1-2304173 |
Session notes for 9.10 (Further NR mobility enhancements) |
Ad-Hoc Chair (CMCC) |
| R1-2304275 |
DRAFT LS on beam indication of target cell(s) and time gap between a PDCCH order and the corresponding PRACH transmission for LTM |
Fujitsu, MediaTek, CATT |
| R1-2304276 |
LS on beam indication of target cell(s) and time gap between a PDCCH order and the corresponding PRACH transmission for LTM |
RAN1, Fujitsu, MediaTek, CATT |
| 9.10.1 |
L1 enhancements for inter-cell beam management |
|
| R1-2302315 |
L1 enhancements for inter-cell beam management |
FUTUREWEI |
| R1-2302368 |
L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2302410 |
FL plan on L1 enhancements for LTM at RAN1#112bis-e |
Moderator (Fujitsu, MediaTek) |
| R1-2302413 |
L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2302423 |
L1 enhancements for inter-cell beam management |
ZTE |
| R1-2302504 |
Discussion on L1 enhancements for L1/L2 mobility |
vivo |
| R1-2302568 |
Discussions on Inter-cell beam management enhancement |
OPPO |
| R1-2302619 |
Discussion on L1 enhancements for inter-cell beam management |
Spreadtrum Communications |
| R1-2302730 |
L1 enhancements for inter-cell beam management |
Lenovo |
| R1-2302752 |
Discussion on L1 enhancements for inter-cell beam management |
NEC |
| R1-2302819 |
L1 Enhancements for Inter-cell Beam Management |
Intel Corporation |
| R1-2302830 |
Layer-1 Enhancements for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2302860 |
Discussion on L1 enhancements for inter-cell beam management |
Sony |
| R1-2302867 |
Discussion on L1 enhancements for L1L2-triggered mobility |
Panasonic |
| R1-2302870 |
Discussion on L1 enhancements for inter-cell beam management |
CATT |
| R1-2302914 |
Views on L1 enhancements for inter-cell beam management |
Fujitsu |
| R1-2302966 |
Discussion on L1 enhancements for inter-cell beam management |
Xiaomi |
| R1-2303021 |
FL summary 1 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2303022 |
FL summary 2 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2303082 |
Enhancements on inter-cell beam management for mobility |
LG Electronics |
| R1-2303148 |
On L1 enhancements for inter-cell beam management |
Samsung |
| R1-2303253 |
Discussion on L1 enhancements for inter-cell beam management |
CMCC |
| R1-2303288 |
Discussion on L1 enhancements for inter-cell mobility |
KDDI Corporation |
| R1-2303331 |
L1 enhancements for inter-cell beam management |
MediaTek Inc. |
| R1-2303410 |
Discussion on L1 enhancements for inter-cell beam management |
FGI |
| R1-2303455 |
Discussion on L1 enhancements for inter-cell beam management |
InterDigital, Inc. |
| R1-2303503 |
L1 enhancements to inter-cell beam management |
Apple |
| R1-2303518 |
Discussion on L1 enhancements for inter-cell beam management |
Google |
| R1-2303610 |
L1 Enhancements for Inter-Cell Beam Management |
Qualcomm Incorporated |
| R1-2303727 |
Discussion on L1 enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2304090 |
FL summary 3 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2304091 |
FL summary 4 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| R1-2304274 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu, MediaTek) |
| 9.10.2 |
Timing advance management to reduce latency |
|
| R1-2302316 |
On TA acquisition schemes of UE based RACH-less and early RACH with RAR |
FUTUREWEI |
| R1-2302369 |
Timing advance management to reduce latency |
Huawei, HiSilicon |
| R1-2302414 |
Timing advance management for L1/L2 Mobility |
Ericsson |
| R1-2302424 |
Enhancements on TA management to reduce latency |
ZTE |
| R1-2302505 |
Discussion on TA management for L1/L2 mobility |
vivo |
| R1-2302569 |
Discussions on Timing Advance Management |
OPPO |
| R1-2302620 |
Discussion on timing advance management to reduce latency |
Spreadtrum Communications |
| R1-2302731 |
Timing advancement management for L1L2 mobility |
Lenovo |
| R1-2302814 |
On Timing Advance Management |
Intel Corporation |
| R1-2302831 |
Timing Advance Management for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2302869 |
Discussion on time advance management to reduce latency |
CATT |
| R1-2302967 |
Discussion on Timing advance management |
xiaomi |
| R1-2303083 |
Enhancements on TA management for mobility |
LG Electronics |
| R1-2303149 |
Candidate cell TA acquisition for NR L1/L2 mobility enhancement |
Samsung |
| R1-2303254 |
Discussion on timing advance management to reduce latency |
CMCC |
| R1-2303260 |
Discussion on Timing advance management to reduce latency |
CAICT |
| R1-2303290 |
Discussion on Timing advance management to reduce latency |
KDDI Corporation |
| R1-2303362 |
UL Timing management to reduce handover latency |
MediaTek Inc. |
| R1-2303381 |
Discussion on TA management for L1/L2 mobility |
Transsion Holdings |
| R1-2303456 |
Discussion on timing advance management to reduce latency |
InterDigital, Inc. |
| R1-2303504 |
Timing advance management for L1/L2 Mobility |
Apple |
| R1-2303519 |
Discussion on timing advance management to reduce latency |
Google |
| R1-2303611 |
TA management to reduce latency for L1/L2 based mobility |
Qualcomm Incorporated |
| R1-2303728 |
Timing advance enhancement for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2303782 |
Discussion on TA management to reduce latency |
ITRI |
| R1-2303875 |
Candidate cell TA acquisition for NR L1/L2 mobility enhancement |
Samsung R&D Institute India |
| R1-2303984 |
Moderator summary on Timing advance management for LTM: Round 1 |
Moderator (CATT) |
| R1-2304060 |
Moderator summary on Timing advance management for LTM: Round 2 |
Moderator (CATT) |
| R1-2304069 |
Moderator summary on Timing advance management for LTM: Round 3 |
Moderator (CATT) |
| R1-2304135 |
Moderator summary on Timing advance management for LTM: Round 4 |
Moderator (CATT) |
| 9.11.1 |
Evaluation on low power WUS |
|
| R1-2302331 |
Evaluation of LP-WUS and Performance Results |
FUTUREWEI |
| R1-2302339 |
Evaluations for LP-WUS |
Huawei, HiSilicon |
| R1-2302506 |
Evaluation methodologies for R18 LP-WUS/WUR |
vivo |
| R1-2302570 |
Evaluation for lower power wake-up signal |
OPPO |
| R1-2302621 |
Discussion on evaluation on low power WUS |
Spreadtrum Communications |
| R1-2302687 |
Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR |
CATT |
| R1-2302815 |
Evaluations on LP-WUS |
Intel Corporation |
| R1-2302827 |
Discussion on evaluation on LP-WUS |
InterDigital, Inc. |
| R1-2302861 |
Evaluation of low power WUS |
Sony |
| R1-2302890 |
Low power WUS Evaluation Methodology |
Nokia, Nokia Shanghai Bell |
| R1-2302948 |
Evaluation on LP-WUS |
ZTE, Sanechips |
| R1-2302968 |
Evaluation on low power WUS |
xiaomi |
| R1-2303150 |
Evaluation on LP-WUS/WUR |
Samsung |
| R1-2303332 |
Evaluation on low power WUS |
MediaTek Inc. |
| R1-2303429 |
Discussion on evaluation for LP-WUS |
LG Electronics |
| R1-2303505 |
On performance evaluation for low power wake-up signal |
Apple |
| R1-2303537 |
On LP-WUS evaluation |
Nordic Semiconductor ASA |
| R1-2303612 |
Evaluation methodology for LP-WUS |
Qualcomm Incorporated |
| R1-2303759 |
Low power WUS evaluations |
Ericsson |
| R1-2303897 |
Evaluation methodologies for R18 LP-WUS/WUR |
vivo |
| R1-2304057 |
Evaluation on low power WUS |
MediaTek Inc. |
| R1-2304076 |
FL summary #1 of evaluation methodologies on LP-WUS/WUR |
Moderator (vivo) |
| R1-2304150 |
FL summary #2 of evaluation methodologies on LP-WUS/WUR |
Moderator (vivo) |
| R1-2304151 |
FL summary #1 of evaluation results on LP-WUS/WUR |
Moderator (vivo) |
| R1-2304287 |
Final summary of evaluation methodologies on LP-WUS/WUR |
Moderator (vivo) |
| 9.11.2 |
Low power WUS receiver architectures |
|
| R1-2302340 |
Discussion on architecture of LP-WUS receiver |
Huawei, HiSilicon |
| R1-2302391 |
Discussion on low power wake up receiver architectures |
Panasonic |
| R1-2302507 |
Discussion on low power wake-up receiver architecture |
vivo |
| R1-2302571 |
Discussion on low power WUS receiver |
OPPO |
| R1-2302688 |
Low-Power WUS receiver Architectures and its performance |
CATT |
| R1-2302816 |
Discussion on LP-WUS receiver architecture |
Intel Corporation |
| R1-2302828 |
Discussion on LP-WUS receiver architectures |
InterDigital, Inc. |
| R1-2302891 |
Low Power WUS receiver architectures |
Nokia, Nokia Shanghai Bell |
| R1-2302949 |
LP-WUS receiver architectures |
ZTE, Sanechips |
| R1-2303151 |
Receiver architecture for LP-WUS |
Samsung |
| R1-2303333 |
Low power WUS receiver architectures |
MediaTek Inc. |
| R1-2303506 |
On low power wake-up receiver architectures |
Apple |
| R1-2303613 |
Receiver architecture for LP-WUS |
Qualcomm Incorporated |
| R1-2303729 |
Discussion on low power WUS receiver architectures |
NTT DOCOMO, INC. |
| R1-2303760 |
Low power WUS receiver architectures |
Ericsson |
| R1-2303941 |
Summary #1 on LP WUR architectures |
Moderator (Apple) |
| R1-2303942 |
Summary #2 on LP WUR architectures |
Moderator (Apple) |
| R1-2303943 |
Summary #3 on LP WUR architectures |
Moderator (Apple) |
| R1-2304249 |
Summary #4 on LP WUR architectures |
Moderator (Apple) |
| R1-2304250 |
[Draft] Reply LS to RAN4 on LP WUR architectures |
Moderator (Apple) |
| R1-2304251 |
Reply LS to RAN4 on LP WUR architectures |
RAN1, Apple |
| R1-2304288 |
[Draft] Reply LS to RAN4 on LP WUR architectures |
Moderator (Apple) |
| 9.11.3 |
L1 signal design and procedure for low power WUS |
|
| R1-2302332 |
LP-WUS Physical Signal Design |
FUTUREWEI |
| R1-2302341 |
Signal design and procedure for LP-WUS |
Huawei, HiSilicon |
| R1-2302392 |
Discussion on low power wake up signal design |
Panasonic |
| R1-2302409 |
L1 signal design and procedure for low power WUS |
TCL Communication Ltd. |
| R1-2302508 |
Discussion on physical signal and procedure for low power WUS |
vivo |
| R1-2302572 |
Design consideration on lower power wake-up signal and procedure |
OPPO |
| R1-2302622 |
Discussion on L1 signal design and procedure for low power WUS |
Spreadtrum Communications |
| R1-2302689 |
Physical layer signals/procedures and higher layer protocol for Low-Power WUR |
CATT |
| R1-2302817 |
Discussions on L1 signal design and procedure for LP-WUS |
Intel Corporation |
| R1-2302829 |
Discussion on L1 signal design and procedure for LP-WUS |
InterDigital, Inc. |
| R1-2302862 |
On L1 signal design and procedures for low power WUS |
Sony |
| R1-2302892 |
L1 signal design and procedures for low power WUS |
Nokia, Nokia Shanghai Bell |
| R1-2302950 |
LP-WUS design and related procedure |
ZTE, Sanechips |
| R1-2302969 |
Discussions on L1 signal design and procedure for low power WUS |
xiaomi |
| R1-2303033 |
Discussion on signal design and procedure for LP-WUS |
China Telecom |
| R1-2303061 |
L1 signal design and procedure for low-power WUS |
Sharp |
| R1-2303152 |
Signal design and procedure for LP-WUS |
Samsung |
| R1-2303255 |
Discussion on L1 signal design and procedure for LP-WUS |
CMCC |
| R1-2303334 |
L1 signal design and procedure for low power WUS |
MediaTek Inc. |
| R1-2303421 |
Discussion on L1 signal design and procedure for low power WUS |
EURECOM |
| R1-2303430 |
Discussion on L1 signal design and procedure for LP-WUS |
LG Electronics |
| R1-2303507 |
On the L1 signal design and procedures for low power wake-up signal |
Apple |
| R1-2303538 |
On LP-WUS signal design |
Nordic Semiconductor ASA |
| R1-2303614 |
L1 signal design and procedures for LP-WUR |
Qualcomm Incorporated |
| R1-2303673 |
Discussion on L1 signal design and procedure for LP-WUS |
NEC |
| R1-2303730 |
Discussion on L1 signal design and procedure for low power WUS |
NTT DOCOMO, INC. |
| R1-2303761 |
L1 signal design and procedure for low power WUS |
Ericsson |
| R1-2303808 |
Discussion on the L1 signal design and procedure for low power WUS |
Lenovo |
| R1-2303828 |
L1 signal design and procedure for low power WUS |
TCL Communication Ltd. |
| R1-2303894 |
Discussion on low power wake up signal design |
Panasonic |
| R1-2303900 |
Discussion on signal design and procedure for LP-WUS |
China Telecom |
| R1-2304036 |
Summary#1 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2304095 |
Summary#2 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2304144 |
Summary#3 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2304248 |
Summary#4 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2304269 |
Collection of LLS results on low power WUS |
Moderator (Nordic Semiconductor ASA) |
| 9.12 |
Further NR coverage enhancements |
|
| R1-2304174 |
Session notes for 9.12 (Further NR coverage enhancements) |
Ad-Hoc Chair (CMCC) |
| 9.12.1 |
PRACH coverage enhancements |
|
| R1-2302350 |
Discussion on PRACH coverage enhancements |
Huawei, HiSilicon |
| R1-2302509 |
Discussions on remaining issues of PRACH coverage enhancements |
vivo |
| R1-2302573 |
PRACH coverage enhancements |
OPPO |
| R1-2302623 |
Discussion on PRACH coverage enhancements |
Spreadtrum Communications |
| R1-2302690 |
PRACH coverage enhancements |
CATT |
| R1-2302759 |
Discussion on PRACH coverage enhancements |
ZTE |
| R1-2302818 |
Discussions on PRACH coverage enhancement |
Intel Corporation |
| R1-2302834 |
PRACH coverage enhancements |
TCL Communication Ltd. |
| R1-2302835 |
PRACH coverage enhancements |
TCL Communication Ltd. |
| R1-2302863 |
PRACH Coverage Enhancement using Multiple PRACH Transmissions |
Sony |
| R1-2302880 |
PRACH coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2302885 |
Discussion on PRACH coverage enhancements |
Panasonic |
| R1-2302915 |
Discussion on PRACH coverage enhancements |
Fujitsu |
| R1-2302970 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2303034 |
Discussion on PRACH coverage enhancement |
China Telecom |
| R1-2303086 |
Discussion on solutions for NR PRACH coverage enhancement |
Mavenir |
| R1-2303090 |
PRACH coverage enhancements |
Lenovo |
| R1-2303153 |
PRACH coverage enhancements |
Samsung |
| R1-2303206 |
PRACH coverage enhancements |
ETRI |
| R1-2303209 |
Discussion on PRACH coverage enhancements |
Quectel |
| R1-2303256 |
Discussion on PRACH coverage enhancements |
CMCC |
| R1-2303353 |
On PRACH coverage enhancements |
MediaTek Inc. |
| R1-2303411 |
Discussion on CFRA for Multiple PRACH Transmission |
FGI |
| R1-2303453 |
Discussion on PRACH coverage enhancements |
InterDigital, Inc. |
| R1-2303508 |
Discussion on PRACH coverage enhancement |
Apple |
| R1-2303615 |
PRACH Coverage Enhancements |
Qualcomm Incorporated |
| R1-2303640 |
Views on multiple PRACH transmission for coverage enhancement |
Sharp |
| R1-2303661 |
Discussion on PRACH coverage enhancement |
Ericsson |
| R1-2303681 |
Discussion on PRACH coverage enhancement |
NEC |
| R1-2303731 |
Discussion on PRACH coverage enhancements |
NTT DOCOMO, INC. |
| R1-2303750 |
Discussion on PRACH repeated transmission for NR coverage enhancement |
LG Electronics |
| R1-2303959 |
FL Summary#1 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2303960 |
FL Summary#2 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2303961 |
FL Summary#3 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2303962 |
FL Summary#4 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2304070 |
[Draft] LS on PRACH coverage enhancement |
China Telecom |
| R1-2304141 |
LS on PRACH coverage enhancement |
RAN1, China Telecom |
| R1-2304234 |
Final summary on PRACH coverage enhancements |
Moderator (China Telecom) |
| 9.12.2 |
Power domain enhancements |
|
| R1-2302351 |
Discussion on coverage enhancement in power domain |
Huawei, HiSilicon |
| R1-2302510 |
Discussions on remaining issues of power domain enhancements |
vivo |
| R1-2302574 |
The study of power domain enhancements |
OPPO |
| R1-2302624 |
Discussion on power domain enhancements |
Spreadtrum Communications |
| R1-2302691 |
Discussion on MPR/PAR reduction enhancements |
CATT |
| R1-2302760 |
Discussion on power domain enhancements |
ZTE |
| R1-2302787 |
Discussions on power domain enhancement |
Intel Corporation |
| R1-2302864 |
Considerations on tone reservation for PAPR reduction |
Sony |
| R1-2302881 |
RAN1 impacts for power domain enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2302886 |
Discussion on power domain enhancements |
Panasonic |
| R1-2302916 |
Discussion on Power domain enhancements |
Fujitsu |
| R1-2302971 |
Discussion on power domain enhancements |
Xiaomi |
| R1-2303035 |
Discussion on power domain enhancements |
China Telecom |
| R1-2303091 |
Power domain enhancements |
Lenovo |
| R1-2303154 |
Power domain enhancements |
Samsung |
| R1-2303257 |
Discussion on power domain enhancements |
CMCC |
| R1-2303354 |
Views on power domain enhancements |
MediaTek Inc. |
| R1-2303454 |
Discussion on power domain enhancements |
InterDigital, Inc. |
| R1-2303509 |
Discussion on power domain coverage enhancement |
Apple |
| R1-2303616 |
Power-domain enhancements |
Qualcomm Incorporated |
| R1-2303658 |
Discussion on power domain enhancements |
Google Inc. |
| R1-2303662 |
Power Domain Enhancement Schemes and Performance |
Ericsson |
| R1-2303732 |
Discussion on power domain enhancements |
NTT DOCOMO, INC. |
| R1-2303751 |
Discussion on Power Domain Enhancements |
LG Electronics |
| R1-2303767 |
Power domain enhancements for Rel-18 CovEnh |
Sharp |
| R1-2303777 |
DMRS design for power domain enhancements |
Indian Institute of Tech (H) |
| R1-2303921 |
FL summary of power domain enhancements (AI 9.12.2) |
Moderator (Nokia) |
| R1-2303922 |
FL summary #2 of power domain enhancements (AI 9.12.2) |
Moderator (Nokia) |
| R1-2303923 |
FL summary #3 of power domain enhancements (AI 9.12.2) |
Moderator (Nokia) |
| R1-2303924 |
FL summary #4 of power domain enhancements (AI 9.12.2) |
Moderator (Nokia) |
| R1-2303925 |
Final FL summary of power domain enhancements (AI 9.12.2) |
Moderator (Nokia) |
| 9.12.3 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
|
| R1-2302352 |
Discussion on dynamic waveform switching for coverage enhancement |
Huawei, HiSilicon |
| R1-2302511 |
Discussions on remaining issues of dynamic waveform switching |
vivo |
| R1-2302575 |
Considerations on dynamic switching between DFT-S-OFDM and CP-OFDM |
OPPO |
| R1-2302625 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Spreadtrum Communications |
| R1-2302692 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
CATT |
| R1-2302761 |
Discussion on dynamic waveform switching |
ZTE |
| R1-2302788 |
Dynamic switching between DFT-S-OFDM and CP-OFDM waveform |
Intel Corporation |
| R1-2302865 |
Considerations on dynamic waveform switching for various PUSCH types |
Sony |
| R1-2302882 |
Dynamic switching between DFT-s-OFDM and CP-OFDM |
Nokia, Nokia Shanghai Bell |
| R1-2302972 |
Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM |
Xiaomi |
| R1-2303018 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2303036 |
Discussion on dynamic waveform switching between DFT-s-OFDM and CP-OFDM |
China Telecom |
| R1-2303039 |
Discussion on dynamic waveform switching |
Panasonic |
| R1-2303085 |
Discussion on solutions for NR dynamic switching between DFT-S-OFDM and CP-OFDM |
Mavenir |
| R1-2303092 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Lenovo |
| R1-2303155 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Samsung |
| R1-2303207 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
ETRI |
| R1-2303258 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
CMCC |
| R1-2303355 |
Dynamic switching between waveforms |
MediaTek Inc. |
| R1-2303382 |
Discussion of dynamic switching between DFT-S-OFDM and CP-OFDM |
Transsion Holdings |
| R1-2303510 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Apple |
| R1-2303617 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Qualcomm Incorporated |
| R1-2303641 |
Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh |
Sharp |
| R1-2303644 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Google Inc. |
| R1-2303663 |
Discussion on Dynamic UL Waveform Switching |
Ericsson |
| R1-2303682 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NEC |
| R1-2303733 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NTT DOCOMO, INC. |
| R1-2303752 |
Discussion on dynamic waveform switching for NR coverage enhancement |
LG Electronics |
| R1-2303788 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2303789 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2303790 |
Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2304121 |
Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2304222 |
Summary #5 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| 9.13 |
NR support for UAV (Uncrewed Aerial Vehicles) |
|
| R1-2304175 |
Session notes for 9.13 (NR support for UAV (Uncrewed Aerial Vehicles) |
Ad-Hoc Chair (Huawei) |
| 9.13.1 |
UE capability and RRC signaling for UAV beamforming |
|
| R1-2302345 |
UE capability and RRC signaling for UAV beamforming |
Huawei, HiSilicon |
| R1-2302512 |
Discussion on UE capability and RRC signaling for UAV beamforming |
vivo |
| R1-2302732 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Lenovo |
| R1-2302866 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Sony |
| R1-2303156 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Samsung |
| R1-2303298 |
Discussion on UE capability for UAV beamforming |
ZTE |
| R1-2303418 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Nokia, Nokia Shanghai Bell |
| R1-2303511 |
On UE capability and RRC signaling for UAV beamforming |
Apple |
| R1-2303618 |
Discussion of UE capability and RRC signaling for UAV beamforming |
Qualcomm Incorporated |
| R1-2303734 |
Discussion on UE capability and RRC signaling for UAV beamforming |
NTT DOCOMO, INC. |
| R1-2303785 |
On UAV beamforming capabilities |
Ericsson |
| R1-2304038 |
Summary#1 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| R1-2304039 |
Summary#2 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| R1-2304040 |
Summary#3 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| 9.15 |
Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology |
|
| R1-2302871 |
SI work plan for Study on self-evaluation towards the IMT-2020 submission of the 3GPP Satellite Radio Interface Technology |
Ericsson |
| R1-2304176 |
Session notes for 9.15 (Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology) |
Ad-Hoc Chair (Huawei) |
| 9.15.1 |
Evaluation methodology |
|
| R1-2302384 |
Evaluation methodology of IMT-2020 satellite |
Huawei, HiSilicon |
| R1-2302435 |
Discussion on self-evaluation methodology for potential 3GPP submission of IMT-2020 Satellite Radio Interface Technology |
Nokia, Nokia Shanghai Bell |
| R1-2302693 |
Considerations on evaluation methodology for IMT2020 Satellite RIT |
CATT,CAICT |
| R1-2302774 |
Discussion on self-evaluation methodology for IMT-2020 satellite radio interface |
OPPO |
| R1-2302873 |
Assumptions for the Self-Evaluation for the Satellite Component of IMT-2020 |
Ericsson, Qualcomm, Thales |
| R1-2303157 |
On evaluation methodology for IMT-2020 Satellite |
Samsung |
| R1-2303299 |
Discussion on the evaluation methodology of Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite |
ZTE |
| R1-2303346 |
Evaluation methodology for IMT-2020 satellite |
MediaTek Inc. |
| R1-2303619 |
eMBB Spectral Efficiency SLS parameters and assumptions |
Qualcomm Incorporated |
| R1-2303626 |
Discussion on simulation assumptions for self-evaluation of IMT-2020 satellite radio interface technology |
Panasonic |
| R1-2304008 |
Feature lead summary #1 on evaluation methodology for IMT-2020 Satellite |
Moderator (Qualcomm) |
| R1-2304009 |
Feature lead summary #2 on evaluation methodology for IMT-2020 Satellite |
Moderator (Qualcomm) |
| R1-2304118 |
Feature lead summary #3 on evaluation methodology for IMT-2020 Satellite |
Moderator (Qualcomm) |
| R1-2304123 |
Feature lead summary #4 on evaluation methodology for IMT-2020 Satellite |
Moderator (Qualcomm) |
| 9.16 |
TEIs |
|
| R1-2302385 |
Rel-18 TEI proposal on HARQ multiplexing on PUSCH |
Huawei, HiSilicon, Ericsson, China Unicom |
| R1-2302400 |
RAN1 TEI proposals for Release 18 |
Nokia, Nokia Shanghai Bell |
| R1-2302513 |
Rel-18 TEI proposals |
vivo |
| R1-2302576 |
TEI on the introduction of a UE capability with up to 6-layer DL MIMO |
OPPO |
| R1-2302762 |
On PUSCH repetition type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI |
ZTE, China Telecom, Sanechips |
| R1-2302973 |
Rel-18 TEI on pathloss RS for Type 1 CG PUSCH |
xiaomi |
| R1-2303620 |
Rel-18 RAN1 TEI proposals |
Qualcomm Incorporated |
| R1-2303851 |
Proposals for Rel-18 TEI |
Ericsson, Verizon, Qualcomm |
| R1-2304077 |
Summary #1 on Rel-18 TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2304108 |
Summary #2 on Rel-18 TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2304223 |
Summary #3 on Rel-18 TEIs |
Moderator (NTT DOCOMO, INC.) |
| 9.17 |
UE features |
|
| R1-2304227 |
Initial RAN1 UE features list for Rel-18 NR after RAN1#112bis-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2304282 |
Initial RAN1 UE features list for Rel-18 NR after RAN1#112bis-e |
Moderators (AT&T, NTT DOCOMO, INC.) |
| 9.17.4 |
UE features for NR NCR |
|
| R1-2302514 |
Discussion on UE features for NCR |
vivo |
| R1-2302898 |
Initial views on UE features for Network Controlled Repeaters |
Nokia, Nokia Shanghai Bell |
| R1-2302917 |
Discussion on UE features for NR NCR |
Fujitsu |
| R1-2303158 |
Discussion on UE features for NR NCR |
Samsung |
| R1-2303177 |
Discussion on other aspects of NCR |
RAN1, Comba |
| R1-2303208 |
Discussion on NCR features |
ETRI |
| R1-2303259 |
Discussion on UE feature of NR NCR |
CMCC |
| R1-2303293 |
Discussion on the UE feature for NCR |
Rapporteur(ZTE) |
| R1-2303652 |
Summary of UE features for NR NCR |
Moderator (AT&T) |
| R1-2303753 |
Discussion on UE features for NR NCR |
LG Electronics |
| R1-2303862 |
UE features for NCR |
Huawei, HiSilicon |
| R1-2303872 |
Legacy UE features for NCR |
Ericsson |
| R1-2304216 |
Session Notes of AI 9.17.4 |
Ad-Hoc Chair (AT&T) |
| 9.17.10 |
UE features for MC enhancements |
|
| R1-2302515 |
Discussion on UE features for Multi-carrier enhancements |
vivo |
| R1-2302577 |
Discussion on UE features for multi-carrier enhancement |
OPPO |
| R1-2302763 |
Discussion on UE feature for MC enhancements |
ZTE |
| R1-2302897 |
Initial views on UE features for Multi-carrier Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303159 |
Discussion on UE features for multi-carrier enhancements |
Samsung |
| R1-2303343 |
On UE feature discussion for Rel-18 MC enhancements |
MediaTek Inc. |
| R1-2303512 |
Initial views on UE features for Rel-18 multi-carrier enhancements |
Apple |
| R1-2303621 |
UE features for MC enhancements |
Qualcomm Incorporated |
| R1-2303735 |
Draft RAN1 UE features list for Rel-18 Multi-carrier enhancements for NR |
NTT DOCOMO, INC. |
| R1-2303736 |
Discussion on UE features for MC enhancements |
NTT DOCOMO, INC. |
| R1-2303762 |
UE features for MCE |
Ericsson |
| R1-2303863 |
UE features for MC enhancements |
Huawei, HiSilicon |
| R1-2304213 |
Summary on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2304224 |
Session Notes for 9.17.10 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 9.17.14 |
UE features for eDSS |
|
| R1-2302516 |
Discussion on UE features for eDSS |
vivo |
| R1-2302578 |
Discussion on UE features for Rel-18 eDSS |
OPPO |
| R1-2302626 |
Discussion on UE features for eDSS |
Spreadtrum Communications |
| R1-2302764 |
Discussion on UE feature for eDSS |
ZTE |
| R1-2302896 |
Initial views on UE features for eDSS |
Nokia, Nokia Shanghai Bell |
| R1-2303160 |
Discussion on UE features for eDSS |
Samsung |
| R1-2303342 |
UE feature discussion for Rel-18 eDSS |
MediaTek Inc. |
| R1-2303513 |
On Rel-18 eDSS UE features |
Apple |
| R1-2303622 |
UE features for eDSS |
Qualcomm Incorporated |
| R1-2303737 |
Discussion on UE features for eDSS |
NTT DOCOMO, INC. |
| R1-2303763 |
Initial UE feature list for Rel18 DSS Enhancements WI |
WI Rapporteur(Ericsson) |
| R1-2303764 |
UE features for Rel18 DSS Enhancements |
Ericsson |
| R1-2303864 |
UE features for eDSS |
Huawei, HiSilicon |
| R1-2304214 |
Summary on UE features for eDSS |
Moderator (NTT DOCOMO, INC.) |
| R1-2304225 |
Session Notes for 9.17.14 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 9.17.15 |
UE features for BWP without restriction |
|
| R1-2302415 |
UE features for BWP without restriction |
Ericsson |
| R1-2302517 |
Discussion on UE features for BWP without restriction |
vivo |
| R1-2302765 |
Discussion on UE feature for BWP without restriction |
ZTE |
| R1-2302876 |
Preliminary UE Features List for BWP Without Restriction |
Vodafone Italia SpA, vivo |
| R1-2302895 |
Initial views on UE features for BWP without restriction |
Nokia, Nokia Shanghai Bell |
| R1-2303350 |
UE features for BWP without restriction |
MediaTek Inc. |
| R1-2303623 |
UE features for BWP without restriction |
Qualcomm Incorporated |
| R1-2303653 |
Summary of UE features for BWP without restriction |
Moderator (AT&T) |
| R1-2303738 |
Discussion on UE features for BWP without restriction |
NTT DOCOMO, INC. |
| R1-2303865 |
UE features for BWP without restriction |
Huawei, HiSilicon |
| R1-2304217 |
Session Notes of AI 9.17.15 |
Ad-Hoc Chair (AT&T) |
| 9.17.16 |
Other |
|
| R1-2302899 |
Initial views on UE features for TEI-18 |
Nokia, Nokia Shanghai Bell |
| R1-2302920 |
UE feature for agreed TEI-18 on SR periodicity |
Ericsson |
| R1-2303283 |
UE feature on support of 1-symbol PRS |
ZTE |
| R1-2304215 |
Summary on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2304226 |
Session Notes for 9.17.16 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 9.18 |
Other |
|
| R1-2302518 |
Discussion on Rel-18 Multi-carrier enhancements, eDSS, NCR and BWP without restriction |
vivo |
| R1-2302579 |
Discussion on remaining issues in Rel-18 eDSS and MC-enh |
OPPO |
| R1-2302740 |
Introduction of dynamic spectrum sharing enhancements |
Ericsson LM |
| R1-2302741 |
Introduction of multi-carrier enhancements |
Ericsson LM |
| R1-2302743 |
Introduction of additional PRS configurations |
Ericsson LM |
| R1-2302820 |
On remaining issues for R18 NCR and MC-Enh |
Intel Corporation |
| R1-2302884 |
On MC-enhancements, BWP without restrictions and eDSS |
Nokia, Nokia Shanghai Bell |
| R1-2303012 |
Introduction of multi-carrier enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2303013 |
Introduction of UL Tx switching across up to 4 bands |
Nokia, Nokia Shanghai Bell |
| R1-2303019 |
Introduction of specification support for BandWidth Part operation without restriction in NR |
Nokia, Nokia Shanghai Bell |
| R1-2303161 |
Introduction of multi-carrier enhancements for NR |
Samsung |
| R1-2303162 |
Introduction of dynamic spectrum sharing (DSS) enhancements |
Samsung |
| R1-2303163 |
Introduction of network controlled repeaters |
Samsung |
| R1-2303164 |
Correction for BWP operation without restriction |
Samsung |
| R1-2303166 |
Discussion on remaining issues for eDSS and MC |
Spreadtrum Communications |
| R1-2303284 |
On the agreed TEI proposal of 1-symbol PRS |
ZTE |
| R1-2303292 |
Discussion on the higher layer parameters for NCR |
Rapporteur(ZTE) |
| R1-2303327 |
On maintenance for MC-Enhancement |
MediaTek Inc. |
| R1-2303383 |
Preliminary Higher Layer Parameters list for BWP Without Restriction for Rel-18 NR |
Vodafone Italia SpA, vivo |
| R1-2303404 |
Draft CRs and higher layer signalling for others |
ZTE |
| R1-2303431 |
Remaining aspects on Rel-18 NCR and Multi-carrier enhancements |
LG Electronics |
| R1-2303514 |
On remaining issues for Rel-18 multi-carrier enhancements |
Apple |
| R1-2303624 |
Views on MC-Enh, BWP without restriction, and eDSS |
Qualcomm Incorporated |
| R1-2303739 |
Draft RAN1 higher layer parameters list for Rel-18 Multi-carrier enhancements for NR |
NTT DOCOMO, INC. |
| R1-2303740 |
Discussion on remaining issues on MC enhancements, eDSS and BWP without restriction |
NTT DOCOMO, INC. |
| R1-2303765 |
Initial higher layer parameter list for Rel18 DSS Enhancements WI |
WI Rapporteur(Ericsson) |
| R1-2303766 |
Discussion on MCE, eDSS and NCR for Rel18 |
Ericsson |
| R1-2303803 |
Introduction of Rel-18 Multi-carrier enhancements |
Huawei, HiSilicon |
| R1-2303804 |
Introduction of Rel-18 network controlled repeaters |
Huawei, HiSilicon |
| R1-2303858 |
Remaining issues for eDSS, NCR, multicarrier enhancements |
Huawei, HiSilicon |
| R1-2304003 |
Introduction of dynamic spectrum sharing enhancements |
Nokia |
| R1-2304020 |
Introduction of Rel-18 network controlled repeaters |
NTT DOCOMO, INC. |
| R1-2304021 |
Summary of discussion on draft 38.201 CR for NCR |
Moderator (NTT DOCOMO, INC.) |
| R1-2304190 |
Summary of email discussions [112bis-e-R18-38.213-BWP_wor] |
Moderator (Samsung) |
| R1-2304191 |
Summary of email discussions [112bis-e-R18-38.213-NR_eDSS] |
Moderator (Samsung) |
| R1-2304192 |
Summary of email discussions [112bis-e-R18-38.213-NR_NCR] |
Moderator (Samsung) |
| R1-2304193 |
Summary of email discussions [112bis-e-R18-38.213-NR_MC_enh] |
Moderator (Samsung) |
| R1-2304194 |
Introduction of BWP operation without restriction |
Moderator (Samsung) |
| R1-2304195 |
Introduction of dynamic spectrum sharing (DSS) enhancements |
Samsung |
| R1-2304196 |
Introduction of multi-carrier enhancements |
Samsung |
| R1-2304197 |
Introduction of Network Controlled Repeaters |
Samsung |
| R1-2304201 |
Introduction of multi-carrier enhancements |
Nokia |
| R1-2304202 |
Introduction of dynamic spectrum sharing enhancements |
Nokia |
| R1-2304203 |
Introduction of specification support for BandWidth Part operation without restriction in NR |
Nokia |
| R1-2304204 |
Summary of email discussion on Multi-Cell Scheduling in [112bis-e-R18-38.214-MC_Enh] |
Moderator (Nokia) |
| R1-2304205 |
Summary of email discussion on the introduction of UL Tx switching across up to 4 bands in [112bis-e-R18-38.214-MC_Enh] |
Moderator (Nokia) |
| R1-2304206 |
Summary of email discussion on the introduction of 1 symbol PRS [112bis-e-R18-38.214-TEI18] |
Moderator (Nokia) |
| R1-2304207 |
Summary of email discussion on eDSS enhancements [112bis-e-R18-38.214-eDSS] |
Moderator (Nokia) |
| R1-2304220 |
Summary of Email discussion on Rel-18 RRC parameters for LS to RAN2 and RAN3 |
Moderator (Ericsson) |
| R1-2304221 |
Collection of updated higher layers parameter list for Rel-18 NR |
Moderator (Ericsson) |
| R1-2304238 |
Consolidated higher layers parameter list for Rel-18 NR |
Moderator (Ericsson) |
| R1-2304241 |
Summary#1 of discussion on MAC CE parameter for NCR |
Moderator (ZTE) |
| R1-2304263 |
Introduction of Rel-18 Multi-carrier enhancements |
Huawei |
| R1-2304264 |
Introduction of Rel-18 network controlled repeaters |
Huawei |
| R1-2304265 |
Summary of email discussion [112bis-e-R18-38.212-NR_MC_enh] |
Moderator (Huawei) |
| R1-2304266 |
Summary of email discussion [112bis-e-R18-38.212-NCR] |
Moderator (Huawei) |
| R1-2304277 |
Introduction of dynamic spectrum sharing enhancements |
Ericsson |
| R1-2304278 |
Introduction of multi-carrier enhancements |
Ericsson |
| R1-2304279 |
Introduction of additional PRS configurations [1symbol_PRS] |
Ericsson |