| 2 |
Approval of Agenda |
|
| R1-2300000 |
Draft Agenda of RAN1#112 meeting |
RAN1 Chair |
| R1-2300003 |
RAN1#112 Meeting Timelines, Scope, Process |
RAN1 Chair, ETSI MCC |
| R1-2300004 |
RAN1#112 Meeting Management |
RAN1 Chair |
| R1-2300770 |
Draft Agenda of RAN1#112 meeting |
RAN1 Chair |
| 3 |
Highlights from RAN plenary |
|
| R1-2300002 |
Highlights from RAN#98e |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2300001 |
Report of RAN1#111 meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2300005 |
Reply LS on Pose Information for XR |
SA4, Qualcomm |
| R1-2300006 |
LS on RB set configuration |
RAN3, ZTE |
| R1-2300007 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
RAN3, ZTE, CATT, Fujitsu |
| R1-2300008 |
Reply LS on XR and Media Services |
RAN3, Ericsson |
| R1-2300009 |
LS on Study on expanded and improved NR positioning |
RAN3, Huawei, CATT, Ericsson, Intel |
| R1-2300010 |
LS on network energy saving techniques |
RAN3, Huawei |
| R1-2300011 |
Reply LS on Time Synchronization Status notification towards UE(s) |
RAN3, ZTE |
| R1-2300012 |
LS Response on Latency impact for NTN verified UE location |
SA2, Qualcomm |
| R1-2300013 |
Reply LS on FS_5MBS_Ph2 progress |
SA2, Huawei |
| R1-2300014 |
Reply LS on L1 measurement and configurations for LTM |
RAN2, CATT, Fujitsu |
| R1-2300015 |
LS on SPS configuration for unicast and multicast |
RAN2, ASUSTEK |
| R1-2300016 |
Reply LS to RAN1 on default CBR configuration |
RAN2, OPPO |
| R1-2300017 |
LS to RAN1 on CAPC for SL-U |
RAN2, InterDigital |
| R1-2300018 |
void |
ETSI MCC |
| R1-2300019 |
LS on reduced 1024 QAM capability |
RAN2, Huawei |
| R1-2300020 |
Reply LS on PDCCH skipping |
RAN2, MediaTek |
| R1-2300021 |
Reply LS on RAN dependency for Ranging & Sidelink Positioning |
RAN2, Xiaomi |
| R1-2300022 |
Reply LS to SA2 on XR |
RAN2, vivo, Huawei |
| R1-2300023 |
Reply LS on LPHAP information delivery to RAN |
RAN2, Huawei |
| R1-2300024 |
LS on RRM agreements on expanded and improved NR positioning |
RAN4, Ericsson |
| R1-2300025 |
LS response to RAN1 for interference modelling and Sub-band configuration |
RAN4, Samsung |
| R1-2300026 |
Reply LS on support of positioning in FR2-2 |
RAN4, Huawei |
| R1-2300027 |
Reply LS on capability for PRS measurement without MG |
RAN4, CATT |
| R1-2300028 |
LS for study on expanded and improved NR positioning |
RAN4, Qualcomm |
| R1-2300029 |
LS on Rel-18 Tx switching |
RAN4, China Telecom |
| R1-2300030 |
LS on PSFCH configured power with multiple resource pools |
RAN4, LG Electronics |
| R1-2300031 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
RAN4, CATT |
| R1-2300032 |
LS on RF simulation parameters to be used in RAN4 for power domain enhancements |
RAN4, Nokia |
| R1-2300033 |
LS on BWP operation without bandwidth restriction |
RAN4, vivo |
| R1-2300034 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN4, Ericsson |
| R1-2300035 |
LS reply on reply LS on XR and Media Services |
SA2, vivo |
| R1-2300103 |
Discussion on RAN2 Reply LS to RAN1 on default CBR configuration |
Huawei, HiSilicon |
| R1-2300104 |
Discussion on RAN4 LS on PSFCH configured power with multiple resource pools |
Huawei, HiSilicon |
| R1-2300135 |
Discussion on reduced 1024QAM capability |
Huawei, HiSilicon |
| R1-2300136 |
On RB set configuration for IAB |
Huawei, HiSilicon |
| R1-2300138 |
Formation of a new ETSI ISG for Terahertz Communications (THZ) |
ETSI ISG THZ |
| R1-2300196 |
Discussion on LS on SPS configuration for unicast and multicast |
Spreadtrum Communications |
| R1-2300292 |
Discussion the LS on PSFCH configured power with multiple resource pools |
OPPO |
| R1-2300293 |
Draft reply LS to RAN4 on PSFCH configured power with multiple resource pools |
OPPO |
| R1-2300294 |
Discussion on default CBR configuration in sidelink |
OPPO |
| R1-2300295 |
Draft reply LS to RAN2 on default CBR configuration |
OPPO |
| R1-2300296 |
Discussion on SL LBT failure indication and consistent SL LBT failure |
OPPO |
| R1-2300304 |
Discussion on the LS on SPS configuration for unicast and multicast |
OPPO |
| R1-2300305 |
Draft reply LS on SPS configuration for unicast and multicast |
OPPO |
| R1-2300336 |
[Draft] Reply LS on SPS configuration for unicast and multicast |
ZTE |
| R1-2300349 |
Discussion on RAN3 LS on RB set configuration |
ZTE, Sanechips |
| R1-2300350 |
Draft reply LS on RB set configuration |
ZTE, Sanechips |
| R1-2300351 |
Draft reply LS on default CBR configuration |
ZTE, Sanechips |
| R1-2300352 |
Draft reply LS on PSFCH configured power with multiple resource pools |
ZTE, Sanechips |
| R1-2300353 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
ZTE, Sanechips |
| R1-2300366 |
Discussion on 1024QAM capabilities |
ZTE, Sanechips |
| R1-2300406 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
vivo |
| R1-2300407 |
Discussion on SL LBT failure indication and consistent SL LBT failure |
vivo |
| R1-2300408 |
Draft reply LS to RAN2 on default CBR configuration |
vivo |
| R1-2300409 |
Draft reply LS on PSFCH configured power with multiple resource pools |
vivo |
| R1-2300410 |
Discussion on PSFCH configured power with multiple resource pools |
vivo |
| R1-2300411 |
Discussion on reply LS on SPS configuration for unicast and multicast |
vivo |
| R1-2300412 |
Discussion on RAN2 LS reply on PDCCH skipping |
vivo |
| R1-2300413 |
Draft reply LS to RAN2 on PDCCH skipping |
vivo |
| R1-2300414 |
Draft reply LS on RB set configuration |
vivo |
| R1-2300506 |
Discussion of RAN4 LS on PSFCH configured power with multiple resource pools |
Nokia, Nokia Shanghai Bell |
| R1-2300507 |
Discussion of RAN2 Reply LS to RAN1 on default CBR configuration |
Nokia, Nokia Shanghai Bell |
| R1-2300508 |
Discussion of RAN2 LS on SL LBT failure indication and consistent SL LBT failure |
Nokia, Nokia Shanghai Bell |
| R1-2300509 |
[Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure |
Nokia, Nokia Shanghai Bell |
| R1-2300539 |
[Draft] Reply LS on default CBR configuration |
xiaomi |
| R1-2300540 |
[Draft] Reply LS on PSFCH configured power with multiple resource pools |
xiaomi |
| R1-2300611 |
Draft reply LS on default CBR configuration |
CATT, GOHIGH |
| R1-2300612 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
CATT, GOHIGH |
| R1-2300613 |
Draft Reply LS on PSFCH configured power with multiple resource pools configuration |
CATT, GOHIGH |
| R1-2300614 |
Discussion on SA2 LS reply on XR and media services |
CATT |
| R1-2300615 |
Discussion on LS on SPS configuration for unicast and multicast |
CATT,CBN |
| R1-2300736 |
Discussion on the LS on CAPC for SL-U |
Lenovo |
| R1-2300737 |
Discussion on PSFCH configured power with multiple resource pools |
Lenovo |
| R1-2300738 |
Discussion on default CBR configuration |
Lenovo |
| R1-2300776 |
Discussion on RB set configuration |
Nokia, Nokia Shanghai Bell |
| R1-2300926 |
On the LS on Default CBR Configuration |
Intel Corporation |
| R1-2300927 |
On the LS on PSFCH Configured Power with Multiple Resource Pools |
Intel Corporation |
| R1-2300928 |
Discussion on LS for reduced 1024 QAM capability |
Intel Corporation |
| R1-2300929 |
Draft reply LS on SPS configuration for unicast and multicast |
Intel Corporation |
| R1-2300976 |
Discussion on RAN2 LS on SPS configuration for unicast and multicast |
CMCC |
| R1-2301120 |
[Draft] Reply LS on CAPC for SL-U |
Ericsson |
| R1-2301121 |
Discussion on CAPC for SL-U |
Ericsson |
| R1-2301122 |
[Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure |
Ericsson |
| R1-2301123 |
Discussion on SL LBT failure indication and consistent SL LBT failure |
Ericsson |
| R1-2301124 |
[Draft] Reply LS on PSFCH configured power with multiple resource pools |
Ericsson |
| R1-2301125 |
Discussion on PSFCH configured power with multiple resource pools |
Ericsson |
| R1-2301126 |
[Draft] Reply LS on default CBR configuration |
Ericsson |
| R1-2301127 |
Discussion on default CBR configuration |
Ericsson |
| R1-2301225 |
Draft reply LS on default CBR configuration |
Samsung |
| R1-2301226 |
Draft reply LS on PSFCH configured power with multiple resource pools |
Samsung |
| R1-2301227 |
Draft Reply LS on RB set configuration |
Samsung |
| R1-2301228 |
Discussion on LS related to reduced 1024 QAM capability |
Samsung |
| R1-2301322 |
Discussion on RAN2 LS on Default CBR Configuration |
Apple |
| R1-2301323 |
Draft Reply LS to RAN2 on Default CBR Configuration |
Apple |
| R1-2301324 |
Draft Reply LS to RAN4 on PSFCH Configured Power with Multiple Resource Pools |
Apple |
| R1-2301325 |
Draft reply LS to RAN2 on SPS configuration for unicast and multicast |
Apple |
| R1-2301326 |
Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT |
Apple |
| R1-2301327 |
Draft reply LS to RAN2 on SL LBT failure indication and consistent SL LBT |
Apple |
| R1-2301379 |
Draft Reply to RAN2 LS on reduced 1024 QAM capability |
Qualcomm Incorporated |
| R1-2301380 |
Draft Reply to RAN2 LS on default CBR configuration |
Qualcomm Incorporated |
| R1-2301381 |
Draft Reply to RAN4 LS on PSFCH configured power with multiple resource pools |
Qualcomm Incorporated |
| R1-2301382 |
Draft reply LS on RB set configuration |
Qualcomm Incorporated |
| R1-2301447 |
Discussion on SPS configuration for MBS |
ZTE |
| R1-2301464 |
[Draft] Reply LS on SPS configuration for unicast and multicast |
ASUSTeK |
| R1-2301467 |
Discussion on LS on reduced 1024 QAM capability |
NTT DOCOMO, INC. |
| R1-2301528 |
Discussion on LS on PSFCH configured power with multiple resource pools |
LG Electronics |
| R1-2301529 |
Discussion on Reply LS to RAN1 on default CBR configuration |
LG Electronics |
| R1-2301530 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
LG Electronics |
| R1-2301531 |
Discussion on LS to RAN1 on CAPC for SL-U |
LG Electronics |
| R1-2301552 |
Discussion on RAN2 LS on 1024-QAM UE capability |
Ericsson |
| R1-2301565 |
Discussion on LS on SL LBT failure indication and consistent SL LBT failure |
Sharp |
| R1-2301611 |
Discussion on RAN2 LS on SPS configuration for unicast and multicast |
MediaTek Inc. |
| R1-2301618 |
Discussion on reply LS on PDCCH skipping |
MediaTek Inc. |
| R1-2301621 |
Draft LS reply on SPS configuration for unicast and multicast |
MediaTek Inc. |
| R1-2301625 |
Discussion of LS on XR and Media Services |
Nokia, Nokia Shanghai Bell |
| R1-2301660 |
On PDCCH skipping LS |
Nokia, Nokia Shanghai Bell |
| R1-2301668 |
Draft reply LS on SPS configuration for unicast and multicast |
Ericsson |
| R1-2301702 |
Discussion on SPS configuration for unicast and multicast |
Huawei, HiSilicon, CBN |
| R1-2301709 |
Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT failure |
Huawei, HiSilicon |
| R1-2301710 |
Discussion on RAN2 LS on on CAPC for SL-U |
Huawei, HiSilicon |
| R1-2301755 |
Draft reply LS on reduced 1024QAM capability |
Huawei, HiSilicon |
| R1-2301756 |
Draft reply LS on RB set configuration for IAB |
Huawei, HiSilicon |
| R1-2301764 |
Draft Reply LS on RB set configuration |
Ericsson |
| R1-2301765 |
Discussion on RAN3 LS on RB set configuration |
Ericsson |
| R1-2301785 |
Discussion on RAN2 LS on SPS configuration for unicast and multicast |
MediaTek Inc. |
| R1-2301914 |
LS on the requirement on low power or high accuracy positioning |
SA2, Huawei |
| R1-2301915 |
LS on PRU procedures |
SA2, Qualcomm |
| R1-2301916 |
LS on support of multiple Target UEs |
SA2, Qualcomm |
| R1-2302228 |
LS on further questions on feMIMO RRC parameters |
RAN2, Ericsson |
| R1-2302248 |
Draft reply LS to RAN2 on further questions on feMIMO RRC parameters |
Moderator (ZTE) |
| R1-2302249 |
Reply LS to RAN2 on further questions on feMIMO RRC parameters |
RAN1, ZTE |
| R1-2302250 |
Post-meeting email discussion on FeMIMO Reply to RAN2 LS RRC |
Moderator (ZTE) |
| 6 |
Releases 8 – 16 E-UTRA Maintenance |
|
| R1-2301153 |
Maintenance for LTE-MTC and NB-IoT |
Ericsson |
| R1-2301906 |
Moderator Summary [112-R8~R16-LTE] |
Moderator (Ericsson) |
| R1-2302051 |
Session notes for 6 (Releases 8 – 16 E-UTRA Maintenance) |
Ad-hoc Chair (CMCC) |
| 7.1 |
Maintenance on NR Releases 15 |
|
| R1-2300616 |
Correction on SRS frequency hopping procedure in Rel-15 |
CATT |
| R1-2301383 |
Discussion on an issue for Type1 HARQ-ACK CB with more than one PDSCH per slot |
Qualcomm Incorporated |
| R1-2301596 |
On PUSCH power control adjustment state and TPC command value of Msg3 retransmission |
MediaTek Inc. |
| R1-2301597 |
On the relation between SUL indicator and pusch-Config/pucch-Config for DCI 0_0 |
MediaTek Inc. |
| R1-2301598 |
[R17] Draft 38.212 CR on SUL indicator and pusch-Config/pucch-Config for DCI 0_0 |
MediaTek Inc. |
| R1-2301716 |
Discussion on the multiplexing between SR/SPS A/N and CSI |
Huawei, HiSilicon |
| R1-2302014 |
Summary of comments on R1-2301596 about power control of Msg3 retransmission |
Moderator (MediaTek Inc.) |
| R1-2302015 |
Summary of comments on R1-2301597 about SUL indicator and configuration |
Moderator (MediaTek Inc.) |
| R1-2302038 |
Summary #1 of discussion on the multiplexing between SR/SPS A/N and CSI |
Moderator (HiSilicon) |
| R1-2302042 |
Summary of correction on SRS frequency hopping procedure |
Moderator (CATT) |
| R1-2302046 |
Summary of [112-R15-NR] Discussion on an issue for Type1 HARQ-ACK CB with more than one PDSCH per slot |
Moderator (Qualcomm) |
| R1-2302048 |
Summary of correction on SRS frequency hopping procedure |
Moderator (CATT) |
| R1-2302121 |
Summary#2 of correction on SRS frequency hopping procedure |
Moderator (CATT) |
| R1-2302139 |
Summary #2 of discussion on the multiplexing between SR/SPS A/N and CSI |
Moderator (HiSilicon) |
| 7.2 |
Maintenance on NR Releases 16 |
|
| R1-2300194 |
Draft CR on Type-1 HARQ-ACK codebook when MDCI based MTRP operation in TS 38.213 |
ZTE |
| R1-2300317 |
Clarification to the switching gap location of the UL Tx Switching |
Nokia, Nokia Shanghai Bell |
| R1-2300325 |
On the switching gap location of the UL Tx Switching |
Nokia, Nokia Shanghai Bell |
| R1-2300617 |
Correction on impact of DAPS handover in Rel-16 |
CATT |
| R1-2300618 |
Correction on impact of DAPS handover in Rel-17 |
CATT |
| R1-2300619 |
Correction on PUSCH selection in Rel-16 |
CATT |
| R1-2300620 |
Correction on PUSCH selection in Rel-17 |
CATT |
| R1-2300621 |
Correction on PUSCH TDRA Tables in Rel-16 |
CATT |
| R1-2300622 |
Correction on PUSCH TDRA Tables in Rel-17 |
CATT |
| R1-2300623 |
Correction on RRC parameter for beta_offset indicator in DCI format 0_2 in Rel-16 |
CATT |
| R1-2300624 |
Correction on RRC parameter for beta_offset indicator in DCI format 0_2 in Rel-17 |
CATT |
| R1-2300625 |
Correction on UCI multiplexing on PUSCH in Rel-16 |
CATT |
| R1-2300626 |
Correction on UCI multiplexing on PUSCH in Rel-17 |
CATT |
| R1-2300789 |
Correction on OFDM symbol duplication for PSFCH |
Sharp |
| R1-2300798 |
Draft CR on positioning SRS power control in 38.213 |
ZTE |
| R1-2300799 |
Discussion on positioning SRS power control in 38.213 |
ZTE |
| R1-2300800 |
Alignment CR for AOA positioning in 38.215 |
ZTE |
| R1-2301079 |
Discussion on PSFCH power control |
ZTE, Sanechips |
| R1-2301080 |
Corrections on PSFCH power determination in TS 38.213 |
ZTE, Sanechips |
| R1-2301314 |
Draft CR for NR 38.214 descriptions |
ZTE |
| R1-2301316 |
Corrections on RSRP measurement in TS 38.214 |
ZTE, Sanechips |
| R1-2301384 |
Clarification of Rel-16 UL Tx Switching |
Qualcomm Incorporated |
| R1-2301448 |
Draft 214 CR on SPS PDSCH dropping |
ZTE |
| R1-2301708 |
Corrections to type 2 channel access for UL multi channel access |
Huawei, HiSilicon |
| R1-2301752 |
Correction to the positioning SRS spatial relation information |
Huawei, HiSilicon |
| R1-2301768 |
draft CR for soft amplitude restriction in R16 eType 2 CB |
Ericsson |
| R1-2301856 |
Moderator summary on Rel-16 UL Tx Switching related issues |
Moderator (Nokia) |
| R1-2301890 |
Summary #1 of correction on SRS spatial relation |
Moderator (Huawei) |
| R1-2301970 |
Summary of positioning SRS power control corrections |
Moderator (ZTE) |
| R1-2301973 |
Summary of Type-1 HARQ-ACK codebook when MDCI based MTRP operation |
Moderator (ZTE) |
| R1-2302009 |
Summary on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302021 |
FL summary of SPS PDSCH dropping in case of mDCI + mTRP |
Moderator (ZTE ) |
| R1-2302027 |
Summary of TDRA alignment between TS 38.331 and TS 38.214 |
Moderator (CATT) |
| R1-2302028 |
Summary of correction on impact of DAPS handover |
Moderator (CATT) |
| R1-2302029 |
Summary of correction on PUSCH selection |
Moderator (CATT) |
| R1-2302030 |
Summary of RRC parameter alignment and editorial corrections |
Moderator (CATT) |
| R1-2302037 |
Summary #1 of corrections to type 2 channel access for UL multi-channel access |
Moderator (Huawei) |
| R1-2302043 |
Summary of discussion on OFDM symbol duplication for PSFCH |
Moderator (Sharp) |
| R1-2302049 |
Moderator summary#2 on Rel-16 UL Tx Switching related issues |
Moderator (Nokia) |
| R1-2302050 |
Moderator summary#3 on Rel-16 UL Tx Switching related issues |
Moderator (Nokia) |
| R1-2302088 |
CR on positioning SRS power control in 38.213 |
Moderator (ZTE) |
| R1-2302089 |
CR on positioning SRS power control in 38.213 |
Moderator (ZTE) |
| R1-2302105 |
[Draft] Reply LS to RAN4 on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302108 |
Summary on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302112 |
FL summary#2 of SPS PDSCH dropping in case of mDCI + mTRP |
Moderator (ZTE ) |
| R1-2302115 |
Corrections on PSFCH power determination in TS 38.213 |
Moderator (LG Electronics) |
| R1-2302116 |
Corrections on PSFCH power determination in TS 38.213 |
Moderator (LG Electronics) |
| R1-2302163 |
Correction on PUSCH TDRA Tables in Rel-16 |
Moderator (CATT), Ericsson |
| R1-2302164 |
Correction on PUSCH TDRA Tables in Rel-17 |
Moderator (CATT), Ericsson |
| R1-2302171 |
Summary#2 on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302172 |
[Draft] Reply LS to RAN4 on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302197 |
[DRAFT] LS on Rel-16 UL Tx Switching period |
Nokia |
| R1-2302198 |
LS on Rel-16 UL Tx Switching period |
RAN1, Nokia |
| R1-2302202 |
Corrections to type 2 channel access for UL multi channel access |
Moderator (Huawei), HiSilicon |
| R1-2302203 |
Corrections to type 2 channel access for UL multi channel access |
Moderator (Huawei), HiSilicon |
| R1-2302231 |
Reply LS to RAN4 on PSFCH configured power with multiple resource pools |
Moderator (LG Electronics) |
| R1-2302232 |
Corrections on PSFCH power determination in TS 38.213 |
Moderator (LG Electronics), Samsung, Qualcomm, Huawei, HiSilicon, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2302233 |
Corrections on PSFCH power determination in TS 38.213 |
Moderator (LG Electronics), Samsung, Qualcomm, Huawei, HiSilicon, ZTE, Sanechips, Nokia, Nokia Shanghai Bell |
| R1-2302237 |
Alignment CR for AOA positioning in 38.215 |
Intel |
| R1-2302238 |
Alignment CR for AOA positioning in 38.215 |
Intel |
| R1-2302239 |
Rel-16 editorial corrections for TS 38.212 |
Huawei |
| R1-2302240 |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) |
Huawei |
| R1-2302241 |
Rel-16 editorial corrections for TS 38.213 |
Samsung |
| R1-2302242 |
Rel-16 editorial corrections for TS 38.213 (mirrored to Rel-17) |
Samsung |
| R1-2302243 |
Rel-16 editorial corrections for TS 38.214 |
Nokia |
| R1-2302244 |
Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) |
Nokia |
| R1-2302252 |
Alignment of parameter names |
Ericsson |
| R1-2302253 |
Correction on contention window adjustments |
Ericsson |
| 8 |
Release 17 Maintenance |
|
| R1-2302245 |
Rel-17 editorial corrections for TS 38.212 |
Huawei |
| R1-2302246 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2302247 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| 8.1 |
Maintenance on Further enhancements on MIMO for NR |
|
| R1-2300092 |
Correction on the limitation of slot offset for aperiodic SRS |
Huawei, HiSilicon |
| R1-2300190 |
Discussion on SRS closed loop power control shared with PUSCH |
ZTE |
| R1-2300191 |
Draft CR on SRS closed loop power control shared with PUSCH in TS 38.213 |
ZTE |
| R1-2300192 |
Draft CR on clarifying aperiodic SRS triggering for antenna switching in TS 38.214 |
ZTE |
| R1-2300193 |
Draft CR on clarifying triggering slot for 1T4R antenna switching with multiple AP SRS resource sets in TS 38.214 |
ZTE |
| R1-2300197 |
Draft 38.213 CR on parameter name alignment for unified TCI framework |
Spreadtrum Communications |
| R1-2300198 |
Draft 38.214 CR on name alignment for TCI state parameter |
Spreadtrum Communications |
| R1-2300255 |
Parameter alignment for unified TCI state for 38.213 |
OPPO |
| R1-2300256 |
Parameter alignment for unified TCI state for 38.214 |
OPPO |
| R1-2300388 |
Draft CR on Default Beam Application Time |
Google |
| R1-2300389 |
Draft CR on ACK for MAC CE based Unified TCI Indication |
Google |
| R1-2300390 |
Clarification on HARQ ACK for Unified TCI Indication |
Google |
| R1-2300415 |
Discussion on the SRS closed loop power control under unified TCI framework |
vivo |
| R1-2300416 |
Draft CR on the SRS closed loop power control under unified TCI framework |
vivo |
| R1-2300417 |
Draft alignment CR on RRC parameters |
vivo, Nokia |
| R1-2300520 |
Draft CR on UE capability description of blind detection number in TS38.213 for enhanced PDCCH with repetition |
Lenovo |
| R1-2300521 |
Draft CR on the power control for SRS resource set for noncodebook |
Lenovo |
| R1-2300627 |
Editorial corrections on beam reporting in uplink panel selection |
CATT |
| R1-2301229 |
Corrections for Beam Failure Recover related to unified TCI state framework |
Samsung |
| R1-2301230 |
Beam application time for cross carrier beam application |
Samsung |
| R1-2301231 |
Draft CR on power control parameters for multiple aperiodic SRS resource sets |
Samsung |
| R1-2301232 |
Draft CR on slot offset parameters for multiple aperiodic SRS resource sets |
Samsung |
| R1-2301385 |
Draft CR on mTRP PUSCH repetitions with one PHR |
Qualcomm Incorporated |
| R1-2301465 |
Correction on reportQuantity |
ASUSTeK |
| R1-2301468 |
Discussion on HARQ-ACK for beam application timing in unified TCI |
NTT DOCOMO, INC. |
| R1-2301469 |
Discussion on multi-slot PDSCH/PUSCH repetition in unified TCI |
NTT DOCOMO, INC. |
| R1-2301640 |
Draft CR on UL SRS Inter-slot GP time location for the first and/or last resource |
Nokia, Nokia Shanghai Bell |
| R1-2301641 |
Draft CR on Repetition number for mTRP PUSCH repetition |
Nokia, Nokia Shanghai Bell |
| R1-2301661 |
Draft CR aligning parameter name related to SFN schemes in 38.214 |
Ericsson |
| R1-2301662 |
Draft CR aligning parameter names related to CSI report procedure in 38.214 |
Ericsson |
| R1-2301720 |
Correction on the power control alignment for aperiodic SRS |
Huawei, HiSilicon |
| R1-2301721 |
Discussion on the power control alignment for aperiodic SRS |
Huawei, HiSilicon |
| R1-2301722 |
Correction on application time of TCI indication |
Huawei, HiSilicon |
| R1-2301759 |
Correction on the parameter name alignment for SRS in TS 38.212 |
Huawei, HiSilicon |
| R1-2301760 |
Correction on the parameter name alignment for SRS in TS 38.214 |
Huawei, HiSilicon |
| R1-2301846 |
Moderator Summary for Rel. 17 NR FeMIMO – Maintenance on HST-SFN (Round 0) |
Moderator (Intel Corporation) |
| R1-2301960 |
Moderator Summary #0 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2301974 |
Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 0 |
Moderator (ZTE) |
| R1-2301982 |
Draft 38.213 CR on parameter name alignment for unified TCI framework |
Spreadtrum Communications |
| R1-2301983 |
Draft 38.214 CR on name alignment for TCI state parameter |
Spreadtrum Communications |
| R1-2301999 |
Moderator Summary on Rel-17 FeMIMO maintenance for SRS in Round 1 |
Moderator (ZTE) |
| R1-2302090 |
CR on mTRP PUSCH repetitions with one PHR |
Moderator (Nokia), Qualcomm Incorporated, Samsung |
| R1-2302093 |
CR on power control parameters for multiple aperiodic SRS resource sets |
Moderator (ZTE), Samsung, ZTE, Huawei, HiSilicon |
| R1-2302097 |
Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam |
Moderator (ZTE) |
| R1-2302122 |
CR on slot offset parameters for multiple aperiodic SRS resource sets |
Moderator (ZTE), Samsung, Huawei, HiSilicon, ZTE |
| R1-2302173 |
Corrections for Beam Failure Recovery related to unified TCI state framework |
Moderator (ZTE), Samsung, ZTE |
| R1-2302180 |
CR on HARQ-ACK for beam indication in unified TCI |
Moderator (ZTE), NTT DOCOMO, Google, ZTE, NEC, Samsung, vivo |
| 8.2 |
Maintenance on Supporting NR from 52.6GHz to 71 GHz |
|
| R1-2300258 |
Discussion on remaining issue for LBT upgrade within gNB COT |
OPPO |
| R1-2300259 |
Draft CR on resolving issue for LBT upgrade within gNB COT |
OPPO |
| R1-2300498 |
Correction on RRC parameters for TDRA tables for multi-PXSCH scheduling in TS38.214 |
vivo |
| R1-2300640 |
Discussion on DL SPS & UL CG operation via DCI format 1_1&0_1 for the features extending NR operation to 71 GHz |
CATT |
| R1-2300641 |
Draft CR for DL SPS & UL CG operation via DCI format 1_1&0_1 for the features extending NR operation to 71 GHz |
CATT |
| R1-2300642 |
Draft CR for editorial correction of pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for the features extending NR operation to 71 GHz |
CATT |
| R1-2300643 |
The remaining issues on channel access mechanism |
CATT |
| R1-2300644 |
Draft CR on UE resuming a UE initiated COT |
CATT |
| R1-2300645 |
Draft CR on channel access type update within gNB COT |
CATT |
| R1-2300709 |
Discussion on LBT type update upon detection of DCI format 2-0 for FR2-2 |
ZTE, Sanechips |
| R1-2300710 |
Draft CR on LBT type update upon detection of DCI format 2-0 for FR2-2 in TS 37.213 |
ZTE, Sanechips |
| R1-2300711 |
Discussion on channel measurement and interference measurement in FR2-2 |
ZTE, Sanechips |
| R1-2300712 |
Correction on channel measurement and interference measurement in FR2-2 in TS 38.214 |
ZTE, Sanechips |
| R1-2300910 |
Discussion on DCI field sizes for multiple PxSCHs scheduled by single DCI |
Ericsson |
| R1-2300911 |
Draft CR on DCI field sizes for multiple PxSCHs scheduled by single DCI |
Ericsson |
| R1-2300912 |
Discussion on K2 indication for multiple PUSCHs scheduled by single DCI |
Ericsson |
| R1-2300913 |
Draft CR on K2 indication for multiple PUSCHs scheduled by single DCI |
Ericsson |
| R1-2300914 |
Discussion on TCI state indication for multiple PDSCHs scheduled by single DCI |
Ericsson |
| R1-2300915 |
Draft CR on TCI state indication for multiple PDSCHs scheduled by single DCI |
Ericsson |
| R1-2300916 |
Discussion on TDRA for multiple PUSCHs scheduled by single DCI |
Ericsson |
| R1-2300917 |
Draft CR on TDRA for multiple PUSCHs scheduled by single DCI |
Ericsson |
| R1-2301102 |
Draft CR on channel access type indication for DCI format x_2 in FR2-2 |
LG Electronics |
| R1-2301103 |
Draft CR on LBT type determination within a COT |
LG Electronics |
| R1-2301386 |
Remaining issues for channel access for NR beyond 52.6GHz |
Qualcomm Incorporated |
| R1-2301527 |
Draft CR on PDCCH validation for SPS and CG Type 2 |
Ericsson Inc. |
| R1-2301652 |
Correction on CSI-RS validation |
ASUSTeK |
| R1-2301705 |
Remaining issues of channel access mechanism for 60 GHz unlicensed operation |
Huawei, HiSilicon |
| R1-2301706 |
Corrections to multi beam channel access in TS37.213 |
Huawei, HiSilicon |
| R1-2301707 |
Corrections to ChanneAccess-CPext field in DCI formats x_2 in TS38.212 |
Huawei, HiSilicon |
| R1-2301728 |
Discussion on UE resuming a UE-initiated COT |
Nokia, Nokia Shanghai Bell |
| R1-2301729 |
Correction on UE resuming a UE-initiated COT |
Nokia, Nokia Shanghai Bell |
| R1-2301730 |
Draft CR on channel access after failure of Type 2 channel access for FR2-2 |
WILUS Inc. |
| R1-2301731 |
Draft CR on channel access procedure upon detection of a common DCI for FR2-2 |
WILUS Inc. |
| R1-2301750 |
Corrections to aperiodic CSI-RS timing for mixed numerologies configuration in TS38.214 |
Huawei, HiSilicon |
| R1-2301757 |
Corrections to spatial domain filter determination for type 2 channel access in COT resumption in TS37.213 |
Huawei, HiSilicon |
| R1-2301758 |
Corrections to r17 PDCCH monitoring capability for CA and DC in TS38.213 |
Huawei, HiSilicon |
| R1-2301812 |
Draft CR on PDCCH validation for SPS and CG Type 2 |
Ericsson Inc. |
| R1-2301840 |
Discussion on DCI field sizes for multiple PxSCHs scheduled by single DCI |
Ericsson |
| R1-2301857 |
Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) |
Moderator (LG Electronics) |
| R1-2301972 |
Summary #1 of Channel Access Procedures |
Moderator (Nokia) |
| R1-2301997 |
FL summary of PDSCH/PUSCH enhancement (RS and timeline) |
Moderator (vivo) |
| R1-2302052 |
Session notes for 8.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) |
Ad-Hoc Chair (Huawei) |
| R1-2302092 |
FL summary on PDCCH monitoring for Rel.17 FR2-2 Maintenance |
Moderator (Lenovo) |
| R1-2302098 |
Draft CR on DCI field sizes for multiple PDSCHs scheduled by single DCI |
Moderator (LG Electronics) |
| R1-2302099 |
Draft CR on PDCCH validation for CG Type 2 |
Moderator (LG Electronics), Ericsson |
| R1-2302100 |
Draft CR on K2 indication for multi-PUSCH scheduling DCI |
Moderator (LG Electronics), Ericsson |
| R1-2302101 |
DRAFT LS to RAN2 on K2 indication for multi-PUSCH scheduling |
Moderator (LG Electronics) |
| R1-2302109 |
Summary #2 of Channel Access Procedures |
Moderator (Nokia) |
| R1-2302110 |
Corrections to aperiodic CSI-RS timing for mixed numerologies configuration in TS38.214 |
Moderator (vivo), Huawei, HiSilicon |
| R1-2302141 |
CR on DCI field sizes for multiple PDSCHs scheduled by single DCI |
Moderator (LG Electronics), Ericsson |
| R1-2302142 |
CR on K2 indication for multi-PUSCH scheduling DCI |
Moderator (LG Electronics), Ericsson |
| R1-2302143 |
Corrections to r17 PDCCH monitoring capability for CA and DC |
Moderator (Lenovo), Huawei, HiSilicon |
| R1-2302144 |
LS to RAN2 on K2 indication for multi-PUSCH scheduling |
RAN1, LG Electronics |
| R1-2302153 |
Correction on channel measurement and interference measurement in FR2-2 in TS 38.214 |
Moderator (Nokia), ZTE, Sanechips |
| R1-2302154 |
Corrections to ChanneAccess-CPext field in DCI formats x_2 in TS38.212 |
Moderator(Nokia), Huawei, HiSilicon, vivo, LG Electronics |
| R1-2302155 |
DRAFT LS to RAN2 on reference subcarrier spacing for FR2-2 |
Moderator (Nokia) |
| R1-2302156 |
Summary #3 of Channel Access Procedures |
Moderator (Nokia) |
| R1-2302183 |
CR on PDCCH validation for CG Type 2 |
Moderator (LG Electronics), Ericsson |
| R1-2302184 |
Corrections to ChanneAccess-CPext field in DCI formats x_2 in TS38.212 |
Moderator (Nokia), Huawei, HiSilicon, vivo, LG Electronics |
| R1-2302185 |
LS to RAN2 on reference subcarrier spacing for FR2-2 |
RAN1, Nokia |
| 8.3 |
Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC |
|
| R1-2300072 |
Correction on semi-static PUCCH carrier switching |
Huawei, HiSilicon |
| R1-2300338 |
Draft CR on PUCCH transmission after multiplexing UCI with different priorities |
ZTE |
| R1-2300364 |
Clarification on PUCCH transmission after multiplexing UCI with different priorities (TP to 38.213) |
Nokia, Nokia Shanghai Bell |
| R1-2300646 |
Correction on the definition of last DCI in Rel-17 |
CATT |
| R1-2300647 |
Correction on HARQ-ACK multiplexing on PUSCH with different priority |
CATT |
| R1-2301233 |
Correction on interaction between intra-UE prioritization and UL transmission collision with DL symbols |
Samsung |
| R1-2301234 |
Correction on PUCCH power control for multiplexing HARQ-ACK of different priorities in a PUCCH |
Samsung |
| R1-2301235 |
Correction on timeline requirements when configured with uci-MuxWithDiffPrio |
Samsung |
| R1-2301725 |
Correction on semi-static channel occupancy |
Nokia, Nokia Shanghai Bell |
| R1-2301746 |
Correction on the reference of intra-UE multiplexing related clauses in 38.212 |
Huawei, HiSilicon |
| R1-2301751 |
Correction on power control of inter priority UCI multiplexing |
Huawei, HiSilicon |
| R1-2302010 |
Moderator summary #1 on Maintenance NR Rel-17 URLLC/IIoT |
Moderator (Nokia) |
| R1-2302011 |
Corrections on intra-UE multiplexing and semi-static channel occupancy |
Moderator (Nokia), Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2302012 |
Miscellaneous corrections on Rel-17 URLLC / IIoT in 38.213 |
Moderator (Nokia), Samsung, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2302013 |
Correction on timeline requirements when configured with uci-MuxWithDiffPrio |
Moderator (Nokia), Samsung |
| R1-2302053 |
Session notes for 8.3 (Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC) |
Ad-hoc Chair (CMCC) |
| R1-2302082 |
Moderator summary #2 on Maintenance NR Rel-17 URLLC/IIoT |
Moderator (Nokia) |
| R1-2302083 |
Corrections on intra-UE multiplexing and semi-static channel occupancy |
Moderator (Nokia), Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2302084 |
Miscellaneous corrections on Rel-17 URLLC / IIoT in 38.213 |
Moderator (Nokia), Samsung, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE |
| R1-2302085 |
Correction on timeline requirements when configured with uci-MuxWithDiffPrio |
Moderator (Nokia), Samsung |
| 8.4 |
Maintenance on Solutions for NR to support non-terrestrial networks (NTN) |
|
| R1-2300260 |
Draft CR on the Type-1 HARQ-ACK codebook |
OPPO |
| R1-2300261 |
Draft CR on the Type-2 HARQ-ACK codebook |
OPPO |
| R1-2301738 |
Maintenance issues for R17 NR NTN |
Ericsson |
| R1-2301741 |
Draft CR 38.211: Correction of timing advance and alignment to 38.331 |
Ericsson |
| R1-2301742 |
Draft CR 38.212: Alignment with 38.331 |
Ericsson |
| R1-2301743 |
Draft CR 38.213: Addition of missing parameter dl-DataToUL-ACK-v1700 |
Ericsson |
| R1-2301907 |
FL Summary #1: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2301908 |
FL Summary #2: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2301909 |
FL Summary #3: Maintenance on Solutions for NR to support NTN |
Moderator (Thales) |
| R1-2302054 |
Session notes for 8.4 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) |
Ad-Hoc Chair (Huawei) |
| R1-2302182 |
Draft CR on the Type-1 HARQ-ACK codebook |
Moderator (Thales) |
| R1-2302229 |
CR on the Type-1 HARQ-ACK codebook |
Moderator (Thales), OPPO, NTT DOCOMO, Xiaomi, Samsung, Ericsson |
| 8.5 |
Maintenance on NR Positioning Enhancements |
|
| R1-2300801 |
Alignment CR for NR positioning in 38.214 |
ZTE |
| R1-2301210 |
Correction on TEG reporting |
Nokia, Nokia Shanghai Bell |
| R1-2301753 |
Correction to the DL-AoD priority subset |
Huawei, HiSilicon |
| R1-2301754 |
Editorial corrections to NR positioning enhancements |
Huawei, HiSilicon |
| R1-2301831 |
FL Summary for Maintenance on NR Positioning Enhancements |
Moderator (CATT) |
| R1-2301891 |
Summary #1 of correction on DL-AoD priority subset |
Moderator (Huawei) |
| R1-2301892 |
Summary #1 of PRS editorial corrections |
Moderator (Huawei) |
| R1-2301905 |
Summary #1 of Correction on TEG reporting |
Moderator (Nokia) |
| R1-2301971 |
Summary #1 of PRS configuration and editorial corrections |
Moderator (ZTE) |
| R1-2302055 |
Session notes for 8.5 (Maintenance on NR Positioning Enhancements) |
Ad-Hoc Chair (Huawei) |
| 8.6 |
Maintenance on Support of Reduced Capability NR Devices |
|
| R1-2300367 |
Discussion on RedCap remaining issues |
ZTE, Sanechips |
| R1-2300368 |
Correction on TDRA misalignment of PUSCH for RedCap |
ZTE, Sanechips |
| R1-2300418 |
Remianing issues on SDT suppor for Rel-17 RedCap UE |
vivo |
| R1-2300499 |
Support for SDT in a RedCap-specific initial DL BWP without SSB |
Ericsson |
| R1-2300542 |
Discussion on remaining details of RedCap SDT operation |
xiaomi |
| R1-2300648 |
Discussion on SDT in separate initial BWP without CD-SSB |
CATT |
| R1-2300649 |
Correction on impact of HD-FDD operation in Rel-17 |
CATT |
| R1-2300854 |
Remaining issue of Rel-17 RedCap UE |
NEC |
| R1-2300977 |
Discussion on SDT procedure related RedCap remaining issues |
CMCC |
| R1-2301148 |
RedCap support of SDT |
Nokia, Nokia Shanghai Bell |
| R1-2301328 |
On Small Data Transmission for Redcap UEs |
Apple |
| R1-2301387 |
Remaining Issues on UE Complexity Reduction |
Qualcomm Incorporated |
| R1-2301470 |
Correction on reference clauses for PDCCH repetition, UCI multiplexing/prioritization, and PUCCH transmission for HD-FDD operation |
NTT DOCOMO, INC. |
| R1-2301471 |
Discussion on corrections and SDT operations for RedCap UE |
NTT DOCOMO, INC. |
| R1-2301542 |
Corrections on invalid symbol determination for PUSCH repetition Type B transmission for RedCap UE |
Sharp, vivo |
| R1-2301607 |
On RedCap remaining issues |
MediaTek Inc. |
| R1-2301608 |
Draft CR on validation of PRACH and PUSCH occasions with NCD-SSB |
MediaTek Inc. |
| R1-2301723 |
Remaining issues during SDT procedure for RedCap UEs |
Huawei, HiSilicon |
| R1-2301781 |
On RedCap remaining issues |
MediaTek Inc. |
| R1-2301782 |
Draft CR on validation of PRACH and PUSCH occasions with NCD-SSB |
MediaTek Inc. |
| R1-2301881 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2301882 |
FL summary #1 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2301883 |
FL summary #2 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2301884 |
FL summary #3 on Rel-17 RedCap maintenance |
Moderator (Ericsson) |
| R1-2302056 |
Session notes for 8.6 (Maintenance on Support of Reduced Capability NR Devices) |
Ad-hoc Chair (CMCC) |
| R1-2302207 |
Corrections on impact of HD-FDD operation for RedCap UE |
Moderator (Ericsson), CATT, NTT DOCOMO, Ericsson |
| R1-2302208 |
Corrections on invalid symbol determination for PUSCH repetition Type B transmission for RedCap UE |
Moderator (Ericsson), Sharp, vivo, Ericsson |
| 8.7 |
Maintenance on UE Power Saving Enhancements |
|
| R1-2300270 |
Remaining issues for DCI-based power saving adaptation |
OPPO |
| R1-2300271 |
Draft CR for DCI-based power saving adaptation |
OPPO |
| R1-2300369 |
Discussion on UE power saving remaining issues |
ZTE, Sanechips |
| R1-2300370 |
Correction on PDCCH skipping |
ZTE, Sanechips |
| R1-2300419 |
Correction on mixed R16 SSSG switching and R17 PDCCH monitoring adaptation |
vivo |
| R1-2300420 |
Correction on UE behaviors during contention resolution timer and RAR window |
vivo |
| R1-2300494 |
Correction on search space set group switch delay |
FGI |
| R1-2300543 |
UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI |
xiaomi |
| R1-2300544 |
UE hehavior for PDCCH skipping when RACH for positive SR is transmited |
xiaomi |
| R1-2300930 |
Discussion on remaining corrections to 38.213 related to UE power saving |
Intel Corporation |
| R1-2301236 |
Corrections on PDCCH skipping |
Samsung |
| R1-2301553 |
Draft CR for 38.213 on PDCCH skipping behavior |
Ericsson |
| R1-2301619 |
Corrections on PDCCH skipping |
MediaTek Inc. |
| R1-2301651 |
Correction on PDCCH skipping |
ASUSTeK |
| R1-2301657 |
Open issues on PDCCH monitoring adaptation for UE power saving |
Nokia, Nokia Shanghai Bell |
| R1-2301658 |
Definition of PDCCH skipping behaviour while SR is pending or cancelled |
Nokia, Nokia Shanghai Bell |
| R1-2301659 |
PDCCH skipping behaviour upon successful completion of contention resolution |
Nokia, Nokia Shanghai Bell |
| R1-2301712 |
Discussion on PDCCH monitoring adaptation and BWP switching |
Huawei, HiSilicon |
| R1-2301748 |
Correction on PDCCH monitoring adaptation and BWP switching |
Huawei, HiSilicon |
| R1-2301749 |
Correction on PDCCH skipping |
Huawei, HiSilicon |
| R1-2302031 |
Corrections on PDCCH skipping |
Moderator (MediaTek), Nokia, Intel, Samsung, Ericsson, ASUSTek, Huawei, HiSilicon |
| R1-2302032 |
Corrections on PDCCH skipping |
Moderator (MediaTek), Nokia, Intel, Samsung, Ericsson, ASUSTek, Huawei, HiSilicon |
| R1-2302033 |
Summary#1 for maintenance on UE power saving enhancements |
Moderator (MediaTek) |
| R1-2302057 |
Session notes for 8.7 (Maintenance on UE Power Saving Enhancements) |
Ad-hoc Chair (CMCC) |
| R1-2302150 |
Draft reply LS to RAN2 on PDCCH skipping |
Moderator (MediaTek) |
| R1-2302151 |
Reply LS on PDCCH skipping |
RAN1, MediaTek |
| 8.8 |
Maintenance on NR coverage enhancement |
|
| R1-2300715 |
Draft Correction on RRC parameters for DMRS bundling |
China Telecom |
| R1-2301472 |
Discussion on remaining issues for NR coverage enhancement |
NTT DOCOMO, INC. |
| R1-2301473 |
Draft CR on unified TCI state with DMRS bundling |
NTT DOCOMO, INC. |
| R1-2301740 |
Correction for window restart with DMRS bundling |
Ericsson |
| R1-2301942 |
FL summary of discussion on joint channel estimation for Rel-17 NR coverage enhancements |
Moderator (China Telecom) |
| R1-2302058 |
Session notes for 8.8 (NR coverage enhancement) |
Ad-hoc Chair (CMCC) |
| 8.10 |
Maintenance on Enhancements to Integrated Access and Backhaul |
|
| R1-2300134 |
Remaining issues on resource multiplexing for IAB |
Huawei, HiSilicon |
| R1-2300774 |
Draft CR Regarding IAB Availability Combinations |
Nokia, Nokia Shanghai Bell |
| R1-2300775 |
Draft CR editorial correction on IAB RRC parameters |
Nokia, Nokia Shanghai Bell |
| R1-2301081 |
Correction on the availability of a soft RB set in an RB set group in TS 38.213 |
ZTE, Sanechips |
| R1-2301237 |
Maintenance on Enhancements to NR IAB |
Samsung |
| R1-2301719 |
Correction on dynamic indication of availability for IAB |
Huawei, HiSilicon |
| R1-2301761 |
Correction on TDM/FDM H/S/NA switching in eIAB |
Ericsson |
| R1-2301762 |
Discussion on TDM/FDM H/S/NA switching in eIAB |
Ericsson |
| R1-2301763 |
Correction on availability indication in eIAB |
Ericsson |
| R1-2301998 |
Summary of [112-R17-IAB] |
Moderator (Qualcomm) |
| R1-2302005 |
Summary of reply LS to R1-2300006 (RAN3 LS on RB set configuration) |
Moderator (ZTE) |
| R1-2302107 |
Summary#2 of [112-R17-IAB] |
Moderator (Qualcomm) |
| R1-2302128 |
Summary#2 of reply LS to R1-2300006 (RAN3 LS on RB set configuration) |
Moderator (ZTE) |
| R1-2302129 |
Draft reply LS on RB set configuration |
Moderator (ZTE) |
| R1-2302130 |
Reply LS on RB set configuration |
RAN1, ZTE |
| R1-2302199 |
DRAFT Correction on availability indication for eIAB |
Moderator (Qualcomm) |
| R1-2302215 |
Correction on availability indication for eIAB |
Moderator (Qualcomm), Huawei, HiSilicon, Ericsson |
| R1-2302216 |
CR editorial correction on IAB RRC parameters |
Moderator (Qualcomm), Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2302217 |
Correction on the availability of a soft RB set in an RB set group in TS 38.213 |
Moderator (Qualcomm), ZTE, Sanechips |
| 8.11 |
Maintenance on NR Sidelink enhancement |
|
| R1-2300105 |
Correction on description of random resource selection in TS 38.214 |
Huawei, HiSilicon |
| R1-2300106 |
Correction on UE-A is the destination UE of a TB transmitted by UE-B in TS 38.214 |
Huawei, HiSilicon |
| R1-2300199 |
Corrections on misalignment for RRC parameters in TS 38.213 |
Spreadtrum Communications, vivo |
| R1-2300200 |
Clarification for preferred or non-preferred resource set indication |
Spreadtrum Communications, OPPO, vivo |
| R1-2300201 |
Clarification of the contiguous partial sensing window |
Spreadtrum Communications |
| R1-2300315 |
Correction on the operation of re-evaluation and/or pre-emption checking for partial sensing |
Spreadtrum Communications, vivo |
| R1-2300421 |
Correction on missing field descriptions of SCI 2-C |
vivo |
| R1-2300422 |
Correction on the sensing occasions for periodic-based partial sensing |
vivo |
| R1-2300505 |
Some editorial issues in NR_SL_enh - incorrectly implemented TPs |
Nokia, Nokia Shanghai Bell |
| R1-2300628 |
Correction on the operations of partial sensing |
CATT, GOHIGH |
| R1-2300629 |
Correction on resource exclusion behavior with non-preferred resource set |
CATT, GOHIGH |
| R1-2300630 |
Correction on the time gap between PSFCH and corresponding SCI format 1-A |
CATT, GOHIGH |
| R1-2300790 |
Clarification on determination of preferred and non-preferred resource set for IUC scheme 1 |
Sharp |
| R1-2300791 |
Clarification on pre-emption and re-evaluation for periodic transmission in partial sensing |
Sharp |
| R1-2300792 |
Clarification on Preserve for periodic based partial sensing |
Sharp |
| R1-2300793 |
Clarification on candidate slots for aperiodic transmission in partial sensing |
Sharp |
| R1-2301082 |
Correction on parameter description for sidelink partial sensing in TS 38.214 |
ZTE, Sanechips |
| R1-2301083 |
Miscellaneous corrections on sensing and IUC parameters in TS 38.214 |
ZTE, Sanechips |
| R1-2301084 |
Correction on sidelink power control procedure in TS 38.213 |
ZTE, Sanechips |
| R1-2301085 |
Correction on IUC scheme 2 in TS 38.213 |
ZTE, Sanechips |
| R1-2301128 |
[Draft] Clarification on valid PSFCH occasions for resource conflict information |
Ericsson |
| R1-2301474 |
Draft CR on half-duplex consideration for SL re-evaluation/pre-emption check |
NTT DOCOMO, INC. |
| R1-2301704 |
Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 |
Huawei, HiSilicon |
| R1-2301807 |
FL summary #1 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2301808 |
FL summary #2 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2301809 |
FL summary #3 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2301810 |
FL summary #4 for AI 8.11: R17 eSL power saving RA maintenance |
Moderator (OPPO) |
| R1-2301811 |
FL summary for AI 8.11: R17 eSL power saving RA maintenance (EOM) |
Moderator (OPPO) |
| R1-2301851 |
Feature lead summary #1 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2301852 |
Feature lead summary #2 for AI 8.11: Inter-UE coordination for Mode 2 enhancements and others |
Moderator (LG Electronics) |
| R1-2302059 |
Session notes for 8.11 (Maintenance on NR Sidelink enhancement) |
Ad-Hoc Chair (Huawei) |
| R1-2302073 |
Discussion summary on default CBR configuration LS from RAN2 |
Moderator (OPPO) |
| R1-2302077 |
Clarification of a field in SCI format 2-C indicating the time offset of the first resource of each tuple with respect to the reference slot |
Moderator (LG Electronics) |
| R1-2302078 |
Clarification on the timeline of transmitting/receiving PSFCH with control information |
Moderator (LG Electronics) |
| R1-2302079 |
Correction on the resource selection mechanism indicated by higher layer |
Moderator (LG Electronics) |
| R1-2302159 |
Clarification of a field in SCI format 2-C indicating the time offset of the first resource of each tuple with respect to the reference slot |
Moderator (LG Electronics), ZTE, Sanechips, Spreadtrum Communications, vivo, Samsung, Intel Corporation |
| R1-2302160 |
Clarification on the timeline of transmitting/receiving PSFCH with control information |
Moderator (LG Electronics), ZTE, Sanechips, Spreadtrum Communications, vivo, Samsung, Intel Corporation |
| R1-2302161 |
Correction on the resource selection mechanism indicated by higher layer |
Moderator (LG Electronics), ZTE, Sanechips, Spreadtrum Communications, vivo, Samsung, Intel Corporation, Huawei, HiSilicon |
| R1-2302174 |
Reply LS to RAN2 on default CBR configuration |
RAN1, OPPO |
| R1-2302175 |
Correction on reservation periodicity for re-evaluation and pre-emption checking |
Moderator (OPPO), ZTE, Sanchips, vivo, Spreadtrum, ITL, Huawei, HiSilicon, Samsung, CATT, GOHIGH, Intel |
| R1-2302176 |
Correction on periodic-based partial sensing occasion index |
Moderator (OPPO), ZTE, Sanchips, vivo, Spreadtrum, ITL, Huawei, HiSilicon, Samsung, CATT, GOHIGH, Intel |
| R1-2302177 |
Correction on resource selection based on decoded PSCCH and measured RSRP |
Moderator (OPPO), ZTE, Sanchips, vivo, Spreadtrum, ITL, Huawei, HiSilicon, Samsung, CATT, GOHIGH, Intel |
| R1-2302178 |
Correction on the parameter description for Y’ candidate slots |
Moderator (OPPO), ZTE, Sanchips, vivo, Spreadtrum, ITL, Huawei, HiSilicon, Samsung, CATT, GOHIGH, Intel |
| 8.12 |
Maintenance on NR Multicast and Broadcast Services |
|
| R1-2300075 |
Draft CR on not applying disabled HARQ-ACK to multicast SPS PDSCH without PDCCH scheduling |
Huawei, HiSilicon, CBN |
| R1-2300076 |
Draft CR on retransmission schemes for MBS HARQ-ACK feedback to TS38.213 |
Huawei, HiSilicon, CBN |
| R1-2300077 |
Draft CR on UL DAI applying to G-CS-RNTI DAI counting |
Huawei, HiSilicon, CBN |
| R1-2300078 |
Draft CR on multicast HARQ-ACK |
Huawei, HiSilicon, CBN |
| R1-2300423 |
Discussion on SPS PDSCH retransmission for FDMed unicast PDSCH and multicast PDSCH |
vivo |
| R1-2300424 |
Draft CR on FDMed unicast PDSCH and multicast PDSCH to TS38.214 |
vivo |
| R1-2300425 |
Draft CR on SPS and dynamic scheduling PDSCH(s) collision for MBS |
vivo |
| R1-2300426 |
Correction on PUCCH determination for NACK only mode 1 for SPS PDSCH |
vivo |
| R1-2300427 |
Draft CR on not applying disabled HARQ-ACK to multicast SPS PDSCH activation and deactivation |
vivo |
| R1-2300428 |
Draft CR on type 3 HARQ-ACK codebook for unicast and multicast |
vivo |
| R1-2300429 |
Discussion on more than 2bits HARQ-ACK for SPS PDSCHs with NACK only feedback mode |
vivo |
| R1-2300430 |
Discussion on overlapping among NACK PUCCH, SR PUCCH and other PUCCH/PUSCH |
vivo |
| R1-2300431 |
Draft CR on overlapping among NACK PUCCH, SR PUCCH and other PUCCH/PUSCH |
vivo |
| R1-2300631 |
Draft editorial CR on DCI format 4_2 in TS 38.212 |
CATT, CBN |
| R1-2300632 |
Draft CR on the parameter maxNrofCodeWordsScheduledByDCI for multicast |
CATT, CBN |
| R1-2300633 |
Discussion on Type1 HARQ codebook generation for fdmed-ReceptionMulticast |
CATT, CBN |
| R1-2300634 |
Draft CR on Type1 HARQ codebook generation for fdmed-ReceptionMulticast |
CATT, CBN |
| R1-2300635 |
Draft CR on K1 generation for type1-Codebook-GenerationMode |
CATT, CBN |
| R1-2300636 |
Draft editorial CR on resource allocation table for multicast in 38.214 |
CATT, CBN |
| R1-2300637 |
Discussion on HARQ ACK timing description for multicast |
CATT, CBN |
| R1-2300638 |
Draft CR on HARQ ACK timing description for multicast |
CATT, CBN |
| R1-2300639 |
Correction on DCI field when two HARQ-ACK codebooks are configured |
CATT, CBN |
| R1-2300924 |
Remaining Issues on Group Scheduling Mechanisms for RRC_CONNECTED Ues supporting MBS |
Nokia, Nokia Shanghai Bell |
| R1-2300925 |
Draft CR on Disabled HARQ-ACK Not Applied to SPS Activation to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2300978 |
Draft CR on SPS release PDCCH validation of DCI with CS-RNTI |
CMCC |
| R1-2300979 |
Draft CR on PDCCH validation for single multicast SPS |
CMCC |
| R1-2300980 |
Draft CR on FDMed unicast PDSCH and group-common PDSCH |
CMCC |
| R1-2300981 |
Draft CR on SPS and dynamic scheduling PDSCH(s) collision for MBS |
CMCC |
| R1-2301030 |
Draft CR on Counting and Ordering of HARQ-ACK bits for NACK-only Feedback Mode 2 to TS38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2301032 |
Draft correction on monitoring for DCI format 4_0 on Type0-PDCCH CSS to TS 38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2301033 |
Draft CR on SPS PDSCH collisions with DG PDSCH for TS38.214 |
Nokia, Nokia Shanghai Bell |
| R1-2301087 |
Draft CR on configuration of G-RNTI / G-CS-RNTI per serving cell |
Lenovo |
| R1-2301088 |
Draft CR on HARQ-ACK feedback for multicast SPS activation/deactivation |
Lenovo |
| R1-2301089 |
Draft CR on multicast HARQ-ACK information in a Type-3 HARQ-ACK codebook |
Lenovo |
| R1-2301090 |
Draft CR on processing timeline for NACK-only mode 2 for multicast |
Lenovo |
| R1-2301104 |
Draft CR on multicast HARQ-ACK |
LG Electronics |
| R1-2301105 |
Draft CR on sps-ConfigDeactivationStateList |
LG Electronics |
| R1-2301238 |
Correction on HARQ-ACK reporting for the “NACK-only” mode in MBS |
Samsung |
| R1-2301239 |
Correction on supporting multiple G-RNTIs/G-SC-RNTIs for the “NACK-only” mode in MBS |
Samsung |
| R1-2301240 |
Correction on multiplexing Type-2 HARQ-ACK codebook in a PUSCH |
Samsung |
| R1-2301241 |
Correction on multiplexing NACK-only HARQ-ACK and CSI and SR in a PUCCH |
Samsung |
| R1-2301242 |
Correction on FDMed unicast and multicast PDSCH receptions |
Samsung |
| R1-2301388 |
Remaining issues for NR MBS |
Qualcomm Incorporated |
| R1-2301389 |
Draft CR on G-RNTI/G-CS-RNTI not configured with harq-FeedbackEnablerMulticast |
Qualcomm Incorporated |
| R1-2301390 |
Draft CR on first HARQ feedback mode for multicast SPS activation/deactivation |
Qualcomm Incorporated |
| R1-2301449 |
Draft editorial CR on RRC signaling for Type-1 codebook for MBS |
ZTE |
| R1-2301450 |
Draft CR on the generation of the type1 HARQ-ACK codebook |
ZTE |
| R1-2301451 |
Draft 213 CR on broadcast PDCCH monitoring in active DL BWP |
ZTE |
| R1-2301452 |
Draft 213 CR on feedback mode for SPS |
ZTE |
| R1-2301453 |
Draft 214 CR on FDM reception |
ZTE |
| R1-2301454 |
Draft 213 CR on PUCCH resource for SPS PDSCH for MBS for NACK-only mode |
ZTE |
| R1-2301455 |
Draft 213 CR on PUCCH resource configuration for MBS |
ZTE |
| R1-2301456 |
Draft CR on intra-UE multiplexing for MBS |
ZTE |
| R1-2301457 |
Draft CR on intra-UE multiplexing with NACK-only PUCCH |
ZTE |
| R1-2301458 |
Draft CR on the Type-3 codebook for MBS |
ZTE |
| R1-2301462 |
Correction on HARQ feedback for multicast SPS (de)activation |
ASUSTeK |
| R1-2301475 |
Draft CR to support NACK-only feedback with multiple G-RNTIs |
NTT DOCOMO, INC. |
| R1-2301612 |
Remaining issues on NR MBS |
MediaTek Inc. |
| R1-2301613 |
Corrections on HARQ-ACK for multicast SPS |
MediaTek Inc. |
| R1-2301614 |
Correction on HARQ-ACK for multicast NACK only mode 2 |
MediaTek Inc. |
| R1-2301622 |
Correction on rate match patter number for MBS broadcast reception |
MediaTek Inc. |
| R1-2301669 |
Draft CR on UE behavior for FDMed unicast and SPS retransmission for multicast |
Ericsson |
| R1-2301670 |
Draft CR on collision handling for SPS and dynamic scheduling PDSCH |
Ericsson |
| R1-2301671 |
Draft CR to 38.213 for NACK only mode 2 configuration with multiple G-RNTI |
Ericsson |
| R1-2301672 |
Draft CR to 38.213 for PTP retransmissions of PTM |
Ericsson |
| R1-2301673 |
Draft CR to 38.213 for the use of HARQ with multicast SPS activation and release |
Ericsson |
| R1-2301674 |
Draft CR to 38.213 for HARQ process enabling for MBS |
Ericsson |
| R1-2301675 |
Draft CR to 38.214 on DCI for enable/disable HARQ for MBS |
Ericsson |
| R1-2301676 |
Maintenance on NR Multicast and Broadcast Services |
Ericsson |
| R1-2301700 |
Draft CR on FDM unicast PDSCH and GC-PDSCH |
Huawei, HiSilicon, CBN |
| R1-2301701 |
Draft CR on collision handling between SPS and DG for MBS |
Huawei, HiSilicon, CBN |
| R1-2301713 |
Remaining issues for Rel-17 MBS |
Huawei, HiSilicon, CBN |
| R1-2301714 |
Draft CR on PDCCH validation for multicast SPS |
Huawei, HiSilicon, CBN |
| R1-2301715 |
Draft CR on HARQ-ACK codebook generation for multicast SPS |
Huawei, HiSilicon, CBN |
| R1-2301786 |
Remaining issues on NR MBS |
MediaTek Inc. |
| R1-2301787 |
Corrections on HARQ-ACK for multicast SPS |
MediaTek Inc. |
| R1-2301788 |
Correction on HARQ-ACK for multicast NACK only mode 2 |
MediaTek Inc. |
| R1-2301789 |
Correction on K1 determination for multicast Type-1 CB |
MediaTek Inc. |
| R1-2301826 |
Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2301827 |
Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS |
Moderator (CMCC) |
| R1-2301917 |
FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2301918 |
FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2301919 |
FLS#3 on the HARQ-ACK related issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2301920 |
Draft CR on Type-1 HARQ-ACK codebook multiplexing for unicast and multicast |
Moderator (Huawei) |
| R1-2301921 |
Draft CR on aligning DCI sizes when configuring two HARQ-ACK codebooks for multicast |
Moderator (Huawei) |
| R1-2301922 |
Draft CR on not applying disabled HARQ-ACK for multicast SPS activation/deactivation |
Moderator (Huawei) |
| R1-2301923 |
Draft CR on retransmission schemes for MBS |
Moderator (Huawei) |
| R1-2301924 |
Draft CR on HARQ-ACK timing for multicast |
Moderator (Huawei) |
| R1-2301925 |
Draft CR on multiplexing Type-2 HARQ-ACK codebook in a PUSCH |
Moderator (Huawei) |
| R1-2301926 |
Draft CR on PUCCH resources for multiplexing multicast HARQ-ACK |
Moderator (Huawei) |
| R1-2301927 |
Draft CR on clarifying Type-3 HARQ-ACK codebook is supported for multicast |
Moderator (Huawei) |
| R1-2301992 |
Draft CR on SPS and dynamic scheduling PDSCH(s) collision for MBS |
Moderator (CMCC), vivo, Ericsson, Huawei, HiSilicon, CBN |
| R1-2301993 |
Draft CR on rate matching pattern number for MBS broadcast reception |
Moderator (CMCC), MediaTek |
| R1-2301994 |
Discussion related to LS on unicast and multicast SPS |
Moderator (ASUSTeK) |
| R1-2302039 |
CR on aligning DCI sizes when configuring two HARQ-ACK codebooks for multicast |
Moderator (Huawei), CATT |
| R1-2302040 |
CR on HARQ-ACK timing for multicast |
Moderator (Huawei), CATT, MediaTek, ZTE, Qualcomm |
| R1-2302041 |
CR on multiplexing Type-2 HARQ-ACK codebook in a PUSCH |
Moderator (Huawei), HiSilicon, CBN, Samsung |
| R1-2302060 |
Session notes for 8.12 (Maintenance on NR Multicast and Broadcast Services) |
Ad-Hoc Chair (Huawei) |
| R1-2302076 |
Draft CR on FDMed unicast PDSCH and group-common PDSCH |
Moderator (CMCC), vivo, Samsung, ZTE, Ericsson, Huawei, HiSilicon, CBN |
| R1-2302133 |
CR on SPS and dynamic scheduling PDSCH(s) collision for MBS |
Moderator (CMCC), vivo, Ericsson, Huawei, HiSilicon, CBN |
| R1-2302134 |
CR on broadcast PDCCH monitoring in active DL BWP |
Moderator (CMCC), ZTE |
| R1-2302166 |
Draft CR on PUCCH resource for UE configured with NACK-only mode2 for SPS |
Moderator (Huawei) |
| R1-2302167 |
Further discussion related to LS on unicast and multicast SPS |
Moderator (ASUSTeK) |
| R1-2302168 |
[Draft] Reply LS on SPS configuration for unicast and multicast |
Moderator (ASUSTeK) |
| R1-2302190 |
Draft CR on FDMed unicast PDSCH and group-common PDSCH |
Moderator (CMCC), vivo, Samsung, ZTE, Ericsson, Huawei, HiSilicon, CBN |
| R1-2302191 |
CR on FDMed unicast PDSCH and group-common PDSCH |
Moderator (CMCC), vivo, Samsung, ZTE, Ericsson, Huawei, HiSilicon, CBN |
| R1-2302192 |
CR on rate matching pattern number for MBS broadcast reception |
Moderator (CMCC), MediaTek |
| R1-2302205 |
CR on PUCCH resource for UE configured with NACK-only mode2 for SPS |
Moderator (Huawei), ZTE |
| R1-2302206 |
CR on PUCCH resources for multiplexing multicast HARQ-ACK |
Moderator (Huawei), vivo |
| R1-2302209 |
Reply LS on SPS configuration for unicast and multicast |
RAN1, ASUSTeK |
| 8.14 |
Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network |
|
| R1-2300116 |
Discussion on SIB accumulation for IoT NTN |
Huawei, HiSilicon |
| R1-2300262 |
Discussion on UE processing time for Rel-17 IoT NTN |
OPPO |
| R1-2300263 |
Draft LS on UE processing time for Rel-17 IoT NTN |
OPPO |
| R1-2300318 |
CR: Including J2000 reference frame in orbital parameters description |
Gatehouse Satcom A/S, Nordic, Sateliot |
| R1-2300358 |
Draft CR on corrections to eMTC support for NTN |
OPPO |
| R1-2301152 |
Maintenance for IoT NTN |
Ericsson |
| R1-2301391 |
Definition of timelines for eMTC / NB-IoT over NTN |
Qualcomm Incorporated |
| R1-2301568 |
Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network |
Nokia, Nokia Shanghai Bell |
| R1-2301739 |
Draft CR on correction of UE capability parameter name in 36.211 |
Nokia, Nokia Shanghai Bell |
| R1-2301747 |
Discussion on processing time for downlink reception with Koffset for IoT NTN |
Huawei, HiSilicon |
| R1-2301858 |
FL summary#1 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN |
Moderator (Sony) |
| R1-2301859 |
FL summary#2 of AI 8.14: Maintenance on Timing Relationships for IoT-NTN |
Moderator (Sony) |
| R1-2301860 |
Summary#1 of [112-R17-IoT_NTN] Email discussion |
Moderator (MediaTek) |
| R1-2301861 |
Summary#2 of [112-R17-IoT_NTN] Email discussion |
Moderator (MediaTek) |
| R1-2302017 |
Draft CR on correction of UE capability parameter name in 36.211 |
Moderator (MediaTek), Nokia, Nokia Shanghai Bell |
| R1-2302018 |
CR on corrections to eMTC support for NTN |
Moderator (Sony) |
| R1-2302061 |
Session notes for 8.14 (Maintenance on NB-IoT/eMTC support for Non-Terrestrial Network) |
Ad-Hoc Chair (Huawei) |
| R1-2302147 |
CR on correction of UE capability parameter name in 36.211 |
Moderator (MediaTek), Nokia, Nokia Shanghai Bell, Ericsson |
| R1-2302181 |
CR on corrections to eMTC support for IoT NTN in TDD |
Moderator (Sony), OPPO |
| 8.16 |
Rel-17 UE features |
|
| R1-2302024 |
Updated RAN1 UE features list for Rel-17 NR after RAN1 #112 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2302025 |
Draft LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2302026 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#112 |
RAN1, AT&T, NTT DOCOMO, INC. |
| 8.16.1 |
UE features topics 1 |
|
| R1-2300140 |
Remaining issues for UE features topics 1 |
Nokia, Nokia Shanghai Bell |
| R1-2300202 |
UE features for R17 NR MBS |
Spreadtrum Communications |
| R1-2300337 |
Discussion on UE features for topics 1 |
ZTE |
| R1-2300432 |
Remaining issues on Rel-17 MBS UE features |
vivo |
| R1-2301392 |
Discussion on Rel-17 UE features topic 1 |
Qualcomm Incorporated |
| R1-2301476 |
Discussion on remaining issues regarding Rel-17 RAN1 UE features topics 1 |
NTT DOCOMO, INC. |
| R1-2301615 |
Views on UE feature Topic 1 |
MediaTek Inc. |
| R1-2301677 |
UE capabilities for NR MBS |
Ericsson |
| R1-2301703 |
Remaining issues for UE features topics 1 |
Huawei, HiSilicon |
| R1-2301800 |
Summary#1 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2301802 |
Session Notes for R17 UE Features 1 |
Moderator (NTT DOCOMO, INC.) |
| R1-2302022 |
Summary#2 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| R1-2302023 |
Summary#3 on UE features for NR MBS |
Moderator (NTT DOCOMO, INC.) |
| 8.16.2 |
UE features topics 2 |
|
| R1-2301221 |
Summary of UE features topics 2 |
Moderator (AT&T) |
| R1-2301243 |
Discussions on Rel-17 UE features for NR positioning on additional path reporting |
Samsung |
| R1-2301393 |
Discussion on Rel-17 UE features topic 2 |
Qualcomm Incorporated |
| R1-2302008 |
Session Notes of AI 8.16.2 |
Ad-Hoc Chair (AT&T) |
| 8.16.3 |
Other |
|
| R1-2301394 |
Discussion on Rel-17 UE features other than topic 1 and 2 |
Qualcomm Incorporated |
| 8.17 |
Other |
|
| R1-2300433 |
Correction on SCS of the reference slot restriction of Rel-17 TX switching |
vivo |
| R1-2300434 |
Correction of CG PUSCH repetition in SDT |
vivo |
| R1-2300435 |
Correction of SSBs mapped to CG PUSCH in SDT |
vivo |
| R1-2300541 |
Discussion on physical layer aspects of small data transmission |
xiaomi |
| R1-2300610 |
Correction on repetition for CG-SDT in TS 38.213 |
ZTE Corporation |
| R1-2300931 |
Correction on CG-PUSCH repetitions for CG-SDT operation |
Intel Corporation |
| R1-2301134 |
Discussion on communication via satellite to unmodified UEs |
Vodafone |
| R1-2301244 |
Maintenance on small data transmission |
Samsung |
| R1-2301769 |
Discussion on physical layer aspects of small data transmission |
xiaomi |
| R1-2301943 |
FL summary of discussion on Rel-17 UL Tx switching |
Moderator (China Telecom) |
| R1-2301962 |
Summary #1 on Rel-17 SDT |
Moderator (ZTE) |
| R1-2302062 |
Session notes for 8.17 (Other) |
Ad-hoc Chair (CMCC) |
| R1-2302135 |
Summary#2 on Rel-17 SDT |
Moderator (ZTE) |
| R1-2302136 |
[Draft] Correction on repetition for CG-SDT |
Moderator (ZTE), Samsung, vivo, Intel |
| R1-2302137 |
Correction on repetition for CG-SDT |
Moderator(ZTE), Samsung, vivo, Intel |
| R1-2302148 |
Draft reply LS on reduced 1024QAM capability |
Moderator (Huawei) |
| R1-2302149 |
Summary of discussion on LS on reduced 1024 QAM capability |
Moderator (Huawei) |
| R1-2302204 |
Summary#3 on Rel-17 SDT |
Moderator (ZTE) |
| R1-2302211 |
Reply LS on reduced 1024QAM capability |
RAN1, Huawei |
| 9.1.1.1 |
Unified TCI framework extension for multi-TRP |
|
| R1-2300048 |
Unified TCI framework extension for multi-TRP |
FUTUREWEI |
| R1-2300093 |
Discussion on unified TCI framework extension for multi-TRP |
Huawei, HiSilicon |
| R1-2300156 |
Details on Unified TCI Extension for MTRP |
InterDigital, Inc. |
| R1-2300181 |
Enhancements on unified TCI framework extension for multi-TRP |
ZTE |
| R1-2300203 |
Discussion on unified TCI framework extension for multi-TRP |
Spreadtrum Communications |
| R1-2300248 |
Unified TCI framework extension for multi-TRP |
OPPO |
| R1-2300327 |
Unified TCI framework extension for multi-TRP |
Panasonic |
| R1-2300333 |
Unified TCI framework extension for multi-TRP |
Ericsson |
| R1-2300436 |
Further discussion on unified TCI framework extension for multi-TRP |
vivo |
| R1-2300487 |
Discussion on unified TCI framework extension for multi-TRP |
FGI |
| R1-2300503 |
Multi-TRP enhancements for the unified TCI framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2300510 |
Discussion of unified TCI framework for multi-TRP |
Lenovo |
| R1-2300522 |
Unified TCI framework extension for multi-TRP/panel |
LG Electronics |
| R1-2300545 |
Unified TCI framework extension for multi-TRP |
xiaomi |
| R1-2300600 |
Discussion on unified TCI framework extension for multi-TRP operation |
TCL Communication Ltd. |
| R1-2300650 |
Further discussions on unified TCI framework extension for multi-TRP operation |
CATT |
| R1-2300740 |
Discussion on unified TCI framework extension for MTRP |
Fujitsu |
| R1-2300820 |
Discussion on unified TCI framework extension for multi-TRP |
NEC |
| R1-2300847 |
Unified TCI framework extension for multi-TRP |
Sharp |
| R1-2300865 |
Discussion on unified TCI framework extension for multi-TRP |
Sony |
| R1-2300899 |
Discussion on unified TCI framework extension for multi-TRP |
Hyundai Motor Company |
| R1-2300932 |
Unified TCI Framework for Multi-TRP |
Intel Corporation |
| R1-2300982 |
Discussion on unified TCI framework extension for multi-TRP |
CMCC |
| R1-2301165 |
Discussion on unified TCI framework extension for multi-TRP |
Google |
| R1-2301245 |
Views on unified TCI extension focusing on m-TRP |
Samsung |
| R1-2301318 |
Discussion on unified TCI framework extension for multi-TRP |
ITRI |
| R1-2301329 |
Unified TCI framework Extension for mTRP |
Apple |
| R1-2301395 |
Extension of unified TCI framework for mTRP |
Qualcomm Incorporated |
| R1-2301461 |
Discussion on sDCI mTRP PDSCH regarding eUTCI framework |
ASUSTeK |
| R1-2301477 |
Discussion on unified TCI framework extension for multi-TRP |
NTT DOCOMO, INC. |
| R1-2301580 |
Unified TCI framework extension for multi-TRP |
MediaTek Inc. |
| R1-2301642 |
Unified TCI framework extension for multi-TRP |
Nokia, Nokia Shanghai Bell |
| R1-2301686 |
Discussion on Unified TCI framework extension for multi-TRP |
CEWiT |
| R1-2301773 |
Moderator summary on extension of unified TCI framework (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2302000 |
Moderator summary on extension of unified TCI framework (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2302123 |
Moderator summary on extension of unified TCI framework (Round 2) |
Moderator (MediaTek Inc.) |
| 9.1.1.2 |
Two TAs for multi-DCI |
|
| R1-2300049 |
Enhancements to support two TAs for multi-DCI |
FUTUREWEI |
| R1-2300094 |
Study on TA enhancement for UL M-TRP transmission |
Huawei, HiSilicon |
| R1-2300157 |
Discussion on mTRP with Multiple TA |
InterDigital, Inc. |
| R1-2300182 |
TA enhancement for multi-DCI |
ZTE |
| R1-2300204 |
Discussion on two TAs for multi-DCI based multi-TRP |
Spreadtrum Communications |
| R1-2300249 |
Two TAs for multi-DCI based multi-TRP operation |
OPPO |
| R1-2300334 |
Two TAs for multi-DCI |
Ericsson |
| R1-2300359 |
Discussion on two TAs for multi-DCI based on multi-TRP operation |
TCL Communication Ltd. |
| R1-2300437 |
Further discussion on two TAs for multi-DCI-based multi-TRP operation |
vivo |
| R1-2300489 |
Discussion on two TAs for multi-DCI |
FGI |
| R1-2300511 |
Discussion of two TAs for multi-DCI UL transmission |
Lenovo |
| R1-2300523 |
Two TAs for multi-TRP/panel |
LG Electronics |
| R1-2300546 |
Discussion on two TAs for multi-TRP operation |
xiaomi |
| R1-2300651 |
On Two TAs for UL multi-DCI multi-TRP operation |
CATT |
| R1-2300821 |
Discussion on two TAs for multi-DCI |
NEC |
| R1-2300919 |
Two TAs for multi-DCI |
Sharp |
| R1-2300933 |
On two TAs for multi-DCI |
Intel Corporation |
| R1-2300983 |
Discussion on two TAs for multi-DCI |
CMCC |
| R1-2301166 |
Discussion on two TAs for multi-DCI |
Google |
| R1-2301246 |
Views on two TAs for m-DCI |
Samsung |
| R1-2301330 |
Views on Two TAs for mDCI mTRP |
Apple |
| R1-2301396 |
Supporting two TAs for multi-DCI based mTRP |
Qualcomm Incorporated |
| R1-2301478 |
Discussion on two TAs for multi-DCI |
NTT DOCOMO, INC. |
| R1-2301581 |
UL Tx Timing Management for MTRP Operation |
MediaTek Inc. |
| R1-2301643 |
Two TAs for UL multi-DCI multi-TRP operation |
Nokia, Nokia Shanghai Bell |
| R1-2301904 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2302044 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2302111 |
Moderator Summary #3 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| 9.1.2 |
CSI enhancement |
|
| R1-2300095 |
CSI enhancement for coherent JT and mobility |
Huawei, HiSilicon |
| R1-2300158 |
Enhanced CSI for CJT and Medium/High UE Velocities |
InterDigital, Inc. |
| R1-2300183 |
CSI enhancement for high/medium UE velocities and CJT |
ZTE |
| R1-2300205 |
Discussion on CSI enhancement for high/medium UE velocities and coherent JT |
Spreadtrum Communications |
| R1-2300250 |
CSI enhancement for high/medium UE velocities and coherent JT |
OPPO |
| R1-2300391 |
On CSI Enhancement |
Google |
| R1-2300438 |
Further discussion on CSI enhancement for high-medium UE velocities and coherent JT |
vivo |
| R1-2300502 |
CSI enhancements for medium UE velocities and coherent JT |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2300512 |
Discussion of CSI enhancement for high speed UE and coherent JT |
Lenovo |
| R1-2300524 |
Potential CSI enhancement for high/medium UE velocities and coherent JT |
LG Electronics |
| R1-2300547 |
Discussion on CSI enhancement for high/medium UE velocities and CJT |
xiaomi |
| R1-2300652 |
Discussion on CSI enhancement |
CATT |
| R1-2300741 |
Views on CSI enhancement for coherent-JT and mobility |
Fujitsu |
| R1-2300812 |
Discussion on CSI enhancement |
NEC |
| R1-2300866 |
More considerations on CSI enhancement for high/medium UE velocities and CJT |
Sony |
| R1-2300900 |
Discussion on CSI enhancement |
Mavenir |
| R1-2300934 |
On CSI enhancements |
Intel Corporation |
| R1-2300984 |
Discussion on CSI enhancement for high/medium UE velocities and CJT |
CMCC |
| R1-2301219 |
Views on CSI Enhancements for CJT |
AT&T |
| R1-2301247 |
Moderator summary on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2301248 |
Summary of OFFLINE discussion on Rel-18 MIMO CSI |
Moderator (Samsung) |
| R1-2301249 |
Views on CSI enhancements |
Samsung |
| R1-2301331 |
Views on Rel-18 MIMO CSI enhancement |
Apple |
| R1-2301397 |
CSI enhancements for medium UE velocities and Coherent-JT |
Qualcomm Incorporated |
| R1-2301479 |
Discussion on CSI enhancement |
NTT DOCOMO, INC. |
| R1-2301525 |
CSI enhancements |
SHARP Corporation |
| R1-2301526 |
On CSI enhancements for NR MIMO evolution |
Ericsson |
| R1-2301573 |
CSI Enhancements |
MediaTek Inc. |
| R1-2301644 |
CSI enhancement for high/medium UE velocities and CJT |
Nokia, Nokia Shanghai Bell |
| R1-2301771 |
On CSI Enhancement |
Google |
| R1-2301944 |
Views on CSI enhancements |
Samsung |
| R1-2301961 |
Views on CSI enhancements |
Samsung |
| R1-2301987 |
Moderator Summary#2 on Rel-18 CSI enhancements: ROUND 1 |
Moderator (Samsung) |
| R1-2301988 |
Moderator Summary for Tue offline on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2301989 |
Moderator Summary for Wed offline on Rel-18 CSI enhancements |
Moderator (Samsung) |
| R1-2302102 |
Moderator Summary#3 on Rel-18 CSI enhancements: ROUND 2 |
Moderator (Samsung) |
| R1-2302224 |
Moderator Summary#4 on Rel-18 CSI enhancements: ROUND 3 |
Moderator (Samsung) |
| R1-2302225 |
DRAFT LS to RAN2/4 on Agreements for Rel-18 MIMO |
Moderator (Samsung) |
| R1-2302226 |
LS to RAN2/4 on Agreements for Rel-18 MIMO |
RAN1, Samsung |
| 9.1.3.1 |
Increased number of orthogonal DMRS ports |
|
| R1-2300050 |
On increasing the number of orthogonal DM-RS ports for MU-MIMO |
FUTUREWEI |
| R1-2300096 |
Enhancements on DMRS in Rel-18 |
Huawei, HiSilicon |
| R1-2300152 |
Discussions on increased number of orthogonal DMRS ports |
New H3C Technologies Co., Ltd. |
| R1-2300159 |
Further Details on DMRS Enhancements |
InterDigital, Inc. |
| R1-2300184 |
DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO |
ZTE |
| R1-2300206 |
Discussion on increased number of orthogonal DMRS ports |
Spreadtrum Communications |
| R1-2300251 |
DMRS enhancement for Rel-18 MIMO |
OPPO |
| R1-2300392 |
On DMRS Enhancement |
Google |
| R1-2300439 |
Further discussion on DMRS enhancements |
vivo |
| R1-2300504 |
On increased number of orthogonal DMRS ports |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2300513 |
Discussion of increased number of orthogonal DMRS ports |
Lenovo |
| R1-2300525 |
Increased number of orthogonal DMRS ports |
LG Electronics |
| R1-2300548 |
Discussion on DMRS enhancement |
Xiaomi |
| R1-2300653 |
Discussion on DMRS enhancements in Rel-18 |
CATT |
| R1-2300782 |
On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO |
Ericsson |
| R1-2300813 |
Discussion on increased number of orthogonal DMRS ports |
NEC |
| R1-2300848 |
Increased number of orthogonal DMRS ports |
Sharp |
| R1-2300935 |
DMRS Enhancements for Rel-18 NR |
Intel Corporation |
| R1-2300985 |
Discussion on increased number of orthogonal DMRS ports |
CMCC |
| R1-2301250 |
Views on DMRS enhancements |
Samsung |
| R1-2301332 |
Views on supporting increased number of orthogonal DMRS ports |
Apple |
| R1-2301398 |
Design for increased number of orthogonal DMRS ports |
Qualcomm Incorporated |
| R1-2301480 |
Discussion on DMRS enhancements |
NTT DOCOMO, INC. |
| R1-2301574 |
Increased number of orthogonal DMRS ports |
MediaTek Inc. |
| R1-2301645 |
Rel-18 UL and DL DMRS Enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2301774 |
FL summary#1 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2301775 |
FL summary#2 on DMRS |
Moderator (NTT DOCOMO) |
| R1-2301776 |
FL summary#3 on DMRS |
Moderator (NTT DOCOMO) |
| 9.1.3.2 |
SRS enhancement targeting TDD CJT and 8 TX operation |
|
| R1-2300051 |
SRS enhancements for TDD CJT and 8TX operation |
FUTUREWEI |
| R1-2300097 |
SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 |
Huawei, HiSilicon |
| R1-2300160 |
SRS Enhancements for CJT and 8TX UEs |
InterDigital, Inc. |
| R1-2300185 |
SRS enhancement targeting TDD CJT and 8 TX operation |
ZTE |
| R1-2300207 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
Spreadtrum Communications |
| R1-2300252 |
SRS enhancement targeting TDD CJT and 8 TX operation |
OPPO |
| R1-2300393 |
On SRS Enhancement |
Google |
| R1-2300440 |
Further discussion on SRS enhancements |
vivo |
| R1-2300514 |
Discussion of SRS enhancement |
Lenovo |
| R1-2300526 |
SRS enhancement targeting TDD CJT and 8 TX operation |
LG Electronics |
| R1-2300549 |
Discussion on SRS enhancements |
xiaomi |
| R1-2300654 |
Discussion on SRS enhancement in Rel-18 |
CATT |
| R1-2300814 |
Discussion on SRS enhancement |
NEC |
| R1-2300849 |
SRS enhancement targeting TDD CJT and 8 TX operation |
Sharp |
| R1-2300936 |
Discussion on SRS enhancement in Rel-18 |
Intel Corporation |
| R1-2300986 |
Discussion on SRS enhancement targeting TDD CJT and 8 TX operation |
CMCC |
| R1-2301039 |
Discussion on SRS enhancement targeting TDD CJT |
ETRI |
| R1-2301077 |
On SRS enhancements targeting TDD CJT and 8 TX operation |
Ericsson |
| R1-2301251 |
Views on SRS enhancements |
Samsung |
| R1-2301317 |
Views on SRS enhancement targeting TDD CJT and 8 TX operation |
KDDI Corporation |
| R1-2301333 |
Views on Rel-18 MIMO SRS enhancement |
Apple |
| R1-2301399 |
SRS enhancement for TDD CJT and 8 Tx operation |
Qualcomm Incorporated |
| R1-2301481 |
Discussion on SRS enhancement |
NTT DOCOMO, INC. |
| R1-2301646 |
SRS enhancement for TDD CJT and 8Tx operation |
Nokia, Nokia Shanghai Bell |
| R1-2301877 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2301878 |
FL Summary #2 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2301879 |
FL Summary #3 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2301880 |
FL Summary #4 on SRS enhancements |
Moderator (FUTUREWEI) |
| 9.1.4.1 |
UL precoding indication for multi-panel transmission |
|
| R1-2300098 |
Discussion on UL precoding indication for multi-panel transmission |
Huawei, HiSilicon |
| R1-2300161 |
On Uplink Multi-panel Transmission |
InterDigital, Inc. |
| R1-2300186 |
Enhancements on UL precoding indication for multi-panel transmission |
ZTE |
| R1-2300208 |
Discussion on UL precoding indication for multi-panel transmission |
Spreadtrum Communications |
| R1-2300253 |
Discussion on UL precoding indication for multi-panel transmission |
OPPO |
| R1-2300328 |
UL Precoding for Multi-panel Transmission |
Panasonic |
| R1-2300394 |
On Simultaneous Multi-Panel Transmission |
Google |
| R1-2300441 |
Further discussion on UL precoding indication for multi-panel transmission |
vivo |
| R1-2300491 |
Discussion on simultaneous transmission on multiple panels |
FGI |
| R1-2300515 |
UL precoding indication for multi-panel transmission |
Lenovo |
| R1-2300527 |
UL precoding indication for multi-panel transmission |
LG Electronics |
| R1-2300550 |
Enhancements on multi-panel uplink transmission |
xiaomi |
| R1-2300655 |
Discussion on UL precoding indication for multi-panel transmission |
CATT |
| R1-2300742 |
Discussion on UL precoding indication for multi-panel transmission |
Fujitsu |
| R1-2300822 |
Discussion on UL precoding indication for multi-panel transmission |
NEC |
| R1-2300850 |
Views on UL multi-panel transmission |
Sharp |
| R1-2300937 |
UL precoding indication for multi-panel transmission (#112) |
Intel Corporation |
| R1-2300987 |
Discussion on UL precoding indication for multi-panel transmission |
CMCC |
| R1-2301076 |
UL precoding indication for multi-panel transmission |
Ericsson |
| R1-2301252 |
Views on UL precoding indication for STxMP |
Samsung |
| R1-2301334 |
Views on UL precoding indication for multi-panel simultaneous PUSCH transmissions |
Apple |
| R1-2301400 |
Simultaneous multi-panel transmission |
Qualcomm Incorporated |
| R1-2301460 |
Discussion on STxMP |
ASUSTeK |
| R1-2301482 |
Discussion on multi-panel transmission |
NTT DOCOMO, INC. |
| R1-2301582 |
Simultaneous transmission across multiple UE panels |
MediaTek Inc. |
| R1-2301647 |
Precoder Indication for Multi-Panel UL Transmission |
Nokia, Nokia Shanghai Bell |
| R1-2301819 |
Summary #1 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2301820 |
Summary #2 on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2301821 |
Summary #3 on Rel-18 STxMP |
Moderator (OPPO) |
| 9.1.4.2 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
|
| R1-2300099 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Huawei, HiSilicon |
| R1-2300162 |
Further Details on SRI/TPMI Enhancement for 8TX UE |
InterDigital, Inc. |
| R1-2300163 |
FL Summary SRI/TPMI Enhancements Preparatory |
Moderator (InterDigital, Inc.) |
| R1-2300164 |
FL Summary SRI/TPMI Enhancements First Round |
Moderator (InterDigital, Inc.) |
| R1-2300165 |
FL Summary SRI/TPMI Enhancements Second Round |
Moderator (InterDigital, Inc.) |
| R1-2300166 |
Recommended Direction on SRITPMI Enhancements for RAN1#112b |
Moderator (InterDigital, Inc.) |
| R1-2300187 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
ZTE |
| R1-2300209 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Spreadtrum Communications |
| R1-2300254 |
SRI TPMI enhancement for 8 TX UL transmission |
OPPO |
| R1-2300395 |
On SRI/TPMI Indication for 8Tx Transmission |
Google |
| R1-2300442 |
Further discussion on enabling 8 TX UL transmission |
vivo |
| R1-2300496 |
Discussion on SRI/TPMI Enhancements for 8 TX UL Transmission |
FGI |
| R1-2300516 |
SRI/TPMI enhancement for enabling 8TX UL transmission |
Lenovo |
| R1-2300528 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
LG Electronics |
| R1-2300551 |
Enhancements on 8Tx uplink transmission |
xiaomi |
| R1-2300656 |
On SRI/TPMI enhancement for 8TX UL transmission |
CATT |
| R1-2300815 |
Discussion on SRI/TPMI enhancement |
NEC |
| R1-2300851 |
Views on 8 TX UL transmission |
Sharp |
| R1-2300867 |
Considerations on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Sony |
| R1-2300938 |
Discussion on enhancement for 8Tx UL transmission |
Intel Corporation |
| R1-2300988 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
CMCC |
| R1-2301135 |
Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission |
KDDI Corporation |
| R1-2301184 |
SRI/TPMI Enhancement for Enabling 8 TX UL Transmission |
Ericsson |
| R1-2301253 |
Views on TPMI/SRI enhancements for 8Tx UL transmission |
Samsung |
| R1-2301335 |
Views on SRI/TPMI enhancement for enabling 8 TX UL transmission |
Apple |
| R1-2301401 |
Enhancements for 8 Tx UL transmissions |
Qualcomm Incorporated |
| R1-2301483 |
Discussion on 8 TX UL transmission |
NTT DOCOMO, INC. |
| R1-2301575 |
SRI/TPMI enhancement for enabling 8 Tx UL transmission |
MediaTek Inc. |
| R1-2301648 |
UL enhancements for enabling 8Tx UL transmission |
Nokia, Nokia Shanghai Bell |
| R1-2301687 |
SRI/TPMI enhancement for enabling 8 TX UL transmission |
CEWiT |
| R1-2301945 |
SRI/TPMI Enhancement for Enabling 8 TX UL Transmission |
Ericsson |
| R1-2302007 |
FL Summary SRI/TPMI Enhancements Third Round |
Moderator (InterDigital, Inc.) |
| 9.2 |
Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface |
|
| R1-2301402 |
Technical report for Rel-18 SI on AI and ML for NR air interface |
Qualcomm Incorporated |
| R1-2302063 |
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-2300043 |
Discussion on common AI/ML characteristics and operations |
FUTUREWEI |
| R1-2300107 |
Discussion on general aspects of AI/ML framework |
Huawei, HiSilicon |
| R1-2300170 |
Discussion on general aspects of common AI PHY framework |
ZTE |
| R1-2300178 |
Discussion on general aspects of AIML framework |
Ericsson |
| R1-2300210 |
Discussion on general aspects of AI/ML framework |
Spreadtrum Communications |
| R1-2300279 |
On general aspects of AI/ML framework |
OPPO |
| R1-2300396 |
On General Aspects of AI/ML Framework |
Google |
| R1-2300443 |
Discussions on AI/ML framework |
vivo |
| R1-2300529 |
General aspects on AI/ML framework |
LG Electronics |
| R1-2300566 |
Views on the general aspects of AI/ML framework |
xiaomi |
| R1-2300603 |
Further discussion on the general aspects of ML for Air-interface |
Nokia, Nokia Shanghai Bell |
| R1-2300670 |
Discussion on general aspects of AI/ML framework |
CATT |
| R1-2300743 |
Discussion on general aspects of AI/ML framework |
Fujitsu |
| R1-2300823 |
Discussion on general aspects of AI ML framework |
NEC |
| R1-2300840 |
Considerations on general aspects on AI-ML framework |
CAICT |
| R1-2300868 |
Considerations on common AI/ML framework |
Sony |
| R1-2300906 |
Discussion on general aspects of AI/ML framework |
KDDI Corporation |
| R1-2300940 |
Discussion on general aspects of AI/ML framework |
Intel Corporation |
| R1-2300989 |
Discussion on general aspects of AI/ML framework |
CMCC |
| R1-2301040 |
Discussion on general aspects of AI/ML framework for NR air interface |
ETRI |
| R1-2301139 |
General aspects of AI/ML framework |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301147 |
Discussion on general aspects of AI/ML framework |
Panasonic |
| R1-2301155 |
Discussion on general aspects of AI/ML framework |
InterDigital, Inc. |
| R1-2301160 |
Discussion on AI/ML Framework |
Rakuten Mobile, Inc |
| R1-2301177 |
General aspects of AI and ML framework for NR air interface |
NVIDIA |
| R1-2301198 |
General aspects of AI/ML framework |
Lenovo |
| R1-2301220 |
General aspects of AI/ML Framework |
AT&T |
| R1-2301254 |
General aspects of AI ML framework and evaluation methodology |
Samsung |
| R1-2301336 |
Discussion on general aspect of AI/ML framework |
Apple |
| R1-2301403 |
General aspects of AI/ML framework |
Qualcomm Incorporated |
| R1-2301484 |
Discussion on general aspects of AI/ML framework |
NTT DOCOMO, INC. |
| R1-2301586 |
Discussion on general aspects of AI/ML LCM |
MediaTek Inc. |
| R1-2301663 |
Discussions on Common Aspects of AI/ML Framework |
TCL Communication Ltd. |
| R1-2301664 |
Identifying Procedures for General Aspects of AI/ML Frameworks |
Indian Institute of Tech (M), CEWiT, IIT Kanpur |
| R1-2301863 |
Summary#1 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2301864 |
Summary#2 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2301865 |
Summary#3 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2301866 |
Summary#4 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2301867 |
Summary#5 of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| R1-2301868 |
Final Summary of General Aspects of AI/ML Framework |
Moderator (Qualcomm) |
| 9.2.2.1 |
Evaluation on AI/ML for CSI feedback enhancement |
|
| R1-2300044 |
Discussion and evaluation of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2300108 |
Evaluation on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2300154 |
Evaluations of AI-CSI |
Ericsson |
| R1-2300171 |
Evaluation on AI CSI feedback enhancement |
ZTE |
| R1-2300211 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
Spreadtrum Communications, BUPT |
| R1-2300280 |
Evaluation methodology and results on AI/ML for CSI feedback enhancement |
OPPO |
| R1-2300348 |
Evaluation on AI ML for CSI feedback enhancement |
Mavenir |
| R1-2300397 |
On Evaluation of AI/ML based CSI |
Google |
| R1-2300444 |
Evaluation on AI/ML for CSI feedback enhancement |
vivo |
| R1-2300501 |
Evaluation of AI/ML based methods for CSI feedback enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2300530 |
Evaluation on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2300567 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
xiaomi |
| R1-2300604 |
Evaluation of ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2300671 |
Evaluation on AI/ML for CSI feedback enhancement |
CATT |
| R1-2300716 |
Evaluation on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2300744 |
Evaluation on AI/ML for CSI feedback enhancement |
Fujitsu |
| R1-2300841 |
Some discussions on evaluation on AI-ML for CSI feedback |
CAICT |
| R1-2300941 |
Evaluation for CSI feedback enhancements |
Intel Corporation |
| R1-2300990 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2301031 |
Evaluation on AI/ML for CSI feedback enhancement |
Indian Institute of Tech (H) |
| R1-2301041 |
Evaluation on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2301097 |
Evaluation of joint CSI estimation and compression with AI/ML |
BJTU |
| R1-2301146 |
Evaluation on AI/ML for CSI Feedback Enhancement |
IIT Kanpur |
| R1-2301156 |
Evaluation on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2301178 |
Evaluation of AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2301199 |
Evaluation on AI/ML for CSI feedback |
Lenovo |
| R1-2301223 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2301255 |
Evaluation on AI/ML for CSI feedback enhancement |
Samsung |
| R1-2301337 |
Evaluation for AI/ML based CSI feedback enhancement |
Apple |
| R1-2301404 |
Evaluation on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2301466 |
Evaluation of AI/ML based methods for CSI feedback enhancement |
SEU |
| R1-2301485 |
Discussion on evaluation on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2301587 |
Evaluation on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2301666 |
Discussion on AI/ML based CSI Feedback Enhancement |
Indian Institute of Tech (M), CEWiT, IIT Kanpur |
| R1-2301688 |
Evaluation of AI and ML for CSI feedback enhancement |
CEWiT |
| R1-2301805 |
Evaluation of AI and ML for CSI feedback enhancement |
CEWiT |
| R1-2301936 |
Summary#1 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| R1-2301937 |
Summary#2 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| R1-2301938 |
Summary#3 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| R1-2301939 |
Summary#4 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| R1-2301940 |
Summary#5 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| R1-2301941 |
Summary#6 for CSI evaluation of [112-R18-AI/ML] |
Moderator (Huawei) |
| 9.2.2.2 |
Other aspects on AI/ML for CSI feedback enhancement |
|
| R1-2300045 |
Discussion on other aspects of AI/ML for CSI feedback enhancement |
FUTUREWEI |
| R1-2300071 |
Further discussions of AI/ML for CSI feedback enhancement |
Keysight Technologies UK Ltd, Universidad de Málaga |
| R1-2300109 |
Discussion on AI/ML for CSI feedback enhancement |
Huawei, HiSilicon |
| R1-2300153 |
Discussion on AI-CSI |
Ericsson |
| R1-2300172 |
Discussion on other aspects for AI CSI feedback enhancement |
ZTE |
| R1-2300212 |
Discussion on other aspects on AI/ML for CSI feedback |
Spreadtrum Communications |
| R1-2300281 |
On sub use cases and other aspects of AI/ML for CSI feedback enhancement |
OPPO |
| R1-2300398 |
On Enhancement of AI/ML based CSI |
Google |
| R1-2300445 |
Other aspects on AI/ML for CSI feedback enhancement |
vivo |
| R1-2300531 |
Other aspects on AI/ML for CSI feedback enhancement |
LG Electronics |
| R1-2300568 |
Discussion on potential specification impact for CSI feedback based on AI/ML |
xiaomi |
| R1-2300605 |
Other aspects on ML for CSI feedback enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2300672 |
Potential specification impact on AI/ML for CSI feedback enhancement |
CATT |
| R1-2300717 |
Discussion on AI/ML for CSI feedback enhancement |
China Telecom |
| R1-2300745 |
Views on specification impact for CSI feedback enhancement |
Fujitsu |
| R1-2300767 |
Discussion on AI/ML for CSI feedback enhancement |
NEC |
| R1-2300842 |
Discussions on AI-ML for CSI feedback |
CAICT |
| R1-2300863 |
Discussion on AI/ML for CSI feedback enhancement |
Panasonic |
| R1-2300869 |
Considerations on CSI measurement enhancements via AI/ML |
Sony |
| R1-2300942 |
On other aspects on AI/ML for CSI feedback |
Intel Corporation |
| R1-2300991 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
CMCC |
| R1-2301042 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
ETRI |
| R1-2301098 |
Joint CSI estimation and compression with AI/ML |
BJTU |
| R1-2301157 |
Discussion on AI/ML for CSI feedback enhancement |
InterDigital, Inc. |
| R1-2301179 |
AI and ML for CSI feedback enhancement |
NVIDIA |
| R1-2301200 |
Further aspects of AI/ML for CSI feedback |
Lenovo |
| R1-2301224 |
Discussion on AI/ML for CSI feedback enhancement |
AT&T |
| R1-2301256 |
Representative sub use cases for CSI feedback enhancement |
Samsung |
| R1-2301313 |
Discussion on AI/ML for CSI Feedback Enhancement |
III |
| R1-2301338 |
Discussion on other aspects of AI/ML for CSI enhancement |
Apple |
| R1-2301405 |
Other aspects on AI/ML for CSI feedback enhancement |
Qualcomm Incorporated |
| R1-2301486 |
Discussion on other aspects on AI/ML for CSI feedback enhancement |
NTT DOCOMO, INC. |
| R1-2301588 |
Other aspects on AI/ML for CSI feedback enhancement |
MediaTek Inc. |
| R1-2301665 |
Discussions on Sub-Use Cases in AI/ML for CSI Feedback Enhancement |
TCL Communication Ltd. |
| R1-2301910 |
Summary #1 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2301911 |
Summary #2 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2301912 |
Summary #3 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| R1-2301913 |
Summary #4 on other aspects of AI/ML for CSI enhancement |
Moderator (Apple) |
| 9.2.3.1 |
Evaluation on AI/ML for beam management |
|
| R1-2300046 |
Discussion and evaluation of AI/ML for beam management |
FUTUREWEI |
| R1-2300110 |
Evaluation on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2300173 |
Evaluation on AI beam management |
ZTE |
| R1-2300179 |
Evaluations of AIML for beam management |
Ericsson |
| R1-2300213 |
Evaluation on AI/ML for beam management |
Spreadtrum Communications |
| R1-2300282 |
Evaluation methodology and results on AI/ML for beam management |
OPPO |
| R1-2300399 |
On Evaluation of AI/ML based Beam Management |
Google |
| R1-2300446 |
Evaluation on AI/ML for beam management |
vivo |
| R1-2300532 |
Evaluation on AI/ML for beam management |
LG Electronics |
| R1-2300569 |
Evaluation on AI/ML for beam management |
xiaomi |
| R1-2300593 |
Discussion for evaluation on AI/ML for beam management |
InterDigital, Inc. |
| R1-2300606 |
Evaluation of ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2300673 |
Evaluation on AI/ML for beam management |
CATT |
| R1-2300718 |
Evaluation on AI/ML for beam management |
China Telecom |
| R1-2300746 |
Evaluation on AI/ML for beam management |
Fujitsu |
| R1-2300843 |
Some discussions on evaluation on AI-ML for Beam management |
CAICT |
| R1-2300943 |
Evaluations for AI/ML beam management |
Intel Corporation |
| R1-2300992 |
Discussion on evaluation on AI/ML for beam management |
CMCC |
| R1-2301180 |
Evaluation of AI and ML for beam management |
NVIDIA |
| R1-2301201 |
Evaluation on AI/ML for beam management |
Lenovo |
| R1-2301257 |
Evaluation on AI/ML for Beam management |
Samsung |
| R1-2301339 |
Evaluation for AI/ML based beam management enhancements |
Apple |
| R1-2301406 |
Evaluation on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2301487 |
Discussion on evaluation on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2301589 |
Evaluation on AI/ML for beam management |
MediaTek Inc. |
| R1-2301689 |
Evaluation on AI/ML for beam management |
CEWiT |
| R1-2301956 |
Feature lead summary #1 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2301957 |
Feature lead summary #2 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2301958 |
Feature lead summary #3 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| R1-2301959 |
Feature lead summary #4 evaluation of AI/ML for beam management |
Moderator (Samsung) |
| 9.2.3.2 |
Other aspects on AI/ML for beam management |
|
| R1-2300047 |
Discussion on other aspects of AI/ML for beam management |
FUTUREWEI |
| R1-2300111 |
Discussion on AI/ML for beam management |
Huawei, HiSilicon |
| R1-2300174 |
Discussion on other aspects for AI beam management |
ZTE |
| R1-2300180 |
Discussion on AIML for beam management |
Ericsson |
| R1-2300195 |
Discussion on other aspects of AI/ML beam management |
New H3C Technologies Co., Ltd. |
| R1-2300214 |
Other aspects on AI/ML for beam management |
Spreadtrum Communications |
| R1-2300283 |
Other aspects of AI/ML for beam management |
OPPO |
| R1-2300400 |
On Enhancement of AI/ML based Beam Management |
Google |
| R1-2300447 |
Other aspects on AI/ML for beam management |
vivo |
| R1-2300533 |
Other aspects on AI/ML for beam management |
LG Electronics |
| R1-2300570 |
Potential specification impact on AI/ML for beam management |
xiaomi |
| R1-2300594 |
Discussion for other aspects on AI/ML for beam management |
InterDigital, Inc. |
| R1-2300607 |
Other aspects on ML for beam management |
Nokia, Nokia Shanghai Bell |
| R1-2300674 |
Potential specification impact on AI/ML for beam management |
CATT |
| R1-2300747 |
Sub use cases and specification impact on AI/ML for beam management |
Fujitsu |
| R1-2300824 |
Discussion on AI/ML for beam management |
NEC |
| R1-2300844 |
Discussions on AI-ML for Beam management |
CAICT |
| R1-2300870 |
Consideration on AI/ML for beam management |
Sony |
| R1-2300944 |
Other aspects on AI/ML for beam management |
Intel Corporation |
| R1-2300993 |
Discussion on other aspects on AI/ML for beam management |
CMCC |
| R1-2301043 |
Discussion on other aspects on AI/ML for beam management |
ETRI |
| R1-2301181 |
AI and ML for beam management |
NVIDIA |
| R1-2301197 |
Discussion on AI/ML for beam management |
Panasonic |
| R1-2301202 |
Further aspects of AI/ML for beam management |
Lenovo |
| R1-2301258 |
Representative sub use cases for beam management |
Samsung |
| R1-2301340 |
Discussion on other aspects of AI/ML for beam management |
Apple |
| R1-2301407 |
Other aspects on AI/ML for beam management |
Qualcomm Incorporated |
| R1-2301488 |
Discussion on other aspects on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2301539 |
Discussion on other aspects on AI/ML for beam management |
KT Corp. |
| R1-2301590 |
Other aspects on AI/ML for beam management |
MediaTek Inc. |
| R1-2301685 |
Discussions on Sub-Use Cases in AI/ML for Beam Management |
TCL Communication Ltd. |
| R1-2301894 |
Summary#1 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2301895 |
Summary#2 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2301896 |
Summary#3 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| R1-2301897 |
Summary#4 for other aspects on AI/ML for beam management |
Moderator (OPPO) |
| 9.2.4.1 |
Evaluation on AI/ML for positioning accuracy enhancement |
|
| R1-2300112 |
Evaluation on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2300141 |
Evaluation of AI/ML for Positioning Accuracy Enhancement |
Ericsson Inc. |
| R1-2300175 |
Evaluation on AI positioning enhancement |
ZTE |
| R1-2300284 |
Evaluation methodology and results on AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2300401 |
On Evaluation of AI/ML based Positioning |
Google |
| R1-2300448 |
Evaluation on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2300534 |
Evaluation on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2300571 |
Evaluation on AI/ML for positioning accuracy enhancement |
xiaomi |
| R1-2300608 |
Evaluation of ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2300675 |
Evaluation on AI/ML for positioning enhancement |
CATT |
| R1-2300719 |
Evaluation on AI/ML for positioning accuracy enhancement |
China Telecom |
| R1-2300748 |
Discussions on evaluation results of AIML positioning accuracy enhancement |
Fujitsu |
| R1-2300845 |
Some discussions on evaluation on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2300994 |
Discussion on evaluation on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2301101 |
Evaluation on AI/ML for positioning accuracy enhancement |
InterDigital, Inc. |
| R1-2301182 |
Evaluation of AI and ML for positioning enhancement |
NVIDIA |
| R1-2301203 |
Discussion on AI/ML Positioning Evaluations |
Lenovo |
| R1-2301259 |
Evaluation on AI/ML for Positioning |
Samsung |
| R1-2301341 |
Evaluation on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2301408 |
Evaluation on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2301591 |
Evaluation of AIML for Positioning Accuracy Enhancement |
MediaTek Inc. |
| R1-2301690 |
Evaluation on AI/ML for Positioning Accuracy Enhancement |
CEWiT |
| R1-2301806 |
Evaluation on AI/ML for Positioning Accuracy Enhancement |
CEWiT |
| R1-2301946 |
Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2301947 |
Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2301948 |
Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2301949 |
Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2302169 |
Summary #5 of Evaluation on AI/ML for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2302170 |
Summary #6 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-2300113 |
Discussion on AI/ML for positioning accuracy enhancement |
Huawei, HiSilicon |
| R1-2300142 |
Other Aspects of AI/ML Based Positioning Enhancement |
Ericsson Inc. |
| R1-2300176 |
Discussion on other aspects for AI positioning enhancement |
ZTE |
| R1-2300215 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
Spreadtrum Communications |
| R1-2300285 |
On sub use cases and other aspects of AI/ML for positioning accuracy enhancement |
OPPO |
| R1-2300402 |
On Enhancement of AI/ML based Positioning |
Google |
| R1-2300449 |
Other aspects on AI/ML for positioning accuracy enhancement |
vivo |
| R1-2300535 |
Other aspects on AI/ML for positioning accuracy enhancement |
LG Electronics |
| R1-2300572 |
Views on the other aspects of AI/ML-based positioning accuracy enhancement |
xiaomi |
| R1-2300602 |
Other aspects on AI-ML for positioning accuracy enhancement |
Baicells |
| R1-2300609 |
Other aspects on ML for positioning accuracy enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2300676 |
Potential specification impact on AI/ML for positioning enhancement |
CATT |
| R1-2300749 |
Discussions on specification impacts for AIML positioning accuracy enhancement |
Fujitsu |
| R1-2300831 |
Discussion on AI/ML for positioning accuracy enhancement |
NEC |
| R1-2300846 |
Discussions on AI-ML for positioning accuracy enhancement |
CAICT |
| R1-2300871 |
On Other Aspects on AI/ML for Positioning Accuracy Enhancement |
Sony |
| R1-2300995 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
CMCC |
| R1-2301115 |
Designs and potential specification impacts of AIML for positioning |
InterDigital, Inc. |
| R1-2301140 |
On potential AI/ML solutions for positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301183 |
AI and ML for positioning enhancement |
NVIDIA |
| R1-2301204 |
AI/ML Positioning use cases and associated Impacts |
Lenovo |
| R1-2301260 |
Representative sub use cases for Positioning |
Samsung |
| R1-2301342 |
On Other aspects on AI/ML for positioning accuracy enhancement |
Apple |
| R1-2301409 |
Other aspects on AI/ML for positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2301489 |
Discussion on other aspects on AI/ML for positioning accuracy enhancement |
NTT DOCOMO, INC. |
| R1-2301592 |
Other Aspects on AI ML Based Positioning Enhancement |
MediaTek Inc. |
| R1-2301667 |
Contributions on AI/ML based Positioning Accuracy Enhancement |
Indian Institute of Tech (M), CEWiT, IIT Kanpur |
| R1-2301847 |
FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2301996 |
FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| R1-2302019 |
FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement |
Moderator (vivo) |
| 9.3 |
Study on evolution of NR duplex operation |
|
| R1-2300996 |
Updated TR 38.858 skeleton for study on evolution of NR duplex operation |
CMCC, Samsung, CATT |
| R1-2300997 |
TR 38.858 v0.2.0 for study on evolution of NR duplex operation |
CMCC, Samsung, CATT |
| R1-2300998 |
Summary on SLS calibration results for NR duplex evolution |
CMCC |
| R1-2301813 |
Summary on SLS calibration results for NR duplex evolution |
CMCC |
| R1-2302086 |
Draft LS on interference modelling for duplex evolution |
Moderator (CMCC) |
| R1-2302087 |
LS on interference modelling for duplex evolution |
RAN1, CMCC |
| 9.3.1 |
Evaluation on NR duplex evolution |
|
| R1-2300086 |
Discussion on evaluation and methodologies on evolution of NR duplex operation |
Huawei, HiSilicon |
| R1-2300151 |
Discussion for Evaluation on NR duplex evolution |
New H3C Technologies Co., Ltd. |
| R1-2300216 |
Discussion on evaluation on NR duplex evolution |
Spreadtrum Communications, BUPT |
| R1-2300286 |
Discussion on evaluation on NR duplex evolution |
OPPO |
| R1-2300329 |
Evaluation methodology for NR duplex evolution |
Kumu Networks |
| R1-2300330 |
Discussion on evaluation for NR duplex evolution |
InterDigital, Inc. |
| R1-2300339 |
Discussion of evaluation on NR duplex evolution |
ZTE |
| R1-2300450 |
Evaluation on NR duplex evolution |
vivo |
| R1-2300573 |
Discussion on evaluation on NR duplex evolution |
xiaomi |
| R1-2300677 |
Discussion on evaluation on NR duplex evolution |
CATT |
| R1-2300872 |
Coupling Loss for SBFD System Level Simulation Calibration |
Sony |
| R1-2300907 |
Evaluation of NR duplex evolution |
Ericsson |
| R1-2300945 |
Evaluations on NR Duplex evolution |
Intel Corporation |
| R1-2300999 |
Remaining issues on evaluation on NR duplex evolution |
CMCC |
| R1-2301063 |
Study on Evaluation for NR duplex evolution |
LG Electronics |
| R1-2301261 |
Discussion on evaluation for NR duplex evolution |
Samsung |
| R1-2301299 |
Coupling loss results for duplex evolution |
Sharp |
| R1-2301343 |
On evaluations for NR duplex evolution |
Apple |
| R1-2301410 |
On Deployment scenarios and evaluation Methodology for NR duplex evolution |
Qualcomm Incorporated |
| R1-2301490 |
Discussion on evaluation on NR duplex evolution |
NTT DOCOMO, INC. |
| R1-2301569 |
On the evaluation methodology for NR duplexing enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2301593 |
Deployment scenarios and evaluation methodology for NR duplex evolution |
MediaTek Inc. |
| R1-2301691 |
Calibration analysis for SBFD |
CEWiT, Reliance Jio |
| R1-2301798 |
Discussion on evaluation on NR duplex evolution |
xiaomi |
| R1-2301822 |
Summary#1 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2301823 |
Summary#2 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2301824 |
Summary#3 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2301825 |
Summary#4 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2302119 |
Summary#5 on evaluation on NR duplex evolution |
Moderator (CMCC) |
| R1-2302138 |
Discussion on evaluation for NR duplex evolution |
InterDigital, Inc. |
| 9.3.2 |
Subband non-overlapping full duplex |
|
| R1-2300087 |
Discussion on potential enhancement on subband non-overlapping full duplex |
Huawei, HiSilicon |
| R1-2300150 |
Discussion for subband non-overlapping full duplex |
New H3C Technologies Co., Ltd. |
| R1-2300167 |
Discussion on subband non-overlapping full duplex |
TCL Communication Ltd. |
| R1-2300217 |
Discussion on subband non-overlapping full duplex |
Spreadtrum Communications |
| R1-2300287 |
Discussion on subband non-overlapping full duplex |
OPPO |
| R1-2300331 |
Discussion on subband non-overlapping full duplex operation |
InterDigital, Inc. |
| R1-2300340 |
Discussion of subband non-overlapping full duplex |
ZTE |
| R1-2300451 |
Discussion on subband non-overlapping full duplex |
vivo |
| R1-2300574 |
Discussion on subband non-overlapping full duplex |
xiaomi |
| R1-2300678 |
Discussion on subband non-overlapping full duplex |
CATT |
| R1-2300750 |
Discussion on subband non-overlapping full duplex |
Fujitsu |
| R1-2300763 |
Discussion on subband non-overlapping full duplex |
NEC |
| R1-2300873 |
Considerations on Subband Full Duplex TDD operations |
Sony |
| R1-2300908 |
Subband non-overlapping full duplex |
Ericsson |
| R1-2300918 |
Discussion on subband non-overlapping full duplex |
Panasonic |
| R1-2300946 |
On SBFD in NR systems |
Intel Corporation |
| R1-2301000 |
Discussion on subband non-overlapping full duplex |
CMCC |
| R1-2301044 |
Discussion on subband non-overlapping full duplex enhancements |
ETRI |
| R1-2301064 |
Study on Subband non-overlapping full duplex |
LG Electronics |
| R1-2301205 |
Subband non-overlapping full duplex |
Lenovo |
| R1-2301262 |
SBFD feasibility and design considerations for NR duplex evolution |
Samsung |
| R1-2301301 |
Discussion on subband non-overlapping full duplex |
Sharp |
| R1-2301344 |
Views on subband non-overlapping full duplex |
Apple |
| R1-2301411 |
Feasibility and techniques for Subband non-overlapping full duplex |
Qualcomm Incorporated |
| R1-2301491 |
Discussion on subband non-overlapping full duplex |
NTT DOCOMO, INC. |
| R1-2301570 |
On subband non-overlapping full duplex for NR |
Nokia, Nokia Shanghai Bell |
| R1-2301594 |
Discussion on subband non-overlapping full duplex for NR |
MediaTek Inc. |
| R1-2301639 |
Discussion on subband non-overlapping full duplex |
KDDI Corporation |
| R1-2301650 |
Details of subband non-overlapping full duplex |
ASUSTeK |
| R1-2301692 |
Discussion on subband non-overlapping full duplex |
CEWiT, Reliance Jio |
| R1-2301732 |
Discussion on subband non-overlapping full duplex |
WILUS Inc. |
| R1-2301745 |
Discussion on subband non-overlapping full duplex |
Indian Institute of Tech (M) |
| R1-2301933 |
Summary #1 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2301934 |
Summary #2 of subband non-overlapping full duplex |
Moderator (CATT) |
| R1-2301935 |
Summary #3 of subband non-overlapping full duplex |
Moderator (CATT) |
| 9.3.3 |
Potential enhancements on dynamic/flexible TDD |
|
| R1-2300088 |
Study on potential enhancements on dynamic/flexible TDD |
Huawei, HiSilicon |
| R1-2300149 |
Discussion on potential enhancements on dynamic/flexible TDD |
New H3C Technologies Co., Ltd. |
| R1-2300168 |
Potential enhancement on dynamic/flexible TDD |
TCL Communication Ltd. |
| R1-2300218 |
Discussion on potential enhancements on dynamic/flexible TDD |
Spreadtrum Communications |
| R1-2300288 |
Discussion on potential enhancements on dynamic/flexible TDD |
OPPO |
| R1-2300332 |
Potential enhancements on dynamic/flexible TDD operation |
InterDigital, Inc. |
| R1-2300341 |
Discussion of enhancements on dynamic/flexible TDD |
ZTE, China Telecom |
| R1-2300452 |
Potential enhancements on dynamic/flexible TDD |
vivo |
| R1-2300575 |
Discussion on potential enhancements on dynamic/flexible TDD |
xiaomi |
| R1-2300679 |
Discussion on potential enhancements on dynamic/flexible TDD |
CATT |
| R1-2300762 |
Views on enhancements of dynamic/flexible TDD |
NEC |
| R1-2300853 |
Discussion on potential enhancements on dynamic/flexible TDD |
Panasonic |
| R1-2300857 |
Potential enhancements on dynamic/flexible TDD |
Lenovo |
| R1-2300874 |
Considerations on Flexible/Dynamic TDD |
Sony |
| R1-2300909 |
Potential enhancements of dynamic TDD |
Ericsson |
| R1-2300947 |
On enhancements for dynamic/flexible TDD |
Intel Corporation |
| R1-2301001 |
Discussion on potential enhancements on flexible/dynamic TDD |
CMCC |
| R1-2301065 |
Study on Potential enhancements on dynamic/flexible TDD |
LG Electronics |
| R1-2301263 |
Dynamic and flexible TDD for NR duplex evolution |
Samsung |
| R1-2301345 |
Views on potential enhancements on dynamic TDD |
Apple |
| R1-2301412 |
On potential enhancements on dynamic/flexible TDD |
Qualcomm Incorporated |
| R1-2301492 |
Discussion on potential enhancements on dynamic/flexible TDD |
NTT DOCOMO, INC. |
| R1-2301571 |
Dynamic TDD enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2301595 |
Discussion on potential enhancements on dynamic/flexible TDD |
MediaTek Inc. |
| R1-2301693 |
Discussion on enhancements on dynamic/flexible TDD |
CEWiT, Reliance Jio |
| R1-2301733 |
Discussion on potential enhancements on dynamic/flexible TDD |
WILUS Inc. |
| R1-2301976 |
Summary #1 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2301977 |
Summary #2 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2301978 |
Summary #3 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| R1-2301979 |
Summary #4 of potential enhancement on dynamic/flexible TDD |
Moderator (LG Electronics) |
| 9.4 |
NR sidelink evolution |
|
| R1-2302064 |
Session notes for 9.4 (NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| 9.4.1.1 |
Channel access mechanism |
|
| R1-2300036 |
On Channel Access Mechanism for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2300060 |
Channel access mechanism for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2300124 |
Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2300219 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2300297 |
On channel access mechanism and resource allocation for SL-U |
OPPO |
| R1-2300313 |
Discussion on Channel Access Mechanisms |
Johns Hopkins University APL |
| R1-2300354 |
Discussion on channel access mechanism for SL-U |
ZTE, Sanechips |
| R1-2300386 |
Sidelink channel access mechanisms |
National Spectrum Consortium |
| R1-2300453 |
Channel access mechanism for sidelink on unlicensed spectrum |
vivo |
| R1-2300576 |
Discussion on channel access mechanism for sidelink-unlicensed |
xiaomi |
| R1-2300680 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2300732 |
Channel access mechanism for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2300751 |
Discussion on channel access mechanism for SL-U |
Fujitsu |
| R1-2300771 |
Clarifications on SL-U channel access mechanism |
CableLabs |
| R1-2300816 |
Channel Access of Sidelink on Unlicensed Spectrum |
NEC |
| R1-2300875 |
Discussion on channel access mechanism for SL-unlicensed |
Sony |
| R1-2300948 |
On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2301002 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
CMCC |
| R1-2301037 |
Considerations on channel access mechanism of SL-U |
CAICT |
| R1-2301045 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
ETRI |
| R1-2301130 |
Channel access mechanism for SL-U |
Ericsson |
| R1-2301173 |
Sidelink channel access on unlicensed spectrum |
InterDigital, Inc. |
| R1-2301189 |
NR Sidelink Unlicensed Channel Access Mechanisms |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2301264 |
On channel access mehanism for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2301297 |
Sidelink channel access on unlicensed spectrum |
Panasonic |
| R1-2301306 |
Discussion of channel access mechanism for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2301346 |
Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum |
Apple |
| R1-2301413 |
Channel Access Mechanism for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2301493 |
Discussion on channel access mechanism in SL-U |
NTT DOCOMO, INC. |
| R1-2301532 |
Discussion on channel access mechanism for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2301543 |
Discussion on channel access mechanism for NR sidelink evolution |
Sharp |
| R1-2301584 |
Discussion on channel access mechanism |
MediaTek Inc. |
| R1-2301627 |
Channel Access Mechanism for SL-U |
ITL |
| R1-2301734 |
Discussion on channel access mechanism for SL-U |
WILUS Inc. |
| R1-2301790 |
FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301791 |
FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301792 |
FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301793 |
FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301794 |
FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301795 |
FL summary #6 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301796 |
FL summary #7 for AI 9.4.1.1: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2301797 |
FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2301980 |
Moderator summary of discussion for LS reply on SL LBT failure indication and consistent SL LBT failure |
Moderator (vivo) |
| R1-2301981 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
Moderator (vivo) |
| R1-2302117 |
Draft reply LS on SL LBT failure indication and consistent SL LBT failure |
Moderator (vivo) |
| R1-2302118 |
Reply LS on SL LBT failure indication and consistent SL LBT failure |
RAN1, vivo |
| 9.4.1.2 |
Physical channel design framework |
|
| R1-2300037 |
On Physical Channel Design Framework for SL-U |
Nokia, Nokia Shanghai Bell |
| R1-2300061 |
Physical channel design for sidelink on unlicensed spectrum |
FUTUREWEI |
| R1-2300125 |
Physical channel design for sidelink operation over unlicensed spectrum |
Huawei, HiSilicon |
| R1-2300220 |
Discussion on Physical channel design for sidelink on unlicensed spectrum |
Spreadtrum Communications |
| R1-2300298 |
On PHY channel designs and procedures for SL-U |
OPPO |
| R1-2300355 |
Discussion on physical layer structures and procedures for SL-U |
ZTE, Sanechips |
| R1-2300387 |
Sidelink Physical Channel Design Considerations |
National Spectrum Consortium |
| R1-2300454 |
Physical channel design framework for sidelink on unlicensed spectrum |
vivo |
| R1-2300577 |
Discussion on physical channel design for sidelink-unlicensed |
xiaomi |
| R1-2300681 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CATT, GOHIGH |
| R1-2300733 |
Physical layer design framework for sidelink on FR1 unlicensed spectrum |
Lenovo |
| R1-2300826 |
Discussion on physical channel design framework |
NEC |
| R1-2300876 |
Discussion on physical channel design framework for SL-unlicensed |
Sony |
| R1-2300901 |
Discussion on Physical channel design framework for sidelink on unlicensed spectrum |
Hyundai Motor Company |
| R1-2300949 |
On the Physical Layer Enhancements for SL Operating in Unlicensed Spectrum |
Intel Corporation |
| R1-2301003 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
CMCC |
| R1-2301131 |
PHY channel design framework for SL-U |
Ericsson |
| R1-2301174 |
SL U physical layer design framework |
InterDigital, Inc. |
| R1-2301190 |
NR Sidelink Unlicensed Physical Channel Design |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2301265 |
On physical channel design framework for sidelink on FR1 unlicensed spectrum |
Samsung |
| R1-2301298 |
Physical channel design for sidelink on unlicensed spectrum |
Panasonic |
| R1-2301307 |
Discussion of physical channel design for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2301347 |
Discussion on Sidelink Physical Channel Design Framework for Unlicensed Spectrum |
Apple |
| R1-2301414 |
Physical Channel Design for Sidelink on Unlicensed Spectrum |
Qualcomm Incorporated |
| R1-2301459 |
Discussion on channel structure for SL-U |
ASUSTeK |
| R1-2301494 |
Discussion on channel design framework in SL-U |
NTT DOCOMO, INC. |
| R1-2301533 |
Discussion on physical channel design framework for sidelink on unlicensed spectrum |
LG Electronics |
| R1-2301544 |
Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum |
Sharp |
| R1-2301585 |
Discussion on physical channel design framework |
MediaTek Inc. |
| R1-2301628 |
Physical Channel Design framework for SL-U |
ITL |
| R1-2301735 |
Discussion on PHY channel design framework for SL-U |
WILUS Inc. |
| R1-2301839 |
PHY channel design framework for SL-U |
Ericsson |
| R1-2301928 |
FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2301929 |
FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2301930 |
FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2301931 |
FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2301932 |
FL summary#5 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-2300038 |
On Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Nokia, Nokia Shanghai Bell |
| R1-2300062 |
Dynamic coexistence between NR and LTE sidelink |
FUTUREWEI |
| R1-2300126 |
Co-channel coexistence for LTE sidelink and NR sidelink |
Huawei, HiSilicon |
| R1-2300221 |
Discussion on Co-channel coexistence for LTE sidelink and NR sidelink |
Spreadtrum Communications |
| R1-2300299 |
Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL |
OPPO |
| R1-2300356 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ZTE, Sanechips |
| R1-2300380 |
Dynamic co-channel coexistence for LTE sidelink and NR sidelink |
TOYOTA Info Technology Center |
| R1-2300455 |
Co-channel coexistence for LTE sidelink and NR sidelink |
vivo |
| R1-2300578 |
Discussion on co-channel coexistence for LTE and NR sidelink |
xiaomi |
| R1-2300682 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CATT, GOHIGH |
| R1-2300734 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Lenovo |
| R1-2300817 |
Co-existence between LTE and NR sidelink |
NEC |
| R1-2300877 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sony |
| R1-2300897 |
Discussion on Sidelink Co-channel Coexistence |
Panasonic |
| R1-2300950 |
On the Co-channel Coexistence between LTE and NR Sidelink |
Intel Corporation |
| R1-2301004 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
CMCC |
| R1-2301046 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ETRI |
| R1-2301129 |
Co-channel coexistence between LTE sidelink and NR sidelink |
Ericsson |
| R1-2301150 |
On sidelink co-channel coexistence issues |
Mitsubishi Electric RCE |
| R1-2301175 |
Co-channel coexistence for LTE sidelink and NR sidelink |
InterDigital, Inc. |
| R1-2301191 |
Discussion on Co-Channel Coexistence for LTE and NR Sidelink |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2301266 |
On co-channel coexistence for LTE sidelink and NR sidelink |
Samsung |
| R1-2301304 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
ASUSTeK |
| R1-2301308 |
Discussion of co-channel coexistence for LTE sidelink and NR sidelink |
Transsion Holdings |
| R1-2301348 |
Discussion on Co-channel Coexistence for LTE Sidelink and NR Sidelink |
Apple |
| R1-2301415 |
Co-channel Coexistence Between LTE SL and NR SL |
Qualcomm Incorporated |
| R1-2301495 |
Discussion on co-channel coexistence of LTE-SL and NR-SL |
NTT DOCOMO, INC. |
| R1-2301534 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
LG Electronics |
| R1-2301545 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
Sharp |
| R1-2301736 |
Discussion on co-channel coexistence for LTE sidelink and NR sidelink |
WILUS Inc. |
| R1-2301853 |
Feature lead summary #1 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2301854 |
Feature lead summary #2 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2301855 |
Feature lead summary #3 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-2300039 |
On Beam Management for Sidelink in FR2 |
Nokia, Nokia Shanghai Bell |
| R1-2300127 |
Enhanced sidelink operation on FR2 licensed spectrum |
Huawei, HiSilicon |
| R1-2300300 |
Sidelink beam management on FR2 licensed spectrum |
OPPO |
| R1-2300314 |
Discussion on Enhanced Sidelink Operation on FR2 Licensed Spectrum |
Johns Hopkins University APL |
| R1-2300357 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
ZTE, Sanechips |
| R1-2300381 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
TOYOTA Info Technology Center |
| R1-2300456 |
Enhanced sidelink operation on FR2 licensed spectrum |
vivo |
| R1-2300579 |
Discussion on SL beam management in FR2 licensed spectrum |
xiaomi |
| R1-2300683 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
CATT |
| R1-2300735 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
Lenovo |
| R1-2300827 |
Discussion on sidelink operation on FR2 licensed spectrum |
NEC |
| R1-2300878 |
Discussion on sidelink beam management on FR2 licensed spectrum |
Sony |
| R1-2300951 |
On Sidelink Operation in FR2 Licensed Spectrum |
Intel Corporation |
| R1-2301005 |
Discussion on sidelink enhancements on FR2 licensed spectrum |
CMCC |
| R1-2301132 |
Study aspects for sidelink in FR2 |
Ericsson |
| R1-2301176 |
On enhanced SL FR2 operation |
InterDigital, Inc. |
| R1-2301192 |
NR Sidelink Operation in FR2 |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2301267 |
On enhanced SL Operation in FR2 |
Samsung |
| R1-2301349 |
Discussion on Sidelink Operation on FR2 |
Apple |
| R1-2301416 |
Enhanced sidelink operation on FR2 licensed spectrum |
Qualcomm Incorporated |
| R1-2301496 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
NTT DOCOMO, INC. |
| R1-2301535 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
LG Electronics |
| R1-2301546 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
Sharp |
| R1-2301616 |
Discussion on SL operation on FR2 |
MediaTek Inc. |
| R1-2301694 |
Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation |
CEWiT |
| R1-2301737 |
Discussion on enhanced sidelink operation on FR2 licensed spectrum |
WILUS Inc. |
| R1-2301843 |
FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2301844 |
FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum |
Moderator (Apple) |
| R1-2301845 |
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-2301218 |
Work Plan for Rel-18 WI on Expanded and Improved NR Positioning |
Intel Corporation |
| R1-2302047 |
Discussion of SA2 LS on PRU Procedures |
Moderator (Qualcomm) |
| R1-2302065 |
Session notes for 9.5 (Study on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2302106 |
Discussion (2nd round) of SA2 LS on PRU Procedures |
Moderator (Qualcomm) |
| R1-2302145 |
[Draft] LS Reply on PRU Procedures |
Moderator (Qualcomm) |
| R1-2302146 |
LS Reply on PRU Procedures |
RAN1, Qualcomm |
| R1-2302220 |
RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning |
Rapporteur (Intel Corporation) |
| 9.5.1.1 |
SL positioning reference signal |
|
| R1-2300040 |
Design of SL positioning reference signal SL-PRS |
Nokia, Nokia Shanghai Bell |
| R1-2300063 |
Discussion on SL positioning reference signal |
FUTUREWEI |
| R1-2300079 |
Considerations on SL-PRS design |
Huawei, HiSilicon |
| R1-2300222 |
Discussion on SL positioning reference signal |
Spreadtrum Communications |
| R1-2300301 |
Discussion on SL positioning reference signal |
OPPO |
| R1-2300457 |
Discussion on SL positioning reference signal |
vivo |
| R1-2300580 |
Discussion on Sidelink positioning reference signal |
xiaomi |
| R1-2300684 |
Discussion on SL positioning reference signal |
CATT, GOHIGH |
| R1-2300720 |
Discussion on SL positioning reference signal |
China Telecom |
| R1-2300787 |
SL positioning reference signal |
Sharp |
| R1-2300802 |
Discussion on SL positioning reference signal |
ZTE |
| R1-2300836 |
Discussion on SL positioning reference signal |
NEC |
| R1-2300879 |
Considerations on SL Positioning Reference Signal |
Sony |
| R1-2300898 |
Discussion on Sidelink Positioning Reference Signal |
Panasonic |
| R1-2300952 |
On SL Positioning Reference Signals |
Intel Corporation |
| R1-2301006 |
Discussion on SL positioning reference signal |
CMCC |
| R1-2301116 |
SL-PRS design and power control for SL-PRS |
InterDigital, Inc. |
| R1-2301142 |
Design considerations on SL positioning reference signal |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301211 |
Discussion on SL PRS Aspects |
Lenovo |
| R1-2301268 |
On SL Positioning Reference Signal |
Samsung |
| R1-2301300 |
Discussion on sidelink positioning reference signal |
ASUSTeK |
| R1-2301350 |
Discussion on SL positioning reference signal |
Apple |
| R1-2301417 |
Reference Signal Design for SL Positioning |
Qualcomm Incorporated |
| R1-2301497 |
Discussion on reference signal for SL positioning |
NTT DOCOMO, INC. |
| R1-2301536 |
Discussion on SL positioning reference signal |
LG Electronics |
| R1-2301636 |
Reference signal design for sidelink positioning |
MediaTek Inc. |
| R1-2301678 |
SL positioning reference signal design |
Ericsson |
| R1-2301695 |
View on SL positioning reference signal design |
CEWiT, Reliance Jio |
| R1-2301875 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2301876 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2302095 |
FL summary #3 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2302096 |
FL summary #4 on SL positioning reference signal |
Moderator (Intel Corporation) |
| 9.5.1.2 |
Measurements and reporting for SL positioning |
|
| R1-2300041 |
On measurements and reporting for SL positioning |
Nokia, Nokia Shanghai Bell |
| R1-2300067 |
Discussion on measurements and reporting for SL positioning |
FUTUREWEI |
| R1-2300080 |
SL positioning methods, measurements, and reporting |
Huawei, HiSilicon |
| R1-2300223 |
Discussion on measurements and reporting for SL positioning |
Spreadtrum Communications |
| R1-2300302 |
Discussion on measurements and reporting for SL positioning |
OPPO |
| R1-2300382 |
Discussion on measurements and reporting for SL positioning |
TOYOTA Info Technology Center |
| R1-2300458 |
Discussion on measurements and reporting for SL positioning |
vivo |
| R1-2300581 |
Discussion on measurements and reporting for SL positioning |
xiaomi |
| R1-2300685 |
Discussion on measurements and reporting for SL positioning |
CATT, GOHIGH |
| R1-2300760 |
Proposed RTT measurement method using Carrier Phase Positioning |
Locaila |
| R1-2300788 |
Measurements and reporting for SL positioning |
Sharp |
| R1-2300803 |
Discussion on SL positioning measurements and reporting |
ZTE |
| R1-2300880 |
Considerations on SL Positioning Measurements and Reporting |
Sony |
| R1-2300953 |
Measurements and reporting for SL positioning |
Intel Corporation |
| R1-2301007 |
Discussion on measurements and reporting for SL positioning |
CMCC |
| R1-2301117 |
Measurement and reporting for SL positioning |
InterDigital, Inc. |
| R1-2301143 |
Measurements and reporting for SL positioning |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301212 |
Discussion on SL Positioning Measurement and Reporting |
Lenovo |
| R1-2301269 |
On Measurements and Reporting for SL Positioning |
Samsung |
| R1-2301351 |
On Measurements and reporting for SL positioning |
Apple |
| R1-2301418 |
Measurements and Reporting for SL Positioning |
Qualcomm Incorporated |
| R1-2301498 |
Discussion on measurement and reporting for SL positioning |
NTT DOCOMO, INC. |
| R1-2301537 |
Discussion on measurements and reporting for SL positioning |
LG Electronics |
| R1-2301562 |
Discussion on measurements and reporting for SL positioning |
DENSO CORPORATION |
| R1-2301633 |
Measurement and reporting design for sidelink positioning |
MediaTek Inc. |
| R1-2301679 |
Measurements and reporting for SL positioning |
Ericsson |
| R1-2301696 |
View on SL positioning methods, measurements and reporting for SL positioning |
CEWiT, Reliance Jio |
| R1-2301950 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2301951 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2301952 |
Summary #3 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| 9.5.1.3 |
Resource allocation for SL positioning reference signal |
|
| R1-2300042 |
On resource allocation for SL positioning reference signal |
Nokia, Nokia Shanghai Bell |
| R1-2300068 |
Discussion on resource allocation for SL PRS |
FUTUREWEI |
| R1-2300081 |
Resource allocations for SL positioning |
Huawei, HiSilicon |
| R1-2300224 |
Discussion on resource allocation for SL positioning reference signal |
Spreadtrum Communications |
| R1-2300303 |
Discussion on resource allocation for SL positioning reference signal |
OPPO |
| R1-2300383 |
Discussion on resource allocation for SL positioning |
TOYOTA Info Technology Center |
| R1-2300459 |
Discussion on resource allocation for SL positioning reference signal |
vivo |
| R1-2300582 |
Discussion on resource allocation for SL positioning reference signal |
xiaomi |
| R1-2300686 |
Discussion on Resource allocation for SL positioning reference signal |
CATT, GOHIGH |
| R1-2300721 |
Discussion on resource allocation for SL positioning reference signal |
China Telecom |
| R1-2300804 |
Discussion on resource allocation for SL positioning reference signal |
ZTE |
| R1-2300837 |
Discussion on resource allocation for SL positioning reference signal |
NEC |
| R1-2300881 |
Considerations on SL Positioning Reference Signal Resource allocation |
Sony |
| R1-2300954 |
On resource allocation for SL positioning |
Intel Corporation |
| R1-2301008 |
Discussion on resource allocation for SL positioning reference signal |
CMCC |
| R1-2301118 |
Resource allocation for SL positioning reference signal |
InterDigital, Inc. |
| R1-2301144 |
Considerations on SL-PRS resource allocation |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301213 |
Discussion on SL Positioning Resource Allocation |
Lenovo |
| R1-2301270 |
On Resource Allocation for SL Positioning Reference Signal |
Samsung |
| R1-2301302 |
Discussion on resource allocation for SL PRS |
ASUSTeK |
| R1-2301352 |
On Resource allocation for SL positioning reference signal |
Apple |
| R1-2301419 |
Resource Allocation for SL-PRS |
Qualcomm Incorporated |
| R1-2301499 |
Discussion on resource allocation for SL positioning |
NTT DOCOMO, INC. |
| R1-2301538 |
Discussion on resource allocation for SL positioning reference signal |
LG Electronics |
| R1-2301547 |
Resource allocation for SL positioning reference signal |
Sharp |
| R1-2301561 |
Discussion on resource allocation for SL positioning reference signal |
DENSO CORPORATION |
| R1-2301634 |
Resource allocation for SL-PRS |
MediaTek Inc. |
| R1-2301649 |
Considerations on resource allocation for SL positioning reference signal |
ITL |
| R1-2301680 |
Resource allocation for SL positioning reference signal |
Ericsson |
| R1-2301697 |
View on SL positioning resource allocation for SL positioning reference signal |
CEWiT, Reliance Jio |
| R1-2301841 |
Resource Allocation for SL-PRS |
Qualcomm Incorporated |
| R1-2302004 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2302045 |
Moderator Summary #2 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2302094 |
Moderator Summary #3 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2302162 |
Moderator Summary #4 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| 9.5.2 |
NR DL and UL carrier phase positioning |
|
| R1-2300085 |
Discussion on carrier phase measurement |
Huawei, HiSilicon |
| R1-2300225 |
Discussion on NR DL and UL carrier phase positioning |
Spreadtrum Communications |
| R1-2300307 |
Discussions on NR carrier phase positioning |
OPPO |
| R1-2300460 |
Discussion on carrier phase positioning |
vivo |
| R1-2300538 |
Discussions on Carrier Phase Measurement for NR Positioning |
BUPT |
| R1-2300583 |
NR DL and UL carrier phase positioning |
xiaomi |
| R1-2300687 |
Discussion on NR DL and UL carrier phase positioning |
CATT |
| R1-2300761 |
Proposed solution for uplink and downlink carrier phase positioning |
Locaila |
| R1-2300778 |
Views on NR DL and UL carrier phase positioning |
Nokia, Nokia Shanghai Bell |
| R1-2300805 |
Discussion on carrier phase measurement based positioning |
ZTE |
| R1-2300955 |
On DL and UL carrier phase positioning |
Intel Corporation |
| R1-2301009 |
Discussion on DL/UL carrier phase positioning |
CMCC |
| R1-2301066 |
Discussion on carrier phase positioning in NR |
LG Electronics |
| R1-2301119 |
Discussion on positioning based on NR carrier phase measurement |
InterDigital, Inc. |
| R1-2301214 |
DL & UL Carrier Phase Positioning Discussion |
Lenovo |
| R1-2301271 |
On NR DL and UL Carrier Phase Positioning |
Samsung |
| R1-2301353 |
On NR DL and UL carrier phase positioning |
Apple |
| R1-2301420 |
NR Carrier Phase Positioning |
Qualcomm Incorporated |
| R1-2301500 |
Discussion on NR DL and UL carrier phase positioning |
NTT DOCOMO, INC. |
| R1-2301630 |
Solutions for carrier phase positioning |
MediaTek Inc. |
| R1-2301681 |
NR DL and UL carrier phase positioning |
Ericsson |
| R1-2301724 |
Discussion on NR UL and DL carrier phase positioning |
IIT Kanpur, CEWiT |
| R1-2301828 |
FL Summary #1 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2301829 |
FL Summary #2 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2301830 |
FL Summary #3 for NR DL and UL carrier phase positioning |
Moderator (CATT) |
| 9.5.3 |
LPHAP (Low Power High Accuracy Positioning) |
|
| R1-2300064 |
Discussions of LPHAP enhancements |
FUTUREWEI |
| R1-2300082 |
Physical layer aspects of LPHAP |
Huawei, HiSilicon |
| R1-2300226 |
Discussion on LPHAP (Low Power High Accuracy Positioning) |
Spreadtrum Communications |
| R1-2300309 |
Discussion on low power high accuracy positioning |
OPPO |
| R1-2300461 |
Discussion on low power high accuracy positioning |
vivo |
| R1-2300584 |
Discussion on Low Power High Accuracy Positioning |
xiaomi |
| R1-2300688 |
Discussion on Low Power High Accuracy Positioning |
CATT |
| R1-2300777 |
Views on LPHAP |
Nokia, Nokia Shanghai Bell |
| R1-2300806 |
Discussion on low power high accuracy positioning |
ZTE |
| R1-2300832 |
Discussion on Low Power High Accuracy Positioning |
NEC |
| R1-2300882 |
Considerations on Low Power High Accuracy Positioning |
Sony |
| R1-2300956 |
On support of LPHAP |
Intel Corporation |
| R1-2301010 |
Discussion on low power high accuracy positioning |
CMCC |
| R1-2301067 |
Discussion on LPHAP in idle/inactive state |
LG Electronics |
| R1-2301141 |
Discussions on Low Power High Accuracy Positioning (LPHAP) techniques |
InterDigital, Inc. |
| R1-2301272 |
On Low Power High Accuracy Positioning |
Samsung |
| R1-2301354 |
On Low Power High Accuracy Positioning |
Apple |
| R1-2301421 |
Discussion on LPHAP Positioning |
Qualcomm Incorporated |
| R1-2301501 |
Discussion on Low Power High Accuracy Positioning |
NTT DOCOMO, INC. |
| R1-2301682 |
On Low Power High Accuracy Positioning |
Ericsson |
| R1-2301967 |
Summary #1 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2301968 |
Summary #2 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2301969 |
Summary #3 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2301990 |
Discussion on LS reply regarding LPHAP |
Moderator (Huawei) |
| R1-2301991 |
Draft LS reply on the requirement for LPHAP |
Moderator (Huawei) |
| R1-2302074 |
LS reply on the requirement for LPHAP |
RAN1, Huawei |
| R1-2302189 |
Summary #4 for low power high accuracy positioning |
Moderator (CMCC) |
| 9.5.4 |
Bandwidth aggregation for positioning measurements |
|
| R1-2300084 |
Signalings and procedures to support PRS/SRS BW aggregation |
Huawei, HiSilicon |
| R1-2300227 |
Discussion on bandwidth aggregation for positioning measurements |
Spreadtrum Communications |
| R1-2300308 |
Discussion on bandwidth aggregation for positioning measurement |
OPPO |
| R1-2300462 |
Discussion on bandwidth aggregation for positioning measurements |
vivo |
| R1-2300585 |
Bandwidth aggregation for positioning measurement |
xiaomi |
| R1-2300689 |
Discussion on bandwidth aggregation for positioning measurements |
CATT |
| R1-2300779 |
Views on Bandwidth aggregation for positioning measurements |
Nokia, Nokia Shanghai Bell |
| R1-2300807 |
Discussion on BW aggregation for positioning |
ZTE |
| R1-2300809 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2300810 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2300957 |
On bandwidth aggregation for positioning measurements |
Intel Corporation |
| R1-2301011 |
Discussion on BW aggregation for positioning measurements |
CMCC |
| R1-2301068 |
Discussion on Bandwidth aggregation for positioning measurements |
LG Electronics |
| R1-2301137 |
Bandwidth aggregation for positioning measurements |
InterDigital, Inc. |
| R1-2301215 |
PRS/SRS Bandwidth Aggregation Aspects |
Lenovo |
| R1-2301273 |
On Bandwidth Aggregation for Positioning Measurements |
Samsung |
| R1-2301355 |
On Bandwidth aggregation for positioning measurements |
Apple |
| R1-2301422 |
Discussion on Bandwidth aggregation for Positioning |
Qualcomm Incorporated |
| R1-2301502 |
Discussion on bandwidth aggregation for positioning measurements |
NTT DOCOMO, INC. |
| R1-2301631 |
PRS/SRS aggregation for positioning measurement |
MediaTek Inc. |
| R1-2301683 |
Bandwidth aggregation for positioning measurements |
Ericsson |
| R1-2302091 |
Summary #3 for BW aggregation positioning |
Moderator (ZTE ) |
| 9.5.5 |
Positioning for RedCap UEs |
|
| R1-2300069 |
On positioning for RedCap UEs in Rel-18 |
FUTUREWEI |
| R1-2300083 |
Discussion on frequency hopping for RedCap positioning |
Huawei, HiSilicon |
| R1-2300228 |
Discussion on positioning for RedCap Ues |
Spreadtrum Communications |
| R1-2300310 |
Discussion on positioning for RedCap UEs |
OPPO |
| R1-2300463 |
Discussion on positioning for RedCap UEs |
vivo |
| R1-2300690 |
Discussion on positioning for RedCap UEs |
CATT |
| R1-2300780 |
Views on Positioning for RedCap UEs |
Nokia, Nokia Shanghai Bell |
| R1-2300808 |
Discussion on Positioning for RedCap UEs |
ZTE |
| R1-2300833 |
Discussion on positioning support for RedCap UEs |
NEC |
| R1-2300883 |
Considerations on Positioning for RedCap UEs |
Sony |
| R1-2300958 |
Positioning for RedCap UEs |
Intel Corporation |
| R1-2301012 |
Discussion on RedCap UE positioning |
CMCC |
| R1-2301069 |
Discussion on positioning support for RedCap UEs |
LG Electronics |
| R1-2301138 |
Positioning for RedCap UEs |
InterDigital, Inc. |
| R1-2301216 |
RedCap Positioning |
Lenovo |
| R1-2301274 |
On Positioning for RedCap UEs |
Samsung |
| R1-2301356 |
On Positioning for RedCap UEs |
Apple |
| R1-2301423 |
Positioning for Reduced Capabilities UEs |
Qualcomm Incorporated |
| R1-2301503 |
Discussion on positioning for RedCap UEs |
NTT DOCOMO, INC. |
| R1-2301632 |
Positioning for RedCap UEs |
MediaTek Inc. |
| R1-2301684 |
Positioning for RedCap Ues |
Ericsson |
| R1-2301727 |
Discussion on NR positioning for RedCap |
IIT Kanpur, CEWiT |
| R1-2301984 |
Feature Lead Summary #1 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2301985 |
Feature Lead Summary #2 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2301986 |
Feature Lead Summary #3 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2302125 |
Draft LS discussion for DL PRS and UL SRS frequency hopping Switching time |
Moderator (Ericsson) |
| R1-2302126 |
[Draft] LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
Moderator (Ericsson) |
| R1-2302127 |
LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs |
RAN1, Ericsson |
| R1-2302210 |
Feature Lead Summary #4 for Positioning for RedCap UEs |
Moderator (Ericsson) |
| R1-2302214 |
Draft LS discussion for DL PRS and UL SRS frequency hopping Switching time |
Moderator (Ericsson) |
| 9.6 |
Enhanced support of reduced capability NR device |
|
| R1-2300177 |
WI work plan for Rel-18 RedCap |
Rapporteur (Ericsson) |
| R1-2301885 |
RAN1 agreements for Rel-18 NR RedCap |
Rapporteur (Ericsson) |
| R1-2302066 |
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-2300058 |
Discussion on R18 RedCap complexity techniques |
FUTUREWEI |
| R1-2300114 |
Discussion on potential solutions to further reduce UE complexity |
Huawei, HiSilicon |
| R1-2300229 |
Discussion on enhanced support of RedCap devices |
Spreadtrum Communications, New H3C |
| R1-2300272 |
Further consideration on reduced UE complexity |
OPPO |
| R1-2300371 |
Discussion on further UE complexity reduction |
ZTE, Sanechips |
| R1-2300464 |
Discussion on further UE complexity reduction |
vivo |
| R1-2300500 |
Further RedCap UE complexity reduction |
Ericsson |
| R1-2300586 |
Discussion on further complexity reduction for eRedCap UEs |
xiaomi |
| R1-2300691 |
Discussion on further complexity reduction for Rel-18 RedCap UE |
CATT |
| R1-2300794 |
Discussion on UE complexity reduction |
Sharp |
| R1-2300852 |
UE complexity reduction for eRedCap |
Panasonic |
| R1-2300855 |
Discussion on Rel-18 RedCap UE |
NEC |
| R1-2300858 |
UE complexity reduction |
Lenovo |
| R1-2300884 |
UE complexity reduction for eRedCap |
Sony |
| R1-2300959 |
Discussion on complexity reduction for eRedCap UE |
Intel Corporation |
| R1-2301013 |
Discussion on further reduced UE complexity |
CMCC |
| R1-2301078 |
Discussion on UE complexity reduction |
DENSO CORPORATION |
| R1-2301106 |
Discussion on further UE complexity reduction for eRedCap |
LG Electronics |
| R1-2301149 |
RedCap UE Complexity Reduction |
Nokia, Nokia Shanghai Bell |
| R1-2301188 |
Considerations for further UE complexity reduction |
Sierra Wireless. S.A. |
| R1-2301193 |
On further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2301275 |
Further UE complexity reduction for eRedCap |
Samsung |
| R1-2301309 |
Discussion on UE complexity reduction |
Transsion Holdings |
| R1-2301357 |
Further RedCap UE Complexity Reduction |
Apple |
| R1-2301424 |
UE complexity reduction for eRedCap |
Qualcomm Incorporated |
| R1-2301504 |
Discussion on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2301609 |
On eRedCap UE complexity reduction |
MediaTek Inc. |
| R1-2301772 |
Discussion on further reduced UE complexity |
CMCC |
| R1-2301783 |
On eRedCap UE complexity reduction |
MediaTek Inc. |
| R1-2301874 |
On further complexity reduction of NR UE |
Nordic Semiconductor ASA |
| R1-2301886 |
FL summary #1 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2301887 |
FL summary #2 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2301888 |
FL summary #3 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| R1-2301889 |
FL summary #4 on Rel-18 RedCap UE complexity reduction |
Moderator (Ericsson) |
| 9.7 |
Network energy savings for NR |
|
| R1-2300133 |
WI Work plan for R18 network energy savings |
Rapporteur (Huawei) |
| R1-2300405 |
Considerations on Network energy savings for NR |
KT Corp. |
| R1-2301717 |
Addition of abbreviations and symbols to TR 38.864 |
Huawei |
| R1-2302234 |
Addition of abbreviations and symbols to TR 38.864 |
Huawei |
| R1-2302235 |
Addition of abbreviations and symbols to TR 38.864 |
Huawei |
| 9.7.1 |
Techniques in spatial and power domains |
|
| R1-2300065 |
Spatial and Power Adaptations for Network Energy Savings |
FUTUREWEI |
| R1-2300073 |
Power saving techniques in spatial and power domains |
Huawei, HiSilicon |
| R1-2300143 |
Techniques in spatial and power domains |
Nokia, Nokia Shanghai Bell |
| R1-2300230 |
Discussion on NES techniques in spatial and power domains |
Spreadtrum Communications |
| R1-2300264 |
Discussion on techniques in spatial and power domains |
OPPO |
| R1-2300360 |
Spatial and power domain adaptation for network energy saving |
Panasonic |
| R1-2300372 |
Discussion on NES techniques in spatial and power domains |
ZTE, Sanechips |
| R1-2300403 |
Network Energy Saving in Spatial and Power Domain |
Google |
| R1-2300465 |
Discussions on NES techniques in spatial and power domain |
vivo |
| R1-2300587 |
Discussion on techniques in spatial and power domains |
Xiaomi |
| R1-2300692 |
Network Energy Saving techniques in spatial and power domain |
CATT |
| R1-2300722 |
Discussion on NES techniques in spatial and power domains |
China Telecom |
| R1-2300752 |
Discussion on NW energy saving techniques in spatial and power domains |
Fujitsu |
| R1-2300768 |
Discussion on network energy saving techniques in spatial and power domains |
NEC |
| R1-2300784 |
Discussion on techniques in spatial and power domains |
InterDigital, Inc. |
| R1-2300960 |
Discussion on NWES techniques in spatial and power domain |
Intel Corporation |
| R1-2301014 |
Discussion on network energy saving techniques in spatial and power domains |
CMCC |
| R1-2301047 |
Network energy saving techniques in spatial domain |
ETRI |
| R1-2301107 |
Discussion on NES techniques in spatial and power domains |
LG Electronics |
| R1-2301163 |
Spatial Domain Adaptation for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301206 |
Network energy saving techniques in spatial and power domains |
Lenovo |
| R1-2301222 |
Network energy savings techniques in spatial and power domains |
AT&T |
| R1-2301276 |
Techniques in spatial and power domains |
Samsung |
| R1-2301310 |
Discussion of NES techniques in spatial domain and power domain |
Transsion Holdings |
| R1-2301319 |
Discussion on techniques in spatial and power domains |
ITRI |
| R1-2301358 |
Discussion on spatial and power domain enhancements to support network energy saving |
Apple |
| R1-2301425 |
Techniques in spatial and power domains |
Qualcomm Incorporated |
| R1-2301505 |
Discussion on spatial and power domain enhancements for NW energy savings |
NTT DOCOMO, INC. |
| R1-2301554 |
NW energy saving techniques in spatial and power domains |
Ericsson |
| R1-2301599 |
On NW energy saving techniques in spatial and power domains |
MediaTek Inc. |
| R1-2301698 |
Discussion on spatial and power adaptations for network energy saving |
CEWiT, Reliance Jio |
| R1-2301964 |
FL summary#1 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2301965 |
FL summary#2 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2301966 |
FL summary#3 for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| R1-2302179 |
Final FL summary for spatial and power domain techniques for R18 NES |
Moderator (Huawei) |
| 9.7.2 |
Enhancements on cell DTX/DRX mechanism |
|
| R1-2300055 |
Network Energy Saving Techniques |
FUTUREWEI |
| R1-2300066 |
Enhancements on cell DTXDRX for NES |
FUTUREWEI |
| R1-2300074 |
Cell DTX/DRX mechanism for network energy saving |
Huawei, HiSilicon |
| R1-2300144 |
Enhancements on cell DTX/DRX mechanism |
Nokia, Nokia Shanghai Bell |
| R1-2300231 |
Discussion on enhancements on cell DTX/DRX mechanism |
Spreadtrum Communications |
| R1-2300265 |
Discussion on enhancements on cell DTX/DRX mechanism |
OPPO |
| R1-2300361 |
Cell DTX/DRX enhancement for network energy saving |
Panasonic |
| R1-2300373 |
Discussion on cell DTX/DRX |
ZTE, Sanechips |
| R1-2300404 |
Network Energy Saving on Cell DTX and DRX |
Google |
| R1-2300466 |
Discussions on enhancements on cell DTX/DRX mechanism |
vivo |
| R1-2300588 |
Discussions on cell DTX-DRX for network energy saving |
xiaomi |
| R1-2300693 |
DTX/DRX for network Energy Saving |
CATT |
| R1-2300723 |
Discussion on cell DTX/DRX mechanism |
China Telecom |
| R1-2300753 |
Discussion on cell DTX/DRX mechanism |
Fujitsu |
| R1-2300764 |
Cell DTX/DRX Configuration for Network Energy Saving |
NEC |
| R1-2300785 |
Discussion on enhancements on cell DTX/DRX mechanism |
InterDigital, Inc. |
| R1-2300961 |
Discussion on enhancements on cell DTX/DRX mechanism |
Intel Corporation |
| R1-2301015 |
Discussion on cell DTX/DRX enhancements |
CMCC |
| R1-2301048 |
Enhancements on cell DTX/DRX mechanism |
ETRI |
| R1-2301108 |
Discussion on cell DTX/DRX mechanism |
LG Electronics |
| R1-2301162 |
Discussion on cell DTX/DRX mechanism |
Rakuten Mobile, Inc |
| R1-2301164 |
RAN1 Considerations for Cell DTX and DRX |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2301277 |
Enhancements on cell DTX/DRX mechanism |
Samsung |
| R1-2301311 |
Discussion on Enhancement on cell DTX DRX mechanism |
Transsion Holdings |
| R1-2301320 |
Discussion on potential enhancements on cell DTX/DRX mechanism for NR |
ITRI |
| R1-2301359 |
Discussion on UE behavior for cell DRX/DTX |
Apple |
| R1-2301426 |
Enhancements on cell DTX and DRX mechanism |
Qualcomm Incorporated |
| R1-2301506 |
Discussion on enhancements on Cell DTX/DRX mechanism |
NTT DOCOMO, INC. |
| R1-2301555 |
RAN1 aspects of cell DTX/DRX |
Ericsson |
| R1-2301600 |
On NW energy saving enhancements for cell DTX/DRX mechanism |
MediaTek Inc. |
| R1-2301699 |
Discussion on cell DTX/DRX mechanism for network energy saving |
CEWiT, Reliance Jio |
| R1-2301814 |
Summary of issues for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2301815 |
Discussion Summary #1 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2302131 |
Discussion Summary #2 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2302218 |
Discussion Summary #3 for enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| 9.8 |
NR network-controlled repeaters |
|
| R1-2300701 |
Discussion on RRC and MAC CE parameters for NCR |
ZTE |
| 9.8.1 |
Side control information and NCR behavior |
|
| R1-2300121 |
Side control information and behaviors for network-controlled repeaters |
Huawei, HiSilicon |
| R1-2300232 |
Discussion on side control information and NCR behavior |
Spreadtrum Communications |
| R1-2300467 |
Discussion on side control information and NCR behavior |
vivo |
| R1-2300589 |
Discussion on side control information and NCR behavior |
xiaomi |
| R1-2300595 |
Discussions on side control information and NCR behavior |
InterDigital, Inc. |
| R1-2300694 |
Side control information to enable NR network-controlled repeaters |
CATT |
| R1-2300702 |
Discussion on side control information for NCR |
ZTE |
| R1-2300724 |
Discussion on side control information and NCR behavior |
China Telecom |
| R1-2300754 |
Discussion on side control information and NCR behavior |
Fujitsu |
| R1-2300772 |
Discussion on side control information and NCR behavior |
Nokia, Nokia Shanghai Bell |
| R1-2300781 |
NCR side control information for NCR operations |
Sharp |
| R1-2300834 |
Discussion on side control information and NCR behaviour |
NEC |
| R1-2300885 |
More considerations on side control information and NCR behavior |
Sony |
| R1-2300920 |
Discussion on side control information and NCR behaviour |
Lenovo |
| R1-2300962 |
Discussion on Side control information to enable NR network-controlled repeater |
Intel Corporation |
| R1-2301016 |
Discussion on side control information and NCR behavior |
CMCC |
| R1-2301036 |
Discussion on side control information and NCR behavior |
NICT |
| R1-2301049 |
Discussion on side control information for network-controlled repeater |
ETRI |
| R1-2301070 |
Discussion on side control information and NCR behavior |
LG Electronics |
| R1-2301099 |
Discussion on side control information and NCR behavior |
Panasonic |
| R1-2301136 |
Discussion on side control information and NCR behavior |
KDDI Corporation |
| R1-2301145 |
Discussion on signaling side control information and NCR behaviour |
IIT Kanpur, CEWiT |
| R1-2301278 |
Discussion on side control information and NCR behavior |
Samsung |
| R1-2301360 |
On side control information and NCR behavior |
Apple |
| R1-2301427 |
On side control information and NCR behavior |
Qualcomm Incorporated |
| R1-2301507 |
Discussion on Side control information and NCR behavior |
NTT DOCOMO, INC. |
| R1-2301617 |
Side control information and NCR behavior |
MediaTek Inc. |
| R1-2301766 |
Side-control information and NCR behavior |
Ericsson |
| R1-2301898 |
Summary#1 of discussion on side control information |
Moderator(ZTE) |
| R1-2301899 |
Summary#2 of discussion on side control information |
Moderator(ZTE) |
| R1-2302034 |
Summary#3 of discussion on side control information |
Moderator (ZTE) |
| R1-2302035 |
Summary#4 of discussion on side control information |
Moderator (ZTE) |
| R1-2302036 |
[Draft] LS to RAN2 on the RRC and MAC CE parameters for NCR |
Moderator (ZTE) |
| R1-2302113 |
LS to RAN2 on the RRC and MAC CE parameters for NCR |
RAN1, ZTE |
| R1-2302227 |
LS to RAN2 on the RRC and MAC CE parameters for NCR |
RAN1, ZTE |
| 9.8.2 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
|
| R1-2300122 |
Other aspects of network-controlled repeaters |
Huawei, HiSilicon |
| R1-2300468 |
Discussion on other aspects of NCR |
vivo |
| R1-2300590 |
Discussion on other aspects of NCR |
xiaomi |
| R1-2300596 |
Discussion on control plane signaling and procedures for network-controlled repeaters |
InterDigital, Inc. |
| R1-2300695 |
Discussion on signaling for side control information for NR network-controlled repeaters |
CATT |
| R1-2300703 |
Discussion on other aspects for NCR |
ZTE |
| R1-2300755 |
Discussion on control plane signaling and procedures relevant to RAN1 |
Fujitsu |
| R1-2300773 |
Discussion on other aspects including control plane signalling and procedures relevant to RAN1 |
Nokia, Nokia Shanghai Bell |
| R1-2300835 |
Discussion on other aspects for network-controlled repeaters |
NEC |
| R1-2300886 |
More considerations on signaling and control procedures relevant to RAN1 |
Sony |
| R1-2300963 |
Discussions on other aspects including control plane signaling and procedures |
Intel Corporation |
| R1-2301017 |
Discussion on other including control plane signalling and procedures |
CMCC |
| R1-2301038 |
Discussion on other aspects of NCR |
CAICT |
| R1-2301050 |
Discussion on NCR signaling and procedures |
ETRI |
| R1-2301071 |
Discussion on other aspects for NCR |
LG Electronics |
| R1-2301279 |
On signaling and procedures for network-controlled repeaters |
Samsung |
| R1-2301361 |
On control plane signaling and procedures for NCR |
Apple |
| R1-2301428 |
On other NCR aspects |
Qualcomm Incorporated |
| R1-2301508 |
Other aspects including control plane signalling and procedures relevant to RAN1 |
NTT DOCOMO, INC. |
| R1-2301637 |
Discussion on NCR control plane signaling and procedures |
Lenovo |
| R1-2301767 |
Other aspects including control signaling and procedures for NCR |
Ericsson |
| R1-2301832 |
Summary#1 on other aspects |
Moderator (Fujitsu) |
| 9.9.1 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
|
| R1-2300130 |
Discussion on multi-cell scheduling with a single DCI |
Huawei, HiSilicon |
| R1-2300233 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Spreadtrum Communications |
| R1-2300289 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
OPPO |
| R1-2300342 |
Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI |
ZTE |
| R1-2300365 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
Nokia, Nokia Shanghai Bell |
| R1-2300469 |
Discussion on multi-cell scheduling |
vivo |
| R1-2300591 |
Discussion on the remaining issues for the multi-cell scheduling with a single DCI |
xiaomi |
| R1-2300696 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CATT |
| R1-2300725 |
Remaining issues on multi-cell scheduling with a single DCI |
China Telecom |
| R1-2300731 |
On multi-cell scheduling via a single DCI |
Lenovo |
| R1-2300756 |
CSI request in case of multi-cell PUSCH scheduling |
Fujitsu |
| R1-2300830 |
Discussion on Multi-cell PXSCH scheduling with a single DCI |
NEC |
| R1-2300964 |
Discussions on multi-cell scheduling with a single DCI |
Intel Corporation |
| R1-2301018 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CMCC |
| R1-2301062 |
Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI |
CAICT |
| R1-2301091 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2301092 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2301093 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2301094 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2301109 |
Discussion on Multi-cell PUSCH/PDSCH scheduling |
LG Electronics |
| R1-2301280 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2301315 |
Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Langbo |
| R1-2301321 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
ITRI |
| R1-2301362 |
On remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI |
Apple |
| R1-2301429 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Qualcomm Incorporated |
| R1-2301509 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
NTT DOCOMO, INC. |
| R1-2301556 |
Multi-cell PUSCH/PDSCH scheduling with a single DCI |
Ericsson |
| R1-2301563 |
Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Google Inc. |
| R1-2301601 |
On multi-cell PUSCH/PDSCH scheduling with a single DCI |
MediaTek Inc. |
| 9.9.2 |
Multi-carrier UL Tx switching scheme |
|
| R1-2300131 |
Discussion on multi-carrier UL Tx switching |
Huawei, HiSilicon |
| R1-2300234 |
Discussion on multi-carrier UL Tx switching scheme |
Spreadtrum Communications |
| R1-2300290 |
Discussion on multi-carrier UL Tx switching scheme |
OPPO |
| R1-2300343 |
Discussion on Multi-carrier UL Tx switching scheme |
ZTE |
| R1-2300470 |
Discussion on UL TX switching |
vivo |
| R1-2300492 |
Discussion on remaining issues of multi-carrier UL Tx switching |
FGI |
| R1-2300592 |
Discussion on multi-carrier UL Tx switching scheme |
xiaomi |
| R1-2300697 |
Discussion on multi-carrier UL Tx switching scheme |
CATT |
| R1-2300726 |
Remaining issues on UL Tx switching across up to 3 or 4 bands |
China Telecom |
| R1-2301019 |
Discussion on multi-carrier UL Tx switching scheme |
CMCC |
| R1-2301059 |
On Multi-Carrier UL Tx Switching |
Nokia, Nokia Shanghai Bell |
| R1-2301110 |
Discussion on Multi-carrier UL Tx switching scheme |
LG Electronics |
| R1-2301281 |
On multi-carrier UL Tx switching |
Samsung |
| R1-2301363 |
On remaining issues for multi-carrier UL Tx switching |
Apple |
| R1-2301430 |
Discussion on Rel-18 UL Tx switching |
Qualcomm Incorporated |
| R1-2301510 |
Discussion on Multi-carrier UL Tx switching scheme |
NTT DOCOMO, INC. |
| R1-2301557 |
Multi-carrier UL Tx switching |
Ericsson |
| R1-2301564 |
Discussion on multi-carrier UL Tx switching scheme |
Google Inc. |
| R1-2301801 |
Summary#1 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2301842 |
Discussion on Multi-carrier UL Tx switching scheme |
NTT DOCOMO, INC. |
| R1-2302114 |
Summary#2 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2302221 |
Summary#3 of discussion on multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| 9.10 |
XR Enhancements for NR |
|
| R1-2301626 |
Work Plan for Rel-18 WI on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL) |
| 9.10.1 |
XR-specific capacity enhancements |
|
| R1-2300070 |
XR-specific capacity enhancements |
FUTUREWEI |
| R1-2300123 |
Discussion on CG enhancements for XR capacity |
Huawei, HiSilicon |
| R1-2300137 |
Capacity Enhancements for XR |
Ericsson |
| R1-2300235 |
Discussion on XR-specific capacity enhancements |
Spreadtrum Communications |
| R1-2300291 |
Discussion on XR specific capacity enhancements |
OPPO |
| R1-2300326 |
On XR-specific capacity enhancements techniques |
Google Inc. |
| R1-2300374 |
Discussion on XR specific capacity enhancements |
ZTE, Sanechips |
| R1-2300471 |
Discussion on XR specific capacity enhancements |
vivo |
| R1-2300493 |
Discussion on XR-specific capacity enhancements |
FGI |
| R1-2300552 |
Discussion on XR-specific capacity enhancements |
xiaomi |
| R1-2300657 |
Design of Multiple CG Occasions |
CATT |
| R1-2300739 |
XR-specific capacity enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2300783 |
Discussion on XR-specific capacity enhancements |
InterDigital, Inc. |
| R1-2300818 |
Discussion on XR-specific capacity enhancements |
NEC |
| R1-2300839 |
XR-specific capacity enhancements techniques |
TCL Communication Ltd. |
| R1-2300887 |
Considerations on XR-specific capacity enhancements |
Sony |
| R1-2300965 |
Discussion on XR capacity enhancement techniques |
Intel Corporation |
| R1-2301020 |
Discussion on XR-specific capacity enhancements |
CMCC |
| R1-2301034 |
Discussion on XR-specific capacity enhancements |
DENSO CORPORATION |
| R1-2301100 |
Discussion on XR capacity enhancement techniques |
Panasonic |
| R1-2301111 |
Discussion on XR-specific capacity enhancements |
LG Electronics |
| R1-2301207 |
XR-related CG Enhancements |
Lenovo |
| R1-2301282 |
Capacity Improvements for XR |
Samsung |
| R1-2301364 |
Discussion on XR-specific capacity enhancements |
Apple |
| R1-2301431 |
Capacity Enhancement Techniques for XR |
Qualcomm Incorporated |
| R1-2301511 |
Discussion on XR-specific capacity enhancements |
NTT DOCOMO, INC. |
| R1-2301606 |
Discussion on XR capacity enhancements |
MediaTek Inc. |
| R1-2301780 |
Discussion on XR capacity enhancements |
MediaTek Inc. |
| R1-2301900 |
Moderator Summary#1 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2301901 |
Moderator Summary#2 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2301902 |
Moderator Summary#3 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| R1-2301903 |
Moderator Summary#4 - XR Specific Capacity Improvements |
Moderator (Ericsson) |
| 9.11 |
NTN (Non-Terrestrial Networks) enhancements |
|
| R1-2300324 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R1-2302067 |
Session notes for 9.11 (NTN (Non-Terrestrial Networks) enhancements) |
Ad-Hoc Chair (Huawei) |
| 9.11.1 |
Coverage enhancement for NR NTN |
|
| R1-2300117 |
Discussion on coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2300148 |
Consideration on coverage enhancement for NR NTN |
Lockheed Martin |
| R1-2300236 |
Discussion on coverage enhancements for NTN |
Spreadtrum Communications |
| R1-2300266 |
Discussion on coverage enhancement for NR NTN |
OPPO |
| R1-2300378 |
Considerations on coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2300472 |
Discussions on coverage enhancements for NR NTN |
vivo |
| R1-2300497 |
Discussion on coverage enhancements for NR NTN |
NTPU, NYCU |
| R1-2300553 |
Discussion on coverage enhancement for NR-NTN |
xiaomi |
| R1-2300601 |
Discussion on coverage enhancement for NR NTN |
Baicells |
| R1-2300658 |
Further discussion on UL coverage enhancement for NR NTN |
CATT |
| R1-2300704 |
Discussion on coverage enhancement for NTN |
ZTE |
| R1-2300765 |
Coverage enhancement for NR NTN |
NEC |
| R1-2300888 |
On coverage enhancement for NR NTN |
Sony |
| R1-2300902 |
Discussion on coverage enhancement for NR NTN |
Hyundai Motor Company |
| R1-2300905 |
Discussion on coverage enhancement for NR-NTN |
Panasonic |
| R1-2300921 |
Discussion on coverage enhancement for NR NTN |
Lenovo |
| R1-2300939 |
On coverage enhancement for NR NTN |
Intel Corporation |
| R1-2301021 |
Discussion on coverage enhancement for NR NTN |
CMCC |
| R1-2301051 |
Discussion on coverage enhancement for NR NTN |
ETRI |
| R1-2301055 |
Coverage enhancement for NR NTN |
MediaTek Inc. |
| R1-2301072 |
Discussion on coverage enhancement for NR NTN |
LG Electronics |
| R1-2301283 |
On coverage enhancement for NR NTN |
Samsung |
| R1-2301365 |
On Coverage Enhancement for NR NTN |
Apple |
| R1-2301432 |
Coverage enhancements for NR NTN |
Qualcomm Incorporated |
| R1-2301512 |
Discussion on coverage enhancement for NR NTN |
NTT DOCOMO, INC. |
| R1-2301548 |
Views on Coverage enhancement for NR NTN |
Sharp |
| R1-2301726 |
On coverage enhancements for NR NTN |
Ericsson |
| R1-2301835 |
Summary #1 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2301836 |
Summary #2 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2301837 |
Summary #3 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2301838 |
Summary #4 on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| R1-2302230 |
Summary EOM on 9.11.1 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO, INC.) |
| 9.11.2 |
Network verified UE location for NR NTN |
|
| R1-2300118 |
Discussion on network-verified UE location for NR NTN |
Huawei, HiSilicon |
| R1-2300267 |
Discussion on network verified UE location for NR NTN |
OPPO |
| R1-2300319 |
Discussion on network verified UE location in NR NTN |
THALES |
| R1-2300320 |
FL Summary #1: Network verified UE location for NR NTN |
THALES |
| R1-2300321 |
FL Summary #2: Network verified UE location for NR NTN |
THALES |
| R1-2300322 |
FL Summary #3: Network verified UE location for NR NTN |
THALES |
| R1-2300323 |
FL Summary #4: Network verified UE location for NR NTN |
THALES |
| R1-2300379 |
Considerations on Network Verified UE Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2300473 |
Discussions on UE location verification in NR NTN |
vivo |
| R1-2300554 |
Discussion on the network verified location for NR-NTN |
xiaomi |
| R1-2300659 |
Discussion on Network verified UE location for NR NTN |
CATT |
| R1-2300705 |
Discussion on network verified UE location for NR NTN |
ZTE |
| R1-2300714 |
Discussion on Network-verified UE location for NTN |
PANASONIC |
| R1-2300889 |
Network verified UE location for NR NTN |
Sony |
| R1-2300966 |
On network verified UE location for NR NTN |
Intel Corporation |
| R1-2301052 |
Discussion on Network verified UE location for NR NTN |
ETRI |
| R1-2301056 |
Network verified UE location for NR NTN |
MediaTek Inc. |
| R1-2301073 |
Discussion on network verified UE location for NR NTN |
LG Electronics |
| R1-2301217 |
NTN NW verified UE location |
Lenovo |
| R1-2301284 |
Network verified UE location for NR NTN |
Samsung |
| R1-2301305 |
On network verified UE location in NR NTN |
Ericsson Limited |
| R1-2301366 |
Discussion on Network Verified UE Location |
Apple |
| R1-2301433 |
Network verified UE location for NR NTN |
Qualcomm Incorporated |
| R1-2301513 |
Discussion on Network verified UE location for NR NTN |
NTT DOCOMO, INC. |
| R1-2301653 |
Discussion on Network Verified Location for NR NTN |
TCL Communication Ltd. |
| R1-2302223 |
FL Summary #5: Network verified UE location for NR NTN |
THALES |
| 9.11.3 |
Disabling of HARQ feedback for IoT NTN |
|
| R1-2300119 |
Discussion on disabling of HARQ feedback for IoT NTN |
Huawei, HiSilicon |
| R1-2300147 |
Considerations for Disablement of HARQ in IoT NTN |
Lockheed Martin |
| R1-2300237 |
Discussion on disabling of HARQ feedback for IoT NTN |
Spreadtrum Communications |
| R1-2300268 |
Discussion on disabling of HARQ feedback for IoT NTN |
OPPO |
| R1-2300555 |
Discussion on the HARQ operation for IoT NTN |
xiaomi |
| R1-2300660 |
Discussion on remaining issues of disabling of HARQ feedback for IoT NTN |
CATT |
| R1-2300706 |
Discussion on disabling of HARQ feedback for IoT-NTN |
ZTE |
| R1-2300825 |
Disabling of HARQ feedback for IoT NTN |
NEC |
| R1-2300890 |
Discussion on disabling of HARQ feedback for IoT-NTN |
Sony |
| R1-2300922 |
Disabling of HARQ feedback for IoT NTN |
Lenovo |
| R1-2301022 |
Discussion on disabling of HARQ feedback for IoT NTN |
CMCC |
| R1-2301057 |
Disabling of HARQ for IoT NTN |
MediaTek Inc. |
| R1-2301151 |
On disabling HARQ feedback for IoT NTN |
Ericsson |
| R1-2301158 |
Disabling of HARQ feedback for IoT NTN |
InterDigital, Inc. |
| R1-2301209 |
On disabling HARQ feedback for IOT-NTN |
Mavenir |
| R1-2301285 |
Disabling of HARQ feedback for IoT NTN |
Samsung |
| R1-2301367 |
Discussion on HARQ Feedback Disabling for IoT NTN |
Apple |
| R1-2301434 |
Disabling HARQ Feedback for IoT-NTN |
Qualcomm Incorporated |
| R1-2301549 |
Views on Disabling of HARQ feedback for IoT NTN |
Sharp |
| R1-2301566 |
Disabling of HARQ feedback for NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2301623 |
Disabling of HARQ feedback for IoT NTN |
Nordic Semiconductor ASA |
| R1-2301803 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator(Lenovo) |
| R1-2301804 |
FLS#2 on disabling of HARQ feedback for IoT NTN |
Moderator(Lenovo) |
| 9.11.4 |
Improved GNSS operations for IoT NTN |
|
| R1-2300120 |
Discussion on improved GNSS operations for IoT NTN |
Huawei, HiSilicon |
| R1-2300238 |
Discussion on improved GNSS operations for IoT NTN |
Spreadtrum Communications |
| R1-2300269 |
Discussion on improved GNSS operations for IoT NTN |
OPPO |
| R1-2300556 |
Discussion on the improved GNSS operation for IoT NTN |
xiaomi |
| R1-2300661 |
Considerations on improved GNSS operations for IoT NTN |
CATT |
| R1-2300707 |
Discussion on improved GNSS operation for IoT-NTN |
ZTE |
| R1-2300766 |
On Improved GNSS Operations for IoT NTN |
NEC |
| R1-2300923 |
Improved GNSS operations for IoT NTN |
Lenovo |
| R1-2301023 |
Discussion on improved GNSS operations for IoT NTN |
CMCC |
| R1-2301058 |
Improved GNSS operations for IoT NTN |
MediaTek Inc. |
| R1-2301159 |
Improved GNSS operations for IoT NTN |
InterDigital, Inc. |
| R1-2301286 |
Improved GNSS operations for IoT NTN |
Samsung |
| R1-2301303 |
On improved GNSS operation in IoT NTN |
Ericsson Limited |
| R1-2301368 |
Discussion on improved GNSS operations for IoT NTN |
Apple |
| R1-2301435 |
Improved GNSS Operations for IoT-NTN |
Qualcomm Incorporated |
| R1-2301567 |
Enhancements for long connections in NB-IoT/eMTC over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2301624 |
Improved GNSS operations for IoT NTN |
Nordic Semiconductor ASA |
| R1-2301833 |
Feature lead summary#1 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2301834 |
Feature lead summary#2 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2302120 |
Feature lead summary#3 of AI 9.11.4 on improved GNSS operations |
Moderator (MediaTek) |
| 9.12 |
Further NR mobility enhancements |
|
| R1-2302068 |
Session notes for 9.12 (Further NR mobility enhancements) |
Ad-Hoc Chair (CMCC) |
| 9.12.1 |
L1 enhancements for inter-cell beam management |
|
| R1-2300056 |
L1 enhancements for inter-cell beam management |
FUTUREWEI |
| R1-2300128 |
L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2300145 |
FL plan on L1 enhancements for LTM at RAN1#112 |
Moderator (Fujitsu) |
| R1-2300146 |
FL summary 1 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2300188 |
L1 enhancements for inter-cell beam management |
ZTE |
| R1-2300239 |
Discussion on L1 enhancements for inter-cell beam management |
Spreadtrum Communications |
| R1-2300311 |
Discussions on Inter-cell beam management enhancement |
OPPO |
| R1-2300335 |
L1 enhancements to inter-cell beam management |
Ericsson |
| R1-2300384 |
Layer-1 Enhancements for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2300474 |
Discussion on L1 enhancements for L1L2 mobility |
vivo |
| R1-2300488 |
Discussion on L1 enhancements for inter-cell beam management |
FGI |
| R1-2300517 |
L1 enhancements for inter-cell beam management |
Lenovo |
| R1-2300536 |
Enhancements on inter-cell beam management for mobility |
LG Electronics |
| R1-2300557 |
Discussion on L1 enhancements for inter-cell beam management in LTM |
Xiaomi |
| R1-2300662 |
Further discussions on L1 enhancements for inter-cell beam management |
CATT |
| R1-2300757 |
Views on L1 enhancements for inter-cell beam management |
Fujitsu |
| R1-2300769 |
Discussion on L1 enhancements for inter-cell beam management |
NEC |
| R1-2300891 |
Discussion on L1 enhancements for inter-cell beam management |
Sony |
| R1-2300967 |
L1 Enhancements for Inter-cell Beam Management |
Intel Corporation |
| R1-2301024 |
Discussion on L1 enhancements for inter-cell beam management |
CMCC |
| R1-2301161 |
Discussion on inter-cell beam management |
Rakuten Mobile, Inc |
| R1-2301167 |
Discussion on L1 enhancements for inter-cell beam management |
Google |
| R1-2301169 |
L1 enhancements for inter-cell beam management |
InterDigital, Inc. |
| R1-2301208 |
Discussion on L1 measurement configuration for LTM |
Panasonic |
| R1-2301287 |
On L1 enhancements for inter-cell beam management |
Samsung |
| R1-2301369 |
L1 Enhancements to Inter-Cell Beam Management |
Apple |
| R1-2301436 |
L1 Enhancements for Inter-Cell Beam Management |
Qualcomm Incorporated |
| R1-2301514 |
Discussion on L1 enhancements for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2301576 |
L1 enhancements for inter-cell beam management |
MediaTek Inc. |
| R1-2302001 |
FL summary 2 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2302002 |
FL summary 3 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2302193 |
DRAFT LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
Moderator (Fujitsu), CATT |
| R1-2302194 |
LS on L1 measurement RS configuration and PDCCH ordered RACH for LTM |
RAN1, Fujitsu, CATT |
| R1-2302195 |
FL summary 4 on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| R1-2302196 |
Final FL summary on L1 enhancements for inter-cell beam management |
Moderator (Fujitsu) |
| 9.12.2 |
Timing advance management to reduce latency |
|
| R1-2300057 |
Discussion of the merits of UE based RACH-less TA acquisition for LTM |
FUTUREWEI |
| R1-2300129 |
Timing advance management to reduce latency |
Huawei, HiSilicon |
| R1-2300189 |
Enhancements on TA management to reduce latency |
ZTE |
| R1-2300240 |
Discussion on timing advance management to reduce latency |
Spreadtrum Communications |
| R1-2300312 |
Discussions on Timing Advance Management |
OPPO |
| R1-2300385 |
Timing Advance Management for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2300475 |
Discussion on TA management for L1L2 mobility |
vivo |
| R1-2300490 |
Discussion on TA management for LTM |
FGI |
| R1-2300518 |
Timing advancement management for L1L2 mobility |
Lenovo |
| R1-2300537 |
Enhancements on TA management for mobility |
LG Electronics |
| R1-2300558 |
Discussion on Timing advance management |
Xiaomi |
| R1-2300663 |
Discussion on time advance management to reduce latency |
CATT |
| R1-2300968 |
On Timing Advance Management |
Intel Corporation |
| R1-2301025 |
Discussion on timing advance management to reduce latency |
CMCC |
| R1-2301035 |
Discussion on TA management to reduce latency |
KDDI Corporation |
| R1-2301095 |
Timing advance management for L1/L2 Mobility |
Ericsson |
| R1-2301168 |
Discussion on timing advance management to reduce latency |
Google |
| R1-2301170 |
Timing advance management to reduce latency |
InterDigital, Inc. |
| R1-2301288 |
Candidate cell TA acquisition for NR L1/L2 mobility enhancement |
Samsung |
| R1-2301370 |
Timing advance management for L1/L2 Mobility |
Apple |
| R1-2301437 |
TA management to reduce latency for L1/L2 based mobility |
Qualcomm Incorporated |
| R1-2301515 |
Timing advance enhancement for inter-cell mobility |
NTT DOCOMO, INC. |
| R1-2301583 |
UL Timing management to reduce handover latency |
MediaTek Inc. |
| R1-2301893 |
Moderator summary on Timing advance management for LTM: Round 1 |
Moderator (CATT) |
| R1-2302016 |
Moderator summary on Timing advance management for LTM: Round 2 |
Moderator (CATT) |
| R1-2302075 |
Moderator summary on Timing advance management for LTM: Round 3 |
Moderator (CATT) |
| R1-2302165 |
Moderator summary on Timing advance management for LTM: Round 4 |
Moderator (CATT) |
| 9.13 |
Study on low-power wake-up signal and receiver for NR |
|
| R1-2300139 |
Impact of WUS Modulation on WUR Power Consumption |
Everactive |
| R1-2300486 |
TR 38.869 v010: Study on low-power wake up signal and receiver for NR |
Rapporteur (vivo) |
| R1-2302236 |
TR 38.869 v010: Study on low-power wake up signal and receiver for NR |
Rapporteur (vivo) |
| 9.13.1 |
Evaluation on low power WUS |
|
| R1-2300052 |
Evaluation of Low Power WUS and performance results |
FUTUREWEI |
| R1-2300100 |
Evaluations for LP-WUS |
Huawei, HiSilicon |
| R1-2300241 |
Discussion on evaluation on low power WUS |
Spreadtrum Communications |
| R1-2300273 |
Evaluation for lower power wake-up signal |
OPPO |
| R1-2300375 |
Evaluation on LP-WUS |
ZTE, Sanechips |
| R1-2300476 |
Evaluation methodologies for R18 LP-WUS/WUR |
vivo |
| R1-2300559 |
Evaluation on low power WUS |
xiaomi |
| R1-2300597 |
Discussion on evaluation on LP-WUS |
InterDigital, Inc. |
| R1-2300664 |
Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR |
CATT |
| R1-2300698 |
Low power WUS Evaluation Methodology |
Nokia, Nokia Shanghai Bell |
| R1-2300892 |
Evaluation of low power WUS |
Sony |
| R1-2300969 |
Evaluations on LP-WUS |
Intel Corporation |
| R1-2301112 |
Discussion on evaluation for LP-WUS |
LG Electronics |
| R1-2301194 |
On LP-WUS evaluation |
Nordic Semiconductor ASA |
| R1-2301289 |
Evaluation on LP-WUS/WUR |
Samsung |
| R1-2301371 |
On performance evaluation for low power wake-up signal |
Apple |
| R1-2301438 |
Evaluation methodology for LP-WUS |
Qualcomm Incorporated |
| R1-2301516 |
Discussion on evaluation methodology for low power WUS |
NTT DOCOMO, INC. |
| R1-2301558 |
Low power WUS evaluations |
Ericsson |
| R1-2301577 |
Evaluation on low power WUS |
MediaTek Inc. |
| R1-2301799 |
Evaluation methodologies and results for R18 LP-WUS/WUR |
vivo |
| R1-2302006 |
FL summary#1 of evaluation on low power WUS |
Moderator (vivo) |
| R1-2302140 |
FL summary#2 of evaluation on low power WUS |
Moderator (vivo) |
| R1-2302212 |
FL summary#3 of evaluation on low power WUS |
Moderator (vivo) |
| R1-2302251 |
FL summary#4 of evaluation on low power WUS |
Moderator (vivo) |
| 9.13.2 |
Low power WUS receiver architectures |
|
| R1-2300053 |
Low Power WUS Receiver Architectures, Considerations, and Modeling |
FUTUREWEI |
| R1-2300101 |
Discussion on architecture of LP-WUS receiver |
Huawei, HiSilicon |
| R1-2300242 |
Discussion on low power WUS receiver architectures |
Spreadtrum Communications |
| R1-2300274 |
Discussion on low power WUS receiver |
OPPO |
| R1-2300362 |
Discussion on low power wake up receiver architectures |
Panasonic |
| R1-2300376 |
LP-WUS receiver architectures |
ZTE, Sanechips |
| R1-2300477 |
Discussion on low power wake-up receiver architecture |
vivo |
| R1-2300598 |
Discussion on LP-WUS receiver architectures |
InterDigital, Inc. |
| R1-2300665 |
Low-Power WUS receiver Architectures and its performance |
CATT |
| R1-2300699 |
Low Power WUS Receiver Architectures |
Nokia, Nokia Shanghai Bell |
| R1-2300970 |
Discussion on LP-WUS receiver architecture |
Intel Corporation |
| R1-2301195 |
On LP-WUS architecture |
Nordic Semiconductor ASA |
| R1-2301290 |
Receiver architecture for LP-WUS |
Samsung |
| R1-2301372 |
On low power wake-up receiver architectures |
Apple |
| R1-2301439 |
Receiver architecture for LP-WUS |
Qualcomm Incorporated |
| R1-2301517 |
Discussion on low power WUS receiver architectures |
NTT DOCOMO, INC. |
| R1-2301559 |
Low power WUS receiver architectures |
Ericsson |
| R1-2301578 |
Low power WUS receiver architectures |
MediaTek Inc. |
| R1-2301816 |
Summary #1 on LP WUR architecture |
Moderator (Apple) |
| R1-2301817 |
Summary #2 on LP WUR architecture |
Moderator (Apple) |
| R1-2301818 |
Summary #3 on LP WUR architecture |
Moderator (Apple) |
| 9.13.3 |
L1 signal design and procedure for low power WUS |
|
| R1-2300054 |
Low Power WUS Design |
FUTUREWEI |
| R1-2300102 |
Signal design and procedure for LP-WUS |
Huawei, HiSilicon |
| R1-2300169 |
L1 signal design and procedure for low power WUS |
TCL Communication Ltd. |
| R1-2300243 |
Discussion on L1 signal design and procedure for low power WUS |
Spreadtrum Communications |
| R1-2300275 |
Design consideration on lower power wake-up signal and procedure |
OPPO |
| R1-2300363 |
Discussion on low power wake up signal design |
Panasonic |
| R1-2300377 |
LP-WUS design and related procedure |
ZTE, Sanechips |
| R1-2300478 |
Discussion on physical signal and procedure for low power WUS |
vivo |
| R1-2300560 |
Discussions on L1 signal design and procedure for low power WUS |
xiaomi |
| R1-2300599 |
Discussion on L1 signal design and procedure for LP-WUS |
InterDigital, Inc. |
| R1-2300666 |
Physical layer signals/procedures and higher layer protocol for Low-Power WUR |
CATT |
| R1-2300700 |
L1 signal design and procedures for low power WUS |
Nokia, Nokia Shanghai Bell |
| R1-2300727 |
Discussion on signal design and procedure for LP-WUS |
China Telecom |
| R1-2300795 |
L1 signal design and procedure for low-power WUS |
Sharp |
| R1-2300819 |
Discussion on L1 signal design and procedure for LP-WUS |
NEC |
| R1-2300893 |
L1 signal design and procedures for LP-WUS |
Sony |
| R1-2300971 |
Discussions on L1 signal design and procedure for LP-WUS |
Intel Corporation |
| R1-2301026 |
Discussion on L1 signal design and procedure for LP-WUS |
CMCC |
| R1-2301113 |
Discussion on L1 signal design and procedure for LP-WUS |
LG Electronics |
| R1-2301133 |
Discussion on L1 signal design and procedure for low power WUS |
EURECOM |
| R1-2301196 |
On LP-WUS signal design |
Nordic Semiconductor ASA |
| R1-2301291 |
Signal design and procedure for LP-WUS |
Samsung |
| R1-2301373 |
On the L1 signal design and procedures for low power wake-up signal |
Apple |
| R1-2301440 |
L1 signal design and procedures for LP-WUR |
Qualcomm Incorporated |
| R1-2301518 |
Discussion on L1 signal design and procedure for low power WUS |
NTT DOCOMO, INC. |
| R1-2301560 |
L1 signal design and procedure for low power WUS |
Ericsson |
| R1-2301579 |
L1 signal design and procedure for low power WUS |
MediaTek Inc. |
| R1-2301638 |
Discussion on the L1 signal design and procedure for low power WUS |
Lenovo |
| R1-2301862 |
Discussion on low power wake up signal design |
Panasonic |
| R1-2302003 |
Summary of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2302158 |
Summary#2 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| R1-2302213 |
Summary#3 of discussions on L1 signal design and procedure for low power WUS |
Moderator (Nordic Semiconductor ASA) |
| 9.14 |
Further NR coverage enhancements |
|
| R1-2302069 |
Session notes for 9.14 (Further NR coverage enhancements) |
Ad-Hoc Chair (CMCC) |
| 9.14.1 |
PRACH coverage enhancements |
|
| R1-2300089 |
Discussion on PRACH coverage enhancements |
Huawei, HiSilicon |
| R1-2300244 |
Discussion on PRACH coverage enhancements |
Spreadtrum Communications |
| R1-2300276 |
PRACH coverage enhancements |
OPPO |
| R1-2300344 |
Discussion on PRACH coverage enhancements |
ZTE |
| R1-2300479 |
Discussions on PRACH coverage enhancements |
vivo |
| R1-2300495 |
Discussion on Resource Allocation for Multiple PRACH Transmission |
FGI |
| R1-2300561 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2300667 |
PRACH coverage enhancements |
CATT |
| R1-2300728 |
Discussion on PRACH coverage enhancement |
China Telecom |
| R1-2300758 |
Discussion on PRACH coverage enhancements |
Fujitsu |
| R1-2300796 |
Discussion on PRACH coverage enhancements |
Panasonic |
| R1-2300828 |
Discussion on PRACH coverage enhancement |
NEC |
| R1-2300838 |
PRACH coverage enhancements |
TCL Communication Ltd. |
| R1-2300860 |
PRACH coverage enhancements |
Lenovo |
| R1-2300894 |
PRACH Coverage Enhancement using Multi PRACH Transmissions |
Sony |
| R1-2300904 |
Discussion on PRACH coverage enhancement |
Mavenir |
| R1-2300972 |
Discussions on PRACH coverage enhancement |
Intel Corporation |
| R1-2301027 |
Discussion on PRACH coverage enhancements |
CMCC |
| R1-2301053 |
PRACH coverage enhancements |
ETRI |
| R1-2301074 |
Discussion on PRACH repeated transmission for NR coverage enhancement |
LG Electronics |
| R1-2301171 |
Discussion on PRACH coverage enhancements |
InterDigital, Inc. |
| R1-2301185 |
Discussion on PRACH coverage enhancement |
Ericsson |
| R1-2301292 |
PRACH coverage enhancements |
Samsung |
| R1-2301374 |
Discussion on PRACH coverage enhancement |
Apple |
| R1-2301441 |
PRACH Coverage Enhancements |
Qualcomm Incorporated |
| R1-2301519 |
Discussion on PRACH coverage enhancements |
NTT DOCOMO, INC. |
| R1-2301550 |
Views on multiple PRACH transmission for coverage enhancement |
Sharp |
| R1-2301603 |
On PRACH coverage enhancements |
MediaTek Inc. |
| R1-2301654 |
PRACH coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2301770 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2301777 |
On PRACH coverage enhancements |
MediaTek Inc. |
| R1-2301848 |
FL Summary#1 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2301849 |
FL Summary#2 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2301850 |
FL Summary#3 on PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2302104 |
FL Summary#4 on PRACH coverage enhancements |
Moderator (China Telecom) |
| 9.14.2 |
Power domain enhancements |
|
| R1-2300090 |
Discussion on coverage enhancement in power domain |
Huawei, HiSilicon |
| R1-2300245 |
Discussion on power domain enhancements |
Spreadtrum Communications |
| R1-2300277 |
The study of power domain enhancements |
OPPO |
| R1-2300345 |
Discussion on power domain enhancements |
ZTE |
| R1-2300480 |
Discussions on power domain enhancements |
vivo |
| R1-2300562 |
Discussion on power domain enhancements |
xiaomi |
| R1-2300668 |
Discussion on MPR/PAR reduction enhancements |
CATT |
| R1-2300729 |
Discussion on power domain enhancements |
China Telecom |
| R1-2300759 |
Discussion on Power domain enhancements |
Fujitsu |
| R1-2300797 |
Discussion on power domain enhancements |
Panasonic |
| R1-2300861 |
Power domain enhancements |
Lenovo |
| R1-2300895 |
Considerations on tone reservation for PAPR reduction |
Sony |
| R1-2300973 |
Discussions on power domain enhancement |
Intel Corporation |
| R1-2301028 |
Discussion on power domain enhancements |
CMCC |
| R1-2301172 |
Discussion on power domain enhancements |
InterDigital, Inc. |
| R1-2301186 |
Power Domain Enhancement Schemes and Performance |
Ericsson |
| R1-2301293 |
Power domain enhancements |
Samsung |
| R1-2301375 |
Discussion on power domain coverage enhancement |
Apple |
| R1-2301442 |
Power-domain enhancements |
Qualcomm Incorporated |
| R1-2301520 |
Discussion on power domain enhancements |
NTT DOCOMO, INC. |
| R1-2301604 |
Views on power domain enhancements |
MediaTek Inc. |
| R1-2301635 |
DMRS design for power domain enhancements |
Indian Institute of Tech (H) |
| R1-2301655 |
RAN1 impacts for power domain enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2301778 |
Views on power domain enhancements |
MediaTek Inc. |
| R1-2301869 |
FL summary of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2301870 |
FL summary #2 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2301871 |
FL summary #3 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2301872 |
FL summary #4 of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2301873 |
Final FL summary of power domain enhancements (AI 9.14.2) |
Moderator (Nokia) |
| R1-2301995 |
DMRS design for power domain enhancements |
Indian Institute of Tech (H) |
| R1-2302080 |
[Draft] LS to RAN4 for results of the LLS performance evaluation of MPR/PAR reduction solutions |
Moderator (Nokia) |
| R1-2302081 |
LS to RAN4 for results of the LLS performance evaluation of MPR/PAR reduction solutions |
RAN1, Nokia |
| 9.14.3 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
|
| R1-2300091 |
Discussion on dynamic waveform switching for coverage enhancement |
Huawei, HiSilicon |
| R1-2300246 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Spreadtrum Communications |
| R1-2300278 |
Considerations on dynamic switching between DFT-S-OFDM and CP-OFDM |
OPPO |
| R1-2300346 |
Discussion on dynamic waveform switching |
ZTE |
| R1-2300481 |
Discussions on dynamic waveform switching |
vivo |
| R1-2300563 |
Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM |
xiaomi |
| R1-2300669 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
CATT |
| R1-2300730 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
China Telecom |
| R1-2300829 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NEC |
| R1-2300856 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2300862 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Lenovo |
| R1-2300864 |
Discussion on dynamic waveform switching |
Panasonic |
| R1-2300896 |
Further considerations on dynamic waveform switching for the UE UL |
Sony |
| R1-2300903 |
Discussion on solutions for NR dynamic switching between DFT-S-OFDM and CP-OFDM |
Mavenir |
| R1-2300974 |
Dynamic switching between DFT-S-OFDM and CP-OFDM waveform |
Intel Corporation |
| R1-2301029 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
CMCC |
| R1-2301054 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
ETRI |
| R1-2301075 |
Discussion on dynamic waveform switching for NR coverage enhancement |
LG Electronics |
| R1-2301086 |
Discussion on dynamic waveform switching |
DENSO CORPORATION |
| R1-2301187 |
Discussion on Dynamic UL Waveform Switching |
Ericsson |
| R1-2301294 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Samsung |
| R1-2301312 |
Discussion of dynamic switching between DFT-S-OFDM and CP-OFDM |
Transsion Holdings |
| R1-2301376 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
Apple |
| R1-2301443 |
Dynamic switching between DFT-S-OFDM and CP-OFDM |
Qualcomm Incorporated |
| R1-2301521 |
Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM |
NTT DOCOMO, INC. |
| R1-2301540 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2301541 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2301551 |
Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh |
Sharp |
| R1-2301605 |
Dynamic switching between waveforms |
MediaTek Inc. |
| R1-2301656 |
Dynamic switching between DFT-s-OFDM and CP-OFDM |
Nokia, Nokia Shanghai Bell |
| R1-2301779 |
Dynamic switching between waveforms |
MediaTek Inc. |
| R1-2302124 |
Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| R1-2302222 |
Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital, Inc.) |
| 9.15 |
NR support for UAV (Uncrewed Aerial Vehicles) |
|
| R1-2302070 |
Session notes for 9.15 (NR support for UAV (Uncrewed Aerial Vehicles) |
Ad-Hoc Chair (Huawei) |
| 9.15.1 |
UE capability and RRC signaling for UAV beamforming |
|
| R1-2300132 |
UE capability and RRC signaling for UAV beamforming |
Huawei, HiSilicon |
| R1-2300482 |
Discussion on UE capability and RRC signaling for UAV beamforming |
vivo |
| R1-2300519 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Lenovo |
| R1-2300564 |
Discussion on UE capability and RRC signaling for UAV beamforming |
xiaomi |
| R1-2300708 |
Discussion on UE capability for UAV beamforming |
ZTE |
| R1-2300713 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Nokia, Nokia Shanghai Bell |
| R1-2301295 |
Discussion on UE capability and RRC signaling for UAV beamforming |
Samsung |
| R1-2301377 |
On UE capability and RRC signaling for UAV beamforming |
Apple |
| R1-2301444 |
Discussion of UE capability and RRC signaling for UAV beamforming |
Qualcomm Incorporated |
| R1-2301522 |
Discussion on UE capability and RRC signaling for UAV beamforming |
NTT DOCOMO, INC. |
| R1-2301629 |
On UAV beamforming capabilities |
Ericsson |
| R1-2301953 |
Summary#1 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| R1-2301954 |
Summary#2 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| R1-2301955 |
Summary#3 of discussion on UAV capability and RRC signaling for UAV |
Moderator (Nokia) |
| 9.16 |
NR support for dedicated spectrum less than 5MHz for FR1 |
|
| R1-2302071 |
Session notes for 9.16 (NR support for dedicated spectrum less than 5MHz for FR1) |
Ad-hoc Chair (CMCC) |
| 9.16.1 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
|
| R1-2300059 |
Discussion on enhancements for less than 5 MHz dedicated spectrum |
FUTUREWEI |
| R1-2300115 |
Discussion on dedicated spectrum less than 5 MHz for FR1 |
Huawei, HiSilicon |
| R1-2300247 |
Discussion on enhancements to operate NR on dedicated spectrum |
Spreadtrum Communications |
| R1-2300316 |
Open issues of dedicated spectrum less than 5MHz for FR1 |
TD Tech, Chengdu TD Tech |
| R1-2300347 |
Discussion on dedicated spectrum less than 5MHz for FR1 |
ZTE |
| R1-2300483 |
Discussion on NR support for dedicated spectrum less than 5MHz |
vivo |
| R1-2300565 |
Views on enhancements to operate NR on dedicated spectrum less than 5 MHz |
xiaomi |
| R1-2300786 |
Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz |
NICT |
| R1-2300859 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
Lenovo |
| R1-2300975 |
Discussion on NR operation with less than 5MHz Bandwidth |
Intel Corporation |
| R1-2301096 |
NR support for below 5 MHz BW |
Nokia, Nokia Shanghai Bell |
| R1-2301114 |
Discussion on enhancements for dedicated spectrum less than 5 MHz |
LG Electronics |
| R1-2301154 |
NR support of spectrum less than 5MHz for FR1 |
Ericsson |
| R1-2301296 |
Enhancements to operate NR on dedicated spectrum less than 5 MHz |
Samsung |
| R1-2301378 |
On dedicated spectrum less than 5MHz for FR1 |
Apple |
| R1-2301445 |
NR support for dedicated spectrum less than 5MHz in FR1 |
Qualcomm Incorporated |
| R1-2301463 |
On enhancements to operate NR on dedicated spectrum less than 5 MHz |
KT Corp. |
| R1-2301523 |
Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz |
NTT DOCOMO, INC. |
| R1-2301610 |
On dedicated spectrum less than 5 MHz |
MediaTek Inc. |
| R1-2301784 |
On dedicated spectrum less than 5 MHz |
MediaTek Inc. |
| R1-2301975 |
Summary of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2302132 |
Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2302157 |
DRAFT LS to RAN on transmission bandwidths for NR on dedicated spectrum less than 5 MHz |
Moderator (Nokia) |
| R1-2302186 |
LS to RAN on transmission bandwidths for NR on dedicated spectrum less than 5 MHz |
RAN1, Nokia |
| R1-2302219 |
Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| 9.17 |
Other |
|
| R1-2300155 |
Proposal for Rel-18 TEI |
Ericsson |
| R1-2300257 |
TEI on the introduction of a UE capability with up to 6-layer DL MIMO |
OPPO |
| R1-2300306 |
Changing Table 5.2.2.1-2 name to 4-bit CQI Table 1 |
RadiSys |
| R1-2300484 |
Rel-18 TEI proposals |
vivo |
| R1-2300485 |
Remaining issues on Rel-18 NR Dynamic spectrum sharing |
vivo |
| R1-2300811 |
TEI proposals for Rel-18 |
ZTE |
| R1-2301060 |
[eDSS] RRC configuration and UE capability for PDCCH on CRS |
Nokia, Nokia Shanghai Bell |
| R1-2301061 |
[TEI18] Extensions to FR1 TRS configurations |
Nokia, Nokia Shanghai Bell |
| R1-2301446 |
Rel-18 RAN1 TEI proposals |
Qualcomm Incorporated |
| R1-2301524 |
Remaining issues on NR PDCCH reception in symbols with LTE CRS REs |
NTT DOCOMO, INC. |
| R1-2301572 |
Discussion on remaining issues in Rel-18 eDSS |
OPPO |
| R1-2301602 |
Potential Rel-18 TEI for PDCCH skipping with NACK aware retransmission |
MediaTek Inc. |
| R1-2301620 |
R18 TEI on BWP without CD-SSB for normal UE |
MediaTek Inc. |
| R1-2301711 |
Remaining issues on NR PDCCH reception in symbols with LTE CRS REs |
Huawei, HiSilicon |
| R1-2301718 |
Rel-18 TEI proposal on HARQ multiplexing on PUSCH |
Huawei, HiSilicon, Ericsson, China Unicom |
| R1-2301744 |
Discussion on remaining issues for Rel-18 DSS |
ZTE |
| R1-2301963 |
Summary #1 on Rel-18 TEIs |
Moderator (NTT DOCOMO) |
| R1-2302020 |
Summary #2 on Rel-18 TEIs |
Moderator (NTT DOCOMO) |
| R1-2302072 |
Session notes for 9.17 (Other - TEI18) |
Ad-hoc Chair (CMCC) |
| R1-2302103 |
Summary #3 on Rel-18 TEIs |
Moderator (NTT DOCOMO) |
| R1-2302152 |
Draft LS on SR periodicity |
Moderator (Ericsson) |
| R1-2302187 |
LS on SR periodicity |
RAN1, Ericsson |
| R1-2302188 |
Summary #4 on Rel-18 TEIs |
Moderator (NTT DOCOMO) |
| R1-2302200 |
Draft LS on 1-symbol PRS |
Moderator (ZTE) |
| R1-2302201 |
LS on 1-symbol PRS |
RAN1, ZTE |