TDoc | Title | Source |
---|---|---|
R1-2306350 | Draft Agenda of RAN1#114 meeting | RAN1 Chair |
R1-2306353 | RAN1#114 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
R1-2306354 | RAN1#114 Meeting Management | RAN1 Chair |
TDoc | Title | Source |
---|---|---|
R1-2306351 | Highlights from RAN#100 | RAN1 Chair |
TDoc | Title | Source |
---|---|---|
R1-2306352 | Report of RAN1#113 meeting | ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2306355 | Reply LS on the N6 PDU Set Identification | SA2, OPPO |
R1-2306356 | Reply LS on Authorization and Provisioning for Ranging/SL positioning service | RAN3, xiaomi |
R1-2306357 | Reply LS on SRS Configuration Request | RAN3, Huawei |
R1-2306358 | Reply LS on the requirement on low power or high accuracy positioning | SA1, Huawei |
R1-2306359 | Reply LS on 3GPP work on Energy Efficiency | SA1, Nokia |
R1-2306360 | LS on 3GPP work on Energy Efficiency | SA4, Qualcomm |
R1-2306361 | LS on required DCI signalling for advanced receiver on MU-MIMO scenario | RAN4, Qualcomm, China Telecom, HiSilicon |
R1-2306362 | LS for ATG UE features | RAN4, CMCC |
R1-2306363 | LS reply on measurement definitions for positioning with bandwidth aggregation | RAN4, Ericsson |
R1-2306364 | LS on MTTD for multi-DCI multi-TRP with two TAs | RAN4, Apple |
R1-2306365 | Reply LS on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | RAN4, Ericsson |
R1-2306366 | LS on multi-carrier enhancement | RAN4, vivo |
R1-2306367 | Reply LS on enhancements to realize increasing UE power high limit for CA and DC | RAN4, Ericsson |
R1-2306368 | LS on FR2 SCell activation enhancements | RAN4, Apple |
R1-2306369 | LS on reporting granularity for timing related positioning measurements | RAN4, Huawei |
R1-2306370 | Reply LS on report of switching periods in Rel-18 uplink Tx switching | RAN4, NTT DOCOMO |
R1-2306371 | LS on C-LBT Failure Recovery | RAN2, InterDigital |
R1-2306372 | Reply LS on PSFCH and S-SSB transmissions over non-contiguous RB sets | RAN4, OPPO, Huawei |
R1-2306373 | LS response to N6 PDU Set Identification | RAN2, Intel |
R1-2306374 | LS to SA2 on reporting positioning measurements taken in RRC_IDLE | RAN2, CATT |
R1-2306375 | LS to SA2 on sidelink positioning agreements | RAN2, Intel |
R1-2306376 | Reply LS on non-simultaneous UL and DL from different two bands during UL CA | RAN2, Nokia |
R1-2306377 | Reply LS on MAC-CE Based Indication for Cross-RRH TCI State Switch | RAN2, Nokia |
R1-2306378 | LS reply on FR2 unknown Scell activation enhancement | RAN2, Apple |
R1-2306379 | LS on new DRX cycles in rational numbers | RAN2, Qualcomm |
R1-2306380 | LS on Signalling alternatives | RAN2, Ericsson |
R1-2306381 | Further Guidelines on UE capability definitions | RAN2, Ericsson |
R1-2306382 | Reply LS on K2 indication for multi-PUSCH | RAN2, Qualcomm |
R1-2306383 | LS on LPHAP | RAN2, Huawei |
R1-2306384 | Reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 | RAN2, Qualcomm |
R1-2306385 | LS on Early TA and RACH-less | RAN2, Ericsson |
R1-2306386 | LS on L1 measurements for LTM | RAN2, Ericsson |
R1-2306387 | LS on longer CG-SDT periodicities | RAN2, Ericsson |
R1-2306388 | LS out on Data Collection Requirements and Assumptions | RAN2, vivo |
R1-2306389 | Reply LS on MCSt resource (re-)selection | RAN2, OPPO |
R1-2306456 | Discussion on RAN2 LS of Data Collection Requirements and Assumptions | Ericsson |
R1-2306471 | Discussion on the Impact of SRS Imbalance | InterDigital, Inc. |
R1-2306481 | Discussion on multicast reception in RRC_INACTIVE | Huawei, HiSilicon, CBN |
R1-2306488 | Further discussion on the reply of soft-satellite switching | Huawei, HiSilicon |
R1-2306489 | Further discussion on the reply of question 3 in the LS for RACH-less handover | Huawei, HiSilicon |
R1-2306502 | Discussion on LPHAP for the parameters for area-specific SRS configuration | Huawei, HiSilicon |
R1-2306541 | Discussion on the UE SRS IL imbalance issue | Huawei, HiSilicon, LG U+ |
R1-2306561 | Discussion on LS on longer CG-SDT periodicities | ZTE |
R1-2306562 | Draft Reply LS on longer CG-SDT periodicities | ZTE |
R1-2306620 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | ZTE |
R1-2306621 | Draft reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario | ZTE |
R1-2306622 | Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario | ZTE |
R1-2306699 | Discussion on LS on UE features for NR ATG | ZTE |
R1-2306700 | Draft Reply LS to RAN4 on UE features for NR ATG | ZTE |
R1-2306705 | Discussions on RAN2 LS on unchanged PCI | vivo |
R1-2306706 | Discussions on RAN2 LS on RACH-less Handover | vivo |
R1-2306707 | Discussions on RAN2 LS on longer CG-SDT periodicities | vivo |
R1-2306708 | Discussions on RAN4 LS on UE features for NR ATG | vivo |
R1-2306709 | Draft reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs | vivo |
R1-2306710 | Discussion on collision handling between paging occasions and CG SDT for HD-FDD UEs | vivo |
R1-2306711 | Discussion on required DCI signalling for advanced receiver on MU-MIMO scenario | vivo |
R1-2306712 | Discussion the UE SRS IL imbalance issue | vivo |
R1-2306713 | Draft reply LS on LPHAP | vivo |
R1-2306714 | Discussion on LS on early TA and rach-less | vivo |
R1-2306715 | Draft reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 | vivo |
R1-2306716 | Discussion on RAN2 LS on multicast reception in RRC_INACTIVE | vivo |
R1-2306717 | Draft reply LS on data collection requirements and assumptions | vivo |
R1-2306718 | Draft reply LS on K2 indication for multi-PUSCH | vivo |
R1-2306801 | Discussion on RAN2 LS on Data Collection Requirements and Assumptions | ZTE |
R1-2306824 | Discussion on LS for CG-PUSCH periodicity for SDT operation | Intel Corporation |
R1-2306859 | Draft Reply LS on measurement definitions for positioning with bandwidth aggregation | ZTE |
R1-2306860 | Draft Reply LS on LPHAP | ZTE |
R1-2306861 | Discussion on SRS antenna switching for TDD-FDD band combination | ZTE |
R1-2306877 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | Nokia, Nokia Shanghai Bell |
R1-2306883 | Draft reply LS on Data Collection Requirements and Assumptions | Spreadtrum Communications |
R1-2306940 | Draft reply LS on L1 measurements for LTM | Lenovo |
R1-2306966 | Discussion on DCI signalling for advanced receiver on MU-MIMO scenario | |
R1-2306967 | Discussion on multicast reception in RRC_INACTIVE | ZTE |
R1-2306968 | [Draft] Reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 | ZTE |
R1-2307000 | Draft reply LS on K2 indication for multi-PUSCH | ZTE, Sanechips |
R1-2307021 | Further discussion on RAN2 LS reply on unchanged PCI | CATT |
R1-2307022 | Draft reply LS on L1 measurements for LTM | CATT |
R1-2307023 | Discussion on reply LS to RAN2 on data collection for AI/ML | CATT |
R1-2307024 | Draft reply LS on LPHAP | CATT |
R1-2307108 | Discussion on reply LS on paging overlapping with CG-SDT for HD-FDD RedCap UE | ZTE, Sanechips |
R1-2307109 | Draft reply LS on paging and CG-SDT conflicting issue for HD-FDD RedCap UE | ZTE, Sanechips |
R1-2307132 | Discussion on reply LS on longer CG-SDT periodicities | NEC |
R1-2307168 | Discussion on RAN2 LS on unchanged PCI | CMCC |
R1-2307169 | Discussion on LS on multicast reception in RRC_INACTIVE | CMCC |
R1-2307170 | Discussion on RAN2 LS on data collection | CMCC |
R1-2307171 | Discussion on RAN4 LS on UE features for NR ATG | CMCC |
R1-2307172 | Draft reply LS on UE features for NR ATG | CMCC |
R1-2307173 | Discussion on RAN2 LS on LPHAP | CMCC |
R1-2307232 | Discussion on RAN4 LS on required DCI signaling for advanced receiver on MU-MIMO | Ericsson |
R1-2307244 | Draft reply LS on Data Collection Requirements and Assumptions | Nokia, Nokia Shanghai Bell |
R1-2307249 | On soft satellite switch with unchanged PCI | Nokia, Nokia Shanghai Bell |
R1-2307254 | Discussion on multicast reception in RRC_INACTIVE | Apple |
R1-2307255 | Draft Reply LS on Data Collection Requirements and Assumptions | Apple |
R1-2307256 | Discussion on RAN2 LS on RACH-less Handover | Apple |
R1-2307257 | Draft Reply LS on RACH-less Handover | Apple |
R1-2307329 | Discussion on LS reply from RAN2 on K2 indication for multi-PUSCH scheduling | Ericsson |
R1-2307421 | Discussion on multicast reception in RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
R1-2307437 | Discussion and draft LS reply on K2 indication for multi-PUSCH scheduling | NTT DOCOMO, INC. |
R1-2307438 | Discussion on LS from RAN2 on Rel-18 AI/ML for air interface | NTT DOCOMO, INC. |
R1-2307439 | Discussion on reply LS on LPHAP | NTT DOCOMO, INC. |
R1-2307520 | Further discussion on SRS insertion loss issue | OPPO |
R1-2307521 | Discussion on LS on required DCI signalling for advanced receiver on MU-MIMO scenario | OPPO |
R1-2307529 | Discussion on PSFCH and S-SSB transmissions over non-contiguous RB sets | OPPO |
R1-2307530 | Draft reply LS on PSFCH and S-SSB transmissions over non-contiguous RB sets | OPPO |
R1-2307547 | Discussion RAN2 LS on unchanged PCI | OPPO |
R1-2307548 | Discussion RAN2 LS on RACH-less Handover | OPPO |
R1-2307570 | Discussion on RAN2 LS on Data Collection Requirements and Assumptions | OPPO |
R1-2307575 | Discussion on RAN2 LS for new rational DRX cycle | OPPO |
R1-2307613 | Discussion and draft reply LS on new DRX cycles in rational numbers | Nokia, Nokia Shanghai Bell |
R1-2307617 | Discussion on RAN4 LS of advanced receiver for MU-MIMO | China Telecom |
R1-2307635 | Discussion on RAN4 LS on the UE SRS IL imbalance issue | Samsung |
R1-2307636 | Discussion on RAN4 LS on required DCI signalling for advanced receiver on MU-MIMO scenario | Samsung |
R1-2307637 | Discussion on reply LS on RACH-less handover | Samsung |
R1-2307638 | Draft reply LS on LPHAP | Samsung |
R1-2307639 | Draft reply LS on introduction of one new RRC parameter and one new UE capability for Rel-17 | Samsung |
R1-2307640 | Discussion on introduction of one new RRC parameter and one new UE capability for Rel-17 | Samsung |
R1-2307641 | Draft reply LS on UE features for NR ATG | Samsung |
R1-2307642 | Discussion on RAN2's LS for data collection requirements and assumptions | Samsung |
R1-2307643 | Draft reply LS on L1 measurements for LTM | Samsung |
R1-2307644 | Discussion on reply LS on K2 indication for multi-PUSCH | Samsung |
R1-2307775 | Discussion on RAN2 LS on RACH-less handover | Ericsson |
R1-2307787 | Draft Reply LS on K2 indication for multi-PUSCH | LG Electronics |
R1-2307788 | Discussion on RAN2 LS on multicast reception in RRC_INACTIVE | LG Electronics |
R1-2307842 | Resolution for RAN4 LS on FDD+TDD SRS Antenna Switching | Ericsson |
R1-2307894 | Discussion on the CSS for multicast MTCH in RRC_INACTIVE | Qualcomm Incorporated |
R1-2307895 | Draft reply LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 | Qualcomm Incorporated |
R1-2307896 | Discussion for LS reply to RAN2 on Data Collection Requirements and Assumptions | Qualcomm Incorporated |
R1-2307897 | Draft LS reply to RAN4 on power imbalance for SRS | Qualcomm Incorporated |
R1-2308027 | Draft reply LS on L1 measurements for LTM | Ericsson |
R1-2308034 | UE SRS IL imbalance | MediaTek Inc. |
R1-2308086 | Discussion on RAN2 LS on multicast reception in RRC_INACTIVE | MediaTek Inc. |
R1-2308087 | DCI signalling for advanced receiver on MU-MIMO scenario | Nokia, Nokia Shanghai Bell |
R1-2308125 | On LS on longer CG-SDT periodicities | Ericsson |
R1-2308129 | Discussion on RAN4 LS on the UE SRS imbalance issue | Ericsson |
R1-2308136 | Draft LS reply on LPHAP for the parameters for area-specific SRS configuration | Huawei, HiSilicon |
R1-2308137 | Discussion on switching time for DL PRS or UL SRS frequency hopping for RedCap UEs | Huawei, HiSilicon |
R1-2308138 | Discussion on measurement definitions for positioning with bandwidth aggregation | Huawei, HiSilicon |
R1-2308140 | Discussion on the RAN2 reply LS on K2 indication for multi-PUSCH | Huawei, HiSilicon |
R1-2308143 | Discussion on SRS antenna switching for TDD-FDD band combinations | Huawei, HiSilicon |
R1-2308144 | Draft reply to RAN 4 LS on the UE SRS IL imbalance issue | Huawei, HiSilicon |
R1-2308147 | Discussion on Reply LS on MCSt resource (re-)selection | Huawei, HiSilicon |
R1-2308153 | Discussion on LS reply to RAN2 on data collection for AI/ML | Huawei, HiSilicon |
R1-2308154 | Discussion on LS on required DCI signaling for advanced receiver in MU-MIMO scenario | Huawei, HiSilicon |
R1-2308155 | Draft reply LS on longer CG-SDT periodicities | Huawei, HiSilicon |
R1-2308164 | Discussion on LS to RAN1 on LPHAP | Ericsson |
R1-2308165 | Draft reply LS on LPHAP | Ericsson |
R1-2308183 | Draft Reply LS on FDD+TDD SRS Antenna Switching | Ericsson |
R1-2308194 | Discussion on the RAN2 LS on L1 measurement for LTM | Huawei, HiSilicon |
R1-2308195 | Discussion on LS on the new DRX cycles in rational numbers | Huawei, HiSilicon |
R1-2308196 | Discussion on the reply to LS for ATG UE features | Huawei, HiSilicon |
R1-2308421 | LS on the PCmax requirement for STxMP in FR2 | RAN4, Qualcomm |
R1-2308453 | FL summary on multicast reception in RRC_INACTIVE | Moderator (Apple) |
R1-2308458 | FL summary on UE SRS IL imbalance issue | Moderator (Huawei) |
R1-2308459 | Draft reply LS on the UE SRS IL imbalance issue | Moderator (Huawei) |
R1-2308466 | Draft reply LS on UE features for NR ATG | Moderator (CMCC) |
R1-2308467 | FL summary on RAN4 LS on UE features of NR ATG | Moderator (CMCC) |
R1-2308491 | FL summary #1 of discussion of LS on required DCI signalling for advanced receiver on MU-MIMO scenario | Moderator (Qualcomm) |
R1-2308494 | Summary on SRS antenna switching for TDD-FDD band combinations | Moderator (Huawei) |
R1-2308531 | Reply LS on UE features for NR ATG | RAN1, CMCC |
R1-2308582 | Reply LS on SRS antenna switching for TDD-FDD band combinations | RAN1, Huawei |
R1-2308597 | Draft reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario | Qualcomm, China Telecom, Huawei |
R1-2308598 | Reply LS on required DCI signalling for advanced receiver on MU-MIMO scenario | RAN1, Qualcomm, China Telecom, Huawei |
R1-2308611 | FL summary#2 on multicast reception in RRC_INACTIVE | Moderator (Apple) |
R1-2308612 | Reply LS on multicast reception in RRC_INACTIVE | RAN1, Apple |
R1-2308650 | Summary#2 on SRS antenna switching for TDD-FDD band combinations | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2308551 | Session notes for 6 (E-UTRA Maintenance) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2308198 | Correction on SRS identity for additional SRS symbols | Huawei, HiSilicon |
R1-2308583 | Correction on SRS identity for additional SRS symbols | Huawei, HiSilicon |
R1-2308584 | Correction on SRS identity for additional SRS symbols | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R1-2308179 | Draft CR on correction of timing relationship for IoT NTN in 36.213 | Nokia, Nokia Shanghai Bell |
R1-2308594 | Session Notes of AI 6.2 (Maintenance on E-UTRA Release 17) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306482 | Draft CR on Type-1 HARQ-ACK codebook for repetition | Huawei, HiSilicon |
R1-2306483 | Draft CR on Type-1 HARQ-ACK codebook for repetition | Huawei, HiSilicon |
R1-2306719 | Draft Rel-16 CR on PUSCH selection rule for UCI multiplexing | vivo |
R1-2306720 | Draft Rel-17 CR on PUSCH selection rule for UCI multiplexing | vivo |
R1-2306969 | Draft CR on TDRA table determination | ZTE |
R1-2306970 | Draft CR on TDRA table determination | ZTE |
R1-2306971 | Draft CR on Type 1 HARQ-ACK codebook for PDSCH repetition | ZTE |
R1-2307025 | Correction on O_ACK determination for Type-2 HARQ-ACK codebook | CATT |
R1-2307026 | Correction on O_ACK determination for Type-2 HARQ-ACK codebook | CATT |
R1-2307027 | Correction on PUCCH resource determination for DCI indicating SCell dormancy | CATT |
R1-2307028 | Correction on the reference clauses for transmission limitation | CATT |
R1-2307029 | Correction on the reference clauses for transmission limitation | CATT |
R1-2307030 | Correction on the HARQ-ACK mapping for CBG based transmission | CATT |
R1-2307031 | Correction on the HARQ-ACK mapping for CBG based transmission | CATT |
R1-2307032 | Clarification on the first SPS PDSCH associated with activation DCI | CATT |
R1-2307033 | Clarification on the first SPS PDSCH associated with activation DCI | CATT |
R1-2307327 | Discussion on DCI 2_0 fields for operation with shared spectrum channel access | Ericsson, LG Electronics |
R1-2307328 | Draft CR on DCI 2_0 fields for operation with shared spectrum channel access | Ericsson, LG Electronics |
R1-2307440 | Draft CR on UL DAI for multi-PUSCH scheduling (Rel-16) | NTT DOCOMO, INC. |
R1-2307441 | Draft CR on UL DAI for multi-PUSCH scheduling (Rel-17) | NTT DOCOMO, INC. |
R1-2307442 | Draft CR on SL NACK report to gNB in mode 1 (Rel-16) | NTT DOCOMO, INC. |
R1-2307443 | Draft CR on SL NACK report to gNB in mode 1 (Rel-17) | NTT DOCOMO, INC. |
R1-2307645 | Correction on UE capability parameter for multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook | Samsung |
R1-2307646 | Draft CR on logical slot definition in TS 38.214 | Samsung |
R1-2307647 | Draft CR on logical slot definition in TS 38.214 | Samsung |
R1-2307733 | Discussion on A/SP-CSI reported in PUSCH repetition Type A | ZTE |
R1-2307734 | Draft CR on A/SP-CSI reported in PUSCH repetition Type A in TS 38.214 | ZTE |
R1-2307772 | Correction on CBGTI indication bitwidth for DCI format 1_1 | Nokia, Nokia Shanghai Bell |
R1-2307773 | Corrections on CBG based PDSCH operation | Nokia, Nokia Shanghai Bell |
R1-2307898 | Clarify several ambiguities with type 2 CG-PUSCH | Qualcomm Incorporated |
R1-2307899 | Correction on RRC parameter name for SRS carrier switching | Qualcomm Incorporated |
R1-2307900 | On impact of SRS antenna swithcing across bands | Qualcomm Incorporated |
R1-2307901 | Clarification on A-CSI-RS triggering offset | Qualcomm Incorporated |
R1-2307902 | Clarify number of CDM groups without data for DMRS | Qualcomm Incorporated |
R1-2307903 | On additional restrictions for (2, 2) span-based PDCCH monitoring | Qualcomm Incorporated |
R1-2307985 | Power scaling of SCell PRACH for UL CA | Ericsson |
R1-2307986 | Draft CR to 38.213 on correction to SCell PRACH power scaling for UL CA | Ericsson |
R1-2308029 | Draft CR on LBRM TBS determination | ZTE |
R1-2308088 | Clarification to multi-CSI-PUCCH-ResourceList | Nokia, Nokia Shanghai Bell |
R1-2308148 | Discussion on collision between NR PDSCH DMRS and LTE-CRS | Huawei, HiSilicon |
R1-2308149 | Correction on collision between NR PDSCH DMRS and LTE-CRS | Huawei, HiSilicon |
R1-2308156 | Correction on Type-2 HARQ-ACK codebook | Huawei, HiSilicon |
R1-2308157 | Draft CR on selection of CSI reports in a PUCCH | Huawei, HiSilicon |
R1-2308180 | Aperiodic Triggering Support for SRS Carrier Switching | Ericsson, T-Mobile USA |
R1-2308181 | Correction for SRS Carrier Switching DCI formats and Power Control | Ericsson |
R1-2308182 | Correction for SRS-CarrierSwitching triggering order for DCI formats 1_1 and 1_2 | Ericsson |
R1-2308212 | Correction on UE capability parameter for multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook | Samsung |
R1-2308415 | Summary of A/SP-CSI reported in PUSCH repetition Type A | Moderator (ZTE) |
R1-2308454 | Correction on PUCCH resource determination for DCI indicating SCell dormancy | Moderator (CATT) |
R1-2308455 | Correction on the HARQ-ACK mapping for CBG based transmission | Moderator (CATT) |
R1-2308456 | Correction on the HARQ-ACK mapping for CBG based transmission | Moderator (CATT) |
R1-2308460 | Summary of clarification on the first SPS PDSCH | Moderator (CATT) |
R1-2308461 | Summary of PUCCH resource determination for DCI indicating SCell dormancy | Moderator (CATT) |
R1-2308462 | Summary of HARQ-ACK mapping for CBG | Moderator (CATT) |
R1-2308463 | Summary of O_ACK determination for Type-2 HARQ-ACK codebook | Moderator (CATT) |
R1-2308474 | FL summary of discussion on Type 1 HARQ-ACK codebook for PDSCH repetition | Moderator (ZTE ) |
R1-2308475 | FL summary of discussion on LBRM TBS determination | Moderator (ZTE ) |
R1-2308481 | Summary of offline discussion on the correction on UE capability parameter for multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook | Moderator (Samsung) |
R1-2308488 | Correction on UE capability parameter for multiple DCIs per MO per CC for the Type-2 HARQ-ACK codebook | Samsung |
R1-2308492 | FL summary #1 of clarifying number of CDM groups without data for DMRS | Moderator (Qualcomm) |
R1-2308493 | FL summary #1 of clarifying several ambiguities with type 2 CG-PUSCH | Moderator (Qualcomm) |
R1-2308495 | Summary on selection of CSI reports in a PUCCH | Moderator (Huawei) |
R1-2308500 | Summary for discussion of CR on UL DAI for multi-PUSCH scheduling | Moderator (NTT DOCOMO, INC.) |
R1-2308501 | Summary for discussion of CR on SL NACK report to gNB in mode 1 | Moderator (NTT DOCOMO, INC.) |
R1-2308530 | Discussion summary on Clarification to Power scaling of SCell PRACH for UL CA | Moderator (Ericsson) |
R1-2308532 | Summary of discussion on PUSCH selection rule for UCI multiplexing | Moderator (vivo) |
R1-2308554 | Offline summary of discussion on A-CSI-RS triggering offset | Moderator (Qualcomm) |
R1-2308557 | Discussion summary of NR Rel-15/16 maintenance for aperiodic triggering support for SRS carrier switching | Moderator (Ericsson) |
R1-2308562 | Summary of discussions on collision between NR PDSCH DMRS and LTE-CRS | Moderator (Huawei) |
R1-2308569 | FL summary #2 of clarifying several ambiguities with type 2 CG-PUSCH | Moderator (Qualcomm) |
R1-2308573 | Correction on Type-2 HARQ-ACK codebook | Huawei, HiSilicon |
R1-2308606 | Discussion summary#2 of NR Rel-15/16 maintenance for aperiodic triggering support for SRS carrier switching | Moderator (Ericsson) |
R1-2308634 | Correction on Type-2 HARQ-ACK codebook | Huawei, HiSilicon |
R1-2308640 | Correction on DCI 2_0 fields for operation with shared spectrum channel access | Ericsson, LG Electronics |
R1-2308641 | Correction on DCI 2_0 fields for operation with shared spectrum channel access | Ericsson, LG Electronics |
R1-2308652 | Correction on PUCCH resource determination for DCI indicating SCell dormancy | Moderator (CATT) |
R1-2308656 | FL summary of discussion on Type-1 HARQ-ACK codebook for SPS PDSCH with repetition | Moderator (Huawei) |
R1-2308684 | Rel-16 editorial corrections for TS 38.214 | Nokia |
R1-2308685 | Rel-16 editorial corrections for TS 38.214 (mirrored to Rel-17) | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2306551 | Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | Huawei, HiSilicon |
R1-2306576 | Correction on SSB configuration for CG-SDT in TS 38.213 | ZTE |
R1-2306604 | Correction to common MBS frequency resource | TD Tech, Chengdu TD Tech |
R1-2306623 | Draft CR on aperiodic SRS triggering for antenna switching in TS 38.214 | ZTE |
R1-2306721 | Correction on timing of first Msg3 repetition in NTN | vivo |
R1-2306722 | Remaining issues for Rel-17 RedCap | vivo |
R1-2306723 | Correction on simultaneous reception of SDT and other channels in TS 38.202 | vivo |
R1-2306724 | Draft CR on HARQ-ACK codebook generation with maxNrofCodeWordsScheduledByDCI configured for both unicast and multicast | vivo |
R1-2306725 | Draft CR on K1 timing | vivo |
R1-2306726 | Draft CR on referred PUCCH resources for multiplexing HARQ-ACK | vivo |
R1-2306727 | Draft CR on intra-UE multiplexing for MBS | vivo |
R1-2306728 | Discussion on overlapping among NACK-only, SR and other PUCCH/PUSCH | vivo |
R1-2306729 | Draft CR on multiplexing NACK-only, CSI and SR in a PUCCH | vivo |
R1-2306730 | Discussion on DCI field interpretation for multi-PXSCH scheduling during BWP switching in FR2-2 | vivo |
R1-2306731 | Correction for enhanced Type-3 codebook | vivo |
R1-2306884 | Draft CR on CORESET(s) configured for MBS | Spreadtrum Communications |
R1-2306899 | Discussion on RRC parameters for PUCCH repetition | vivo |
R1-2306972 | Draft CR on applicable PDSCH TDRA for broadcast reception in Scell | ZTE |
R1-2306973 | Draft CR on Frequency domain resource assignment field of DCI format 4-2 | ZTE, CBN |
R1-2306974 | Draft CR on HARQ-ACK reporting mode determination | ZTE, CBN |
R1-2306975 | Draft CR on HARQ-ACK codebook generation | ZTE, CBN |
R1-2306976 | Draft CR on intra-UE multiplexing for multicast | ZTE, CBN |
R1-2306977 | Draft CR on PUCCH resource for multicast | ZTE |
R1-2306978 | Draft CR on PUCCH slot timing for multicast | ZTE |
R1-2306979 | Draft CR on the k1 slot timing for DCI format 1_0 | ZTE |
R1-2306980 | Draft CR on the SPS PDSCH repetition for MBS | ZTE |
R1-2307001 | Maintenance of Rel-17 RedCap | NEC |
R1-2307020 | On duplicated use of ‘SFN’ in Rel-17 specification | LG Electronics |
R1-2307034 | Discussion on UL channel validation in BWP with NCD-SSB in TDD | CATT |
R1-2307035 | Clarification of enhanced Type-3 HARQ-ACK codebook | CATT |
R1-2307036 | Correction on RRC parameters for HARQ-ACK codebook and PUCCH cell switching | CATT |
R1-2307037 | Correction on PUCCH power control parameter determination | CATT |
R1-2307038 | Correction to power Control parameters for unified TCI framework | CATT |
R1-2307039 | Draft CR on dci-enabler HARQ-ACK for SPS PDSCH | CATT, CBN |
R1-2307040 | Draft CR on HARQ-ACK for multicast SPS PDSCH and for unicast SPS PDSCH multiplexed on the same PUCCH with same priority | CATT, CBN |
R1-2307041 | Draft CR on PDCCH validation for multicast DL SPS | CATT, CBN |
R1-2307042 | Discussion on restriction for a slot timing value indicated by DCI format 1_0 when multicast is configured | CATT, CBN |
R1-2307043 | Draft CR on restriction for a slot timing value indicated by DCI format 1_0 when multicast is configured | CATT, CBN |
R1-2307044 | Discussion on HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast | CATT, CBN |
R1-2307045 | Draft CR on HARQ-ACK codebook generation with both of maxNrofCodeWordsScheduledByDCI for unicast and multicast | CATT, CBN |
R1-2307046 | Draft CR on xOverhead for broadcast TBS determination | CATT, CBN |
R1-2307047 | Draft CR on DL PRS priority determination with Priority indicator field in DCI format 4_2 | CATT, CBN |
R1-2307048 | Discussion on determination of multicast HARQ-ACK codebook reporting on PUSCH | CATT, CBN |
R1-2307049 | Draft CR on determination of multicast HARQ-ACK codebook reporting on PUSCH | CATT, CBN |
R1-2307050 | Correction on PUCCH cell switching | CATT |
R1-2307051 | Correction on HARQ-ACK codebook retransmission when SPS deferral is configured | CATT |
R1-2307130 | Draft CR on RI restriction description for NCJT in TS38.214 | NEC |
R1-2307131 | Draft CR on rank combination value mapping for NCJT in 38.212 | NEC |
R1-2307148 | Correction on RRC parameters for providing an inapplicable value | Fujitsu |
R1-2307174 | Draft CR on PDCCH validation for multicast SPS | CMCC |
R1-2307258 | Maintenance issue on R17 PDCCH monitoring adaptation for UE | Apple |
R1-2307259 | Draft CR on PUSCH repetition type B with DMRS bundling | Apple |
R1-2307343 | Corrections on simultaneous reception during SDT procedure | xiaomi |
R1-2307344 | Discussion on RedCap SDT operation | xiaomi |
R1-2307345 | Corrections on the calculation of the number of coded modulation symbols for UCI multiplexing on TBoMS | xiaomi |
R1-2307346 | Correction on the last symbol of the PDCCH reception in Multi-TRP PDCCH repetition | Xiaomi, Samsung, Qualcomm |
R1-2307416 | Maintenance Issues for Rel-17 NR RedCap | Nokia, Nokia Shanghai Bell |
R1-2307423 | Corrections on RRC parameter names for feMIMO in TS38.213 | Sharp |
R1-2307424 | Corrections on RRC parameter names for feMIMO in TS38.214 | Sharp |
R1-2307425 | Corrections on parameter names for IIoT & URLLC in TS38.213 | Sharp |
R1-2307444 | Discussion on the interpretation of the number of scheduled PUSCH during DCI-based BWP switching | NTT DOCOMO, INC. |
R1-2307445 | Draft CR on the interpretation of the number of scheduled PUSCH during DCI-based BWP switching (Rel-16) | NTT DOCOMO, INC. |
R1-2307446 | Draft CR on the interpretation of the number of scheduled PUSCH during DCI-based BWP switching (Rel-17) | NTT DOCOMO, INC. |
R1-2307447 | Discussion on NDI/RV for the scheduled PUSCHs when BWP switching is indicated | NTT DOCOMO, INC. |
R1-2307448 | Draft CR on NDI/RV for the scheduled PUSCHs when BWP switching is indicated (Rel-16) | NTT DOCOMO, INC. |
R1-2307449 | Draft CR on NDI/RV for the scheduled PUSCHs when BWP switching is indicated (Rel-17) | NTT DOCOMO, INC. |
R1-2307450 | Draft CR on correction of RRC parameters of p0 for PUCCH/SRS in Rel-17 unified TCI framework | NTT DOCOMO, INC. |
R1-2307451 | Discussion on remaining issues for RedCap | NTT DOCOMO, INC. |
R1-2307452 | Discussion on NCJT CMR restriction | NTT DOCOMO, INC. |
R1-2307453 | Draft CR on processing time for MBS PDSCH without feedback | NTT DOCOMO, INC. |
R1-2307454 | Discussion on the interpretation of the number of scheduled PDSCH during DCI-based BWP switching | NTT DOCOMO, INC. |
R1-2307455 | Draft CR on the interpretation of the number of scheduled PDSCH during DCI-based BWP switching | NTT DOCOMO, INC. |
R1-2307456 | Discussion on NDI/RV for the scheduled PDSCHs when BWP switching is indicated | NTT DOCOMO, INC. |
R1-2307457 | Draft CR on NDI/RV for the scheduled PDSCHs when BWP switching is indicated | NTT DOCOMO, INC. |
R1-2307648 | Correction on higher layer parameter for AP CSI multiplexing on PUSCH | Samsung |
R1-2307649 | Correction on higher layer parameter for SP CSI multiplexing on PUSCH | Samsung |
R1-2307650 | Correction on SP CSI multiplexing on PUSCH after DCI activation | Samsung |
R1-2307651 | Discussion on higher layer parameter for AP CSI multiplexing on PUSCH | Samsung |
R1-2307652 | Discussion on higher layer parameter for SP CSI multiplexing on PUSCH | Samsung |
R1-2307653 | Discussion on SP CSI multiplexing on PUSCH after DCI activation | Samsung |
R1-2307654 | Correction on SFN configuration for CSI-RS reception using default beam | Samsung |
R1-2307655 | Discussion on DCI interpretation for multi-PxSCH scheduling and BWP switching | Samsung |
R1-2307656 | Correction on overlapping of multicast PDSCH and unicast PDSCH | Samsung |
R1-2307657 | Correction on timeline requirements for simultaneous PUCCH and PUSCH transmission of different priorities | Samsung |
R1-2307789 | Draft CR on multicast HARQ-ACK | LG Electronics |
R1-2307790 | Draft CR on sps-ConfigDeactivationStateList | LG Electronics |
R1-2307873 | UE hehavior for PDCCH monitoring adaptation and BWP switching indicated in the same DCI | Xiaomi EV Technology |
R1-2307888 | Correction on Rel-17 PDCCH monitoring adaptation | ZTE, Sanechips, CMCC |
R1-2307904 | Draft CR on PDCCH monitoring of MBS broadcast MCCH/MTCH | Qualcomm Incorporated |
R1-2307905 | Draft CR on SSSG switching when monitoring multicast PDCCH in Type3 CSS | Qualcomm Incorporated |
R1-2307906 | Discussion on maximum number of RxTxTEGs for the same DL PRS for Rel-17 Positioning | Qualcomm Incorporated |
R1-2308030 | Discussion on Type 1 HARQ-ACK Codebook Generation for Rel-17 URLLC | ZTE |
R1-2308031 | Draft CR on Type 1 HARQ-ACK Codebook Generation for Rel-17 URLLC | ZTE |
R1-2308032 | Correction on the new RRC parameter introduced for Type 1 HARQ-ACK codebook | ZTE |
R1-2308035 | Draft CR for 38.213 about Type0-PDCCH monitoring on non-zero common search space | MediaTek Inc. |
R1-2308036 | Type0-PDCCH monitoring on non-zero common search space | MediaTek Inc. |
R1-2308037 | Draft CR for 38.213 on UL resource validation with SSB | MediaTek Inc. |
R1-2308038 | On UL resource validation with SSB | MediaTek Inc. |
R1-2308044 | Draft CR Koffset for A-SRS for R17 NR NTN | MediaTek Inc. |
R1-2308045 | K_offset for A-periodic SRS in Rel-17 NR NTN | MediaTek Inc. |
R1-2308046 | Draft CR on the UE-specific K_offset update for PUCCH with HARQ Ack information for DL SPS | MediaTek Inc. |
R1-2308047 | K-offset for HARQ-ACK information for SPS PDSCH reception in Rel-17 NR-NTN | MediaTek Inc. |
R1-2308048 | Draft CR on K-offset for HARQ-ACK information for HARQ codebook in Rel-17 NR-NTN | MediaTek Inc. |
R1-2308049 | K-offset for HARQ-ACK information for HARQ codebook in Rel-17 NR-NTN | MediaTek Inc. |
R1-2308085 | Correction on PUCCH resource determination for NACK-only mode 1 with one bit HARQ-ACK | MediaTek Inc. |
R1-2308089 | Correction to CORESET0 selection for new BWs of bands n79 and n104 | Nokia, Nokia Shanghai Bell |
R1-2308126 | Maintenance issues for Rel-17 NR RedCap | Ericsson |
R1-2308127 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
R1-2308128 | Alignment of PDCCH monitoring adaptation behaviour and BWP switching | Nokia, Nokia Shanghai Bell |
R1-2308132 | Draft CR on monitoring PDCCH occasions for MBS broadcast | Huawei, HiSilicon, CBN |
R1-2308133 | Draft CR on PUCCH resources for multicast HARQ-ACK | Huawei, HiSilicon, CBN |
R1-2308134 | Draft CR on HARQ-ACK codebook for maxNrofCodeWords | Huawei, HiSilicon, CBN |
R1-2308135 | Draft CR on K1 timing for DCI format 1_0 | Huawei, HiSilicon, CBN, CMCC |
R1-2308139 | Discussion on the BWP switching with CBG-based PUSCH transmission in FR2-2 | Huawei, HiSilicon |
R1-2308142 | Discussion on information transmitted on PBCH payload of NCD-SSB | Huawei, HiSilicon |
R1-2308146 | Discussion on PDCCH monitoring adaptation | Huawei, HiSilicon |
R1-2308150 | Draft CR on UE receiving both unicast and MBS broadcast | Huawei, HiSilicon, CMCC, CBN |
R1-2308151 | Discussion on PDCCH monitoring during PDCCH skipping duration | Huawei, HiSilicon |
R1-2308152 | Draft CR on the definition for CFR in TS 38.211 | Huawei, HiSilicon, CBN |
R1-2308162 | Draft CR on k1 timing for DCI format 4-1 | Huawei, HiSilicon, CBN, CMCC |
R1-2308163 | Draft CR on PDCCH validation for multicast SPS | Huawei, HiSilicon, CBN |
R1-2308174 | Draft CR on HARQ codebook generation with different parameter values for maxNrofCodeWordsScheduledByDCI in unicast and multicast | Ericsson |
R1-2308175 | Draft CR on K1 timing for DCI 1_0 with MBS | Ericsson |
R1-2308176 | Draft CR on PUCCH resources for multiplexing HARQ-ACK | Ericsson |
R1-2308177 | draft CR on intra UE HARQ multiplexing | Ericsson |
R1-2308178 | draft CR on type3 codebook for unicast and multicast | Ericsson |
R1-2308189 | Discussion on Rel-17 maintenance issues for MBS | Huawei, HiSilicon, CBN |
R1-2308190 | Draft CR on HARQ-ACK for multicast to 38.213 | Huawei, HiSilicon, CBN |
R1-2308191 | Draft CR on NCD-SSB for RedCap | Huawei, HiSilicon |
R1-2308192 | Correction on HARQ-ACK timing for FR2-2 | Huawei, HiSilicon |
R1-2308193 | Corrections to K2 indication for multi-PUSCH scheduling in TS38.214 | Huawei, HiSilicon |
R1-2308197 | Correction on Rel-17 group based beam reporting | Huawei, HiSilicon |
R1-2308199 | Correction on description of valid PSFCH occasion for IUC scheme 2 in TS 38.213 | Nokia, Nokia Shanghai Bell |
R1-2308208 | Discussion on NCJT CMR restriction | NTT DOCOMO, INC. |
R1-2308216 | FL Summary for Rel-17 Maintenance on NR Positioning Enhancements | Moderator (CATT) |
R1-2308220 | FL summary #1 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
R1-2308221 | FL summary #2 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
R1-2308222 | FL summary #3 on Rel-17 RedCap maintenance | Moderator (Ericsson) |
R1-2308223 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
R1-2308241 | Moderator Summary for Rel.17 NR FeMIMO maintenance: Item 2c: mTRP beam management | Moderator (CATT) |
R1-2308268 | Summary on correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | Moderator (Huawei) |
R1-2308269 | Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | Moderator (Huawei) |
R1-2308270 | FLS#1 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
R1-2308271 | FLS#2 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
R1-2308272 | FLS#3 on the HARQ-ACK related issues for Rel-17 NR MBS | Moderator (Huawei) |
R1-2308273 | Draft CR on HARQ-ACK codebook for maxNrofCodeWords | Moderator (Huawei), CATT |
R1-2308274 | Draft CR on Type-2 HARQ-ACK codebook on PUSCH for multicast | Moderator (Huawei), CATT |
R1-2308275 | Draft CR on k1 timing for UE monitoring MBS multicast | Moderator (Huawei), ZTE |
R1-2308276 | Draft CR on PUCCH resources for multicast HARQ-ACK | Moderator (Huawei) |
R1-2308325 | Moderator Summary#1 of Maintenance on Rel-17 SRS | Moderator (ZTE) |
R1-2308329 | Moderator Summary for Rel. 17 NR FeMIMO – HST-SFN (Round 0) | Moderator (Intel) |
R1-2308335 | Moderator Summary #1 for Maintenance on Rel-17 Multi-Beam | Moderator (ZTE) |
R1-2308353 | Summary for Rel.17 NR FeMIMO maintenance: mTRP PUCCH/PUSCH enhancement | Moderator (Nokia) |
R1-2308354 | Moderator Summary for Rel.17 NR FeMIMO maintenance CSI enhancement | Moderator (Huawei) |
R1-2308365 | Summary of email discussion under [114-R17-Others] for Type0-PDCCH monitoring on non-zero common search space | Moderator (MediaTek Inc.) |
R1-2308375 | CR on RI restriction description for NCJT in TS38.214 | NEC, Samsung |
R1-2308377 | Moderator summary#1 of Rel-17 URLLC & IIoT maintenance | Moderator (Nokia) |
R1-2308378 | Miscellaneous corrections on Rel-17 enhanced URLLC & IIoT | Moderator (Nokia) |
R1-2308379 | Correction on timeline requirements for simultaneous PUCCH and PUSCH transmission of different priorities | Moderator (Nokia), Samsung |
R1-2308380 | Draft LS on Rel-17 PUCCH repetition enhancements | Moderator (Nokia) |
R1-2308381 | [114-R17-CovEnh] FL summary of maintenance issues for Rel-17 NR coverage enhancements | Moderator (China Telecom) |
R1-2308382 | Summary #1 on maximum number of RxTxTEGs for the same DL PRS for Rel-17 Positioning | Moderator (Qualcomm) |
R1-2308383 | Moderator’s summary#1 on scheduling related issues for Rel-17 NR MBS | Moderator (CMCC) |
R1-2308384 | Moderator’s summary#2 on scheduling related issues for Rel-17 NR MBS | Moderator (CMCC) |
R1-2308398 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
R1-2308399 | Summary #1 on K2 indication for multi-PUSCH scheduling | Moderator (LG Electronics) |
R1-2308401 | Moderator summary of draft CR on correction of timing of Msg3 repetition | Moderator (vivo) |
R1-2308402 | Draft CR on resource allocation of CORESET(s) configured in CFR | Moderator (CMCC) |
R1-2308403 | Draft CR on the definition for CFR in TS 38.211 | Moderator (CMCC) |
R1-2308407 | Summary#1 for maintenance on UE power saving enhancements | Moderator (MediaTek) |
R1-2308409 | [114-R17-Others] Summary on CORESET0 for bands n79 and n104 | Moderator (Nokia) |
R1-2308411 | Moderator Summary for draft CRs for Rel-17 NR_NTN_solutions-Core | Moderator (MediaTek) |
R1-2308413 | Correction on description of valid PSFCH occasion for scheme 2 in TS 38.213 | Huawei, HiSilicon |
R1-2308417 | Summary#1 on Rel-17 SDT | Moderator (ZTE) |
R1-2308418 | Correction on simultaneous reception of SDT and other channels in TS 38.202 | Moderator (ZTE) |
R1-2308427 | Miscellaneous corrections on Rel-17 enhanced URLLC & IIoT | Moderator (Nokia), CATT, vivo, Sharp |
R1-2308428 | Correction on timeline requirements for simultaneous PUCCH and PUSCH transmission of different priorities | Moderator (Nokia), Samsung |
R1-2308429 | LS on Rel-17 PUCCH repetition enhancements | RAN1, Nokia |
R1-2308430 | Correction on SP CSI multiplexing on PUSCH after DCI activation | Samsung |
R1-2308431 | Correction on SFN configuration for CSI-RS reception using default beam | Samsung |
R1-2308439 | Reply LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 | RAN1, Qualcomm Incorporated |
R1-2308440 | Summary of discussions related to reply to RAN2 LS in R1-2306384 | Moderator (Qualcomm Incorporated) |
R1-2308444 | Correction on HARQ-ACK timing for FR2-2 | Moderator (LG Electronics), Huawei, HiSilicon, Fujitsu, ZTE, Sanechips |
R1-2308445 | Draft Reply LS on K2 indication for multi-PUSCH | LG Electronics |
R1-2308446 | Reply LS on K2 indication for multi-PUSCH | RAN1, LG Electronics |
R1-2308452 | Moderator Summary#2 for Rel.17 NR FeMIMO maintenance CSI enhancement | Moderator (Huawei) |
R1-2308489 | Correction on PUSCH repetition type B with DMRS bundling | Moderator (China Telecom), Apple, Ericsson, vivo, Huawei, HiSilicon |
R1-2308490 | Correction on the calculation of the number of coded modulation symbols for UCI multiplexing on TBoMS | Moderator (China Telecom), Xiaomi, Huawei, HiSilicon |
R1-2308499 | Summary#2 for maintenance on UE power saving enhancements | Moderator (MediaTek) |
R1-2308524 | [Draft] Corrections on PDCCH monitoring adaptation | Apple, OPPO, Moderator (MediaTek) |
R1-2308525 | Corrections on PDCCH monitoring adaptation | Apple, OPPO, Moderator (MediaTek) |
R1-2308526 | [Draft] Alignment on SSSG switching | ZTE, Sanechips, CMCC, Apple, Moderator (MediaTek) |
R1-2308527 | Alignment on SSSG switching | ZTE, Sanechips, CMCC, Apple, Moderator (MediaTek) |
R1-2308534 | Session notes for 7.2 (Maintenance on Supporting NR from 52.6GHz to 71 GHz) | Ad-Hoc Chair (Huawei) |
R1-2308535 | Session notes for 7.2 (Maintenance on Enhanced Industrial Internet of Things (IoT) and URLLC) | Ad-hoc Chair (CMCC) |
R1-2308536 | Session notes for 7.2 (Maintenance on Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
R1-2308537 | Session notes for 7.2 (Maintenance on NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
R1-2308538 | Session notes for 7.2 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
R1-2308539 | Session notes for 7.2 (Maintenance on UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
R1-2308540 | Session notes for 7.2 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
R1-2308541 | Session notes for 7.2 (Maintenance on NR Sidelink enhancement) | Ad-Hoc Chair (Huawei) |
R1-2308542 | Session notes for 7.2 (Maintenance on NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
R1-2308556 | Correction to CORESET0 selection for new BWs of bands n79 and n104 | Nokia, Nokia Shanghai Bell, Samsung |
R1-2308564 | Correction on simultaneous reception of SDT and other channels in TS 38.202 | Moderator (ZTE), Xiaomi, vivo, Ericsson, Samsung, Intel, Qualcomm, New H3C |
R1-2308565 | Summary#2 on Rel-17 SDT | Moderator (ZTE) |
R1-2308586 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
R1-2308588 | Correction on PUSCH repetition type B with DMRS bundling | Moderator (China Telecom), Apple, Ericsson, vivo, Huawei, HiSilicon |
R1-2308589 | Correction on the calculation of the number of coded modulation symbols for UCI multiplexing on TBoMS | Moderator (China Telecom), Xiaomi, Huawei, HiSilicon |
R1-2308617 | Draft CR on HARQ-ACK codebook for maxNrofCodeWords | Moderator (Huawei), CATT, CBN, vivo, ZTE, Qualcomm |
R1-2308618 | Draft CR on Type-2 HARQ-ACK codebook on PUSCH for multicast | Moderator (Huawei), CATT, CBN |
R1-2308619 | CR on multiplexing NACK-only, CSI and SR in a PUCCH | Moderator (Huawei), vivo, ZTE |
R1-2308621 | Draft CR on PDCCH validation for multicast SPS | Moderator (CMCC) |
R1-2308622 | Draft CR on K1 timing for type 1 codebook | Moderator (Huawei), vivo, Samsung, CATT, CBN, ZTE, Qualcomm |
R1-2308623 | Draft CR on HARQ-ACK codebook for multicast SPS | Moderator (Huawei), ZTE |
R1-2308629 | Moderator summary#2 of Rel-17 URLLC & IIoT maintenance | Moderator (Nokia) |
R1-2308633 | Clarification of TDD UL validation and SDT operation for RedCap UEs | Moderator (Ericsson), NEC, MediaTek Inc., ZTE, Ericsson |
R1-2308635 | Summary#3 for maintenance on UE power saving enhancements | Moderator (MediaTek) |
R1-2308636 | Correction for the mapping of rank combination value for Rel-17 NCJT CSI | Moderator (Huawei), NEC, Samsung, HiSilicon |
R1-2308657 | Session notes for 7.2 (Maintenance on Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
R1-2308658 | Clarification of TDD UL validation and SDT operation for RedCap UEs | Moderator (Ericsson), NEC, MediaTek Inc., ZTE, NTT DOCOMO, Ericsson |
R1-2308660 | CR on HARQ-ACK codebook for maxNrofCodeWords | Moderator (Huawei), CATT, CBN, vivo, ZTE, Qualcomm |
R1-2308661 | CR on K1 timing for type 1 codebook | Moderator (Huawei), vivo, Samsung, CATT, CBN, ZTE, Qualcomm |
R1-2308665 | CR on HARQ-ACK codebook for multicast SPS | Moderator (Huawei), ZTE |
R1-2308686 | Alignment of terminology across specifications | Ericsson |
R1-2308687 | Rel-17 editorial corrections for TS 38.212 | Huawei |
R1-2308688 | Rel-17 editorial corrections for TS 38.213 | Samsung |
R1-2308689 | Rel-17 editorial corrections for TS 38.214 | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2308672 | Consolidated higher layers parameter list for Rel-18 | Moderator (Ericsson) |
R1-2308673 | DRAFT LS on Rel-18 higher-layers parameter list | Moderator (Ericsson) |
R1-2308674 | LS on Rel-18 higher-layers parameter list | RAN1, Ericsson |
R1-2308676 | Summary of Email discussion on LS for Rel-18 higher layer parameters | Moderator (Ericsson) |
R1-2308677 | Collection of updated higher layers parameter list for Rel-18 | Moderator (Ericsson) |
R1-2308690 | Introduction of MIMO evolution for Rel-18 for TS38.215 | Intel Corporation |
R1-2308691 | Introduction of Rel-18 Positioning Enhancements for TS38.215 | Intel Corporation |
R1-2308692 | Introduction of sidelink channel access procedures for Rel-18 NR sidelink evolution | NTT DOCOMO, INC. |
R1-2308693 | Introduction of IoT (Internet of Things) NTN (non-terrestrial network) enhancements | Motorola Mobility |
R1-2308694 | Introduction of dynamic spectrum sharing (DSS) enhancements | Samsung |
R1-2308695 | Introduction of support for enhanced reduced capability NR devices | Samsung |
R1-2308696 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Samsung |
R1-2308697 | Introduction of multi-carrier enhancements for NR | Samsung |
R1-2308698 | Introduction of MIMO Evolution for Downlink and Uplink | Samsung |
R1-2308699 | Introduction of further mobility enhancements | Samsung |
R1-2308700 | Introduction of Network Controlled Repeaters - NR_NCR-Core | Samsung |
R1-2308701 | Introduction of NR NTN enhancements | Samsung |
R1-2308702 | Introduction of expanded and improved NR positioning | Samsung |
R1-2308703 | Introduction of NR sidelink evolution - NR_SL_enh2-Core | Samsung |
R1-2308704 | Introduction of NR Sidelink operation on shared spectrum | Ericsson |
R1-2308705 | Introduction of NR sidelink evolution | Ericsson |
R1-2308706 | Introduction of expanded and improved NR positioning | Ericsson |
R1-2308707 | Introduction of MIMO evolution for downlink and uplink | Ericsson |
R1-2308708 | Introduction of NR support for dedicated spectrum less than 5MHz for FR1 | Ericsson |
R1-2308709 | Introduction of Rel-18 Multi-carrier enhancements | Huawei |
R1-2308710 | Introduction of Rel-18 MIMO Evolution for Downlink and Uplink | Huawei |
R1-2308711 | Introduction of Rel-18 Further NR mobility enhancements | Huawei |
R1-2308712 | Introduction of Rel-18 NR NTN enhancements | Huawei |
R1-2308713 | Introduction of NR positioning enhancement in Rel-18 | Huawei |
R1-2308714 | Introduction of Rel-18 NR sidelink evolution | Huawei |
R1-2308715 | Release 18 TS38.202 Editor CR for MIMO | Qualcomm |
R1-2308716 | Introduction of specification support for MIMO enhancements on CSI | Nokia |
R1-2308717 | Introduction of specification support for MIMO enhancements on uTCI_STxMP_DMRS_SRS_8Tx_2TA | Nokia |
R1-2308718 | Introduction of specification support for mobility enhancements | Nokia |
R1-2308719 | Introduction of specification support for Expanded and Improved NR Positioning | Nokia |
R1-2308720 | Introduction of specification enhancements for NR sidelink evolution | Nokia |
R1-2308721 | Introduction of multi-cell PDSCH / PUSCH scheduling | Nokia |
R1-2308722 | Introduction of Rel-18 network controlled repeaters | NTT DOCOMO, INC. |
R1-2308723 | Introduction of BWP operation without restriction | Samsung |
R1-2308724 | Introduction of dynamic spectrum sharing enhancements | Nokia |
R1-2308725 | Introduction of specification support for BandWidth Part operation without restriction in NR | Nokia |
R1-2308726 | Introduction of Rel-18 network controlled repeaters | Huawei |
R1-2308727 | Introduction of dynamic spectrum sharing enhancements | Ericsson |
R1-2308728 | Introduction of multi-carrier enhancements | Ericsson |
R1-2308732 | Release 18 TS38.202 Editor CR for NR sidelink evolution | Qualcomm |
R1-2308733 | Introduction of Rel-18 network energy saving for NR | Huawei |
R1-2308734 | Introduction of Rel-18 further NR Coverage enhancement | Huawei |
R1-2308735 | Introduction of Rel-18 NR demodulation performance evolution | Huawei |
R1-2308736 | Introduction of Rel-18 NR support for dedicated spectrum less than 5MHz for FR1 | Huawei |
R1-2308737 | Introduction of Rel-18 XR enhancements for NR | Huawei |
R1-2308738 | Introduction of further NR coverage enhancements | Samsung |
R1-2308739 | Introduction of network energy savings for NR | Samsung |
R1-2308740 | Introduction of XR Enhancements for NR | Samsung |
R1-2308741 | Introduction of further NR coverage enhancements | Nokia |
R1-2308742 | Introduction of specification support for NR NTN enhancements | Nokia |
R1-2308743 | Introduction of specification support for network energy saving | Nokia |
R1-2308744 | Introduction of specification for XR Enhancements for NR | Nokia |
R1-2308745 | Introduction of enhanced reduced capability NR devices | Nokia |
R1-2308746 | Introduction of UL Tx switching across up to 4 bands | Nokia |
R1-2308747 | Introduction of Rel-18 NR NTN enhancements for TS38.215 | Intel Corporation |
R1-2308750 | Introduction of IoT NTN enhancements | FUTUREWEI |
R1-2308751 | Editor’s summary on draft CR 36.212 for IoT_NTN_enh-Core | FUTUREWEI |
R1-2308752 | Introduction of RS for pathloss determination of Type 1 CG PUSCH [PL RS Type 1 CG] | Samsung |
R1-2308753 | Introduction of multiplexing in a PUSCH with repetitions HARQ-ACK associated with DL assignments received after an UL grant for the PUSCH [HARQ-ACK MUX on PUSCH] | Samsung |
R1-2308754 | Introduction of QCL-TypeD priorities for overlapping CORESETs in M-DCI/M-TRP operation [QCL-TypeD CORESET priority for M-TRP] | Samsung |
R1-2308755 | Editor’s summary of email discussions [Post-114-36.213-IoT_NTN_enh-Core] | Motorola Mobility |
R1-2308756 | Editor’s summary on draft CR 37.213 for SL-U | Ericsson |
R1-2308757 | Editor’s summary on draft CR 38.211 for NR_SL_enh2-Core | Ericsson |
R1-2308758 | Editor’s summary on draft CR 38.211 for NR_MIMO_evo_DL_UL-Core | Ericsson |
R1-2308759 | Editor’s summary on draft CR 38.211 for NR_LessThan_5MHz_FR1-Core | Ericsson |
R1-2308760 | Summary of email discussion [Post114-38.212-NR_cov_enh2-Core] | Moderator (Huawei) |
R1-2308761 | Summary of email discussion [Post114-38.212-NR_demod_enh3-Perf] | Moderator (Huawei) |
R1-2308762 | Summary of email discussion [Post114-38.212-NR_FR1_lessthan_5MHz_BW-Core] | Moderator (Huawei) |
R1-2308763 | Summary of email discussion [Post114-38.212-NR_MIMO_evo_DL_UL] | Moderator (Huawei) |
R1-2308764 | Summary of email discussion [Post114-38.212-NR_Mob_enh2-Core] | Moderator (Huawei) |
R1-2308765 | Summary of email discussion [Post114-38.212-NR_MC_enh] | Moderator (Huawei) |
R1-2308766 | Summary of email discussion [Post114-38.212-Netw_Energy_NR-Core] | Moderator (Huawei) |
R1-2308767 | Summary of email discussion [Post114-38.212-NR_pos_enh2-Core] | Moderator (Huawei) |
R1-2308768 | Summary of email discussion [Post114-38.212-NR_SL_enh2-Core] | Moderator (Huawei) |
R1-2308769 | Summary of email discussion [Post114-38.212-NR_XR_enh-Core] | Moderator (Huawei) |
R1-2308770 | Summary of email discussions [114-R18-38.213-NR_cov_enh2] | Samsung |
R1-2308771 | Summary of email discussions [114-R18-38.213-NR_FR1_lessthan_5MHz_BW] | Samsung |
R1-2308772 | Summary of email discussions [114-R18-38.213-NR_MIMO_evo_DL_UL] | Samsung |
R1-2308773 | Summary of email discussions [114-R18-38.213-NR_mob_enh2] | Samsung |
R1-2308774 | Summary of email discussions [114-R18-38.213-NR_Netw_Energy_NR] | Samsung |
R1-2308775 | Summary of email discussions [114-R18-38.213-NR_NTN_enh] | Samsung |
R1-2308776 | Summary of email discussions [114-R18-38.213-NR_pos_enh2] | Samsung |
R1-2308777 | Summary of email discussions [114-R18-38.213-NR_redcap_enh] | Samsung |
R1-2308778 | Summary of email discussions [114-R18-38.213-NR_SL_enh2] | Samsung |
R1-2308779 | Summary of email discussions [114-R18-38.213-NR_XR_enh] | Samsung |
R1-2308780 | Summary of email discussion on the introduction of UL Tx switching across up to 4 bands in [Post-114-38.214-MC_Enh] | Nokia |
R1-2308781 | Summary on email discussion on NR_MIMO_evo_DL_UL-Core-uTCI-STxMP-DMRS-SRS-8TXUL-2TA | Nokia |
R1-2308782 | Summary on email discussion on NR_MIMO_evo_DL_UL-Core-CSI | Nokia |
R1-2308783 | Summary on email discussion on NR_SL_enh2-Core | Nokia |
R1-2308784 | Summary on email discussion on NR_pos_enh2-Core | Nokia |
R1-2308785 | Summary on email discussion on NR_redcap_enh-Core | Nokia |
R1-2308786 | Summary on email discussion on Netw_Energy_NR | Nokia |
R1-2308787 | Summary on email discussion on NR_XR_enh-Core | Nokia |
R1-2308788 | Summary on email discussion on NR_NTN_enh-Core | Nokia |
R1-2308789 | Summary on email discussion on NR_Mob_enh2-Core | Nokia |
R1-2308790 | Summary on email discussion on NR_cov_enh2-Core | Nokia |
R1-2308791 | Editor’s summary on draft CR 38.211 for NR_pos_enh2-Core | Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2307658 | RRC parameters for Rel-18 NR MIMO | Moderator (Samsung) |
R1-2308667 | Updated list of RRC parameters for Rel-18 NR MIMO | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2306391 | Unified TCI framework extension for multi-TRP | Panasonic |
R1-2306421 | Unified TCI framework extension for multi-TRP | FUTUREWEI |
R1-2306458 | Remaining Issues on Unified TCI for mTRP | InterDigital, Inc. |
R1-2306533 | Discussion on unified TCI framework extension for multi-TRP | Huawei, HiSilicon |
R1-2306599 | Unified TCI framework extension for multi-TRP | Ericsson |
R1-2306609 | Enhancements on unified TCI framework extension for multi-TRP | ZTE |
R1-2306629 | Discussion on unified TCI framework extension for multi-TRP | Spreadtrum Communications |
R1-2306732 | Further discussion on unified TCI framework extension for multi-TRP | vivo |
R1-2306854 | Unified TCI Framework Extension for multi-TRP | Intel Corporation |
R1-2306926 | Discussion on unified TCI framework extension for multi-TRP operation | TCL |
R1-2306931 | Discussion of unified TCI framework for multi-TRP | Lenovo |
R1-2306997 | Moderator summary on extension of unified TCI framework (Round 0) | Moderator (MediaTek Inc.) |
R1-2306998 | Moderator summary on extension of unified TCI framework (Round 1) | Moderator (MediaTek Inc.) |
R1-2306999 | Moderator summary on extension of unified TCI framework (Round 2) | Moderator (MediaTek Inc.) |
R1-2307006 | Unified TCI framework extension for multi-TRP/panel | LG Electronics |
R1-2307053 | Remaining issues on unified TCI framework extension for multi-TRP operation | CATT |
R1-2307119 | Discussion on unified TCI framework extension for multi-TRP | NEC |
R1-2307149 | Discussion on unified TCI framework extension for multi-TRP | Fujitsu |
R1-2307175 | Discussion on unified TCI framework extension for multi-TRP | CMCC |
R1-2307260 | Extension of Unified TCI framework for multi-TRP | Apple |
R1-2307336 | Unified TCI framework extension for multi-TRP | Sharp |
R1-2307347 | Unified TCI framework extension for multi-TRP | xiaomi |
R1-2307458 | Discussion on unified TCI framework extension for multi-TRP | NTT DOCOMO, INC. |
R1-2307511 | Unified TCI framework extension for multi-TRP | OPPO |
R1-2307591 | Discussion on unified TCI framework extension for multi-TRP | Hyundai Motor Company |
R1-2307594 | Summary of pre-meeting offline discussion on extension of unified TCI framework | Moderator (MediaTek Inc.) |
R1-2307605 | Unified TCI framework extension for multi-TRP | Nokia, Nokia Shanghai Bell |
R1-2307659 | Views on unified TCI extension focusing on m-TRP | Samsung |
R1-2307758 | Discussion on unified TCI framework extension for multi-TRP | Transsion Holdings |
R1-2307776 | Discussion on unified TCI framework extension for multi-TRP | FGI |
R1-2307848 | Discussion on unified TCI framework extension for multi-TRP | |
R1-2307889 | Discussion on unified TCI framework extension for multi-TRP | ITRI |
R1-2307907 | Extension of unified TCI framework for mTRP | Qualcomm Incorporated |
R1-2307997 | Discussion on Unified TCI framework extension for multi-TRP | CEWiT |
R1-2308070 | Remaining issues on unified TCI framework extension for multi-TRP | MediaTek Inc. |
R1-2308112 | Multi-TRP enhancements for the unified TCI framework | Fraunhofer IIS, Fraunhofer HHI |
R1-2308451 | Moderator summary on extension of unified TCI framework (Round 3) | Moderator (MediaTek Inc.) |
R1-2308630 | Moderator summary on extension of unified TCI framework (Final) | Moderator (MediaTek Inc.) |
TDoc | Title | Source |
---|---|---|
R1-2306394 | Discussions on two TAs for multi-DCI | Ruijie Network Co. Ltd |
R1-2306396 | Discussions on two TAs for multi-DCI | Ruijie Network Co. Ltd |
R1-2306422 | Enhancements to support two TAs for multi-DCI | FUTUREWEI |
R1-2306459 | Remaining Issues on Multiple TA for mTRP Operation | InterDigital, Inc. |
R1-2306534 | Study on TA enhancement for UL M-TRP transmission | Huawei, HiSilicon |
R1-2306600 | Two TAs for multi-DCI | Ericsson |
R1-2306610 | TA enhancement for multi-DCI | ZTE |
R1-2306630 | Discussion on two TAs for multi-DCI based multi-TRP | Spreadtrum Communications |
R1-2306733 | Further discussion on two TAs for multi-DCI-based multi-TRP operation | vivo |
R1-2306853 | On two TAs for multi-DCI | Intel Corporation |
R1-2306872 | Discussion on two TAs for multi-DCI based on multi-TRP operation | TCL |
R1-2306932 | Discussion of two TAs for multi-DCI UL transmission | Lenovo |
R1-2307007 | Two TAs for multi-TRP/panel | LG Electronics |
R1-2307054 | Remaining issues on TA enhancement for multi-DCI | CATT |
R1-2307120 | Discussion on two TAs for multi-DCI | NEC |
R1-2307176 | Discussion on two TAs for multi-DCI | CMCC |
R1-2307261 | Two TAs for multi-DCI Uplink Transmissions | Apple |
R1-2307337 | Two TAs for multi-DCI | Sharp |
R1-2307348 | Discussion on two TAs for multi-TRP operation | xiaomi |
R1-2307459 | Discussion on two TAs for multi-DCI | NTT DOCOMO, INC. |
R1-2307512 | Two TAs for multi-DCI based multi-TRP operation | OPPO |
R1-2307606 | Two TAs for UL multi-DCI multi-TRP operation | Nokia, Nokia Shanghai Bell |
R1-2307660 | Views on two TAs for m-DCI | Samsung |
R1-2307737 | Discussion on two TAs for mTRP operation | ETRI |
R1-2307759 | Discussion on two TAs for multi-DCI based multi-TRP operation | Transsion Holdings |
R1-2307777 | Discussion on two TAs for multi-DCI | FGI |
R1-2307849 | Discussion on two TAs for multi-DCI | |
R1-2307876 | Discussion on multi-TA Cells for beam failure recovery | ASUSTEK |
R1-2307908 | Supporting two TAs for multi-DCI based mTRP | Qualcomm Incorporated |
R1-2308071 | Remaining issues on UL Tx timing management for MTRP | MediaTek Inc. |
R1-2308338 | Moderator Summary #1 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2308425 | Moderator Summary #2 on Two TAs for multi-DCI | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2306460 | Remaining Details on Rel-18 CSI | InterDigital, Inc. |
R1-2306535 | CSI enhancement for coherent JT and mobility | Huawei, HiSilicon |
R1-2306611 | CSI enhancement for high/medium UE velocities and CJT | ZTE |
R1-2306631 | Discussion on CSI enhancement for high/medium UE velocities and coherent JT | Spreadtrum Communications |
R1-2306734 | Further discussion on CSI enhancement for high-medium UE velocities and coherent JT | vivo |
R1-2306831 | Remaining details on CSI enhancements | Intel Corporation |
R1-2306900 | Views on CSI enhancement for high/medium UE velocities and coherent JT | Sony |
R1-2306933 | Discussion of CSI enhancement for high speed UE and coherent JT | Lenovo |
R1-2306951 | On CSI Enhancement | |
R1-2307008 | Potential CSI enhancement for high/medium UE velocities and coherent JT | LG Electronics |
R1-2307055 | Remaining issues on CSI enhancement | CATT |
R1-2307126 | Discussion on CSI enhancement | NEC |
R1-2307150 | Discussion on remaining issues of Rel-18 MIMO CSI enhancement | Fujitsu |
R1-2307177 | Discussion on CSI enhancement for high/medium UE velocities and CJT | CMCC |
R1-2307262 | Views on Rel-18 MIMO CSI enhancement | Apple |
R1-2307349 | Remained issues discussion on CSI enhancement for high/medium UE velocities and CJT | xiaomi |
R1-2307460 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
R1-2307513 | CSI enhancement for high/medium UE velocities and coherent JT | OPPO |
R1-2307607 | CSI enhancement for high/medium UE velocities and CJT | Nokia, Nokia Shanghai Bell |
R1-2307661 | Moderator summary on Rel-18 CSI enhancements | Moderator (Samsung) |
R1-2307662 | Views on CSI enhancements | Samsung |
R1-2307725 | Discussion on CSI enhancement | Mavenir |
R1-2307885 | Views on CSI Enhancements for CJT | AT&T |
R1-2307893 | On CSI enhancements for Rel-18 NR MIMO evolution | Ericsson |
R1-2307909 | CSI enhancements for medium UE velocities and Coherent-JT | Qualcomm Incorporated |
R1-2308064 | CSI Enhancements | MediaTek Inc. |
R1-2308206 | Discussion on CSI enhancement | NTT DOCOMO, INC. |
R1-2308366 | Moderator Summary#2 on Rel-18 CSI enhancements: Round 1 | Moderator (Samsung) |
R1-2308395 | DRAFT LS to RAN2 on CBSR for Rel-18 MIMO | Samsung |
R1-2308396 | LS to RAN2 on CBSR for Rel-18 MIMO | RAN1, Samsung |
R1-2308400 | Moderator Summary for Tuesday offline on Rel-18 CSI enhancements | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2306395 | Discussions on increased number of orthogonal DMRS ports | New H3C Technologies Co., Ltd. |
R1-2306398 | Discussions on increased number of orthogonal DMRS ports | Ruijie Network Co. Ltd |
R1-2306423 | On increasing the number of orthogonal DM-RS ports for MU-MIMO | FUTUREWEI |
R1-2306461 | Remaining Details on DMRS Enhancements | InterDigital, Inc. |
R1-2306536 | Discussion on DMRS enhancements in Rel-18 | Huawei, HiSilicon |
R1-2306612 | DMRS enhancement for UL/DL MU-MIMO and 8 Tx UL SU-MIMO | ZTE, China Telecom |
R1-2306632 | Discussion on increased number of orthogonal DMRS ports | Spreadtrum Communications |
R1-2306735 | Further discussion on DMRS enhancements | vivo |
R1-2306855 | DMRS Enhancements for Rel-18 | Intel Corporation |
R1-2306934 | Discussion of increased number of orthogonal DMRS ports | Lenovo |
R1-2306952 | On DMRS Enhancement | |
R1-2307009 | Increased number of orthogonal DMRS ports | LG Electronics |
R1-2307056 | Remaining issues on DMRS enhancement | CATT |
R1-2307127 | Discussion on increased number of orthogonal DMRS ports | NEC |
R1-2307178 | Discussion on increased number of orthogonal DMRS ports | CMCC |
R1-2307231 | On increased number of orthogonal DMRS ports for MU-MIMO and 8 Tx UL SU-MIMO | Ericsson |
R1-2307263 | Views on remaining issues for DMRS enhancement | Apple |
R1-2307338 | Increased number of orthogonal DMRS ports | Sharp |
R1-2307350 | Discussion on DMRS enhancement | xiaomi |
R1-2307461 | Discussion on DMRS enhancements | NTT DOCOMO, INC. |
R1-2307514 | DMRS enhancement for Rel-18 MIMO | OPPO |
R1-2307608 | Rel-18 UL and DL DMRS Enhancements | Nokia, Nokia Shanghai Bell |
R1-2307663 | Views on DMRS enhancements | Samsung |
R1-2307910 | Design for increased number of orthogonal DMRS ports | Qualcomm Incorporated |
R1-2308209 | FL summary on DMRS#1 | Moderator (NTT DOCOMO) |
R1-2308210 | FL summary on DMRS#2 | Moderator (NTT DOCOMO) |
R1-2308211 | FL summary on DMRS#3 | Moderator (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306397 | Discussions on SRS enhancement in Rel-18 | New H3C Technologies Co., Ltd. |
R1-2306424 | SRS enhancements for TDD CJT and 8TX operation | FUTUREWEI |
R1-2306462 | Remaining Details on SRS for CJT and 8TX UEs | InterDigital, Inc. |
R1-2306537 | Discussion on SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18 | Huawei, HiSilicon |
R1-2306613 | SRS enhancement targeting TDD CJT and 8 TX operation | ZTE |
R1-2306633 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | Spreadtrum Communications |
R1-2306736 | Further discussion on SRS enhancements | vivo |
R1-2306807 | On SRS enhancements targeting TDD CJT and 8 TX operation | Ericsson |
R1-2306935 | Discussion of SRS enhancement | Lenovo |
R1-2306953 | On SRS Enhancement | |
R1-2307010 | SRS enhancement targeting TDD CJT and 8 TX operation | LG Electronics |
R1-2307057 | SRS enhancement for CJT and 8Tx operation | CATT |
R1-2307128 | Discussion on SRS enhancement | NEC |
R1-2307179 | Discussion on SRS enhancement targeting TDD CJT and 8 TX operation | CMCC |
R1-2307264 | Views on Rel-18 MIMO SRS enhancement | Apple |
R1-2307339 | SRS enhancement targeting TDD CJT and 8 TX operation | Sharp |
R1-2307351 | Discussion on SRS enhancements | xiaomi |
R1-2307462 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
R1-2307515 | SRS enhancement targeting TDD CJT and 8 TX operation | OPPO |
R1-2307595 | Discussions on SRS enhancement targeting TDD CJT and 8 TX operation | KDDI Corporation |
R1-2307609 | SRS enhancement for TDD CJT and 8Tx operation | Nokia, Nokia Shanghai Bell |
R1-2307664 | Views on SRS enhancements | Samsung |
R1-2307738 | Discussion on SRS enhancement targeting TDD CJT | ETRI |
R1-2307911 | SRS enhancement for TDD CJT and 8 Tx operation | Qualcomm Incorporated |
R1-2308203 | SRS enhancement for CJT and 8Tx operation | CATT |
R1-2308293 | FL Summary #1 on SRS enhancements | Moderator (FUTUREWEI) |
R1-2308294 | FL Summary #2 on SRS enhancements | Moderator (FUTUREWEI) |
R1-2308295 | FL Summary #3 on SRS enhancements | Moderator (FUTUREWEI) |
TDoc | Title | Source |
---|---|---|
R1-2306392 | UL Precoding for Multi-panel Transmission | Panasonic |
R1-2306463 | Remaining Issues Multi-panel Uplink Transmission | InterDigital, Inc. |
R1-2306538 | Discussion on UL precoding indication for multi-panel transmission | Huawei, HiSilicon |
R1-2306554 | Discussions on UL precoding indication for multi-panel transmission | Ruijie Network Co. Ltd |
R1-2306614 | Enhancements on UL precoding indication for multi-panel transmission | ZTE |
R1-2306634 | Discussion on UL precoding indication for multi-panel transmission | Spreadtrum Communications |
R1-2306737 | Further discussion on UL precoding indication for multi-panel transmission | vivo |
R1-2306806 | UL precoding indication for multi-panel transmission | Ericsson |
R1-2306849 | UL precoding indication for multi-panel transmission | Intel Corporation |
R1-2306936 | UL precoding indication for multi-panel transmission | Lenovo |
R1-2306954 | On Simultaneous Multi-Panel Transmission | |
R1-2307011 | UL precoding indication for multi-panel transmission | LG Electronics |
R1-2307058 | Remaining issues on UL precoding indication for multi-panel transmission | CATT |
R1-2307121 | Discussion on UL precoding indication for multi-panel transmission | NEC |
R1-2307151 | Discussion on UL precoding indication for multi-panel transmission | Fujitsu |
R1-2307180 | Discussion on UL precoding indication for multi-panel transmission | CMCC |
R1-2307265 | Remaining issues on UL precoding indication for multi-panel simultaneous PUSCH transmissions | Apple |
R1-2307352 | Enhancements on multi-panel uplink transmission | xiaomi |
R1-2307463 | Discussion on multi-panel transmission | NTT DOCOMO, INC. |
R1-2307516 | Discussion on UL precoding indicaton for multi-panel transmission | OPPO |
R1-2307592 | Discussion on UL precoding indication for multi-panel transmission | Hyundai Motor Company |
R1-2307610 | Precoder Indication for Multi-Panel UL Transmission | Nokia, Nokia Shanghai Bell |
R1-2307665 | Views on UL precoding indication for STxMP | Samsung |
R1-2307731 | Views on UL multi-panel transmission | Sharp |
R1-2307760 | Discussion on UL precoding indication for multi-panel transmission | Transsion Holdings |
R1-2307859 | Discussion on power control for STxMP | ASUSTeK |
R1-2307912 | Simultaneous multi-panel transmission | Qualcomm Incorporated |
R1-2308072 | Remaining issues on simultaneous UL transmission across multi-panel | MediaTek Inc. |
R1-2308213 | Summary #1 on Rel-18 STxMP | Moderator (OPPO) |
R1-2308214 | Summary #2 on Rel-18 STxMP | Moderator (OPPO) |
R1-2308215 | Summary #3 on Rel-18 STxMP | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2306464 | Remaining Issues on 8TX UE | InterDigital, Inc. |
R1-2306465 | FL Summary SRI/TPMI Enhancements; Preparatory | Moderator (InterDigital, Inc.) |
R1-2306466 | FL Summary SRI/TPMI Enhancements; First Round | Moderator (InterDigital, Inc.) |
R1-2306467 | FL Summary SRI/TPMI Enhancements; Second Round | Moderator (InterDigital, Inc.) |
R1-2306468 | FL Summary SRI/TPMI Enhancements; Third Round | Moderator (InterDigital, Inc.) |
R1-2306469 | FL Summary SRI/TPMI Enhancements; Forth Round | Moderator (InterDigital, Inc.) |
R1-2306470 | Recommended Direction on SRITPMI Enhancements for RAN1#114b | Moderator (InterDigital, Inc.) |
R1-2306539 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Huawei, HiSilicon |
R1-2306555 | Discussions on SRI/TPMI enhancement for enabling 8 TX UL transmission | Ruijie Network Co. Ltd |
R1-2306615 | SRI/TPMI enhancement for enabling 8 TX UL transmission | ZTE |
R1-2306635 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | Spreadtrum Communications |
R1-2306738 | Further discussion on enabling 8 TX UL transmission | vivo |
R1-2306850 | Discussion on enhancement for 8Tx UL transmission | Intel Corporation |
R1-2306901 | Considerations on SRI/TPMI enhancement for enabling 8 TX UL | Sony |
R1-2306937 | SRI/TPMI enhancement for enabling 8TX UL transmission | Lenovo |
R1-2306955 | On SRI/TPMI Indication for 8Tx Transmission | |
R1-2307012 | SRI/TPMI enhancement for enabling 8 TX UL transmission | LG Electronics |
R1-2307059 | Enhancement of SRI/TPMI for 8TX UL transmission | CATT |
R1-2307129 | Discussion on SRI/TPMI enhancement | NEC |
R1-2307152 | Discussion on SRI/TPMI enhancement for 8Tx UL transmission | Fujitsu |
R1-2307181 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | CMCC |
R1-2307266 | Views on SRI/TPMI enhancement for enabling 8 TX UL transmission | Apple |
R1-2307353 | Enhancements on 8Tx uplink transmission | xiaomi |
R1-2307464 | Discussion on 8 TX UL transmission | NTT DOCOMO, INC. |
R1-2307517 | SRI TPMI enhancement for 8 TX UL transmission | OPPO |
R1-2307611 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
R1-2307666 | Views on TPMI/SRI enhancements for 8Tx UL transmission | Samsung |
R1-2307732 | Views on 8 TX UL transmission | Sharp |
R1-2307778 | Discussion on SRI/TPMI Enhancements for 8 TX UL Transmission | FGI |
R1-2307843 | SRI/TPMI Enhancement for Enabling 8 TX UL Transmission | Ericsson |
R1-2307913 | Enhancements for 8 Tx UL transmissions | Qualcomm Incorporated |
R1-2307998 | SRI/TPMI enhancement for enabling 8 TX UL transmission | CEWiT |
R1-2308018 | Discussion on SRI/TPMI enhancement for enabling 8 TX UL transmission | KDDI Corporation |
R1-2308065 | SRI/TPMI Enhancements for Enabling 8 TX UL Transmission | MediaTek Inc. |
R1-2308328 | UL enhancements for enabling 8Tx UL transmission | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R1-2307914 | Updated TR 38.843 including RAN1 agreements from RAN1#113 | Qualcomm Incorporated |
R1-2308543 | Session notes for 9.2 (Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface) | Ad-hoc Chair (CMCC) |
R1-2308681 | Updated TR 38.843 including RAN1 agreements from RAN1#113 and RAN1#114 | Rapporteur (Qualcomm Incorporated) |
R1-2308730 | Reply LS (to Part A) on Data Collection Requirements and Assumptions | RAN1, Qualcomm |
R1-2308731 | Reply LS (to Part B) on Data Collection Requirements and Assumptions | RAN1, Qualcomm |
TDoc | Title | Source |
---|---|---|
R1-2306430 | Discussion on general aspects of AI/ML framework | FUTUREWEI |
R1-2306474 | General aspects of AI and ML framework for NR air interface | NVIDIA |
R1-2306510 | Discussion on general aspects of AI/ML framework | Huawei, HiSilicon |
R1-2306556 | Discussions on general aspects of AI/ML framework | Ruijie Network Co. Ltd |
R1-2306636 | Discussion on general aspects of AIML framework | Spreadtrum Communications |
R1-2306694 | Discussion on general aspects of AI-ML framework | Continental Automotive Technologies GmbH |
R1-2306739 | Discussions on AI/ML framework | vivo |
R1-2306794 | Discussion on general aspects of common AI PHY framework | ZTE |
R1-2306851 | General aspects of AI/ML framework for NR air interface | Intel Corporation |
R1-2306881 | Discussion on general aspects of AI/ML framework | Panasonic |
R1-2306902 | Considerations on common AI/ML framework | Sony |
R1-2306928 | Discussion on general aspects of AIML framework | Ericsson |
R1-2306956 | On General Aspects of AI/ML Framework | |
R1-2307013 | General aspects on AI/ML framework | LG Electronics |
R1-2307075 | Discussion on general aspects of AI/ML framework | CATT |
R1-2307122 | Discussion on general aspects of AI ML framework | NEC |
R1-2307153 | Discussion on general aspects of AI/ML framework | Fujitsu |
R1-2307182 | Discussion on general aspects of AI/ML framework | CMCC |
R1-2307234 | General aspects of AI/ML framework | Fraunhofer IIS, Fraunhofer HHI |
R1-2307237 | Further discussion on the general aspects of ML for Air-interface | Nokia, Nokia Shanghai Bell |
R1-2307250 | Discussion on general aspects of AI/ML framework | InterDigital, Inc. |
R1-2307267 | Discussion on general aspect of AI/ML framework | Apple |
R1-2307332 | Discussion on general aspects of AI/ML framework | KDDI Corporation |
R1-2307374 | Views on the general aspects of AI/ML framework | xiaomi |
R1-2307465 | Discussion on general aspects of AI/ML framework | NTT DOCOMO, INC. |
R1-2307563 | On general aspects of AI/ML framework | OPPO |
R1-2307598 | Discussion on general aspects of AI/ML framework | NYCU, NTPU |
R1-2307667 | General aspects of AI/ML framework and evaluation methodology | Samsung |
R1-2307805 | Discussion on general aspects of AI/ML framework | Lenovo |
R1-2307816 | Discussion on general aspects of AI/ML framework | Sharp |
R1-2307861 | Considerations on general aspects on AI-ML framework | CAICT |
R1-2307886 | General Aspects of AI/ML framework | AT&T |
R1-2307915 | General aspects of AI/ML framework | Qualcomm Incorporated |
R1-2308019 | Considering on system architecture for AI/ML framework deployment | TCL |
R1-2308091 | On General Aspects of AI/ML Framework | IIT Kanpur, Indian Institute of Tech (M) |
R1-2308131 | Discussions on General Aspects of AI/ML Framework | Indian Institute of Technology Madras (IITM), IIT Kanpur, CEWiT |
R1-2308286 | Summary#1 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308287 | Summary#2 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308288 | Summary#3 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308289 | Summary#4 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308290 | Summary#5 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308291 | Summary#6 of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
R1-2308292 | Final summary of General Aspects of AI/ML Framework | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2306431 | Discussion on evaluation of AI/ML for CSI feedback enhancement | FUTUREWEI |
R1-2306475 | Evaluation of AI and ML for CSI feedback enhancement | NVIDIA |
R1-2306511 | Evaluation on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
R1-2306606 | Evaluation of AI-CSI | Ericsson |
R1-2306637 | Discussion on evaluation on AIML for CSI feedback enhancement | Spreadtrum Communications,BUPT |
R1-2306740 | Evaluation on AI/ML for CSI feedback enhancement | vivo |
R1-2306795 | Evaluation on AI CSI feedback enhancement | ZTE |
R1-2306809 | Evaluation on AI/ML for CSI feedback enhancement | China Telecom |
R1-2306832 | Evaluations on AI/ML for CSI feedback | Intel Corporation |
R1-2306957 | On Evaluation of AI/ML based CSI | |
R1-2307076 | Evaluation and discussion on AI/ML for CSI feedback enhancement | CATT |
R1-2307154 | Evaluation on AI/ML for CSI feedback enhancement | Fujitsu |
R1-2307183 | Discussion on evaluation on AI/ML for CSI feedback enhancement | CMCC |
R1-2307238 | Evaluation of ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
R1-2307251 | Evaluation on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
R1-2307268 | Evaluation for AI/ML based CSI feedback enhancement | Apple |
R1-2307375 | Discussion on evaluation on AI/ML for CSI feedback enhancement | xiaomi |
R1-2307466 | Discussion on evaluation on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
R1-2307564 | Evaluation methodology and results on AI/ML for CSI feedback enhancement | OPPO |
R1-2307668 | Views on Evaluation of AI/ML for CSI feedback enhancement | Samsung |
R1-2307728 | Evaluation on AIML for CSI feedback enhancement | Mavenir |
R1-2307739 | Evaluation on AI/ML for CSI feedback enhancement | ETRI |
R1-2307806 | Evaluation on AI/ML for CSI feedback | Lenovo |
R1-2307916 | Evaluation on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
R1-2307999 | Evaluation of AI/ML for CSI feedback Enhancement | CEWiT |
R1-2308053 | Evaluation on AI/ML for CSI feedback enhancement | MediaTek Inc. |
R1-2308158 | Observations on AI/ML for CSI Feedback Enhancement | Indian Institute of Technology Madras (IITM), IIT Kanpur, CEWiT |
R1-2308340 | Summary#1 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308341 | Summary#2 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308342 | Summary#3 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308343 | Summary#4 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308344 | Summary#5 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308345 | Summary#6 for CSI evaluation of [114-R18-AI/ML] | Moderator (Huawei) |
R1-2308682 | Evaluation results of AI/ML for CSI feedback enhancement | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306432 | Discussion on other aspects of AI/ML for CSI feedback enhancement | FUTUREWEI |
R1-2306476 | AI and ML for CSI feedback enhancement | NVIDIA |
R1-2306512 | Discussion on AI/ML for CSI feedback enhancement | Huawei, HiSilicon |
R1-2306605 | Discussions on AI-CSI | Ericsson |
R1-2306638 | Discussion on other aspects on AIML for CSI feedback | Spreadtrum Communications |
R1-2306741 | Other aspects on AI/ML for CSI feedback enhancement | vivo |
R1-2306796 | Discussion on other aspects for AI CSI feedback enhancement | ZTE |
R1-2306833 | Discussion on AI/ML for CSI feedback | Intel Corporation |
R1-2306898 | Discussion on AI/ML for CSI feedback | SEU |
R1-2306903 | Considerations on CSI measurement enhancements via AI/ML | Sony |
R1-2306945 | Discussion on AI/ML for CSI feedback enhancement | NEC |
R1-2306958 | On Enhancement of AI/ML based CSI | |
R1-2307004 | Discussion on AI/ML for CSI feedback enhancement | Panasonic |
R1-2307014 | Other aspects on AI/ML for CSI feedback enhancement | LG Electronics |
R1-2307077 | Discussion on other aspects for AI/ML CSI feedback enhancement | CATT |
R1-2307155 | Views on specification impact for CSI feedback enhancement | Fujitsu |
R1-2307184 | Discussion on other aspects on AI/ML for CSI feedback enhancement | CMCC |
R1-2307239 | Other aspects on ML for CSI feedback enhancement | Nokia, Nokia Shanghai Bell |
R1-2307252 | Discussion on AI/ML for CSI feedback enhancement | InterDigital, Inc. |
R1-2307269 | Discussion on other aspects of AI/ML for CSI enhancement | Apple |
R1-2307376 | Remained issues discussion on specification impact for CSI feedback based on AI/ML | xiaomi |
R1-2307467 | Discussion on other aspects on AI/ML for CSI feedback enhancement | NTT DOCOMO, INC. |
R1-2307565 | On sub use cases and other aspects of AI/ML for CSI feedback enhancement | OPPO |
R1-2307618 | Discussion on AI/ML for CSI feedback enhancement | China Telecom |
R1-2307634 | Discussion on AI/ML based methods for CSI feedback enhancement | Fraunhofer IIS, Fraunhofer HHI |
R1-2307669 | Discussion on potential specification impact for CSI feedback enhancement | Samsung |
R1-2307740 | Discussion on other aspects on AI/ML for CSI feedback enhancement | ETRI |
R1-2307807 | Further aspects of AI/ML for CSI feedback | Lenovo |
R1-2307862 | Discussions on AI-ML for CSI feedback | CAICT |
R1-2307887 | Discussion on AI/ML for CSI feedback enhancement | AT&T |
R1-2307917 | Other aspects on AI/ML for CSI feedback enhancement | Qualcomm Incorporated |
R1-2307996 | Varying CSI feedback granularity based on channel conditions | Rakuten Symphony |
R1-2308020 | Discussions on CSI measurement enhancement for AI/ML communication | TCL |
R1-2308052 | Other aspects on AI/ML for CSI feedback enhancement | MediaTek Inc. |
R1-2308090 | Other aspects on AI/ML for CSI feedback enhancement | IIT Kanpur, Indian Institute of Tech (M) |
R1-2308099 | Other aspects on AI/ML for CSI feedback enhancement | ITL |
R1-2308159 | Discussions on Other Aspects on AI/ML for CSI Feedback Enhancement | Indian Institute of Technology Madras (IITM), IIT Kanpur, CEWiT |
R1-2308243 | Summary #1 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2308244 | Summary #2 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2308245 | Summary #3 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2308246 | Summary #4 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
R1-2308247 | Summary #5 on other aspects of AI/ML for CSI enhancement | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2306420 | Evaluation methodology and results on AI/ML for beam management | Keysight Technologies UK Ltd |
R1-2306433 | Discussion on evaluation of AI/ML for beam management | FUTUREWEI |
R1-2306477 | Evaluation of AI and ML for beam management | NVIDIA |
R1-2306513 | Evaluation on AI/ML for beam management | Huawei, HiSilicon |
R1-2306639 | Evaluation on AI/ML for beam management | Spreadtrum Communications |
R1-2306689 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
R1-2306742 | Evaluation on AI/ML for beam management | vivo |
R1-2306797 | Evaluation on AI beam management | ZTE |
R1-2306808 | Evaluation methodology and results on AI/ML for beam management | BJTU |
R1-2306810 | Evaluation on AI/ML for beam management | China Telecom |
R1-2306856 | Evaluation of AI/ML for Beam Management | Intel Corporation |
R1-2306930 | Evaluation of AIML for beam management | Ericsson |
R1-2306959 | On Evaluation of AI/ML based Beam Management | |
R1-2307015 | Evaluation on AI/ML for beam management | LG Electronics |
R1-2307078 | Evaluation and discussion on AI/ML for beam management | CATT |
R1-2307156 | Evaluation on AI/ML for beam management | Fujitsu |
R1-2307185 | Discussion on evaluation on AI/ML for beam management | CMCC |
R1-2307240 | Evaluation of ML for beam management | Nokia, Nokia Shanghai Bell |
R1-2307270 | Evaluation for AI/ML based beam management enhancements | Apple |
R1-2307377 | Evaluation on AI/ML for beam management | xiaomi |
R1-2307468 | Discussion on evaluation on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2307566 | Evaluation methodology and results on AI/ML for beam management | OPPO |
R1-2307670 | Evaluation on AI/ML for Beam management | Samsung |
R1-2307741 | Evaluation on AI/ML for beam management | ETRI, LG Uplus |
R1-2307808 | Evaluation on AI/ML for beam management | Lenovo |
R1-2307918 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
R1-2308000 | Evaluation on AI/ML for beam management | CEWiT |
R1-2308054 | Evaluation on AI/ML for beam management | MediaTek Inc. |
R1-2308188 | Evaluation on AI/ML for beam management | New H3C Technologies Co., Ltd. |
R1-2308200 | Evaluation on AI/ML for beam management | BUPT |
R1-2308201 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
R1-2308259 | Evaluation on AI/ML for beam management | Qualcomm Incorporated |
R1-2308260 | Evaluation for AI/ML based beam management enhancements | Apple |
R1-2308318 | Feature lead summary #0 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2308319 | Feature lead summary #1 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2308320 | Feature lead summary #2 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2308321 | Feature lead summary #3 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2308327 | Evaluation on AI/ML for beam management | BUPT |
R1-2308346 | Discussion for evaluation on AI/ML for beam management | InterDigital, Inc. |
R1-2308585 | Feature lead summary #4 evaluation of AI/ML for beam management | Moderator (Samsung) |
R1-2308680 | Evaluation results for AI/ML in BM | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2306399 | Discussion on other aspects of AI/ML beam management | New H3C Technologies Co., Ltd. |
R1-2306434 | Discussion on other aspects of AI/ML for beam management | FUTUREWEI |
R1-2306478 | AI and ML for beam management | NVIDIA |
R1-2306514 | Discussion on AI/ML for beam management | Huawei, HiSilicon |
R1-2306640 | Other aspects on AI/ML for beam management | Spreadtrum Communications |
R1-2306690 | Discussion for other aspects on AI/ML for beam management | InterDigital, Inc. |
R1-2306743 | Other aspects on AI/ML for beam management | vivo |
R1-2306798 | Discussion on other aspects for AI beam management | ZTE |
R1-2306857 | Other Aspects on AI/ML for Beam Management | Intel Corporation |
R1-2306904 | Considerations on AI/ML for beam management | Sony |
R1-2306929 | Discussion on AI/ML for beam management | Ericsson |
R1-2306960 | On Enhancement of AI/ML based Beam Management | |
R1-2307016 | Other aspects on AI/ML for beam management | LG Electronics |
R1-2307079 | Discussion on other aspects for AI/ML beam management | CATT |
R1-2307137 | Discussion on AI ML for beam management | NEC |
R1-2307157 | Discussion for specification impacts on AI/ML for beam management | Fujitsu |
R1-2307186 | Discussion on other aspects on AI/ML for beam management | CMCC |
R1-2307233 | Discussion on AI/ML for beam management | Panasonic |
R1-2307241 | Other aspects on ML for beam management | Nokia, Nokia Shanghai Bell |
R1-2307271 | Discussion on other aspects of AI/ML based beam management enhancements | Apple |
R1-2307378 | Potential specification impact on AI/ML for beam management | xiaomi |
R1-2307469 | Discussion on other aspects on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2307567 | Other aspects of AI/ML for beam management | OPPO |
R1-2307671 | Discussion on potential specification impact for beam management | Samsung |
R1-2307730 | Prediction of untransmitted beams in a UE-side AI-ML model | Rakuten Symphony |
R1-2307742 | Discussion on other aspects on AI/ML for beam management | ETRI |
R1-2307809 | Further aspects of AI/ML for beam management | Lenovo |
R1-2307863 | Discussions on AI-ML for Beam management | CAICT |
R1-2307867 | Discussion on other aspects on AI/ML for beam management | KT Corp. |
R1-2307919 | Other aspects on AI/ML for beam management | Qualcomm Incorporated |
R1-2308055 | Other aspects on AI/ML for beam management | MediaTek Inc. |
R1-2308160 | Discussion on other aspects of AI/ML for beam management | Indian Institute of Technology Madras (IITM), IIT Kanpur, CEWiT |
R1-2308261 | Discussion on other aspects of AI/ML based beam management enhancements | Apple |
R1-2308313 | Summary#1 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2308314 | Summary#2 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2308315 | Summary#3 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2308316 | Summary#4 for other aspects on AI/ML for beam management | Moderator (OPPO) |
R1-2308317 | Summary#5 for other aspects on AI/ML for beam management | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2306454 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Ericsson |
R1-2306479 | Evaluation of AI and ML for positioning enhancement | NVIDIA |
R1-2306515 | Evaluation on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2306744 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
R1-2306799 | Evaluation on AI positioning enhancement | ZTE |
R1-2306811 | Evaluation on AI/ML for positioning accuracy enhancement | China Telecom |
R1-2306961 | On Evaluation of AI/ML based Positioning | |
R1-2307080 | Evaluation and discussion on AI/ML for positioning accuracy enhancement | CATT |
R1-2307187 | Discussion on evaluation on AI/ML for positioning accuracy enhancement | CMCC |
R1-2307235 | Evaluating the impact of AI/ML on positioning accuracy enhancements | Fraunhofer IIS, Fraunhofer HHI |
R1-2307242 | Evaluation of ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
R1-2307272 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
R1-2307379 | Evaluation on AI/ML for positioning accuracy enhancement | xiaomi |
R1-2307568 | Evaluation methodology and results on AI/ML for positioning accuracy enhancement | OPPO |
R1-2307582 | Evaluation on AI/ML for positioning accuracy enhancement | InterDigital, Inc. |
R1-2307672 | Evaluation on AI/ML for Positioning | Samsung |
R1-2307810 | Discussion on AI/ML Positioning Evaluations | Lenovo |
R1-2307920 | Evaluation on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
R1-2308056 | Evaluation of AIML for Positioning Accuracy Enhancement | MediaTek Inc. |
R1-2308161 | Evaluation of AI/ML for Positioning Accuracy Enhancement | Indian Institute of Technology Madras (IITM), IIT Kanpur, CEWiT |
R1-2308205 | Evaluation and discussion on AI/ML for positioning accuracy enhancement | CATT |
R1-2308248 | Evaluation on AI/ML for positioning accuracy enhancement | Apple |
R1-2308330 | Evaluation on AI/ML for positioning accuracy enhancement | China Telecom |
R1-2308337 | Evaluation on AI/ML for positioning accuracy enhancement | vivo |
R1-2308355 | Summary #1 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308356 | Summary #2 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308357 | Summary #3 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308358 | Summary #4 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308359 | Summary #5 of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308628 | Final summary of Evaluation on AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2308683 | Evaluation results of AI/ML for positioning accuracy enhancement | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2306418 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | New H3C Technologies Co., Ltd. |
R1-2306455 | Other Aspects of AI/ML Based Positioning Enhancement | Ericsson |
R1-2306480 | AI and ML for positioning enhancement | NVIDIA |
R1-2306516 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2306641 | Discussion on other aspects on AIML for positioning accuracy enhancement | Spreadtrum Communications |
R1-2306745 | Other aspects on AI/ML for positioning accuracy enhancement | vivo |
R1-2306800 | Discussion on other aspects for AI positioning enhancement | ZTE |
R1-2306905 | Remaining issues on AI/ML for positioning accuracy enhancement | Sony |
R1-2306962 | On Enhancement of AI/ML based Positioning | |
R1-2307017 | Other aspects on AI/ML for positioning accuracy enhancement | LG Electronics |
R1-2307081 | Discussion on other aspects for AI/ML positioning accuracy enhancement | CATT |
R1-2307133 | Discussion on AI/ML for positioning accuracy enhancement | NEC |
R1-2307158 | Discussions on specification impacts for AIML positioning accuracy enhancement | Fujitsu |
R1-2307188 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | CMCC |
R1-2307236 | On potential AI/ML solutions for positioning | Fraunhofer IIS, Fraunhofer HHI |
R1-2307243 | Other aspects on ML for positioning accuracy enhancement | Nokia, Nokia Shanghai Bell |
R1-2307273 | On Other aspects on AI/ML for positioning accuracy enhancement | Apple |
R1-2307342 | Other aspects on AI-ML for positioning accuracy enhancement | Baicells |
R1-2307380 | Views on the other aspects of AI/ML-based positioning accuracy enhancement | xiaomi |
R1-2307470 | Discussion on other aspects on AI/ML for positioning accuracy enhancement | NTT DOCOMO, INC. |
R1-2307569 | On sub use cases and other aspects of AI/ML for positioning accuracy enhancement | OPPO |
R1-2307583 | Designs and potential specification impacts of AIML for positioning | InterDigital, Inc. |
R1-2307673 | Discussion on potential specification impact for Positioning | Samsung |
R1-2307811 | AI/ML Positioning use cases and associated Impacts | Lenovo |
R1-2307864 | Discussions on AI-ML for positioning accuracy enhancement | CAICT |
R1-2307921 | Other aspects on AI/ML for positioning accuracy enhancement | Qualcomm Incorporated |
R1-2308057 | Other Aspects on AI ML Based Positioning Enhancement | MediaTek Inc. |
R1-2308254 | FL summary #1 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2308255 | FL summary #2 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
R1-2308256 | FL summary #3 of other aspects on AI/ML for positioning accuracy enhancement | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2307190 | TP on section 7.3 performance evaluation results for semi-static SBFD for TR 38.858 | CMCC |
R1-2307191 | TP on Annex B.2 system level simulation results for semi-static SBFD for TR 38.858 | CMCC |
R1-2308229 | TP on section 7.3 performance evaluation results for semi-static SBFD for TR 38.858 | CMCC |
R1-2308230 | TP on Annex B.2 system level simulation results for semi-static SBFD for TR 38.858 | CMCC |
R1-2308675 | TR 38.858 v0.5.0 for study on evolution of NR duplex operation | Rapporteur (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2306400 | Discussion for Evaluation on NR duplex evolution | New H3C Technologies Co., Ltd. |
R1-2306542 | Discussion on evaluation and methodologies on evolution of NR duplex operation | Huawei, HiSilicon |
R1-2306642 | Discussion on evaluation on NR duplex evolution | Spreadtrum Communications, BUPT, New H3C |
R1-2306695 | Discussion on evaluations on NR duplex evolution | InterDigital, Inc. |
R1-2306746 | Evaluation on NR duplex evolution | vivo |
R1-2306814 | Discussion on evaluation of NR duplex evolution | MediaTek Inc. |
R1-2306835 | Evaluations on NR Duplex Evolution | Intel Corporation |
R1-2306874 | On the evaluation methodology for NR duplexing enhancements | Nokia, Nokia Shanghai Bell |
R1-2306885 | Study on Evaluation for NR duplex evolution | LG Electronics |
R1-2306906 | SBFD System Level Simulation Results | Sony |
R1-2306981 | Prototype and Simulation Results for SBFD | ZTE |
R1-2307083 | SBFD evaluation results | CATT |
R1-2307159 | Evaluation on NR duplex evolution | Fujitsu |
R1-2307189 | TP on evaluation methodology and assumptions for TR 38.858 | CMCC |
R1-2307192 | Evaluation on NR duplex evolution | CMCC |
R1-2307274 | On evaluations for NR duplex evolution | Apple |
R1-2307324 | Evaluation of NR duplex evolution | Ericsson |
R1-2307330 | Discussion on evaluation on NR duplex evolution | Panasonic |
R1-2307381 | Discussion on evaluation on NR duplex evolution | xiaomi |
R1-2307471 | Discussion on evaluation on NR duplex evolution | NTT DOCOMO, INC. |
R1-2307571 | Discussion on evaluation on NR duplex evolution | OPPO |
R1-2307674 | Discussion on evaluation for NR duplex evolution | Samsung |
R1-2307817 | Evaluation of NR duplex evolution | Sharp |
R1-2307922 | On Deployment scenarios and evaluation Methodology for NR duplex evolution | Qualcomm Incorporated |
R1-2308001 | LLS for evaluation of coverage performance in TDD and SBFD systems | CEWiT |
R1-2308101 | Evaluation on NR duplex operation | China Unicom, Huawei, HiSilicon |
R1-2308326 | Discussion on evaluation on NR duplex evolution | xiaomi |
R1-2308336 | Discussion on evaluation and methodologies on evolution of NR duplex operation | Huawei, HiSilicon |
R1-2308397 | Summary#1 on evaluation on NR duplex evolution | Moderator (Samsung) |
R1-2308408 | Study on Evaluation for NR duplex evolution | LG Electronics |
R1-2308424 | Summary#2 on evaluation on NR duplex evolution | Moderator (Samsung) |
R1-2308498 | Summary#3 on evaluation on NR duplex evolution | Moderator (Samsung) |
R1-2308528 | TP on CLI handling for SBFD for TR38.858 | Moderator (Samsung) |
R1-2308529 | TP on Annex B.3.2 for TR38.858 | Moderator (Samsung) |
R1-2308614 | TP Conclusion of Semi-static SBFD for TR38.858 | Moderator (Samsung) |
R1-2308615 | Final Summary of Evaluation on NR duplex | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2306401 | Discussion for subband non-overlapping full duplex | New H3C Technologies Co., Ltd. |
R1-2306543 | Discussion on potential enhancement on subband non-overlapping full duplex | Huawei, HiSilicon |
R1-2306557 | Discussions on subband non-overlapping full duplex | Ruijie Network Co. Ltd |
R1-2306643 | Discussion on subband non-overlapping full duplex | Spreadtrum Communications |
R1-2306680 | Discussion on subband non-overlapping full duplex | TCL |
R1-2306696 | Discussion on subband non-overlapping full duplex operations | InterDigital, Inc. |
R1-2306747 | Discussion on subband non-overlapping full duplex | vivo |
R1-2306815 | Discussion on subband non-overlapping full duplex for NR | MediaTek Inc. |
R1-2306836 | On SBFD in NR systems | Intel Corporation |
R1-2306875 | On subband non-overlapping full duplex for NR | Nokia, Nokia Shanghai Bell |
R1-2306886 | Study on Subband non-overlapping full duplex | LG Electronics |
R1-2306907 | Remaining issues on Subband Full Duplex TDD operations | Sony |
R1-2306942 | Discussion on subband non-overlapping full duplex | NEC |
R1-2306982 | Discussion of subband non-overlapping full duplex | ZTE |
R1-2307082 | TP on SBFD for TR38.858 | CATT, CMCC, Samsung |
R1-2307084 | Discussion on subband non-overlapping full duplex | CATT |
R1-2307160 | Discussion on subband non-overlapping full duplex | Fujitsu |
R1-2307193 | Discussion on subband non-overlapping full duplex | CMCC |
R1-2307275 | Views on subband non-overlapping full duplex | Apple |
R1-2307325 | Subband non-overlapping full duplex | Ericsson |
R1-2307331 | Discussion on subband non-overlapping full duplex | Panasonic |
R1-2307333 | TP on section 7.4.1 performance evaluation results for dynamic SBFD for TR 38.858 | CATT |
R1-2307334 | TP on Annex B.3.1 SLS results for dynamic SBFD for TR 38.858 | CATT |
R1-2307382 | Discussion on subband non-overlapping full duplex | xiaomi |
R1-2307422 | Coverage enhancement aspects on subband non-overlapping full duplex | SK Telecom, LG Uplus, Nokia, LG Electronics |
R1-2307472 | Discussion on subband non-overlapping full duplex | NTT DOCOMO, INC. |
R1-2307572 | Discussion on subband non-overlapping full duplex | OPPO |
R1-2307675 | On SBFD for NR duplex evolution | Samsung |
R1-2307743 | Discussion on subband non-overlapping full duplex enhancements | ETRI |
R1-2307812 | Subband non-overlapping full duplex | Lenovo |
R1-2307818 | Discussion on subband non-overlapping full duplex | Sharp |
R1-2307890 | Discussion on sub-band non-overlapping full duplex | ITRI |
R1-2307923 | Feasibility and techniques for Subband non-overlapping full duplex | Qualcomm Incorporated |
R1-2308002 | Discussion on subband non-overlapping full duplex | CEWiT |
R1-2308026 | Discussion on subband non-overlapping full duplex | KT Corp. |
R1-2308104 | Details of subband non-overlapping full duplex | ASUSTeK |
R1-2308115 | Discussion on subband non-overlapping full duplex | WILUS Inc. |
R1-2308258 | TP on SBFD for TR38.858 | CATT, CMCC, Samsung |
R1-2308302 | Summary #1 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2308303 | Summary #2 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2308304 | Summary #3 of subband non-overlapping full duplex | Moderator (CATT) |
R1-2308385 | TP on Annex B.3.1 SLS results for dynamic SBFD for TR 38.858 | Moderator (CATT) |
R1-2308457 | TP on section 7.4.1 performance evaluation results for dynamic SBFD for TR 38.858 | Moderator (CATT) |
R1-2308464 | TP on SBFD for TR 38.858 section 6 and section 13 | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2306402 | Discussion on potential enhancement on dynamic/flexible TDD | New H3C Technologies Co., Ltd. |
R1-2306544 | Study on potential enhancements on dynamic/flexible TDD | Huawei, HiSilicon |
R1-2306644 | Discussion on potential enhancements on dynamic/flexible TDD | Spreadtrum Communications |
R1-2306681 | Potential enhancement on dynamic/flexible TDD | TCL |
R1-2306697 | Discussion on potential enhancements on dynamic/flexible TDD | InterDigital, Inc. |
R1-2306748 | Potential enhancements on dynamic/flexible TDD | vivo |
R1-2306816 | Discussion on potential enhancements for dynamic/flexible TDD | MediaTek Inc. |
R1-2306837 | On Dynamic/Flexible TDD enhancements | Intel Corporation |
R1-2306876 | Dynamic TDD enhancements | Nokia, Nokia Shanghai Bell |
R1-2306887 | Study on Potential enhancements on dynamic/flexible TDD | LG Electronics |
R1-2306908 | Remaining issues on Dynamic/Flexible TDD | Sony |
R1-2306941 | Views on enhancements of dynamic/flexible TDD | NEC |
R1-2306983 | Discussion of enhancements on dynamic/flexible TDD | ZTE, China Telecom |
R1-2307085 | Discussion on potential enhancements on dynamic/flexible TDD | CATT |
R1-2307194 | Discussion on potential enhancements on dynamic/flexible TDD | CMCC |
R1-2307276 | Views on potential enhancements on dynamic TDD | Apple |
R1-2307326 | Potential enhancements of dynamic TDD | Ericsson |
R1-2307340 | Discussion on potential enhancements on dynamic/flexible TDD | Panasonic |
R1-2307383 | Discussion on potential enhancements on dynamic/flexible TDD | xiaomi |
R1-2307411 | Potential enhancements on dynamic/flexible TDD | Lenovo |
R1-2307473 | Discussion on potential enhancements on dynamic/flexible TDD | NTT DOCOMO, INC. |
R1-2307573 | Discussion on potential enhancements on dynamic/flexible TDD | OPPO |
R1-2307619 | Field test for dynamic/flexible TDD | China Telecom, ZTE |
R1-2307676 | Dynamic and flexible TDD for NR duplex evolution | Samsung |
R1-2307924 | On potential enhancements on dynamic/flexible TDD | Qualcomm Incorporated |
R1-2308003 | Discussion on enhancements on dynamic/flexible TDD | CEWiT |
R1-2308116 | Discussion on potential enhancements on dynamic/flexible TDD | WILUS Inc. |
R1-2308185 | Draft TP on section 8.3 and 8.4 CLI handling schemes for TR 38.858 | LG Electronics |
R1-2308186 | Draft TP on section 8.3 performance evaluation result for TR 38.858 | LG Electronics |
R1-2308187 | Draft TP on Annex B.4 SLS results for dynamic TDD for TR 38.858 | LG Electronics |
R1-2308368 | Summary #1 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2308369 | Summary #2 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2308370 | Summary #3 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2308371 | Summary #4 of potential enhancement on dynamic/flexible TDD | Moderator (LG Electronics) |
R1-2308372 | TP on section 8.3 and 8.4 CLI handling schemes for TR 38.858 | Moderator (LG Electronics) |
R1-2308373 | TP on section 8.3 performance evaluation result for TR 38.858 | Moderator (LG Electronics) |
R1-2308374 | TP on Annex B.4 SLS results for dynamic TDD for TR 38.858 | Moderator (LG Electronics) |
R1-2308412 | TP on section 8.3 performance evaluation result for TR 38.858 | Moderator (LG Electronics) |
R1-2308470 | TP on section 8.3 performance evaluation result for TR 38.858 | Moderator (LG Electronics) |
R1-2308533 | TP on Annex B.4 SLS results for dynamic TDD for TR 38.858 | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2307531 | Higher layer parameters list for Rel-18 NR sidelink evolution WI | OPPO, Huawei, HiSilicon, LG Electronics |
R1-2308277 | FL summary #1 for AI 9.4: Higher layer parameters for R18 SL-Evo | Moderator (OPPO, Huawei, HiSilicon, LG Electronics) |
R1-2308278 | FL summary #2 for AI 9.4: Higher layer parameters for R18 SL-Evo | Moderator (OPPO, Huawei, HiSilicon, LG Electronics) |
R1-2308279 | FL summary for AI 9.4: Higher layer parameters for R18 SL-Evo (EOM) | Moderator (OPPO, Huawei, HiSilicon, LG Electronics) |
R1-2308544 | Session notes for 9.4 (NR sidelink evolution) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306439 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | FUTUREWEI |
R1-2306446 | On Channel Access Mechanism for SL-U | Nokia, Nokia Shanghai Bell |
R1-2306457 | SL-U Channel Acces Mechanism Discussion | CableLabs |
R1-2306521 | Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
R1-2306645 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | Spreadtrum Communications |
R1-2306749 | Channel access mechanism for sidelink on unlicensed spectrum | vivo |
R1-2306791 | Discussion on channel access mechanism for SL-U | KRRI |
R1-2306817 | Discussion on Channel Access Mechanisms | Johns Hopkins University APL |
R1-2306909 | Discussion on channel access mechanism for SL-unlicensed | Sony |
R1-2307086 | Remaining issues on channel access mechanism for sidelink on unlicensed spectrum | CATT, GOHIGH |
R1-2307111 | Channel Access of Sidelink on Unlicensed Spectrum | NEC |
R1-2307161 | Discussion on channel access mechanism for SL-U | Fujitsu |
R1-2307195 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | CMCC |
R1-2307226 | Channel access mechanism for sidelink on FR1 unlicensed spectrum | Lenovo |
R1-2307277 | Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum | Apple |
R1-2307384 | Remaining issues on SL-U channel access mechanism | xiaomi |
R1-2307426 | Discussion on channel access mechanism for NR sidelink evolution | Sharp |
R1-2307474 | Discussion on channel access mechanism in SL-U | NTT DOCOMO, INC. |
R1-2307532 | Remaining issues on SL-U channel access mechanism and resource allocation | OPPO |
R1-2307599 | Discussion on channel access mechanism for SL-U | ZTE, Sanechips |
R1-2307630 | Sidelink channel access on unlicensed spectrum | Panasonic |
R1-2307677 | On channel access mehanism for sidelink on FR1 unlicensed spectrum | Samsung |
R1-2307744 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | ETRI |
R1-2307761 | Discussion of channel access mechanism for sidelink in unlicensed spectrum | Transsion Holdings |
R1-2307782 | Sidelink channel access on unlicensed spectrum | InterDigital, Inc. |
R1-2307865 | Considerations on channel access mechanism of SL-U | CAICT |
R1-2307925 | Channel Access Mechanism for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
R1-2307974 | Discussion on channel access mechanism for sidelink on unlicensed spectrum | LG Electronics |
R1-2308023 | NR Sidelink Unlicensed Channel Access Mechanisms | Fraunhofer HHI, Fraunhofer IIS |
R1-2308074 | Discussion on channel access mechanism | MediaTek Inc. |
R1-2308100 | Channel Access Mechanism for SL-U | ITL |
R1-2308107 | Channel access mechanism for SL-U | Ericsson |
R1-2308117 | Discussion on channel access mechanism for SL-U | WILUS Inc. |
R1-2308280 | FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2308281 | FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2308282 | FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2308283 | FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2308284 | FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism | Moderator (OPPO) |
R1-2308285 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) | Moderator (OPPO) |
R1-2308631 | Draft LS on resource selection for MCSt | Moderator (OPPO) |
R1-2308632 | FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM2) | Moderator (OPPO) |
R1-2308664 | LS on resource selection for MCSt | RAN1, OPPO |
TDoc | Title | Source |
---|---|---|
R1-2306440 | Discussion on physical channel design for sidelink on unlicensed spectrum | FUTUREWEI |
R1-2306447 | On Physical Channel Design Framework for SL-U | Nokia, Nokia Shanghai Bell |
R1-2306522 | Physical channel design for sidelink operation over unlicensed spectrum | Huawei, HiSilicon |
R1-2306646 | Discussion on Physical channel design for sidelink on unlicensed spectrum | Spreadtrum Communications |
R1-2306750 | Physical channel design framework for sidelink on unlicensed spectrum | vivo |
R1-2306792 | Discussion on physical channel design framework for SL-U | KRRI |
R1-2306910 | Discussion on physical channel design framework for SL-unlicensed | Sony |
R1-2307087 | Remaining issues on physical channel design framework for sidelink on unlicensed spectrum | CATT, GOHIGH |
R1-2307113 | Discussion on physical channel design framework | NEC |
R1-2307196 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | CMCC |
R1-2307227 | Physical layer design framework for sidelink on FR1 unlicensed spectrum | Lenovo |
R1-2307278 | On Sidelink Physical Channel Design Framework for Unlicensed Spectrum | Apple |
R1-2307385 | Remaining issues on SL-U physical channel structures and procedures | xiaomi |
R1-2307427 | Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum | Sharp |
R1-2307475 | Discussion on channel design framework in SL-U | NTT DOCOMO, INC. |
R1-2307533 | Remaining issues on SL-U PHY channel designs and procedures | OPPO |
R1-2307600 | Discussion on physical layer structures and procedures for SL-U | ZTE, Sanechips |
R1-2307631 | Physical channel design for sidelink on unlicensed spectrum | Panasonic |
R1-2307678 | On physical channel design framework for sidelink on FR1 unlicensed spectrum | Samsung |
R1-2307745 | Discussion on physical channel design framework for SL-U | ETRI |
R1-2307762 | Discussion of physical channel design for sidelink in unlicensed spectrum | Transsion Holdings |
R1-2307783 | SL U physical layer design framework | InterDigital, Inc. |
R1-2307860 | Discussion on channel design for SL-U | ASUSTeK |
R1-2307926 | Physical Channel Design for Sidelink on Unlicensed Spectrum | Qualcomm Incorporated |
R1-2307975 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
R1-2308024 | NR Sidelink Unlicensed Physical Channel Design | Fraunhofer HHI, Fraunhofer IIS |
R1-2308075 | Discussion on physical channel design framework | MediaTek Inc. |
R1-2308108 | PHY channel design framework for SL-U | Ericsson |
R1-2308118 | Discussion on PHY channel design framework for SL-U | WILUS Inc. |
R1-2308207 | Discussion on physical channel design framework for sidelink on unlicensed spectrum | LG Electronics |
R1-2308262 | FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308263 | FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308264 | FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308265 | FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308266 | FL summary#5 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308267 | FL summary#6 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
R1-2308591 | FL summary#7 for AI 9.4.1.2 SL-U physical channel design framework | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306448 | On Co-channel Coexistence for LTE Sidelink and NR Sidelink | Nokia, Nokia Shanghai Bell |
R1-2306751 | Co-channel coexistence for LTE sidelink and NR sidelink | vivo |
R1-2307088 | Remaining issues on co-channel coexistence for LTE sidelink and NR sidelink | CATT, GOHIGH |
R1-2307279 | On Higher Layer Signalling Related to Co-channel Coexistence | Apple |
R1-2307386 | Discussion on co-channel coexistence for LTE and NR sidelink | xiaomi |
R1-2307428 | Discussion on co-channel coexistence for LTE sidelink and NR sidelink | Sharp |
R1-2307534 | Discussion on higher layer parameter for co-channel coexistence | OPPO |
R1-2307601 | Higher layer signaling for NR sidelink and LTE sidelink co-channel coexistence | ZTE, Sanechips |
R1-2307679 | Remaining details on co-channel coexistence for LTE sidelink and NR sidelink | Samsung |
R1-2307784 | Co-channel coexistence for LTE sidelink and NR sidelink | InterDigital, Inc. |
R1-2307927 | Co-channel Coexistence Between LTE SL and NR SL | Qualcomm Incorporated |
R1-2308109 | Discussion on co-channel coexistence between LTE sidelink and NR sidelink | Ericsson |
R1-2308141 | Co-channel coexistence for LTE sidelink and NR sidelink | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R1-2306449 | On Beam Management for Sidelink in FR2 | Nokia, Nokia Shanghai Bell |
R1-2306523 | Enhanced sidelink operation on FR2 licensed spectrum | Huawei, HiSilicon |
R1-2306647 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Spreadtrum Communications |
R1-2306685 | Discussion on sidelink beam management on FR2 licensed spectrum | TOYOTA InfoTechnology Center |
R1-2306752 | Enhanced sidelink operation on FR2 licensed spectrum | vivo |
R1-2306818 | Discussion on Enhanced Sidelink Operation on FR2 Licensed Spectrum | Johns Hopkins University APL |
R1-2306847 | On Sidelink Operation in FR2 Licensed Spectrum | Intel Corporation |
R1-2306911 | Discussion on sidelink beam management on FR2 licensed spectrum | Sony |
R1-2307089 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | CATT |
R1-2307114 | Discussion on sidelink operation on FR2 licensed spectrum | NEC |
R1-2307197 | Discussion on sidelink enhancements on FR2 licensed spectrum | CMCC |
R1-2307228 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Lenovo |
R1-2307280 | On Sidelink Operation on FR2 | Apple |
R1-2307387 | Discussion on SL beam management in FR2 licensed spectrum | xiaomi |
R1-2307429 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | Sharp |
R1-2307476 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | NTT DOCOMO, INC. |
R1-2307535 | On sidelink beam management in FR2 | OPPO |
R1-2307602 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | ZTE, Sanechips |
R1-2307680 | On enhanced SL Operation in FR2 | Samsung |
R1-2307746 | Discussion on enhanced SL operation on FR2 licensed spectrum | ETRI |
R1-2307781 | On beam failure indication for sidelink operation on FR2 licensed spectrum | Continental Automotive |
R1-2307785 | On enhanced SL FR2 operation | InterDigital, Inc. |
R1-2307928 | Enhanced sidelink operation on FR2 licensed spectrum | Qualcomm Incorporated |
R1-2307976 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | LG Electronics |
R1-2308004 | Views on beam enhancement procedures for sidelink FR2 operation | CEWiT |
R1-2308025 | Sidelink Operation in FR2 | Fraunhofer HHI, Fraunhofer IIS |
R1-2308076 | Discussion on SL operation on FR2 | MediaTek Inc. |
R1-2308110 | Study aspects for sidelink in FR2 licensed spectrum | Ericsson |
R1-2308119 | Discussion on enhanced sidelink operation on FR2 licensed spectrum | WILUS Inc. |
R1-2308299 | FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
R1-2308300 | FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
R1-2308301 | FL summary #3 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
R1-2308605 | FL summary #4 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2306450 | On Sidelink Carrier Aggregation for NR | Nokia, Nokia Shanghai Bell |
R1-2306524 | Sidelink CA operation | Huawei, HiSilicon |
R1-2306648 | Discussion on Sidelink CA operation | Spreadtrum Communications |
R1-2306753 | Discussion on Rel-18 Sidelink CA | vivo |
R1-2306848 | On Sidelink Carrier Agreegation | Intel Corporation |
R1-2307090 | Discussion on NR sidelink CA operation | CATT, GOHIGH |
R1-2307112 | Analysis of Sidelink Carrier Aggregation | NEC |
R1-2307198 | Discussion on sidelink CA operation | CMCC |
R1-2307229 | On Sidelink Carrier Aggregation for NR | Lenovo |
R1-2307281 | On Sidelink Carrier Aggregation Operation | Apple |
R1-2307388 | Discussion on Sidelink CA operation in Rel-18 | xiaomi |
R1-2307430 | Discussion on sidelink CA operation | Sharp |
R1-2307477 | Discussion on Sidelink CA operation | NTT DOCOMO, INC. |
R1-2307536 | Discussion on carrier aggregation in NR Sidelink evolution | OPPO |
R1-2307603 | Discussion on sidelink CA operation | ZTE, Sanechips |
R1-2307681 | On Sidelink CA operation | Samsung |
R1-2307747 | Discussion on sidelink CA operation | ETRI |
R1-2307763 | Discussion of sidelink operation on CA | Transsion Holdings |
R1-2307786 | Sidelink CA operation | InterDigital, Inc. |
R1-2307929 | NR Sidelink Carrier Aggregation | Qualcomm Incorporated |
R1-2307977 | Discussion on sidelink CA operation | LG Electronics |
R1-2307978 | FL Summary #1 for AI 9.4.4: Sidelink CA operation | Moderator (LG Electronics) |
R1-2307979 | FL Summary #2 for AI 9.4.4: Sidelink CA operation | Moderator (LG Electronics) |
R1-2307980 | FL Summary #3 for AI 9.4.4: Sidelink CA operation | Moderator (LG Electronics) |
R1-2308077 | Discussion on SL CA operation | MediaTek Inc. |
R1-2308111 | Discussion on sidelink carrier aggregation operation | Ericsson |
R1-2308120 | Discussion on sidelink CA operation | WILUS Inc. |
R1-2308130 | Views on NR V2 Sidelink CA in Rel-18 | Volkswagen AG |
R1-2308419 | FL Summary #4 for AI 9.4.4: Sidelink CA operation | Moderator (LG Electronics) |
R1-2308420 | FL Summary #5 for AI 9.4.4: Sidelink CA operation | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2306838 | Higher layer parameters for Rel-18 expanded and improved NR Positioning | Rapporteur (Intel Corporation) |
R1-2308483 | FLS on list of RRC parameters on Rel-18 WI on expanded and improved NR positioning | Rapporteur (Intel Corporation) |
R1-2308484 | RAN1 agreements for Rel-18 WI on Expanded and Improved NR Positioning | Rapporteur (Intel Corporation) |
R1-2308545 | Session notes for 9.5 (Expanded and Improved NR Positioning) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306441 | Discussion on SL positioning reference signal | FUTUREWEI |
R1-2306451 | Design of SL positioning reference signal SL-PRS | Nokia, Nokia Shanghai Bell |
R1-2306494 | Finalizing SL-PRS design | Huawei, HiSilicon |
R1-2306558 | Discussions on SL positioning reference signal | Ruijie Network Co. Ltd |
R1-2306649 | Discussion on SL positioning reference signal | Spreadtrum Communications |
R1-2306686 | Discussion on SL positioning reference signal design | TOYOTA InfoTechnology Center |
R1-2306754 | Discussion on SL positioning reference signal | vivo |
R1-2306839 | On SL Positioning Reference Signals | Intel Corporation |
R1-2306862 | Discussion on SL positioning reference signal | ZTE |
R1-2306912 | Remaining issues on SL Positioning Reference Signal | Sony |
R1-2307091 | Remaining issues on SL positioning reference signal | CATT, GOHIGH |
R1-2307123 | Discussion on SL positioning reference signal | NEC |
R1-2307199 | Discussion on SL positioning reference signal | CMCC |
R1-2307282 | On SL positioning reference signal | Apple |
R1-2307389 | Discussion on sidelink positioning reference signal | xiaomi |
R1-2307537 | Discussion on SL positioning reference signal | OPPO |
R1-2307584 | SL-PRS design and power control for SL-PRS | InterDigital, Inc. |
R1-2307620 | Discussion on SL positioning reference signal | China Telecom |
R1-2307682 | On SL Positioning Reference Signal | Samsung |
R1-2307823 | Remaining issues on SL PRS Design | Lenovo |
R1-2307852 | SL positioning reference signal | Sharp |
R1-2307869 | On Muting for Sidelink Positioning Reference Signals | Continental Automotive |
R1-2307930 | Reference Signal Design for SL Positioning | Qualcomm Incorporated |
R1-2307981 | Discussion on SL positioning reference signal | LG Electronics |
R1-2308005 | Further discussion on sidelink positioning reference signal design | CEWiT |
R1-2308017 | Discussion on sidelink positioning reference signal | ASUSTeK |
R1-2308096 | Reference signal design for sidelink positioning | MediaTek Korea Inc. |
R1-2308166 | SL positioning reference signal design | Ericsson |
R1-2308296 | FL summary #1 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2308297 | FL summary #2 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2308298 | FL summary #3 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2308482 | FL summary #4 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2308555 | FL summary #5 on SL positioning reference signal | Moderator (Intel Corporation) |
R1-2308558 | Draft LS on Priority Handling for SL Positioning | Moderator (Intel Corporation) |
R1-2308559 | LS on Priority Handling for SL Positioning | RAN1, Intel Corporation |
TDoc | Title | Source |
---|---|---|
R1-2306442 | Discussion on measurements and reporting for SL positioning | FUTUREWEI |
R1-2306452 | On measurements and reporting for SL positioning | Nokia, Nokia Shanghai Bell |
R1-2306495 | Finalizing SL positioning methods and measurements | Huawei, HiSilicon |
R1-2306559 | Discussions on measurements and reporting for SL positioning | Ruijie Network Co. Ltd |
R1-2306650 | Discussion on measurements and reporting for SL positioning | Spreadtrum Communications |
R1-2306755 | Discussion on measurements and reporting for SL positioning | vivo |
R1-2306840 | On Measurements and Reporting for SL Positioning | Intel Corporation |
R1-2306863 | Discussion on SL positioning measurements and reporting | ZTE |
R1-2306913 | On measurements and reporting for SL positioning | Sony |
R1-2307092 | Remaining issues on measurements and reporting for SL positioning | CATT, GOHIGH |
R1-2307200 | Discussion on measurements and reporting for SL positioning | CMCC |
R1-2307283 | On Measurements and reporting for SL positioning | Apple |
R1-2307390 | Remaining issues on measurements and reporting for SL positioning | xiaomi |
R1-2307538 | Discussion on measurements and reporting for SL positioning | OPPO |
R1-2307585 | Measurement and reporting for SL positioning | InterDigital, Inc. |
R1-2307683 | On Measurements and Reporting for SL Positioning | Samsung |
R1-2307824 | Remaining SL Positioning Measurement and Reporting Issues | Lenovo |
R1-2307853 | Measurements and reporting for SL positioning | Sharp |
R1-2307870 | On Measurements for Sidelink Positioning Congestion Control | Continental Automotive |
R1-2307874 | Discussion on SL positioning measurements and reporting | BUPT |
R1-2307931 | Measurements and Reporting for SL Positioning | Qualcomm Incorporated |
R1-2307982 | Discussion on measurements and reporting for SL positioning | LG Electronics |
R1-2308006 | Discussion on measurements and reporting for SL positioning methods | CEWiT |
R1-2308097 | Measurement and reporting design for sidelink positioning | MediaTek Korea Inc. |
R1-2308167 | Measurements and reporting for SL positioning | Ericsson |
R1-2308360 | Summary #1 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2308361 | Summary #2 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2308362 | Summary #3 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2308363 | Summary #4 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2308666 | Final summary on Measurements and reporting for SL positioning | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2306443 | Discussion on resource allocation for SL PRS | FUTUREWEI |
R1-2306453 | On resource allocation for SL positioning reference signal | Nokia, Nokia Shanghai Bell |
R1-2306496 | Finalizing SL PRS resource allocation | Huawei, HiSilicon |
R1-2306560 | Discussions on resource allocation for SL positioning reference signal | Ruijie Network Co. Ltd |
R1-2306651 | Discussion on resource allocation for SL positioning reference signal | Spreadtrum Communications |
R1-2306687 | Discussion on resource allocation for SL positioning reference signal | TOYOTA InfoTechnology Center |
R1-2306756 | Discussion on resource allocation for SL positioning reference signal | vivo |
R1-2306841 | On Resource Allocation for SL Positioning | Intel Corporation |
R1-2306864 | Discussion on resource allocation for SL positioning reference signal | ZTE |
R1-2306914 | Considerations on resource allocation for SL positioning | Sony |
R1-2307093 | Remaining issues on resource allocation for SL positioning reference signal | CATT, GOHIGH |
R1-2307124 | Discussion on resource allocation for SL positioning reference signal | NEC |
R1-2307201 | Discussion on resource allocation for SL positioning reference signal | CMCC |
R1-2307284 | On Resource allocation for SL positioning reference signal | Apple |
R1-2307391 | Remaining issues on resource allocation for SL positioning reference signal | xiaomi |
R1-2307539 | Discussion on resource allocation for SL positioning reference signal | OPPO |
R1-2307586 | Resource allocation for SL positioning reference signal | InterDigital, Inc. |
R1-2307621 | Discussion on SL positioning reference signal resource allocation | China Telecom |
R1-2307684 | On Resource Allocation for SL Positioning Reference Signal | Samsung |
R1-2307825 | Remaining aspects for SL Positioning Resource Allocation | Lenovo |
R1-2307854 | Resource allocation for SL positioning reference signal | Sharp |
R1-2307858 | Discussion on Resource Allocation for SL-PRS | Panasonic |
R1-2307868 | Considerations on Resource Allocation and Congestion Control for Sidelink Positioning | Continental Automotive |
R1-2307932 | Resource Allocation for SL-PRS | Qualcomm Incorporated |
R1-2307983 | Discussion on resource allocation for SL positioning reference signal | LG Electronics |
R1-2308007 | On SL positioning resource allocation for SL positioning | CEWiT |
R1-2308016 | Discussion on resource allocation for SL PRS | ASUSTeK |
R1-2308098 | Resource allocation for sidelink positioning | MediaTek Korea Inc. |
R1-2308168 | Resource allocation for SL positioning reference signal | Ericsson |
R1-2308184 | Discussions on resource allocation for SL positioning | ITL |
R1-2308367 | Moderator Summary #0 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308423 | Moderator Summary #1 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308426 | Moderator Summary #1 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308471 | Moderator Summary #2 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308479 | Draft LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning | Moderator (Qualcomm) |
R1-2308572 | Moderator Summary #3 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308627 | Moderator Summary #4 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2308651 | LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning | RAN1, Qualcomm |
TDoc | Title | Source |
---|---|---|
R1-2306497 | Remaining issues of carrier phase positioning | Huawei, HiSilicon |
R1-2306573 | Discussions on NR DL and UL carrier phase positioning | Ruijie Network Co. Ltd |
R1-2306652 | Discussion on NR DL and UL carrier phase positioning | Spreadtrum Communications |
R1-2306757 | Discussion on carrier phase positioning | vivo |
R1-2306819 | Views on NR DL and UL carrier phase positioning | Nokia, Nokia Shanghai Bell |
R1-2306842 | On NR DL and UL Carrier Phase Positioning | Intel Corporation |
R1-2306865 | Discussion on carrier phase positioning | ZTE |
R1-2306873 | Remaining issues on NR DL and UL carrier phase positioning | Locaila |
R1-2306888 | Discussion on carrier phase positioning in NR | LG Electronics |
R1-2307094 | Remaining issues on NR DL and UL carrier phase positioning | CATT |
R1-2307202 | Discussion on DL/UL carrier phase positioning | CMCC |
R1-2307285 | On NR DL and UL carrier phase positioning | Apple |
R1-2307392 | NR DL and UL carrier phase positioning | xiaomi |
R1-2307478 | Discussion on NR DL and UL carrier phase positioning | NTT DOCOMO, INC. |
R1-2307522 | Discussions on NR carrier phase positioning | OPPO |
R1-2307587 | Discussion on positioning based on NR carrier phase measurement | InterDigital, Inc. |
R1-2307685 | On NR DL and UL Carrier Phase Positioning | Samsung |
R1-2307826 | Remaining DL/UL CPP Issues | Lenovo |
R1-2307933 | NR Carrier Phase Positioning | Qualcomm Incorporated |
R1-2308093 | Solutions for carrier phase positioning | MediaTek Korea Inc. |
R1-2308113 | Discussion on NR DL/UL carrier phase positioning | IIT Kanpur, CEWiT |
R1-2308169 | NR DL and UL carrier phase positioning | Ericsson |
R1-2308217 | FL Summary #1 for NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2308218 | FL Summary #2 for NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2308219 | FL Summary #3 for NR DL and UL carrier phase positioning | Moderator (CATT) |
R1-2308643 | [Draft] Reply LS on PRU Procedures | CATT |
R1-2308644 | Reply LS on PRU Procedures | RAN1, CATT |
TDoc | Title | Source |
---|---|---|
R1-2306445 | On remaining open issues in LPHAP | FUTUREWEI |
R1-2306498 | Remaining issues of physical layer aspects of LPHAP | Huawei, HiSilicon |
R1-2306653 | Discussion on LPHAP (Low Power High Accuracy Positioning) | Spreadtrum Communications |
R1-2306758 | Discussion on low power high accuracy positioning | vivo |
R1-2306820 | Views on LPHAP | Nokia, Nokia Shanghai Bell |
R1-2306843 | Support of LPHAP in NR | Intel Corporation |
R1-2306866 | Discussion on low power high accuracy positioning | ZTE |
R1-2306878 | Discussion on Low Power High Accuracy Positioning | Quectel |
R1-2306889 | Discussion on LPHAP in idle/inactive state | LG Electronics |
R1-2306915 | On Low Power High Accuracy Positioning | Sony |
R1-2307095 | Remaining issues on Low Power High Accuracy Positioning | CATT |
R1-2307134 | Discussion on Low Power High Accuracy Positioning | NEC |
R1-2307203 | Discussion on low power high accuracy positioning | CMCC |
R1-2307286 | On Low Power High Accuracy Positioning | Apple |
R1-2307393 | Discussion on Low Power High Accuracy Positioning | xiaomi |
R1-2307479 | Discussion on Low Power High Accuracy Positioning | NTT DOCOMO, INC. |
R1-2307524 | Discussion on low power high accuracy positioning | OPPO |
R1-2307588 | Discussions on Low Power High Accuracy Positioning (LPHAP) techniques | InterDigital, Inc. |
R1-2307686 | On Low Power High Accuracy Positioning | Samsung |
R1-2307934 | Discussion on LPHAP Positioning | Qualcomm Incorporated |
R1-2308092 | LPHAP design | MediaTek Korea Inc. |
R1-2308170 | On Low Power High Accuracy Positioning | Ericsson |
R1-2308305 | Summary #1 for low power high accuracy positioning | Moderator (CMCC) |
R1-2308306 | Summary #2 for low power high accuracy positioning | Moderator (CMCC) |
R1-2308307 | Summary #3 for low power high accuracy positioning | Moderator (CMCC) |
R1-2308347 | FLS on LPHAP LS reply | Moderator (Huawei) |
R1-2308348 | Draft reply LS on LPHAP | Huawei |
R1-2308349 | Reply LS on LPHAP | RAN1, Huawei |
R1-2308570 | Draft LS on the longer PRS/SRS periodicity for LPHAP | Moderator (Huawei) |
R1-2308571 | LS on the longer PRS/SRS periodicity for LPHAP | RAN1, Huawei |
R1-2308648 | Draft LS on RSRP based TA validation for LPHAP | Huawei |
R1-2308649 | LS on RSRP based TA validation for LPHAP | RAN1, Huawei |
TDoc | Title | Source |
---|---|---|
R1-2306499 | Remaining issues of BW aggregation for PRS and SRS | Huawei, HiSilicon, China Unicom, China Telecom |
R1-2306574 | Discussions on bandwidth aggregation for positioning measurements | Ruijie Network Co. Ltd |
R1-2306654 | Discussion on bandwidth aggregation for positioning measurements | Spreadtrum Communications |
R1-2306759 | Discussion on bandwidth aggregation for positioning measurements | vivo |
R1-2306821 | Views on bandwidth aggregation for positioning measurements | Nokia, Nokia Shanghai Bell |
R1-2306844 | On bandwidth aggregation for positioning | Intel Corporation |
R1-2306867 | Discussion on BW aggregation for positioning | ZTE |
R1-2306870 | Summary #1 for BW aggregation positioning | Moderator (ZTE) |
R1-2306871 | Summary #2 for BW aggregation positioning | Moderator (ZTE) |
R1-2306890 | Discussion on Bandwidth aggregation for positioning measurements | LG Electronics |
R1-2307096 | Remaining issues on bandwidth aggregation for positioning measurements | CATT |
R1-2307204 | Discussion on BW aggregation for positioning measurements | CMCC |
R1-2307287 | On Bandwidth aggregation for positioning measurements | Apple |
R1-2307394 | Bandwidth aggregation for positioning measurement | xiaomi |
R1-2307480 | Discussion on bandwidth aggregation for positioning measurements | NTT DOCOMO, INC. |
R1-2307523 | Discussion on bandwidth aggregation for positioning measurement | OPPO |
R1-2307589 | Bandwidth aggregation for positioning measurements | InterDigital, Inc. |
R1-2307687 | On Bandwidth Aggregation for Positioning Measurements | Samsung |
R1-2307827 | Remaining PRS Bandwidth aggregation issues | Lenovo |
R1-2307935 | Discussion on Bandwidth aggregation for Positioning | Qualcomm Incorporated |
R1-2308094 | PRS/SRS aggregation for positioning measurement | MediaTek Korea Inc. |
R1-2308171 | Bandwidth aggregation for positioning measurements | Ericsson |
R1-2308448 | Draft Reply LS on measurement definitions for positioning with bandwidth aggregation | ZTE |
R1-2308449 | Reply LS on measurement definitions for positioning with bandwidth aggregation | RAN1, ZTE |
R1-2308450 | Summary #3 for BW aggregation positioning | Moderator (ZTE) |
R1-2308645 | Draft LS on TRP ID for positioning with bandwidth aggregation | Moderator (ZTE) |
R1-2308646 | LS on TRP ID for positioning with bandwidth aggregation | RAN1, ZTE |
TDoc | Title | Source |
---|---|---|
R1-2306444 | On remaining open issues in RedCap UE positioning | FUTUREWEI |
R1-2306500 | Remaining issues of RedCap positioning | Huawei, HiSilicon |
R1-2306655 | Discussion on positioning for RedCap UEs | Spreadtrum Communications |
R1-2306760 | Discussion on positioning for RedCap UEs | vivo |
R1-2306822 | Views on Positioning for RedCap Ues | Nokia, Nokia Shanghai Bell |
R1-2306845 | Positioning for RedCap UEs | Intel Corporation |
R1-2306868 | Discussion on Positioning for RedCap UEs | ZTE |
R1-2306891 | Discussion on positioning support for RedCap UEs | LG Electronics |
R1-2306916 | Remaining Issues on Positioning for RedCap UEs | Sony |
R1-2307097 | Remaining issues on positioning for RedCap UEs | CATT |
R1-2307118 | Positioning for RedCap UEs | NEC |
R1-2307205 | Discussion on RedCap UE positioning | CMCC |
R1-2307288 | On Positioning for RedCap UEs | Apple |
R1-2307481 | Discussion on positioning for RedCap UEs | NTT DOCOMO, INC. |
R1-2307525 | Discussion on positioning for RedCap UEs | OPPO |
R1-2307590 | Positioning for RedCap UEs | InterDigital, Inc. |
R1-2307688 | On Positioning for RedCap UEs | Samsung |
R1-2307828 | Remaining RedCap Positioning Issues | Lenovo |
R1-2307936 | Positioning for Reduced Capabilities UEs | Qualcomm Incorporated |
R1-2308095 | Positioning for RedCap UEs | MediaTek Korea Inc. |
R1-2308114 | Discussion on NR positioning for RedCap | IIT Kanpur, CEWiT |
R1-2308172 | Positioning for RedCap UEs | Ericsson |
R1-2308392 | Feature Lead summary #1 for Positioning for RedCap Ues | Moderator (Ericsson) |
R1-2308393 | Feature Lead summary #2 for Positioning for RedCap Ues | Moderator (Ericsson) |
R1-2308394 | Feature Lead summary #3 for Positioning for RedCap Ues | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2308228 | RAN1 agreements for Rel-18 NR RedCap | Rapporteur (Ericsson) |
R1-2308546 | Session notes for 9.6 (Enhanced support of reduced capability NR device) | Ad-hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2306390 | CSI report of Reduced Capability Devices | GDCNI |
R1-2306435 | Discussion on R18 RedCap complexity | FUTUREWEI |
R1-2306529 | Discussion on potential solutions to further reduce UE complexity | Huawei, HiSilicon |
R1-2306656 | Discussion on enhanced support of RedCap devices | Spreadtrum Communications |
R1-2306683 | Further RedCap UE complexity reduction | Ericsson |
R1-2306761 | Discussion on further UE complexity reduction | vivo |
R1-2306917 | Redcap complexity reduction | Sony |
R1-2306996 | UE complexity reduction for eRedCap | Panasonic |
R1-2307002 | Discussion on Rel-18 RedCap UE | NEC |
R1-2307098 | Discussion on further complexity reduction for Rel-18 RedCap UE | CATT |
R1-2307138 | Discussion on further UE complexity reduction | ZTE, Sanechips |
R1-2307206 | Discussion on further reduced UE complexity | CMCC |
R1-2307289 | Further RedCap UE complexity reduction | Apple |
R1-2307395 | Discussion on further complexity reduction for eRedCap UEs | xiaomi |
R1-2307417 | RedCap UE Complexity Reduction | Nokia, Nokia Shanghai Bell |
R1-2307482 | Discussion on further UE complexity reduction for eRedCap | NTT DOCOMO, INC. |
R1-2307554 | Further consideration on reduced UE complexity | OPPO |
R1-2307622 | Discussion on further complexity reduction for eRedCap UEs | China Telecom |
R1-2307689 | Further UE complexity reduction for eRedCap | Samsung |
R1-2307757 | Discussion on UE complexity reduction | DENSO CORPORATION |
R1-2307764 | Discussion on UE complexity reduction | Transsion Holdings |
R1-2307791 | Discussion on further UE complexity reduction for eRedCap | LG Electronics |
R1-2307841 | Considerations for further UE complexity reduction | Semtech Neuchatel SA |
R1-2307855 | Discussion on complexity reduction for eRedCap UE | Sharp |
R1-2307937 | UE complexity reduction for eRedCap | Qualcomm Incorporated |
R1-2308021 | On further complexity reduction of NR UE | Nordic Semiconductor ASA |
R1-2308039 | On eRedCap UE complexity reduction | MediaTek Inc. |
R1-2308224 | FL summary #1 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2308225 | FL summary #2 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2308226 | FL summary #3 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2308227 | FL summary #4 on Rel-18 RedCap UE complexity reduction | Moderator (Ericsson) |
R1-2308609 | [Draft] LS on reduced peak data rate for Rel-18 eRedCap UEs | Moderator (Ericsson) |
R1-2308610 | LS on reduced peak data rate for Rel-18 eRedCap UEs | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2306552 | Higher layer signalling for Rel-18 NES | Huawei, HiSilicon |
R1-2308642 | Comments collection for RRC parameters for R18 NES | Moderator (Huawei) |
R1-2308669 | Sorted RAN1 agreements for Rel-18 network energy savings post 114 | Rapporteur (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306472 | Techniques in spatial and power domains | Nokia, Nokia Shanghai Bell |
R1-2306504 | CSI enhancements for network energy saving | Huawei, HiSilicon |
R1-2306575 | Discussions on network energy savings techniques in spatial and power domains | Ruijie Network Co. Ltd |
R1-2306624 | Spatial and Power Adaptations for Network Energy Savings | FUTUREWEI |
R1-2306657 | Discussion on NES techniques in spatial and power domains | Spreadtrum Communications |
R1-2306762 | Discussions on NES techniques in spatial and power domain | vivo |
R1-2306802 | Spatial and power domain adaptation for network energy saving | Panasonic |
R1-2306828 | Discussion on NWES techniques in spatial and power domain | Intel Corporation |
R1-2306946 | Discussion on network energy saving techniques in spatial and power domains | NEC |
R1-2306963 | Network Energy Saving in Spatial and Power Domain | |
R1-2307099 | Network Energy Saving techniques in spatial and power domain | CATT |
R1-2307139 | Discussion on NES techniques in spatial and power domains | ZTE, Sanechips |
R1-2307162 | Discussion on NW energy saving techniques in spatial and power domains | Fujitsu |
R1-2307207 | Discussion on spatial and power domains enhancements for network energy saving | CMCC |
R1-2307290 | Discussion on remaining issues for spatial and power domain enhancements to support network energy saving | Apple |
R1-2307396 | Discussion on techniques in spatial and\n power domains | xiaomi |
R1-2307404 | On network energy saving techniques in spatial and power domains | KT Corp. |
R1-2307483 | Discussion on spatial and power domain enhancements for NW energy savings | NTT DOCOMO, INC. |
R1-2307540 | Discussion on techniques in spatial and power domains | OPPO |
R1-2307623 | Discussion on spatial and power domain CSI adaptation for NES | China Telecom |
R1-2307690 | Remaining Issues on NES techniques in spatial and power domains | Samsung |
R1-2307748 | Discussion on NES techniques in spatial and power domains | ETRI |
R1-2307765 | Discussion of NES techniques in spatial domain and power domain | Transsion Holdings |
R1-2307779 | Discussion on TCI state and beam management for NES spatial and power domain adaptation | FGI |
R1-2307792 | Discussion on NES techniques in spatial and power domains | LG Electronics |
R1-2307813 | Network energy saving techniques in spatial and power domains | Lenovo |
R1-2307821 | Discussion on techniques in spatial and power domains | InterDigital, Inc. |
R1-2307891 | Discussion on NES techniques in spatial and power domain | ITRI |
R1-2307938 | Techniques in spatial and power domains | Qualcomm Incorporated |
R1-2307984 | Spatial Domain Adaptation for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2307987 | NW energy saving techniques in spatial and power domains | Ericsson |
R1-2308008 | Discussion on spatial and power adaptations for network energy savings | CEWiT |
R1-2308081 | On NES Techniques in spatial and power domains | MediaTek Inc. |
R1-2308105 | Discussion on spatial/power domain adaptation | ASUSTeK |
R1-2308250 | FL summary#1 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2308251 | FL summary#2 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2308252 | FL summary#3 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2308253 | FL summary#4 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2308599 | FL summary#5 for SD and PD adaptation for R18 NES | Moderator (Huawei) |
R1-2308600 | Final summary for SD and PD adaptation for R18 NES | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306473 | Enhancements on cell DTX/DRX mechanism | Nokia, Nokia Shanghai Bell |
R1-2306505 | Cell DTX/DRX mechanism for network energy saving | Huawei, HiSilicon |
R1-2306577 | Discussions on enhancements on cell DTX/DRX mechanism | Ruijie Network Co. Ltd |
R1-2306625 | Cell DTX/DRX for NES | FUTUREWEI |
R1-2306658 | Discussion on enhancements on cell DTXDRX mechanism | Spreadtrum Communications |
R1-2306763 | Discussions on enhancements on cell DTX/DRX mechanism | vivo |
R1-2306803 | Cell DTX/DRX enhancement for network energy saving | Panasonic |
R1-2306829 | Discussion on enhancements on cell DTX/DRX mechanism | Intel Corporation |
R1-2306948 | Cell DTX/DRX Configuration for Network Energy Saving | NEC |
R1-2306964 | Network Energy Saving on Cell DTX and DRX | |
R1-2307100 | DTX/DRX for network Energy Saving | CATT |
R1-2307140 | Discussion on cell DTX/DRX | ZTE, Sanechips |
R1-2307163 | Discussion on cell DTX/DRX mechanism | Fujitsu |
R1-2307208 | Discussion on cell DTX/ DRX mechanism | CMCC |
R1-2307291 | Discussion on remaining issues for cell DTX/DRX mechanism | Apple |
R1-2307397 | Discussions on cell DTX-DRX for network energy saving | xiaomi |
R1-2307484 | Discussion on enhancements on Cell DTX/DRX mechanism | NTT DOCOMO, INC. |
R1-2307541 | Discussion on enhancements on cell DTX/DRX mechanism | OPPO |
R1-2307624 | Discussion on the mechanism of Cell DTX/DRX for NES | China Telecom |
R1-2307691 | Remaining issues on cell DTX/DRX mechanism | Samsung |
R1-2307749 | Discussion on cell DTX/DRX mechanism | ETRI |
R1-2307766 | Discussion on Enhancement on cell DTX DRX mechanism | Transsion Holdings |
R1-2307793 | Discussion on cell DTX/DRX mechanism | LG Electronics |
R1-2307814 | Enhancements on cell DTX/DRX mechanism | Lenovo |
R1-2307822 | Discussion on enhancements on cell DTX/DRX mechanism | InterDigital, Inc. |
R1-2307838 | Considerations of Cell DTX/DRX Signaling and Reliability | Fraunhofer IIS, Fraunhofer HHI |
R1-2307939 | Enhancements on cell DTX and DRX mechanism | Qualcomm Incorporated |
R1-2307988 | RAN1 aspects of cell DTX/DRX | Ericsson |
R1-2308009 | Discussion on cell DTX/DRX mechanism for network energy saving | CEWiT |
R1-2308082 | On enhancements of cell DTX/DRX mechanism | MediaTek Inc. |
R1-2308106 | Discussion on cell DTX/DRX | ASUSTeK |
R1-2308350 | Summary of issues for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2308351 | Discussion summary #1 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2308352 | Discussion summary #2 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2308496 | Discussion summary #3 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2308497 | Discussion summary #4 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
R1-2308620 | Discussion summary #5 for enhancements on cell DTX/DRX mechanism | Moderator (Intel Corporation) |
TDoc | Title | Source |
---|---|---|
R1-2307940 | Initial higher layer parameters for Rel-18 XR enhancements | Qualcomm Incorporated |
R1-2308028 | Work Plan for Rel-18 WI on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs), Ericsson (RAN1 FL) |
R1-2308668 | Summary of discussions on RRC parameters for Rel-18 XR WI | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2306403 | Discussions on XR-specific capacity enhancements | New H3C Technologies Co., Ltd. |
R1-2306427 | XR-specific capacity enhancements | FUTUREWEI |
R1-2306526 | Discussion on CG enhancements for XR capacity | Huawei, HiSilicon |
R1-2306607 | Capacity Enhancements for XR | Ericsson |
R1-2306628 | Discussion on XR capacity enhancement techniques | Panasonic |
R1-2306659 | Discussion on XR-specific capacity enhancements | Spreadtrum Communications |
R1-2306698 | Discussion on XR-specific capacity enhancements | Honor |
R1-2306764 | Discussion on XR specific capacity enhancements | vivo |
R1-2306918 | Remaining Issues on XR specific capacity enhancements | Sony |
R1-2307101 | Design of Multiple CG Occasions and unused CG occasion feedback | CATT |
R1-2307115 | Discussion on XR-specific capacity enhancements | NEC |
R1-2307141 | Discussion on XR specific capacity enhancements | ZTE, Sanechips |
R1-2307209 | Discussion on XR-specific capacity enhancements | CMCC |
R1-2307292 | XR-specific capacity enhancements | Apple |
R1-2307398 | Discussion on XR-specific capacity enhancements | xiaomi |
R1-2307405 | On XR-specific capacity enhancements | KT Corp. |
R1-2307485 | Discussion on XR specific capacity improvement enhancements | NTT DOCOMO, INC. |
R1-2307574 | Discussion on XR specific capacity enhancements | OPPO |
R1-2307597 | XR specific capacity enhancements | TCL |
R1-2307612 | XR-specific capacity enhancements | Nokia, Nokia Shanghai Bell |
R1-2307692 | Capacity enhancements for XR | Samsung |
R1-2307771 | On XR-specific capacity enhancements techniques | Google Inc. |
R1-2307794 | Discussion on XR-specific capacity enhancements | LG Electronics |
R1-2307815 | XR-related CG Enhancements | Lenovo |
R1-2307819 | Remaining issues on UTO-UCI content and reporting | Sharp |
R1-2307820 | Discussion on XR-specific capacity enhancements | InterDigital, Inc. |
R1-2307866 | Discussion on XR specific capacity enhancements | CAICT |
R1-2307941 | Remaining Issues on Capacity Enhancement Techniques for XR | Qualcomm Incorporated |
R1-2308063 | XR capacity enhancements | MediaTek Inc. |
R1-2308202 | XR-specific capacity enhancements | Apple |
R1-2308331 | Moderator Summary#1 - XR Specific Capacity Improvements | Moderator (Ericsson) |
R1-2308332 | Moderator Summary#2 - XR Specific Capacity Improvements | Moderator (Ericsson) |
R1-2308333 | Moderator Summary#3 - XR Specific Capacity Improvements | Moderator (Ericsson) |
R1-2308334 | Moderator Summary#4 - XR Specific Capacity Improvements | Moderator (Ericsson) |
R1-2308613 | Moderator Final Summary - XR Specific Capacity Improvements | Moderator (Ericsson) |
R1-2308637 | Draft LS on stage 2 description for physical layer enhancements for XR | Nokia |
R1-2308653 | Draft Reply LS on new DRX cycles in rational numbers | Qualcomm |
R1-2308654 | Reply LS on new DRX cycles in rational numbers | RAN1, Qualcomm |
R1-2308659 | LS on stage 2 description for physical layer enhancements for XR | RAN1, Nokia |
TDoc | Title | Source |
---|---|---|
R1-2306408 | Discussion on RAN4 LS on the system parameters for NTN above 10 GHz | THALES |
R1-2306409 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
R1-2306704 | Correction on corresponding scaling factors table | IPLOOK |
R1-2308416 | Discussion on RAN4 LS on FR2-NTN aspects | Moderator (Nokia) |
R1-2308432 | Moderator Summary for RRC parameters for Rel-18 IoT NTN enhancements | Moderator (MediaTek) |
R1-2308441 | Draft reply LS to RAN2 on unchanged PCI | Moderator (CATT) |
R1-2308442 | Discussion on RAN2 LS reply on unchanged PCI | CATT |
R1-2308443 | Moderator summary on reply LS on RACH-less handover | Moderator (Samsung) |
R1-2308480 | Summary of offline discussion on RRC parameters for Rel-18 NR NTN enhancements | Moderator (Thales) |
R1-2308547 | Session notes for 9.9 (NTN (Non-Terrestrial Networks) enhancements) | Ad-Hoc Chair (Huawei) |
R1-2308566 | Reply LS to RAN2 on unchanged PCI | RAN1, CATT |
R1-2308567 | Draft Reply LS on RACH-less Handover | Moderator (Samsung) |
R1-2308568 | Reply LS on RACH-less Handover | RAN1, Samsung |
R1-2308678 | RAN1 agreements for Rel-18 WI on NR NTN enhancements up to RAN1#114 | WI rapporteur (Thales) |
R1-2308749 | RAN1 agreements for Rel-18 WI on IoT NTN enhancements up to RAN1#114 | WI rapporteur (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2306419 | On coverage enhancements for NR NTN | Ericsson |
R1-2306486 | Discussion on coverage enhancement for NR NTN | Huawei, HiSilicon |
R1-2306563 | Discussion on coverage enhancement for NTN | ZTE |
R1-2306660 | Discussion on coverage enhancements for NTN | Spreadtrum Communications |
R1-2306765 | Discussions on remaining issues of coverage enhancements in NR NTN | vivo |
R1-2306892 | Discussion on coverage enhancement for NR NTN | LG Electronics |
R1-2306943 | Coverage enhancement for NR NTN | NEC |
R1-2307102 | Further discussion on UL coverage enhancement for NR NTN | CATT |
R1-2307210 | Discussion on coverage enhancement for NR NTN | CMCC |
R1-2307245 | Remaining issues related to NTN coverage enhancements | Nokia, Nokia Shanghai Bell |
R1-2307293 | On Coverage Enhancement for NR NTN | Apple |
R1-2307341 | Discussion on coverage enhancement for NR NTN | Baicells |
R1-2307399 | Discussion on coverage enhancement for NR-NTN | xiaomi |
R1-2307406 | Discussion on coverage enhancement for NR-NTN | Panasonic |
R1-2307431 | Discussions on Coverage enhancement for NR NTN | Sharp |
R1-2307486 | Discussion on coverage enhancement for NR NTN | NTT DOCOMO, INC. |
R1-2307543 | Discussion on coverage enhancement for NR NTN | OPPO |
R1-2307593 | Discussion on coverage enhancement for NR NTN | Hyundai Motor Company |
R1-2307614 | Coverage enhancement for NR NTN | Lenovo |
R1-2307693 | On coverage enhancement for NR NTN | Samsung |
R1-2307735 | Discussion on coverage enhancements for NR NTN | CCU, NTPU |
R1-2307750 | Discussion on coverage enhancement for NR NTN | ETRI |
R1-2307942 | Coverage enhancements for NR NTN | Qualcomm Incorporated |
R1-2308050 | Coverage enhancement for NR NTN | MediaTek Inc. |
R1-2308322 | Summary #1 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
R1-2308323 | Summary #2 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
R1-2308324 | Summary #3 on 9.9.1 Coverage enhancement for NR NTN | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2306404 | Discussion on network verified UE location in NR NTN | THALES |
R1-2306410 | Feature Lead Summary #1 on Network verified UE location for NR NTN | Moderator (THALES) |
R1-2306411 | Feature Lead Summary #2 on Network verified UE location for NR NTN | Moderator (THALES) |
R1-2306412 | Feature Lead Summary #3 on Network verified UE location for NR NTN | Moderator (THALES) |
R1-2306413 | Feature Lead Summary #4 on Network verified UE location for NR NTN | Moderator (THALES) |
R1-2306487 | Discussion on network-verified UE location for NR NTN | Huawei, HiSilicon |
R1-2306564 | Discussion on network verified UE location for NR NTN | ZTE |
R1-2306766 | Discussions on remaining issues of UE location verification in NR NTN | vivo |
R1-2306793 | Discussion on Network-verified UE location for NR-NTN | PANASONIC |
R1-2306893 | Discussion on network verified UE location for NR NTN | LG Electronics |
R1-2306919 | On network verified UE location for NR NTN | Sony |
R1-2306949 | On Network verified UE location in NR NTN | Ericsson |
R1-2307103 | Further discussion on Network verified UE location for NR NTN | CATT |
R1-2307246 | Further aspects related to network verified UE location | Nokia, Nokia Shanghai Bell |
R1-2307294 | On Network Verified UE Location | Apple |
R1-2307400 | Discussion on the network verified location for NR-NTN | xiaomi |
R1-2307432 | Network verified UE location for Rel-18 NR NTN | Sharp |
R1-2307487 | Discussion on Network verified UE location for NR NTN | NTT DOCOMO, INC. |
R1-2307544 | Discussion on network verified UE location for NR NTN | OPPO |
R1-2307694 | Network verified UE location for NR NTN | Samsung |
R1-2307751 | Discussion on Network verified UE location for NR NTN | ETRI |
R1-2307837 | Network verified UE location for NR NTN | Lenovo |
R1-2307875 | Discussion on Network Verified UE Location | TCL |
R1-2307943 | Network verified UE location for NR NTN | Qualcomm Incorporated |
R1-2308051 | Network verified UE location for NR NTN | MediaTek Inc. |
R1-2308608 | Feature Lead Summary #5 on Network verified UE location for NR NTN | Moderator (THALES) |
TDoc | Title | Source |
---|---|---|
R1-2306490 | Discussion on disabling of HARQ feedback for IoT NTN | Huawei, HiSilicon |
R1-2306565 | Discussion on disabling of HARQ feedback for IoT-NTN | ZTE |
R1-2306661 | Discussion on disabling of HARQ feedback for IoT NTN | Spreadtrum Communications |
R1-2306879 | Disabling of HARQ feedback for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
R1-2306920 | Discussion on disabling of HARQ feedback for IoT-NTN | Sony |
R1-2307104 | Discussion on remaining issues of disabling of HARQ feedback for IoT NTN | CATT |
R1-2307117 | Disabling of HARQ feedback for IoT NTN | NEC |
R1-2307211 | Discussion on disabling of HARQ feedback for IoT NTN | CMCC |
R1-2307295 | On HARQ Feedback Disabling for IoT NTN | Apple |
R1-2307401 | Discussion on the HARQ operation for IoT NTN | xiaomi |
R1-2307433 | Disabling of HARQ feedback for IoT NTN | Sharp |
R1-2307545 | Discussion on disabling of HARQ feedback for IoT NTN | OPPO |
R1-2307615 | Disabling of HARQ feedback for IoT NTN | Lenovo |
R1-2307695 | Disabling of HARQ feedback for IoT NTN | Samsung |
R1-2307799 | On disabling HARQ feedback for IoT NTN | Ericsson |
R1-2307944 | Disabling HARQ Feedback for IoT-NTN | Qualcomm Incorporated |
R1-2308010 | Disabling of HARQ feedback for IoT NTN | Nordic Semiconductor ASA |
R1-2308058 | Disabling of HARQ for IoT NTN | MediaTek Inc. |
R1-2308231 | FLS#1 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
R1-2308232 | FLS#2 on disabling of HARQ feedback for IoT NTN | Moderator (Lenovo) |
TDoc | Title | Source |
---|---|---|
R1-2306491 | Discussion on improved GNSS operations for IoT NTN | Huawei, HiSilicon |
R1-2306566 | Discussion on improved GNSS operation for IoT-NTN | ZTE |
R1-2306662 | Discussion on improved GNSS operations for IoT NTN | Spreadtrum Communications |
R1-2306880 | Enhancements for long connections in NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
R1-2306944 | On Improved GNSS Operations for IoT NTN | NEC |
R1-2306950 | On improved GNSS operation in IoT NTN | Ericsson |
R1-2307105 | Discussion on remaining issues of improved GNSS operations for IoT NTN | CATT |
R1-2307212 | Discussion on improved GNSS operations for IoT NTN | CMCC |
R1-2307296 | On improved GNSS operations for IoT NTN | Apple |
R1-2307402 | Discussion on the improved GNSS operation for IoT NTN | xiaomi |
R1-2307546 | Discussion on improved GNSS operations for IoT NTN | OPPO |
R1-2307616 | Improved GNSS operations for IoT NTN | Lenovo |
R1-2307696 | Improved GNSS operations for IoT NTN | Samsung |
R1-2307945 | Improved GNSS Operations for IoT-NTN | Qualcomm Incorporated |
R1-2308011 | Improved GNSS operations for IoT NTN | Nordic Semiconductor ASA |
R1-2308059 | Improved GNSS operations | MediaTek Inc. |
R1-2308235 | Feature lead summary#1 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
R1-2308236 | Feature lead summary#2 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
R1-2308237 | Feature lead summary#3 of AI 9.9.4 on improved GNSS operations | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2307223 | L1 enhancements for inter-cell beam management | KDDI Corporation |
R1-2308548 | Session notes for 9.10 (Further NR mobility enhancements) | Ad-Hoc Chair (CMCC) |
R1-2308663 | Rel-18 RRC parameters for NR mobility enhancement WI for RAN1 114 | Rapporteur (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2306405 | FL plan on L1 enhancements for LTM at RAN1#114 | Moderator (Fujitsu, MediaTek) |
R1-2306425 | L1 enhancements for inter-cell beam management | FUTUREWEI |
R1-2306518 | L1 enhancements for inter-cell beam management | Huawei, HiSilicon |
R1-2306578 | Discussions on L1 enhancements for inter-cell beam management | Ruijie Network Co. Ltd |
R1-2306601 | L1 enhancements to inter-cell beam management | Ericsson |
R1-2306616 | L1 enhancements for inter-cell beam management | ZTE |
R1-2306663 | Discussion on L1 enhancements for inter-cell beam management | Spreadtrum Communications |
R1-2306767 | Discussion on L1 enhancement for LTM | vivo |
R1-2306812 | Layer-1 Enhancements for L1/L2-triggered Mobility | Nokia, Nokia Shanghai Bell |
R1-2306938 | L1 enhancements for inter-cell beam management | Lenovo |
R1-2306947 | Discussion on L1 enhancements for inter-cell beam management | NEC |
R1-2307018 | Enhancements on inter-cell beam management for mobility | LG Electronics |
R1-2307060 | Remaining issues on L1 enhancements for inter-cell beam management | CATT |
R1-2307164 | Views on L1 enhancements for inter-cell beam management | Fujitsu |
R1-2307213 | Discussion on L1 enhancements for inter-cell beam management | CMCC |
R1-2307297 | L1 Enhancements for Inter-Cell Beam Management | Apple |
R1-2307335 | FL plan on L1 enhancements for LTM at RAN1#114 | Moderator (Fujitsu, MediaTek) |
R1-2307354 | Discussion on L1 enhancements for inter-cell beam management in LTM | xiaomi |
R1-2307403 | L1 enhancements for inter-cell beam management | KDDI Corporation |
R1-2307408 | FL summary 1 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2307409 | FL summary 2 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2307410 | FL summary 3 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2307488 | Discussion on L1 enhancements for inter-cell mobility | NTT DOCOMO, INC. |
R1-2307526 | Discussions on Inter-cell beam management enhancement | OPPO |
R1-2307697 | On L1 enhancements for inter-cell beam management | Samsung |
R1-2307767 | Discussion on measurement enhancement of L1L2 triggered mobility | Transsion Holdings |
R1-2307780 | Discussion on L1 enhancements for inter-cell beam management | FGI |
R1-2307839 | Remaining issues on L1 triggered mobility | InterDigital, Inc. |
R1-2307850 | Discussion on L1 enhancements for inter-cell beam management | |
R1-2307946 | L1 Enhancements for Inter-Cell Beam Management | Qualcomm Incorporated |
R1-2308084 | L1 enhancements for inter-cell beam management | MediaTek Inc. |
R1-2308447 | Draft reply LS on L1 measurements for LTM | Moderator (Ericsson) |
R1-2308465 | Reply LS on L1 measurements for LTM | RAN1, Ericsson |
R1-2308592 | FL summary 4 on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2308593 | Final summary on L1 enhancements for inter-cell beam management | Moderator (Fujitsu, MediaTek) |
R1-2308624 | DRAFT LS on L1 measurement and TA management for LTM | Fujitsu, MediaTek, CATT |
R1-2308625 | LS on L1 measurement and TA management for LTM | RAN1, CATT, Fujitsu, MediaTek |
TDoc | Title | Source |
---|---|---|
R1-2306426 | UE based RACH-less TA determination for inter-cell LTM | FUTUREWEI |
R1-2306519 | Timing advance management to reduce latency | Huawei, HiSilicon |
R1-2306579 | Discussions on timing advance management to reduce latency | Ruijie Network Co. Ltd |
R1-2306602 | Timing advance management for L1/L2 Mobility | Ericsson |
R1-2306617 | Enhancements on TA management to reduce latency | ZTE |
R1-2306664 | Discussion on timing advance management to reduce latency | Spreadtrum Communications |
R1-2306768 | Discussion on TA management for LTM | vivo |
R1-2306813 | Timing Advance Management for L1/L2-triggered Mobility | Nokia, Nokia Shanghai Bell |
R1-2306939 | Timing advancement management for L1L2 mobility | Lenovo |
R1-2307019 | Enhancements on TA management for mobility | LG Electronics |
R1-2307061 | Remaining issues on TA management to reduce latency | CATT |
R1-2307214 | Discussion on timing advance management to reduce latency | CMCC |
R1-2307298 | Timing advance management for L1/L2 Mobility | Apple |
R1-2307355 | Discussion on Timing advance management | xiaomi |
R1-2307489 | Timing advance enhancement for inter-cell mobility | NTT DOCOMO, INC. |
R1-2307527 | Discussions on Timing Advance Management | OPPO |
R1-2307698 | Candidate cell TA acquisition for NR L1/L2 mobility enhancement | Samsung |
R1-2307752 | Discussion on TA management for mobility enhancements | ETRI |
R1-2307768 | Discussion on TA management for L1/L2 mobility | Transsion Holdings |
R1-2307840 | Discussion on the remaining details for timing advance management | InterDigital, Inc. |
R1-2307851 | Discussion on timing advance management to reduce latency | |
R1-2307892 | Discussion on TA management to reduce latency | ITRI |
R1-2307947 | TA management to reduce latency for L1/L2 based mobility | Qualcomm Incorporated |
R1-2308012 | Discussion on TA management to reduce latency | CAICT |
R1-2308073 | UL Timing management to reduce handover latency | MediaTek Inc. |
R1-2308242 | Moderator summary on Timing advance management for LTM: Round 1 | Moderator (CATT) |
R1-2308405 | Moderator summary on Timing advance management for LTM: Round 2 | Moderator (CATT) |
R1-2308468 | Moderator summary on Timing advance management for LTM: Round 3 | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2307829 | Draft TR 38.869 v030: Study on low-power wake up signal and receiver for NR | Rapporteur (vivo) |
R1-2307830 | Draft TP for TR38.869 for clean up | Rapporteur (CMCC), vivo |
R1-2308386 | Draft TP for TR38.869 for clean up | Rapporteur (vivo) |
R1-2308433 | Draft TP for TR38.869 for clean up | Rapporteur (vivo) |
R1-2308729 | TR 38.869 v0.4.0: Study on low-power wake up signal and receiver for NR | Rapporteur (vivo), CMCC |
TDoc | Title | Source |
---|---|---|
R1-2306428 | Evaluation of LP-WUS and Performance Results | FUTUREWEI |
R1-2306548 | Evaluations for LP-WUS | Huawei, HiSilicon |
R1-2306665 | Discussion on evaluation on low power WUS | Spreadtrum Communications |
R1-2306691 | Discussion on evaluation on LP-WUS | InterDigital, Inc. |
R1-2306769 | Evaluation results for R18 LP-WUS/WUR | vivo |
R1-2306921 | Evaluation of low-power WUS | Sony |
R1-2307062 | Remaining issues of Deployment scenarios and evaluation methodologies and preliminary performance results of LP-WUR | CATT |
R1-2307142 | Evaluation on LP-WUS | ZTE, Sanechips |
R1-2307215 | Remaining issues for evaluation methodology for LP-WUS/WUR | CMCC |
R1-2307299 | On performance evaluation for low power wake-up signal | Apple |
R1-2307356 | Evaluation on low power WUS | xiaomi |
R1-2307418 | Low power WUS Evaluation Methodology | Nokia, Nokia Shanghai Bell |
R1-2307490 | Evaluation methodology for low power WUS | NTT DOCOMO, INC. |
R1-2307555 | Evaluation for lower power wake-up signal | OPPO |
R1-2307699 | Evaluation on LP-WUS/WUR | Samsung |
R1-2307831 | Draft TP for LP-WUS power evaluation results for TR38.869 – IDLE/INACTIVE | Moderator (CMCC), vivo |
R1-2307832 | Draft TP for LP-WUS power evaluation results for TR38.869 – CONNECTED | Moderator (CMCC), vivo |
R1-2307833 | Draft TP for LP-WUS coverage results for TR38.869 | Moderator (CMCC), vivo |
R1-2307834 | Draft TP for LP-WUS network power consumption evaluation results for TR38.869 | Moderator (CMCC), vivo |
R1-2307835 | Draft TP for LP-WUS overhead evaluation results for TR38.869 | Moderator (CMCC), vivo |
R1-2307836 | FL summary #1 of evaluation on LP-WUS/WUR | Moderator (CMCC) |
R1-2307948 | Evaluation methodology for LP-WUS | Qualcomm Incorporated |
R1-2307989 | Low power WUS evaluations | Ericsson |
R1-2308067 | Evaluation on low power WUS | MediaTek Inc. |
R1-2308234 | Low power WUS Evaluation Methodology | Nokia, Nokia Shanghai Bell |
R1-2308249 | Evaluation results for R18 LP-WUS/WUR | vivo |
R1-2308339 | Draft TP for LP-WUS coverage results for TR38.869 | Moderator (vivo) |
R1-2308387 | Draft TP for LP-WUS power evaluation results for TR38.869 – IDLE/INACTIVE | Moderator (vivo) |
R1-2308388 | Draft TP for LP-WUS power evaluation results for TR38.869 – CONNECTED | Moderator (vivo) |
R1-2308389 | Draft TP for LP-WUS coverage results for TR38.869 | Moderator (vivo) |
R1-2308390 | Draft TP for LP-WUS network power consumption evaluation results for TR38.869 | Moderator (vivo) |
R1-2308391 | Draft TP for LP-WUS overhead evaluation results for TR38.869 | Moderator (vivo) |
R1-2308434 | TP for LP-WUS power evaluation results for TR38.869 – CONNECTED | Moderator (vivo) |
R1-2308435 | TP for LP-WUS coverage results for TR38.869 | Moderator (vivo) |
R1-2308436 | TP for LP-WUS overhead evaluation results for TR38.869 | Moderator (vivo) |
R1-2308437 | Draft TP for LP-WUS overhead evaluation results for TR38.869 | Moderator (vivo) |
R1-2308438 | Low power WUS evaluations | Ericsson |
R1-2308563 | Evaluation for lower power wake-up signal | OPPO |
R1-2308603 | Draft TP for TR conclusion - evaluations | Rapporteur (vivo) |
R1-2308670 | TP for LP-WUS power evaluation results for TR38.869 – IDLE/INACTIVE | Moderator (vivo) |
R1-2308671 | TP for TR conclusion - evaluations | Rapporteur (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2306549 | Discussion on architecture of LP-WUS receiver | Huawei, HiSilicon |
R1-2306692 | Discussion on LP-WUS receiver architectures | InterDigital, Inc. |
R1-2306770 | Remaining issues on low power wake-up receiver architecture | vivo |
R1-2306804 | Discussion on low power wake up receiver architectures | Panasonic |
R1-2307063 | Low-Power WUS receiver Architectures and its performance | CATT |
R1-2307143 | LP-WUS receiver architectures | ZTE, Sanechips |
R1-2307300 | On low power wake-up receiver architectures | Apple |
R1-2307301 | Summary #1 on LP WUR architectures | Moderator (Apple) |
R1-2307302 | Summary #2 on LP WUR architectures | Moderator (Apple) |
R1-2307303 | Summary #3 on LP WUR architectures | Moderator (Apple) |
R1-2307419 | Low Power WUS receiver architectures | Nokia, Nokia Shanghai Bell |
R1-2307556 | Discussion on low power WUS receiver | OPPO |
R1-2307700 | Receiver architecture for LP-WUS | Samsung |
R1-2307949 | Receiver architecture for LP-WUS | Qualcomm Incorporated |
R1-2307990 | Low power WUS receiver architectures | Ericsson |
R1-2308068 | Low power WUS receiver architectures | MediaTek Inc. |
R1-2308472 | Remaining issues on low power wake-up receiver architecture | vivo |
R1-2308595 | Summary #4 on LP WUR architecture | Moderator (Apple) |
R1-2308596 | Draft TP for LP-WUR architecture analysis for TR38.869 | Moderator (Apple) |
R1-2308604 | Draft TP for the conclusion of TR38.869 on LP-WUR architecture | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2306429 | LP-WUS Physical Signal Design and Performance | FUTUREWEI |
R1-2306550 | Further details on signal design and procedure for LP-WUS | Huawei, HiSilicon |
R1-2306626 | Discussion on L1 signal design and procedure for low power WUS | EURECOM |
R1-2306666 | Discussion on L1 signal design and procedure for low power WUS | Spreadtrum Communications |
R1-2306682 | L1 signal design and procedure for low power WUS | TCL |
R1-2306693 | Discussion on L1 signal design and procedure for LP-WUS | InterDigital, Inc. |
R1-2306771 | Discussion on physical signal and procedure for low power WUS | vivo |
R1-2306805 | Discussion on low power wake up signal design | Panasonic |
R1-2306922 | On L1 signal design and procedures for LP-WUS | Sony |
R1-2306927 | WUS Design Considerations and Impact on WUR Power | Everactive |
R1-2307064 | Physical layer signals/procedures and higher layer protocol for Low-Power WUR | CATT |
R1-2307116 | Discussion on L1 signal design and procedure for LP-WUS | NEC |
R1-2307144 | LP-WUS design and related procedure | ZTE, Sanechips |
R1-2307216 | Discussion on L1 signal design for low power WUS | CMCC |
R1-2307304 | On the L1 signal design and procedures for low power wake-up signal | Apple |
R1-2307357 | Discussions on L1 signal design and procedure for low power WUS | xiaomi |
R1-2307420 | L1 signal design and procedures for low power WUS | Nokia, Nokia Shanghai Bell |
R1-2307491 | L1 signal design and procedure for low power WUS | NTT DOCOMO, INC. |
R1-2307557 | Design consideration on lower power wake-up signal and procedure | OPPO |
R1-2307625 | Discussion on signal design and procedure for LP-WUS | China Telecom |
R1-2307701 | Signal design and procedure for LP-WUS | Samsung |
R1-2307795 | Discussion on L1 signal design and procedure for LP-WUS | LG Electronics |
R1-2307856 | Discussion on L1 signal design and procedure for low power WUS | Sharp |
R1-2307950 | L1 signal design and procedures for LP-WUR | Qualcomm Incorporated |
R1-2307991 | L1 signal design and procedure for low power WUS | Ericsson |
R1-2308022 | On LP-WUS signal design | Nordic Semiconductor ASA |
R1-2308069 | L1 signal design and procedure for low power WUS | MediaTek Inc. |
R1-2308102 | Discussion on the L1 signal design and procedure for low power WUS | Lenovo |
R1-2308103 | Discussion on evaluation on LP-WUS | Lenovo |
R1-2308204 | Physical layer signals/procedures and higher layer protocol for Low-Power WUR | CATT |
R1-2308257 | On the L1 signal design and procedures for low power wake-up signal | Apple |
R1-2308404 | Summary#1 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2308414 | Summary#2 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2308469 | On the L1 signal design and procedures for low power wake-up signal | Apple |
R1-2308473 | Summary#3 of discussions on L1 signal design and procedure for low power WUS | Moderator (Nordic Semiconductor ASA) |
R1-2308601 | TP for LP-WUS LLS observations | Moderator (Nordic Semiconductor ASA) |
R1-2308602 | TP for Conclusions in 9.11.3 AI | Moderator (Nordic Semiconductor ASA) |
R1-2308638 | TP on description of envelop IF | Moderator (Nordic Semiconductor ASA) |
R1-2308639 | TP for Conclusions in 9.11.3 AI | Moderator (Nordic Semiconductor ASA) |
R1-2308647 | R18 SI LLS results | Moderator (Nordic Semiconductor ASA) |
TDoc | Title | Source |
---|---|---|
R1-2307857 | Initial higher layer parameter list for Rel-18 coverage enhancements | Rapporteur (China Telecom) |
R1-2308549 | Session notes for 9.12 (Further NR coverage enhancements) | Ad-Hoc Chair (CMCC) |
R1-2308679 | RAN1 agreements for Rel-18 WI on Further NR coverage enhancements | Rapporteur (China Telecom) |
TDoc | Title | Source |
---|---|---|
R1-2306406 | Discussions on PRACH coverage enhancements | New H3C Technologies Co., Ltd. |
R1-2306545 | Discussion on PRACH coverage enhancements | Huawei, HiSilicon |
R1-2306580 | Discussions on PRACH coverage enhancements | Ruijie Network Co. Ltd |
R1-2306667 | Discussion on PRACH coverage enhancements | Spreadtrum Communications |
R1-2306701 | PRACH coverage enhancements | Nokia, Nokia Shanghai Bell |
R1-2306772 | Discussions on remaining issues of PRACH coverage enhancements | vivo |
R1-2306825 | Discussions on PRACH coverage enhancement | Intel Corporation |
R1-2306858 | Discussion on PRACH coverage enhancements | Panasonic |
R1-2306894 | Discussion on PRACH repeated transmission for NR coverage enhancement | LG Electronics |
R1-2306923 | Remaining issues on multiple PRACH transmissions for PRACH coverage enhancement | Sony |
R1-2306984 | Discussion on PRACH coverage enhancements | ZTE |
R1-2307065 | PRACH coverage enhancements | CATT |
R1-2307135 | Discussion on PRACH coverage enhancement | NEC |
R1-2307165 | Discussion on PRACH coverage enhancements | Fujitsu |
R1-2307217 | Discussion on PRACH coverage enhancements | CMCC |
R1-2307224 | Discussion on PRACH coverage enhancements | Quectel |
R1-2307305 | Discussion on PRACH coverage enhancement | Apple |
R1-2307358 | Discussion on PRACH coverage enhancements | xiaomi |
R1-2307412 | PRACH coverage enhancements | Lenovo |
R1-2307434 | Multiple PRACH transmissions for Rel-18 CovEnh | Sharp |
R1-2307492 | Discussion on PRACH coverage enhancements | NTT DOCOMO, INC. |
R1-2307558 | PRACH coverage enhancements | OPPO |
R1-2307596 | PRACH coverage enhancements | TCL |
R1-2307626 | Discussion on PRACH coverage enhancement | China Telecom |
R1-2307632 | Discussion on PRACH coverage enhancements | Google Inc. |
R1-2307702 | PRACH coverage enhancements | Samsung |
R1-2307727 | Discussion on PRACH coverage enhancement | Mavenir |
R1-2307753 | PRACH coverage enhancements | ETRI |
R1-2307844 | Discussion on PRACH Coverage Enhancement | Ericsson |
R1-2307871 | Discussion on PRACH coverage enhancements | InterDigital, Inc. |
R1-2307951 | PRACH Coverage Enhancements | Qualcomm Incorporated |
R1-2308060 | PRACH coverage enhancements | MediaTek Inc. |
R1-2308308 | FL Summary#1 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2308309 | FL Summary#2 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2308310 | FL Summary#3 on PRACH coverage enhancements | Moderator (China Telecom) |
R1-2308311 | FL Summary#4 on PRACH coverage enhancements | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R1-2306546 | Discussion on coverage enhancement in power domain | Huawei, HiSilicon |
R1-2306581 | Discussions on power domain enhancements | Ruijie Network Co. Ltd |
R1-2306668 | Discussion on power domain enhancements | Spreadtrum Communications |
R1-2306702 | RAN1 impacts for power domain enhancements | Nokia, Nokia Shanghai Bell |
R1-2306773 | Discussions on remaining issues of power domain enhancements | vivo |
R1-2306895 | Discussion on Power Domain Enhancements | LG Electronics |
R1-2306985 | Discussion on power domain enhancements | ZTE |
R1-2307166 | Discussion on power domain enhancements | Fujitsu |
R1-2307218 | Discussion on power domain enhancements | CMCC |
R1-2307306 | Discussion on power domain coverage enhancement | Apple |
R1-2307359 | Discussion on power domain enhancements | xiaomi |
R1-2307413 | Power domain enhancements | Lenovo |
R1-2307435 | Power domain enhancements for Rel-18 CovEnh | Sharp |
R1-2307493 | Discussion on power domain enhancements | NTT DOCOMO, INC. |
R1-2307559 | The study of power domain enhancements | OPPO |
R1-2307703 | Power domain enhancements | Samsung |
R1-2307845 | Finalization of Power Domain Enhancement Schemes | Ericsson |
R1-2307872 | Discussion on power domain enhancements | InterDigital, Inc. |
R1-2307952 | Power-domain enhancements | Qualcomm Incorporated |
R1-2308061 | Power domain enhancements | MediaTek Inc. |
R1-2308238 | FL summary of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2308239 | FL summary #2 of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2308240 | Final FL summary of power domain enhancements (AI 9.12.2) | Moderator (Nokia) |
R1-2308560 | [Draft] LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC | Moderator (Nokia) |
R1-2308561 | LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC | RAN1, Nokia |
TDoc | Title | Source |
---|---|---|
R1-2306547 | Discussion on dynamic waveform switching for coverage enhancement | Huawei, HiSilicon |
R1-2306582 | Discussions on dynamic switching between DFT-S-OFDM and CP-OFDM | Ruijie Network Co. Ltd |
R1-2306669 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Spreadtrum Communications |
R1-2306703 | Dynamic switching between DFT-s-OFDM and CP-OFDM | Nokia, Nokia Shanghai Bell |
R1-2306774 | Discussions on remaining issues of dynamic waveform switching | vivo |
R1-2306826 | Dynamic switching between DFT-S-OFDM and CP-OFDM waveform | Intel Corporation |
R1-2306896 | Discussion on dynamic waveform switching for NR coverage enhancement | LG Electronics |
R1-2306924 | Remaining issues on dynamic waveform switching | Sony |
R1-2306986 | Discussion on dynamic waveform switching | ZTE |
R1-2307005 | Discussion on dynamic waveform switching | Panasonic |
R1-2307066 | Dynamic switching between DFT-S-OFDM and CP-OFDM | CATT |
R1-2307136 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NEC |
R1-2307219 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | CMCC |
R1-2307253 | Dynamic switching between DFT-S-OFDM and CP-OFDM | InterDigital, Inc. |
R1-2307307 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Apple |
R1-2307360 | Discussion on dynamic switching between DFT-s-OFDM and CP-OFDM | xiaomi |
R1-2307414 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Lenovo |
R1-2307436 | Dynamic switching between DFT-S-OFDM and CP-OFDM for Rel-18 CovEnh | Sharp |
R1-2307494 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | NTT DOCOMO, INC. |
R1-2307560 | Considerations on dynamic switching between DFT-S-OFDM and CP-OFDM | OPPO |
R1-2307627 | Discussion on dynamic waveform switchin between DFT-s-OFDM and CP-OFDM | China Telecom |
R1-2307633 | Discussion on dynamic switching between DFT-S-OFDM and CP-OFDM | Google Inc. |
R1-2307704 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Samsung |
R1-2307726 | Discussion on solutions for NR dynamic switching between DFT-S-OFDM and CP-OFDM | Mavenir |
R1-2307754 | Dynamic switching between DFT-S-OFDM and CP-OFDM | ETRI |
R1-2307769 | Discussion of dynamic switching between DFT-S-OFDM and CP-OFDM | Transsion Holdings |
R1-2307846 | Discussion on Dynamic UL Waveform Switching | Ericsson |
R1-2307953 | Dynamic switching between DFT-S-OFDM and CP-OFDM | Qualcomm Incorporated |
R1-2308013 | Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2308014 | Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2308015 | Summary #3 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
R1-2308062 | Dynamic waveform switching | MediaTek Inc. |
R1-2308364 | Draft LS on Reporting of power headroom information for an assumed PUSCH | Moderator (InterDigital, Inc.) |
R1-2308376 | LS on power headroom information for an assumed PUSCH | RAN1, InterDigital, Inc. |
R1-2308476 | Draft LS on Details of power headroom information for assumed PUSCH | Moderator (InterDigital, Inc.) |
R1-2308477 | LS on Details of power headroom information for assumed PUSCH | RAN1, InterDigital, Inc. |
R1-2308478 | Summary #4 on dynamic switching between DFT-S-OFDM and CP-OFDM | Moderator (InterDigital, Inc.) |
TDoc | Title | Source |
---|---|---|
R1-2308552 | Session notes for 9.13 (NR support for dedicated spectrum less than 5MHz for FR1) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2306393 | Open issues of dedicated spectrum less than 5MHz for FR1 | TD Tech, Chengdu TD Tech |
R1-2306437 | Discussion on less than 5 MHz dedicated spectrum | FUTUREWEI |
R1-2306531 | Discussion on dedicated spectrum less than 5 MHz for FR1 | Huawei, HiSilicon |
R1-2306670 | Discussion on enhancements to operate NR on dedicated spectrum | Spreadtrum Communications |
R1-2306775 | Remaining issues on NR support for dedicated spectrum less than 5MHz | vivo |
R1-2306897 | NR support for below 5 MHz BW | Nokia, Nokia Shanghai Bell |
R1-2306987 | Discussion on NR operation for dedicated spectrum less than 5 MHz | ZTE |
R1-2307308 | NR support of spectrum less than 5MHz for FR1 | Apple |
R1-2307361 | Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz | xiaomi |
R1-2307415 | Enhancements to operate NR on dedicated spectrum less than 5 MHz | Lenovo |
R1-2307495 | Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz | NTT DOCOMO, INC. |
R1-2307705 | Enhancements to operate NR on dedicated spectrum less than 5 MHz | Samsung |
R1-2307770 | Discussion on Enhancements on NR dedicated spectrum less than 5MH | Transsion Holdings |
R1-2307796 | Discussion on enhancements for dedicated spectrum less than 5 MHz | LG Electronics |
R1-2307800 | NR support of spectrum less than 5MHz for FR1 | Ericsson |
R1-2307954 | NR support for dedicated spectrum less than 5MHz for FR1 | Qualcomm Incorporated |
R1-2308040 | On dedicated spectrum less than 5 MHz | MediaTek Inc. |
R1-2308406 | Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2308422 | Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2308587 | Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
R1-2308607 | Summary#4 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz | Moderator (Lenovo) |
TDoc | Title | Source |
---|---|---|
R1-2308550 | Session notes for 9.14 (Study on Self-Evaluation towards the 3GPP submission of a IMT-2020 Satellite Radio Interface Technology) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2306507 | Evaluation methodology of IMT-2020 satellite | Huawei, HiSilicon |
R1-2306567 | Discussion on the evaluation methodology of the self-evaluation | ZTE |
R1-2307247 | Remaining discussion on evaluation methodology for IMT-2020 Satellite submission | Nokia, Nokia Shanghai Bell |
R1-2307551 | Discussion on self-evaluation methodology for IMT-2020 satellite radio interface | OPPO |
R1-2307706 | Discussion on remaining issues for evaluation methodology | Samsung |
R1-2307729 | Consideration on IMT-2020 Satellite self-evaluation | THALES |
R1-2307955 | Further discussion on self-evaluation assumptions | Qualcomm Incorporated |
R1-2308233 | Feature lead summary on Evaluation Methodology for IMT-2020 satellite | Moderator (Qualcomm Incorporated) |
R1-2308748 | [Post-114-ITU-Sat-01] Email discussion on link budget template | Moderator (Qualcomm Incorporated) |
TDoc | Title | Source |
---|---|---|
R1-2306407 | Simulation results for the study on self-evaluation towards the IMT-2020 of the 3GPP Satellite RIT | THALES |
R1-2306414 | Feature Lead Summary #1 on self-evaluation results for NR NTN | Moderator (THALES) |
R1-2306415 | Feature Lead Summary #2 on self-evaluation results for NR NTN | Moderator (THALES) |
R1-2306416 | Feature Lead Summary #3 on self-evaluation results for NR NTN | Moderator (THALES) |
R1-2306417 | Feature Lead Summary #4 on self-evaluation results for NR NTN | Moderator (THALES) |
R1-2306508 | Self-evaluation results for NR NTN | Huawei, HiSilicon |
R1-2306568 | Discussion on the Self-evaluation results for NR NTN | ZTE |
R1-2307067 | Initial evaluation result for NR NTN | CATT |
R1-2307248 | Initial evaluation results related to IMT-2020 Satellite for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2307362 | Self-evaluation results for NR NTN | xiaomi |
R1-2307407 | Initial evaluation results on NR-NTN for self-evaluation of IMT-2020 satellite radio interface technology | Panasonic |
R1-2307496 | Calibration results and peak data rate analysis for NR NTN | NTT DOCOMO, INC. |
R1-2307552 | Self-evaluation results for NR NTN | OPPO |
R1-2307707 | Discussion on evaluation results for NR NTN | Samsung |
R1-2307774 | Satellite IMT-2020 self-evaluation: Peak data rate and spectral efficiency | Ericsson |
R1-2307956 | Self-evaluation results for NR NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R1-2306509 | Self-evaluation results for IoT NTN | Huawei, HiSilicon |
R1-2306569 | Discussion on the Self-evaluation results for IoT NTN | ZTE |
R1-2307553 | Self-evaluation results for IoT NTN | OPPO |
R1-2307708 | Discussion on evaluation results for IoT NTN | Samsung |
R1-2307957 | Self-evaluation results for IOT NTN | Qualcomm Incorporated |
R1-2308033 | Self-evaluation results for IoT NTN | MediaTek Inc. |
R1-2308410 | Feature Lead summary for 9.14.3: Self-Evaluation Results for IoT NTN | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2306882 | Rel-18 TEI on complexity reduction solutions for FR2 | Spreadtrum Communications |
R1-2306988 | On PUSCH repetition type A scheduled by DCI format 0-0 with CRC scrambled by C-RNTI | ZTE, China Telecom, Sanechips, NTT DOCOMO, INC. |
R1-2307518 | TEI on the introduction of a UE capability with up to 6-layer DL MIMO | OPPO, CMCC, China Telecom, NTT DOCOMO, Lenovo, China Unicom |
R1-2307958 | Rel-18 RAN1 TEI proposals | Qualcomm Incorporated |
R1-2308312 | Summary #1 on Rel-18 TEIs | Moderator (NTT DOCOMO, INC.) |
R1-2308485 | Summary #2 on Rel-18 TEIs | Moderator (NTT DOCOMO, INC.) |
R1-2308486 | Draft reply LS on longer CG-SDT periodicities | Moderator (NTT DOCOMO, INC.) |
R1-2308487 | Reply LS on longer CG-SDT periodicities | RAN1, NTT DOCOMO, INC. |
R1-2308553 | Summary #3 on Rel-18 TEIs | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2308518 | Updated RAN1 UE features list for Rel-18 LTE after RAN1#114 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2308519 | Draft LS on Rel-18 RAN1 UE features list for LTE after RAN1#114 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2308520 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#115 | RAN1, AT&T, NTT DOCOMO, INC. |
R1-2308521 | Updated RAN1 UE features list for Rel-18 NR after RAN1#114 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2308522 | Draft LS on Rel-18 RAN1 UE features list for NR after RAN1#114 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2308523 | LS on Rel-18 RAN1 UE features list for NR after RAN1#114 | RAN1, AT&T, NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R1-2306540 | UE features for NR MIMO evolution | Huawei, HiSilicon |
R1-2306583 | On UE features for Rel. 18 MIMO evolution WI | Nokia, Nokia Shanghai Bell |
R1-2306618 | Discussion on UE features for NR MIMO evolution | ZTE |
R1-2306671 | Discussion on UE features for NR MIMO evolution | Spreadtrum Communications |
R1-2306776 | Discussion on Rel-18 MIMO UE features | vivo |
R1-2306852 | UE features for NR-MIMO evolution | Intel Corporation |
R1-2306965 | UE feature on NR MIMO evolution | |
R1-2307068 | On UE features for NR MIMO evolution | CATT |
R1-2307230 | Discussion on UE features for Rel18 MIMO | Ericsson |
R1-2307309 | Views on UE features for Rel-18 NR MIMO evolution | Apple |
R1-2307363 | Discussion on UE features for MIMO evolution | xiaomi |
R1-2307497 | Discussion on UE features for NR MIMO evolution | NTT DOCOMO, INC. |
R1-2307519 | UE features for Rel-18 MIMO evolution | OPPO |
R1-2307709 | UE features for Rel-18 MIMO | Samsung |
R1-2307877 | Summary of UE features for NR MIMO evolution | Moderator (AT&T) |
R1-2307959 | UE features for NR MIMO evolution | Qualcomm Incorporated |
R1-2308066 | UE Features for NR MIMO Evolution | MediaTek Inc. |
R1-2308574 | Session Notes of AI 9.16.1 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306501 | UE features for Rel-18 expanded and improved positioning | Huawei, HiSilicon |
R1-2306584 | On UE features for expanded and improved NR positioning | Nokia, Nokia Shanghai Bell |
R1-2306672 | Discussion on UE features for expanded and improved NR positioning | Spreadtrum Communications |
R1-2306688 | Discussion on Rel-18 Positioning UE features | TOYOTA InfoTechnology Center |
R1-2306777 | Discussion on Rel-18 positioning UE features | vivo |
R1-2306846 | UE features for Rel-18 expanded and improved NR Positioning | Intel Corporation |
R1-2306869 | Discussion on UE feature for Rel-18 NR positioning | ZTE |
R1-2307110 | Further discussion on UE features for expanded and improved NR positioning | CATT |
R1-2307310 | On UE features for expanded and improved NR positioning | Apple |
R1-2307368 | Discussion on UE features for expanded and improved NR positioning | xiaomi |
R1-2307498 | Discussion on UE features for expanded and improved NR positioning | NTT DOCOMO, INC. |
R1-2307576 | Discussion on UE features for expanded and improved NR positioning | OPPO |
R1-2307710 | UE features for expanded and improved NR positioning | Samsung |
R1-2307878 | Summary of UE features for expanded and improved NR positioning | Moderator (AT&T) |
R1-2307960 | UE features on Expanded and improved NR Positioning | Qualcomm Incorporated |
R1-2308121 | Views on UE features for expanded and improved NR Positioning | IIT Kanpur, CEWiT |
R1-2308122 | Views on UE features for expanded and improved NR Positioning | IIT Kanpur, CEWiT |
R1-2308123 | Views on UE features for expanded and improved NR Positioning | IIT Kanpur, CEWiT |
R1-2308124 | Views on UE features for expanded and improved NR Positioning | IIT Kanpur, CEWiT |
R1-2308173 | UE features for expanded and improved NR positioning | Ericsson |
R1-2308575 | Session Notes of AI 9.16.2 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306506 | UE features for Rel-18 network energy saving | Huawei, HiSilicon |
R1-2306585 | Initial views on UE features for NR network energy savings | Nokia, Nokia Shanghai Bell |
R1-2306778 | Discussions on UE features for network energy saving | vivo |
R1-2306830 | Discussion on UE features for NES | Intel Corporation |
R1-2307070 | Discussion on Rel-18 UE features for Network Energy Saving | CATT |
R1-2307145 | Discussion on UE features for NES | ZTE, Sanechips |
R1-2307499 | Discussion on UE features for NR NW energy savings | NTT DOCOMO, INC. |
R1-2307542 | Discussion on UE features for NR network energy savings | OPPO |
R1-2307711 | UE features for NR network energy savings | Samsung |
R1-2307879 | Summary of UE features for NR network energy savings | Moderator (AT&T) |
R1-2307961 | UE features for NES | Qualcomm Incorporated |
R1-2307992 | UE features for network energy savings | Ericsson |
R1-2308083 | On UE features for NR network energy savings | MediaTek Inc. |
R1-2308576 | Session Notes of AI 9.16.3 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306517 | Discussions on UE features for NR NCR | Huawei, HiSilicon |
R1-2306570 | Discussion on UE features for NCR | ZTE |
R1-2306586 | On UE features for NR NCR | Nokia, Nokia Shanghai Bell |
R1-2306779 | Discussion on UE feature for NCR | vivo |
R1-2306834 | Dicussion on UE feature for NCR | Intel Corporation |
R1-2306925 | Views on UE features for NR NCR | Sony |
R1-2307071 | Discussion on UE features for NCR | CATT |
R1-2307106 | UE features for NCR | Ericsson |
R1-2307167 | Discussion on UE features for NCR | Fujitsu |
R1-2307220 | Discussion on UE feature of NR NCR | CMCC |
R1-2307311 | Views on UE features for Rel-18 NR NCR | Apple |
R1-2307500 | Discussion on UE features for NR NCR | NTT DOCOMO, INC. |
R1-2307712 | UE features for NR NCR | Samsung |
R1-2307755 | Discussion on NCR features | ETRI |
R1-2307880 | Summary of UE features for NR NCR | Moderator (AT&T) |
R1-2307962 | UE features on NR NCR | Qualcomm Incorporated |
R1-2308577 | Session Notes of AI 9.16.4 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306492 | UE features for NR NTN enhancements | Huawei, HiSilicon |
R1-2306571 | Discussion on UE features for NR-NTN | ZTE |
R1-2306587 | On UE features for NR NTN enhancements | Nokia, Nokia Shanghai Bell |
R1-2306673 | Discussions on UE feature of NR NTN enhancements | Spreadtrum Communications |
R1-2306780 | Discussions on UE features of NR NTN enhancements | vivo |
R1-2306823 | On UE features for NR NTN enhancements | Ericsson |
R1-2307125 | Discussion on the UE features for NR NTN enhancements. | NEC |
R1-2307312 | Discussion on UE Features for Rel-18 NR NTN Enhancements | Apple |
R1-2307369 | Discussion on the UE features for NR NTN | xiaomi |
R1-2307501 | Discussion on UE features for NR NTN enhancements | NTT DOCOMO, INC. |
R1-2307549 | Discussion on UE features for NR NTN enhancements | OPPO |
R1-2307713 | UE features for NR NTN enhancements | Samsung |
R1-2307881 | Summary of UE features for NR NTN enhancements | Moderator (AT&T) |
R1-2307963 | UE features on NR NTN enhancements | Qualcomm Incorporated |
R1-2308043 | UE features for NR NTN | MediaTek Inc. |
R1-2308578 | Session Notes of AI 9.16.5 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306520 | UE features on R18 Mobility Enhancement | Huawei, HiSilicon |
R1-2306588 | Iniitial views on UE features for NR mobility enhancements | Nokia, Nokia Shanghai Bell |
R1-2306619 | Discussion on UE features for NR mobility enhancements | ZTE |
R1-2306781 | Discussion on Rel-18 NR mobility enhancement UE features | vivo |
R1-2307107 | UE features for NR mobility enhancements | Ericsson |
R1-2307313 | On UE features for NR mobility enhancements | Apple |
R1-2307528 | Discussion on UE features for NR mobility enhancements | OPPO |
R1-2307714 | UE features for mobility | Samsung |
R1-2307882 | Summary of UE features for NR mobility enhancements | Moderator (AT&T) |
R1-2307964 | UE features on NR mobility enhancements | Qualcomm Incorporated |
R1-2308579 | Session Notes of AI 9.16.6 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306525 | UE features for NR sidelink evolution | Huawei, HiSilicon |
R1-2306589 | On UE features for NR sidelink evolution | Nokia, Nokia Shanghai Bell |
R1-2306674 | Discussion on UE features for NR sidelink evolution | Spreadtrum Communications |
R1-2306782 | Discussion on UE features for Rel-18 sidelink | vivo |
R1-2307072 | Discussion on UE features for NR sidelink evolution | CATT, GOHIGH |
R1-2307314 | Discussion on UE features for Rel-18 NR Sidelink Evolution | Apple |
R1-2307370 | Discussion on UE features for NR sidelink evolution | xiaomi |
R1-2307502 | Discussion on UE features for NR SL evolution | NTT DOCOMO, INC. |
R1-2307577 | UE features list for Rel-18 NR sidelink evolution WI | OPPO, Huawei, HiSilicon, LG Electronics |
R1-2307604 | Discussion on UE features for NR sidelink evolution | ZTE, Sanechips |
R1-2307715 | UE features for NR sidelink evolution | Samsung |
R1-2307965 | UE Features for Sidelink Evolution | Qualcomm Incorporated |
R1-2308078 | Discussion on UE feature for Rel-18 SL evolution | MediaTek Inc. |
R1-2308502 | Summary on UE features for NR sidelink evolution | Moderator (NTT DOCOMO, INC.) |
R1-2308510 | Session Notes for 9.16.7 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306436 | Discussion on UE features for R18 RedCap | FUTUREWEI |
R1-2306530 | UE features for eRedCap | Huawei, HiSilicon |
R1-2306590 | On UE features for eRedCap | Nokia, Nokia Shanghai Bell |
R1-2306675 | Discussion on UE features for eRedCap | Spreadtrum Communications |
R1-2306684 | UE features for eRedCap | Ericsson |
R1-2306783 | Discussion on UE features for R18 eRedCap | vivo |
R1-2307003 | UE Feature for Rel-18 RedCap UE | NEC |
R1-2307073 | Discussion on UE features for R18 RedCap | CATT |
R1-2307146 | Discussion on UE features for eRedcap | ZTE, Sanechips |
R1-2307221 | Discussion on UE features for R18 eRedCap | CMCC |
R1-2307315 | On UE features for eRedcap | Apple |
R1-2307371 | Discussion on UE features for eRedCap | xiaomi |
R1-2307503 | Discussion on UE features for eRedCap | NTT DOCOMO, INC. |
R1-2307561 | Rel-18 eRedCap UE features | OPPO |
R1-2307716 | UE features for eRedCap | Samsung |
R1-2307966 | UE features for eRedCap | Qualcomm Incorporated |
R1-2308041 | UE features for eRedCap | MediaTek Inc. |
R1-2308503 | Summary on UE features for eRedCap | Moderator (NTT DOCOMO, INC.) |
R1-2308511 | Session Notes for 9.16.8 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306503 | Discussion on UE features for MC enhancements | Huawei, HiSilicon |
R1-2306591 | On UE features for MC enhancements | Nokia, Nokia Shanghai Bell |
R1-2306676 | Discussion on UE features for multi-carrier enhancement | Spreadtrum Communications |
R1-2306784 | Discussion on UE features for Multi-carrier enhancements | vivo |
R1-2306989 | Discussion on UE feature for MC enhancements | ZTE |
R1-2307074 | Discussion on UE features for Multi-carrier enhancements | CATT |
R1-2307316 | Views on UE features for Rel-18 MC enhancements | Apple |
R1-2307372 | Discussion on UE features for MC enhancements | xiaomi |
R1-2307504 | Discussion on UE features for Multi-carrier enhancements | NTT DOCOMO, INC. |
R1-2307578 | Discussion on UE features for multi-carrier enhancement | OPPO |
R1-2307717 | UE features for multi-carrier enhancements | Samsung |
R1-2307797 | Discussion on UE features for MC enhancements | LG Electronics |
R1-2307967 | UE features for MC enhancements | Qualcomm Incorporated |
R1-2307993 | UE features for MCE | Ericsson |
R1-2308080 | On UE feature discussion for Rel-18 MC enhancements | MediaTek Inc. |
R1-2308504 | Summary on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2308512 | Session Notes for 9.16.9 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306527 | UE features for Rel-18 XR | Huawei, HiSilicon |
R1-2306592 | Initial views on UE features for XR enhancements | Nokia, Nokia Shanghai Bell |
R1-2306608 | On UE features for XR enhancements | Ericsson |
R1-2306627 | Initial UE feature list for XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
R1-2306785 | Discussion on Rel-18 XR UE features | vivo |
R1-2307069 | Discussion on Rel-18 UE features for XR in RAN1 | CATT |
R1-2307147 | Discussion on UE features for XR enhancements | ZTE, Sanechips |
R1-2307317 | Views on UE features for XR enhancements | Apple |
R1-2307505 | Discussion on UE features for Rel-18 XR enhancements | NTT DOCOMO, INC. |
R1-2307579 | Discussion on UE features for XR | OPPO |
R1-2307718 | UE features for XR | Samsung |
R1-2308505 | Summary on UE features for XR enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2308513 | Session Notes for 9.16.10 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306493 | UE features for IoT NTN enhancements | Huawei, HiSilicon |
R1-2306572 | Discussion on UE features for IoT-NTN | ZTE |
R1-2306593 | On UE features for IoT NTN enhancements | Nokia, Nokia Shanghai Bell |
R1-2306677 | Discussion on UE features for IoT NTN enhancements | Spreadtrum Communications |
R1-2307318 | Discussion on UE features for Rel-18 IoT NTN Enhancements | Apple |
R1-2307364 | Discussion on the UE features for IoT NTN | xiaomi |
R1-2307550 | Discussion on UE features for IoT NTN enhancements | OPPO |
R1-2307719 | UE features for IoT NTN enhancements | Samsung |
R1-2307802 | On UE features for IoT NTN enhancements | Ericsson |
R1-2307883 | Summary of UE features for IoT NTN enhancements | Moderator (AT&T) |
R1-2307968 | UE features for IOT NTN | Qualcomm Incorporated |
R1-2308580 | Session Notes of AI 9.16.11 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306438 | Discussion on UE features for less than 5 MHz dedicated spectrum | FUTUREWEI |
R1-2306532 | UE features for Rel-18 dedicated spectrum less than 5MHz | Huawei, HiSilicon |
R1-2306594 | On UE features for dedicated spectrum less than 5MHz | Nokia, Nokia Shanghai Bell |
R1-2306678 | Discussion on UE features for dedicated spectrum less than 5MHz | Spreadtrum Communications |
R1-2306786 | Discussion on UE features for dedicated spectrum less than 5MHz | vivo |
R1-2306990 | Discussion on UE feature for dedicated spectrum less than 5MHz | ZTE |
R1-2307319 | On UE features for dedicated spectrum less than 5MHz | Apple |
R1-2307506 | Discussion on UE features for dedicated spectrum less than 5MHz | NTT DOCOMO, INC. |
R1-2307720 | UE features for dedicated spectrum less than 5MHz | Samsung |
R1-2307801 | On UE features for LessThan5MHzFR1 | Ericsson |
R1-2307969 | UE features for dedicated spectrum less than 5MHz | Qualcomm Incorporated |
R1-2308506 | Summary on UE features for dedicated spectrum less than 5MHz | Moderator (NTT DOCOMO, INC.) |
R1-2308514 | Session Notes for 9.16.12 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306484 | UE features for eDSS | Huawei, HiSilicon |
R1-2306595 | On UE features for eDSS | Nokia, Nokia Shanghai Bell |
R1-2306679 | Discussion on UE features for eDSS | Spreadtrum Communications |
R1-2306787 | Discussion on UE features for eDSS | vivo |
R1-2306991 | Discussion on UE feature for eDSS | ZTE |
R1-2307320 | Views On UE features for Rel-18 NR eDSS | Apple |
R1-2307365 | Discussion on UE features for eDSS | xiaomi |
R1-2307507 | Discussion on UE features for eDSS | NTT DOCOMO, INC. |
R1-2307580 | Discussion on UE features for eDSS enhancement | OPPO |
R1-2307721 | UE features for eDSS | Samsung |
R1-2307970 | UE features for eDSS | Qualcomm Incorporated |
R1-2307994 | UE features for Rel18 DSS Enhancements | Ericsson |
R1-2308507 | Summary on UE features for eDSS | Moderator (NTT DOCOMO, INC.) |
R1-2308515 | Session Notes for 9.16.13 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306596 | On UE features for BWP without restriction | Nokia, Nokia Shanghai Bell |
R1-2306603 | UE features for BWP without restriction | Ericsson |
R1-2306788 | Discussion on UE features for BWP without restriction | vivo |
R1-2306992 | Discussion on UE feature for BWP without restriction | ZTE |
R1-2307321 | On UE features for BWP without restriction | Apple |
R1-2307508 | Discussion on UE features for BWP without restriction | NTT DOCOMO, INC. |
R1-2307722 | UE features for BWP without restriction | Samsung |
R1-2307803 | Updated RAN1 UE features list for BWP Without Restriction for Rel-18 NR | Vodafone |
R1-2307884 | Summary of UE features for BWP without restriction | Moderator (AT&T) |
R1-2307971 | UE features for BWP without restriction | Qualcomm Incorporated |
R1-2308042 | UE features for BWP without restriction | MediaTek Inc. |
R1-2308145 | UE features for BWP without restriction | Huawei, HiSilicon |
R1-2308581 | Session Notes of AI 9.16.14 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2306553 | UE features for Coverage Enhancement | Huawei, HiSilicon |
R1-2306597 | Initial views on UE features for coverage enhancements | Nokia, Nokia Shanghai Bell |
R1-2306789 | Discussions on UE features of NR coverage enhancements | vivo |
R1-2306993 | Discussion on UE feature for coverage enhancements | ZTE |
R1-2307322 | Views on UE features for Rel-18 NR coverage enhancements | Apple |
R1-2307366 | Discussion on UE features for coverage enhancements | xiaomi |
R1-2307509 | Initial views on UE features for NR further coverage enhancements | NTT DOCOMO, INC. |
R1-2307562 | Rel-18 UE features for coverage enhancements | OPPO |
R1-2307628 | Initial UE feature for Rel-18 coverage enhancements | Rapporteur (China Telecom) |
R1-2307723 | UE features for Coverage Enhancements | Samsung |
R1-2307847 | UE Features for Coverage Enhancements | Ericsson |
R1-2307972 | UE features for coverage enhancements | Qualcomm Incorporated |
R1-2308508 | Summary on UE features for coverage enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2308516 | Session Notes for 9.16.15 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306528 | UE features for endorsed Rel-18 TEI on HARQ multiplexing | Huawei, HiSilicon, Ericsson, China Unicom |
R1-2306598 | On UE features for TEI18 | Nokia, Nokia Shanghai Bell |
R1-2306994 | Discussion on UE feature for Rel-18 TEI | ZTE |
R1-2307367 | UE features for endorsed Rel-18 TEI on pathloss RS for Type 1 CG-PUSCH | xiaomi |
R1-2308509 | Summary on UE features for TEIs | Moderator (NTT DOCOMO, INC.) |
R1-2308517 | Session Notes for 9.16.16 | Ad-Hoc Chair (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2306485 | Discussions on draft CRs and higher layer signalling for other Rel-18 items | Huawei, HiSilicon |
R1-2306790 | Discussion on remaininig issues of Rel-18 Multi-carrier and NCR enhancements | vivo |
R1-2306827 | Discussion on remaining issues for multi-carrier enhancement | Intel Corporation |
R1-2306995 | Draft CRs and higher layer signalling for others | ZTE |
R1-2307052 | Discussion on remaining issues on MCE and NCR | CATT |
R1-2307222 | Discussion on Rel-18 NCR | CMCC |
R1-2307225 | Discussion on remaining issues of Rel-18 multi-carrier enhancement | Lenovo |
R1-2307323 | Views on draft CRs and remaining issues for Rel-18 MC enhancements | Apple |
R1-2307373 | CR and Higher layer signalling for Rel-18 TEI on pathloss RS for Type 1 CG-PUSCH and MC-Enh | xiaomi |
R1-2307510 | Discussion on higher layer parameters and remaining issues on Rel-18 Wis | NTT DOCOMO, INC. |
R1-2307581 | Discussion on Rel-18 higher layer parameters | OPPO |
R1-2307629 | On TS38.214 CR for Rel-18 UL Tx switching | China Telecom |
R1-2307724 | Discussion on higher layer signalling for multi-carrier enhancements | Samsung |
R1-2307736 | On Rel-18 MC-enhancements | Nokia, Nokia Shanghai Bell |
R1-2307756 | Discussion on NCR maintenance | ETRI |
R1-2307798 | Remaining issues on Rel-18 MC enhancements | LG Electronics |
R1-2307804 | Open issues in Higher Layer Parameters for BWP without restrictions | Vodafone, vivo |
R1-2307973 | Views on draft CRs and higher layer signalling for R18 MC enhancements | Qualcomm Incorporated |
R1-2307995 | Discussion on higher layer signaling and remaining issues for NR Rel-18 | Ericsson |
R1-2308079 | On maintenance for MC-Enhancement | MediaTek Inc. |
R1-2308590 | Summary of NR_BWP_wor higher layer signalling email discussion | Moderator (Vodafone) |
R1-2308616 | Post RAN1#114 initial input for RRC of Rel-18 TEI on mDCI based mTRP | Moderator (Qualcomm) |
R1-2308626 | Summary of discussion on higher layer signalling for MC-Enh | Moderator (NTT DOCOMO, INC.) |
R1-2308655 | Summary of discussions on high layer parameters for endorsed Rel-18 TEI on HARQ multiplexing on PUSCH | Moderator (HiSilicon) |
R1-2308662 | Summary of discussion on higher layer signalling for Rel-18 TEI on pathloss RS for Type 1 CG-PUSCH | Moderator (xiaomi) |