Kyocera · 9.1.1

Kyocera proposes distinct configuration strategies for UE-side and NW-side AI/ML models, specifically requiring Set B to be explicitly configured for UE measurements while allowing Set A to be virtually configured for reference mapping. They argue against reporting full beam indices for NW-side models when M equals the resource set size, proposing instead to report only the index of the strongest beam to reduce overhead. Regarding consistency, Kyocera requires that beam properties, set sizes, and resource indexing remain consistent between training and inference phases for the same associated ID, and prioritizes defining these UE assumptions before extending associated ID applicability across cells to prevent revealing proprietary network information. For performance monitoring, they support Type 1 Option 2 metrics based on ground truth measurements (Alt 1-3) and explicitly deprioritize Alt 4 (probability-only metrics) due to the lack of ground truth validation. They further propose specific Beam Accuracy Indicator (BAI) definitions and handling mechanisms for monitoring sets that are subsets of Set A.

Kyocera proposes that for UE-side AI/ML models, Set A be virtually configured for reference mapping while Set B is explicitly configured for measurements, requiring a new IE to associate beams with these sets. They require the introduction of an 'associated ID' within the CSI framework (nzp-CSI-RS-ResourceSet/csi-SSB-ResourceSet) to ensure consistency of network-side additional conditions, arguing that this ID should be limited to small geographical areas or single cells to avoid revealing proprietary vendor information. For inference reporting, they support 4-bit probability precision and propose studying confidence intervals defined as statistical ranges for predicted RSRP. Regarding performance monitoring, Kyocera supports Type 1 Option 2 metrics including beam prediction accuracy and RSRP differences, but deprioritizes probability-based metrics (Alt 4) due to the lack of ground truth. They propose a 'BeamCorrespondence' IE to link monitoring resources to beam indices and argue that Type 2 monitoring and NW-side monitoring should be left to vendor implementation without specification impact.