R1-2601986
discussion
Maintenance on AI/ML for NR air interface
From vivo
Summary
This document from vivo addresses remaining issues for AI/ML-based beam management in NR Release 19, specifically focusing on PDSCH rate-matching and PUCCH reporting configurations. It contains two technical proposals: one to exclude virtual CSI-RS in Set A from PDSCH rate-matching to save resources, and another to restrict RS-PAI reporting configurations on PUCCH to avoid unsupported small payload sizes.
Position
vivo proposes clarifying TS 38.211 to exclude virtual CSI-RS resources configured only in Set A from PDSCH rate-matching, arguing that these resources are for inference only and do not require measurement, thus preventing resource waste. They require restricting the configuration of nroftransmissionOccasion-r19 for periodic and semi-persistent CSI reporting on PUCCH, specifically prohibiting values of 1 or 3. This restriction is mandated because NR specifications do not support PUCCH carrying 1 or 2 information bits for RS-PAI reporting, and allowing such configurations would lead to unspecified UE and base station behaviors.
Key proposals
- Proposal 1 (Sec Remaining issues for AI based beam management): Adopt TP for TS 38.211 Clause 7.3.1.5 to clarify that CSI-RS only configured in Set A is not used to perform PDSCH rate-matching, preventing unnecessary resource waste.
- Proposal 2 (Sec Remaining issues for AI based beam management): Adopt TP for TS 38.214 Clause 5.2.1.4.3b to clarify that when a UE is configured with P-CSI or SP-CSI on PUCCH for RS-PAI reporting, the value M provided by nroftransmissionOccasion-r19 shall not be set to 1 or 3, avoiding unspecified behavior for 1 or 2 bit payloads.