RAN1 / #124bis / NR_AIML_air / Verify

ZTE · 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

R1-2602244 discussion not treated 3gpp.org ↗
Discussion on maintenance of AI for Air Interface
Position extracted by AI
ZTE proposes updating TS 38.214 section 5.2.1.6 to correctly capture CPU occupation duration for UE-side data collection for beam management, specifically addressing the omission of periodic CSI reports. They require that for UE-sided models, only always-on SSB and P/SP CSI-RS are supported as resource types for data collection. They propose reusing the existing CPU occupation time definition for CSI-ReportConfig with reportQuantity set to 'none' and TRS-info not configured, extending this to the new 'none-bm-r19' reportQuantity. They specify that CPU occupation for semi-persistent and aperiodic CSI reports must align with the transmission occasions of CSI-RS/SSB resources for L1-RSRP computation. They argue that without these changes, incorrect UE behavior regarding CPU occupation duration for training data collection will occur.
Summary
This document from ZTE addresses maintenance issues for Rel-19 AI use cases, specifically focusing on the CPU occupation duration for UE-side data collection in beam management. It identifies a gap in the current specification where periodic CSI reports for this purpose are not correctly supported, leading to potential incorrect UE behavior. The document contains one primary proposal to update TS 38.214 to reflect RAN1 agreements.

Prior contributions

ZTE 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 ZTE'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.