R1-2410463
discussion
Discussion for LS reply on applicable functionality reporting
From Qualcomm
Summary
Qualcomm's discussion document addresses RAN2's liaison statement questions about applicable functionality reporting for beam prediction in UE-sided AI/ML models. The document contains no formal proposals but provides detailed technical responses to support the development of beam management procedures.
Position
Qualcomm strongly advocates FOR mandatory associated ID signaling and inference configuration in Step 3, arguing this is the only feasible solution for UE applicability determination. They push AGAINST performance monitoring approaches and immediate activation upon Step 3 reception, insisting on their proposed 3-step flow with delayed activation until Step 5.
Key proposals
- Associated ID signaling in Step 3 is essential - without it UE cannot determine which AI/ML model to download or identify applicability of models for network-side additional conditions
- Inference configuration (CSI-ReportConfig) must also be included in Step 3 since there is no one-to-one mapping between associated ID and inference configuration
- RAN1 terminologies should replace RAN2 terminologies: 'supported functionalities' maps to AI/ML-specific UE capability parameters, activation uses CSI-ReportConfig mechanism
- Proposed call flow: Step 3 sends associated IDs and CSI-ReportConfig, Step 4 UE reports applicable CSI-ReportConfigId(s), Step 5 activates the inference configuration from Step 3
- UE cannot feasibly determine applicable functionalities without network-side additional conditions (associated ID) - performance monitoring approach is not viable
- AI/ML CSI-ReportConfig behavior differs from legacy: configuration is NOT activated in Step 3 but waits until Step 5 for periodic reporting
- Associated ID can be configured within CSI framework and may be part of inference configuration, with details on per-resource-set vs per-pair configuration still FFS
- Step 4 applicable functionality reporting content: UE reports whether indicated associated ID and accompanying configuration is applicable
- No inference configuration needed in Step 5 - instead activate Step 3 configuration using MAC-CE/DCI for AP/SP or different behavior for periodic reporting
- Multiple functionalities can potentially be activated simultaneously with L1/L2 signaling reusing existing CSI report activation mechanisms