R1-2407829
LS out
Draft reply LS on applicable functionality reporting for beam management UE-sided model
From vivo
Summary
This is a reply liaison statement from vivo's RAN1 to RAN2 providing detailed answers to 10 questions about applicable functionality reporting for beam management UE-sided AI/ML models. The document contains technical clarifications but no formal proposals, focusing on the procedural aspects of AI/ML model deployment in NR.
Position
Vivo advocates FOR mandatory associated IDs as essential for maintaining consistency between AI/ML training and inference phases, pushing for FG-specific granularity in functionality definition. They are advocating AGAINST providing inference configuration in early steps, preferring a separation of concerns where associated IDs and inference configurations are handled separately to avoid premature activation.
Key proposals
- At least two sub-use cases (BM-Case 1 and BM-Case 2) will be defined as separate Functionality Groups (FGs) for beam management AI/ML capabilities
- Associated ID is used to indicate NW-side additional conditions which cannot be explicitly standardized, and is mandatory for UE to determine applicable functionalities
- UE cannot determine applicable functionalities without NW-side providing associated IDs first, as consistency between training and inference conditions is crucial
- Associated IDs in step 3 are separate from inference configuration and can be FG-specific
- Step 4 applicable functionality reporting must contain associated IDs supported by UE and may include cell IDs where training data originated
- Inference configuration in Step 5 includes CSI framework configuration (report configuration, Set B/Set A) and associated ID for interference
- Associated ID can be configured within CSI framework as working assumption
- UE may assume similar properties of DL Tx beam or beam set/list associated with the same associated ID
- Inference configuration provided in Step 3 does not activate functionality immediately
- Multiple applicable functionalities can be activated simultaneously using existing beam report mechanisms
- Current signaling for beam report activation/deactivation is sufficient without extra signaling needed
- Inference timing depends on beam report type: periodic needs no activation signaling, semi-persistent/aperiodic requires MAC CE or DCI