ZTE · 5
RAN1#124bis · Source verification
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 · 2 docs
[Draft] Reply LS on capability reporting for PRS Processing Window
Position extracted by AI
ZTE, representing RAN1, responds to RAN2's inquiry regarding UE-based positioning Case 1 capabilities. They assert that the specific capabilities defined in items 58-2-9 and 58-2-10, which relate to the number of activated PRS processing windows and DL PRS buffering capabilities outside the Measurement Gap, must be known to both the gNB and the Location Management Function (LMF). This stance ensures that network-side entities have the necessary visibility into UE processing constraints for positioning procedures.
Summary
This document is a Liaison Statement reply from RAN1 to RAN2 regarding capability reporting for Positioning Reference Signal (PRS) processing windows in Release 19. It contains one specific technical response addressing RAN2's inquiry about capabilities 58-2-9 and 58-2-10, stating that these capabilities must be known to both the gNB and the LMF.
Discussion on capability reporting for PRS Processing Window
Position extracted by AI
ZTE proposes that Feature Groups 27-23 and 58-2-11, which define support for more than one activated PRS processing window across all active DL BWPs, must be known to both the gNB and the LMF. This stance is driven by the NRPPa Measurement Preconfiguration and Activation procedures, where the LMF requests the gNB to configure and activate PPWs; without LMF knowledge of these capabilities, configuration failures may occur if requests exceed UE limits. Furthermore, ZTE proposes that Feature Groups 58-2-9 and 58-2-10, concerning DL PRS measurement outside Measurement Gaps and buffering capabilities for UE-based positioning Case 1, should also be known to both the gNB and the LMF. This ensures consistency with Rel-17 legacy positioning, where similar capabilities are already shared between nodes to facilitate proper PPW configuration and resource reservation.
Summary
ZTE addresses RAN2 questions regarding the visibility of UE capabilities for PRS Processing Window (PPW) in NR positioning, specifically for Rel-19 AI/ML features. The document contains two main proposals arguing that specific Feature Groups (FGs) related to multiple activated PPWs and buffering capabilities should be known to both the gNB and the LMF to ensure correct configuration and activation.
Prior contributions at RAN1#119 · 1 doc · Nov 18, 2024
Discussion and reply LS on applicable functionality reporting for beam management UE-sided model
Position extracted by AI
ZTE opposes Option 1 for UE-side model inference applicability, arguing it causes substantial waste of air interface resources and complicates NW scheduling. They support Option 3, emphasizing its compatibility with legacy CSI-ReportConfig design. ZTE proposes that AI/ML beam management feature groups be defined at least per sub-use case level (BM-Case1, BM-Case2), with condition combinations aligned between NW and UE outside UE capability indication to support future extensions. They argue that the provision of associated ID in Step 3 should be optional and that inference configuration in Step 3 is unnecessary for determining applicability. ZTE requires that Step 4 reporting include condition combinations and model availability, while Step 5 inference configuration comprises associated CSI report configurations. Finally, they propose that functionality activation depends on CSI report temporal characteristics and that L1/L2 signaling for activation/deactivation should reuse existing CSI report mechanisms.
Summary
ZTE analyzes the applicable functionality reporting procedures for UE-sided AI/ML beam management models, specifically addressing questions from a RAN2 Letter of Agreement. The document presents 15 distinct proposals across four sections, arguing against Option 1 for inference applicability due to resource waste and scheduling complexity, while strongly supporting Option 3 for its compatibility with legacy CSI report designs.
How this was derived
The AI extracted the "position extracted" field above directly from each Tdoc during summarization.
Always verify critical claims against the original Tdocs linked above.