Search

Search the 3GPP archive

3 results · status: noted
R1-2603260 Samsung NR_AIML_air discussion noted
FL summary #0 for AI/ML in beam management
This document summarizes the remaining issues for UE-side AI/ML models in beam management, specifically focusing on CSI reporting for performance monitoring, model inference, and processing timelines. It presents approximately 15 distinct proposals and observations across three…
Samsung proposes adopting zero-padding for RS-PAI payloads on PUCCH to resolve the incompatibility of 1-bit or 2-bit payloads with NR specifications. They support relaxing configuration restrictions for Set A resources, specifically…
R1-2603261 Samsung NR_AIML_air discussion noted
FL summary #1 for AI/ML in beam management
This document summarizes the remaining issues and proposals for AI/ML-based beam management in NR Rel-19, specifically focusing on UE-side model performance monitoring, inference reporting, and processing timelines. It addresses critical specification gaps regarding PUCCH…
Samsung supports the majority view on zero-padding RS-PAI payloads to 3 bits for PUCCH transmission, arguing that padding after CSI multiplexing reduces overhead compared to per-report padding. They propose relaxing the configuration…
R1-2603328 AT&T NR_AIML_air discussion noted
Summary for LS R1-2601764 on capability reporting for PRS Processing Window
This document summarizes the RAN1 discussion regarding LS R1-2601764 on capability reporting for PRS Processing Window (PPW) in the context of AI/ML-based positioning. It captures divergent views from vendors on whether capabilities 58-2-9, 58-2-10, and 58-2-11 should be…
AT&T, acting as the moderator, presents FL Proposal 4-1 stating that FG 58-2-9, 58-2-10, and 58-2-11 should not be reported to the gNB. This position aligns with the architectural principle cited by Huawei and Qualcomm that the gNB should…