Lenovo · 9.1.1
Specification support for beam management ·
RAN1#120 · Source verification
the AI's delta
new
vs RAN1#119
Lenovo is a new contributor in this meeting. They propose supporting UE-initiated beam management procedures for data collection to enable UE-side model training. They require combining an associated ID with performance monitoring to ensure consistency between training and inference, arguing the associated ID alone is insufficient. New proposals include specific overhead reduction techniques for BM-Case 2, such as differential RSRP quantification relative to the global maximum. They introduce the concept of AI Process Units (APUs) to manage UE hardware resources and propose refining CSI computation time to account for AI inference latency.
AI-synthesized from contributions · all text is paraphrased
Every position summary on this site is generated by an AI from the actual Tdoc contributions. This page shows you the exact source documents the AI read to produce the summary above, so you can verify it yourself. Click any Tdoc ID to view its detail page, or click "3gpp.org ↗" to read the original on the official 3GPP server.
Contributions at RAN1#120 · 1 doc
AI/ML specification support for beam management
Position extracted by AI
Lenovo proposes supporting UE-initiated beam management procedures for data collection to enable UE-side model training. They require combining an associated ID with performance monitoring to ensure consistency between training and inference, arguing that the associated ID alone is insufficient due to signaling overhead. For BM-Case 2, they propose specific overhead reduction techniques, including differential RSRP quantification relative to the global maximum and reporting unique beams with time-stamp indicators. They introduce the concept of AI Process Units (APUs) to manage UE hardware resources and propose refining CSI computation time to account for AI inference latency. For performance monitoring, they support Alt 2 and Alt 3 metrics, which rely on L1-RSRP differences, and propose event-triggered beam reports for hybrid monitoring scenarios.
Summary
Lenovo submits 27 proposals for AI/ML-enabled beam management in NR Rel-19, addressing data collection, model inference, and performance monitoring for both UE-side and NW-side models. The document focuses on specification support for BM-Case 1 (spatial prediction) and BM-Case 2 (temporal prediction), including mechanisms for overhead reduction, consistency between training and inference, and lifecycle management.
Prior contributions at RAN1#119 · 1 doc · Nov 18, 2024
AI/ML specification support for beam management
Position extracted by AI
Lenovo advocates for a comprehensive AI/ML beam management framework that supports both UE-side and NW-side inference with strong emphasis on: 1) UE autonomy in data collection and model training initiation, 2) unified configuration approaches supporting both BM-Case1 and BM-Case2 through common frameworks, 3) robust performance monitoring with multiple metric alternatives (Alt 1, 2, 3), and 4) practical overhead reduction through variable-size beam reports and differential RSRP quantization. They push for flexible associated ID mechanisms combined with performance monitoring rather than rigid pre-defined conditions, and emphasize hardware resource management through AI process units.
Summary
This Lenovo contribution presents 26 proposals for AI/ML specification support in NR beam management, covering data collection, model inference for both UE-side and NW-side implementations, performance monitoring, and UE capability reporting across spatial-domain (BM-Case1) and temporal (BM-Case2) beam prediction use cases.
How this was derived
The AI extracted the "position extracted" field above directly from each Tdoc during summarization.
For the delta summary at the top, the AI compared Lenovo's consolidated stance at RAN1#120
against their stance at RAN1#119 and classified the change as
new.
Always verify critical claims against the original Tdocs linked above.