Patent Description:
In a data communication network, various positioning techniques can be used to determine the position of a mobile device (referred to herein as a user equipment or a UE). Some of these positioning techniques may involve determining distance and/or angular information of RF signals received by one or more base stations of the data communication network. These determinations, however, typically require the mobile device to communicate with multiple base stations. Communicating in this manner can often exceed the power budgets for some low-power mobile devices. <CIT> discloses that the position of User Equipment may be determined based on information communicated through direct UE-to-UE communications to obtain additional measurements of position metrics that can be used to determine relative or absolute positions of the UE. <CIT> discloses a locating method, a system, and a related device where the locating method includes; determining, by a location server, a base station set and an auxiliary UE set that participate in locating of to-be-located target UE, where the to-be-located target UR is any one of a plurality of to-be-located UEs; receiving, by the location server from the to-be-located target UE, a first RSTD set of positioning reference signals PRSs sent by any two base stations in the base station set to the to-be-located target UE, and a second RSTD set of a PRS sent by an auxiliary UE in the auxiliary UE set to the to-be-located target UR and a PRS sent by a reference base station in the base station to set to the to-be-located target UE; and determining location information of base stations included in the base station set. According to embodiments of the present invention, locating accuracy and flexibility can be improved.

Embodiments described herein provide for a high-accuracy determination the position of a first user equipment (UE) using a single base station are presented. This is accomplished by leveraging communications with a second UE having a known location relative to the base station. Wireless reference signals measured by the first UE and second UE, along with a reference signal from the first UE to the second UE (e.g., using a sidelink communication channel), can be used to determine the position of the first UE geometrically. The determination can be made by the first UE, second UE, or a location server, depending on desired functionality. Optional features are defined in the dependent claims.

This summary is neither intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of this disclosure, any or all drawings, and each claim. The foregoing, together with other features and examples, will be described in more detail below in the following specification, claims, and accompanying drawings.

Several illustrative embodiments will now be described with respect to the accompanying drawings, which form a part hereof. While some embodiments in which one or more aspects of the disclosure may be implemented as described below, other embodiments may be used, and various modifications may be made without departing from the scope of the disclosure.

The following description is directed to certain implementations for the purposes of describing innovative aspects of various embodiments. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations may be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency (RF) signals according to any communication standard, such as any of the Institute of Electrical and Electronics Engineers (IEEE) IEEE <NUM> standards (including those identified as Wi-Fi® technologies), the Bluetooth® standard, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals that are used to communicate within a wireless, cellular or internet of things (IoT) network, such as a system utilizing <NUM>, <NUM>, <NUM>, <NUM>, or further implementations thereof, technology.

As used herein, an "RF signal" or "reference signal" comprises an electromagnetic wave that transports information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single "reference signal" or multiple "reference signals" to a receiver. However, the receiver (or different receivers) may receive multiple "reference signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a "multipath" RF signal.

Additionally, unless otherwise specified, references to "reference signals," "positioning reference signals," "reference signals for positioning," and the like may be used to refer to signals used for positioning of a user equipment (UE). As described in more detail herein, such signals may comprise any of a variety of signal types but may not necessarily be limited to a Positioning Reference Signal (PRS) as defined in relevant wireless standards.

<FIG> is a simplified illustration of a positioning system <NUM> in which a UE <NUM>, location server <NUM>, and/or other components of the positioning system <NUM> can use the techniques provided herein for determining and estimated location of UE <NUM>, according to an embodiment. The techniques described herein may be implemented by one or more components of the positioning system <NUM>. The positioning system <NUM> can include: a UE <NUM>; one or more satellites <NUM> (also referred to as space vehicles (SVs)) for a Global Navigation Satellite System (GNSS) such as the Global Positioning System (GPS), GLONASS, Galileo or Beidou; base stations <NUM>; access points (APs) <NUM>; location server <NUM>; network <NUM>; and external client <NUM>. Generally put, the positioning system <NUM> can estimate a location of the UE <NUM> based on RF signals received by and/or sent from the UE <NUM> and known locations of other components (e.g., GNSS satellites <NUM>, base stations <NUM>, APs <NUM>) transmitting and/or receiving the RF signals. Additional details regarding particular location estimation techniques are discussed in more detail with regard to <FIG>.

It should be noted that <FIG> provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated as necessary. Specifically, although only one UE <NUM> is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system <NUM>. Similarly, the positioning system <NUM> may include a larger or smaller number of base stations <NUM> and/or APs <NUM> than illustrated in <FIG>. The illustrated connections that connect the various components in the positioning system <NUM> comprise data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality. In some embodiments, for example, the external client <NUM> may be directly connected to location server <NUM>. A person of ordinary skill in the art will recognize many modifications to the components illustrated.

Depending on desired functionality, the network <NUM> may comprise any of a variety of wireless and/or wireline networks. The network <NUM> can, for example, comprise any combination of public and/or private networks, local and/or wide-area networks, and the like. Furthermore, the network <NUM> may utilize one or more wired and/or wireless communication technologies. In some embodiments, the network <NUM> may comprise a cellular or other mobile network, a wireless local area network (WLAN), a wireless wide-area network (WWAN), and/or the Internet, for example. Examples of network <NUM> include a Long-Term Evolution (LTE) wireless network, a Fifth Generation (<NUM>) wireless network (also referred to as New Radio (NR) wireless network or <NUM> NR wireless network), a Wi-Fi WLAN, and the Internet. LTE, <NUM> and NR are wireless technologies defined, or being defined, by the 3rd Generation Partnership Project (3GPP). Network <NUM> may also include more than one network and/or more than one type of network.

The base stations <NUM> and access points (APs) <NUM> may be communicatively coupled to the network <NUM>. In some embodiments, the base station <NUM> may be owned, maintained, and/or operated by a cellular network provider, and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of the network <NUM>, a base station <NUM> may comprise a node B, an Evolved Node B (eNodeB or eNB), a base transceiver station (BTS), a radio base station (RBS), an NR NodeB (gNB), a Next Generation eNB (ng-eNB), or the like. A base station <NUM> that is a gNB or ng-eNB may be part of a Next Generation Radio Access Network (NG-RAN) which may connect to a <NUM> Core Network (5GC) in the case that Network <NUM> is a <NUM> network. An AP <NUM> may comprise a Wi-Fi AP or a Bluetooth® AP or an AP having cellular capabilities (e.g., <NUM> LTE and/or <NUM> NR), for example. Thus, UE <NUM> can send and receive information with network-connected devices, such as location server <NUM>, by accessing the network <NUM> via a base station <NUM> using a first communication link <NUM>. Additionally or alternatively, because APs <NUM> also may be communicatively coupled with the network <NUM>, UE <NUM> may communicate with network-connected and Internet-connected devices, including location server <NUM>, using a second communication link <NUM>, or via one or more other UEs <NUM>.

As used herein, the term "base station" may generically refer to a single physical transmission point, or multiple co-located physical transmission points, which may be located at a base station <NUM>. A Transmission Reception Point (TRP) (also known as transmit/receive point) corresponds to this type of transmission point, and the term "TRP" may be used interchangeably herein with the terms "gNB," "ng-eNB," and "base station. " In some cases, a base station <NUM> may comprise multiple TRPs - e.g. with each TRP associated with a different antenna or a different antenna array for the base station <NUM>. Physical transmission points may comprise an array of antennas of a base station <NUM> (e.g., as in a Multiple Input-Multiple Output (MIMO) system and/or where the base station employs beamforming). The term "base station" may additionally refer to multiple non-co-located physical transmission points, the physical transmission points may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a Remote Radio Head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical transmission points may be the serving base station receiving the measurement report from the UE <NUM> and a neighbor base station whose reference RF signals the UE <NUM> is measuring.

As used herein, the term "cell" may generically refer to a logical communication entity used for communication with a base station <NUM>, and may be associated with an identifier for distinguishing neighboring cells (e.g., a Physical Cell Identifier (PCID), a Virtual Cell Identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet-of-Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) over which the logical entity operates.

The location server <NUM> may comprise a server and/or other computing device configured to determine an estimated location of UE <NUM> and/or provide data (e.g., "assistance data") to UE <NUM> to facilitate location measurement and/or location determination by UE <NUM>. According to some embodiments, location server <NUM> may comprise a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL user plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for UE <NUM> based on subscription information for UE <NUM> stored in location server <NUM>. In some embodiments, the location server <NUM> may comprise, a Discovered SLP (D-SLP) or an Emergency SLP (E-SLP). The location server <NUM> may also comprise an Enhanced Serving Mobile Location Center (E-SMLC) that supports location of UE <NUM> using a control plane (CP) location solution for LTE radio access by UE <NUM>. The location server <NUM> may further comprise a Location Management Function (LMF) that supports location of UE <NUM> using a control plane (CP) location solution for NR or LTE radio access by UE <NUM>.

The location server <NUM> may further comprise a Location Management Function (LMF) that supports location of UE <NUM> using a control plane (CP) location solution for NR radio access by UE <NUM>. In a CP location solution, signaling to control and manage the location of UE <NUM> may be exchanged between elements of network <NUM> and with UE <NUM> using existing network interfaces and protocols and as signaling from the perspective of network <NUM>. In a UP location solution, signaling to control and manage the location of UE <NUM> may be exchanged between location server <NUM> and UE <NUM> as data (e.g. data transported using the Internet Protocol (IP) and/or Transmission Control Protocol (TCP)) from the perspective of network <NUM>.

As previously noted (and discussed in more detail below), the estimated location of UE <NUM> may be based on measurements of RF signals sent from and/or received by the UE <NUM>. In particular, these measurements can provide information regarding the relative distance and/or angle of the UE <NUM> from one or more components in the positioning system <NUM> (e.g., GNSS satellites <NUM>, APs <NUM>, base stations <NUM>). The estimated location of the UE <NUM> can be estimated geometrically (e.g., using multiangulation and/or multilateration), based on the distance and/or angle measurements, along with known position of the one or more components.

Although terrestrial components such as APs <NUM> and base stations <NUM> may be fixed, embodiments are not so limited. Mobile components may be used. For example, in some embodiments, a location of the UE <NUM> may be estimated at least in part based on measurements of RF signals <NUM> communicated between the UE <NUM> and one or more other UEs <NUM>, which may be mobile or fixed. When or more other UEs <NUM> are used in the position determination of a particular UE <NUM>, the UE <NUM> for which the position is to be determined may be referred to as the "target UE," and each of the one or more other UEs <NUM> used may be referred to as an "anchor UE. " For position determination of a target UE, the respective positions of the one or more anchor UEs may be known and/or jointly determined with the target UE. Direct communication between the one or more other UEs <NUM> and UE <NUM> may comprise sidelink and/or similar Device-to-Device (D2D) communication technologies. Sidelink, which is defined by 3GPP, is a form of D2D communication under the cellular-based LTE and NR standards.

An estimated location of UE <NUM> can be used in a variety of applications - e.g. to assist direction finding or navigation for a user of UE <NUM> or to assist another user (e.g. associated with external client <NUM>) to locate UE <NUM>. A "location" is also referred to herein as a "location estimate", "estimated location", "location", "position", "position estimate", "position fix", "estimated position", "location fix" or "fix". The process of determining a location may be referred to as "positioning," "position determination," "location determination," or the like. A location of UE <NUM> may comprise an absolute location of UE <NUM> (e.g. a latitude and longitude and possibly altitude) or a relative location of UE <NUM> (e.g. a location expressed as distances north or south, east or west and possibly above or below some other known fixed location (including, e.g., the location of a base station <NUM> or AP <NUM>) or some other location such as a location for UE <NUM> at some known previous time, or a location of another UE <NUM> at some known previous time). A location may be specified as a geodetic location comprising coordinates which may be absolute (e.g. latitude, longitude and optionally altitude), relative (e.g. relative to some known absolute location) or local (e.g. X, Y and optionally Z coordinates according to a coordinate system defined relative to a local area such a factory, warehouse, college campus, shopping mall, sports stadium or convention center). A location may instead be a civic location and may then comprise one or more of a street address (e.g. including names or labels for a country, state, county, city, road and/or street, and/or a road or street number), and/or a label or name for a place, building, portion of a building, floor of a building, and/or room inside a building etc. A location may further include an uncertainty or error indication, such as a horizontal and possibly vertical distance by which the location is expected to be in error or an indication of an area or volume (e.g. a circle or ellipse) within which UE <NUM> is expected to be located with some level of confidence (e.g. <NUM>% confidence).

The external client <NUM> may be a web server or remote application that may have some association with UE <NUM> (e.g. may be accessed by a user of UE <NUM>) or may be a server, application, or computer system providing a location service to some other user or users which may include obtaining and providing the location of UE <NUM> (e.g. to enable a service such as friend or relative finder, asset tracking or child or pet location). Additionally or alternatively, the external client <NUM> may obtain and provide the location of UE <NUM> to an emergency services provider, government agency, etc..

As previously noted, the example positioning system <NUM> can be implemented using a wireless communication network, such as an LTE-based or <NUM> NR-based network. <NUM> NR is a wireless RF interface undergoing standardization by the 3rd Generation Partnership Project (3GPP). <NUM> NR is poised to offer enhanced functionality over previous generation (LTE) technologies, such as significantly faster and more responsive mobile broadband, enhanced conductivity through Internet of Things (IoT) devices, and more. Additionally, <NUM> NR enables new positioning techniques for UEs, including Angle of Arrival (AoA)/Angle of Departure (AoD) positioning, UE-based positioning, and multi-cell Round Trip signal propagation Time (RTT) positioning. With regard to RTT positioning, this involves taking RTT measurements between the UE and multiple base stations.

<FIG> shows a diagram of a <NUM> NR positioning system <NUM>, illustrating an embodiment of a positioning system (e.g., positioning system <NUM>) implementing <NUM> NR. The <NUM> NR positioning system <NUM> may be configured to determine the location of a UE <NUM> by using access nodes, which may include NR NodeB (gNB) <NUM>-<NUM> and <NUM>-<NUM> (collectively and generically referred to herein as gNBs <NUM>), ng-eNB <NUM>, and/or WLAN <NUM> to implement one or more positioning methods. The gNBs <NUM> and/or the ng-eNB <NUM> may correspond with base stations <NUM> of <FIG>, and the WLAN <NUM> may correspond with one or more access points <NUM> of <FIG>. Optionally, the <NUM> NR positioning system <NUM> additionally may be configured to determine the location of a UE <NUM> by using an LMF <NUM> (which may correspond with location server <NUM>) to implement the one or more positioning methods. Here, the <NUM> NR positioning system <NUM> comprises a UE <NUM>, and components of a <NUM> NR network comprising a Next Generation (NG) Radio Access Network (RAN) (NG-RAN) <NUM> and a <NUM> Core Network (<NUM> CN) <NUM>. A <NUM> network may also be referred to as an NR network; NG-RAN <NUM> may be referred to as a <NUM> RAN or as an NR RAN; and <NUM> CN <NUM> may be referred to as an NG Core network. The <NUM> NR positioning system <NUM> may further utilize information from GNSS satellites <NUM> from a GNSS system like Global Positioning System (GPS) or similar system (e.g. GLONASS, Galileo, Beidou, Indian Regional Navigational Satellite System (IRNSS)). Additional components of the <NUM> NR positioning system <NUM> are described below. The <NUM> NR positioning system <NUM> may include additional or alternative components.

It should be noted that <FIG> provides only a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as necessary. Specifically, although only one UE <NUM> is illustrated, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the <NUM> NR positioning system <NUM>. Similarly, the <NUM> NR positioning system <NUM> may include a larger (or smaller) number of GNSS satellites <NUM>, gNBs <NUM>, ng-eNBs <NUM>, Wireless Local Area Networks (WLANs) <NUM>, Access and mobility Management Functions (AMF)s <NUM>, external clients <NUM>, and/or other components. The illustrated connections that connect the various components in the <NUM> NR positioning system <NUM> include data and signaling connections which may include additional (intermediary) components, direct or indirect physical and/or wireless connections, and/or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality.

The UE <NUM> may comprise and/or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL)-Enabled Terminal (SET), or by some other name. Moreover, UE <NUM> may correspond to a cellphone, smartphone, laptop, tablet, personal data assistant (PDA), navigation device, Internet of Things (IoT) device, or some other portable or moveable device. Typically, though not necessarily, the UE <NUM> may support wireless communication using one or more Radio Access Technologies (RATs) such as using GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE <NUM> Wi-Fi®, Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX™), <NUM> NR (e.g., using the NG-RAN <NUM> and <NUM> CN <NUM>), etc. The UE <NUM> may also support wireless communication using a WLAN <NUM> which (like the one or more RATs, and as previously noted with respect to <FIG>) may connect to other networks, such as the Internet. The use of one or more of these RATs may allow the UE <NUM> to communicate with an external client <NUM> (e.g., via elements of <NUM> CN <NUM> not shown in <FIG>, or possibly via a Gateway Mobile Location Center (GMLC) <NUM>) and/or allow the external client <NUM> to receive location information regarding the UE <NUM> (e.g., via the GMLC <NUM>). The external client <NUM> of <FIG> may correspond to external client <NUM> of <FIG>, as implemented in or communicatively coupled with a <NUM> NR network.

The UE <NUM> may include a single entity or may include multiple entities, such as in a personal area network where a user may employ audio, video and/or data I/O devices, and/or body sensors and a separate wireline or wireless modem. An estimate of a location of the UE <NUM> may be referred to as a location, location estimate, location fix, fix, position, position estimate, or position fix, and may be geodetic, thus providing location coordinates for the UE <NUM> (e.g., latitude and longitude), which may or may not include an altitude component (e.g., height above sea level, height above or depth below ground level, floor level or basement level). Alternatively, a location of the UE <NUM> may be expressed as a civic location (e.g., as a postal address or the designation of some point or small area in a building such as a particular room or floor). A location of the UE <NUM> may also be expressed as an area or volume (defined either geodetically or in civic form) within which the UE <NUM> is expected to be located with some probability or confidence level (e.g., <NUM>%, <NUM>%, etc.). A location of the UE <NUM> may further be a relative location comprising, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location which may be defined geodetically, in civic terms, or by reference to a point, area, or volume indicated on a map, floor plan or building plan. In the description contained herein, the use of the term location may comprise any of these variants unless indicated otherwise. When computing the location of a UE, it is common to solve for local X, Y, and possibly Z coordinates and then, if needed, convert the local coordinates into absolute ones (e.g. for latitude, longitude and altitude above or below mean sea level).

Base stations in the NG-RAN <NUM> shown in <FIG> may correspond to base stations <NUM> in <FIG> and may include gNBs <NUM>. Pairs of gNBs <NUM> in NG-RAN <NUM> may be connected to one another (e.g., directly as shown in <FIG> or indirectly via other gNBs <NUM>). The communication interface between base stations (gNBs <NUM> and/or ng-eNB <NUM>) may be referred to as an Xn interface <NUM>. Access to the <NUM> network is provided to UE <NUM> via wireless communication between the UE <NUM> and one or more of the gNBs <NUM>, which may provide wireless communications access to the <NUM> CN <NUM> on behalf of the UE <NUM> using <NUM> NR. The wireless interface between base stations (gNBs <NUM> and/or ng-eNB <NUM>) and the UE <NUM> may be referred to as a Uu interface <NUM>. <NUM> NR radio access may also be referred to as NR radio access or as <NUM> radio access. In <FIG>, the serving gNB for UE <NUM> is assumed to be gNB <NUM>-<NUM>, although other gNBs (e.g. gNB <NUM>-<NUM>) may act as a serving gNB if UE <NUM> moves to another location or may act as a secondary gNB to provide additional throughput and bandwidth to UE <NUM>.

Base stations in the NG-RAN <NUM> shown in <FIG> may also or instead include a next generation evolved Node B, also referred to as an ng-eNB, <NUM>. Ng-eNB <NUM> may be connected to one or more gNBs <NUM> in NG-RAN <NUM>-e.g. directly or indirectly via other gNBs <NUM> and/or other ng-eNBs. An ng-eNB <NUM> may provide LTE wireless access and/or evolved LTE (eLTE) wireless access to UE <NUM>. Some gNBs <NUM> (e.g. gNB <NUM>-<NUM>) and/or ng-eNB <NUM> in <FIG> may be configured to function as positioning-only beacons which may transmit signals (e.g., Positioning Reference Signal (PRS)) and/or may broadcast assistance data to assist positioning of UE <NUM> but may not receive signals from UE <NUM> or from other UEs. Some gNBs <NUM> (e.g., gNB <NUM>-<NUM> and/or another gNB not shown) and/or ng-eNB <NUM> may be configured to function as detecting-only nodes may scan for signals containing, e.g., PRS data, assistance data, or other location data. Such detecting-only nodes may not transmit signals or data to UEs but may transmit signals or data (relating to, e.g., PRS, assistance data, or other location data) to other network entities (e.g., one or more components of <NUM> CN <NUM>, external client <NUM>, or a controller) which may receive and store or use the data for positioning of at least UE <NUM>. It is noted that while only one ng-eNB <NUM> is shown in <FIG>, some embodiments may include multiple ng-eNBs <NUM>. Base stations (e.g., gNBs <NUM> and/or ng-eNB <NUM>) may communicate directly with one another via an Xn communication interface. Additionally or alternatively, base stations may communicate directly or indirectly with other components of the <NUM> NR positioning system <NUM>, such as the LMF <NUM> and AMF <NUM>.

<NUM> NR positioning system <NUM> may also include one or more WLANs <NUM> which may connect to a Non-3GPP InterWorking Function (N3IWF) <NUM> in the <NUM> CN <NUM> (e.g., in the case of an untrusted WLAN <NUM>). For example, the WLAN <NUM> may support IEEE <NUM> Wi-Fi access for UE <NUM> and may comprise one or more Wi-Fi APs (e.g., APs <NUM> of <FIG>). Here, the N3IWF <NUM> may connect to other elements in the <NUM> CN <NUM> such as AMF <NUM>. In some embodiments, WLAN <NUM> may support another RAT such as Bluetooth. The N3IWF <NUM> may provide support for secure access by UE <NUM> to other elements in <NUM> CN <NUM> and/or may support interworking of one or more protocols used by WLAN <NUM> and UE <NUM> to one or more protocols used by other elements of <NUM> CN <NUM> such as AMF <NUM>. For example, N3IWF <NUM> may support IPSec tunnel establishment with UE <NUM>, termination of IKEv2/IPSec protocols with UE <NUM>, termination of N2 and N3 interfaces to <NUM> CN <NUM> for control plane and user plane, respectively, relaying of uplink (UL) and downlink (DL) control plane Non-Access Stratum (NAS) signaling between UE <NUM> and AMF <NUM> across an N1 interface. In some other embodiments, WLAN <NUM> may connect directly to elements in <NUM> CN <NUM> (e.g. AMF <NUM> as shown by the dashed line in <FIG>) and not via N3IWF <NUM>. For example, direct connection of WLAN <NUM> to 5GCN <NUM> may occur if WLAN <NUM> is a trusted WLAN for 5GCN <NUM> and may be enabled using a Trusted WLAN Interworking Function (TWIF) (not shown in <FIG>) which may be an element inside WLAN <NUM>. It is noted that while only one WLAN <NUM> is shown in <FIG>, some embodiments may include multiple WLANs <NUM>.

Access nodes may comprise any of a variety of network entities enabling communication between the UE <NUM> and the AMF <NUM>. This can include gNBs <NUM>, ng-eNB <NUM>, WLAN <NUM>, and/or other types of cellular base stations. However, access nodes providing the functionality described herein may additionally or alternatively include entities enabling communications to any of a variety of RATs not illustrated in <FIG>, which may include non-cellular technologies. Thus, the term "access node," as used in the embodiments described herein below, may include but is not necessarily limited to a gNB <NUM>, ng-eNB <NUM> or WLAN <NUM>.

In some embodiments, an access node, such as a gNB <NUM>, ng-eNB <NUM>, and/or WLAN <NUM> (alone or in combination with other components of the <NUM> NR positioning system <NUM>), may be configured to, in response to receiving a request for location information from the LMF <NUM>, obtain location measurements of uplink (UL) signals received from the UE <NUM>) and/or obtain downlink (DL) location measurements from the UE <NUM> that were obtained by UE <NUM> for DL signals received by UE <NUM> from one or more access nodes. As noted, while <FIG> depicts access nodes (gNB <NUM>, ng-eNB <NUM>, and WLAN <NUM>) configured to communicate according to <NUM> NR, LTE, and Wi-Fi communication protocols, respectively, access nodes configured to communicate according to other communication protocols may be used, such as, for example, a Node B using a Wideband Code Division Multiple Access (WCDMA) protocol for a Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using an LTE protocol for an Evolved UTRAN (E-UTRAN), or a Bluetooth® beacon using a Bluetooth protocol for a WLAN. For example, in a <NUM> Evolved Packet System (EPS) providing LTE wireless access to UE <NUM>, a RAN may comprise an E-UTRAN, which may comprise base stations comprising eNBs supporting LTE wireless access. A core network for EPS may comprise an Evolved Packet Core (EPC). An EPS may then comprise an E-UTRAN plus an EPC, where the E-UTRAN corresponds to NG-RAN <NUM> and the EPC corresponds to 5GCN <NUM> in <FIG>. The methods and techniques described herein for obtaining a civic location for UE <NUM> may be applicable to such other networks.

The gNBs <NUM> and ng-eNB <NUM> can communicate with an AMF <NUM>, which, for positioning functionality, communicates with an LMF <NUM>. The AMF <NUM> may support mobility of the UE <NUM>, including cell change and handover of UE <NUM> from an access node (e.g., gNB <NUM>, ng-eNB <NUM>, or WLAN <NUM>)of a first RAT to an access node of a second RAT. The AMF <NUM> may also participate in supporting a signaling connection to the UE <NUM> and possibly data and voice bearers for the UE <NUM>. The LMF <NUM> may support positioning of the UE <NUM> using a CP location solution when UE <NUM> accesses the NG-RAN <NUM> or WLAN <NUM> and may support position procedures and methods, including UE assisted/UE based and/or network based procedures/methods, such as Assisted GNSS (A-GNSS), Observed Time Difference Of Arrival (OTDOA) (which may be referred to in NR as Time Difference Of Arrival (TDOA)), Real Time Kinematic (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhance Cell ID (ECID), angle of arrival (AoA), angle of departure (AoD), WLAN positioning, round trip signal propagation delay (RTT), multi-cell RTT, and/or other positioning procedures and methods. The LMF <NUM> may also process location service requests for the UE <NUM>, e.g., received from the AMF <NUM> or from the GMLC <NUM>. The LMF <NUM> may be connected to AMF <NUM> and/or to GMLC <NUM>. In some embodiments, a network such as 5GCN <NUM> may additionally or alternatively implement other types of location-support modules, such as an Evolved Serving Mobile Location Center (E-SMLC) or a SUPL Location Platform (SLP). It is noted that in some embodiments, at least part of the positioning functionality (including determination of a UE <NUM>'s location) may be performed at the UE <NUM> (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by wireless nodes such as gNBs <NUM>, ng-eNB <NUM> and/or WLAN <NUM>, and/or using assistance data provided to the UE <NUM>, e.g., by LMF <NUM>).

The Gateway Mobile Location Center (GMLC) <NUM> may support a location request for the UE <NUM> received from an external client <NUM> and may forward such a location request to the AMF <NUM> for forwarding by the AMF <NUM> to the LMF <NUM>. A location response from the LMF <NUM> (e.g., containing a location estimate for the UE <NUM>) may be similarly returned to the GMLC <NUM> either directly or via the AMF <NUM>, and the GMLC <NUM> may then return the location response (e.g., containing the location estimate) to the external client <NUM>.

A Network Exposure Function (NEF) <NUM> may be included in 5GCN <NUM>. The NEF <NUM> may support secure exposure of capabilities and events concerning 5GCN <NUM> and UE <NUM> to the external client <NUM>, which may then be referred to as an Access Function (AF) and may enable secure provision of information from external client <NUM> to 5GCN <NUM>. NEF <NUM> may be connected to AMF <NUM> and/or to GMLC <NUM> for the purposes of obtaining a location (e.g. a civic location) of UE <NUM> and providing the location to external client <NUM>.

As further illustrated in <FIG>, the LMF <NUM> may communicate with the gNBs <NUM> and/or with the ng-eNB <NUM> using an NR Positioning Protocol annex (NRPPa) as defined in 3GPP Technical Specification (TS) <NUM>. NRPPa messages may be transferred between a gNB <NUM> and the LMF <NUM>, and/or between an ng-eNB <NUM> and the LMF <NUM>, via the AMF <NUM>. As further illustrated in <FIG>, LMF <NUM> and UE <NUM> may communicate using an LTE Positioning Protocol (LPP) as defined in 3GPP TS <NUM>. Here, LPP messages may be transferred between the UE <NUM> and the LMF <NUM> via the AMF <NUM> and a serving gNB <NUM>-<NUM> or serving ng-eNB <NUM> for UE <NUM>. For example, LPP messages may be transferred between the LMF <NUM> and the AMF <NUM> using messages for service-based operations (e.g., based on the Hypertext Transfer Protocol (HTTP)) and may be transferred between the AMF <NUM> and the UE <NUM> using a <NUM> NAS protocol. The LPP protocol may be used to support positioning of UE <NUM> using UE assisted and/or UE based position methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and/or ECID. The NRPPa protocol may be used to support positioning of UE <NUM> using network based position methods such as ECID, AoA, uplink TDOA (UL-TDOA) and/or may be used by LMF <NUM> to obtain location related information from gNBs <NUM> and/or ng-eNB <NUM>, such as parameters defining DL-PRS transmission from gNBs <NUM> and/or ng-eNB <NUM>.

In the case of UE <NUM> access to WLAN <NUM>, LMF <NUM> may use NRPPa and/or LPP to obtain a location of UE <NUM> in a similar manner to that just described for UE <NUM> access to a gNB <NUM> or ng-eNB <NUM>. Thus, NRPPa messages may be transferred between a WLAN <NUM> and the LMF <NUM>, via the AMF <NUM> and N3IWF <NUM> to support network-based positioning of UE <NUM> and/or transfer of other location information from WLAN <NUM> to LMF <NUM>. Alternatively, NRPPa messages may be transferred between N3IWF <NUM> and the LMF <NUM>, via the AMF <NUM>, to support network-based positioning of UE <NUM> based on location related information and/or location measurements known to or accessible to N3IWF <NUM> and transferred from N3IWF <NUM> to LMF <NUM> using NRPPa. Similarly, LPP and/or LPP messages may be transferred between the UE <NUM> and the LMF <NUM> via the AMF <NUM>, N3IWF <NUM>, and serving WLAN <NUM> for UE <NUM> to support UE assisted or UE based positioning of UE <NUM> by LMF <NUM>.

In a <NUM> NR positioning system <NUM>, positioning methods can be categorized as being "UE assisted" or "UE based. " This may depend on where the request for determining the position of the UE <NUM> originated. If, for example, the request originated at the UE (e.g., from an application, or "app," executed by the UE), the positioning method may be categorized as being UE based. If, on the other hand, the request originates from an external client or AF <NUM>, LMF <NUM>, or other device or service within the <NUM> network, the positioning method may be categorized as being UE assisted (or "network-based").

With a UE-assisted position method, UE <NUM> may obtain location measurements and send the measurements to a location server (e.g., LMF <NUM>) for computation of a location estimate for UE <NUM>. For RAT-dependent position methods location measurements may include one or more of a Received Signal Strength Indicator (RSSI), Round Trip signal propagation Time (RTT), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Time Difference (RSTD), Time of Arrival (TOA), AoA, Receive Time-Transmission Time Difference (Rx-Tx), Differential AoA (DAoA), AoD, or Timing Advance (TA) for gNBs <NUM>, ng-eNB <NUM>, and/or one or more access points for WLAN <NUM>. Additionally or alternatively, similar measurements may be made of sidelink signals transmitted by other UEs, which may serve as anchor points for positioning of the UE <NUM> if the positions of the other UEs are known. The location measurements may also or instead include measurements for RAT-independent positioning methods such as GNSS (e.g., GNSS pseudorange, GNSS code phase, and/or GNSS carrier phase for GNSS satellites <NUM>), WLAN, etc..

With a UE-based position method, UE <NUM> may obtain location measurements (e.g., which may be the same as or similar to location measurements for a UE assisted position method) and may further compute a location of UE <NUM> (e.g., with the help of assistance data received from a location server such as LMF <NUM> or broadcast by gNBs <NUM>, ng-eNB <NUM>, or WLAN <NUM>). With a network based position method, one or more base stations (e.g., gNBs <NUM> and/or ng-eNB <NUM>), one or more APs (e.g., in WLAN <NUM>), or N3IWF <NUM> may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AoA, or ToA) for signals transmitted by UE <NUM>, and/or may receive measurements obtained by UE <NUM> or by an AP in WLAN <NUM> in the case of N3IWF <NUM>, and may send the measurements to a location server (e.g., LMF <NUM>) for computation of a location estimate for UE <NUM>.

Positioning of the UE <NUM> also may be categorized as UL, DL, or DL-UL based, depending on the types of signals used for positioning. If, for example, positioning is based solely on signals received at the UE <NUM> (e.g., from a base station or other UE), the positioning may be categorized as DL based. On the other hand, if positioning is based solely on signals transmitted by the UE <NUM> (which may be received by a base station or other UE, for example), the positioning may be categorized as UL based. Positioning that is DL-UL based includes positioning, such as RTT-based positioning, that is based on signals that are both transmitted and received by the UE <NUM>. Sidelink (SL)-assisted positioning comprises signals communicated between the UE <NUM> and one or more other UEs. According to some embodiments, UL, DL, or DL-UL positioning as described herein may be capable of using SL signaling as a complement or replacement of SL, DL, or DL-UL signaling.

Depending on the type of positioning (e.g., UL, DL, or DL-UL based) the types of reference signals used can vary. For DL-based positioning, for example, these signals may comprise PRS (e.g., DL-PRS transmitted by base stations or SL-PRS transmitted by other UEs), which can be used for TDOA, AoD, and RTT measurements. Other reference signals that can be used for positioning (UL, DL, or DL-UL) may include Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSIRS), synchronization signals (e.g., synchronization signal block (SSB) Synchronizations Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. Moreover, reference signals may be transmitted in a Tx beam and/or received in an Rx beam (e.g., using beamforming techniques), which may impact angular measurements, such as AoD and/or AoA.

<FIG> is a diagram illustrating a simplified environment <NUM> including two base stations <NUM>-<NUM> and <NUM>-<NUM> (which may correspond to base stations <NUM> of <FIG> and/or gNBs <NUM> and/or ng-eNB <NUM> of <FIG>) producing directional beams for transmitting RF reference signals, and a UE <NUM>. Each of the directional beams is rotated, e.g., through <NUM> or <NUM> degrees, for each beam sweep, which may be periodically repeated. Each direction beam can include an RF reference signal (e.g., a PRS resource), where base station <NUM>-<NUM> produces a set of RF reference signals that includes Tx beams <NUM>-a, <NUM>-b, <NUM>-c, <NUM>-d, <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h, and the base station <NUM>-<NUM> produces a set of RF reference signals that includes Tx beams <NUM>-a, <NUM>-b, <NUM>-c, <NUM>-d, <NUM>-e, <NUM>-f, <NUM>-g, and <NUM>-h. Because UE <NUM> may also include an antenna array, it can receive RF reference signals transmitted by base stations <NUM>-<NUM> and <NUM>-<NUM> using beamforming to form respective receive beams (Rx beams) <NUM>-a and <NUM>-b. Beamforming in this manner (by base stations <NUM> and optionally by UEs <NUM>) can be used to make communications more efficient. They can also be used for other purposes, including taking AoD measurements.

AoD can be measured when a base station <NUM> uses beam sweeping to transmit reference signals in each of a plurality of directions, using a respective plurality of beams (e.g., beams <NUM>-a through <NUM>-f). By using RSRP measurements of each reference signal at the UE <NUM>, the beam <NUM> the most aligned with the UE <NUM> can be identified (as one having the highest value). Additional techniques may be performed to determine an accurate AoD based on the alignment. For UE-based positioning, information regarding each beam <NUM> (e.g., beam width and boresight) may be provided to the UE <NUM> to allow the UE to calculate AoD. Alternatively, for UE-assisted positioning, the UE may provide RSRP measurements to a location server <NUM> (e.g., LMF <NUM>), which can use the RSRP measurements and beam information to calculate the AoD.

Network-based positioning of a UE may often require the UE to communicate with a plurality of base stations. In RTT-based positioning, for example RTT measurements can involve transmitting and receiving wireless reference signals with multiple base stations, and further reporting Rx-Tx time difference measurements to a serving base station. With many types of UEs, such as mobile phones, the power requirements of RTT-based positioning may not be an issue. However, with "light" UEs, which typically have a much tighter power budget, these types of communications can be problematic.

As used herein, the term "light" or "low-tier" UE or device refers to a wireless device having a relatively low operating bandwidth, as compared with a "premium" UE or device, which has a relatively high operating bandwidth. Light UEs may also be called "reduced-capability" UEs. For reduced-capability devices in <NUM> NR, 3GPP is developing "NR Light" standards that allow for NR devices with reduced complexity and energy consumption to meet the higher latency and data rate acquirements in a <NUM> NR environment (as compared with narrowband IoT (NB-IoT) or LTE-M in and LTE environment). As such, references to light or low tier UEs or devices herein may refer to <NUM> NR devices using NR Light, and references to premium UEs or devices herein may refer to <NUM> NR devices using standard NR. Examples of light UEs can include wearable devices (e.g., smart watches), relaxed/narrowband IoT devices, low-end mobile phones, and the like. The current operating bandwidth of these devices is roughly <NUM>-<NUM> megahertz (MHz), although some low-tier UEs may have a higher or lower operating bandwidth. Examples of premium UEs may comprise high-end mobile phones (e.g., smart phones), tablets, vehicles, and the like. Premium UEs currently operate at a bandwidth of <NUM> or more. Generally speaking, light UEs have a relatively lower bandwidth (e.g., less than <NUM>), lower processing capabilities, and/or lower power budgets than premium UEs.

As noted, network-based positioning often requires communication with multiple base stations. For example, high-accuracy positioning determinations (e.g. with an accuracy of <NUM> or less) often require multi-RTT, in which RTT measurements are made between a UE and multiple base stations. However, the power requirements of communicating with multiple base stations can often be burdensome to light UEs. Moreover, light UEs may be incapable of obtaining reference signals (e.g., PRS) from multiple base stations due to antenna loss, low bandwidth, fewer antennas, and reduced baseband capabilities, compared with premium UEs. Additionally, light UEs have a reduced transmit power, which can result in a lower quality uplink (UL) measurement at the base station of an RF signal transmitted by a light UE.

Embodiments provided herein address these and other issues by providing techniques in which the position of a light UE may be determined with high accuracy using a single base station. This is accomplished by leveraging a premium UE having a known location relative to the base station. Techniques can be used for UE-assisted and UE-based positioning. <FIG> helps illustrated how this is accomplished.

<FIG> is a simplified diagram illustrating how a network-based position determination of a light UE <NUM> may be made using a single base station <NUM> (e.g., the serving base station of the light UE <NUM> and/or premium UE <NUM>), according to an embodiment. Here, positioning of the light UE <NUM> is accomplished using communications with a premium UE <NUM>, where both light UE <NUM> and premium UE <NUM> receive reference signals <NUM>, <NUM> from the base station <NUM>. This positioning may be facilitated with the use of a location server <NUM>.

The position of the light UE <NUM> can be determined mathematically by solving for the distance, RT, of the light UE <NUM> from the base station <NUM>, as well as angle, θT. It can be noted that the baseline from which the angle θT is measured may be measured from true north or based on any coordinate system used by the network for positioning (e.g., geographical coordinates, East-North-Up (ENU), etc.). Solving for these two variables can be accomplished with the help of the premium UE <NUM>, which can measure a reference signal <NUM>, as well as a sidelink signal <NUM> provided by the light UE <NUM> in response to the light UE receiving reference signal <NUM>.

The distance RT can be determined based on a time difference at the premium UE <NUM> of receiving the reference signal <NUM> and sidelink signal <NUM>. Where Rsum is the combined distance of distance RT and the distance, RR, between the light UE <NUM> and premium UE <NUM>, then solving for RT results in the following expression: <MAT>.

If L is defined as the distance between the base station <NUM> and premium UE <NUM>, then equation (<NUM>) can be modified as follows: <MAT>.

Because the location of the premium UE <NUM> is known (or can be determined beforehand), distance L and angle θR can be obtained based on this premium UE location and the known location of the base station <NUM> (e.g., from an almanac of base station locations stored by the location server <NUM> and/or premium UE <NUM>). Additionally, as explained in further detail below, θT can be determined from an AoD measurement of a reference signal transmitted by the base station <NUM> (which may be different than the reference signal <NUM> used to determine distance RT) Thus, once Rsum is determined, range RT can be determined using equation (<NUM>).

To solve for Rsum, embodiments can determine differences in times at which the reference signal <NUM> is received at the light UE <NUM> and reference signal <NUM> is received at premium UE <NUM>. The sidelink signal <NUM> sent from the light UE <NUM> to the premium UE <NUM> can be triggered by the receipt of the reference signal <NUM> at the light UE <NUM>, and a time at which the reference signal <NUM> is received at the light UE <NUM> can be relayed to the premium UE <NUM> using a sidelink connection as well. An illustration of this is provided in <FIG>.

<FIG> is a time-distance diagram illustrating how timing can be used to determine Rsum in the configuration shown in <FIG>, according to an embodiment. Here, a base station <NUM> transmits reference signals <NUM> and <NUM> (e.g., a DL-PRS), which our received by both the light UE <NUM> (which receives reference signal <NUM> first) and the premium UE <NUM>. The different angles of reference signals <NUM> and <NUM> in <FIG> reflect the different paths of reference signals <NUM> and <NUM> in <FIG>.

As explained in further detail below, reference signal <NUM> and reference signal <NUM> may comprise the same or different reference signals. (Because reference signals <NUM> and <NUM> in <FIG> are illustrated as being transmitted at the same time, this would be reflective of transmission of a single reference signal. But embodiments are not so limited. ) The location server <NUM> may coordinate the transmission and measurement of the reference signal(s) by providing information to the base station <NUM> regarding how to transmit the reference signal(s), as well as information to the light UE <NUM> and premium UE <NUM> regarding when to measure the reference signal(s).

Because reference signals travel at approximately the speed of light, c, the value for Rsum can be determined from: <MAT> where TRx_sidelink is the time (ToA) at which the sidelink signal <NUM> is received by the premium UE, TRx_RS is the time (ToA) at which the reference signal <NUM> is received by the premium UE, and TUE_Rx→Tx is the Time difference between the time (ToA) at which the light UE <NUM> receives the reference signal <NUM> and the time at which the light UE <NUM> transmits the sidelink signal <NUM>. With the value of Rsum, distance RT can be determined from equation (<NUM>) above, and the position of the light UE <NUM> can be determined based on distance RT, angle θT, and the position of the base station <NUM>. Because the value of Rsum is based on a difference between times at which the light UE <NUM> and premium UE <NUM> receive the reference signal, no synchronization is required between the light UE <NUM>, premium UE <NUM>, or base station <NUM> to perform the positioning of the light UE <NUM> using the techniques described herein.

As noted, depending on desired functionality, a single reference beam may be used for the determination of distance Rsum as described in relation to <FIG> and <FIG>. <FIG> illustrate an example of this.

<FIG> are diagrams of a base station <NUM>, light UE <NUM>, and premium UE <NUM> similar to those shown in <FIG>, provided to illustrate how beams may be used differently in different embodiments and/or situations, depending on desired functionality. In <FIG>, for example, a single reference signal beam <NUM> is wide enough to be received by both light UE <NUM> and premium UE <NUM>, allowing it to be used in the previously-described process regarding determining Rsum. As can be seen, whether the reference signal beam <NUM> is sufficiently wide may depend not only on the width of the reference signal beam, but also how close the light UE <NUM> and the premium UE <NUM> are to each other. (In some instances, for example, the light UE <NUM> and premium UE <NUM> may be sufficiently close such that a relatively narrow beam - as illustrated in <FIG>, for example - may be used by both the light UE <NUM> and premium UE <NUM>. ) In <FIG>, however, the light UE <NUM> is aligned with a first reference signal beam <NUM>, and a premium UE <NUM> is more aligned with a second reference signal beam <NUM>. In such instances, even if the premium UE <NUM> is capable of detecting both first reference signal beam <NUM> and a second reference signal beam <NUM>, it may be preferable for the premium UE <NUM> to take a ToA measurement of the second reference signal beam <NUM>, rather than the first reference signal beam <NUM> (e.g., due to more favorable SNR values to take a ToA measurement). Although reference signal beams <NUM>, <NUM> may be transmitted at different times, because the time difference in the transmission of first reference signal beam <NUM> and the second reference signal beam <NUM> is known, this time difference can be accounted for in equation (<NUM>), allowing for the determination of Rsum in cases where different reference signal beams transmitted at different times are used.

The calculation of the position of the light UE <NUM> and/or values distance RT and angle θT may be performed by different entities, depending on desired functionality. This may depend, for example, on whether the position of the light UE <NUM> is UE-based (e.g., where the request for the position of the light UE <NUM> comes from the light UE <NUM> itself) or whether it is UE-assisted (e.g., where the request for the position of the light UE <NUM> comes from the network or other entity outside the light UE, such as the external client <NUM> of <FIG> or external client <NUM> of <FIG>). Accordingly, different processes can be used to determine the position of the light UE <NUM>. <FIG> illustrate some example processes.

<FIG> is a call-flow diagram illustrating an embodiment of a process of performing UE-based position determination of a light UE <NUM>, in which some calculations are offloaded to the premium UE <NUM>. As with the other figures provided herein, FI GP. <NUM> is provided as a nonlimiting example. As discussed in more detail below, alternative embodiments may perform certain functions (e.g., the determination of the premium UE position, the AoD measurement, the ToA measurements, etc.) in a different order, simultaneously, etc. It can be noted that arrows between the various components illustrated in <FIG> illustrate messages or information sent from one component to another. It will be understood, however, that there may be any number of intervening devices, servers, etc. that may relay such messages, including other components in <FIG>. , a message from the light UE <NUM> to the location server <NUM> may pass through the base station <NUM> and perhaps the premium UE <NUM>. ) Additionally, although wireless reference signals are referred to as PRS (e.g., DL-PRS transmitted by the base station <NUM>), alternative embodiments may utilize other wireless reference signal types.

At block <NUM>, the light UE <NUM> obtains a position request. This position request may come, for example, from an application (or app) executed by the light UE <NUM>. This may be a result from user interaction with the light UE <NUM>, based on a determined schedule, or based on other triggers. Additionally or alternatively, a position request may come from a separate device (e.g., it the premium UE <NUM> or another device in communication with the light UE <NUM>) requesting the position of the light UE <NUM>.

In response, the light UE <NUM> may generate a position request notification. As indicated at arrow <NUM>, the request can be sent to the location server <NUM>, which can coordinate the functionality of the various components illustrated in <FIG> to determine of the position of the light UE <NUM>. According to some embodiments, additional communications between the light UE <NUM> and location server <NUM> may occur to determine capabilities of the light UE <NUM> (including, for example, the capability of the light UE <NUM> to communicate with the premium UE <NUM>). In some embodiments, communication between the location server <NUM> and light UE <NUM> may occur via an LPP positioning session.

As illustrated, according to some embodiments the position request notification may additionally be sent to the premium UE <NUM>. This can notify the premium UE <NUM> of the position request received by the light UE <NUM> (at block <NUM>) and trigger the premium UE <NUM> to obtain its position information, at block <NUM>. Here, too, the position request notification provided to the premium UE <NUM> may be part of a larger communication exchange in which positioning capabilities are shared between the light UE <NUM> and premium UE <NUM>. According to some embodiments, location between the light UE <NUM> and premium UE <NUM> may occur over an existing sidelink connection. Alternatively, a new sidelink connection may be created in response to the position request received at block <NUM>. According to some embodiments, rather than the light UE <NUM> providing the position request notification at arrow <NUM>, the notification may be provided by the location server <NUM>, in response to the location server's receipt of the position request notification at arrow <NUM>.

The selection of a premium UE <NUM> to use in the position determination of the light UE <NUM> may be made in any of a variety of ways, depending on desired functionality. For example, as noted, the light UE <NUM> may have an existing sidelink communication channel with a premium UE <NUM> that can be leveraged for positioning purposes. In such instances, the premium UE <NUM> may be selected based on an existing sidelink channel. Additionally or alternatively, the premium UE <NUM> may be selected by the light UE <NUM> based on a scan of nearby premium UEs as well as a confirmed capability of performing positioning and this manner. Some embodiments may use a signal quality metric such as SNR and/or RSSI, for example, to select of the premium UE <NUM>. Signal quality measures can be used to select a premium UE <NUM> that has adequate signal quality to perform the functions described herein, while not being too close to the light UE <NUM> to result in positioning errors for the position determination of the light UE <NUM>. Accordingly, in such embodiments, a certain range of SNR and/or RSSI values may be selected to balance these considerations, and premium UEs having SNR and/or RSSI values that fall within this range may be selected over other premium UEs having SNR and/or RSSI values falling outside this range. Other embodiments may utilize additional or alternative techniques for premium UE selection.

At block <NUM>, the premium UE <NUM> determines its location. This can be performed in any of a variety of ways, including GNSS and/or other non-network means. Additionally or alternatively, position determination for the premium UE <NUM> can be network-based and may involve the location server <NUM>. In such instances, the premium UE <NUM> may request assistance data, as indicated by arrow <NUM>, and the location server <NUM> may send the requested assistance data at arrow <NUM>. In some embodiments, the premium UE <NUM> may obtain a high-accuracy position determination based on, for example, multi-RTT positioning based on communication with a plurality of base stations (which may include communication with the base station <NUM>). For multi-RTT positioning, assistance data may include a location of each base station with which RTT measurements are made.

As indicated by arrow <NUM>, the location server can then schedule the transmission and receipt of PRS resources by the base station <NUM>, premium UE <NUM>, and the light UE <NUM>. According to embodiments, this may include the scheduling of PRS for both the measurement of RSRP by the light UE <NUM> (at block <NUM>) and the measurement of ToA (at blocks <NUM> and <NUM>) by both the light UE <NUM> and premium UE <NUM>. Alternatively, these different PRS may be scheduled at different times. The scheduling of PRS resources may also involve the location server <NUM> configuring the base station <NUM> to provide assistance data to the light UE <NUM> for AoD determination. In some embodiments, the base station <NUM> may configure the premium UE <NUM> and/or light UE <NUM> to measure the PRS. (In such instances, the scheduling of PRS resources may be viewed as being sent from the base station <NUM>, rather than the location server <NUM>, to the premium UE <NUM> and/or light UE <NUM>.

At arrow <NUM>, the assistance data is sent from the base station <NUM> to the light UE <NUM>. Here, the assistance data can be used to enable the light UE <NUM> to determine the AoD based on an RSRP measurement of a PRS transmitted by the base station <NUM>. As such, it may include beam width and boresight information of the PRS. Timing and/or other information regarding the PRS may be included in the assistance data as well.

At block <NUM>, the base station <NUM> transmits the PRS, which is measured by the light UE <NUM> in an RSRP measurement, as indicated at block <NUM>. As previously indicated, the base station <NUM> may transmit the PRS as part of a beam sweep, in which different PRS resources are transmitted using different beams. In this way, the resulting measured RSRP at block <NUM> may indicate the beam with which the light UE <NUM> is most closely aligned (e.g., the beam corresponding to the PRS having the highest RSRP value). The light UE <NUM> can then determine the AoD, at block <NUM>, using the measured RSRP values and assistance data. As previously noted, the AoD may correspond with (or used to be determine) angle θT of <FIG>.

As an alternative to the light UE <NUM> determining the AoD, the determination of the AoD may be made by the premium UE <NUM>, according to some embodiments. This can reduce the amount of computation (and corresponding processing resources and power) performed by the light UE <NUM>. In such embodiments, the RSRP measurements may be provided to the premium UE <NUM>, which went may determine the AoD based on the RSRP measurements and assistance data. (In these embodiments, the assistance data would be provided by the base station <NUM> or location server <NUM> to the premium UE <NUM>, rather than the light UE <NUM>, at arrow <NUM>.

The determined AoD can then be sent to the premium UE <NUM>, as indicated by arrow <NUM>, to enable the premium UE <NUM> to subsequently calculate the position of the light UE <NUM>. Optionally, the determined AoD (and/or an indication of the beam with which the light UE <NUM> is most closely aligned) can be sent to the base station <NUM> (as shown at arrow <NUM>). This can be to indicate to the base station <NUM> which beam to subsequently use when sending PRS to the light UE <NUM> for ToA measurements. Because the premium UE <NUM> may be closer to the light UE <NUM> then the base station <NUM>, the light UE <NUM> can save power by transmitting to the premium UE <NUM>, rather than transmitting directly to the base station <NUM>. Thus, the AoD and/or beam used may be sent from the light UE <NUM> to the premium UE <NUM>, which then relays the information to the base station <NUM>.

At arrow <NUM>, the base station <NUM> can then send PRS, which can be measured by the premium UE <NUM> and light UE <NUM> as previously described and illustrated in <FIG>. More particularly, the premium UE <NUM> measures the ToA of the PRS at block <NUM>, and at block <NUM> the light UE <NUM> measures the ToA of the PRS and determines an Rx-Tx time difference (e.g. TUE_Rx→Tx of <FIG>) between a time the PRS is received at the light UE <NUM> and a time the light UE transmits a PRS (at arrow <NUM>) to be received by the premium UE <NUM>. As noted in the previously-described embodiments, alternative embodiments may send a different PRS (e.g., a PRS resource using a different beam) for ToA measurement at block <NUM> than the PRS received by the light UE <NUM> block <NUM>.

At arrow <NUM>, the light UE <NUM> then sends a PRS to the premium UE <NUM>, along with the Rx-Tx time difference. As previously described, the PRS may comprise a signal (e.g., sidelink signal <NUM>) sent via a sidelink communication channel. This can comprise, for example, a sidelink PRS (SL-PRS), or other reference signal that can provide for an accurate ToA measurement by the premium UE <NUM>.

At block <NUM>, the premium UE <NUM> determines the position of the light UE <NUM>. More specifically, using the AoD received at arrow <NUM> and determining the distance (RT) of the light UE <NUM> from the base station <NUM> (e.g., using equation (<NUM>) above), and a known location for the base station <NUM>, the premium UE <NUM> can determine the position of the light UE <NUM>. This determined position can then be sent to the light UE, as indicated by arrow <NUM>. The known location of the base station <NUM> may be obtained by the premium UE <NUM> based on an almanac of base station locations, which may be stored at the premium UE <NUM> (and used for positioning of the premium UE <NUM>, for example) or location server <NUM>. If stored at the location server <NUM>, the location server may provide the location of the base station <NUM> as assistance data in previous communications (e.g., at arrow <NUM>, arrow <NUM>, or separately-communicated assistance data (not shown)).

<FIG> is call-flow diagram illustrating an embodiment of another process of performing UE-based position determination of a light UE <NUM>. In contrast to the process illustrated in <FIG>, however, calculations and position determination are performed at the light UE <NUM> itself. As can be seen, many of the operations performed in the process of <FIG> may be similar to the operations performed in the process of <FIG>.

The position request at block <NUM> and position request notification at arrow <NUM> may be similar to corresponding operations in <FIG>. In this embodiment, however, the position request is provided directly to the location server <NUM>, which obtains the position information for the premium UE at block <NUM>. Again, communications to the location server <NUM> may be relayed through the premium UE <NUM> to reduce the amount of transmission power for the light UE <NUM> required to send the position request notification at arrow <NUM>. In such instances, the position request notification may be sent via a sidelink communication channel between the light UE <NUM> and premium UE <NUM>.

As illustrated, obtaining the position information for the premium UE at block <NUM> may optionally include a positioning session between the location server <NUM> and premium UE <NUM>, as indicated by arrow <NUM>. For example, the location server <NUM> may request to the position of the premium UE <NUM>, which may be provided to the location server <NUM>, if known. Otherwise, UE-assisted positioning of the premium UE <NUM> may be performed. When the position of the premium UE <NUM> is obtained, the location server <NUM> can then send the position information to the light UE <NUM>, as indicated at block <NUM>.

As indicated at arrow <NUM>, the location server <NUM> can schedule PRS resources, as described previously in regard to <FIG>. This can result in the base station <NUM> sending assistance data to the light UE <NUM>, as indicated at arrow <NUM>. Further, the assistance data may also include a location of the base station <NUM>, which (along with the position of the premium UE <NUM>) can be subsequently used to determine the position of the light UE <NUM>.

The elements <NUM>-<NUM> may be similar to corresponding actions in <FIG>. One difference is that in the process of <FIG>, the AoD is not needed by the premium UE <NUM> for determining the position of the light UE <NUM> (because the light UE <NUM> determines its own location). Accordingly, the action at arrow <NUM> is optional. Unless, the light UE <NUM> may send the AoD or been used to the premium UE <NUM> so that the premium UE can relay this information to the base station (at arrow <NUM>), which may impact how the PRS is sent at arrow <NUM>, as previously noted.

At block <NUM>, rather than calculate the location of the light UE <NUM>, the premium UE <NUM> can determine the time difference of the ToAs (e.g., TRx_sidelink - TRx_RS, of equation (<NUM>) and <FIG>), which can be provided to the light UE <NUM>, as indicated at arrow <NUM>. With this information, along with the AoD and location information for the premium UE <NUM> and base station <NUM>, the light UE <NUM> can determine its position, as shown at block <NUM>, in the manner described above.

<FIG> is call-flow diagram illustrating an embodiment of a process of performing UE-assisted position determination of a light UE <NUM>. Here, calculations and position determination are performed at the location server <NUM>, based on information received from the premium UE <NUM> and light UE <NUM>. Many of the operations performed in the process of <FIG> may be similar to the operations performed in the processes of <FIG> and <FIG>, as previously described.

This process may begin with a position request obtained at the location server <NUM>, as indicated at block <NUM>. As indicated previously, UE-assisted (or network-based) positioning can be based on a request from an external client (e.g., external client <NUM> of <FIG> and/or external client <NUM> of <FIG>). Additionally or alternatively, the request may come from a service within the wireless network that may need the position of the light UE <NUM> to provide particular functionality.

In response to the position request, the location server <NUM> may notify the light UE <NUM> and (optionally) premium UE <NUM> of the position request via position request notification, as indicated at arrow <NUM>. In some embodiments, this may comprise initiating a communication session between the location server <NUM> and light UE <NUM>, and/or between the location server <NUM> and premium UE <NUM>.

Elements <NUM>-<NUM> may be similar to corresponding features in <FIG>, as previously described. In <FIG>, the determination of the AoD may be made by the light UE <NUM> or by the location server <NUM>. If the determination is made by the location server <NUM>, the light UE <NUM> can provide RSRP measurements to the location server <NUM>, as shown in arrows <NUM>, and the assistance data does not need to be sent from the base station <NUM> the light UE <NUM> at arrow <NUM>. (Again, this may be sent via the premium UE <NUM>, which may result in reduced transmission power. ) Otherwise, the assistance data can be sent by the base station <NUM>, and the AoD may be determined by the light UE <NUM> at block <NUM>, using the assistance data, and sent to the location server <NUM> (at arrow <NUM>). As with the processes illustrated in <FIG> and <FIG>, the RSRP measurement and/or AoD determination can be sent to the base station <NUM>, which may inform which beam to use when sending the PRS at arrow <NUM>.

Elements <NUM>-<NUM> may be similar to corresponding elements in <FIG>. The difference in <FIG>, however, is that the time difference is sent from the premium UE <NUM> to the location server <NUM> (rather than to the light UE <NUM>), at arrow <NUM>. With this information, the location server <NUM> can then determine the position of the light UE, at block <NUM>.

<FIG> is a simplified diagram illustrating a variation to the configuration illustrated in <FIG>, which may be performed according to embodiments. Here, rather than a single premium UE <NUM>, multiple premium UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> (collectively and generically referred to herein simply as premium UEs <NUM>) are used.

The process of determining the location of the light UE <NUM> may be generally similar to the process illustrated in <FIG> and described in conjunction with <FIG>. However, because multiple premium UEs <NUM> are used, angle information may not be needed. That is, rather than (or in addition to) determining the position of the light UE <NUM> using distance RT and angle θT, the position may be determined instead using multilateration. That is, each premium UE <NUM> can receive a respective sidelink signal <NUM> from the light UE <NUM>, as well as a direct reference signal from the base station <NUM> (similar to reference signal <NUM> and <FIG>) to determine a respective determine Rsum using equation (<NUM>). (To reduce clutter, direct reference signals are not illustrated in <FIG>. ) Because Rsum is the sum of RT and the respective RR for each premium UE <NUM>, the value of Rsum can be used to form a respective ellipse <NUM> for each premium UE <NUM> in which the base station <NUM> and premium UE <NUM> are foci of the respective ellipse. (Again, to reduce clutter, only applicable portions of ellipses <NUM> are illustrated in <FIG>) The device determining the location of the light UE <NUM> (e.g., the light UE <NUM>, any/all of the premium UEs <NUM>, or the location server <NUM> (not illustrated in <FIG>)) may do so by determining the pointed which the ellipses <NUM> converge. As such, no AoD or other angular determinations may be needed. Even so, according to some embodiments, an AoD may be determined and sent to the base station <NUM> as described previously (e.g., relating to actions <NUM>-<NUM> of <FIG>) to enable the base station <NUM> to select a beam with which to transmit the reference signal <NUM>.

The number of premium UEs <NUM> used to determine the position of the light UE <NUM> in this manner may vary, depending on the situation. A larger or smaller number of premium UEs <NUM> than illustrated in <FIG>, for example, can be used. In some circumstances, such as when two premium UEs <NUM> are used, there may be ambiguities (e.g., multiple convergence points) in the position of the light UE <NUM>. In such instances, other data can be leveraged to resolve the ambiguities. This other data can include, for example, tracking information for the light UE <NUM>, other (previous and/or simultaneous) position determinations for the light UE <NUM>, or the like.

It can be noted that embodiments for determining the location of the light UE <NUM> in the manner illustrated in <FIG> may follow a similar process as those illustrated in <FIG>. (As noted above, a determination of AoD by the light UE <NUM> may be optional. Thus, actions related to the AoD determination described in <FIG> may be optional as well. ) Because multiple premium UEs <NUM> are used, the functionality of the premium UE <NUM> illustrated in <FIG> may be replicated for all premium UEs <NUM>. That said, the determination of the position of the light UE at block <NUM> of <FIG> (and accompanying actions <NUM> and <NUM>) may be performed by a single premium UE <NUM>, if desired.

It also can be noted that reference signals and sidelink signals may be the same or different, depending on desired functionality. For example, a single reference signal <NUM> may be sent to the light UE <NUM>, which may then send respective sidelink signals <NUM> to each of the premium UEs <NUM>. In another example, the light UE <NUM> may receive a single reference signal <NUM> and send a single sidelink signal <NUM> to all or a subset premium UEs <NUM>. Alternatively, a different reference signal <NUM> may be used for each premium UE <NUM> such that, for each premium UE, the light UE <NUM> receives a respective reference signal <NUM> and sends a corresponding respective sidelink signal <NUM> to the premium UE. Different embodiments may employ different combinations of reference signals. Similarly, one or more reference signals from the base station <NUM> to the premium UEs <NUM> (not illustrated in <FIG> but corresponding to reference signal <NUM> in <FIG>) may be used. , if all premium UEs <NUM> are within a single beam, a single reference signal may be used. Alternatively, different reference signals may be sent to different premium UEs <NUM>.

<FIG> is a flow diagram of a method <NUM> of determining the position of a first mobile device, according to an embodiment. Here, the first mobile device may correspond with the light UE <NUM>, and the second mobile device may correspond with the premium UE <NUM>, as described in <FIG>. Further, as illustrated in the example processes of <FIG> and the descriptions of <FIG> and <FIG>, the operations performed by different devices may vary, depending on whether positioning is UE-assisted or UE-based, and/or other factors. Accordingly, means for performing the functionality illustrated in one or more of the blocks shown in <FIG> may be performed by hardware and/or software components of a light UE <NUM>, premium UE <NUM>, or location server <NUM>. Example components of a light UE <NUM> or premium UE <NUM> are illustrated in <FIG> (which generally describes a mobile device) and described in more detail below. Example components of a location server are illustrated in <FIG> (which generally describes a computer system) and described in more detail below.

At block <NUM>, the functionality comprises determining a first time difference, wherein the first time difference comprises a time difference between: (i) a time a first wireless reference signal transmitted by a network entity arrives at the first mobile device, and (ii) a time the first mobile device transmits a second wireless reference signal. An example of this first time difference is provided in equation (<NUM>) as TUE_Rx→Tx, which, as noted, can be used to account for delays at the first mobile device (e.g., light UE <NUM>) when determining Rsum. As indicated in the above-described embodiments, the first wireless reference signal (e.g., reference signal <NUM> in <FIG> and <FIG>) may be transmitted by a network entity comprising a base station. More broadly, the network entity may comprise any type of base station or TRP (including a gNB or eNB, for example). In some embodiments, a network entity may alternatively comprise another UE having a known location and capable of performing the operations of a base station as indicated in the previously-described embodiments. Where the network entity comprises a base station or TRP, the first wireless reference signal may comprise a downlink (DL) reference signal such as a PRS, SSB, Tracking Reference Signal (TRS), Channel State Information Reference Signal (CSIRS), Demodulation Reference Signal (DMRS), etc. Where the network entity comprises another UE, the first wireless reference signal may comprise a sidelink (SL) reference signal, such as an SL-PRS, DMRS, CSIRS, etc. The second wireless reference signal transmitted by the first mobile device may also comprise an SL reference signal. According to some embodiments, determining the first time difference is performed at the mobile device, which can measure/calculate the time difference based on a ToA of the first wireless reference signal and a time of transmission of the second wireless reference signal. Alternatively, the first time difference may be determined at the second mobile device or at a location server by receiving information indicative of the first time difference from the first mobile device.

Means for performing functionality at block <NUM> may comprise a bus <NUM>, wireless communication interface <NUM>, digital signal processor (DSP) <NUM>, processing unit <NUM>, memory <NUM>, and/or other components of a mobile device, as illustrated in <FIG>. Additionally or alternatively, means for performing functionality at block <NUM> may comprise a bus <NUM>, communications subsystem <NUM>, processing unit(s) <NUM>, working memory <NUM>, and/or other components of a computer, as illustrated in <FIG>.

At block <NUM>, the functionality comprises determining a second time difference, wherein the second time difference comprises a time difference between (i) a time a third wireless reference signal transmitted by the network entity arrives at a second mobile device, and (ii) a time the second wireless reference signal arrives at the second mobile device. An example of a second time difference is provided in equation (<NUM>) as TRx_sidelink - TRx_RS. As described in the embodiments above, ToA measurements may be taken by the second wireless device of the second wireless reference signal and the third wireless reference signal to determine this time difference. Alternatively, this time difference may be determined by the first mobile device or location server based on information received from the second mobile device (e.g., at arrow <NUM> of <FIG> or arrow <NUM> of <FIG>). As noted, the first wireless reference signal and the third wireless reference signal may comprise the same signal in some embodiments. Alternatively, they may comprise distinctive reference signals. In the latter case, determining the position of the first mobile device may be further based on a difference in time between the transmission of the first wireless reference signal and the third wireless reference signal.

Means for performing functionality at block <NUM> may comprise a bus <NUM>, wireless communication interface <NUM>, DSP <NUM>, processing unit <NUM>, memory <NUM>, and/or other components of a mobile device, as illustrated in <FIG>. Additionally or alternatively, means for performing functionality at block <NUM> may comprise a bus <NUM>, communications subsystem <NUM>, processing unit(s) <NUM>, working memory <NUM>, and/or other components of a computer, as illustrated in <FIG>.

At block <NUM>, the functionality comprises determining the position of the first mobile device based on the first time difference and the second time difference. As described in the embodiments above, a relative position a light UE from a base station can be determined based on angle and distance from the base station. Accordingly, angle θT can be determined from the AoD and distance RT can be calculated in the manner above to determine a position of the first mobile device relative to a position of the base station. Moreover, the absolute position of the first mobile device can be determined in further view of the absolute position of the base station. As such, embodiments of the method <NUM> may further comprise determining an AoD of the first wireless reference signal based on a measurement taken by the first mobile device, wherein determining the position of the first mobile device is further based on the AoD. Determining the AoD may comprise obtaining, with the second mobile device, assistance data from a location server; and receiving, with the second mobile device, the measurement taken by the first mobile device. In such instances, the AoD may be determined by the second mobile device based on the measurement and the assistance data. Here, the assistance data comprises boresight and beam width of the first wireless reference signal. Additionally or alternatively, the method may comprise sending with the second mobile device, an indication of the AoD to the network entity or the location server. In some embodiments, determining the AoD may comprise receiving, with a location server, the measurement taken by the first mobile device. In such embodiments, the AoD may be determined by the location server based on the measurement taken by the first mobile device.

As noted, an AoD may not necessarily be needed for determination of the position of the first mobile device. As indicated in <FIG>, for example, the position of the first mobile device (the light UE <NUM>) can be determined based on multi-lateration. Multi-lateration may be performed by calculating Rsum for the second mobile device and one or more additional mobile devices. As such, according to some embodiments, the method <NUM> may further comprise a third time difference, wherein the third time difference comprises a time difference between (i) a time a fourth wireless reference signal transmitted by the network entity arrives at a third mobile device, and (ii) a time the third mobile device receives a fifth wireless reference signal transmitted by the first mobile device. In such instances, determining position of the first mobile device may be further based on the third time difference.

In embodiments where the operations of <FIG> are performed at the first mobile device, functionality may vary. According to some embodiments, the method <NUM> may further comprise receiving, with the first mobile device from the second mobile device, information indicative of the second time difference, receiving, with the first mobile device from the network entity or a location server, an indication of a position of the second mobile device relative to a position of the network entity, and determining, with the first mobile device, a distance between the first mobile device and the network entity based at least in part on the indication of the second time difference. In such embodiments, determining the position of the first mobile device maybe further based on the distance. In some embodiments, the indication of the position of the second mobile device relative to the position of the network entity may comprise a distance between the second mobile device and the network entity or a position of the network entity and a position of the second mobile device.

As noted in the previously-described embodiments, the determination of the position of the first mobile device may be based on different data (e.g., multi-lateration versus distance and angle from base station). In some embodiments, the distance (e.g., distance L in <FIG>) between the network entity and second mobile device determining may be determined. As such, embodiments of the method <NUM> may further comprise determining a distance between the second mobile device and the network entity, wherein determining the position of the first mobile device is further based on the distance between the second mobile device and the network entity.

At block <NUM>, the functionality comprises providing the position of the first mobile device. As previously noted, the way in which the position is provided can vary depending on circumstance. In some embodiments, for example, the second mobile device may determine the position of the first mobile device. In such cases, providing the position of the first mobile device may comprise sending the position of the first mobile device from the first mobile device to the second mobile device, or to a location server. Where the position is calculated by the first mobile device, the calculation may be performed on a specialized application or lower-level function, in which case providing the position of the first mobile device may comprise providing, the position of the first mobile device to an application executed by the first mobile device.

In instances in which UE-assisted positioning is performed, a location server may provide the position to a requesting entity. In such embodiments, to determine the distance between the first mobile device and the base station, a location server may receive, from the second mobile device, information indicative of the first time difference and/or second time difference from the second mobile device. The location server may further determine the position of the first mobile device and provide the position of the first mobile device. Such embodiments may further comprise receiving a request for the position of the first mobile device from a requesting entity, wherein providing the position of the first mobile device comprises sending the position of the first mobile device to the requesting entity.

In some embodiments, the frequency bands used to transmit the wireless reference signals may be different. For example, the first wireless reference signal may be in a first frequency band, and the second wireless reference signal in a second frequency band; one may be Time Division Duplex (TDD) the other Frequency Division Duplex (FDD); one may be in FR1 and the other in FR2, and so on. As such, according to some embodiments of the method <NUM>, the first wireless reference signal may be on a first wireless frequency band and the second wireless reference signal, the third wireless reference signal, or both, may be on a second frequency band.

Wireless reference signals may also be within a given time-domain window, depending on desired functionality. For example, according to some embodiments, the various network components may configured such that, if the first wireless reference signal is transmitted in a slot n (where slot n is a given slot in a Orthogonal Frequency-Division Multiplexing (OFDM) regime), the second and/or third wireless reference signals may need to be transmitted in slot n+k, such that they are within X ms of the first wireless reference signals. Here, the value for X could be, for example, <NUM>, <NUM>, <NUM>, etc..

<FIG> illustrates an embodiment of a mobile device <NUM>, which can be utilized as a light UE, premium UE, or other UE as described herein above (e.g., in association with <FIG>). For example, the mobile device <NUM> can perform one or more of the functions of the method shown in <FIG>. It should be noted that <FIG> is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by <FIG> can be localized to a single physical device and/or distributed among various networked devices, which may be disposed at different physical locations. Furthermore, as previously noted, the functionality of the UE discussed in the previously described embodiments may be executed by one or more of the hardware and/or software components illustrated in <FIG>.

The mobile device <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include a processing unit(s) <NUM> which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structures or means. As shown in <FIG>, some embodiments may have a separate DSP <NUM>, depending on desired functionality. Location determination and/or other determinations based on wireless communication may be provided in the processing unit(s) <NUM> and/or wireless communication interface <NUM> (discussed below). The mobile device <NUM> also can include one or more input devices <NUM>, which can include without limitation one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, and/or the like; and one or more output devices <NUM>, which can include without limitation one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, and/or the like.

The mobile device <NUM> may also include a wireless communication interface <NUM>, which may comprise without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth® device, an IEEE <NUM> device, an IEEE <NUM>. <NUM> device, a Wi-Fi device, a WiMAX device, a WAN device, and/or various cellular devices, etc.), and/or the like, which may enable the mobile device <NUM> to communicate with other devices as described in the embodiments above. The wireless communication interface <NUM> may permit data and signaling to be communicated (e.g., transmitted and received) with TRPs of a network, for example, via eNBs, gNBs, ng-eNBs, access points, various base stations and/or other access node types, and/or other network components, computer systems, and/or any other electronic devices (UEs/mobile devices, etc.) communicatively coupled with TRPs, as described herein. The communication can be carried out via one or more wireless communication antenna(s) <NUM> that send and/or receive wireless signals <NUM>. According to some embodiments, the wireless communication antenna(s) <NUM> may comprise a plurality of discrete antennas, antenna arrays, or any combination thereof.

Depending on desired functionality, the wireless communication interface <NUM> may comprise a separate receiver and transmitter, or any combination of transceivers, transmitters, and/or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers, such as wireless devices and access points. The mobile device <NUM> may communicate with different data networks that may comprise various network types. For example, a Wireless Wide Area Network (WWAN) may be a CDMA network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMAX (IEEE <NUM>) network, and so on. A CDMA network may implement one or more RATs such as CDMA2000, WCDMA, and so on. CDMA2000 includes IS-<NUM>, IS-<NUM> and/or IS-<NUM> standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, LTE Advanced, <NUM> NR, and so on. <NUM> NR, LTE, LTE Advanced, GSM, and WCDMA are described in documents from 3GPP. Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project X3" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE <NUM>. 11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, an IEEE <NUM>. 15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.

The mobile device <NUM> can further include sensor(s) <NUM>. Sensors <NUM> may comprise, without limitation, one or more inertial sensors and/or other sensors (e.g., accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), barometer(s), and the like), some of which may be used to obtain position-related measurements and/or other information.

Embodiments of the mobile device <NUM> may also include a Global Navigation Satellite System (GNSS) receiver <NUM> capable of receiving signals <NUM> from one or more GNSS satellites using an antenna <NUM> (which could be the same as antenna <NUM>). Positioning based on GNSS signal measurement can be utilized to complement and/or incorporate the techniques described herein. The GNSS receiver <NUM> can extract a position of the mobile device <NUM>, using conventional techniques, from GNSS satellites (e.g., GNSS satellites <NUM>) of a GNSS system, such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, BeiDou Navigation Satellite System (BDS) over China, and/or the like. Moreover, the GNSS receiver <NUM> can be used with various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems, such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), and Geo Augmented Navigation system (GAGAN), and/or the like.

It can be noted that, although GNSS receiver <NUM> is illustrated in <FIG> as a distinct component, embodiments are not so limited. As used herein, the term "GNSS receiver" may comprise hardware and/or software components configured to obtain GNSS measurements (measurements from GNSS satellites). In some embodiments, therefore, the GNSS receiver may comprise a measurement engine executed (as software) by one or more processing units, such as processing unit(s) <NUM>, DSP <NUM>, and/or a processing unit within the wireless communication interface <NUM> (e.g., in a modem). A GNSS receiver may optionally also include a positioning engine, which can use GNSS measurements from the measurement engine to determine a position of the GNSS receiver using an Extended Kalman Filter (EKF), Weighted Least Squares (WLS), a hatch filter, particle filter, or the like. The positioning engine may also be executed by one or more processing units, such as processing unit(s) <NUM> or DSP <NUM>.

The mobile device <NUM> may further include and/or be in communication with a memory <NUM>. The memory <NUM> can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (RAM), and/or a read-only memory (ROM), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.

The memory <NUM> of the mobile device <NUM> also can comprise software elements (not shown in <FIG>), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above may be implemented as code and/or instructions in memory <NUM> that are executable by the mobile device <NUM> (and/or processing unit(s) <NUM> or DSP <NUM> within mobile device <NUM>). In an aspect, then such code and/or instructions can be used to configure and/or adapt a general-purpose computer (or other device) to perform one or more operations in accordance with the described methods.

<FIG> is a block diagram of an embodiment of a computer system <NUM>, which may be used, in whole or in part, to provide the functions of one or more network components as described in the embodiments herein (e.g., location server <NUM> of <FIG>, <FIG>, and <FIG>). It should be noted that <FIG> is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. <FIG>, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner. In addition, it can be noted that components illustrated by <FIG> can be localized to a single device and/or distributed among various networked devices, which may be disposed at different geographical locations.

The computer system <NUM> is shown comprising hardware elements that can be electrically coupled via a bus <NUM> (or may otherwise be in communication, as appropriate). The hardware elements may include processing unit(s) <NUM>, which may comprise without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), and/or other processing structure, which can be configured to perform one or more of the methods described herein. The computer system <NUM> also may comprise one or more input devices <NUM>, which may comprise without limitation a mouse, a keyboard, a camera, a microphone, and/or the like; and one or more output devices <NUM>, which may comprise without limitation a display device, a printer, and/or the like.

The computer system <NUM> may further include (and/or be in communication with) one or more non-transitory storage devices <NUM>, which can comprise, without limitation, local and/or network accessible storage, and/or may comprise, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a RAM and/or ROM, which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like. Such data stores may include database(s) and/or other data structures used store and administer messages and/or other information to be sent to one or more devices via hubs, as described herein.

The computer system <NUM> may also include a communications subsystem <NUM>, which may comprise wireless communication technologies managed and controlled by a wireless communication interface <NUM>, as well as wired technologies (such as Ethernet, coaxial communications, universal serial bus (USB), and the like). The wireless communication interface <NUM> may send and receive wireless signals <NUM> (e.g., signals according to <NUM> NR or LTE) via wireless antenna(s) <NUM>. Thus the communications subsystem <NUM> may comprise a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device, and/or a chipset, and/or the like, which may enable the computer system <NUM> to communicate on any or all of the communication networks described herein to any device on the respective network, including a UE/mobile device, base stations and/or other TRPs, and/or any other electronic devices described herein. Hence, the communications subsystem <NUM> may be used to receive and send data as described in the embodiments herein.

In many embodiments, the computer system <NUM> will further comprise a working memory <NUM>, which may comprise a RAM or ROM device, as described above. Software elements, shown as being located within the working memory <NUM>, may comprise an operating system <NUM>, device drivers, executable libraries, and/or other code, such as one or more applications <NUM>, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processing unit within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) <NUM> described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system <NUM>. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as an optical disc), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system <NUM> and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system <NUM> (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.

For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both.

With reference to the appended figures, components that can include memory can include non-transitory machine-readable media. The term "machine-readable medium" and "computer-readable medium" as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion. In embodiments provided hereinabove, various machine-readable media might be involved in providing instructions/code to processing units and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Common forms of computer-readable media include, for example, magnetic and/or optical media, any other physical medium with patterns of holes, a RAM, a programmable ROM (PROM), erasable PROM (EPROM), a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.

The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the figures provided herein can be embodied in hardware and/or software. Also, technology evolves and, thus many of the elements are examples that do not limit the scope of the disclosure to those specific examples.

It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, numerals, or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as is apparent from the discussion above, it is appreciated that throughout this Specification discussion utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "associating," "measuring," "performing," or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this Specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

Terms, "and" and "or" as used herein, may include a variety of meanings that also is expected to depend, at least in part, upon the context in which such terms are used. Typically, "or" if used to associate a list, such as A, B, or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B, or C, here used in the exclusive sense. In addition, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in the singular or may be used to describe some combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example and claimed subject matter is not limited to this example. Furthermore, the term "at least one of" if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc..

Claim 1:
A method of determining a position of a first mobile device, the method comprising:
determining (<NUM>) a first time difference, wherein the first time difference comprises a time difference between:
a time a first wireless reference signal transmitted by a network entity arrives at the first mobile device, and
a time the first mobile device transmits a second wireless reference signal;
determining (<NUM>) a second time difference, wherein the second time difference comprises a time difference between:
a time a third wireless reference signal transmitted by the network entity arrives at a second mobile device, and
a time the second wireless reference signal arrives at the second mobile device;
determining (<NUM>) the position of the first mobile device based on the first time difference and the second time difference; and
providing (<NUM>) the position of the first mobile device.