Network-assisted positioning estimation based on round-trip radio frequency fingerprint (RFFP)

By using the network-based machine learning feature extraction model and the machine learning fusion model on the user's equipment side in the wireless communication system, combined with the uplink RF fingerprint information, high-precision positioning estimation in complex environments is achieved, and the existing solutions are solved The problem of decreasing positioning accuracy in technology.

CN119096159APending Publication Date: 2024-12-06QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380035551.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-03-30
Filing Date
2023-03-31
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the prior art, it is difficult to achieve high-precision 5G standard-based positioning estimation in wireless communication systems. Especially in complex multipath environments, the multipath effect and noise interference of the positioning signal have a great impact, resulting in a decrease in positioning accuracy.

Method used

A network-based machine learning feature extraction model is used to extract radio frequency fingerprints (RFFP) from the uplink reference signal (RS-P), and combined with the machine learning feature fusion model on the user equipment (UE) side to perform positioning estimation. This method uses machine learning model to derive the exact position of the UE through the bidirectional RF fingerprint information exchange between the sending and receiving point (TRP) and the UE.

Benefits of technology

It improves positioning accuracy in complex environments, enhances the accuracy and stability of positioning signals, can more effectively resist multipath effect and noise interference, and improves the positioning performance of 5G networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096159A_ABST
    Figure CN119096159A_ABST
Patent Text Reader

Abstract

In an aspect, a user equipment (UE) transmits an uplink reference signal (RS-P) for positioning to one or more transmit-receive points (TRPs). The TRP or location management function (LMF) extracts features from one or more uplink radio frequency fingerprints (RFFP) of the uplink RS-P via one or more network components via one or more network-based machine learning (ML) feature extraction models, and transmits the extracted features to the UE for location estimation. Other aspects relate to a UE-based round-trip RFFP positioning estimation session of a UE. Other aspects relate to network-based round-trip RFFP positioning estimation of a UE. The UE-based round-trip RFFP positioning estimate and the network-based round-trip RFFP positioning estimate may be based on an uplink RFFP (e.g., SRS) of an uplink reference signal (RS-P) for positioning and a downlink RFFP (e.g., DL PRS) of a downlink RS-P.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims U.S. Non-Provisional Application No. 18 / 192,937, filed on March 30, 2023, entitled “NETWORK-ASSISTED AND ROUND-TRIP RADIO FREQUENCY FINGERPRINT-BASED (RFFP) POSITION ESTIMATION”, U.S. Provisional Application No. 63 / 363,887, filed on April 29, 2022, entitled “NETWORK-ASSISTED AND ROUND-TRIP RADIO FREQUENCY FINGERPRINT-BASED (RFFP) POSITION ESTIMATION”, and U.S. Provisional Application No. 63 / 363,887, filed on April 29, 2022, entitled “ROUND TRIPRADIO FREQUENCY FINGERPRINT-BASED (RFFP) POSITION ESTIMATION The present invention relates to U.S. Provisional Application No. 63 / 363,899, filed on April 29, 2022, entitled “USER EQUIPMENT (UE)-ASSISTED RADIO FREQUENCY FINGERPRINT-BASED (RFFP) POSITION ESTIMATION”, and U.S. Provisional Application No. 63 / 363,893, filed on April 29, 2022, entitled “USER EQUIPMENT (UE)-ASSISTED RADIO FREQUENCY FINGERPRINT-BASED (RFFP) POSITION ESTIMATION”, each of which is assigned to the assignee of the present application, and each of which is expressly incorporated herein by reference in its entirety. Background Art 1. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications.

[0004] 2. Description of related technologies

[0005] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0006] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS procedures and technologies, and high-density deployments of 5G, enable highly accurate 5G-based positioning. Summary of the invention

[0007] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects related to the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0008] In one aspect, a method of operating a user equipment (UE) includes: sending an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); receiving one or more features associated with the uplink RS-P, the one or more features extracted by one or more network components from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P via one or more network-based machine learning (ML) feature extraction models; and determining a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0009] In one aspect, a method of operating a network component; obtaining one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs) from a user equipment (UE); extracting one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and sending the one or more extracted features to one or more target devices.

[0010] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs) via the at least one transceiver; receive one or more features associated with the uplink RS-P via the at least one transceiver, the one or more features being extracted from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P by one or more network components via one or more network-based machine learning (ML) feature extraction models; and determine a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0011] In one aspect, a network component includes: a memory; at least one transceiver; and at least one processor, the processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs) from a user equipment (UE); extract one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and send the one or more extracted features to one or more target devices via the at least one transceiver.

[0012] In one aspect, a user equipment (UE) includes: a component for sending an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); a component for receiving one or more features associated with the uplink RS-P, the one or more features being extracted from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P by one or more network components via one or more network-based machine learning (ML) feature extraction models; and a component for determining a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0013] In one aspect, a network component includes: a component for obtaining one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs) from a user equipment (UE); a component for extracting one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and a component for sending the one or more extracted features to one or more target devices.

[0014] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), causes the UE to: transmit an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); receive one or more features associated with the uplink RS-P, the one or more features extracted by one or more network components from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P via one or more network-based machine learning (ML) feature extraction models; and determine a positioning estimate for the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0015] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, causes the network component to: obtain from a user equipment (UE) one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs); extract one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and send the one or more extracted features to one or more target devices.

[0016] In one aspect, a method of operating a user equipment (UE) includes: receiving one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs); sending an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receiving uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; obtaining one or more downlink RFFPs associated with the one or more downlink RS-Ps; and providing the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0017] In one aspect, a method of operating a transmit receive point (TRP) includes: receiving a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session of a user equipment (UE); sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; receiving an uplink RS-P from the UE in response to the request; obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and sending uplink RFFP measurement information associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0018] In one aspect, a method of operating a transmit receive point (TRP) includes: receiving a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; receiving an uplink RS-P from the UE in response to the request; obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and receiving downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0019] In one aspect, a method of operating a network positioning estimation entity includes: obtaining a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtaining a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFP) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0020] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more downlink reference signals (RS-Ps) for positioning from one or more transmit receive points (TRPs) via the at least one transceiver; send an uplink RS-P to the one or more TRPs via the at least one transceiver, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs via the at least one transceiver; obtain one or more downlink RFFPs associated with the one or more downlink RS-Ps; and provide the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0021] In one aspect, a transmit receive point (TRP) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session of a user equipment (UE); send, via the at least one transceiver in response to the request, a downlink reference signal for positioning (RS-P) to the UE; receive, via the at least one transceiver, an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and send, via the at least one transceiver, uplink RFFP measurement information associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0022] In one aspect, a TRP includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); send, via the at least one transceiver in response to the request, a downlink reference signal for positioning (RS-P) to the UE; receive, via the at least one transceiver, an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and receive, via the at least one transceiver, downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0023] In one aspect, a network positioning estimation entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFPs) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0024] In one aspect, a user equipment (UE) includes: a component for receiving one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs); a component for sending an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; a component for receiving uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; a component for obtaining one or more downlink RFFPs associated with the one or more downlink RS-Ps; and a component for providing the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0025] In one aspect, a transmit receive point (TRP) includes: a component for receiving a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); a component for sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; a component for receiving an uplink RS-P from the UE in response to the request; a component for obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and a component for sending uplink RFFP measurement information associated with the uplink RFFP to the UE for UE-based positioning estimation via a UE-based machine learning (ML) feature fusion model.

[0026] In one aspect, a TRP includes: a component for receiving a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); a component for sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; a component for receiving an uplink RS-P from the UE in response to the request; a component for obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and a component for receiving downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0027] In one aspect, a network positioning estimation entity includes: a component for obtaining a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); a component for obtaining a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFP) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and a component for providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0028] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a user equipment (UE) causes the UE to: receive one or more downlink reference signals (RS-Ps) for positioning from one or more transmit receive points (TRPs); send an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; obtain one or more downlink RFFPs associated with the one or more downlink RS-Ps; and provide the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0029] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions which, when executed by a transmit receive point (TRP), causes the TRP to: receive a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); send a downlink reference signal for positioning (RS-P) to the UE in response to the request; receive an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and send uplink RFFP measurement information associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0030] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a TRP, cause the TRP to: receive a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); send a downlink reference signal for positioning (RS-P) to the UE in response to the request; receive an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and receive downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0031] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a network positioning estimation entity causes the network positioning estimation entity to: obtain a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFP) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0032] In one aspect, a method of operating a network component includes: receiving one or more features associated with one or more downlink reference signals for positioning (RS-P) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features extracted by one or more devices from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps via one or more machine learning (ML) feature extraction models; and providing the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0033] In one aspect, a method of operating a user equipment (UE) includes: receiving one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs); obtaining one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extracting one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and sending the one or more features.

[0034] In one aspect, a network component includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, one or more features associated with one or more downlink reference signals for positioning (RS-Ps) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps; and provide the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0035] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs) via the at least one transceiver; obtain one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extract one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and send the one or more features via the at least one transceiver.

[0036] In one aspect, a network component includes: a component for receiving one or more features associated with one or more downlink reference signals for positioning (RS-P) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps via one or more machine learning (ML) feature extraction models; and a component for providing the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0037] In one aspect, a user equipment (UE) includes: a component for receiving one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs); a component for obtaining one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; a component for extracting one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and a component for sending the one or more features.

[0038] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: receive one or more features associated with one or more downlink reference signals for positioning (RS-Ps) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features extracted by one or more devices from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps via one or more machine learning (ML) feature extraction models; and provide the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0039] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a user equipment (UE) causes the UE to: receive one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs); obtain one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extract one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and transmit the one or more features.

[0040] In one aspect, a method of operating a user equipment (UE) includes: sending a reference signal for positioning (RS-P); obtaining one or more features associated with the RS-P, the one or more features being extracted by one or more entities from one or more radio frequency fingerprints (RFFP) of the RS-P via one or more machine learning (ML) feature extraction models; and providing the one or more features to a UE-based ML feature fusion model to derive a positioning estimate of the UE.

[0041] In one aspect, a method of operating an entity; obtaining one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); extracting one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and sending the one or more extracted features to one or more target devices.

[0042] In one aspect, a method of operating a user equipment (UE) includes: receiving one or more reference signals for positioning (RS-P); sending RS-P, the one or more RS-Ps and the RS-P are associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receiving RFFP measurement information associated with the RS-P; obtaining one or more RFFPs associated with the one or more RS-Ps; and providing the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0043] In one aspect, a method of operating a network positioning estimation entity includes: obtaining a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint being associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtaining a second set of features associated with one or more round-trip radio frequency fingerprints (RFFP) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and providing the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE.

[0044] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a reference signal for positioning (RS-P) via the at least one transceiver; obtain one or more features associated with the RS-P, the one or more features being extracted from one or more radio frequency fingerprints (RFFP) of the RS-P by one or more entities via one or more machine learning (ML) feature extraction models; and provide the one or more features to a UE-based ML feature fusion model to derive a positioning estimate of the UE.

[0045] In one aspect, an entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); extract one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and send the one or more extracted features to one or more target devices via the at least one transceiver.

[0046] In one aspect, a UE includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more reference signals for positioning (RS-P) via the at least one transceiver; send the RS-P via the at least one transceiver, the one or more RS-Ps and the RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive RFFP measurement information associated with the RS-P via the at least one transceiver; obtain one or more RFFPs associated with the one or more RS-Ps; and provide the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0047] In one aspect, a network positioning estimation entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint (RFFP) being associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more round-trip radio frequency fingerprints (RFFP) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE.

[0048] In one aspect, a user equipment (UE) includes: a component for sending a reference signal for positioning (RS-P); a component for obtaining one or more features associated with the RS-P, the one or more features being extracted from one or more radio frequency fingerprints (RFFPs) of the RS-P by one or more entities via one or more machine learning (ML) feature extraction models; and a component for providing the one or more features to a UE-based ML feature fusion model to derive a positioning estimate of the UE.

[0049] In one aspect, an entity includes: a component for obtaining one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); a component for extracting one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and a component for sending the one or more extracted features to one or more target devices.

[0050] In one aspect, a UE includes: a component for receiving one or more reference signals for positioning (RS-P); a component for sending the RS-P, the one or more RS-Ps and the RS-P are associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; a component for receiving RFFP measurement information associated with the RS-P; a component for obtaining one or more RFFPs associated with the one or more RS-Ps; and a component for providing the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0051] In one aspect, a network positioning estimation entity includes: a component for obtaining a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint (RFFP) being associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); a component for obtaining a second set of features associated with one or more round-trip radio frequency fingerprints (RFFP) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and a component for providing the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE.

[0052] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), causes the UE to: transmit a reference signal for positioning (RS-P); obtain one or more features associated with the RS-P, the one or more features extracted by one or more entities from one or more radio frequency fingerprints (RFFP) of the RS-P via one or more machine learning (ML) feature extraction models; and provide the one or more features to a UE-based ML feature fusion model to derive a positioning estimate for the UE.

[0053] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by an entity, cause the entity to: obtain one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); extract one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and send the one or more extracted features to one or more target devices.

[0054] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a UE causes the UE to: receive one or more reference signals for positioning (RS-P); send RS-Ps, the one or more RS-Ps and the RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive RFFP measurement information associated with the RS-P; obtain one or more RFFPs associated with the one or more RS-Ps; and provide the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0055] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which when executed by a network positioning estimation entity causes the network positioning estimation entity to: obtain a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint (RFFP) being associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more round-trip radio frequency fingerprints (RFFP) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE.

[0056] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0058] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0059] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.

[0060] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0061] Figure 4Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.

[0062] Figure 5 is a diagram illustrating an example frame structure according to aspects of the present disclosure.

[0063] Figure 6 is a graph representing radio frequency (RF) channel estimation in accordance with aspects of the present disclosure.

[0064] Figure 7 Example neural networks in accordance with aspects of the present disclosure are illustrated.

[0065] Figure 8 is a diagram illustrating the use of a machine learning model for RF fingerprinting (RFFP) based positioning in accordance with aspects of the present disclosure.

[0066] Fig. 9 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0067] Fig.10 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0068] Fig.11 The various aspects of the present disclosure are respectively illustrated. Figures 9 and 10 An example specific implementation of the process.

[0069] Fig.12 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0070] Fig.13 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0071] Fig.14 The various aspects of the present disclosure are respectively illustrated. Figure 12 to Figure 13 An example specific implementation of the process.

[0072] Fig.15 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0073] Fig.16 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0074] Fig.17 The various aspects of the present disclosure are respectively illustrated. Figure 15 to Figure 16 An example specific implementation of the process.

[0075] Fig.18 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0076] Fig.19 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0077] Fig. 20 The various aspects of the present disclosure are respectively illustrated. Figure 15 to Figure 16 An example specific implementation of the process. DETAILED DESCRIPTION

[0078] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

[0079] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0080] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0081] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by a program instruction executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".

[0082] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or may be stationary (e.g., at certain times) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.

[0083] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0084] The term "base station" may refer to a single physical transmit-receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0085] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0086] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0087] Figure 1An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base station may include an eNB and / or an ng-eNB (where the wireless communication system 100 corresponds to an LTE network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base station may include a femtocell, a picocell, a microcell, etc.

[0088] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0089] Among other functions, the base station 102 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) over a backhaul link 134, which may be wired or wireless.

[0090] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0091] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).

[0092] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0093] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0094] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' using LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.

[0095] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which may operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend downward to a frequency of 3 GHz, where the wavelength is 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short distances. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0096] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.

[0097] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0098] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signals received from that direction (e.g., increase their gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.

[0099] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.

[0100] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, while if the UE is forming an uplink beam, it is an uplink transmit beam.

[0101] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0102] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0103] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0104] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.

[0105] For example, still referring to Figure 1 , one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0106] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0107] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UE (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.

[0108] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0109] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on sidelink 160.

[0110] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such transmitters typically transmit a signal that is marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0111] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0112] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 may receive communication signals (e.g., signal 124) from SV 112.

[0113] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.

[0114] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0115] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0116] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally viewed as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0117] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, service steering), lawful interception (user plane collection), service usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink service verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 may also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0118] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0119] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0120] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or may alternatively each correspond to a single server.

[0121] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

[0122] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and the like. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0123] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a B node (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone base station or a single-chip base station) or a decomposed base station.

[0124] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0125] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0126] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226), which may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with a core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link, or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via corresponding midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0127] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0128] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 280. CU280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

[0129] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling or modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.

[0130] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

[0131] The SMO framework 255 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .

[0132] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or communicate with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.

[0133] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0134] Figure 3A , Figure 3B and Figure 3C The example may be combined with UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the 5GC 210 / 260 (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0135] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 may be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0136] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As specific examples, short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver, UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0137] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.

[0138] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0139] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), may include separate transmitter circuit systems and separate receiver circuit systems in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0140] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0141] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuit systems, or various combinations thereof.

[0142] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which when executed cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0143] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0144] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0145] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0146] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. The channel estimate from the channel estimator can be used to determine the coding and modulation scheme and for spatial processing. The channel estimate can be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate the RF carrier with the corresponding spatial stream for transmission.

[0147] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point that is most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0148] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0149] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0150] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0151] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

[0152] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.

[0153] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that may be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C Various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0154] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, ​​and 392 may provide for communication between the different logical entities.

[0155] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed "by a UE", "by a base station", "by a network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).

[0156] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated differently from a network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0157] Please note that Figure 3A UE 302 illustrated in the figure may represent a "low-level" UE or an "advanced" UE. As further described below, although low-level UEs and advanced UEs may have the same types of components (e.g., both may have WWAN transceiver 310, processing system 332, memory component 340, etc.), these components may have different degrees of functionality (e.g., increased or decreased performance, more or less capabilities, etc.), depending on whether UE 302 corresponds to a low-level UE or an advanced UE.

[0158] For example, UEs may be classified into low-level UEs (e.g., wearable devices such as smart watches, glasses, rings, etc.) and high-level UEs (e.g., smart phones, tablets, laptops, etc.). Low-level UEs are alternatively referred to as capability-constrained NR UEs, capability-constrained UEs, NR-light UEs, light UEs, NR-ultra-light UEs, or ultra-light UEs. High-level UEs are alternatively referred to as full-capability UEs or simply UEs. Compared to advanced UEs, low-level UEs typically have lower baseband processing capabilities, fewer antennas (e.g., one receiver antenna as a baseline in FR1 or FR2, optionally with two receiver antennas), lower operating bandwidth capabilities (e.g., 20 MHz for FR1 without supplementary uplink or carrier aggregation, or 50 MHz or 100 MHz for FR2), only half-duplex frequency division duplex (HD-FDD) capabilities, smaller HARQ buffers, reduced physical downlink control channel (PDCCH) monitoring, restricted modulation (e.g., 64QAM for downlink and 16QAM for uplink), relaxed processing timeline requirements and / or lower uplink transmit power. Different UE classes can be distinguished by UE category and / or UE capabilities. For example, certain types of UEs can be assigned a "low-level" category (e.g., by original equipment manufacturers (OEMs), applicable wireless communication standards, etc.), while other types of UEs can be assigned a "high-level" category. Certain classes of UEs can also report their type (e.g., "low-level" or "high-level") to the network. Additionally, certain resources and / or channels may be dedicated to certain types of UEs.

[0159] As will be appreciated, the accuracy of low-level UE positioning may be limited. For example, low-level UEs may operate on a reduced bandwidth, such as 5MHz to 20MHz for wearable devices and "relaxed" IoT devices (i.e., IoT devices with relaxed or lower capability parameters (such as lower throughput, relaxed latency requirements, lower energy consumption, etc.)), which results in lower positioning accuracy. As another example, the receive processing capabilities of low-level UEs may be limited due to their lower cost RF / baseband. Therefore, the reliability of measurement and positioning calculations will be reduced. In addition, such low-level UEs may not be able to receive multiple PRSs from multiple TRPs, further reducing positioning accuracy. As yet another example, the transmit power of the low-level UE can be reduced, which means that there will be lower quality uplink measurement results for low-level UE positioning.

[0160] Advanced UEs typically have larger form factors and are more expensive than low-level UEs, and have more features and capabilities than low-level UEs. For example, with respect to positioning, advanced UEs may operate over a full PRS bandwidth (such as 100 MHz) and measure PRS from more TRPs than low-level UEs, both of which result in higher positioning accuracy. As another example, the receive processing capability of an advanced UE may be higher (e.g., faster) due to its higher-capability RF / baseband. In addition, the transmit power of an advanced UE may be higher than that of a low-level UE. Thus, the reliability of the measurement and positioning calculations will be increased.

[0161] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 4 Examples of various positioning methods according to various aspects of the present disclosure are illustrated. In an OTDOA or DL-TDOA positioning process, as shown in scenario 410, the UE measures the difference between the arrival times (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurements), and reports these differences to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known positions of the base stations involved and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.

[0162] For DL-AoD positioning, the positioning entity uses measurement reports from the UE regarding received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station, as shown in scenario 420. The positioning entity can then estimate the position of the UE based on the determined angle and the known location of the transmitting base station.

[0163] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but UL-TDOA is based on uplink reference signals (e.g., sounding reference signals (SRS)) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the receive-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known location of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.

[0164] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0165] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received to transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, as shown in scenario 430, a first entity (e.g., a UE or a base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distance to the second entity and the known location of the second entity. RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy, as shown in scenario 440.

[0166] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing and signal strength of the detected neighboring base stations. The UE's position is then estimated based on this information and the known location of the base stations.

[0167] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, silent sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in an overhead message broadcast periodically, etc.). In some cases, the UE itself is able to detect neighboring network nodes without the use of assistance data.

[0168] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may also include an expected RSTD value and associated uncertainty, or a search window around the expected RSTD. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any resource used for positioning measurements is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.

[0169] The position estimate may be referred to by other names, such as a position estimate, a position, a fix, a position fix, a fix, and the like. The position estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The position estimate may be further defined relative to some other known position or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be contained with some specified or default confidence level).

[0170] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 5 5 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0171] LTE (and in some cases NR) utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Thus, for a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into multiple subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0172] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) is 800 with 4K FFT size.

[0173] exist Figure 5 In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 5 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0174] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) in the frequency domain (also referred to as physical RBs (PRBs)). The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 5In the parameter set of , for a normal cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0175] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 5 Example locations of REs carrying reference signals (labeled "R") are illustrated.

[0176] A set of resource elements (REs) used for transmission of a PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

[0177] The transmission of PRS resources within a given PRB has a specific comb size (also referred to as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. Figure 5 An example PRS resource configuration for comb-4 (which spans four symbols) is illustrated. That is, the positions of shaded REs (labeled as "R") indicate the PRS resource configuration of comb-4.

[0178] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols in a timeslot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers in a timeslot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol Comb-2: {0,1}; 4-symbol Comb-2: {0,1,0,1}; 6-symbol Comb-2: {0,1,0,1,0,1}; 12-symbol Comb-2: {0,1,0,1,0,1,0,1,0,1,0,1}; 4-symbol Comb-4: {0,2,1,3} (as in Figure 5 ); 12-symbol comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 6-symbol comb-6: {0,3,1,4,2,5}; 12-symbol comb-6: {0,3,1,4,2,5,0,3,1,4,2,5}; and 12-symbol comb-12:

[0179] {0,6,3,9,1,7,4,10,2,8,5,11}.

[0180] A "PRS resource set" is a set of PRS resources used to send a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in the PRS resource set have the same periodicity, common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from the following: 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ=0,1,2,3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0181] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.

[0182] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity", "PRS positioning instance", "positioning opportunity", "positioning instance", "positioning repetition", or simply "opportunity", "instance", or "repetition".

[0183] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets with the same values ​​for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the physical downlink shared channel (PDSCH) are also supported by PRS), the same point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.

[0184] The concept of frequency layer is somewhat similar to the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. The UE can indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, the UE can indicate whether it can support one or four positioning frequency layers.

[0185] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to a downlink positioning reference signal, an uplink positioning reference signal, or a sidelink positioning reference signal, unless otherwise indicated by the context. If it is necessary to further distinguish the type of PRS, the downlink positioning reference signal may be referred to as a "DL-PRS", the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as a "UL-PRS", and the sidelink positioning reference signal may be referred to as a "SL-PRS". In addition, for signals (e.g., DMRS) that can be sent in the downlink, uplink, and / or sidelink, these signals may be prefixed with "DL," "UL," or "SL" to distinguish the direction. For example, "UL-DMRS" may be different from "DL-DMRS."

[0186] Figure 6 600 is a graph representing a channel estimate of a multipath channel between a receiver device (e.g., any of the UEs or base stations described herein) and a transmitter device (e.g., any other of the UEs or base stations described herein) according to aspects of the present disclosure. The channel estimate represents the strength of a radio frequency (RF) signal (e.g., a PRS) received through a multipath channel as a function of time delay and may be referred to as a channel energy response (CER), a channel impulse response (CIR), or a power delay profile (PDP) of the channel. Thus, the horizontal axis is in units of time (e.g., milliseconds) and the vertical axis is in units of signal strength (e.g., decibels). Note that a multipath channel is a channel between a transmitter and a receiver over which an RF signal follows multiple paths or multipaths due to the transmission of the RF signal on multiple beams and / or due to propagation characteristics of the RF signal (e.g., reflection, refraction, etc.).

[0187] exist Figure 6 In the example of , the receiver detects / measures multiple (four) clusters of channel taps. Each channel tap represents one multipath that the RF signal follows between the transmitter and the receiver. That is, the channel taps represent the arrival of the RF signal on one multipath. Each cluster of channel taps indicates that the corresponding multipath follows substantially the same path. Different clusters may exist because the RF signal is transmitted on different transmit beams (and therefore at different angles), or because of the propagation characteristics of the RF signal (e.g., may follow different paths due to reflections), or both.

[0188] The cluster of all channel taps for a given RF signal represents the multipath channel (or simply channel) between the transmitter and the receiver. Figure 6 In the channel shown, the receiver receives a first cluster of two RF signals on the channel taps at time T1, a second cluster of five RF signals on the channel taps at time T2, a third cluster of five RF signals on the channel taps at time T3, and a fourth cluster of four RF signals on the channel taps at time T4. Figure 6 In the example of , because the first cluster of RF signals at time T1 arrives first, it is assumed to correspond to an RF signal transmitted on a transmit beam aligned with line of sight (LOS) or the shortest path. The third cluster at time T3 includes the strongest RF signals and may correspond to, for example, an RF signal transmitted on a transmit beam aligned with a non-line of sight (NLOS) path. Note that although Figure 6 Clusters of two to five channel taps are illustrated, but it should be understood that a cluster may have more or less than the illustrated number of channel taps.

[0189] Machine learning can be used to generate models that can be used to facilitate various aspects associated with data processing. One particular application of machine learning involves generating measurement models for processing reference signals (e.g., PRS) used for positioning, such as feature extraction, reporting of reference signal measurement results (e.g., selecting which extracted features to report), etc.

[0190] Machine learning models are generally categorized as supervised or unsupervised. Supervised models can be further subdivided into regression models or classification models. Supervised learning involves learning a function that maps inputs to outputs based on example input-output pairs. For example, given a training data set with two variables, age (input) and height (output), a supervised learning model can be generated that predicts a person's height based on their age. In a regression model, the output is continuous. An example of a regression model is linear regression, which simply tries to find the line that best fits the data. Extensions of linear regression include multiple linear regression (e.g., finding the plane of best fit) and polynomial regression (e.g., finding the curve of best fit).

[0191] Another example of a machine learning model is a decision tree model. In a decision tree model, a tree structure is defined as having multiple nodes. Decisions are used to move from the root node at the top of the decision tree to the leaf nodes (i.e., nodes that do not have additional child nodes) at the bottom of the decision tree. In general, a higher number of nodes in a decision tree model is associated with a higher decision accuracy.

[0192] Another example of a machine learning model is a decision forest. Random forest is an ensemble learning technique built on top of decision trees. Random forest involves creating multiple decision trees using a bootstrapped dataset of the original data and randomly selecting a subset of variables at each step of the decision tree. The model then selects the mode of all predictions of each decision tree. By relying on a "majority decision" model, the risk of error from a single tree is reduced.

[0193] Another example of a machine learning model is a neural network (NN). A neural network is essentially a network of mathematical equations. A neural network accepts one or more input variables and produces one or more output variables by passing through the network of equations. In other words, a neural network receives a vector of inputs and returns a vector of outputs.

[0194] Figure 7 An example neural network 700 in accordance with aspects of the present disclosure is illustrated. The neural network 700 includes an input layer "i" that receives "n" (one or more) inputs (illustrated as "input 1", "input 2", and "input n"), one or more hidden layers (illustrated as hidden layers "h1", "h2", and "h3") for processing the inputs from the input layer, and an output layer "o" that provides "m" (one or more) outputs (labeled as "output 1" and "output m"). The number of inputs "n", hidden layers "h", and outputs "m" may be the same or different. In some designs, the hidden layer "h" may include a linear function and / or an activation function, with the nodes of each successive hidden layer (illustrated as circles) processing the linear function and / or activation function of the nodes from the previous hidden layer.

[0195] In a classification model, the output is discrete. An example of a classification model is logistic regression. Logistic regression is similar to linear regression, but is used to model the probability of a limited number of results (usually two). In essence, a logistic equation is created in such a way that the output value can only be between "0" and "1". Another example of a classification model is a support vector machine. For example, for two categories of data, a support vector machine will find a hyperplane or boundary between the two categories of data that maximizes the margin between the two categories. There are many planes that can separate the two categories, but only one plane can maximize the margin or distance between these categories. Another example of a classification model is naive Bayes based on Bayes' theorem. Other examples of classification models include decision trees, random forests, and neural networks, which are similar to the above examples, except that the output is discrete rather than continuous.

[0196] Unlike supervised learning, unsupervised learning is used to draw inferences and find patterns based on input data without reference to labeled results. Two examples of unsupervised learning models include clustering and dimensionality reduction.

[0197] Clustering is an unsupervised technique that involves grouping or clustering of data points. Clustering is often used for customer segmentation, fraud detection, and document classification. Common clustering techniques include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering. Dimensionality reduction is the process of reducing the number of random variables under consideration by obtaining a set of principal variables. In simpler terms, dimensionality reduction is the process of reducing the dimensionality of a feature set (or, in simpler terms, reducing the number of features). Most dimensionality reduction techniques can be categorized as feature elimination or feature extraction. An example of dimensionality reduction is called principal component analysis (PCA). In the simplest sense, PCA involves projecting higher dimensional data (e.g., three dimensions) into a smaller space (e.g., two dimensions). This produces data of lower dimensionality (e.g., two dimensions instead of three dimensions) while retaining all the original variables in the model.

[0198] Regardless of which machine learning model is used, at a high level, a machine learning module (e.g., implemented by a processing system such as processor 332, 384, or 394) may be configured to iteratively analyze training input data (e.g., measurements of reference signals to / from various target UEs) and associate the training input data with an output data set (e.g., a set of possible or probable candidate locations for the various target UEs) so that the same output data set can be determined later when provided with similar input data (e.g., from other target UEs at the same or similar locations).

[0199] NR supports RF fingerprint (RFFP) based positioning, which is a positioning and location technology that uses RFFP captured by a mobile device to determine the location of a mobile device. The RFFP can be a received signal strength indicator (RSSI), CER, CIR, PDP, or a histogram of channel frequency response (CFR). The RFFP can represent a single channel received from a transmitter (e.g., PRS), all channels received from a specific transmitter, or all channels that can be detected at a receiver. The RFFP measured by a mobile device (e.g., UE) and the position of the transmitter associated with the measured RFFP (i.e., the transmitter that sends the RF signal measured by the mobile device to determine the RFFP) can be used to determine (e.g., triangulate) the position of the mobile device.

[0200] Machine learning positioning techniques have been shown to provide superior positioning performance when compared to classical positioning schemes. In positioning based on machine learning RFFP, a machine learning model (e.g., neural network 700) takes the RFFP of a downlink reference signal (e.g., PRS) as input and outputs a positioning measurement result (e.g., ToA, RSTD) or a mobile device position corresponding to the input RFFP. The machine learning model (e.g., neural network 700) is trained using "ground truth" (i.e., known) positioning measurement results or mobile device positions as reference (i.e., expected) outputs of the RFFP training set.

[0201] For example, a machine learning model may be trained to determine the RSTD measurements of a pair of TRPs based on the RFFP of the PRS sent by the TRP. The reference output for training such a model would be the correct (i.e., ground truth) RSTD measurements of the location of the mobile device when the mobile device obtains the RFFP measurement of the PRS. The network (e.g., a location server) may determine the RSTD expected for the pair of TRPs based on the known location of the mobile device and the known location of the (measured) TRPs involved. The known location of the mobile device may be determined from multiple reported RSTD measurements and / or any other measurements reported by the mobile device (e.g., GPS measurements).

[0202] Figure 8 800 is a diagram illustrating the use of a machine learning model for RFFP-based positioning in accordance with aspects of the present disclosure. Figure 8 In an example, during the "offline" phase, RFFPs (e.g., CER / CIR / CFR) captured by the mobile device are stored in a database. The database may be located at the mobile device or a network entity (e.g., a location server), and each RFFP may include measurements of an RF signal (or channel or link) transmitted by one or more transmitters that are connected to the mobile device during the "offline" phase. Figure 8 1 to BS N). For UE-based downlink RFFP positioning, the network (e.g., location server) configures the base station to send a downlink reference signal (e.g., PRS) to the mobile device, and the RFFP is the CER / CIR / CFR of the configured downlink reference signal detected by the mobile device.

[0203] Each measured RFFP is associated with the known location of the mobile device at the time it measured the RFFP, which is Figure 8 The location of the mobile device can be determined by, for example, the above reference Figure 4 It should be noted that although Figure 8 The RFFP information for a single mobile device is illustrated, but it should be understood that the RFFP information for multiple mobile devices may be collected and stored in a database.

[0204] Based on the information captured during the offline phase, a machine learning model (e.g., neural network 700) is trained to predict positioning measurements and the location of the mobile device based on the RFFP measured by the mobile device. More specifically, a training set of RFFP measurements is used to extract features associated with known positioning measurements, or the location of the mobile device when the RFFP is captured is used as a label. After training, during the "online" phase, the trained machine learning model can be used to predict (infer) features of the mobile device based on the RFFP currently measured by the mobile device, and then predict the location of the mobile device (illustrated as "Pos M"). For UE-based RFFP positioning, the network (e.g., a location server) provides the trained machine learning model to the mobile device. For UE-assisted positioning, the mobile device can provide the RFFP measurements to the network for processing.

[0205] As used herein, a positioning measurement "feature" is a processed (e.g., compressed) representation of raw positioning measurement data or, alternatively, one or more other positioning measurement features (e.g., features of features, etc.). In some designs, processing (e.g., or refining or compressing) raw positioning measurement data into corresponding positioning measurement features may be implemented for various reasons, such as reducing the amount of positioning measurement data to be transmitted on a physical channel between a UE and a gNB. Examples of positioning measurement features include time of arrival (e.g., TOA, TDOA, OTDOA, etc.), reference signal time difference, angle of departure (AoD), channel impulse response (CIR) (e.g., timing and amplitude of a predefined number of peaks in a channel estimate, etc.), channel frequency response (CFR), etc. Positioning measurement features may be used for ML-based feature extraction in various contexts (e.g., RFFP, etc.), but references to features in the various aspects described below are generally to RFFP-based features.

[0206] In network (NW)-assisted RFFP positioning, the NW (e.g., LMF, gNB, etc.) configures UL reference signals (e.g., SRS), the UE transmits the UL reference signals, and the TRP receives and uses them to extract features (e.g., using a TRP-based ML model). Then, for UE-based positioning estimation, the TRP transmits the extracted features back to the UE, where the UE passes them to its local ML model to infer positioning. In some designs, the advantages of NW-assisted RFFP may include facilitating UE-based positioning estimation for UEs with limited capabilities (such as NR-Light UEs or RedCap UEs) (e.g., the NW can do most of the "heavy lifting", including measurement processing and feature extraction, and the UE only needs to transmit SRS, receive the extracted features, and pass them to a simple local ML model).

[0207] Various aspects of the present disclosure relate to network-assisted positioning estimation based on uplink RFFP. These aspects may provide various technical advantages, such as improved positioning estimation, especially for UEs with limited capabilities (such as NR-Light UEs or RedCap UEs).

[0208] Fig. 9 An exemplary process 900 of communicating according to an aspect of the present disclosure is illustrated. Fig. 9 The process 900 is performed by a UE such as UE 302 .

[0209] refer to Fig. 9 At 910, UE 302 (e.g., transmitter 314 or 324, etc.) transmits a reference signal for positioning (RS-P). For example, UE 302 may transmit an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs).

[0210] refer to Fig. 9 At 920, the UE 302 (e.g., the receiver 312 or 322, etc.) obtains one or more features associated with the RS-P, the one or more features being extracted by one or more entities from one or more radio frequency fingerprints (RFFPs) of the RS-P via one or more machine learning (ML) feature extraction models. For example, the UE 302 may receive one or more features associated with the uplink RS-P, the one or more features being extracted by one or more network components from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P via one or more network-based machine learning (ML) feature extraction models.

[0211] refer to Fig. 9 At 930, the UE 302 (e.g., the positioning component 342, the processor 332, etc.) determines a positioning estimate for the UE based at least in part on the one or more features and an output of the UE-based ML feature fusion model. In a specific example, the UE 302 provides the one or more features to the UE-based ML feature fusion model to derive a positioning estimate for the UE.

[0212] refer to Fig. 9 In some designs, the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models. In a specific example, the one or more features are extracted by the one or more TRPs. In some designs, the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models. In some designs, the one or more features are extracted by a network location estimation entity (e.g., LMF).

[0213] refer to Fig. 9 In some designs, the one or more features include a first set of features extracted by one or more transmit receive points (TRPs) via a first set of ML feature extraction models, and the one or more features include a second set of features extracted by a network location estimation entity via a second set of ML feature extraction models. In a specific example, the one or more features include a first set of features extracted by the one or more TRPs via a first set of network-based ML feature extraction models, and the one or more features include a second set of features extracted by the network location estimation entity via a second set of network-based ML feature extraction models.

[0214] refer to Fig. 9 In some designs, the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS. In a specific example, the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0215] refer to Fig. 9 In some designs, the one or more features include multipath delay and angle features, potential device-specific features jointly trained with the UE-based ML feature fusion model at the network-side training component, potential device-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof. In a specific example, the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at the network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0216] Fig.10 An exemplary process 1000 of communicating according to an aspect of the present disclosure is illustrated. Fig.10 The process 1000 is performed by an entity. For example, the entity may be a network component such as a TRP (e.g., BS 302 or an O-RAN component), a network positioning estimation entity such as an LMF integrated with or remote from the TRP (e.g., network entity 306), etc. In other designs, the entity may be a UE (e.g., an anchor UE).

[0217] refer to Fig.10At 1010, the entity (e.g., receiver 352 or 362, positioning component 388, network transceiver 380 or 390, etc.) obtains one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE). In a specific example, the entity obtains one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs) from the user equipment (UE).

[0218] refer to Fig.10 At 1020, the entity (e.g., positioning component 388 or 398, processor 384 or 394, etc.) extracts one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models. In a specific example, the entity extracts one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models.

[0219] refer to Fig.10 At 1030, the entity (eg, transmitter 354 or 364, network transceiver 380 or 390, etc.) transmits the one or more extracted features to one or more target devices.

[0220] refer to Fig.10 , in some designs, the entity corresponds to a corresponding transmit-receive point (TRP) or another UE that measures the RS-P to obtain a corresponding RFFP, and the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof. In a specific example, the entity (e.g., a network component) corresponds to a corresponding TRP that measures the uplink RS-P to obtain a corresponding uplink RFFP, and the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof. In other designs, the entity corresponds to a network positioning estimation entity that receives the one or more RFFPs, and the one or more target devices include one or more transmit-receive points (TRPs) or one or more other UEs. In a specific example, the entity (e.g., a network component) corresponds to a network positioning estimation entity that receives RFFP measurement information from the one or more TRPs, and the one or more target devices include one or more TRPs.

[0221] refer to Fig.10, in some designs, the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS. In a specific example, the uplink RS-P corresponds to an uplink sounding reference signal (SRS). In some designs, the one or more features include multipath delay and angle features, potential transmit receive point (TRP) specific features jointly trained with the UE-based ML feature fusion model at the network-side training component, potential device specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving an association between multipath and a virtual anchor point or reflector, or any combination thereof. In a specific example, the one or more features include multipath delay and angle features, potential TRP specific features jointly trained with the UE-based ML feature fusion model at the network-side training component, potential TRP specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving an association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0222] Fig.11 The various aspects of the present disclosure are respectively illustrated. Figures 9 and 10 An example implementation of the processes 900 to 1000 is 1100. In particular, Fig.11 The communication framework for describing the network-assisted positioning estimation based on RFFP is illustrated. Fig.11 , a UE 302, a TRP 304, and a LMF (eg, integrated in one of the TRPs 304 or in a remote entity such as a network entity 306) are depicted.

[0223] refer to Fig.11 , the UE 302 includes ML model 2 1102, the TRP 304 includes ML model 1 / 1a 1104 (e.g., ML model 1, ML model 1a, or both), and the LMF 304, 306 includes ML model 1 / 1b 1106 (e.g., ML model 1, ML model 1b, or both). At 1110, the UE 302 sends a UL RS (e.g., SRS) to the TRP 304. At 1112, the TRP 304 optionally sends the UL RS information to the LMF 304, 306. Optionally, features are extracted from the UL RFFP of the UL RS via ML model 1 / 1a 1104 at the TRP 304 or via ML model 1 / 1b at the LMF 304, 306. At 1116 , the extracted features are optionally transmitted by the LMF 304 , 306 to the TRP 304 , and at 1116 , the extracted features are optionally transmitted by the TRP 304 to the UE 302 .

[0224] refer to Fig.11, ML model 1 / 1a 1104 and ML model 1 / 1b 1106 are feature extraction models. The ML Model 1 part of ML model 1 / 1a 1104 is a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs extracted feature 1. The ML Model 1a part of ML model 1 / 1a 1104 is a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs extracted feature 1a. The ML Model 1 part of ML model 1 / 1b 1106 is a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs extracted feature 1. The ML Model 1b part of ML model 1 / 1b 1106 is a feature extraction model that accepts extracted feature 1a as input and outputs extracted feature 1b. In this context, the extracted feature 1b is "enhanced" (or refined, compressed, etc.) relative to the extracted feature 1a. ML model 2 is a feature fusion model that accepts the extracted features 1 (or 1a or 1b ) as input and outputs an estimated location of the UE 302 .

[0225] refer to Fig.11 In some designs, for the NW-assisted approach, the RFFP ML model may be split in the following manner: a portion of the model may be performed at the NW side and the rest of the model may be performed at the UE. In the model, the TRP uses the TRP ML model to compute some features, e.g., based on UL-SRS channel observations, and reports these features to the UE. The UE utilizes all the features reported from the TRP, performs feature fusion, and infers the UE positioning. For example, one candidate architecture that facilitates such positioning estimation may be expressed as: where p is the position, and is the extracted feature at TRP i, and g φ (·) is the TRP ML model, and f θ (·) is a UE ML model that utilizes all features reported from the TRP, performs feature fusion, and infers the UE position. In some designs, in such an architecture, the execution of the ML model is split between the UE and the network at inference time. In some designs, the features computed by the TRP may use a TRP-specific ML model or a common processing ML model.

[0226] In some designs, the TRP feature extraction model And UE feature fusion model f θ It can be:

[0227] · Option 1: Offline training by UE vendor → UE updates TRP for model ID using capability exchange, TRP vendor retrieves structure and parameters of model from public repository; UE may also update TRP for model details using capability messaging, and / or

[0228] · Option 2 : Trained offline by TRP vendor → NW updates UE for model ID using assistance data, UE vendor retrieves structure and parameters of model from public repository; NW may also update UE for model details using assistance information messaging, and / or

[0229] · Option 3 : Offline training through coordination between UE and TRP provider → Switching between different models can be done by exchanging model ID or model details using UE Capability Messaging and Assistance Information Messaging, and / or

[0230] · Option 4 : Online training → UE, TRP and (possibly) LMF involve online training.

[0231] In some designs, the NW ML model can be:

[0232] · Option 1 : Run on the TRP side to extract features, or

[0233] · Option 2 : Run on the LMF side to extract features, or

[0234] · Option 3 : Further split between TRP and LMF, where LMF can apply further processing to the features extracted by TRP.

[0235] Some examples of features extracted on the NW side include, but are not limited to:

[0236] Multipath delays + angles generated by ML / classical methodologies, e.g. mapped to existing reported decipherable features (which the UE can still utilize to generate the RFFP), and / or

[0237] Latent features generated by a per-TRP feature processor jointly trained with the fused ML model at the UE Such as uninterpretable features, and / or

[0238] Latent features generated by a per-TRP feature processor (e.g., autoencoder) trained independently from the fused NN at the UE For example, features may be interpreted, and / or

[0239] • Association of each observed multipath with a virtual anchor point / reflector in the environment, e.g., virtual anchor point based positioning techniques.

[0240] Various aspects of the present disclosure relate to UE-assisted positioning estimation based on downlink RFFP. These aspects may provide various technical advantages, such as improved positioning estimation, especially for UEs with limited capabilities (such as NR-Light UEs or RedCap UEs).

[0241] Fig.12 An exemplary process 1200 of communicating according to an aspect of the present disclosure is illustrated. Fig.12 Process 1200 is performed by a network component such as a TRP (e.g., BS 302 or an O-RAN component), a network positioning estimation entity such as an LMF integrated with or remote from the TRP (e.g., network entity 306), and the like.

[0242] refer to Fig.12 At 1210, the network component (e.g., receiver 352 or 362, network transceiver 380 or 390, etc.) receives one or more features associated with one or more downlink reference signals for positioning (RS-P) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFP) of the one or more downlink RS-Ps.

[0243] refer to Fig.12 At 1220, a network component (e.g., positioning component 388 or 398, processor 384 or 394, etc.) provides the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0244] refer to Fig.12 In some designs, the network component corresponds to a corresponding TRP in the one or more TRPs that sends the one or more downlink RS-Ps. In some designs, the one or more features are received from the UE. In some designs, the positioning estimate is further sent to a network positioning estimation entity (e.g., LMF). In some designs, the one or more ML feature extraction models include one or more TRP-specific ML feature extraction models or a common ML feature extraction model.

[0245] refer to Fig.12In some designs, the network component corresponds to a network location estimation entity (e.g., a LMF). In some designs, the one or more features are received from at least one of the one or more TRPs. In some designs, the one or more features include a first set of features extracted by the UE via a UE-based ML feature extraction model, or the one or more features include a second set of features extracted by the at least one TRP, the second set of features including one or more enhanced features from at least one network-side ML feature extraction model that accepts the first set of features as input, or a combination thereof.

[0246] refer to Fig.12 In some designs, the one or more RS-Ps correspond to one or more downlink positioning reference signals (PRS). In some designs, the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the network-based ML feature fusion model at the network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0247] Fig.13 An exemplary process 1300 of communicating according to an aspect of the present disclosure is illustrated. Fig.13 The process 1300 is performed by a UE such as UE 302.

[0248] refer to Fig.13 At 1310, UE 302 (eg, receiver 312 or 322, etc.) receives one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs).

[0249] refer to Fig.13 At 1320, the UE 302 (eg, the positioning component 342, the processor 332, etc.) obtains one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps.

[0250] refer to Fig.13 At 1330, the UE 302 (eg, positioning component 342, processor 332, etc.) extracts one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models.

[0251] refer to Fig.13At 1340, UE 302 (e.g., transmitter 314 or 324, etc.) sends the one or more features (e.g., via TRP to a network positioning estimation entity, or via ML model 2a to TRP for further feature extraction / enhancement, etc.).

[0252] refer to Fig.13 , in some designs, wherein the one or more RS-Ps correspond to one or more downlink positioning reference signals (PRS). In some designs, the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with a network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0253] Fig.14 The various aspects of the present disclosure are shown respectively. Figure 12 to Figure 13 An example implementation 1400 of the processes 1200 to 1300 is provided. In particular, Fig.14 A communication framework is illustrated describing a UE-assisted positioning estimation based on RFFP. Fig.14 , a UE 302, a TRP 304, and a LMF (eg, integrated in one of the TRPs 304 or in a remote entity such as a network entity 306) are depicted.

[0254] refer to Fig.14, the UE 302 includes ML model 1 1402, the TRP 304 includes ML model 2a / 2b 1404 (e.g., ML model 2a, ML model 2b, or both), and the LMF 304, 306 includes ML model 3a / 3b 1406 (e.g., ML model 3a, ML model 3b, or both). At 1410, the TRP 304 sends a DL RS (e.g., DL PRS) to the UE 302. Optionally, features are extracted from a DL RFFP of the DL RS via ML model 1 at the UE 302. At 1412, the extracted features are optionally transmitted by the UE 302 to the TRP 304 (e.g., a TRP associated with a serving gNB). At 1414, an estimated position of the UE 302 (e.g., output according to the ML model 2b portion of the ML model 2a / 2b 1404) is optionally transmitted by the TRP to the LMF 304, 306. Alternatively, at 1416, extracted features 1 (e.g., features extracted by ML model 1 1402 at UE 302) or extracted features 2 (e.g., features extracted by the ML model 2a portion of ML model 2a / 2b 1404) are optionally transmitted by the TRP to the LMF 304, 306 (e.g., to facilitate the LMF itself to perform the positioning estimate).

[0255] refer to Fig.14 , ML model 1 1402 and the ML model 1a portion of ML model 2a / 2b 1404 are feature extraction models. ML model 1 1402 is a feature extraction model that accepts DL RFFP (based on the DL RS or DL ​​PRS) as input and outputs extracted feature 1. The ML model 2a portion of ML model 2a / 2b 1404 accepts extracted feature 1 as input and outputs extracted feature 2. In this context, the extracted feature b is "enhanced" (or refined, compressed, etc.) relative to the extracted feature 1. The ML model 2b portion of ML model 2a / 2b 1404 and ML model 3a / 3b 1406 are feature fusion models. The ML model 2b portion of ML model 2a / 2b 1404 accepts extracted feature 1 as input and outputs an estimated positioning of UE 302. The ML model 3a portion of ML model 3a / 3b 1406 accepts extracted feature 2 as input and outputs an estimated positioning of UE 302. The ML model 3b portion of the ML model 3a / 3b 1406 accepts the extracted features 1 as input and outputs an estimated location of the UE 302 .

[0256] refer to Fig.14In some designs, for the UE-assisted approach, the RFFP ML model may be split in the following manner: a portion of the model may be executed at the UE and the rest of the model may be executed at the NW. In this model, the UE uses the UE ML model to compute some features, e.g., based on DL-PRS channel observations, and reports these features to the NW. The NW utilizes all the features reported from the UE, performs feature fusion, and infers the UE positioning.

[0257] For example, one candidate architecture that facilitates such localization estimation can be expressed as: where p is the position, and is the extracted feature of TRP i, and g(·) is the UE ML model, and f θ (·) is the NW ML model, which utilizes all features reported from the UE, performs feature fusion, and infers UE positioning. In some designs, in such an architecture, the execution of the ML model is split between the UE and the network at inference time. In some designs, the features computed by the UE may use a TRP-specific ML model or a common processing ML model for all TRPs as well as a UE ML model.

[0258] In some designs, NWf θ (·) ML models can be:

[0259] · Option 1 : Runs on the TRP side to fuse the features extracted by the UE and produce an RFFP positioning estimate, or

[0260] · Option 2 : Runs on the LMF side to fuse the features extracted by the UE and produce an RFFP positioning estimate, or

[0261] · Option 3 : Further split between TRP and LMF, where TRP can apply further processing using the TRPML model to extract more features and pass them to LMF for fusion using the LMF ML model.

[0262] Some examples of characteristics reported by the UE may include, for example:

[0263] Multipath delays + angles generated by ML / classical methods, e.g. mapped to existing reported interpretable features (which NW can still leverage to generate RFFPs), and / or

[0264] Latent features generated by a per-TRP feature processor jointly trained with the fused ML model at the network Such as uninterpretable features, and / or

[0265] Latent features generated by per-TRP feature processors (e.g., autoencoders) trained independently from the ensemble NN at the network Such as uninterpretable features, and / or

[0266] • Association of each observed multipath with a virtual anchor point / reflector in the environment, e.g., virtual anchor point based positioning techniques.

[0267] refer to Fig.14 , in some designs, the TRP / LMF feature fusion model f θ and UE feature extraction model g φ (·) can be:

[0268] · Option 1 : Trained offline by the UE vendor, e.g., the UE uses capability exchange for f θ Model ID updates TRP, TRP / LMF provider retrieves f from public repository θ Model structure and parameters; UE may also use capability messaging to send and receive information specific to model f θ Details of updated TRP, and / or

[0269] · Option 2 : Trained offline by TRP / LMF providers, e.g., NW uses auxiliary data for g φ (·) Model ID updates the UE, and the UE vendor retrieves g from the public repository φ (·) Model structure and parameters; NW may also use auxiliary data messaging to send and receive information specific to the model g φ (·)

[0270] Update UE with details, and / or

[0271] · Option 3 : Offline training through coordination between UE and TRP / LMF providers, for example, switching between different models can be done by exchanging model IDs or model details using UE capability messaging and assistance information messaging, and / or

[0272] · Option 4 : Online training, such as UE, TRP and (possibly) LMF involves online training.

[0273] Various aspects of the present disclosure relate to round-trip UE-based and RFFP-based positioning estimation.Such aspects may provide various technical advantages, such as improved positioning estimation.

[0274] Fig.15 An exemplary process 1500 of communicating according to an aspect of the present disclosure is illustrated. Fig.15 The process 1500 is performed by a UE such as UE 302.

[0275] refer to Fig.15 At 1510, UE 302 (e.g., receiver 312 or 322, etc.) receives one or more reference signals for positioning (RS-P). In a specific example, UE 302 receives one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs).

[0276] refer to Fig.15 At 1520, UE 302 (e.g., transmitter 314 or 324, etc.) sends RS-P, the one or more RS-Ps and the RS-P are associated with the UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE. In a specific example, UE 302 sends an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P are associated with the UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE. It should be understood that the operations at 1510 and 1520 can occur in any order (e.g., uplink RS-P followed by downlink RS-P, or downlink RS-P followed by uplink RS-P).

[0277] refer to Fig.15 At 1530, the UE 302 (e.g., receiver 312 or 322, etc.) receives RFFP measurement information associated with the RS-P. In a specific example, the UE 302 receives uplink RFFP measurement information (e.g., UL RFFP, extracted features, etc.) associated with the uplink RS-P as measured at the one or more TRPs.

[0278] refer to Fig.15 At 1540, the UE 302 (eg, the positioning component 342, the processor 332, etc.) obtains one or more RFFPs associated with the one or more RS-Ps. In a specific example, the UE 302 obtains one or more downlink RFFPs associated with the one or more downlink RS-Ps.

[0279] refer to Fig.15 At 1550, the UE 302 (e.g., the positioning component 342, the processor 332, etc.) provides the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE. In a specific example, the UE 302 provides the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0280] refer to Fig.15In some designs, the one or more RS-Ps correspond to a downlink positioning reference signal (PRS) or a sidelink sounding reference signal (SRS), and the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS. In a specific example, the one or more downlink RS-Ps correspond to a downlink positioning reference signal (PRS), and the uplink RS-P corresponds to an uplink sounding reference signal (SRS). In some designs, the RFFP measurement information includes one or more RFFPs of the uplink SRS or the sidelink SRS. In a specific example, the uplink RFFP measurement information includes one or more uplink RFFPs of the uplink SRS. In some designs, the UE-based ML feature fusion model includes a UE-based ML feature extraction model, which extracts one or more features associated with the RS-P based on the one or more RFFPs. In a specific example, the UE-based ML feature fusion model includes a UE-based ML feature extraction model, which extracts one or more features associated with the uplink RS-P based on the one or more uplink RFFPs. In some designs, the RFFP measurement information includes one or more features extracted from one or more RFFPs associated with the RS-P via one or more ML feature extraction models at one or more entities. In a specific example, the uplink RFFP measurement information includes one or more features extracted from one or more uplink RFFPs via one or more network-based ML feature extraction models at the one or more TRPs. In some designs, the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models. In a specific example, the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0281] Fig.16 An exemplary process 1600 of communicating according to an aspect of the present disclosure is illustrated. Fig.16 Process 1600 is performed by a TRP (e.g., BS 302 or an O-RAN component).

[0282] refer to Fig.16 At 1610, the TRP (eg, receiver 352 or 362, network transceiver 380, etc.) receives a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE).

[0283] refer to Fig.16At 1620, the TRP (eg, transmitter 354 or 364, etc.) sends a downlink reference signal for positioning (RS-P) to the UE in response to the request.

[0284] refer to Fig.16 At 1630, the TRP (e.g., receiver 352 or 364, etc.) receives an uplink RS-P from the UE in response to the request. It should be understood that the operations at 1620 and 1630 can occur in any order (e.g., uplink RS-P followed by downlink RS-P, or downlink RS-P followed by uplink RS-P).

[0285] refer to Fig.16 At 1640, the TRP (e.g., positioning component 388, processor 384, etc.) obtains the uplink RFFP of the uplink RS-P as measured at the TRP.

[0286] refer to Fig.16 At 1650, the TRP (e.g., transmitter 354 or 364, network transceiver 380, etc.) sends uplink RFFP measurement information (e.g., UL RFFP, extracted features, etc.) associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0287] refer to Fig.16 , in some designs, the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and the uplink RS-P corresponds to an uplink sounding reference signal (SRS). In some designs, the uplink RFFP measurement information includes the uplink RFFP. In some designs, the uplink RFFP measurement information includes one or more features extracted from the uplink RFFP via one or more network-based ML feature extraction models. In some designs, the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models. In some designs, the one or more features are extracted from the uplink RFFP at the TRP or network positioning estimation entity.

[0288] Fig.17 The various aspects of the present disclosure are shown respectively. Figure 15 to Figure 16 An example implementation of the processes 1500 to 1600 is 1700. In particular, Fig.17 A communication framework depicting round-trip UE-based and RFFP-based positioning estimation is illustrated. Fig.17, a UE 302, a TRP 304, and a LMF (eg, integrated in one of the TRPs 304 or in a remote entity such as a network entity 306) are depicted.

[0289] refer to Fig.17 , UE 302 includes an ML model f θ (.) 1702, TRP 304 optionally includes ML model ULg φ (.) 1704, and LMF 304, 306 optionally includes ML model ULg φ (.) 1706. At 1710, the LMF 304, 306 sends a request for UL and DL resources for a round trip (or RTT) RFFP positioning estimation session. At 1712, the UE 302 sends a UL RS (e.g., SRS) to the TRP 304. At 1714, the TRP 304 sends a DL RS (e.g., DL PRS) to the UE 302. As described above, operations 1712 to 1714 may occur in any order. Optionally, at the TRP 304, the ULg φ (.) 1704 extracts features from the UL RFFP of the UL RS. Fig.17 , but the ML model ULg at LMF 304, 306 φ (.) 1706 may alternatively be used for feature extraction. At 1716, the extracted features are optionally transmitted by TRP 304 to UE 302. Alternatively, at 1718, TRP 304 may alternatively provide the UL RFFP, in which case it may be via ML model f θ (.) 1702 implements feature extraction at UE 302 (e.g., in this case, ML model f θ (.) The feature fusion model of 1702 may include a feature extraction model component). In some designs, the UL and DL resources for the DL RS at 1712 and / or the UL RS at 1714 may be arranged to be close together in time (e.g., in the same time slot, or within a threshold number of symbols, etc.) to improve positioning estimation accuracy.

[0290] refer to Fig.17 , ML model ULg φ (.)1704 and ML model ULg φ (.) 1706 is a feature extraction model. ML model ULg φ (.) 1704 is a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs extracted UL features. ML Model ULg φ(.) 1706 is also a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs extracted UL features. ML model f θ (.)1702 is a feature fusion model. ML model f θ (.) 1702 accepts as input the extracted UL features or the UL RFFP and the DL RFFP (obtained at UE 302 via direct measurement) and outputs an estimated position of UE 302. As described above, the ML model f θ (.) 1702 fuses the features together into the estimated positioning, but may also include a feature extraction component for processing the UL RFFP and / or the DL RFFP.

[0291] refer to Fig.17 In some designs, for the UE-based RT-RFFP method, the UE utilizes the DL RFFP features obtained by observing the DL RS and the UL-RFFP features (or UL extracted features) reported from the TRP, and performs feature fusion, and infers the UE positioning.

[0292] For example, one candidate architecture that facilitates such localization estimation can be expressed as: where p is the position, and is the extracted feature at TRP i, g φ (·) is the TRP ML model, and f θ (·) is the UE ML model, which utilizes all features reported from the TRP and the features observed at DL, and performs feature fusion, and infers the UE positioning.

[0293] In some designs, the UL features calculated by the TRP may use a TRP-specific ML model or a common processing ML model. In some designs, the UL features may be optional, and It can be a UL channel, i.e. In some designs, the timing of the UL and DL resources used in RT-RFFP positioning needs to be close in time.

[0294] Some examples of UL features reported by the NW side may include, for example:

[0295] Multipath delays + angles generated by ML / classical methods for the UL channel, e.g. mapped to existing reported decipherable features (UEs can still utilize these decipherable features to generate RFFP),

[0296] and / or

[0297] Latent features generated by a per-TRP feature processor jointly trained with the UE-side fused ML model Such as uninterpretable features, and / or

[0298] Latent features generated by a per-TRP feature processor (e.g., autoencoder) trained independently from the fused ML model on the UE side Such as uninterpretable features, and / or

[0299] • Association of each observed multipath with a virtual anchor point / reflector in the environment, e.g., virtual anchor point based positioning techniques.

[0300] In some designs, the ML model used to extract UL features This could be, for example:

[0301] · Option 1 : Run on the TRP side to extract features, and / or

[0302] · Option 2 : Run on the LMF side to extract features, and / or

[0303] · Option 3 : Further split between TRP and LMF, where LMF can apply further processing to the features extracted by TRP.

[0304] In some designs, the TRP feature extraction model And UE feature fusion model f θ This could be, for example:

[0305] · Option 1 : Offline training by UE vendor → UE updates TRP for model ID using capability exchange, TRP vendor retrieves structure and parameters of model from public repository; UE may also update TRP for model details using capability messaging, and / or

[0306] · Option 2 : Trained offline by TRP vendor → NW updates UE for model ID using assistance data, UE vendor retrieves structure and parameters of model from public repository; NW may also update UE for model details using assistance information messaging, and / or

[0307] · Option 3 : Offline training through coordination between UE and TRP provider → Switching between different models can be done by exchanging model ID or model details using UE Capability Messaging and Assistance Information Messaging, and / or

[0308] · Option 4 : Online training → UE, TRP and (possibly) LMF involve online training / refinement.

[0309] Various aspects of the present disclosure relate to round-trip network-based and RFFP-based positioning estimates.Such aspects may provide various technical advantages, such as improved positioning estimates.

[0310] Fig.18 An exemplary process 1800 of communicating according to an aspect of the present disclosure is illustrated. Fig.18 Process 1800 is performed by a TRP (e.g., BS 302 or an O-RAN component).

[0311] refer to Fig.18 At 1810, the TRP (eg, receiver 352 or 362, network transceiver 380, etc.) requests to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate for a user equipment (UE).

[0312] refer to Fig.18 At 1820, the TRP (eg, transmitter 354 or 364, etc.) sends a downlink reference signal for positioning (RS-P) to the UE in response to the request.

[0313] refer to Fig.18 At 1830, the TRP (e.g., receiver 352 or 364, etc.) receives an uplink RS-P from the UE in response to the request. It should be understood that the operations at 1820 and 1830 can occur in any order (e.g., uplink RS-P followed by downlink RS-P, or downlink RS-P followed by uplink RS-P).

[0314] refer to Fig.18 , at 1840, the TRP (e.g., positioning component 388, processor 384, etc.) obtains the uplink RFFP of the uplink RS-P as measured at the TRP.

[0315] refer to Fig.18 At 1850, the TRP (eg, receiver 352 or 364, etc.) receives downlink RFFP measurement information (eg, DL RFFP, extracted features, etc.) associated with the downlink RS-P as measured at the UE.

[0316] refer to Fig.18In some designs, the TRP may further extract one or more features associated with the uplink RFFP via one or more network-based machine learning (ML) feature extraction models, or alternatively may send the uplink RFFP to a network location estimation entity (e.g., for feature extraction thereon). In some designs, the downlink RFFP measurement information may include the downlink RFFP as measured at the UE. In some designs, the TRP may further extract one or more features associated with the downlink RFFP via one or more network-based machine learning (ML) feature extraction models, or alternatively may send the downlink RFFP to a network location estimation entity (e.g., for feature extraction thereon).

[0317] refer to Fig.18 In some designs, the TRP may further obtain a first set of features associated with the uplink RFFP and a second set of features associated with the downlink RFFP measurement information, and may provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate for the UE. In some designs, the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0318] Fig.19 An exemplary process 1900 of communicating according to an aspect of the present disclosure is illustrated. Fig.19 Process 1900 is performed by a network positioning estimation entity such as a TRP (e.g., BS 302 or an O-RAN component), a network entity 306 such as an LMF integrated with or remote from the TRP, or the like.

[0319] refer to Fig.19 At 1910, the network positioning estimation entity (e.g., network transceiver 380 or 390, positioning component 388 or 398, receiver 352 or 362, etc.) obtains a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint (RFFP) being associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE). In a specific example, the network positioning estimation entity obtains a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by the user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE).

[0320] refer to Fig.19 At 1920, the network positioning estimation entity (e.g., network transceiver 380 or 390, positioning component 388 or 398, receiver 352 or 362, etc.) obtains a second set of features associated with one or more round-trip radio frequency fingerprints (RFFPs) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE. In a specific example, the network positioning estimation entity obtains a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFPs) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE.

[0321] refer to Fig.19 At 1320, the network positioning estimation entity (e.g., positioning component 388 or 398, processor 388 or 398, etc.) provides the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE. In a specific example, the network positioning estimation entity provides the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0322] refer to Fig.19 In some designs, the first set of features is extracted at the network positioning estimation entity or the one or more transmit receive points (TRPs) or one or more other UEs, or the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE or the one or more other UEs, or a combination thereof. In a specific example, the first set of features is extracted at the network positioning estimation entity or the one or more TRPs, or the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE, or a combination thereof. In some designs, the network positioning estimation entity corresponds to a transmit receive point (TRP), or the network positioning estimation entity corresponds to a location management function (LMF). In a specific example, the network positioning estimation entity corresponds to a corresponding TRP in the one or more TRPs, or the network positioning estimation entity corresponds to a location management function (LMF).

[0323] Fig. 20 The various aspects of the present disclosure are respectively illustrated. Figure 18 to Figure 19 The example implementation 2000 of the processes 1800 to 1900 is described in detail. In particular, Fig. 20 A communication framework depicting round-trip network-based and RFFP-based positioning estimation is illustrated. Fig. 20 , a UE 302, a TRP 304, and a LMF (eg, integrated in one of the TRPs 304 or in a remote entity such as a network entity 306) are depicted.

[0324] refer to Fig. 20 , UE 302 includes ML model DLk ψ (.) 2002, TRP 304 including ML model ULg φ (.) 2004, and optionally includes an ML model f θ (.) 2006-A, and LMF 304, 306 optionally includes ML model f θ (.) 2006-B. On the one hand, the ML model f θ (.)2006-A and ML model f θ (.) 2006-B is optional, as these respective feature fusion models may be implemented at either entity (i.e., TRP or LMF) or both. At 2010, LMF 304, 306 sends a request for UL and DL resources for a round trip (or RTT) RFFP positioning estimation session. At 2012, TRP 304 sends a DL RS (e.g., DL PRS) to UE 302. At 2014, UE 302 sends a UL RS (e.g., SRS) to TRP 304. As described above, operations 2012 to 2014 may occur in any order. Optionally, at UE 302, via ML model DLk ψ (.) 2002 extracts features from the DL RFFP of the DL RS. At 2016, the extracted features are optionally transmitted by UE 302 to TRP 304. Alternatively, at 2018, UE 302 may alternatively provide the DL RFFP, in which case it may be provided via the ML model ULg φ (.)2004 implements feature extraction at 304. In some designs, the ML model f θ (.) 2006-A may be used to derive a location estimate for UE 302. Alternatively, to facilitate the use of the ML model f θ (.) 2006-B Positioning estimate at LMF 304, 306, TRP 304 may optionally send DL RFFP and / or UL RFFP to LMF 304, 306 at 2020, and / or may optionally send extracted UL features and / or extracted DL features to LMF 304, 306. In some designs, UL and DL resources for DL ​​RS at 2012 and / or UL RS at 2014 may be arranged close together in time (e.g., in the same time slot, or within a threshold number of symbols, etc.) to improve positioning estimate accuracy.

[0325] refer to Fig. 20 , ML model DLk ψ (.)2002 and ML model ULg φ(.)2004 is a feature extraction model. ML model DLk ψ (.)2002 is a feature extraction model that accepts DL RFFP (based on the DL RS or DL ​​PRS) as input and outputs the extracted DL features. ML model ULg φ (.) 2004 is a feature extraction model that accepts UL RFFP (based on the UL RS or SRS) as input and outputs the extracted UL features. ML model f θ (.)2006-A and ML model f θ (.)2006-B is a feature fusion model. ML model f θ (.)2006-A and ML model f θ (.) 2006-B accepts the extracted UL features or the UL RFFP (or UL extracted features) and / or the DL RFFP (or DL ​​extracted features) as input and outputs an estimated positioning of the UE 302. As described above, the ML model f θ (.)2006-A and ML model f θ (.)2006-B fuses the features together into the estimated positioning, but may also include a feature extraction component for processing the UL RFFP and / or the DL RFFP.

[0326] refer to Fig. 20 In some designs, for the network-based RT-RFFP method, the network utilizes the DL RFFPP features (or extracted DL features) corresponding to the DL RS reported by the DL RS and the observed UL-RFFP features (or UL extracted features) reported from the TRP, and performs feature fusion, and infers the UE positioning.

[0327] For example, one candidate architecture that facilitates such localization estimation can be expressed as: Where p is the position, is the extracted feature at the UE, k ψ (·) is the UE ML feature extraction model, is the extracted feature at TRP i, g φ (·) is the TRP ML feature extraction model, and f θ (·) is a network ML model that utilizes all features reported / observed from the TRP and features reported from the UE, and performs feature fusion, and infers the UE positioning.

[0328] In some designs, the UL features calculated (e.g., extracted) by the TRP may use a TRP-specific ML model or a common processing ML model. In some designs, UL feature extraction may be optional, and It can be a UL channel, i.e. In some designs, DL feature extraction may be optional, and It can be a DL channel, i.e. In some designs, the timing of the UL and DL resources used in RT-RFFP positioning needs to be close in time.

[0329] Some examples of DL extraction features reported by the UE may include, for example:

[0330] Multipath delays + angles generated by ML / classical methods for the DL channel, e.g. mapped to existing reported decipherable features (which the NW can still leverage to feed back into generating the DL RFFP), and / or

[0331] Latent features generated by the UE feature processing ML model jointly trained with the fusion ML model on the NW side Such as uninterpretable features, and / or

[0332] Latent features generated by a UE feature processing ML model trained jointly with at least the UL feature processing ML model (i.e., running on the TRP) and / or a fused ML model at the TRP and the server side Such as uninterpretable features, and / or

[0333] Latent features generated by the UE feature processing ML model trained independently from the fused ML model on the NW side Such as uninterpretable features, and / or

[0334] • Association of each observed multipath with a virtual anchor point / reflector in the environment, e.g., virtual anchor point based positioning techniques.

[0335] Some examples of UL extraction features reported by the TRP to the server (e.g., LMF) side may include, for example:

[0336] Multipath delays + angles generated by ML / classical methods for the UL channel, e.g. mapped to existing reported decipherable features (which the server can still use to feed back generation of the UL RFFP), and / or

[0337] Latent features generated by a per-TRP feature processing ML model trained jointly with the fusion ML model on the server side Such as uninterpretable features, and / or

[0338] Latent features generated by a per-TRP feature processing ML model trained jointly with at least a DL feature processing ML model (i.e., running at the UE) and a fusion ML model on the server side Such as uninterpretable features, and / or

[0339] Latent features generated by a per-TRP feature processor (e.g., autoencoder) trained independently from the server-side fused ML model For example, uninterpretable features, and / or

[0340] • Association of each observed multipath with a virtual anchor point / reflector in the environment, e.g., virtual anchor point based positioning techniques.

[0341] In some designs, the fusion ML model f θ (·) can be, for example:

[0342] · Option 1 : running on the TRP side, and / or

[0343] · Option 2 : Run on the server (e.g., LMF) side

[0344] In some designs, the TRP feature extraction model and UE feature extraction model k ψ (·) and the fusion model f θ This could be, for example:

[0345] · Option 1 : Offline training by the UE vendor, e.g. the UE updates the TRP for the model ID using capability exchange, and the TRP vendor retrieves the structure and parameters of the model from a public repository;

[0346] UE can also update TRP for model details using capability messaging

[0347] · Option 2 : Offline training by TRP vendor, e.g. NW updates UE for model ID using assistance data, UE vendor retrieves the structure and parameters of the model from a public repository; NW may also update UE for model details using assistance information messaging

[0348] · Option 3 : Offline training via coordination between UE and TRP provider, e.g. switching between different models can be done by exchanging model ID or model details using UE Capability Messaging and Assistance Information Messaging [Most likely]

[0349] · Option 4 : Online training, e.g. UE, TRP and (possibly) LMF involve online training / refinement

[0350] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each subordinate clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. Various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0351] Specific implementation examples are described in the following numbered clauses:

[0352] Clause 1. A method of operating a user equipment (UE), the method comprising: sending an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); receiving one or more features associated with the uplink RS-P, the one or more features being extracted from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P by one or more network components via one or more network-based machine learning (ML) feature extraction models; and determining a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0353] Clause 2. The method of clause 1, wherein the one or more features are extracted by the one or more TRPs.

[0354] Clause 3. The method of clause 2, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0355] Clause 4. A method according to any one of clauses 1 to 3, wherein the one or more features are extracted by a network position estimation entity.

[0356] Clause 5. A method according to any one of clauses 1 to 4, wherein the one or more features include a first set of features extracted by the one or more TRPs via a first set of network-based ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of network-based ML feature extraction models.

[0357] Clause 6. A method as described in any of clauses 1 to 5, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0358] Clause 7. A method according to any one of clauses 1 to 6, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0359] Clause 8. A method of operating a network component; obtaining from a user equipment (UE) one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs); extracting one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and sending one or more extracted features to one or more target devices.

[0360] Clause 9. A method according to clause 8, wherein the network component corresponds to measuring the uplink RS-P to obtain a corresponding TRP of a corresponding uplink RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0361] Clause 10. A method according to any one of clauses 8 to 9, wherein the network component corresponds to a network position estimation entity that receives the RFFP measurement information from the one or more TRPs, and wherein the one or more target devices include the one or more TRPs.

[0362] Clause 11. A method as described in any of clauses 8 to 10, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0363] Clause 12. A method according to any one of clauses 8 to 11, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0364] Clause 13. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs) via the at least one transceiver; receive one or more features associated with the uplink RS-P via the at least one transceiver, the one or more features being extracted from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P by one or more network components via one or more network-based machine learning (ML) feature extraction models; and determine a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0365] Clause 14. A UE according to clause 13, wherein the one or more features are extracted by the one or more TRPs.

[0366] Clause 15. The UE of clause 14, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0367] Clause 16. A UE as described in any of clauses 13 to 15, wherein the one or more features are extracted by a network position estimation entity.

[0368] Clause 17. A UE according to any of clauses 13 to 16, wherein the one or more features include a first set of features extracted by the one or more TRPs via a first set of network-based ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of network-based ML feature extraction models.

[0369] Clause 18. A UE as set forth in any of clauses 13 to 17, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0370] Clause 19. A UE according to any one of clauses 13 to 18, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0371] Clause 20. A network component comprising: a memory; at least one transceiver; and at least one processor, the processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain from a user equipment (UE) one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs); extract one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and send the one or more extracted features to one or more target devices via the at least one transceiver.

[0372] Clause 21. A network component according to clause 20, wherein the network component corresponds to measuring the uplink RS-P to obtain a corresponding TRP of a corresponding uplink RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0373] Clause 22. A network component according to any one of clauses 20 to 21, wherein the network component corresponds to a network position estimation entity that receives the RFFP measurement information from the one or more TRPs, and wherein the one or more target devices include the one or more TRPs.

[0374] Clause 23. A network component as described in any of clauses 20 to 22, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0375] Clause 24. A network component according to any one of clauses 20 to 23, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0376] Clause 25. A user equipment (UE), comprising: a component for sending an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); a component for receiving one or more features associated with the uplink RS-P, the one or more features being extracted from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P by one or more network components via one or more network-based machine learning (ML) feature extraction models; and a component for determining a positioning estimate of the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0377] Clause 26. A UE according to clause 25, wherein the one or more features are extracted by the one or more TRPs.

[0378] Clause 27. The UE of clause 26, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0379] Clause 28. A UE as described in any of clauses 25 to 27, wherein the one or more features are extracted by a network position estimation entity.

[0380] Clause 29. A UE according to any of clauses 25 to 28, wherein the one or more features include a first set of features extracted by the one or more TRPs via a first set of network-based ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of network-based ML feature extraction models.

[0381] Clause 30. A UE as set forth in any of clauses 25 to 29, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0382] Clause 31. A UE according to any one of clauses 25 to 30, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0383] Clause 32. A network component comprising: a component for obtaining one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs) from a user equipment (UE); a component for extracting one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and a component for sending one or more extracted features to one or more target devices.

[0384] Clause 33. A network component according to clause 32, wherein the network component corresponds to measuring the uplink RS-P to obtain a corresponding TRP of a corresponding uplink RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0385] Clause 34. A network component according to any one of clauses 32 to 33, wherein the network component corresponds to a network position estimation entity that receives the RFFP measurement information from the one or more TRPs, and wherein the one or more target devices include the one or more TRPs.

[0386] Clause 35. A network component as set forth in any of clauses 32 to 34, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0387] Clause 36. A network component according to any one of clauses 32 to 35, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0388] Clause 37. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: send an uplink reference signal for positioning (RS-P) to one or more transmit receive points (TRPs); receive one or more features associated with the uplink RS-P, the one or more features extracted by one or more network components from one or more uplink radio frequency fingerprints (RFFPs) of the uplink RS-P via one or more network-based machine learning (ML) feature extraction models; and determine a positioning estimate for the UE based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

[0389] Clause 38. A non-transitory computer-readable medium as described in Clause 37, wherein the one or more features are extracted by the one or more TRPs.

[0390] Clause 39. The non-transitory computer-readable medium of Clause 38, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0391] Clause 40. The non-transitory computer-readable medium of any one of clauses 37 to 39, wherein the one or more features are extracted by a network location estimation entity.

[0392] Clause 41. A non-transitory computer-readable medium according to any one of clauses 37 to 40, wherein the one or more features include a first set of features extracted by the one or more TRPs via a first set of network-based ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of network-based ML feature extraction models.

[0393] Clause 42. The non-transitory computer-readable medium of any one of clauses 37 to 41, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0394] Clause 43. A non-transitory computer-readable medium according to any one of clauses 37 to 42, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0395] Clause 44. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a network component, cause the network component to: obtain from a user equipment (UE) one or more uplink radio frequency fingerprints (RFFPs) associated with an uplink reference signal for positioning (RS-P) as measured at one or more transmit receive points (TRPs); extract one or more features associated with the one or more uplink RFFPs via one or more network-based machine learning (ML) feature extraction models; and send one or more extracted features to one or more target devices.

[0396] Clause 45. A non-transitory computer-readable medium according to clause 44, wherein the network component corresponds to measuring the uplink RS-P to obtain a corresponding TRP of a corresponding uplink RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0397] Clause 46. A non-transitory computer-readable medium as described in any of clauses 44 to 45, wherein the network component corresponds to a network location estimation entity that receives the RFFP measurement information from the one or more TRPs, and wherein the one or more target devices include the one or more TRPs.

[0398] Clause 47. The non-transitory computer-readable medium of any one of clauses 44 to 46, wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0399] Clause 48. A non-transitory computer-readable medium according to any one of clauses 44 to 47, wherein the one or more features include multipath delay and angle features, potential TRP-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0400] Additional specific implementation examples are described in the following numbered additional clauses:

[0401] Additional clause 1. A method of operating a user equipment (UE), the method comprising: receiving one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs); sending an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receiving uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; obtaining one or more downlink RFFPs associated with the one or more downlink RS-Ps; and providing the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0402] Additional clause 2. A method according to additional clause 1, wherein the one or more downlink RS-Ps correspond to a downlink positioning reference signal (PRS), and wherein the uplink RS-Ps correspond to an uplink sounding reference signal (SRS).

[0403] Additional clause 3. A method according to any one of additional clauses 1 to 2, wherein the uplink RFFP measurement information comprises one or more uplink RFFPs of the uplink SRS.

[0404] Additional clause 4. A method according to additional clause 3, wherein the UE-based ML feature fusion model includes a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the uplink RS-P based on the one or more uplink RFFPs.

[0405] Additional clause 5. A method according to any one of additional clauses 1 to 4, wherein the uplink RFFP measurement information includes one or more features extracted from one or more uplink RFFPs via one or more network-based ML feature extraction models at the one or more TRPs.

[0406] Additional clause 6. The method according to additional clause 5, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0407] Additional clause 7. A method of operating a transmit receive point (TRP), the method comprising: receiving a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; receiving an uplink RS-P from the UE in response to the request; obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and sending uplink RFFP measurement information associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0408] Additional clause 8. A method according to additional clause 7, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0409] Additional clause 9. A method according to any one of additional clauses 7 to 8, wherein the uplink RFFP measurement information comprises the uplink RFFP.

[0410] Additional clause 10. A method according to any one of additional clauses 7 to 9, wherein the uplink RFFP measurement information comprises one or more features extracted from the uplink RFFP via one or more network-based ML feature extraction models.

[0411] Additional clause 11. The method according to additional clause 10, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0412] Additional clause 12. A method according to any of additional clauses 10 to 11, wherein the one or more features are extracted from the uplink RFFP at the TRP or network position estimation entity.

[0413] Additional clause 13. A method of operating a transmit receive point (TRP), the method comprising: receiving a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; receiving an uplink RS-P from the UE in response to the request; obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and receiving downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0414] Additional Clause 14. The method according to Additional Clause 13 further comprises: extracting one or more features associated with the uplink RFFP via one or more network-based machine learning (ML) feature extraction models, or sending the uplink RFFP to a network positioning estimation entity.

[0415] Additional clause 15. A method according to any of additional clauses 13 to 14, wherein the downlink RFFP measurement information comprises a downlink RFFP as measured at the UE.

[0416] Additional Clause 16. The method according to Additional Clause 15 further comprises: extracting one or more features associated with the downlink RFFP via one or more network-based machine learning (ML) feature extraction models, or sending the downlink RFFP to a network positioning estimation entity.

[0417] Additional clause 17. According to the method described in any one of additional clauses 13 to 16, the method also includes: obtaining a first set of features associated with the uplink RFFP and a second set of features associated with the downlink RFFP measurement information; and providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0418] Additional clause 18. A method according to any one of additional clauses 13 to 17, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0419] Additional clause 19. A method for operating a network positioning estimation entity, the method comprising: obtaining a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtaining a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFPs) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0420] Additional clause 20. A method according to additional clause 19, wherein the first set of features is extracted at the network positioning estimation entity or the one or more TRPs, or wherein the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE, or a combination thereof.

[0421] Additional clause 21. A method according to any one of additional clauses 19 to 20, wherein the network positioning estimation entity corresponds to a corresponding TRP among the one or more TRPs, or wherein the network positioning estimation entity corresponds to a location management function (LMF).

[0422] Additional clause 22. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs) via the at least one transceiver; send an uplink RS-P to the one or more TRPs via the at least one transceiver, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs via the at least one transceiver; obtain one or more downlink RFFPs associated with the one or more downlink RS-Ps; and provide the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0423] Additional clause 23. A UE according to additional clause 22, wherein the one or more downlink RS-Ps correspond to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0424] Additional clause 24. A UE according to any of additional clauses 22 to 23, wherein the uplink RFFP measurement information comprises one or more uplink RFFPs of the uplink SRS.

[0425] Additional clause 25. A UE according to additional clause 24, wherein the UE-based ML feature fusion model includes a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the uplink RS-P based on the one or more uplink RFFPs.

[0426] Additional clause 26. A UE according to any of additional clauses 22 to 25, wherein the uplink RFFP measurement information comprises one or more features extracted from one or more uplink RFFPs via one or more network-based ML feature extraction models at the one or more TRPs.

[0427] Additional clause 27. A UE according to additional clause 26, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0428] Additional clause 28. A transmit receive point (TRP), the transmit receive point (TRP) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); send, via the at least one transceiver in response to the request, a downlink reference signal for positioning (RS-P) to the UE; receive, via the at least one transceiver from the UE in response to the request, an uplink RS-P; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and send, via the at least one transceiver, uplink RFFP measurement information associated with the uplink RFFP to the UE via a UE-based machine learning (ML) feature fusion model for UE-based positioning estimation.

[0429] Additional clause 29. A TRP according to additional clause 28, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0430] Additional clause 30. A TRP according to any one of additional clauses 28 to 29, wherein the uplink RFFP measurement information includes the uplink RFFP.

[0431] Additional clause 31. A TRP according to any of additional clauses 28 to 30, wherein the uplink RFFP measurement information includes one or more features extracted from the uplink RFFP via one or more network-based ML feature extraction models.

[0432] Additional Clause 32. A TRP according to Additional Clause 31, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0433] Additional clause 33. A TRP according to any of additional clauses 31 to 32, wherein the one or more features are extracted from the uplink RFFP at the TRP or network position estimation entity.

[0434] Additional clause 34. A TRP, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); send, via the at least one transceiver in response to the request, a downlink reference signal for positioning (RS-P) to the UE; receive, via the at least one transceiver in response to the request, an uplink RS-P from the UE; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and receive, via the at least one transceiver, downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0435] Additional Clause 35. A TRP according to Additional Clause 34, wherein the at least one processor is further configured to: extract one or more features associated with the uplink RFFP via one or more network-based machine learning (ML) feature extraction models, or send the uplink RFFP to a network positioning estimation entity via the at least one transceiver.

[0436] Additional clause 36. A TRP according to any of additional clauses 34 to 35, wherein the downlink RFFP measurement information includes the downlink RFFP as measured at the UE.

[0437] Additional Clause 37. A TRP according to Additional Clause 36, wherein the at least one processor is further configured to: extract one or more features associated with the downlink RFFP via one or more network-based machine learning (ML) feature extraction models, or send the downlink RFFP to a network positioning estimation entity via the at least one transceiver.

[0438] Additional clause 38. A TRP according to any one of additional clauses 34 to 37, wherein the at least one processor is further configured to: obtain a first set of features associated with the uplink RFFP and a second set of features associated with the downlink RFFP measurement information; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0439] Additional clause 39. A TRP according to any one of additional clauses 34 to 38, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0440] Additional clause 40. A network positioning estimation entity, the network positioning estimation entity comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFPs) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0441] Additional clause 41. A network positioning estimation entity according to additional clause 40, wherein the first set of features is extracted at the network positioning estimation entity or the one or more TRPs, or wherein the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE, or a combination thereof.

[0442] Additional clause 42. A network positioning estimation entity according to any one of Additional clauses 40 to 41, wherein the network positioning estimation entity corresponds to a corresponding TRP among the one or more TRPs, or wherein the network positioning estimation entity corresponds to a location management function (LMF).

[0443] Additional clause 43. A user equipment (UE), comprising: a component for receiving one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs); a component for sending an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; a component for receiving uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; a component for obtaining one or more downlink RFFPs associated with the one or more downlink RS-Ps; and a component for providing the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0444] Additional clause 44. A UE according to additional clause 43, wherein the one or more downlink RS-Ps correspond to downlink positioning reference signals (PRS), and wherein the uplink RS-Ps correspond to uplink sounding reference signals (SRS).

[0445] Additional clause 45. A UE as set forth in any of additional clauses 43 to 44, wherein the uplink RFFP measurement information comprises one or more uplink RFFPs of the uplink SRS.

[0446] Additional clause 46. A UE according to additional clause 45, wherein the UE-based ML feature fusion model includes a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the uplink RS-P based on the one or more uplink RFFPs.

[0447] Additional clause 47. A UE according to any of additional clauses 43 to 46, wherein the uplink RFFP measurement information comprises one or more features extracted from one or more uplink RFFPs via one or more network-based ML feature extraction models at the one or more TRPs.

[0448] Additional clause 48. A UE according to additional clause 47, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0449] Additional clause 49. A transmit receive point (TRP), the transmit receive point (TRP) comprising: a component for receiving a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); a component for sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; a component for receiving an uplink RS-P from the UE in response to the request; a component for obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and a component for sending uplink RFFP measurement information associated with the uplink RFFP to the UE for UE-based positioning estimation via a UE-based machine learning (ML) feature fusion model.

[0450] Additional clause 50. A TRP according to additional clause 49, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0451] Additional clause 51. A TRP according to any one of additional clauses 49 to 50, wherein the uplink RFFP measurement information includes the uplink RFFP.

[0452] Additional clause 52. A TRP according to any one of additional clauses 49 to 51, wherein the uplink RFFP measurement information includes one or more features extracted from the uplink RFFP via one or more network-based ML feature extraction models.

[0453] Additional clause 53. A TRP according to additional clause 52, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0454] Additional clause 54. A TRP according to any of additional clauses 52 to 53, wherein the one or more features are extracted from the uplink RFFP at the TRP or a network position estimation entity.

[0455] Additional clause 55. A TRP, comprising: a component for receiving a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate of a user equipment (UE); a component for sending a downlink reference signal for positioning (RS-P) to the UE in response to the request; a component for receiving an uplink RS-P from the UE in response to the request; a component for obtaining an uplink RFFP of the uplink RS-P as measured at the TRP; and a component for receiving downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0456] Additional Clause 56. According to the TRP described in Additional Clause 55, the method also includes: a component for extracting one or more features associated with the uplink RFFP via one or more network-based machine learning (ML) feature extraction models, or a component for sending the uplink RFFP to a network positioning estimation entity.

[0457] Additional clause 57. A TRP according to any of additional clauses 55 to 56, wherein the downlink RFFP measurement information includes the downlink RFFP as measured at the UE.

[0458] Additional Clause 58. According to the TRP described in Additional Clause 57, the method also includes: a component for extracting one or more features associated with the downlink RFFP via one or more network-based machine learning (ML) feature extraction models, or a component for sending the downlink RFFP to a network positioning estimation entity.

[0459] Additional Clause 59. According to a TRP described in any one of Additional Clauses 55 to 58, the method further includes: a component for obtaining a first set of features associated with the uplink RFFP and a second set of features associated with the downlink RFFP measurement information; and a component for providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0460] Additional clause 60. A TRP according to any one of additional clauses 55 to 59, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0461] Additional clause 61. A network positioning estimation entity, comprising: a component for obtaining a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); a component for obtaining a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFP) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and a component for providing the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0462] Additional clause 62. A network positioning estimation entity according to additional clause 61, wherein the first set of features is extracted at the network positioning estimation entity or at the one or more TRPs, or wherein the second set of features is extracted at the network positioning estimation entity or at the one or more TRPs or at the UE, or a combination thereof.

[0463] Additional clause 63. A network positioning estimation entity according to any one of Additional clauses 61 to 62, wherein the network positioning estimation entity corresponds to a corresponding TRP among the one or more TRPs, or wherein the network positioning estimation entity corresponds to a location management function (LMF).

[0464] Additional clause 64. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), causes the UE to: receive one or more downlink reference signals (RS-Ps) for positioning from one or more transmit receive points (TRPs); send an uplink RS-P to the one or more TRPs, the one or more downlink RS-Ps and the uplink RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive uplink RFFP measurement information associated with the uplink RS-P as measured at the one or more TRPs; obtain one or more downlink RFFPs associated with the one or more downlink RS-Ps; and provide the uplink RFFP measurement information and the one or more downlink RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0465] Additional clause 65. A non-transitory computer-readable medium according to additional clause 64, wherein the one or more downlink RS-Ps correspond to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0466] Additional clause 66. The non-transitory computer readable medium of any of additional clauses 64 to 65, wherein the uplink RFFP measurement information comprises one or more uplink RFFPs of the uplink SRS.

[0467] Additional clause 67. A non-transitory computer-readable medium according to additional clause 66, wherein the UE-based ML feature fusion model includes a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the uplink RS-P based on the one or more uplink RFFPs.

[0468] Additional clause 68. A non-transitory computer-readable medium as described in any of additional clauses 64 to 67, wherein the uplink RFFP measurement information includes one or more features extracted from one or more uplink RFFPs via one or more network-based ML feature extraction models at the one or more TRPs.

[0469] Additional clause 69. A non-transitory computer-readable medium according to additional clause 68, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0470] Additional clause 70. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a transmit receive point (TRP), cause the TRP to: receive a request to perform a UE-based round-trip radio frequency fingerprinting (RFFP) positioning estimation session for a user equipment (UE); send a downlink reference signal for positioning (RS-P) to the UE in response to the request; receive an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and send uplink RFFP measurement information associated with the uplink RFFP to the UE for UE-based positioning estimation via a UE-based machine learning (ML) feature fusion model.

[0471] Additional clause 71. A non-transitory computer-readable medium according to additional clause 70, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0472] Additional clause 72. The non-transitory computer-readable medium of any one of additional clauses 70 to 71, wherein the uplink RFFP measurement information comprises the uplink RFFP.

[0473] Additional clause 73. A non-transitory computer-readable medium as described in any of additional clauses 70 to 72, wherein the uplink RFFP measurement information includes one or more features extracted from the uplink RFFP via one or more network-based ML feature extraction models.

[0474] Additional clause 74. A non-transitory computer-readable medium according to additional clause 73, wherein the one or more network-based ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0475] Additional clause 75. A non-transitory computer readable medium as described in any of additional clauses 73 to 74, wherein the one or more features are extracted from the uplink RFFP at the TRP or network position estimation entity.

[0476] Additional clause 76. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a TRP, cause the TRP to: receive a request to perform a network-based round-trip radio frequency fingerprinting (RFFP) positioning estimate for a user equipment (UE); send a downlink reference signal for positioning (RS-P) to the UE in response to the request; receive an uplink RS-P from the UE in response to the request; obtain an uplink RFFP of the uplink RS-P as measured at the TRP; and receive downlink RFFP measurement information associated with the downlink RS-P as measured at the UE.

[0477] Additional Clause 77. A non-transitory computer-readable medium according to Additional Clause 76, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the TRP, cause the TRP to: extract one or more features associated with the uplink RFFP via one or more network-based machine learning (ML) feature extraction models, or send the uplink RFFP to a network positioning estimation entity.

[0478] Additional clause 78. The non-transitory computer-readable medium of any of additional clauses 76 to 77, wherein the downlink RFFP measurement information comprises a downlink RFFP as measured at the UE.

[0479] Additional Clause 79. A non-transitory computer-readable medium according to Additional Clause 78, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the TRP, cause the TRP to: extract one or more features associated with the downlink RFFP via one or more network-based machine learning (ML) feature extraction models, or send the downlink RFFP to a network positioning estimation entity.

[0480] Additional clause 80. A non-transitory computer-readable medium according to any one of additional clauses 76 to 79, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the TRP, cause the TRP to: obtain a first set of features associated with the uplink RFFP and a second set of features associated with the downlink RFFP measurement information; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0481] Additional clause 81. A non-transitory computer-readable medium according to any one of additional clauses 76 to 80, wherein the downlink RS-P corresponds to a downlink positioning reference signal (PRS), and wherein the uplink RS-P corresponds to an uplink sounding reference signal (SRS).

[0482] Additional clause 82. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a network positioning estimation entity, cause the network positioning estimation entity to: obtain a first set of features associated with an uplink round-trip radio frequency fingerprint (RFFP), the uplink round-trip radio frequency fingerprint (RFFP) being associated with an uplink reference signal for positioning (RS-P) sent by a user equipment (UE) to one or more transmit receive points (TRPs), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtain a second set of features associated with one or more downlink round-trip radio frequency fingerprints (RFFPs) sent by the one or more TRPs to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and provide the first set of features and the second set of features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0483] Additional clause 83. A non-transitory computer-readable medium according to additional clause 82, wherein the first set of features is extracted at the network positioning estimation entity or the one or more TRPs, or wherein the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE, or a combination thereof.

[0484] Additional clause 84. A non-transitory computer-readable medium according to any one of additional clauses 82 to 83, wherein the network positioning estimation entity corresponds to a corresponding TRP among the one or more TRPs, or wherein the network positioning estimation entity corresponds to a location management function (LMF).

[0485] Additional additional specific implementation examples are described in the following numbered additional clauses:

[0486] Additional additional clauses 1. A method of operating a network component, the method comprising: receiving one or more features associated with one or more downlink reference signals (RS-P) for positioning sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFP) of the one or more downlink RS-Ps; and providing the one or more features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0487] Additional clause 2. A method according to additional clause 1, wherein the network component corresponds to a corresponding TRP in the one or more TRPs that sends the one or more downlink RS-Ps.

[0488] Additional clause 3. The method of additional clause 2, wherein the one or more features are received from the UE.

[0489] Additional clause 4. A method as described in any of additional clauses 2 to 3, further comprising: sending the positioning estimate to a network positioning estimation entity.

[0490] Additional clause 5. A method according to any one of additional clauses 2 to 4, wherein the one or more ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0491] Additional clause 6. A method according to any of additional clauses 1 to 5, wherein the network component corresponds to a network position estimation entity.

[0492] Additional clause 7. A method according to any one of additional clauses 1 to 6, wherein the one or more features are received from at least one TRP of the one or more TRPs.

[0493] Additional clause 8. A method according to additional clause 7, wherein the one or more features include a first set of features extracted by the UE via a UE-based ML feature extraction model, or wherein the one or more features include a second set of features extracted by the at least one TRP, the second set of features including one or more enhanced features from at least one network-side ML feature extraction model that accepts the first set of features as input, or a combination thereof.

[0494] Additional clause 9. A method according to any one of additional clauses 1 to 8, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0495] Additional clause 10. A method according to any one of additional clauses 1 to 9, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with the network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0496] Additional clause 11. A method of operating a user equipment (UE), the method comprising: receiving one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs); obtaining one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extracting one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and sending the one or more features.

[0497] Additional clause 12. A method according to additional clause 11, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0498] Additional clause 13. A method according to any one of additional clauses 11 to 12, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with a network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0499] Additional clause 14. A network component comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, one or more features associated with one or more downlink reference signals (RS-P) for positioning sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps; and provide the one or more features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0500] Additional clause 15. A network component according to additional clause 14, wherein the network component corresponds to a corresponding TRP in the one or more TRPs that sends the one or more downlink RS-Ps.

[0501] Additional clause 16. The network component of additional clause 15, wherein the one or more characteristics are received from the UE.

[0502] Further additional clause 17. A network component according to any of further additional clauses 15 to 16, wherein the at least one processor is further configured to: send the positioning estimate via the at least one transceiver to a network positioning estimation entity.

[0503] Additional clause 18. A network component according to any one of additional clauses 15 to 17, wherein the one or more ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0504] Additional clause 19. A network component according to any one of additional clauses 14 to 18, wherein the network component corresponds to a network position estimation entity.

[0505] Additional clause 20. A network component according to any of additional clauses 14 to 19, wherein the one or more features are received from at least one TRP of the one or more TRPs.

[0506] Additional clause 21. A network component according to additional clause 20, wherein the one or more features include a first set of features extracted by the UE via a UE-based ML feature extraction model, or wherein the one or more features include a second set of features extracted by the at least one TRP, the second set of features including one or more enhanced features from at least one network-side ML feature extraction model that accepts the first set of features as input, or a combination thereof.

[0507] Further additional clause 22. A network component according to any of further additional clauses 14 to 21, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0508] Additional clause 23. A network component according to any one of additional clauses 14 to 22, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with the network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0509] Additional clause 24. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more downlink reference signals (RS-P) for positioning from one or more transmit receive points (TRPs) via the at least one transceiver; obtain one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extract one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and send the one or more features via the at least one transceiver.

[0510] Additional clause 25. The UE according to additional clause 24, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0511] Additional clause 26. A UE according to any one of additional clauses 24 to 25, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with a network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0512] Additional clause 27. A network component comprising: a component for receiving one or more features associated with one or more downlink reference signals for positioning (RS-P) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFP) of the one or more downlink RS-Ps; and a component for providing the one or more features to a network-based ML feature fusion model to derive a positioning estimate of the UE.

[0513] Additional clause 28. A network component according to additional clause 27, wherein the network component corresponds to a corresponding TRP in the one or more TRPs that sends the one or more downlink RS-Ps.

[0514] Additional clause 29. The network component of additional clause 28, wherein the one or more characteristics are received from the UE.

[0515] Further additional clause 30. A network component as described in any of further additional clauses 28 to 29, further comprising means for sending the position estimate to a network position estimation entity.

[0516] Additional clause 31. A network component according to any of additional clauses 28 to 30, wherein the one or more ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0517] Further additional clause 32. A network component according to any of further additional clauses 27 to 31, wherein the network component corresponds to a network position estimation entity.

[0518] Further additional clause 33. A network component according to any of further additional clauses 27 to 32, wherein the one or more features are received from at least one TRP of the one or more TRPs.

[0519] Additional clause 34. A network component according to additional clause 33, wherein the one or more features include a first set of features extracted by the UE via a UE-based ML feature extraction model, or wherein the one or more features include a second set of features extracted by the at least one TRP, the second set of features including one or more enhanced features from at least one network-side ML feature extraction model that accepts the first set of features as input, or a combination thereof.

[0520] Further additional clause 35. A network component according to any of further additional clauses 27 to 34, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0521] Additional clause 36. A network component according to any one of additional clauses 27 to 35, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with the network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0522] Additional clause 37. A user equipment (UE), comprising: a component for receiving one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs); a component for obtaining one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; a component for extracting one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and a component for sending the one or more features.

[0523] Additional clause 38. A UE according to additional clause 37, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0524] Additional clause 39. A UE according to any one of additional clauses 37 to 38, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with a network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

[0525] Additional clause 40. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a network component, cause the network component to: receive one or more features associated with one or more downlink reference signals for positioning (RS-P) sent by one or more transmit receive points (TRPs) to a user equipment (UE), the one or more features being extracted by one or more devices via one or more machine learning (ML) feature extraction models from one or more downlink radio frequency fingerprints (RFFPs) of the one or more downlink RS-Ps; and provide the one or more features to a network-based ML feature fusion model to derive a positioning estimate for the UE.

[0526] Additional clause 41. A non-transitory computer-readable medium according to additional clause 40, wherein the network component corresponds to a corresponding TRP in the one or more TRPs that sends the one or more downlink RS-Ps.

[0527] Additional clause 42. The non-transitory computer-readable medium of additional clause 41, wherein the one or more characteristics are received from the UE.

[0528] Additional clause 43. A non-transitory computer-readable medium according to any one of additional clauses 41 to 42, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the network component, cause the network component to perform the following operations: send the positioning estimate to a network positioning estimation entity.

[0529] Additional clause 44. A non-transitory computer-readable medium according to any one of additional clauses 41 to 43, wherein the one or more ML feature extraction models include one or more TRP-specific ML feature extraction models or common ML feature extraction models.

[0530] Additional clause 45. The non-transitory computer readable medium of any one of additional clauses 40 to 44, wherein the network component corresponds to a network position estimation entity.

[0531] Additional clause 46. A non-transitory computer-readable medium as described in any of additional clauses 40 to 45, wherein the one or more features are received from at least one TRP of the one or more TRPs.

[0532] Additional additional clause 47. A non-transitory computer-readable medium according to additional additional clause 46, wherein the one or more features include a first set of features extracted by the UE via a UE-based ML feature extraction model, or wherein the one or more features include a second set of features extracted by the at least one TRP, the second set of features including one or more enhanced features from at least one network-side ML feature extraction model that accepts the first set of features as input, or a combination thereof.

[0533] Additional clause 48. A non-transitory computer readable medium as described in any of additional clauses 40 to 47, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0534] Additional clause 49. A non-transitory computer-readable medium according to any one of additional clauses 40 to 48, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with the network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0535] Additional clause 50. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive one or more downlink reference signals for positioning (RS-P) from one or more transmit receive points (TRPs); obtain one or more downlink radio frequency fingerprints (RFFPs) associated with the one or more downlink RS-Ps; extract one or more features from the one or more downlink RFFPs via one or more UE-based machine learning (ML) feature extraction models; and send the one or more features.

[0536] Additional clause 51. A non-transitory computer readable medium according to additional clause 50, wherein the one or more downlink RS-Ps correspond to one or more downlink positioning reference signals (PRS).

[0537] Additional clause 52. A non-transitory computer-readable medium according to any one of additional clauses 50 to 51, wherein the one or more features include multipath delay and angle features, potential TRP-specific features trained jointly with a network-based ML feature fusion model at a network-side training component, potential TRP-specific features trained independently of the network-based ML feature fusion model at the network-side training component, multipath features involving associations between multipaths and virtual anchor points or reflectors, or any combination thereof.

[0538] 1) Further additional specific implementation examples are described in the following numbered additional clauses: :

[0539] Further additional clauses 1. A method of operating a user equipment (UE), the method comprising: sending a reference signal (RS-P) for positioning; obtaining one or more features associated with the RS-P, the one or more features being extracted from one or more radio frequency fingerprints (RFFP) of the RS-P by one or more entities via one or more machine learning (ML) feature extraction models; and providing the one or more features to a UE-based ML feature fusion model to derive a positioning estimate of the UE.

[0540] Further additional clause 2. A method according to further additional clause 1, wherein the one or more features are extracted by the one or more transmit receive points (TRPs).

[0541] Further additional clause 3. The method according to further additional clause 2, wherein the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models.

[0542] Further additional clause 4. A method according to any one of further additional clauses 1 to 3, wherein the one or more features are extracted by a network position estimation entity.

[0543] Further additional clause 5. A method according to any one of further additional clauses 1 to 4, wherein the one or more features include a first set of features extracted by one or more transmit receive points (TRPs) via a first set of ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of ML feature extraction models.

[0544] Further additional clause 6. A method according to any one of further additional clauses 1 to 5, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0545] Further additional clause 7. A method according to any one of further additional clauses 1 to 6, wherein the one or more features include multipath delay and angle features, potential device-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential device-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0546] Further additional clause 8. A method of operating an entity; obtaining one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); extracting one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and sending one or more extracted features to one or more target devices.

[0547] Further additional clause 9. A method according to further additional clause 8, wherein the entity corresponds to a corresponding transmit receive point (TRP) or another UE that measures the RS-P to obtain a corresponding RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0548] Further additional clause 10. A method according to any one of further additional clauses 8 to 9, wherein the entity corresponds to a network positioning estimation entity that receives the one or more RFFPs, and wherein the one or more target devices include one or more transmit receive points (TRPs) or one or more other UEs.

[0549] Further additional clause 11. A method according to any one of further additional clauses 8 to 10, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0550] Further additional clause 12. A method according to any one of further additional clauses 8 to 11, wherein the one or more features include multipath delay and angle features, potential transmit receive point (TRP) specific features trained jointly with the UE-based ML feature fusion model at the network side training component, potential device specific features trained independently of the UE-based ML feature fusion model at the network side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0551] Further additional clause 13. A method of operating a user equipment (UE), the method comprising: receiving one or more reference signals for positioning (RS-P); sending RS-P, the one or more RS-Ps and the RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receiving RFFP measurement information associated with the RS-P; obtaining one or more RFFPs associated with the one or more RS-Ps; and providing the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0552] Further additional clause 14. A method according to further additional clause 13, wherein the one or more RS-Ps correspond to a downlink positioning reference signal (PRS) or a sidelink sounding reference signal (SRS), and wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0553] Further additional clause 15. The method according to further additional clause 14, wherein the RFFP measurement information includes one or more RFFPs of the uplink SRS or the sidelink SRS.

[0554] Further additional clause 16. A method according to further additional clause 15, wherein the UE-based ML feature fusion model comprises a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the RS-P based on the one or more RFFPs.

[0555] Further additional clause 17. A method according to any one of further additional clauses 13 to 16, wherein the RFFP measurement information comprises one or more features extracted from one or more RFFPs associated with the RS-P via one or more ML feature extraction models at one or more entities.

[0556] Further additional clause 18. The method according to further additional clause 17, wherein the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models.

[0557] Further additional clause 19. A method of operating a network positioning estimation entity, the method comprising: obtaining a first set of features associated with a round-trip radio frequency fingerprint (RFFP), the round-trip radio frequency fingerprint (RFFP) being associated with a reference signal (RS-P) for positioning sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtaining a second set of features associated with one or more round-trip radio frequency fingerprints (RFFP) sent to the UE, the second set of features being associated with the round-trip RFFP positioning estimation session of the UE; and providing the first set of features and the second set of features to an ML feature fusion model to derive a positioning estimate of the UE.

[0558] Further additional clause 20. A method according to further additional clause 19, wherein the first set of features is extracted at the network positioning estimation entity or the one or more transmit receive points (TRPs) or one or more other UEs, or wherein the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE or the one or more other UEs, or a combination thereof.

[0559] Further additional clause 21. A method according to any one of further additional clauses 19 to 20, wherein the network positioning estimation entity corresponds to a transmit receive point (TRP), or wherein the network positioning estimation entity corresponds to a location management function (LMF).

[0560] Further additional clause 22. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a reference signal (RS-P) for positioning via the at least one transceiver; obtain one or more features associated with the RS-P, the one or more features being extracted from one or more radio frequency fingerprints (RFFP) of the RS-P by one or more entities via one or more machine learning (ML) feature extraction models; and provide the one or more features to a UE-based ML feature fusion model to derive a positioning estimate of the UE.

[0561] Further additional clause 23. A UE according to further additional clause 22, wherein the one or more features are extracted by the one or more transmit receive points (TRPs).

[0562] Further additional clause 24. The UE according to further additional clause 23, wherein the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models.

[0563] Further additional clause 25. A UE according to any of further additional clauses 22 to 24, wherein the one or more features are extracted by a network position estimation entity.

[0564] Further additional clause 26. A UE according to any one of further additional clauses 22 to 25, wherein the one or more features include a first set of features extracted by one or more transmit receive points (TRPs) via a first set of ML feature extraction models, and wherein the one or more features include a second set of features extracted by a network positioning estimation entity via a second set of ML feature extraction models.

[0565] Further additional clause 27. A UE according to any of further additional clauses 22 to 26, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0566] Further additional clause 28. A UE according to any one of further additional clauses 22 to 27, wherein the one or more features include multipath delay and angle features, potential device-specific features jointly trained with the UE-based ML feature fusion model at a network-side training component, potential device-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0567] Further additional clause 29. An entity comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: obtain one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P) from a user equipment (UE); extract one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and send one or more extracted features to one or more target devices via the at least one transceiver.

[0568] Further additional clause 30. An entity according to further additional clause 29, wherein the entity corresponds to a corresponding transmit receive point (TRP) or another UE that measures the RS-P to obtain a corresponding RFFP, and wherein the one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

[0569] Further additional clause 31. An entity according to any one of further additional clauses 29 to 30, wherein the entity corresponds to a network positioning estimation entity that receives the one or more RFFPs, and wherein the one or more target devices include one or more transmit receive points (TRPs) or one or more other UEs.

[0570] Further additional clause 32. An entity according to any of further additional clauses 29 to 31, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0571] Further additional clause 33. An entity according to any one of further additional clauses 29 to 32, wherein the one or more features include multipath delay and angle features, potential transmit receive point (TRP) specific features trained jointly with the UE-based ML feature fusion model at a network-side training component, potential device specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and virtual anchor points or reflectors, or any combination thereof.

[0572] Further additional clause 34. A UE, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more reference signals for positioning (RS-P) via the at least one transceiver; send RS-P via the at least one transceiver, the one or more RS-Ps and the RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session of the UE; receive RFFP measurement information associated with the RS-P via the at least one transceiver; obtain one or more RFFPs associated with the one or more RS-Ps; and provide the RFFP measurement information and the one or more RFFPs to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate of the UE.

[0573] Further additional clause 35. A UE according to further additional clause 34, wherein the one or more RS-Ps correspond to a downlink positioning reference signal (PRS) or a sidelink sounding reference signal (SRS), and wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

[0574] Further additional clause 36. The UE according to further additional clause 35, wherein the RFFP measurement information comprises one or more RFFPs of the uplink SRS or the sidelink SRS.

[0575] Further additional clause 37. A UE according to further additional clause 36, wherein the UE-based ML feature fusion model comprises a UE-based ML feature extraction model, and the UE-based ML feature extraction model extracts one or more features associated with the RS-P based on the one or more RFFPs.

[0576] Further additional clause 38. A UE according to any of further additional clauses 34 to 37, wherein the RFFP measurement information comprises one or more features extracted from one or more RFFPs associated with the RS-P via one or more ML feature extraction models at one or more entities.

[0577] Further additional clause 39. The UE ...

Claims

1. A method of operating a user equipment (UE), the method comprising: Sending a reference signal for positioning (RS-P); obtaining one or more features associated with the RS-P, the one or more features extracted by one or more entities from one or more radio frequency fingerprints (RFFPs) of the RS-P via one or more machine learning (ML) feature extraction models; and A position estimate for the UE is determined based at least in part on the one or more features and an output of a UE-based ML feature fusion model.

2. The method of claim 1, wherein the one or more features are extracted by the one or more transmit receive points (TRPs). 3 . The method of claim 2 , wherein the one or more ML feature extraction models comprise one or more entity-specific ML feature extraction models or common ML feature extraction models. The method according to claim 1 , wherein the one or more features are extracted by a network location estimation entity.

5. The method according to claim 1, wherein the one or more features include a first set of features extracted by one or more transmit receive points (TRPs) via a first set of ML feature extraction models, and The one or more features include a second set of features extracted by the network location estimation entity via a second set of ML feature extraction models.

6. The method of claim 1, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

7. The method of claim 1, wherein the one or more features include multipath delay and angle features, potential device-specific features jointly trained with a UE-based ML feature fusion model at a network-side training component, potential device-specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

8. A method of operating an entity; obtaining, from a user equipment (UE), one or more radio frequency fingerprints (RFFPs) associated with a reference signal for positioning (RS-P); extracting one or more features associated with the one or more RFFPs via one or more machine learning (ML) feature extraction models; and The one or more extracted features are sent to one or more target devices.

9. The method according to claim 8, wherein the entity corresponds to a corresponding transmission reception point (TRP) or another UE that measures the RS-P to obtain a corresponding RFFP, and The one or more target devices include the UE, a network positioning estimation entity, or a combination thereof.

10. The method according to claim 8, wherein the entity corresponds to a network position estimation entity that receives the one or more RFFPs, and The one or more target devices include one or more transmit reception points (TRPs) or one or more other UEs.

11. The method of claim 8, wherein the RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS.

12. The method of claim 8, wherein the one or more features include multipath delay and angle features, potential transmit receive point (TRP) specific features jointly trained with a UE-based ML feature fusion model at a network-side training component, potential device specific features trained independently of the UE-based ML feature fusion model at the network-side training component, multipath features involving association between multipath and a virtual anchor point or reflector, or any combination thereof.

13. A method of operating a user equipment (UE), the method comprising: receiving one or more reference signals for positioning (RS-P); sending an RS-P, the one or more RS-Ps and the RS-P being associated with a UE-based round-trip radio frequency fingerprint (RFFP) positioning estimation session for the UE; receiving RFFP measurement information associated with the RS-P; obtaining one or more RFFPs associated with the one or more RS-Ps; as well as The RFFP measurement information and the one or more RFFPs are provided to a UE-based machine learning (ML) feature fusion model to derive a positioning estimate for the UE.

14. The method according to claim 13, wherein the one or more RS-Ps correspond to a downlink positioning reference signal (PRS) or a sidelink sounding reference signal (SRS), and The RS-P corresponds to an uplink sounding reference signal (SRS) or a sidelink SRS. 15 . The method of claim 14 , wherein the RFFP measurement information includes one or more RFFPs of the uplink SRS or the sidelink SRS.

16. The method of claim 15, wherein the UE-based ML feature fusion model comprises a UE-based ML feature extraction model, wherein the UE-based ML feature extraction model extracts one or more features associated with the RS-P based on the one or more RFFPs.

17. The method of claim 13, wherein the RFFP measurement information comprises one or more features extracted from one or more RFFPs associated with the RS-P via one or more ML feature extraction models at one or more entities.

18. The method of claim 17, wherein the one or more ML feature extraction models include one or more entity-specific ML feature extraction models or common ML feature extraction models.

19. A method of operating a network location estimation entity, the method comprising: obtaining a first set of features associated with a round-trip radio frequency fingerprint (RFFP) associated with a reference signal for positioning (RS-P) sent by a user equipment (UE), the first set of features being associated with a round-trip RFFP positioning estimation session of the user equipment (UE); obtaining a second set of features associated with one or more round-trip radio frequency fingerprints (RFFPs) sent to the UE, the second set of features being associated with the round-trip RFFP position estimation session for the UE; as well as The first set of features and the second set of features are provided to an ML feature fusion model to derive a positioning estimate for the UE.

20. The method according to claim 19, wherein the first set of features is extracted at the network location estimation entity or the one or more transmit receive points (TRPs) or one or more other UEs, or wherein the second set of features is extracted at the network positioning estimation entity or the one or more TRPs or the UE or the one or more other UEs, or A combination of them.

21. The method according to claim 19, The network location estimation entity corresponds to a Transmit Reception Point (TRP), or the network location estimation entity corresponds to a Location Management Function (LMF).