RF sensing communication

Abstract

An RF sensing method includes: generating an RF sensing request at an application device, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; sending the RF sensing request from the application device to the network entity; and receiving an RF sensing report at the application device from the network entity indicating the result of the RF sensing.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of Indian Patent Application No. 202021045182 entitled “RADIO FREQUENCY SENSING COMMUNICATION”, filed on October 16, 2020, which has been assigned to the assignee of this application and whose entire contents are incorporated herein by reference for all purposes. Background Technology

[0003] Wireless communication systems have undergone several generations of development, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data radio service with Internet capabilities, fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax), and fifth-generation (5G) service. Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), and GSM TDMA variants.

[0004] The fifth-generation (5G) mobile standard demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data rate to each of tens of thousands of users, and 1 gigabits per second (Gbps) to dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency significantly reduced compared to the current standard.

[0005] Overview

[0006] In one embodiment, a radio frequency (RF) sensing request device includes: an interface; a memory; and one or more processors communicatively coupled to the interface and the memory and configured to: send an RF sensing request to a network entity via the interface, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; and receive an RF sensing report from the network entity via the interface indicating the result of the RF sensing.

[0007] In one embodiment, an RF sensing method includes: generating an RF sensing request at an application device, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; sending the RF sensing request from the application device to the network entity; and receiving an RF sensing report at the application device from the network entity indicating the result of the RF sensing.

[0008] In one embodiment, an RF sensing request device includes: means for generating an RF sensing request, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; means for sending the RF sensing request to the network entity; and means for receiving an RF sensing report from the network entity indicating the result of the RF sensing.

[0009] In one embodiment, a non-transient processor-readable storage medium includes processor-readable instructions that cause one or more processors of an RF sensing requesting device to perform the following actions to facilitate the localization of a user equipment: generating an RF sensing request, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; sending the RF sensing request to the network entity; and receiving from the network entity an RF sensing report indicating the result of the RF sensing.

[0010] In one embodiment, a network entity includes: an interface; a memory; and one or more processors communicatively coupled to the interface and the memory and configured to: receive a radio frequency (RF) sensing request from an application device via the interface, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; determine a first RF configuration and a second RF configuration based on the RF sensing request; and transmit the first RF configuration to an RF transmitter and the second RF configuration to an RF receiver via the interface.

[0011] In one embodiment, a radio frequency (RF) sensing coordination method includes: receiving an RF sensing request from an application device at a network entity, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; determining a first RF configuration and a second RF configuration at the network entity based on the RF sensing request; and transmitting the first RF configuration from the network entity to an RF transmitter and the second RF configuration to an RF receiver.

[0012] In one embodiment, a network entity includes: means for receiving a radio frequency (RF) sensing request from an application device, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; means for determining a first RF configuration and a second RF configuration based on the RF sensing request; and means for transmitting the first RF configuration to an RF transmitter and the second RF configuration to an RF receiver.

[0013] In one embodiment, a non-transient processor-readable storage medium includes processor-readable instructions that cause one or more processors of a network entity to perform the following operations: receive a radio frequency (RF) sensing request from an application device, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; determine a first RF configuration and a second RF configuration based on the RF sensing request; and transmit the first RF configuration to an RF transmitter and the second RF configuration to an RF receiver. Brief description of the attached diagram

[0015] Figure 1 This is a simplified diagram of an example wireless communication system.

[0016] Figure 2 yes Figure 1 The diagram shows a block diagram of the components of an example user equipment.

[0017] Figure 3 This is a block diagram of the components of an example send / receive point.

[0018] Figure 4 This is a block diagram of the components of the example server, and various embodiments of this example server are described below. Figure 1 As shown in the image.

[0019] Figure 5 This is a simplified diagram of a passive positioning configuration.

[0020] Figure 6 This is a block diagram of an example application device.

[0021] Figure 7 This is a block diagram of an example sensing management function.

[0022] Figure 8 It is the signaling and process flow used for radio frequency sensing.

[0023] Figure 9 This is a simplified diagram of an example of presence detection performed via radio frequency sensing.

[0024] Figure 10 This is a simplified diagram of an example of environmental mapping performed through radio frequency sensing.

[0025] Figure 11 This is a simplified diagram of an example of biological function detection performed through radio frequency sensing.

[0026] Figure 12 This is a flowchart of a radio frequency sensing method.

[0027] Figure 13 This is a flowchart of the radio frequency sensing coordination method.

[0028] Detailed description

[0029] This article discusses techniques for radio frequency (RF) sensing using cellular networks. For example, an application device (also known as an application function) may request RF sensing (also known as passive localization) to be performed, for example, for object location detection, for object movement detection, for environment mapping, for biometric detection, etc. The application device may send a request for RF sensing to a network entity (e.g., a sensing management function that coordinates physical signaling (from one or more transmitters and received by one or more receivers)). This request may include auxiliary data to help coordinate the RF sensing and / or the processing results of the RF sensing. The network entity may obtain RF sensing results (e.g., measurements) from the receivers and may process the RF sensing results into further results (e.g., object type, object presence, biometrics, etc.) and provide an RF sensing report to another entity (e.g., to the application device). The application device may provide feedback to the network entity to assist in future RF sensing and / or future processing of RF sensing results. These are examples, and other examples (for UEs and / or guidelines) may be implemented.

[0030] Many applications can benefit from the techniques discussed in this paper. For example, object identification can be performed based on the amount of energy reflected by an object, which depends on one or more reflective surfaces of that object and is a function of that object (e.g., an automated guided vehicle (AGV), furniture, a human, other living organism, etc.). For human identification, a classifier can be trained based on reflections from different people, and an entity can be able to identify a specific human based on small variations in the reflections caused by each person. For example, different people have different shapes, and these different shapes generate different amounts of reflected energy. Identification of specific humans may be particularly feasible in environments with a limited number of people to distinguish (e.g., in a home, a small business, etc.). As another example application, group size can be detected. An entity can be trained to determine and output the size of a group in a specific area based on sensed information. Different levels of group detection can be performed, such as binary detection (presence or absence of a group) or multi-level detection (e.g., small group, medium group, large group, etc.). Multi-level detection can be based on a threshold of the presence of people. Group detection can be separate from or built upon human presence detection. As another example application, one or more objects can be tracked. For example, detected objects can be tracked over time, and the tracking duration can be infinite or specified (e.g., specified by application functionality). As another example application, object velocity can be detected. For example, the velocity of the tracked object can be determined and can be precisely indicated and / or categorized by velocity range (e.g., slow, medium, fast, etc.). As another example application, various biological functions can be detected, and metrics of these biological functions can be determined. For example, respiratory rate and / or heart rate can be detected based on radio frequency reflections. By using determined rates, an entity can determine one or more corresponding states (such as mood, sleep stage, etc.) of the person whose biological function metrics are determined. For example, different emotions can cause changes in a person's heart rate and / or the amplitude of chest displacement. Such changes can result in different RF reflections, which can correspond to emotions that are detected and categorized. By processing the RF reflections, the entity can determine (e.g., identify) such changes and map these changes to biological states (e.g., mood, sleep stage, etc.).

[0031] The projects and / or technologies described herein can provide one or more of the following capabilities, as well as others not mentioned. RF sensing can be provided using cellular networks (e.g., cellular-connected devices). It can facilitate any of the many RF sensing applications, such as automotive radar applications, object presence detection, environment mapping, biometric presence detection, biometric determination, etc. Other capabilities can be provided, and not every implementation according to this disclosure is required to provide any of the capabilities discussed, let alone all of them.

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

[0033] This description may refer to a sequence of actions to be performed by elements such as a computing device. The various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of both. The sequence of actions described herein can be implemented in a non-transitory computer-readable medium storing a corresponding set of computer instructions that, upon execution, will cause the associated processor to perform the functionality described herein. Therefore, the aspects described herein can be implemented in several different forms, all of which fall within the scope of this disclosure, including the claimed subject matter.

[0034] As used herein, the terms “User Equipment” (UE) and “Base Station” are not specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise stated. Generally, such a UE can be any wireless communication device (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. The UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT”, “Client Equipment”, “Wireless Equipment”, “Subscriber Equipment”, “Subscriber Terminal”, “Subscriber Station”, “User Terminal” or “UT”, “Mobile Terminal”, “Mobile Station”, “Mobile Equipment”, or variations thereof. Generally, a 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 via a wired access network, a WiFi network (e.g., based on IEEE 802.11, etc.).

[0035] Depending on the network in which the base station is deployed, it may operate according to one of several RATs when communicating with the UE. Examples of base stations include access points (APs), network nodes, B-nodes, evolved B-nodes (eNBs), or generic B-nodes (gNodeBs, gNBs). Additionally, in some systems, the base station may provide purely edge node signaling functions, while in others, it may provide additional control and / or network management functions.

[0036] The UE can be implemented using any of several types of devices, including but not limited to printed circuit (PC) cards, dense flash memory devices, external or internal modems, wireless or wired telephones, smartphones, tablet devices, consumer asset tracking devices, asset tags, etc. The communication link through which the UE can send signals to the RAN is called an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the RAN can send signals to the UE is called a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0037] As used herein, depending on the context, the terms "cell" or "sector" may correspond to one of multiple 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 identifiers to distinguish adjacent cells operating via the same or different carriers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a carrier may support multiple cells and may be configured with different protocol types that 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 the geographic coverage area on which a logical entity operates (e.g., a sector).

[0038] Reference Figure 1Examples of communication system 100 include UE 105, UE 106, radio access network (RAN) (here, fifth-generation (5G) next-generation (NG) RAN (NG-RAN) 135), 5G core network (5GC) 140, and server 150. UE 105 and / or UE 106 can be, for example, IoT devices, location tracker devices, cellular phones, vehicles (e.g., cars, trucks, buses, ships, etc.) or other devices. 5G networks can also be referred to as new radio (NR) networks; NG-RAN 135 can be referred to as 5G RAN or NR RAN; and 5GC 140 can be referred to as NG core network (NGC). Standardization of NG-RAN and 5GC is underway within the Third Generation Partnership Project (3GPP). Accordingly, NG-RAN 135 and 5GC 140 can comply with current or future standards from 3GPP for 5G support. NG-RAN 135 can be another type of RAN, such as 3G RAN, 4G Long Term Evolution (LTE) RAN, etc. UE106 can be similarly configured and coupled to UE105 to send and / or receive signals to and / or from similar entities in system 100, but for simplicity of the figures, in Figure 1 Such signaling is not indicated in this document. Similarly, for simplicity, the discussion focuses on UE 105. Communication system 100 may utilize information from the constellation 185 of spacecraft (SVs) 190, 191, 192, 193 of a satellite positioning system (SPS) (e.g., a Global Navigation Satellite System (GNSS)), such as GPS, GLONASS, Galileo, or BeiDou, or some other local or regional SPS (such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Coverage Service (EGNOS), or the Wide Area Augmentation System (WAAS)). Additional components of communication system 100 are described below. Communication system 100 may include additional or replacement components.

[0039] like Figure 1As shown, NG-RAN 135 includes NR B-nodes (gNB) 110a, 110b and Next Generation Evolution B-node (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Functions (AMF) 115, Session Management Functions (SMF) 117, Location Management Functions (LMF) 120 and Gateway Mobility Location Center (GMLC) 125. gNBs 110a, 110b and ng-eNB 114 are communicatively coupled to each other, each configured to conduct bidirectional wireless communication with UE 105, and each communicatively coupled to and configured to conduct bidirectional communication with AMF 115. gNBs 110a, 110b and ng-eNB 114 may be referred to as base stations (BS). AMF 115, SMF 117, LMF 120 and GMLC 125 are communicatively coupled to each other, and the GMLC is communicatively coupled to an external client 130. SMF 117 can be used as the initial contact point for Service Control Functions (SCF) (not shown) to create, control, and delete media sessions. Base stations (such as gNB 110a, 110b, and / or ng-eNB 114) can be macrocells (e.g., high-power cellular base stations), small cells (e.g., low-power cellular base stations), or access points (e.g., short-range base stations configured to use short-range technologies such as WiFi, WiFi Direct (WiFi-D)). (Communication via Low Energy (BLE), Zigbee, etc.). One or more BSs (e.g., one or more of gNB 110a, 110b and / or ng-eNB 114) can be configured to communicate with UE 105 via multiple carriers. Each of gNB 110a, 110b and ng-eNB 114 can provide communication coverage for a corresponding geographic area (e.g., cell). Each cell can be divided into multiple sectors based on the base station antennas.

[0040] Figure 1A general explanation of each component is provided, wherein any or all of the components may be used appropriately, and each component may be repeated or omitted as needed. Specifically, although one UE 105 is explained, many UEs (e.g., hundreds, thousands, millions, etc.) may be used in communication system 100. Similarly, communication system 100 may include a larger (or smaller) number of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNB 110a, 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The explained connections connecting the various components in 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. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0041] Although Figure 1 While 5G-based networks have been described, similar network implementations and configurations can be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. The implementations described herein (for 5G technologies and / or for one or more other communication technologies and / or protocols) can be used to transmit (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 servers), and / or calculate the location of UE 105 at a location-capable device (such as UE 105, gNB 110a, 110b, or LMF 120) based on measurement parameters of such directional transmissions received at UE 105. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (evolved B-node) 114, and gNB (g B-node) 110a, 110b are examples and may be replaced by or include various other location server functions and / or base station functions in various embodiments.

[0042] System 100 is capable of wireless communication because its components can communicate directly or indirectly (at least sometimes using a wireless connection), for example, via gNB 110a, 110b, ng-eNB 114 and / or 5GC 140 (and / or one or more other devices not shown, such as one or more other base transceiver stations). For indirect communication, the communication may be altered during transmission from one entity to another, such as changing the header information of data packets, changing the format, etc. UE 105 may include multiple UEs and may be a mobile wireless communication device, but can communicate wirelessly and via wired connections. UE 105 can be any of a variety of devices, such as a smartphone, tablet computer, vehicle-based device, etc., but these are merely examples, as UE 105 does not need to be any of these configurations, and other configurations of the UE can be used. Other UEs may include wearable devices (e.g., smartwatches, smart jewelry, smart glasses, or head-mounted devices). Other UEs, whether currently existing or developed in the future, may also be used. In addition, other wireless devices (whether mobile or not) can be implemented within system 100 and can communicate with each other and / or with UE 105, gNB 110a, 110b, ng-eNB 114, 5GC 140, and / or external client 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 client 130 (e.g., a computer system), for example, to allow external client 130 (e.g., via GMLC 125) to request and / or receive location information about UE 105.

[0043] UE 105 or other devices can 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 Communications), CDMA (Code Division Multiple Access), LTE (Long Term Evolution), V2X (vehicle-to-everything, e.g., V2P (vehicle to pedestrian), V2I (vehicle to infrastructure), V2V (vehicle to vehicle) etc.), IEEE (e.g., 802.11p). V2X communication can be cellular (Cellular-V2X (C-V2X)) and / or WiFi (e.g., DSRC (Dedicated Short Range Connectivity)). System 100 can support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals on multiple carriers simultaneously. Each modulated signal can 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, etc. Each modulated signal can be transmitted on a different carrier and can carry pilot, overhead information, data, etc. UEs 105 and 106 can communicate with each other via UE-to-UE sidelink (SL) communication by transmitting on one or more sidelink channels (such as the Physical Sidelink Synchronization Channel (PSSCH), Physical Sidelink Broadcast Channel (PSBCH), or Physical Sidelink Control Channel (PSCCH)).

[0044] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Positioning Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 105 may correspond to a cellular phone, smartphone, laptop device, tablet device, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not mandatory, UE 105 may support one or more Radio Access Technologies (RATs) 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). Wireless communication can be achieved using technologies such as Bit-Band (BT), WiMAX, and 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140). UE 105 can support wireless communication using a Wireless Local Area Network (WLAN), which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE 105 (e.g., via elements of 5GC 140) to... Figure 1 (not shown in the diagram) or possibly via GMLC 125, communicate with external client 130 and / or allow external client 130 (e.g., via GMLC 125) to receive location information about UE 105.

[0045] UE 105 may include a single entity or may include multiple entities, such as in a personal area network, where the user may employ audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 105 may be referred to as location, location estimation, location locking, lock, positioning, location estimation, or location locking, and may be geographic, providing location coordinates (e.g., latitude and longitude) of UE 105, which may or may not include an elevation component (e.g., height above sea level; height above ground level, floor level, or basement level, or depth below). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., expressed as a postal address or a designation of a point or smaller area within 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 UE 105 can be expressed as a relative location, which includes, for example, distance and direction from a known location. A relative location can be expressed as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be, for example, geographically, municipally, 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" can include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and possibly z coordinates are typically solved, and then (if necessary) the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and elevation above or below mean sea level).

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

[0047] Figure 1 The base stations (BSs) in the NG-RAN 135 shown include NRB nodes (referred to as gNBs 110a and 110b). Each pair of gNBs 110a and 110b in the NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication between UE 105 and one or more of the gNBs 110a and 110b. gNBs 110a and 110b can use 5G to provide wireless communication access to the 5GC140 on behalf of UE 105. Figure 1 In this context, it is assumed that the serving gNB of UE 105 is gNB 110a, but another gNB (e.g., gNB 110b) may act as the serving gNB or as a secondary gNB to provide additional throughput and bandwidth to UE 105 if UE 105 moves to another location.

[0048] Figure 1The base station (BS) in NG-RAN 135 shown may include ng-eNB 114 (also referred to as a next-generation evolved B node). ng-eNB 114 may be connected to one or more of gNBs 110a and 110b in NG-RAN 135 (possibly via one or more other gNBs and / or one or more other ng-eNBs). ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of gNBs 110a, 110b and / or ng-eNB 114 may be configured to act as a location-only beacon, transmitting signals to aid in determining the location of UE 105, but may not be able to receive signals from UE 105 or other UEs.

[0049] gNB 110a, 110b and / or ng-eNB 114 may each include one or more TRPs. For example, each sector within a BS cell may include a TRP, but multiple TRPs may share one or more components (e.g., share a processor but have separate antennas). System 100 may exclusively include macro TRPs, or system 100 may have different types of TRPs, such as macro, pico, and / or femto TRPs. Macro TRPs may cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by terminals with service subscriptions. Pico TRPs may cover a relatively small geographic area (e.g., a pico cell) and allow unrestricted access by terminals with service subscriptions. Femto or home TRPs may cover a relatively small geographic area (e.g., a femto cell) and allow restricted access by terminals associated with that femto cell (e.g., a user's terminal in a residence).

[0050] 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 RU 111, DU 112, and CU 113. RU 111, DU 112, and CU 113 define the functionality of the gNB 110a. Although the gNB 110a is shown as having a single RU, a single DU, and a single CU, a gNB may include one or more RUs, one or more DUs, and / or one or more CUs. The interface between CU 113 and DU 112 is referred to as the F1 interface. RU 111 is configured to perform digital front-end (DFE) functions (e.g., analog-to-digital conversion, filtering, power amplification, transmit / receive) and digital beamforming, and includes a portion of the physical (PHY) layer. RU 111 may perform DFE using massive MIMO and may be integrated with one or more antennas of the gNB 110a. DU 112 stores the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer of gNB 110a. A DU can support one or more cells, and each cell is supported by one DU. The operation of DU 112 is controlled by CU 113. CU 113 is configured to perform functions for delivering user data, mobility control, radio access network sharing, location, session management, etc., although some functions are exclusively assigned to DU 112. CU 113 stores the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 110a. UE 105 can communicate with CU 113 via the RRC, SDAP, and PDCP layers, with DU 112 via the RLC, MAC, and PHY layers, and with RU 111 via the PHY layer.

[0051] As mentioned, although Figure 1 The diagram depicts nodes configured to communicate according to 5G communication protocols, but nodes configured to communicate according to other communication protocols (such as, for example, LTE or IEEE 802.11x protocols) can also be used. For example, in an evolved packet system (EPS) providing LTE radio 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 containing evolved B-nodes (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... Figure 1 NG-RAN 135 and EPC corresponds to Figure 1 5GC 140 in the middle.

[0052] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115; for positioning functionality, AMF 115 communicates with LMF 120. AMF 115 supports the mobility of UE 105 (including radio cell changes and handover) and can participate in supporting signaling connections to UE 105 and, possibly, data and voice bearers for UE 105. LMF 120 can communicate directly with UE 105, for example, wirelessly, or directly with gNB 110a, 110b, and / or ng-eNB 114. The LMF 120 supports UE 105 positioning when UE 105 accesses NG-RAN 135, and supports various positioning protocols / methods, such as Auxiliary 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 Cellular ID (E-CID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other positioning methods. The LMF 120 can process location service requests for UE 105 received, for example, from AMF115 or GMLC 125. The LMF 120 can connect to AMF115 and / or GMLC 125. The LMF 120 may be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). The node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as an Enhanced Serving Mobility Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least some of the location functionality (including the derivation of the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 for signals transmitted by radio nodes (such as gNB 110a, 110b and / or ng-eNB 114), and / or auxiliary data provided to UE 105, for example, by LMF 120). AMF 115 can be used as a control node to process signaling between UE 105 and 5GC 140 and can provide QoS (Quality of Service) streaming and session management. AMF 115 can support the mobility of UE 105 (including cell changes and handovers) and can participate in supporting signaling connections to UE 105.

[0053] Server 150 (e.g., a cloud server) is configured to obtain the location estimate of UE 105 and provide it to external client 130. Server 150 may, for example, be configured to run a microservice / service for obtaining the location estimate of UE 105. Server 150 may, for example, obtain the location estimate from (e.g., by sending a location request) one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, CU 113), and / or ng-eNB 114, and / or LMF 120. As another example, one or more of UE 105, gNB 110a, 110b (e.g., via RU 111, DU 112, and CU 113), and / or LMF 120 may push the location estimate of UE 105 to server 150.

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

[0055] like Figure 1 Further explanation is provided: the LMF 120 can use the new Radio Positioning Protocol A (which may be referred to as NPPa or NRPPa) to communicate with gNB 110a, 110b, and / or ng-eNB 114. This new Radio Positioning Protocol A is defined in 3GPP Technical Specification (TS) 38.455. NRPPa can be the same as, similar to, or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455, where NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and the LMF 120, and / or between ng-eNB 114 and the LMF 120. Figure 1As further explained, LMF 120 and UE 105 can communicate using the LTE Location Protocol (LPP), which is defined in 3GPP TS 36.355. LMF 120 and UE 105 can also 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 LPP. Here, LPP and / or NPP messages can be transmitted between UE 105 and LMF 120 via AMF 115 and UE 105's serving gNB 110a, 110b, or serving ng-eNB 114. For example, LPP and / or NPP messages can be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP and / or NPP protocols can be used to support the location of UE 105 using UE-assisted and / or UE-based location methods (such as A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based location methods (such as E-CID) (e.g., in conjunction with measurements obtained by gNB110a, 110b, or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters for directional SS transmissions from gNB 110a, 110b, and / or ng-eNB 114. LMF 120 can coexist with or be integrated with the gNB or TRP, or can be configured to communicate directly or indirectly with the gNB and / or TRP, located away from the gNB and / or TRP.

[0056] Using a UE-assisted positioning method, UE 105 can obtain location measurements and send these measurements to a location server (e.g., LMF 120) for calculating the location estimate of UE 105. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), and / or Reference Signal Received Quality (RSRQ) for gNB 110a, 110b, ng-eNB 114, and / or WLAN AP. Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190-193.

[0057] Using a UE-based positioning method, UE 105 can obtain a location measurement (e.g., which may be the same as or similar to a location measurement for a UE-assisted positioning method) and can calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110a, 110b, ng-eNB 114 or other base stations or APs).

[0058] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can acquire location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, or Time of Arrival (ToA) of signals transmitted by UE 105) and / or can receive measurements acquired by UE 105. These base stations or APs can then transmit these measurements to a location server (e.g., LMF 120) for calculating a location estimate for UE 105.

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

[0060] The LPP or NPP message sent from LMF 120 to UE 105 may instruct UE 105 to perform any of a variety of tasks, depending on the desired functionality. For example, the LPP or NPP message may contain 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 or NPP message may instruct UE 105 to obtain one or more measurement parameters (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a specific cell supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or supported by some other type of base station (such as eNB or WiFi AP)). UE 105 can send these measurement parameters back to LMF 120 via service gNB110a (or service ng-eNB 114) and AMF 115 in an LPP or NPP message (e.g., within a 5G NAS message).

[0061] As mentioned, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) used to support and interact with mobile devices (such as UE 105) (e.g., to enable voice, data, location, and other functionalities). In some such embodiments, the 5GC 140 can be configured to control different air interfaces. For example, non-3GPP interoperability functions (N3IWF) in the 5GC 140 can be used. Figure 1 (Not shown) Connects 5GC140 to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for UE 105 and may include one or more WiFi APs. Here, N3IWF may connect to the WLAN and other components in 5GC 140, such as AMF 115. In some embodiments, both NG-RAN 135 and 5GC 140 may be replaced by one or more other RANs and one or more other core networks. For example, in EPS, NG-RAN 135 may be replaced by E-UTRAN containing eNBs, and 5GC 140 may be replaced by EPC containing a Mobility Management Entity (MME) instead of AMF 115, an E-SMLC instead of LMF 120, and a GMLC similar to GMLC 125. In such EPS, the E-SMLC may use LPPa instead of NRPPa to send location information to and receive location information from eNBs in the E-UTRAN, and may use LPP to support UE 105's positioning. In these other embodiments, the location of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks, the difference being that the functions and procedures described herein for gNB110a, 110b, ng-eNB 114, AMF 115 and LMF120 can be applied alternatively to other network elements, such as eNB, WiFi AP, MME and E-SMLC, in some cases.

[0062] As mentioned, in some embodiments, positioning functionality can be achieved at least in part using directional SS beams transmitted by base stations (such as gNB 110a, 110b and / or ng-eNB 114) to determine the location of the UE (e.g., Figure 1 Within the range of UE 105. In some instances, the UE can use directional SS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

[0063] Also refer to Figure 2UE 200 is an example of one of UEs 105 and 106, and includes a computing platform containing a processor 210, a memory 211 containing 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, memory 211, sensors 213, transceiver interface 214, user interface 216, SPS receiver 217, camera 218, and positioning device 219 can be communicatively coupled to each other via a bus 220 (which can be configured for, for example, optical and / or electrical communication). One or more of the illustrated devices (e.g., camera 218, positioning device 219, and / or one or more sensors 213, etc.) can be omitted from UE 200. Processor 210 may include one or more intelligent hardware devices (e.g., a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc.). Processor 210 may include multiple processors, including a general-purpose / 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 of processors 230-234 may include multiple devices (e.g., multiple processors). For example, sensor processor 234 may include processors for, for example, RF (radio frequency) sensing (where one or more transmitted (cellular) wireless signals and reflections are used to identify, map, and / or track objects), and / or ultrasound, etc. Modem processor 232 may support dual SIM / dual connectivity (or even more SIMs). For example, one SIM (subscriber identity module or subscriber identification module) may be used by an original equipment manufacturer (OEM), and another SIM may be used by an end user of UE 200 to obtain connectivity. Memory 211 is a non-transient storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 211 stores software 212, which may be processor-readable, processor-executable software code containing instructions configured to cause processor 210 to perform the various functions described herein when executed. Alternatively, software 212 may not be directly executable by processor 210, but may be configured (e.g., when compiled and executed) to cause processor 210 to perform various functions. This specification may refer to processor 210 performing functions, but this includes other implementations, such as processor 210 performing software and / or firmware implementations. This specification may refer to processor 210 performing functions as a shorthand for one or more of processors 230-234 performing that function.This specification may refer to the UE 200 execution function as an abbreviation for one or more appropriate components of the UE 200 performing the function. The processor 210 may include memory with stored instructions as a supplement to and / or replacement of memory 211. The functionality of the processor 210 is discussed more fully below.

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

[0065] UE 200 may include a modem processor 232, which may be capable of performing baseband processing on signals received and downconverted by transceiver 215 and / or SPS receiver 217. Modem processor 232 may also perform baseband processing on signals to be upconverted for transmission by transceiver 215. Alternatively, baseband processing may be performed by processor 230 and / or DSP 231. However, other configurations may be used to perform baseband processing.

[0066] UE 200 may include sensors 213, which may include 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. An inertial measurement unit (IMU) may include, for example, one or more accelerometers (e.g., collectively responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes (e.g., three-dimensional gyroscopes). Sensors 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., supporting one or more compass applications). Environmental sensors may include, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones. Sensors 213 can generate analog and / or digital signals, and indications of these signals can be stored in memory 211 and processed by DSP 231 and / or processor 230 to support one or more applications (such as, for example, applications involving positioning and / or navigation operations).

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

[0068] The IMU can be configured to provide measurements of the UE 200's direction of motion and / or velocity, which can be used for relative position determination. For example, one or more accelerometers and / or one or more gyroscopes of the IMU can detect the UE 200's linear acceleration and rotational velocity, respectively. The UE 200's linear acceleration and rotational velocity measurements can be integrated over time to determine the UE 200's instantaneous direction of motion and displacement. The instantaneous direction of motion and displacement can be integrated to track the UE 200's position. For example, an SPS receiver 217 (and / or some other means) can be used to determine the UE 200's reference position at a given moment, and measurements acquired from the accelerometers and gyroscopes after that moment can be used for dead reckoning to determine the UE 200's current position based on its movement (direction and distance) relative to that reference position.

[0069] (A) Magnetometers can determine the strength of magnetic fields in different directions, which can be used to determine the orientation of UE 200. For example, this orientation can be used to provide a digital compass for UE 200. (A) Magnetometers may include two-dimensional magnetometers configured to detect and provide indications of magnetic field strength in two orthogonal dimensions. (A) Magnetometers may include three-dimensional magnetometers configured to detect and provide indications of magnetic field strength in three orthogonal dimensions. (A) Magnetometers may provide means for sensing magnetic fields and, for example, providing magnetic field indications to processor 210.

[0070] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a wireless transmitter 242 and a wireless receiver 244 coupled to 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 wireless signals 248 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 248. Thus, wireless transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to transmit signals according to various radio access technologies (RATs) (e.g., with TRP and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), 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, and WiFi Direct (WiFi-D). Zigbee, etc. The new radio can use millimeter-wave frequencies and / or sub-6 GHz frequencies. Wired transceiver 250 may include a wired transmitter 252 and a wired receiver 254 configured for wired communication, for example, a network interface that can be used to communicate with NG-RAN 135 to send and receive communications from NG-RAN 135. Wired transmitter 252 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or wired receiver 254 may include multiple receivers, which may be discrete components or combined / integrated components. Wired transceiver 250 may be configured, for example, for optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214 (e.g., via optical and / or electrical connections). Transceiver interface 214 may be at least partially integrated with transceiver 215. The wireless transmitter 242, the wireless receiver 244, and / or the antenna 246 may each include multiple transmitters, multiple receivers, and / or multiple antennas for transmitting and / or receiving appropriate signals, respectively.

[0071] User interface 216 may include one or more of a number of devices, such as, for example, speakers, microphones, display devices, vibration devices, keyboards, touchscreens, etc. User interface 216 may include any device that includes more than one of these devices. User interface 216 may be configured to enable a user to interact with one or more applications stored in the main memory of UE 200. For example, user interface 216 may store indications of analog and / or digital signals in memory 211 in response to actions from the user, for processing by DSP 231 and / or general-purpose processor 230. Similarly, applications in the main memory of UE 200 may store indications of analog and / or digital signals in memory 211 to present output signals to the user. User interface 216 may include audio input / output (I / O) devices, including, for example, speakers, microphones, digital-to-analog circuitry systems, analog-to-digital circuitry systems, amplifiers, and / or gain control circuitry systems (any device including more than one of these devices). Other configurations of the audio I / O devices may be used. Alternatively or concurrently, the user interface 216 may include one or more touch sensors that respond to touch and / or pressure on, for example, the keyboard and / or touchscreen of the user interface 216.

[0072] SPS receiver 217 (e.g., a Global Positioning System (GPS) receiver) can receive and acquire SPS signal 260 via SPS antenna 262. SPS antenna 262 is configured to convert SPS signal 260 from a wireless signal to a wired signal (e.g., an electrical or optical signal) and can be integrated with antenna 246. SPS receiver 217 can be configured to process the acquired SPS signal 260 fully or partially to estimate the location of UE 200. For example, SPS receiver 217 can be configured to determine the location of UE 200 by performing trilateration using SPS signal 260. SPS receiver 217 can be combined with general-purpose processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown) to process the acquired SPS signal fully or partially and / or calculate the estimated location of UE 200. Memory 211 may store indications (e.g., measurements) of SPS signal 260 and / or other signals (e.g., signals acquired from wireless transceiver 240) for use during positioning operations. General-purpose processor 230, DSP 231, and / or one or more dedicated processors, and / or memory 211 may provide or support a position engine for processing measurements to estimate the position of UE 200.

[0073] 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 imager), lenses, analog-to-digital circuitry, frame buffers, etc. Additional processing, conditioning, encoding, and / or compression of the signals representing the captured images may be performed by a general-purpose processor 230 and / or a DSP 231. Alternatively, video processor 233 may perform conditioning, encoding, compression, and / or manipulation of the signals representing the captured images. Video processor 233 may decode / decompress stored image data for presentation on a display device (not shown), for example, a user interface 216.

[0074] Location 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 SPS receiver 217. PD 219 may appropriately cooperate with processor 210 and memory 211 to perform at least a portion of one or more location methods, although the description herein may only refer to PD 219 being configured to perform or to be performed according to a location method. PD 219 may additionally or alternatively be configured to: perform trilateration using terrestrial signals (e.g., at least some signals 248), assist in acquiring and using SPS signal 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 the serving base station (e.g., the cell center) and / or another technology (such as E-CID). PD 219 can be configured to determine the location of UE 200 using one or more images from camera 218 and image recognition combined with the known location of landmarks (e.g., natural landmarks such as mountains and / or man-made landmarks such as buildings, bridges, streets, etc.). PD 219 can be configured to determine the location of 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 positioning beacon)), and can use a combination of these technologies (e.g., SPS and terrestrial positioning signals) to determine the location of UE 200. PD 219 may include one or more sensors 213 (e.g., gyroscopes, accelerometers, magnetometers, etc.) that sense the orientation and / or motion of UE 200 and provide an indication of such orientation and / or motion, and processor 210 (e.g., processor 230 and / or DSP 231) can be configured to use this indication to determine the motion of UE 200 (e.g., velocity vector and / or acceleration vector). PD 219 can be configured to provide an indication of uncertainty and / or error in the determined positioning and / or motion. The functionality of PD 219 can be provided in a variety of ways and / or configurations, such as by a general-purpose / application processor 230, transceiver 215, SPS receiver 217 and / or another component of UE 200, and can be provided by hardware, software, firmware or various combinations thereof.

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

[0076] This specification may refer to processor 310 performing functions, but this includes other implementations, such as processor 310 performing software and / or firmware implementations. This specification may refer to processor 310 performing functions as a shorthand for one or more processors included in processor 310 performing that function. This description may refer to TRP 300 performing functions as a shorthand for one or more appropriate components (e.g., processor 310 and memory 311) of TRP 300 (and thus one of gNB 110a, 110b and / or ng-eNB 114) performing that function. Processor 310 may include memory with stored instructions as a complement and / or alternative to memory 311. The functionality of processor 310 is discussed more fully below.

[0077] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a wireless transmitter 342 and a wireless receiver 344 coupled to one or more antennas 346 for transmitting and / or receiving wireless signals 348 (e.g., on one or more uplink channels and / or one or more downlink channels) and converting signals from wireless signals 348 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 348. Thus, wireless transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to support 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 Telephone 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, and WiFi Direct (WiFi-D). 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 NG-RAN 135 to send communications to and receive communications from LMF 120 (e.g., and / or one or more other network entities). 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, for example, optical communication and / or electrical communication.

[0078] Figure 3 The configuration of TRP 300 shown is exemplary and not intended to limit this disclosure (including the claims), and other configurations may be used. For example, the description herein discusses TRP 300 being configured to perform several functions or TRP 300 performing several functions, but one or more of these functions may be performed by LMF 120 and / or UE 200 (i.e., LMF 120 and / or UE 200 may be configured to perform one or more of these functions).

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

[0080] Transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 440 may include a wireless transmitter 442 and a wireless receiver 444 coupled to one or more antennas 446 for transmitting and / or receiving wireless signals 448 (e.g., on one or more downlink channels) and converting signals from wireless signals 448 to wired (e.g., electrical and / or optical) signals and from wired (e.g., electrical and / or optical) signals to wireless signals 448. Thus, wireless transmitter 442 may include multiple transmitters that may be discrete components or combined / integrated components, and / or wireless receiver 444 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 440 can be configured to support 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 Telephone 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, and WiFi Direct (WiFi-D). 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 NG-RAN 135 to send communications to and receive communications from TRP 300 (e.g., and / or one or more other entities). 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, for example, optical communication and / or electrical communication.

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

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

[0083] Positioning technology

[0084] For terrestrial positioning of UEs in cellular networks, techniques such as Advanced Forward Link Trilateral Measurement (AFLT) and Observed Time Difference of Arrival (OTDOA) typically operate in a “UE-assisted” mode, where measurements of reference signals transmitted by the base station (e.g., PRS, CRS, etc.) are acquired by the UE and subsequently provided to a location server. The location server then calculates the UE's location based on these measurements and the known location of the base station. Because these techniques use a location server (rather than the UE itself) to calculate the UE's location, they are not frequently used in applications such as car or cellular phone navigation, which typically rely on satellite-based positioning instead.

[0085] UEs can use Satellite Positioning System (SPS) (Global Navigation Satellite System (GNSS)) to achieve high-accuracy positioning using Precise Point Positioning (PPP) or Real-Time Kinematics (RTK) techniques. These techniques use auxiliary data, such as measurements from ground-based stations. LTE Release 15 allows data to be encrypted so that only UEs subscribed to the service can read the information. This auxiliary data changes over time. Therefore, a UE with a subscribed service may not be able to easily "crack the encryption" for other UEs by passing the data to them without paying for the subscription. This transmission needs to be repeated every time the auxiliary data changes.

[0086] In UE-assisted positioning, the UE sends 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) containing multiple "entries" or "records," one record per cell, where each record contains the geographic cell location, but may also include other data. Identifiers of the "records" among the multiple "records" in the BSA can be referenced. The BSA and measurements from the UE are used to calculate the UE's positioning.

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

[0088] Positioning technologies can be characterized and / or evaluated based on one or more criteria, such as positioning accuracy and / or latency. Latency is the time elapsed between the event that triggers the determination of positioning-related data and the availability of that data at the positioning system interface (e.g., the interface of the LMF120). The latency for the availability of positioning-related data during positioning system initialization is called the First Time Locked (TTFF) and is greater than the latency after the TTFF. The reciprocal of the time elapsed between two consecutive availability of positioning-related data is called the update rate, i.e., the rate at which positioning-related data is generated after the first lock. Latency can depend on (e.g., the UE's) processing capacity. For example, assuming an allocation of 272 PRBs (Physical Resource Blocks), the UE can report its processing capacity as the duration (in time units, e.g., milliseconds) of DL PRS symbols that it can process per T time units (e.g., T ms). Other examples of capabilities that may affect latency are the number of TRPs from which the UE can process PRS, the number of PRS the UE can process, and the UE's bandwidth.

[0089] One or more of many different positioning techniques (also known as positioning methods) can be used to determine the location of an entity (such as one of UE105, 106). Known positioning techniques include RTT, multiple RTT, OTDOA (also known as TDOA, and including UL-TDOA and DL-TDOA), Enhanced Cellular Identifier (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 range between the two entities. This range, plus the known location of the first entity and the angle (e.g., azimuth) between the two entities, can be used to determine the location of the second entity. In multiple RTT (also known as multi-cell RTT), multiple ranges from one entity (e.g., UE) to other entities (e.g., TRP) and the known locations of those other entities can be used to determine the location of this one entity. In TDOA, the travel time difference between an entity and other entities can be used to determine the relative range with respect to those other entities, and those relative ranges, combined with the known locations of those other entities, can be used to determine the location of this one entity. 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 range between devices (range determined using signals (e.g., signal travel time, signal received power, etc.)) and the known location of one of these devices, can be used to determine the location of the other device. The angle of arrival or angle of departure can be an azimuth angle 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., radially outward from the Earth's center). E-CID uses the identity of the serving cell, timing advance (i.e., the difference between the receive and transmit times at the UE), estimated timing and power of detected neighboring cell signals, and possible angles of arrival (e.g., the angle of arrival of signals from the base station at the UE, or vice versa) to determine the location of the UE. In TDOA, the time difference of arrival of signals from different sources at the receiving device, along with the known locations of these sources and the known offsets of the transmission times from these sources, are used to determine the location of the receiving device.

[0090] In network-centric RTT estimation, the serving base station instructs the UE to scan / receive RTT measurement signals (e.g., PRS) on serving cells of two or more adjacent base stations (and typically the serving base station, as at least three base stations are required). These one or more base stations transmit the 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 an LMF120). The UE records the arrival time (also referred to as reception time, time received, or time of arrival (ToA)) of each RTT measurement signal relative to the UE's current downlink timing (e.g., as derived by the UE from DL signals received from its serving base station), and (e.g., when instructed by its serving base station) transmits a shared or individual RTT response message (e.g., an SRS (probe reference signal) for positioning, i.e., UL-PRS) to these one or more base stations, and may transmit the time difference T between the ToA of the RTT measurement signal and the transmission time of the RTT response message. Rx→Tx (i.e., UE T) Rx-Tx or UE Rx-Tx This 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. This is achieved by comparing the transmission time of the RTT measurement signal from the base station with the difference T between the ToA of the RTT response at the base station and the time difference T. Tx→Rx Time difference T with UE report Rx→Tx The base station can infer the propagation time between the base station and the UE. From this propagation time, the base station can determine the distance between the UE and the base station by assuming that the propagation time is the speed of light.

[0091] UE-centric RTT estimation is similar to network-based methods, except that the UE transmits uplink RTT measurement signals (e.g., when instructed by a serving base station), which are received by multiple base stations near the UE. Each involved base station responds with a downlink RTT response message, which may include in its 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.

[0092] For both network-centric and UE-centric procedures, the side performing RTT calculation (network or UE) typically (but not always) transmits a first message or signal (e.g., an RTT measurement signal), while 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 transmission time of the RTT response message or signal.

[0093] Multiple-RTT (Multiple-Time To-Trip) techniques can be used to determine location. For example, a first entity (e.g., a UE) may emit one or more signals (e.g., unicast, multicast, or broadcast from a base station), and multiple second entities (e.g., other TSPs, such as a base station and / or the UE) may receive signals from the first entity and respond to those received signals. The first entity receives responses from the multiple second entities. The first entity (or another entity, such as an LMF) may use the responses from the second entities to determine the range to the second entities, and the location of the first entity may be determined by trilateration using the multiple ranges and the known locations of the second entities.

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

[0095] For positioning techniques that use PRS (Location Reference Signal) signals (e.g., TDOA and RTT), the PRS signals transmitted by multiple TRPs are measured, and the arrival time, known transmission time, and known location of the TRPs are used to determine the range from the UE to the TRPs. For example, RSTD (Reference Signal Time Difference) can be determined for PRS signals received from multiple TRPs, and these RSTDs are used in TDOA techniques to determine the UE's location. The Location Reference Signal may be referred to as the PRS or PRS signal. 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, such that a PRS signal from a more distant TRP may be overwhelmed by a PRS signal from a closer TRP, thus the signal from the more distant TRP may not be detected. PRS silencing can be used to help reduce interference by silencing some PRS signals (reducing the power of the PRS signal, e.g., reducing it to zero and thus not transmitting the PRS signal). In this way, the UE can more easily detect the weaker PRS signal (at the UE) without the interference of a stronger PRS signal. The term RS and its variations (e.g., PRS, SRS, CSI-RS (Channel State Information - Reference Signal)) can refer to one or more reference signals.

[0096] Positioning Reference Signals (PRS) include a downlink PRS (DL PRS, often simply referred to as PRS) and an uplink PRS (UL PRS) (which may be referred to as the SRS (Detection Reference Signal) used for positioning). PRS may include PN codes (pseudo-random codes) or be generated using PN codes (e.g., by modulating a carrier signal with PN codes) so that the PRS source can be used as a pseudo-satellite. PN codes can be unique for a PRS source (at least unique within a specified area, such that the same PRS from different PRS sources does not overlap). PRS may include PRS resources of a frequency layer or a set of PRS resources. 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 the higher-level parameters DL-PRS-PositioningFrequencyLayer (DL-PRS-PositioningFrequencyLayer), DL-PRS-ResourceSet (DL-PRS-Resource Set), and DL-PRS-Resource (DL-PRS-Resource). Each frequency layer has a DL PRS subcarrier spacing (SCS) for the DL PRS resource set and DL PRS resources within that frequency layer. Each frequency layer also has a DL PRS cyclic prefix (CP) for the DL PRS resource set and DL PRS resources within that frequency layer. In 5G, a resource block occupies 12 consecutive subcarriers and a specified number of symbols. Furthermore, 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 element for each symbol, such that for comb N, every Nth resource element is a PRS resource element). The PRS resource set is identified by the PRS resource set ID and can be associated with a specific TRP (identified by the cell ID) transmitted by the base station's antenna panel. A PRS resource ID in a PRS resource set can be associated with an omnidirectional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station can transmit one or more beams). Each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a PRS resource (or simply a resource) can also be referred to as a beam. This does not imply at all whether the UE is aware of the base station and beam transmitting the PRS.

[0097] The TRP can be configured, for example, by instructions received from a server and / or by software within the TRP, to transmit DL PRS according to a schedule. Based on this schedule, the TRP can transmit DL PRS intermittently (e.g., periodically at consistent intervals from the initial transmission). The TRP can be configured to transmit one or more PRS resource sets. A resource set is a collection of PRS resources across a TRP, wherein these resources have the same periodicity, a shared silent mode configuration (if any), and the same cross-slot repetition factor. Each PRS resource set comprises multiple PRS resources, wherein each PRS resource comprises multiple resource elements (REs), which may reside in multiple resource blocks (RBs) within N (or more) consecutive symbols in a time slot. An RB is a set of REs spanning one or more consecutive symbols in the time domain and a consecutive subcarrier number (12 for 5G) in the frequency domain. Each PRS resource is configured with an RE offset, a time slot offset, a symbol offset within a time slot, and a number of consecutive symbols that the PRS resource can occupy within a time slot. The RE offset defines the initial RE offset of the first symbol within a DL PRS resource in the frequency range. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on this initial offset. The slot offset is the starting slot of the DL PRS resource relative to the slot offset of the corresponding resource set. The symbol offset determines the starting symbol of the DL PRS resource within the starting slot. Transmitted REs can be repeated across slots, with each transmission referred to as a repetition, allowing for multiple repetitions within a PRS resource. 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 can transmit one or more beams).

[0098] PRS resources can also be defined by quasi-co-location and starting PRB parameters. The quasi-co-location (QCL) parameter defines any quasi-co-location information of the DL PRS resource with other reference signals. The DL PRS can be configured to be QCL type D with DL PRS or SS / PBCH (Synchronization Signal / Physical Broadcast Channel) blocks from serving or non-serving cells. The DL PRS can also be configured to be QCL type C with SS / PBCH blocks from serving or non-serving cells. The starting PRB parameter defines the starting PRB index of the DL PRS resource relative to reference point A. The granularity of the starting PRB index is one PRB, and the minimum value can be 0 and the maximum value is 2176 PRBs.

[0099] A PRS resource set is a collection of PRS resources with the same periodicity, the same silent mode configuration (if any), and the same cross-slot repetition factor. Each time all repetitions of all PRS resources in a PRS resource set are configured for transmission is called an "instance". Therefore, 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 the PRS resource set, such that the instance is completed once the specified number of repetitions have been transmitted for each of the specified number of PRS resources. An instance can also be referred to as an "opportunity". A DLPRS configuration, including DL PRS transmission scheduling, can be provided to the UE to facilitate DL PRS measurement (or even enable the UE to measure DL PRS).

[0100] Multiple frequency layers of a PRS can be aggregated to provide an effective bandwidth greater than any bandwidth of any individual layer. Multiple frequency layers belonging to component carriers (which can be coherent and / or separate) and satisfying criteria such as quasi-coexistence (QCL) and having the same antenna port can be stitched together to provide a larger effective PRS bandwidth (for DL ​​PRS and UL PRS), thereby improving the accuracy of time of arrival measurements. Stitching involves combining PRS measurements on individual bandwidth segments into a unified fragment so that the stitched PRS can be regarded as taken from a single measurement. In the case of QCL, different frequency layers behave similarly, resulting in a larger effective bandwidth for PRS stitching. A larger effective bandwidth (which may 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). An aggregated PRS comprises a collection of PRS resources, and each PRS resource in the aggregated PRS may be referred to as a PRS component, and each PRS component may be transmitted on different component carriers, frequency bands, or frequency layers, or on different portions of the same frequency band.

[0101] RTT positioning is an active positioning technology because RTT uses positioning signals sent by the TRP to the UE and by the UE (participating in RTT positioning) to the TRP. The TRP can send a DL-PRS signal received by the UE, and the UE can send an SRS (Probe Reference Signal) signal received by multiple TRPs. The Probe Reference Signal may be referred to as SRS or SRS signal. In 5G multi-RTT, coordinated positioning can be used, where the UE sends a single UL-SRS for positioning received by multiple TRPs, instead of sending a separate UL-SRS for positioning for each TRP. A participating TRP will typically search for UEs currently residing on that TRP (the served UE, where the TRP is the serving TRP) and also search for UEs residing on neighboring TRPs (neighbor UEs). A neighboring TRP can be a TRP of a single BTS (e.g., gNB), or it can be a TRP of a single BTS and a TRP of a single BTS. For RTT positioning (including multi-RTT positioning), the DL-PRS and UL-SRS positioning signals in the PRS / SRS positioning signal pair used to determine the RTT (and thus the range between the UE and TRP) may occur close to each other in time, so that the errors caused by UE movement 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 transmitted from the TRP and the UE within approximately 10 ms of each other. In cases where the SRS positioning signal is being transmitted by the UE and the PRS and SRS positioning signals are transmitted close to each other in time, it has been found that this may lead to radio frequency (RF) signal congestion (which may result in excessive noise, etc.) (especially if many UEs are concurrently attempting positioning), and / or computational congestion at the TRP where many UEs are concurrently attempting to measure.

[0102] RTT positioning can be UE-based or UE-assisted. In UE-based RTT, UE 200 determines the RTT and corresponding range to each of TRP 300, and determines the location of UE 200 based on the range to TRP 300 and the known location 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 the RTT and range. TRP 300 provides the range to a location server (e.g., server 400), and the server determines the location of UE 200, for example, based on the range to different TRP 300s. RTT and / or range may be determined by TRP 300, which receives signals from UE 200, by TRP 300 in conjunction with one or more other devices (e.g., one or more other TRP 300 and / or server 400), or by one or more devices other than TRP 300 that receive signals from UE 200.

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

[0104] Location estimation (e.g., for a UE) may be referred to by other names, such as location estimate, location, positioning, location lock, lock, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), or it can be municipal and include street addresses, postal addresses, or some other verbal description of location. Location estimation can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible altitude). Location estimation may include expected errors or uncertainties (e.g., by including the area or volume that the expected location will be included within with a specified or default confidence level).

[0105] RF sensing (passive positioning)

[0106] Reference Figure 5The passive positioning configuration 500 includes a target object 510, a transceiver 521, transmitters 522 and 523, and receivers 524 and 525. While positioning technologies such as RTT, OTDOA, UTDOA (UL OTDOA), and E-CID are active positioning technologies (where the target device includes RF devices), passive positioning technologies can be used to determine the location information of a target device that may or may not contain RF devices. Passive positioning is known as radio frequency sensing and has numerous applications, including health detection, context information acquisition, automotive radar, etc. Health detection applications detect one or more biological functions (e.g., measure one or more biometrics) and include, for example, heartbeat detection, heart rate detection, respiration detection, and respiratory rate detection. These biological functions can be monitored and detected over time. Context information acquisition applications include, for example, location detection, location tracking, orientation discovery, and range estimation. Automotive radar applications include, for example, intelligent cruise control (to maintain separation between a first vehicle and a second vehicle in front of the first vehicle and in the same lane (e.g., a driver-specified distance, a safe distance (e.g., a driver-specified or pre-programmed time interval)), collision prevention, etc.

[0107] Configuration 500 is an example of a multistatic radar. A shared transmitter and receiver (transceiver) is called a monostatic radar, while a transmitter not shared with a receiver is called a bistatic radar. Multistatic radars comprise multiple monostatic and / or bistatic radars with shared coverage areas and spatial diversity. In this example, transceiver 521 provides a monostatic radar where transmitted signal 531 is reflected as reflected signal 532 received by transceiver 521. Transmitters 522, 523 and receivers 524, 525 of transceiver 521 provide bistatic radar where transmitted signal 533 from transmitter 522 is reflected as reflected signals 534, 535 received by receivers 524, 525 respectively, while transmitted signal 536 from transmitter 523 is reflected as reflected signal 537 received by receiver 525. Other signals may be transmitted and other reflections may be received (e.g., by the receiver of transceiver 521), but for simplicity of the figures, ... Figure 5The signals are not shown in the figures. For example, transmitted signal 536 can be reflected and received by receiver 524, and / or signal 531 can be reflected and received by one or both of receivers 524 and 525, but for simplicity of the figures, these reflections are not shown. In addition to receiving reflected signals 534, 535, and 537, one or more of receivers 524 and 525 can directly receive transmitted signals 533 and 536 from transmitters 522 and 523, where transmitted signals 533 and 536 and reflected signals 534, 535, and 537 are used to determine RF sensing information (e.g., range to an object, object presence, channel characteristics, etc.). Transmitted signal 531 can also be directly received by one or more of receivers 524 and 525, and reflections of transmitted signal 531 are received by one or more of receivers 524 and 525, but for simplicity of the figures, these signal paths are not shown. Figure 5 Not shown in the image.

[0108] refer to Figure 6 And further refer to Figure 1-5 Application device 600 includes a processor 610, an interface 620, and a memory 630, which are communicatively coupled to each other via a bus 640. Application device 600 may include... Figure 6 The components shown may include one or more other components. For example, application device 600 may be a UE, a part of UE 200, a part of TRP 300, or a part of server 400, and therefore may include... Figure 2 , Figure 3 or Figure 4 The interface 620 may include one or more of the components shown. For example, processor 610 may include one or more of the components of processor 210. Interface 620 may include one or more of the components of transceiver 215, or transceiver 315, or transceiver 415. For example, interface 620 may include wireless transmitter 242 and antenna 246, or wireless receiver 244 and antenna 246, or wireless transmitter 242, wireless receiver 244, and antenna 246. Alternatively or alternatively, interface 620 may include wired transmitter 252 and / or wired receiver 254. Memory 630 may be configured similarly to memory 211, for example, including software having processor-readable instructions configured to cause processor 610 to perform functions.

[0109] The description herein may refer to processor 610 performing functions, but this includes other implementations, such as implementations of software and / or firmware (stored in memory 630) performed by processor 610. The description herein may refer to application device 600 performing functions as a shorthand for one or more appropriate components of application device 600 (e.g., processor 610 and memory 630) performing the function. Processor 610 (possibly in conjunction with memory 630 and, where appropriate, with interface 620) includes RF sensing unit 650 configured to request RF sensing for determining location information of a target object (e.g., one or more RF measurements, one or more ranges, one or more location estimates, etc.) and for receiving RF sensing reports regarding the RF sensing results. RF sensing unit 650 will be discussed further below, and this description may generally refer to processor 610 or generally application device 600 as performing any function of RF sensing unit 650, and application device 600 is configured to perform the function of RF sensing unit 650. Application device 600 is an application layer entity that can be directly or indirectly (e.g., via AMF 115) connected to SnMF (Sensing Management Function) to request RF sensing and receive RF sensing reports.

[0110] Also refer to Figure 7 The SnMF 700 includes a processor 710, an interface 720, and a memory 730, which are communicatively coupled to each other via a bus 740. The SnMF 700 may include... Figure 7 The components shown in the diagram may include one or more other components. For example, SnMF 700 may be part of server 400 and therefore may include... Figure 4 and / or Figure 3 One or more components are shown, or may be self-contained devices. For example, interface 720 may include one or more of the components of transceiver 415 (e.g., wireless transmitter 442 and antenna 446 and / or wireless receiver 444 and antenna 446 and / or wired transmitter 452 and / or wired receiver 454) and / or transceiver 315 (e.g., wireless transmitter 342 and antenna 346 and / or wireless receiver 344 and antenna 346 and / or wired transmitter 352 and / or wired receiver 354). Memory 730 may be configured similarly to memory 411 and / or memory 311, for example, including software having processor-readable instructions configured to cause processor 710 to perform functions. SnMF 700 and server 400 and / or TRP 300 may be integrated in a physical entity, wherein SnMF 700 and server 400 and / or TRP 300 share one or more components.

[0111] The description herein may refer to the processor 710 performing functions, but this includes other implementations, such as the processor 710 executing software and / or firmware (stored in memory 730). The description herein may refer to the SnMF 700 performing functions as a shorthand for one or more appropriate components of the SnMF 700 (e.g., processor 710 and memory 730) performing the function. The processor 710 (possibly in conjunction with memory 730 and, where appropriate, with interface 720) includes an RF sensing coordination unit 750. The RF sensing coordination unit 750 is configured to respond to RF sensing requests from application device 600 by scheduling RF sensing, collecting information from the RF sensing, and providing an RF sensing report with the results of the RF sensing (e.g., including location information of one or more target objects and / or one or more target environments). The RF sensing coordination unit 750 is further discussed below, and this description may generally refer to the processor 710 or SnMF 700 as performing any function of the RF sensing coordination unit 750, and SnMF 700 is configured to perform the function of the RF sensing coordination unit 750.

[0112] RF sensing can be requested by RF sensing unit 650 and coordinated by RF sensing coordination unit 750 for various purposes. For example, RF sensing unit 650 can request object presence detection to detect the presence of one or more target objects in a specified area. For object presence detection (or simply presence detection), RF sensing coordination unit 750 can select one or more relevant nodes for the area, such as one or more base stations (e.g., gNBs) and / or one or more UEs in or near the area (e.g., a room, an outdoor area, etc.), and determine whether the channel is time-varying (indicating the introduction, removal, and / or movement of one or more objects). As another example, RF sensing unit 650 can request health (e.g., biological function) detection (e.g., heart rate detection of a human or other biological entity) for one or more entities. For biological function detection, RF sensing coordination unit 750 can coordinate entity pairs (e.g., one or more base stations and / or one or more UEs) to obtain Doppler measurements of signals reflected from the target object. The Doppler measurements can be analyzed to determine biological functions such as heart rate, respiration, respiratory rate, etc. As another example, RF sensing unit 650 can request an environment map to measure one or more characteristics of the environment. For the environment map, RF sensing coordination unit 750 can coordinate measurements (e.g., via scheduling signaling and requesting measurements) of one or more characteristics (e.g., path loss, fading, interference, Doppler shift, etc.) of one or more RF channels by one or more entities (e.g., one or more base stations and / or one or more UEs). SnMF 700 can be configured to provide SLAM (Simultaneous Localization and Mapping) to determine an environment map and locate target objects within that map.

[0113] Also refer to Figure 8 Application device (AD) 600 and SnMF 700 are configured to cooperate with one or more transmitters 805 and one or more receivers 806 to provide RF sensing for determining the location information of target object / environment 807. Figure 8 The signaling and process flow 800 for RF sensing is shown. Flow 800 includes the stages shown and is an example, as stages can be added, rearranged, and / or removed.

[0114] In phase 810, AD 600 sends RF sensing request 812 to SnMF 700. RF sensing unit 650 is configured to generate RF sensing request 812 and generate RF sensing request 812 indicating the type of RF sensing requested, such as presence detection, bio-function detection, environment mapping, environment detection, etc. RF sensing request 812 may indicate the target object / environment 807 to be detected and / or the type of RF sensing to be performed. RF sensing request 812 may include auxiliary data that can assist SnMF 700 (and / or other entities) in RF sensing, location information determination, object tracking, object identification, etc. For example, the auxiliary data may provide information about the location of the target object / environment 807, and / or may provide an indication of the type of target object identified (e.g., a person, etc.), especially when RF sensing request 812 is provided in response to RF sensing report 852 (i.e., based on information provided in RF sensing report 852), which will be discussed further below. Additionally or alternatively, auxiliary data may include the identities of one or more of the transmitters 805 and / or receivers 806 to be used for RF sensing. AD 600 (e.g., RF sensing unit 650) may be configured to generate RF sensing request 812 including one or more parameters / criteria regarding the requested RF sensing. For example, RF sensing request 812 may include an indication of time constraints for RF sensing, such as the length of time the RF sensing will be performed, the future time of RF sensing termination, etc. As another example, RF sensing request 812 may include the frequency of RF sensing (how frequently RS sensing signaling is sent / measured) and / or the frequency of reporting RF sensing results (how frequently RS sensing results (e.g., measurements) are reported). As another example, the RF sensing request 812 may include one or more criteria for reporting the presence of target objects / environment 807, such as reporting any object new to the area, reporting any object leaving the area, reporting all objects in the area with non-zero Doppler measurements, or reporting any object in the area with at least a threshold Doppler measurement. These criteria are examples, and one or more other criteria may be used as an alternative to or supplement to one or more of the listed example criteria.

[0115] Also refer to Figure 9For an presence detection request, the RF sensing unit 650 can generate an RF sensing request 812 to identify an area of ​​floor 900 of building 910 as to be monitored to determine the presence (e.g., introduction, removal, and / or movement) of a target object / environment 807 and / or identify the target object / environment 807 to be detected. The AD 600 can be configured to identify the area in one or more ways, such as defining one or more parameters of the area's perimeter (e.g., coordinates of the vertices of the area, coordinates of the center of the area, and the shape of the area, coordinates of points on the perimeter, etc.), the identities of one or more base stations (e.g., one or more gNBs and / or one or more access points, etc.) to be used for RF sensing, etc. For example, an area definition could be an indication of floor 900, or an indication of room 920 within floor 900, or it could include the coordinates of each of the four corners 921, 922, 923, 924 of an area 925 to be monitored, or it could include an indication of base stations (e.g., access point 931 to be used by transmitter 805 and access points 932, 933 to be used by receiver 806). These area definitions are examples, and areas can be defined in other ways. RF sensing request 812 can identify any object from a variety of objects (e.g., a person, a group of people, inanimate objects (e.g., an automated guided vehicle (AGV), also known as an automated guided vehicle) etc.) as target objects / environments 807 to be detected (e.g., tracked). For example, RS sensing request 812 could provide an indication of a person 940, or an indication of a group of objects 951, 952, 953 being assembled along conveyor belt 950.

[0116] Also refer to Figure 10For an environment detection (e.g., mapping) request, the RF sensing unit 650 can be configured to generate an RF sensing request 812 to identify an area as a target object / environment 807 to be detected. The RF sensing request 812 can identify the area to be detected for its environment in a similar manner to identifying an area to be monitored for presence detection (e.g., specifying the perimeter of area 1010, specifying transmitter(s) 805 and receiver(s) 806 from base stations 1021, 1022, 1023 (where the area is a zone on which signals transmitted by transmitter(s) 805 can be reflected and received by receiver(s) 806), specifying geographical items such as street 1030, etc.). The RF sensing request 812 can indicate the channels(s) to be monitored and can indicate the characteristics of the channels(s) to be detected. For example, the RS sensing request 812 can indicate one or more inter-base station channels (e.g., one or more gNB inter-channels) and / or one or more UE-to-base station channels. (Various) channel characteristics may include, for example, path loss, fading, interference, and / or Doppler shift. RF sensing requests may include one or more criteria for (Various) characteristics, such as a corresponding minimum threshold before reporting the corresponding characteristic (e.g., path loss). While presence detection in Figure 9 The image is shown as an indoor scene and environmental detection is in Figure 10 The images are shown as being in an outdoor scene, but these are examples and not intended to limit this disclosure, as presence detection can be performed for an outdoor scene and environment detection can be performed for an indoor scene, or a combination thereof.

[0117] Also refer to Figure 11For a biometric detection request, RF sensing unit 650 can generate RF sensing request 812 to identify the transmitter(s) 805 and receiver(s) to be used, and / or to identify the entity(s) whose functions are to be detected. For example, RF sensing unit 650 may include the identities of a smartwatch 1110 as transmitter 805 (or one of transmitters 805) and a smartphone 1120 as receiver 806 (or one of receivers 806) for biometric detection of a person 1130 (as a target object / environment 807). Alternatively or additionally, RF sensing request 812 may include the identity of person 1130. Alternatively or additionally, RF sensing request 812 may, for example, identify base stations 1141 and 1142 as transmitter 805 and receiver 806, respectively. The use of smartwatch 1110 and smartphone 1120 (i.e., two UEs) in combination is an example and not intended to limit this disclosure. Similarly, the use of the two base stations 1141 and 1142 is exemplary and not intended to limit this disclosure. For example, for biometric detection, RF sensing request 812 may instruct one or more UEs and one or more base stations. RF sensing request 812 may include one or more parameters and / or one or more criteria for biometric detection. For example, RF sensing request 812 may include an indication of the Doppler rate to be detected (e.g., receiver 806 and / or SnMF 700). RF sensing request 812 may, for example, include a range of expected Doppler shifts (e.g., upper and lower limits). The expected Doppler shift may be auxiliary data that the entity detecting the Doppler shift can use to narrow the search for the Doppler shift. Additionally or alternatively, this range may be used as a reporting criterion such that heart rate is reported if the Doppler shift is within the indicated range, and not reported otherwise.

[0118] Refer again Figure 8 And continue to refer to Figure 1-7In steps 9-11, at stage 820, SnMF 700 determines the transmitters 805 and receivers 806 to be used for RF sensing and schedules the corresponding reference signaling. RF sensing coordination unit 750 can use the information in RF sensing request 812 to determine the transmitters 805 and receivers 806. For example, RF sensing coordination unit 750 can use the type of RF sensing to be performed (e.g., presence detection, environmental detection, bio-function detection, etc.), the indicated area, the indicated bio-function type, and / or the indicated transmitters and / or receivers to determine the physical signaling, transmitters 805, and receivers 806 expected or required to provide the requested RF sensing. The RF sensing coordination unit 750 can select physical signaling to achieve the desired sensing, such as covering the area of ​​its environment to be detected, covering the presence detection area, enabling the detection of the biometrics of the indicated object (e.g., a person), and / or including the indicated transmitter(s) and / or the indicated receiver(s) (if any). For example, UL probing for RF sensing used for environment mapping by the UE may be preferred. The RF sensing coordination unit 750 can send RS configuration messages 822, 824 to the transmitter(s) 805 and the receiver(s) 806, respectively. The RS configuration messages 822, 824 contain at least parameters of the RS to be sent by the transmitter(s) 805. RS configuration messages 822 and 824 can be sent as requests for RS signaling to the corresponding service TRP 300 of transmitters 805 and receivers 806, whereby TRP 300 sends configuration parameters to transmitters 805 and receivers 806. RS configuration messages 822 and 824 are thus functionally represented, wherein each of messages 822 and 824 may include multiple messages and be transmitted from SnMF 700 to transmitters 805 and receivers 806 via one or more intermediate entities.

[0119] In phase 830, transmitter 805 transmits a configured RS. Transmitter 805 is configured to respond to RS configuration message 822 by transmitting an appropriate RS 832. RS 832 is received directly by receiver 806 and reflected by the target object / environment, and reflected RS 834 is received by receiver 806. For example, access point 932 may transmit RS 972 reflected from item 951, and reflected RS 974 is received by access point 931, for example, to determine the presence of item 951 in area 925, determine the speed of item 951, etc. As another example, access point 933 may transmit RS 976 reflected from person 960 as reflected RS 978, which is received by access point 932 to determine RF sensing information about person 960 (e.g., presence, speed 962, location, etc.). As another example, RS 1040 can be transmitted by base station 1022 and reflected by vehicles 1041, 1042, person 1050, and buildings 1061, 1062, 1063, and the reflected RS can be received by base station 1021 and / or base station 1023. The reflected signal can be used to determine RS sensing information, such as the location and / or speed of vehicles 1041, 1042, and / or person 1050 (e.g., speed 1052 of person 1050), environmental characteristics (e.g., channel parameters, etc.). As another example, smartwatch 1110 can transmit RS 1112, which is reflected from person 1130, and the reflected RS 1114 is received by smartphone 1120 and used for RF sensing (e.g., heartbeat detection, heart rate determination, etc.). As another example, base station 1141 can transmit RS 1152, which is reflected from person 1130 as reflected RS 1154, which is received by base station 1142 so that reflected RS 1154 can be used for RF sensing (e.g., for breathing detection, breathing rate determination, etc.). Because the characteristics of the target object or environment reflect signals and therefore appear to transmit reflected signals, they can be referred to as virtual transmitters or virtual access points. Receiver 806 measures RS 834 from one or more virtual transmitters.

[0120] In phase 840, receiver 806 reports RF sensing results to SnMF 700 (directly and / or via the serving TRP) in an RF sensing result message 842. For example, receiver 806 may measure the ToA and / or AoA of RS 834, and the RF sensing result message 842 may include one or more measurements and / or information derived from one or more measurements (e.g., one or more distances, one or more location estimates, etc.). The RF sensing result message 842 may include one or more channel characteristics (e.g., path loss, fading, interference, Doppler, etc.). For example, for a UE receiver, receiver 806 may record and report all paths, path strength, path loss, fading, etc. The RF sensing result message 842 may include different characteristics of different objects (e.g., different Doppler) and / or different characteristics of the environment, such as different channels (e.g., different frequencies).

[0121] At stage 850, SnMF 700 can determine an RF sensing report 852 for the target object / environment 807 and send the RF sensing report 852 to AD600. SnMF 700 can collect RF sensing results from one or more RF sensing result messages 842 and perform one or more operations to determine the RF sensing report 852. The RF sensing report 852 may include one or more indications of: for example, the presence of a target object in the region of interest, a measure of biological function (e.g., heart rate, respiratory rate), the motion of the object, the number of objects detected, object types (e.g., human, group of people, other organisms, AGV, UAV, etc.), channel characteristics, position and / or angle relative to the object, confidence level of one or more corresponding indications, location of a virtual transmitter, location of corresponding entities, etc. For example, SnMF 700 may indicate the presence of object 951 in region 925 and / or the velocity of object 951 and / or the current presence of a single object in region 925. As another example, RF sensing report 852 may indicate the velocity 962 (speed and direction) of a person 960 (as target object / environment 807) in room 920 and identify the target object / environment 807 as a person. The indicated velocity may be a linear velocity (such as velocity 962), radial velocity, or angular velocity. SnMF 700 may determine location information and include that location information in RF sensing report 852. For example, RF sensing report 852 may include the location(s) of one or more target objects, one or more distances to one or more target objects, the direction(s) of one or more target objects relative to one or more reference points (e.g., base station locations), and / or the location(s) of one or more virtual access points (virtual transmitters corresponding to reflectors). As another example, RF sensing report 852 may include one or more location indications for one or more of one or more transmitters 805 and / or receivers 806. For example, if desired information (e.g., heart rate, location, etc.) is not obtained due to the location of transmitters 805 and / or receivers 806 (e.g., if transmitters 805 and receivers 806 are too far apart to obtain heart rate information with at least the desired accuracy), the transmitter and / or receiver locations can be reported. The RF sensing report 852 may include other information, such as an indication of whether the RF sensing was successful (i.e., a positive or negative result of the requested RF sensing), for example, whether the location of an object was detected within the requested threshold accuracy or whether the heart rate could be determined. The SnMF 700 (e.g., the RF sensing coordination unit 750) can use information from the RF sensing request 812 to influence the RF sensing report 852.For example, SnMF 700 can send RF sensing report 852 at the reporting frequency indicated by RF sensing request 812 and / or within the reporting duration indicated by RF sensing request 812.

[0122] At stage 860, AD 600 (e.g., RF sensing unit 650) can analyze RF sensing report 852 and determine location information based on RF sensing report 852. RF sensing unit 650 can process information from RF sensing report 852 to determine location information, such as one or more locations of objects, one or more distances, one or more object velocities, channel characteristics, etc. RF sensing unit 650 can be configured to determine other information, such as object presence, presence and / or metrics of biometrics, object separation (e.g., for automotive radar applications (such as intelligent cruise control and / or collision avoidance) and / or other applications (such as navigation)), etc. Additionally or alternatively, RF sensing unit 650 can analyze RF sensing report 852 for one or more reasons other than determining location information. For example, RF sensing unit 650 can compare RS sensing results in RF sensing report 852 with information obtained by RF sensing unit 650 through other means. The RF sensing unit 650 can, for example, compare indications of the location and / or type of an object with other information, such as one or more images acquired by a camera (e.g., camera 218), information input by a user (e.g., through user interface 216), etc. The RF sensing unit 650 can determine that the RF sensing result in the RF sensing report 852 is incorrect (e.g., based on inconsistencies between the RF sensing result and other information) and take appropriate action, such as discarding or ignoring the RF sensing result. For example, the RF sensing unit 650 can discard or ignore the object ID of a "person" based on analysis of an image of the object indicating that the object is not a person (e.g., an AGV). As another example, the RF sensing unit 650 can discard or ignore the location of an object based on user input indicating that the object is set at a location different from the location indicated in the RF sensing report 852. These are examples and not intended to limit this disclosure.

[0123] Process 800 can return to stage 810. AD 600 (e.g., RF sensing unit 650) can send a follow-up sensing request to SnMF 700; that is, RF sensing request 812 can be either the original sensing request or a follow-up sensing request. The follow-up sensing request can be based on RF sensing report 852. For example, RF sensing request 812 can request information different from previously requested information, such as the location of another object, tracking of another object, environmental sensing, tracking of fewer objects compared to all previously requested objects to be tracked, etc. As another example, RF sensing request 812 can include one or more indications confirming the accuracy of the information in RF sensing report 852 and / or one or more indications of inaccuracy of the information in RF sensing report 852 (e.g., contradicting indications in RF sensing report 852 regarding object location, object type, etc.). The SnMF 700 (e.g., the RF sensing coordination unit 750) can use information based on the RF sensing report 852 and / or other auxiliary data to adjust the signaling requested by (e.g., by RS configuration messages 822, 824) and / or one or more algorithms used to determine the RF sensing report 852 (e.g., identifying object type, determining location, etc.). The RF sensing coordination unit 750 may employ machine learning (e.g., neural networks) to adjust the signaling and / or algorithms. The auxiliary data may include the auxiliary data and / or other data discussed above, such as data based on information from one or more other sources (e.g., one or more of the sensors 213). The process 800 may be repeated multiple times so that information from the RF sensing report 852 and / or information derived therefrom can be provided as feedback in the RF sensing request 812, which can lead to iterative improvement of the information in the RF sensing report 852 and thereby increase the confidence of the results.

[0124] Reference Figure 12 And further refer to Figure 1-11 The RF sensing method 1200 includes the stages shown. However, method 1200 is an example and not a limitation. Method 1200 can be modified, for example, by adding, removing, rearranging, combining, executing concurrently, and / or splitting a single stage into multiple stages.

[0125] In phase 1210, method 1200 includes: generating an RF sensing request at an application device, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing. For example, the RF sensing unit 650 of application device 600 may generate a request for RF sensing (e.g., RF sensing request 812) using user input, a request from an application that desires (or even needs) RF sensing information, input from one or more sensors, information from an RF sensing report (e.g., RF sensing report 852), and / or other information. The request includes a request for a network entity (e.g., SnMF 700) to coordinate RF sensing of a region and / or object, and specifies one or more criteria for the RF sensing. The request for the area and / or the object can be direct (e.g., defining the area or identifying the object), or it can be indirect or implicit (e.g., identifying one or more transmitters 805 and one or more receivers 806). The area can be designated for various types of RF sensing, such as object presence detection or environmental detection. The RF sensing request 812 may include, for example, auxiliary data that can assist SnMF 700 (and / or other entities) in RF sensing, location information determination, object tracking, object identification, etc. The processor 610 (possibly in conjunction with memory 630) may include means for generating the RF sensing request.

[0126] In stage 1220, method 1200 includes sending the RF sensing request from the application device to the network entity. For example, AD 600 sends RF sensing request 812 to SnMF 700. Processor 610 (possibly combined with memory 630) and interface 620 (e.g., wireless receiver 244 and antenna 246, or wired transmitter 252 or other devices) may include means for sending the RF sensing request to the network entity.

[0127] At stage 1230, method 1200 includes receiving an RF sensing report at the application device from the network entity indicating the result of the RF sensing. For example, AD 600 receives RF sensing report 852 from SnMF 700 (e.g., RF sensing coordination unit 750). Processor 610 (possibly in conjunction with memory 630, possibly in conjunction with interface 620 (e.g., wireless receiver 244 and antenna 246, or wired receiver 254 or another device)) may include means for receiving the RF sensing report.

[0128] Implementations of method 1200 may include one or more of the following features. In one example implementation, the at least one criterion includes an indication of the type of RF sensing. In a further example implementation, the type of RF sensing includes one of the following: object presence detection, environmental detection, or biological function detection. In another example implementation, the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and the at least one criterion includes defining multiple coordinates of the area. In another example implementation, the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and the request is for object presence detection in the area. For example, RF sensing request 812 may request object presence detection for a specified area (such as area 925). In a further example implementation, the at least one criterion includes a threshold Doppler phase shift for the object presence to be reported.

[0129] Additionally or alternatively, implementations of method 1200 may include one or more of the following features. In one example implementation, the RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological function. In a further example implementation, the at least one biological function includes at least one of heartbeat or respiration, and the at least one criterion includes a first identity of the RF transmitter to be used for the RF sensing and a second identity of the RF receiver. For example, RF sensing request 812 may request the detection of the presence of a heartbeat, the presence of a subject's respiration, heart rate, and / or respiratory rate. In another further example implementation, the at least one criterion includes Doppler rate. In a further example implementation, the at least one criterion includes a range of Doppler rates. The RF sensing request may indicate a Doppler phase shift value (e.g., a minimum value) and / or a range of Doppler phase shifts for RF sensing (e.g., for heartbeat reporting, respiration reporting, and / or object presence reporting).

[0130] Additionally or alternatively, implementations of method 1200 may include one or more of the following features. In one example implementation, the at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides RF sensing reports indicating the results of the RF sensing. The RF sensing request 812 may, for example, indicate how long the requested RF sensing should be performed, how frequently reference signals should be transmitted and measured, and / or how frequently RF sensing results should be reported. In another example implementation, the at least one criterion includes an indication of the expected result of the RF sensing. For example, the RF sensing request 812 may indicate the expected object type, the expected object location, and / or one or more expected channel characteristics, etc. The expected result may be based on user input, sensor input (e.g., one or more images captured by a camera), etc. The expected result may be used to ignore erroneous information to improve the accuracy of the reported RF sensing results. In another example implementation, method 1200 includes: at the application device, receiving input about the subject of the RF sensing from at least one information source other than the network entity; and sending a response from the application device to the network entity to the RF sensing report, the response including the input about the subject of the RF sensing. For example, RF sensing unit 650 may receive input about RF sensing results (e.g., user input and / or sensor input) and send feedback to SnMF 700 based on the input, for example, to confirm, refute, or revise the RF sensing results (e.g., to reject or correct the object type indicated in RF sensing report 852, to reject or correct the object location specified in RF sensing report 852). SnMF 700 may use the input to update one or more algorithms and / or update coordinated reference signaling (e.g., one or more selected transmitters and / or one or more selected receivers) for future RF sensing to improve the accuracy of the reported RF sensing results. In another example implementation, the RF sensing request is a first RF sensing request, and method 1200 further includes sending a second RF sensing request based on the first RF sensing request from the application device to the network entity. For example, processor 610 may receive RF sensing report 852 at stage 850, analyze RF sensing report 852 at stage 860, determine a new request based on RF sensing report 852 as discussed above, and return to stage 810 to send the new request to SnMF 700. This can help iteratively improve the request and thus improve the resulting RF sensing and / or response actions (e.g., movement avoidance, route change, etc.).

[0131] Alternatively or concurrently, implementations of method 1200 may include one or more of the following features. In an example implementation, method 1200 may include: receiving the RF sensing request at the network entity; scheduling the transmission of at least one reference signal from at least one RF transmitter; receiving RF sensing results from at least one receiver of at least one reflected reference signal; generating an RF sensing report; and sending the RF sensing report from the network entity to the RF sensing requesting device. For example, RF sensing coordination unit 750 may receive the RF sensing request, schedule RS transmissions for RF sensing (e.g., sending RS configuration messages 822, 824), receive sensing results (e.g., RF sensing results from receiver 806), generate an RF sensing report 852 including one or more RF sensing results (possibly including location information), and send the RF sensing report, for example, to the entity requesting RF sensing (e.g., AD 600). Processor 710 (possibly in conjunction with memory 730 and possibly with interface 720 (e.g., a wireless receiver, wireless transmitter, wired receiver, and / or wired transmitter)) may include means for receiving the RF sensing request, scheduling RS transmissions, receiving RF sensing results, generating an RF sensing report, and transmitting the RF sensing report. In another example implementation, the RF sensing results include indications of at least one of the following: object location, object type, channel characteristics, or object presence. For example, RF sensing report 852 may indicate one or more locations of one or more objects, one or more object types of one or more corresponding objects, one or more channel characteristics, and / or the presence (or absence) of one or more objects in one or more corresponding areas.

[0132] Reference Figure 13 And further refer to Figure 1-11 The radio frequency sensing coordination method 1300 includes the stages shown. However, method 1300 is an example and not a limitation. Method 1300 can be modified, for example, by adding, removing, rearranging, combining, concurrently executing, and / or splitting a single stage into multiple stages.

[0133] In stage 1310, method 1300 includes: receiving a radio frequency (RF) sensing request from an application device at a network entity, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of an area or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the area, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing. For example, SnMF 700 receives an RF sensing request 812 from application device 600 in stage 810 of process 800. Processor 710 (possibly in combination with memory 730, possibly in combination with interface 720 (e.g., wireless receiver 444 and antenna 446 and / or wired receiver 454 and / or wireless receiver 344 and antenna 346 and / or wired receiver 354)) may include means for receiving the RF sensing request.

[0134] At stage 1320, method 1300 includes determining a first radio frequency (RF) configuration and a second RF configuration at the network entity based on the RF sensing request. For example, SnMF 700 determines the RS configuration at stage 820, as discussed above. Processor 710 (possibly in conjunction with memory 730 and possibly with interface 720) may include means for determining the first RF configuration and the second RF configuration.

[0135] At stage 1330, method 1300 includes transmitting the first radio frequency configuration from the network entity to a radio frequency transmitter and transmitting the second radio frequency configuration to a radio frequency receiver. For example, SnMF 700 transmits RS configuration messages 822 and 824 to transmitter 805 and receiver 806, respectively. SnMF 700 may determine RS configurations for one or more transmitters and one or more receivers and appropriately transmit these RS configurations to the transmitters and receivers. Processor 710 (possibly in conjunction with memory 730 and possibly with interface 720 (e.g., wireless transmitter 442 and antenna 446 and / or wired transmitter 452 and / or wireless transmitter 342 and antenna 346 and / or wired transmitter 352)) may include means for transmitting the first reference signal configuration message and the second reference signal configuration.

[0136] Implementations of method 1300 may include one or more of the following features. In one example implementation, determining the first radio frequency configuration and the second radio frequency configuration is further based on desired radio frequency sensing to be implemented by the radio frequency transmitter and the radio frequency receiver. In a further example implementation, the desired radio frequency sensing includes detection of the environment in the area, presence detection in the area, biological function detection of the object, or any combination thereof.

[0137] Additionally or alternatively, implementations of method 1300 may include one or more of the following features. In an example implementation, method 1300 further includes: receiving, at the network entity, an RF result message indicating one or more results of RF sensing performed by the RF receiver from the RF receiver; determining an RF sensing report at the network entity based on the RF result message; and transmitting the RF sensing report from the network entity to the application device. For example, SnMF receives an RS sensing result message 842 from receiver 806, uses the information in the RS sensing result message 842 to determine an RF sensing report 852, and sends the RF sensing report 852 to application device 600. Processor 710 (possibly in conjunction with memory 730, possibly in conjunction with interface 720 (e.g., wireless receiver 444 and antenna 446 and / or wired receiver 454 and / or wireless receiver 344 and antenna 346 and / or wired receiver 354)) may include means for receiving the RF sensing result message. Processor 710 (possibly in conjunction with memory 730 and possibly with interface 720) may include means for determining the radio frequency (RF) sensing report. Processor 710 (possibly in conjunction with memory 730 and possibly with interface 720 (e.g., wireless transmitter 442 and antenna 446 and / or wired transmitter 452 and / or wireless transmitter 342 and antenna 346 and / or wired transmitter 352)) may include means for transmitting the RF sensing report. In a further example implementation, the RF sensing report indicates the presence of the target object in the region of interest, a measure of biometrics, the movement of the target object, the number of detected objects, the location of the target object, or any combination thereof.

[0138] Implementation Example

[0139] Examples of each implementation are provided in the following numbered clauses.

[0140] Clause 1: A radio frequency (RF) sensing request device, comprising:

[0141] interface;

[0142] Memory; and

[0143] One or more processors, which are communicatively coupled to the interface and the memory and are configured to:

[0144] The interface sends an RF sensing request to a network entity, the RF sensing request including a request for RF sensing of at least one of the network entity's coordinated areas or objects, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the area, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing; and

[0145] Receive an RF sensing report indicating the result of the RF sensing from the network entity via this interface.

[0146] Clause 2: An RF sensing request device as described in Clause 1, wherein the at least one criterion includes an indication of the type of RF sensing.

[0147] Clause 3: RF sensing request device as in Clause 2, wherein the type of RF sensing includes one of the following: object presence detection, environmental detection, or biological function detection.

[0148] Clause 4: An RF sensing request device as described in Clause 1, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and wherein the at least one criterion includes multiple coordinates defining the area.

[0149] Clause 5: An RF sensing request device as described in Clause 1, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, the request being for the detection of the presence of objects in the area.

[0150] Clause 6: An RF sensing request device as described in Clause 5, wherein the at least one criterion includes a threshold Doppler phase shift for the presence of an object to be reported.

[0151] Clause 7: An RF sensing request device as described in Clause 1, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological function.

[0152] Clause 8: An RF sensing request device as described in Clause 7, wherein the at least one biological function includes at least one of heartbeat or breathing, and wherein the at least one criterion includes a first identity of the RF transmitter to be used for the RF sensing and a second identity of the RF receiver.

[0153] Clause 9: RF sensing request device as in Clause 7, wherein the at least one criterion includes Doppler rate.

[0154] Clause 10: RF sensing request device as in Clause 9, wherein the at least one criterion includes a range of Doppler rates.

[0155] Clause 11: An RF sensing request device as described in Clause 1, wherein the at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

[0156] Clause 12: An RF sensing request device as described in Clause 1, wherein the at least one criterion includes an indication of the expected outcome of the RF sensing.

[0157] Clause 13: An RF sensing request device as described in Clause 1, wherein the one or more processors are configured to:

[0158] Receive input about the RF-sensing subject from at least one information source other than the network entity; and

[0159] Send a response to the RF sensing report to the network entity, the response including input about the subject of the RF sensing.

[0160] Clause 14: An RF sensing request device as described in Clause 1, wherein the RF sensing request is a first RF sensing request, and wherein the one or more processors are configured to send a second RF sensing request based on the first RF sensing request to the network entity via the interface.

[0161] Clause 15: A radio frequency (RF) sensing method, comprising:

[0162] An RF sensing request is generated at the application device. The RF sensing request includes a request for a network entity to coordinate RF sensing of at least one of the areas or objects. The RF sensing request includes at least one criterion for the RF sensing, which includes at least one of the following: an indication of the area, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing.

[0163] The application device sends the RF sensing request to the network entity; and

[0164] The application device receives an RF sensing report from the network entity indicating the result of the RF sensing.

[0165] Clause 16: The method of Clause 15, wherein the at least one criterion includes an indication of the type of RF sensing.

[0166] Clause 17: The method of Clause 16, wherein the type of RF sensing includes one of the following: object presence detection, environmental detection, or biological function detection.

[0167] Clause 18: The method of Clause 15, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and wherein the at least one criterion includes multiple coordinates defining the area.

[0168] Clause 19: The method of Clause 15, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area for the detection of the presence of objects in the area.

[0169] Clause 20: The method of Clause 19, wherein the at least one criterion includes a threshold Doppler phase shift for the presence of the object to be reported.

[0170] Clause 21: The method of Clause 15, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological function.

[0171] Clause 22: The method of Clause 21, wherein the at least one biological function includes at least one of heartbeat or breathing, and the at least one criterion includes a first identity of the RF transmitter to be used for the RF sensing and a second identity of the RF receiver.

[0172] Clause 23: The method of Clause 21, wherein the at least one criterion includes the Doppler rate.

[0173] Clause 24: The method of Clause 23, wherein the at least one criterion includes a range of Doppler rates.

[0174] Clause 25: The method of Clause 15, wherein the at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

[0175] Clause 26: The method of Clause 15, wherein the at least one criterion includes an indication of the expected result of the RF sensing.

[0176] Clause 27: The method as described in Clause 15 further includes:

[0177] The application device receives input about the RF-sensing subject from at least one information source other than the network entity; and

[0178] The application device sends a response to the network entity regarding the RF sensing report, which includes input about the subject of the RF sensing.

[0179] Clause 28: The method of Clause 15, wherein the RF sensing request is a first RF sensing request, and the method further includes sending a second RF sensing request based on the first RF sensing request from the application device to the network entity.

[0180] Clause 29: A radio frequency (RF) sensing request device, comprising:

[0181] A means for generating an RF sensing request, the RF sensing request including a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing;

[0182] A means for sending the RF sensing request to the network entity; and

[0183] A means for receiving an RF sensing report from the network entity that indicates the result of the RF sensing.

[0184] Clause 30: RF sensing request device as in Clause 29, wherein the at least one criterion includes an indication of the type of RF sensing.

[0185] Clause 31: An RF sensing request device as described in Clause 30, wherein the type of RF sensing includes one of the following: object presence detection, environmental detection, or biological function detection.

[0186] Clause 32: An RF sensing request device as described in Clause 29, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and wherein the at least one criterion includes multiple coordinates defining the area.

[0187] Clause 33: An RF sensing request device as described in Clause 29, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area for the detection of the presence of objects in the area.

[0188] Clause 34: An RF sensing request device as described in Clause 33, wherein the at least one criterion includes a threshold Doppler phase shift for the presence of an object to be reported.

[0189] Clause 35: An RF sensing request device as described in Clause 29, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological function.

[0190] Clause 36: An RF sensing request device as described in Clause 35, wherein the at least one biological function includes at least one of heartbeat or breathing, and the at least one criterion includes a first identity of the RF transmitter to be used for the RF sensing and a second identity of the RF receiver.

[0191] Clause 37: RF sensing request device as in Clause 35, wherein the at least one criterion includes Doppler rate.

[0192] Clause 38: RF sensing request device as in Clause 37, wherein the at least one criterion includes a range of Doppler rates.

[0193] Clause 39: An RF sensing request device as in Clause 29, wherein the at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

[0194] Clause 40: An RF sensing request device as described in Clause 29, wherein the at least one criterion includes an indication of the expected outcome of the RF sensing.

[0195] Clause 41: The RF sensing request device as described in Clause 29 further includes:

[0196] A means for receiving input about the RF-sensing subject from at least one information source other than the network entity; and

[0197] A means for sending a response to the RF sensing report to the network entity, the response including input about the subject of the RF sensing.

[0198] Clause 42: An RF sensing request device as described in Clause 29, wherein the RF sensing request is a first RF sensing request, and the RF sensing request device further includes means for sending a second RF sensing request based on the first RF sensing request to the network entity.

[0199] Clause 43: A non-transient processor-readable storage medium comprising processor-readable instructions that cause one or more processors of a radio frequency (RF) sensing request device to perform actions to facilitate the location of a user equipment:

[0200] An RF sensing request is generated, which includes a request for a network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of the following: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing;

[0201] Send the RF sensing request to the network entity; and

[0202] Receive an RF sensing report from the network entity indicating the result of the RF sensing.

[0203] Clause 44: A non-transient processor-readable storage medium as described in Clause 43, wherein the at least one criterion includes an indication of the type of RF sensing.

[0204] Clause 45: A non-transient processor-readable storage medium as described in Clause 44, wherein the type of RF sensing includes one of the following: object presence detection, environmental detection, or biological function detection.

[0205] Clause 46: A non-transient processor-readable storage medium as described in Clause 43, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and wherein the at least one criterion includes multiple coordinates defining the area.

[0206] Clause 47: A non-transient processor-readable storage medium as described in Clause 43, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of the area for the detection of the presence of an object in the area.

[0207] Clause 48: A non-transient processor-readable storage medium as described in Clause 47, wherein the at least one criterion includes a threshold Doppler phase shift for the presence of an object to be reported.

[0208] Clause 49: A non-transient processor-readable storage medium as described in Clause 43, wherein the RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological function.

[0209] Clause 50: A non-transient processor-readable storage medium as described in Clause 49, wherein the at least one biological function includes at least one of heartbeat or respiration, and the at least one criterion includes a first identity of the RF transmitter to be used for the RF sensing and a second identity of the RF receiver.

[0210] Clause 51: A non-transient processor-readable storage medium as described in Clause 49, wherein the at least one criterion includes the Doppler rate.

[0211] Clause 52: A non-transient processor-readable storage medium as described in Clause 51, wherein the at least one criterion includes a range of Doppler rates.

[0212] Clause 53: A non-transient processor-readable storage medium as described in Clause 43, wherein the at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

[0213] Clause 54: A non-transient processor-readable storage medium as described in Clause 43, wherein the at least one criterion includes an indication of the expected outcome of the RF sensing.

[0214] Clause 55: A non-transient processor-readable storage medium as described in Clause 43 further includes processor-readable instructions that cause the one or more processors to perform the following operations:

[0215] Receive input about the RF-sensing subject from at least one information source other than the network entity; and

[0216] Send a response to the RF sensing report to the network entity, the response including input about the subject of the RF sensing.

[0217] Clause 56: A non-transient processor-readable storage medium as described in Clause 43, wherein the RF sensing request is a first RF sensing request, and the non-transient processor-readable storage medium further includes processor-readable instructions that cause the one or more processors to perform the following operation: send a second RF sensing request to the network entity based on the first RF sensing request.

[0218] Clause 57: A network entity comprising:

[0219] interface;

[0220] Memory; and

[0221] One or more processors, which are communicatively coupled to the interface and the memory and are configured to:

[0222] The network entity receives a radio frequency (RF) sensing request from the application device via the interface. The RF sensing request includes a request for the network entity to coordinate RF sensing of at least one of the areas or objects. The RF sensing request includes at least one criterion for the RF sensing, which includes at least one of the following: an indication of the area, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing.

[0223] Based on the radio frequency sensing request, a first radio frequency configuration and a second radio frequency configuration are determined; and

[0224] The first radio frequency configuration is transmitted to the radio frequency transmitter via this interface, and the second radio frequency configuration is transmitted to the radio frequency receiver.

[0225] Clause 58: A network entity as described in Clause 57, wherein the one or more processors are further configured to determine the first radio frequency configuration and the second radio frequency configuration based on desired radio frequency sensing to be implemented by the radio frequency transmitter and the radio frequency receiver.

[0226] Clause 59: A network entity as described in Clause 58, wherein the desired radio frequency sensing includes detection of the environment in the area, detection of presence in the area, detection of the biological function of the object, or any combination thereof.

[0227] Clause 60: A network entity as described in Clause 57, wherein the one or more processors are further configured to:

[0228] Receive, via this interface, an RF result message indicating one or more results of RF sensing performed by the RF receiver;

[0229] Based on this RF result message, an RF sensing report is determined; and

[0230] The radio frequency sensing report is transmitted to the application device via this interface.

[0231] Clause 61: A network entity as described in Clause 60, wherein the radio frequency sensing report indicates the presence of the target object in the region of interest, a measure of biological function, the movement of the target object, the number of objects detected, the location of the target object, or any combination thereof.

[0232] Clause 62: A radio frequency sensing coordination method, comprising:

[0233] At the network entity, a radio frequency (RF) sensing request is received from an application device. The RF sensing request includes a request for the network entity to coordinate RF sensing of at least one of a region or an object. The RF sensing request includes at least one criterion for the RF sensing, which includes at least one of the following: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing.

[0234] At the network entity, a first radio frequency configuration and a second radio frequency configuration are determined based on the radio frequency sensing request; and

[0235] The network entity transmits the first radio frequency configuration to the radio frequency transmitter and the second radio frequency configuration to the radio frequency receiver.

[0236] Clause 63: The radio frequency sensing coordination method of Clause 62, wherein the determination of the first radio frequency configuration and the second radio frequency configuration is further based on the desired radio frequency sensing to be implemented by the radio frequency transmitter and the radio frequency receiver.

[0237] Clause 64: The radio frequency sensing coordination method as described in Clause 63, wherein the desired radio frequency sensing includes detection of the environment of the area, detection of presence in the area, detection of the biological function of the object, or any combination thereof.

[0238] Clause 65: The radio frequency sensing coordination method as described in Clause 62 further includes:

[0239] At the network entity, an RF result message indicating one or more results of RF sensing performed by the RF receiver is received from the RF receiver;

[0240] At the network entity, an RF sensing report is determined based on the RF result message; and

[0241] The radio frequency sensing report is transmitted from the network entity to the application device.

[0242] Clause 66: The radio frequency sensing coordination method as described in Clause 65, wherein the radio frequency sensing report indicates the presence of the target object in the region of interest, a measure of biological function, the movement of the target object, the number of detected objects, the location of the target object, or any combination thereof.

[0243] Clause 67: A network entity comprising:

[0244] A means for receiving a radio frequency (RF) sensing request from an application device, the RF sensing request including a request for the network entity to coordinate RF sensing of at least one of a region or an object, wherein the RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including at least one of: an indication of the region, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing;

[0245] A means for determining a first radio frequency configuration and a second radio frequency configuration based on the radio frequency sensing request; and

[0246] A means for transmitting the first radio frequency configuration to a radio frequency transmitter and the second radio frequency configuration to a radio frequency receiver.

[0247] Clause 68: A network entity as described in Clause 67, wherein the means for determining the first radio frequency configuration and the second radio frequency configuration includes means for further determining the first radio frequency configuration and the second radio frequency configuration based on desired radio frequency sensing to be implemented by the radio frequency transmitter and the radio frequency receiver.

[0248] Clause 69: A network entity as described in Clause 68, wherein the desired radio frequency sensing includes detection of the environment in the area, detection of presence in the area, detection of the biological function of the object, or any combination thereof.

[0249] Clause 70: As in Clause 67, network entities further include:

[0250] A means for receiving from the radio frequency receiver a radio frequency result message indicating one or more results of radio frequency sensing performed by the radio frequency receiver;

[0251] A means for determining an RF sensing report based on the RF result message; and

[0252] A device for transmitting the radio frequency sensing report to the application device.

[0253] Clause 71: A network entity as described in Clause 70, wherein the radio frequency sensing report indicates the presence of the target object in the region of interest, a measure of biological function, the movement of the target object, the number of objects detected, the location of the target object, or any combination thereof.

[0254] Clause 72: A non-transient processor-readable storage medium comprising processor-readable instructions that cause one or more processors of a network entity to perform the following operations:

[0255] The application device receives a radio frequency (RF) sensing request, which includes a request for the network entity to coordinate RF sensing of at least one of the areas or objects, wherein the RF sensing request includes at least one criterion for the RF sensing, which includes at least one of the following: an indication of the area, the identity of at least one RF sensing device, or the identity of the target object of the RF sensing.

[0256] Based on the radio frequency sensing request, a first radio frequency configuration and a second radio frequency configuration are determined; and

[0257] The first radio frequency configuration is transmitted to the radio frequency transmitter and the second radio frequency configuration is transmitted to the radio frequency receiver.

[0258] Clause 73: A non-transient processor-readable storage medium as described in Clause 72, wherein processor-readable instructions for causing the one or more processors to determine the first radio frequency configuration and the second radio frequency configuration include processor-readable instructions causing the one or more processors to perform the following: further determine the first radio frequency configuration and the second radio frequency configuration based on desired radio frequency sensing to be implemented by the radio frequency transmitter and the radio frequency receiver.

[0259] Clause 74: A non-transient processor-readable storage medium as described in Clause 73, wherein the desired radio frequency sensing includes detection of the environment in the area, detection of presence in the area, detection of the biological function of the object, or any combination thereof.

[0260] Clause 75: A non-transient processor-readable storage medium as described in Clause 72 further includes processor-readable instructions that cause the one or more processors to perform the following operations:

[0261] Receive from the radio frequency receiver a radio frequency result message indicating one or more results of radio frequency sensing performed by the radio frequency receiver;

[0262] Based on this RF result message, an RF sensing report is determined; and

[0263] The radio frequency sensing report is transmitted to the application device.

[0264] Clause 76: A non-transient processor-readable storage medium as described in Clause 75, wherein the radio frequency sensing report indicates the presence of the target object in the region of interest, a measure of biological function, the motion of the target object, the number of detected objects, the location of the target object, or any combination thereof.

[0265] Other considerations

[0266] Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software and computers, the above-described functions can be implemented using software, hardware, firmware, hardwired, or any combination thereof executed by a processor. Features implementing the functions can also be physically located in various positions, including being distributed such that different parts of the function are implemented at different physical locations.

[0267] As used herein, the singular forms of “a,” “some,” and “the” also include the plural forms, unless the context clearly indicates otherwise. As used herein, the terms “comprising,” “having,” “including,” and / or “containing” indicate the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0268] Similarly, as used herein, the "or" (possibly followed by "at least one of" or "one or more of") used in item enumeration indicates a disjunctive enumeration such that an enumeration of, for example, "at least one of A, B, or C," or an enumeration of "one or more of A, B, or C," or an enumeration of "A or B or C" represents A or B or C or AB (A and B) or AC (A and C) or BC (B and C) or ABC (i.e., A and B and C), or a combination having more than one feature (e.g., AA, AAB, ABBC, etc.). Therefore, an item (e.g., a processor) being configured to perform a function with respect to at least one of A or B, or an item being configured to perform a function A or function B, means that the item can be configured to perform a function with respect to A, or can be configured to perform a function with respect to B, or can be configured to perform a function with respect to both A and B. For example, the phrase "the processor is configured to measure at least one of A or B" or "the processor is configured to measure A or measure B" means that the processor can be configured to measure A (and may or may not be configured to measure B), or can be configured to measure B (and may or may not be configured to measure A), or can be configured to measure both A and B (and may be configured to select which or both of A and B to measure). Similarly, a description of means for measuring at least one of A or B includes: means for measuring A (which may or may not measure B), or means for measuring B (and may or may not be configured to measure A), or means for measuring A and B (which may be able to select which or both of A and B to measure). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y indicates that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both function X and function Y. For example, the phrase processor being configured to measure "at least one of X or Y" means that the processor can be configured to measure X (and may or may not be configured to measure Y), or can be configured to measure Y (and may or may not be configured to measure X), or can be configured to measure both X and Y (and can be configured to select which or both of X and Y to measure).

[0269] As used herein, unless otherwise stated, a description of a function or operation “based on” an item or condition means that the function or operation is based on the described item or condition and may be based on one or more items and / or conditions other than the described item or condition.

[0270] Substantial modifications can be made to suit specific requirements. For example, custom hardware can be used, and / or specific elements can be implemented in the hardware, in processor-executed software (including portable software such as applets), or both. Furthermore, connections to other computing devices (such as network input / output devices) can be employed. Unless otherwise stated, the interconnected or communicating components (functionally or otherwise) shown in the figures and / or discussed herein are communicatively coupled. That is, they can be directly or indirectly connected to enable communication between them.

[0271] The systems and devices discussed above are examples. Various configurations may appropriately omit, substitute, or add various procedures or components. For example, features described with reference to certain configurations may be combined in various other configurations. Different aspects and elements of a configuration may be combined in a similar manner. Furthermore, technology evolves, and thus many elements are examples and do not limit the scope of this disclosure or the claims.

[0272] A wireless communication system is a system in which communication is transmitted wirelessly, that is, through the atmospheric space via electromagnetic waves and / or sound waves rather than through wires or other physical connections. A wireless communication network may not necessarily transmit all communications wirelessly, but may be configured to transmit at least some communications wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require that the device's functionality be exclusively or uniformly primarily used for communication, or that the device is a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio (each radio being part of a transmitter, receiver, or transceiver) for wireless communication.

[0273] Specific details are provided in this specification to provide a thorough understanding of the example configurations (including implementations). However, these configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. This specification provides example configurations without limiting the scope, applicability, or configuration of the claims. Rather, the preceding description of the configurations provides a description for implementing the techniques. Various changes can be made to the function and arrangement of the elements.

[0274] As used herein, the terms “processor-readable medium,” “machine-readable medium,” and “computer-readable medium” refer to any medium that participates in providing data that enables a machine to operate in a particular manner. Using a computing platform, various processor-readable media may involve providing instructions / code to (such as) processors for execution, and / or being used to store and / or carry such instructions / code (e.g., as signals). In many implementations, processor-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media include, for example, optical discs and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0275] Having described several example configurations, various modifications, substitutions, constructs, and equivalents can be used. For example, the above elements can be components of a larger system, where other rules may take precedence over the application of this disclosure or otherwise modify the application of the invention. Furthermore, several operations may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the claims.

[0276] A statement whose value exceeds (or is greater than or higher than) a first threshold is equivalent to a statement whose value meets or exceeds a second threshold slightly greater than the first threshold. For example, in the resolution of the computing system, the second threshold is one value higher than the first threshold. A statement whose value is less than the first threshold (or within or below the first threshold) is equivalent to a statement whose value is less than or equal to a second threshold slightly lower than the first threshold. For example, in the resolution of the computing system, the second threshold is one value lower than the first threshold.

Claims

1. A radio frequency (RF) sensing request device for biological function detection, the RF sensing request device comprising: interface; Memory; as well as One or more processors, which are communicatively coupled to the interface and the memory and configured to: An RF sensing request is sent to a network entity via the interface. The RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological entity. The RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including: Doppler rate, a first identity of the RF transmitter and a second identity of the RF receiver to be used for the RF sensing, and the identity of the at least one biological entity. The RF sensing request includes a request for the network entity to coordinate RF sensing of the RF transmitter and the RF receiver for at least one biological function. The RF sensing request includes an indication that the Doppler rate is to be detected for sensing the at least one biological function, and the at least one biological function includes at least one of heartbeat or respiration. as well as Receive an RF sensing report indicating the result of the RF sensing from the network entity via the interface.

2. The radio frequency (RF) sensing request device as described in claim 1, wherein, The RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and the at least one criterion includes defining multiple coordinates of the area.

3. The radio frequency (RF) sensing request device as described in claim 1, wherein, The RF sensing request includes a request for the network entity to coordinate RF sensing of a region, the request being for the detection of the presence of objects in the region.

4. The radio frequency (RF) sensing request device as described in claim 1, wherein, The at least one criterion includes a threshold Doppler phase shift for the existence of the object to be reported.

5. The radio frequency (RF) sensing request device as described in claim 1, wherein, The at least one criterion includes the range of Doppler rates.

6. The radio frequency (RF) sensing request device as claimed in claim 1, wherein, The at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

7. The radio frequency (RF) sensing request device as claimed in claim 1, wherein, The at least one criterion includes an indication of the expected outcome of the RF sensing.

8. The radio frequency (RF) sensing request device as claimed in claim 1, wherein, The one or more processors are configured to: Receive input about the RF-sensing subject from at least one information source other than the network entity; as well as Send a response to the RF sensing report to the network entity, the response including the input regarding the subject of the RF sensing.

9. The radio frequency (RF) sensing request device as claimed in claim 1, wherein, The RF sensing request is a first RF sensing request, and wherein one or more processors are configured to send a second RF sensing request based on the first RF sensing request to the network entity via the interface.

10. A radio frequency (RF) sensing method for detecting biological functions, the method comprising: An RF sensing request is generated at the application device. The RF sensing request includes a request for a network entity to coordinate RF sensing of at least one biological entity. The RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including a Doppler rate, a first identity of the RF transmitter and a second identity of the RF receiver to be used for the RF sensing, and the identity of the at least one biological entity. The RF sensing request includes a request for the network entity to coordinate RF sensing of the RF transmitter and the RF receiver for at least one biological function. The RF sensing request includes an indication that the Doppler rate is to be detected for sensing the at least one biological function, and the at least one biological function includes at least one of heartbeat or respiration. The RF sensing request is sent from the application device to the network entity; as well as The application device receives an RF sensing report from the network entity indicating the result of the RF sensing.

11. The method of claim 10, wherein, The RF sensing request includes a request for the network entity to coordinate RF sensing of the area, and the at least one criterion includes defining multiple coordinates of the area.

12. The method of claim 10, wherein, The RF sensing request includes a request for the network entity to coordinate RF sensing of a region, the request being for the detection of the presence of objects in the region.

13. The method of claim 10, wherein, The at least one criterion includes a threshold Doppler phase shift for the existence of the object to be reported.

14. The method of claim 10, wherein, The at least one criterion includes at least one of the following: the duration of the RF sensing, a first frequency of the RF sensing, or a second frequency at which the network entity provides an RF sensing report indicating the result of the RF sensing.

15. The method of claim 10, wherein, The at least one criterion includes an indication of the expected outcome of the RF sensing.

16. The method of claim 10, further comprising: The application device receives input about the RF-sensing subject from at least one information source other than the network entity. as well as The application device sends a response to the RF sensing report to the network entity, the response including the input regarding the subject of the RF sensing.

17. The method of claim 10, wherein, The RF sensing request is a first RF sensing request, and the method further includes sending a second RF sensing request based on the first RF sensing request from the application device to the network entity.

18. A network entity for detecting biological functions, the network entity comprising: interface; Memory; as well as One or more processors, which are communicatively coupled to the interface and the memory and configured to: The network entity receives an RF sensing request from the application device via the interface. The RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological entity. The RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including Doppler rate, a first identity of the RF transmitter and a second identity of the RF receiver to be used for the RF sensing, and the identity of the at least one biological entity. The RF sensing request includes a request for the network entity to coordinate RF sensing of the RF transmitter and the RF receiver for at least one biological function. The RF sensing request includes an indication that the Doppler rate is to be detected for sensing the at least one biological function, and the at least one biological function includes at least one of heartbeat or respiration. The first radio frequency configuration and the second radio frequency configuration are determined based on the RF sensing request; as well as The first radio frequency configuration is transmitted to the radio frequency transmitter via the interface, and the second radio frequency configuration is transmitted to the radio frequency receiver.

19. The network entity as claimed in claim 18, wherein, The one or more processors are further configured to determine the first RF configuration and the second RF configuration based on the desired RF sensing to be implemented by the RF transmitter and the RF receiver.

20. A radio frequency (RF) sensing coordination method for biological function detection, the method comprising: A network entity receives an RF sensing request from an application device. The RF sensing request includes a request for the network entity to coordinate RF sensing of at least one biological entity. The RF sensing request includes at least one criterion for the RF sensing, the at least one criterion including a Doppler rate, a first identity of the RF transmitter and a second identity of the RF receiver to be used for the RF sensing, and the identity of the at least one biological entity. The RF sensing request includes a request for the network entity to coordinate RF sensing of the RF transmitter and the RF receiver for at least one biological function. The RF sensing request includes an indication that the Doppler rate is to be detected for sensing the at least one biological function, and the at least one biological function includes at least one of heartbeat or respiration. At the network entity, a first radio frequency configuration and a second radio frequency configuration are determined based on the RF sensing request; as well as The first radio frequency configuration is transmitted from the network entity to the radio frequency transmitter, and the second radio frequency configuration is transmitted from the network entity to the radio frequency receiver.

21. The RF sensing coordination method as described in claim 20, wherein, The determination of the first RF configuration and the second RF configuration is further based on the desired RF sensing to be achieved by the RF transmitter and the RF receiver.

Images