Huawei · 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 of Rel-19 AI/ML for air interface
Position extracted by AI
Huawei proposes relaxing legacy PDSCH rate-matching rules in TS 38.211 to exclude NZP CSI-RS resources that are only configured in Set A (for inference or applicability check) or Set B (for applicability check Option B), arguing these virtual resources are not actually transmitted and thus should not waste PDSCH resources. They prefer zero-padding for 1-bit or 2-bit RS-PAI payloads on PUCCH over restricting the number of transmission occasions (M), citing simplicity and alignment with existing CSI part 2 padding mechanisms. Huawei requires aligning RRC parameter notations in TS 38.214 and TS 38.212 with TS 38.331, specifically standardizing terms like 'resourcesForChannelPrediction-r19' and 'csi-PAI-r19'. They argue that for Option B applicability checks, resources configured for prediction and measurement are only for applicability verification and do not trigger actual measurement or rate-matching behaviors.
Summary
This Huawei contribution addresses remaining issues for Rel-19 AI/ML-based beam management, specifically focusing on resource handling for virtual CSI-RS and PUCCH reporting constraints. The document presents four text proposals to relax legacy rate-matching rules for non-transmitted resources in Set A/B, support zero-padding for small RS-PAI payloads on PUCCH, and align RRC parameter notations across TS 38.214 and TS 38.212.
Prior contributions
Huawei 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 Huawei'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.