RAN1 / #124bis / NR_AIML_air / Verify

NEC · 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-2602110 discussion not treated 3gpp.org ↗

Remaining Issues on AIML for NR Air Interface

      Position extracted by AI
    

NEC proposes that for monitoring reports, the UE shall drop the report if the linked inference report is deactivated, ensuring no wrong RS-PAI is reported. They require that P/SP NZP-CSI-RS resources configured for Set A (virtual beams) be available for PDSCH transmission during model inference to prevent unnecessary resource waste from rate-matching. NEC argues that if a CSI-ReportConfig becomes inapplicable due to UE-side model unavailability, the UE shall transmit a CSI report with an invalid value rather than attempting inference. Finally, they support a zero-padding solution for RS-PAI payloads on PUCCH to handle cases where the payload size is 1 or 2 bits, avoiding restrictions on the number of transmission occasions.

      Summary
    

NEC presents four technical proposals addressing remaining issues in AI/ML-based beam management for the NR air interface, specifically focusing on monitoring report behavior, resource availability, and payload formatting. The document aims to resolve ambiguities regarding linked inference report deactivation, PDSCH rate-matching for virtual CSI-RS resources, handling of inapplicable CSI configurations, and PUCCH payload padding.

Prior contributions

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