TDoc | Title | Source |
---|---|---|
R1-2405780 | Draft Agenda of RAN1#118 meeting | RAN1 Chair |
R1-2405783 | RAN1#118 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
R1-2407209 | RAN1#118 Meeting Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2405781 | Highlights from RAN#104 | RAN1 Chair |
TDoc | Title | Source |
---|---|---|
R1-2405782 | Report of RAN1#117 meeting | ETSI MCC |
TDoc | Title | Source |
---|---|---|
R1-2405784 | LS on RACH during uplink transmission extension | RAN2, Samsung |
R1-2405785 | LS on DL coverage enhancements | RAN2, CMCC |
R1-2405786 | LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | RAN2, ZTE |
R1-2405787 | Reply LS on Rel-18 higher-layers parameter list | RAN2, Ericsson |
R1-2405788 | LS on synchronization source change at the transmitting anchor UE in SL positioning | RAN4, Ericsson |
R1-2405789 | Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 | RAN4, Qualcomm |
R1-2405790 | LS on inconsistent issue between extended k1 range and RRC parameter DL-DataToUL-ACK-v1700 for R17 NTN | RAN4, CMCC |
R1-2405791 | LS on UE capability for multi-carrier enhancement | RAN4, vivo |
R1-2405792 | Reply LS on LTM L1 intra and inter-frequency measurements | RAN4, Ericsson |
R1-2405793 | Reply LS on reference point for SSB-TimeOffset | RAN4, Apple |
R1-2405794 | LS on RAN4 UE feature list for Rel-18 (version 5) | RAN4, CMCC |
R1-2405795 | LS on terminology definitions for AI-ML in NG-RAN | RAN3, Ericsson |
R1-2405796 | LS on Clarification of requirements for Ambient IoT | SA2, Ericsson |
R1-2405797 | Reply LS RP-240891 on NTZ solution impacts to RAN | RAN, InterDigital |
R1-2405798 | LS on Avoiding Cross-TSG TEI | RAN, NEC |
R1-2405799 | Reply LS on SLPP parameters provision | RAN2, vivo |
R1-2405830 | On LS on Clarification of requirements for Ambient IoT | Ericsson |
R1-2405841 | Discussion on the reply of LS on DL coverage enhancement | Huawei, HiSilicon |
R1-2405896 | Draft Reply LS on Clarification of requirements for Ambient IoT | Spreadtrum Communications |
R1-2405897 | Discussion on LS on DL coverage enhancements | Spreadtrum Communications |
R1-2405964 | LS on Physical Properties of Sensing Targets in Automotive Scenarios for ISAC | 5GAA, Huawei, Continental Corp. |
R1-2405971 | Discussion on LS on DL coverage enhancements | CMCC |
R1-2405972 | Draft Reply LS on DL coverage enhancements | CMCC |
R1-2405973 | Discussion on the UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | CMCC |
R1-2406122 | Discussion of RAN2 LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Ericsson |
R1-2406124 | Discussion on UL synchronization for contention based Msg3 transmission without Msg1Msg2 | ZTE Corporation, Sanechips |
R1-2406125 | [Draft] Reply LS on UL synchronization for contention based Msg3 transmission without Msg1Msg2 | ZTE Corporation, Sanechips |
R1-2406126 | Discussion on LS on DL coverage enhancements | ZTE Corporation, Sanechips |
R1-2406145 | Draft reply LS on clarification of requirements for Ambient IoT | vivo |
R1-2406146 | Discussion on LS on DL coverage enhancements | vivo |
R1-2406147 | Draft reply LS on DL coverage enhancements | vivo |
R1-2406148 | Discussion on LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | vivo |
R1-2406149 | Draft reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | vivo |
R1-2406150 | Draft reply LS on synchronization source change at the transmitting anchor UE in SL positioning | vivo |
R1-2406218 | Discussion on LS from RAN4 on synchronization source change | OPPO |
R1-2406219 | Draft reply LS to RAN4 on synchronization source change | OPPO |
R1-2406220 | Discussion on RACH during uplink transmission extension | OPPO |
R1-2406221 | Draft reply LS on RACH during uplink transmission extension | OPPO |
R1-2406233 | Discussion on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | OPPO |
R1-2406234 | Draft reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | OPPO |
R1-2406235 | Discussion on DL coverage enhancements | OPPO |
R1-2406236 | Draft reply LS on DL coverage enhancements | OPPO |
R1-2406246 | Discussion on LS from SA2 on clarification of requirements for Ambient IoT | OPPO |
R1-2406247 | Draft reply LS to SA2 on clarification of requirements for Ambient IoT | OPPO |
R1-2406251 | Discussion of 5GAA LS on ISAC | OPPO |
R1-2406267 | Discussion on the SA2 LS on the requirements of Ambient IoT | Xiaomi |
R1-2406268 | Draft reply LS on clarification of requirements for Ambient IoT | Xiaomi |
R1-2406319 | Draft Reply LS on Clarification of requirements for Ambient IoT | CATT |
R1-2406320 | Discussion on LS reply on DL coverage enhancements | CATT |
R1-2406321 | Discussion on LS reply on UL synchronization for contention based Msg3 transmission | CATT |
R1-2406322 | Discussion on synchronization source change at the transmitting anchor UE in SL positioning | CATT, CICTCI |
R1-2406323 | Draft reply LS on synchronization source change at the transmitting anchor UE in SL positioning | CATT, CICTCI |
R1-2406398 | Discussion on requirements for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406399 | Draft reply to LS on requirements for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406425 | Discussion on RAN2 LS on RACH during uplink transmission extension | Nokia, Nokia Shanghai Bell |
R1-2406426 | Discussion on RAN2 LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Nokia, Nokia Shanghai Bell |
R1-2406532 | Draft LS reply on synchronization source change at the transmitting anchor UE in SL positioning | Intel Corporation |
R1-2406551 | Discussion on RAN2 LS on DL coverage enhancements | NEC |
R1-2406552 | Discussion on RAN2 LS on UL synchronization for contention based Msg3 transmission without Msg1Msg2 | NEC |
R1-2406616 | Discussion on RAN2 LS for DL coverage enhancements | Samsung |
R1-2406617 | Discussion on RAN4 LS on synchronization source change in SL positioning | Samsung |
R1-2406675 | Discussion of RAN4 LS on synchronization source change at the transmitting anchor UE in SL positioning | Nokia |
R1-2406753 | Discussion of LS response related to DL coverage enhancements for NR over NTN operation | Nokia |
R1-2406816 | Discussion on RAN2 LS on DL Coverage Enhancements | Apple |
R1-2406817 | Draft Reply LS to RAN2 on DL Coverage Enhancements | Apple |
R1-2406818 | Discussion on RAN2 LS on RACH during uplink transmission extension | Apple |
R1-2406819 | Discussion on RAN2 LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Apple |
R1-2406820 | Draft Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Apple |
R1-2406876 | [Draft] Reply LS on DL coverage enhancements | Ericsson |
R1-2406877 | Discussion on RAN2 LS on DL coverage enhancements | Ericsson |
R1-2406903 | Discussion on LS on Physical Properties of Sensing Targets in Automotive Scenarios for ISAC | Ericsson |
R1-2406952 | Draft reply LS on synchronization source change at Tx UE in SL positioning | ZTE Corporation, Sanechips |
R1-2406981 | Discussion on LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Huawei, HiSilicon |
R1-2406982 | Discussion on SA2 LS on Clarification of requirements for Ambient IoT | Huawei, HiSilicon |
R1-2406998 | Discussion on synchronization source change at the transmitting anchor UE in SL positioning | Huawei, HiSilicon |
R1-2407006 | On RACH during uplink transmission extension for NTN IOT | Qualcomm Incorporated |
R1-2407007 | On contention based Msg3 transmission without Msg1/Msg2 for NTN IOT | Qualcomm Incorporated |
R1-2407008 | Draft reply LS on Clarification of requirements for Ambient IoT | Qualcomm Incorporated |
R1-2407167 | Discussion on LS on synchronization source change at the transmitting anchor UE in SL positioning | Ericsson |
R1-2407168 | Discussion on LS to RAN1 on 4 ARP IDs in SLPP reports | Ericsson |
R1-2407221 | On contention based Msg3 transmission without Msg1/Msg2 for NTN IOT | Qualcomm Incorporated |
R1-2407383 | Reply LS on UE capability for multi-carrier enhancements | RAN2, NTT DOCOMO |
R1-2407413 | LS on power control parameters for unified TCI state framework | RAN2, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2405836 | Corrections on Rel-17 MBS broadcast scrambling to TS 38.211 | Huawei, HiSilicon |
R1-2405837 | Correction on the timing of Msg3 retransmission in NTN | Huawei, HiSilicon |
R1-2405874 | Discussion on transmission power for simultaneously transmitted SRS resources | Huawei, HiSilicon |
R1-2405947 | Draft CR on RRC parameter correction for SRS power control | |
R1-2406112 | Draft CR on PDSCH scrambling for MBS | ZTE Corporation, Sanechips |
R1-2406113 | Draft CR on PDSCH reception for MBS | ZTE Corporation, Sanechips |
R1-2406127 | Correction on timing of Msg3 retransmission in NTN | ZTE Corporation, Sanechips |
R1-2406324 | UE procedure for applying transform precoding on PUSCH from Rel-17 | CATT, Nokia |
R1-2406325 | Clarification on UE procedure for applying transform precoding on PUSCH | CATT, Nokia |
R1-2406326 | Correction on PT-RS assumption for MsgB PDSCH | CATT |
R1-2406327 | Discussion on the first SPS PDSCH after activation | CATT |
R1-2406328 | Clarification on the first SPS PDSCH after activation | CATT |
R1-2406329 | Clarification on the first CG PUSCH after activation | CATT |
R1-2406330 | Clarification on the cyclic shift hopping for PUCCH transmission | CATT |
R1-2406331 | Discussion on higher layer parameters for DCI format 2_3 | CATT |
R1-2406332 | Draft CR on transition time of BWP change triggered by DCI format 1_1/0_1 scheduling multi-PXSCHs for Rel-17 | CATT |
R1-2406333 | Draft CR on transition time of BWP change triggered by DCI format 1_1/0_1 scheduling multi-PXSCHs for Rel-18 | CATT |
R1-2406387 | Discussion on the operation order for SPS PDSCH reception | CATT |
R1-2406388 | Clarification on the operation order for SPS PDSCH reception | CATT |
R1-2406400 | Discussion on Rel-17 RedCap UE behavior in initial DL BWP | ZTE Corporation, Sanechips |
R1-2406401 | Draft Rel-17 RedCap UE bahavior correction on initial DL BWP | ZTE Corporation, Sanechips, CATT, Ericsson |
R1-2406402 | Correction on PEI for UE power saving | ZTE Corporation, Sanechips |
R1-2406462 | Discussion on SRS Tx power and power headroom reporting | ZTE Corporation, Sanechips |
R1-2406545 | Draft CR on CapabilityIndex Report in TS38.214 | NEC |
R1-2406546 | Draft CR on CapabilityIndex Report in TS38.214 (mirror on Rel-18) | NEC |
R1-2406553 | Draft CR on mapping of beta_offset indicator values to offset indexes | NEC |
R1-2406618 | Discussion on SRS transmission occasion | Samsung |
R1-2406761 | Clarification on SSSG timer reset time instant for R17 UE power saving | MediaTek Inc. |
R1-2406794 | Multiplexing of UCI on Configured Grant PUSCH | Nokia |
R1-2406795 | Continuation of the RAN1#117 RedCap open issues discussion | Nokia |
R1-2406821 | On SRS open loop power control with overlapping SRS resources | Apple |
R1-2406822 | Clarify ambiguities with CG-PUSCH retransmission | Apple |
R1-2406823 | Remaining issues on uplink Tx switching timeline | Apple |
R1-2407009 | Clarification on PTRS with 2 CWs PDSCH and PUSCH retransmission | Qualcomm Incorporated |
R1-2407093 | Discussion on QCL assumption for periodic CSI-RS in unified TCI framework | Nokia |
R1-2407094 | Draft CR on QCL assumption for periodic CSI-RS in unified TCI framework | Nokia |
R1-2407097 | Draft CR for 38.214 on enhanced type II CSI reports | Ericsson |
R1-2407098 | Discussion on corrections to enhanced Type II CSI reports | Ericsson |
R1-2407117 | Correction on receiving Msg4 and a CORESET associated with CSS set | |
R1-2407148 | Draft CR for 38.213 on PUCCH transmission power formula | Ericsson |
R1-2407149 | Draft CR for 38.213 on PUCCH transmission power formula (Rel-18 mirror) | Ericsson |
R1-2407151 | Draft CR for 38.214 on simultaneous DL reception | Ericsson, Google Inc |
R1-2407152 | Draft CR for 38.214 on simultaneous DL reception (Rel-17 mirror) | Ericsson, Google Inc |
R1-2407153 | Draft CR for 38.214 on simultaneous DL reception (Rel-18 mirror) | Ericsson, Google Inc |
R1-2407176 | Draft CR on Multi-Resource SRS Port Power Scaling | Ericsson, Nokia |
R1-2407177 | SRS Tx Occasion and Power Scaling | Ericsson, Nokia |
R1-2407210 | Summary of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2407261 | Moderator summary #1 of clarification on PTRS with 2 CWs PDSCH and PUSCH retransmission | Moderator (Qualcomm) |
R1-2407264 | FLS#1 on R17 MBS broadcast PDSCH scrambling | Moderator (Huawei) |
R1-2407265 | Draft CR on MBS broadcast PDSCH configuration | Moderator (Huawei), ZTE |
R1-2407298 | Moderator summary 1 of SSSG timer reset instant for R17 UE power saving | Moderator (MediaTek Inc.) |
R1-2407299 | Moderator summary 2 of SSSG timer reset instant for R17 UE power saving | Moderator (MediaTek Inc.) |
R1-2407351 | Moderator summary 1 of PEI for Rel-17 UE power saving | Moderator (ZTE Corp.) |
R1-2407352 | Summary#1 of discussion on RedCap UE behavior on initial DL BWP and NCD-SSB | Moderator (ZTE) |
R1-2407357 | Moderator Summary for strongest coefficient indication for Rel-16 eType II reporting | Moderator (Ericsson) |
R1-2407360 | Summary on CapabilityIndex Report in TS38.214 | Moderator (NEC) |
R1-2407362 | Summary on RRC parameter correction for SRS power control | Moderator (Google) |
R1-2407366 | Summary #1 of UE procedure for applying transform precoding on PUSCH | Moderator (CATT) |
R1-2407368 | Summary #1 of definition transition time for BWP change triggered by DCI format 1_1/0_1 scheduling multi-PXSCHs | Moderator (CATT) |
R1-2407372 | Moderator summary on receiving Msg4 and a common CORESET | Moderator (Google) |
R1-2407373 | Moderator summary on QCL assumption for pCSI-RS in uTCI | Moderator (Nokia) |
R1-2407381 | Draft CR on PDSCH reception for MBS | Moderator (ZTE) |
R1-2407411 | Summary on Msg3 retransmission timing in NTN | Moderator (ZTE) |
R1-2407414 | Summary#2 of discussion on RedCap UE behavior on initial DL BWP and NCD-SSB | Moderator (ZTE) |
R1-2407415 | CR on RRC parameter correction for SRS power control | Moderator (Google), Google, ZTE, Samsung |
R1-2407416 | CR on RRC parameter correction for SRS power control | Moderator (Google), Google, ZTE, Samsung |
R1-2407418 | CR on CapabilityIndex Report in TS38.214 | NEC, Huawei, HiSilicon, Samsung, Ericsson |
R1-2407419 | CR on CapabilityIndex Report in TS38.214 (mirror on Rel-18) | NEC, Huawei, HiSilicon, Samsung, Ericsson |
R1-2407421 | Moderator summary #2 of clarification on PTRS with 2 CWs PDSCH and PUSCH retransmission | Moderator (Qualcomm) |
R1-2407422 | Summary of mapping of beta_offset indicator values to offset indexes in TS 38.213 | Moderator (NEC) |
R1-2407423 | Draft reply LS on power control parameters for unified TCI state framework | Ericsson |
R1-2407424 | LS response on power control parameters for unified TCI state framework | RAN1, Ericsson |
R1-2407425 | Moderator summary 2 of PEI for R17 UE power saving | Moderator (ZTE Corporation) |
R1-2407429 | Summary of the first CG PUSCH after activation | Moderator (CATT) |
R1-2407430 | Summary of the first SPS PDSCH after activation | Moderator (CATT) |
R1-2407431 | Summary of PUCCH cyclic shift hopping | Moderator (CATT) |
R1-2407432 | Summary on higher layer parameters for DCI format 2_3 | Moderator (CATT) |
R1-2407436 | Draft LS on separate Initial DL BWP for Rel-17 RedCap | ZTE |
R1-2407439 | CR on transition time of BWP change triggered by DCI format 1_1/0_1 scheduling multi-PDSCHs/multi-PUSCHs | Moderator (CATT), Ericsson, Samsung |
R1-2407440 | CR on transition time of BWP change triggered by DCI format 1_1/0_1 scheduling multi-PDSCHs/multi-PUSCHs | Moderator (CATT), Ericsson, Samsung |
R1-2407441 | Moderator summary #1 on ambiguities with retransmission of a CG-PUSCH | Moderator (Apple Inc.) |
R1-2407442 | Moderator summary #1 on remaining issues for uplink Tx switching | Moderator (Apple Inc.) |
R1-2407454 | Draft CR on PDSCH reception for MBS | Moderator (ZTE) |
R1-2407471 | Session notes for 7 (Pre-Rel-18 NR maintenance-Adhoc#1) | Ad-Hoc Chair (CMCC) |
R1-2407483 | Summary #2 of UE procedure for applying transform precoding on PUSCH | Moderator (CATT) |
R1-2407484 | Draft LS on higher layer parameters for DCI format 2_3 | CATT |
R1-2407496 | Draft CR on Remaining issues for uplink Tx switching | Moderator (Apple), Ericsson |
R1-2407497 | Draft CR on Remaining issues for uplink Tx switching | Moderator (Apple), Ericsson |
R1-2407500 | Summary #2 of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2407514 | Summary#2 of mapping of beta_offset indicator values to offset indexes in TS 38.213 | Moderator (NEC) |
R1-2407518 | CR on Remaining issues for uplink Tx switching | Moderator (Apple), Ericsson, Nokia, Samsung |
R1-2407519 | CR on Remaining issues for uplink Tx switching | Moderator (Apple), Ericsson, Nokia, Samsung |
R1-2407522 | Summary #2 on Msg3 retransmission timing in NTN | Moderator (ZTE) |
R1-2407523 | Correction on timing of Msg3 retransmission in NTN | Moderator (ZTE), Huawei, HiSilicon, Ericsson, vivo, Samsung, CATT |
R1-2407524 | Correction on timing of Msg3 retransmission in NTN | Moderator (ZTE), Huawei, HiSilicon, Ericsson, vivo, Samsung, CATT |
R1-2407525 | Correction on timing of Msg3 retransmission in NTN | Moderator (ZTE), Huawei, HiSilicon, Ericsson, vivo, Samsung, CATT |
R1-2407526 | Correction on timing of Msg3 retransmission in NTN | Moderator (ZTE), Huawei, HiSilicon, Ericsson, vivo, Samsung, CATT |
R1-2407534 | LS on higher layer parameters for DCI format 2_3 | RAN1, CATT |
R1-2407535 | CR on PDSCH reception for MBS | Moderator (ZTE), Huawei, Samsung, Qualcomm, CATT, Sanechips |
R1-2407536 | CR on PDSCH reception for MBS | Moderator (ZTE), Huawei, Samsung, Qualcomm, CATT, Sanechips |
R1-2407537 | Summary#3 of discussion on RedCap UE behavior on initial DL BWP and NCD-SSB | Moderator (ZTE) |
R1-2407547 | Final summary of NR Pre-Rel18 maintenance discussion for SRS power scaling and transmission occasion | Moderator (Ericsson) |
R1-2407550 | Summary#2 on higher layer parameters for DCI format 2_3 | Moderator (CATT) |
R1-2407551 | Summary #2 of definition transition time for BWP change triggered by DCI format 1_1/0_1 scheduling multi-PXSCHs | Moderator (CATT) |
R1-2407553 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
R1-2407556 | Rel-17 RedCap UE behavior correction on initial DL BWP | ZTE Corporation, Sanechips, CATT, Ericsson |
R1-2407557 | Rel-17 RedCap UE behavior correction on initial DL BWP | ZTE Corporation, Sanechips, CATT, Ericsson |
R1-2407562 | Correction on Multi-Resource SRS Port Power Scaling | Moderator (Ericsson), Nokia, Google, Samsung |
R1-2407569 | Alignment of parameter names | Ericsson |
R1-2407570 | Alignment of parameter names | Ericsson |
R1-2407572 | Rel-17 editorial corrections for TS 38.213 | Samsung |
R1-2407573 | Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) | Samsung |
R1-2407576 | Rel-17 editorial corrections for TS 38.214 | Nokia |
R1-2407577 | Rel-17 editorial corrections for TS 38.214 mirrored to Rel-18 | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2407566 | Maintenance of NR Sidelink operation on shared spectrum | Ericsson |
R1-2407567 | Rel-18 Editorial Corrections for TS 38.202 | Qualcomm |
R1-2407568 | Alignment of parameter names | Ericsson |
R1-2407571 | Rel-18 editorial corrections for TS 38.212 | Huawei |
R1-2407574 | Rel-18 editorial corrections for TS 38.213 | Samsung |
R1-2407575 | Rel-18 editorial corrections for TS 38.214 | Nokia |
TDoc | Title | Source |
---|---|---|
R1-2405844 | Correction on PSFCH power control | Huawei, HiSilicon |
R1-2405845 | Discussions on remaining issues of R18 NR sidelink from RAN1#117 | Huawei, HiSilicon |
R1-2405846 | Maintenance of Rel-18 Multicarrier Enhancements | Huawei, HiSilicon |
R1-2405860 | Correction on STxMP schemes in 38.212 | Huawei, HiSilicon |
R1-2405861 | Correction on STxMP schemes in 38.213 | Huawei, HiSilicon |
R1-2405862 | Correction on STxMP schemes in 38.214 | Huawei, HiSilicon |
R1-2405864 | Correction on PSSCH transmission decode behaviour in TS 38.214 | Huawei, HiSilicon |
R1-2405883 | FL Summary on Maintenance of 8TX | Moderator (InterDigital, Inc.) |
R1-2405898 | Draft CR on codebookSubset configuration for fullpowerMode2 with 8 antenna ports | Spreadtrum Communications |
R1-2405930 | Draft CR on miscellaneous corrections of DCI format 0_3 in 38.214 | Spreadtrum Communications |
R1-2405931 | Draft CR on HARQ-ACK codebook generation when BWP switching | Spreadtrum Communications |
R1-2405948 | Discussion on SSB RO mapping for two TA | |
R1-2405949 | Draft CR on SSB RO mapping for two TA | |
R1-2405974 | Draft CR on intra-slot TDM-ed unicast PDSCH and multicast PDSCH in RRC_INACTIVE mode | CMCC |
R1-2406019 | Corrections to TS 38.214 on SRS for positioning with frequency hopping | Intel Corporation |
R1-2406033 | Draft CR on beam collision between PDSCH with offset less than a threshold and PDCCH in S-DCI based MTRP | ZTE Corporation, Sanechips |
R1-2406034 | Draft CR on beam collision between PDSCH with offset less than a threshold and PDCCH in M-DCI based MTRP | ZTE Corporation, Sanechips |
R1-2406035 | Draft CR on implicit BFD-RS determination for S-DCI based MTRP | ZTE Corporation, Sanechips |
R1-2406036 | Discussion on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE | ZTE Corporation, Sanechips |
R1-2406037 | Draft CR on consistency between SSB index and TCI state in LTM Cell Switch Command MAC CE | ZTE Corporation, Sanechips |
R1-2406038 | Discussion on applying TCI state indicated in LTM Cell Switch Command MAC CE to a list of CCs | ZTE Corporation, Sanechips |
R1-2406039 | Discussion on precoding determination of STxMP SDM/SFN scheme in TS38.211 | ZTE Corporation, Sanechips |
R1-2406040 | Draft CR on precoding determination of STxMP SDM/SFN scheme in TS38.211 | ZTE Corporation, Sanechips |
R1-2406041 | Discussion on SRS transmission for NCB PUSCH in STxMP SDM/SFN scheme in TS 38.214 | ZTE Corporation, Sanechips |
R1-2406042 | Draft CR on SRS transmission for NCB PUSCH in STxMP SDM/SFN scheme in TS 38.214 | ZTE Corporation, Sanechips |
R1-2406074 | Draft CR on HARQ-ACK skipping for Rel-18 multi-cell scheduling | Lenovo |
R1-2406114 | Draft CR on PDSCH scrambling for MBS in RRC_INACTIVE | ZTE Corporation, Sanechips |
R1-2406115 | Draft CR on DCI format for MBS reception in RRC_INACTIVE | ZTE Corporation, Sanechips |
R1-2406116 | Draft CR on PDSCH reception for MBS in RRC_INACTIVE | ZTE Corporation, Sanechips |
R1-2406117 | Draft CR on indicated unified TCI state for multi-cell scheduling | ZTE Corporation, Sanechips |
R1-2406118 | Draft CR on application of indicated unified TCI state by DCI format 1_3 | ZTE Corporation, Sanechips |
R1-2406119 | Draft CR on search space of DCI format 0_3 and DCI format 1_3 | ZTE Corporation, Sanechips |
R1-2406120 | Draft CR on HARQ-ACK generation in case of DL BWP switching | ZTE Corporation, Sanechips |
R1-2406121 | Discussion on HARQ-ACK generation in case of DL BWP switching | ZTE Corporation, Sanechips |
R1-2406151 | Clarification on COT sharing flag in 38.212 | vivo |
R1-2406152 | Clarification on channel occupancy sharing information in 37.213 | vivo |
R1-2406153 | Draft CR on HARQ-ACK codebook for DL BWP switching | vivo |
R1-2406154 | Draft CR on MBS and multi-carrier scheduling | vivo |
R1-2406155 | Draft CR on SRS resource set indication | vivo |
R1-2406156 | Draft CR on PHR report for mDCI-based sTxMP | vivo |
R1-2406157 | Discussion on PHR report for mDCI-based sTxMP | vivo |
R1-2406158 | Correction on RRC parameters for unified TCI extension for mTRP in TS38.213 | vivo |
R1-2406159 | Correction on RRC parameters for unified TCI extension for mTRP in TS38.214 | vivo |
R1-2406160 | Draft CR on time offset for PRACH repetition in CFRA | vivo |
R1-2406161 | Discussion on FR2-NTN inclusion to specifications | vivo |
R1-2406162 | Draft CR on FR2-NTN inclusion to TS38.213 | vivo |
R1-2406163 | Draft CR on alignment on the indication of number of HARQ processes for PUSCH | vivo |
R1-2406164 | Draft CR on alignment on parameters used for PUCCH repetition for msg4 HARQ-ACK | vivo |
R1-2406165 | Draft CR on bandwidth part considering SRS frequency hopping for positioning | vivo |
R1-2406166 | Draft CR on DCI format 3_2 for SL PRS scheduling | vivo |
R1-2406167 | Draft CR on DL PRS measurement in RRC_IDLE mode | vivo |
R1-2406168 | Draft CR on PRS for carrier phase positioning | vivo |
R1-2406169 | Draft CR on SL PRS power control based on SL pathloss | vivo |
R1-2406170 | Draft CR on higher-layer parameter for SRS transmission with frequency hopping in TS 38.213 | vivo |
R1-2406171 | Draft CR on higher-layer parameter for SRS frequency hopping in TS 38.211 | vivo |
R1-2406213 | Draft CR for correction on interlace RB-based transmission in partial sensing | OPPO |
R1-2406214 | Draft CR for indication of remaining channel occupancy duration | OPPO, Qualcomm |
R1-2406215 | Draft CR for correction on CAPC value for PSFCH and S-SSB | OPPO |
R1-2406216 | Draft CR for correction on PSFCH power control | OPPO, ZTE, Sanechips |
R1-2406217 | Draft CR for correction on PSSCH decoding behaviour | OPPO |
R1-2406334 | Draft CR on SL PRS mapping to the physical resources | CATT, CICTCI |
R1-2406335 | Discussion on the higher layer parameters in a dedicated SL PRS resource pool | CATT, CICTCI |
R1-2406336 | Draft CR on the contention window adjustment procedures for SL-U | CATT, CICTCI, OPPO |
R1-2406337 | Draft CR on the determination of sidelink symbol for SL-U | CATT, CICTCI |
R1-2406338 | Draft CR on rate matching pattern for multicast reception in RRC_INACTIVE state | CATT, CBN, China Broadnet |
R1-2406339 | Draft CR on Type-2 HARQ-ACK codebook determination for PDSCHs scheduled by DCI format 1_3 | CATT |
R1-2406340 | Draft CR on HARQ-ACK codebook retransmission triggered by DCI 1_3 | CATT |
R1-2406341 | Draft CR on maxNrofCodeWordsScheduledByDCI for second Type-2 HARQ-ACK codebook | CATT |
R1-2406342 | Draft CR on HARQ-ACK information skipping due to BWP change for second Type-2 HARQ-ACK codebook | CATT |
R1-2406343 | Correction on higher layer parameters for SL PRS resource selection in a dedicated SL PRS resource pool | CATT, CICTCI |
R1-2406344 | Correction on UE procedure for transmitting the physical sidelink shared channel | CATT, CICTCI |
R1-2406345 | Correction on Type-1 PHR for UL simultaneous multi-panel transmission | CATT |
R1-2406346 | Correction on precoding matrices for 8Tx UL transmission | CATT |
R1-2406347 | Correction on channel measurements derivation for computing CSI | CATT |
R1-2406348 | Draft CR on transition time of BWP change triggered by DCI format 1_3/0_3 | CATT |
R1-2406349 | Correction on RRC parameters for Msg4 HARQ-ACK repetition in TS38.213 | CATT |
R1-2406350 | Discussion on channel measurements derivation for computing CSI | CATT |
R1-2406351 | Correction on SRS frequency hopping for positioning | CATT |
R1-2406460 | Discussion on the maximum number of PL RS maintained simultaneously for candidate cells | ZTE Corporation, Sanechips |
R1-2406461 | Draft CR on the maximum number of PL RS maintained simultaneously for candidate cells | ZTE Corporation, Sanechips |
R1-2406520 | Correction on UE assumptions for CQI/PMI/RI calculation for type 1 spatial domain adaptation | Fujitsu |
R1-2406535 | Remaining issues on PSFCH power control | NEC |
R1-2406547 | Draft CR on indicated TCI state in TS38.214 | NEC |
R1-2406550 | Draft CR on DMRS port index in TS38.211 | NEC |
R1-2406561 | Discussion on missing RRC parameter for LTM early UL sync | NEC |
R1-2406564 | Draft CR on CBSR configuration for CJT in TS38.214 | NEC |
R1-2406565 | Discussion on CBSR configuration for CJT | NEC |
R1-2406601 | Discussion on EPRE of CSI-RS and PDSCH for NES | LG Electronics |
R1-2406619 | Draft CR on HARQ-ACK skipping for DL/UL BWP switching in multi-cell scheduling | Samsung |
R1-2406620 | Draft CR on Search Space for DCI formats 0_3/1_3 | Samsung |
R1-2406621 | Moderator summary on maintenance issues for Rel-18 CSI enhancements | Moderator (Samsung) |
R1-2406622 | Discussion on mDCI based STx2P out-of-order operation | Samsung |
R1-2406623 | Draft CR on mDCI based STx2P out-of-order operation | Samsung |
R1-2406624 | Discussion on twoPHRmode for single-DCI based STx2P | Samsung |
R1-2406625 | Draft CR on twoPHRmode for single-DCI based STx2P | Samsung |
R1-2406626 | Draft CR on applying apply-IndicatedTCIState to PDCCH repetition | Samsung |
R1-2406627 | Discussions on cell-specific BFR under eUTCI | Samsung |
R1-2406628 | Draft CR on determining a BFD RS set with two indicated TCI states | Samsung |
R1-2406629 | Draft CR on cell-specific beam resetting for MDCI MTRP under eUTCI | Samsung |
R1-2406630 | Remaining issues on network energy saving | Samsung |
R1-2406631 | Correction on power assumption for type 1 spatial domain adaptation | Samsung |
R1-2406632 | Correction on CSI related operation based on NES capability | Samsung |
R1-2406633 | Correction on CSI processing criteria and CSI computation time for low layer triggered mobility (LTM) CSI report. | Samsung |
R1-2406634 | Draft CR for Correcting S-SSB Transmission in Non-Anchor RB Set | Samsung |
R1-2406676 | Correction on IUC in co-existence case in TS 38.214 | ZTE, Sanechips |
R1-2406677 | Correction on PSFCH resource mapping for contiguous RB resource pool in TS 38.213 | ZTE, Sanechips |
R1-2406678 | Correction on PSSCH transmission decode behaviour in TS 38.214 | ZTE, Sanechips |
R1-2406679 | Supplementary higher layer parameter for section 8 in TS 38.214 | ZTE, Sanechips |
R1-2406680 | Correction on contiguous RB based resource allocation in TS 38.214 | ZTE, Sanechips |
R1-2406681 | Correction on resource allocation in frequency domain in TS 38.214 | ZTE, Sanechips |
R1-2406790 | Draft CR on UE behaviour to maintain pathloss for LTM candidate cells | Nokia |
R1-2406796 | Draft CR on correction of UCI-onPUSCH for PUSCH scheduled by DCI format 0_3 | Nokia |
R1-2406804 | Draft CR for 38.214 on editorial corrections | Ericsson |
R1-2406805 | Draft CR for 38.214 correcting RRC parameters | Ericsson |
R1-2406806 | Draft CR for 38.213 correcting RRC and UE capability parameters | Ericsson |
R1-2406810 | Autonomous and Aperiodic triggering for GNSS enhancements in IoT-NTN | Ericsson |
R1-2406824 | Draft CR on DCI format for scheduling of MBS | Apple |
R1-2406908 | Correction on SSB to CG PUSCH mapping for NTN RACH-less handover | ZTE Corporation, Sanechips |
R1-2406909 | Remaining issues for multi-carrier scheduling with single DCI | NTT DOCOMO, INC. |
R1-2406910 | Draft CR on PHR reporting for STxMP when twoPHRMode is not provided | NTT DOCOMO, INC. |
R1-2406911 | Draft CR on virtual PHR reporting in Rel-18 unified TCI framework | NTT DOCOMO, INC. |
R1-2406912 | Draft CR on RRC parameter alignment for STxMP | NTT DOCOMO, INC. |
R1-2406913 | Draft CR on PCMAX in PHR reporting for STxMP | NTT DOCOMO, INC. |
R1-2406914 | Draft CR on threshold for A-CSI-RS for Rel-18 TCI framework | NTT DOCOMO, INC. |
R1-2406915 | Draft CR on CAPC value for PSFCH+S-SSB for SL-U | NTT DOCOMO, INC. |
R1-2406916 | Draft CR on multi-channel access vs PSFCH prioritization for SL-U | NTT DOCOMO, INC. |
R1-2406917 | Draft CR on sensing with two starting symbols | NTT DOCOMO, INC. |
R1-2406918 | Maintenance of resource selection in MAC layer for SL-U | NTT DOCOMO, INC. |
R1-2406953 | Draft CR for collision handling of positioning SRS with Tx hopping in TDD system | ZTE Corporation, Sanechips |
R1-2406954 | Draft CR for staircase pattern for SRS Tx hopping in TS 38.211 | ZTE Corporation, Sanechips |
R1-2406955 | Correction on SL PRS power control in TS 38.213 | ZTE Corporation, Sanechips |
R1-2406956 | Corrections on positioning in TS 38.214 | ZTE Corporation, Sanechips |
R1-2406957 | Draft CR for DL PRS measurement in TS 38.214 | ZTE Corporation, Sanechips |
R1-2406958 | Draft CR for measurement window in TS 38.214 | ZTE Corporation, Sanechips |
R1-2406983 | Discussion on CSI-RS EPRE for type 1 spatial domain adaptation | Huawei, HiSilicon |
R1-2406984 | Correction on PHR calculation for STxMP in 38.213 | Huawei, HiSilicon |
R1-2406985 | Corrections to power control parameters for the UL transmission after LTM cell swtich in TS38.213 | Huawei, HiSilicon |
R1-2406986 | Correction on the application time of cell DRX for NR NTN | Huawei, HiSilicon |
R1-2406987 | Determination of PSFCH resources for a PSSCH | Huawei, HiSilicon |
R1-2406988 | Correction on CPE starrting position for PSFCH | Huawei, HiSilicon |
R1-2406989 | Correction on SCell dormancy indication case 2 in case of BWP switching | Huawei, HiSilicon |
R1-2406990 | Correction on type 2 HARQ-ACK codebook skipping in case of BWP switching | Huawei, HiSilicon |
R1-2406991 | Correction on PDCCH overbooking in TS 38.213 | Huawei, HiSilicon |
R1-2406992 | Corrections on Type2-HARQ-ACK codebook for DCI format 1_3 in TS 38.213 | Huawei, HiSilicon |
R1-2406993 | Corrections on Rel-18 UL Tx switching with two configured bands | Huawei, HiSilicon |
R1-2406994 | Corrections to the Pathloss RS in LTM TCI state in TS38.213 | Huawei, HiSilicon |
R1-2406995 | Corrections to the UL/SUL indication for CFRA in TS38.213 | Huawei, HiSilicon |
R1-2406996 | Corrections to the first UL transmission after LTM cell switch in TS38.213 | Huawei, Ericsson, Nokia, ZTE Corporation, Sanechips, HiSilicon |
R1-2406997 | Correction on COT sharing information processing delay | Huawei, HiSilicon |
R1-2406999 | Corrections on Rel-18 MBS multicast scrambling to TS 38.211 | Huawei, HiSilicon |
R1-2407000 | Correction on the description of TCI activation in 38.214 | Huawei, HiSilicon |
R1-2407001 | Correction on UE capability and DCI field for unified TCI in 38.214 | Huawei, HiSilicon |
R1-2407010 | Maintenance of Rel-18 Mobility Enhancement | Qualcomm Incorporated |
R1-2407011 | Draft CR on the Rel-18 TDD configuration in the LTM candidate cell | Qualcomm Incorporated |
R1-2407012 | Draft CR on the exclusion of the sync raster points of 3MHz for Table 13-1 | Qualcomm Incorporated |
R1-2407013 | Correction on Type-2 HARQ-ACK codebook for multi-cell PDSCH scheduling | Qualcomm Incorporated |
R1-2407014 | Maintenance on NR MIMO Evolution for Downlink and Uplink | Qualcomm Incorporated |
R1-2407015 | Discussion of cell DRX application time for NR NTN | Qualcomm Incorporated |
R1-2407016 | Draft CR on the application time of cell DRX for NR NTN | Qualcomm Incorporated |
R1-2407054 | Discussion on power offset for spatial domain adaptation for Rel-18 NES | Ericsson |
R1-2407099 | Correction on SRS frequency hopping for positioning | Nokia |
R1-2407101 | Draft CR for 38.214 on enhanced type II CB for CJT and predicted PMI | Ericsson |
R1-2407102 | Discussion on corrections to enhanced type II CB for CJT and predicted PMI | Ericsson |
R1-2407108 | Correction on PDCCH Search Space for Rel-18 Multi-Carrier Enhancements | Langbo |
R1-2407110 | Correction on Minimum Scheduling Offset for Rel-18 Multi-Carrier Enhancements | Langbo |
R1-2407125 | Correction on LTM CSI report | ASUSTeK |
R1-2407147 | Draft CR for 38.213 on deactivation of candidate TCI states | Ericsson |
R1-2407150 | Draft CR for 38.214 on Unified TCI States Activation/Deactivation MAC CE for sTRP operation | Ericsson |
R1-2407154 | Draft CR for 38.214 on simultaneous UL transmisson | Ericsson, Google Inc |
R1-2407163 | Corrections on Rel-18 MBS RNTI to TS 38.202 | Huawei, HiSilicon |
R1-2407164 | Correction on table caption for DCI format 0_3/1_3 in TS 38.212 | Huawei, HiSilicon |
R1-2407165 | Corrections on Rel-18 MBS RNTI to TS 38.211 | Huawei, HiSilicon |
R1-2407169 | Draft CR for correction to SRS for positioning with tx hopping in 38.211 | Ericsson |
R1-2407170 | Draft CR for correction to SRS for positioning with tx hopping in 38.214 | Ericsson |
R1-2407171 | Draft CR for correction to sidelink Positioning in 38.212 | Ericsson |
R1-2407172 | Draft CR for correction to SRS for positioning with tx hopping in 38.213 | Ericsson |
R1-2407173 | Draft CR for correction to sidelink Positioning in 38.214 | Ericsson |
R1-2407174 | Draft CR for the support of multiple Rx ARP measurements on SL-PRS | Ericsson |
R1-2407178 | Draft CR on PTRS-DMRS Association for 8 Tx UL MIMO | Ericsson |
R1-2407179 | Draft CR on CBGTI Field Size Determination for 8 Tx UL MIMO | Ericsson |
R1-2407180 | Draft CR on Multi-TRP PUSCH Repetition | Ericsson |
R1-2407181 | Draft CR on PT-RS Power for Non-Codebook Based 8 Tx PUSCH | Ericsson |
R1-2407187 | Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension (Round 0) | Moderator (MediaTek Inc.) |
R1-2407188 | Summary on Rel-18 STxMP | Moderator (OPPO) |
R1-2407192 | FL summary#1 on Rel-18 MIMO DMRS | Moderator (NTT DOCOMO) |
R1-2407193 | FL summary #1 for AI 8.1: SL-U channel access and RA | Moderator (OPPO) |
R1-2407194 | FL summary #2 for AI 8.1: SL-U channel access and RA | Moderator (OPPO) |
R1-2407195 | FL summary for AI 8.1: SL-U channel access and RA (EOM) | Moderator (OPPO) |
R1-2407196 | Summary#1 of discussions on time offset for PRACH repetition in CFRA | Moderator (vivo) |
R1-2407197 | Summary of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2407205 | FL Summary for maintenance on NR carrier phase positioning | Moderator (CATT) |
R1-2407212 | Summary of discussion on FR2-NTN inclusion to specifications | Moderator (vivo) |
R1-2407223 | Summary #1 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2407224 | Summary #2 on Measurements and reporting for SL positioning | Moderator (vivo) |
R1-2407225 | Feature lead summary#1 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2407226 | Feature lead summary#2 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2407227 | Feature lead summary#3 on multi-cell scheduling with a single DCI | Moderator (Lenovo) |
R1-2407231 | FL Summary #1 for AI 8.1: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2407232 | FL Summary #2 for AI 8.1: Co-channel coexistence for LTE sidelink and NR sidelink | Moderator (LG Electronics) |
R1-2407233 | Moderator Summary on GNSS enhancements for IoT-NTN | Moderator (Ericsson) |
R1-2407234 | Feature Lead summary #1 for Maintenance of Positioning for RedCap Ues | Moderator (Ericsson) |
R1-2407235 | (Draft) CR for correction on bandwidth part for SRS frequency hopping for positioning | Moderator (Ericsson) |
R1-2407236 | (Draft) CR for correction on staircase pattern for SRS frequency hopping for positioning | Moderator (Ericsson) |
R1-2407237 | (Draft) CR for correction on sequence generation for SRS frequency hopping for positioning | Moderator (Ericsson) |
R1-2407238 | (Draft) CR for correction on starting position for SRS frequency hopping for positioning | Moderator (Ericsson) |
R1-2407239 | (Draft) CR for correction on slot offset configuration for SRS with tx hopping | Moderator (Ericsson) |
R1-2407240 | (Draft) CR for correction on definition of “Cycle” for SRS with tx hopping | Moderator (Ericsson) |
R1-2407241 | (Draft) CR for correction on collision handling of positioning SRS with Tx hopping | Moderator (Ericsson) |
R1-2407242 | FL summary#1 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2407243 | FL summary#2 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2407244 | FL summary#3 for AI 8.1 SL-U physical channel design framework | Moderator (Huawei) |
R1-2407245 | Correction on PSFCH Power Control | Moderator (Huawei), Huawei, Hisilicon, NEC |
R1-2407246 | Correction on PSFCH Power Control | Moderator (Huawei), OPPO, ZTE, Sanechips |
R1-2407247 | RAN1 agreements for R18 NR SL-U PHY channel design until RAN1#118 | Rapporteur (Huawei) |
R1-2407256 | FL summary #1 on SL positioning reference signal and Alignment CRs for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407257 | Alignment CR to TS 38.211 Corrections for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407258 | Alignment CR to TS 38.212 Corrections for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407259 | Alignment CR to TS 38.213 Corrections for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407260 | Alignment CR to TS 38.214 Corrections for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407263 | Moderator Summary #1 on Two TAs for multi-DCI | Moderator (Ericsson) |
R1-2407286 | Summary of discussion on the exclusion of the sync raster points of 3MHz for Table 13-1 | Moderator (Qualcomm) |
R1-2407294 | Summary of alignment on the indication of number of HARQ processes | Moderator (vivo) |
R1-2407295 | Summary#1 for CSI-RS EPRE issue for R18 NES | Moderator (Huawei) |
R1-2407300 | Moderator Summary #0 on resource allocation for SL PRS | Moderator (Qualcomm) |
R1-2407309 | CR on SRS transmission for NCB PUSCH in STxMP SDM/SFN scheme | Moderator (OPPO), ZTE Corporation, Sanechips, Samsung |
R1-2407310 | CR on mDCI based STx2P out-of-order operation | Moderator (OPPO), Samsung, Qualcomm |
R1-2407311 | CR on Multi-TRP PUSCH Repetition | Moderator (OPPO), Ericsson, Samsung |
R1-2407314 | Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension (Round 1) | Moderator (MediaTek Inc.) |
R1-2407315 | Feature lead summary on RACH during uplink transmission extension | Moderator (Qualcomm) |
R1-2407316 | FL summary 1 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2407317 | FL summary 2 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2407328 | Summary#2 of discussions on time offset for PRACH repetition in CFRA | Moderator (vivo) |
R1-2407329 | Correction on PSFCH Power Control | Moderator (Huawei) |
R1-2407334 | Draft final CR on Correction on threshold for A-CSI-RS reception for Rel-18 TCI framework | Moderator (MediaTek Inc.) |
R1-2407335 | Draft final CR on Type1 PHR for reference PUSCH transmission if twoPHRMode is not provided | Moderator (MediaTek Inc.) |
R1-2407336 | Draft final CR on Type1 PHR reporting for M-DCI based STxMP when twoPHRMode is not provided | Moderator (MediaTek Inc.) |
R1-2407337 | Draft final CR on Type1 PHR reporting for S-DCI based STxMP when twoPHRMode is not provided | Moderator (MediaTek Inc.) |
R1-2407348 | FL summary on R18 MBS intra-slot TDM PDSCH reception | Moderator (CMCC) |
R1-2407349 | Summary#2 of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2407350 | Draft CR on MBS multicast PDSCH configuration | Moderator (Huawei), ZTE |
R1-2407358 | CR on Precoding Matrices for 8TX UL MIMO Transmission | Moderator (InterDigital), CATT, Samsung |
R1-2407359 | CR on CBGTI Field Size Determination for 2CW Transmission by 8TX UL MIMO | Moderator (InterDigital), Ericsson, Samsung |
R1-2407361 | CR on CBSR configuration for CJT in TS38.214 | Samsung, NEC, Ericsson, New H3C |
R1-2407367 | Summary of rate matching pattern for multicast reception in RRC_INACTIVE state | Moderator (CATT) |
R1-2407369 | Correction on the determination of sidelink symbol for SL-U | Moderator (Huawei), CATT, CICTCI, Samsung |
R1-2407370 | Correction on PSSCH transmission decoding behaviour | Moderator (Huawei), ZTE, Sanechips, Huawei, HiSilicon, OPPO |
R1-2407371 | Correction on S-SSB transmission on non-anchor RB set | Moderator (Huawei), Samsung, Huawei, HiSilicon |
R1-2407374 | Summary#3 of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2407375 | Summary of discussion on CSI related operation based on NES capability | Moderator (Samsung) |
R1-2407376 | [Draft] LS on a RRC parameter needed for the sequence generation of PSCCH DMRS for a dedicated SL PRS resource pool | Qualcomm |
R1-2407377 | LS on a RRC parameter needed for the sequence generation of PSCCH DMRS for a dedicated SL PRS resource pool | RAN1, Qualcomm |
R1-2407379 | CR on DL PRS measurement in RRC_IDLE mode | Moderator (CATT), vivo, ZTE Corporation, Sanechips |
R1-2407380 | CR for measurement window in TS 38.214 | Moderator (CATT), ZTE Corporation, Sanechips |
R1-2407382 | Draft CR on PDSCH reception for MBS in RRC_INACTIVE | Moderator (ZTE) |
R1-2407391 | Draft CR on PTRS-DMRS Association for 8 Tx UL MIMO | Moderator (NTT DOCOMO), Ericsson, Samsung |
R1-2407392 | Correction on SSB to CG PUSCH mapping for NTN RACH-less handover | Moderator(ZTE), Samsung |
R1-2407393 | Correction on bandwidth part for SRS frequency hopping for positioning | Moderator (Ericsson), vivo |
R1-2407394 | Correction on staircase pattern for SRS frequency hopping for positioning | Moderator (Ericsson), ZTE, SaneChip |
R1-2407395 | (Draft) CR for correction on definition of “Cycle” for SRS with tx hopping | Moderator (Ericsson) |
R1-2407396 | (Draft) CR for correction on collision handling of positioning SRS with Tx hopping | Moderator (Ericsson) |
R1-2407397 | Feature Lead summary #2 for Maintenance of Positioning for RedCap Ues | Moderator (Ericsson) |
R1-2407398 | Summary#2 for CSI-RS EPRE issue for R18 NES | Moderator (Huawei) |
R1-2407400 | (draft) Reply LS on synchronization source change at the transmitting anchor UE in SL positioning | Ericsson |
R1-2407401 | Reply LS on synchronization source change at the transmitting anchor UE in SL positioning | RAN1, Ericsson |
R1-2407402 | Corrections to TS 38.213 on OLPC for SL PRS | Moderator (Intel Corporation), vivo, ZTE Corporation, Sanechips |
R1-2407403 | Alignment CR to TS 38.214 Corrections for Rel-18 Positioning | Moderator (Intel Corporation) |
R1-2407404 | Summary#2 of discussion on FR2-NTN inclusion to specifications | Moderator (vivo) |
R1-2407405 | Draft LS on FR2-NTN inclusion to specifications | vivo |
R1-2407406 | LS on FR2-NTN inclusion to specifications | RAN1, vivo |
R1-2407407 | CR on FR2-NTN inclusion to TS 38.213 | Moderator(vivo), Nokia, Ericsson |
R1-2407410 | Correction on IUC in co-channel coexistence case in TS 38.214 | Moderator (LG Electronics), ZTE Corporation, Sanechips, CATT, CICTCI, vivo, Nokia |
R1-2407412 | CR on SSB-RO mapping for two TA | Moderator (Ericsson), Google, Samsung, Ericsson, New H3C |
R1-2407427 | Feature Lead summary #3 for Maintenance of Positioning for RedCap UEs | Moderator (Ericsson) |
R1-2407428 | (Draft) CR for correction on definition of “Cycle” for SRS with tx hopping | Moderator (Ericsson) |
R1-2407434 | Correction on definition of “Cycle” for SRS with tx hopping | Moderator (Ericsson), CATT, Ericsson, Intel Corporation, Samsung |
R1-2407435 | Summary#4 of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2407443 | FL summary 3 of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2407444 | Final FL summary of Maintenance on Further NR Mobility Enhancements | Moderator (Fujitsu) |
R1-2407446 | [draft] LS on missing RRC parameters for early UL sync PRACH transmission for LTM | Moderator (Fujitsu) |
R1-2407447 | LS on missing RRC parameters for early UL sync PRACH transmission for LTM | RAN1, Fujitsu |
R1-2407448 | Correction on power control parameters for the UL transmission after LTM cell switch | Moderator (Fujitsu), Huawei, HiSilicon, ZTE, Sanechips, Ericsson, Nokia, Lenovo, Apple |
R1-2407449 | Correction on the first UL transmission after LTM cell switch | Moderator (Fujitsu), Huawei, Ericsson, Nokia, ZTE Corporation, Sanechips, HiSilicon, Lenovo, Apple |
R1-2407450 | Correction on the TDD configuration in the LTM candidate cell | Moderator (Fujitsu), Qualcomm, Ericsson, Nokia, Google, ZTE, Huawei, Lenovo, Apple |
R1-2407451 | Correction on determination of restricted type for candidate cell PRACH transmission in LTM | Moderator (Fujitsu), Ericsson, Nokia, ZTE, Huawei, Lenovo, Apple |
R1-2407452 | Correction on CSI processing criteria and CSI computation time for LTM CSI report. | Moderator (Fujitsu), Samsung, ASUSTeK, Ericsson, Nokia, ZTE, Huawei, Lenovo, Apple |
R1-2407453 | Correction on the UL/SUL indication for CFRA | Moderator (Fujitsu), Huawei, HiSilicon, Ericsson, Nokia, ZTE, Lenovo, Apple |
R1-2407457 | CR on PTRS-DMRS Association for 8 Tx UL MIMO | Moderator (NTT DOCOMO), Ericsson, Samsung |
R1-2407458 | Correction on threshold for A-CSI-RS reception for Rel-18 TCI framework | Moderator (MediaTek. Inc), NTT DOCOMO. INC, Samsung, Ericsson, vivo |
R1-2407459 | Type1 PHR for reference PUSCH transmission if twoPHRMode is not provided | Moderator (MediaTek. Inc), NTT DOCOMO. INC, Samsung, Ericsson, vivo |
R1-2407460 | Type1 PHR reporting for M-DCI based STxMP when twoPHRMode is not provided | Moderator (MediaTek. Inc), NTT DOCOMO. INC, Samsung, Ericsson, vivo |
R1-2407461 | Type1 PHR reporting for S-DCI based STxMP when twoPHRMode is not provided | Moderator (MediaTek. Inc), NTT DOCOMO. INC, Samsung, Ericsson, vivo |
R1-2407462 | Draft CR on the application time of cell DRX for NR NTN | Moderator (Huawei) |
R1-2407463 | Summary of discussion on application time of cell DRX for NR NTN | Moderator (Huawei) |
R1-2407464 | Final summary of discussions on time offset for PRACH repetition in CFRA | Moderator (vivo) |
R1-2407465 | CR on time offset for PRACH repetition in CFRA | Moderator (vivo), China Telecom, Samsung |
R1-2407472 | Session notes for 8.1 (Maintenance on Rel-18 work items - Positioning Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2407473 | Session notes for 8.1 (Maintenance on Rel-18 work items - Mobility Enhancement) | Ad-Hoc Chair (CMCC) |
R1-2407474 | Session notes for 8.1 (Maintenance on Rel-18 work items – Multi-Carrier) | Ad-Hoc Chair (CMCC) |
R1-2407475 | Session notes for 8.1 (Maintenance on Rel-18 work items - IoT NTN/NR NTN Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2407476 | Session notes for 8.1 (Maintenance on Rel-18 work items - Sidelink Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2407477 | Session notes for 8.1 (Maintenance on Rel-18 work items - MBS Enhancement) | Ad-Hoc Chair (Huawei) |
R1-2407485 | LS on resource selection avoidance in Option 1 of Type 1 LBT blocking (inter-UE case) | RAN1, OPPO |
R1-2407486 | Correction on reference section numbers for PSFCH prioritization in multi-channel access procedures | Moderator (OPPO), NTT DOCOMO, INC. |
R1-2407487 | Correction on interlace RB-based transmission in partial sensing | Moderator (OPPO), Samsung |
R1-2407488 | Correction on CPE starting position for PSFCH | Moderator (OPPO), Huawei, HiSilicon |
R1-2407503 | Summary#5 of discussion on Multi-carrier UL Tx switching scheme | Moderator (NTT DOCOMO, INC.) |
R1-2407504 | Draft Reply LS on UL Tx switching | NTT DOCOMO, INC. |
R1-2407505 | Reply LS on UL Tx switching | RAN1, NTT DOCOMO, INC. |
R1-2407508 | Correction on the TDD configuration in the LTM candidate cell | Moderator (Fujitsu), Qualcomm, Ericsson, Nokia, Google, ZTE, Huawei, Lenovo, Apple |
R1-2407509 | Draft CR on the application time of cell DRX for NR NTN | Moderator (Huawei), HiSilicon, Qualcomm, Nokia, Samsung, Apple, Ericsson, NTT Docomo |
R1-2407510 | Summary#2 of discussion on application time of cell DRX for NR NTN | Moderator (Huawei) |
R1-2407515 | Corrections on Rel-18 UL Tx switching with two configured bands | Moderator (NTT DOCOMO), Huawei, HiSilicon, Apple |
R1-2407527 | Correction on PSFCH Power Control | Moderator (Huawei), Huawei, HiSilicon, NEC, Samsung, OPPO, CATT, CICTCI |
R1-2407528 | Correction on PSFCH resource mapping for contiguous RB resource pool | Moderator (Huawei), ZTE, Sanechips, Huawei, HiSilicon, Samsung |
R1-2407529 | CR on Beam collision between PDSCH with offset less than a threshold and PDCCH in M-DCI based MTRP | Moderator (MediaTek. Inc), ZTE Corporation, Sanechips, Ericsson, Samsung |
R1-2407530 | CR on Beam collision between PDSCH with offset less than a threshold and PDCCH in S-DCI based MTRP | Moderator (MediaTek. Inc), ZTE Corporation, Sanechips, Ericsson, Samsung |
R1-2407531 | CR on unified TCI state actviation for sDCI-based mTRP | Moderator (MediaTek. Inc), Huawei, HiSilicon, Ericsson, Samsung |
R1-2407539 | LS on resource selection avoidance in Option 1 of Type 1 LBT blocking (inter-UE case) | RAN1, OPPO |
R1-2407540 | Correction on SL-U COT sharing flag indication | Moderator (OPPO), vivo, CATT, CICTCI |
R1-2407541 | Correction on applicable CAPC for PSFCH and S-SSB transmissions | Moderator (OPPO), Samsung, NTT DOCOMO, vivo, LG Electronics |
R1-2407542 | Correction on SL-U reference duration | Moderator (OPPO), CATT, CICTCI, Samsung, LG Electronics |
R1-2407545 | Correction on HARQ-ACK skipping for Rel-18 multi-cell scheduling | Moderator (Lenovo), Samsung, Ericsson, Huawei, HiSilicon, ZTE Corporation, Sanechips, Cybercore, CATT, New H3C |
R1-2407564 | CR on the application time of cell DRX for NR NTN | Moderator (Huawei), HiSilicon, Qualcomm, Nokia, Samsung, Apple, Ericsson, NTT Docomo |
TDoc | Title | Source |
---|---|---|
R1-2407385 | Updated RAN1 UE features list for Rel-18 NR after RAN1 #118 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2407386 | Draft LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#118 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2407387 | LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#118 | RAN1, AT&T, NTT DOCOMO |
R1-2407388 | Updated RAN1 UE features list for Rel-18 LTE after RAN1 #118 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2407389 | Draft LS on updated Rel-18 RAN1 UE features lists for LTE after RAN1#118 | Moderators (AT&T, NTT DOCOMO, INC.) |
R1-2407390 | LS on updated Rel-18 RAN1 UE features lists for LTE after RAN1#118 | RAN1, AT&T, NTT DOCOMO |
TDoc | Title | Source |
---|---|---|
R1-2405932 | Discussion on UE feature for topics A | ZTE Corporation, Sanechips |
R1-2406225 | Discussion on UE features for multi-carrier enhancement | OPPO |
R1-2406635 | UE features for other Rel-18 work items (Topics A) | Samsung |
R1-2406797 | UE Features for Other Topics A | Nokia |
R1-2406980 | UE features for other Rel-18 work items (Topics A) | Huawei, HiSilicon |
R1-2407017 | UE features for other Rel-18 work items (Topics A) | Qualcomm Incorporated |
R1-2407161 | Rel-18 UE features topics set A | Ericsson |
R1-2407198 | Summary of discussion on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
R1-2407199 | Session Notes of AI 8.2.1 | Ad-Hoc Chair (NTT DOCOMO, INC.) |
R1-2407417 | Summary#2 of discussion on UE features for MC enhancements | Moderator (NTT DOCOMO, INC.) |
TDoc | Title | Source |
---|---|---|
R1-2405835 | UE features for other Rel-18 work items (Topics B) | Huawei, HiSilicon |
R1-2406020 | UE features for Rel-18 Work Items (Topics B) | Intel Corporation |
R1-2406352 | Remaining issues on UE features for Rel-18 LTM | CATT |
R1-2406636 | UE features for other Rel-18 work items (Topics B) | Samsung |
R1-2406798 | UE Features for Other Topics B (NES, MobEnh, IoT-NTN) | Nokia |
R1-2406825 | Views on UE features for other Rel-18 work items (Topics B) | Apple |
R1-2406919 | Discussion on UE features for other Rel-18 work items (Topics B) | NTT DOCOMO, INC. |
R1-2406961 | UE features for other Rel-18 work items (Topics B) | ZTE Corporation, Sanechips |
R1-2407018 | UE features for other Rel-18 work items (Topics B) | Qualcomm Incorporated |
R1-2407055 | Rel-18 UE features topics set B | Ericsson |
R1-2407501 | Summary of UE features for other Rel-18 work items (Topics B) | Moderator (AT&T) |
R1-2407502 | Session Notes of AI 8.2.2 | Ad-Hoc Chair (AT&T) |
TDoc | Title | Source |
---|---|---|
R1-2407478 | Session notes for 9.1 (AI/ML for NR Air Interface) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2405808 | Discussion on specification support for AI/ML-based beam management | FUTUREWEI |
R1-2405899 | Discussion on AIML for beam management | Spreadtrum Communications |
R1-2405944 | Specification Support for AI/ML for Beam Management | Kyocera |
R1-2405950 | AI/ML based Beam Management | |
R1-2405963 | AI/ML for Beam Management | Tejas Networks Limited |
R1-2405975 | Discussion on specification support for beam management | CMCC |
R1-2406014 | Specification support for AI/ML for beam management | Intel Corporation |
R1-2406054 | Discussion on AI/ML-based beam management | ZTE Corporation, Sanechips |
R1-2406141 | AI/ML for beam management | Ericsson |
R1-2406172 | Specification support for beam management | vivo |
R1-2406254 | On specification for AI/ML-based beam management | OPPO |
R1-2406269 | Specification support for beam management | Xiaomi |
R1-2406305 | Discussion on specification support on AI/ML for beam management | Fujitsu |
R1-2406353 | Specification support for AI/ML-based beam management | CATT |
R1-2406395 | Discussion on AIML Beam Management | TCL |
R1-2406416 | Discussions on AI/ML for beam management | LG Electronics |
R1-2406440 | AI/ML specification support for beam management | Lenovo |
R1-2406463 | Discussions on AI/ML for beam management | Sony |
R1-2406492 | Specification support for AI-enabled beam management | NVIDIA |
R1-2406497 | Discussion on AI/ML for beam management | InterDigital, Inc. |
R1-2406526 | Discussion on specification support for beam management | Panasonic |
R1-2406541 | Discussion on specification support for beam management | NEC |
R1-2406571 | Discussion on AI/ML based beam management | Hyundai Motor Company |
R1-2406586 | AI/ML for Beam Management | Nokia |
R1-2406593 | Discussions on specification support for beam management | Ruijie Networks Co. Ltd |
R1-2406637 | Discussion for supporting AI/ML based beam management | Samsung |
R1-2406699 | Discussion on specification support for AI/ML beam management | Transsion Holdings |
R1-2406718 | Discussion on specification support for beam management | ETRI |
R1-2406765 | Discussion on specification support for AIML-based beam management | MediaTek Inc. |
R1-2406826 | Discussion on AI/ML beam management | Apple |
R1-2406884 | Discussion on AI/ML based beam management | KT Corp. |
R1-2406888 | AI/ML for Beam Management | Meta Ireland |
R1-2406894 | Discussions on AI/ML for beam management | CAICT |
R1-2406920 | Discussion on AI/ML for beam management | NTT DOCOMO, INC. |
R1-2406969 | Discussion on specification support for beam management | Sharp |
R1-2406977 | Discussion on beam management for AI/ML | Huawei, HiSilicon |
R1-2407019 | Specification support for AI-ML-based beam management | Qualcomm Incorporated |
R1-2407064 | Discussions on Specification Support of AI/ML for Beam Management | Indian Institute of Tech (M), IIT Kanpur |
R1-2407109 | Specification support for beam management | Fraunhofer HHI, Fraunhofer IIS |
R1-2407116 | A Novel Model-ID Free Approach for Interoperability in AI/ML Beam Management Use Cases | NTU |
R1-2407120 | Specification support for AI/ML beam management | ITL |
R1-2407142 | Specification support for beam management | KDDI Corporation |
R1-2407320 | FL summary #0 for AI/ML in beam management | Moderator (Samsung) |
R1-2407321 | FL summary #1 for AI/ML in beam management | Moderator (Samsung) |
R1-2407322 | FL summary #2 for AI/ML in beam management | Moderator (Samsung) |
R1-2407323 | FL summary #3 for AI/ML in beam management | Moderator (Samsung) |
R1-2407324 | FL summary #4 for AI/ML in beam management | Moderator (Samsung) |
R1-2407554 | FL summary #5 for AI/ML in beam management | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2405945 | AI/ML for Positioning Accuracy Enhancement | Ericsson Inc. |
R1-2405951 | AI/ML based Positioning | |
R1-2405976 | Discussion on specification support for positioning accuracy enhancement | CMCC |
R1-2406015 | Specification support for AI/ML for positioning accuracy enhancement | Intel Corporation |
R1-2406055 | Discussion on AI/ML-based positioning enhancement | ZTE Corporation, Pengcheng Laboratory |
R1-2406173 | Specification support for positioning accuracy enhancement | vivo |
R1-2406206 | Discussion on support for AIML positioning | InterDigital, Inc. |
R1-2406255 | On specification for AI/ML-based positioning accuracy enhancements | OPPO |
R1-2406270 | Discussion on AI/ML-based positioning accuracy enhancement | Xiaomi |
R1-2406306 | Discussion on specification support for AI/ML positioning accuracy enhancement | Fujitsu |
R1-2406354 | Specification support for AI/ML-based positioning | CATT, CICTCI |
R1-2406394 | Discussion on specification support for positioning accuracy enhancement | TCL |
R1-2406441 | Specification impacts for AI/ML Positioning | Lenovo |
R1-2406464 | Discussion on AI/ML for positioning accuracy enhancement | Sony |
R1-2406493 | Specification support for AI-enabled positioning | NVIDIA |
R1-2406536 | Discussion on specification support for AIML based positioning accuracy enhancement | NEC |
R1-2406587 | AI/ML for Positioning Accuracy Enhancement | Nokia |
R1-2406594 | Discussions on specification support for positioning accuracy enhancement | Ruijie Networks Co. Ltd |
R1-2406638 | Discussion for supporting AI/ML based positioning accuracy enhancement | Samsung |
R1-2406711 | AI/ML positioning accuracy enhancement | Fraunhofer IIS, Fraunhofer HHI |
R1-2406719 | Discussion on specification support for positioning accuracy enhancement | ETRI |
R1-2406827 | Discussion on Specification Support for AI/ML-based positioning | Apple |
R1-2406921 | Discussion on AI/ML for positioning accuracy enhancement | NTT DOCOMO, INC. |
R1-2406970 | Discussion on specification support for AI/ML based positioning accuracy enhancements | Sharp |
R1-2406978 | Discussion on AI/ML for positioning accuracy enhancement | Huawei, HiSilicon |
R1-2407020 | Specification support for AI-ML-based positioning accuracy enhancement | Qualcomm Incorporated |
R1-2407063 | Discussion on Specification Support of AI/ML for Positioning Accuracy Enhancement | Indian Institute of Tech (M), IIT Kanpur |
R1-2407076 | Discussion on specification support for AI/ML positioning accuracy enhancement | CEWiT |
R1-2407105 | Design for AI/ML based positioning | MediaTek Korea Inc. |
R1-2407166 | Discussions on positioning accuracy enhancement for AI/ML | ITL |
R1-2407267 | Summary #1 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2407268 | Summary #2 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2407269 | Summary #3 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2407270 | Summary #4 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2407271 | Summary #5 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
R1-2407272 | Summary #6 of specification support for positioning accuracy enhancement | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2405900 | Discussion on AIML for CSI prediction | Spreadtrum Communications, BUPT |
R1-2405952 | AI/ML based CSI Prediction | |
R1-2405961 | Discussion on AI/ML for CSI prediction | Tejas Networks Limited |
R1-2405977 | Discussion on AI/ML for CSI prediction | CMCC |
R1-2406016 | AI/ML for CSI prediction | Intel Corporation |
R1-2406056 | Discussion on study for AI/ML CSI prediction | ZTE Corporation, Sanechips |
R1-2406068 | Discussion on AI/ML for CSI prediction | BJTU |
R1-2406070 | AI/ML for CSI prediction | Ericsson |
R1-2406174 | Discussion on CSI prediction | vivo |
R1-2406256 | Additional study on AI/ML-based CSI prediction | OPPO |
R1-2406271 | Views on UE-side AI/ML model based CSI prediction | Xiaomi |
R1-2406307 | Discussion on CSI prediction with AI/ML | Fujitsu |
R1-2406355 | Further study on AI/ML for CSI prediction | CATT |
R1-2406389 | Discussion on AI/ML for CSI prediction | China Telecom |
R1-2406391 | Discussion on AI/ML for CSI prediction | Panasonic |
R1-2406417 | Study on CSI prediction | LG Electronics |
R1-2406442 | On AI/ML for CSI prediction | Lenovo |
R1-2406465 | Discussion on model monitoring of AI/ML CSI Prediction | Sony |
R1-2406494 | Additional study on AI-enabled CSI prediction | NVIDIA |
R1-2406501 | Discussion on AI/ML-based CSI prediction | InterDigital, Inc. |
R1-2406533 | Discussion on CSI prediction | NEC |
R1-2406588 | AI/ML for CSI Prediction | Nokia |
R1-2406639 | Discussion for further study on AI/ML-based CSI prediction | Samsung |
R1-2406683 | Discussion on AI/ML for CSI prediction | SK Telecom |
R1-2406788 | Additional Study on AI/ML - CSI Prediction | MediaTek Korea Inc. |
R1-2406828 | Discussion on AI based CSI prediction | Apple |
R1-2406870 | Discussion on AI/ML for CSI prediction | AT&T |
R1-2406904 | AI/ML for CSI prediction | Mavenir |
R1-2406922 | Discussion on AI/ML for CSI prediction | NTT DOCOMO, INC. |
R1-2406979 | Discussion on CSI prediction for AI/ML | Huawei, HiSilicon |
R1-2407021 | Additional study on CSI prediction | Qualcomm Incorporated |
R1-2407183 | Further study on AI/ML for CSI prediction | CATT |
R1-2407338 | Summary #1 of CSI prediction | Moderator (LG Electronics) |
R1-2407339 | Summary #2 of CSI prediction | Moderator (LG Electronics) |
R1-2407340 | Summary #3 of CSI prediction | Moderator (LG Electronics) |
R1-2407341 | Summary #4 of CSI prediction | Moderator (LG Electronics) |
R1-2407578 | Text Proposals to capture the outputs of 9.1.3.1 | Moderator (LG Electronics) |
TDoc | Title | Source |
---|---|---|
R1-2405809 | Discussion on additional study on AI/ML for NR air interface for CSI compression | FUTUREWEI |
R1-2405863 | Discussion on AI/ML for CSI compression | Huawei, HiSilicon |
R1-2405901 | Discussion on AIML for CSI compression | Spreadtrum Communications, BUPT |
R1-2405953 | AI/ML based CSI Compression | |
R1-2405960 | Discussion on AI/ML for CSI Compression | Tejas Networks Limited |
R1-2405978 | Discussion on AI/ML for CSI compression | CMCC |
R1-2406017 | AI/ML for CSI compression | Intel Corporation |
R1-2406057 | Discussion on study for AI/ML CSI compression | ZTE Corporation, Sanechips |
R1-2406069 | AI/ML for CSI compression | Ericsson |
R1-2406175 | Discussion on CSI compression | vivo |
R1-2406257 | Additional study on AI/ML-based CSI compression | OPPO |
R1-2406272 | Views on two-sided AI/ML model based CSI compression | Xiaomi |
R1-2406308 | Discussion on CSI compression with AI/ML | Fujitsu |
R1-2406356 | Further study on AI/ML for CSI compression | CATT |
R1-2406392 | Discussion on AI/ML for CSI compression | Panasonic |
R1-2406396 | Discussions on AIML CSI compression | TCL |
R1-2406418 | Study on CSI compression | LG Electronics |
R1-2406443 | On AI/ML for CSI compression | Lenovo |
R1-2406466 | Discussion on CSI compression | Sony |
R1-2406495 | Additional study on AI-enabled CSI compression | NVIDIA |
R1-2406502 | Discussion on AI/ML-based CSI compression | InterDigital, Inc. |
R1-2406534 | Discussion on CSI compression | NEC |
R1-2406589 | AI/ML for CSI Compression | Nokia |
R1-2406640 | Discussion for further study on AI/ML-based CSI compression | Samsung |
R1-2406720 | Discussion on AI/ML for CSI compression | ETRI |
R1-2406789 | Additional study on AI/ML - CSI compression | MediaTek Korea Inc. |
R1-2406829 | Discussion on AI based CSI compression | Apple |
R1-2406871 | Discussion on AI/ML for CSI compression | AT&T |
R1-2406895 | Discussions on AI/ML for CSI feedback | CAICT |
R1-2406923 | Discussion on AI/ML for CSI compression | NTT DOCOMO, INC. |
R1-2407022 | Additional study on CSI compression | Qualcomm Incorporated |
R1-2407065 | Discussion on AI/ML for CSI Compression | Indian Institute of Tech (M), IIT Kanpur |
R1-2407077 | Discussion on AI/ML for CSI Compression | CEWiT |
R1-2407121 | Discussion on AI/ML based CSI compression | ITL |
R1-2407186 | AI/ML for CSI compression | Intel Corporation |
R1-2407266 | Further study on AI/ML for CSI compression | CATT |
R1-2407342 | Summary#1 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407343 | Summary#2 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407344 | Summary#3 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407345 | Summary#4 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407346 | Summary#5 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407347 | Final summary of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407433 | Summary of Evaluation Results for AI/ML CSI compression | Moderator (Qualcomm) |
R1-2407495 | Summary#6 of Additional study on AI/ML for NR air interface: CSI compression | Moderator (Qualcomm) |
R1-2407499 | Updated summary of Evaluation Results for AI/ML CSI compression | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2405810 | Discussion on other aspects of AI/ML model and data on AI/ML for NR air-interface | FUTUREWEI |
R1-2405902 | Discussion on other aspects of AI/ML model and data | Spreadtrum Communications |
R1-2405954 | AI/ML Model and Data | |
R1-2405962 | Other aspects of AI/ML Model and Data | Tejas Networks Limited |
R1-2405979 | Discussion on other aspects of AI/ML model and data | CMCC |
R1-2406018 | Other study aspects of AI/ML for air interface | Intel Corporation |
R1-2406058 | Discussion on other aspects of AI/ML model and data | ZTE Corporation, Sanechips |
R1-2406064 | Discussion on other aspects of AI/ML model and data | Continental Automotive |
R1-2406142 | Discussion on other aspects of AI/ML | Ericsson |
R1-2406176 | Other aspects of AI/ML model and data | vivo |
R1-2406258 | Additional study on other aspects of AI/ML model and data | OPPO |
R1-2406259 | Draft TP to capture the output of Agenda item 9.1.3.3 (to collect comments) | OPPO |
R1-2406273 | Further study on AI/ML model and data | Xiaomi |
R1-2406309 | Discussion on other aspects of AI/ML model and data | Fujitsu |
R1-2406357 | Further study on AI/ML for other aspects | CATT, CICTCI |
R1-2406397 | Discussions on Other Aspects of AIML in NR air interface | TCL |
R1-2406419 | Discussion on other aspects of AI/ML model and data | LG Electronics |
R1-2406444 | Discussion on other aspects of AI/ML model and data | Lenovo |
R1-2406459 | Discussion on other aspects of AI/ML model and data | IIT Kanpur |
R1-2406496 | Additional study on other aspects of AI model and data | NVIDIA |
R1-2406503 | Discussion on other aspects of AI/ML model and data | InterDigital, Inc. |
R1-2406542 | Discussion on other aspects of AI/ML model and data | NEC |
R1-2406590 | Other Aspects of AI/ML Model and Data | Nokia |
R1-2406641 | Discussion for further study on other aspects of AI/ML model and data | Samsung |
R1-2406674 | Discussion on other aspects for AI/ML for air interface | Panasonic |
R1-2406721 | Discussion on other aspects of AI/ML model and data | ETRI |
R1-2406830 | Discussion on other aspects of AI/ML model and data | Apple |
R1-2406872 | Other Aspects of AI/ML framework | AT&T |
R1-2406889 | Other Aspects of AI/ML Model and Data | Meta Ireland |
R1-2406924 | Discussion on other aspects of AI/ML model and data | NTT DOCOMO, INC. |
R1-2406962 | Discussion on other aspects of AI/ML model and data | SHARP Corporation |
R1-2406964 | Discussion on other aspects of AI/ML model and data | Sharp |
R1-2406976 | Discussion on other aspects of the additional study for AI/ML | Huawei, HiSilicon |
R1-2407023 | Other aspects of AI/ML model and data | Qualcomm Incorporated |
R1-2407302 | Summary #1 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2407303 | Summary #2 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2407304 | Summary #3 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2407305 | Summary #4 for other aspects of AI/ML model and data | Moderator (OPPO) |
R1-2407520 | TPs to capture the outputs of 9.1.3.3 | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2406648 | List of RRC and MAC CE impact for Rel-19 MIMO Ph5 | Samsung |
R1-2407284 | DRAFT LS to RAN2 on RRC and MAC CE impacts for Rel-19 NR MIMO Ph5 | Moderator (Samsung) |
R1-2407285 | LS to RAN2 on RRC and MAC CE impacts for Rel-19 NR MIMO Ph5 | RAN1, Samsung |
TDoc | Title | Source |
---|---|---|
R1-2405814 | Enhancements for UE-initiated/event-driven beam management | FUTUREWEI |
R1-2405870 | On UE initiated/event-driven beam management | Huawei, HiSilicon |
R1-2405875 | On Rel-19 UE/Event-Driven Beam Management | InterDigital, Inc. |
R1-2405887 | Enhancements for UE-initiated/event-driven beam management | MediaTek Inc. |
R1-2405903 | Discussion on UE-initiated/event-driven beam management | Spreadtrum Communications |
R1-2405980 | Discussion on enhancements for UE-initiated/event-driven beam management | CMCC |
R1-2406027 | Enhancements for event driven beam management | Intel Corporation |
R1-2406028 | Discussion on enhancements for UE-initiated/event-driven beam management | ZTE Corporation, Sanechips |
R1-2406043 | Offline summary for Rel-19 MIMO UEIBM (9.2.1) pre-RAN1#118 | Moderator (ZTE) |
R1-2406044 | Moderator Summary #1 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2406045 | Moderator Summary #2 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2406046 | Moderator Summary #3 on UE-initiated/event-driven beam management | Moderator (ZTE) |
R1-2406177 | Discussion on UE-initiated/event-driven beam management | vivo |
R1-2406260 | Discussions on UE-initiated/event-driven beam management | OPPO |
R1-2406279 | Enhancements for UE-initiated/event-driven beam management | Xiaomi |
R1-2406310 | Discussion on enhancements for UE-initiated/event-driven beam management | Fujitsu |
R1-2406363 | On UE-initiated/event-driven beam management | CATT |
R1-2406420 | UE-initiated beam management | LG Electronics |
R1-2406454 | Enhancements for UE-initiated/Event-Driven Beam Management | Panasonic |
R1-2406467 | Enhancements for UE-initiated/event-driven beam management | Sony |
R1-2406521 | Enhancements for UE-initiated/event-driven beam management | Lenovo |
R1-2406531 | Discussion on UE-initiated/event-driven beam management | TCL |
R1-2406543 | Discussion on enhancements for UE-initiated or event-driven beam management | NEC |
R1-2406574 | Discussion on enhancements for UE-initiated/event-driven beam management | Hyundai Motor Company |
R1-2406576 | Discussion on UE-initiated/event-driven beam management | HONOR |
R1-2406595 | Discussions on enhancements for UE-initiated/event-driven beam management | Ruijie Networks Co. Ltd |
R1-2406642 | Views on Rel-19 UE-initiated/event-driven beam management | Samsung |
R1-2406682 | Discussions on enhancements for UE-initiated/event-driven beam management | KDDI Corporation |
R1-2406700 | Enhancements for UE-initiated/event-driven beam management | Transsion Holdings |
R1-2406722 | Enhancements for UE-initiated/event-driven beam management | ETRI |
R1-2406745 | Enhancements to facilitate UE-initiated/event-driven beam management | Nokia |
R1-2406831 | Enhancements for UE-initiated beam management | Apple |
R1-2406887 | Enhancements for UE Initiated Beam Management | Meta Ireland |
R1-2406925 | Discussion on enhancements for UE-initiated/event-driven beam management | NTT DOCOMO, INC. |
R1-2407002 | Enhancements for UE-initiated/event-driven beam management | Sharp |
R1-2407024 | UE-initiated/event-driven beam management | Qualcomm Incorporated |
R1-2407066 | Discussion on UE-initiated/event-driven beam management | ITRI |
R1-2407075 | Enhancements for UE-initiated/event-driven beam management | CEWiT |
R1-2407111 | Discussion on enhancements for UE-initiated or event-driven beam management | |
R1-2407122 | Discussion on UE initiated beam report | ASUSTeK |
R1-2407143 | Enhancements for UE-initiated/event-driven beam management | NICT |
R1-2407145 | Enhancements for UE-initiated beam management | Ericsson |
R1-2407470 | Moderator Summary #4 on UE-initiated/event-driven beam management | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R1-2405871 | On 128 CSI-RS ports and UE reporting enhancement | Huawei, HiSilicon |
R1-2405876 | On Rel-19 Enhancements of CSI | InterDigital, Inc. |
R1-2405888 | CSI enhancements to support up to 128 CSI-RS ports | MediaTek Inc. |
R1-2405904 | Discussion on CSI enhancements | Spreadtrum Communications |
R1-2405936 | CSI enhancements | Tejas Networks Limited |
R1-2405943 | CSI enhancements for Rel. 19 MIMO | Fraunhofer IIS, Fraunhofer HHI |
R1-2405955 | CSI Enhancement for NR MIMO | |
R1-2405981 | Discussion on CSI enhancements | CMCC |
R1-2406024 | CSI enhancements for MIMO | Intel Corporation |
R1-2406029 | Discussion on CSI enhancements | ZTE Corporation, Sanechips |
R1-2406178 | Discussion on Rel-19 CSI enhancements | vivo |
R1-2406261 | CSI enhancements for Rel-19 MIMO | OPPO |
R1-2406280 | Views on CSI enhancement | Xiaomi |
R1-2406311 | Discussion on Rel-19 CSI enhancements | Fujitsu |
R1-2406364 | Views on Rel-19 MIMO CSI enhancements | CATT |
R1-2406431 | CSI enhancements | TCL |
R1-2406468 | More views on CSI enhancements | Sony |
R1-2406522 | Discussion on CSI enhancements | Lenovo |
R1-2406548 | Discussion on CSI enhancements | NEC |
R1-2406577 | Discussion on CSI enhancements | HONOR |
R1-2406643 | Moderator summary for OFFLINE discussion on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2406644 | Moderator summary on Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2406645 | Views on Rel-19 CSI enhancements | Samsung |
R1-2406723 | Discussion on Rel-19 CSI enhancements | ETRI |
R1-2406746 | CSI enhancement for NR MIMO Phase 5 | Nokia |
R1-2406832 | Views on R19 MIMO CSI enhancement | Apple |
R1-2406907 | CSI enhancements for large antenna arrays and CJT | Ericsson |
R1-2406926 | Discussion on CSI enhancements | NTT DOCOMO, INC., NTT CORPORATION |
R1-2407003 | CSI enhancements | Sharp |
R1-2407025 | CSI enhancements for >32 ports and UE-assisted CJT | Qualcomm Incorporated |
R1-2407074 | CSI Enhancements | CEWiT |
R1-2407126 | Discussion on CSI enhancements for NR MIMO Phase 5 | KDDI Corporation |
R1-2407144 | CSI enhancements | NICT |
R1-2407184 | CSI enhancements for >32 ports and UE-assisted CJT | Qualcomm Incorporated |
R1-2407262 | Views on Rel-19 CSI enhancements | Samsung |
R1-2407279 | Moderator Summary#2 on Rel-19 CSI enhancements: Round 2 | Moderator (Samsung) |
R1-2407280 | Moderator Summary#3 on Rel-19 CSI enhancements: Round 3 | Moderator (Samsung) |
R1-2407281 | Moderator Summary#4 on Rel-19 CSI enhancements: Round 4 | Moderator (Samsung) |
R1-2407282 | Moderator Summary on Tuesday offline for Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2407283 | Moderator Summary on Wednesday offline for Rel-19 CSI enhancements | Moderator (Samsung) |
R1-2407308 | CSI enhancements for large antenna arrays and CJT | Ericsson |
R1-2407466 | Moderator Summary on Thursday offline for Rel-19 CSI enhancements | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R1-2405872 | On codebook for 3-antenna-port UL transmission | Huawei, HiSilicon |
R1-2405877 | On Rel-19 CB-based UL for 3TX UE | InterDigital, Inc. |
R1-2405879 | Summary of Offline Discussions on 3TX CB-based Uplink | Moderator (InterDigital, Inc.) |
R1-2405880 | FL Summary Support for 3TX CB-based Uplink; First Round | Moderator (InterDigital, Inc.) |
R1-2405881 | FL Summary Support for 3TX CB-based Uplink; Second Round | Moderator (InterDigital, Inc.) |
R1-2405882 | Recommended Direction on 3TX CB-based Uplink in RAN1#118b | Moderator (InterDigital, Inc.) |
R1-2405889 | Support for 3-antenna-port codebook-based transmissions | MediaTek Inc. |
R1-2405905 | Discussion on 3-antenna-port codebook-based transmissions | Spreadtrum Communications |
R1-2405956 | Uplink 3 Port Codebook based Transmission | |
R1-2405982 | Discussion on support for 3-antenna-port codebook-based transmissions | CMCC |
R1-2406025 | Support for 3Tx UL MIMO | Intel Corporation |
R1-2406030 | Discussion on 3-antenna-port codebook-based transmissions | ZTE Corporation, Sanechips |
R1-2406179 | Discussion on 3-antenna-port codebook-based uplink transmissions | vivo |
R1-2406262 | Discussion on 3-antenna-port codebook-based transmissions | OPPO |
R1-2406281 | Discussion on the support of 3-antenna-port CB based transmissions | Xiaomi |
R1-2406312 | Discussion on uplink enhancement for UE with 3Tx | Fujitsu |
R1-2406365 | On support for 3-antenna-port codebook-based transmissions | CATT |
R1-2406523 | Support for 3-antenna-port codebook-based transmissions | Lenovo |
R1-2406549 | Discussion on 3-antenna-port codebook-based transmissions | NEC |
R1-2406646 | Views on Rel-19 3-antenna-port codebook-based transmissions | Samsung |
R1-2406747 | On the support for 3-antenna-port codebook-based transmissions | Nokia |
R1-2406833 | Views on R19 3Tx codebook based transmission | Apple |
R1-2406927 | Discussion on support for 3-antenna-port codebook-based transmissions | NTT DOCOMO, INC. |
R1-2407004 | Support for 3-antenna-port codebook-based transmission | Sharp |
R1-2407026 | 3 Tx UL MIMO transmissions | Qualcomm Incorporated |
R1-2407182 | Support for 3 Tx UL Transmissions | Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2405873 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | Huawei, HiSilicon |
R1-2405878 | On Rel-19 Asymmetric mTRP Operation | InterDigital, Inc. |
R1-2405890 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | MediaTek Inc. |
R1-2405906 | Enhancements for asymmetric DL sTRP/UL mTRP scenarios | Spreadtrum Communications |
R1-2405937 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Tejas Networks Limited |
R1-2405983 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | CMCC |
R1-2406026 | Enhancements for asymmetric DL/UL scenarios | Intel Corporation |
R1-2406031 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | ZTE Corporation, Sanechips, China Telecom |
R1-2406086 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | China Telecom, ZTE |
R1-2406180 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | vivo |
R1-2406263 | Enhancements on asymmetric DL sTRP/UL mTRP scenarios | OPPO |
R1-2406265 | Discussion on asymmetric DL sTRP/UL mTRP scenarios | TCL |
R1-2406282 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | Xiaomi |
R1-2406313 | Discussion on UL-only mTRP operation | Fujitsu |
R1-2406366 | On asymmetric DL sTRP/UL mTRP scenarios | CATT |
R1-2406455 | Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios | Panasonic |
R1-2406469 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Sony |
R1-2406524 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Lenovo |
R1-2406544 | Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios | NEC |
R1-2406647 | Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios | Samsung |
R1-2406701 | Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios | Transsion Holdings |
R1-2406724 | Discussion on UL enhancement through asymmetric DL and UL | ETRI |
R1-2406748 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Nokia |
R1-2406803 | Enhancement for asymmetric DL sTRP UL mTRP scenarios | Ericsson |
R1-2406834 | Enhancements for asymmetric DL sTRP/UL mTRP | Apple |
R1-2406928 | Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios | NTT DOCOMO, INC. |
R1-2407005 | Enhancement for asymmetric DL sTRP/UL mTRP scenarios | Sharp |
R1-2407027 | Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios | Qualcomm Incorporated |
R1-2407112 | Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios | |
R1-2407123 | Discussion on asymmetric DL sTRP and UL mTRP | ASUSTeK |
R1-2407189 | Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
R1-2407190 | Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
R1-2407191 | Summary #3 on Rel-19 asymmetric DL sTRP/UL mTRP | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R1-2405815 | Discussion on SBFD TX/RX/measurement procedures | MediaTek Inc. |
R1-2405831 | Discussion for SBFD TX RX measurement procedures | New H3C Technologies Co., Ltd. |
R1-2405847 | On subband full duplex design | Huawei, HiSilicon |
R1-2405907 | Discussion on SBFD TX/RX/measurement procedures | Spreadtrum Communications |
R1-2405933 | Discussion on transmission, reception and measurement procedures for SBFD operation | ZTE Corporation, Sanechips |
R1-2405940 | Discussion for SBFD TX/RX/ measurement procedures | Tejas Networks Limited |
R1-2405984 | Discussion on SBFD TX/RX/measurement procedures | CMCC |
R1-2406059 | Discussion on SBFD TX/RX/measurement procedures | LG Electronics |
R1-2406087 | Discussion on SBFD TX/RX/measurement procedures | China Telecom |
R1-2406102 | Discussion on SBFD TX/RX/measurement procedures | TCL |
R1-2406134 | SBFD TX/RX/measurement procedures | Ericsson |
R1-2406181 | Discussion on Rel-19 SBFD operation | vivo |
R1-2406209 | Discussion on SBFD TX/RX/measurement procedures | Kookmin University |
R1-2406237 | Discussion on SBFD Tx/Rx/measurement procedures | OPPO |
R1-2406283 | Discussion on reception and transmission procedure for SBFD operation | Xiaomi |
R1-2406314 | Discussion on Tx/Rx/measurement procedures for SBFD operation | Fujitsu |
R1-2406367 | Discussion on SBFD TX/RX/measurement procedures | CATT |
R1-2406470 | SBFD Operations | Sony |
R1-2406568 | Discussion on SBFD TX/RX/measurement procedures | Panasonic |
R1-2406578 | Discussion on SBFD TX/RX/measurement procedures | HONOR |
R1-2406596 | Discussions on SBFD TX/RX/measurement procedures | Ruijie Networks Co. Ltd |
R1-2406598 | Views on SBFD TX/RX Measurement Procedures | Lenovo |
R1-2406649 | SBFD operation and procedures | Samsung |
R1-2406684 | On SBFD TX/RX/measurement procedures | Nokia, Nokia Shanghai Bell |
R1-2406691 | Discussion on subband non-overlapping full duplex Tx-Rx and measurement operations | NEC |
R1-2406702 | Discussion on SBFD operation | Transsion Holdings |
R1-2406707 | PRG allocation for SBFD | ASUS |
R1-2406725 | Discussion on SBFD TX/RX/measurement procedures | ETRI |
R1-2406749 | Discussion on TX RX and measurement procedures for SBFD operation | InterDigital, Inc. |
R1-2406800 | SBFD Tx/Rx/measurement aspects | Sharp |
R1-2406835 | Views on SBFD TX/RX/measurement procedures | Apple |
R1-2406929 | Discussion on SBFD TX/RX/measurement procedures | NTT DOCOMO, INC. |
R1-2406963 | Discussion on SBFD TX/RX/measurement procedures | Google Ireland Limited |
R1-2407028 | SBFD Transmission, Reception and Measurement Procedures | Qualcomm Incorporated |
R1-2407067 | Discussion on SBFD TX/RX/measurement procedures | ITRI |
R1-2407084 | Discussion on SBFD TX/RX/measurement procedures | CEWiT |
R1-2407158 | Discussion on SBFD TX/RX/measurement procedures | WILUS Inc. |
R1-2407218 | Summary #1 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
R1-2407219 | Summary #2 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
R1-2407220 | Summary #3 of SBFD TX/RX/measurement procedures | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2405816 | Discussion on SBFD Random Access Operation | MediaTek Inc. |
R1-2405832 | Discussion for SBFD random access operation | New H3C Technologies Co., Ltd. |
R1-2405848 | On subband full duplex random access operation | Huawei, HiSilicon |
R1-2405908 | Discussion on SBFD random access operation | Spreadtrum Communications |
R1-2405934 | Discussion on SBFD random access operation | ZTE Corporation, Sanechips |
R1-2405941 | Discussion on SBFD Random Access Operation | Tejas Networks Limited |
R1-2405985 | Discussion on SBFD random access operation | CMCC |
R1-2406060 | Discussion on SBFD random access operation | LG Electronics |
R1-2406088 | Discussion on SBFD random access operation | China Telecom |
R1-2406103 | Discussion on SBFD random access operation | TCL |
R1-2406106 | Discussion on SBFD random access operation | Korea Testing Laboratory |
R1-2406135 | SBFD Random access operation | Ericsson |
R1-2406182 | Discussion on random access for Rel-19 SBFD | vivo |
R1-2406210 | Discussion on SBFD random access operation | Kookmin University |
R1-2406238 | Discussion on SBFD random access operation | OPPO |
R1-2406284 | Discussion on SBFD random access operation | Xiaomi |
R1-2406368 | Discussion on SBFD random access operation | CATT |
R1-2406471 | SBFD PRACH Operations | Sony |
R1-2406514 | Discussion on SBFD random access operation | Fujitsu |
R1-2406562 | Discussion on random access for SBFD | NEC |
R1-2406569 | Discussion on SBFD random access operation | Panasonic |
R1-2406575 | Discussion on SBFD random access operation | Hyundai Motor Company |
R1-2406650 | Random access on SBFD resources | Samsung |
R1-2406685 | SBFD random access operation | Nokia, Nokia Shanghai Bell |
R1-2406688 | SBFD random access operation | Lenovo |
R1-2406703 | Discussion on SBFD random access operation | Transsion Holdings |
R1-2406726 | SBFD random access operation | ETRI |
R1-2406750 | On SBFD random access operation | InterDigital, Inc. |
R1-2406781 | On SBFD random access operation | Google Ireland Limited |
R1-2406801 | SBFD random access aspects | Sharp |
R1-2406836 | Views on SBFD random access operation | Apple |
R1-2406886 | Discussion on SBFD Random Access operation | KT Corp. |
R1-2406930 | Discussion on SBFD random access operation | NTT DOCOMO, INC. |
R1-2407029 | SBFD Random Access Operation | Qualcomm Incorporated |
R1-2407068 | Discussion on SBFD random access operation for SBFD aware UEs in RRC CONNECTED state | ITRI |
R1-2407085 | Discussion on SBFD random access operation | CEWiT |
R1-2407159 | Discussion on SBFD random access operation | WILUS Inc. |
R1-2407228 | Summary#1 on SBFD random access operation | Moderator (CMCC) |
R1-2407229 | Summary#2 on SBFD random access operation | Moderator (CMCC) |
R1-2407230 | Summary#3 on SBFD random access operation | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2405817 | Discussion on CLI Handling in SBFD system | MediaTek Inc. |
R1-2405833 | Discussion on CLI handling | New H3C Technologies Co., Ltd. |
R1-2405849 | On cross-link interference handling for subband full duplex | Huawei, HiSilicon |
R1-2405909 | Discussion on CLI handling | Spreadtrum Communications |
R1-2405935 | Discussion on CLI handling for Rel-19 duplex operation | ZTE Corporation, Sanechips |
R1-2405942 | Discussion on gNB-gNB CLI handling | Tejas Networks Limited |
R1-2405986 | Discussion on CLI handling | CMCC |
R1-2406061 | Discussion on CLI handling | LG Electronics |
R1-2406136 | SBFD CLI handling | Ericsson |
R1-2406183 | Discussion on CLI handling for Rel-19 NR duplex | vivo |
R1-2406239 | CLI handling in NR duplex operation | OPPO |
R1-2406285 | Discussion on CLI handling for SBFD operation | Xiaomi |
R1-2406369 | Discussion on CLI handling for NR duplex evolution | CATT |
R1-2406472 | CLI handling for SBFD | Sony |
R1-2406563 | CLI handling for NR duplex operations | NEC |
R1-2406570 | Discussion on CLI handling | Panasonic |
R1-2406651 | Cross-link interference handling for SBFD | Samsung |
R1-2406686 | Cross-link interference handling for duplex evolution | Nokia, Nokia Shanghai Bell |
R1-2406716 | Further Considerations and Recommendations for CLI mitigation for Subband Full Duplex | Charter Communications, Inc |
R1-2406727 | Discussion on CLI handling for SBFD operation | ETRI |
R1-2406751 | On CLI handling for SBFD operation | InterDigital, Inc. |
R1-2406782 | On the gNB-to-gNB CLI and the UE-to-UE CLI handling | Google Ireland Limited |
R1-2406837 | Views on CLI handling | Apple |
R1-2406931 | Discussion on CLI handling | NTT DOCOMO, INC. |
R1-2407030 | Enhancements for CLI handling | Qualcomm Incorporated |
R1-2407062 | Cross-link interference management for duplexing evolution | Lenovo |
R1-2407086 | Discussion on CLI handling | CEWiT |
R1-2407160 | Discussion on CLI handling for NR duplex operation | WILUS Inc. |
R1-2407353 | Summary #1 of CLI handling | Moderator (Huawei) |
R1-2407354 | Summary #2 of CLI handling | Moderator (Huawei) |
R1-2407355 | Summary #3 of CLI handling | Moderator (Huawei) |
R1-2407533 | LS to RAN3 on PHY/L1 aspects of information exchange among gNBs for CLI mitigation | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R1-2406752 | Update for TR 38.769 “Study on Solutions for Ambient IoT (Internet of Things)” | Huawei |
R1-2407363 | Draft Reply LS on Clarification of requirements for Ambient IoT | Ericsson |
R1-2407364 | Reply LS on Clarification of requirements for Ambient IoT | RAN1, Ericsson |
R1-2407365 | Moderator summary for RAN1 reply to SA2 LS on Clarification of requirements for Ambient IoT | Moderator (Ericsson) |
R1-2407399 | Draft Reply LS on Clarification of requirements for Ambient IoT | Ericsson |
R1-2407479 | Session notes for 9.4 (Study on solutions for Ambient IoT in NR) | Ad-Hoc Chair (Huawei) |
R1-2407489 | Update for TR 38.769 “Study on Solutions for Ambient IoT (Internet of Things)” | Huawei |
R1-2407513 | TR 38.769 v0.1.0 “Study on Solutions for Ambient IoT (Internet of Things)” | Huawei |
R1-2407579 | TR 38.769 v1.0.0 “Study on Solutions for Ambient IoT (Internet of Things)” | Huawei |
TDoc | Title | Source |
---|---|---|
R1-2405800 | Discussion on evaluation assumptions and results for Ambient IoT devices | FUTUREWEI |
R1-2405818 | Evaluation assumptions and results for Ambient IoT | Nokia |
R1-2405824 | Evaluation assumptions and results for Ambient IoT | Ericsson |
R1-2405850 | Evaluation methodology and assumptions for Ambient IoT | Huawei, HiSilicon |
R1-2405910 | Discussion on evaluation assumptions and results for Ambient IoT | Spreadtrum Communications |
R1-2405938 | Evaluation assumption and link level simulation of AIoT | Tejas Networks Limited |
R1-2405987 | Discussion on evaluation methodology and assumptions | CMCC |
R1-2406089 | Discussion on evaluation assumptions and results for Ambient IoT | China Telecom |
R1-2406184 | Evaluation methodologies assumptions and results for Ambient IoT | vivo |
R1-2406240 | Discussion on evaluation assumptions and results for A-IoT | OPPO |
R1-2406286 | Evaluation methodology& assumptions and results for Ambient IoT | Xiaomi |
R1-2406370 | The evaluation methodology and preliminary results of Ambient IoT | CATT |
R1-2406403 | Discussion on Ambient IoT evaluations | ZTE Corporation, Sanechips |
R1-2406433 | Analysis of cfo drift for Ambient IoT | Wiliot Ltd. |
R1-2406473 | Ambient IoT evaluations | Sony |
R1-2406579 | Discussion on evaluation assumptions and results for Ambient IoT | HONOR |
R1-2406599 | Initial evaluation by link level simulation for Ambient IoT R2D | Panasonic |
R1-2406602 | Discussion on Ambient IoT evaluation | LG Electronics |
R1-2406652 | Considerations for evaluation assumptions and results | Samsung |
R1-2406692 | Discussion on ambient IoT evaluation framework | NEC |
R1-2406771 | Evaluation assumptions and results for A-IoT | MediaTek Inc. |
R1-2406811 | Discussion on the evaluation assumptions for Ambient IoT devices | Lenovo |
R1-2406838 | On evaluation assumptions and link budget analysis for AIoT | Apple |
R1-2406890 | Evaluations for Ambient IoT | InterDigital, Inc. |
R1-2406932 | Study on evaluation assumptions and results for Ambient IoT | NTT DOCOMO, INC. |
R1-2407031 | Evaluation Assumptions and Results | Qualcomm Incorporated |
R1-2407087 | Discussion on Evaluation assumptions and results | CEWiT |
R1-2407095 | Evaluation assumptions and results for Ambient IoT | Indian Institute of Tech (M), IIT Kanpur |
R1-2407134 | Evaluation assumption and results for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407185 | Discussion on evaluation methodology and assumptions | CMCC |
R1-2407325 | FL summary #1 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2407326 | FL summary #2 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2407327 | FL summary #3 for Ambient IoT evaluation | Moderator (CMCC) |
R1-2407560 | Final FL summary for Ambient IoT evaluation | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2405801 | Discussion on Rel-19 Ambient IoT device architecture | FUTUREWEI |
R1-2405819 | Ambient IoT device architectures | Nokia |
R1-2405825 | Ambient IoT device architectures | Ericsson |
R1-2405851 | Ultra low power device architectures for Ambient IoT | Huawei, HiSilicon |
R1-2405911 | Discussion on Ambient IoT device architectures | Spreadtrum Communications |
R1-2405939 | Study the Ambient IoT Device Architecture | Tejas Networks Limited |
R1-2405988 | Discussion on Ambient IoT device architectures | CMCC |
R1-2406090 | Discussion on Ambient IoT device architectures | China Telecom |
R1-2406185 | Discussion on Ambient IoT Device architectures | vivo |
R1-2406241 | Discussion on device architecture for A-IoT device | OPPO |
R1-2406287 | Discussion on ambient IoT device architectures | Xiaomi |
R1-2406371 | Study of the Ambient IoT devices architecture | CATT |
R1-2406404 | Discussion on Ambient IoT device architectures | ZTE Corporation, Sanechips |
R1-2406566 | Discussion on ambient IoT device architectures | TCL |
R1-2406603 | Discussion on Ambient IoT device architectures | LG Electronics |
R1-2406653 | Considerations for Ambient-IoT device architectures | Samsung |
R1-2406693 | Device architecture requirements for ambient IoT | NEC |
R1-2406772 | Ambient IoT device architectures | MediaTek Inc. |
R1-2406812 | Discussion on the Ambient IoT device architectures | Lenovo |
R1-2406839 | On device architecture for AIoT | Apple |
R1-2406891 | Device architectures for Ambient IoT | InterDigital, Inc. |
R1-2406933 | Study on device architectures for Ambient IoT | NTT DOCOMO, INC. |
R1-2407032 | Ambient IoT Device Architecture | Qualcomm Incorporated |
R1-2407096 | Discussion on Ambient IoT device architectures | Indian Institute of Tech (M), IIT Kanpur |
R1-2407133 | Views on Architecture of Ambient IoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407175 | Ambient IoT device architecture | Sony |
R1-2407273 | RAN1#118 FL Summary #1 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2407274 | RAN1#118 FL Summary #2 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2407275 | RAN1#118 FL Summary #3 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
R1-2407276 | RAN1#118 FL Summary #4 for 9.4.1.2 Ambient IoT Device Architecture | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R1-2405802 | Discussion on physical layer design for Rel-19 Ambient IoT devices | FUTUREWEI |
R1-2405820 | General aspects of physical layer design for Ambient IoT | Nokia |
R1-2405826 | General aspects of physical layer design for Ambient IoT | Ericsson |
R1-2405852 | On general aspects of physical layer design for Ambient IoT | Huawei, HiSilicon |
R1-2405912 | Discussion on general aspects of physical layer design for Ambient IoT | Spreadtrum Communications |
R1-2405968 | Discussion on general aspects of physical layer design for Ambient IoT | TCL |
R1-2405989 | Discussion on general aspects of A-IoT physical layer design | CMCC |
R1-2406082 | Discussion on Physical Layer Design for Ambient-IoT | EURECOM |
R1-2406091 | Discussion on general aspects of physical layer design for Ambient IoT | China Telecom |
R1-2406186 | Discussion on General Aspects of Physical Layer Design | vivo |
R1-2406242 | Discussion on general aspects of physical layer design of A-IoT communication | OPPO |
R1-2406288 | Discussion on physical layer design of Ambient IoT | Xiaomi |
R1-2406315 | Consideration on general aspects of physical layer | Fujitsu |
R1-2406372 | Discussion on general aspects of physical layer design | CATT |
R1-2406405 | Discussion on general aspects of physical layer design for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406445 | On General Physical Layer Design Considerations for Ambient IoT (internet of things) Applications | Lekha Wireless Solutions |
R1-2406474 | General aspects of Ambient IoT physical layer design | Sony |
R1-2406557 | Discussion on general aspects of ambient IoT physical layer design | NEC |
R1-2406600 | General aspects of physical layer design for Ambient IoT | Panasonic |
R1-2406604 | General aspects of Ambient IoT physical layer design | LG Electronics |
R1-2406654 | Considerations on general aspects of Ambient IoT | Samsung |
R1-2406728 | Discussion on general aspects of physical layer design | ETRI |
R1-2406773 | General aspects of physical layer design | MediaTek Inc. |
R1-2406813 | Discussion on the physical layer design aspects for Ambient IoT devices | Lenovo |
R1-2406840 | On general physical layer design aspects for AIoT | Apple |
R1-2406878 | Discussion on general aspects of physical layer design | Sharp |
R1-2406892 | On the general aspects of physical layer design for Ambient IoT | InterDigital, Inc. |
R1-2406934 | Study on general aspects of physical layer design for Ambient IoT | NTT DOCOMO, INC. |
R1-2407033 | General aspects of physical layer design | Qualcomm Incorporated |
R1-2407088 | Discussion on General aspects of physical layer design | CEWiT |
R1-2407119 | General aspects of physical layer design for Ambient IoT | ITL |
R1-2407131 | Discussion on General aspects of physical layer design of AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407248 | Feature Lead Summary #1 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
R1-2407249 | Feature Lead Summary #2 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
R1-2407250 | Feature Lead Summary #3 for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2405803 | Frame Structure and Timing Aspects for Ambient IoT | FUTUREWEI |
R1-2405821 | Frame structure and timing aspects for Ambient IoT | Nokia |
R1-2405827 | Frame structure and timing aspects for Ambient IoT | Ericsson |
R1-2405853 | On frame structure and timing aspects of Ambient IoT | Huawei, HiSilicon |
R1-2405913 | Discussion on frame structure and timing aspects for Ambient IoT | Spreadtrum Communications |
R1-2405965 | Discussion on frame structure and timing aspects of A-IoT | Tejas Networks Limited |
R1-2405990 | Discussion on frame structure and timing aspects for A-IoT | CMCC |
R1-2406011 | Discussions on frame structure and timing aspects for A-IoT | Intel Corporation |
R1-2406071 | Discussion on frame structure and physical layer procedures for Ambient IoT | Lenovo |
R1-2406092 | Discussion on frame structure and timing aspects for Ambient IoT | China Telecom |
R1-2406187 | Discussion on Frame structure, random access, scheduling and timing aspects for Ambient IoT | vivo |
R1-2406243 | Discussion on frame structure and timing aspects of A-IoT communication | OPPO |
R1-2406266 | Discussion on A-IoT Frame Structure and Timing Aspects | Panasonic |
R1-2406289 | Discussion on frame structure and timing aspects for Ambient IoT | Xiaomi |
R1-2406316 | Discussion on frame structure and timing aspects | Fujitsu |
R1-2406373 | Study of Frame structure and timing aspects for Ambient IoT | CATT |
R1-2406406 | Discussion on frame structure and physical layer procedure for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406421 | Discussion on frame structure and timing aspects for Ambient IoT | BUPT |
R1-2406453 | Discussion on Frame Structure and Timing Aspects for Ambient IoT | IIT, Kharagpur |
R1-2406456 | Frame structure and timing aspects of Ambient IoT | InterDigital, Inc. |
R1-2406475 | Frame structure and timing aspects for Ambient IoT | Sony |
R1-2406558 | Discussion on frame structure and timing for ambient IoT | NEC |
R1-2406580 | Discussion on frame structure and timing aspects for Ambient IoT | HONOR |
R1-2406605 | Frame structure and timing aspects for Ambient IoT | LG Electronics |
R1-2406655 | Considerations for frame structure and timing aspects | Samsung |
R1-2406729 | Discussion on frame structure and timing aspects | ETRI |
R1-2406774 | Frame structure and timing aspects | MediaTek Inc. |
R1-2406841 | Frame structure and timing aspects for Ambient IoT | Apple |
R1-2406879 | Discussion on frame structure and timing aspects | Sharp |
R1-2406935 | Study on frame structure and timing aspects for Ambient IoT | NTT DOCOMO, INC. |
R1-2407034 | Frame structure and timing aspects | Qualcomm Incorporated |
R1-2407070 | Discussion on Frame structure and timing aspects for A-IoT | China Unicom |
R1-2407089 | Discussion on Frame structure and timing aspects | CEWiT |
R1-2407107 | Discussion on frame structure and timing aspects for Ambient IoT | TCL |
R1-2407113 | Discussion on frame structure and timing aspects | |
R1-2407130 | Frame structure and timing aspects of AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407137 | Discussion on frame structure and timing aspect | ASUSTeK |
R1-2407202 | FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2407203 | FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2407204 | FL summary #3 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2407490 | FL summary #4 on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
R1-2407532 | Final FL summary on frame structure and timing aspects for Rel-19 Ambient IoT | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2405804 | D2R and R2D Channel/Signal Aspects for Ambient IoT | FUTUREWEI |
R1-2405822 | R2D and D2R channel/signal aspects for Ambient IoT | Nokia |
R1-2405828 | Downlink and uplink channel/signal aspects for Ambient IoT | Ericsson |
R1-2405854 | Physical channels and signals for Ambient IoT | Huawei, HiSilicon |
R1-2405914 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | Spreadtrum Communications |
R1-2405969 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | TCL |
R1-2405991 | Discussion on downlink and uplink channel/signal aspects | CMCC |
R1-2406012 | Discussions on physical channel and signals for A-IoT | Intel Corporation |
R1-2406072 | Discussion on channel/signal aspects for Ambient IoT | Lenovo |
R1-2406093 | Discussion on downlink and uplink channel/signal aspects for Ambient IoT | China Telecom |
R1-2406143 | Considerations for downlink and uplink channel/signal aspects | Semtech Neuchatel SA |
R1-2406188 | Discussion on Downlink and uplink channel/signal aspects | vivo |
R1-2406244 | Discussion on downlink and uplink channel/signal aspects for A-IoT | OPPO |
R1-2406290 | Discussion on downlink and uplink channel and signal aspects for Ambient IoT | Xiaomi |
R1-2406317 | Discussion on downlink and uplink channel/signal aspects | Fujitsu |
R1-2406374 | DL and UL Physical Channels/signals design in support of Ambient IoT devices | CATT |
R1-2406407 | Discussion on channel and signal for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406429 | Discussion on downlink and uplink channels and signals for A-IoT | Panasonic |
R1-2406457 | Downlink and uplink channels aspects of Ambient IoT | InterDigital, Inc. |
R1-2406476 | Downlink and uplink channel / signal aspects for Ambient IoT | Sony |
R1-2406505 | Considerations on Control Information, Proximity Determination, and Intermediate UE for A-IoT | Continental Automotive |
R1-2406559 | Discussion on downlink and uplink channel for ambient IoT | NEC |
R1-2406581 | Discussion on downlink and uplink channel/signal aspects for A-IoT | HONOR |
R1-2406606 | Downlink and uplink channel/signal aspects for Ambient IoT | LG Electronics |
R1-2406656 | Considerations for downlink and uplink channel/signal aspect | Samsung |
R1-2406730 | Discussion on downlink and uplink channel/signal aspects for A-IoT | ETRI |
R1-2406775 | Downlink and uplink channel/signal aspects | MediaTek Inc. |
R1-2406842 | On physical channels/signals and proximity determination for AIoT | Apple |
R1-2406844 | FL summary#1 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2406845 | FL summary#2 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2406846 | FL summary#3 on downlink and uplink channel/signal aspects | Moderator (Apple) |
R1-2406880 | Discussion on downlink and uplink channel/signal aspects | Sharp |
R1-2406936 | Study on downlink and uplink channel/signal aspects for Ambient IoT | NTT DOCOMO, INC. |
R1-2407035 | Downlink and uplink channel/signal aspects | Qualcomm Incorporated |
R1-2407071 | Discussion on downlink and uplink channel aspects for A-IoT | China Unicom |
R1-2407090 | Discussion on Downlink and Uplink channel/signal aspects | CEWiT |
R1-2407114 | Discussion on downlink and uplink transmission aspects | |
R1-2407129 | Discussion on Downlink and Uplink channel signal aspects for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407141 | Discussion on downlink and uplink channel/signal aspect | ASUSTeK |
R1-2407555 | Final summary on downlink and uplink channel/signal aspects | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R1-2405805 | Discussion on External Carrier Waveform Characteristics for Rel-19 Ambient IoT devices | FUTUREWEI |
R1-2405823 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | Nokia |
R1-2405829 | Waveform characteristics of carrier wave provided externally to the Ambient IoT device | Ericsson |
R1-2405855 | On external carrier wave for backscattering based Ambient IoT device | Huawei, HiSilicon |
R1-2405915 | Discussion on waveform characteristics of external carrier-wave for Ambient IoT | Spreadtrum Communications |
R1-2405967 | Discussion on CW waveform characteristics of A-IoT | Tejas Networks Limited |
R1-2405970 | Discussion on waveform characteristics of external carrier-wave for Ambient IoT | TCL |
R1-2405992 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | CMCC |
R1-2406013 | Discussions on waveform characteristics of carrier-wave for A-IoT | Intel Corporation |
R1-2406073 | Discussion on external carrier wave for Ambient IoT | Lenovo |
R1-2406094 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | China Telecom |
R1-2406144 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | Semtech Neuchatel SA |
R1-2406189 | Discussion on CW waveform and interference handling at AIoT UL receiver | vivo |
R1-2406245 | Discussion on Waveform characteristics of carrier-wave provided externally to the A-IoT device | OPPO |
R1-2406291 | Discussion on waveform characteristics of carrier-wave | Xiaomi |
R1-2406318 | Analyses on interference between AIoT and NR | Fujitsu |
R1-2406375 | Discussion on the waveform characteristics of carrier-wave for the Ambient IoT device | CATT |
R1-2406408 | Discussion on carrier wave for Ambient IoT | ZTE Corporation, Sanechips |
R1-2406430 | Discussion on waveform characteristics of carrier-wave for Ambient IoT device | Panasonic |
R1-2406560 | Discussion on the waveform of carrier-wave for the Ambient IoT | NEC |
R1-2406607 | Considerations on carrier-wave transmission for Ambient IoT | LG Electronics |
R1-2406657 | Considerations for Waveform characteristics of carrier-wave | Samsung |
R1-2406731 | Discussion on carrier-wave for Ambient IoT | ETRI |
R1-2406776 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | MediaTek Inc. |
R1-2406843 | On carrier waveform and interference handling for AIoT | Apple |
R1-2406893 | On the carrier-wave for Ambient IoT | InterDigital, Inc. |
R1-2406937 | Study on waveform characteristics of carrier-wave for Ambient IoT | NTT DOCOMO, INC. |
R1-2407036 | Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | Qualcomm Incorporated |
R1-2407072 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | China Unicom |
R1-2407091 | Discussion on Waveform characteristics of carrier-wave provided externally to the Ambient IoT device | CEWiT |
R1-2407124 | Controllable Carrier Wave Characteristics | Sony |
R1-2407128 | Discussion on Carrier wave related aspects for AIoT | IIT Kanpur, Indian Institute of Tech (M) |
R1-2407312 | FL summary#1 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2407313 | FL summary#2 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2407426 | Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device | CMCC |
R1-2407468 | FL summary#3 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2407469 | FL summary#4 on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
R1-2407544 | Final FL summary on CW waveform characteristics for A-IoT | Moderator (Spreadtrum Communications) |
TDoc | Title | Source |
---|---|---|
R1-2405811 | Discussion of on-demand SSB Scell operation | FUTUREWEI |
R1-2405856 | On-demand SSB SCell operation for eNES | Huawei, HiSilicon |
R1-2405894 | On-demand SSB SCell operation | Tejas Networks Limited |
R1-2405916 | Discussion on on-demand SSB SCell operation | Spreadtrum Communications |
R1-2405957 | On-demand SSB SCell Operation | |
R1-2405993 | Discussion on on-demand SSB SCell operation | CMCC |
R1-2406021 | Design of on-demand SSB SCell operation | Intel Corporation |
R1-2406049 | On-demand SSB SCell Operation | Nokia, Nokia Shanghai Bell |
R1-2406095 | Discussion on on-demand SSB operation for SCell | China Telecom |
R1-2406190 | Discussions on on-demand SSB Scell operation | vivo |
R1-2406226 | Discussion on the enhancement to support on demand SSB SCell operation | OPPO |
R1-2406292 | Discussion on on-demand SSB SCell operation | Xiaomi |
R1-2406376 | Discussion on on-demand SSB SCell operation | CATT |
R1-2406409 | Discussion on on-demand SSB for NES | ZTE Corporation, Sanechips |
R1-2406477 | On-demand SSB SCell operation | Sony |
R1-2406507 | Discussion on on-demand SSB SCell operation | InterDigital, Inc. |
R1-2406515 | Discussion on on-demand SSB SCell operation | Fujitsu |
R1-2406608 | On-demand SSB SCell operation | LG Electronics |
R1-2406658 | On-demand SSB SCell operation | Samsung |
R1-2406689 | On-demand SSB SCell operation | Lenovo |
R1-2406694 | Discussion on on-demand SSB for SCell operation | NEC |
R1-2406704 | Discussion on On-Demand SSB SCell operation | Transsion Holdings |
R1-2406708 | DCI based signaling for on-demand SSB | ASUSTeK |
R1-2406732 | Discussion on On-demand SSB SCell operation | ETRI |
R1-2406758 | On-demand SSB SCell operation | MediaTek Inc. |
R1-2406783 | Discussion on on-demand SSB SCell operation | Panasonic |
R1-2406847 | On-demand SSB SCell Operation | Apple |
R1-2406902 | Discussion of On-demand SSB SCell operation | Mavenir |
R1-2406938 | Discussion on on-demand SSB SCell operation | NTT DOCOMO, INC. |
R1-2406971 | Discussion on details of on-demand SSB operation on Scell | Sharp |
R1-2407037 | On-demand SSB operation for Scell | Qualcomm Incorporated |
R1-2407056 | On-demand SSB SCell operation | Ericsson |
R1-2407080 | Discussion on on-demand SSB Scell operation | CEWiT |
R1-2407330 | Summary #1 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2407331 | Summary #2 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2407332 | Summary #3 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2407333 | Summary #4 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2407437 | DRAFT LS to RAN2 for on-demand SSB SCell operation | Moderator (LG Electronics) |
R1-2407438 | LS to RAN2 for on-demand SSB SCell operation | RAN1, LG Electronics |
R1-2407543 | Summary #5 of on-demand SSB for NES | Moderator (LG Electronics) |
R1-2407549 | Draft LS on timeline for On-demand SSB operation on SCell | Apple |
R1-2407565 | LS on timeline for On-demand SSB operation on SCell | RAN1, Apple |
TDoc | Title | Source |
---|---|---|
R1-2405812 | Discussion of on-demand SIB1 for idle/inactive mode UEs | FUTUREWEI |
R1-2405857 | Discussion on on-demand SIB1 for eNES | Huawei, HiSilicon |
R1-2405893 | On-demand SIB1 for idle/inactive mode UEs | Tejas Networks Limited |
R1-2405917 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Spreadtrum Communications |
R1-2405958 | On-demand SIB1 for Idle/Inactive Mode UE | |
R1-2405994 | Discussion on on-demand SIB1 for UEs in idle/inactive mode | CMCC |
R1-2406022 | Study of on-demand SIB1 for idle/inactive mode UEs | Intel Corporation |
R1-2406050 | On-demand SIB1 for Idle/Inactive mode UEs | Nokia, Nokia Shanghai Bell |
R1-2406096 | Discussion on on-demand SIB1 for idle/inactive mode UEs | China Telecom |
R1-2406191 | Discussions on on-demand SIB1 for idle/inactive mode UEs | vivo |
R1-2406227 | Discussion on the enhancement to support on demand SIB1 for idle/inactive mode UE | OPPO |
R1-2406293 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Xiaomi |
R1-2406377 | Discussion on on-demand SIB1 | CATT |
R1-2406410 | Discussion on on-demand SIB1 for NES | ZTE Corporation, Sanechips |
R1-2406478 | On-demand SIB1 for idle/inactive mode UEs | Sony |
R1-2406508 | Discussion on on-demand SIB1 for idle/inactive mode UEs | InterDigital, Inc. |
R1-2406516 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Fujitsu |
R1-2406609 | On-demand SIB1 for idle/inactive mode UEs | LG Electronics |
R1-2406659 | On-demand SIB1 for idle/inactive mode UEs | Samsung |
R1-2406690 | On-demand SIB1 for idle/inactive mode UEs | Lenovo |
R1-2406695 | Discussion on on-demand SIB1 for UEs in idle/inactive mode | NEC |
R1-2406705 | Discussion on on-demand SIB1 transmission for idle/inactive mode UEs | Transsion Holdings |
R1-2406709 | Triggering of on-demand SIB1 | ASUSTeK |
R1-2406733 | On-demand SIB1 for idle/inactive mode UEs for NES | ETRI |
R1-2406759 | On-demand SIB1 for idle or inactive mode UEs | MediaTek Inc. |
R1-2406784 | Discussion on on-demand SIB1 for idle/inactive mode UEs | Panasonic |
R1-2406848 | On On-demand SIB1 for IDLE/INACTIVE mode UEs | Apple |
R1-2406939 | Discussion on on-demand SIB1 for idle/inactive mode UEs | NTT DOCOMO, INC. |
R1-2406968 | Discussion on on-demand SIB1 in idle/inactive mode | CAICT |
R1-2406972 | Discussion on on-demand SIB1 transmission for idle UEs | Sharp |
R1-2407038 | On-demand SIB1 procedure | Qualcomm Incorporated |
R1-2407057 | Study of on-demand SIB1 for UEs in idle/inactive mode for NES | Ericsson |
R1-2407081 | Discussion on on-demand SIB1 | CEWiT |
R1-2407083 | On-demand SIB1 for NES | CEWiT |
R1-2407103 | On-demand SIB1 for NES | Fraunhofer IIS, Fraunhofer HHI, Vodafone, Deutsche Telekom, CEWiT |
R1-2407127 | On-demand SIB1 for Idle/Inactive mode UEs | III |
R1-2407156 | Discussion on on-demand SIB1 for idle/inactive mode UEs | DENSO CORPORATION |
R1-2407213 | FL summary 1 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2407214 | FL summary 2 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2407215 | FL summary 3 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2407216 | FL summary 4 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
R1-2407217 | FL summary 5 for on-demand SIB1 in idle/inactive mode | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R1-2405813 | Discussion of the adaptation of common signal/channel transmissions | FUTUREWEI |
R1-2405858 | On common channel/signal adaptation for eNES | Huawei, HiSilicon |
R1-2405892 | Adaptation of common signal/channel transmissions | Tejas Networks Limited |
R1-2405918 | Discussion on adaptation of common signal/channel transmissions | Spreadtrum Communications |
R1-2405959 | Adaptation of Common Signals | |
R1-2405995 | Discussion on adaptation of common signal/channel transmissions | CMCC |
R1-2406023 | Adaptation of common signal/channel transmissions for Network Energy Saving | Intel Corporation |
R1-2406051 | Adaptation of common signal/channel transmissions | Nokia, Nokia Shanghai Bell |
R1-2406097 | Discussion on common signal/channel adaptation | China Telecom |
R1-2406192 | Discussions on adaptation of common signal/channel transmissions | vivo |
R1-2406228 | Discussion on adaptation of common signal/channel transmission | OPPO |
R1-2406294 | Discussion on adaptation of common signal and channel transmissions | Xiaomi |
R1-2406378 | Discussion on adaptation of common signal/channel transmissions | CATT |
R1-2406411 | Discussion on common signal channel for NES | ZTE Corporation, Sanechips |
R1-2406479 | Adaptation of common signal/channel transmissions | Sony |
R1-2406509 | Discussion on adaptation of common signal/channel transmissions | InterDigital, Inc. |
R1-2406517 | Discussion on adaptation of common signal / channel transmissions | Fujitsu |
R1-2406582 | Discussion on adaptation of common signal channel transmissions | HONOR |
R1-2406610 | Adaptation of common signal/channel transmissions | LG Electronics |
R1-2406660 | Adaptation of common signal/channel transmissions | Samsung |
R1-2406687 | Discussion on adaptation of common signal/channel transmission | PANASONIC R&D Center Germany |
R1-2406696 | Discussion on adaptation of common signal/channel transmissions for Cell DTX/DRX | NEC |
R1-2406706 | Discussion on adaptive transmission of common signal or common channel | Transsion Holdings |
R1-2406712 | Discussion on adaptation of common signal/channel transmission | Panasonic |
R1-2406734 | Adaptation of common signal/channel transmissions for NES | ETRI |
R1-2406760 | Adaptation of common signal/channel transmissions | MediaTek Inc. |
R1-2406807 | Adaptation of common signals and channels | Lenovo |
R1-2406849 | On adaptation of common signal/channel for NES enhancements | Apple |
R1-2406940 | Discussion on adaptation of common signal/channel transmissions | NTT DOCOMO, INC. |
R1-2406973 | Discussion on adaptation of common signal/channel transmissions | Sharp |
R1-2407039 | Adaptation of common channel transmissions | Qualcomm Incorporated |
R1-2407058 | Adaptation of common signal/channel transmissions for NES | Ericsson |
R1-2407069 | Discussion on adaptation of common signal/channel transmissions | ITRI |
R1-2407082 | Discussion on adaptation of common signal and channel transmissions | CEWiT |
R1-2407100 | Adaptation of Common Signals and Channels for NES | Fraunhofer IIS, Fraunhofer HHI |
R1-2407157 | Discussion on adaptation of common signal/channel transmissions | DENSO CORPORATION |
R1-2407277 | Summary#1 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2407278 | Summary#2 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2407408 | Summary#3 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2407409 | Summary#4 of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
R1-2407552 | Final summary of AI 9.5.3 for R19 NES | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R1-2407493 | Summary of RAN1 agreements on LP-WUS/WUR for NR | Rapporteur (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2405806 | Discussion on LP-WUS and LP-SS Design | FUTUREWEI |
R1-2405867 | Signal Design of LP-WUS and LP-SS | Huawei, HiSilicon |
R1-2405919 | Discussion on LP-WUS and LP-SS design | Spreadtrum Communications |
R1-2405966 | Preliminary Assessment on Low-Power Wake-Up Receiver | Tejas Networks Limited |
R1-2405996 | Discussion on LP-WUS and LP-SS design | CMCC |
R1-2406083 | Discussion on LP-WUS and LP-SS Design | EURECOM |
R1-2406104 | Discussion on LP-WUS and LP-SS Design | TCL |
R1-2406193 | Discussion on LP-WUS and LP-SS design | vivo |
R1-2406222 | Signal design for LP-WUS and LP-SS | OPPO |
R1-2406295 | Discussion on LP-WUS and LP-SS design | Xiaomi |
R1-2406379 | Design of LP-WUS and LP-SS | CATT |
R1-2406412 | Discussion on LP-WUS design | ZTE Corporation, Sanechips |
R1-2406422 | LP-WUS and LP-SS design | Nokia |
R1-2406480 | LP-WUS and LP-SS design | Sony |
R1-2406498 | Discussion on LP-WUS and LP-SS design framework for Low power WUS | InterDigital, Inc. |
R1-2406504 | Discussion on LP-WUS and LP-SS design | Everactive |
R1-2406537 | Discussion on LP-WUS and LP-SS design | NEC |
R1-2406583 | Discussion on LP-WUS and LP-SS design | HONOR |
R1-2406597 | Discussions on LP-WUS and LP-SS design | Ruijie Networks Co. Ltd |
R1-2406611 | Discussion on LP-WUS and LP-SS design | LG Electronics |
R1-2406661 | Discussion on LP-WUS and LP-SS design | Samsung |
R1-2406762 | LP-WUS and LP-SS design | MediaTek Inc. |
R1-2406785 | Discussion on the LP-WUS and LP-SS design | Panasonic |
R1-2406814 | Discussion on LP-WUS and LP-SS design | Lenovo |
R1-2406850 | LP-WUS and LP-SS design | Apple |
R1-2406881 | Discussion on LP-WUS and LP-SS design | Sharp |
R1-2406941 | Discussion on LP-WUS and LP-SS design | NTT DOCOMO, INC. |
R1-2407040 | LP-WUS and LP-SS design | Qualcomm Incorporated |
R1-2407059 | LP-WUS and LP-SS design | Ericsson |
R1-2407136 | On LP-WUS and LP-SS design | Nordic Semiconductor ASA |
R1-2407287 | Summary #1 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2407356 | Summary #2 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2407420 | Summary #3 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2407491 | Summary #4 of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
R1-2407492 | Final summary of discussions on LP-WUS and LP-SS design | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R1-2405807 | Discussion on LP-WUS Operation in IDLE/INACTIVE Modes | FUTUREWEI |
R1-2405868 | Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode | Huawei, HiSilicon |
R1-2405920 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Spreadtrum Communications |
R1-2405997 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | CMCC |
R1-2406105 | Discussion on LP-WUS Operation in IDLE/INACTIVE modes | TCL |
R1-2406194 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | vivo |
R1-2406223 | Further consideration on LP-WUS operation in RRC_IDLE/INACTIVE modes | OPPO |
R1-2406296 | Discussion on LP-WUS operation in Idle/Inactive modes | Xiaomi |
R1-2406380 | System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes | CATT |
R1-2406413 | Discussion on LP-WUS operation in IDLE/INACTIVE mode | ZTE Corporation, Sanechips |
R1-2406423 | LP-WUS operation in IDLE/INACTIVE mode | Nokia |
R1-2406481 | LP-WUS operation in IDLE / INACTIVE modes | Sony |
R1-2406499 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | InterDigital, Inc. |
R1-2406519 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Fujitsu |
R1-2406538 | Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode | NEC |
R1-2406567 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | KT Corp. |
R1-2406612 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | LG Electronics |
R1-2406662 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Samsung |
R1-2406735 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | ETRI |
R1-2406763 | LP-WUS operation in IDLE INACTIVE modes | MediaTek Inc. |
R1-2406786 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Panasonic |
R1-2406815 | Discussion on LP-WUS operation in Idle/Inactive modes | Lenovo |
R1-2406851 | LP-WUS operation in IDLE/INACTIVE modes | Apple |
R1-2406853 | Summary #1 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2406854 | Summary #2 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2406855 | Summary #3 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2406882 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | Sharp |
R1-2406942 | Discussion on LP-WUS operation in IDLE/INACTIVE modes | NTT DOCOMO, INC. |
R1-2407041 | LP-WUR operation in idle and inactive modes | Qualcomm Incorporated |
R1-2407060 | LP-WUS operation in IDLE and INACTIVE modes | Ericsson |
R1-2407135 | On LP-WUS operation in IDLE/Inactive | Nordic Semiconductor ASA |
R1-2407506 | Summary #4 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2407507 | Summary #5 on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2407558 | Draft LS on LP-WUS operation in IDLE/INACTIVE mode | Moderator (Apple) |
R1-2407559 | LS on LP-WUS operation in IDLE/INACTIVE mode | RAN1, Apple |
TDoc | Title | Source |
---|---|---|
R1-2405869 | Procedures and functionalities of LP-WUS in CONNECTED mode | Huawei, HiSilicon |
R1-2405921 | Discussion on LP-WUS operation in CONNECTED modes | Spreadtrum Communications |
R1-2405998 | Discussion on LP-WUS operation in CONNECTED mode | CMCC |
R1-2406195 | Discussion on LP-WUS operation in CONNECTED modes | vivo |
R1-2406224 | Further consideration on LP-WUS operation in connected mode | OPPO |
R1-2406297 | Discussion on LP-WUS operation in Connected mode | Xiaomi |
R1-2406381 | System design and procedure of LP-WUS operation for UE in CONNECTED Modes | CATT |
R1-2406390 | Discussion on LP-WUS operation in CONNECTED mode | Panasonic |
R1-2406414 | Discussion on LP-WUS operation in CONNECTED mode | ZTE Corporation, Sanechips |
R1-2406424 | LP-WUS operation in CONNECTED mode | Nokia |
R1-2406482 | LP-WUS operation in CONNECTED mode | Sony |
R1-2406500 | Discussion on RRC CONNECTED mode LP-WUS monitoring | InterDigital, Inc. |
R1-2406510 | Discussion on LP-WUS operation in CONNECTED modes | Lenovo |
R1-2406539 | Discussion on LP-WUS operation in RRC CONNECTED mode | NEC |
R1-2406613 | Discussion on LP-WUS operation in CONNECTED modes | LG Electronics |
R1-2406663 | Discussion on LP-WUS operation in CONNECTED modes | Samsung |
R1-2406736 | Discussion on LP-WUS operation in CONNECTED modes | ETRI |
R1-2406764 | LP-WUS operation in CONNECTED modes | MediaTek Inc. |
R1-2406852 | LP-WUS operation in CONNECTED modes | Apple |
R1-2406883 | Discussion on LP-WUS operation in CONNECTED modes | Sharp |
R1-2406943 | Discussion on LP-WUS operation in CONNECTED mode | NTT DOCOMO, INC. |
R1-2407042 | LP-WUR operation in connected mode | Qualcomm Incorporated |
R1-2407061 | LP-WUS operation in CONNECTED mode | Ericsson |
R1-2407104 | Discussion on LP-WUS procedures in Connected mode | TCL |
R1-2407301 | FL summary #1 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2407378 | FL summary #2 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2407516 | FL summary #3 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
R1-2407517 | FL summary #4 on LP-WUS operation in CONNECTED mode | Moderator (NTT DOCOMO) |
TDoc | Title | Source |
---|---|---|
R1-2407480 | Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) | Ad-Hoc Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R1-2405922 | Discussion on ISAC deployment scenarios | Spreadtrum Communications |
R1-2405999 | Discussion on ISAC deployment scenarios | CMCC, China Southern Power Grid |
R1-2406009 | Deployment scenarios for ISAC channel modeling | Intel Corporation |
R1-2406047 | Discussion on ISAC deployment scenarios and requirements | EURECOM |
R1-2406067 | Discussion on deployment scenarios for ISAC | Tejas Network Limited |
R1-2406075 | Discussion on ISAC deployment scenarios | KPN N.V. |
R1-2406084 | Discussion on ISAC deployment scenarios | Tiami Networks |
R1-2406098 | Discussion on ISAC deployment scenarios | China Telecom |
R1-2406137 | Discussion on ISAC deployment scenarios | Nokia, Nokia Shanghai Bell |
R1-2406196 | Views on Rel-19 ISAC deployment scenarios | vivo |
R1-2406207 | Discussion on ISAC deployment scenarios | InterDigital, Inc. |
R1-2406249 | Discussion on ISAC deployment scenarios | OPPO |
R1-2406298 | Deployment scenarios and evaluation assumptions for ISAC channel model | Xiaomi |
R1-2406382 | Discussion on ISAC deployment scenarios | CATT, CICTCI |
R1-2406450 | Discussion on ISAC deployment scenarios | LG Electronics |
R1-2406483 | Discussion on ISAC deployment scenarios | Sony |
R1-2406488 | Deployment scenarios for integrated sensing and communication with NR | NVIDIA |
R1-2406528 | Discussion on ISAC deployment scenarios | Panasonic |
R1-2406529 | Discussion on deployment scenarios for ISAC | KRRI, Hanbat National University |
R1-2406664 | Discussion on ISAC deployment scenarios | Samsung |
R1-2406715 | Discussion on ISAC deployment scenarios | Lenovo |
R1-2406767 | Discussion on ISAC deployment scenario | MediaTek Inc. |
R1-2406792 | Discussion on ISAC deployment scenarios | TOYOTA InfoTechnology Center |
R1-2406856 | Discussion on ISAC deployment scenarios | Apple |
R1-2406867 | Deployment Scenarios for ISAC Channel Modeling | AT&T, FirstNet |
R1-2406873 | FL Summary #1 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2406874 | FL Summary #2 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2406875 | FL Summary #3 on ISAC Deployment Scenarios | Moderator (AT&T) |
R1-2406896 | Considerations on ISCA deployment scenarios | CAICT |
R1-2406905 | Discussion on ISAC Deployment Scenarios | Ericsson |
R1-2406944 | Study on deployment scenarios for ISAC channel modelling | NTT DOCOMO, INC. |
R1-2406959 | Discussion on ISAC deployment scenarios | ZTE Corporation, Sanechips |
R1-2406974 | Deployment scenarios for ISAC channel model | Huawei, HiSilicon |
R1-2407043 | Discussion on ISAC deployment scenarios | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R1-2405923 | Discussion on ISAC channel modeling | Spreadtrum Communications |
R1-2405946 | FR2 Channel Measurements for ISAC | ROHDE & SCHWARZ, Fraunhofer |
R1-2406000 | Discussion on channel modeling methodology for ISAC | CMCC,BUPT,SEU, PML |
R1-2406010 | Discussion on ISAC channel modeling | Intel Corporation |
R1-2406048 | Discussion on ISAC channel modeling | EURECOM |
R1-2406066 | Discussion on ISAC channel modelling | Tejas Network Limited |
R1-2406085 | Discussion on ISAC Channel Modeling | Tiami Networks |
R1-2406099 | Discussion on ISAC channel modelling | China Telecom |
R1-2406107 | ISAC Channel Measurements and Modeling | BUPT, CMCC, VIVO |
R1-2406138 | Discussion on ISAC channel modelling | Nokia, Nokia Shanghai Bell |
R1-2406197 | Views on Rel-19 ISAC channel modelling | vivo,BUPT |
R1-2406208 | Discussion on ISAC channel modeling | InterDigital, Inc. |
R1-2406211 | Measurement-Based EO Study and Multi-Dimensional Target Modeling | NIST |
R1-2406212 | Measurement-Based EO Study and Multi-Dimensional Target Modeling | NIST |
R1-2406250 | Study on ISAC channel modelling | OPPO |
R1-2406299 | Summary #1 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2406300 | Summary #2 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2406301 | Summary #3 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2406302 | Summary #4 on ISAC channel modelling | Moderator (Xiaomi) |
R1-2406383 | Discussion on ISAC channel modelling | CATT, CICTCI |
R1-2406451 | Discussion on ISAC channel modelling | LG Electronics |
R1-2406484 | Discussion on Channel Modelling for ISAC | Sony |
R1-2406489 | Channel modeling for integrated sensing and communication with NR | NVIDIA |
R1-2406530 | Discussion on channel modelling for ISAC | KRRI, Hanbat National University |
R1-2406665 | Discussion on ISAC channel modelling | Samsung |
R1-2406698 | Channel modeling methodology updates for ISAC | Keysight Technologies UK Ltd |
R1-2406710 | Discussion on ISAC channel model | Xiaomi, BJTU |
R1-2406713 | Discussion on ISAC Channel Modelling | Panasonic |
R1-2406714 | Discussion on Channel Modelling for ISAC | Lenovo |
R1-2406768 | Discussion on ISAC channel modelling | MediaTek Inc. |
R1-2406793 | Discussion on ISAC channel modelling | TOYOTA InfoTechnology Center |
R1-2406799 | General Requirements for Automotive ISAC | DENSO CORPORATION |
R1-2406857 | Discussion on ISAC channel modelling | Apple |
R1-2406868 | Discussions on ISAC Channel Modeling | AT&T |
R1-2406897 | Considerations on ISAC channel modelling | CAICT |
R1-2406906 | Discussion on ISAC Channel Modelling | Ericsson |
R1-2406945 | Discussion on ISAC channel modeling | NTT DOCOMO, INC. |
R1-2406960 | Discussion on channel modelling for ISAC | ZTE Corporation, Sanechips |
R1-2406975 | Channel modelling for ISAC | Huawei, HiSilicon |
R1-2407044 | Discussion on ISAC channel modelling | Qualcomm Incorporated |
R1-2407092 | Discussion on ISAC Channel Modelling | CEWiT |
R1-2407200 | Study on ISAC channel modelling | OPPO |
R1-2407211 | Views on Rel-19 ISAC channel modelling | vivo, BUPT |
TDoc | Title | Source |
---|---|---|
R1-2407251 | Data source descriptions for 7 – 24 GHz SI | Moderator (Intel Corporation) |
R1-2407481 | Session notes for 9.8 (Study on channel modelling enhancements for 7-24GHz for NR) | Ad-Hoc Chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R1-2405865 | Considerations on the 7-24GHz channel model validation | Huawei, HiSilicon |
R1-2405884 | On Angle Scaling for MIMO CDL Channel | InterDigital, Inc. |
R1-2405895 | Channel Model Validation of TR 38.901 for 7-24 GHz | Sharp |
R1-2406007 | Discussion on channel modeling verification for 7-24 GHz | Intel Corporation |
R1-2406128 | Discussion on the channel model validation | ZTE Corporation, Sanechips |
R1-2406139 | Discussion on Channel model validation of TR38.901 for 7-24GHz | Nokia |
R1-2406198 | Views on channel model validation of TR38.901 for 7-24GHz | vivo |
R1-2406252 | Discussion on channel model validation for 7~24GHz | OPPO |
R1-2406384 | Views on channel model validation of TR38.901 for 7-24GHz | CATT |
R1-2406393 | New measurement results for TR38.901 channel model validation and adaptation/extension consideration | Keysight Technologies UK Ltd |
R1-2406485 | Further discussion on channel model validation of TR38.901 for 7-24 GHz | Sony |
R1-2406490 | Channel model validation of TR 38901 for 7-24 GHz | NVIDIA |
R1-2406666 | Discussion on channel model validation of TR38.901 for 7 - 24 GHz | Samsung |
R1-2406717 | Discussion on validation of channel model | Ericsson |
R1-2406744 | Discussion on channel model validation of TR38.901 for 7-24GHz | BUPT, Spark NZ Ltd |
R1-2406858 | Discussion on validation of channel model | Apple |
R1-2406869 | Discussion on Validation of the Channel Model in 38901 | AT&T |
R1-2406946 | Discussion on channel model validation for 7-24 GHz | NTT DOCOMO, INC. |
R1-2407045 | Channel Model Validation of TR38.901 for 7-24 GHz | Qualcomm Incorporated |
R1-2407106 | Measurements of the angular spread in a suburban macrocell | Vodafone, Ericsson |
R1-2407252 | Summary of issues for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2407253 | Summary #1 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2407254 | Summary #2 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2407255 | Summary #3 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2407467 | Summary #4 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
R1-2407494 | Summary #5 of discussions for Rel-19 7-24 GHz Channel Modeling Validation | Moderator (Intel Corporation) |
TDoc | Title | Source |
---|---|---|
R1-2405866 | Considerations on the 7-24GHz channel model extension | Huawei, HiSilicon |
R1-2405885 | On Channel Model Extension for FR3 | InterDigital, Inc. |
R1-2406008 | Discussion on channel model adaptation/extension | Intel Corporation |
R1-2406062 | Discussion on channel modelling adaptation/extension for 7-24GHz | LG Electronics |
R1-2406129 | Discussion on the channel model adaptation and extension | ZTE Corporation, Sanechips |
R1-2406140 | Discussion on Channel model adaptation/extension of TR38.901 for 7-24GHz | Nokia |
R1-2406199 | Views on channel model adaptation/extension of TR38.901 for 7-24GHz | vivo |
R1-2406253 | Discussion on channel model adaptation and extension | OPPO |
R1-2406385 | Views on channel model adaptation/extension of TR38.901 for 7-24GHz | CATT |
R1-2406491 | Channel model adaptation of TR 38901 for 7-24 GHz | NVIDIA |
R1-2406518 | Discussion on channel model adaptation/extension for 7-24 GHz | Fujitsu |
R1-2406667 | Discussion on channel model adaptation/extension of TR38.901 for 7 - 24 GHz | Samsung |
R1-2406742 | Discussion on adaptation and extension of channel model | Ericsson |
R1-2406743 | Discussion on near-field propagation and spatial non-stationarity | BUPT, CMCC |
R1-2406766 | Discussion on channel modelling enhancements for 7-24GHz for NR | MediaTek Inc. |
R1-2406859 | Channel Model Adaptation and Extension of TR38.901 for 7-24 GHz | Apple |
R1-2407046 | Channel Model Adaptation/Extension of TR38.901 for 7-24GHz | Qualcomm Incorporated |
R1-2407073 | Channel model adaptation/extension of TR38.901 for 7-24 GHz | CEWiT |
R1-2407201 | Discussion on channel model adaptation/extension | Intel Corporation |
R1-2407290 | Summary#1 of channel model adaptation and extension | Moderator (ZTE) |
R1-2407291 | Summary#2 of channel model adaptation and extension | Moderator (ZTE) |
R1-2407292 | Summary#3 of channel model adaptation and extension | Moderator (ZTE) |
R1-2407293 | Summary#4 of channel model adaptation and extension | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R1-2406860 | Work plan for Rel-19 Further NR Mobility Enhancements | Apple, China Telecom |
TDoc | Title | Source |
---|---|---|
R1-2405859 | Measurements related enhancements for LTM | Huawei, HiSilicon |
R1-2405924 | Discussion on measurements related enhancements for LTM | Spreadtrum Communications |
R1-2406001 | Discussion on measurements related enhancements for LTM | CMCC |
R1-2406032 | Discussion on measurements related enhancements for LTM | ZTE Corporation, Sanechips |
R1-2406063 | Discussion on measurements related enhancements for LTM | LG Electronics |
R1-2406200 | Views on measurements related enhancements for LTM | vivo |
R1-2406264 | Discussions on measurement enhancement for LTM | OPPO |
R1-2406303 | Measurements related enhancements for LTM | Xiaomi |
R1-2406386 | Discussion on measurements related enhancements for LTM | CATT |
R1-2406432 | Measurements enhancements for LTM | TCL |
R1-2406458 | Measurements related enhancements for LTM | InterDigital, Inc. |
R1-2406486 | Measurements related enhancements for LTM | Sony |
R1-2406525 | Measurements related enhancements for LTM | Lenovo |
R1-2406527 | Discussion on measurements related enhancements for LTM | Fujitsu |
R1-2406668 | Views on Rel-19 measurement related enhancements for LTM | Samsung |
R1-2406697 | Discussion on measurements related enhancements for LTM | NEC |
R1-2406737 | Discussion on NR mobility enhancement based on CSI-RS measurements | ETRI |
R1-2406769 | LTM measurements related enhancements | MediaTek Inc. |
R1-2406791 | Measurement related enhancements for LTM | Nokia |
R1-2406861 | Measurements enhancements for LTM | Apple |
R1-2406947 | Discussion on measurement related enhancements for LTM | NTT DOCOMO, INC. |
R1-2406966 | Discussion on measurement related enhancements for LTM | KDDI Corporation |
R1-2407047 | Measurement related enhancement for LTM | Qualcomm Incorporated |
R1-2407053 | Discussion on measurements related enhancements for LTM | Sharp |
R1-2407115 | Discussion on measurements related enhancements for LTM | |
R1-2407146 | Measurement related enhancements for LTM | Ericsson |
R1-2407318 | FL summary 1 of Measurements related enhancements for LTM | Moderator (Fujitsu) |
R1-2407319 | FL summary 2 of Measurements related enhancements for LTM | Moderator (Fujitsu) |
R1-2407445 | Final FL summary of Measurements related enhancements for LTM | Moderator (Fujitsu) |
TDoc | Title | Source |
---|---|---|
R1-2405843 | Discussions on scheduling enhancements considering RRM measurements for XR | Huawei, HiSilicon |
R1-2405886 | Enhancements to enable TX/RX for XR during RRM measurements | Fraunhofer IIS, Fraunhofer HHI |
R1-2405929 | Discussion on enabling TX/RX for XR during RRM measurements | Spreadtrum Communications |
R1-2406002 | Discussion on enabling TX/RX for XR during RRM measurements | CMCC |
R1-2406065 | Enabling TX/RX for XR during RRM measurements | Nokia |
R1-2406081 | Enabling TX/RX for XR during RRM measurements | Lenovo |
R1-2406201 | Discussion on enabling data transmissions for XR during RRM measurements | vivo |
R1-2406248 | Enhancements to enable TX/RX for XR during RRM measurements | OPPO |
R1-2406274 | Discussion on enabling TX/RX for XR during RRM measurements | Xiaomi |
R1-2406304 | Discussion on Enabling TX/RX for XR During RRM Measurements | Meta |
R1-2406358 | Signaling control of scheduling restriction during measurement gap in support of XR services | CATT |
R1-2406415 | Discussion on measurement gap for XR | ZTE Corporation, Sanechips |
R1-2406428 | Discussion on enabling TX/RX for XR during RRM measurements | Panasonic |
R1-2406487 | Discussion on enabling TX/RX for XR during RRM measurements | Sony |
R1-2406506 | Discussion on enabling TX/RX for XR during RRM measurements | InterDigital, Inc. |
R1-2406540 | Discussion on enabling TX/RX for XR during RRM measurements | NEC |
R1-2406614 | Discussion on XR during RRM measurements | LG Electronics |
R1-2406669 | Discussion on enabling TX/RX for XR during RRM measurements | Samsung |
R1-2406770 | Enabling TX RX for XR during RRM measurements | MediaTek Inc. |
R1-2406787 | On enabling Tx/Rx for XR during RRM measurements | Google Ireland Limited |
R1-2406862 | Views on Enabling TX/RX for XR during RRM measurements | Apple |
R1-2406899 | Enabling TX/RX for XR during RRM measurements | TCL |
R1-2406948 | Discussion on Enabling TX/RX for XR during RRM | NTT DOCOMO, INC. |
R1-2407048 | Enabling Tx/Rx for XR during RRM measurements | Qualcomm Incorporated |
R1-2407155 | Discussion on TX/RX for XR during RRM measurements | CAICT |
R1-2407162 | RRM measurement gap and scheduling restriction enhancements to TX/RX XR traffic | Ericsson |
R1-2407288 | Moderator summary #1 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2407289 | Moderator summary #2 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2407511 | Moderator summary #3 - Enabling TX/RX for XR during RRM measurements | Moderator (Nokia) |
R1-2407512 | Draft LS on gaps/restrictions that are caused by RRM measurements | Nokia |
R1-2407561 | LS on gaps/restrictions that are caused by RRM measurements | RAN1, Nokia |
TDoc | Title | Source |
---|---|---|
R1-2406439 | Work plan for Rel-19 NR_NTN_Ph3 | THALES |
R1-2407384 | Summary for Reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Moderator (ZTE) |
R1-2407482 | Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3) | Ad-Hoc Chair (Huawei) |
R1-2407521 | Summary #2 for Reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Moderator (ZTE) |
R1-2407546 | Draft Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Moderator (ZTE) |
R1-2407548 | Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | RAN1, ZTE |
TDoc | Title | Source |
---|---|---|
R1-2405834 | On NR-NTN downlink coverage enhancement | Ericsson |
R1-2405838 | Discussion on downlink coverage enhancements for NR NTN | Huawei, HiSilicon |
R1-2405891 | Discussions on downlink coverage enhancements for NR NTN | Fraunhofer IIS, Fraunhofer HHI |
R1-2405925 | Discussion on NR-NTN downlink coverage enhancement | Spreadtrum Communications |
R1-2406003 | Discussion on NR-NTN DL coverage enhancement | CMCC |
R1-2406052 | Discussion on DL coverage enhancements for NR-NTN | NICT |
R1-2406108 | NR-NTN downlink coverage enhancement | InterDigital, Inc. |
R1-2406130 | Discussion on DL coverage enhancement for NR NTN | ZTE Corporation, Sanechips |
R1-2406202 | Discussion on NR-NTN downlink coverage enhancement | vivo |
R1-2406229 | Discussion on NR-NTN downlink coverage enhancement | OPPO |
R1-2406275 | Discussion on NR-NTN downlink coverage enhancement | Xiaomi |
R1-2406359 | Further consideration on downlink coverage enhancement for NR NTN | CATT |
R1-2406434 | Discussion on NR NTN Downlink coverage enhancements | THALES |
R1-2406435 | FL Summary #1: NR-NTN downlink coverage enhancements | Moderator (THALES) |
R1-2406436 | FL Summary #2: NR-NTN downlink coverage enhancements | Moderator (THALES) |
R1-2406437 | FL Summary #3: NR-NTN downlink coverage enhancements | Moderator (THALES) |
R1-2406438 | FL Summary #4: NR-NTN downlink coverage enhancements | Moderator (THALES) |
R1-2406446 | Discussion on NR-NTN downlink coverage enhancement | LG Electronics |
R1-2406452 | Discussion on NR NTN Downlink Coverage Enhancements | IIT, Kharagpur |
R1-2406511 | Discussion on downlink coverage enhancement for NR NTN | Lenovo |
R1-2406554 | NR-NTN downlink coverage enhancement | NEC |
R1-2406572 | NR-NTN downlink coverage enhancement with beam groups | Sharp |
R1-2406584 | Discussion on NR-NTN downlink coverage enhancement | HONOR |
R1-2406592 | Discussion on downlink coverage enhancement for NR NTN | Baicells |
R1-2406615 | NR-NTN Downlink Coverage Enhancement | Panasonic |
R1-2406670 | Discussion on downlink coverage enhancement for NR-NTN | Samsung |
R1-2406738 | Discussion on NR-NTN downlink coverage enhancement | ETRI |
R1-2406754 | Downlink coverage enhancements for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2406777 | NR-NTN - downlink coverage enhancement | MediaTek Inc. |
R1-2406863 | On NR-NTN Downlink Coverage Enhancement | Apple |
R1-2406885 | Discussion on NR-NTN DL coverage enhancement | KT Corp. |
R1-2406900 | Discussion on NR-NTN downlink coverage enhancement | TCL |
R1-2406949 | Discussion on DL coverage enhancement for NR-NTN | NTT DOCOMO, INC. |
R1-2406965 | Downlink Coverage Enhancement for NR NTN | Google Ireland Limited |
R1-2407049 | Downlink coverage enhancement for NR NTN | Qualcomm Incorporated |
R1-2407078 | Downlink Coverage Enhancements for NR NTN | CEWiT |
R1-2407079 | Discussion on NR NTN Downlink Coverage Enhancements | CEWiT |
R1-2407118 | Discussion on downlink coverage enhancement for NR-NTN | CSCN |
R1-2407132 | Operator input to NTN DL Coverage Enhancements | Inmarsat, Viasat |
R1-2407455 | Draft Reply LS on DL coverage enhancements | CMCC |
R1-2407456 | Moderator’s summary on the discussion of the reply LS on DL coverage enhancements | Moderator (CMCC) |
R1-2407538 | Reply LS on DL coverage enhancements | RAN1, CMCC |
TDoc | Title | Source |
---|---|---|
R1-2405839 | Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN | Huawei, HiSilicon |
R1-2405926 | Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Spreadtrum Communications |
R1-2406004 | Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN | CMCC |
R1-2406100 | Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | China Telecom |
R1-2406109 | Discussion on half-duplex RedCap issues for NTN FR1 operation | InterDigital, Inc. |
R1-2406131 | Discussion on support of RedCap/eRedCap UEs for NR NTN | ZTE Corporation, Sanechips |
R1-2406203 | Discussion on support of RedCap and eRedCap UEs with NR-NTN | vivo |
R1-2406230 | Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | OPPO |
R1-2406276 | Discussion on the support of Redcap UE in NR NTN | Xiaomi |
R1-2406360 | Discussion on the enhancement of RedCap and eRedCap UEs In NTN | CATT |
R1-2406447 | Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands | LG Electronics |
R1-2406585 | Discussion on support of RedCap/eRedCap UEs in NR NTN | HONOR |
R1-2406671 | Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Samsung |
R1-2406739 | Discussion on HD UEs with NR NTN | ETRI |
R1-2406755 | Considerations on (e)RedCap operation in NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2406778 | NR-NTN - Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | MediaTek Inc. |
R1-2406808 | On HD-FDD Redcap UEs for NTN | Ericsson |
R1-2406864 | On support of RedCap UEs with NR NTN operation | Apple |
R1-2406898 | Discussion on support of RedCap/eRedCap UEs in NTN | CAICT |
R1-2406901 | Discussion on HD-FDD Redcap UEs and eRedcap UEs for FR1-NTN | TCL |
R1-2406950 | Discussion on support of RedCap and eRedCap UEs in FR1-NTN | NTT DOCOMO, INC. |
R1-2407050 | Support of Redcap and eRedcap UEs in NR NTN | Qualcomm Incorporated |
R1-2407140 | Views on RedCap for NR-NTN | Inmarsat, Viasat |
R1-2407306 | Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
R1-2407307 | Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
R1-2407498 | Final Summary for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R1-2405840 | Discussion on uplink capacity/throughput enhancement for FR1-NTN | Huawei, HiSilicon |
R1-2405927 | Discussion on NR-NTN uplink capacity/throughput enhancement | Spreadtrum Communications |
R1-2406005 | Discussion on the NR-NTN uplink capacity/throughput enhancements | CMCC |
R1-2406053 | Discussion on NR-NTN uplink capacity/throughput enhancement | NICT |
R1-2406076 | Discussion on the NR-NTN uplink capacity/throughput enhancements | TCL |
R1-2406079 | Discussion on the NR-NTN uplink capacity/throughput enhancements | TCL |
R1-2406080 | Discussion on the NR-NTN uplink capacity/throughput enhancements | TCL |
R1-2406101 | Discussion on NR-NTN uplink enhancement | China Telecom |
R1-2406110 | NR-NTN uplink capacity/throughput enhancement | InterDigital, Inc. |
R1-2406123 | On uplink capacity/cell throughput enhancement for NR NTN | Ericsson |
R1-2406132 | Discussion on UL capacity enhancement for NR NTN | ZTE Corporation, Sanechips |
R1-2406204 | Discussion on NR-NTN uplink capacity enhancement | vivo |
R1-2406231 | Discussion on NR-NTN uplink capacity/throughput enhancement | OPPO |
R1-2406277 | Discussion on NR-NTN PUSCH capacity enhancement | Xiaomi |
R1-2406361 | Discussion on UL capacity enhancement for NR NTN | CATT |
R1-2406448 | Discussion on NR-NTN uplink capacity/throughput enhancement | LG Electronics |
R1-2406513 | Discussion on Uplink Capacity/Cell Throughput Enhancement for FR1-NTN | Fujitsu |
R1-2406555 | NR-NTN uplink capacity/throughput enhancement | NEC |
R1-2406591 | Uplink capacity/throughput enhancement for NR-NTN | Panasonic |
R1-2406672 | Discussion on uplink capacity/throughput enhancement for NR-NTN | Samsung |
R1-2406740 | Discussion on NR-NTN uplink capacity/throughput enhancement | ETRI |
R1-2406756 | Uplink capacity enhancement considerations for NR over NTN | Nokia, Nokia Shanghai Bell |
R1-2406757 | Discussion on uplink capacity/throughput enhancement for NR-NTN | Lenovo |
R1-2406779 | NR-NTN - uplink capacity/throughput enhancement | MediaTek Inc. |
R1-2406802 | NR-NTN uplink capacity enhancement | Sharp |
R1-2406865 | On NR-NTN Uplink Capacity Enhancement | Apple |
R1-2406951 | Discussion on NR-NTN uplink capacity/throughput enhancement | NTT DOCOMO, INC. |
R1-2406967 | Uplink Capacity Enhancement for NR NTN | Google Ireland Limited |
R1-2407051 | NR-NTN uplink capacity / throughput enhancement | Qualcomm Incorporated |
R1-2407139 | Views on UL Capacity Enhancements for NR-NTN | Inmarsat, Viasat |
R1-2407206 | Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements | Moderator (MediaTek) |
R1-2407207 | Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements | Moderator (MediaTek) |
R1-2407208 | Feature lead summary #3 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements | Moderator (MediaTek) |
R1-2407222 | Discussion on NR-NTN uplink capacity/throughput enhancement | NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R1-2405842 | Discussion on UL capacity enhancements for IoT NTN | Huawei, HiSilicon |
R1-2405928 | Discussion on IoT-NTN uplink capacity/throughput enhancement | Spreadtrum Communications |
R1-2406006 | Discussion on the IoT -NTN uplink capacity/throughput enhancements | CMCC |
R1-2406077 | Discussion on the IoT-NTN uplink capacity/throughput enhancements | TCL |
R1-2406078 | Discussion on the IoT-NTN uplink capacity/throughput enhancements | TCL |
R1-2406111 | IoT-NTN uplink capacity/throughput enhancement | InterDigital, Inc. |
R1-2406133 | Discussion on UL capacity enhancement for IoT NTN | ZTE Corporation, Sanechips |
R1-2406205 | Discussion on IoT-NTN uplink capacity enhancement | vivo |
R1-2406232 | Discussion on IoT-NTN uplink capacity/throughput enhancement | OPPO |
R1-2406278 | Discussion on IoT-NTN uplink capacity enhancement | Xiaomi |
R1-2406362 | Discussion on UL capacity enhancement for IoT NTN | CATT |
R1-2406427 | IoT-NTN uplink capacity enhancement | Nokia, Nokia Shanghai Bell |
R1-2406449 | Discussion on IoT-NTN uplink capacity/throughput enhancement | LG Electronics |
R1-2406512 | Discussion on uplink capacity enhancement for IoT NTN | Lenovo |
R1-2406556 | IoT-NTN uplink capacity/throughput enhancement | NEC |
R1-2406573 | IoT NTN OCC methods for NPUSCH and NPRACH | Sharp |
R1-2406673 | Discussion on uplink capacity/throughput enhancement for IoT-NTN | Samsung |
R1-2406741 | Discussion on uplink capacity/throughput enhancement for IoT NTN | ETRI |
R1-2406780 | IoT-NTN - uplink capacity/throughput enhancemen | MediaTek Inc. |
R1-2406809 | On uplink capacity enhancements for IoT-NTN | Ericsson |
R1-2406866 | On IoT-NTN Uplink Capacity Enhancement | Apple |
R1-2407052 | IOT-NTN uplink capacity/throughput enhancement | Qualcomm Incorporated |
R1-2407138 | Views on UL Capacity Enh for IoT-NTN | Inmarsat, Viasat |
R1-2407296 | FL Summary #1 for IoT-NTN | Moderator (Sony) |
R1-2407297 | FL Summary #2 for IoT-NTN | Moderator (Sony) |
R1-2407563 | Final FL summary for IoT-NTN | Moderator (Sony) |