R1-2602836
discussion
Remaining Issues of Rel-19 AIML
From Ericsson
Summary
This Ericsson contribution addresses remaining specification issues for Rel-19 AI/ML beam management, specifically focusing on the reporting of the RS-Prediction Accuracy Indicator (RS-PAI) on PUCCH. It identifies a conflict where certain configurations result in 1-bit or 2-bit RS-PAI payloads, which are unsupported by current NR specifications for PUCCH. The document presents one primary proposal to resolve this by applying zero-padding to ensure the payload meets the minimum bit requirement.
Position
Ericsson supports zero-padding the RS-PAI to 3 bits when nroftransmissionOccasion-r19 results in 1-bit or 2-bit payloads, ensuring compliance with PUCCH constraints that prohibit 1 or 2 information bits apart from HARQ-ACK/SR. They oppose restricting the network configuration by prohibiting nroftransmissionOccasion-r19 values of 1 or 3, arguing that such restrictions would hinder the network's ability to detect inaccuracies in specific monitoring occasions. They argue that limiting the network to supporting at least seven occasions reduces visibility into error instances, whereas zero-padding preserves the network's functionality for performance metric calculation. They present a technical case that equivalent information can be obtained via UE-reported measurements on Set A beams, but emphasize that if RS-PAI is used, the zero-padding solution is preferred to maintain granular monitoring capabilities.
Key proposals
- Proposal 1 (Sec Conclusion): Support zero-padding the RS-PAI to 3 bits if nroftransmissionOccasion-r19 is a value of 1 or 3 to avoid unsupported 1-bit or 2-bit reporting scenarios on PUCCH.