Ericsson · 8.1

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.

Ericsson, as the Ad-Hoc Chair, facilitates the endorsement of specification corrections for Rel-19 AI/ML features. They support zero-padding UCI bit sequences to 3 bits in TS 38.212 to ensure PUCCH compatibility when RS-PAI payload is small. They endorse updating TS 38.214 Clause 5.2.1.6 to include periodic CSI reports for UE-side data collection in CPU duration calculations. They confirm that for UE-sided models, data collection resources are restricted to always-on SSB and P/SP CSI-RS. They agree to reuse existing CPU occupation time definitions for CSI-ReportConfig with reportQuantity 'none' and no TRS-info. They note the absence of consensus on PDSCH rate matching around NZP CSI-RS in Set A for inference.