R1-2602244
discussion
Discussion on maintenance of AI for Air Interface
From ZTE
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.
Position
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.
Key proposals
- Proposal 1 (Sec 2.1.1): To adopt changes in section 5.2.1.6 of TS 38.214 to include periodic CSI report for UE-side data collection for beam management and capture the corresponding CPU occupation duration.
- Proposal 1 (Sec 2.1.1): To reflect RAN1 agreements accurately by supporting periodic CSI reports for UE-side data collection, addressing the current lack of support for this resource type.
- Proposal 1 (Sec 2.1.1): To define CPU occupation for CSI-ReportConfig with reportQuantity set to 'none-bm-r19', ensuring it aligns with the timing of periodic or semi-persistent CSI-RS/SSB resources for L1-RSRP computation.
- Proposal 1 (Sec 2.1.1): To specify that for semi-persistent CSI reports (excluding initial triggers), CPU occupation starts from the first symbol of the earliest transmission occasion and ends after the last symbol of the latest resource in that occasion.
- Proposal 1 (Sec 2.1.1): To define CPU occupation for aperiodic CSI reports as starting from the first symbol after PDCCH triggering and ending based on the latest CSI-RS/SSB resource for channel measurement.
- Proposal 1 (Sec 2.1.1): To maintain existing CPU occupation definitions for reportQuantity set to 'none' with TRS-info not configured, ensuring consistency with previous agreements.
- Proposal 1 (Sec 2.1.1): To define CPU occupation for reportQuantity set to 'none-csi-r19' from the first symbol of each transmission occasion until a defined duration after the periodic or semi-persistent CSI-RS resource.
- Proposal 1 (Sec 2.1.1): To ensure that the CPU occupation duration parameters are defined in table 5.4-2, providing a standardized reference for implementation.
- Proposal 1 (Sec 2.1.1): To clarify that only always-on SSB and P/SP CSI-RS are supported for UE-sided model data collection resource types, as per RAN1 agreements.
- Proposal 1 (Sec 2.1.1): To reuse existing CPU occupation time logic for CSI reports with reportQuantity 'none' when TRS-info is not configured, extending this logic to the new 'none-bm-r19' case.