Systems and methods for supporting location uncertainty for scheduled locations

Abstract

A location of a user equipment (UE) is determined based on location measurements received from one or more other entities for the UE at a scheduled positioning time (804). The location measurements are obtained at multiple times based on the scheduled positioning time (802). An uncertainty of the location indicating a difference between the location of the UE at the scheduled positioning time and an actual location of the UE is determined (806), and the location and the uncertainty of the location are sent to the requesting entity (808). The uncertainty of the location is based on a location uncertainty and a time uncertainty with respect to the scheduled positioning time, which are combined into a single location uncertainty.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefits of U.S. Provisional Application No. 63 / 186,163, filed May 9, 2021, entitled “Systems and methods for supporting a combined location and time uncertainty for a scheduled location,” and U.S. Non-Provisional Application No. 17 / 739,132, filed May 8, 2022, entitled “Systems and methods for supporting a location uncertainty for a scheduled location,” both of which have been assigned to the assignee of this application and are expressly incorporated herein by reference in their entirety. Background Technology

[0003] field

[0004] The topics disclosed in this article relate to the location determination of mobile devices, and more specifically to the location of mobile devices that support the use of scheduled location times.

[0005] Relevant background

[0006] Wireless communication systems have undergone several generations of development, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data wireless services with internet capabilities, and fourth-generation (4G) services (e.g., LTE or WiMax). The fifth-generation (5G) mobile standard demands even higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide tens of megabits per second of data rate to each of tens of thousands of users, and 1 gigabits per second of data rate to dozens of employees on an office floor.

[0007] Obtaining the location of a mobile device accessing a wireless (e.g., 5G) network can be useful for many applications, including emergency calls, personal navigation, asset tracking, and locating friends or family members. However, in many applications, reducing latency is desirable. There are many components that contribute to latency during the location process. One way to reduce latency is to use a scheduled location time, which allows the Location Services (LCS) client to specify a precise future time when the user equipment's (UE) location will be obtained. However, using a scheduled location time can introduce additional uncertainty into the UE's location, and it is desirable to control or mitigate this uncertainty.

[0008] Overview

[0009] The following is a simplified overview relating to one or more aspects disclosed herein. Thus, this overview should not be considered an exhaustive overview relating to all aspects of the conception, nor should it be considered to identify key or decisive elements relating to all aspects of the conception or to depict the scope associated with any particular aspect. Accordingly, the sole purpose of the following overview is to present, in a simplified form, certain concepts relating to one or more aspects of the mechanism disclosed herein before the detailed description given below.

[0010] The location of the User Equipment (UE) is determined at a scheduled positioning time T based on location measurements received from one or more other entities. Location measurements are obtained at multiple times based on the scheduled positioning time. An uncertainty indicating the difference between the UE's location at the scheduled positioning time and its actual location is determined, and this location and its uncertainty are sent to the requesting entity. This uncertainty is based on both location uncertainty and time uncertainty, which are combined into a single location uncertainty.

[0011] In one implementation, a method for locating a UE at an entity at a scheduled location time includes: receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determining the location of the UE based on the location measurements; determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmitting the location and the uncertainty in the location to another entity.

[0012] In one implementation, an entity configured in a wireless network to locate a UE at a scheduled location time includes: an external interface configured to communicate with other entities in the wireless network; at least one memory; and at least one processor coupled to the external interface and the at least one memory, the at least one processor being configured to: receive location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determine the location of the UE based on the location measurements; determine an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmit the location and the uncertainty in the location to another entity.

[0013] In one implementation, an entity configured in a wireless network to locate a user equipment (UE) at a scheduled location time includes: means for receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; means for determining the location of the UE based on the location measurements; means for determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and means for transmitting the location and the uncertainty in the location to another entity.

[0014] In one implementation, a non-transient storage medium includes program code stored thereon, the program code being operable to configure at least one processor in an entity in a wireless network for locating a user equipment (UE) at a scheduled location time, the program code including instructions for: receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determining the location of the UE based on the location measurements; determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmitting the location and the uncertainty in the location to another entity.

[0015] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Brief description of the attached diagram

[0017] The accompanying drawings are provided to help describe various aspects of this disclosure, and the drawings are provided for illustrative purposes only and not for limiting the aspects.

[0018] Figure 1The text explains wireless communication systems, including next-generation (NG) radio access networks.

[0019] Figure 2 An extended architecture diagram of an NG-RAN node including a Location Server Agent (LSS) is shown.

[0020] Figure 3 The explanation explains the message transmission flow used to determine the UE's location using the scheduled positioning time.

[0021] Figure 4 The explanation focuses on location determination for the UE using the scheduled positioning time and the resulting location and uncertainty.

[0022] Figure 5 The location uncertainty and timing uncertainty associated with the estimated location of the UE are explained.

[0023] Figure 6 This describes the message flow used to determine the UE's location using the scheduled positioning time.

[0024] Figure 7 A schematic block diagram illustrates certain exemplary features of an entity configured to perform positioning of a UE using a scheduled positioning time.

[0025] Figure 8 A flowchart is shown for an exemplary method to support locating a UE using a scheduled location time.

[0026] Elements, stages, steps, and / or actions with the same reference numerals in different figures may correspond to each other (e.g., they may be similar or identical). Furthermore, some elements in the various figures are labeled using a numerical prefix followed by a letter or number suffix. Elements with the same numerical prefix but different suffixes may be different instances of the same type of element. A numerical prefix without any suffix is ​​used herein to refer to any element with that numerical prefix. For example, Figure 1 Different instances of gNB 110-1 and 110-2 are shown. A reference to gNB 110 can refer to either gNB 110-1 or 110-2.

[0027] Detailed description

[0028] Various aspects of this disclosure are provided below in the description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, elements well-known in this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0029] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than the others. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0030] Those skilled in the art will appreciate that the information and signals described below can be represented using any of a variety of different techniques and arts. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0031] Furthermore, many aspects are described in the form of sequences of actions performed by elements of, for example, computing devices. It will be appreciated that the various actions described herein can be performed by special-purpose circuitry (e.g., application-specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be considered to be fully embodied in any form of non-transient computer-readable storage medium storing a corresponding set of computer instructions that, upon execution, will cause an associated processor of the device to perform the functions described herein. Thus, various aspects of this disclosure can be embodied in several different forms, all of which are contemplated to fall within the scope of the claimed subject matter. Furthermore, for each aspect described herein, a corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0032] As used herein, the terms “User Equipment” (UE) and “base station” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, Industrial IoT (IIoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a radio access network (RAN). As used herein, the term “UE” can be interchangeably referred to as “access terminal” or “AT,” “client device,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or “UT,” “mobile terminal,” “mobile station,” “mobile device,” or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) (e.g., based on IEEE 802.11, etc.), etc.

[0033] A base station may operate according to one of several RATs when communicating with a UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, B-Node, Evolved B-Node (eNB), New Radio (NR) B-Node (also known as gNB or gNodeB), etc. The communication link through which the UE can send signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can send signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse or DL / forward traffic channel.

[0034] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be the serving base station from which the UE receives measurement reports and neighboring base stations from which the UE is measuring its reference RF signal.

[0035] To support UE location, two main categories of location solutions have been defined: control plane and user plane. Using control plane (CP) location, location-related and location support signaling can be carried over existing network (and UE) interfaces using existing protocols dedicated to signaling transmission. Using user plane (UP) location, location-related and location support signaling can be carried using protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP) as part of other data.

[0036] The 3rd Generation Partnership Project (3GPP) has defined control plane location solutions for UEs using radio access based on GSM (2G), UMTS (3G), LTE (4G), and New Radio (NR) for 5G. These solutions are defined in 3GPP Technical Specifications (TS) 23.271 and 23.273 (common parts), 43.059 (GSM access), 25.305 (UMTS access), 36.305 (LTE access), and 38.305 (NR access). The Open Mobility Alliance (OMA) similarly defines an up-plane location solution called Secure User Plane Location (SUPL), which can be used to locate UEs accessing any of several radio interfaces supporting IP packet access, such as General Packet Radio Service (GPRS) in GSM, GPRS in UMTS, or IP access in LTE or NR.

[0037] Both CP and UP location solutions can utilize a Location Server (LS) to support positioning. The LS can be part of or accessible from the UE's serving or home network, or simply accessible via the Internet or local intranet. If positioning of the UE is required, the LS can initiate a session with the UE (e.g., a positioning session or a SUPL session) and coordinate location measurements performed by the UE and the determination of the estimated location of the UE. During the location session, the LS can request positioning capabilities from the UE (or the UE can provide these capabilities without request), provide auxiliary data to the UE (e.g., upon request or without request), and request location estimates or measurements from the UE, such as those for Global Navigation Satellite System (GNSS), Auxiliary GNSS (A-GNSS), Time Difference of Arrival (TDOA), Angle of Departure (AOD), Angle of Arrival (AOA), Round Trip Time (RTT), Multi-Cell RTT, or combinations thereof, or other positioning methods. Auxiliary data can be used by the UE to acquire and measure GNSS and / or Positioning Reference Signal (PRS) signals (e.g., by providing the expected characteristics of these signals, such as frequency, expected time of arrival, signal decoding, signal Doppler).

[0038] In UE-based operating modes, auxiliary data may be used by the UE, either additionally or alternatively, to help determine a location estimate from the obtained location measurement (e.g., to provide satellite ephemeris in the case of GNSS positioning or to provide base station location and other base station characteristics (such as PRS timing) in the case of ground positioning using, for example, TDOA, AOD, multi-RTT, etc).

[0039] In UE-assisted operation mode, the UE can return location measurements to the LS, which can determine the UE's estimated location based on these measurements and possibly also on other known or configured data (e.g., satellite ephemeris data for GNSS positioning or base station characteristics (including base station location and possible PRS timing) in cases of ground positioning using, for example, TDOA, AoD, Multi-RTT, etc.).

[0040] In some scenarios, the UE requesting the location of a target UE, the Location Services (LCS) client, or the Application Function (AF) can know when the location should be obtained. For example, using periodically delayed Mobile Termination Location Requests (MT-LR), the UE's location is obtained at fixed periodic intervals, thus knowing the location time in advance. In another example, such as in a factory or warehouse with mobile tools, components, packaging, etc., the exact time when the mobile tools, components, or packaging will arrive at a specific location or complete a specific movement or operation can be accurately anticipated. In such scenarios, locating the tools, components, or packaging to confirm the anticipated location at a specific time and to make any further adjustments may subsequently be useful or critical. Additionally, the location of a UE can sometimes be scheduled to occur at a specific future time. For example, all vehicles on a road may be located simultaneously to provide indication of traffic congestion and to assist communication and safety. Similarly, people, containers, transportation systems, etc., may also be located at certain common times. In scenarios such as these, the time when the location should be obtained (which may be referred to as the scheduled location time) can be provided in advance to obtain the location accurately at the requested time and / or reduce the effective waiting time for providing location results to the receiving UE, LCS client, or AF.

[0041] As discussed above, the scheduled location time allows an external LCS client, AF, or UE to specify the time when the UE's location will be obtained in the future. The UE's location at the precise scheduled location time is typically the target, although some uncertainty or error may be allowed in LCS Quality of Service (QoS) regarding achieving the scheduled location time. Uncertainty or error can include multiple sources of error. For example, uncertainty can include location uncertainty, which reflects the difference between the estimated location of the target UE at the time of measurement and the actual location of the target UE at the time of measurement. Another source of uncertainty can be time uncertainty, which is attributed to the difference between the measurement time and the scheduled location time. For example, if a location request for the UE includes a scheduled location time T, the location measurement for the UE can occur at a slightly different time T1. The UE could be at location L at time T and at a slightly different location L1 at time T1, and the estimated location of the UE at time T1 could be location L1'. Position uncertainty (or measurement uncertainty) or error can be expressed as L1-L1' (e.g., where vector subtraction can be used if L1 and L1' are each vectors, or subtraction of corresponding coordinates can be used if L1 and L1' each include X and Y coordinates or X, Y, and Z coordinates according to some Cartesian coordinate system). Time uncertainty or error can be similarly expressed as T-T1. Thus, the total uncertainty or error includes the position error L1-L1' and the time error T-T1. If the UE is moving at a constant speed V, the time error will result in a corresponding additional position error V*(T-T1). Therefore, if the UE is moving and requires very accurate positioning, the impact of the time error can be significant. However, the LCS client, AF, or UE may not be able to determine the level of importance of the time error; for example, they may not be able to determine whether the returned position is still useful and available.

[0042] It is desirable to combine location uncertainty and temporal uncertainty into a single combined location uncertainty, which expresses the combined error of the two types of uncertainty. This combination can be performed, for example, if the location server has information about the UE's movement (e.g., speed), or if UE location measurements are obtained shortly before and shortly after the scheduled positioning time. Combined location uncertainty avoids the need for the LCS client to know any information about temporal error. Combined uncertainty can represent the expected (or possible) difference between the UE's actual location at the scheduled positioning time and the location the UE could obtain at a time that corresponds to a slightly different time from the scheduled positioning time. The end result can be a simplification of the use of scheduled positioning times from the LCS client's perspective.

[0043] Figure 1A positioning architecture diagram of a communication system 100 is shown. This system can support scheduling locations before they are needed (at the scheduled positioning time) and utilize a combination of location uncertainty and time uncertainty, as well as the use of location management functions in NG-RAN. The location management function in NG-RAN can be a "Location Server Agent (LSS)" or a "Location Management Component (LMC)" and... Figure 1 It may be located in one or more gNB 110s or outside of gNB 110 but within NG-RAN135. Note that LMC or LSS are optional elements and may not always be present.

[0044] Communication system 100 can be configured to support the positioning of user equipment (UE) 102. Here, communication system 100 includes UE 102 and components of a fifth-generation (5G) network, including a next-generation (NG) radio access network (RAN) (NG-RAN) 135 and a 5G core network (5GCN) 140. The 5G network may also be referred to as a new radio (NR) network; NG-RAN 135 may be referred to as 5GRAN or NR RAN; and 5GCN 140 may be referred to as an NG core network (NGC). Communication system 100 may further utilize information from a satellite carrier (SV) 190 of a Global Navigation Satellite System (GNSS) (such as GPS, GLONASS, Galileo, or BeiDou) or some other local or regional satellite positioning system (SPS) (such as IRNSS, EGNOS, or WAAS). Additional components of communication system 100 are described below. Communication system 100 may include additional or replacement components.

[0045] It should be noted that Figure 1 Only a general description of the individual components is provided, whereby any or all of the components may be used appropriately, and each component may be repeated or omitted as needed. Specifically, although only one UE 102 is described, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the communication system 100. Similarly, the communication system 100 may include a larger (or smaller) number of SV 190, gNB 110, next-generation evolved B-node (ng-eNB) 114, AMF 115, external client 130, and / or other components. The described connections connecting the various components in the communication system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or radio connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0046] Although Figure 1While 5G-based networks have been explained, similar network implementations and configurations can be used for other communication technologies, such as 3G and LTE. The implementations described in this paper (whether for 5G technology or other communication technologies and protocols) can be used to configure an increased number of location-related information or resources associated with broadcast communications from a wireless node (e.g., broadcasting of auxiliary data), the transmission of Position Reference Signals (PRS), or some other location-related functions of the wireless node in response to a received request.

[0047] UE 102 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), Secure User Plane Location Enabled (SUPL) terminal (SET), or some other name. Furthermore, UE 102 may correspond to a cellular phone, smartphone, laptop device, tablet device, PDA, tracking device, navigation device, Internet of Things (IoT) device, or some other portable or mobile device. Typically, although not required, UE 102 may use one or more radio access technologies (RATs) such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), LTE, High Rate Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi), etc. (BT), WiMAX, 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GCN 140), etc.) are used to support wireless communication. UE102 can also support wireless communication using a wireless local area network (WLAN), which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. Using one or more of these RATs allows UE102 to communicate with external client 130 (via... Figure 1 The 5GCN 140 (not shown) or may be connected via a Gateway Mobile Location Center (GMLC) 125, and / or allow an external client 130 (e.g., via GMLC 125) to receive location information about the UE 102.

[0048] UE 102 may include a single entity or may include multiple entities, such as in a personal area network in which the user may employ audio, video, and / or data I / O devices, and / or body sensors, as well as separate wired or wireless modems. An estimate of the location of UE 102 may be referred to as location, location estimate, location lock, lock, positioning, location estimation, or location lock, and may be geodetic, providing location coordinates (e.g., latitude and longitude) of UE 102, which may or may not include an elevation component (e.g., altitude; height above or depth below ground level, floor level, or basement level). Alternatively, the location of UE 102 may be expressed as a municipal location (e.g., expressed as a postal address or designation of a point or smaller area within a building (such as a specific room or floor)). The location of UE 102 may also be expressed as an area or volume within which UE 102 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.) (geodetic or municipally defined). The location of UE102 may further be a relative location, which includes, for example, distance and direction defined relative to an origin at a known location, or relative to X, Y (and Z) coordinates, which may be defined geodetically, municipalally, or with reference to a point, area, or volume indicated on a map, floor plan, or building plan. In the description contained herein, the term location may include any of these variations unless otherwise indicated. When calculating the location of the UE, local x, y, and possibly z coordinates are typically solved, and then, if necessary, the local coordinates are converted to absolute coordinates (e.g., for latitude, longitude, and elevation above or below mean sea level).

[0049] Figure 1 The base stations (BSs) in the NG-RAN 135 shown include NRB nodes, also referred to as gNB110-1 and 110-2 (collectively and generally referred to as gNB 110 herein). Pairs of gNB 110s in the NG-RAN 135 can be interconnected—for example, as shown in... Figure 1 The connection shown is either a direct connection or an indirect connection via another gNB 110. Access to the 5G network is provided to UE 102 via wireless communication between UE 102 and one or more gNBs 110, which may use 5G NR to provide wireless communication access to the 5GCN 140 on behalf of UE 102. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 1In this context, assuming the serving gNB for UE 102 is gNB 110-1, other gNBs (e.g., gNB 110-2) may act as serving gNBs or as secondary gNBs to provide additional throughput and bandwidth to UE 102 if UE 102 moves to another location. A location server agent (LSS) 117, optionally present within a node in NG-RAN 135 (such as serving gNB 110-1), may perform location server functions as discussed herein.

[0050] Figure 1 The base station (BS) in the NG-RAN 135 shown may additionally or alternatively include a next-generation evolved B node (also referred to as an ng-eNB) 114. The ng-eNB 114 may be connected to one or more gNBs 110 in the NG-RAN 135—for example, directly or indirectly via other gNBs 110 and / or other ng-eNBs. The ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 102. Figure 1 Some gNB 110s (e.g., gNB110-2) and / or ng-eNB 114s can be configured to act as location-only beacons, capable of transmitting signals (e.g., PRS signals) and / or broadcasting auxiliary data to assist UE 102's positioning, but may not receive signals from UE 102 or from other UEs. Note that although in Figure 1 The diagram shows only one ng-eNB 114, but some embodiments may include multiple ng-eNB 114s.

[0051] Figure 1The location server in the UE 102 may correspond to, for example, a Location Management Function (LMF) 120, a Secure User Plane Location (SUPL) Location Platform (SLP) 129 in 5GCN 140, a Location Server Agent (LSS) 117 (or Location Management Component (LMC)) in NG-RAN 135, or a gNB 110. Such a location server may be able to provide the UE 102 with location assistance data, including, for example, information about the signal to be measured (e.g., expected signal timing, signal decoding, signal frequency, signal Doppler), the location and identity of the ground transmitter (e.g., gNB 110), and / or signal, timing, and orbit information about GNSS SVs, to facilitate positioning technologies such as A-GNSS, AFLT, AoD, Downlink (DL) TDOA, RTT, and ECID. This facilitation may include improving the accuracy of signal acquisition and measurement performed by the UE 102, and in some cases, enabling the UE 102 to calculate its estimated location based on location measurements. For example, a location server (e.g., LMF 120 or SLP 129) can access an almanac (also known as a Base Station Almanac (BSA)) that indicates the location and identity of cellular transceivers and / or local transceivers in one or more specific areas (such as specific locations) and can provide information describing signals transmitted by a cellular base station or AP (e.g., gNB), such as transmit power and signal timing. UE 102 can obtain signal strength measurements (e.g., Received Signal Strength Indication (RSSI)) for signals received from cellular transceivers and / or local transceivers, and / or can obtain signal-to-noise ratio (S / N), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Time of Arrival (TOA), Angle of Arrival (AOA), Angle of Departure (AOD), Receive Time-Transmit Time Difference (Rx-Tx), or Round-Trip Time (RTT) between UE 102 and a cellular transceiver (e.g., gNB) or local transceiver (e.g., WiFi Access Point (AP)). UE 102 can use these measurements together with auxiliary data (e.g., ground almanac data or GNSS satellite data, such as GNSS almanac and / or GNSS ephemeris information) received from a location server (e.g., LMF 120 or SLP 129) or broadcast by base stations in NG-RAN 135 (e.g., gNB110-1, gNB 110-2) to determine the location of UE 102.

[0052] As mentioned, although Figure 1The diagram depicts nodes configured to communicate according to the 5G NR and LTE communication protocols for NG-RAN 135, but nodes configured to communicate according to other communication protocols (such as, for example, the LTE protocol for the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) or the IEEE 802.11x protocol for WLAN) may also be used. For example, in a 4G Evolved Packet System (EPS) providing LTE radio access to UE 102, the RAN may include an E-UTRAN, which may include base stations with evolved B-nodes (eNBs) supporting LTE radio access. The core network for the EPS may include an evolved packet core (EPC). The EPS may include an E-UTRAN plus an EPC, where the E-UTRAN corresponds to... Figure 1 NG-RAN 135 and EPC corresponds to Figure 1 5GC 140.

[0053] gNB 110 and ng-eNB 114 can communicate with Access and Mobility Management Function (AMF) 115, which in turn communicates with Location Management Function (LMF) 120 for positioning functionality. AMF 115 supports the mobility of UE 102 (including cell changes and handovers) and can participate in supporting signaling connections to UE 102, as well as possible data and voice bearers for UE 102. LMF 120 supports the scheduling of positioning for UE 102 when the UE accesses NG-RAN 135 and supports various positioning procedures / methods, such as Auxiliary GNSS (A-GNSS), Downlink Time Difference of Arrival (DL-TDOA), Multi-Cell RTT, Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cellular ID (ECID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other positioning procedures. LMF 120 can also process location service requests for UE 102 received, for example, from AMF 115 or GMLC 125. LMF 120 may be connected to AMF 115 and / or GMLC 125. In some embodiments, the node / system implementing LMF 120 may additionally or alternatively implement other types of location support modules, such as Enhanced Serving Mobility Location Center (E-SMLC). Note that in some embodiments, at least a portion of the location functionality (including the derivation of the location of UE 102) may be performed at UE 102 (e.g., using signal measurements obtained by UE 102 against signals transmitted by radio nodes (such as gNB 110 and ng-eNB 114), and auxiliary data provided to UE 102, for example, by LMF 120). In the case of OMA SUPL positioning, the location server may be a SUPL Location Platform (SLP), such as SLP 129, instead of LMF 120.

[0054] Gateway Mobile Location Center (GMLC) 125 can support location requests for UE 102 received from external client 130, and can forward such location requests to AMF 115 for forwarding to LMF 120, or can forward the location request directly to LMF 120. Location responses from LMF 120 or LSS 117 (e.g., containing a location estimate for UE 102) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing the location estimate) to external client 130. GMLC 125 is shown connected to... Figure 1 Both AMF 115 and LMF120 are available, but in some implementations only one of these connections can be supported by 5GCN 140.

[0055] When UE 102 accesses NG-RAN 135, gNB 110-1 can support the location of UE 102. gNB 110-1 can also process location service requests for UE 102 received, for example, directly or indirectly from GMLC 125. In some embodiments, the node / system implementing gNB 110-1 may additionally or alternatively implement other types of location support modules, such as Enhanced Serving Mobility Location Center (E-SMLC) or Secure User Plane Location (SUPL) Location Platform (SLP) 129. It will be noted that in some embodiments, at least a portion of the location functionality (including deriving the location of UE 102) can be performed at UE 102 (e.g., using signal measurements against signals transmitted by the radio node and auxiliary data provided to UE 102).

[0056] To support location services for Internet of Things (IoT) UEs, including those from external client 130, a Network Open Function (NEF) 127 can be included in the 5GCN 140. NEF 127 supports the secure opening of capabilities and events related to the 5GCN 140 and UE 102 to the external client 130; these capabilities and events may also be referred to as Application Functions (AFs), and enable the secure provisioning of information from the external client 130 to the 5GCN 140. In the context of location services, NEF 127 can be used to obtain the current or last known location of UE 102, an indication of location changes for UE 102, or an indication of when UE 102 becomes available (or reachable). NEF 127 can be connected to the GMLC 125 to support the last known location, current location, and / or delayed periodic and triggered locations of UE 102. If needed, NEF 127 may include or be combined with GMLC 125, and may subsequently obtain the location information of UE 102 directly from LSS 117 or LMF 120 (e.g., it may be connected to LSS 117 or LMF 120). NEF 127 may also be connected to AMF 115 so that NEF 127 can obtain the location of UE 102 directly from AMF 115.

[0057] User plane function (UPF) 126 supports voice and data bearer for UE 102 and enables UE 102 to access other networks, such as the Internet, for voice and data. UPF 126 functions may include: external PDU session interconnection point to the data network, packet (e.g., Internet Protocol (IP)) routing and forwarding, user plane portion of packet inspection and policy rule enforcement, user plane Quality of Service (QoS) handling, downlink packet buffering, and downlink data notification triggering. UE 102's location report (e.g., including location estimates determined by LSS 117 in or attached to serving gNB 110-1) can be returned by gNB 110-1 to external client 130 via UPF 126 and User plane aggregator (UPA) 128 (if present). UPF 126 can be connected to SLP 129 to enable location of UE 102 using SUPL. SLP 129 can be further connected to external client 130 or accessed from external client 140.

[0058] UPA 128 is optional and enables external client 130 to receive UE 102 location reports on the user plane by interacting only with UPA 128. UPA 128 avoids the need for gNB 110-1 (or LSS117) to establish a user plane location reporting session directly with the external client, which improves security. UPA 128 can also provide security for NG-RAN 112 and / or external client 130 by authenticating and authorizing external client 130 and / or gNB 110-1 (or LSS117). UPA 128 can be part of 5GCN 150 or can be external to 5GCN 150 (e.g., associated with external client 130). In some implementations, UPA 128 can be part of LMF 120, GMLC 125, or can be connected to LMF 120 or GMLC 125. UPA 128 can also be referred to as a router, IP router, UP router, or routing function.

[0059] LMF 120 can use the New Radio Positioning Protocol A (NRPPa) to communicate with gNB 110 and / or ng-eNB 114, which is defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages can then be transmitted between gNB 110 and LMF 120 and / or between ng-eNB 114 and LMF 120 via AMF 115. LMF 120 and UE 102 can communicate using the LTE Positioning Protocol (LPP), which is defined in 3GPP TS 37.355. Here, LPP messages can be transmitted between UE 102 and LMF 120 via AMF 115 and UE 102's serving gNB 110-1 or serving ng-eNB 114. For example, LPP messages can be transmitted between LMF 120 and AMF 115 using Hypertext Transfer Protocol (HTTP), and between AMF 115 and UE 102 using 5G Non-Access Stratum (NAS) protocol. The LPP protocol can be used to support the location of UE 102 using UE-assisted and / or UE-based location methods (such as A-GNSS, RTK, DL-TDOA, multi-cell RTT, and / or ECID). The NRPPa protocol can be used to support the location of UE 102 using network-based or network-associated location methods (such as ECID, AOA, and multi-cell RTT) (e.g., to enable measurements to be obtained by gNB 110 or ng-eNB 114) and / or can be used by LMF 120 to obtain location-related information from gNB 110 and / or ng-eNB 114, such as defining parameters of PRS transmissions from gNB 110 and / or ng-eNB 114.

[0060] Using a UE-assisted positioning method, UE 102 can obtain location measurements and send them to a location server (e.g., an LMF 120, SLP 129, or LSS117 (or LMC) within a node in NG-RAN 135, such as in serving gNB 110-1) to calculate a location estimate for UE 102. For example, location measurements may include one or more of the following: Received Signal Strength Indication (RSSI), Round-Trip Time (RTT), Reference Signal Time Difference (RSTD), Receive Time-Transmit Time Difference (Rx-Tx), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), AOA, and / or AOD for gNB 110, ng-eNB114, and / or WLAN access point (AP). Location measurements may additionally or alternatively include measurements of GNSS pseudorange, code phase, and / or carrier phase for SV 190. Using a UE-based positioning method, UE 102 can obtain location measurements (e.g., which may be the same as or similar to location measurements obtained by a UE-assisted positioning method) and can calculate the location of UE 102 (e.g., using auxiliary data received from a location server (such as LMF 120) or broadcast by gNB 110, ng-eNB 114, or other base stations or APs). Using a network-based positioning method, one or more base stations (e.g., gNB 110 and / or ng-eNB 114) or APs can obtain location measurements (e.g., RSSI, RTT, RSRP, RSRQ, AOA, or Time of Arrival (TOA) measurements) for signals transmitted by UE 102 and / or can receive measurements obtained by UE 102, and can send these measurements to a location server (e.g., LMF 120, SLP 129, or LSS117 (or LMC) within a node in NG-RAN 135, such as in serving gNB 110-1) to calculate a location estimate for UE 102.

[0061] Information provided by gNB 110 and / or ng-eNB 114 to a location server (e.g., LMF 120) using NRPPa, or to an LSS117 within a node in NG-RAN 135 (such as in serving gNB 110-1) using the Xn Application Protocol (XnAP), may include timing and configuration information for PRS transmission and location coordinates. The location server may subsequently provide some or all of this information to UE 102 in an LPP message via NG-RAN 135 and 5GC 140 as supplementary data.

[0062] The LPP message sent from the location server to UE 102 can instruct UE 102 to perform any of a variety of operations, depending on the desired functionality. For example, the LPP message may contain instructions for UE 102 to obtain measurements for GNSS (or A-GNSS), WLAN, and / or DL-TDOA (or some other positioning method). In the case of DL-TDOA, the LPP message may instruct UE 102 to obtain one or more measurements (e.g., RSTD measurements) of PRS signals transmitted within a specific cell supported by a specific gNB 110 and / or ng-eNB 114 (or supported by some other type of base station (such as eNB or WiFi AP)). RSTD measurements may include the time difference between the arrival of a signal (e.g., a PRS signal) transmitted or broadcast by one gNB 110 and a similar signal transmitted by another gNB 110 at UE 102. UE 102 can send measurements back to the location server, for example, via service gNB 110-1 (or service ng-eNB 114) and AMF 115 in an LPP message (e.g., within a 5G NAS message) to LMF 120, or to LSS117 within a node in NG-RAN 135, such as in service gNB 110-1.

[0063] As mentioned, while a communication system 100 is described in relation to 5G technology, the communication system 100 can be implemented to support other communication technologies (such as GSM, WCDMA, LTE, etc.) used to support and interact with mobile devices (such as UE 102) (e.g., to enable voice, data, location, and other functionalities). In some such embodiments, the 5GC 140 can be configured to control different air interfaces. For example, in some embodiments, non-3GPP interoperability functions (N3IWF) in the 5GCN 140 can be used directly or by employing them. Figure 1(Not shown) Connects 5GCN 140 to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for UE 102 and may include one or more WiFi APs. Here, N3IWF may connect to the WLAN and other components in 5GC 140, such as AMF 115. In some other embodiments, both NG-RAN 135 and 5GCN 140 may be replaced by other RANs and other core networks. For example, in EPS, NG-RAN 135 may be replaced by E-UTRAN containing eNBs, and 5GC 140 may be replaced by EPC containing a Mobility Management Entity (MME) instead of AMF 115, an E-SMLC instead of LMF 120, and a GMLC similar to GMLC 125. In such EPS, the E-SMLC may use LTE Location Protocol A (LPPa) instead of NRPPa to send and receive location information from eNBs in the E-UTRAN, and LPP may be used to support the location of UE 102. In these other embodiments, on-demand resource allocation for UE 102 can be supported in a manner similar to that described herein for 5G networks, the difference being that the functions and procedures described herein for gNB 110, ng-eNB 114, AMF 115, and LMF 120 can, in some cases, be alternatively applied to other network elements, such as eNBs, WiFi APs, MMEs, and E-SMLCs. It should be noted that gNB 110 and ng-eNB 114 may not always both be present in NG-RAN 135. Furthermore, when both gNB 110 and ng-eNB 114 are present, the NG interface with AMF 115 may exist for only one of them.

[0064] As explained, gNB 110 may be allowed to control one or more Transport Points (TPs) 111, such as broadcast-only TPs, for improved support of DL positioning methods such as DL-TDOA or ECID. Additionally, gNB 110 may be allowed to control one or more Receive Points (RPs) 113, such as Internal Location Measurement Units (LMUs), for UL measurements of positioning methods such as Uplink Time Difference of Arrival (UL-TDOA) or ECID. TPs 111 and RPs 113 may be combined into a Transport Receive Point (TRP) 112 or defined as part of a Transport Receive Point (TRP) 112 to support downlink (DL) and / or uplink (UL) positioning methods such as DL-TDOA, UL-TDOA, and multi-cell round-trip time of propagation (RTT). Furthermore, gNB 110 may be allowed to include a Location Server Agent (LSS) 117 to support the positioning of target UE 102 by serving gNB 110. LSS117 (or LMC) can support some or all of the same functions as LMF 120, the difference being that LSS117 resides in NG-RAN 135, while LMF 120 resides in 5GCN 140. The term "location server agent" is used herein for NG-RAN location management functionality, but other terms such as "local LMF" or "NG-RAN LMF" may also be used. Location services for UE 102 provided by the serving gNB 110 can be used to provide location services to UE 102, the serving AMF 115, or LMF 120, and improve NG-RAN operations—for example, by reducing location determination latency and increasing the number of UEs 102 that can be located.

[0065] As explained, the ng-eNB 114 can control one or more TP 111a. TP 111a can use different protocols than TP 111 in gNBs 110-1 and 110-2. For example, TP 111a can use LTE-related protocols, while TP 111 uses 5G NR-related protocols. TP 111a can perform similar functions to TP 111 in gNBs 110-1 and 110-2, and accordingly, TP 111 and 111a can be collectively referred to as TP 111 in this document.

[0066] The location management functionality in NG-RAN 135 (i.e., LSS117) can have capabilities comparable to those of a 5GCN LMF (e.g., LMF120). Operators can limit LSS117 to support, for example, NR Radio Access Technology (RAT) related location scheduling. LSS117 (if present) can communicate with the gNB Central Unit (gNB-CU) and can support location determination and reporting, as described later. LMF 120 can manage the scheduling of one or more Transport Points (TPs) 111 and one or more Receive Points (RPs) 113, where TPs 111 are configured to transmit downlink (DL) reference signals (RS) to be measured by UE 102, and RPs 113 are configured to receive and measure uplink (UL) resource signals (RS) transmitted by UE 102 and UL transmissions transmitted by UE 102.

[0067] The LMF 120, SLP 129, and LSS117 (or LMC) in gNB 110 can perform various functions. For example, LMF120 (or SLP 129) can request location measurements from UE 102, for example, using RRC or LPP, and can manage UL location measurements performed by gNB 110 or TRP 112 of UE 102, and can manage static and dynamic scheduling of DL-PRS and broadcasting of auxiliary data by gNB 110. LMF 120 (or SLP 129) can further interact with other gNB 110s to coordinate location support (e.g., obtaining UL location measurements of UE 102 or requesting changes to DL-PRS broadcasts). LSS117 can receive location measurements and can determine location estimates for UE 102. The above functions are provided as examples only. Additional or different functions can be performed if needed. LSS117 can communicate with other gNB 110s using XnAP or location-specific protocols over XnAP to coordinate support for these functions.

[0068] Therefore, LSS117 can support NG-RAN 135 in determining the location of UE 102, which can be requested by UE 102 (e.g., using LPP), by the serving AMF 115 (e.g., using NGAP or a location-specific protocol delivered by NGAP), by another gNB110 / ng-eNB 114 (e.g., using XnAP or a location-specific protocol delivered by XnAP), or LMF 120 (e.g., using the NRPPA protocol). This capability will allow for location support with reduced latency in location determination (because NG-RAN 135 is closer to UE 102 than LMF 120) and offload location support from LMF.

[0069] Figure 2An architectural diagram of NG-RAN node 200 is shown. NG-RAN node 200 may include LSS 117 or may be coupled to LSS 117 (which is within NG-RAN), for example, as a separate entity or as part of another gNB. According to one implementation, NG-RAN node 200 may be gNB 110. For example, Figure 2 The architecture shown can be applied to Figure 1 Any gNB 110-1 and 110-2 in NG-RAN135 shown.

[0070] As explained, gNB 110 includes a gNB Central Unit (gNB-CU) 202 and gNB Distributed Units (gNB-DUs) 204 and 206, which may be physically co-located within gNB 110 or physically separate. gNB-CU 202 is a logical or physical node that hosts support for the RRC, SDAP, and PDCP protocols of the gNB used on the NR Uu air interface and controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. As explained, gNB-CU 202 can communicate with AMF 115 via the NG interface. gNB-CU 202 can further communicate with one or more other gNB 110s via the Xn interface. gNB-DUs 204 and 206 are logical or physical nodes that host support for the RLC, MAC, and PHY protocol layers used on the NR Uu air interface of gNB 110, and their operation is partially controlled by gNB-CU 202. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-CU 202 requests location measurements (e.g., E-CID) from gNB-DUs 204 and 206. gNB-DUs 204 and 206 report the measurements back to the gNB-CU 202. gNB-DU 204 or 206 may include location measurement functionality. It should be understood that separate measurement nodes are not excluded.

[0071] LSS117 can be part of gNB-CU 202 (e.g., a logical function of gNB-CU 202). However, to offload location support from gNB-CU 202 and allow for a multi-vendor environment, a separate LSS117 is permitted, which can be connected to gNB-CU 202 via the F1 interface. Alternatively, the LSS117 within NG-RAN 135 can be external to gNB 110, for example, as part of another gNB, and can be connected to gNB 110 via the Xn interface. gNB-CU 202 can then forward all location-related signaling to LSS117 and / or gNB-DU 204 and 206 or TRP 112.

[0072] Additionally, as explained, gNB 110 may include TP 111 and RP 113 combined into TRP 112, and LSS 117, which may be physically or logically located within gNB 110. gNB-CU 202 may be configured to communicate with TP 111, RP 113, and LSS 117, for example, via an F1 interface. Thus, gNB-CU 202 controls one or more TP 111, RP 113, and LSS 117 that can be accessed from gNB-CU 202 via the F1 interface.

[0073] In some embodiments, NG-RAN node 200 (or gNB 110) may include Figure 2 A subset of the components shown. For example, NG-RAN node 200 may include gNB-CU 202 and LSS117, but may not include one or more of gNB-DU 204 and 206, RP 113, or TP 111. Alternatively, NG-RAN node 200 may include one or more of gNB-DU 204 and 206, RP 113, or TP 111, but may not include LSS117. Furthermore, Figure 2 The components shown can be logically separate but physically co-located, or they can be physically partially or completely separate. For example, LSS117 can be physically separate from gNB-CU 202, or it can be physically combined with gNB-CU 202. Similarly, one or more of gNB-DU 204 and 206, RP 113, or TP 111 can be physically separate from gNB-CU 202, or they can be physically combined with gNB-CU 202. In the case of physical separation, the F1 interface can define signaling on the physical link or connection between the two separate components. In some implementations, gNB-CU 202 can be split into a control plane portion (referred to as CU-CP or gNB-CU-CP) and a user plane portion (referred to as CU-UP or gNB-CU-UP). In this scenario, both gNB-CU-CP and gNB-CU-UP can interact with gNB-DU 204 and 206 to support NR Uu air interface signaling for the control plane and user plane, respectively. However, only gNB-CU-CP can interact with LSS117, TP 111, and RP 113 to support and control location-related communications.

[0074] Protocol layering between gNB-CU 202 and TP 111, RP 113, and LSS117 can be based on F1 C as defined in 3GPP TS 38.470, which uses F1AP at the top level as specified in 3GPP TS 38.473. New location-supporting messages can be added directly to F1AP or introduced into new location-specific protocols that use F1AP for transmission.

[0075] The location protocol between gNB-CU 202 and LSS117 can include all location-related protocols on the NG, Xn, and NR-Uu interfaces. For example, the location protocol between AMF 115 and NG-RAN node 200 can use NGAP. The location protocol between NG-RAN node 200 and other NG-RAN nodes (e.g., gNB 110) can use XnAP or protocols above XnAP, such as the Extended NR Location Protocol A (NRPPa) as defined in 3GPP TS 39.455. The location protocol between NG-RAN node 200 and UE 102 can use RRC and / or LPP.

[0076] Location-supporting messages can be carried within a transparent F1AP messaging container. For example, NGAP location reporting control and NAS transmission messages can be carried within UL / DLNGAP messaging. Location-related XnAP messages can be carried within UL / DL XnAP messaging. Location-related RRC (LPP) messages can be carried within UL / DL RRC (LPP) messaging.

[0077] The above support can also be implemented using a single F1AP UL / DL LSS messaging container and / or using a new location protocol transmitted via F1AP. Thus, the gNB-CU 202 can forward any location-related delivery messages received on the NG, Xn, and Uu interfaces to the LSS117 (within the same gNB 110, e.g., in cases where the gNB includes an LSS, such as...). Figure 2 (as explained in the text) or forwarded to another gNB (e.g., in the case where the gNB does not have an LSS).

[0078] The location protocol between LSS117 and gNB-DU 204 and 206, TP 111 and RP 113 (which can be coordinated by gNB-CU 202) may include the transmission of UL / DL PRS configuration and UL / DL PRS measurement information. This functionality is similar to the functionality of the LTE LMU specified in 3GPP TS 36.305 and TS 36.459 (SLmAP), and also similar to the functionality between LMF 120 and NG-RAN node 200. Therefore, NRPPa can be extended to support TRP location measurement / configuration messages, which can be carried in F1AP transmission messages.

[0079] Therefore, NG-RAN node 200 can support signaling and location protocols between gNB-CU 202 and LSS117 based on F1AP, supporting the same location protocols as those supported on the NG, Xn, and NR-Uu interfaces. Furthermore, it supports UL / DLPRS configuration and the transmission of measurement information from gNB-DU / TRP to LSS / from LSS to gNB-DU / TRP. It can be seen that NG-RAN Location Functionality (LSS) can be implemented using existing interfaces and protocols. However, assuming shared location protocols on Xn, NG, and F1, defining a new generic RAN location protocol would be effective, which can transmit messages via Xn-C or F1-C (and possibly NG). Assuming that most functionality is also required between LMF and NG-RAN nodes (i.e., supporting new Rel-16 location methods and features via 5GCNLMF), it is also possible to extend NRPPa to support additional RAN location messages.

[0080] As discussed above, the UE 102, LCS client 130, or AF requesting the location of the target UE can know the time when the location should be obtained. This time can be provided as part of the location-related request, as the scheduled location time. A location server (such as LMF 120 or LSS 117) can schedule the location measurement of the target UE 102 to occur at or near the scheduled location time and return the obtained UE location to the receiving UE, LCS client, or AF. The exact location of UE 102 at the scheduled location time can be the target, although some uncertainty or error in achieving the scheduled location time is permissible in LCS Quality of Service (QoS). The scheduled location time can be used with 5GC-MT-LR, 5GC-MO-LR, or a delayed 5GC-MT-LR for periodic or triggered location events.

[0081] Figure 3The text describes a message receiving stream 300 between the LCS client / AF 130, 5GCN 140, and NG-RAN 135 and the UE 102, using scheduled positioning times to determine the location of the UE 102. Location determination can be performed by (e.g., in 5GCN 140) the LMF 120 or by the LSS 117 in NG-RAN 135 (e.g., in a UE-assisted positioning procedure such as multiple RTT). The positioning procedure used during message receiving stream 300 may include the transmission and measurement of one or both of the DL PRS and UL probe reference signal (SRS). DL PRS and UL SRS measurements can be used, for example, to support positioning methods such as multi-cell RTT (also known as multi-RTT), where UE 102 obtains DL PRS measurements (e.g., transmitted by gNB 110) (e.g., Rx-Tx measurements) and gNB 110 in NG-RAN 135 obtains UL SRS measurements (e.g., transmitted by UE 102) (e.g., Rx-Tx measurements). Additionally, this procedure can be used in conjunction with positioning measurements (such as UL TDOA, UL AOA, DL TDOA, DL AOD, A-GNSS, WLAN, RTT, or some combination thereof). When using scheduled positioning times, as explained in message transmission stream 300, the positioning procedure consists of two phases: a positioning preparation phase 310 and a positioning execution phase 320.

[0082] In phase 312, the location preparation phase 310 begins when a location-related request is sent by LCS client 130, AF, or UE 102 to a location server (such as LMF 120 in 5GCN 140) requesting the UE's current location. This request includes a scheduled location time T and is sent at some time t1 prior to the scheduled location time, i.e., at time T-t1.

[0083] In phase 314, as part of the positioning preparation phase 310, the 5GCN 140, NG-RAN 135, and / or UE 102 interact to determine a suitable positioning method and schedule a location measurement by UE 102 at or near time T, or a location measurement performed by UE 102 occurs. The positioning preparation phase 310 ends just before time T.

[0084] In phase 322, the positioning execution phase 320 begins at or near time T, where NG-RAN 135 and / or UE 102 obtain the location measurements scheduled during the positioning preparation phase 310.

[0085] In phase 324, following the location measurement in phase 322, the location execution phase 320 includes the determination of the UE location (e.g., performed by UE 102 for a UE-based location method; or performed by LMF 120 in 5GCN 140 or LSS117 in NG-RAN 135 for a UE-assisted or network-based location method).

[0086] In phase 326, the UE location is transmitted to the receiving LCS client 130, AF, or UE 102 at a time t2 after the scheduled location time T, that is, at time T+t2.

[0087] Duration of the positioning preparation phase ( Figure 3 The t1 in the equation is not included in the total position response time. Instead, the position response time is equal to the duration of the positioning execution phase. Figure 3 (t2 in the text) can reduce the waiting time.

[0088] The scheduled location time is applied only when the external LCS client 130, AF, or UE 102 knows a specific time when the UE's location will be needed in the future. The LCS client, AF, or UE can provide a requirement for the accuracy of the scheduled location time as a supplement to the scheduled location time, which is part of the location request for UE 102. The accuracy of the scheduled location time indicates how close the desired location of UE 102 is to the scheduled location time. For example, if the scheduled location time is T and the accuracy of the scheduled location time is t, it may be necessary to obtain the location of UE 102 at time T*, where T* must be within the time period Tt to T+t. Obtaining the location of UE 102 at time T* will then satisfy the requirement of the scheduled location time accuracy t.

[0089] When scheduled location time accuracy is included, the scheduled location time may or may not interact with LCS Quality of Service (QoS). For example, regarding location accuracy requirements as part of LCS QoS, when scheduled location time accuracy is included, interaction may not be required, and the location accuracy requirement may not be affected by the presence of scheduled location time and scheduled location accuracy. Regarding response time requirements as part of LCS QoS, low latency requirements and latency tolerance requirements for response time can still be permitted individually, but may only apply to... Figure 3 The positioning execution phase shown is not applied to Figure 3The location preparation phase in the LCS QoS class. Regarding the LCS QoS class, in the case of an assured class for LCS QoS, the scheduled location timing accuracy can be met; otherwise, if the scheduled location timing accuracy cannot be met, the UE location may not be obtained, and the reason for the error may be provided to the LCS client, AF, or UE instead. In the case of a best-effort class for LCS QoS, if the scheduled location timing accuracy is not met, the location can still be obtained and provided to the LCS client, AF, or UE, with an indication regarding the failure to meet the scheduled location timing accuracy.

[0090] When scheduled location time accuracy is explicitly or implicitly omitted, LCS QoS response time requirements can be treated as just described, and LCS QoS location accuracy requirements can be reinterpreted as applicable to the accuracy of the obtained location relative to the UE's actual location at the scheduled location time. Reinterpreting LCS QoS location accuracy in this way can mean that location errors or location uncertainties can include components caused by the UE's movement during the time period between the scheduled location time and the time applicable to the location obtained for the UE. This may affect location determination but avoids the need for the LCS client to specify scheduled location time accuracy.

[0091] It should be understood that during positioning, measurements can be obtained at or near the scheduled positioning time T. The determination of the UE's location is based on these measurements; however, the positioning procedure may use optimal measurements (e.g., measurements based on the strongest received signal or the signal with the least interference), and accordingly, the time applicable to the location obtained for the UE may not be precisely the scheduled positioning time T. Thus, although the UE's location determination may have a scheduled positioning time T, the time applicable to the determined location of the UE may be a slightly different time T1. For example, the location measurements used to determine the UE's location may be obtained at time T1.

[0092] Furthermore, location determination with or without the use of scheduled positioning time will typically involve location uncertainty. For example, the estimated location for the UE may differ from the UE's actual location, and the difference between the estimated and actual locations is a location error or uncertainty.

[0093] The uncertainty of the obtained location for the UE can include a component from the location determination and can further include a component caused by time error (i.e., positioning time uncertainty). The positioning time uncertainty t can be expressed in two alternative ways. One option (A) is to explicitly specify t, which, in the case of a scheduled positioning time, can be supported by the scheduled positioning time uncertainty or the scheduled positioning time accuracy (e.g., which can be equal to t). Another option (B) can be to include the positioning time uncertainty as part of the location uncertainty, which is considered as the uncertainty or error of the UE's location at time T. For example, suppose the UE is at location L at time T, at location L1 at time T1 (where T1 is close to T), and at time T1 estimates (e.g., calculates) location L2 for the UE. Then, in option A, the location error is L1-L2, and the time error is T-T1. In option B, the location error is L-L2, and there is no explicit time error.

[0094] Figure 4 An example of using the scheduled positioning time T to determine the location of UE 102 is explained when the applicable time T1 for determining the location of UE 102 is different from the time T1. As indicated by white dot 402, UE 102 may be at location L at the scheduled positioning time T. Gray dot 404 indicates the actual location L1 of UE 102 at time T1, where T1 is the time applicable to the location obtained for UE 102. Based on the assumption that UE 102 is moving, the actual location L1 indicated by gray dot 404 (at time T1) is at a different location than the location L indicated by white dot 402 (at time T). If UE 102 is stationary between time T and T1, the actual location L1 at time T1 will coincide with the location L at time T. Additionally, Figure 4 The black dot 406 in the diagram represents the estimated (e.g., calculated) position L2 of UE 102 at time T1. Due to position errors (e.g., errors in position measurement and / or position calculation), the estimated position L2 (at time T1) represented by the black dot 406 is at a different position than the actual position L1 (at time T1).

[0095] Therefore, as from Figure 4 As explained, due to the use of the scheduled positioning time, the location error may include a component caused by the location determination, and may further include a component caused by the movement of the UE 102 during the time period between the scheduled positioning time and the time applicable to the location obtained for the UE 102. Accordingly, when reporting the determined location of the UE 102 at the scheduled positioning time, the location uncertainty should include not only the location error component but also the time error component.

[0096] In one option, namely Figure 4 In option A as explained, the uncertainty in location can be reported using separate location error and time error components. For example, the location error component is an estimate (e.g., prediction) of the difference x between the actual location L1 at measurement time T1 and the estimated location L2 at measurement time T1, i.e., x = L1 - L2. The time error component is an estimate of the difference t between the scheduled positioning time T and the measurement time T1, i.e., t = T - T1.

[0097] In another option, namely Figure 4 In option B as explained, the location uncertainty can be reported based on a combination of location error components and time error components. For example, the time error component can be converted into a location error based on the known (e.g., measured) velocity of UE 102 or based on UE 102 location measurements obtained shortly before and after the scheduled positioning time. Accordingly, the combined location error can be reported as an estimate of L-L2, which includes the time error component, and thus, the individual time error component is not reported.

[0098] Figure 5 Example 500 illustrates the uncertainty that can be associated with the determined location of UE 102 due to the location uncertainty and time uncertainty from the scheduled location time. Figure 5 The explanation covers 2D position in the horizontal plane (e.g., in the XY coordinate system), but... Figure 5 The 3D version can be achieved by... Figure 5 The circle shown is created by transforming it into a sphere. (As...) Figure 4 As described, UE 102 has an actual position L at a scheduled positioning time T, an actual position L1 at a measurement time T1, and an estimated position L2 at a measurement time T1, wherein time T1 can differ from time T by a maximum amount t according to Tt≤T1≤T+t. For example, t can be a scheduled positioning time accuracy requirement or accuracy target, which can be implicit and can be estimated based on the known time for obtaining the position measurement for UE 102.

[0099] like Figure 5The estimated location L2, as described by black dot 502, is a location obtained by a location server (e.g., LMF120 or LSS117), or a location obtained by UE 102 for UE 102 at time T1, where UE 102 is at its actual location L1. The estimated location L2 is associated with a location uncertainty region 504, which is described as the gray interior of a circle of radius x surrounding point 502, where x is the estimated maximum difference between the estimated location L2 and the actual location L1 at time T1, i.e., x = MAX(L1 - L2). There may be some confidence level associated with the value x. For example, x can be estimated such that L1 - L2 has a 67% (or 90% or 95%) probability of being less than x. The actual location L1 at time T1 can be anywhere within the uncertainty region 504 of radius x (e.g., with some level of confidence). It should be understood that the uncertainty region 504 may not be the interior of a circle, but may have other geometries (e.g., it may be the interior of an ellipse or a three-dimensional sphere or ellipsoid). Furthermore, as already discussed, the magnitude (radius) of the uncertainty can be determined by the desired confidence level. In other words, although the estimated location L2 is known, the actual location L1 at time T1 is unknown, but the uncertainty can be determined using the desired confidence level, for example, such that the actual location L1 has the desired probability (confidence level) of being located within the uncertainty region 504. The determination of the location uncertainty region 504 with the desired confidence level is routinely performed and reported during positioning.

[0100] If the estimated location has the maximum error, i.e., the actual location L1 lies on the perimeter (or surface) of the uncertain region (or volume) 504, then gray point 506 represents one possibility for the actual location L1 of the UE. The actual location L1 at point 506 is associated with a time uncertainty t, which is the difference (or maximum difference) between the scheduled positioning time T and the measurement time T1, i.e., t = T - T1 (or t = MAX(T - T1)). The location server (e.g., LMF 120 or LSS 117 (or UE 102)) can determine the distance D associated with the time uncertainty t, for example, based on the speed of UE 102 (whereby the server (or UE 102) can receive data from UE 102), or D can be determined using one or more location measurements. The distance D can be an estimate of the maximum distance between location L and location L1, and therefore can be an estimate of the maximum distance UE 102 can move between time T and time T1. As before, distance D can have an associated confidence level—for example, where the actual distance between locations L and L1 is less than D with a confidence level of 67% (or 90% or 95%). Distance D can be determined based on the estimated velocity v of UE 102 and the time uncertainty t, resulting in D = v*t. The distance D associated with the time uncertainty t can be determined based on several measurements, or based on UE 102 location measurements obtained shortly before and after the scheduled positioning time T. For example, multiple measurements can be obtained close to or at the scheduled positioning time T, and the determination of the estimated location L2 of UE 102 can be based on the best measurement from measurement time T1 (e.g., based on the measurement of the strongest received signal or the signal with the least interference, etc.). The location server (or UE 102) can generate additional location estimates using multiple measurements over time periods Tt to T+t, and distance D can be determined based on these location estimates. The actual position L can subsequently be located within a distance D of the actual position L1, and therefore can be located anywhere within the uncertain region 508, which is the interior of a circle 516 with radius D centered on position L1. Possible positions L with the maximum distance to the estimated position L2 are indicated by white dots 510. Other gray dots 506 and white dots 510 can be used in... Figure 5 Add similar exemplary positions L1 and L. The white point 510 with the maximum distance from position L2 will be located on the circumference of a circle 514 centered at position L2 with a radius of x+D.

[0101] White dot 510 represents one possible actual location L for UE 102 at the scheduled positioning time T. However, the actual location L1 (shown as gray dot 506) can be located anywhere on or inside the perimeter of uncertainty region 504. Similarly, for each possible actual location L1, the actual location L can be anywhere on or inside the perimeter of uncertainty region 508, which in this example is the interior of circle 516 (although in different examples it may be another geometry, such as an ellipse, sphere, or ellipsoid). For each possible actual location L1, the combination of uncertainty region 504 of actual location L1 and uncertainty region 508 of actual location L results in uncertainty region 512 of actual location L, which is the union of all possible uncertainty regions 508. Figure 5 In the example, the uncertainty region 512 is the interior of circle 514, but in other examples it may have other geometries (e.g., ellipse, sphere, or ellipsoid). Accordingly, the location uncertainty region 512 of position L associated with the estimated position L2 at point 502 (which may also be referred to as location uncertainty only) can be generated based on the location uncertainty x of position L1 (which is also the location error of position L2 relative to position L1) and the distance D corresponding to the time uncertainty t of position L1 (which is also the time error of position L2). In this example, the combined location uncertainty 512 (which applies to the previously described option (B)) can be the interior of a circle with radius x+D.

[0102] Figure 6 This describes message flow 600 between LCS client 130, 5GCN LCS entity 602 (such as GMLC 125 or AMF 115 and NEF127), LMF 120, gNB 110, and UE 102 for message transmission of a multi-RTT location procedure as described in 3GPP TS 38.305, where the UE's location determination time is pre-scheduled. The serving gNB 110-1 and multiple adjacent gNBs 110-2, 110-3, and 110-4 can be collectively referred to as gNB 110. While the use of LMF 120... Figure 6The explanation should be understood that other entities can be used instead of LMF 120 to determine the location and location uncertainty of UE 102, including, for example, SLP 129, or LSS117 (or LMC) or UE 102 in NG-RAN 135. For example, LSS 117 could be a logical function serving gNB 110-1CU. In some implementations, LSS117 can be inside gNB 110-1 but connected to the CU or outside gNB 110-1. For example, if LSS117 is outside gNB 110-1 or separate from gNB 110-1CU, additional messages (e.g., XnAP messages) can be used to pass messages from gNB 110-1 to LSS117 and back from LSS117 to gNB 110-1. For inclusivity, Figure 6 The positioning procedure described herein includes both DL PRS and UL SRS measurements. DL PRS and UL SRS measurements can, for example, be used to support positioning methods such as multi-cell RTT (also known as multi-RTT), where UE 102 obtains DL measurements and gNB 110 obtains UL measurements. However, it should be understood that... Figure 6 The procedure described herein can be used with other types of positioning methods, such as those that rely solely on DL PRS by excluding the phase associated with UL PRS, or those that rely solely on UL SRS by excluding the phase associated with DL PRS. Accordingly, the procedure can be used with positioning measurements such as UL-TDOA, UL-AOA, DL-TDOA, DL-AOD, A-GNSS, WLAN, RTT, multi-cell RTT, or some combination thereof. For example, to support UL positioning methods such as UL-TDOA or UL-AOA, where gNB 110 measures the UL SRS signal from UE 102, but UE 102 does not measure the DL PRS signal or other DL signals (e.g., from SV 190 or WLAN AP) from gNB 110, these can be omitted. Figure 6 Phases 0, 7, 8, 9a, and 10 are also included. Similarly, to support DL positioning methods such as DL-TDOA, DL-AOD, A-GNSS, or WLAN, where UE 102 measures the DL PRS signal or other DL signals (e.g., from SV 190 or WLAN AP) from gNB 110, but gNB 110 does not measure the UL SRS signal from UE 102, this can be omitted. Figure 6 Phases 2-6, 9b, and 11.

[0103] like Figure 6As explained in the document, the positioning procedure can request and schedule the location of UE102 before it is needed (e.g., at time T). Accordingly, the left side of the message flow is a timeline, explaining when each phase is executed relative to the scheduled positioning time T. As explained, phases 0-8 are all parts of the positioning preparation phase and are executed before time T. At time T, UL and DL signals are transmitted and measured. After time T, the positioning execution phase occurs, which is explained as including phases 9-12 and C. Message flow 600 explains that LMF 120 is used for positioning determination, but if needed, LSS117 (or LMC) in service gNB 110-1 or UE102 itself can be used to further reduce the waiting time in the positioning procedure, for example, during the positioning execution phase. Figure 6 In Phase A, a location service request from LCS client 130 is sent to LMF 120 via one or more 5GCN LCS entities 602, and includes a scheduled location time T in a format suitable for LCS client 130. In this example, the location time T may be provided in Coordinated Universal Time (UTC) and defines a request to obtain the location of the target device at T = 12:34:0000Z in the future. This request may include the uncertainty required for the UE's location, which could be the maximum difference (e.g., maximum distance) between the UE's estimated location and the UE's actual location at the scheduled location time T. For example, the request may include a time window or uncertainty t for the location time; that is, the expected location time is T ± t seconds. Figure 4 The positioning time uncertainty t discussed herein can be represented in two alternative ways. One option (A) is to explicitly specify t. The other option (B) is to include the positioning time uncertainty as part of the location uncertainty, which is considered as an uncertainty or error in the UE's location at time T. For example, suppose UE 102 is at location L at time T, at location L1 (close to T) at time T1, and obtains location L2 for the UE at time T1. With option A, the location error is L1-L2, and the time error is T-T1. With option B, the location error is L-L2, and there is no time error. Option B may require a more complex implementation such as LMF 120 (or SLP 129, LSS117, or UE 102), which requires determining the location uncertainty based on both the location error and the time error, such as Figure 5As discussed in [the document]. Therefore, in the implementation of supporting combined location and time uncertainties for the scheduled positioning time, based on support for option B, a time window or uncertainty t can be provided in stage A, instead of just the required location accuracy (e.g., maximum location error). However, the location server (e.g., LMF 120) can still determine a time window or uncertainty t that is not visible to the LCS client 130, which can be used to help support the required location accuracy specified by the LCS client 130.

[0104] In phase B, LMF 120 schedules a location session for target UE 102 so that the UE location can be obtained (e.g., as close as possible) at the requested time T (i.e., in this example, the UE location is valid at time T = 12:34:0000Z).

[0105] The positioning preparation phase begins at phase 0 at time T–t1, where t1 depends on the expected duration of the positioning preparation phase (which depends, for example, on the chosen positioning method, etc.).

[0106] In Phase 0, LMF 120 and gNB 110 can use, for example, NRPPaDL PRS configuration information exchange as described in 3GPP TS 38.455 to obtain or send to gNB 110 DL PRS configuration information required for a positioning method (e.g., multi-RTT positioning) (e.g., including parameters for DL ​​PRS transmission, such as PRS frequency, bandwidth, timing, decoding, silence, frequency hopping). PRS configuration information can also be sent as auxiliary data to UE 102 (in Phase 7) and / or LSS 117 (not shown). PRS configuration information can be used by: UE 102 to assist DL PRS measurements in Phase 9a; LMF 120 to request UL SRS configuration information from serving gNB 110-1 for UE 102 in Phase 2; and / or by LSS 117 to assist in calculating the location of UE 102.

[0107] In Phase 1, LMF 120 may use the LPP capability delivery procedure to request the location capability of UE 102, for example, as described in 3GPP TS 37.355.

[0108] In phase 2, LMF 120 sends an NRPPa location information request message to serving gNB 110-1 to request UL information for UE 102.

[0109] In phase 3, the service gNB 110-1 determines the resources available for UL SRS and configures UE 102 with the UL-SRS resource set in phase 3a.

[0110] In phase 4, service gNB 110-1 provides UL SRS configuration information to LMF 120 in an NRPPa location information response message.

[0111] In phase 5a, LMF 120 sends an NRPPa location activation request to serving gNB 110-1, requesting UE SRS activation. The NRPPa location activation request message may include the time T for measuring the location of UE 102, and thus include that UE 102 needs to transmit UL SRS so that the UL measurement at phase 9b can occur at or near time T. In phase 5b, serving gNB 110-1 activates UE SRS transmission at or near time T. UE 102 will wait until or near time T before initiating UL SRS transmission. In phase 5c, serving gNB 110-1 sends an NRPPa location activation response message to LMF 120 instructing UE 102 to activate SRS.

[0112] In Phase 6, LMF 120 requests UL measurements of UE 102's UL SRS transmission from each of the selected gNBs 110 by sending an NRPPa Measurement Request message to each of the selected gNBs 110. Each message may include an indication of the physical measurement time T' to perform the UL measurement. Time T' ultimately defines the time when UE 102's location is valid / acquired. Time T' may specify, for example, an NR or LTE system frame number (SFN) and / or a subframe slot number. Time T' may have a one-to-one (1:1) relationship with T (e.g., a 1:1 relationship with the UTC time requested in Phase A). For example, T' may be equal to T or may be slightly different (e.g., 1-100 milliseconds (ms) different). This difference may be necessary if it is not possible to schedule UE 102's UL SRS transmission or gNB 110's DL PRS transmission exactly at time T. The message includes all the information required for gNB / TRP 110 to perform the UL measurement.

[0113] In phase 7, LMF 120 sends an LPP Assistance Data Message to UE 102. This message includes any assistance data required by UE 102 to perform necessary DL PRS measurements (e.g., including PRS configuration information sent or received by LMF 120 in phase 0).

[0114] In phase 8, LMF 120 sends an LPP request location information message to UE 102 to request DL measurement (e.g., UE Rx-Tx) to support multiple RTT. The request location information message includes an indication of time T' as in phase 6 (e.g., where T' = T or T' is slightly different from T). The request location information message may further indicate the type of positioning method to be used, such as UE-assisted multiple RTT.

[0115] In phase 9a, at or near the scheduled positioning time T, UE 102 performs location measurements, such as DL PRS measurements (e.g., RSTD, RSRP, RSRQ, AOD, AOA, Rx-Tx) from all gNBs 110 provided in the auxiliary data of phase 7. UE 102 performs measurements such that the measurement / position is valid at time T' (e.g., corresponding to the physical time base of T). Location measurements may additionally or alternatively include one of the following: GNSS pseudorange, GNSS code phase, GNSS carrier phase, WiFi measurements (RSSI, AOA, or RTT), Bluetooth measurements (RSSI, AOA, or RTT), measurements of DL NR signals (RSTD, RSRP, RSRQ, AOD, AOA, Rx-Tx) from gNBs, or measurements performed by sensors (e.g., inertial sensors, barometers, etc.).

[0116] In phase 9b, at or near time T, each gNB 110 configured in phase 6 measures UL SRS transmissions from UE 102, such as AOA, RSRP, Rx-Tx, TOA. The gNB 110 performs the measurement such that the measurement / location is valid at time T' (e.g., corresponding to the physical time base of T).

[0117] UE 102 and / or gNB 110 thus acquire multiple measurements in phases 9a and 9b within a time period that may include the scheduled positioning time T. For example, the measurements may occur within time periods of less than 1 second, less than 100 ms, less than 10 ms, or less than 1 ms during the duration.

[0118] In phase 10, UE 102 reports the measurements performed in phase 9a to LMF 120 in an LPP location information provision message, which may identify the measurement time T”. The location report in phase 10 includes the measurement / location estimate and may optionally include the time T” (e.g., where T” is as close as possible to the requested time T’; i.e., ideally T” = T’). Then the positioning time error = (T” - T’). UE 102 can provide an indication of its velocity and / or the distance moved between time T’ and time T” or allow LMF 120 to determine the UE 102’s velocity or distance moved by measurements (e.g., sensor measurements).

[0119] In phase 11, each of the adjacent gNBs 110-2, 110-3, and 110-4 reports the measurement performed in phase 9b to the LMF120 in an NRPPa measurement response message, which may also identify the time T”' when the measurement was obtained. The position report in phase 11 includes the measurement / position estimate, and optionally includes the time T”' together (e.g., where T”' is as close as possible to the requested time T'; i.e., ideally T”' = T'). Then the positioning time error = (T”' - T').

[0120] In phase 12, LMF 120 determines the location of UE 102 based on measurements received in phases 10 and 11. For example, LMF 120 can determine the RTT and calculate the location of UE 102 based on UE 102 and the gNB 110Rx-Tx time difference measurement for each gNB 110, for which corresponding UL and DL measurements are provided in phases 10 and 11. LMF 120 further determines the location uncertainty. For example, LMF 120 can determine the location of UE 102 with an uncertainty not exceeding the required uncertainty indicated in phase A. Figure 4 and 5 As discussed herein, LMF 120 can determine an uncertainty that is an indication of the difference between the determined (i.e., estimated) location of UE 102 and the actual location of UE 102 at the scheduled positioning time T. The location of UE 102 can be an estimate of the actual location of UE 102 at time T1, which is within a time period including the scheduled positioning time T. This time period can, for example, be less than 1 second, less than 100 ms, less than 10 ms, or less than 1 ms. The uncertainty of the location of UE 102 can indicate an error in the estimate of the actual location of UE 102 at time T1, combined with an error in the estimate of the distance UE 102 moves between time T and time T1. Figure 4 and Figure 5 The location uncertainty discussed herein can be, for example, a combination of a first location uncertainty based on location measurements but not on the scheduled positioning time and a second location uncertainty based on the scheduled positioning time. For example, as... Figure 4 and 5As discussed herein, LMF 120 can determine location uncertainty by determining a first location uncertainty based on an estimate of the difference between the determined location L2 and the actual location L1 of UE 102 at time T1 during multiple time periods and / or time segments measured in phases 9a and 9b. A second location uncertainty can be determined based on an estimate of the difference between the actual location L1 of UE 102 at time T1 and the actual location L of UE 102 at the scheduled positioning time T. LMF 120 can combine the first and second location uncertainties to determine the location uncertainty of UE 102.

[0121] It should be understood that although phase 12 explains the location and uncertainty of UE 102 determined by LMF 120, other entities may also perform this phase, including UE 102, SLP 129, gNB 110, LSS117 (or LMC in NG-RAN 135).

[0122] In phase C, LMF 120 sends a location service response to LCS client 140 via one or more 5GCN LCS entities 602, providing the location of UE 102 and a location uncertainty indicating the difference between the UE's location at the scheduled location time T and the UE's actual location. In this example, a timestamp indicating a location time of T = 12:34:0000Z+δ may also be included. This location estimate is received by LCS client 130 at time T+t2 (i.e., in this example, at T = 12:34:0000Z+δ+t2), where t2 is the waiting time and δ (which can be positive or negative) is the difference between the requested location time and the actual location time.

[0123] Figure 7 A schematic block diagram illustrating certain exemplary features of entity 700 in an explanatory wireless network is shown. Entity 700 is configured to perform localization of UE 102 using a scheduled localization time and a combination of location and time uncertainties, as discussed herein. Entity 700 may be an LMF 120, SLP 129, gNB 110, LSS117 (or LMC) in NG-RAN 135, or UE 102, as... Figure 1 and 2 As shown in the diagram. Entity 700 can be configured to perform... Figure 6 The message flow 600 explained in the text includes the determination of uncertainty, such as Figure 4 and 5 The explanation in the text, and Figure 8The procedure 800 described herein and other algorithms discussed herein. Entity 700 may include, for example, one or more processors 702, memory 704, and external interfaces 710 (e.g., wired or wireless network interfaces to base stations, UEs, and / or entities in the core network), which may be operatively coupled to non-transient computer-readable medium 720 and memory 704 via one or more connections 706 (e.g., bus, line, fiber, link, etc.). In some example implementations, all or part of entity 700 may take the form of a chipset, etc. Depending on the implementation, entity 700 may include additional components not described herein. For example, if entity 700 is a UE, it may be able to... Figure 1 The SV 190 shown includes additional components (such as an SPS receiver) that receive and process SPS signals to measure GNSS pseudorange, GNSS code phase, GNSS carrier phase, etc., and sensors (e.g., inertial sensors, such as one or more accelerometers, one or more gyroscopes, magnetometers, barometers, etc.). The UE's external interface 710 may include a WWAN transceiver, comprising transmitters and receivers capable of measuring RSTD, RSRP, RSRQ, AOD, AOA, Rx-Tx, etc., of DL NR signals from the gNB, and / or a WLAN transceiver, comprising transmitters and receivers capable of measuring, for example, WiFi measurements (such as RSSI, AOA, or RTT), Bluetooth measurements (such as RSSI, AOA, or RTT), etc. If entity 700 is a base station, the external interface may include a WWAN transceiver comprising transmitters and receivers capable of measuring AOA, RSRP, Rx-TX, TOA, etc., of UL SRS signals from the UE 102. The external interface 710 of the base station may further include wired or wireless network interfaces to the core network entity.

[0124] The one or more processors 702 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 702 may be configured to perform the functions discussed herein by implementing one or more instructions or program code 708 on a non-transient computer-readable medium, such as medium 720 and / or memory 704. In some embodiments, the one or more processors 702 may represent one or more circuits that may be configured to perform at least a portion of a data signal calculation procedure or process associated with the operation of entity 700.

[0125] Medium 720 and / or memory 704 may store instruction or program code 708 containing executable code or software instructions that, when executed by one or more processors 702, cause those processors 702 to operate as a dedicated computer programmed to perform the techniques disclosed herein. As explained in entity 700, medium 720 and / or memory 704 may include one or more components or modules that may be implemented by the one or more processors 702 to perform the methodologies described herein. Although each component or module is described as software in medium 720 executable by the one or more processors 702, it should be understood that each component or module may be stored in memory 704 or may be dedicated hardware in or outside of the one or more processors 702.

[0126] Several software modules and data tables may reside in medium 720 and / or memory 704 and be utilized by one or more processors 702 to manage both the communication and functionality described herein. It should be understood that the organization of the contents of medium 720 and / or memory 704 as shown in entity 700 is merely exemplary, and thus, the functionality of the individual modules and / or data structures may be combined, separated, and / or constructed in different ways depending on the implementation of entity 700.

[0127] The medium 720 and / or memory 704 may include a location measurement module 722, which, when implemented by one or more processors 702, configures the processors 702 to receive location measurements for the UE from one or more other entities (such as UE 102 or one or more gNBs 110) via an external interface 710. The location measurements may be obtained by the one or more other entities at multiple times within a time period including the scheduled positioning time; for example, the time period may be less than 1 second, less than 100 ms, less than 10 ms, or less than 1 ms. The one or more processors 702 may be further configured to receive the UE's velocity at or near the scheduled positioning time.

[0128] The medium 720 and / or memory 704 may include a positioning module 724, which, when implemented by one or more processors 702, configures the processors 702 to determine the UE's location based on location measurements. For example, the location may be an estimate of the UE's actual location over a time period including a scheduled positioning time. For example, the one or more processors 702 may be further configured to receive a request for the UE's location from another entity, such as LCS client 140, AF, or UE 102. This request may include a required uncertainty regarding the UE's location, which includes the maximum difference between the UE's location at the scheduled positioning time and the UE's actual location. The one or more processors 702 may be configured to determine the UE's location with an uncertainty not exceeding the required uncertainty.

[0129] The medium 720 and / or memory 704 may include an uncertainty module 726, which, when implemented by one or more processors 702, configures the processors 702 to determine an uncertainty in the determined location, wherein the uncertainty indicates the difference between the UE's determined location at a scheduled positioning time and the UE's actual location. For example, the determined location for the UE may be an estimate of the UE's actual location at time T1, which is close to the scheduled positioning time T, and the location uncertainty may indicate an error in the estimate of the UE's actual location at time T1, combined with an error in the estimate of the distance the UE moves between the scheduled positioning time T and time T1. For example, the one or more processors 702 may be configured to determine the location uncertainty by determining a first location uncertainty based on an estimate of the difference between the UE's determined location at one time during a plurality of time periods in which positioning measurements are obtained and the UE's actual location. For example, the one or more processors 702 may be further configured to determine a second location uncertainty based on an estimate of the difference between the UE's actual location at that one time and the UE's actual location at the scheduled positioning time. For example, the second location uncertainty may be based on, for instance, the velocity of the UE received using positioning measurements, or on UE location measurements obtained shortly before and after the scheduled positioning time. For example, one or more processors 702 may be configured to combine the first and second location uncertainties to determine the location uncertainty.

[0130] The medium 720 and / or memory 704 may include a reporting module 728, which, when implemented by one or more processors 702, configures one or more processors 702 to send the location and location uncertainty to another entity, such as a requesting entity (which may be, for example, LCS client 140, AF, or UE 102), via an external interface 710.

[0131] The methodologies described herein can be implemented through various means depending on the application. For example, these methodologies can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, the one or more processors 702 can be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0132] For firmware and / or software implementations, these methodologies can be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methodologies described herein. For example, software code can be stored in a non-transient computer-readable medium 720 or memory 704 connected to and executed by one or more processors 704. Memory can be implemented within or outside of the one or more processors. As used herein, the term "memory" means any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type or number of memories, or the type of medium on which memory is stored.

[0133] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 708 on a non-transient computer-readable medium (such as medium 720 and / or memory 704). Examples include computer-readable media encoding data structures and computer-readable media encoding computer program code 708. For example, a non-transient computer-readable medium including program code 708 stored thereon may include program code 708 that supports UE location determination using scheduled positioning time and combined location and time uncertainties in a manner consistent with the disclosed embodiments. The non-transient computer-readable medium 720 includes a physical computer storage medium. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transient computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code 708 in the form of instructions or data structures and that can be accessed by a computer; as used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs, wherein disks often magnetically reproduce data, while discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0134] In addition to being stored on the computer-readable medium 720, instructions and / or data may also be provided as signals included on a transmission medium in the communication apparatus. For example, the communication apparatus may include an external interface 710 having signals indicating instructions and data. These instructions and data are configured to cause one or more processors to perform the functions outlined in the claims. That is, the communication apparatus includes a transmission medium having signals indicating information for performing the disclosed functions.

[0135] Memory 704 can represent any data storage device. Memory 704 may include, for example, main memory and / or secondary memory. Main memory may include, for example, random access memory, read-only memory, etc. Although described in this example as being separate from one or more processors 702, it should be understood that all or part of the main memory may be located within one or more processors 702 or otherwise co-located / coupled with one or more processors 702. Secondary memory may include, for example, memory of the same or similar type as the main memory and / or one or more data storage devices or systems (such as, for example, disk drives, optical disc drives, tape drives, solid-state drives, etc.).

[0136] In some implementations, secondary memory may be operatively accommodated or otherwise configured to be coupled to non-transient computer-readable medium 720. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of all or part of a computer-readable medium 720 that may include computer-implementable program code 708 stored thereon, which, when executed by one or more processors 702, may be operatively implemented to perform all or part of the example operations as described herein. Computer-readable medium 720 may be part of memory 704.

[0137] Figure 8 A flowchart of an exemplary method 800 for locating user equipment (e.g., UE 102) at a scheduled location time is shown, the method being performed by an entity (such as...) in a manner consistent with the disclosed implementation. Figure 7 The entity can be UE 102, LMF 120, SLP 129, gNB 110, LSS117 or LMC in NG-RAN 135.

[0138] In box 802, the entity receives location measurements for the UE from one or more other entities, which are obtained by the one or more other entities at multiple times within a time period including the scheduled location time, for example, as in Figure 6 As discussed in stages 10 and 11. For example, one or more other entities may include at least one of the UE, the serving gNB (e.g., gNB 110-1), or the neighboring gNB (e.g., gNB 110). Location measurements may include at least one of GNSS pseudorange, GNSS code phase, GNSS carrier phase, WiFi measurements (e.g., RSSI, AOA, or RTT), Bluetooth measurements (e.g., RSSI, AOA, or RTT), measurements of DL NR signals (e.g., DL PRS signals) from the gNB (e.g., RSTD, RSRP, RSRQ, AOD, AOA, Rx-Tx), measurements of UL NR signals (e.g., UL SRS signals) from the UE (e.g., AOA, RSRP, Rx-Tx, TOA), and measurements performed by a sensor (e.g., an inertial sensor or barometer for the UE). For example, the time period may be less than 1 second, less than 100 ms, less than 10 ms, or less than 1 ms. An apparatus for receiving location measurements for a UE from one or more other entities, the location measurements obtained by the one or more other entities at multiple times within a time period including a scheduled positioning time, may include, for example, an external interface 710 and one or more processors 702, the one or more processors 702 having executable code or software instructions in dedicated hardware or in memory 704 and / or media 720 in implementation entity 700, such as Figure 7The position measurement module 722 is shown.

[0139] In box 804, the entity determines the UE's location based on location measurements, for example, such as Figure 6 The stage 12 discussed. An apparatus for determining the location of a UE based on location measurements may include, for example, one or more processors 702, which have executable code or software instructions in memory 704 and / or media 720 of dedicated hardware or implementation entity 700, such as Figure 7 The positioning module 724 shown.

[0140] In box 806, the entity determines the uncertainty of location, where this uncertainty indicates the difference between the UE's location at the scheduled positioning time and the UE's actual location, for example, as... Figure 6 The discussion in stage 12 and in Figure 4 and 5 As discussed in [the document]. For example, the UE's location is an estimate of the UE's actual location at a certain time within a time period. Location uncertainty can subsequently indicate the error in the estimate of the UE's actual location at that time, combined with errors in the estimate of the distance the UE moved between the scheduled positioning time and that time. An apparatus for determining location uncertainty (wherein the uncertainty indicates the difference between the UE's location at the scheduled positioning time and the UE's actual location) may include, for example, one or more processors 702, which have executable code or software instructions in the memory 704 and / or medium 720 of the dedicated hardware or implementation entity 700, such as […]. Figure 7 The uncertainty module 726 is shown.

[0141] In box 808, an entity sends its location and location uncertainty to another entity, for example, as... Figure 6 As discussed in stage C, an apparatus for transmitting location and location uncertainty to another entity may include, for example, one or more processors 702, which have executable code or software instructions in dedicated hardware or the memory 704 and / or medium 720 of the implementation entity 700, such as... Figure 7 The report module 728 shown.

[0142] In one implementation, location uncertainty can include a combination of a first location uncertainty and a second location uncertainty, wherein the first location uncertainty is based on location measurements but not on a scheduled positioning time, and the second location uncertainty is based on the scheduled positioning time. For example, an entity can determine location uncertainty by determining the first location uncertainty based on an estimate of the difference between the UE's location and its actual location at a time during multiple time periods (or within a time period), for example, as in... Figure 6 Phase 12 and Figure 4 and Figure 5 The entity discussed can determine the second location uncertainty based on an estimate of the difference between the UE's actual location at one time and the UE's actual location at the scheduled location time, for example, as in Figure 6 Phase 12 and Figure 4 and Figure 5 The entity under discussion can combine a first positional uncertainty and a second positional uncertainty to determine the positional uncertainty, for example, as in... Figure 6 Phase 12 and Figure 4 and Figure 5 The discussed method is an apparatus for determining position uncertainty by determining a first position uncertainty based on an estimate of the difference between the UE's position at one time during a plurality of time periods and the UE's actual position. This apparatus may include, for example, one or more processors 702, which have executable code or software instructions in memory 704 and / or media 720 of a dedicated hardware or implementation entity 700, such as... Figure 7 The uncertainty module 726 is shown. An apparatus for determining a second location uncertainty based on an estimate of the difference between the actual location of the UE at one time and the actual location of the UE at a scheduled positioning time may include, for example, one or more processors 702, which have executable code or software instructions in the memory 704 and / or medium 720 of the dedicated hardware or implementation entity 700, such as... Figure 7 The uncertainty module 726 is shown. An apparatus for combining a first position uncertainty and a second position uncertainty to determine the position uncertainty may include, for example, one or more processors 702, which have executable code or software instructions in a memory 704 and / or medium 720 of a dedicated hardware or implementation entity 700, such as... Figure 7 The uncertainty module 726 is shown.

[0143] In one implementation, an entity may receive a request for the location of a UE from another entity. This request includes a required uncertainty regarding the UE's location, which includes the maximum difference between the UE's location at the scheduled location time and the UE's actual location, for example, as in... Figure 6 This is discussed in phase A. An entity can determine the location of the UE, where the uncertainty of the location does not exceed the required uncertainty, for example, as in... Figure 6 The process discussed in stage 12. An apparatus for receiving a request for the location of a UE from another entity (the request including a required uncertainty regarding the UE's location, the required uncertainty including the maximum difference between the UE's location at a scheduled location time and the UE's actual location) may include, for example, one or more processors 702, the one or more processors 702 having executable code or software instructions in dedicated hardware or the memory 704 and / or medium 720 of the implementation entity 700, such as... Figure 7 The positioning module 724 is shown. An apparatus for determining the location of a UE (where the uncertainty of the location does not exceed the required uncertainty) may include, for example, one or more processors 702, which have executable code or software instructions in the memory 704 and / or medium 720 of the dedicated hardware or implementation entity 700, such as Figure 7 The positioning module 724 shown.

[0144] Throughout this specification, the terms "an example," "an example," "some examples," or "exemplary implementation" mean that a particular feature, structure, or characteristic described in conjunction with a feature and / or example may be included in at least one feature and / or example of the claimed subject matter. Therefore, phrases appearing throughout the specification such as "an example," "an example," "some examples," or "in some implementations," or other similar phrases, do not necessarily all refer to the same feature, example, and / or limitation. Furthermore, these particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0145] Some portions of the detailed description included herein are presented in the form of algorithms or symbolic representations of operations on binary digital signals stored in the memory of a particular device or dedicated computing device or platform. In the context of this particular specification, the terms "particular device," etc., include general-purpose computers that, once programmed, perform specific operations according to instructions from program software. Algorithm descriptions or symbolic representations are examples of techniques used by those skilled in the art of signal processing or related fields to convey the essence of their work to others skilled in the art. An algorithm herein and generally is considered as a self-consistent sequence of operations or similar signal processing leading to a desired result. In this context, the operation or processing involves the physical manipulation of physical quantities. Typically, but not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transmitted, combined, compared, or otherwise manipulated. It has proven convenient at times to refer to such signals as bits, data, values, elements, symbols, characters, items, numbers, numerical values, etc., primarily for reasons of general use. However, it should be understood that all such terms, or similar terms, are to be associated with the appropriate physical quantity and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the discussion herein, throughout this specification, the use of terms such as “processing,” “calculating,” “determining,” and “determining” refers to the actions or processes of a particular device (such as a dedicated computer, dedicated computing device, or similar dedicated electronic computing device). In the context of this specification, therefore, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or transforming signals that are generally represented as physical electronic or magnetic quantities within the memory, registers, or other information storage, transmission, or display devices of such dedicated computer or similar dedicated electronic computing device.

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

[0147] As used herein, the terms “and,” “or,” and “and / or” may include a variety of meanings, which are also contemplated, at least in part, depending on the context in which such terms are used. Generally, “or,” when used to relate a list such as A, B, or C, is intended to mean A, B, and C (in the inclusive sense) and A, B, or C (in the exclusive sense). Additionally, the term “one or more” as used herein may be used to describe any feature, structure, or characteristic in the singular form, or to describe multiple features, structures, or characteristics, or some other combination thereof. However, it should be noted that this is merely an illustrative example, and the claimed subject matter is not limited to this example.

[0148] While the features currently considered exemplary have been explained and described, those skilled in the art will understand that various other modifications can be made and equivalents can be substituted without departing from the claimed subject matter. Additionally, numerous modifications can be made to adapt a particular scenario to the teachings of the claimed subject matter without departing from the central concepts described herein.

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

[0150] In view of this specification, various embodiments may include different combinations of features. Examples of implementations are described in the following numbered clauses:

[0151] Clause 1. A method for locating a user equipment (UE) at an entity at a scheduled location time, comprising: receiving a location measurement for the UE from one or more other entities, the location measurement being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determining the location of the UE based on the location measurement; determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmitting the location and the uncertainty in the location to another entity.

[0152] Clause 2. The method of Clause 1, wherein the entity is a UE, a location management function (LMF), a secure user plane location (SUPL) location platform (SLP), a new radio node B (gNB), a location server agent (LSS), or a location management component (LMC).

[0153] Clause 3. The method of either Clause 1 or 2, wherein the one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

[0154] Clause 4. The method of any of Clauses 1-3, wherein the location measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi (also known as Wi-Fi) measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink (DL) New Radio (NR) signals from NR Node B (gNB), including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); measurement of uplink (UL) NR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by sensors including inertial sensors or barometers.

[0155] Clause 5. The method of any of Clauses 1-4, wherein the time period is less than 1 second, less than 100 milliseconds (ms), less than 10 ms, or less than 1 ms.

[0156] Clause 6. The method of any of Clauses 1-5, wherein the location of the UE is an estimate of the actual location of the UE at a time within the time period.

[0157] Clause 7. The method of Clause 6, wherein the uncertainty of the location is combined with the error in the estimate of the distance the UE moves between the scheduled location time and the time to make up the error in the estimate of the actual location of the UE at that time.

[0158] Clause 8. The method of any of Clauses 1-7, wherein the uncertainty of the location comprises a combination of a first location uncertainty (which is based on a location measurement but not on a scheduled positioning time) and a second location uncertainty (which is based on a scheduled positioning time).

[0159] Clause 9. The method of Clause 8, wherein determining the uncertainty of the location comprises: determining the first location uncertainty based on an estimate of the difference between the location of the UE at a time during the plurality of time periods and the actual location of the UE; determining the second location uncertainty based on an estimate of the difference between the actual location of the UE at that time and the actual location of the UE at the scheduled location time; and combining the first location uncertainty and the second location uncertainty to determine the uncertainty of the location.

[0160] Clause 10. The method of any of Clauses 1-9 further comprises: receiving from the other entity a request for the location of the UE, the request including a required uncertainty regarding the location of the UE, the required uncertainty including the maximum difference between the location of the UE at a scheduled location time and the actual location of the UE; and determining the location of the UE, wherein the uncertainty of the location does not exceed the required uncertainty.

[0161] Clause 11. An entity configured in a wireless network to locate a user equipment (UE) at a scheduled location time, comprising: an external interface configured to communicate with other entities in the wireless network; at least one memory; and at least one processor coupled to the external interface and the at least one memory, the at least one processor being configured to: receive location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determine the location of the UE based on the location measurements; determine an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmit the location and the uncertainty in the location to another entity.

[0162] Clause 12. An entity as described in Clause 11, wherein the entity is a UE, a Location Management Function (LMF), a Secure User Plane Location (SUPL) Location Platform (SLP), a New Radio Node B (gNB), a Location Server Agent (LSS), or a Location Management Component (LMC).

[0163] Clause 13. An entity as in any of Clauses 11 or 12, wherein the one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

[0164] Clause 14. An entity of any of Clauses 11-13, wherein the location measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; Measurement of downlink (DL) New Radio (NR) signals from NR Node B (gNB), including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); Measurement of uplink (UL) NR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and Measurement performed by a sensor including an inertial sensor or a barometer.

[0165] Clause 15. An entity of any of Clauses 11-14, wherein the time period is less than 1 second, less than 100 milliseconds (ms), less than 10 ms or less than 1 ms.

[0166] Clause 16. An entity of any of Clauses 11-15, wherein the location of the UE is an estimate of the actual location of the UE at a time within the time period.

[0167] Clause 17. An entity as described in Clause 16, wherein the uncertainty of the location is combined with the error in the estimate of the distance the UE has moved between the scheduled location time and the time in which the error is in the estimate of the actual location of the UE at that time.

[0168] Clause 18. An entity of any of Clauses 11-17, wherein the uncertainty of the location comprises a combination of a first location uncertainty (which is based on a location measurement but not on a scheduled positioning time) and a second location uncertainty (which is based on a scheduled positioning time).

[0169] Clause 19. An entity as described in Clause 18, wherein the at least one processor is configured to determine the uncertainty of the location by being configured to perform the following operations: determining the first location uncertainty based on an estimate of the difference between the location of the UE at a time during the plurality of time periods and the actual location of the UE; determining the second location uncertainty based on an estimate of the difference between the actual location of the UE at that time and the actual location of the UE at the scheduled location time; and combining the first location uncertainty and the second location uncertainty to determine the uncertainty of the location.

[0170] Clause 20. An entity of any of Clauses 11-19, wherein the at least one processor is further configured to: receive from the other entity a request for the location of the UE, the request including a required uncertainty for the location of the UE, the required uncertainty including the maximum difference between the location of the UE at a scheduled positioning time and the actual location of the UE; and determine the location of the UE, wherein the uncertainty of the location does not exceed the required uncertainty.

[0171] Clause 21. An entity configured in a wireless network to locate a user equipment (UE) at a scheduled location time, comprising: means for receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; means for determining the location of the UE based on the location measurements; means for determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and means for transmitting the location and the uncertainty in the location to another entity.

[0172] Clause 22. An entity as described in Clause 21, wherein the entity is the UE, the Location Management Function (LMF), the Secure User Plane Location (SUPL) Location Platform (SLP), the New Radio Node B (gNB), the Location Server Agent (LSS), or the Location Management Component (LMC).

[0173] Clause 23. An entity as in any of Clauses 21 or 22, wherein the one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

[0174] Clause 24. An entity of any of Clauses 21-23, wherein the location measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; Measurement of downlink (DL) New Radio (NR) signals from NR Node B (gNB), including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); Measurement of uplink (UL) NR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and Measurement performed by a sensor including an inertial sensor or a barometer.

[0175] Clause 25. An entity of any of Clauses 21-24, wherein the time period is less than 1 second, less than 100 milliseconds (ms), less than 10 ms or less than 1 ms.

[0176] Clause 26. An entity of any of Clauses 21-25, wherein the location of the UE is an estimate of the actual location of the UE at a time within the time period.

[0177] Clause 27. An entity as described in Clause 26, wherein the uncertainty of the location is combined with the error in the estimate of the distance the UE has moved between the scheduled location time and the time to estimate the error in the estimate of the UE's actual location at that time.

[0178] Clause 28. An entity of any of Clauses 21-27, wherein the uncertainty of the location comprises a combination of a first location uncertainty (which is based on a location measurement but not on a scheduled positioning time) and a second location uncertainty (which is based on a scheduled positioning time).

[0179] Clause 29. The entity of Clause 28, wherein the means for determining the uncertainty of the location comprises: means for determining the first location uncertainty based on an estimate of the difference between the location of the UE at a time during the plurality of time periods and the actual location of the UE; means for determining the second location uncertainty based on an estimate of the difference between the actual location of the UE at the time and the actual location of the UE at a scheduled positioning time; and means for combining the first location uncertainty and the second location uncertainty to determine the uncertainty of the location.

[0180] Clause 30. An entity of any of Clauses 21-29 further includes: means for receiving from the other entity a request for the location of the UE, the request including a required uncertainty regarding the location of the UE, the required uncertainty including the maximum difference between the location of the UE at a scheduled positioning time and the actual location of the UE; and means for determining the location of the UE, wherein the uncertainty of the location does not exceed the required uncertainty.

[0181] Clause 31. A non-transient storage medium including program code stored thereon, the program code being operable to configure at least one processor of an entity in a wireless network for locating a user equipment (UE) at a scheduled location time, the program code including instructions for: receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including the scheduled location time; determining the location of the UE based on the location measurements; determining an uncertainty in the location, wherein the uncertainty indicates a difference between the location of the UE at the scheduled location time and the actual location of the UE; and transmitting the location and the uncertainty in the location to another entity.

[0182] Clause 32. The non-transient storage medium as in Clause 31, wherein the entity is the UE, the Location Management Function (LMF), the Secure User Plane Location (SUPL) Location Platform (SLP), the New Radio Node B (gNB), the Location Server Agent (LSS), or the Location Management Component (LMC).

[0183] Clause 33. A non-transient storage medium as in any of Clauses 31 or 32, wherein the one or more other entities include at least one of the UE, the serving gNB, or the adjacent gNB.

[0184] Clause 34. A non-transient storage medium such as any of Clauses 31-33, wherein the location measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink (DL) New Radio (NR) signals from NR Node B (gNB), including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); measurement of uplink (UL) NR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by sensors including inertial sensors or barometers.

[0185] Clause 35. A non-transient storage medium such as any of Clauses 31-34, wherein the time period is less than 1 second, less than 100 milliseconds (ms), less than 10 ms, or less than 1 ms.

[0186] Clause 36. A non-transient storage medium such as any of Clauses 31-35, wherein the location of the UE is an estimate of the actual location of the UE at a time within the time period.

[0187] Clause 37. A non-transient storage medium as described in Clause 36, wherein the uncertainty of the location is combined with an error in the estimate of the distance the UE has moved between the scheduled location time and the actual location of the UE at that time.

[0188] Clause 38. A non-transient storage medium such as any of Clauses 31-37, wherein the uncertainty of the location comprises a combination of a first location uncertainty (which is based on a location measurement but not on a scheduled location time) and a second location uncertainty (which is based on a scheduled location time).

[0189] Clause 39. A non-transient storage medium as described in Clause 38, wherein the instructions for determining the uncertainty of the location include instructions for: determining the first location uncertainty based on an estimate of the difference between the location of the UE at one time during the plurality of time periods and the actual location of the UE; determining the second location uncertainty based on an estimate of the difference between the actual location of the UE at that one time and the actual location of the UE at a scheduled positioning time; and combining the first location uncertainty and the second location uncertainty to determine the uncertainty of the location.

[0190] Clause 40. A non-transient storage medium as described in any of Clauses 31-39, wherein the program code further includes instructions for: receiving from the other entity a request for the location of the UE, the request including a required uncertainty regarding the location of the UE, the required uncertainty including the maximum difference between the location of the UE at a scheduled positioning time and the actual location of the UE; and determining the location of the UE, wherein the uncertainty of the location does not exceed the required uncertainty.

[0191] While the foregoing disclosure has illustrated illustrative aspects of this disclosure, it should be noted that various changes and modifications may be made therein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions in the method claims according to the aspects of this disclosure described herein need not be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, pluralism is also contemplated unless explicitly stated to be limited to the singular.

Claims

1. A method for locating a user equipment (UE) at a physical location during a scheduled location time, comprising: The location measurements for the UE are received from one or more other entities, which are obtained by the one or more other entities at multiple times within a time period including the scheduled location time. The estimated location of the UE is determined based on the location measurements obtained during the time period; The uncertainty of the estimated location is determined, wherein the uncertainty indicates the difference between the estimated location of the UE and the actual location of the UE at the scheduled positioning time, and wherein the uncertainty of the estimated location includes a combination of a first location uncertainty and a second location uncertainty of the estimated location, the first location uncertainty being based on the location measurement but not on the scheduled positioning time, and the second location uncertainty being based on the scheduled positioning time. as well as The estimated location and the uncertainty of the estimated location are sent to another entity.

2. The method of claim 1, wherein the entity is the UE, the location management function LMF, the secure user plane location SUPL location platform SLP, the new radio node B gNB, the location server agent LSS, or the location management component LMC.

3. The method as described in claim 1, wherein, The one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

4. The method of claim 1, wherein the position measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round-Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink DL new radio NR signals from NR node B gNB, including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); measurement of uplink ULNR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by a sensor including an inertial sensor or a barometer.

5. The method of claim 1, wherein the time period is less than 1 second.

6. The method as described in claim 1, wherein the time period is less than 100ms.

7. The method as described in claim 1, wherein the time period is less than 10 ms.

8. The method as described in claim 1, wherein the time period is less than 1 ms.

9. The method of claim 1, wherein the estimated location of the UE is an estimate of the actual location of the UE at a time within the time period.

10. The method of claim 9, wherein the uncertainty indication of the estimated location is combined with an error in the estimation of the actual location of the UE at the time based on an error in the estimation of the distance the UE has moved between the scheduled positioning time and the time.

11. The method of claim 1, wherein determining the uncertainty of the estimated location comprises: The first position uncertainty is determined based on an estimate of the difference between the estimated position of the UE and the actual position of the UE at a time during the plurality of time periods; The second location uncertainty is determined based on an estimate of the difference between the actual location of the UE at the one time and the actual location of the UE at the scheduled location time; as well as The uncertainty of the position is determined by combining the first position uncertainty and the second position uncertainty.

12. The method of claim 1, further comprising: Receive a request for the estimated location of the UE from the other entity, the request including a required uncertainty for the estimated location of the UE, the required uncertainty including the maximum difference between the estimated location of the UE and the actual location of the UE at the scheduled positioning time; as well as Determine the estimated location of the UE, wherein the uncertainty of the estimated location does not exceed the required uncertainty.

13. An entity configured in a wireless network to locate a user equipment (UE) at a scheduled location time, comprising: An external interface configured to communicate with other entities in the wireless network; At least one memory; as well as At least one processor, said at least one processor being coupled to said external interface and said at least one memory and configured to: The location measurements for the UE are received from one or more other entities, which are obtained by the one or more other entities at multiple times within a time period including the scheduled location time. The estimated location of the UE is determined based on the location measurements obtained during the time period; The uncertainty of the estimated location is determined, wherein the uncertainty indicates the difference between the estimated location of the UE and the actual location of the UE at the scheduled positioning time, and wherein the uncertainty of the estimated location includes a combination of a first location uncertainty and a second location uncertainty of the estimated location, the first location uncertainty being based on the location measurement but not on the scheduled positioning time, and the second location uncertainty being based on the scheduled positioning time. as well as The estimated location and the uncertainty of the estimated location are sent to another entity.

14. The entity as described in claim 13, wherein the entity is the UE, the location management function LMF, the secure user plane location SUPL location platform SLP, the new radio node BgNB, the location server agent LSS, or the location management component LMC.

15. The entity as claimed in claim 13, wherein, The one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

16. The entity of claim 13, wherein the position measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round-Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink DL new radio NR signals from NR node B gNB, including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); measurement of uplink ULNR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by a sensor including an inertial sensor or a barometer.

17. The entity of claim 13, wherein the time period is less than 1 second.

18. The entity of claim 13, wherein the time period is less than 100 ms.

19. The entity of claim 13, wherein the time period is less than 10 ms.

20. The entity of claim 13, wherein the time period is less than 1 ms.

21. The entity of claim 13, wherein the estimated location of the UE is an estimate of the actual location of the UE at a time within the time period.

22. The entity of claim 21, wherein the uncertainty of the estimated location is indicated by an error in the estimation of the actual location of the UE at the time, which is a combination of an error in the estimation of the distance the UE moves between the scheduled positioning time and the time.

23. The entity of claim 13, wherein the at least one processor is configured to determine the uncertainty of the estimated location by being configured to perform the following operations: The first position uncertainty is determined based on an estimate of the difference between the estimated position of the UE and the actual position of the UE at a time during the plurality of time periods; The second location uncertainty is determined based on an estimate of the difference between the actual location of the UE at the one time and the actual location of the UE at the scheduled location time; as well as The uncertainty of the position is determined by combining the first position uncertainty and the second position uncertainty.

24. The entity of claim 13, wherein the at least one processor is further configured to: Receive a request for the estimated location of the UE from the other entity, the request including a required uncertainty regarding the location of the UE, the required uncertainty including the maximum difference between the estimated location of the UE and the actual location of the UE at a scheduled positioning time; and Determine the estimated location of the UE, wherein the uncertainty of the estimated location does not exceed the required uncertainty.

25. An entity configured in a wireless network to locate a user equipment (UE) at a scheduled location time, comprising: A means for receiving location measurements for the UE from one or more other entities, the location measurements being obtained by the one or more other entities at multiple times within a time period including a scheduled location time; A means for determining the estimated location of the UE based on the location measurements obtained during the time period; A means for determining the uncertainty of the estimated location, wherein the uncertainty indicates the difference between the estimated location of the UE and the actual location of the UE at a scheduled positioning time, and wherein the uncertainty of the estimated location includes a combination of a first location uncertainty and a second location uncertainty of the estimated location, the first location uncertainty being based on the location measurement but not on the scheduled positioning time, and the second location uncertainty being based on the scheduled positioning time. as well as A means for sending the estimated location and the uncertainty of the estimated location to another entity.

26. The entity of claim 25, wherein the position measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round-Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink DL new radio NR signals from NR node B gNB, including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmit Time Difference (Rx-Tx); measurement of uplink ULNR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by a sensor including an inertial sensor or a barometer.

27. The entity of claim 25, wherein the estimated location of the UE is an estimate of the actual location of the UE at a time within the time period.

28. The entity of claim 25, further comprising: A means for receiving a request for the estimated location of the UE from the other entity, the request including a required uncertainty for the estimated location of the UE, the required uncertainty including the maximum difference between the estimated location of the UE and the actual location of the UE at a scheduled positioning time; as well as A means for determining the estimated location of the UE, wherein the uncertainty of the location does not exceed the required uncertainty.

29. The entity of claim 25, wherein the entity is the UE, the location management function LMF, the secure user plane location SUPL location platform SLP, the new radio node B gNB, the location server agent LSS, or the location management component LMC.

30. The entity of claim 25, wherein the one or more other entities include at least one of the UE, the serving gNB, or the neighboring gNB.

31. The entity of claim 25, wherein the time period is less than 1 second.

32. The entity of claim 25, wherein the time period is less than 100 ms.

33. The entity of claim 25, wherein the time period is less than 10 ms.

34. The entity of claim 25, wherein the time period is less than 1 ms.

35. A non-transient storage medium including program code stored thereon, the program code being operable to configure at least one processor in an entity in a wireless network for locating a user equipment (UE) at a scheduled location time, the program code including instructions for: The location measurements for the UE are received from one or more other entities, which are obtained by the one or more other entities at multiple times within a time period including the scheduled location time. The estimated location of the UE is determined based on the location measurements obtained during the time period; The uncertainty of the estimated location is determined, wherein the uncertainty indicates the difference between the estimated location of the UE and the actual location of the UE at the scheduled positioning time, and wherein the uncertainty of the estimated location includes a combination of a first location uncertainty and a second location uncertainty of the estimated location, the first location uncertainty being based on the location measurement but not on the scheduled positioning time, and the second location uncertainty being based on the scheduled positioning time. as well as The estimated location and the uncertainty of the estimated location are sent to another entity.

36. The non-transient storage medium of claim 35, wherein the position measurement includes at least one of the following: Global Navigation Satellite System (GNSS) pseudorange; GNSS code phase; GNSS carrier phase; WiFi measurement including Received Signal Strength Indication (RSSI), Angle of Arrival (AOA), or Round-Trip Time (RTT); Bluetooth measurement including RSSI, AOA, or RTT; measurement of downlink DL new radio NR signals from NR node B gNB, including Reference Signal Time Difference (RSTD), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Angle of Departure (AOD), AOA, or Receive Time-Transmission Time Difference (Rx-Tx); measurement of uplink UL NR signals from the UE, including AOA, RSRP, Rx-Tx, and Time of Arrival (TOA); and measurements performed by a sensor including an inertial sensor or a barometer.

37. The non-transient storage medium of claim 35, wherein the estimated location of the UE is an estimate of the actual location of the UE at a time within the time period.

38. The non-transient storage medium of claim 35, wherein the program code further comprises instructions for the following operations: Receive a request for the estimated location of the UE from the other entity, the request including a required uncertainty regarding the estimated location of the UE, the required uncertainty including the maximum difference between the estimated location of the UE and the actual location of the UE at a scheduled positioning time; and Determine the estimated location of the UE, wherein the uncertainty of the estimated location does not exceed the required uncertainty.

Images