Scheduled positioning of target device using mobile anchoring device
Through the location server optimizes the positioning operation of mobile devices based on GDOP, the problem of insufficient positioning accuracy in 5G wireless communication systems is solved, and more efficient resource utilization and precise position determination are achieved.
Patent Information
- Application Number
- CN202380035168.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-26
- Filing Date
- 2023-04-05
- Publication Date
- 2024-11-19
AI Technical Summary
In 5G wireless communication systems, it is difficult for the prior art to effectively utilize geometric accuracy decay factor (GDOP) to optimize the positioning accuracy of mobile devices, resulting in insufficient positioning accuracy or waste of resources.
Receive positioning requests from mobile devices through the location server, determine multiple positioning sets based on GDOP, and configure the mobile device to perform positioning operations within a specific time window to assist in position determination of the target object, optimizing positioning accuracy and resource utilization.
It improves the positioning accuracy and resource utilization of mobile devices, reduces the number of wireless sensing operations, and reduces the system load.
Smart Images

Figure CN118985154A_ABST
Abstract
Description
Background Art 1. Technical Field
[0002] Aspects of the present disclosure relate generally to wireless communications.
[0003] 2. Description of related technologies
[0004] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.
[0005] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transmission speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G, enable high-precision positioning based on 5G. Summary of the invention
[0006] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0007] In one aspect, a method of wireless communication performed by a location server includes: receiving a request to determine a location of a first mobile device at a first scheduled time; determining a first location of a second mobile device during a first time window; and configuring the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0008] In one aspect, a method of wireless communication performed by a location server includes: determining a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device; determining whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configuring the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0009] In one aspect, a method of wireless communication performed by a location server includes: determining to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; determining a first position of a mobile device during a first time window; and configuring the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0010] In one aspect, a location server comprises: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a request to determine a location of a first mobile device at a first scheduled time; determine a first location of a second mobile device during a first time window; and configure the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0011] In one aspect, a location server comprises: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device; determine whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configure the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0012] In one aspect, a location server comprises: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine to perform a wireless sensing operation at a first scheduled time to determine a location of a target object; determine a first position of a mobile device during a first time window; and configure the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0013] In one aspect, a location server includes: a component for receiving a request to determine the location of a first mobile device at a first scheduled time; a component for determining a first location of a second mobile device during a first time window; and a component for configuring the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time to assist in determining the location of the first mobile device at the first scheduled time.
[0014] In one aspect, a location server includes: components for determining a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device; components for determining whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and components for configuring the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0015] In one aspect, a location server includes: a component for determining to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; a component for determining a first position of a mobile device during a first time window; and a component for configuring the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time to assist in determining the location of the target object at the first scheduled time.
[0016] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: receive a request to determine a location of a first mobile device at a first scheduled time; determine a first location of a second mobile device during a first time window; and configure the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0017] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: determine a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device; determine whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configure the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0018] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a location server, cause the location server to: determine to perform a wireless sensing operation at a first scheduled time to determine a location of a target object; determine a first position of a mobile device during a first time window; and configure the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0019] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.
[0021] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0022] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.
[0023] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.
[0024] Figure 4 is a diagram illustrating an example of a downlink frame structure according to aspects of the present disclosure.
[0025] Figure 5 An example wireless communication network in which multiple UEs can receive positioning reference signals (PRS) from multiple base stations in accordance with aspects of the present disclosure is illustrated.
[0026] Figure 6 Example UE positioning operations in accordance with aspects of the present disclosure are illustrated.
[0027] Fig. 7A and Figure 7B An example multi-RTT positioning process using advance scheduling in accordance with aspects of the present disclosure is illustrated.
[0028] Figure 8 An example call flow for positioning operations that may be performed in accordance with certain aspects of the present disclosure is illustrated.
[0029] Fig. 9 An example of a call flow for positioning operations that may be performed in accordance with certain aspects of the present disclosure is illustrated.
[0030] FIG. 10A to FIG. 10D A positioning environment during an example time window is shown in accordance with aspects of the present disclosure.
[0031] Fig.11A and Fig. 11B Examples of object sensing according to aspects of the present disclosure are illustrated.
[0032] Fig.12 An example method of wireless communications performed by a location server according to aspects of the present disclosure is illustrated.
[0033] Fig.13 An example method of wireless communications performed by a location server according to aspects of the present disclosure is illustrated.
[0034] Fig.14 An example method of wireless communications performed by a location server according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0035] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.
[0036] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or superior to other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0037] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.
[0038] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."
[0039] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. The UE may be mobile or (e.g., at certain times) may be stationary and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. Typically, a UE may communicate with a core network via a RAN, and through the core network, the UE may connect to external networks such as the Internet and to other UEs. Of course, other mechanisms are also possible for the UE to connect to the core network and / or the Internet, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.
[0040] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.
[0041] The term "base station" may refer to a single physical transmit-receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. As used herein, because a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.
[0042] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to the UE to be measured by the UE, and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).
[0043] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.
[0044] Figure 1An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In one aspect, the macro cell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femto cells, pico cells, micro cells, etc.
[0045] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.
[0046] Among other functions, the base station 102 may perform functions related to one or more of the following: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) over a backhaul link 134, which may be wired or wireless.
[0047] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.
[0048] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).
[0049] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).
[0050] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or a listen before talk (LBT) procedure prior to communication in order to determine whether a channel is available.
[0051] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA) or MulteFire.
[0052] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180 that can operate in communication with the UE 182 at mmW frequencies and / or near mmW frequencies. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmitting and / or receiving) on the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.
[0053] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.
[0054] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.
[0055] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.
[0056] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that the parameters of the second beam (e.g., transmit beam or receive beam) for the second reference signal may be derived based on information about the first beam (e.g., receive beam or transmit beam) of the first reference signal. For example, the UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.
[0057] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, while if the UE is forming an uplink beam, it is an uplink transmit beam.
[0058] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, despite the portion of FR1 being greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) that is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0059] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.
[0060] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.
[0061] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that is configurable and can be used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those signaling information and signals specific to the UE may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.
[0062] For example, still refer to Figure 1 , one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.
[0063] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.
[0064] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102, or may be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.
[0065] In one aspect, the sidelink 160 may operate on an interesting wireless communication medium that may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the interesting medium may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.
[0066] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. Furthermore, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on sidelink 160.
[0067] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SV 112 can be part of a satellite positioning system that the UE 104 can use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal that is marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SV 112, the transmitter can sometimes be located on a ground-based control station, base station 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SV 112.
[0068] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, and the like, such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), and the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.
[0069] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from a SV 112.
[0070] The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., through which UE 190 can indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (through which UE 190 can indirectly obtain WLAN-based Internet connectivity). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth ® etc.
[0071] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 may communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, a next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either (or both) the gNB 222 or the ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
[0072] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).
[0073] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the embodiment of the present invention can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network-specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.
[0074] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the transmission of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.
[0075] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.
[0076] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).
[0077] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.
[0078] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.
[0079] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including transmission of user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.
[0080] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a B node (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called a stand-alone base station or a single-chip base station) or a decomposed base station.
[0081] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0082] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0083] Figure 2CAn example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226), which may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link, or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.
[0084] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO framework 255) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0085] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 280. CU 280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.
[0086] DU 285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on functional splits such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 285 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 285 or with control functions hosted by CU 280.
[0087] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, a RU 287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and the CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).
[0088] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some specific implementations, the SMO framework 255 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 261) via the O1 interface. Additionally, in some specific implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via the O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255 .
[0089] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.
[0090] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0091] Figure 3A , Figure 3B and Figure 3C The example may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including a location server 230 and a LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the 5GC 210 / 260 (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (for example, in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. In addition, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.
[0092] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 may be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.
[0093] At least in some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth ® 、Zigbee ® 、Z-Wave ®, PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), etc.) and other network nodes (such as other UEs, access points, base stations, etc.) for communicating (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth ® Transceiver, Zigbee ® and / or Z-Wave ® transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.
[0094] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.
[0095] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.
[0096] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations may include separate transmitter circuits and separate receiver circuits, or may be implemented in other ways in other implementations. The transmitter circuit and the receiver circuit of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350 , short-range wireless transceivers 320 and 360 ) may also include a network listening module (NLM) or the like for performing various measurements.
[0097] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.
[0098] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.
[0099] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.
[0100] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.
[0101] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.
[0102] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transmission of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
[0103] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0104] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.
[0105] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.
[0106] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
[0107] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0108] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.
[0109] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.
[0110] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that may be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of a cellular device, a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.
[0111] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or be part of a communication interface for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide for communication between the different logical entities.
[0112] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). In addition, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions, and / or functions are described herein as being performed "by a UE," "by a base station," "by a network entity," and the like. However, as will be appreciated, such operations, actions and / or functions may actually be performed by a specific component or combination of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).
[0113] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated separately from a network operator or a cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).
[0114] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 4 is a diagram 400 illustrating an example of a downlink frame structure in accordance with aspects of the present disclosure. Other wireless communication technologies may have different frame structures and / or different channels.
[0115] LTE (and in some cases NR) utilizes OFDM on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Therefore, for a system bandwidth of 1.25 megahertz (MHz), 2.5MHz, 5MHz, 10MHz, or 20MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into multiple subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.
[0116] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (µ), for example, 15kHz (µ=0), 30kHz (µ=1), 60kHz (µ=2), 120kHz (µ=3), and 240kHz (µ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (µ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (µs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (µ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (µ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (µ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (µ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17µs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.
[0117] exist Figure 4 In the example of , a parameter set of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 4 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.
[0118] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 4In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0119] Some REs carry downlink reference (pilot) signals (DL-RS). DL-RS may include positioning reference signal (PRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (SSB), etc. Figure 4 Example locations of REs carrying PRS (labeled “R”) are illustrated.
[0120] A set of resource elements (REs) used for transmission of a PRS is referred to as a "PRS resource". A set of resource elements may span multiple PRBs in the frequency domain and N (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.
[0121] The transmission of a PRS resource within a given PRB has a specific comb size (also referred to as "comb density"). The comb size N represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. Figure 4 An example PRS resource configuration for comb-6 (which spans six symbols) is illustrated. That is, the positions of shaded REs (marked as "R") indicate the PRS resource configuration of comb-6.
[0122] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols in a slot using a full frequency domain staggered pattern. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers in a slot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2,1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2,5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb - 12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5,11}.
[0123] A "PRS resource set" is a set of PRS resources used to transmit a PRS signal, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by the TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from: 2^µ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120,10240} slots, where µ = 0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.
[0124] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, a "PRS resource" (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.
[0125] A "PRS instance" or "PRS opportunity" is an instance of a periodically repeated time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity", "PRS positioning instance", "positioning opportunity", "positioning instance", "positioning repetition", or simply "opportunity", "instance", or "repetition".
[0126] A "positioning frequency layer" (also referred to simply as a "frequency layer") is a set of one or more PRS resource sets with the same values for certain parameters across one or more TRPs. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the physical downlink shared channel (PDSCH) are also supported by PRS), the same point A, the same value of the downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, and the minimum value is 24 PRBs and the maximum value is 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per TRP per frequency layer.
[0127] The concept of frequency layer is somewhat similar to the concept of component carrier and bandwidth part (BWP), but the difference is that component carrier and BWP are used by one base station (or macro cell base station and small cell base station) to send data channels, while frequency layer is used by several (usually three or more) base stations to send PRS. The UE can indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, the UE can indicate whether it can support one or four positioning frequency layers.
[0128] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. as defined in LTE and NR. In addition, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If further distinction is needed between the types of PRS, the downlink positioning reference signal may be referred to as "DL-PRS", while the uplink positioning reference signal (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS". In addition, for signals that can be sent in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS".
[0129] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle of departure (DL-AoD) in NR. In the OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the arrival time (ToA) of the reference signal (e.g., positioning reference signal (PRS)) received from the paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurement), and reports these differences to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the assistance data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known positioning of the base stations involved and the RSTD measurements, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.
[0130] For DL-AoD positioning, the positioning entity uses measurement reports from the UE on received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the position of the UE based on the determined angle and the known position of the transmitting base station.
[0131] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but UL-TDOA is based on uplink reference signals (e.g., sounding reference signals (SRS)) sent by the UE to multiple base stations. Specifically, the UE sends one or more uplink reference signals, which are measured by a reference base station and multiple non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location and relative timing of the base stations involved. Based on the receive-to-receive (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known positioning of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the position of the UE.
[0132] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the position of the UE.
[0133] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the received to transmitted (Rx-Tx) time difference. The Rx-Tx time difference measurement can be made or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) so that the location of the first entity can be determined based on the distance to the second entity and the known location of the second entity (e.g., using multi-point positioning). RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy.
[0134] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing and signal strength of the detected neighboring base stations. The UE's position is then estimated based on this information and the known positioning of the base stations.
[0135] To assist the positioning operation, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include: an identifier of the base station (or cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive time slots including PRS, the periodicity of consecutive time slots including PRS, silent sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a specific positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in an overhead message broadcast periodically, etc.). In some cases, the UE itself is able to detect neighboring network nodes without the use of assistance data.
[0136] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and an associated uncertainty, or a search window around the expected RSTD. In some cases, the value range of the expected RSTD may be + / -500 microseconds (µs). In some cases, when any resource used for positioning measurements is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32µs. In other cases, when all resources used for positioning measurements are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8µs.
[0137] The position estimate may be referred to by other names, such as a location estimate, a location, a fix, a location fix, a fix, etc. The location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, a postal address, or some other verbal description of the location. The location estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be contained with some specified or default confidence level).
[0138] The quality of position estimates that can be obtained from a group of transmitters (e.g., base stations, WLAN APs, Global Navigation Satellite System (GNSS) satellites, positioning beacons, etc.) can be quantified using a metric called Dilution of Precision (DOP). DOP is a well-known metric that represents the impact on the accuracy of positioning measurements due to the geometry of the transmitter relative to the target UE. The calculation of the DOP metric uses the known location of the transmitter and at least the coarse location of the UE.
[0139] More specifically, wireless signals from transmitters usually have fixed accuracy. Therefore, relative transmitter-receiver geometry plays an important role in determining the accuracy of the estimated position of the receiver. Due to the relative geometry of any given transmitter and receiver, the accuracy of the transmitted signal is converted into corresponding components in each of the three dimensions (i.e., x, y, z) of the position measured by the receiver. According to the relative position of the transmitter, the accuracy of multiple transmitters relative to the receiver is combined to determine the level of accuracy in each dimension measured by the receiver. When the transmitters are close together from the perspective of the receiver (for example, multiple transmitters can be separated in space but appear in a line from the perspective of the receiver), the geometry is called weak and the DOP value is high. When the transmitter is far away from the perspective of the receiver, the geometry is strong and the DOP value is low. Therefore, due to the wider angular separation between the transmitters used to calculate the position of the receiver, a low DOP value represents better position accuracy. Other factors that can increase the effective DOP are obstacles, such as nearby mountains or buildings.
[0140] There are several variations of DOP, including Geometric Dilution of Precision (GDOP), Horizontal Dilution of Precision (HDOP), Vertical Dilution of Precision (VDOP), Positioning (3D) Dilution of Precision (PDOP), and Temporal Dilution of Precision (TDOP). GDOP is used to represent both 3D positioning uncertainty and timing uncertainty, while PDOP is only used to represent 3D positioning uncertainty and TDOP is only used to represent timing uncertainty. VDOP is used to represent vertical positioning uncertainty.
[0141] As described above, a good (ie, low) DOP value generally depends on the spatial distribution of transmitters relative to the target UE and the measurement uncertainty of each link between the UE and the corresponding transmitter (which may be based on the link quality). Figure 5 An example wireless communication network 500 is illustrated in which multiple UEs can receive PRSs from multiple base stations in accordance with various aspects of the present disclosure. Specifically, a first UE 504-1 and a second UE 504-2 (collectively, UE 504) can be capable of detecting and processing PRSs transmitted by base stations 502-1, 502-2, 502-3, 502-4, and 502-5 (collectively, base stations 502). In an aspect, base stations 502 can periodically or on-demand (e.g., when directed by a location server or requested by UE 504) transmit PRSs to enable UEs 504 in their coverage area to measure properties of those PRSs (e.g., ToA, RSTD, Rx-Tx time difference, AoA, etc.) for positioning purposes. As will be appreciated, although the PRSs are transmitted by base stations 502-1, 502-2, 502-3, 502-4, and 502-5 (collectively, base stations 502), the PRSs can be transmitted by base stations 502-1, 502-2, 502-3, 502-4, and 502-5 (collectively, base stations 502). In an aspect, base stations 502 can transmit PRSs periodically or on-demand (e.g., when directed by a location server or requested by UE 504) to enable UEs 504 in their coverage area to measure properties of those PRSs (e.g., ToA, RSTD, Rx-Tx time difference, AoA, etc.) for positioning purposes. Figure 5 Two UEs 504 and five base stations 502 are illustrated, but there may be more or less than two UEs 504 and five base stations 502.
[0142] exist Figure 5 In the example of , a subset of base stations 502-1, 502-2, 502-3, and 502-5 will likely provide a good (or at least adequate) DOP for UE 504-1, while a subset of base stations 502-3, 502-4, and 502-5 will likely provide a good (or at least adequate) DOP for UE 504-2. Measuring PRS from base stations 502 whose positions are highly "correlated" with respect to other base stations 502 from the perspective of UE 504 (i.e., have a low spatial distribution) is unlikely to improve the positioning quality of UE 504. Thus, for UE 504-1, because base station 502-4 is substantially consistent with base station 502-3 from the perspective of UE 504-1, adding base station 502-4 to the set of base stations 502 that UE 504-1 is measuring is unlikely to improve (at least significantly improve) the position estimate for UE 504-1. Similarly, for UE 504-2, because base stations 502-1 and 502-2 are substantially coincident with base station 502-3 from the perspective of UE 504-2, adding base stations 502-1 and 502-2 to the set of base stations 502 being measured by UE 504-2 is unlikely to improve (at least significantly) the position estimate for UE 504-2. Note that reference to "measuring a base station" more specifically refers to measuring the PRS from that base station.
[0143] The UE 504 can measure the data from several base stations 502 (in Figure 5 In the case of strong signals of the base stations 502 (five in the example), such as in a dense network deployment, the target UE 504 may not need to process PRS from all available base stations 502 in order to estimate its position or to achieve an estimate of its position. Instead, it may be sufficient to select a subset of base stations 502 that satisfy a quality metric (e.g., a DOP threshold). Therefore, since the set of base stations 502-1, 502-2, 502-3, and 502-5 provides a good DOP for UE 504-1, UE 504-1 may measure PRS only from these base stations 502 to calculate its position or enable another positioning entity to calculate its position. Similarly, since the set of base stations 502-3, 502-4, and 502-5 provides a good DOP for UE 504-2, UE 504-2 may measure PRS only from these base stations 502 to calculate its position or enable another positioning entity to calculate its position.
[0144] Figure 6Example UE positioning operations 600 according to aspects of the present disclosure are illustrated. The UE positioning operations 600 may be performed by the UE 204, the NG-RAN node 602 in the NG-RAN 220 (e.g., the gNB 222, the gNB-CU 226, the ng-eNB 224, or other nodes in the NG-RAN 220), the AMF 264, the LMF 270, and the 5GC location service (LCS) entity 680 (e.g., any third-party application requesting the location of the UE 204, a public service access point (PSAP), an E-911 server, etc.).
[0145] The location service request to obtain the location of the target (i.e., UE 204) can be initiated by the 5GC LCS entity 680, the AMF 264 serving the UE 204, or the UE 204 itself. Figure 6 These options are illustrated as stages 610a, 610b, and 610c, respectively. Specifically, at stage 610a, the 5GC LCS entity 680 transmits a location service request to the AMF 264. Alternatively, at stage 610b, the AMF 264 itself generates the location service request. Alternatively, at stage 610c, the UE 204 transmits a location service request to the AMF 264.
[0146] Once the AMF 264 receives (or generates) the location service request, it forwards the location service request to the LMF 270 at stage 620. The LMF 270 then performs an NG-RAN positioning procedure with the NG-RAN node 602 at stage 630a and a UE positioning procedure with the UE 204 at stage 630b. The specific NG-RAN positioning procedure and the UE positioning procedure may depend on the type of positioning method used to locate the UE 204, which may depend on the capabilities of the UE 204. The positioning method may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and / or downlink and uplink-based (e.g., LTE / NR E-CID, multi-RTT, etc.), as described above. The corresponding positioning procedures are described in detail in 3GPP Technical Specification (TS) 38.305, which is publicly available and incorporated herein by reference in its entirety.
[0147] The NG-RAN positioning procedure and the UE positioning procedure may utilize LTE Positioning Protocol (LPP) signaling between the UE 204 and the LMF 270 and LPP Type A (LPPa) or New Radio Positioning Protocol Type A (NRPPa) signaling between the NG-RAN node 602 and the LMF 270. LPP is used point-to-point between a location server (e.g., LMF 270) and a UE (e.g., UE 204) to obtain location-related measurements or location estimates or to transmit assistance data. A single LPP session is used to support a single location request (e.g., for a single mobile-terminated location request (MT-LR), mobile-originated location request (MO-LR), or network-induced location request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session includes one or more LPP transactions, where each LPP transaction performs a single operation (e.g., capability exchange, assistance data transfer, or location information transfer). LPP transactions are referred to as LPP procedures.
[0148] A prerequisite for stage 630 is that the LCS-correlation identifier (ID) and the AMF ID have been passed to the LMF 270 by the serving AMF 264. Both the LCS-correlation ID and the AMF ID may be represented as strings selected by the AMF 264. The LCS-correlation ID and the AMF ID are provided by the AMF 264 to the LMF 270 in the location service request at stage 620. When the LMF 270 subsequently initiates stage 630, the LMF 270 also includes the LCS-correlation ID for the location session and the AMF ID indicating the AMF instance serving the UE 204. The LCS-correlation ID is used to ensure that during the positioning session between the LMF 270 and the UE 204, the positioning response message from the UE 204 is returned by the AMF 264 to the correct LMF 270 and carries an indication (the LCS-correlation ID) that can be recognized by the LMF 270.
[0149] Note that the LCS correlation ID is used as a location session identifier, which can be used to identify messages exchanged between the AMF 264 and the LMF 270 for a specific location session for the UE 204, as described in more detail in 3GPP TS 23.273, which is publicly available and incorporated herein by reference in its entirety. As mentioned above and shown in stage 620, a location session between the AMF 264 and the LMF 270 for a specific UE 204 is initiated by the AMF 264, and the LCS correlation ID can be used to identify the location session (e.g., can be used by the AMF 264 to identify state information of the location session, etc.).
[0150] The LPP positioning method and associated signaling content are defined in the 3GPP LPP standard (3GPP TS 37.355, which is publicly available and incorporated herein by reference in its entirety). LPP signaling can be used to request and report measurement results related to the following positioning methods: LTE-OTDOA, DL-TDOA, A-GNSS, E-CID, Sensor, TBS, WLAN, Bluetooth, DL-AoD, UL-AoA, and Multi-RTT. Currently, an LPP measurement report may include the following measurement results: (1) one or more ToA, TDOA, RSTD, or Rx-Tx time difference measurement results, (2) one or more AoA and / or AoD measurement results (currently only used for base stations to report UL-AoA and DL-AoD to LMF 270), (3) one or more multipath measurement results (ToA, RSRP, AoA / AoD per path), (4) one or more motion states (e.g., walking, driving, etc.) and trajectories (currently only used for UE 204), and (5) one or more report quality indicators.
[0151] As part of the NG-RAN node positioning procedure (stage 630a) and the UE positioning procedure (stage 630b), the LMF 270 may provide LPP assistance data in the form of downlink positioning reference signal (DL-PRS) configuration information for the selected positioning method to the NG-RAN node 602 and the UE 204. Alternatively or additionally, the NG-RAN node 602 may provide DL-PRS and / or uplink PRS (UL-PRS) configuration information to the UE 204 for the selected positioning method. Note that although Figure 6 A single NG-RAN node 602 is illustrated, but multiple NG-RAN nodes 602 may be involved in a positioning session.
[0152] Once configured with a DL-PRS and / or UL-PRS configuration, the NG-RAN node 602 and the UE 204 transmit and receive / measure the corresponding PRS at the scheduled time. The NG-RAN node 602 and the UE 204 then transmit their corresponding measurements to the LMF 270. In some cases, the NG-RAN node 602 may transmit its measurements to the UE 204, which may forward them to the LMF 270 using LPP signaling. Alternatively, the NG-RAN node 602 may transmit its measurements directly to the LMF 270 in LPPa or NRPPa signaling. In some cases, the UE 204 may transmit its measurements to the NG-RAN node 602 in RRC, uplink control information (UCI), or MAC control element (MAC-CE) signaling, and the NG-RAN node 602 may forward the measurements to the LMF 270 using LPPa or NRPPa signaling. Alternatively, the UE 204 may transmit its measurements directly to the LMF 270 using LPP signaling.
[0153] Once the LMF 270 obtains measurements from the UE 204 and / or the NG-RAN node 602 (depending on the type of positioning method), it uses those measurements to calculate an estimate of the location of the UE 204. Then, at stage 640, the LMF 270 transmits a location services response including a location estimate for the UE 204 to the AMF 264. Then, at stage 650, the AMF 264 forwards the location services response to the entity that generated the location services request. Specifically, if the location services request was received from the 5GC LCS entity 680 at stage 610a, then at stage 650a, the AMF 264 transmits the location services response to the 5GC LCS entity 680. However, if a location services request was received from the UE 204 at stage 610c, then at stage 650c, the AMF 264 transmits the location services response to the UE 204. Alternatively, if the AMF 264 generates a location services request at stage 610b, then at stage 650b the AMF 264 itself stores / uses the location services response.
[0154] Note that although the foregoing has described the UE positioning operation 600 as a UE-assisted positioning operation, it may instead be a UE-based positioning operation. A UE-assisted positioning operation is one in which the LMF 270 calculates the location of the UE 204, while a UE-based positioning operation is one in which the UE 204 calculates its own location. In the case of a UE-based positioning operation, stages 610c and 650c will be performed. The LMF 270 may still coordinate the transmission / measurement of the DL-PRS (and possibly the UL-PRS), but the measurements will be forwarded to the UE 204 rather than the LMF 270. Thus, the location service response at stages 640 and 650c may be the measurements from the involved NG-RAN node 602 rather than the location estimate of the UE 204. Alternatively, in the case in which the involved NG-RAN node 602 forwards its corresponding measurements directly to the UE 204 (e.g., via RRC signaling), the location service response at stage 640 may simply be a confirmation that the NG-RAN node and UE positioning process at stage 630 is complete.
[0155] In some scenarios, the target UE (e.g., UE 204), LCS client (e.g., 5GCLCS entity 680), or application function (AF) requesting the location of the target UE may know the time when the location should be obtained. For example, in the case of periodic positioning, the UE's location is obtained at a fixed periodic interval using a periodically delayed 5GC mobile terminal location request (5GC-MT-LR). In this case, the location time is known in advance. As another example, for industrial IoT (IIoT) positioning, in a factory or warehouse with mobile tools, components, packages, etc., there may be an accurate expectation that the mobile tools, components, packages, etc. will arrive at a specific location or will have completed a specific movement or operation. Then, locating the tools, components, packages, etc. to confirm the expectations and make any further adjustments may be useful or even critical. As another example, for scheduled locations, the location of the UE may sometimes be scheduled to occur at a specific time in the future. For example, all vehicles on the road may be located simultaneously to provide an indication of traffic congestion and assist V2X communication. In addition, people, containers, transportation systems, etc. may also be located at certain common times.
[0156] In the above scenario, a known time called a scheduled location time may be provided in advance to reduce the effective delay in providing the location result. Figure 6 Describes the general UE positioning operations. Figure 6, the main impact of advance scheduling on 5GC is at stages 610 and 620. At stage 610, the scheduled location time T is included in the location service request from the 5GC LCS entity 680, from the AMF 264, or from the UE 204. Then, at stage 620, the location service request including the scheduled location time T is passed to the LMF 270. The scheduled location time T specifies the future time when the location of the UE 204 is to be obtained. In other words, the scheduled location time T is the time when the estimated location of the UE 204 is expected to be valid. The impact on the RAN is at stage 630, where as part of locating the UE 204, the LMF 270 schedules the positioning measurements to be performed by the UE 204 and / or the NG-RAN node 602 to occur at or near the scheduled location time T. The time when the UE 204 and / or the NG-RAN node 602 is expected to perform the positioning measurements is called the scheduled measurement time T'.
[0157] Fig. 7A and Figure 7B An example multi-RTT positioning process 700 using advance scheduling according to aspects of the present disclosure is illustrated. Since the multi-RTT positioning process is a downlink-based and uplink-based positioning process, the downlink-based or uplink-based positioning process will be a subset of the multi-RTT positioning process 700. When the scheduled position time is used, the positioning process can be divided into a position preparation phase (phases 705 to 750) and a position execution phase (phases 755 to 765).
[0158] The location preparation phase begins at time T-t1 when the LMF 270 receives a location request from the AMF 264 (not shown) and determines the positioning method to be used. The location preparation phase ends after the LMF 270 has requested downlink measurements from the target UE 204, uplink measurements from the gNB 222 involved, and / or a location estimate from the UE 204. The location preparation phase includes any of the following: providing assistance data to the UE (for downlink measurements or location estimation) and requesting configuration information from the gNB 222 or providing configuration information to the gNB.
[0159] The location execution phase starts at the scheduled location time T when the target UE 204 obtains downlink measurements (and possibly determines a location estimate based on those measurements) and / or when the gNB 222 obtains uplink measurements, and ends at time T+t2 when the UE location information has been provided to the LMF 270 (UE 204 and / or gNB 222 location measurements or UE location estimate). Fig. 7A and Figure 7B The effective positioning process delay in is then determined by the phase that includes only the position execution phase (ie, between time T and time T+t2).
[0160] Specific reference Fig. 7A and Figure 7B At stage 705a, the LCS client 790 (e.g., an application running on the target UE 204, a remote application, etc.) transmits an LCS request to the LCS entity 680. The LCS request includes a future time T at which the location of the UE 204 is desired. At stage 705b, the LCS entity 680 forwards the LCS request to the LMF 290. At stage 710, the LMF 270 schedules a location session so that the location of the UE 204 is available and valid at the requested location time T. Fig. 7A As shown, the subsequent location preparation phase starts at time T-t1, where t1 depends on the expected duration of the location preparation phase. The expected duration of the location preparation phase depends on the selected positioning method, which is a multi-RTT positioning process here.
[0161] At stage 715 (the first stage of the location preparation stage), LMF 270 performs DL-PRS configuration information exchange with the target UE 204's serving and neighboring gNB 222 via NRPPa signaling. At stage 720, LMF 270 performs capability transfer with UE 204 via LPP signaling. Specifically, LMF 270 transmits an LPP request capability message to the target UE 204, as in Figure 6 At stage 610 of the present invention, and in response, UE 204 transmits an LPP Offer Capability message to LMF 270, as in Figure 6 at stage 620.
[0162] At stage 725, the LMF 270 transmits an NRPPa positioning information request to the serving gNB 222 (or TRP) of the target UE 204 to request UL-SRS configuration information for the UE 204. The LMF 270 may provide any auxiliary data required by the serving gNB 222 (e.g., path loss reference, spatial relationship, SSB configuration, etc.). At stage 730a, the serving gNB 222 determines the resources available for UL-SRS and configures the target UE 204 with a UL-SRS resource set. At stage 730b, the serving gNB 222 provides the UL-SRS configuration information to the UE 204. At stage 735, the serving gNB 222 transmits an NRPPa positioning information response message to the LMF 270. The NRPPa positioning information response message includes the UL-SRS configuration information transmitted to the UE 204.
[0163] At stage 735a, the LMF 270 transmits an NRPPa Positioning Activation Request message to the serving gNB 222, commanding it to configure the UE 204 to activate UL-SRS transmission on the configured / allocated resources. The UL-SRS may be an aperiodic (e.g., on-demand) UL-SRS, and therefore, at stage 735b, the serving gNB 222 configures / commands the UE 204 to activate (i.e., start) UL-SRS transmission. At stage 735c, the serving gNB 222 transmits an NRPPa Positioning Activation Response message to the LMF 270 to indicate that UL-SRS transmission has been activated.
[0164] At stage 740, the LMF 270 transmits an NRPPa measurement request message to the gNB 222. The NRPPa measurement request message includes all information required to enable the gNB 222 to perform uplink measurements of UL-SRS transmissions from the target UE 204. The NRPPa measurement request message also includes a physical measurement time T' indicating when the location measurement results will be obtained. The time T' defines the time T that the location of the target UE 204 will be valid and can be specified as a system frame number (SFN), a subframe, a time slot, an absolute time, etc. The time T' is provided in the same units as the time T.
[0165] At stage 745, the LMF 270 transmits assistance data for the multi-RTT positioning process 700 to the UE 204 in one or more LPP Provide Assistance Data messages, as at stage 730 of Figure 7. The LPP Provide Assistance Data message includes all information required to enable the UE 204 to perform positioning measurements (here, Rx-Tx time difference measurements) of the DL-PRS transmissions from the gNB 222. At stage 750, the LMF 270 transmits an LPP Request Location Information message to the target UE 204, as at stage 740 of Figure 7. The LPP Request Location Information message may also include a time T' (but it may be a different time T' than the time provided to the gNB 222 at stage 740). At this point, the location preparation phase ends.
[0166] At stage 755a, the target UE 204 performs measurement (here, Rx-Tx time difference measurement) of the DL-PRS sent by the gNB involved at time T' (or makes the measurement valid at time T') based on the assistance data received at stage 745. At stage 755b, the gNB involved 222 performs measurement (here, Tx-Rx time difference measurement) of the UL-SRS sent by the target UE 204 at time T' (or makes the measurement valid at time T') based on the assistance data received in the NRPPa measurement request message at stage 740.
[0167] At stage 760, the target UE 204 transmits an LPP Provide Location Information message. The LPP Provide Location Information message includes the positioning measurements performed by the UE 204 at stage 755a. At stage 765, the gNB 222 involved transmits an NRPPa Measurement Response message to the LMF 270. The NRPPa Measurement Response message includes the measurements of the UL-SRS measured at stage 755b. The responses at stages 760 and 765 include the time T'' at which the measurements were obtained. The time T'' should be equal to the time T', but may not be exactly equal to the time T' due to processing delays, timing issues and / or other factors. The difference between time T' and T'' is the location time error (δ).
[0168] At stage 770a, LMF 270 transmits an LCS response message to LCS entity 680. The LCS response message includes the location of target UE 204 at time T+δ. LCS entity 680 forwards the LCS response message to LCS client 790. LCS client 790 receives the location of target UE 204 with a timestamp T+δ at time T+t2, where time t2 is the delay between time T and the response time. The delay t2 as observed by LCS client 790 does not include the location preparation phase from time T-t1 to time T. Any movement of UE 204 during the delay time t2 should have a negligible effect on the validity and accuracy of the location estimate. That is, the location of UE 204 at time T+t2 should be approximately the same as the location of UE 204 at time T.
[0169] Figure 8 An example call flow 800 for positioning operations that may be performed according to certain aspects of the present disclosure is illustrated. In this example, a network 802 controls the operation of sidelink anchor devices 804, 806, 808 and a target UE 810 during positioning operations. For the purposes of the following discussion, it is assumed that the sidelink anchor devices 806 and 808 are being used as preferred anchor devices by the target UE 810. Therefore, in conjunction with Figure 8 Only sidelink anchor devices 804 and 806 are involved in the described positioning operation. However, the network 802 may use only the preferred anchor reports as positioning assistance data and choose to use additional sidelink anchor devices or fewer sidelink anchor devices than the reported preferred sidelink anchor devices.
[0170] like Figure 8As shown, the network 802 sends a PRS send request to each of the preferred side link anchor devices 806 and 808. The PRS send request to each of these preferred side link anchor devices requests each preferred side link anchor device to send one or more PRSs. In this example, the network 802 sends a PRS send request to the side link anchor device 806 to request the side link anchor device 806 to send a PRS on PRS resource 2, and sends a PRS resource send request to the side link anchor device 808 to request the side link anchor device 808 to send a PRS on PRS resource 4. In a system employing a larger number of preferred side link anchor devices, similar PRS requests are transmitted to each of the additional preferred side link anchor devices.
[0171] The network 802 transmits a PRS measurement request to the target UE 810 to measure the PRS that has been requested to be sent from the sidelink anchor devices 806 and 808. In this example, the network 802 transmits a PRS measurement request to the target UE 810 to measure one or more PRSs sent in PRS resource 2 of the sidelink anchor device 806 and one or more PRSs sent in PRS resource 4 of the sidelink anchor device 808. In response to the PRS resource sending request from the network 802, the sidelink anchor device 806 sends its PRS in PRS resource 2, and the sidelink anchor device 808 sends its PRS in PRS resource 4. The target UE 810 responds to the PRS measurement request from the network 802 by measuring the PRS sent on PRS resource 2 of the sidelink anchor device 806 and the PRS sent on PRS resource 4 of the sidelink anchor device 808. The measurements made by the target UE 810 are reported in a PRS measurement report, which is communicated directly to the network 802 , which uses it to determine the location of the target UE 810 .
[0172] The network 802 may use various positioning methods to determine the location of the target UE 810 using the PRS measurement reports. According to certain aspects, the network 802 uses the data received in the PRS measurement reports to determine the location of the target UE 810 using time difference of arrival (TDOA) positioning, as described above with reference to Figure 5 As described. Since the target UE 810 is Figure 8In the call flow 800 of FIG. 802 , the PRS is not sent, so the network 802 may take additional steps to compensate for the synchronization error between the side link anchor devices. In one example, the network 802 may transmit a PRS sending request to a first side link anchor device 806 among the side link anchor devices within the positioning environment, wherein the PRS sending request is a request for the first side link anchor device 806 to send one or more PRSs. The network 802 may transmit a PRS measurement request to a second side link anchor device 808 among the side link anchor devices within the positioning environment, wherein the second request is a request for the second side link anchor device 808 to measure the PRS sent by the first side link anchor device. The second side link anchor device 808 reports the measurement of the PRS to the network 802, and the network may use the PRS measurement to compensate for the synchronization error between the first side link anchor device and the second side link anchor device.
[0173] According to certain aspects of the present disclosure, the network 802 may use multi-cell round trip time (multi-RTT) positioning to determine the location of the target UE 810. In such instances, the network 802 may also transmit a PRS transmission request to the target UE 810 requesting the transmission of one or more PRSs. Additionally, the network 802 may transmit a PRS measurement request to each sidelink anchor device requesting the sidelink anchor device to measure the transmitted PRS of the target UE 810. The sidelink anchor device reports the Rx-Tx time difference measurement to the network 802, which uses the Rx-Tx time difference measurement reported by the sidelink anchor device and the Rx-Tx time difference measurement reported by the target UE to determine the location of the target UE 810 using a multi-RTT positioning method.
[0174] Fig. 9 An example of a call flow 900 for positioning operations that may be performed according to certain aspects of the present disclosure is illustrated. In this example, a network 902 controls the operation of side link anchor devices 904, 906, 908 and a target UE 910 during a positioning operation. For the purposes of the following discussion, it is assumed that all side link anchor devices 904, 906, and 908 have been selected by the network 902 to determine the positioning of the target UE 910.
[0175] like Fig. 9 As shown, the network 902 sends a PRS transmission request to the target UE 910. The PRS transmission request to the target UE 910 requests the target UE 910 to transmit one or more PRSs. In this example, the network 902 sends a PRS transmission request to the target UE 910 requesting that one or more PRSs be transmitted in PRS resource 1.
[0176] The network 902 sends a PRS measurement request to each of the sidelink anchor devices 904, 906, and 908. Fig. 9, a PRS measurement request to each sidelink anchor device requests the sidelink anchor device to measure one or more PRSs sent in PRS resource 1 of the target UE 910. The target UE 910 sends one or more PRSs in PRS resource 1, which is received by each of the sidelink anchor devices 904, 906, and 908. Each sidelink anchor device measures the signal strength of the PRS in PRS resource 1 and reports the PRS measurement to the network 902 in a corresponding measurement report. The network 902 can determine the positioning of the target UE 910 using the PRS measurement reports received from the sidelink anchor devices 904, 906, and 908.
[0177] Conventional NR positioning relies on measurements to and by an anchor such as a gNB / TRP at a fixed location (e.g., an anchor at a known location that is not movable). Mobile anchoring devices may appear in SL positioning. However, conventional NR positioning does not define any procedures for the use of mobile anchoring devices when the positioning of a target mobile device is scheduled in advance. Certain aspects of the present disclosure are implemented with the recognition that it may be desirable to employ a mobile anchoring device (e.g., a mobile UE, a mobile gNB, such as in a mobile integrated access backhaul / vehicle relay (IAB / VMR), or in a GNSS where the satellites are mobile) when performing positioning operations to determine the position of a target mobile device at a scheduled future time.
[0178] According to certain aspects of the present disclosure, Fig. 7A and Figure 7B The scheduling and determination of the location of a target mobile device at a scheduled future time is performed in a manner similar to that shown in . However, certain aspects of the present disclosure incorporate solutions that facilitate the use of mobile anchor devices in location operations that occur at future scheduled times. The scheduling can be based on a one-time request for location at a specified time, an aperiodic scheduling of multiple location requests, and / or a periodic location request in which the first instance for performing a periodic location begins at a specified time.
[0179] According to certain aspects of the present disclosure, a location server (eg, LMF) performs operations in multiple phases when using a mobile anchor device. Although certain aspects of the present disclosure may refer to a single mobile anchor device, it should be understood that these aspects can be extended to scenarios using multiple mobile anchor devices.
[0180] In one aspect, a location server may receive a request to determine the location of a target mobile device at a first scheduled time. In preparation for using a mobile anchor device, the location server may perform a location preparation phase in which the location of the mobile anchor device is determined. During this phase, the location server also configures the mobile anchor device (and any other participating fixed anchor devices) to send and / or receive PRS during a time window corresponding to the first scheduled time in order to determine the location of the target mobile device. An initial determination of the location of the mobile anchor device is performed to ensure that scheduled PRS transmission / reception occurs at a time when the mobile anchor device is at a known location. The location server may also make a determination as to whether the mobile anchor device is at a location for performing useful PRS transmission / reception that will result in high-quality PRS measurements. In some aspects, the location server may use the location of the mobile anchor device to optimize the combination of fixed and / or mobile anchor devices used to achieve the desired GDOP attribute to determine the location of the target mobile device.
[0181] In some aspects, the location server determines a first position of the mobile anchor device during a first time window prior to a first scheduled time. The location server then configures the mobile anchor device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining a position of the target mobile device at the first scheduled time. In some aspects, the mobile anchor device is configured to perform a positioning operation that includes 1) transmitting a PRS to be measured by the target mobile device during the second time window, 2) measuring one or more PRSs received from the target mobile device during the second time window, or 3) a combination thereof.
[0182] According to certain aspects of the present disclosure, a location server may implement scheduling for determining the location of a mobile anchoring device. However, in such instances, the location server does not need to receive a direct request from an external client (e.g., UE, RAN node, PSAP, etc.) to initiate the determination of the location of the mobile anchoring location. Instead, in certain aspects, the location of the mobile anchoring device is used for the purpose of locating the target mobile device based on an external client request. In certain aspects, the signaling associated with the existing way of scheduling future positioning operations can be supplemented with signaling that supports similar scheduling of mobile anchoring devices. In certain aspects, the scheduling of the location determination of the mobile anchoring device may be based on the past and expected trajectory of the mobile anchoring device. In certain aspects, the location of the mobile anchoring device used by the location server in its location determination may not be the first location of the target mobile device as determined during the first time window. Instead, the location of the mobile anchoring device used by the location server in its location determination may be based on the first location (as determined during the first time window) and the expected location of the mobile anchoring device (based on the first location (or location history) and its expected trajectory in the positioning environment). In certain aspects, the location server may configure the second time window to occur within the time threshold of the first time window. The mobile anchor device may be expected to be at the first location or within a threshold distance of the first location during the second time window.
[0183] In some aspects, a request to determine the location of a target mobile device at a first scheduled time may indicate a tolerance for deviation from the first scheduled time. In such instances, the location server may adjust the first scheduled time, for example, based on GDOP considerations. Then, the location server may schedule a second time window based on the first scheduled time and the indicated tolerance. If the request does not indicate a tolerance and / or the use of the first scheduled time cannot meet the GDOP considerations, the location server may transmit a request to change the first scheduled time (including any suggested deviation). The requesting client and the location server may then engage in a negotiation to determine other times at which the location of the target mobile device may be determined.
[0184] It may be noted that the anchor used to locate the mobile anchor device may be different from the anchor used to locate the target mobile device. Therefore, the GDOP considerations used by the location server to locate the mobile anchor device may be different from the GDOP considerations used by the location server to locate the target mobile device. Ideally, the time at which the location of the mobile anchor device should be known will be the same as the time at which the mobile anchor performs its PRS transmission and / or measurement to assist in determining the location of the target mobile device. However, this ideal situation may impose conflicting scheduling for PRS transmission and / or measurement. In some aspects, the location server may reconcile such conflicts by scheduling a first time window and a second time window (e.g., two "scheduled location" operations) so that they are within a threshold time of each other, thereby allowing time for separating scheduling conflicts. The location server may also attempt to align the timing of positioning operations performed by two anchor sets (e.g., a first anchor set for determining the location of the mobile anchor device and a second anchor set for determining the location of the target mobile device) to reduce the number of conflicts.
[0185] In one aspect of the present disclosure, a location server (alone or with the assistance of one or more anchoring UEs) determines a first positioning set of one or more mobile anchoring devices based on GDOP considerations for determining the positioning of a target mobile device. The location server performs a positioning operation to determine whether any mobile anchoring device is within a threshold distance of the first positioning set. To this end, the location server may receive positioning information indicating the positioning of one or more mobile anchoring devices from one or more network entities (e.g., anchoring UEs, base stations, etc.) and compare the received positioning information with the first positioning set to determine which (if any) mobile anchoring devices are within a threshold distance of the positioning of the first positioning set. Mobile anchoring devices within the threshold distance are configured by the location server to perform a positioning operation to determine the positioning of the target mobile device. The location server may determine whether the mobile anchoring devices within the threshold distance are capable of performing positioning operations before they are configured.
[0186] In some cases, the location server may not be able to meet the timing requirements for determining the location of the target mobile device at the specified first scheduled time. In such instances, the location server may receive a tolerance for deviation from the first scheduled time and schedule a second time window based on the first scheduled time and the tolerance. As part of this scheduling based on the indicated tolerance, the location server may first transmit a request to the requesting client to change the first scheduled time based on the tolerance.
[0187] According to certain aspects of the present disclosure, a location server may send a control message for moving a mobile anchoring device to a desired location. Such a control message may be communicated directly to the mobile anchoring device or indirectly to an anchoring device that controls the movement of the mobile anchoring device. In certain aspects, the control message may be communicated via an application layer. For example, the location server may configure (directly or indirectly) one or more mobile anchoring devices to move to one or more locations in a first location set. As an example, the location server may transmit a request to one or more network entities requesting the one or more network entities to configure the mobile anchoring device to move to a location in the first location set. In certain aspects, the location server may receive a confirmation message from the network entity indicating that the mobile anchoring device has moved to the desired location. The confirmation message may also indicate the identity of the mobile anchoring device that has moved to the desired location.
[0188] FIG. 10A to FIG. 10D Illustrated is a positioning environment 1000 during an example time window in accordance with aspects of the present disclosure. Fig. 10A The positioning environment 1000 is depicted during the above-mentioned first time window when determining the position of the mobile anchor device 1002. Fig. 10A , the positioning environment includes fixed anchor devices 1004 and 1006 located on a first side of an obstacle 1008 and fixed devices 1010, 1012, and 1014 located on a second side of the obstacle 1008. In this example, the obstacle 1008 blocks radio wave propagation. Here, the location server has determined that the fixed anchor devices 1004, 1006, and 1014 are most suitable for determining the location of the mobile anchor device 1002 (e.g., these devices provide the best unobstructed path and / or expected GDOP characteristics for determining the location of the mobile anchor device 1002). Therefore, the location server configures the fixed anchor devices 1004, 1006, 1014 and the mobile anchor device 1002 to perform positioning operations during a first time window, thereby assisting in determining the location of the mobile anchor device 1002 (here shown as at location 1). Fig. 10A Also shown is a target mobile device 1016 at location 2 located on the same side of the obstacle 1008 as the fixed anchor devices 1006 , 1004 and the mobile anchor device 1002 .
[0189] Fig. 10BA first example of positioning of various devices in the positioning environment 1000 during the second time window described above in accordance with aspects of the present disclosure is shown. Here, the location server has determined that the fixed anchor devices 1004, 1006 and the mobile anchor device 1002 are best suited to determine the location of the target mobile device 1016 (e.g., these devices provide the best unobstructed path and / or desired GDOP characteristics for determining the location of the target mobile device 1016). Therefore, the location server configures the fixed anchor devices 1004, 1006, the mobile anchor device 1002, and the target mobile device 1016 to perform positioning operations during the second time window to assist in determining the location of the target mobile device 1016 (here shown as at location 2). During the second time window, the mobile anchor device 1002 is still located at location 1 (or at least within a threshold distance of location 1).
[0190] Fig. 10C 1000 during the second time window described above according to aspects of the present disclosure. Fig. 10A When compared, the target mobile device 1016 has moved to Fig. 10C 3 in the second time window. Here, the location server has determined that the fixed anchor devices 1010, 1012, 1014 and the mobile anchor device 1002 are best suited to determine the location of the target mobile device 1016 (e.g., these devices provide the best unobstructed path and / or desired GDOP characteristics for determining the location of the target mobile device 1016). Therefore, the location server configures the fixed anchor devices 1010, 1012, 1014, the mobile anchor device 1002, and the target mobile device 1016 to perform positioning operations during the second time window to assist in determining the location of the target mobile device 1016 (here shown as at location 3). During the second time window, the mobile anchor device 1002 is still located at location 1 (or at least within a threshold distance of location 1).
[0191] Fig. 10DA third example of the positioning of various devices in the positioning environment 1000 during the second time window described above in accordance with aspects of the present disclosure is shown. Here, the location server has determined that the mobile anchor device 1002 should move from position 1 to position 4 for operations to be performed during the second time window. For example, the location server may determine that the mobile anchor device 1002 is more suitable for use with the fixed anchor devices 1010, 1012, and 1014 to determine the location of the target mobile device 1016 when it is at position 4 than when it is at position 1 (e.g., the devices at these positions provide the best unobstructed path and / or expected GDOP characteristics for determining the location of the target mobile device 1016). Therefore, the location server may transmit one or more control messages to the mobile anchor device 1002 directly or indirectly through other network entities, which control messages instruct the mobile anchor device 1002 to move to position 4 when the second time window arrives. With the mobile anchor device 1002 correctly located, the location server configures the fixed anchor devices 1004, 1006, the mobile anchor device 1002, and the target mobile device 1016 to perform positioning operations during a second time window to assist in determining the location of the target mobile device 1016 (shown here as at Position 2).
[0192] exist FIG. 10A to FIG. 10D In the example shown in , the target mobile device 1016 is configured to send and / or receive PRS through a location server. However, the disclosed positioning operation can also be extended to object sensing scenarios in which the object has a radio reflective surface. In this regard, wireless communication signals (e.g., RF signals configured to carry OFDM symbols according to wireless communication standards such as LTE, NR, etc.) sent between the UE and the base station can be used for environmental sensing (also known as "RF sensing" or "radar"). The use of wireless communication signals for environmental sensing can be considered as consumer-grade radar with advanced detection capabilities, which enables non-contact / device-free interaction with devices / systems, etc. The wireless communication signal can be a cellular communication signal, such as an LTE or NR signal, a WLAN signal such as a Wi-Fi signal, etc. As a specific example, the wireless communication signal can be an OFDM waveform as utilized in LTE and NR. High-frequency communication signals such as mmW RF signals are particularly beneficial for use as radar signals because higher frequencies at least provide more accurate ranging (distance) detection.
[0193] Possible use cases for RF sensing include health monitoring use cases such as heartbeat detection, respiratory rate monitoring, etc., gesture recognition use cases such as human activity recognition, keystroke detection, sign language recognition, etc., contextual information acquisition use cases such as location detection / tracking, direction finding, ranging estimation, etc., and automotive radar use cases such as smart cruise control, collision avoidance, etc.
[0194] There are different types of sensing, including monostatic sensing (also called "active sensing") and bistatic sensing (also called "passive sensing"). Fig.11A and Fig. 11B These different types of sensing are illustrated. Specifically, Fig.11A is a diagram 1100 illustrating a single-station sensing scenario, and Fig. 11B FIG1130 is a diagram illustrating a bistatic sensing scenario. Fig.11A , a transmitter (Tx) and a receiver (Rx) are co-located in the same device 1104 (e.g., UE). The device 1104 transmits one or more RF sensing signals 1134 (e.g., uplink or sidelink positioning reference signals (PRS) if the device 1104 is a UE), and some of the RF sensing signals 1134 are reflected from one or more reflective RF surfaces of the target object 1106, as shown by reflections 1136. The sensing device 1104 may measure various properties (e.g., time of arrival (ToA), angle of arrival (AoA), phase shift, etc.) of the reflections 1136 of the RF sensing signals 1134 to determine characteristics (e.g., size, shape, speed, motion state, etc.) of the target object 1106.
[0195] exist Fig. 11B In , the transmitter (Tx) and receiver (Rx) are not co-located, i.e., they are separate devices (e.g., UE and base station). Note that although Fig. 11B The use of a downlink RF signal as the RF sensing signal 1132 is illustrated, but an uplink RF signal or a sidelink RF signal may also be used as the RF sensing signal 1132. In the downlink scenario, as shown in the figure, the transmitter device 1102 is a base station and the receiver 1108 is a UE, while in the uplink scenario, the transmitter is a UE and the receiver is a base station.
[0196] For more details, refer to Fig. 11B , the transmitter device 1102 transmits RF sensing signals 1132 and 1134 (e.g., positioning reference signals (PRS)) to the receiver device 1104, but some of the RF sensing signals 1134 are reflected from one or more RF reflective surfaces of the target object 1106. The receiver device 1104 (also referred to as a “sensing device”) may measure the time of arrival (ToA) of the RF sensing signals 1132 received directly from the transmitter device 1102 and the ToA of the RF sensing signals 1134 reflected from the target object 1106, as shown by reflection 1136.
[0197] More specifically, as described above, a transmitter device (e.g., a base station) may transmit a single RF signal or multiple RF signals to a receiver device (e.g., a UE). However, due to the propagation characteristics of RF signals through multipath channels, the receiver may receive multiple RF signals corresponding to each transmitted RF signal. Each path may be associated with a cluster of one or more channel taps. Typically, the time at which the receiver detects the first cluster of channel taps is considered to be the TOA of the RF signal on the site line (LOS) path (i.e., the shortest path between the transmitter and the receiver). Later clusters of channel taps are considered to have been reflected by objects between the transmitter and the receiver, and are therefore along a non-LOS (NLOS) path between the transmitter and the receiver.
[0198] Therefore, returning to the reference Fig. 11B , the RF sensing signal 1132 follows a LOS path between the transmitter device 1102 and the receiver 1108, and the RF sensing signal 1134 follows a NLOS path between the transmitter device 1102 and the receiver 1108 due to reflection from the target object 1106. The transmitter device 1102 may have transmitted multiple RF sensing signals 1132, 1134, some of which follow the LOS path and others of which follow the NLOS path. Alternatively, the transmitter device 1102 may have transmitted a single RF sensing signal in a sufficiently wide beam, a portion of which follows the LOS path (RF sensing signal 1132), and a portion of which follows the NLOS path (RF sensing signal 1134).
[0199] Based on the TOA of the LOS path, the TOA of the NLOS path, and the speed of light, the receiver device can determine the distance to the target object. For example, the receiver device can calculate the distance to the target object as the difference between the TOA of the LOS path and the TOA of the NLOS path multiplied by the speed of light. In addition, if the receiver device is capable of receiving beamforming, the receiver device may be able to determine the approximate direction to the target object as the direction (angle) of the receiving beam on which the RF sensing signal along the NLOS path is received. That is, the receiver device can determine the direction to the target object as the angle of arrival (AoA) of the RF sensing signal, which is the angle of the receiving beam used to receive the RF sensing signal. The receiver device can then optionally report this information to the transmitter device, its serving base station, an application server associated with the core network, an external client, a third-party application, or some other sensing entity. Alternatively, the receiver device can report the ToA measurement results to the transmitter device or other sensing entity (for example, if the receiver device itself does not have the processing power to perform the calculation), and the transmitter device can determine the distance and optionally determine the direction to the target object.
[0200] Note that if the RF sensing signal is an uplink RF signal sent by the UE to the base station, the base station will perform object detection based on the uplink RF signal just like the UE does based on the downlink RF signal.
[0201] As with conventional radar, radar signals based on wireless communication can be used to estimate the range (distance), velocity (Doppler), and angle (AoA) of a target object. However, the performance (e.g., the resolution and maximum value of range, velocity, and angle) may depend on the design of the reference signal.
[0202] Fig.12 An example method 1200 of wireless communication performed by a location server in accordance with aspects of the present disclosure is illustrated. At operation 1202, the location server receives a request to determine a location of a first mobile device at a first scheduled time. In one aspect, operation 1202 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0203] At operation 1204, the location server determines a first location of the second mobile device during the first time window. In one aspect, operation 1204 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0204] At operation 1206, the location server configures the second mobile device to perform positioning operations during a second time window corresponding to the first scheduled time, thereby assisting in determining the position of the first mobile device at the first scheduled time. In one aspect, operation 1206 can be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which can be considered as means for performing the operation.
[0205] As will be appreciated, a technical advantage of method 1200 is that a location server uses a second mobile device in a scheduled determination of a position of a first mobile device at a future time.
[0206] Fig.13An example method 1300 of wireless communication performed by a location server in accordance with aspects of the present disclosure is illustrated. At operation 1302, the location server determines a first set of locations of one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device. In an aspect, operation 1302 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or a location component 398, any or all of which may be considered as means for performing the operation.
[0207] At operation 1304, the location server determines whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations. In one aspect, operation 1304 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0208] At operation 1306, the location server, in response to determining that the at least one second mobile device is within a threshold distance of at least one location in the first location set, configures the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within a threshold distance of at least one location in the first location set. In one aspect, operation 1306 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered means for performing the operation.
[0209] As will be appreciated, a technical advantage of method 1300 is that the location server uses the second mobile device in a scheduled determination of the location of the first mobile device at a future time. In addition, the scheduled determination of the location of the first mobile device is performed when at least one second mobile device is located at a location where the GDOP is optimized.
[0210] Fig.14 An example method 1400 of wireless communication performed by a location server according to aspects of the present disclosure is illustrated. At operation 1402, the location server determines to perform a wireless sensing operation at a first scheduled time to determine the location of a target object. In one aspect, operation 1402 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0211] At operation 1404, the location server determines a first position of the mobile device during the first time window. In one aspect, operation 1404 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0212] At operation 1406, the location server configures the mobile device to transmit the wireless sensing signal during the second time window corresponding to the first scheduled time to assist in determining the location of the target object at the first scheduled time. In one aspect, operation 1406 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered as means for performing the operation.
[0213] As will be appreciated, a technical advantage of method 1400 is that a location server uses a mobile device in a scheduled determination of a location of a target object at a future time.
[0214] In the above detailed description, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause can refer to a specific combination of one clause with other clauses in the clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
[0215] Specific implementation examples are described in the following numbered clauses:
[0216] Clause 1. A method of wireless communication performed by a location server, the method comprising: receiving a request to determine the location of a first mobile device at a first scheduled time; determining a first location of a second mobile device during a first time window; and configuring the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0217] Clause 2. The method of clause 1, further comprising determining the first positioning of the first mobile device based on measurements of one or more positioning reference signals (PRS) sent or received by the second mobile device during the positioning operation and the first positioning of the second mobile device.
[0218] Clause 3. The method of any one of clauses 1 to 2, further comprising determining a schedule indicating a second scheduled time for the first time window during which the first position of the second mobile device is to be determined.
[0219] Clause 4. The method of any one of clauses 1 to 3, further comprising: receiving a tolerance for deviation from the first scheduled time; and scheduling the second time window based on the first scheduled time and the tolerance.
[0220] Clause 5. The method according to clause 4 further comprises: transmitting a request to change the first scheduled time based on the tolerance, wherein the request to change the first scheduled time is based on the determination that the location server is unable to schedule the positioning of the first mobile device at the first scheduled time.
[0221] Clause 6. A method according to any one of clauses 1 to 5, the method further comprising: configuring the second time window to occur within a time threshold of the first time window, wherein the second mobile device is expected to be at the first location or within a threshold distance of the first location during the second time window.
[0222] Clause 7. A method according to any one of clauses 1 to 6, wherein determining the first position of the second mobile device during the first time window includes: configuring a first set of anchor devices to perform a positioning operation during the first time window to determine the first position of the second mobile device.
[0223] Clause 8. The method of clause 7, wherein: the first set of anchoring devices includes fixed anchoring devices at known locations.
[0224] Clause 9. A method according to any one of clauses 7 to 8, the method further comprising: determining the first set of anchor devices based at least in part on a geometric dilution of precision (GDOP) consideration associated with a known position of the first set of anchor devices; and configuring a second set of anchor devices to perform a positioning operation to determine the position of the first mobile device, wherein the second set of anchor devices includes one or more anchor devices different from the first set of anchor devices, wherein the second set of anchor devices is configured to perform the positioning operation during the second time window to determine the position of the first mobile device.
[0225] Clause 10. The method of clause 9, further comprising scheduling the first time window and the second time window based on reconciliation of scheduling conflicts between positioning operations performed by the first set of anchor devices and the second set of anchor devices.
[0226] Clause 11. The method according to any one of clauses 9 to 10, wherein: the second set of anchoring devices are fixed anchoring devices at known locations.
[0227] Clause 12. A method according to any one of clauses 1 to 11, wherein configuring the second mobile device to perform the positioning operation includes: configuring the second mobile device to send a positioning reference signal (PRS) to be measured by the first mobile device during the second time window; configuring the second mobile device to measure one or more PRSs received from the first mobile device during the second time window; or a combination thereof.
[0228] Clause 13. The method according to Clause 12 further includes: receiving a first measurement report from the second mobile device based on the measurement of the one or more PRSs received by the second mobile device from the first mobile device during the second time window; receiving a second measurement report from the first mobile device based on the measurement of the one or more PRSs sent by the second mobile device during the second time window; or a combination thereof.
[0229] Clause 14. The method of any one of clauses 1 to 13, wherein: the second time window is based at least in part on the first position of the second mobile device determined during the first time window.
[0230] Clause 15. A method according to any one of clauses 1 to 14, wherein: the second time window is based on the expected position of the second mobile device during the second time window, and the expected position of the second mobile device during the second time window is based on the first position of the second mobile device during the first time window.
[0231] Clause 16. A method according to any one of clauses 1 to 15, wherein: the second time window is also based on a GDOP consideration for determining the positioning of the first mobile device during the second time window, and the GDOP consideration is based on the expected position of the second mobile device during the second time window and one or more known positions of one or more anchor devices used to determine the positioning of the first mobile device during the second time window.
[0232] Clause 17. The method of any one of clauses 1 to 16, further comprising configuring the second mobile device to move to a second location for use in determining the location of the first mobile device during the second time window.
[0233] Clause 18. The method of Clause 17, wherein configuring the second mobile device to move to the second location comprises transmitting one or more requests to one or more network entities to configure the second mobile device to move to the second location.
[0234] Clause 19. A method according to any one of clauses 17 to 18, wherein: the second position is determined based on a GDOP consideration associated with the second position and one or more known positions of one or more anchoring devices.
[0235] Clause 20. A method of wireless communication performed by a location server, the method comprising: determining a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining a location of a first mobile device; determining whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configuring the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0236] Clause 21. The method of clause 20, further comprising: determining that the at least one second mobile device is capable of performing the positioning operation before configuring the at least one second mobile device to perform the positioning operation.
[0237] Clause 22. A method according to any one of clauses 20 to 21, wherein determining that at least one second mobile device is close to at least one location in the first positioning set includes: receiving positioning information indicating the locations of one or more second mobile devices from one or more network entities; and comparing the positioning information with the first positioning set; and determining that the second mobile device is within a threshold distance of the first positioning set.
[0238] Clause 23. The method of any of clauses 20 to 22, further comprising: configuring one or more second mobile devices to move to one or more locations in the first set of locations.
[0239] Clause 24. A method according to Clause 23, wherein configuring the one or more second mobile devices to move to the one or more locations in the first positioning set includes: transmitting a request to one or more network entities requesting the one or more network entities to configure the one or more second mobile devices to move to the one or more locations in the first positioning set.
[0240] Clause 25. The method of clause 24, further comprising: receiving a confirmation message from at least one of the one or more network entities, the confirmation message indicating that at least one second mobile device has moved to at least one location in the first set of the one or more locations.
[0241] Clause 26. The method of clause 25, wherein: the confirmation message further indicates an identity of the at least one second mobile device that has moved to the at least one location in the first set of the one or more locations.
[0242] Clause 27. A method of wireless communication performed by a location server, the method comprising: determining to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; determining a first position of a mobile device during a first time window; and configuring the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0243] Clause 28. The method of clause 27, further comprising determining the location of the target object based on measurements of the wireless sensing signals by a receiver device and the first location of the mobile device.
[0244] Clause 29. The method of any one of clauses 27 to 28, wherein: the determining the first position of the mobile device at the first scheduled time is based on a request received by the location server.
[0245] Clause 30. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a request to determine the location of a first mobile device at a first scheduled time via the at least one transceiver; determine a first location of a second mobile device during a first time window; and configure the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0246] Clause 31. A location server according to clause 30, wherein the at least one processor is further configured to: determine the first positioning of the first mobile device based on measurements of one or more positioning reference signals (PRS) sent or received by the second mobile device during the positioning operation and the first positioning of the second mobile device.
[0247] Clause 32. A location server according to any one of clauses 30 to 31, wherein the at least one processor is further configured to: determine a schedule indicating a second scheduled time for the first time window, wherein the first position of the second mobile device is to be determined during the first time window.
[0248] Clause 33. A location server according to any one of clauses 30 to 32, wherein the at least one processor is further configured to: receive a tolerance for deviation from the first scheduled time via the at least one transceiver; and schedule the second time window based on the first scheduled time and the tolerance.
[0249] Clause 34. A location server according to clause 33, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a request to change the first scheduled time based on the tolerance, wherein the request to change the first scheduled time is based on the determination that the location server is unable to schedule the positioning of the first mobile device at the first scheduled time.
[0250] Clause 35. A location server according to any one of clauses 30 to 34, wherein the at least one processor is further configured to: configure the second time window to occur within a time threshold of the first time window, wherein the second mobile device is expected to be at the first location or within a threshold distance of the first location during the second time window.
[0251] Clause 36. A location server according to any one of clauses 30 to 35, wherein the at least one processor is configured to determine the first position of the second mobile device during the first time window, including the at least one processor being configured to: configure a first set of anchor devices to perform positioning operations during the first time window to determine the first position of the second mobile device.
[0252] Clause 37. The location server of clause 36, wherein: the first set of anchor devices includes fixed anchor devices at known locations.
[0253] Clause 38. A location server according to any one of clauses 36 to 37, wherein the at least one processor is further configured to: determine the first set of anchor devices based at least in part on geometric dilution of precision (GDOP) considerations associated with the known positions of the first set of anchor devices; and configure a second set of anchor devices to perform a positioning operation to determine the position of the first mobile device, wherein the second set of anchor devices includes one or more anchor devices different from the first set of anchor devices, and wherein the second set of anchor devices is configured to perform the positioning operation during the second time window to determine the position of the first mobile device.
[0254] Clause 39. The location server of clause 38, wherein the at least one processor is further configured to schedule the first time window and the second time window based on reconciliation of scheduling conflicts between positioning operations performed by the first set of anchor devices and the second set of anchor devices.
[0255] Clause 40. The location server of any of clauses 38 to 39, wherein: the second set of anchor devices are fixed anchor devices at known locations.
[0256] Clause 41. A location server according to any one of clauses 30 to 40, wherein the at least one processor is configured to configure the second mobile device to perform the positioning operation, including the at least one processor being configured to: configure the second mobile device to send a positioning reference signal (PRS) to be measured by the first mobile device during the second time window; configure the second mobile device to measure one or more PRSs received from the first mobile device during the second time window; or a combination thereof.
[0257] Clause 42. A location server according to clause 41, wherein the at least one processor is further configured to: receive a first measurement report from the second mobile device via the at least one transceiver based on measurements of the one or more PRSs received by the second mobile device from the first mobile device during the second time window; receive a second measurement report from the first mobile device via the at least one transceiver based on measurements of the one or more PRSs sent by the second mobile device during the second time window; or a combination thereof.
[0258] Clause 43. A location server as described in any of clauses 30 to 42, wherein: the second time window is based at least in part on the first position of the second mobile device determined during the first time window.
[0259] Clause 44. A location server according to any one of clauses 30 to 43, wherein: the second time window is based on an estimated position of the second mobile device during the second time window, and the estimated position of the second mobile device during the second time window is based on the first position of the second mobile device during the first time window.
[0260] Clause 45. A location server according to any one of clauses 30 to 44, wherein: the second time window is also based on a GDOP consideration for determining the position of the first mobile device during the second time window, and the GDOP consideration is based on the expected position of the second mobile device during the second time window and one or more known positions of one or more anchor devices used to determine the position of the first mobile device during the second time window.
[0261] Clause 46. A location server according to any one of clauses 30 to 45, wherein the at least one processor is further configured to: configure the second mobile device to move to a second location for determining the location of the first mobile device during the second time window.
[0262] Clause 47. A location server according to clause 46, wherein the at least one processor is configured to configure the second mobile device to move to the second location, including the at least one processor being configured to: transmit one or more requests to configure the second mobile device to move to the second location to one or more network entities via the at least one transceiver.
[0263] Clause 48. A location server according to any of clauses 46 to 47, wherein: the second position is determined based on a GDOP consideration associated with the second position and one or more known positions of one or more anchor devices.
[0264] Clause 49. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining the location of a first mobile device; determine whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configure the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0265] Clause 50. The location server of Clause 49, wherein the at least one processor is further configured to determine that the at least one second mobile device is capable of performing the positioning operation before the at least one second mobile device is configured to perform the positioning operation.
[0266] Clause 51. A location server according to any one of clauses 49 to 50, wherein the at least one processor is configured to determine that at least one second mobile device is close to at least one location in the first positioning set, including the at least one processor being configured to: receive positioning information indicating the locations of one or more second mobile devices from one or more network entities via the at least transceiver; and compare the positioning information with the first positioning set; and determine that the second mobile device is within a threshold distance of the first positioning set.
[0267] Clause 52. The location server of any of clauses 49 to 51, wherein the at least one processor is further configured to: configure one or more second mobile devices to move to one or more locations in the first set of locations.
[0268] Clause 53. A location server according to clause 52, wherein the at least one processor is configured to configure the one or more second mobile devices to move to the one or more locations in the first positioning set, including the at least one processor being configured to: transmit a request to one or more network entities via the at least one transceiver requesting the one or more network entities to configure the one or more second mobile devices to move to one or more locations in the first positioning set.
[0269] Clause 54. A location server according to clause 53, wherein the at least one processor is further configured to: receive a confirmation message from at least one of the one or more network entities via the at least one transceiver, the confirmation message indicating that at least one second mobile device has moved to at least one location in the first set of the one or more locations.
[0270] Clause 55. The location server of clause 54, wherein: the confirmation message further indicates an identity of the at least one second mobile device that has moved to the at least one location in the first set of the one or more locations.
[0271] Clause 56. A location server, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; determine a first position of a mobile device during a first time window; and configure the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0272] Clause 57. The location server of Clause 56, wherein the at least one processor is further configured to determine the location of the target object based on measurements of the wireless sensing signals by a receiver device and the first location of the mobile device.
[0273] Clause 58. The location server of any one of clauses 56 to 57, wherein: the determining of the first position of the mobile device at the first scheduled time is based on a request received by the location server.
[0274] Clause 59. A location server comprising: a component for receiving a request to determine the location of a first mobile device at a first scheduled time; a component for determining a first location of a second mobile device during a first time window; and a component for configuring the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time to assist in determining the location of the first mobile device at the first scheduled time.
[0275] Clause 60. The location server of clause 59, further comprising: a component for determining the first positioning of the first mobile device based on measurements of one or more positioning reference signals (PRS) sent or received by the second mobile device during the positioning operation and the first positioning of the second mobile device.
[0276] Clause 61. A location server according to any one of clauses 59 to 60, further comprising: a component for determining a schedule indicating a second scheduled time for the first time window, wherein the first position of the second mobile device is to be determined during the first time window.
[0277] Clause 62. A location server according to any one of clauses 59 to 61, further comprising: a component for receiving a tolerance for deviation from the first scheduled time; and a component for scheduling the second time window based on the first scheduled time and the tolerance.
[0278] Clause 63. A location server according to clause 62, wherein the location server further comprises: a component for transmitting a request to change the first scheduled time based on the tolerance, wherein the request to change the first scheduled time is based on the determination that the location server is unable to schedule the positioning of the first mobile device at the first scheduled time.
[0279] Clause 64. A location server according to any one of clauses 59 to 63, wherein the location server further comprises: a component for configuring the second time window to occur within a time threshold of the first time window, wherein the second mobile device is expected to be at the first location or within a threshold distance of the first location during the second time window.
[0280] Clause 65. A location server according to any one of clauses 59 to 64, wherein the component for determining the first position of the second mobile device during the first time window includes: a component for configuring a first set of anchor devices to perform a positioning operation during the first time window in order to determine the first position of the second mobile device.
[0281] Clause 66. The location server of clause 65, wherein: the first set of anchor devices includes fixed anchor devices at known locations.
[0282] Clause 67. A location server according to any one of clauses 65 to 66, wherein the location server further comprises: a component for determining the first set of anchor devices based at least in part on a geometric dilution of precision (GDOP) consideration associated with the known location of the first set of anchor devices; and a component for configuring a second set of anchor devices to perform a positioning operation in order to determine the location of the first mobile device, wherein the second set of anchor devices comprises one or more anchor devices different from the first set of anchor devices, wherein the second set of anchor devices is configured to perform the positioning operation during the second time window to determine the location of the first mobile device.
[0283] Clause 68. The location server of Clause 67, further comprising means for scheduling the first time window and the second time window based on reconciliation of scheduling conflicts between positioning operations performed by the first set of anchor devices and the second set of anchor devices.
[0284] Clause 69. The location server of any of clauses 67 to 68, wherein: the second set of anchor devices are fixed anchor devices at known locations.
[0285] Clause 70. A location server according to any one of clauses 59 to 69, wherein the component for configuring the second mobile device to perform the positioning operation includes: a component for configuring the second mobile device to send a positioning reference signal (PRS) to be measured by the first mobile device during the second time window; a component for configuring the second mobile device to measure one or more PRSs received from the first mobile device during the second time window; or a combination thereof.
[0286] Clause 71. According to the location server described in Clause 70, the location server also includes: a component for receiving a first measurement report from the second mobile device based on the measurement of the one or more PRSs received by the second mobile device from the first mobile device during the second time window; a component for receiving a second measurement report from the first mobile device based on the measurement of the one or more PRSs sent by the second mobile device during the second time window; or a combination thereof.
[0287] Clause 72. A location server as described in any of clauses 59 to 71, wherein: the second time window is based at least in part on the first position of the second mobile device determined during the first time window.
[0288] Clause 73. A location server according to any one of clauses 59 to 72, wherein: the second time window is based on an estimated position of the second mobile device during the second time window, and the estimated position of the second mobile device during the second time window is based on the first position of the second mobile device during the first time window.
[0289] Clause 74. A location server according to any one of clauses 59 to 73, wherein: the second time window is also based on a GDOP consideration for determining the position of the first mobile device during the second time window, and the GDOP consideration is based on the expected position of the second mobile device during the second time window and one or more known positions of one or more anchor devices used to determine the position of the first mobile device during the second time window.
[0290] Clause 75. The location server of any one of clauses 59 to 74, further comprising means for configuring the second mobile device to move to a second location for determining the location of the first mobile device during the second time window.
[0291] Clause 76. The location server of clause 75, wherein the means for configuring the second mobile device to move to the second location comprises means for transmitting one or more requests to one or more network entities to configure the second mobile device to move to the second location.
[0292] Clause 77. A location server according to any one of clauses 75 to 76, wherein: the second position is determined based on GDOP considerations associated with the second position and one or more known positions of one or more anchor devices.
[0293] Clause 78. A location server comprising: a component for determining a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining the location of a first mobile device; a component for determining whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and a component for configuring the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0294] Clause 79. The location server of clause 78, further comprising: means for determining that the at least one second mobile device is capable of performing the positioning operation before the at least one second mobile device is configured to perform the positioning operation.
[0295] Clause 80. A location server according to any one of clauses 78 to 79, wherein the component for determining that at least one second mobile device is close to at least one location in the first positioning set includes: a component for receiving positioning information indicating the location of one or more second mobile devices from one or more network entities; and a component for comparing the positioning information with the first positioning set; and a component for determining that the second mobile device is within a threshold distance of the first positioning set.
[0296] Clause 81. The location server of any of clauses 78 to 80, further comprising means for configuring one or more second mobile devices to move to one or more locations in the first set of locations.
[0297] Clause 82. A location server according to clause 81, wherein the component for configuring the one or more second mobile devices to move to the one or more locations in the first positioning set includes: a component for transmitting a request to one or more network entities requesting the one or more network entities to configure the one or more second mobile devices to move to one or more locations in the first positioning set.
[0298] Clause 83. According to the location server described in Clause 82, the location server also includes: a component for receiving a confirmation message from at least one of the one or more network entities, the confirmation message indicating that at least one second mobile device has moved to at least one location in the first set of the one or more locations.
[0299] Clause 84. The location server of clause 83, wherein: the confirmation message further indicates an identity of the at least one second mobile device that has moved to the at least one location in the first set of the one or more locations.
[0300] Clause 85. A location server comprising: a component for determining to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; a component for determining a first position of a mobile device during a first time window; and a component for configuring the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time to assist in determining the location of the target object at the first scheduled time.
[0301] Clause 86. The location server of clause 85, further comprising: means for determining the location of the target object based on measurements of the wireless sensing signals by a receiver device and the first location of the mobile device.
[0302] Clause 87. A location server as described in any of clauses 85 to 86, wherein: the determining of the first position of the mobile device at the first scheduled time is based on a request received by the location server.
[0303] Clause 88. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a location server, cause the location server to: receive a request to determine a location of a first mobile device at a first scheduled time; determine a first location of a second mobile device during a first time window; and configure the second mobile device to perform a positioning operation during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the first mobile device at the first scheduled time.
[0304] Clause 89. A non-transitory computer-readable medium according to clause 88, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: determine the first positioning of the first mobile device based on measurements of one or more positioning reference signals (PRS) sent or received by the second mobile device during the positioning operation and the first positioning of the second mobile device.
[0305] Clause 90. A non-transitory computer-readable medium according to any one of clauses 88 to 89, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: determine a schedule indicating a second scheduled time for the first time window, wherein the first position of the second mobile device will be determined during the first time window.
[0306] Clause 91. A non-transitory computer-readable medium according to any one of clauses 88 to 90, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: receive a tolerance for deviation from the first scheduled time; and schedule the second time window based on the first scheduled time and the tolerance.
[0307] Clause 92. A non-transitory computer-readable medium according to clause 91, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: transmit a request to change the first scheduled time based on the tolerance, wherein the request to change the first scheduled time is based on the determination that the location server is unable to schedule the positioning of the first mobile device at the first scheduled time.
[0308] Clause 93. A non-transitory computer-readable medium according to any one of clauses 88 to 92, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: configure the second time window to occur within a time threshold of the first time window, wherein the second mobile device is expected to be at the first location or within a threshold distance of the first location during the second time window.
[0309] Clause 94. A non-transitory computer-readable medium as described in any one of clauses 88 to 93, wherein the computer executable instructions that, when executed by the location server, cause the location server to determine the first position of the second mobile device during the first time window include computer executable instructions that, when executed by the location server, cause the location server to perform the following: configure a first set of anchor devices to perform positioning operations during the first time window to determine the first position of the second mobile device.
[0310] Clause 95. The non-transitory computer-readable medium of clause 94, wherein: the first set of anchoring devices comprises fixed anchoring devices at known locations.
[0311] Clause 96. A non-transitory computer-readable medium according to any one of clauses 94 to 95, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: determine the first set of anchor devices based at least in part on geometric dilution of precision (GDOP) considerations associated with the known positions of the first set of anchor devices; and configure a second set of anchor devices to perform a positioning operation to determine the position of the first mobile device, wherein the second set of anchor devices includes one or more anchor devices different from the first set of anchor devices, and wherein the second set of anchor devices is configured to perform the positioning operation during the second time window to determine the position of the first mobile device.
[0312] Clause 97. A non-transitory computer-readable medium according to clause 96, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: schedule the first time window and the second time window based on reconciliation of scheduling conflicts between positioning operations performed by the first set of anchor devices and the second set of anchor devices.
[0313] Clause 98. The non-transitory computer-readable medium of any one of clauses 96 to 97, wherein: the second set of anchoring devices are fixed anchoring devices at known locations.
[0314] Clause 99. A non-transitory computer-readable medium as described in any one of clauses 88 to 98, wherein the computer executable instructions that, when executed by the location server, cause the location server to configure the second mobile device to perform the positioning operation include computer executable instructions that, when executed by the location server, cause the location server to: configure the second mobile device to send a positioning reference signal (PRS) to be measured by the first mobile device during the second time window; configure the second mobile device to measure one or more PRSs received from the first mobile device during the second time window; or a combination thereof.
[0315] Clause 100. A non-transitory computer-readable medium according to clause 99, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: receive from the second mobile device a first measurement report based on measurements of the one or more PRSs received by the second mobile device from the first mobile device during the second time window; receive from the first mobile device a second measurement report based on measurements of the one or more PRSs sent by the second mobile device during the second time window; or a combination thereof.
[0316] Clause 101. The non-transitory computer-readable medium of any one of clauses 88 to 100, wherein: the second time window is based at least in part on the first position of the second mobile device determined during the first time window.
[0317] Clause 102. A non-transitory computer-readable medium as described in any one of clauses 88 to 101, wherein: the second time window is based on an estimated position of the second mobile device during the second time window, and the estimated position of the second mobile device during the second time window is based on the first position of the second mobile device during the first time window.
[0318] Clause 103. A non-transitory computer-readable medium as described in any one of clauses 88 to 102, wherein: the second time window is also based on a GDOP consideration for determining the position of the first mobile device during the second time window, and the GDOP consideration is based on the expected position of the second mobile device during the second time window and one or more known positions of one or more anchor devices used to determine the position of the first mobile device during the second time window.
[0319] Clause 104. A non-transitory computer-readable medium according to any one of clauses 88 to 103, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: configure the second mobile device to move to a second location, thereby determining the location of the first mobile device during the second time window.
[0320] Clause 105. A non-transitory computer-readable medium as described in clause 104, wherein the computer executable instructions that, when executed by the location server, cause the location server to configure the second mobile device to move to the second location include computer executable instructions that, when executed by the location server, cause the location server to perform the following: transmit one or more requests to one or more network entities to configure the second mobile device to move to the second location.
[0321] Clause 106. A non-transitory computer-readable medium as described in any of clauses 104 to 105, wherein: the second position is determined based on a GDOP consideration associated with the second position and one or more known positions of one or more anchor devices.
[0322] Clause 107. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a location server, cause the location server to: determine a first set of locations for one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration for determining the location of a first mobile device; determine whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; and in response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, configure the at least one second mobile device to perform a positioning operation to determine the location of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations.
[0323] Clause 108. According to the non-transitory computer-readable medium described in Clause 107, the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, enable the location server to: determine that the at least one second mobile device is capable of performing the positioning operation before the at least one second mobile device is configured to perform the positioning operation.
[0324] Clause 109. A non-transitory computer-readable medium according to any one of clauses 107 to 108, wherein the computer executable instructions that, when executed by the location server, cause the location server to determine that at least one second mobile device is close to at least one location in the first location set include computer executable instructions that, when executed by the location server, cause the location server to: receive location information indicating the location of one or more second mobile devices from one or more network entities; and compare the location information with the first location set; and determine that the second mobile device is within a threshold distance of the first location set.
[0325] Clause 110. A non-transitory computer-readable medium according to any one of clauses 107 to 109, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: configure one or more second mobile devices to move to one or more locations in the first location set.
[0326] Clause 111. A non-transitory computer-readable medium according to clause 110, wherein the computer executable instructions that, when executed by the location server, cause the location server to configure the one or more second mobile devices to move to the one or more locations in the first location set include computer executable instructions that, when executed by the location server, cause the location server to perform the following: transmit a request to one or more network entities requesting the one or more network entities to configure the one or more second mobile devices to move to one or more locations in the first location set.
[0327] Clause 112. A non-transitory computer-readable medium according to clause 111, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the location server, cause the location server to: receive a confirmation message from at least one of the one or more network entities, the confirmation message indicating that at least one second mobile device has moved to at least one location in the first set of the one or more locations.
[0328] Clause 113. The non-transitory computer-readable medium of Clause 112, wherein: the confirmation message further indicates an identity of the at least one second mobile device that has moved to the at least one location in the first set of the one or more locations.
[0329] Item 114. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location server, cause the location server to: determine to perform a wireless sensing operation at a first scheduled time to determine the location of a target object; determine a first position of a mobile device during a first time window; and configure the mobile device to send a wireless sensing signal during a second time window corresponding to the first scheduled time, thereby assisting in determining the location of the target object at the first scheduled time.
[0330] Clause 115. The non-transitory computer-readable medium of clause 114, wherein the non-transitory computer-readable medium further comprises computer-executable instructions which, when executed by the location server, cause the location server to: determine the location of the target object based on the measurement of the wireless sensing signal by the receiver device and the first location of the mobile device.
[0331] Clause 116. The non-transitory computer-readable medium of any one of clauses 114 to 115, wherein: the determining of the first position of the mobile device at the first scheduled time is based on a request received by the location server.
[0332] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0333] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0334] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.
[0335] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.
[0336] In one or more example aspects, the function can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. Storage media can be any available medium that can be accessed by a computer. Exemplarily and not restrictively, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0337] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.
Claims
1. A method of wireless communication performed by a location server, the method comprising: receiving a request to determine a location of a first mobile device at a first scheduled time; determining a first location of a second mobile device during a first time window; as well as The second mobile device is configured to perform positioning operations during a second time window corresponding to the first scheduled time to assist in determining the position of the first mobile device at the first scheduled time.
2. The method according to claim 1, further comprising: The positioning of the first mobile device is determined based on measurements of one or more positioning reference signals PRS sent or received by the second mobile device during the positioning operation and the first positioning of the second mobile device.
3. The method according to claim 1, further comprising: A schedule is determined indicating a second scheduled time for the first time window during which the first position of the second mobile device is to be determined.
4. The method according to claim 1, further comprising: receiving a tolerance for deviation from the first scheduled time; as well as The second time window is scheduled based on the first scheduled time and the tolerance.
5. The method according to claim 4, further comprising: A request to change the first scheduled time is transmitted based on the tolerance, wherein the request to change the first scheduled time is based on the determination that the location server is unable to schedule the positioning of the first mobile device at the first scheduled time.
6. The method according to claim 1, further comprising: The second time window is configured to occur within a time threshold of the first time window, wherein the second mobile device is expected to be at or within a threshold distance of the first location during the second time window.
7. The method of claim 1 , wherein determining the first location of the second mobile device during the first time window comprises: A first set of anchor devices is configured to perform positioning operations during the first time window to determine the first position of the second mobile device.
8. The method according to claim 7, wherein: The first set of anchoring devices includes fixed anchoring devices at known locations.
9. The method according to claim 7, further comprising: determining the first set of anchor devices based at least in part on a geometric dilution of precision (GDOP) consideration associated with known locations of the first set of anchor devices; as well as A second set of anchor devices is configured to perform a positioning operation to determine the position of the first mobile device, wherein the second set of anchor devices includes one or more anchor devices different from the first set of anchor devices, and wherein the second set of anchor devices is configured to perform the positioning operation during the second time window to determine the position of the first mobile device.
10. The method according to claim 9, further comprising: The first time window and the second time window are scheduled based on reconciliation of scheduling conflicts between positioning operations performed by the first set of anchor devices and the second set of anchor devices.
11. The method according to claim 9, wherein: The second set of anchoring devices are fixed anchoring devices at known locations.
12. The method of claim 1, wherein configuring the second mobile device to perform the positioning operation comprises: configuring the second mobile device to transmit a positioning reference signal PRS to be measured by the first mobile device during the second time window; configuring the second mobile device to measure one or more PRSs received from the first mobile device during the second time window; or A combination of them.
13. The method according to claim 12, further comprising: receiving, from the second mobile device, a first measurement report based on measurements of the one or more PRSs received by the second mobile device from the first mobile device during the second time window; receiving, from the first mobile device, a second measurement report based on measurements of the one or more PRSs sent by the second mobile device during the second time window; or A combination of them.
14. The method of claim 1, wherein: The second time window is based at least in part on the first position of the second mobile device determined during the first time window.
15. The method of claim 1, wherein: The second time window is based on an estimated location of the second mobile device during the second time window, and The estimated position of the second mobile device during the second time window is based on the first position of the second mobile device during the first time window.
16. The method of claim 1, wherein: The second time window is also based on a GDOP consideration used to determine the location of the first mobile device during the second time window, and The GDOP considers an expected position of the second mobile device during the second time window based on one or more known locations of one or more anchor devices used to determine the location of the first mobile device during the second time window.
17. The method according to claim 1, further comprising: The second mobile device is configured to move to a second location for use in determining the location of the first mobile device during the second time window.
18. The method of claim 17, wherein configuring the second mobile device to move to the second location comprises: One or more requests are transmitted to one or more network entities to configure the second mobile device to move to the second location.
19. The method of claim 17, wherein: The second position is determined based on a GDOP consideration associated with the second position and one or more known positions of one or more anchor devices.
20. A method of wireless communication performed by a location server, the method comprising: determining a first set of positions of one or more second mobile devices based on a geometric dilution of precision (GDOP) consideration used to determine the position of the first mobile device; determining whether at least one second mobile device is within a threshold distance of at least one location in the first set of locations; as well as In response to determining that the at least one second mobile device is within the threshold distance of the at least one location in the first set of locations, The at least one second mobile device is configured to perform a positioning operation to determine the position of the first mobile device when the at least one second mobile device is within the threshold distance of the at least one position in the first set of positions.
21. The method according to claim 20, further comprising: It is determined that the at least one second mobile device is capable of performing the positioning operation before configuring the at least one second mobile device to perform the positioning operation.
22. The method of claim 20, wherein determining that at least one second mobile device is proximate to at least one location in the first set of locations comprises: receiving, from one or more network entities, location information indicating the location of one or more second mobile devices; as well as Comparing the positioning information with the first positioning set; as well as It is determined that the second mobile device is within a threshold distance of the first set of location positions.
23. The method according to claim 20, further comprising: One or more second mobile devices are configured to move to one or more locations in the first set of locations.
24. The method of claim 23, wherein configuring the one or more second mobile devices to move to the one or more locations in the first set of locations comprises: A request is transmitted to one or more network entities requesting the one or more network entities to configure the one or more second mobile devices to move to one or more locations in the first set of locations.
25. The method according to claim 24, further comprising: A confirmation message is received from at least one of the one or more network entities, the confirmation message indicating that at least one second mobile device has moved to at least one location in the first set of the one or more locations.
26. The method of claim 25, wherein: The confirmation message further indicates an identity of the at least one second mobile device that has moved to the at least one location in the first set of the one or more locations.
27. A method of wireless communication performed by a location server, the method comprising: determining to perform a wireless sensing operation at a first scheduled time to determine a location of a target object; determining a first location of the mobile device during a first time window; as well as The mobile device is configured to transmit wireless sensing signals during a second time window corresponding to the first scheduled time to assist in determining the location of the target object at the first scheduled time.
28. The method according to claim 27, further comprising: The location of the target object is determined based on measurements of the wireless sensing signals by a receiver device and the first location of the mobile device.
29. The method of claim 27, wherein: Determining the first position of the mobile device at the first scheduled time is based on a request received by the location server.
30. A location server, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a request to determine a location of a first mobile device at a first scheduled time; determining a first location of a second mobile device during a first time window; as well as The second mobile device is configured to perform positioning operations during a second time window corresponding to the first scheduled time to assist in determining the position of the first mobile device at the first scheduled time.
