R1-2409625 discussion

Discussion on AIML for beam management

From Spreadtrum
Status: not treated
WI: NR_AIML_air
Agenda: 9.1.1
Release: Rel-19
Source: 3gpp.org ↗
Spreadtrum's prior position on 9.1.1 at RAN1#118bis · AI-synthesized, paraphrased
verify sources →
Advocates for UE-initiated data collection for UE-side models, supports up to 16 beams reporting per instance, and favors reusing existing CSI frameworks to minimize specification impact while opposing larger quantization steps to maintain accuracy.

Summary

Spreadtrum presents 15 proposals and 6 observations regarding AI/ML for NR Beam Management, focusing on UE-side and NW-side model configurations, inference reporting, and performance monitoring. The document argues for specific signaling frameworks to ensure consistency between training and inference, particularly emphasizing the use of associated IDs and dedicated monitoring configurations.

Position

Spreadtrum supports Option 1 or Option 2 for UE functionality determination, requiring the associated ID to be configured for both training and inference to guarantee consistency. They oppose configuring only Set B resources for UE-side inference and argue that larger quantization steps should not be considered for NW-side model inference. For BM-Case 2, they propose reusing the TCI indication framework and supporting implicit time reporting, while allowing adaptive selection of reported beam counts. They require the associated ID to be configured in CSI-ReportConfig and oppose Alt.4 for performance monitoring, instead supporting dedicated monitoring configurations and Option 1 for training-inference consistency.

Key proposals

Your notes

Private to your account