R1-2500669
discussion
Discussion on specification support for beam management
Summary
Ruijie Networks presents five proposals for Rel-19 AI/ML beam management specification support, focusing on performance monitoring, BM-Case 2 configuration, associated ID handling, and L1-RSRP reporting. The document addresses open issues regarding the linkage between monitoring resources and Set A beams, time domain behavior combinations, reference time instances for predictions, and overhead reduction in NW-sided models.
Position
Ruijie Networks proposes using the inference report configuration ID to explicitly identify the relationship between monitoring resource sets and Set A beams, ensuring clear linkage in the CSI framework. They support allowing all combinations of time domain behaviors for inference and monitoring reports to accommodate diverse reporting requirements. For BM-Case 2, they prefer Option 3, anchoring the reference time for predicted results to the latest CSI-RS/SSB transmission occasion in Set B that is no later than the CSI reference resource. Regarding associated IDs, they propose configuring them within CSI-ReportConfig, mandating at least one ID for Set A/B consistency while optionally supporting a separate ID for Set B to handle cases where Set B is not a subset of Set A. Finally, they propose configurable parameters M and X for L1-RSRP reporting in NW-sided models to reduce overhead by limiting reports to beams within a specific dB gap of the strongest signal.
Key proposals
- Proposal 1 (Performance monitoring): Use the ID of an inference report configuration to identify the connection or relationship between RSs in monitoring resource sets and Set A beams.
- Proposal 2 (Performance monitoring): Support all combinations of time domain behaviors (periodic, semi-persistent, aperiodic) for inference report and monitoring report ConfigTypes.
- Proposal 3 (Configuration for BM-Case 2): Support Option 3 for the reference time of the earliest predicted result instance, based on the latest CSI-RS/SSB transmission occasion in Set B no later than the CSI reference resource.
- Proposal 4 (Associated ID related): Configure associated IDs within the CSI framework (CSI-ReportConfig), supporting at least one ID for Set A/B consistency and optionally another for Set B.
- Proposal 5 (L1-RSRP omission): For NW-sided models, support reporting L1-RSRPs and beam info for up to M beams within X dB gap to the largest measured value, with X and M configured by gNB.
- Observation (Associated ID related): For BM-Case 1 and 2, if Set B is a subset of Set A, one associated ID per pair is assumed; if different, distinct IDs may be needed.
- Observation (L1-RSRP omission): Configurable X and M parameters significantly reduce reporting overhead for different deployment scenarios in NW-sided models.
- Agreement (Agreement section): For UE-sided model BM-Case 1, beam information in inference result reports is CRI/SSBRI of resources in Set A.
- Conclusion (Conclusion section): For BM-Case 2 UE-side model, only fixed Set B across different time instances is supported for a single CSI report.
- Agreement (Agreement section): Two CSI-ResourceConfigIds are configured separately for Set A and Set B when configured within CSI report configuration.
- Agreement (Agreement section): UE is allowed to do UAI reporting via OtherConfig, with applicability reports based on CSI-ReportConfig or inference parameter sets.
- Agreement (Agreement section): For monitoring Type 1 Option 2, reuse CSI framework for L1 signaling configuration with dedicated resource sets and report configurations.
- Conclusion (Conclusion section): Aperiodic and semi-persistent CSI reports for inference can be activated after RRCReconfigurationComplete, while periodic reports are considered activated after completion.
- Agreement (Agreement section): Send LS to RAN2 clarifying that 'functionality' granularity may differ for Supported, Applicable, and Activated functionalities in beam management.