R1-2407692
discussion
Discussion on LS on applicable functionality reporting for beam management UE-sided model
From Spreadtrum
Summary
Spreadtrum provides RAN1's response to RAN2's liaison statement on applicable functionality reporting for beam management UE-sided AI/ML models, presenting 8 comprehensive proposals addressing granularity, network-side conditions, configuration content, and activation mechanisms.
Position
Spreadtrum advocates FOR mandatory network-side additional conditions and structured configuration frameworks, pushing for sub-use case level granularity and comprehensive inference configuration requirements. They are positioned AGAINST optional network-side conditions and functionality-specific additional conditions, emphasizing the need for UE guidance through proper network configuration rather than autonomous UE decision-making.
Key proposals
- Proposal 1 (Sec 2): The granularity of functionality should be at least at the level of sub-use cases rather than broader use cases
- Proposal 2 (Sec 2): It is correct that RAN2 assumption of a NW-side additional condition assumed as associated ID
- Proposal 3 (Sec 2): NW-side additional condition should not be functionality specific to maintain network configuration consistency
- Proposal 4 (Sec 2): NW-side additional condition is mandatory from RAN1 perspective as it's not feasible for UE to decide applicable functionalities without it, and gNB must provide inference configuration in Step 3
- Proposal 5 (Sec 2): The content reported by UE in step 4 should be applicable functionality and corresponding details of the applicable functionality
- Proposal 6 (Sec 2): The content of inference configuration in Step 5 should be the same as or subset of the content in Step 3
- Proposal 7 (Sec 2): Whether functionality will be activated immediately upon receiving Step 3/5 depends on CSI configuration type - periodic activates immediately, semi-persistent and aperiodic need L1/L2 signaling
- Proposal 8 (Sec 2): If more than one functionality are configured in Step 3 or Step 5, multiple/all applicable functionalities can be activated