R1-2409859
discussion
Discussion on RAN2 LS on applicable functionality reporting for beam management UE-sided model
From NEC
Summary
This NEC document responds to RAN2 questions about applicable functionality reporting for AI/ML beam management in NR, presenting 13 proposals and 2 observations addressing signaling procedures, network-side conditions, and functionality activation mechanisms.
Position
NEC advocates FOR Option 3 approach where UE initiates parameter alignment reporting rather than network-side configuration in Step 3, supports sub-use case granularity for functionality definitions, and pushes AGAINST providing inference configuration in Step 3. They emphasize using existing CSI framework for inference configuration and believe UE can decide applicable functionalities without mandatory network-side additional conditions, with performance monitoring as backup.
Key proposals
- Proposal 1 (General): For Q1, the granularity is a sub-use case or finer. And further discuss whether capability comprises signalling of detailed information such as Set A and Set B, observation/prediction window, output type, and prediction accuracy, etc.
- Proposal 2 (NW-side conditions): For Q2, it is needed to confirm RAN2 assumption of a NW-side additional condition assumed as associated ID is correct.
- Proposal 4 (NW-side conditions): For Q4-1, it is feasible for UE to decide the applicable functionalities without NW-side additional condition. When the NW-side additional condition is not provided, the default assumption should be that UE assumes that the consistency between model training and model inference is ensured by the NW.
- Proposal 5 (NW-side conditions): Remove UAI related part in RAN1 solution.
- Proposal 6 (NW-side conditions): For Q4-2, it is NOT required for gNB to provide inference configuration in Step 3.
- Proposal 7 (NW-side conditions): For applicability for inference for UE-side model, support Option 3.
- Proposal 8 (NW-side conditions): For Q5, support to report applicable Functionality ID/list or confirmation information. If the terminology 'functionality' is not pursued anymore, and if Option 3 will be supported, applicable inference related parameters can be reported in Step 4.
- Proposal 9 (NW-side conditions): For Q6, the inference configuration is CSI report configuration and resource configuration using the CSI framework.
- Proposal 10 (Functionality Activation): For Q7, our understanding is that inference configuration is NOT provided in Step 3. Even it is provided, it cannot activate the functionality immediately upon receiving Step 3.
- Proposal 11 (Functionality Activation): For Q8, configuration in Step 5 does activate the functionality immediately upon receiving Step 5.
- Proposal 12 (Functionality Activation): For Q9, if more than one functionality are configured in Step 5, the multiple/all applicable functionalities can be activated up to UE capability.
- Proposal 13 (Functionality Activation): For Q10, support to further study the need of L1/L2 signaling for functionality activation/deactivation in addition to RRC reconfigurations.