Enhanced assistance data for radio frequency sensing

Abstract

Radio frequency (RF) sensing of a target object by a wireless network is supported by a sensing node and a network node using sensing assistance data. The sensing assistance data can include information for Doppler estimation from the received RF signal. For example, information for Doppler estimation can include an indication of phase coherence of an RF signal, such as phase coherence found in a positioning reference signal (PRS) resource, a resource set, a transmit-receive point (TRP), a frequency layer, or any combination thereof. The sensing assistance data can include an association of a PRS resource and a reference point object (RPO) so that RF signals reflected from the RPO can be excluded from the sensing measurements. The sensing assistance data can include beam pattern information of PRS resources for beam coordination for RF sensing.

Description

[0001] Related Applications

[0002] This application claims the benefit of U.S. application No. 17 / 836,777, filed on June 9, 2022, entitled “ENHANCED ASSISTANCE DATA FOR RADIOFREQUENCY SENSING,” which is assigned to the assignee of this application and is incorporated herein by reference in its entirety. Background Art Technical Field :

[0003] The subject matter disclosed herein relates generally to wireless communications, and more particularly to radio frequency sensing in wireless communication systems.

[0004] information :

[0005] Radar is a range-finding technology that can be used to determine the distance of an object relative to a given location. A radar system operates by sending and receiving electromagnetic pulses. Some of these pulses reflect from objects or surfaces along the transmission path, producing "echoes". The radar system can determine the distance of an object or surface based on the round-trip time between sending a pulse and receiving the echo of that pulse.

[0006] In a monostatic radar system, the antenna used to transmit the pulse (the "transmit antenna") is co-located with the antenna used to receive the echo (the "receive antenna"). For example, the transmit antenna and the receive antenna are typically located on the same device. This allows simple synchronization between the timing of the transmitted pulse and the timing of the received echo, since the same device (or system) clock can be used for both. In a multistatic radar system, the transmit antenna is located at a considerable distance from the receive antenna. The spatial diversity provided by a multistatic radar system provides high accuracy of the target location and allows different aspects of the target to be observed simultaneously.

[0007] Radio frequency (RF) sensing is a technology similar to (and may include) radar that can be used to determine one or more of the following: the presence, location, identity, or a combination thereof of an object. RF sensing can be used, for example, in wireless communication systems, such as cellular communication systems (5G and above). With large bandwidths being allocated, for example, to 5G and above, cellular communication system RF sensing can be considered a key feature in future cellular systems. Improvements in RF sensing are desired. Summary of the invention

[0008] Radio frequency (RF) sensing of a target object by a wireless network is supported by sensing nodes and network nodes using sensing assistance data. The sensing assistance data can include information for Doppler estimation based on received RF signals. For example, the information for Doppler estimation can include an indication of phase coherence of the RF signal, such as phase coherence found in a positioning reference signal (PRS) resource, a resource set, a transmit receive point (TRP), a frequency layer, or any combination thereof. The sensing assistance data can include an association of a PRS resource and a reference point object (RPO), so that RF signals reflected from the RPO can be excluded from the sensing measurement. The sensing assistance data can include beam pattern information of the PRS resource for beam coordination for RF sensing.

[0009] In one specific implementation, a method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: receiving sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node; receiving the RF signal; and performing Doppler estimation using the RF signal and the sensing assistance data.

[0010] In one specific implementation, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node via the at least one transceiver; receive the RF signal via the at least one transceiver; and perform Doppler estimation using the RF signal and the sensing assistance data.

[0011] In one embodiment, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: a component for receiving sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node; a component for receiving the RF signal; and a component for performing Doppler estimation using the RF signal and the sensing assistance data.

[0012] In one embodiment, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for: receiving sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node; receiving the RF signal; and performing Doppler estimation using the RF signal and the sensing assistance data.

[0013] In one specific implementation, a method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including information for performing Doppler estimation based on an RF signal; and transmitting the sensing assistance data including the information for performing Doppler estimation based on the RF signal to the sensing node.

[0014] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data including information for performing Doppler estimation based on an RF signal; and transmit the sensing assistance data including the information for performing Doppler estimation based on the RF signal to the sensing node via the at least one transceiver.

[0015] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including information for performing Doppler estimation based on an RF signal; and a component for transmitting the sensing assistance data including the information for performing Doppler estimation based on the RF signal to the sensing node.

[0016] In one specific implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including information for performing Doppler estimation based on an RF signal; and transmitting the sensing assistance data including the information for performing Doppler estimation based on the RF signal to the sensing node.

[0017] In one specific implementation, a method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: receiving sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving a PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0018] In one specific implementation, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive sensing assistance data including at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node via the at least one transceiver; receive the PRS resource via the at least one transceiver; and perform sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0019] In one specific implementation, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: receiving sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving the PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0020] In one specific implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for: receiving sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving a PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0021] In one specific implementation, a method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including an association between at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmitting the sensing assistance data including the association between the at least one PRS resource and the at least one RPO to the sensing node.

[0022] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmit the sensing assistance data including the association of the at least one PRS resource and the at least one RPO to the sensing node via the at least one transceiver.

[0023] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and a component for transmitting the sensing assistance data including the association of the at least one PRS resource and the at least one RPO to the sensing node.

[0024] In one specific implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including an association between at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmitting the sensing assistance data including the association between the at least one PRS resource and the at least one RPO to the sensing node.

[0025] In one specific implementation, a method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: receiving beam pattern information including a positioning reference signal (PRS) resource for beam coordination for RF sensing from a network node; receiving the PRS resource; and performing sensing based on the PRS resource and the beam pattern information.

[0026] In one specific implementation, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor being coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node via the at least one transceiver; receive PRS resources via the at least one transceiver; and perform sensing based on the PRS resources and the beam pattern information.

[0027] In one specific implementation, a sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: a component for receiving beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node; a component for receiving the PRS resources; and a component for performing sensing based on the PRS resources and the beam pattern information.

[0028] In one specific implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for: receiving beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node; receiving PRS resources; and performing sensing based on the PRS resources and the beam pattern information.

[0029] In one specific implementation, a method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network includes: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmitting the sensing assistance data including the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node.

[0030] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: at least one transceiver; at least one memory; and at least one processor, the at least one processor being coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data including beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmit the sensing assistance data including the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node via the at least one transceiver.

[0031] In one specific implementation, a network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network includes: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and a component for transmitting the sensing assistance data including the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node.

[0032] In one specific implementation, a non-transitory storage medium includes program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code including instructions for the following operations: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data including beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmitting the sensing assistance data including the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node.

[0033] 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

[0034] 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.

[0035] Figure 1 An example wireless communication system that may be used for radio frequency (RF) sensing services in accordance with various aspects of the present disclosure is illustrated.

[0036] Figure 2 A block diagram of a user equipment (UE) is illustrated, which may be Figure 1 One of the UEs in.

[0037] Figure 3 A block diagram of a transmit / receive point (TRP) is illustrated, which can be Figure 1 One of the base stations in.

[0038] Figure 4 A block diagram of a server is shown, which may be Figure 1 One of the servers in .

[0039] Figure 5 Sensing entities that may be used for RF sensing as discussed herein are illustrated.

[0040] Figure 6 Network entities that may be used for RF sensing as discussed herein are illustrated.

[0041] Figure 7 An example of a bistatic radar system that may be used for RF sensing is illustrated.

[0042] Figure 8 A sensing environment including a sensing entity, a target object, and a plurality of reference point objects (RPOs) is illustrated.

[0043] Fig. 9 A sensing environment including a transmitter node that transmits a reference signal for sensing using a beam pattern is illustrated.

[0044] Fig.10 Signaling and process flows illustrating messaging including sensing assistance data messages between a network entity and a sensing entity for RF sensing are illustrated.

[0045] Fig.11 A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including information for Doppler estimation.

[0046] Fig.12 A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including information for Doppler estimation.

[0047] Fig.13 A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including information for RPO.

[0048] Fig.14 A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including information for RPO.

[0049] Fig.15A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including beam pattern information for sensing reference signals.

[0050] Fig.16 A flow chart is illustrated for an exemplary process for supporting RF sensing in a wireless network using sensing assistance data including beam pattern information for sensing reference signals. DETAILED DESCRIPTION

[0051] Techniques for radio frequency sensing are discussed herein. For example, a reference signal (e.g., a channel state information reference signal or a positioning reference signal) may be used to enhance a legacy positioning process (e.g., a new radio user equipment positioning process) for radio frequency sensing. As another example, a positioning reference signal may be scheduled and an indication that the positioning reference signal will be used for radio frequency sensing may be provided. The positioning reference signal may also be used for positioning and may be indicated as being used for positioning. The positioning reference signal for sensing may be scheduled in the same frequency layer as the positioning reference signal for positioning. The indication that the positioning reference signal for sensing will be used for sensing may include an indication that the frequency layer containing the positioning reference signal for sensing is used for sensing. These techniques are examples, and other specific implementations of the techniques for radio frequency sensing may also be used or may alternatively be used.

[0052] The items and / or techniques described herein may provide one or more of the following capabilities, as well as other capabilities not mentioned. For example, when both positioning and sensing are performed, the latency of radio frequency sensing may be reduced and / or kept low. The priority of positioning and radio frequency sensing may be adapted. Power consumption of transmission / reception points and / or user equipment may be saved. Other capabilities may be provided, and not every specific implementation according to the present disclosure must provide any of the capabilities discussed, let alone all of the capabilities.

[0053] Obtaining the location of a mobile device accessing a wireless network can be used for many applications, including, for example, emergency calls, personal navigation, consumer asset tracking, locating friends or family members, etc. Existing positioning methods include methods based on measuring radio signals transmitted from various devices or entities, including satellite vehicles (SVs) and terrestrial radio sources such as base stations and access points in wireless networks. It is expected that standardization for 5G wireless networks will include support for various positioning methods that can utilize reference signals transmitted by base stations for positioning determination in a manner similar to how LTE wireless networks currently utilize positioning reference signals (PRS) and / or cell-specific reference signals (CRS).

[0054] This specification may quote a sequence of actions to be performed by, for example, an element of a computing device. Each action described herein can be performed by a dedicated circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of the two. The sequence of actions described herein may be embodied in a non-transient computer-readable medium having a corresponding set of computer instructions stored thereon, which, when executed, will cause an associated processor to perform the functionality described herein. Thus, the various aspects described herein may be implemented in a number of different forms, all of which fall within the scope of the present disclosure, including the claimed subject matter.

[0055] As used herein, the terms "user equipment" (UE) and "base station" are not dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headsets, 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 can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as an "access terminal" or "AT", a "client device", a "wireless device", a "subscriber device", a "subscriber terminal", a "subscriber station", a "user terminal" or UT, a "mobile terminal", a "mobile station", a "mobile device", or variations thereof. In general, the UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a WiFi network (e.g., based on IEEE 802.11, etc.), etc. The UE can be implemented by any of a variety of types of devices, including but not limited to a printed circuit (PC) card, a compact flash device, an external modem or an internal modem, a wireless or wired phone, a smart phone, a tablet device, a consumer asset tracking device, an asset tag, etc.

[0056] Depending on the network in which the base station is deployed, the base station may operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, node Bs, evolved node Bs (eNBs), or general node Bs (gNodeBs, gNBs). In addition, in some systems, the base station may only provide edge node signaling functions, while in other systems, the base station may provide additional control functions and / or network management functions. The communication link by which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). The communication link by which the UE can send a signal to another UE is called a side link (SL) or a side link channel. As used herein, the term traffic channel (TCH) may refer to a UL / reverse, DL / forward, or SL traffic channel.

[0057] The term "base station" may refer to a single physical transmit receive point (TRP) (which may also be referred to as a transmit / receive point) or 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 the cell 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 (for example, 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 the UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring.

[0058] As used herein, depending on the context, the term "cell" or "sector" may correspond to one of a plurality of cells of a base station or to the base station itself. The term "cell" may refer to a logical communication entity used to communicate with a base station (e.g., on a carrier) and may be associated with an identifier to distinguish between adjacent cells operating via the same carrier or different carriers (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types that may provide access to different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types). In some examples, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) on which the logical entity operates.

[0059] The RF sensing system may employ an RF sensing server to support determination of characteristics of one or more objects in a wireless network (e.g., a cellular network), such as relative position, identity, motion state, etc. The RF sensing server may be part of or accessible from a serving network or a home network for a UE, or may simply be accessible via the Internet or a local intranet. With the increasing bandwidth (BW) allocated to cellular communication systems (5G and above) and the increasing number of use cases introduced for cellular communication systems, RF sensing may be considered a key feature in future cellular systems.

[0060] Positioning services used in cellular communication systems such as LTE and 5G NR are well established. On the other hand, sensing services for use in cellular communication systems are under development. New RF sensing services can be enabled in future cellular communication systems using, for example, joint positioning and sensing services. For example, upper layer (medium access control (MAC) and above) procedures for UE positioning can be reused (or enhanced) for RF sensing services. In the physical (PHY) layer, the large bandwidth of the positioning reference signal (PRS) used in the positioning procedures can make it suitable for RF sensing.

[0061] In one or more specific implementations described herein, techniques, equipment, and systems are provided to support RF sensing using sensing assistance data. For example, the sensing assistance data may include information for performing Doppler estimation based on received RF signals. In order to support Doppler estimation, phase coherence of the RF signal is required. The sensing assistance data may therefore include RF signals with phase coherence, such as positioning reference signal (PRS) resources, resource sets, transmit receive points (TRPs), frequency layers, or any combination thereof. If PRS coherent transmission is not supported, the sensing assistance data may identify that the reference signal is associated with a PRS that supports Doppler estimation. The sensing assistance data may include an indication of a search window for Doppler estimation, such as an expected Doppler and an expected Doppler uncertainty.

[0062] In some implementations, the sensing assistance data may identify one or more reference point objects (RPOs) associated with one or more PRS resources. For example, RPOs present clutter in the received signal because PRSs may be reflected from RPOs other than target objects. By removing rejection of RPOs from the received RF signal, sensing performance may be enhanced.

[0063] In some implementations, the sensing assistance data may provide beam pattern information for PRS resources, for example, to support beam coordination for RF sensing. For example, the PRS beam pattern information may be similar to or may be beam pattern information configured for UE-based Angle of Departure (AoD)-based positioning.

[0064] Figure 1An example of a communication system 100 is illustrated including UE 105, UE 106, a radio access network (RAN) (here, fifth generation (5G) next generation (NG) RAN (NG-RAN) 135), a 5G core network (5GC) 140, and a server 150 that can be used for positioning services and can be used for RF sensing services as discussed herein. UE 105 and / or UE 106 can be, for example, an IoT device, a location tracker device, a cellular phone, a vehicle (e.g., a car, truck, bus, ship, etc.), or other device. A 5G network may also be referred to as a new radio (NR) network; NG-RAN 135 may be referred to as a 5GRAN or NRRAN; and 5GC 140 may be referred to as an NG core network (NGC). Standardization of NG-RAN and 5GC is ongoing in the 3rd Generation Partnership Project (3GPP). Therefore, NG-RAN 135 and 5GC 140 may follow current standards or future standards from 3GPP for 5G support. NG-RAN 135 may be another type of RAN, such as a 3G RAN, a 4G Long Term Evolution (LTE) RAN, etc. UE 106 may be similarly configured and coupled to UE 105 to transmit and / or receive signals to and / or from similar other entities in system 100, but for simplicity of the drawings, the NG-RAN 135 is not shown in FIG. Figure 1 105. Similarly, for simplicity, the discussion focuses on the UE 105. The communication system 100 can utilize information from a constellation 185 of satellite vehicles (SVs) 190, 191, 192, 193 of a satellite positioning system (SPS) (e.g., a global navigation satellite system (GNSS)) such as the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the Galileo system, or the BeiDou system, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Overlay Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of the communication system 100 are described below. The communication system 100 may include additional or alternative components.

[0065] like Figure 1As shown in FIG. 1 , the NG-RAN 135 includes NR Node Bs (gNBs) 110a, 110b and a next generation eNodeB (ng-eNB) 114, and the 5GC 140 includes an access and mobility management function (AMF) 115, a session management function (SMF) 117, a location management function (LMF) 120, and a gateway mobile location center (GMLC) 125. The gNBs 110a, 110b, and the ng-eNB 114 are communicatively coupled to each other, each configured to perform bidirectional wireless communication with the UE 105, and each communicatively coupled to the AMF 115 and configured to perform bidirectional communication with the AMF. The gNBs 110a, 110b, and the ng-eNB 114 may be referred to as base stations (BSs). The AMF 115, the SMF 117, the LMF 120, and the GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to the external client 130. The SMF 117 may serve as an initial contact point for a service control function (SCF) (not shown) to create, control, and delete media sessions. A base station (such as gNB 110a, 110b, and / or ng-eNB 114) may be a macro cell (e.g., a high-power cellular base station), or a small cell (e.g., a low-power cellular base station), or an access point (e.g., a short-range base station configured to utilize a short-range technology (e.g., WiFi, WiFi Direct (WiFi-D), Low Energy (BLE), Zigbee, etc.) for communication). One or more BSs (e.g., one or more of gNB 110a, 110b, and / or ng-eNB 114) may be configured to communicate with UE 105 via multiple carriers. Each of gNB 110a, 110b, and ng-eNB 114 may provide communication coverage for a corresponding geographic area (e.g., a cell). Each cell may be divided into multiple sectors according to the base station antenna.

[0066] Figure 1A generalized illustration of various components is provided, wherein any or all of the components may be utilized as appropriate, and each of the components may be repeated or omitted as desired. Specifically, although one UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in the communication system 100. Similarly, the communication system 100 may include a greater (or smaller) number of SVs (i.e., more or less than the four SVs 190-193 shown), gNBs 110a, 110b, ng-eNBs 114, AMFs 115, external clients 130, and / or other components. The illustrated connections connecting the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0067] Although Figure 1 A 5G-based network is illustrated, but similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. Implementations described herein (which are used for 5G technology and / or for one or more other communication technologies and / or protocols) may be used to send (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105), and / or provide location assistance to UE 105 (via GMLC 125 or other location server), and / or calculate the position of UE 105 at a device with positioning capabilities such as UE 105, gNB 110a, 110b, or LMF 120 based on measurements received at UE 105 for such directional transmitted signals. The gateway mobile location center (GMLC) 125, location management function (LMF) 120, access and mobility management function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114 and gNB (gNodeB) 110a, 110b are examples and may be replaced by or include various other location server functionalities and / or base station functionalities, respectively, in various embodiments.

[0068] The system 100 is capable of wireless communication because the components of the system 100 can communicate with each other (at least sometimes using wireless connections), directly or indirectly, for example, via gNBs 110a, 110b, ng-eNBs 114, and / or 5GCs 140 (and / or one or more other devices not shown, such as one or more other transceiver base stations). The system 100 can be capable of performing positioning services for UEs 105 and 106 based on wireless communication between the components of the system 100. The system 100 can further be capable of performing sensing services based on wireless communication between the components of the system 100 using base stations (e.g., one or more of gNBs 110, ng-eNBs 114) and UEs 105 and 106. For indirect communication, the communication can be changed during transmission from one entity to another, for example, to change header information of a data packet, change the format, etc. The UE 105 can include multiple UEs and can be a mobile wireless communication device, but can communicate wirelessly as well as via a wired connection. UE 105 can be any of a variety of devices, such as a smartphone, a tablet computer, a vehicle-based device, etc., but these devices are examples because UE 105 need not be in any of these configurations and other configurations of UE can be used. Other UEs may include wearable devices (e.g., smart watches, smart jewelry, smart glasses, or headphones, etc.). Other UEs may also be used, whether currently existing or developed in the future. In addition, other wireless devices (whether mobile or not) can be implemented within the system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140 and / or external clients 130. For example, such other devices may include Internet of Things (IoT) devices, medical devices, home entertainment and / or automation devices, etc. 5GC 140 can communicate with external clients 130 (e.g., computer systems), for example, to allow external clients 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0069] UE 105 or other devices may be configured to communicate in various networks and / or for various purposes and / or using various technologies (e.g., 5G, Wi-Fi communication, multi-frequency Wi-Fi communication, satellite positioning, one or more types of communication (e.g., GSM (Global System for Mobile), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (Vehicle to Vehicle, e.g., V2P (vehicle to pedestrian), V2I (vehicle to infrastructure), V2V (vehicle to vehicle), etc.), IEEE802.11p, etc.). V2X communication may be cellular (Cellular-V2X (C-V2X)) and / or WiFi-based (e.g., DSRC (Dedicated Short Range Connection)). The system 100 may support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter may send modulated signals on multiple carriers simultaneously. Each modulated signal may be a code division multiple access (CDMA) signal, a time division multiple access (TDMA) signal, an orthogonal frequency division multiple access (OFDMA) signal, a single carrier frequency division multiple access (SC-FDMA) signal, or the like. Each modulated signal may be transmitted on a different carrier and may carry pilots, overhead information, data, or the like. UEs 105, 106 may communicate with each other through UE-to-UE sidelink communication by transmitting on one or more sidelink (SL) channels such as a physical sidelink synchronization channel (PSSCH), a physical sidelink broadcast channel (PSBCH), or a physical sidelink control channel (PSCCH).

[0070] UE 105 may include and / or may be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a terminal (SET) enabled with secure user plane location (SUPL), or some other name. In addition, UE 105 may correspond to a cellular phone, a smart phone, a laptop, a tablet device, a PDA, a consumer asset tracking device, a navigation device, an Internet of Things (IoT) device, a health monitor, a security system, a smart city sensor, a smart meter, a wearable tracker, or some other portable or mobile device. Typically, although not necessarily, UE 105 may use one or more radio access technologies (RATs) to support wireless communications, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 may use a wireless local area network (WLAN) to support wireless communications, which may be connected to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or packet cable. Using one or more of these RATs may allow UE 105 (e.g., via elements of 5GC 140 ( Figure 1 125) and / or allows the external client 130 to receive location information about the UE 105 (eg, via the GMLC 125).

[0071] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where users may employ audio, video and / or data I / O (input / output) devices and / or body sensors and separate wired or wireless modems. The estimate of the location of UE 105 may be referred to as location, location estimate, location fix, fix, position, position estimate or position fix, and may be geographic, thereby providing location coordinates (e.g., latitude and longitude) about UE 105, which may or may not include an altitude component (e.g., height above sea level; height above or depth below ground level, floor level or basement level). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., a postal address or a designation of a point or smaller area in a building, such as a specific room or floor). The location of UE 105 may be expressed as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 105 may be expressed as a relative location, including, for example, a distance and direction relative to a known location. The relative location may be expressed as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to a certain origin at a known location, which may be defined, for example, geographically, in municipal form, or with reference to a point, area, or volume indicated, for example, on a map, floor plan, or building plan. In the description contained herein, the use of the term "location" may include any of these variants unless otherwise indicated. When calculating the location of the UE, the local x-coordinate, y-coordinate, and possibly z-coordinate are typically solved, and the local coordinates are then converted (if necessary) into absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level).

[0072] UE 105 may be configured to communicate with other entities using one or more of a variety of technologies. UE 105 may be configured to be indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. D2D P2P links may be supported using any suitable D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Etc. One or more UEs in a group of UEs utilizing D2D communication may be located within a geographic coverage area of ​​a transmit / receive point (TRP), such as one or more of gNB 110a, gNB 110b, and / or ng-eNB 114. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from a base station for other reasons. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE may transmit to other UEs in the group. A TRP may facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving a TRP. One or more UEs in a group of UEs utilizing D2D communication may be located within a geographic coverage area of ​​a TRP. Other UEs in such a group may be outside such geographic coverage area or may be unable to receive transmissions from a base station for other reasons. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE may transmit to other UEs in the group. The TRP may facilitate the scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without involving a TRP.

[0073] Figure 1 The base stations (BS) in the NG-RAN 135 shown in the figure include NR B nodes (referred to as gNB 110a and gNB 110b). Each pair of gNBs 110a, 110b in the NG-RAN 135 may be connected to each other via one or more other gNBs. Access to the 5G network is provided to the UE 105 via wireless communications between the UE 105 and one or more of the gNBs 110a, 110b, which may provide wireless communications access to the 5GC 140 on behalf of the UE 105 using 5G. Figure 1 , it is assumed that the serving gNB for UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may serve as the serving gNB if UE 105 moves to another location, or may serve as a secondary gNB to provide additional throughput and bandwidth to UE 105.

[0074] Figure 1The base stations (BSs) in the NG-RAN 135 shown in the figure may include an ng-eNB 114, which is also referred to as a next generation evolved Node B. The ng-eNB 114 may be connected to one or more of the gNBs 110a, 110b in the NG-RAN 135 via one or more other gNBs and / or one or more other ng-eNBs. The ng-eNB 114 may provide LTE wireless access and / or evolved LTE (eLTE) wireless access to the UE 105. One or more of the gNBs 110a, 110b and / or ng-eNB 114 may be configured to function as a positioning-only beacon that may transmit signals to assist in determining the location of the UE 105, but may not be able to receive signals from the UE 105 or other UEs.

[0075] The gNBs 110a, 110b, and / or the ng-eNB 114 may each include one or more TRPs. For example, each sector within a cell of the BS may include a TRP, but multiple TRPs may share one or more components (e.g., sharing a processor but having separate antennas). The system 100 may include only a macro TRP, or the system 100 may have different types of TRPs, such as a macro TRP, a pico TRP, and / or a femto TRP, among others. A macro TRP may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to terminals with service subscriptions. A pico TRP may cover a relatively small geographic area (e.g., a pico cell) and may allow unrestricted access to terminals with service subscriptions. A femto or home TRP may cover a relatively small geographic area (e.g., a femto cell) and may allow restricted access to terminals associated with the femto cell (e.g., terminals of users in a home).

[0076] Each of the gNBs 110a, 110b, and / or ng-eNB 114 may include a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the gNB 110a includes a RU 111, a DU 112, and a CU 113. The RU 111, the DU 112, and the CU 113 divide the functionality of the gNB 110a. Although the gNB 110a is shown as having a single RU, a single DU, and a single CU, the gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between the CU 113 and the DU 112 is referred to as the F1 interface. The RU 111 is configured to perform digital front end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmission / reception) and digital beamforming, and includes a portion of the physical (PHY) layer. The RU 111 may perform DFE using massive multiple input / multiple output (MIMO) and may be integrated with one or more antennas of the gNB 110a. DU 112 hosts the radio link control (RLC), medium access control (MAC), and physical layers of gNB 110a. One DU can support one or more cells, and each cell is supported by a single DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for transmitting user data, mobility control, radio access network sharing, positioning, session management, etc., although some functions are only assigned to DU 112. CU 113 hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of gNB 110a. UE 105 can communicate with CU 113 via the RRC layer, SDAP layer, and PDCP layer, communicate with DU 112 via the RLC layer, MAC layer, and PHY layer, and communicate with RU 111 via the PHY layer.

[0077] As mentioned, although Figure 1 Nodes configured to communicate according to a 5G communication protocol are depicted, but nodes configured to communicate according to other communication protocols (such as an LTE protocol or an IEEE 802.11x protocol) may also be used. For example, in an evolved packet system (EPS) that provides LTE wireless access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations with evolved Node Bs (eNBs). The core network for the EPS may include an evolved packet core (EPC). The EPS may include the E-UTRAN plus the EPC, where the E-UTRAN corresponds to the UE 105. Figure 1 The NG-RAN 135 in the figure and the EPC correspond to the 5GC 140 in the figure.

[0078] The gNB 110a, gNB 110b, and ng-eNB 114 may communicate with the AMF 115; for positioning functionality, the AMF communicates with the LMF 120. The AMF 115 may support mobility of the UE 105, including cell changes and handovers, and may participate in supporting signaling connections with the UE 105 and possible data bearers and voice bearers for the UE 105. The LMF 120 may communicate directly with the UE 105, or directly with the gNB 110a, 110b, and / or ng-eNB 114, for example, via wireless communications. The LMF 120 may support positioning of the UE 105 when the UE 105 accesses the NG-RAN 135, and may support various positioning procedures / methods, such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (e.g., downlink (DL) OTDOA or uplink (UL) OTDOA), Round Trip Time (RTT), Multi-cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AoA), Angle of Departure (AoD), and / or other positioning methods. The LMF 120 may process a location service request for the UE 105 received from, for example, the AMF 115 or the GMLC 125. The LMF 120 may be connected to the AMF 115 and / or the GMLC 125. The LMF 120 may be referred to by other names, such as a Location Manager (LM), a Location Function (LF), a Commercial LMF (CLMF), or a Value-Added LMF (VLMF). A node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an enhanced serving mobile location center (E-SMLC) or a secure user plane location (SUPL) location platform (SLP). At least a portion of the positioning functionality (including the derivation of the location of UE 105) may be performed at UE 105 (e.g., using signal measurements obtained by UE 105 for signals sent by wireless nodes (such as gNB 110a, 110b and / or ng-eNB 114) and / or auxiliary data provided to UE 105 by LMF 120, for example). AMF 115 may serve as a control node for processing signaling between UE 105 and 5GC 140, and may provide QoS (quality of service) flow and session management. AMF 115 may support mobility of UE 105 (including cell changes and handovers), and may participate in supporting signaling connections to UE 105.

[0079] The server 150 (e.g., a cloud server) is configured to obtain a location estimate for the UE 105 and provide the location estimate to the external client 130. The server 150 may, for example, be configured to run a microservice / service that obtains a location estimate for the UE 105. The server 150 may, for example, obtain a location estimate from the UE 105, one or more of the gNBs 110a, 110b (e.g., via the RU 111, DU 112, and CU 113), and / or the ng-eNB 114, and / or the LMF 120 (e.g., by transmitting a location request to them). As another example, the UE 105, one or more of the gNBs 110a, 110b (e.g., via the RU 111, DU 112, and CU 113), and / or the LMF 120 may push the location estimate of the UE 105 to the server 150. Additionally or alternatively, the server 150 may function as a sensing server as discussed herein. For example, the server 150 may provide sensing assistance data to a sensing entity (e.g., a UE 105 or a base station 110), and may receive sensing measurements and / or sensing estimates generated by the sensing entity based at least in part on the sensing assistance data. In some implementations, the server 150 may be located outside the 5GC 140 when operating as a sensing server, while in other locations the server 150 may be located within the 5GC 140.

[0080] The GMLC 125 may support location requests for the UE 105 received from the external client 130 via the server 150, and may forward such location requests to the AMF 115 for forwarding by the AMF 115 to the LMF 120, or may forward the location requests directly to the LMF 120. A location response (e.g., containing a location estimate of the UE 105) from the LMF 120 may be returned to the GMLC 125 directly or via the AMF 115, and the GMLC 125 may then return the location response (e.g., containing the location estimate) to the external client 130 via the server 150. The GMLC 125 is shown as being connected to both the AMF 115 and the LMF 120, but may not be connected to either the AMF 115 or the LMF 120 in some implementations.

[0081] like Figure 1As further illustrated in FIG. 1 , LMF 120 may communicate with gNB 110a, 110b, and / or ng-eNB 114 using a new radio positioning protocol A (which may be referred to as NPPa or NRPPa), which may be defined in 3GPP Technical Specification (TS) 38.455. NRPPa may be the same as, similar to, or an extension of LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, wherein NRPPa messages are transmitted between gNB 110a (or gNB 110b) and LMF 120 and / or between ng-eNB 114 and LMF 120 via AMF 115. Figure 1 As further illustrated, the LMF 120 and the UE 105 may communicate using the LTE Positioning Protocol (LPP), which may be defined in 3GPP TS 36.355. The LMF 120 and the UE 105 may additionally or alternatively communicate using a new radio positioning protocol (which may be referred to as NPP or NRPP), which may be the same as, similar to, or an extension of the LPP. Here, LPP messages and / or NPP messages may be transmitted between the UE 105 and the LMF 120 via the AMF 115 and the serving gNB 110a, 110b or the serving ng-eNB 114 of the UE 105. For example, the LPP messages and / or NPP messages may be transmitted between the LMF 120 and the AMF 115 using the 5G Location Service Application Protocol (LCS AP), and may be transmitted between the AMF 115 and the UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP protocol and / or the NPP protocol may be used to support positioning of the UE 105 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, OTDOA, and / or E-CID. The NRPPa protocol may be used to support positioning of the UE 105 using a network-based positioning method such as E-CID (e.g., in conjunction with measurements obtained by the gNB 110a, 110b, or ng-eNB 114) and / or may be used by the LMF 120 to obtain location-related information from the gNB 110a, 110b, and / or ng-eNB 114, such as parameters defining directional SS (synchronization signal) or PRS transmissions from the gNB 110a, 110b, and / or ng-eNB 114. The LMF 120 may be co-located or integrated with the gNB or TRP, or may be located remotely from the gNB and / or TRP and configured to communicate directly or indirectly with the gNB and / or TRP.

[0082] Using UE-assisted positioning methods, UE 105 may obtain location measurements and transmit the measurements to a location server (e.g., LMF 120) for use in calculating a location estimate for UE 105. For example, the location measurements may include one or more of received signal strength indication (RSSI), round trip signal propagation time (RTT), reference signal time difference (RSTD), reference signal received power (RSRP), and / or reference signal received quality (RSRQ) of gNB 110a, 110b, ng-eNB 114, and / or WLAN APs. The location measurements may additionally or alternatively include measurements of GNSS pseudoranges, code phases, and / or carrier phases of SVs 190-193.

[0083] Using the UE-based positioning method, UE 105 can obtain a position measurement (e.g., the position measurement can be the same or similar to the position measurement for the UE-assisted positioning method), and the position of UE 105 can be calculated (e.g., with the aid of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base station or AP).

[0084] With network-based positioning methods, one or more base stations (e.g., gNBs 110a, 110b and / or ng-eNB 114) or APs may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or time of arrival (ToA) of signals sent by UE 105) and / or may receive measurements obtained by UE 105. The one or more base stations or APs may transmit the measurements to a location server (e.g., LMF 120) for use in calculating a location estimate for UE 105.

[0085] The information provided by gNB 110a, 110b and / or ng-eNB 114 to LMF 120 using NRPPa may include timing and configuration information for directional SS or PRS transmission and location coordinates. LMF 120 may provide some or all of this information to UE 105 as assistance data in an LPP message and / or an NPP message via NG-RAN 135 and 5GC 140.

[0086] The LPP message or NPP message transmitted from LMF 120 to UE 105 may instruct UE 105 to do any of a variety of things depending on the desired functionality. For example, the LPP message or NPP message may include instructions for UE 105 to obtain measurements for GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP message or NPP message may instruct UE 105 to obtain one or more measurements (e.g., beam ID measurements, beam width measurements, average angle measurements, RSRP measurements, RSRQ measurements) of directional signals transmitted within a particular cell supported by one or more of gNBs 110a, 110b, and / or ng-eNB 114 (or supported by some other type of base station (such as an eNB or WiFi AP)). UE 105 may transmit the measurement quantity back to LMF 120 in an LPP message or an NPP message (e.g., within a 5G NAS message) via serving gNB 110a (or serving ng-eNB 114) and AMF 115.

[0087] As noted, although the communication system 100 is described with respect to 5G technology, the communication system 100 may be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) for supporting and interacting with mobile devices such as UE 105 (e.g., to implement voice, data, positioning, and other functionality). In some such embodiments, the 5GC 140 may be configured to control different air interfaces. For example, the non-3GPP interworking function (N3IWF, Figure 1115) connects the 5GC 140 to the WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for the UE 105 and may include one or more WiFi APs. Here, the N3IWF may be connected to the WLAN and other elements in the 5GC 140, such as the AMF 115. In some embodiments, both the NG-RAN 135 and the 5GC 140 may be replaced by one or more other RANs and one or more other core networks. For example, in the EPS, the NG-RAN 135 may be replaced by an E-UTRAN including an eNB, and the 5GC 140 may be replaced by an EPC including a mobility management entity (MME) replacing the AMF 115, an E-SMLC replacing the LMF 120, and a GMLC that may be similar to the GMLC 125. In such an EPS, the E-SMLC may use LPPa instead of NRPPa to transmit location information to and receive location information from the eNB in ​​the E-UTRAN, and may use LPP to support positioning of the UE 105. In these other embodiments, positioning of UE 105 using directional PRS may be supported in a manner similar to that described herein for 5G networks, with the difference that the functions and processes described herein for gNB 110a, 110b, ng-eNB 114, AMF 115, and LMF 120 may in some cases be applied alternatively to other network elements, such as eNBs, WiFi APs, MMEs, and E-SMLCs.

[0088] As mentioned, in some embodiments, positioning functionality may be implemented at least in part using directional SS beams or directional PRS beams transmitted by a base station (such as gNB 110a, 110b and / or ng-eNB 114) at a UE (e.g., Figure 1 In some instances, the UE may use directional SS beams or directional PRS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the positioning of the UE.

[0089] Figure 2UE 200 is illustrated, which is an example of one of UEs 105, 106, and includes a computing platform including a processor 210, a memory 211 including software (SW) 212, one or more sensors 213, a transceiver interface 214 for a transceiver 215 (which includes a wireless transceiver 240 and a wired transceiver 250), a user interface 216, a satellite positioning system (SPS) receiver 217, a camera 218, and a positioning device (PD) 219. The processor 210, the memory 211, the sensor 213, the transceiver interface 214, the user interface 216, the SPS receiver 217, the camera 218, and the positioning device 219 are communicatively coupled to each other via a bus 220 (which may be configured, for example, for optical communication and / or electrical communication). One or more of the illustrated devices (e.g., the camera 218, the positioning device 219, and / or one or more of the sensors 213, etc.) may be omitted from the UE 200. The processor 210 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc. The processor 210 may include multiple processors, including a general / application processor 230, a digital signal processor (DSP) 231, a modem processor 232, a video processor 233, and / or a sensor processor 234. One or more processors in the processors 230-234 may include multiple devices (e.g., multiple processors). For example, the sensor processor 234 may include, for example, a processor for RF (radio frequency) sensing (wherein one or more (cellular) wireless signals and reflections sent are used to identify, map and / or track objects) and / or ultrasound, etc. The modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, a SIM (subscriber identity module or subscriber identity module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by a terminal user of the UE 200 to obtain connectivity. The memory 211 is a non-transitory storage medium that may include a random access memory (RAM), a flash memory, an optical disk memory, and / or a read-only memory (ROM), etc. Memory 211 stores software 212, which may be processor-readable, processor-executable software code containing instructions that are configured to cause processor 210 to perform various functions described herein when executed. Alternatively, software 212 may not be directly executable by processor 210, but may be configured to cause processor 210 to perform the functions, for example, when compiled and executed. The description may refer to processor 210 performing the functions, but this includes other implementations, such as implementations in which processor 210 executes software and / or firmware. The description may refer to processor 210 performing the functions as shorthand for one or more of processors 230-234 performing the functions.The description may refer to UE 200 performing a function as shorthand for one or more appropriate components of UE 200 performing the function. Processor 210 may include memory with stored instructions in addition to and / or in lieu of memory 211. The functionality of processor 210 is discussed more fully below.

[0090] Figure 2 The configuration of UE 200 shown in is an example and is not intended to limit the present disclosure (including the claims), and other configurations may be used. For example, an example configuration of the UE includes one or more of the processors 230-234 in the processor 210, a memory 211, and a wireless transceiver 240. Other example configurations include one or more of the processors 230-234 in the processor 210, a memory 211, a wireless transceiver, and one or more of the following: a sensor 213, a user interface 216, an SPS receiver 217, a camera 218, a PD 219, and / or a wired transceiver.

[0091] The UE 200 may include a modem processor 232 capable of performing baseband processing of signals received and down-converted by the transceiver 215 and / or the SPS receiver 217. The modem processor 232 may perform baseband processing of signals to be up-converted for transmission by the transceiver 215. Additionally or alternatively, the baseband processing may be performed by the general / application processor 230 and / or the DSP 231. However, other configurations may be used to perform baseband processing.

[0092] UE 200 may include a sensor 213, which may include, for example, one or more of various types of sensors, such as one or more inertial sensors, one or more magnetometers, one or more environmental sensors, one or more optical sensors, one or more weight sensors, and / or one or more radio frequency (RF) sensors, etc. An inertial measurement unit (IMU) may include, for example, one or more accelerometers (e.g., collectively responsive to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes (e.g., three-dimensional gyroscopes). Sensor 213 may include one or more magnetometers (e.g., three-dimensional magnetometers) to determine orientation (e.g., relative to magnetic north and / or true north), which may be used for any of a variety of purposes (e.g., to support one or more compass applications). Environmental sensors may include, for example, one or more temperature sensors, one or more air pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. Sensor 213 may generate analog and / or digital signals, indications of which may be stored in memory 211 and processed by DSP 231 and / or general / application processor 230 to support one or more applications (such as, for example, applications involving positioning operations and / or navigation operations).

[0093] The sensor 213 may be used for relative position measurement, relative position determination, motion determination, etc. The information detected by the sensor 213 may be used for motion detection, relative displacement, dead reckoning, sensor-based position determination, and / or sensor-assisted position determination. The sensor 213 may be used to determine whether the UE 200 is fixed (stationary) or moving and / or whether to report certain useful information related to the mobility of the UE 200 to the LMF 120. For example, based on the information obtained / measured by the sensor 213, the UE 200 may notify / report to the LMF 120 that the UE 200 has detected movement or that the UE 200 has moved, and report the relative displacement / distance (e.g., via dead reckoning or sensor-based position determination or sensor-assisted position determination implemented by the sensor 213). In another example, for relative positioning information, the sensor / IMU may be used to determine the angle and / or orientation of another device relative to the UE 200, etc.

[0094] The IMU may be configured to provide measurements of the direction of motion and / or speed of motion of the UE 200, which may be used for relative position determination. For example, one or more accelerometers and / or one or more gyroscopes of the IMU may detect the linear acceleration and rotational speed of the UE 200, respectively. The linear acceleration measurements and rotational speed measurements of the UE 200 may be integrated over time to determine the instantaneous direction of motion and displacement of the UE 200. The instantaneous direction of motion and displacement may be integrated to track the position of the UE 200. For example, the reference position of the UE 200 at a certain moment may be determined, for example, using the SPS receiver 217 (and / or by some other components), and the measurements obtained from the accelerometers and gyroscopes after that moment may be used for dead reckoning to determine the current position of the UE 200 based on the movement (direction and distance) of the UE 200 relative to the reference position.

[0095] The magnetometer may determine the strength of a magnetic field in different directions, which may be used to determine the orientation of the UE 200. For example, the orientation may be used to provide a digital compass for the UE 200. The magnetometer may include a two-dimensional magnetometer configured to detect magnetic field strength in two orthogonal dimensions and provide an indication of the magnetic field strength. The magnetometer may include a three-dimensional magnetometer configured to detect magnetic field strength in three orthogonal dimensions and provide an indication of the magnetic field strength. The magnetometer may provide a means for sensing a magnetic field and providing an indication of the magnetic field, for example, to the processor 210.

[0096] The transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless connections and wired connections, respectively. For example, the wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to an antenna 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and converting signals from the wireless signals 248 to wired signals (e.g., electrical signals and / or optical signals) and from wired signals (e.g., electrical signals and / or optical signals) to the wireless signals 248. The wireless transmitter 242 includes appropriate components (e.g., a power amplifier and a digital-to-analog converter). The wireless receiver 244 includes appropriate components (e.g., one or more amplifiers, one or more frequency filters, and an analog-to-digital converter). The wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 may be configured to communicate signals (e.g., with the TRP and / or one or more other devices) according to various radio access technologies (RATs), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE802.11p), WiFi, WiFi Direct (WiFi-D), Zigbee, etc. The new radio may use millimeter wave frequencies and / or frequencies below 6 GHz. The wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface that may be used to communicate with the NG-RAN 135 to transmit communications to the NG-RAN 135 and receive communications from the NG-RAN. The wired transmitter 252 may include a plurality of transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 254 may include a plurality of receivers that may be discrete components or combined / integrated components. The wired transceiver 250 may be configured, for example, for optical communication and / or electrical communication. The transceiver 215 may be communicatively coupled to the transceiver interface 214, for example, via an optical connection and / or an electrical connection. The transceiver interface 214 may be at least partially integrated with the transceiver 215. The wireless transmitter 242, the wireless receiver 244 and / or the antenna 246 may include multiple transmitters, multiple receivers and / or multiple antennas, respectively, for transmitting and / or receiving appropriate signals, respectively.

[0097] The user interface 216 may include one or more devices such as, for example, a speaker, a microphone, a display device, a vibration device, a keyboard, a touch screen, etc. The user interface 216 may include any device more than one of these devices. The user interface 216 may be configured to enable a user to interact with one or more applications hosted by the UE 200. For example, the user interface 216 may store an indication of an analog signal and / or a digital signal in the memory 211 in response to an action from the user to be processed by the DSP 231 and / or the general / application processor 230. Similarly, an application hosted on the UE 200 may store an indication of an analog signal and / or a digital signal in the memory 211 to present an output signal to the user. The user interface 216 may include an audio input / output (I / O) device, which includes, for example, a speaker, a microphone, a digital-to-analog circuit, an analog-to-digital circuit, an amplifier, and / or a gain control circuit (including any device more than one of these devices). Other configurations of audio I / O devices may be used. Additionally or alternatively, the user interface 216 may include one or more touch sensors that respond to touch and / or pressure on, for example, a keyboard and / or a touch screen of the user interface 216 .

[0098] The SPS receiver 217 (e.g., a global positioning system (GPS) receiver) can receive and acquire the SPS signal 260 via the SPS antenna 262. The SPS antenna 262 is configured to convert the SPS signal 260 from a wireless signal to a wired signal (e.g., an electrical signal or an optical signal) and can be integrated with the antenna 246. The SPS receiver 217 can be configured to process the acquired SPS signal 260 in whole or in part to estimate the position of the UE 200. For example, the SPS receiver 217 can be configured to determine the position of the UE 200 by performing trilateration using the SPS signal 260. The general / application processor 230, the memory 211, the DSP 231, and / or one or more dedicated processors (not shown) can be utilized in conjunction with the SPS receiver 217 to process the acquired SPS signal in whole or in part and / or calculate the estimated position of the UE 200. The memory 211 may store indications (e.g., measurements) of the SPS signals 260 and / or other signals (e.g., signals obtained from the wireless transceiver 240) for use in performing positioning operations. The general / application processor 230, the DSP 231, and / or one or more dedicated processors and / or the memory 211 may provide or support a location engine for processing measurements to estimate the location of the UE 200.

[0099] UE 200 may include a camera 218 for capturing still or moving images. Camera 218 may include, for example, an imaging sensor (e.g., a charge coupled device or a CMOS (complementary metal oxide semiconductor) imager), a lens, analog-to-digital circuits, a frame buffer, etc. Additional processing, conditioning, encoding, and / or compression of signals representing captured images may be performed by general / application processor 230 and / or DSP 231. Additionally or alternatively, video processor 233 may perform conditioning, encoding, compression, and / or manipulation of signals representing captured images. Video processor 233 may decode / decompress stored image data for presentation on a display device (not shown) (e.g., of user interface 216).

[0100] Positioning device (PD) 219 may be configured to determine the location of UE 200, the movement of UE 200, and / or the relative location of UE 200, and / or time. For example, PD 219 may communicate with SPS receiver 217 and / or include some or all of the SPS receivers. PD 219 may work appropriately with processor 210 and memory 211 to perform at least a portion of one or more positioning methods, but the description herein may refer to PD 219 being configured to perform according to the positioning method or the PD performing according to the positioning method. PD 219 may be additionally or alternatively configured to: use ground-based signals (e.g., at least some signals 248) for trilateration, assist in obtaining and use SPS signals 260, or both to determine the location of UE 200. PD 219 may be configured to determine the location of UE 200 based on the cell of a serving base station (e.g., cell center) and / or another technology (such as E-CID). The PD 219 may be configured to determine the location of the UE 200 using one or more images from the camera 218 and image recognition combined with known locations of landmarks (e.g., natural landmarks (such as mountains) and / or artificial landmarks (such as buildings, bridges, streets), etc.). The PD 219 may be configured to determine the location of the UE 200 using one or more other technologies (e.g., relying on the UE's self-reported location (e.g., part of the UE's location beacon)), and may use a combination of technologies (e.g., SPS and ground positioning signals) to determine the location of the UE 200. The PD 219 may include one or more sensors (e.g., gyroscopes, accelerometers, magnetometers, etc.) in the sensor 213, which may sense the orientation and / or movement of the UE 200 and provide an indication of the orientation and / or movement, and the processor 210 (e.g., the general / application processor 230 and / or the DSP 231) may be configured to use the indication to determine the movement of the UE 200 (e.g., velocity vector and / or acceleration vector). PD 219 may be configured to provide an indication of uncertainty and / or error in the determined position and / or motion. The functionality of PD 219 may be provided in a variety of ways and / or configurations, such as by general / application processor 230, transceiver 215, SPS receiver 217, and / or another component of UE 200, and may be provided by hardware, software, firmware, or various combinations thereof.

[0101] Figure 3An example of a TRP 300 illustrating a gNB 110a, 110b, and / or ng-eNB 114 includes a computing platform including a processor 310, a memory 311 including software (SW) 312, and a transceiver 315. The processor 310, the memory 311, and the transceiver 315 may be communicatively coupled to one another via a bus 320 (which may be configured, for example, for optical and / or electrical communications). One or more of the illustrated devices (e.g., a wireless transceiver) may be omitted from the TRP 300. The processor 310 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc. The processor 310 may include a plurality of processors (e.g., including a general / application processor, a DSP, a modem processor, a video processor, and / or a sensor processor, such as a processor). Figure 2 ). The memory 311 is a non-transitory storage medium that may include random access memory (RAM), flash memory, optical disk memory, and / or read-only memory (ROM), etc. The memory 311 stores software 312, which may be a processor-readable, processor-executable software code containing instructions that are configured to cause the processor 310 to perform various functions described herein when executed. Alternatively, the software 312 may not be directly executable by the processor 310, but may be configured to cause the processor 310 to perform the function, for example, when compiled and executed.

[0102] The description may refer to processor 310 performing a function, but this includes other specific implementations, such as a specific implementation in which processor 310 executes software and / or firmware. The description may refer to processor 310 performing a function as shorthand for one or more of the processors included in processor 310 performing the function. The description may refer to TRP 300 performing a function as shorthand for one or more appropriate components (e.g., processor 310 and memory 311) of TRP 300 (and thereby one of gNB 110a, 110b and / or ng-eNB 114) performing the function. Processor 310 may include a memory with stored instructions in addition to and / or in lieu of memory 311. The functionality of processor 310 is discussed more fully below.

[0103] The transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless connections and wired connections, respectively. For example, the wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels and / or one or more downlink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more uplink channels) wireless signals 348 and converting signals from the wireless signals 348 to wired signals (e.g., electrical signals and / or optical signals) and from wired signals (e.g., electrical signals and / or optical signals) to the wireless signals 348. Thus, the wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 may be configured to communicate in accordance with a plurality of radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Zigbee, etc.) to communicate signals (e.g., with UE 200, one or more other UEs, and / or one or more other devices). The wired transceiver 350 may include a wired transmitter 352 and a wired receiver 354 configured for wired communication, for example, a network interface that can be used to communicate with the NG-RAN 135 to send communications to, for example, the LMF 120 and / or one or more other network entities and receive communications therefrom. The wired transmitter 352 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 354 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 350 may be configured, for example, for optical communication and / or electrical communication.

[0104] Figure 3 The configuration of the TRP 300 shown in is an example and is not a limitation of the present disclosure (including the claims), and other configurations may be used. For example, the description herein discusses that the TRP 300 is configured to perform several functions or that the TRP performs several functions, but one or more of these functions may be performed by the LMF 120 and / or the UE 200 (i.e., the LMF 120 and / or the UE 200 may be configured to perform one or more of these functions).

[0105] Figure 4 The server 400 (LMF 120 or server 150 may be an example thereof) is illustrated to include: a computing platform including a processor 410, a memory 411 including software (SW) 412, and a transceiver 415. The processor 410, the memory 411, and the transceiver 415 may be communicatively coupled to each other via a bus 420 (the bus may be configured, for example, for optical communication and / or electrical communication). One or more of the devices shown (e.g., a wireless transceiver) may be omitted from the server 400. The processor 410 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc. The processor 410 may include a plurality of processors (e.g., including a general / application processor, a DSP, a modem processor, a video processor, and / or a sensor processor, such as Figure 2 ). Memory 411 is a non-transitory storage medium that may include random access memory (RAM), flash memory, optical disk storage, and / or read-only memory (ROM), etc. Memory 411 stores software 412, which may be a processor-readable, processor-executable software code containing instructions that are configured to cause processor 410 to perform various functions described herein when executed. Alternatively, software 412 may not be directly executable by processor 410, but may be configured to cause processor 410 to perform the function, for example, when compiled and executed. The description may refer to processor 410 performing a function, but this includes other specific implementations, such as specific implementations in which processor 410 executes software and / or firmware. The description may refer to processor 410 performing a function as a shorthand for one or more of the processors included in processor 410 performing the function. The description may refer to server 400 performing a function as a shorthand for one or more appropriate components of server 400 performing the function. Processor 410 may include a memory with stored instructions as a supplement and / or alternative to memory 411. The functionality of processor 410 is discussed more fully below.

[0106] The transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless connections and wired connections, respectively. For example, the wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting (e.g., on one or more downlink channels) and / or receiving (e.g., on one or more uplink channels) wireless signals 448 and converting signals from the wireless signals 448 to wired signals (e.g., electrical signals and / or optical signals) and from wired signals (e.g., electrical signals and / or optical signals) to the wireless signals 448. Thus, the wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 may be configured to communicate in accordance with a plurality of radio access technologies (RATs) such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Phone System), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Zigbee, etc.) to communicate signals (e.g., with UE 200, one or more other UEs, and / or one or more other devices). The wired transceiver 450 may include a wired transmitter 452 and a wired receiver 454 configured for wired communication, for example, a network interface that can be used to communicate with the NG-RAN 135 to send communications to, for example, the TRP 300 and / or one or more other network entities and receive communications therefrom. The wired transmitter 452 may include multiple transmitters that may be discrete components or combined / integrated components, and / or the wired receiver 454 may include multiple receivers that may be discrete components or combined / integrated components. The wired transceiver 450 may be configured, for example, for optical communication and / or electrical communication.

[0107] The description herein may refer to processor 410 performing a function, but this includes other implementations, such as implementations in which processor 410 executes software (stored in memory 411) and / or firmware. The description herein may refer to server 400 performing a function as shorthand for one or more appropriate components of server 400 (e.g., processor 410 and memory 411) performing that function.

[0108] Figure 4The configuration of the server 400 shown in is an example and is not intended to limit the present disclosure (including the claims), and other configurations may be used. For example, the wireless transceiver 440 may be omitted. Additionally or alternatively, the description herein discusses that the server 400 is configured to perform several functions or that the server performs several functions, but one or more of these functions may be performed by the TRP 300 and / or the UE 200 (i.e., the TRP 300 and / or the UE 200 may be configured to perform one or more of these functions).

[0109] Positioning Technology

[0110] For terrestrial positioning of UEs in cellular networks, techniques such as Advanced Forward Link Trilateration (AFLT) and Observed Time Difference of Arrival (OTDOA) typically operate in a "UE-assisted" mode, where measurements of reference signals (e.g., downlink Positioning Reference Signal (PRS), Cell-Specific Reference Signal (CRS), etc.) transmitted by base stations are acquired by the UE and then provided to a location server. The location server then calculates the position of the UE based on the measurements and the known positions of the base stations. Because these techniques use a location server (rather than the UE itself) to calculate the position of the UE, these positioning techniques are not frequently used in applications such as automotive or cell phone navigation, which instead typically rely on satellite-based positioning.

[0111] The UE can use a Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to use Precise Point Positioning (PPP) or Real-Time Kinematics (RTK) techniques for high accuracy positioning. These techniques use assistance data, such as measurements from ground-based stations. LTE Release 15 allows the data to be encrypted so that only UEs subscribed to the service can read the information. Such assistance data changes over time. As a result, a UE subscribed to the service may not be able to easily "crack the encryption" for other UEs by passing the data to other UEs that have not paid for the subscription. This transfer needs to be repeated each time the assistance data changes.

[0112] In UE-assisted positioning, the UE transmits measurements (e.g., TDOA, Angle of Arrival (AoA), etc.) to a positioning server (e.g., LMF / eSMLC). The positioning server has a base station almanac (BSA) that contains multiple "entries" or "records", one record per cell, where each record contains a geographic cell location, but may also include other data. An identifier of a "record" among multiple "records" in the BSA may be referenced. The BSA and the measurements from the UE may be used to calculate the positioning of the UE.

[0113] In conventional UE-based positioning, the UE calculates its own position, avoiding the transmission of measurements to the network (e.g., a location server), which in turn improves latency and scalability. The UE uses relevant BSA record information from the network (e.g., the location of the gNB (more broadly, base stations)). The BSA information can be encrypted. However, since the BSA information changes much less frequently than, for example, the PPP or RTK assistance data described previously, it may be easier (compared to PPP or RTK information) to make the BSA information available to UEs that are not subscribed and have not paid for decryption keys. The transmission of reference signals by the gNB makes the BSA information potentially accessible to crowdsourcing or driving attacks, essentially enabling the BSA information to be generated based on in-the-field observations and / or over-the-top observations.

[0114] Positioning techniques may be characterized and / or evaluated based on one or more criteria, such as positioning determination accuracy and / or latency. Latency is the time elapsed between an event that triggers the determination of positioning-related data and the availability of the data at a positioning system interface (e.g., an interface of LMF 120). When the positioning system is initialized, the latency for the availability of positioning-related data is called the time to first fix (TTFF) and is greater than the latency after the TTFF. The inverse of the time elapsed between two consecutive positioning-related data availabilities is called the update rate, i.e., the rate at which positioning-related data is generated after the first fix. Latency may depend on (e.g., UE's) processing capabilities. For example, assuming 272 PRBs (physical resource blocks) are allocated, the UE may report the processing capabilities of the UE as the duration (in time units (e.g., milliseconds) of the DL PRS symbols that the UE can process per T amount of time (e.g., Tms). Other examples of capabilities that may affect latency are the number of TRPs from which the UE can process PRSs, the number of PRSs that the UE can process, and the bandwidth of the UE.

[0115] One or more of many different positioning techniques (also referred to as positioning methods) may be used to determine the location of an entity (such as one of UEs 105, 106). For example, known positioning determination techniques include RTT, multi-RTT, OTDOA (also referred to as TDOA and including UL-TDOA and DL-TDOA), enhanced cell identification (E-CID), DL-AoD, UL-AoA, etc. RTT uses the time it takes for a signal to travel from one entity to another and back to determine the distance between the two entities. This distance plus the known position of a first one of the entities and the angle (e.g., azimuth) between the two entities may be used to determine the position of a second one of the entities. In multi-RTT (also referred to as multi-cell RTT), multiple distances from one entity (e.g., UE) to other entities (e.g., TRP) and the known positions of the other entities may be used to determine the position of the one entity. In TDOA techniques, the travel time difference between one entity and the other entities may be used to determine the relative distance to the other entities, and the relative distance combined with the known positions of the other entities may be used to determine the position of the one entity. The angle of arrival and / or angle of departure can be used to help determine the location of an entity. For example, the angle of arrival or angle of departure of a signal combined with the distance between devices (the distance determined using the signal (e.g., the travel time of the signal, the received power of the signal, etc.)) and the known position of one of the devices can be used to determine the location of the other device. The angle of arrival or angle of departure can be an azimuth relative to a reference direction (such as true north). The angle of arrival or angle of departure can be a zenith angle relative to directly upward from the entity (i.e., relative to radially outward from the center of the earth). E-CID uses the identity of the serving cell, the timing advance (i.e., the difference between the reception time and the transmission time at the UE), the estimated timing and power of the detected neighbor cell signals, and the possible angle of arrival (e.g., the angle of arrival of the signal from the base station at the UE, or vice versa) to determine the location of the UE. In TDOA, the difference in the arrival time of signals from different sources at the receiving device together with the known positions of these sources and the known offsets of the transmission times from these sources are used to determine the location of the receiving device.

[0116] In network-centric RTT estimation, a serving base station commands a UE to scan / receive RTT measurement signals (e.g., PRS) on serving cells of two or more neighboring base stations (and typically a serving base station, since at least three base stations are required). The one or more base stations transmit RTT measurement signals on low reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., a location server, such as LMF 120). The UE records the arrival time (also referred to as reception time, received time, received time, or arrival time (ToA)) of each RTT measurement signal relative to the current downlink timing of the UE (e.g., as derived by the UE from a DL signal received from its serving base station), and (e.g., when commanded by its serving base station) transmits a common or individual RTT response message (e.g., an SRS (sounding reference signal) for positioning, i.e., UL-PRS) to the one or more base stations, and may calculate the time difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx The UE TRx-Tx or UE ERx-Tx is included in the payload of each RTT response message. The RTT response message will include a reference signal from which the base station can infer the ToA of the RTT response. The difference T between the transmission time of the RTT measurement signal from the base station and the ToA of the RTT response at the base station is calculated by comparing the difference T between the transmission time of the RTT measurement signal from the base station and the ToA of the RTT response at the base station. Tx→Rx The time difference T reported by the UE Rx→Tx , the base station can infer the propagation time between the base station and the UE, from which the base station can determine the distance between the UE and the base station by assuming the speed of light during the propagation time.

[0117] UE-centric RTT estimation is similar to the network-based approach, except that the UE sends an uplink RTT measurement signal (e.g., when ordered by a serving base station), which is received by multiple base stations in the vicinity of the UE. Each base station involved responds with a downlink RTT response message, which may include in the RTT response message payload the time difference between the ToA of the RTT measurement signal at the base station and the transmission time of the RTT response message from the base station.

[0118] For both network-centric and UE-centric processes, the side performing the RTT calculation (the network or the UE) typically (but not always) sends a first message or signal (e.g., an RTT measurement signal), and the other side responds with one or more RTT response messages or signals, which may include the difference between the ToA of the first message or signal and the sending time of the RTT response message or signal.

[0119] Multi-RTT techniques may be used to determine positioning. For example, a first entity (e.g., a UE) may transmit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and a plurality of second entities (e.g., other TSPs, such as base stations and / or UEs) may receive signals from the first entity and respond to the received signals. The first entity receives responses from the plurality of second entities. The first entity (or another entity, such as an LMF) may use the responses from the second entity to determine the distance to the second entity, and may use the plurality of distances and the known positions of the second entity to determine the position of the first entity by trilateration.

[0120] In some instances, additional information may be obtained in the form of an angle of arrival (AoA) or angle of departure (AoD) that defines a straight line direction (e.g., which may be in the horizontal plane or in three dimensions) or a range of possible directions (e.g., of the UE as seen from the location of a base station). The intersection of the two directions may provide another estimate of the UE's position.

[0121] For positioning techniques (e.g., TDOA and RTT) that use PRS (positioning reference signal) signals, PRS signals transmitted by multiple TRPs are measured, and the arrival times of these signals, the known transmission times, and the known locations of the TRPs are used to determine the distance from the UE to the TRP. For example, RSTD (reference signal time difference) can be determined for PRS signals received from multiple TRPs, and the RSTD can be used in the TDOA technique to determine the location (position) of the UE. Positioning reference signals may be referred to as PRS or PRS signals. PRS signals are typically transmitted using the same power, and PRS signals with the same signal characteristics (e.g., the same frequency shift) may interfere with each other, so that PRS signals from farther TRPs may be drowned out by PRS signals from closer TRPs, so that signals from farther TRPs may not be detected. PRS muting can be used to help reduce interference by muting some PRS signals (reducing the power of the PRS signal, for example, to zero and thereby not sending the PRS signal). In this way, the UE can more easily detect (at the UE) a weaker PRS signal without a stronger PRS signal interfering with the weaker PRS signal. The term RS and its variants (e.g., PRS, SRS, CSI-RS (Channel State Information - Reference Signal)) may refer to one reference signal or more than one reference signal.

[0122] The positioning reference signal (PRS) includes a downlink PRS (DL PRS, often referred to as PRS for short) and an uplink PRS (UL PRS) (the uplink PRS may be referred to as an SRS (sounding reference signal) for positioning). The PRS may include a PN code (pseudo-random number) or be generated using a PN code (e.g., by modulating a carrier signal with a PN code) so that the source of the PRS can be used as a pseudo-satellite. The PN code may be unique to the PRS source (at least unique within a specified area, so that the same PRS from different PRS sources do not overlap). The PRS may include PRS resources and / or PRS resource sets of a frequency layer. The DL PRS positioning frequency layer (or simply frequency layer) is a collection of DL PRS resource sets from one or more TRPs, whose PRS resources have common parameters configured by higher-layer parameters DL-PRS-PositioningFrequencyLayer, DL-PRS-ResourceSet, and DL-PRS-Resource. Each frequency layer has a DL PRS subcarrier spacing (SCS) for the DL PRS resource set and DL PRS resources in the frequency layer. Each frequency layer has a DL PRS cyclic prefix (CP) for the DL PRS resource set and DL PRS resources in the frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. A common resource block is a set of resource blocks that occupy a channel bandwidth. A bandwidth part (BWP) is a set of consecutive common resource blocks and may include all common resource blocks within the channel bandwidth or a subset of the common resource blocks. In addition, the DL PRS point A parameter defines the frequency of the reference resource block (and the lowest subcarrier of the resource block), where DL PRS resources belonging to the same DL PRS resource set have the same point A, and all DL PRS resource sets belonging to the same frequency layer have the same point A. The frequency layers also have the same DL PRS bandwidth, the same starting PRB (and center frequency), and the same comb size value (i.e., the frequency of the PRS resource elements per symbol, so that for comb-N, every Nth resource element is a PRS resource element). A PRS resource set is identified by a PRS resource set ID and may be associated with a specific TRP (identified by a cell ID) transmitted by an antenna panel of a base station. A PRS resource ID in a PRS resource set may be associated with an omni-directional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station may transmit one or more beams). Each PRS resource in a PRS resource set may be transmitted on a different beam, and as such, a PRS resource (or simply a resource) may also be referred to as a beam. This does not imply anything about whether the base station and beam on which the PRS is transmitted are known to the UE.

[0123] The TRP may be configured, for example, by instructions received from a server and / or by software in the TRP to transmit DL PRS on a schedule. According to the schedule, the TRP may transmit DL PRS intermittently (e.g., periodically at consistent intervals from the initial transmission). The TRP may be configured to transmit one or more PRS resource sets. A resource set is a collection of PRS resources across a TRP, where the resources have the same periodicity, a common muting mode configuration (if any), and the same cross-slot repetition factor. Each PRS resource set in a PRS resource set includes a plurality of PRS resources, where each PRS resource includes a plurality of OFDM (orthogonal frequency division multiplexing) resource elements (REs), which may be in a plurality of resource blocks (RBs) within N (one or more) consecutive symbols within a slot. PRS resources (or, in general, reference signal (RS) resources) may be referred to as OFDM PRS resources (or OFDMRS resources). RBs are RE sets that span a certain number of one or more consecutive symbols in the time domain and a certain number (12 for 5G RBs) of consecutive subcarriers in the frequency domain. Each PRS resource is configured with an RE offset, a slot offset, a symbol offset within a slot, and the number of consecutive symbols that the PRS resource can occupy within a slot. The RE offset defines the starting RE offset in frequency for the first symbol within the DL PRS resource. The relative RE offsets of the remaining symbols within the DL PRS resource are defined based on the initial offset. The slot offset is the starting slot of the DL PRS resource relative to the corresponding resource set slot offset. The symbol offset determines the starting symbol of the DL PRS resource within the starting slot. The transmitted REs may be repeated across slots, where each transmission is referred to as a repetition, so that there may be multiple repetitions in the PRS resource. The DL PRS resources in a DL PRS resource set are associated with the same TRP, and each DL PRS resource has a DL PRS resource ID. The DL PRS resource ID in a DL PRS resource set is associated with a single beam transmitted from a single TRP (although a TRP may transmit one or more beams).

[0124] PRS resources can also be defined by quasi-co-location parameters and starting PRB parameters. Quasi-co-location (QCL) parameters can define any quasi-co-location information of DLPRS resources and other reference signals. DL PRS can be configured as QCL type D with DL PRS or SS / PBCH (synchronization signal / physical broadcast channel) blocks from a serving cell or a non-serving cell. DL PRS can be configured as QCL type C with SS / PBCH blocks from a serving cell or a non-serving cell. The starting PRB parameter defines the starting PRB index of the DLPRS resource with respect to reference point A. The starting PRB index has a granularity of one PRB and can have a minimum value of 0 PRBs and a maximum value of 2176 PRBs.

[0125] A PRS resource set is a collection of PRS resources with the same periodicity, the same muting pattern configuration (if any), and the same repetition factor across time slots. Each time all repetitions of all PRS resources in a PRS resource set are configured to be transmitted is referred to as an "instance". Thus, an "instance" of a PRS resource set is a specified number of repetitions for each PRS resource and a specified number of PRS resources within a PRS resource set, such that once the specified number of repetitions is transmitted for each of the specified number of PRS resources, the instance is complete. An instance may also be referred to as an "opportunity". A DL PRS configuration including a DL PRS transmission schedule may be provided to a UE to facilitate (or even cause) the UE to measure a DL PRS.

[0126] Multiple frequency layers of PRS can be aggregated to provide an effective bandwidth that is greater than any bandwidth in the bandwidth of each layer. Multiple frequency layers belonging to a component carrier (which can be continuous and / or separate) and satisfying criteria such as quasi co-location (QCL) and having the same antenna port can be spliced ​​to provide a larger effective PRS bandwidth (for DL ​​PRS and UL PRS), thereby improving the accuracy of arrival time measurement. Splicing includes combining PRS measurements on various bandwidth segments into a unified fragment so that the spliced ​​PRS can be regarded as taken from a single measurement. In the case of quasi co-location, different frequency layers behave similarly, so that the splicing of PRS produces a larger effective bandwidth. The larger effective bandwidth (which can be referred to as the bandwidth of the aggregated PRS or the frequency bandwidth of the aggregated PRS) provides better time domain resolution (e.g., the resolution of TDOA). The aggregated PRS includes a collection of PRS resources, and each PRS resource in the aggregated PRS can be referred to as a PRS component, and each PRS component can be sent on different component carriers, frequency bands or frequency layers, or on different parts of the same frequency band.

[0127] RTT positioning is an active positioning technology because RTT uses positioning signals transmitted by the TRP to the UE and positioning signals transmitted by the UE (participating in RTT positioning) to the TRP. The TRP can transmit a DL-PRS signal received by the UE, and the UE can transmit an SRS (sounding reference signal) signal received by multiple TRPs. The sounding reference signal may be referred to as an SRS or an SRS signal. In 5G multi-RTT, coordinated positioning can be used, in which the UE transmits a single UL-SRS for positioning received by multiple TRPs, rather than transmitting a separate UL-SRS for positioning for each TRP. The TRP participating in multi-RTT will typically search for UEs currently residing on the TRP (served UEs, where the TRP is the serving TRP) and also search for UEs residing on adjacent TRPs (neighboring UEs). The neighbor TRP may be the TRP of a single BTS (base transceiver station) (e.g., a gNB), or may be the TRP of one BTS and the TRP of a separate BTS. For RTT positioning (including multi-RTT positioning), the DL-PRS signal and the UL-SRS positioning signal in the PRS / SRS positioning signal pair used to determine the RTT (and thereby the distance between the UE and the TRP) may occur close to each other in time so that errors due to UE motion and / or UE clock drift and / or TRP clock drift are within acceptable limits. For example, the signals in the PRS / SRS positioning signal pair may be sent from the TRP and the UE, respectively, within approximately 10 ms of each other. In the case where the SRS positioning signal is being transmitted by the UE and the PRS and SRS positioning signals are communicated close to each other in time, it has been found that radio frequency (RF) signal congestion may result (which may result in excessive noise, etc.) (especially if many UEs are attempting to locate concurrently), and / or computational congestion may result at the TRP where many UEs are attempting to be measured concurrently.

[0128] RTT positioning can be UE-based or UE-assisted. In UE-based RTT, UE 200 determines the RTT and corresponding distance to each TRP in TRP 300, and determines the positioning of UE 200 based on the distance to TRP 300 and the known position of TRP 300. In UE-assisted RTT, UE 200 measures the positioning signal and provides the measurement information to TRP 300, and TRP 300 determines RTT and distance. TRP 300 provides the distance to a location server (e.g., server 400), and the server determines the position of UE 200 based on the distance to different TRPs 300, for example. RTT and / or distance can be determined by TRP 300 receiving signals from UE 200, determined by the TRP 300 in combination with one or more other devices (e.g., one or more other TRPs 300 and / or server 400), or determined by one or more devices other than TRP 300 that receive signals from UE 200.

[0129] Various positioning technologies are supported in 5G NR. The NR native positioning methods supported in 5G NR include DL-only positioning methods, UL-only positioning methods, and DL+UL positioning methods. Downlink-based positioning methods include DL-TDOA and DL-AoD. Uplink-based positioning methods include UL-TDOA and UL-AoA. Combined DL+UL-based positioning methods include RTT with one base station and RTT with multiple base stations (multi-RTT).

[0130] A positioning estimate (e.g., for a UE) may be referred to by other names, such as position estimate, position, fix, position fix, fix, etc. The positioning estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, postal address, or some other textual description of the location. The positioning estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The positioning 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).

[0131] RF Sensing

[0132] Radio frequency sensing (RF sensing) is a technology for sensing the presence and / or movement of one or more objects in an environment based at least in part on the transmission and reception of electromagnetic signals. RF sensing uses infrastructure (e.g., base stations and UEs) and the time and frequency resources of a cellular communication system to measure the environment of a transmitting device and a receiving device to detect the presence and / or movement of objects. Changes in the environment can be detected based on changes in a wireless communication channel between a transmitting device and a receiving device. For example, the presence or movement of an object in the environment can interfere with or otherwise change the phase or amplitude of a wireless communication signal sent from a transmitting device, reflected by an object, and received by a receiving device and thereby interfere with or otherwise change the wireless channel. The scope of application and / or accuracy of RF sensing may depend on the amount and / or detail of information communicated between the transmitting device and the receiving device.

[0133] For example, a wireless communication network that complies with the IEEE (Institute of Electrical and Electronics Engineers) 802.11 family of standards (such as WLAN) can be used to implement the RF sensing system. A transmitting device can send a sounding data set to a receiving device on a wireless channel. The sounding data set may include information carried in one or more training fields configured for channel estimation and sounding control information based at least in part on the configuration of the transmitting device. The receiving device can obtain the CSI of the wireless channel based on the received sounding data set and selectively generate a channel report for the wireless channel based at least in part on the CSI and the sounding control information. For example, the receiving device can generate a channel report only when the characteristics of the wireless channel have changed by at least a threshold amount. The channel report can indicate a change to the wireless channel, which in turn can be used to sense one or more objects near the transmitting device and / or the receiving device.

[0134] The CSI report may be provided, for example, to a base station or other network entity based on one or more measurements of a CSI-RS (channel state information-reference signal). For example, the CSI may include a CQI (channel quality indicator), a RI (rank indicator), and / or a PMI (precoding matrix indicator) that may be derived from one or more measurements of the CSI-RS. Additionally or alternatively, the CSI may include other information such as a CSI-RS indicator (CRI), a layer indicator (LI), a SS / PBCH block resource indicator (synchronization signal / physical broadcast channel BRI (SSBRI)), and / or a L-1 RSRP (layer 1 RSRP).

[0135] Techniques for using cellular communication systems (e.g., 5G and above) for RF sensing are discussed herein. The large bandwidth provided for such cellular communication systems may allow such cellular communication systems to provide accurate RF sensing services. Upper layer (e.g., MAC layer and above) processes for positioning (e.g., NR UE positioning) may be reused or modified (e.g., enhanced) for providing RF sensing services. PRS may be used for RF sensing, for example, due to the large bandwidth of PRS in the physical layer (PHY). For example, in FR1 (450 MHz-6 GHz (range below 6 GHz)), PRS may have a bandwidth of 100 MHz, in FR2 (24.25 GHz-52.6 GHz (millimeter wave)), PRS may have a bandwidth of 400 MHz, and for FR3 (10 GHz-20 GHz, e.g., 13 GHz), PRS may have a bandwidth of 200 MHz. In terahertz (THz) signaling, PRS may have a bandwidth of 1 GHz or more (e.g., for short-range (e.g., several meters) RF sensing). In addition, carrier aggregation can be used to increase the bandwidth of PRS.

[0136] Figure 5 5. A sensing entity 500 is illustrated that can be used for RF sensing as discussed herein. The sensing entity 500 includes a processor 510, a transceiver 520, and a memory 530 that are communicatively coupled to each other via a bus 540. For example, the sensing entity 500 may be a UE or a base station. For example, the sensing entity 500 may include one or more other components, such as Figure 2 Any of those components shown in FIG. 2 , so that the UE 200 may be an example of the sensing entity 500, and / or Figure 3 , so that TRP 300 can be an example of sensing entity 500. For example, processor 510 may include one or more of the components of processor 210. Transceiver 520 may include one or more of the components of transceiver 215, for example, wireless transmitter 242 and antenna 246, or wireless receiver 244 and antenna 246, or wireless transmitter 242, wireless receiver 244, and antenna 246. Additionally or alternatively, transceiver 520 may include wired transmitter 252 and / or wired receiver 254. Memory 530 may be configured similarly to memory 211, for example, including software having processor-readable instructions configured to cause processor 510 to perform functions. As another example, processor 510 may include one or more of the components of processor 310, transceiver 520 may include one or more of the components of transceiver 315, and memory 530 may be configured similarly to memory 311, e.g., including software having processor-readable instructions configured to cause processor 510 to perform functions.

[0137] The description herein may refer to the processor 510 performing a function, but this includes other specific implementations, such as a specific implementation in which the processor 510 executes software (stored in the memory 530) and / or firmware. The description herein may refer to the sensing entity 500 performing a function as shorthand for one or more appropriate components of the sensing entity 500 (e.g., the processor 510 and the memory 530) performing the function. The processor 510 (possibly in combination with the memory 530 and, where appropriate, the transceiver 520) may include one or more units or modules for performing the functions described herein. For example, the processor 510 may include a sensing protocol unit 550, a sensing assistance data (AD) unit 560, a sensing measurement unit 570, and a sensing estimation unit 580. The sensing protocol unit 550, the sensing assistance data (AD) unit 560, the sensing measurement unit 570, and the sensing estimation unit 580 are discussed further below, and the description may generally refer to the processor 510 or generally the sensing entity 500 as performing any functions of the sensing protocol unit 550, the sensing assistance data (AD) unit 560, the sensing measurement unit 570, and the sensing estimation unit 580. The sensing entity 500 is configured to perform the functions of the sensing protocol unit 550, the sensing assistance data (AD) unit 560, the sensing measurement unit 570, and the sensing estimation unit 580 discussed herein.

[0138] Figure 6 6. A network entity 600 is illustrated that may be used for RF sensing as discussed herein. The sensing entity 600 includes a processor 610, a transceiver 620, and a memory 630 that are communicatively coupled to each other via a bus 640. The network entity 600 may include one or more other components such as Figure 3 and / or Figure 4 ), so that TRP 300 and / or server 400 may be examples of network entity 600. For example, processor 610 may include one or more of the components of processor 310 and / or processor 410. Transceiver 620 may include one or more of the components of transceiver 315 and / or transceiver 415. Memory 630 may be configured similarly to memory 311 and / or memory 411, for example, including software having processor-readable instructions configured to cause processor 610 to perform functions.

[0139] The description herein may refer to the processor 610 performing a function, but this includes other specific implementations, such as a specific implementation in which the processor 610 executes software (stored in the memory 630) and / or firmware. The description herein may refer to the network entity 600 performing a function as shorthand for one or more appropriate components of the network entity 600 (e.g., the processor 610 and the memory 630) performing the function. The processor 610 (possibly in combination with the memory 630 and, where appropriate, the transceiver 620) may include one or more units or modules for performing the functions described herein. For example, the processor 610 may include a sensing procedure unit 650, a sensing assistance data (AD) unit 660, a sensing measurement unit 670, and a sensing estimation unit 680. The sensing procedures unit 650, the sensing assistance data (AD) unit 660, the sensing measurement unit 670, and the sensing estimation unit 680 are discussed further below, and the description may generally refer to the processor 610, or generally the network entity 600, as performing any functionality of the sensing procedures unit 650, the sensing assistance data (AD) unit 660, the sensing measurement unit 670, and the sensing estimation unit 680. The network entity 600 is configured to perform the functionality of the sensing procedures unit 650, the sensing assistance data (AD) unit 660, the sensing measurement unit 670, and the sensing estimation unit 680 discussed herein.

[0140] RF sensing may include a single-base system or a multi-base system. A single-base system includes a device that both transmits a signal and receives reflections of the signal. A single-base system can be used to identify the motion state of a transmitting / receiving device or to identify objects in the environment of a transmitting / receiving device. A multi-base system includes a system with a receiving device that is different from the transmitting device. For example, one or more transmitting devices transmit a signal, and one or more separate receiving devices receive reflections of the signal from an object. An example multi-base system is a dual-base system, where one transmitting device transmits and one receiving device receives, but there may be any number of transmitting devices or receiving devices. A multi-base system can be used to identify the motion state of an object that reflects a signal.

[0141] Figure 7 An example bistatic RF sensing system 700 is shown. The bistatic system 700 includes a transmitter (TX) 710 and a receiver (RX) 720. The transmitter 710 and the receiver 720 are spatially separated by a baseline (L). In some implementations, the transmitter 710 may be an example of a base station 110 (or a UE 105 or 106), and the receiver 720 may be an example of a base station 110 (or a UE 105 or 106). Figure 1 An example of one of the different base stations 102 (or UE 105 or 106).

[0142] Transmitter 710 is configured to send pulses 712 in several directions. Each of these pulses 712 may be a beamformed RF signal having a particular width and directionality. An object or surface along the trajectory of any of these pulses 712 may cause the pulse 712 to reflect or scatter. The reflected pulse may be referred to as an "echo" of the pulse from which it originated. Figure 7 In the example of FIG. 7 , target object 701 is located along the path of one of pulses 712. Pulse 712(i) incident on target object 701 is reflected as echo 722. Figure 7 As shown, echo 722 is reflected in the direction of receiver 720. Receiver 720 may determine ranging information about target object 701 based at least in part on the timing of echo 722. Example ranging information may include, but is not limited to, a distance, direction, or speed of target object 701.

[0143] In some implementations, the receiver 720 can determine the distance L between the transmitter 710 and the receiver 720 based at least in part on the baseline distance L, the angle of arrival (θ R ) and the flight time (τ) of the incident pulse 712 (i) sent by the transmitter 710 to the echo 722 received by the receiver 720 to determine the distance (R) of the target object 701 relative to the receiver 720 R ). More specifically, the distance R can be calculated according to Formula 1: R .

[0144]

[0145] Where R T +R R represents the combined distance from the target object 701 to each of the transmitter 710 and the receiver 720. Figure 7 As shown, R T +R R A distance range 702 (in an elliptical shape) around the transmitter 710 and the receiver 720 where the target object 701 may be located is defined. More specifically, it can be calculated according to Formula 2 as a function of the baseline (L), the flight time of the reflected pulse (τ), and the propagation speed of the pulse (c p ) to calculate R T +R R .

[0146] R T +R R =c p τ+L (2)

[0147] Refer to Formula 1 and Formula 2, baseline L and propagation speed c prepresents a fixed or preconfigured value inherent to system 700. The arrival angle θ may be determined based on the time difference of arrival (TDOA) of echo 722 between different receiving antennas of receiver 720 in the antenna array or based on the antenna sector (corresponding to a preset beam of a phased array antenna) used by receiver 720 to receive echo 722. R However, in order to calculate the flight time τ, the receiver 720 must have knowledge of the time at which the incident pulse 712 (i) was transmitted at the receiver's location. More specifically, the transmission time (T) of the incident pulse can be varied according to Equation 3. 脉冲 ) and the echo receiving time (T 回波 ) to calculate the flight time τ.

[0148] τ=T 回波 -T 脉冲 (3)

[0149] For a fixed transmitter 710 and a fixed receiver 720, the target bistatic Doppler frequency is given by:

[0150]

[0151] Where v is the velocity of the target object 701, β is the departure angle θ T and the arrival angle θ R The difference between , and δ is the angle between the velocity vector v and the angle β.

[0152] Because the transmitter 710 and the receiver 720 are implemented in (or correspond to) separate wireless communication devices, the transmitter 710 may need to communicate the transmission timing T of the incident pulse to the receiver 720. 脉冲 However, because the transmitter 710 transmits pulses 712 in several directions, the transmitter 710 may not know which of the pulses 712 is incident on the target object 701. Therefore, the transmitter 710 may need to communicate the timing of each of the pulses 712 to the receiver 720, and the receiver 720 may need to determine which of the pulses 712 caused the echo 722. In some implementations, a packet format according to the IEEE 802.11 standard or a message according to the 3GPP standard may be used to transmit such timing information (T 脉冲 ) is transmitted from the transmitter 710 to the receiver 720.

[0153] In some implementations, the transmitter 710 may send timing information to the receiver 720 prior to transmitting the pulse 712, followed by a synchronization sequence (not shown for simplicity). The timing information may be used to synchronize a receiver clock of the receiver 720 with a transmit clock of the transmitter 710. For example, the timing information may indicate a timing offset or delay between one or more portions of the synchronization sequence and the start of the transmission of the pulse 712. Thus, upon detecting at least a portion of the synchronization sequence and the subsequent echo 722, the receiver 720 may determine the exact time at which the incident pulse 712(i) was transmitted by the transmitter 710. The receiver 720 may determine the timing T of the echo. 回波 The timing of the transmitted pulse T 脉冲 The distance R of the target object 701 is compared to determine the distance R of the target object 701. R (Such as described with respect to equations 1-3).

[0154] In some implementations, the transmitter 710 may also determine ranging information about the target object 701. For example, the transmitter 710 may determine its relative distance RT to the target object 701. For example, in some aspects, the receiver 720 may provide feedback to the transmitter 710 regarding the echo 722. The feedback may include the timing T of the echo. 回波 , the timing of the transmitted pulse T 脉冲 , flight time τ, arrival angle θ R , calculated distance R R or any combination thereof. Transmitter 710 may then determine the angle of departure θ of incident pulse 712 (i) based at least in part on the angle of departure θ of incident pulse 712 (i). T To calculate the distance RT of the target object 701. For example, the transmitter 710 can calculate the distance RT of the target object 701 by setting the departure angle θ T Substituting the arrival angle θ into Equation 1 R The transmitter 710 may determine the departure angle θ based on the antenna sector (corresponding to a particular beam of the phased array antenna) used by the transmitter 710 to transmit the incident pulse 712 (i). T .

[0155] One of the important measurements for RF sensing is Doppler estimation. However, current positioning procedures, such as in NR or LTE, do not support Doppler estimation. Therefore, for RF sensing in wireless networks such as system 100, support for Doppler estimation must be provided. In one specific implementation, to support RF sensing, assistance data may be provided to a sensing node, such as UE 105 or base station 110, along with information that can be used to perform Doppler estimation based on RF signals. For example, due to the large bandwidth of a positioning reference signal (PRS) used for positioning, the PRS may be suitable for use in RF sensing, such as for Figure 7Pulse 712 is shown. Current PRS used in NR or LTE do not support Doppler measurements. For example, phase coherence is not guaranteed for PRS, such as in NR or LTE. However, phase coherence is critical for Doppler estimation (e.g., discussed in Equation 4), and Doppler estimation is a key RF sensing measurement. Therefore, where PRS is used for RF sensing, information for Doppler estimation that may be provided to the sensing node in the assistance data may include an indication of the phase coherence of the PRS.

[0156] The indication of PRS phase coherence may be provided in the assistance data in various ways. For example, in one implementation, the assistance data may indicate a specific PRS (e.g., PRS resource) or PRS group (resource set) with phase coherence. The sensing node (e.g., UE 105 or base station 110) may use one or more beams (resources) from the indicated PRS group (resource set) for Doppler estimation and report the results.

[0157] In another specific implementation, the assistance data may indicate a specific TRP that supports the transmission of PRS with phase coherence. The sensing node (e.g., UE 105 or base station 110) may use the PRS received from the indicated TRP for Doppler estimation. For example, if not all resource sets associated with a TRP do not support PRS phase coherence, the assistance data may further indicate a specific group (resource set) of PRS associated with the TRP with phase coherence. This specific implementation may reduce signaling overhead because some TRPs may always support PRS phase coherence. For example, some gNB vendors may support phase coherence for some deployments. The sensing node (e.g., UE 105 or base station 110) may use PRS from the PRS group associated with the indicated TRP for Doppler estimation.

[0158] In another specific implementation, the assistance data may indicate a specific frequency layer that supports PRS with phase coherence. For example, the assistance data may indicate a frequency layer that can be used for RF sensing, and because Doppler estimation is important for most sensing use cases, the indication that the frequency layer can be used for RF sensing implicitly indicates that the PRS configured by default under the specific frequency layer supports Doppler estimation. The sensing node (e.g., UE 105 or base station 110) may use the PRS received in the frequency layer for Doppler estimation. In some specific implementations, the assistance data may indicate a PRS (e.g., one or more of a resource, a resource set, and a TRP) that does not support Doppler estimation (e.g., due to hardware limitations, phase coherence may be challenging for two PRS resources that are always far apart in the time domain). The sensing node (e.g., UE 105 or base station 110) may exclude from the Doppler estimation any PRS that is identified as not supporting Doppler estimation.

[0159] Thus, the indication of phase coherence of the PRS provided in the assistance data for RF sensing may include any combination of frequency layers, transmit reception points (TRPs), PRS resource sets, and PRS resources.

[0160] There are base station deployments, such as by some gNB vendors, that may not support phase coherence in PRS transmission. In such instances, other reference signals that may support Doppler estimation may be associated with the PRS to enable Doppler estimation. In this implementation, the information provided in the assistance data for Doppler estimation may indicate the PRS and the reference signal associated for Doppler estimation, i.e., a specific reference signal associated with the PRS that the sensing node may use for Doppler estimation. For example, the association between the PRS and the other reference signals for Doppler estimation may be a quasi-co-sited (QCL) signal, which may be implemented, for example, by a QCL-Type A configuration, a QCL-Type B configuration, or a QCL-Type C configuration. The associated reference signal may be a narrowband reference signal, but should be configured to be close to the PRS in the time domain. As an example, the reference signal that may be associated with the PRS for Doppler estimation is a tracking reference signal (TRS). In some implementations, the reference signal that may be associated with the PRS for Doppler estimation may be a non-NR signal, such as a radar waveform. For example, if the PRS and the associated radar waveform are transmitted from a co-located transmitter or even by the same transmitter, the radar waveform may be associated with the PRS for Doppler estimation. If the radar waveform is associated with the PRS for Doppler estimation, the information provided in the assistance data for Doppler estimation may also include the configuration of the radar waveform, such as the waveform type and parameters used for the radar waveform.

[0161] Based on the sensing measurements collected at the server, the server may also include in the assistance data a search window for Doppler estimation as part of the information for Doppler estimation, e.g., the information including expected Doppler and expected Doppler-Uncertainty. For example, if the RF signal used for Doppler estimation is a PRS, the server may define multiple sets of expected Doppler and expected Doppler uncertainty, e.g., with different sets for each PRS resource or PRS group (resource set). If the assistance data is sensing node specific, each set of expected Doppler and expected Doppler uncertainty may be associated with a path index. For example, the path index is a channel impulse response tap index relative to the first arrival path for the sensing node. In some implementations, the path index may be based on Cx1 / Cx2 sampling. If the sensing node is a base station such as gNB 110, the information for Doppler estimation may be provided by the server (or transmitting node) to the base station in appropriate messaging, which is referred to herein as assistance data.

[0162] Within the sensing environment, there may be multiple reference point objects (RPOs) in addition to the sensing targets. The RPOs and sensing targets will all reflect the RF signal to be received by the sensing node. However, only the reflected signal from the sensing target is desired for the sensing measurement.

[0163] As an example, Figure 8 A sensing environment 800 including a sensing receiver node 820 and a sensing transmitter node 810 configured for RF sensing of a target 852 is illustrated. The sensing receiver node 820 is illustrated as a UE (e.g., such as UE 105) and may sometimes be referred to herein as a sensing node 820 or UE 820, while the sensing transmitter node 810 is illustrated as a base station (such as gNB 110) and may sometimes be referred to herein as a transmitter node 810 or base station 810. For example, base station 810 may be an example transmitter for RF sensing, and UE 820 and / or base station 830 may be examples of a sensing entity 500 for sensing a reference signal for RF sensing. The same entity (e.g., base station 810 (or UE 820)) may be a transmitter and receiver of a reference signal for RF sensing (for monostatic RF sensing).

[0164] Base stations 810, 830 and UE 820 may send and receive radio frequency reference signals in order to perform RF sensing of a target 852, which is illustrated as a vehicle and may sometimes be referred to herein as vehicle 852. For example, base station 810 transmits signals 881, 882, 883 that are reflected from vehicle 852, tree 840, and building 861, respectively, and received by UE 820. The received reflected signals may be measured to obtain one or more reference signal measurements, and these measurements may be used to determine one or more parameters based on the reference signal measurements (e.g., based on the timing, magnitude, and direction of the received signals). For example, the one or more parameters may include the presence of objects (such as tree 840, vehicle 852, and building 861), the range to one or more of the objects relative to one or more reference points (e.g., base stations 810, 830, and / or UE 820), the direction of motion of one or more of the objects (relative to a reference such as a global direction reference), the speed of one or more of the objects, etc. For example, velocity 871 of vehicle 852 may be determined relative to a global directional reference (eg, north / east).

[0165] Immobile persistent objects such as buildings 861, 862 and tree 840 may be considered RPOs. Reference signals are received by UE 820 from reflections of RPOs such as buildings 861 and tree 840 together with reflections for target 852, but only the reflected signal from target 852 may be desired for sensing measurements. Therefore, it may be desirable to determine and ignore reflections from RPOs.

[0166] Therefore, in one specific implementation, sensing assistance data may be provided from a network node (e.g., a server or a sensing transmitter node) to a sensing node, the sensing assistance data including an association of a PRS resource and an RPO. Sensing of the target may then be performed based on the received PRS resource and the association of the PRS resource and the RPO. For example, a PRS resource associated with an RPO may be excluded from the PRS resources used to perform sensing of the target.

[0167] The association of one or more PRS resources with one or more RPOs may be based on a three-dimensional (3D) map of the environment generated in a network node (e.g., a server or a sensing transmitter node). For example, the network node may fuse the 3D map and sensing measurement reports from one or more sensing nodes to extract the RPOs. For example, assuming that the sensing node is substantially stationary (i.e., moves little or not between sensing measurement reports), the RPO reflects the RF signal at a higher power than the mobile sensing target and at zero Doppler. The identified RPO corresponds to a clutter source in a reflected reference signal that may be received by the sensing node. Therefore, the sensing node may remove the reference signal associated with the RPO from the received reference signal to enhance sensing performance.

[0168] As an example, the PRS resources associated with the RPO provided to the sensing node in the assistance data may be based on the location of the sensing node. The location of the sensing node may be obtained by the network node, for example, from the sensing node. For example, the sensing node may obtain the location of the sensing node from, for example, Figure 1 The SPS 185 shown may obtain its position from other positioning methods and may report its position to the network node. In another specific implementation, the network node may obtain the position of the sensing node from, for example, a database where the sensing node is stationary and known, such as a base station or a roadside unit (RSU). The network node may determine assistance data for the sensing node, including a PRS associated with the RPO regarding the position of the sensing node, and provide the assistance data to the sensing node.

[0169] The auxiliary data may include an association of a PRS to an RPO, which may be a one-to-many association or a many-to-one association. As an example, the auxiliary data may include an identifier (ID) and a position of each RPO associated with the PRS. For example, each PRS may be associated with a list of RPOs, each RPO in the list being associated with an RPO-ID and an RPO position. Table 1 illustrates an example of an association of a PRS to an RPS in a specific implementation.

[0170]

[0171] Table 1

[0172] The assistance data may also indicate high-level characteristics of the RPOs. For example, each RPO may be associated with at least one of a category (e.g., building, human, tree, etc.), radar cross section (RCS), material, size, shape, or any combination thereof. Due to beam-based operation, one PRS may be associated with a different RPO than another PRS. If the sensing node is a base station such as gNB 110, the association of PRS resources and RPOs may be provided by a network node (e.g., a server or a transmitter node) to the base station in appropriate messaging, which is referred to herein as assistance data.

[0173] In another specific implementation, the beam pattern information of the PRS used for positioning can be reused to support beam coordination for RF sensing. For example, auxiliary data can be transmitted from a network node (e.g., a server or a sensing transmission node) to a sensing node, and the auxiliary data includes beam pattern information of PRS resources used for beam coordination for RF sensing. The sensing node can perform sensing based on the received PRS resources and beam pattern information.

[0174] As an example, Fig. 9A sensing environment 900 including a sensing transmitter node 910 configured for RF sensing of targets 952 and 954 and a plurality of sensing receiver nodes 920, 930, and 940 is illustrated. The sensing receiver node 920 is illustrated as a UE (e.g., such as UE 105) and may sometimes be referred to herein as a sensing node 920 or UE 920, while the sensing receiver nodes 930 and 940 are illustrated as base stations (e.g., such as gNB 110) and may sometimes be referred to herein as sensing nodes 930, 940 or base stations 930, 940. The sensing transmitter node 910 is illustrated as a base station (such as gNB 110) and may sometimes be referred to herein as a transmitter node 910 or base station 910. For example, the base station 810 may be an example transmitter for RF sensing, and the UE 920 and / or the base stations 930, 940 may be examples of a sensing entity 500 for sensing a reference signal for RF sensing. The same entity (eg, base station 910) may be a transmitter and receiver of reference signals for RF sensing (for mono-static RF sensing).

[0175] Base station 910 is illustrated as transmitting PRS in different beam patterns 912 and 914. Beam pattern information for beam patterns 912 and 914 may be provided to UE 920 and base stations 930, 940, which may be used to support beam coordination for RF sensing of targets 952 and 954. For example, using the beam pattern information, UE 920 and base station 930 may use beam coordination for RF sensing of target 952 using PRS resources in beam pattern 912, whereas UE 920 and base station 940 may use beam coordination for RF sensing of target 954 using PRS resources in beam pattern 914. As an example, the beam pattern information may provide an indication of a beam direction, which may be used by UE 920 and base stations 930 and 940 to determine reception of PRS resources reflected from a target, e.g., based on a known orientation of the sensing node relative to the transmitting node and / or the target. For example, the sensing node may identify any line-of-sight (LOS) PRS resources that are not reflected from the target based on the AoD and the known orientation of the sensing node relative to the transmitting node. The sensing node may further identify which non-line-of-sight (NLOS) PRS resources are reflected from the target based on the AoD and the known orientation of the sensing node relative to the transmitting node and the target node.

[0176] Currently, PRS beam pattern information is only configured for UE-based AoD-based positioning. To support RF sensing, a more general signaling framework for PRS beam pattern signaling may be used. For example, in one implementation, a network node (e.g., a server or a transmitting node) may indicate a specific PRS frequency layer that may support RF sensing, and the PRS beam pattern information may be included in the assistance data for the PRS at that frequency layer even if a UE-based AoD-based positioning session is not configured.

[0177] In another specific implementation, a network node (e.g., a server or a transmitting node) may indicate PRS beam pattern information for some PRS resources. For example, if PRS supports AoD-based positioning, the assistance data for AoD may be reused for RF sensing. If PRS does not support AoD-based positioning, the assistance data for sensing may be configured to include an expected beam direction and an expected beam direction uncertainty.

[0178] If the sensing node is a base station such as gNB 110, beam pattern information of PRS resources for beam coordination for RF sensing may be provided by a network node (e.g., a server or a transmitter node) to the base station in appropriate messaging, which is referred to herein as assistance data.

[0179] Fig.10 An example is shown that can be used in an RF sensing session such as Figure 1 1000 is a signaling and process flow of various messages transmitted between components of a wireless communication system 100 depicted in the wireless communication system 100, the RF sensing session including assistance data to support RF sensing as discussed herein. Flow 1000 is an example and other flows are possible, for example, omitting one or more stages shown, adding one or more stages, and / or modifying one or more stages shown. The sensing entity 500 in flow 1000 may be a UE or a base station, and the network entity 600 may be a sensing server, for example Figure 1 The server 150 is shown, which may be located in or outside the 5GC 140. The sending entity 1004 may be a base station or, in some implementations, a UE. The sending entity 1004 is illustrated as being separate from the network entity 600, but may be the network entity 600 in some implementations. The signaling and process flow 1000 may be similar to the signaling and process flow for location services supported by NG-RAN.

[0180] As illustrated, the request capabilities message 1010 may be sent by the network entity 600 (eg, by the sensing procedures unit 650 via Figure 6 The transceiver 620 shown in FIG. 6A) is transmitted to the sensing entity 500 (eg, transmitted to the sensing entity 500 via the transceiver 520). Figure 5The sensing protocol unit 550 shown, for example, to request sensing capabilities from the sensing entity 500.

[0181] The provide capabilities message 1012 to the network entity 600 may be returned by the sensing entity 500 (e.g., by the sensing procedures unit 550 via the transceiver 520) to the network entity 600 (e.g., returned to the sensing procedures unit 650 via the transceiver 620) to provide the capabilities of the sensing entity 500. For example, the sensing entity 500 may indicate its ability to perform RF sensing measurements. In some implementations, the provide capabilities message 1012 may include information that may be used to generate sensing assistance data specifically for the sensing entity 500, such as the current location of the sensing entity 500.

[0182] At stage 1014, the network entity 600 (e.g., the sensing assistance data unit 660) may generate sensing assistance data. The sensing assistance data may be general assistance data, which may be broadcast or multicast to a plurality of sensing entities (not shown), or may be generated specifically for the network entity 600, e.g., the sensing assistance data may be generated based at least in part on the capabilities of the sensing entity 500. The sensing assistance data may include information for sensing unit-based RF sensing, e.g., information that will enable the sensing entity 500 to generate a desired estimate. For example, the sensing assistance data may include the location of one or more transmitters, with which the sensing entity 500 may determine the location of a target via multilateration.

[0183] As discussed above, the network entity 600 may generate sensing assistance data that includes information for supporting Doppler estimation, such as an indication of the phase coherence of a PRS that may be based on any combination of frequency layers, TRPs, PRS resource sets, and PRS resources. The sensing assistance data may include an indication of a PRS in a frequency layer that does not support Doppler estimation. The information for supporting Doppler estimation may additionally or alternatively include an indication of reference signals associated with the PRS, which may be, for example, QCL signals, and may be TRS or non-NR signals such as radar waveforms. The reference signal may be close to the PRS in the time domain. For example, the sensing assistance data may include waveform time and parameters for a radar waveform. The expected Doppler and the expected Doppler uncertainty may be generated by the network entity 600 to reduce the search window for Doppler estimation. For example, the expected Doppler and the expected Doppler uncertainty may be defined in multiple sets for each PRS resource or each PRS resource set. For example, a path index may be generated that may include a channel impulse response tap index relative to a first arrival path or based on Cx1 / Cx2 sampling for Doppler estimation.

[0184] As mentioned above Figure 8As discussed, the network entity 600 (e.g., the sensing assistance data unit 660) may additionally or alternatively generate sensing assistance data that associates one or more reference signal resources (e.g., such as PRS resources) with one or more RPOs. For example, each PRS resource may be associated with multiple RPOs, and each RPO may be associated with multiple PRS resources. For example, the network entity 600 may fuse the sensing measurement report and the 3D map to extract the RPO associated with the PRS resource. The RPO associated with the PRS resource may be based on the location of the sensing entity 500, which may be obtained by the network entity 600 from the sensing node (e.g., in a previous positioning session or in a message such as the provide capability message 1012 from the sensing entity 500), or may be obtained from a database in the case where the sensing entity 500 is a stationary node (such as a base station or RSU). The RPO associated with the PRS resource may include an ID and a location. For example, each PRS resource may be associated with an RPO list, which includes an identifier and a location for each RPO in the list. The RPO associated with a PRS resource may be associated with characteristics such as category, RCS, material, size, shape, or any combination thereof.

[0185] As mentioned above Fig. 9 As discussed, the network entity 600 (e.g., the sensing assistance data unit 660) may additionally or alternatively generate sensing assistance data including beam pattern information of a PRS that may be used for beam coordination for RF sensing. For example, even if a UE-based AoD-based positioning session is not configured, the network entity 600 may indicate a PRS frequency layer that supports RF sensing and may specify that PRS beam pattern information may be included under the frequency layer. If the PRS supports AoD-based positioning, the network entity 600 may reuse the assistance data for AoD, or if the AoD does not support AoD-based positioning, the network entity 600 may identify an expected beam direction and an expected beam direction uncertainty for the PRS beam pattern information.

[0186] A provide assistance data message 1016 is transmitted by the network entity (e.g., by the sensing procedures unit 650 via the transceiver 620) to the sensing entity 500 (e.g., transmitted to the sensing procedures unit 550 via the transceiver 520) to provide the sensing assistance data generated in stage 1014. The sensing assistance data is received by the sensing entity 500 and may be processed by the sensing entity 500 (e.g., the sensing assistance data unit 560) to assist in acquiring and measuring reference signals for RF sensing.

[0187] The request sensing information message 1018 is transmitted by the network entity (e.g., by the sensing process unit 650 via the transceiver 620) to the sensing entity 500 (e.g., transmitted to the sensing process unit 550 via the transceiver 520) to request measurement of reference signals for RF sensing. The network entity 600 may also indicate whether sensing node-based RF sensing is requested, whereby the sensing entity 500 determines the sensing measurements, or sensing node-assisted RF sensing is requested, whereby the sensing entity 500 measures reference signals and transmits the measurements to the network entity 600 to determine the sensing measurements.

[0188] Reference signal 1020 is sent by transmitting entity 1004 (eg, via Figure 3 340 shown). The reference signal may be reflected by the target (and may be reflected by one or more RPOs). The reference signal is received by the sensing entity 500 (e.g., received to the sensing measurement unit 570 via the transceiver 520). For example, the reference signal may be a PRS. In some implementations, other reference signals may be used in addition or alternatively. The reference signal (e.g., a PRS resource, a PRS resource set, a TRP, and / or a frequency layer) may have phase coherence for Doppler estimation. The reflected reference signal received by the sensing entity 500 may also be reflected by one or more RPOs. In addition, the reference signal may be sent in a beam pattern as provided in the assistance data.

[0189] At stage 1022, the sensing entity 500 (e.g., the sensing measurement unit 570) may process and measure the received reference signal for RF sensing. The sensing measurement may be performed using the received reference signal reflected from the target based on the sensing assistance data received from the network entity 600 in the message 1016. For example, as discussed above, the sensing entity 500 may perform Doppler estimation using phase-coherent PRS resources, resource sets, TRPs, or frequency layers and / or associated reference signals identified in the sensing assistance data. The Doppler estimation may be based on the exclusion of PRSs that do not support Doppler estimation, as indicated in the sensing assistance data. The expected Doppler and expected Doppler uncertainty provided in the sensing assistance data may be used by the sensing entity 500 to reduce the search window for Doppler estimation. For example, a channel impulse response tap index relative to the first arrival path or a path index based on Cx1 / Cx2 sampling may be included for Doppler estimation by the sensing entity 500.

[0190] As mentioned above Figure 8As discussed, in the presence of RPO, the sensing measurements performed by the sensing entity 500 may be based on the received reference signals and the association of these reference signals with the RPO received in the sensing assistance data in the message 10 16. For example, the sensing entity 500 (e.g., the sensing measurement unit 570) may exclude reference signals, such as PRS resources associated with the RPO, from the reference signals used for the sensing measurements.

[0191] As mentioned above Fig. 9 As discussed, in the case where the beam pattern information is provided in the sensing assistance data message 10 16, the sensing entity 500 (e.g., the sensing measurement unit 570) may perform sensing measurements based on the received reference signal and the beam pattern information for beam coordination received in the assistance data. For example, the sensing entity 500 may identify beams that are not reflected from the target based on the beam pattern information, or identify beams that are likely to be reflected from the target, and may perform sensing measurements based on these beams accordingly.

[0192] At stage 1024, the sensing entity 500 (e.g., the sensing estimation unit 580) may optionally determine a sensing estimate based on the sensing measurements performed in stage 1022. For example, the sensing entity 500 may determine the distance or location of the target relative to the sensing entity 500, the speed and / or direction of travel of the target based on the reference signal measurements. For example, the sensing entity 500 may use multilateration to determine the location of the target based on the distances to multiple (e.g., three or more) transmitters and the positioning information of these transmitters.

[0193] A provide sensing information message 1026 is transmitted by the sensing entity 500 (e.g., by the sensing procedure unit 550 via the transceiver 520) to the network entity 600 (e.g., transmitted to the sensing procedure unit 650 via the transceiver 620) to provide sensing information, such as reference signal measurements obtained in stage 1022 and / or sensing estimates obtained in stage 1024.

[0194] At stage 1028 , the network entity 600 (eg, the sensing measurement unit 670 and the sensing estimation unit 680 ) may determine sensing information, such as a sensing estimate for a target, based on the sensing measurement or estimation information provided by the sensing entity 500 in the provide sensing information message 1026 .

[0195] Fig.11 A flow chart of an exemplary process 1100 for supporting radio frequency (RF) sensing in a wireless network is shown, which may be performed by a sensing node such as a Figure 5 and Fig.10 The sensing node 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0196] At block 1110, a sensing node receives a signal from a network node such as Figure 6 and Fig.10 The network entity 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1 The base station 110 shown in FIG. 1 receives sensing assistance data including information for performing Doppler estimation based on the RF signal, for example, as shown in FIG. Fig.10 is configured to communicate with the transceiver 520 (e.g., Figure 2 The wireless receiver 244 and antenna 246 or the receiver 254 or the antenna 246 of the UE 200 in Figure 3 The processor 510 that performs the functions of the sensing assistance data unit 560 by dedicated hardware or implementing executable code or software instructions in the memory 530 (in combination with the wireless receiver 344 and antenna 346 or receiver 354 of the TRP 300) may include a component for receiving sensing assistance data including information for performing Doppler estimation based on RF signals from a network node.

[0197] At block 1120, the sensing node receives an RF signal, e.g., as provided by Fig.10 The reference signal 1020 is illustrated as an example. It is configured to communicate with the transceiver 520 (eg, Figure 2 The wireless receiver 244 and antenna 246 of the UE 200 or Figure 3 The processor 510 that performs the functions of the sensing measurement unit 570 through dedicated hardware or implementing executable code or software instructions in the memory 530 may include components for receiving RF signals.

[0198] At block 1130, the sensing node performs Doppler estimation using the RF signal and the sensing assistance data, e.g., as in Fig.10 The processor 510 configured to perform the functions of the sensing measurement unit 570 by dedicated hardware or implementing executable code or software instructions in the memory 530 may include means for performing Doppler estimation using the RF signal and the sensing assistance data.

[0199] In one implementation, the RF signal may be a positioning reference signal (PRS), and wherein the information used for Doppler estimation may include an indication of the phase coherence of the PRS, e.g., as referenced Fig.10For example, the indication of the phase coherence of the PRS may be an indication of at least one PRS group having phase coherence, and performing Doppler estimation may be based on at least one PRS group having phase coherence, for example, as described in reference to Fig.10 The indication of the phase coherence of the PRS may include an indication of at least one transmit receive point (TRP) that supports the transmission of the PRS with phase coherence, and performing the Doppler estimation may be based on the PRS received from at least one TRP that supports the transmission of the PRS with phase coherence, for example, as described in reference Fig.10 The indication of the phase coherence of the PRS may further include an indication of at least one PRS group with phase coherence from at least one TRP supporting the transmission of the PRS with phase coherence, and performing the Doppler estimation may be further based on the at least one PRS group with phase coherence, for example, as described in reference Fig.10 The indication of the phase coherence of the PRS may include an indication of a frequency layer supporting the transmission of the PRS with phase coherence, and performing Doppler estimation may be based on the PRS received from the frequency layer supporting the transmission of the PRS with phase coherence, for example, as described in reference Fig.10 The indication of the phase coherence of the PRS may further include an indication of the PRS in the frequency layer that does not support Doppler estimation, and performing Doppler estimation may be based on excluding the PRS that does not support Doppler estimation, for example, as described in reference Fig.10 In one implementation, the indication of the phase coherence of the PRS may include an indication of a frequency layer, a transmit receive point (TRP), a PRS resource set, and any combination of PRS resources that support phase coherence, for example, as described in reference to Fig.10 as discussed in stages 1014 and 1022.

[0200] In one implementation, the information used for Doppler estimation may include a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation, such as a reference signal. Fig.10 For example, the PRS and the reference signal associated for Doppler estimation may be quasi-co-sited (QCL) signals, such as reference Fig.10 The reference signal may be configured to be close to the PRS in the time domain, for example, as described in stages 1014 and 1022 of the present invention. Fig.10 For example, the reference signal may include at least one of a tracking reference signal (TRS) or a radar waveform, such as a reference signal. Fig.10The sensing assistance data may also include waveform type and parameters for the radar waveform, for example, as discussed in reference to stages 1014 and 1022. Fig.10 as discussed in stages 1014 and 1022.

[0201] In one specific implementation, the information for Doppler estimation may include information of a search window for Doppler estimation, and the information of the search window for Doppler estimation includes an expected Doppler and an expected Doppler uncertainty, for example, as shown in FIG. Fig.10 For example, the RF signal may include a positioning reference signal (PRS), and the expected Doppler and expected Doppler uncertainty may be defined in multiple sets for each PRS resource or each PRS resource set, for example, as described in reference Fig.10 The sensing assistance data may be specific to the sensing node, and each set of expected Doppler and expected Doppler uncertainty may be associated with a path index, where the path index is a channel impulse response tap index relative to the first arrival path or based on Cx1 / Cx2 sampling, for example, as described in reference Fig.10 as discussed in stages 1014 and 1022.

[0202] Fig.12 A flow chart of an exemplary process 1200 for supporting radio frequency (RF) sensing in a wireless network is shown, which may be performed by a network node such as a Figure 6 and Fig.10 The network node 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1 The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0203] At block 1210, a network node obtains sensing assistance data for a sensing node in a wireless network, the sensing assistance data including information for performing Doppler estimation based on an RF signal, such as in Fig.10 The processor 610 configured to perform the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 may include means for obtaining sensing assistance data for a sensing node in a wireless network, the sensing assistance data including information for performing Doppler estimation based on the RF signal.

[0204] At block 1220, the network node sends a signal to a sensor node such as Figure 5 and Fig.10 The sensing entity 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1The base station 110 shown in FIG. 1 transmits sensing assistance data including information for performing Doppler estimation based on the RF signal, for example, as shown in FIG. Fig.10 is configured to communicate with transceiver 620 (e.g., Figure 4 The transmitter 442 and antenna 446 of the server 400 or the transmitter 452 or Figure 3 The processor 610 that performs the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 (the transmitter 342 and antenna 346 or the transmitter 352 of the TRP 300) may include a component for transmitting sensing assistance data including information for performing Doppler estimation based on RF signals to a sensing node.

[0205] In one specific implementation, the network node may receive a sensing report from a sensing node, for example, Fig.10 is configured to communicate with transceiver 620 (e.g., Figure 4 The receiver 444 and antenna 446 of the server 400 or the receiver 454 or Figure 3 The processor 610 that performs the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 (the transmitter 344 and antenna 346 or the transmitter 354 of the TRP 300) may include a component for receiving a sensing report from a sensing node.

[0206] In one implementation, the RF signal may be a positioning reference signal (PRS), and wherein the information used for Doppler estimation may include an indication of the phase coherence of the PRS, e.g., as referenced Fig.10 For example, the indication of the phase coherence of the PRS may be an indication of at least one PRS group having phase coherence, and performing Doppler estimation may be based on at least one PRS group having phase coherence, for example, as described in reference to Fig.10 The indication of the phase coherence of the PRS may include an indication of at least one transmit receive point (TRP) that supports the transmission of the PRS with phase coherence, and performing the Doppler estimation may be based on the PRS received from at least one TRP that supports the transmission of the PRS with phase coherence, for example, as described in reference Fig.10 The indication of the phase coherence of the PRS may further include an indication of at least one PRS group with phase coherence from at least one TRP supporting the transmission of the PRS with phase coherence, and performing the Doppler estimation may be further based on the at least one PRS group with phase coherence, for example, as described in reference Fig.10The indication of the phase coherence of the PRS may include an indication of a frequency layer supporting the transmission of the PRS with phase coherence, and performing Doppler estimation may be based on the PRS received from the frequency layer supporting the transmission of the PRS with phase coherence, for example, as described in reference Fig.10 The indication of the phase coherence of the PRS may further include an indication of the PRS in the frequency layer that does not support Doppler estimation, and performing Doppler estimation may be based on excluding the PRS that does not support Doppler estimation, for example, as described in reference Fig.10 In one implementation, the indication of the phase coherence of the PRS may include an indication of a frequency layer, a transmit receive point (TRP), a PRS resource set, and any combination of PRS resources that support phase coherence, for example, as described in reference to Fig.10 as discussed in stages 1014 and 1022.

[0207] In one implementation, the information used for Doppler estimation may include a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation, such as a reference signal. Fig.10 For example, the PRS and the reference signal associated for Doppler estimation may be quasi-co-sited (QCL) signals, such as reference Fig.10 The reference signal may be configured to be close to the PRS in the time domain, for example, as described in stages 1014 and 1022 of the present invention. Fig.10 For example, the reference signal may include at least one of a tracking reference signal (TRS) or a radar waveform, such as a reference signal. Fig.10 The sensing assistance data may also include waveform type and parameters for the radar waveform, for example, as discussed in reference to stages 1014 and 1022. Fig.10 as discussed in stages 1014 and 1022.

[0208] In one specific implementation, the information for Doppler estimation may include information of a search window for Doppler estimation, and the information of the search window for Doppler estimation includes an expected Doppler and an expected Doppler uncertainty, for example, as shown in FIG. Fig.10 For example, the RF signal may include a positioning reference signal (PRS), and the expected Doppler and expected Doppler uncertainty may be defined in multiple sets for each PRS resource or each PRS resource set, for example, as described in reference Fig.10The sensing assistance data may be specific to the sensing node, and each set of expected Doppler and expected Doppler uncertainty may be associated with a path index, where the path index is a channel impulse response tap index relative to the first arrival path or based on Cx1 / Cx2 sampling, for example, as described in reference Fig.10 as discussed in stages 1014 and 1022.

[0209] Fig.13 A flow chart of an exemplary process 1300 for supporting radio frequency (RF) sensing in a wireless network is shown, which may be performed by a sensing node such as a Figure 5 and Fig.10 The sensing node 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1 The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0210] At block 1310, a sensing node receives a signal from a network node such as Figure 6 and Fig.10 The network entity 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1 The base station 110 shown in FIG. 1 receives sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO), such as, for example, Fig.10 and reference to stage 1014 and message 1016 Figure 8 is configured to communicate with a transceiver 520 (eg, Figure 2 The wireless receiver 244 and antenna 246 or the receiver 254 or the antenna 246 of the UE 200 in Figure 3 The processor 510 that performs the functions of the sensing assistance data unit 560 by dedicated hardware or implementing executable code or software instructions in the memory 530 in combination with the wireless receiver 344 and antenna 346 or receiver 354 of the TRP 300 may include a component for receiving associated sensing assistance data including at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node.

[0211] At block 1320, the sensing node receives a PRS resource, for example, as provided by Fig.10 The reference signal 1020 is illustrated as an example. It is configured to communicate with the transceiver 520 (eg, Figure 2 The wireless receiver 244 and antenna 246 of the UE 200 or Figure 3The processor 510 that performs the functions of the sensing measurement unit 570 in combination with the wireless receiver 344 and antenna 346 of the TRP 300 in the memory 530 through dedicated hardware or implementing executable code or software instructions in the memory 530 may include components for receiving PRS resources.

[0212] At block 1330, the sensing node performs sensing based on the PRS resources and the association of at least one PRS resource with at least one RPO, e.g., as in Fig.10 of stage 1022 and refer to Figure 8 The processor 510 configured to perform the functions of the sensing measurement unit 570 by dedicated hardware or implementing executable code or software instructions in the memory 530 may include means for performing sensing based on PRS resources and an association of at least one PRS resource and at least one RPO.

[0213] In one specific implementation, the sensing node performs sensing based on the PRS resources and the association of the at least one PRS resource with the at least one RPO by excluding at least one PRS resource associated with the at least one RPO from the PRS resources used to perform sensing, for example, as in Fig.10 of stage 1022 and refer to Figure 8 The processor 510 configured to perform the functions of the sensing measurement unit 570 by dedicated hardware or implementing executable code or software instructions in the memory 530 may include means for excluding at least one PRS resource associated with at least one RPO from the PRS resources used to perform sensing.

[0214] In one specific implementation, the sensing assistance data may include an identifier and a location of each of the at least one RPO, for example, as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0215] In one specific implementation, the sensing assistance data may include, for each of the at least one PRS resource, an RPO list including an identifier and a position for each RPO in the RPO list, for example, as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0216] In one specific implementation, for each of the at least one RPO, the sensing assistance data includes at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof, such as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0217] In one specific implementation, at least one PRS resource may be associated with multiple RPOs, and at least one RPO may be associated with multiple PRS resources, e.g., Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0218] Fig.14 A flow chart showing an exemplary process 1400 for supporting radio frequency (RF) sensing in a wireless network, which may be performed by a network node such as a Figure 6 and Fig.10 The network node 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1 The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0219] At block 1410, a network node obtains sensing assistance data for a sensor node in a wireless network, the sensing assistance data comprising an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO), e.g., as in Fig.10 In stage 1014 and with reference to Figure 8 The processor 610 configured to perform the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 may include means for obtaining sensing assistance data for a sensing node in a wireless network, the sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO).

[0220] At block 1420, the network node sends a signal to a sensor node such as Figure 5 and Fig.10 The sensing entity 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1 The base station 110 shown in FIG. 1 transmits associated sensing assistance data including at least one PRS resource and at least one RPO, for example, as in Fig.10 Message 1016 and reference Figure 8 is configured to communicate with the transceiver 620 (eg, Figure 4 The transmitter 442 and antenna 446 of the server 400 or the transmitter 452 or Figure 3 The processor 610 that performs the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 (the transmitter 342 and antenna 346 or the transmitter 352 of the TRP 300) may include a component for transmitting associated sensing assistance data including at least one PRS resource and at least one RPO to a sensing node.

[0221] In one specific implementation, at least one RPO is determined based on the three-dimensional map and one or more sensing measurement reports received from one or more sensing nodes, for example, as in Fig.10 In stage 1014 and with reference to Figure 8 discussed.

[0222] In one specific implementation, the sensing assistance data may include an identifier and a location of each of the at least one RPO, for example, as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0223] In one specific implementation, the sensing assistance data may include, for each of the at least one PRS resource, an RPO list including an identifier and a position for each RPO in the RPO list, for example, as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0224] In one specific implementation, for each of the at least one RPO, the sensing assistance data includes at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof, such as in Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0225] In one specific implementation, at least one PRS resource may be associated with multiple RPOs, and at least one RPO may be associated with multiple PRS resources, e.g., Fig.10 of stage 1014 and refer to Figure 8 discussed.

[0226] Fig.15 A flow chart of an exemplary process 1500 for supporting radio frequency (RF) sensing in a wireless network is shown, which may be performed by a sensing node such as a Figure 5 and Fig.10 The sensing node 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1 The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0227] At block 1510, a sensing node receives a signal from a network node such as Figure 6 and Fig.10 The network entity 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1The base station 110 shown receives sensing assistance data including beam pattern information of positioning reference signal (PRS) resources for beam coordination for RF sensing, for example, as shown in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 is configured to communicate with a transceiver 520 (eg, Figure 2 The wireless receiver 244 and antenna 246 or the receiver 254 or the antenna 246 of the UE 200 in Figure 3 The processor 510 that performs the functions of the sensing assistance data unit 560 by dedicated hardware or implementing executable code or software instructions in the memory 530 in combination with the wireless receiver 344 and antenna 346 or receiver 354 of the TRP 300 may include components for sensing assistance data of beam pattern information of positioning reference signal (PRS) resources for beam coordination for RF sensing.

[0228] At block 1520, the sensing node receives a PRS resource, e.g., as provided by Fig.10 The reference signal 1020 is illustrated as an example. It is configured to communicate with the transceiver 520 (eg, Figure 2 The wireless receiver 244 and antenna 246 of the UE 200 or Figure 3 The processor 510 that performs the functions of the sensing measurement unit 570 in combination with the wireless receiver 344 and antenna 346 of the TRP 300 in the memory 530 through dedicated hardware or implementing executable code or software instructions in the memory 530 may include components for receiving PRS resources.

[0229] At block 1530, the sensing node performs sensing based on the PRS resources and beam pattern information, e.g., as in Fig.10 of stage 1022 and refer to Fig. 9 The processor 510 configured to perform the functions of the sensing measurement unit 570 by dedicated hardware or implementing executable code or software instructions in the memory 530 may include means for performing sensing based on the PRS resources and beam pattern information.

[0230] In one specific implementation, the sensing assistance data may also include an indication of a frequency layer that supports RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for the PRS resources in the frequency layer, for example, as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 For example, a positioning session based on an angle of departure (AoD) may not be configured for a sensing node, e.g., as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0231] In one specific implementation, the PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing may include assistance data for AoD based positioning, for example, as described in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0232] In one implementation, the beam pattern information of the PRS resources for beam coordination for RF sensing may include an expected beam direction and an expected beam direction uncertainty, for example, as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0233] Fig.16 A flow chart of an exemplary process 1600 for supporting radio frequency (RF) sensing in a wireless network is shown, which may be performed by a network node such as a Figure 6 and Fig.10 The network node 600 illustrated in FIG. 1 may be, for example, Figure 1 The sensor server 150 or Figure 1 The base station 110 shown in FIG. 1 is implemented in a manner consistent with the disclosed embodiments.

[0234] At block 1610, a network node obtains sensing assistance data for a sensing node in a wireless network, the sensing assistance data including beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing, e.g., as described in Fig.10 In stage 1014 and with reference to Figure 8 The processor 610 configured to perform the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 may include means for obtaining sensing assistance data for a sensing node in a wireless network, the sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO).

[0235] At block 1620, the network node sends a signal to a sensor node such as Figure 5 and Fig.10 The sensing entity 500 illustrated in FIG. 1 may be, for example, Figure 1 The UE 105 shown or Figure 1 The base station 110 shown in FIG. 1 transmits sensing assistance data including beam pattern information of PRS resources for beam coordination for RF sensing, for example, as shown in FIG. Fig.10 Message 1016 and reference Figure 8 is configured to communicate with the transceiver 620 (eg, Figure 4 The transmitter 442 and antenna 446 of the server 400 or the transmitter 452 or Figure 3 The processor 610 that performs the functions of the sensing assistance data unit 660 by dedicated hardware or implementing executable code or software instructions in the memory 630 (the transmitter 342 and antenna 346 or the transmitter 352 of the TRP 300) may include a component for transmitting associated sensing assistance data including at least one PRS resource and at least one RPO to a sensing node.

[0236] In one specific implementation, the sensing assistance data may also include an indication of a frequency layer that supports RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for the PRS resources in the frequency layer, for example, as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 For example, a positioning session based on an angle of departure (AoD) may not be configured for a sensing node, e.g., as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0237] In one specific implementation, the PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing may include assistance data for AoD based positioning, for example, as described in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0238] In one implementation, the beam pattern information of the PRS resources for beam coordination for RF sensing may include an expected beam direction and an expected beam direction uncertainty, for example, as in Fig.10 and reference to stage 1014 and message 1016 Fig. 9 discussed.

[0239] Reference throughout this specification to "one example," "an example," "some examples," or "exemplary implementations" means that the particular features, structures, or characteristics described in conjunction with the features and / or examples may be included in at least one feature and / or example of the claimed subject matter. Thus, the phrases "in one example," "an example," "some examples," or "in some implementations," or other similar phrases, appearing throughout the specification do not necessarily all refer to the same features, examples, and / or limitations. Furthermore, these particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0240] Some parts of the specific embodiments included herein are presented in the form of algorithms or symbolic representations of operations on binary digital signals stored in the memory of a specific device or a special computing device or platform. In the context of this specific specification, the term specific device, etc. includes a general-purpose computer that performs specific operations according to instructions from program software once programmed. Algorithmic descriptions or symbolic representations are examples of techniques used by ordinary technicians in signal processing or related fields to convey the essence of their work to other technicians in the field. The algorithm here is generally considered to be a self-consistent sequence of operations or similar signal processing that leads to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, but not necessarily, such quantities can take the form of electrical or magnetic signals that can be stored, transferred, combined, compared or otherwise manipulated. Mainly for reasons of common use, it has been proven that it is sometimes convenient to refer to such signals as bits, data, values, elements, symbols, characters, items, numbers, numerical values, etc. However, it should be understood that all of these or similar terms should be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion herein, it should be appreciated that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," etc. refer to the actions or processes of a specific apparatus, such as a special purpose computer, a special purpose computing apparatus, or a similar special purpose electronic computing device. Thus, in the context of this specification, a special purpose computer or similar special purpose electronic computing device is capable of manipulating or transforming signals that are typically represented as physical electronic or magnetic quantities within a memory, register, or other information storage device, transmission device, or display device of the special purpose computer or similar special purpose electronic computing device.

[0241] In the above detailed description, numerous specific details are set forth to provide a thorough understanding of the claimed subject matter. However, those skilled in the art will appreciate that the claimed subject matter may be practiced without these specific details. In other instances, methods and devices known to those of ordinary skill in the art are not described in detail to avoid obscuring the claimed subject matter.

[0242] As used herein, the terms "and," "or," and "and / or" may include a variety of meanings that are also intended to depend at least in part on the context in which such terms are used. In general, "or," if used in connection with a list, such as A, B, or C, is intended to mean A, B, and C (used herein in an inclusive sense) as well as A, B, or C (used herein in an exclusive sense). Additionally, the term "one or more," as used herein, may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a plurality of features, structures, or characteristics, or some other combination thereof. It should be noted, however, that this is merely an illustrative example, and claimed subject matter is not limited to this example.

[0243] While what is presently considered to be example features has been illustrated and described, it will be appreciated by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the claimed subject matter. Additionally, many modifications may be made to adapt a particular scenario to the teachings of the claimed subject matter without departing from the central concepts described herein.

[0244] In view of this description, various embodiments may include different combinations of features. Specific implementation examples are described in the following numbered clauses:

[0245] Clause 1. A method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: receiving sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node; receiving the RF signal; and performing Doppler estimation using the RF signal and the sensing assistance data.

[0246] Clause 2. The method of clause 1, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information used for Doppler estimation comprises an indication of phase coherence of the PRS.

[0247] Clause 3. The method of clause 2, wherein the indication of phase coherence of the PRS comprises an indication of at least one group of PRSs having phase coherence, and wherein performing the Doppler estimation is based on the at least one group of PRSs having phase coherence.

[0248] Clause 4. A method according to any of clauses 2-3, wherein the indication of the phase coherence of the PRS includes an indication of at least one transmit receive point (TRP) that supports the transmission of the PRS with phase coherence, and wherein the Doppler estimation is performed based on the PRS received from the at least one TRP that supports the transmission of the PRS with phase coherence.

[0249] Clause 5. A method according to clause 4, wherein the indication of the phase coherence of the PRS also includes an indication of at least one PRS group with phase coherence from at least one TRP supporting the transmission of the PRS with phase coherence, and wherein performing the Doppler estimation is further based on the at least one PRS group with phase coherence.

[0250] Clause 6. A method according to any one of clauses 2-5, wherein the indication of the phase coherence of the PRS includes an indication of a frequency layer supporting the transmission of the PRS with phase coherence, and wherein the Doppler estimation is performed based on the PRS received from the frequency layer supporting the transmission of the PRS with phase coherence.

[0251] Clause 7. The method of clause 6, wherein the indication of phase coherence of the PRS further comprises an indication of the PRS in the frequency layer that does not support Doppler estimation, wherein performing the Doppler estimation is based on excluding the PRS that does not support the Doppler estimation.

[0252] Clause 8. A method according to any of clauses 2-7, wherein the indication of phase coherence of the PRS includes an indication of any combination of frequency layers, transmit reception points (TRPs), PRS resource sets, and PRS resources that support phase coherence.

[0253] Clause 9. A method according to any of clauses 1-8, wherein the information used for Doppler estimation comprises a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

[0254] Clause 10. The method of clause 9, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals.

[0255] Clause 11. The method of any of clauses 9-10, wherein the reference signal is configured to be close to the PRS in the time domain.

[0256] Clause 12. The method of any of clauses 9-11, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

[0257] Clause 13. The method of clause 12, wherein the sensing assistance data further comprises a waveform type and parameters for the radar waveform.

[0258] Clause 14. The method of any one of clauses 1-13, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

[0259] Clause 15. The method of clause 14, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

[0260] Clause 16. A method according to any one of clauses 14-15, wherein the sensing assistance data is specific to the sensing node and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cx1 / Cx2 sampling.

[0261] Clause 17. The method of any of clauses 1-16, wherein the sensing node comprises one of a user equipment or a base station.

[0262] Clause 18. A method as described in any of clauses 1-17, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0263] Clause 19. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node via the at least one transceiver; receive the RF signal via the at least one transceiver; and perform Doppler estimation using the RF signal and the sensing assistance data.

[0264] Clause 20. The sensing node of Clause 19, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information used for Doppler estimation comprises an indication of phase coherence of the PRS.

[0265] Clause 21. The sensing node of Clause 20, wherein the indication of phase coherence of the PRS comprises an indication of at least one group of PRSs having phase coherence, and wherein performing the Doppler estimation is based on the at least one group of PRSs having phase coherence.

[0266] Clause 22. A sensing node according to any of clauses 20-21, wherein the indication of the phase coherence of the PRS includes an indication of at least one transmit receive point (TRP) that supports transmission of the PRS with phase coherence, and wherein the Doppler estimation is performed based on the PRS received from the at least one TRP that supports transmission of the PRS with phase coherence.

[0267] Clause 23. A sensing node according to clause 22, wherein the indication of the phase coherence of the PRS also includes an indication of at least one PRS group with phase coherence from the at least one TRP supporting the transmission of the PRS with phase coherence, and wherein performing the Doppler estimation is further based on the at least one PRS group with phase coherence.

[0268] Clause 24. A sensing node according to any of clauses 20-23, wherein the indication of the phase coherence of the PRS comprises an indication of a frequency layer supporting transmission of the PRS with phase coherence, and wherein performing the Doppler estimation is based on PRS received from the frequency layer supporting transmission of the PRS with phase coherence.

[0269] Clause 25. The sensing node of clause 24, wherein the indication of phase coherence of the PRS further comprises an indication of the PRS in a frequency layer that does not support Doppler estimation, wherein performing the Doppler estimation is based on excluding the PRS that does not support the Doppler estimation.

[0270] Clause 26. A sensing node as set forth in any of clauses 20-25, wherein the indication of phase coherence of the PRS comprises an indication of any combination of frequency layer, transmit reception point (TRP), PRS resource set, and PRS resources supporting phase coherence.

[0271] Clause 27. A sensing node as described in any of clauses 19-26, wherein the information used for Doppler estimation comprises a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

[0272] Clause 28. The sensing node of Clause 27, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals.

[0273] Clause 29. A sensing node as recited in any of Clauses 27-28, wherein the reference signal is configured to be close to the PRS in the time domain.

[0274] Clause 30. The sensing node of any of clauses 27-29, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

[0275] Clause 31. The sensing node of clause 30, wherein sensing assistance data further comprises a waveform type and parameters for the radar waveform.

[0276] Clause 32. A sensing node as described in any of clauses 19-31, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

[0277] Clause 33. The sensing node of clause 32, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

[0278] Clause 34. A sensing node according to any of clauses 32-33, wherein the sensing assistance data is specific to the sensing node, and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cx1 / Cx2 sampling.

[0279] Clause 35. A sensing node as recited in any of clauses 19-34, wherein the sensing node comprises one of a user equipment or a base station.

[0280] Clause 36. A sensing node as described in any of clauses 19-35, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0281] Clause 37. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: a component for receiving sensing assistance data including information for performing Doppler estimation based on an RF signal from a network node; a component for receiving the RF signal; and a component for performing Doppler estimation using the RF signal and the sensing assistance data.

[0282] Clause 38. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: receiving sensing assistance data comprising information for performing Doppler estimation based on an RF signal from a network node; receiving the RF signal; and performing Doppler estimation using the RF signal and the sensing assistance data.

[0283] Clause 39. A method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising information for performing Doppler estimation based on an RF signal; and transmitting the sensing assistance data comprising the information for performing Doppler estimation based on the RF signal to the sensing node.

[0284] Clause 40. The method of clause 39, further comprising: receiving a sensing report from the sensing node.

[0285] Clause 41. The method of any of clauses 39-40, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information used for Doppler estimation comprises an indication of phase coherence of the PRS.

[0286] Clause 42. The method of clause 41, wherein the indication of phase coherence of the PRS comprises an indication of at least one group of PRSs having phase coherence.

[0287] Clause 43. A method as described in any of clauses 41-42, wherein the indication of the phase coherence of the PRS comprises an indication of at least one transmit receive point (TRP) that supports transmission of the PRS with phase coherence.

[0288] Clause 44. A method according to clause 43, wherein the indication of the phase coherence of the PRS also includes an indication of at least one PRS group with phase coherence from the at least one TRP that supports the transmission of the PRS with phase coherence.

[0289] Clause 45. The method of any of clauses 41-44, wherein the indication of phase coherence of the PRS comprises an indication of frequency layers that support transmission of the PRS with phase coherence.

[0290] Clause 46. The method of clause 45, wherein the indication of phase coherence of the PRS further comprises an indication of the PRS in the frequency layer that does not support Doppler estimation.

[0291] Clause 47. A method according to any of clauses 41-46, wherein the indication of phase coherence of the PRS comprises an indication of any combination of frequency layers, transmit reception points (TRPs), PRS resource sets, and PRS resources that support phase coherence.

[0292] Clause 48. The method of any of clauses 39-47, wherein the information used for Doppler estimation comprises a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

[0293] Clause 49. The method of Clause 48, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals.

[0294] Clause 50. The method of any of clauses 48-49, wherein the reference signal is configured to be close to the PRS in the time domain.

[0295] Clause 51. The method of any of clauses 48-50, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

[0296] Clause 52. The method of clause 51, wherein the sensing assistance data further comprises a waveform type and parameters for the radar waveform.

[0297] Clause 53. The method of any of clauses 39-52, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

[0298] Clause 54. The method of clause 53, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

[0299] Clause 55. A method according to any one of clauses 53-54, wherein the sensing assistance data is specific to the sensing node and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cxl / Cx2 sampling.

[0300] Clause 56. The method of any of clauses 39-55, wherein the sensing node comprises one of a user equipment or a base station.

[0301] Clause 57. A method as described in any of clauses 39-56, wherein the network node comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0302] Clause 58. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising information for performing Doppler estimation based on an RF signal; and transmit the sensing assistance data comprising the information for performing Doppler estimation based on the RF signal to the sensing node via the at least one transceiver.

[0303] Clause 59. The network node of clause 58, further comprising: receiving a sensing report from the sensing node.

[0304] Clause 60. A network node as set forth in any of clauses 58-59, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information for Doppler estimation comprises an indication of phase coherence of the PRS.

[0305] Clause 61. The network node of Clause 60, wherein the indication of phase coherence of the PRS comprises an indication of at least one group of PRSs having phase coherence.

[0306] Clause 62. A network node as set forth in any of clauses 60-61, wherein the indication of phase coherence of the PRS comprises an indication of at least one transmit receive point (TRP) that supports transmission of the PRS with phase coherence.

[0307] Clause 63. A network node according to clause 62, wherein the indication of phase coherence of the PRS also includes an indication of at least one PRS group with phase coherence from the at least one TRP supporting transmission of PRS with phase coherence.

[0308] Clause 64. A network node as set forth in any of clauses 60-63, wherein the indication of phase coherence of the PRS comprises an indication of a frequency layer supporting transmission of the PRS with phase coherence.

[0309] Clause 65. The network node of Clause 64, wherein the indication of phase coherence of the PRS further comprises an indication of the PRS in the frequency layer for which Doppler estimation is not supported.

[0310] Clause 66. A network node as set forth in any of clauses 60-65, wherein the indication of phase coherence of the PRS comprises an indication of any combination of a frequency layer, a transmit reception point (TRP), a PRS resource set, and a PRS resource that supports phase coherence.

[0311] Clause 67. A network node as set forth in any of clauses 58-66, wherein the information for Doppler estimation comprises a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

[0312] Clause 68. The network node of Clause 67, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals.

[0313] Clause 69. A network node as set forth in any of clauses 67-68, wherein the reference signal is configured to be close to the PRS in the time domain.

[0314] Clause 70. The network node of any of clauses 67-69, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

[0315] Clause 71. The network node of clause 70, wherein the sensing assistance data further comprises a waveform type and parameters for the radar waveform.

[0316] Clause 72. A network node as recited in any of Clauses 58-71, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

[0317] Clause 73. The network node of clause 72, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

[0318] Clause 74. A network node according to any of clauses 72-73, wherein the sensing assistance data is specific to the sensing node, and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cx1 / Cx2 sampling.

[0319] Clause 75. The network node of any of clauses 58-74, wherein the sensing node comprises one of a user equipment or a base station.

[0320] Clause 76. A network node as set forth in any of clauses 58-75, wherein the network node comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0321] Clause 77. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising information for performing Doppler estimation based on an RF signal; and a component for transmitting the sensing assistance data comprising the information for performing Doppler estimation based on the RF signal to the sensing node.

[0322] Clause 78. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising information for performing Doppler estimation based on an RF signal; and transmitting the sensing assistance data comprising the information for performing Doppler estimation based on the RF signal to the sensing node.

[0323] Clause 79. A method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: receiving sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving a PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0324] Clause 80. The method of clause 79, wherein performing sensing based on the PRS resources and the association of the at least one PRS resource and the at least one RPO comprises excluding the at least one PRS resource associated with the at least one RPO from the PRS resources used to perform sensing.

[0325] Clause 81. The method of any of clauses 79-80, wherein the sensing assistance data comprises an identifier and a location of each of the at least one RPO.

[0326] Clause 82. A method according to any of clauses 79-81, wherein the sensing assistance data comprises, for each of the at least one PRS resource, an RPO list comprising an identifier and a position for each RPO in the RPO list.

[0327] Clause 83. The method of any one of clauses 79-82, wherein for each of the at least one RPO, the sensing assistance data comprises at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof.

[0328] Clause 84. The method of any of clauses 79-83, wherein the at least one PRS resource is associated with a plurality of RPOs, and the at least one RPO is associated with a plurality of PRS resources.

[0329] Clause 85. The method of any of clauses 79-84, wherein the sensing node comprises one of a user equipment or a base station.

[0330] Clause 86. A method as described in any of clauses 79-85, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0331] Clause 87. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive sensing assistance data including at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node via the at least one transceiver; receive the PRS resource via the at least one transceiver; and perform sensing based on the PRS resource and the association between the at least one PRS resource and the at least one RPO.

[0332] Clause 88. A sensing node according to clause 87, wherein the at least one processor is configured to: perform sensing based on the PRS resources and the association between the at least one PRS resource and the at least one RPO by being configured to exclude the at least one PRS resource associated with the at least one RPO from the PRS resources used to perform sensing.

[0333] Clause 89. The sensing node of any of clauses 87-88, wherein the sensing assistance data comprises an identifier and a location of each of the at least one RPO.

[0334] Clause 90. A sensing node as described in any of clauses 87-89, wherein the sensing assistance data comprises, for each of the at least one PRS resource, an RPO list comprising an identifier and a position for each RPO in the RPO list.

[0335] Clause 91. A sensing node according to any of clauses 87-90, wherein for each of the at least one RPO, the sensing assistance data comprises at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof.

[0336] Clause 92. The sensing node of any of clauses 87-91, wherein the at least one PRS resource is associated with a plurality of RPOs, and the at least one RPO is associated with a plurality of PRS resources.

[0337] Clause 93. The sensing node of any of clauses 87-92, wherein the sensing node comprises one of a user equipment or a base station.

[0338] Clause 94. A sensing node as described in any of clauses 87-93, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0339] Clause 95. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: receiving sensing assistance data including an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving a PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0340] Clause 96. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: receiving sensing assistance data comprising an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO) from a network node; receiving a PRS resource; and performing sensing based on the PRS resource and the association of the at least one PRS resource and the at least one RPO.

[0341] Clause 97. A method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising an association between at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmitting the sensing assistance data comprising the association between the at least one PRS resource and the at least one RPO to the sensing node.

[0342] Clause 98. The method of clause 97, wherein the at least one RPO is determined based on a three-dimensional map and one or more sensing measurement reports received from one or more sensing nodes.

[0343] Clause 99. The method of any of clauses 97-98, wherein the sensing assistance data comprises an identifier and a location of each of the at least one RPO.

[0344] Clause 100. The method of any of clauses 97-99, wherein the sensing assistance data comprises, for each of the at least one PRS resource, an RPO list comprising an identifier and a position for each RPO in the RPO list.

[0345] Clause 10 1. The method of any one of clauses 97-100, wherein for each of the at least one RPO, the sensing assistance data comprises at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof.

[0346] Clause 102. The method of any of clauses 97-101, wherein the at least one PRS resource is associated with a plurality of RPOs, and the at least one RPO is associated with a plurality of PRS resources.

[0347] Clause 103. The method of any of clauses 97-102, wherein the sensing node comprises one of a user equipment or a base station.

[0348] Clause 104. The method of any of clauses 97-103, wherein the network node comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0349] Clause 105. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising an association between at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmit the sensing assistance data comprising the association between the at least one PRS resource and the at least one RPO to the sensing node via the at least one transceiver.

[0350] Clause 106. The network node of clause 105, wherein the at least one RPO is determined based on a three-dimensional map and one or more sensing measurement reports received from one or more sensing nodes.

[0351] Clause 107. The network node of any of clauses 105-106, wherein the sensing assistance data comprises an identifier and a location of each of the at least one RPO.

[0352] Clause 108. A network node as set forth in any of clauses 105-107, wherein the sensing assistance data comprises, for each of the at least one PRS resource, an RPO list comprising an identifier and a position for each RPO in the RPO list.

[0353] Clause 109. The network node of any of clauses 105-108, wherein for each of the at least one RPO, the sensing assistance data comprises at least one of a category, a radar cross section, a material, a size, a shape, or any combination thereof.

[0354] Clause 110. The network node of any of clauses 105-109, wherein the at least one PRS resource is associated with a plurality of RPOs, and the at least one RPO is associated with a plurality of PRS resources.

[0355] Clause 111. The network node of any of clauses 105-110, wherein the sensing node comprises one of a user equipment or a base station.

[0356] Clause 112. A network node as recited in any of clauses 105-111, wherein the network node comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0357] Clause 113. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and a component for transmitting the sensing assistance data comprising the association of the at least one PRS resource and the at least one RPO to the sensing node.

[0358] Clause 114. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising an association of at least one positioning reference signal (PRS) resource and at least one reference point object (RPO); and transmitting to the sensing node the sensing assistance data comprising the association of the at least one PRS resource and the at least one RPO.

[0359] Clause 115. A method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: receiving beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node; receiving PRS resources; and performing sensing based on the PRS resources and the beam pattern information.

[0360] Clause 116. The method of clause 115, wherein the sensing assistance data further includes an indication of a frequency layer that supports RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for PRS resources in the frequency layer.

[0361] Clause 117. The method of any of clauses 116-116, wherein no angle of departure (AoD) based positioning session is configured for the sensing node.

[0362] Clause 118. A method according to any of clauses 115-117, wherein PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing includes assistance data for the AoD based positioning.

[0363] Clause 119. The method of any of clauses 115-118, wherein the beam pattern information of the PRS resources used for beam coordination for RF sensing comprises an expected beam direction and an expected beam direction uncertainty.

[0364] Clause 120. The method of any of clauses 115-119, wherein the sensing node comprises one of a user equipment or a base station.

[0365] Clause 121. The method of any of clauses 115-120, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0366] Clause 122. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receive beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node via the at least one transceiver; receive PRS resources via the at least one transceiver; and perform sensing based on the PRS resources and the beam pattern information.

[0367] Clause 123. The sensing node of clause 122, wherein the sensing assistance data further comprises an indication of a frequency layer supporting RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for PRS resources in the frequency layer.

[0368] Clause 124. A sensing node as recited in any of clauses 122-123, wherein an angle of departure (AoD) based positioning session is not configured for the sensing node.

[0369] Clause 125. A sensing node according to any of clauses 122-124, wherein PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing includes assistance data for the AoD based positioning.

[0370] Clause 126. The sensing node of any of clauses 122-125, wherein the beam pattern information of the PRS resources used for beam coordination for RF sensing comprises an expected beam direction and an expected beam direction uncertainty.

[0371] Clause 127. The sensing node of any of clauses 122-126, wherein the sensing node comprises one of a user equipment or a base station.

[0372] Clause 128. A sensing node as set forth in any of clauses 122-127, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0373] Clause 129. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: a component for receiving beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node; a component for receiving the PRS resources; and a component for performing sensing based on the PRS resources and the beam pattern information.

[0374] Clause 130. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: receiving beam pattern information including positioning reference signal (PRS) resources for beam coordination for RF sensing from a network node; receiving PRS resources; and performing sensing based on the PRS resources and the beam pattern information.

[0375] Clause 131. A method performed by a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmitting the sensing assistance data comprising the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node.

[0376] Clause 132. A method according to clause 131, wherein the sensing assistance data also includes an indication of a frequency layer that supports RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for PRS resources in the frequency layer.

[0377] Clause 133. The method of clause 132, wherein an angle of departure (AoD) based positioning session is not configured for the sensing node.

[0378] Clause 134. A method according to any of clauses 131-133, wherein PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing includes assistance data for the AoD based positioning.

[0379] Clause 135. The method of any of clauses 131-134, wherein the beam pattern information of the PRS resources used for beam coordination for RF sensing comprises an expected beam direction and an expected beam direction uncertainty.

[0380] Clause 136. The method of any of clauses 131-135, wherein the sensing node comprises one of a user equipment or a base station.

[0381] Clause 137. The method of any of clauses 131-136, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0382] Clause 138. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: at least one transceiver; at least one memory; and at least one processor, the at least one processor being coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: obtain sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmit the sensing assistance data comprising the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node via the at least one transceiver.

[0383] Clause 139. A network node according to clause 138, wherein the sensing assistance data further includes an indication of a frequency layer that supports RF sensing, and the beam pattern information of the PRS resources used for beam coordination for RF sensing is for PRS resources in the frequency layer.

[0384] Clause 140. The network node of clause 139, wherein an angle of departure (AoD) based positioning session is not configured for the sensing node.

[0385] Clause 141. A network node according to any of clauses 138-140, wherein PRS resources support angle of departure (AoD) based positioning, and the beam pattern information of the PRS resources used for beam coordination for RF sensing includes assistance data for the AoD based positioning.

[0386] Clause 142. A network node as set forth in any of clauses 138-141, wherein the beam pattern information of the PRS resources used for beam coordination for RF sensing comprises an expected beam direction and an expected beam direction uncertainty.

[0387] Clause 143. The network node of any of clauses 138-142, wherein the sensing node comprises one of a user equipment or a base station.

[0388] Clause 144. A network node as set forth in any of clauses 138-143, wherein the network node from which the sensing assistance data is received comprises a network server or the sensing node is a sensing receiver node and the network node is a sensing sender node.

[0389] Clause 145. A network node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the network node comprising: a component for obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and a component for transmitting the sensing assistance data comprising the beam pattern information of the PRS resource for beam coordination for RF sensing to the sensing node.

[0390] Clause 146. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a network node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: obtaining sensing assistance data for a sensing node in the wireless network, the sensing assistance data comprising beam pattern information of a positioning reference signal (PRS) resource for beam coordination for RF sensing; and transmitting to the sensing node the sensing assistance data comprising the beam pattern information of the PRS resource for beam coordination for RF sensing.

[0391] Therefore, it is intended that the claimed subject matter not be limited to the particular examples disclosed, but that the claimed subject matter may also include all aspects falling within the scope of the appended claims and their equivalents.

Claims

1. A method performed by a sensing node in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the method comprising: receiving, from a network node, sensing assistance data including information for performing Doppler estimation based on the RF signal; receiving the RF signal; as well as Doppler estimation is performed using the RF signal and the sensing assistance data.

2. The method of claim 1, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information used for Doppler estimation comprises an indication of phase coherence of the PRS.

3. The method of claim 2, wherein the indication of the phase coherence of the PRS comprises an indication of at least one PRS group having phase coherence, and wherein performing the Doppler estimation is based on the at least one PRS group having phase coherence.

4. The method of claim 2, wherein the indication of the phase coherence of the PRS comprises an indication of at least one transmit receive point (TRP) that supports transmission of the PRS with phase coherence, and wherein the Doppler estimation is performed based on the PRS received from the at least one TRP that supports transmission of the PRS with phase coherence.

5. The method of claim 2, wherein the indication of the phase coherence of the PRS comprises an indication of a frequency layer supporting transmission of PRS having phase coherence, and wherein performing the Doppler estimation is based on PRS received from the frequency layer supporting transmission of PRS having phase coherence.

6. The method of claim 2, wherein the indication of phase coherence of the PRS comprises an indication of any combination of frequency layers, transmit receive points (TRPs), PRS resource sets, and PRS resources that support phase coherence.

7. The method of claim 1, wherein the information used for Doppler estimation includes a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

8. The method of claim 7, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals. 9 . The method of claim 7 , wherein the reference signal is configured to be close to the PRS in the time domain.

10. The method of claim 7, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

11. The method of claim 1, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

12. The method of claim 11, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

13. The method of claim 11, wherein the sensing assistance data is specific to the sensing node, and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cx1 / Cx2 sampling.

14. The method of claim 1, wherein the network node from which the sensing assistance data is received comprises a network server, or the sensing node is a sensing receiver node and the network node is a sensing sender node.

15. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: at least one transceiver; at least one memory; as well as at least one processor coupled to the at least one transceiver and the at least one memory, wherein the at least one processor is configured to: receiving, via the at least one transceiver, sensing assistance data including information for performing Doppler estimation from the RF signal from a network node; receiving the RF signal via the at least one transceiver; as well as Doppler estimation is performed using the RF signal and the sensing assistance data.

16. The sensing node of claim 15, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the information used for Doppler estimation comprises an indication of phase coherence of the PRS.

17. The sensing node of claim 16, wherein the indication of phase coherence of the PRS comprises an indication of at least one group of PRSs having phase coherence, and wherein performing the Doppler estimation is based on the at least one group of PRSs having phase coherence.

18. The sensing node of claim 16, wherein the indication of the phase coherence of the PRS comprises an indication of at least one transmit receive point (TRP) that supports transmission of the PRS with phase coherence, and wherein the Doppler estimation is performed based on the PRS received from the at least one TRP that supports transmission of the PRS with phase coherence.

19. The sensing node of claim 16, wherein the indication of the phase coherence of the PRS comprises an indication of a frequency layer supporting transmission of the PRS with phase coherence, and wherein performing the Doppler estimation is based on PRS received from the frequency layer supporting transmission of the PRS with phase coherence.

20. The sensing node of claim 16, wherein the indication of phase coherence of the PRS comprises an indication of any combination of frequency layer, transmit receive point (TRP), PRS resource set, and PRS resources supporting phase coherence.

21. The sensing node of claim 15, wherein the information used for Doppler estimation comprises a positioning reference signal (PRS) and an indication of a reference signal associated for Doppler estimation.

22. The sensing node of claim 21, wherein the PRS and the reference signal associated for Doppler estimation are quasi co-located (QCL) signals.

23. The sensing node of claim 21, wherein the reference signal is configured to be close to the PRS in the time domain.

24. The sensing node of claim 21, wherein the reference signal comprises at least one of a tracking reference signal (TRS) or a radar waveform.

25. The sensing node of claim 15, wherein the information for Doppler estimation comprises information of a search window for the Doppler estimation, the information for the search window for the Doppler estimation comprising an expected Doppler and an expected Doppler uncertainty.

26. The sensing node of claim 25, wherein the RF signal comprises a positioning reference signal (PRS), and wherein the expected Doppler and the expected Doppler uncertainty are defined in a plurality of sets for each PRS resource or each set of PRS resources.

27. The sensing node of claim 25, wherein the sensing assistance data is specific to the sensing node, and each set of the expected Doppler and the expected Doppler uncertainty is associated with a path index, wherein the path index is a channel impulse response tap index relative to a first arrival path or is based on Cx1 / Cx2 sampling.

28. The sensing node of claim 15, wherein the network node from which the sensing assistance data is received comprises a network server, or the sensing node is a sensing receiver node and the network node is a sensing sender node.

29. A sensing node in a wireless network configured to support radio frequency (RF) sensing in the wireless network, the sensing node comprising: means for receiving, from a network node, sensing assistance data comprising information for performing Doppler estimation from RF signals; means for receiving said RF signal; as well as Means for performing Doppler estimation using the RF signal and the sensing assistance data.

30. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a sensing entity in a wireless network for supporting radio frequency (RF) sensing in the wireless network, the program code comprising instructions for: receiving, from a network node, sensing assistance data including information for performing Doppler estimation based on the RF signal; receiving the RF signal; and Doppler estimation is performed using the RF signal and the sensing assistance data.

Images