R1-2407604
LS in
LS on applicable functionality reporting for beam management UE-sided model
From Intel
Summary
This is a liaison statement from RAN2 to RAN1 regarding AI/ML functionality reporting procedures for beam management UE-sided models, containing no specific proposals but presenting 10 detailed questions about the signaling procedure and functionality management.
Position
RAN2 is seeking RAN1's technical input and validation on their agreed signaling procedures for AI/ML beam management functionality reporting, advocating for a structured 5-step process while acknowledging multiple technical aspects remain for further study (FFS). They are pushing for clarity on functionality granularity, network-side conditions, and activation mechanisms.
Key proposals
- Step 1 procedure: Network sends UECapabilityEnquiry message to initiate AI/ML supported functionalities reporting from UE
- Step 2 procedure: UE sends UECapabilityInformation message containing supported functionalities at UE side
- Step 3 configurations: Network provides UAI reporting allowance, optional NW-side additional conditions, and FFS inference configuration
- Step 4 applicable functionality reporting: UE reports in two scenarios - upon configuration/change via UAI and as response to NW-side conditions
- Step 5 inference configuration: Network configures inference after applicable functionality reporting or provides updated configuration
- Q1 granularity question: What is the granularity of functionality - use case level, sub-use case level, or others
- Q2-Q3 NW-side conditions: Content should be associated ID and whether it is functionality specific
- Q4 information requirements: What information UE needs to decide applicable functionalities before Step 4
- Q7-Q8 activation timing: Whether inference configuration activates functionality immediately upon receiving Step 3 or Step 5
- Q10 signaling requirements: Whether L1/L2 signaling for functionality activation/deactivation is needed