Sharp · 8.1
Maintenance on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface ·
RAN1#124bis · Source verification
the AI's delta
new
vs RAN1#124
First tracked appearance at RAN1_124bis
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#124bis · 1 doc
Maintenance on AI/ML for NR Air Interface
Position extracted by AI
Sharp requires that configurations resulting in 1 or 2-bit RS-PAI payloads be prevented for P-CSI and SP-CSI on PUCCH to avoid unspecified UE behavior, preferring network-side configuration restrictions over UE-side zero padding to alleviate UE burden. They propose that the determination of Zref and Z'ref timelines must consider the maximum computation time among both M and Mx updated CSI reports, ensuring AI/ML-based reports are not excluded from timing constraints. Sharp clarifies that for CSI reports with non-zero CPU and APU requirements, if the report is not considered within the available processing units, the UE is not required to update it, thereby preventing inconsistent priority handling where lower-priority reports are updated while higher-priority AI/ML reports are dropped. Finally, they propose reusing the legacy beam management CSI computation time for RS-PAI model monitoring reports to fill the current specification gap.
Summary
Sharp presents four technical proposals to resolve specification maintenance issues for AI/ML-based beam management in NR Rel-19, specifically focusing on RS-PAI reporting constraints, CSI computation timelines, and processing unit allocation. The document addresses gaps in TS 38.214 regarding PUCCH payload sizes for RS-PAI, the inclusion of AI/ML reports in Z/Z' timeline calculations, priority handling for CPU/APU resources, and the definition of computation time for model monitoring reports.
Prior contributions
Sharp has no prior contributions to 8.1 in the meetings currently tracked. This is either a new contributor to this sub-topic or the earliest meeting in our history.
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 Sharp's consolidated stance at RAN1#124bis
against their stance at RAN1#124 and classified the change as
new.
Always verify critical claims against the original Tdocs linked above.