R1-2603260
discussion
FL summary #0 for AI/ML in beam management
From Samsung
Summary
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 main technical areas, aiming to resolve specification ambiguities regarding payload sizing, resource rate-matching, and CPU/APU occupation rules.
Position
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.
Key proposals
- Proposal 2.1.1 (Sec 2.1): Adopt zero-padding for RS-PAI payloads on PUCCH to 3 bits when the configured number of transmission occasions results in 1 or 2 bits, ensuring compatibility with NR PUCCH constraints.
- Proposal 1 (Sec 2.1, NEC): Define that a monitoring report shall be dropped if its linked inference report is not activated, preventing invalid RS-PAI reporting.
- Proposal 2.2.1-A (Sec 2.2): Clarify that CSI-RS resources configured only in Set A (for inference) are not used for PDSCH rate-matching, allowing these resources to be reused for data transmission.
- Proposal 2.2.1-B (Sec 2.2): Specify that NZP CSI-RS resources in Set A are not rate-matched when CSI-ResourcePeriodicityAndOffset is absent, enabling resource utilization during non-transmission occasions.
- Proposal 1 (Sec 2.2, Samsung): Relax the configuration restriction requiring all resources in Set A to have the same time domain behavior, allowing mixed periodicity/semi-persistent configurations.
- Proposal 3 (Sec 2.2, NEC): Define UE behavior to transmit a CSI report with an invalid value if the applicability status of the corresponding CSI-ReportConfig changes from applicable to inapplicable.
- Proposal 2.3.1 (Sec 2.3): Correct the CPU occupation time definition for UE-side data collection for beam management to include periodic CSI reports, aligning with RAN1 agreements.
- Proposal 2 (Sec 2.3, Sharp): Clarify that the maximum value Z and Z’ among M updated CSI reports and Mx updated CSI reports are used to determine time locations Zref and Z’ref, ensuring AI/ML reports are considered in timeline calculations.
- Proposal 3 (Sec 2.3, Sharp): Clarify the determination of updated AI/ML CSI reports based on CPU and APU availability, ensuring higher-priority reports are not skipped due to lower-priority report updates.
- Proposal 4 (Sec 2.3, Sharp): Specify the CSI computation time for model monitoring CSI reports (RS-PAI) to resolve undefined processing timelines.
- Proposal 2.1.1 (Sec 3): Reiterate the adoption of zero-padding for 1-bit or 2-bit RS-PAI payloads on PUCCH for online decision.
- Proposal 2.2.1-A (Sec 3): Reiterate the proposal to exclude Set A-only CSI-RS from PDSCH rate-matching for online decision.
- Proposal 2.2.1-B (Sec 3): Reiterate the proposal regarding rate-matching exemption for Set A resources without periodicity configuration for online decision.
- Proposal 2.3.1 (Sec 3): Reiterate the correction of CPU occupation time for data collection for online decision.