Samsung · 8.1

Samsung argues that the current restriction requiring all resources in Set A to share the same periodicity is too restrictive and proposes relaxing this constraint to allow mixed periodicities. They contend that PDSCH rate-matching around virtual CSI-RS in Set A causes unnecessary resource waste and propose clarifying that such resources should not trigger rate-matching. Regarding PUCCH reporting, Samsung prefers zero-padding over configuration restrictions for RS-PAI payloads smaller than 3 bits, stating this approach aligns with NR design principles. They assert that restricting bullet A and B is acceptable given the limited size of Set A (up to 64 resources) and maximum NZP CSI-RS resource ID (192), but insist on relaxing bullet C to allow more flexible resource ID selection.

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 allowing mixed time domain behaviors and excluding Set A-only CSI-RS from PDSCH rate-matching to improve spectral efficiency. Samsung endorses correcting the CPU occupation time definitions for UE-side data collection to accurately reflect periodic CSI report support. They also support clarifying the determination of updated AI/ML CSI reports based on CPU/APU availability to ensure correct prioritization and timeline adherence.

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 restriction for Set A resources to allow different time domain behaviors, enhancing flexibility for AI/ML inference configurations. Samsung requires clarification that CSI-RS resources configured only in Set A are not used for PDSCH rate-matching, thereby preventing unnecessary resource waste. They also support correcting the CPU occupation timeline for UE-side data collection to accurately include periodic CSI reports for beam management. Furthermore, Samsung argues for clarifying the determination of updated AI/ML CSI reports based on CPU and APU availability to ensure higher-priority reports are processed correctly.

Samsung, NEC, and LG propose a correction to TS 38.212 to resolve an unsupported payload size issue for AI/ML beam management. They identify that for P/SP CSI reporting on PUCCH for performance monitoring, the RS-PAI information bit count may fall below 3 bits. Since NR specifications do not support PUCCH carrying 1 or 2 information bits for CSI (excluding HARQ-ACK/SR), they require that the number of information bits of the related CSI be zero-padded to 3 bits. This ensures compatibility with existing PUCCH format constraints while enabling the transmission of AI/ML-related CSI reports.

Samsung, as moderator, proposes a correction to TS 38.214 Section 5.2.1.6 to accurately reflect RAN1 agreements on CPU processing criteria for AI/ML beam management. They require the inclusion of periodic CSI reports for UE-side data collection, which are currently missing from the specification. They define specific CPU occupation windows for semi-persistent, aperiodic, and 'none-csi-r19' report quantities based on CSI-RS/SSB resource symbols and PDCCH triggering. They argue that without this change, UE behavior for CPU duration during data collection for training would be incorrect.