Systems and methods for supporting on-demand positioning reference signals in wireless networks

Abstract

Techniques are provided for implementing on-demand location reference signals (PRS) with user equipment (UE). An example method for determining the location of a mobile device includes: sending a request for a downlink location reference signal to a network server, wherein the request includes location reference signal configuration information; receiving auxiliary data based on the location reference signal configuration information; measuring one or more downlink location reference signals at least in part based on the location reference signal configuration information; and determining the location of the mobile device at least in part based on the measurement and auxiliary data obtained from the one or more downlink location reference signals. Another example method for determining the location of a mobile device includes: sending a request to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; transmitting one or more uplink positioning reference signals based on the uplink positioning reference signal configuration information; receiving first auxiliary data based on the downlink positioning reference signal configuration information; measuring one or more downlink positioning reference signals at least in part based on the downlink positioning reference signal configuration information; receiving second auxiliary data based on the measurements of one or more uplink positioning reference signals; and determining the location at least in part based on the measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements.

Description

Background Technology

[0001] Wireless communication systems have evolved through multiple generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services supporting the Internet, fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax), and fifth-generation (5G) services (e.g., 5G New Radio (NR)). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS) and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and TDMA-based Global System for Mobile Access (GSM) variants.

[0002] Obtaining the location (also known as "location") of a mobile device accessing a wireless network can be useful for many applications, including, for example, emergency calls, personal navigation, consumer asset tracking, locating friends or family members, etc. Existing location methods include those based on measuring radio signals transmitted from various devices, including spacecraft in a wireless network and ground-based wireless power sources such as base stations and access points. Base stations in a wireless network can be configured to transmit reference signals that enable mobile devices to perform location measurements. Improvements to location-related signaling can improve the accuracy, latency, and / or efficiency of locating mobile devices. Summary of the Invention

[0003] An example method for determining the location of a mobile device according to the present disclosure includes: sending a request for a downlink positioning reference signal to a network server, wherein the request includes positioning reference signal configuration information; receiving auxiliary data based on the positioning reference signal configuration information; measuring one or more downlink positioning reference signals at least in part based on the positioning reference signal configuration information; and determining the location based at least in part on the measurement and auxiliary data obtained from the one or more downlink positioning reference signals.

[0004] Implementations of such a method may include one or more of the following features: The request for a downlink positioning reference signal may be a Mobile Initiated Location Request (MO-LR). The request for a downlink positioning reference signal may be a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request. The positioning reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. A MO-LR response message indicating the start time and duration of one or more downlink positioning reference signals may be received. Receive auxiliary data may include a Receive Radio Resource Control (RRC) Reconfiguration message. Receive auxiliary data may include a Receive LPP Provide Auxiliary Data message. The positioning reference signal configuration information may be associated with one or more positioning reference signal resources in the positioning frequency layer.

[0005] An example method for providing location information to a mobile device according to the present disclosure includes: receiving a request for a downlink positioning reference signal, wherein the request includes positioning reference signal configuration information; determining one or more base stations providing the downlink positioning reference signal based on the positioning reference signal configuration information; providing the positioning reference signal configuration information to the one or more base stations; and providing auxiliary data based on the positioning reference signal configuration information.

[0006] Implementations of such a method may include one or more of the following features: A request for a downlink location reference signal may be based on a Mobile Initiated Location Request (MO-LR) received by a network server. A request for a downlink location reference signal may be based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by a network base station. Location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink location reference signal, and an RSRP measurement of the downlink signal received by the mobile device. A response message indicating the start time and duration of one or more downlink location reference signals may be provided. Determining one or more base stations providing the downlink location reference signal may include selecting one or more location reference signal resources from the location frequency layer. Determining one or more base stations providing the downlink location reference signal may include selecting one or more downlink location reference signal beams based on the approximate location of the mobile device. The approximate location of the mobile device may be based on at least one of the coverage area of ​​the serving cell of the mobile device, a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device, and an Enhanced Cell Identifier (ECID) measurement of the downlink signal received by the mobile device. Providing auxiliary data may include sending an LPP (Local Power Providing Auxiliary Data) message to the mobile device. Providing auxiliary data may also include sending an NRPPa (Non-Related Assistance Information Control) message to the serving base station of the mobile device.

[0007] An example method for determining the location of a mobile device according to the present disclosure includes: sending a request to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; sending one or more uplink positioning reference signals; receiving first auxiliary data based on the downlink positioning reference signal configuration information; measuring one or more downlink positioning reference signals at least in part based on the downlink positioning reference signal configuration information; receiving second auxiliary data based on the measurements of one or more uplink positioning reference signals; and determining the location at least in part based on the measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements.

[0008] Implementations of such a method may include one or more of the following features: The request for downlink location reference signals and uplink location reference signals may be a Mobile Initiated Location Request (MO-LR). The request for downlink location reference signals and uplink location reference signals may be a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request. Downlink location reference signal configuration information or uplink location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink location reference signals and uplink location reference signals, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. A MO-LR response message indicating the start time and duration of one or more downlink location reference signals may be received. Receiving uplink configuration parameters may include receiving a Radio Resource Control (RRC) message including uplink configuration parameters. An uplink activation message may be received, such that sending one or more uplink location reference signals is in response to receiving the uplink activation message. The uplink activation message may be a Media Access Control (MAC-CE) element, or other encapsulated or unencapsulated information elements provided in Layer 1 (i.e., the physical layer) or Layer 2 (i.e., the MAC layer). Uplink positioning reference signal measurement may be a gNB Rx-Tx time difference measurement. First auxiliary data may be included in a Radio Resource Control (RRC) reconfiguration message. Receiving second auxiliary data may include receiving an LPP-provided auxiliary data message. Downlink positioning reference signal configuration information may be associated with one or more positioning reference signal resources in the positioning frequency layer.

[0009] An example method for providing location information to a mobile device according to the present disclosure includes: receiving a request for a downlink positioning reference signal and an uplink positioning reference signal, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; determining one or more base stations providing the downlink positioning reference signal based on the downlink positioning reference signal configuration information; requesting uplink positioning reference signal configuration information from at least one of the one or more base stations; providing the downlink positioning reference signal configuration information to the one or more base stations; receiving uplink positioning reference signal measurement information from the one or more base stations; and transmitting auxiliary data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0010] Implementations of such a method may include one or more of the following features: A request for a downlink location reference signal may be based on a Mobile Initiated Location Request (MO-LR) received by a network server. A request for a downlink location reference signal may be based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by a network base station. Downlink location reference signal configuration information or uplink location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink and uplink location reference signals, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. A response message indicating the start time and duration of one or more downlink location reference signals may be provided. Determining one or more base stations providing the downlink location reference signal may include selecting one or more location reference signal resources from a location frequency layer. Determining one or more base stations providing the downlink location reference signal may include selecting one or more downlink location reference signal beams based on the approximate location of the mobile device. The approximate location of a mobile device can be based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device. Providing auxiliary data may include sending an LPP (Local Point Provided) auxiliary data message to the mobile device. Providing auxiliary data may also include sending an NRPPa (Non-Related Point Provided) auxiliary information control message to the serving base station of the mobile device.

[0011] An example apparatus according to this disclosure includes a memory, at least one transceiver, at least one processor communicatively coupled to the memory and at least one transceiver, and the at least one processor is configured to: send a request for a downlink positioning reference signal to a network server, wherein the request includes positioning reference signal configuration information; receive auxiliary data based on the positioning reference signal configuration information via the at least one transceiver; measure one or more downlink positioning reference signals at least in part based on the positioning reference signal configuration information; and determine a location at least in part based on the measurement and auxiliary data obtained from the one or more downlink positioning reference signals.

[0012] Implementations of such a device may include one or more of the following features: The request for a downlink positioning reference signal may be a Mobile Initiated Location Request (MO-LR). The request for a downlink positioning reference signal may be a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request. The positioning reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. At least one processor may also be configured to receive a MO-LR response message indicating the start time and duration of one or more downlink positioning reference signals. At least one processor may be configured to receive a Radio Resource Control (RRC) reconfiguration message. At least one processor may be configured to receive an LPP Provide Auxiliary Data message. The positioning reference signal configuration information may be associated with one or more positioning reference signal resources in the positioning frequency layer.

[0013] An example apparatus according to the present disclosure includes a memory, at least one transceiver, at least one processor communicatively coupled to the memory and at least one transceiver, and the at least one processor is configured to: receive a request for a downlink positioning reference signal via the at least one transceiver, wherein the request includes positioning reference signal configuration information; determine one or more base stations providing the downlink positioning reference signal based on the positioning reference signal configuration information; provide the positioning reference signal configuration information to the one or more base stations; and provide auxiliary data based on the positioning reference signal configuration information.

[0014] Implementations of such a device may include one or more of the following features: A request for a downlink location reference signal may be based on a Mobile Initiated Location Request (MO-LR) received by a network server. A request for a downlink location reference signal may be based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by a network base station. Location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink location reference signal, and an RSRP measurement of the downlink signal received by the mobile device. At least one processor may also be configured to provide a response message indicating the start time and duration of one or more downlink location reference signals. At least one processor may also be configured to select one or more location reference signal resources from a location frequency layer. At least one processor may also be configured to select one or more downlink location reference signal beams based on the approximate location of the mobile device. The approximate location of the mobile device may be based on at least one of the coverage area of ​​the serving cell of the mobile device, a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device, and an Enhanced Cell Identifier (ECID) measurement of the downlink signal received by the mobile device. At least one processor may also be configured to send an LPP (Local Power Provided Assistance) data message to the mobile device. At least one processor can also be configured to send NRPPa auxiliary information control messages to the serving base station of the mobile device.

[0015] An example apparatus according to this disclosure includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver. The at least one processor is configured to: send a request for downlink positioning reference signals and uplink positioning reference signals to a network server via the at least one transceiver, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; receive uplink configuration parameters based on the uplink positioning reference signal configuration information via the at least one transceiver; transmit one or more uplink positioning reference signals; receive first auxiliary data based on the downlink positioning reference signal configuration information via the at least one transceiver; measure one or more downlink positioning reference signals at least partially based on the downlink positioning reference signal configuration information; receive second auxiliary data based on the measurements of one or more uplink positioning reference signals via the at least one transceiver; and determine a position at least partially based on the measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements.

[0016] Implementations of such a device may include one or more of the following features: The request for downlink location reference signals and uplink location reference signals may be a Mobile Initiated Location Request (MO-LR). The request for downlink location reference signals and uplink location reference signals may be a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request. Downlink location reference signal configuration information or uplink location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink location reference signals and uplink location reference signals, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. At least one processor may also be configured to receive a Mobile Initiated Location Request (MO-LR) response message indicating the start time and duration of one or more downlink location reference signals. At least one processor may also be configured to receive a Radio Resource Control (RRC) message including uplink configuration parameters. At least one processor may also be configured to receive an uplink activation message and, in response to receiving the uplink activation message, send one or more uplink location reference signals. The uplink activation message can be a Media Access Control (MAC-CE) element, or other encapsulated or unencapsulated information elements provided in Layer 1 (i.e., the physical layer) or Layer 2 (i.e., the MAC layer). Uplink positioning reference signal measurements can be gNB Rx-Tx time difference measurements. At least one processor can also be configured to receive Radio Resource Control (RRC) reconfiguration messages. At least one processor can also be configured to receive LPP-provided auxiliary data messages. Downlink positioning reference signal configuration information can be associated with one or more positioning reference signal resources in the positioning frequency layer.

[0017] An example apparatus according to this disclosure includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver. The at least one processor is configured to: receive, via the at least one transceiver, a request for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; determine, based on the downlink positioning reference signal configuration information, one or more base stations providing the downlink positioning reference signals; request uplink positioning reference signal configuration information from at least one of the one or more base stations; provide downlink positioning reference signal configuration information to the one or more base stations; receive uplink positioning reference signal measurement information from the one or more base stations via the at least one transceiver; and transmit auxiliary data via the at least one transceiver based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0018] Implementations of such a device may include one or more of the following features: A request for a downlink location reference signal may be based on a Mobile Initiated Location Request (MO-LR) received by a network server. A request for a downlink location reference signal may be based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by a network base station. Downlink location reference signal configuration information or uplink location reference signal configuration information may include at least one of a Quality of Service indicator, a duration indicating how long the mobile device needs the requested downlink and uplink location reference signals, and a Reference Signal Received Power (RSRP) measurement of the downlink signal received by the mobile device. At least one processor may also be configured to provide a response message indicating the start time and duration of one or more downlink location reference signals. At least one processor may also be configured to select one or more location reference signal resources from a location frequency layer. At least one processor may also be configured to select one or more downlink location reference signal beams based on the approximate location of the mobile device. The approximate location of the mobile device can be based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device. At least one processor can also be configured to send an LPP (Local Point Provided Assistance) data message to the mobile device. At least one processor can also be configured to send an NRPPa (Non-Reference Point Provided Assistance) information control message to the serving base station of the mobile device.

[0019] An example apparatus for determining the location of a mobile device according to the present disclosure includes: components for sending a request for a downlink positioning reference signal to a network server, wherein the request includes positioning reference signal configuration information; components for receiving auxiliary data based on the positioning reference signal configuration information; components for measuring one or more downlink positioning reference signals at least in part based on the positioning reference signal configuration information; and components for determining the location based at least in part on the measurement and auxiliary data obtained from the one or more downlink positioning reference signals.

[0020] An example apparatus for providing location information to a mobile device according to the present disclosure includes: components for receiving a request for a downlink positioning reference signal, wherein the request includes positioning reference signal configuration information; components for determining one or more base stations providing the downlink positioning reference signal based on the positioning reference signal configuration information; components for providing the positioning reference signal configuration information to the one or more base stations; and components for providing auxiliary data based on the positioning reference signal configuration information.

[0021] An example apparatus for determining the location of a mobile device according to the present disclosure includes: components for sending a request to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; components for receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; components for sending one or more uplink positioning reference signals; components for receiving first auxiliary data based on the downlink positioning reference signal configuration information; components for measuring one or more downlink positioning reference signals at least partially based on the downlink positioning reference signal configuration information; components for receiving second auxiliary data based on the measurements of one or more uplink positioning reference signals; and components for determining the location at least partially based on measurements obtained from one or more downlink positioning reference signals and uplink positioning reference signal measurements.

[0022] An example apparatus for providing location information to a mobile device according to the present disclosure includes: components for receiving requests for downlink positioning reference signals and uplink positioning reference signals, wherein the requests include downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; components for determining one or more base stations providing the downlink positioning reference signals based on the downlink positioning reference signal configuration information; components for requesting uplink positioning reference signal configuration information from at least one of the one or more base stations; components for providing downlink positioning reference signal configuration information to the one or more base stations; components for receiving uplink positioning reference signal measurement information from the one or more base stations; and components for transmitting auxiliary data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0023] An example non-transitory processor-readable storage medium according to the present disclosure includes processor-readable instructions configured to enable one or more processors to determine the location of a mobile device, comprising: code for sending a request to a network server for a downlink positioning reference signal, wherein the request includes positioning reference signal configuration information; code for receiving auxiliary data based on the positioning reference signal configuration information; code for measuring one or more downlink positioning reference signals at least in part based on the positioning reference signal configuration information; and code for determining the location at least in part based on the measurement and auxiliary data obtained from the one or more downlink positioning reference signals.

[0024] An example non-transitory processor-readable storage medium according to the present disclosure includes processor-readable instructions configured to enable one or more processors to provide location information to a mobile device, comprising: code for receiving a request for a downlink positioning reference signal, wherein the request includes positioning reference signal configuration information; code for determining one or more base stations providing the downlink positioning reference signal based on the positioning reference signal configuration information; code for providing the positioning reference signal configuration information to the one or more base stations; and code for providing auxiliary data based on the positioning reference signal configuration information.

[0025] An example non-transitory processor-readable storage medium according to the present disclosure includes processor-readable instructions configured to enable one or more processors to determine the location of a mobile device, comprising: code for sending a request to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; code for receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; code for sending one or more uplink positioning reference signals; code for receiving first auxiliary data based on the downlink positioning reference signal configuration information; code for measuring one or more downlink positioning reference signals at least partially based on the downlink positioning reference signal configuration information; code for receiving second auxiliary data based on the measurements of one or more uplink positioning reference signals; and code for determining the location at least partially based on the measurements obtained from one or more downlink positioning reference signals and the uplink positioning reference signal measurements.

[0026] An example non-transitory processor-readable storage medium according to the present disclosure includes processor-readable instructions configured to enable one or more processors to provide location information to a mobile device, comprising: code for receiving a request for a downlink positioning reference signal and an uplink positioning reference signal, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; code for determining one or more base stations providing the downlink positioning reference signal based on the downlink positioning reference signal configuration information; code for requesting the uplink positioning reference signal configuration information from at least one of the one or more base stations; code for providing the downlink positioning reference signal configuration information to the one or more base stations; code for receiving uplink positioning reference signal measurement information from the one or more base stations; and code for transmitting auxiliary data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0027] The items and / or technologies described herein can provide one or more of the following capabilities, as well as others not mentioned. Mobile devices can be configured to request downlink location reference signals on demand or provide uplink location reference signals. On-demand requests enable communication networks to dynamically change location reference signal resource allocation. Mobile devices can use a Mobile Initiated Location Request (MO-LR) procedure or an On-Demand System Information (SI) request procedure to request DL-PRS transmissions from the network on demand or to request UL-PRS configuration on demand. On-demand location reference signal procedures can be implemented by extending existing MO-LR and / or SI request procedures, and thus reduce the need to create new procedures. Other capabilities can be provided, and not every embodiment of this disclosure must provide any, let alone all, of the discussed capabilities. Attached Figure Description

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

[0029] Figure 2 This is a block diagram of the components of an example user device.

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

[0031] Figure 4 This is a block diagram of the components of the sample server.

[0032] Figure 5A and Figure 5B An example downlink positioning reference signal resource set is shown.

[0033] Figure 6 This is a diagram of an example subframe format used for positioning reference signal transmission.

[0034] Figure 7 This is a conceptual diagram of an example of a frequency layer.

[0035] Figure 8 This is a sample message flow diagram used to extend the mobile initiation location request process to implement on-demand DL-PRS.

[0036] Figure 9A and Figure 9B Includes sample message flow diagrams for extending the mobile-initiated location request process to enable on-demand DL-PRS and UL-PRS.

[0037] Figure 10A and Figure 10B Includes a sample message flow diagram for extending the on-demand system information process to enable on-demand DL-PRS.

[0038] Figure 11A and Figure 11B Includes example message flow diagrams for extending on-demand system information processes to enable on-demand DL-PRS and UL-PRS.

[0039] Figure 12 This is a flowchart of an example method for determining the location of a mobile device using on-demand positioning reference signals.

[0040] Figure 13 This is a flowchart of an example method for providing auxiliary data for on-demand positioning reference signals.

[0041] Figure 14 This is a flowchart of an example method for determining the location of a mobile device using on-demand downlink positioning reference signals and uplink positioning reference signals.

[0042] Figure 15 This is a flowchart of an example method for providing auxiliary data for on-demand downlink positioning reference signals and uplink positioning reference signals.

[0043] 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, multiple instances of an element may be indicated by adding a letter after the first digit of the element. For example, multiple instances of element 110 may be designated as 110a, 110b, 110c, etc. When only the first digit is used to refer to such an element, any instance of that element will be understood (e.g., element 110 in the previous example would refer to elements 110b, 110c, and 110b). Detailed Implementation

[0044] This article discusses techniques for providing on-demand location reference signals (PRS) to user equipment (UEs). Existing implementations of downlink (DL) PRS transmission are typically in an "always-on" configuration, where the base station transmits PRS regardless of UE requirements within the network. Such an "always-on" configuration can utilize scarce resources such as bandwidth and energy, and incurs unnecessary overhead when UE positioning is not required during specific time periods or in specific areas of the network. In networks utilizing beamforming-based DL-PRS transmission (e.g., 5G NR), DL-PRS transmission across all beam scanning directions can lead to unnecessary DL-PRS transmissions. "Always-on" configurations can also utilize static allocation of DL-PRS resources. Typically, static DL-PRS resource allocation does not allow for the temporary addition of DL-PRS resources to achieve higher positioning accuracy and / or lower latency positioning requirements in specific areas or at specific times. Similarly, static allocation of DL-PRS resources does not allow for the reduction of DL-PRS resources when positioning requirements can be met with fewer DL-PRS resources, or when no UE needs to be positioned for a period of time.

[0045] The on-demand DL-PRS technology described in this paper enables networks to dynamically change DL-PRS resource allocation as needed (e.g., based on the requirements of a specific use case or application). In the examples, on-demand DL-PRS technology allows networks to dynamically change configuration parameters such as the DL-PRS timing period, the duration of the DL-PRS timing, the DL-PRS bandwidth, and the DL-PRS spatial direction.

[0046] A DL PRS configuration can define DL-PRS transmission (e.g., within one or more cells and / or by one or more base stations) based on a specific set of DL-PRS configuration parameter values. For example, DL-PRS transmission can use specific values ​​for parameters such as DL-PRS bandwidth, DL-PRS frequency (or multiple DL-PRS frequencies), duration of DL-PRS positioning events, spatial direction of DL-PRS positioning events, period of DL-PRS positioning events, DL-PRS encoding, and DL-PRS silent mode. A DL PRS configuration can be static, and if the specific values ​​of the DL-PRS transmission parameters do not change, or can be changed as described herein (e.g., replaced with a different DL PRS configuration), then the DL PRS configuration can correspond to "always-on" DL-PRS transmission.

[0047] In this embodiment, on-demand DL-PRS is implemented in the network by defining a different set of DL-PRS configurations, the parameter values ​​of which can be configured in the network using an operation and maintenance (O&M) process. For example, a set of DL-PRS configuration parameter values ​​(also referred to herein as "parameters") can be configured to correspond to "normal" DL-PRS transmissions, and in some networks, "normal" DL-PRS transmissions may be equivalent to no DL-PRS transmissions at all (e.g., to minimize resource usage). In other examples, one or more levels of increased DL-PRS transmissions can each be associated with a different set of DL-PRS configuration parameter values, such as those defining DL-PRS bandwidth, DL-PRS frequency, duration of DL-PRS positioning timings, spatial direction of DL-PRS positioning timings, and period of DL-PRS positioning timings. The transmission of DL-PRS can then be altered (e.g., increased or decreased) by changing the DL-PRS configuration used to transmit DL-PRS. The change can be "on demand," in which entities such as UEs or location service (LCS) clients can be allowed to indicate new DL PRS configurations or a new set of DL PRS configurations (e.g., "high QoS", "low QoS") for transmitting DL PRS in one or more specific cells and / or by one or more specific base stations.

[0048] On-demand DL-PRS can impact UE-based positioning based on requests from internal UE clients. For example, when an application residing in the UE requires location, there may be no (or insufficient) DL-PRS resources available (e.g., all gNBs around the UE's location may "turn off" DL-PRS). Furthermore, for certain positioning measurements (e.g., UE Rx-Tx time difference measurements), the UE may require both DL-PRS and uplink PRS (UL-PRS, also known as Sounding Reference Signal (SRS) for Positioning) to perform the measurement. When an internal UE client requests location, the UE may not be configured with the desired UL-PRS (e.g., desired period, bandwidth, duration, etc.). The on-demand PRS technology described herein enables the UE to request DL-PRS transmissions from the network and / or provide UL-PRS configuration on demand.

[0049] In embodiments, the target UE can use a Mobile Initiated Location Request (MO-LR) procedure or an On-Demand System Information (SI) Request procedure to request one or more DL-PRS transmissions from the network and / or request UL-PRS configuration information on demand. The techniques provided herein reduce the impact on the UE and the network because they extend existing procedures rather than creating new ones. In the examples, the procedures for determining and configuring new PRS can be the same and are independent of whether the PRS demand is triggered by the network or the UE. These techniques and configurations are examples, and other techniques and configurations can be used.

[0050] refer to Figure 1 Examples of communication system 100 include UE 105, radio access network (RAN) 135, here a fifth-generation (5G) next-generation (NG) RAN (NG-RAN), and 5G core network (5GC) 140. For example, UE 105 can be an IoT device, a location tracker device, a cellular phone, or other device. The 5G network can also be referred to as a new radio (NR) network; NG-RAN 135 can be referred to as a 5G RAN or NR RAN; and 5GC 140 can be referred to as an NG core network (NGC). RAN 135 can be another type of RAN, such as a 3G RAN, a 4G Long Term Evolution (LTE) RAN, etc. Communication system 100 may utilize information from constellation 185 of spacecraft (SVs) 190, 191, 192, 193 of a satellite positioning system (SPS) (e.g., a Global Navigation Satellite System (GNSS)). SPSs may include GPS, GLONASS, Galileo, or BeiDou, or other local or regional SPSs such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Navigation Overlay Service (EGNOS), or the Wide Area Augmentation System (WAAS). Additional components of communication system 100 are described below. Communication system 100 may include additional or alternative components.

[0051] like Figure 1As shown, NG-RAN 135 includes NR NodeBs (gNB) 110a, 110b and a next-generation eNodeB (ng-eNB) 114, and 5GC 140 includes Access and Mobility Management Functions (AMF) 115, Session Management Functions (SMF) 117, Location Management Functions (LMF) 120 and Gateway Mobility Location Center (GMLC) 125. gNBs 110a, 110b and ng-eNB 114 are communicatively coupled to each other, each configured to communicate bidirectionally with UE 105, and each communicatively coupled to AMF 115 and configured to communicate bidirectionally with AMF 115. AMF 115, SMF 117, LMF 120 and GMLC 125 are communicatively coupled to each other, and GMLC is communicatively coupled to an external client 130. SMF 117 can be used as an initial contact point for Service Control Functions (SCF) (not shown) to create, control and delete media sessions.

[0052] Figure 1 A general description of the various components is provided, any or all of which can be used appropriately, and each component can be copied or omitted as needed. Specifically, although one UE 105 is shown, many UEs (e.g., hundreds, thousands, millions, etc.) can be used in the communication system 100. Similarly, the communication system 100 may include more (or fewer) numbers of SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a and 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The connections of the various components in the connected communication system 100 shown include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components can be rearranged, combined, separated, replaced, and / or omitted according to the desired functionality.

[0053] Although Figure 1A 5G-based network is illustrated, but similar network implementations and configurations can be used for other communication technologies such as 3G, Long Term Evolution (LTE), etc. The implementations described herein (whether for 5G technology and / or for one or more other communication technologies and / or protocols) can be used to transmit (or broadcast) directional synchronization signals, receive and measure directional signals at a UE (e.g., UE 105) and / or provide location assistance to UE 105 (via GMLC 125 or other location servers) and / or calculate the location of UE 105 at a positioning-capable device such as UE 105, gNB110a, 110b, or LMF 120 based on measurements received at UE 105 for such directional transmission signals. Gateway Mobile Location Center (GMLC) 125, Location Management Function (LMF) 120, Access and Mobility Management Function (AMF) 115, SMF 117, ng-eNB (eNodeB) 114, and gNB (gNodeB) 110a, 110b are examples, and in various embodiments, these other location server functions and / or base station functions may be replaced by or included by various other location server functions and / or base station functions, respectively.

[0054] UE 105 may include and / or may be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), terminal (SET) supporting Secure User Plane Location (SUPL), or some other name. Furthermore, UE 105 may correspond to a mobile phone, smartphone, laptop, tablet, PDA, consumer asset tracking device, navigation device, Internet of Things (IoT) device, asset tracker, health monitor, security system, smart city sensor, smart meter, wearable tracker, or some other portable or mobile device. Typically, although not mandatory, UE 105 may support wireless communication using 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-Speed ​​Packet Data (HRPD), IEEE 802.11 WiFi (also known as Wi-Fi). (BT), Global Microwave Access Interoperability (WiMAX), 5G New Radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. UE 105 can support wireless communication using a wireless local area network (WLAN), which can connect to other networks (e.g., the Internet) using, for example, digital subscriber line (DSL) or packet cable. The use of one or more of these RATs can allow UE 105 to communicate with external client 130 (e.g., via...). Figure 1The components of 5GC 140 (not shown, or possibly via GMLC 125) and / or allow external client 130 to receive location information about UE 105 (e.g., via GMLC 125).

[0055] In a personal area network, such as one where the user can use audio, video, and / or data I / O (input / output) devices, and / or body sensors, as well as separate wired or wireless modems, UE 105 may include a single entity or may include multiple entities. An estimate of the location of UE 105 may be referred to as location, location estimate, location lock, lock, positioning, location estimation, or location lock, and may be geographic, providing the location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an altitude component (e.g., altitude above sea level, altitude above ground level, floor level, or basement level, or depth below ground level, floor level, or basement level). Alternatively, the location of UE 105 may be represented as a city location (e.g., as a postal address or designation of a point or small area within a building (such as a specific room or floor)). The location of UE 105 may be represented as an area or volume (defined in geographic or city form) in which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 105 can be represented as a relative location, including, for example, distance and orientation from a known location. A relative location can be represented as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to an origin at a known location, which can be defined, for example, geographically, in urban terms, or by reference to a point, area, or volume indicated, for example, on a map, floor plan, or architectural plan. In the description contained herein, unless otherwise stated, the use of the term "location" can include any of these variations. When calculating the location of the UE, the local x, y, and possibly z coordinates are typically solved, and then, if necessary, the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and altitude above or below mean sea level).

[0056] UE 105 can be configured to communicate with other entities using one or more of a variety of technologies. UE 105 can be configured to indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. The D2D P2P links can be supported by any suitable D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc. Etc. One or more UEs in a group utilizing D2D communication may be within the geographic coverage area of ​​one or more Transmit / Receive Points (TRPs) such as gNB 110a, 110b, and / or ng-eNB 114. Other UEs in such a group may be outside such geographic coverage areas or may not be able to receive transmissions from the base station. Multiple groups of UEs communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE can transmit to other UEs in the group. TRPs can facilitate the scheduling of resources for D2D communication. In other cases, D2D communication can occur between UEs without the involvement of a TRP.

[0057] Figure 1 The base stations (BS) in the NG-RAN 135 shown include NR Node Bs, referred to as gNodeBs (gNBs) 110a and 110b. The gNBs 110a and 110b in the NG-RAN 135 can be interconnected via one or more other gNBs. Access to the 5G network is provided to UE 105 via wireless communication between UE 105 and one or more of the gNBs 110a and 110b. One or more of the gNBs 110a and 110b can use 5G to provide wireless communication access to the 5GC 140 on behalf of UE 105. Figure 1 In this example, assuming that the serving gNB of UE 105 is gNB 110a, if UE 105 moves to another location, another gNB (e.g., gNB 110b) can act as the serving gNB or as the secondary gNB to provide additional throughput and bandwidth to UE 105.

[0058] Figure 1 The base station (BS) in the NG-RAN 135 shown may include ng-eNB 114, also known as a next-generation evolved Node B. ng-eNB 114 may connect to one or more of the gNBs 110a and 110b in the NG-RAN 135, possibly via one or more other gNBs and / or one or more other ng-eNBs. ng-eNB 114 may provide LTE radio access and / or evolved LTE (eLTE) radio access to UE 105. One or more of the gNBs 110a, 110b, and / or ng-eNB 114 may be configured as location-only beacons, capable of transmitting signals to assist in determining the location of UE 105, but not capable of receiving signals from UE 105 or other UEs.

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

[0060] As mentioned above, although Figure 1 The diagram illustrates a node configured to communicate according to a 5G communication protocol, but nodes configured to communicate according to other communication protocols, such as LTE or IEEE 802.11x, can be used. For example, in an evolved packet system (EPS) providing LTE radio access to UE 105, the RAN may include an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), which may include base stations comprising evolved Node Bs (eNBs). 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 In the NG-RAN 135, EPC corresponds to 5GC 140.

[0061] gNB 110a, 110b, and ng-eNB 114 can communicate with AMF 115. For positioning functionality, AMF 115 communicates with LMF 120. AMF 115 can support UE 105 mobility (including cell changes and handovers) and can participate in supporting signaling connections to UE 105, as well as possible data and voice bearers for UE 105. For example, LMF 120 can communicate directly with UE 105 wirelessly. When UE 105 accesses NG-RAN 135, LMF 120 can support UE 105 positioning and can support positioning procedures / methods such as Auxiliary GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other positioning methods. LMF 120 can process location service requests for UE 105, such as requests received from AMF 115 or GMLC 125. LMF 120 can connect to AMF 115 and / or GMLC 125. LMF 120 may be referred to by other names, such as Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value-Added LMF (VLMF). Nodes / systems implementing LMF 120 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). At least some positioning functions (including deriving the location of UE 105) can be performed at UE 105 (e.g., using signal measurements obtained by UE 105 of signals transmitted by radio nodes such as gNB 110a, 110b, and / or ng-eNB 114, and / or auxiliary data provided to UE 105, for example, by LMF 120).

[0062] GMLC 125 can support location requests for UE 105 received from external client 130 and can forward such location requests to AMF 115, which in turn forwards them to LMF 120, or can forward the location requests directly to LMF 120. Location responses from LMF 120 (e.g., containing location estimates for UE 105) can be returned to GMLC 125 directly or via AMF 115, and GMLC 125 can then return the location response (e.g., containing location estimates) to external client 130. GMLC 125 is shown connected to both AMF 115 and LMF 120, but in some implementations, 5GC 140 may support only one of these connections.

[0063] like Figure 1 As further illustrated, the LMF 120 can communicate with gNB110a, 110b, and / or ng-eNB 114 using the New Radio Positioning Protocol A (NRPPa), which is defined in 3GPP Technical Specification (TS) 38.455. NRPPa can be the same as, similar to, or an extension of the LTE Positioning Protocol A (LPPa) defined in 3GPP TS 36.455. NRPPa messages are transmitted via AMF 115 between gNB 110a (or gNB 110b) and the LMF 120, and / or between the ng-eNB 114 and the LMF 120. Figure 1 As further illustrated, LMF 120 and UE 105 can communicate using the LTE Positioning Protocol (LPP), which is defined in 3GPP TS 37.355. Here, LPP messages can be transmitted between UE 105 and LMF 120 via AMF 115 and the serving gNB 110a, 110b, or serving ng-eNB 114 for UE 105. For example, LPP messages can be transmitted between LMF 120 and AMF 115 using the 5G Location Services Application Protocol (LCS AP), and between AMF 115 and UE 105 using the 5G Non-Access Stratum (NAS) protocol. The LPP protocol can be used to support the positioning of UE 105 using UE-assisted and / or UE-based positioning methods (e.g., A-GNSS, RTK, OTDOA, and / or E-CID). The NRPPa protocol can be used to support the location of UE 105 using network-based location methods such as E-CID (e.g., when used with measurements obtained from gNB 110a, 110b, or ng-eNB 114), and / or can be used by LMF 120 to obtain location-related information from gNB 110a, 110b, and / or ng-eNB 114, such as defining parameters for directional SS transmissions from gNB 110a, 110b, and / or ng-eNB 114.

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

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

[0066] Using a network-based positioning method, one or more base stations (e.g., gNB 110a, 110b and / or ng-eNB 114) or APs can obtain location measurements (e.g., measurements of RSSI, RTT, Rx-Tx time difference, RSRP, RSRQ, or Time of Arrival (TOA) of signals transmitted by UE 105) and / or can receive measurements obtained by UE 105. One or more base stations or APs can send the measurements to a location server (e.g., LMF 120) for calculating the location estimate of UE 105.

[0067] The information provided to the LMF 120 by the gNB 110a, 110b and / or ng-eNB 114 using NRPPa may include timing and configuration information for directing SS or PRS transmissions and location coordinates. The LMF 120 may provide some or all of this information as supplementary data to the UE 105 in an LPP message via NG-RAN 135 and 5GC140.

[0068] The LPP message sent from LMF 120 to UE 105 can instruct UE 105 to do any of a variety of things according to the desired functionality. For example, the LPP message can contain instructions to enable UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP message can instruct UE 105 to obtain one or more measurements of directional signals transmitted in a specific cell (e.g., beam ID, beamwidth, average angle, RSRP, RSRQ measurements) supported by one or more of gNB 110a, 110b, and / or ng-eNB 114 (or supported by some other type of base station such as eNB or WiFi AP). UE 105 can send the measurements back to LMF 120 via serving gNB 110a (or serving ng-eNB 114) and AMF 115 in an LPP message (e.g., within a 5G NAS message).

[0069] As described above, although the 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., which are used to support and interact with mobile devices such as UE 105 (e.g., to implement voice, data, location, and other functions). In some such embodiments, 5GC 140 can be configured to control different air interfaces. For example, 5GC 140 can use the non-3GPP interoperability function (N3IWF) in 5GC 150. Figure 1(Not shown) Connected to a WLAN. For example, the WLAN may support IEEE 802.11 WiFi access for UE 105 and may include one or more WiFi APs. Here, the N3IWF may connect to the WLAN and other components in 5GC 140, such as AMF 115. In some embodiments, both NG-RAN 135 and 5GC 140 may be replaced by one or more other RANs and one or more other core networks. For example, in EPS, NG-RAN 135 may be replaced by E-UTRAN containing eNBs, and 5GC 140 may be replaced by EPC containing a Mobility Management Entity (MME) replacing AMF 115, E-SMLC replacing LMF 120, and GMLC similar to GMLC 125. In such EPS, E-SMLC may use LPPa instead of NRPPa to send location information to and receive location information from eNBs in E-UTRAN, and may use LPP to support UE 105's positioning. In these other embodiments, the positioning of UE 105 using directional PRS can be supported in a manner similar to that described herein for 5G networks, except that the functions and procedures described herein for gNB 110a, 110b, ng-eNB 114, AMF 115 and LMF 120 can, in some cases, be alternatively applied to other network elements such as eNB, WiFiAP, MME and E-SMLC.

[0070] As described above, in some embodiments, the positioning function may be implemented at least in part using directional SS or PRS beams, the directional SS or PRS beams being used by the UE whose positioning will be determined (e.g., Figure 1 The UE (105) can be located within the range of base stations (such as gNB 110a, 110b and / or ng-eNB 114). In some cases, the UE can use directional SS or PRS beams from multiple base stations (such as gNB 110a, 110b, ng-eNB 114, etc.) to calculate the UE's location.

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

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

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

[0074] UE 200 may include sensor 213, which may include, for example, an inertial measurement unit (IMU) 270, one or more magnetometers 271, and / or one or more environmental sensors 272. IMU 270 may include one or more inertial sensors, such as one or more accelerometers 273 (e.g., jointly responding to acceleration of UE 200 in three dimensions) and / or one or more gyroscopes 274. The magnetometer can provide measurements to determine orientation (e.g., relative to magnetic north and / or true north), which can be used for any of a variety of purposes, such as supporting one or more compass applications. Environmental sensors 272 may include, for example, one or more temperature sensors, one or more atmospheric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. Sensor 213 may generate analog and / or digital signal indications, which may be stored in memory 211 and processed by DSP 231 and / or general-purpose processor 230 to support one or more applications, such as applications for positioning and / or navigation operations.

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

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

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

[0078] Transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250, which are configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 240 may include a transmitter 242 and a receiver 244 coupled to one or more antennas 246 for transmitting (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receiving (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248, and converting signals from wireless signals 248 into wired (e.g., electrical and / or optical) signals, and from wired (e.g., electrical and / or optical) signals into wireless signals 248. Therefore, transmitter 242 may include multiple transmitters that may be discrete components or combined / integrated components, and / or receiver 244 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 240 can be configured to communicate signals according to various Radio Access Technologies (RATs) (e.g., with TRPs and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), V2C (Uu), IEEE 802.11 (including IEEE 802.11p), WiFi, and WiFi Direct (WiFi-D). Zigbee, etc. NR systems can be configured to operate on different frequency layers, such as FR1 (e.g., 410-7125MHz) and FR2 (e.g., 24.25-52.6GHz), and can be extended to new frequency bands, such as sub-6GHz and / or 100GHz, and higher frequency bands (e.g., FR2x, FR3, FR4). Wired transceiver 250 may include transmitter 252 and receiver 254, configured for wired communication, for example, with NG-RAN 135, to transmit and receive communication, for example, to gNB 110a. Transmitter 252 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or receiver 254 may include multiple receivers, which may be discrete components or combined / integrated components. Wired transceiver 250 may be configured for, for example, optical and / or electrical communication. Transceiver 215 may be communicatively coupled to transceiver interface 214, for example, via optical and / or electrical connections. Transceiver interface 214 can be at least partially integrated with transceiver 215.

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

[0080] SPS receiver 217 (e.g., a Global Positioning System (GPS) receiver) is capable of receiving and acquiring SPS signal 260 via SPS antenna 262. Antenna 262 is configured to convert the wireless SPS signal 260 into a wired signal, such as an electrical signal or an optical signal, and may be integrated with antenna 246. SPS receiver 217 may be configured to process the acquired SPS signal 260, in whole or in part, to estimate the location of UE 200. For example, SPS receiver 217 may be configured to use SPS signal 260 to determine the location of UE 200 by trilateration. In conjunction with SPS receiver 217, general-purpose processor 230, memory 211, DSP 231, and / or one or more dedicated processors (not shown) may be used to process the acquired SPS signal and / or calculate the estimated location of UE 200, in whole or in part. Memory 211 may store indications (e.g., measurements) of SPS signal 260 and / or other signals (e.g., signals acquired from wireless transceiver 240) for use in performing positioning operations. A general-purpose processor 230, a DSP 231, and / or one or more dedicated processors and / or a memory 211 can provide or support a location engine for processing measurements to estimate the position of the UE 200.

[0081] UE 200 may include a camera 218 for capturing still or moving images. Camera 218 may include, for example, an imaging sensor (e.g., a charge-coupled device or a CMOS imager), a lens, analog-to-digital circuitry, a frame buffer, etc. General-purpose processor 230 and / or DSP 231 may perform additional processing, conditioning, encoding, and / or compression on the signals representing the captured images. Additionally or alternatively, video processor 233 may perform conditioning, encoding, compression, and / or manipulation on the signals representing the captured images. Video processor 233 may decode / decompress stored image data for presentation on a display device (not shown), such as user interface 216.

[0082] The Positioning (Motion) Device (PMD) 219 can be configured to determine the location and possible motion of the UE 200. For example, the PMD 219 can communicate with, and / or include, some or all of the SPS receivers 217. Additionally or alternatively, the PMD 219 can be configured to determine the location of the UE 200 using ground-based signals (e.g., at least some of signals 248) for trilateration, for assisting in acquiring and using the SPS signal 260, or for both. The PMD 219 can be configured to determine the location of the UE 200 using one or more other techniques (e.g., relying on the UE's self-reported location (e.g., part of the UE's positioning beacon)), and can use a combination of techniques (e.g., SPS and ground positioning signals) to determine the location of the UE 200. PMD 219 may include one or more of sensors 213 (e.g., gyroscope, accelerometer, magnetometer, etc.) that can sense the orientation and / or motion of UE 200 and provide indications thereof. Processor 210 (e.g., general-purpose processor 230 and / or DSP 231) may be configured to use these indications to determine the motion of UE 200 (e.g., velocity vector and / or acceleration vector). PMD 219 may be configured to provide indications of uncertainty and / or error in the determined positioning and / or motion. In the example, PMD 219 may be referred to as a positioning engine (PE) and may be executed by general-purpose processor 230. For example, PMD 219 may be a logical entity and may be integrated with general-purpose processor 230 and memory 211.

[0083] Also refer to Figure 3Examples of TRP 300 for gNB 110a, gNB 110b, and ng-eNB 114 include a computing platform comprising a processor 310, a memory 311 including software (SW) 312, a transceiver 315, and (optionally) an SPS receiver 317. The processor 310, memory 311, transceiver 315, and SPS receiver 317 can be communicatively coupled to each other via a bus 320 (which can be configured for, for example, optical and / or electrical communications). One or more of the illustrated devices (e.g., a wireless interface and / or SPS receiver 317) may be omitted from the TRP 300. The SPS receiver 317 may be configured similarly to SPS receiver 217 to receive and acquire SPS signal 360 via SPS antenna 362. The processor 310 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), etc. Processor 310 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as...) Figure 4 (As shown). Memory 311 is a non-transitory storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 311 stores software 312, which may be processor-readable and processor-executable software code containing instructions configured to cause processor 310 to perform the various functions described herein when executed. Alternatively, software 312 may not be executed directly by processor 310, but may be configured to cause processor 310 to perform these functions, for example, when compiled and executed. This description may refer to processor 310 performing functions, but this includes other implementations, such as processor 310 performing software and / or firmware. This description may refer to processor 310 performing functions as an abbreviation of one or more processors included in processor 310 performing the function. This description may refer to TRP 300 performing functions as an abbreviation of one or more suitable components of TRP 300 (and therefore one of gNB 110a, gNB 110b, ng-eNB 114) performing the function. In addition to and / or replacing memory 311, processor 310 may include memory with stored instructions. The functionality of processor 310 will be discussed more fully below.

[0084] Transceiver 315 may include a wireless transceiver 340 and / or a wired transceiver 350, which are configured to communicate with other devices via wireless and wired connections, respectively. For example, wireless transceiver 340 may include a transmitter 342 and a receiver 344 coupled to one or more antennas 346 for transmitting (e.g., on one or more uplink channels) and / or receiving (e.g., on one or more downlink channels) wireless signals 348, and converting signals from wireless signals 348 into wired (e.g., electrical and / or optical) signals, and from wired (e.g., electrical and / or optical) signals into wireless signals 348. Therefore, transmitter 342 may include multiple transmitters that may be discrete components or combined / integrated components, and / or receiver 344 may include multiple receivers that may be discrete components or combined / integrated components. The wireless transceiver 340 can be configured to communicate signals according to various Radio Access Technologies (RATs) (e.g., with UE 200, one or more other UEs, and / or one or more other devices), such as 5G New Radio (NR), GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), AMPS (Advanced Mobile Telephone Systems), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), LTE (Long Term Evolution), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, and WiFi Direct (WiFi-D). Zigbee, etc. The wired transceiver 350 may include a transmitter 352 and a receiver 354, configured for wired communication, for example, with the core network 140, to send and receive communications, for example, to and from the LMF 120 or other network servers. The transmitter 352 may include multiple transmitters, which may be discrete components or combined / integrated components, and / or the receiver 354 may include multiple receivers, which may be discrete components or combined / integrated components. The wired transceiver 350 may be configured for, for example, optical communication and / or electrical communication.

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

[0086] Also refer to Figure 4Example servers such as the LMF 120 include a computing platform comprising a processor 410, a memory 411 including software (SW) 412, and a transceiver 415. The processor 410, memory 411, and transceiver 415 can be communicatively coupled to each other via a bus 420 (which can be configured for, for example, optical and / or electrical communications). One or more of the illustrated devices (e.g., wireless interfaces) may be omitted from server 400. The processor 410 may include one or more intelligent hardware devices, such as a central processing unit (CPU), microcontroller, application-specific integrated circuit (ASIC), etc. The processor 410 may include multiple processors (e.g., including general-purpose / application processors, DSPs, modem processors, video processors, and / or sensor processors, such as… Figure 4 (As shown). Memory 411 is a non-transitory storage medium, which may include random access memory (RAM), flash memory, disk storage, and / or read-only memory (ROM), etc. Memory 411 stores software 412, which may be processor-readable and processor-executable software code containing instructions configured to cause processor 410 to perform the various functions described herein when executed. Alternatively, software 412 may not be executed directly by processor 410, but may be configured to cause processor 410 to perform these functions, for example, when compiled and executed. This description may refer to processor 410 performing functions, but this includes other implementations, such as processor 410 performing software and / or firmware. This description may refer to processor 410 performing functions as a shorthand for one or more processors included in processor 410 performing the function. This description may refer to server 400 (or LMF 120) performing functions as a shorthand for one or more suitable components of server 400 performing the function. In addition to and / or instead of memory 411, processor 410 may include memory with stored instructions. The functions of processor 410 will be discussed in more detail below.

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

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

[0089] refer to Figure 5A and Figure 5BThe diagram illustrates an example downlink PRS resource set. Typically, a PRS resource set is a collection of PRS resources spanning a single base station (e.g., TRP 300) that share the same period, a common silence mode configuration, and the same repetition factor across time slots. A first PRS resource set 502 comprises four resources and a repetition factor of 4, with a time slot equal to one time slot. A second PRS resource set 504 comprises four resources and a repetition factor of 4, with a time slot equal to four time slots. The repetition factor indicates the number of times each PRS resource is repeated in each individual instance of the PRS resource set (e.g., values ​​1, 2, 4, 6, 8, 16, 32). The time slot represents the offset in time slots between two repeated instances of PRS resources corresponding to the same PRS resource ID within a single instance of the PRS resource set (e.g., values ​​1, 2, 4, 8, 16, 32). The duration spanned by a PRS resource set containing repeated PRS resources does not exceed the PRS period. The repetition of PRS resources allows receiver beams to scan across the repetitions and combine RF gains to increase coverage. Repetition can also achieve in-instance muting. For example... Figure 5A and Figure 5B A single instance of the PRS resource set shown can also be referred to as a "PRS moment".

[0090] refer to Figure 6 This illustrates example subframes and time slot formats used for positioning reference signal transmission. The example subframes and time slot formats are included in... Figure 5A and Figure 5B The PRS resource set shown. Figure 6 The subframe and time slot formats described are examples and not limitations, and include a comb-2 format 602 with 2 symbols, a comb-4 format 604 with 4 symbols, a comb-2 format 606 with 12 symbols, a comb-4 format 608 with 12 symbols, a comb-6 format 610 with 6 symbols, a comb-12 format 612 with 12 symbols, a comb-2 format 614 with 6 symbols, and a comb-6 format 616 with 12 symbols. Typically, a subframe may include 14 symbol periods indexed from 0 to 13. Typically, a base station may transmit PRS from antenna port 5000 on one or more time slots within each subframe configured for PRS transmission.

[0091] A base station can transmit PRS on a specific PRS bandwidth, which can be configured by higher layers. PRS resources can be located anywhere in the frequency grid. The common reference point for PRS can be defined as "PRS point A". "PRS point A" can be used as the common reference point for the PRS resource block grid and can be represented by the Absolute Radio Channel Number (ARFCN). The PRS Starting Physical Resource Block (PRB) can then be defined as the frequency offset between PRS point A and the lowest subcarrier of the lowest PRS resource block represented in resource blocks. The base station can transmit PRS on subcarriers spaced apart within the PRS bandwidth.

[0092] The base station can also transmit PRS based on parameters such as PRS period, PRS resource set slot offset, PRS resource slot offset, PRS resource repetition factor, and PRS resource time interval. The PRS period is the period during which PRS resources are transmitted, measured in slots. The PRS period can depend on the subcarrier spacing (SCS) and can be, for example, 2. μ The time slots are {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}, with μ = 0, 1, 2, and 3 for SCS 15kHz, 30kHz, 60kHz, and 120kHz, respectively. The PRS resource set time slot offset defines the time slot offset relative to time slot number 0 of the system frame number (SFN) / TRP (i.e., the time slot defining the occurrence of the first PRS resource in the PRS resource set). The PRS resource time slot offset relative to the corresponding PRS resource set time slot offset defines the starting time slot of the PRS resource. As described above, the PRS resource repetition factor defines how many times each PRS resource is repeated for a single instance of the PRS resource set, and the PRS resource time interval defines the offset between two repeating instances of the PRS resource within a single instance of the PRS resource set, in units of time slots.

[0093] PRS resources may be muted. Mute can be signaled using a bitmap to indicate which configured PRS resources are transmitted at zero power (i.e., muted). In one option, the mute bitmap can have a length of {2, 4, 6, 8, 16, 32} bits, and mute is applied to each transmission instance of the PRS resource set. Each bit in the bitmap can correspond to a configurable number of consecutive instances of the PRS resource set. If the corresponding bit in the bitmap indicates "0", all PRS resources within an instance of the PRS resource set can be muted (transmitted at zero power). The number of consecutive instances can be controlled by the parameter PRS mute bit repetition factor, which can have values ​​{1, 2, 4, 8}. In another option, mute can be applied to each repetition of each PRS resource. Each bit in the bitmap can correspond to a single repetition of the PRS resource within an instance of the PRS resource set. The length of the bitmap can then be equal to the PRS resource repetition factor.

[0094] generally, Figure 5A and Figure 5B The PRS resource shown can be a set of resource elements used for PRS transmission. The set of resource elements can span multiple Physical Resource Blocks (PRBs) in the frequency domain and N (e.g., one or more) consecutive symbols within a single time slot in the time domain. In a given OFDM symbol, the PRS resource occupies consecutive PRBs. A PRS resource is described by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size N, resource element offset in the frequency domain, start time slot and start symbol, number of symbols per PRS resource (i.e., duration of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). The comb size indicates the number of subcarriers carrying the PRS in each symbol. For example, a comb size of comb-4 means that every fourth subcarrier in a given symbol carries the PRS.

[0095] A PRS resource set is a group of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same transmit / receive point (e.g., TRP 300). Each PRS resource in a PRS resource set may have the same period, a common silence pattern, and the same repetition factor across time slots. A PRS resource set is identified by a PRS resource set ID and may be associated with a specific TRP (identified by a cell ID) transmitted by the antenna panel of a base station. The PRS resource ID in a PRS resource set may be associated with an omnidirectional signal and / or with a single beam (and / or beam ID) transmitted from a single base station (where a base station may transmit one or more beams). Each PRS resource in a PRS resource set may be transmitted on a different beam; thus, a PRS resource, or simply a resource, may also be referred to as a beam. It should be noted that this has no impact on whether the UE knows the base station and the beam on which it transmits PRS.

[0096] refer to Figure 7 The diagram illustrates a conceptual representation of an example positioning frequency layer 700. In this example, positioning frequency layer 700 can be a collection of PRS resource sets spanning one or more TRPs. Positioning frequency layers can have the same subcarrier spacing (SCS) and cyclic prefix (CP) type, the same PRS point A, the same PRS bandwidth value, the same starting PRB, and the same comb size value. A parameter set (numerology) supporting PDSCH can support PRS. Each PRS resource set in the positioning frequency layer 700 is a collection of PRS resources spanning one TRP, which have the same period, common silence mode configuration, and the same repetition factor across time slots.

[0097] It should be noted that the terms Positioning Reference Signal and PRS refer to reference signals that can be used for positioning, such as, but not limited to, PRS signals, Navigation Reference Signal (NRS) in 5G, Downlink Positioning Reference Signal (DL-PRS), Uplink Positioning Reference Signal (UL-PRS), Tracking Reference Signal (TRS), Cell-Specific Reference Signal (CRS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Sounding Reference Signal (SRS).

[0098] If the PRS is sent by the TRP, it can be called a DL-PRS; if the PRS is sent by the UE, it can be called a UL-PRS. A UL-PRS can be based on an SRS with enhancements for positioning purposes. A UL-PRS can also be called a "positioning SRS". In some respects, a UL-PRS can be considered an uplink equivalent of a DL-PRS.

[0099] The ability of a UE to process PRS signals can vary based on the UE's capabilities. However, industry standards can typically be developed to establish common PRS capabilities for UEs in the network. For example, an industry standard might require the duration of a DL PRS symbol in milliseconds (ms), and assuming the UE supports and reports a maximum DL PRS bandwidth in MHz, the UE can process it once every T ms. As an example, and not a limitation, the maximum DL PRS bandwidth for the FR1 band could be 5MHz, 10MHz, 20MHz, 40MHz, 50MHz, 80MHz, or 100MHz, and the maximum DL PRS bandwidth for the FR2 band could be 50MHz, 100MHz, 200MHz, or 400MHz. These standards can also indicate DL PRS buffering capabilities as Type 1 (i.e., sub-slot / symbol-level buffering) or Type 2 (i.e., slot-level buffering). Common UE capabilities can indicate the duration N of a DL PRS symbol in ms, and assuming the UE supports and reports a maximum DL PRS bandwidth in MHz, the UE can process it once every T ms. Example T values ​​can include 8ms, 16ms, 20ms, 30ms, 40ms, 80ms, 160ms, 320ms, 640ms, and 1280ms, and example N values ​​can include 0.125ms, 0.25ms, 0.5ms, 1ms, 2ms, 4ms, 6ms, 8ms, 12ms, 16ms, 20ms, 25ms, 30ms, 32ms, 35ms, 40ms, 45ms, and 50ms. The UE can be configured to report a combined (N, T) value per frequency band, where N is the duration (in ms) of the DL PRS symbols processed per T ms for a given maximum bandwidth (B) (in MHz) supported by the UE. Typically, it is not expected that the UE will support DL PRS bandwidth exceeding the reported DL PRS bandwidth value. UE DL PRS processing capability can be defined for a single positioning frequency layer 700. UE DL PRS processing capability for, for example... Figure 6 The DL PRS comb factor configuration shown may be unknown. UE processing capability can indicate the maximum number of DL PRS resources that the UE can process in its subordinate time slots. For example, for each SCS: 15kHz, 30kHz, 60kHz, the maximum number for the FR1 band can be 1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64, and for each SCS: 15kHz, 30kHz, 60kHz, 120kHz, the maximum number for the FR2 band can be 1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64.

[0100] refer to Figure 8Example message flow 800 is shown for extending the Mobile Initiated Location Request (MO-LR) procedure to enable on-demand DL-PRS. Example message flow 800 includes a UE 105 and three example TRPs 300, such as the first gNB1 110a, gNB2 110b, and the third gNB3 110c, as well as elements of the core network 140, such as AMF 115 and LMF 120. Message flow 800 can be used to extend existing MO-LR procedures for requesting auxiliary data (e.g., for DL-TDOA, DL-AoD, or multi-RTT). For example, UE 105 can be configured to request UE-assisted or UE-based location-based auxiliary data from LMF 120 using one or more of the positioning methods, and can include additional parameters to indicate DL-PRS preferences. For example, additional parameters may describe the desired PRS configuration and may include one or more of the following: preferred time or time period for PRS configuration (e.g., current time, start time plus stop time); preferred PRS resource bandwidth; preferred duration of PRS positioning timing; preferred period of PRS positioning timing; preferred carrier frequency or frequency layer of PRS resources; and preferred number and location of gNB / TRPs for PRS configuration around the requested UE location, wherein the location of gNB / TRPs may be specified using PCI or CGI, or specified as a specific location or geographic region, which may be specified using absolute global coordinates or using a region identifier (e.g., similar to NR). The location can be represented by the region ID used in the Rel-16 sidelink, or by coordinates relative to a known reference location (such as the location of a specific cell, such as the serving cell provided to the UE in auxiliary data); the preferred PRS beam direction of a single gNB (or multiple preferred PRS beam directions); RSRP or RSRQ measurements performed by the UE on available DL signals (e.g., radio resource management (RRM) measurements); Quality of Service (QoS) parameters describing the accuracy and latency of the target location (e.g., expected accuracy and response time of any location estimate based on PRS measurements (e.g., requested by an internal client (e.g., an App)); and the UE's PRS capabilities (e.g., defined for LPP). Other parameters may also be used based on the configuration and capabilities of the corresponding gNB and UE.

[0101] In the example, these additional parameters can be provided explicitly, for example, indicating the desired PRS resource bandwidth in some units (e.g., PRB, Hz, etc.), or indicating the duration in the number of OFDM symbols or slots, etc. In the example, the additional parameters can be combined into qualitative descriptors such as "high-precision PRS," "medium-precision PRS," and "low-precision PRS" and / or "low-latency PRS," "medium-latency PRS," and "high-latency PRS," where each qualitative descriptor can have an associated quantitative definition. The LMF120 can be configured to determine the appropriate explicit parameters for the PRS configuration using some pre-configured mapping table / function (e.g., via O&M).

[0102] Referring to message flow 800, in phase 0, UE 105 can receive location requests from an internal client (e.g., an App). UE 105 can determine the need to modify DL-PRS transmissions (e.g., increased DL-PRS bandwidth, increased duration of location timing (e.g., increased PRS resource repetition factor), DL-PRS transmissions from a closer gNB, etc.) to meet the application's QoS requirements. In phase 1, if UE 105 is in CM-IDLE state, UE 105 can be configured to initiate a UE-triggered service request as defined in clause 4.2.3.2 of 3GPP TS 23.502 to establish a signaling connection with the AMF. During this phase, AMF 115 can announce to UE 105 its support for MO-LR for on-demand DL-PRS requests; for example, in the 5GS network feature support information element defined in 3GPP TS 24.501. In Phase 2, UE 105 is configured to send an MO-LR request message, included in a UL NAS TRANSPORT message, to the serving AMF 115. This message includes a request to change DL-PRS transmission. The request may include UE 105's DL-PRS capabilities (e.g., in an embedded LPP provisioning capability message) and parameters for preferred DL-PRS configuration (which may include preferred DL-PRS bandwidth, preferred duration of DL-PRS positioning timing, preferred DL-PRS beam direction for a specific gNB (if known to the UE), and a preferred number of nearby gNBs to which this applies). The requested DL-PRS configuration parameters may be provided in an LPP request auxiliary data message included in the MO-LR request. In the example, the request to change (e.g., increase) DL-PRS transmission may also include Quality of Service (QoS) indicators, such as the desired accuracy of location estimation and / or an indication of when an internal client needs a response time for location estimation. The MO-LR request message may also include the duration for which the requested DL-PRS configuration is required at the UE (e.g., the number of seconds or minutes required for DL-PRS configuration). The MO-LR request may also include (e.g., in an embedded LPP location information delivery message) RSRP measurements of the DL signal received by the UE (e.g., per beam) (e.g., E-CID location measurement report) to assist the LMF 120 in determining the beam orientation of the nearby gNB and / or DL-PRS.

[0103] In Phase 3, AMF 115 selects LMF 120 (e.g., as described in Section 5.1 of 3GPP TS 23.273), and in Phase 4, AMF 115 invokes the Nlmf_Location_DetermineLocation service operation to LMF 120. The service operation may indicate one or more of the following: (i) ancillary data requests; (ii) on-demand DL-PRS requests; and (iii) MO-LR requests. The service operation may also include MO-LR requests received in Phase 2, any LPP messages received in Phase 2 that are included in the MO-LR requests in Phase 2, and / or a list of ancillary data types subscribed to by UE 105.

[0104] In phase 5, LMF 120 can first verify that UE 105 has subscribed to a new DL-PRS configuration request based on a list of auxiliary data types subscribed to by UE 105 received in phase 4. Then, based on the request in phase 4, LMF 120 can be configured to determine a new DL-PRS configuration (or multiple DL-PRS configurations) for nearby gNBs in phase 5 (e.g., based on the preferred number of gNBs indicated in phase 2). The determination in phase 5 can also be based on DL-PRS requests received from other UEs in phase 2 and / or the positioning processes of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-110c can use modified (e.g., increased) DL-PRS bandwidth, modified (e.g., longer) duration of the DL-PRS positioning timing, DL-PRS transmissions on a new frequency, and / or DL-PRS positioning timings at higher frequencies. In the example, the new DL-PRS configuration can be selected from a set of one or more pre-configured DL-PRS configuration parameters, such as PRS resources in the positioning frequency layer 700. In a DL-PRS network with beamforming, the LMF 120 can determine the directional DL-PRS beam for each gNB 110a-110c that should be received by the UE 105. The directional DL-PRS beam can be selected by the LMF 120 based on the known approximate location of the target UE 105, for example, by the coverage area of ​​the UE 105's serving or camped cell and / or by the RSRP / ECID measurements provided by the UE 105 in Phase 2.

[0105] In Phase 6, LMF 120 is configured to send an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in Phase 5. This message includes the requested DL-PRS transport characteristics defined for the new DL-PRS configuration determined by that gNB. For example, LMF 120 may include parameter values ​​defined for the new DL-PRS configuration determined by gNB 110 in the NRPPa PRS configuration request message sent to gNB 110. The request may also include the start time and duration of each new DL-PRS configuration (e.g., requested by the UE in Phase 2 or determined by LMF in Phase 5). In Phase 7, each of the gNBs 110a-110c may return a response to LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs 110a-110c indicate that the new DL-PRS configuration is not supported, the LMF 120 can execute stages 15 and 16 to restore the old DL-PRS configuration in each of the gNBs that indicated the new DL-PRS configuration could be supported, to avoid interference between gNBs 110 that support the new DL-PRS configuration and those that do not. In this case, at stage 9, the LMF 120 can provide the UE with the old DL-PRS configuration instead of the new DL-PRS configuration.

[0106] In Phase 8, without providing a start time, after (or before) sending confirmation in Phase 7, or at the start time indicated in Phase 6, each of the gNBs 110a-110c supporting the new DL-PRS configuration is confirmed to have changed from the old DL-PRS configuration to the new DL-PRS configuration in Phase 7. In some cases, the old DL-PRS configuration may correspond to not sending DL-PRS. In some cases, the start time for switching to the new DL-PRS configuration may result in the new DL-PRS being sent after Phase 9 or 10 / 11. This may be typical when the new DL-PRS configuration includes one or more DL-PRS timings. In Phase 9, the LMF120 sends an LPP Provide Auxiliary Data Message to the target UE 105 to provide the new DL-PRS configuration determined in Phase 5 and confirmed in Phase 7. For example, the LMF 120 may include parameter values ​​defined for each new DL-PRS configuration determined in Phase 5 in the LPP Provide Auxiliary Data Message, and may indicate the cell, gNB 110, and / or TRP to which each DL-PRS configuration is applied. In Phase 10, when the auxiliary data with the new DL-PRS configuration has been transmitted to UE 105, LMF 120 returns an Nlmf_Location_DetermineLocation response to AMF 115. The Phase 10 response (or the Phase 9 message) may indicate whether the Phase 2 MO-LR request can be supported (i.e., satisfied), and may (e.g., if MO-LR support is indicated) include the start time and duration of each new DL-PRS configuration (e.g., if the start time requested by UE 105 in Phase 2 differs from the duration determined by LMF 120 in Phase 5). The start time and duration of the new DL-PRS configuration may also be referred to as the validity period or expiration time of the LPP providing auxiliary data message including the DL-PRS configuration. If the Phase 2 on-demand DL-PRS request cannot be satisfied, the reason for failure may be included in the service operation in Phase 10 or in the LPP providing auxiliary data in Phase 9.

[0107] In phase 11, AMF 115 forwards the response from phase 10 to target UE 105 in the form of an MO-LR response. This MO-LR response may indicate whether the MO-LR request from phase 2 can be supported (i.e. satisfied) and may include the start time and duration of each new DL-PRS configuration (if received in phase 10), or may include any failure indications received in phase 10.

[0108] In Phase 12, target UE 105 acquires and measures the DL-PRS transmitted by gNBs 110a-110c based on the new DL-PRS configuration provided in Phase 9. For example, UE 105 may acquire RSTD measurements. In Phase 13, UE 105 determines its location based on the DL-PRS measurements acquired in Phase 12 and the auxiliary data received in Phase 9. In Phase 14, UE 105 provides a location estimate to the internal client that requested location in Phase 0. In Phase 15, if the duration of the new DL-PRS was not included in Phase 6, LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in Phase 5, including a request to restore the old DL-PRS configuration for each gNB 110a-110c. LMF 120 can use the determined duration of the DL-PRS in Phase 5 to determine when to execute Phase 15. In phase 16, each of the gNBs 110a-110c returns a response to the LMF 120, indicating whether the old DL-PRS configuration can be restored. In phase 17, when the duration received in phase 6 expires, or after receiving and confirming the request to restore the old DL-PRS configuration in phases 15 and 16, each of the gNBs 110a-110c begins sending the old DL-PRS configuration.

[0109] Figure 9A and Figure 9B Example message flow 900 is shown for extending the Mobile Initiated Location Request (MO-LR) procedure to enable on-demand DL-PRS and UL-PRS. Example message flow 900 includes a UE 105 and three example TRPs 300, such as the first gNB1 110a, gNB2 110b, and the third gNB3 110c, as well as elements of the core network 140, such as AMF 115 and LMF 120. Message flow 900 can be used to extend the existing MO-LR procedure for UE-triggered on-demand DL-PRS and UL-PRS.

[0110] In Phase 0, UE 105 can receive location requests from internal clients (e.g., Apps). UE 105 is configured to determine if changes to DL-PRS and UL-PRS transports are needed (e.g., increased UL-PRS bandwidth, increased duration of location timing, DL-PRS transports from a closer gNB, etc.) to meet the application's QoS requirements. In Phase 1, if UE 105 is in CM-IDLE state, UE 105 can be configured to initiate a UE-triggered service request as defined in Clause 4.2.3.2 of 3GPP TS 23.502 to establish a signaling connection with AMF 115. In Phase 2, UE 105 is configured to send an MO-LR request message to the serving AMF 115, including a UL NAS TRANSPORT message, which includes a request to change DL-PRS transport and UL-PRS configurations. The request may include UE 105's DL-PRS and UL-PRS capabilities and parameters for preferred DL-PRS and UL-PRS configurations (e.g., for each preferred DL-PRS and UL-PRS configuration, it may include preferred PRS bandwidth, preferred duration of PRS positioning timing, preferred PRS beam direction, and / or a preferred number of nearby gNBs 110a-110c for which this applies). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP request auxiliary data message included in the MO-LR request. Requests to change (e.g., increase) PRS transmissions may also include Quality of Service (QoS) indicators, such as the desired accuracy of location estimation and / or indications of when the internal client needs a response time for location estimation. The MO-LR request message may also include the duration for which the requested PRS configuration is required at the UE (e.g., the number of seconds or minutes required for the DL-PRS and UL-PRS configuration). The MO-LR request may also include RSRP measurements (e.g., per beam) of the DL signals received by the UE (e.g., E-CID location measurement report) to assist the LMF in determining the beam orientation of nearby gNBs and / or PRSs.

[0111] In Phase 3, AMF 115 is configured to select LMF 120 (e.g., as described in Section 5.1 of 3GPP TS 23.273). In Phase 4, AMF 115 invokes the Nlmf_Location_DetermineLocation service operation to LMF 120. The service operation may indicate one or more of the following: (i) ancillary data requests; (ii) on-demand DL-PRS and / or UL-PRS requests; (iii) MO-LR requests. The service operation may also include MO-LR requests received in Phase 2, any LPP messages received in Phase 2 that are included in the MO-LR requests in Phase 2, and / or a list of ancillary data types subscribed to by UE 105.

[0112] In Phase 5, LMF 120 can first verify that UE 105 has subscribed to request new DL-PRS and UL-PRS configurations based on a list of auxiliary data types subscribed to by UE 105 received in Phase 4. Then, in Phase 5, based on the requests in Phase 4, LMF 120 determines new DL-PRS configurations for nearby gNBs 110a-110c (e.g., based on the preferred number of gNBs indicated in Phase 2). The determination in Phase 5 can also be based on DL-PRS requests received from other UEs in Phase 2 and / or the positioning processes of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-110c can use changed (e.g., increased) DL-PRS bandwidth, changed (e.g., longer) duration of DL-PRS positioning timing, DL-PRS transmissions on new frequencies, and / or higher frequency DL-PRS positioning timings. In the example, the new DL-PRS configuration can be selected from a set of one or more pre-configured DL-PRS configuration parameters. In a network with beamforming DL-PRS, LMF 120 can determine the directional DL-PRS beam for each gNB 110a-110c that should be received by UE 105. The directional DL-PRS beam can be selected by LMF 120 based on the known approximate location of the target UE 105, for example, by the coverage area of ​​the UE's serving or camped cell and / or by RSRP / ECID measurements provided by UE 105 in Phase 2. As an option at Phase 5, LMF 120 can determine, adjust, or change one or more parameters of a preferred UL-PRS configuration, in some cases, which may have already been sent by UE 105 in Phase 2 (and received by LMF 120 in Phase 4). For example, LMF 120 can determine or change such UL-PRS parameters to a preferred UL-PRS bandwidth and / or a preferred duration of the UL-PRS positioning timing, for example, if the determination or change is indicated to be supported by the UL-PRS capability of UE 105 sent in Phase 2.

[0113] In phase 6, LMF 120 sends an NRPPa Location Information Request message to serving gNB 110a to request UL-PRS configuration for target UE 105. The NRPPa Location Information Request message includes the desired UL-PRS configuration parameters from phase 2 or phase 5 (if these parameters are determined or changed in phase 5).

[0114] In phase 7, the serving gNB 110a of target UE 105 determines the UL-PRS configuration based on the parameters received in phase 6. If the request can be partially satisfied, gNB 110a selects possible configuration parameters, which may differ from the parameters requested in phase 6. In phase 8, the serving gNB 110a of target UE 105 provides the UL-PRS configuration parameters to LMF 120. In phase 9, the serving gNB 110a of target UE 105 provides the UL-PRS configuration parameters to UE 105 in a Radio Resource Control (RRC) message. In the example, if LMF 120 also selected the UL-PRS configuration in phase 5 (in addition to the DL-PRS selection), phases 6 through 9 may not be necessary. In this case, the UL-PRS configuration parameters can be provided to UE 105 in phase 13. In phase 10, LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in phase 5. This message includes the requested DL-PRS transport characteristics defined as the new DL-PRS configuration determined by that gNB. The request may also include the start time and duration of each new DL-PRS configuration (e.g., requested by the UE in phase 2 or determined by LMF 120 in phase 5). In phase 11, each of the gNBs 110a-110c returns a response to LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs indicate that the new DL-PRS configuration is not supported, LMF 120 may execute phases 26 and 27 to restore the old DL-PRS configuration in each of the gNBs 110a-110c that indicated the new DL-PRS configuration can be supported, to avoid interference between gNBs that support the new DL-PRS configuration and those that do not. In this scenario, during phase 13, the LMF 120 can provide the UE with the old DL-PRS configuration instead of the new DL-PRS configuration.

[0115] In phase 12, without providing a start time, after (or before) sending confirmation in phase 11 or at the start time indicated in phase 10, each of the gNBs 110a-110c supporting the new DL-PRS configuration is confirmed to have changed from the old DL-PRS configuration to the new DL-PRS configuration in phase 11. In some cases, the old DL-PRS configuration may correspond to not sending DL-PRS. In phase 13, the LMF 120 sends an LPP Provide Auxiliary Data Message to the target UE 105 to provide the new DL-PRS configuration determined in phase 5 and confirmed in phase 11 (e.g., providing parameters defining these configurations). In phase 14, the LMF 120 sends an NRPPa Location Activation Request Message to the serving gNB 110a of the target UE 105 to request activation of the UL-PRS in UE 105 according to one or more configurations provided to UE 105 in phase 9. In phase 15, serving gNB 110a sends a MAC control element to UE 105 to activate UL-PRS according to the request in phase 14. If a start time is provided in phase 14, serving gNB 110a sends the command at the requested start time. In phase 16, if UL-PRS has been successfully activated, serving gNB 110a returns an NRPPa location activation response message to LMF 120. If the requested start time provided in phase 14 cannot be met, serving gNB 110a can determine a different start time and provide the selected start time to LMF 120. In phase 17, target UE 105 sends UL-PRS according to the activation configuration in phase 15.

[0116] like Figure 9B As shown, in phase 18, LMF 120 sends an NRPPa measurement request message to gNBs 110a-110c selected in phase 5 to request UL-PRS measurements (e.g., gNB Rx-Tx time difference measurements). In phase 19, when auxiliary data with the new DL-PRS configuration has been transmitted to UE 105 and the NRPPa UL-PRS measurement request has been activated at gNBs 110a-110c, LMF 120 returns an Nlmf_Location_DetermineLocation response to AMF 115, which can indicate the success or failure of the request sent by AMF 115 in phase 4. If the on-demand PRS request in phase 2 cannot be satisfied, the reason for failure can be included in the service operation in phase 19 or in the provision of auxiliary data via LPP in phase 13. In phase 20, AMF115 sends an MO-LR response message to the target UE 105 and may indicate the success or failure of supporting the MO-LR request, as shown in phase 19, and may include any failure reasons received in phase 19.

[0117] Alternatively, phases 19 and 20 can appear Figure 9A / Figure 9B The later stages of the process. In one alternative, stages 19 and 20 may occur after stage 23, when both the LPP providing auxiliary data message including DL-PRS configuration in stage 13 and the LPP providing auxiliary data message with UL-PRS measurement results in stage 23 have been provided to UE 105. In another alternative, stages 19 and 20 may occur after stage 30, when the LPP providing auxiliary data message including DL-PRS configuration in stage 13, the LPP providing auxiliary data message with UL-PRS measurement results in stage 23, and the UL-PRS deactivation in stage 30 occur.

[0118] In phase 21a, target UE 105 acquires and measures the DL-PRS sent by gNBs 110a-110c according to the new DL-PRS configuration provided in phase 13. In phase 21b, gNBs 110a-110c, having received the measurement request in phase 18, acquire and measure the UL-PRS sent by target UE 105 in phase 17.

[0119] In the example, LMF 120 can determine the start time for switching to the new DL-PRS configuration (phase 12) and activating UL-PRS transmission (phase 17) such that phases 12 and 17 occur approximately simultaneously (e.g., in cases where one or more UL-PRS and DL-PRS events are sent / requested). For example, the start time can be selected such that phases 12 and 17 occur together (e.g., after phase 20). In phase 22, gNBs 110a-110c provide UL-PRS measurements to LMF 120. In phase 23, LMF 120 forwards the UL-PRS measurements received in phase 22 to the target UE 105 in an LPP auxiliary data message.

[0120] In phase 24, UE 105 is configured to determine its location based on the DL-PRS measurements obtained in phase 21a, the UL-PRS measurements received in phase 23, and the auxiliary data received in phase 13. In phase 25, UE 105 provides a location estimate to the internal client that requested the location in phase 0.

[0121] In phase 26, if the duration of the new DL-PRS was not included in phase 10, LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in phase 5, including a request to restore the old DL-PRS configuration of each gNB 110a-110c. LMF 120 may use the determined duration of the DL-PRS in phase 5 to determine when to execute phase 26. In phase 27, each of the gNBs 110a-110c returns a response to LMF 120 indicating whether the old DL-PRS configuration can be restored. In phase 28, each of the gNBs 110a-110c may begin sending the old DL-PRS configuration when the duration received in phase 10 expires, or after receiving and confirming the request to restore the old DL-PRS configuration in phases 26 and 27. In phase 29, LMF 120 may send an NRPPa location deactivation request message to the serving gNB 110a of the target UE 105 to request the deactivation of the UE's UL-PRS transmission. In phase 30, the serving gNB 110a sends a MAC control element to the target UE to deactivate the UL-PRS transmission according to the request in phase 29.

[0122] refer to Figure 10A and Figure 10B Example message flow 1000 is shown for extending the On-Demand System Information (SI) procedure to implement On-Demand DL-PRS. Example message flow 1000 includes a UE 105 and three example TRPs 300, such as the first gNB1 110a, gNB2 110b, and the third gNB3 110c, as well as elements of the core network 140, such as AMF 115 and LMF 120. Message flow 1000 can be used to extend the On-Demand System Information (SI) procedure for requesting broadcast auxiliary data. Location auxiliary data can be provided via LPP point-to-point (unicast) or via location SI (broadcast). Location SI messages containing DL-PRS auxiliary data can be broadcast periodically or when there is a request from a UE. In the example, the core network 140 can be configured to determine whether the requested broadcast auxiliary data (i.e., a Location System Information Block (posSIB)) is provided using broadcast or point-to-point (unicast) via an RRC reconfiguration message. This procedure can be applied to On-Demand PRS. For example, a broadcast message (e.g., System Information Block 1 (SIB1) or a broadcast auxiliary data element) may include an indicator of whether the network supports on-demand PRS. For example, a broadcast message may indicate: on-demand-prs ENUMERATED{dl-prs, ul-prs, ul-and-dl-prs}.

[0123] This indicator (or equivalent indicator) can also be used with the example message flows 800 and 900 described above to instruct the UE that on-demand PRS is supported in the network via the MO-LR process.

[0124] refer to Figure 10A In Phase 1, gNBs 110a-110c in the network broadcast SIB1, which may include an indicator of whether on-demand DL-PRS is available / supported by the gNB. UE 105 can receive SIB1 from the serving gNB 110a. In Phase 2, UE 105 is configured to receive location requests from internal clients (e.g., Apps). UE 105 can determine that changes to DL-PRS transmissions are needed (e.g., increased DL-PRS bandwidth, increased duration of location timings (e.g., increased PRS resource repetition factor), DL-PRS transmissions from a closer gNB, etc.) to meet the application's QoS requirements. In Phase 3, UE 105 sends an RRC-specific SIB request message to the serving gNB to request on-demand DL-PRS (e.g., a request to change DL-PRS transmissions). The request may include parameters for the DL-PRS capability of UE 105 and the preferred DL-PRS configuration (which may include preferred DL-PRS bandwidth, preferred duration of DL-PRS positioning timing, preferred DL-PRS beam direction for a specific gNB (if known to the UE), and preferred number of nearby gNBs to which this applies). The request for increased DL-PRS transmission may also include Quality of Service (QoS) indicators, such as the required accuracy of location estimation and / or an indication of when the internal client needs a response time for location estimation. The RRC-specific SIB request message may also include the duration for which the requested DL-PRS configuration is required at the UE (e.g., the number of seconds or minutes required for DL-PRS configuration). The RRC-specific SIB request message may also include RSRP measurements (e.g., per beam) of the DL signals received by UE 105 (e.g., RRC measurement reports) to assist LMF 120 in determining the beam direction of nearby gNBs and / or DL-PRS. In phase 4, the serving gNB 110a sends an NRPPa auxiliary information feedback message to LMF 120. This message includes an on-demand DL-PRS request received from UE 105 in Phase 3.

[0125] In Phase 5, based on the request in Phase 4, LMF 120 is configured to determine a new DL-PRS configuration for nearby gNBs 110a-110c (e.g., based on the preferred number of gNBs indicated in Phase 3). The determination in Phase 5 can also be based on DL-PRS requests received from other UEs as in Phase 3 and / or the location processes of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-110c can use altered (e.g., increased) DL-PRS bandwidth, altered (e.g., longer) duration of DL-PRS location timing, DL-PRS transmission on a new frequency, and / or DL-PRS location timing at a higher frequency. In some cases, the new DL-PRS configuration can be selected from a set of one or more pre-configured DL-PRS configuration parameters. In networks with beamforming DL-PRS, LMF 120 can determine the directional DL-PRS beam for each gNB that should be received by UE 120. The directional DL-PRS beam can be selected by the LMF 120 based on the known approximate location of the target UE 105, such as by the coverage area of ​​the UE 105's serving or camped cell and / or by the RSRP measurements provided by the UE in Phase 3.

[0126] In phase 6, LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in phase 5. This message includes the requested DL-PRS transport characteristics defined for the new DL-PRS configuration determined by that gNB. The request may also include the start time and duration of each new DL-PRS configuration (e.g., requested by UE 105 in phase 3 or determined by LMF 120 in phase 5). In phase 7, each of the gNBs 110a-110c returns a response to LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs 110a-110c indicate that the new DL-PRS configuration is not supported, the LMF 120 can execute stages 15 and 16 to restore the old DL-PRS configuration in each of the gNBs 110a-110c that indicated the new DL-PRS configuration could be supported, to avoid interference between gNBs that support the new DL-PRS configuration and those that do not. In this case, in stages 9 and 10, the LMF 120 will provide the UE 105 with the old DL-PRS configuration instead of the new DL-PRS configuration.

[0127] In Phase 8, without providing a start time, after (or before) sending the acknowledgment in Phase 7 or at the start time indicated in Phase 6, each of the gNBs 110a-110c supporting the new DL-PRS configuration is confirmed in Phase 7 to have changed from the old DL-PRS configuration to the new DL-PRS configuration. In some cases, the old DL-PRS configuration may correspond to not sending DL-PRS. In Phase 9, LMF 120 is configured to send an NRPPa Auxiliary Information Control Message to the serving gNB 110a to provide the new DL-PRS configuration determined in Phase 5 and confirmed in Phase 7. The DL-PRS configuration information may be provided in posSIB format (i.e., using parameters and encoding defined for broadcast auxiliary data). In Phase 10, the serving gNB 110a is configured to provide the DL-PRS configuration information received in Phase 9 to UE 105 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an octet string containing the DL-PRS configuration in posSIB format received in Phase 9. In phase 11, UE 105 confirms the RRC reconfiguration and returns an RRC reconfiguration complete message to the serving gNB.

[0128] refer to Figure 10B In phase 12, target UE 105 acquires and measures the DL-PRS transmitted by the gNB based on the new DL-PRS configuration provided in phase 10. For example, UE 105 may acquire RSTD measurements. In phase 13, UE 105 determines its location based on the DL-PRS measurements acquired in phase 12 and the auxiliary data received in phase 10. In phase 14, UE 105 is configured to provide a location estimate to the internal client that requested location in phase 2.

[0129] In phase 15, if the duration of the new DL-PRS is not included in phase 6, LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in phase 5, including a request to restore the old DL-PRS configuration of each gNB. LMF 120 may use the determined duration of the DL-PRS in phase 5 to determine when to execute phase 15. In phase 16, each of the gNBs 110a-110c returns a response to LMF 120 indicating whether the old DL-PRS configuration can be restored. In phase 17, each of the gNBs 110a-110c may begin sending the old DL-PRS configuration when the duration received in phase 6 expires, or after receiving and confirming the request to restore the old DL-PRS configuration in phases 15 and 16. In phase 18, LMF 120 may be configured to send an NRPPa auxiliary information control message to the serving gNB, including posSIB information of the restored DL-PRS configuration.

[0130] refer to Figure 11A and Figure 11B Example message flow 1100 is shown for extending the On-Demand System Information (SI) procedure to implement On-Demand DL-PRS and UL-PRS. Example message flow 1100 includes UE 105 and three example TRPs 300, such as the first gNB 1110a, gNB2 110b, and the third gNB3 110c, as well as elements of the core network 140, such as AMF 115 and LMF 120. Message flow 1100 can be used to extend the On-Demand System Information (SI) procedure for requesting broadcast auxiliary data.

[0131] refer to Figure 11AIn Phase 1, gNBs 110a-110c in the network broadcast SIB1, which may include indicators of whether on-demand DL-PRS and UL-PRS are available / supported by the gNB. UE 105 can receive SIB1 from the serving gNB 110a. In Phase 2, UE 105 can receive location requests from internal clients (e.g., Apps). UE 105 can determine that changes to DL-PRS and UL-PRS transmissions are needed (e.g., increased UL-PRS bandwidth, increased duration of location timing, DL-PRS transmissions from a closer gNB, etc.) to meet the application's QoS requirements. In Phase 3, UE 105 sends an RRC-specific SIB request message to the serving gNB 110a to request on-demand DL-PRS transmissions and UL-PRS configuration. The request may include the UE's DL-PRS and UL-PRS capabilities and parameters for the preferred DL-PRS and UL-PRS configuration (which may include preferred PRS bandwidth, preferred duration of PRS positioning timing, preferred PRS beam orientation, and preferred number of nearby gNBs to which this applies). Requests to change PRS transmission may also include Quality of Service (QoS) indicators, such as the required accuracy of location estimation and / or an indication of when the internal client needs a response time for location estimation. The RRC-specific SIB request message may also include the duration for which the requested PRS configuration is required at UE 105 (e.g., the number of seconds or minutes required for DL-PRS and UL-PRS configuration). The RRC-specific SIB request message may also include RSRP measurements (e.g., per beam) of the DL signals received by UE 105 (e.g., RRC measurement reports) to assist LMF 120 in determining the beam orientation of nearby gNBs and / or PRS.

[0132] In phase 4, the serving gNB 110a sends an NRPPa Assistance Information Feedback message to the LMF 120. This message includes the on-demand DL-PRS and UL-PRS requests received from UE 105 in phase 3. In phase 5, based on the requests in phase 4, the LMF 120 is configured to determine a new DL-PRS configuration for nearby gNBs (e.g., based on the preferred number of gNBs indicated in phase 3). The determination in phase 5 can also be based on DL-PRS requests received from other UEs in phase 3 and / or the location processes of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB can use increased DL-PRS bandwidth, longer duration of DL-PRS location timing, DL-PRS transmissions on new frequencies, and / or higher frequency DL-PRS location timing. In some cases, the new DL-PRS configuration can be selected from a set of one or more pre-configured DL-PRS configuration parameters. In a DL-PRS network utilizing beamforming, LMF 120 can determine the directional DL-PRS beam for each gNB that should be received by UE 105. The directional DL-PRS beam can be selected by LMF 120 based on the known approximate location of the target UE 105, such as by the coverage area of ​​the serving or camped cell of UE 105 and / or by the RSRP measurements provided by UE 105 in Phase 3. In Phase 6, LMF 120 sends an NRPPa location information request message to serving gNB 110a to request UL-PRS configuration for the target UE 105. The NRPPa location information request message includes the desired UL-PRS configuration parameters from Phase 3. In Phase 7, serving gNB 110a of the target UE 105 determines the UL-PRS configuration based on the parameters received in Phase 6. If the request can be partially satisfied, gNB 110a selects possible configuration parameters, which may differ from the parameters requested in Phase 6. In phase 8, the serving gNB 110a of target UE 105 provides UL-PRS configuration parameters to LMF 120. In phase 9, the serving gNB 110a of target UE 105 provides UL-PRS configuration parameters to UE 105 in an RRC message. In an embodiment, if LMF 120 also selected UL-PRS configuration in phase 5 (in addition to DL-PRS selection), phases 6 to 9 may not be necessary. In this case, the UL-PRS configuration parameters can be provided to UE 105 in phases 13 / 14.

[0133] In phase 10, LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-110c identified in phase 5, including the new DL-PRS configuration identified for that gNB. This request may also include the start time and duration of each new DL-PRS configuration (e.g., requested by UE 105 in phase 3 or determined by LMF 120 in phase 5). In phase 11, each of the gNBs 110a-110c returns a response to LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs indicate that the new DL-PRS configuration is not supported, LMF 120 may execute phases 26 and 27 to restore the old DL-PRS configuration in each of the gNBs 110a-110c that indicated the new DL-PRS configuration can be supported, to avoid interference between gNBs that support the new DL-PRS configuration and those that do not. In this scenario, during phases 13 / 14, the LMF120 may provide the old DL-PRS configuration to the UE 105 instead of the new DL-PRS configuration. In phase 12, without a provided start time, after (or before) sending confirmation in phase 11 or at the start time indicated in phase 10, each of the gNBs 110a-110c supporting the new DL-PRS configuration is confirmed to have changed from the old DL-PRS configuration to the new DL-PRS configuration in phase 11. In some cases, the old DL-PRS configuration may correspond to not sending DL-PRS. In phase 13, the LMF 120 sends an NRPPa auxiliary information control message to the serving gNB 110a to provide the new DL-PRS configuration determined in phase 5 and confirmed in phase 11. The DL-PRS configuration information may be provided in the form of posSIB (i.e., using parameters and encoding defined for broadcast auxiliary data).

[0134] In phase 14, the serving gNB 110a may provide the UE with the DL-PRS configuration information received in phase 13 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an octet string containing the DL-PRS configuration in posSIB format received in phase 13. In phase 15, UE 105 acknowledges the RRC reconfiguration and returns an RRC reconfiguration complete message to the serving gNB 110a. In phase 16, LMF 120 sends an NRPPa Location Activation Request message to the serving gNB 110a of the target UE 105 to request the activation of the UL-PRS in UE 105 according to one or more configurations provided to UE 105 in phase 9. In phase 17, the serving gNB 110a may send a MAC control element to UE 105 to activate the UL-PRS according to the request in phase 16. If a start time is provided in phase 16, the serving gNB 110a may send the command at the requested start time. In phase 18, if the UL-PRS has been successfully activated, service gNB 110a returns an NRPPa location activation response message to LMF 120. If the requested start time provided in phase 16 cannot be met, service gNB 110a can determine a different start time and provide the selected start time to LMF 120.

[0135] Message Stream 1100 Figure 11B The process continues, and in phase 19, target UE 105 is configured to send UL-PRS according to the configuration activated in phase 17. In phase 20, LMF 120 sends an NRPPa measurement request message to gNBs 110a-110c selected in phase 5 to request UL-PRS measurement (e.g., gNB Rx-Tx time difference measurement). In phase 21a, target UE acquires and measures the DL-PRS sent by gNB according to the new DL-PRS configuration provided in phase 14. In phase 21b, gNBs 110a-110c, having received the measurement request in phase 20, acquire and measure the UL-PRS sent by target UE 105 in phase 19. In phase 22, gNBs 110a-110c can provide the UL-PRS measurement to LMF 120. In the example, LMF 120 can determine the start time for switching to the new DL-PRS configuration (phase 12) and activating UL-PRS transmission (phase 19) such that phases 12 and 19 occur approximately simultaneously (e.g., in cases where one or more UL-PRS and DL-PRS events are sent / requested). For example, the start time can be selected such that phases 12 and 19 occur together (e.g., after phase 20).

[0136] In this embodiment, at stage 23, LMF 120 may forward the UL-PRS measurement received at stage 22 to the target UE 105 in an LPP (Local Power Provider) auxiliary data message. At stage 24, UE 105 may be configured to determine its location based on the DL-PRS measurement obtained at stage 21a, the UL-PRS measurement received at stage 23, and the auxiliary data received at stage 14. At stage 25, UE 105 may be configured to provide a location estimate to the internal client that requested location at stage 2.

[0137] In phase 26, if the duration of the new DL-PRS was not included in phase 10, LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-110c determined in phase 5, including a request to restore the old DL-PRS configuration of each gNB. LMF 120 may use the determined duration of the DL-PRS in phase 5 to determine when to execute phase 26. In phase 27, each of the gNBs 110a-110c may return a response to LMF 120 indicating whether the old DL-PRS configuration can be restored. In phase 28, each of the gNBs 110a-110c begins sending the old DL-PRS configuration when the duration received in phase 10 expires, or after receiving and confirming the request to restore the old DL-PRS configuration in phases 26 and 27. In phase 29, LMF 120 may send an NRPPa auxiliary information control message to the serving gNB, including posSIB information of the restored DL-PRS configuration. In phase 30, LMF 120 may send an NRPPa location deactivation request message to the serving gNB 110a of the target UE to request the deactivation of the UE's UL-PRS transmission. In phase 31, serving gNB 110a may send a MAC control element to the target UE 105 to activate the UL-PRS transmission according to the request in phase 30.

[0138] refer to Figure 12 And further reference Figures 1 to 11B A method 1200 for determining the location of a mobile device using on-demand positioning reference signals includes the stages shown. However, method 1200 is illustrative and not limiting. For example, method 1200 can be modified by adding, removing, rearranging, combining, performing stages simultaneously, and / or dividing a single stage into multiple stages. Method 1200 can be derived from, for example, Figure 1 UE 105 or Figure 2 The UE 200 in the UE is used to execute.

[0139] At stage 1202, the method includes sending a request for a downlink location reference signal to a network server (e.g., AMF 115 or LMF 120), wherein the request includes location reference signal configuration information. A mobile device, such as UE 200, is a component for sending (e.g., transmitting) the request for the downlink location reference signal. In an embodiment, UE 200 may receive a location request from an internal application and determine that it may need increased DL-PRS bandwidth, increased duration of location timing, and / or DL-PRS transmissions from more nearby gNBs to meet QoS requirements from that application. In an example, UE 200 may send an MO-LR request message to the serving AMF 115, including a request for increased DL-PRS transmissions within a UL NAS TRANSPORT message. This request may include parameters of UE 200's DL-PRS capabilities and preferred DL-PRS configurations (e.g., preferred DL-PRS bandwidth, preferred duration of DL-PRS location timing, preferred DL-PRS beam direction, and preferred number of nearby gNBs, etc.). The requested DL-PRS configuration parameters can be provided in an LPP request auxiliary data message included in the MO-LR request. In the example, the request for increased DL-PRS transmission may also include Quality of Service (QoS) indicators, such as the required accuracy of location estimation and / or an indication of when the internal client needs a response time for location estimation. The MO-LR request message may also include the duration for which the requested DL-PRS configuration is required at UE 200. The MO-LR request may also include RSRP measurements (e.g., per beam) of the DL signals received by UE 200 (e.g., E-CID location measurement reports) to assist LMF 120 in determining the beam direction of nearby gNBs and / or DL-PRS.

[0140] In another embodiment, UE 200 may be configured to send an RRC-specific SIB request message to the serving gNB to request on-demand DL-PRS (e.g., a request for increased DL-PRS transmission). This request may include parameters of the UE 200's DL-PRS capabilities and preferred DL-PRS configurations (e.g., preferred DL-PRS bandwidth, preferred duration of DL-PRS positioning timing, preferred DL-PRS beam direction for a specific gNB, and preferred number of nearby gNBs, etc.). The request may also include QoS indicators, such as the required accuracy of location estimation and / or an indication of when an internal client needs a response time for location estimation. The RRC-specific SIB request message may also include the duration for which the requested DL-PRS configuration is required at the UE (e.g., the number of seconds or minutes required for DL-PRS configuration). The RRC-specific SIB request message may also include RSRP measurements (e.g., per beam) of the DL signals received by UE 200 (e.g., RRC measurement reports) to assist LMF 120 in determining the beam direction of nearby gNBs and / or DL-PRS.

[0141] In an embodiment, a request for a downlink positioning reference signal may be provided to the LMF 120 from the AMF 115, the previous serving AMF, the previous serving LMF, and / or the previous serving TRP 300 such as gNB 110a. For example, there may be handover between serving cells (e.g., serving TRPs), and the request for the downlink positioning reference signal may be a continuous request for a specific duration.

[0142] In phase 1204, the method includes receiving auxiliary data based on positioning reference signal configuration information. UE 200 is the component used to receive the auxiliary data. In an embodiment, a network server such as LMF 120 may be configured to determine a new DL-PRS configuration for a nearby gNB based at least in part on the PRS configuration information received in phase 1202. This determination may also be based on DL-PRS requests received from other UEs and / or positioning processes of other UEs occurring approximately simultaneously. The new DL-PRS configuration may use increased DL-PRS bandwidth, longer duration of DL-PRS positioning opportunities, DL-PRS transmissions on new frequencies, and / or DL-PRS positioning opportunities at higher frequencies. In an example, the new DL-PRS configuration may be selected from a set of one or more pre-configured DL-PRS configuration parameters, such as PRS resources in positioning frequency layer 700. In a network with beamforming DL-PRS, LMF 120 may determine directional DL-PRS beams for different gNBs that UE 200 can receive. The directional DL-PRS beam can be selected by LMF 120 based on the known approximate location of UE 200, such as the coverage area of ​​the serving or camped cell of UE 105 and / or given by the RSRP / ECID measurements provided by UE 200 in phase 1202.

[0143] In this embodiment, LMF 120 can be configured to send an NRPPa auxiliary information control message to serving gNB 110a to provide a new DL-PRS configuration. The DL-PRS configuration information can be provided in posSIB format (i.e., using parameters and encoding defined for broadcast auxiliary data). Serving gNB 110a can be configured to provide the DL-PRS configuration information to UE 200 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery can consist of an octet string containing the DL-PRS configuration in posSIB format.

[0144] In phase 1206, the method includes measuring one or more downlink positioning reference signals (DL-PRSs) at least in part based on downlink positioning reference signal configuration information. UE 200 is a component for measuring one or more downlink positioning reference signals. UE 200 is configured to acquire and measure DL-PRS transmitted by gNB 110a-110c according to the DL-PRS configuration provided in the auxiliary data received in phase 1204. For example, but not limited to, UE 200 may acquire RSTD measurements based on DL-PRS transmissions. UE 200 may be configured to acquire other measurements based on DL-PRS transmissions.

[0145] In phase 1208, the method includes determining location (e.g., the location of the UE) based at least in part on measurements and auxiliary data obtained from one or more downlink positioning reference signals. UE 200 is an example component for determining location. UE 200 is configured to determine location based on DL-PRS measurements obtained in phase 1206 and auxiliary data received in phase 1204. For example, UE 200 may utilize RSTD measurements to determine distances to multiple gNBs and utilize the locations of the gNBs to determine its current location. Other known positioning techniques such as OTDOA, AoD, multiple RTT, and ECID may also be used to determine the location of UE 200.

[0146] refer to Figure 13 And further reference Figures 1 to 11B Method 1300 for providing auxiliary data for on-demand positioning reference signals includes the stages shown. However, method 1300 is illustrative and not limiting. For example, method 1300 can be modified by adding, removing, rearranging, combining, performing stages simultaneously, and / or dividing a single stage into multiple stages. Method 1300 can be provided by a server or location server (e.g., Figure 1 LMF 120 or Figure 4 The server in the middle (400) is used to execute.

[0147] At stage 1302, the method includes receiving a request for a downlink positioning reference signal (e.g., sent by a UE such as UE 105), wherein the request includes positioning reference signal configuration information. A server 400, such as LMF 120, is a component for receiving the request for DL-PRS. In an embodiment, UE 200 may be configured to send an MO-LR request message, including a UL NAS TRANSPORT message, to serving AMF 115, which includes a request for increased DL-PRS transmission. This request may include configuration information, such as UE 200's DL-PRS capabilities and parameters of preferred DL-PRS configuration (e.g., preferred DL-PRS bandwidth, preferred duration of DL-PRS positioning timing, preferred DL-PRS beam direction, and preferred number of nearby gNBs). The requested DL-PRS configuration parameters may be provided in an LPP request auxiliary data message included in the MO-LR request. In the example, the request for increased DL-PRS transmission may also include Quality of Service (QoS) indicators, such as the required accuracy of location estimation and / or an indication of when the internal client needs a response time for location estimation. The MO-LR request message may also include the duration for which the requested DL-PRS configuration is required at UE 200. The MO-LR request may also include RSRP measurements (e.g., per beam) of the DL signal received by UE 200 (e.g., E-CID location measurement report) to assist LMF 120 in determining the beam direction of nearby gNBs and / or DL-PRS. AMF 115 may invoke the Nlmf_Location_DetermineLocation service operation to LMF 120. The service operation may include the MO-LR request received from UE 200.

[0148] In this embodiment, the serving gNB 110a is configured to send an NRPPa auxiliary information feedback message to the LMF 120. This message may include DL-PRS configuration information received by gNB 110a from UE 105 via an RRC dedicated SIB request.

[0149] At stage 1304, the method includes determining one or more base stations providing downlink positioning reference signals based on positioning reference signal configuration information. Server 400 is a component for determining the one or more base stations. In an embodiment, LMF 120 may be configured to determine a new DL-PRS configuration for a nearby base station (e.g., gNB) based at least in part on the configuration information. For example, the new DL-PRS configuration for each base station may use increased DL-PRS bandwidth, longer-duration DL-PRS positioning timing, DL-PRS transmission on a new frequency, and / or higher-frequency DL-PRS positioning timing. In the example, the new DL-PRS configuration may be selected from one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in positioning frequency layer 700. In a network with beamforming DL-PRS, LMF 120 may determine the directional DL-PRS beams that should be received by UE 105 for each base station. The directional DL-PRS beam can be selected by the LMF 120 based on the known approximate location of the target UE 105, such as by the coverage area of ​​the serving or camped cell of the UE 105 and / or by the RSRP / ECID measurements provided in the DL-PRS request received in phase 1302.

[0150] In phase 1306, the method includes providing positioning reference signal configuration information to one or more base stations. Server 400 is a component for providing DL-PRS configuration information. In the example, LMF 120 is configured to send an NRPPa PRS configuration request message to each of the base stations determined in phase 1304, the message including a new DL-PRS configuration determined for that base station. The request may also include the start time and duration of each new DL-PRS configuration (e.g., provided in a request received in phase 1302, or determined by LMF 120).

[0151] In phase 1308, the method includes providing auxiliary data based on positioning reference configuration information. Server 400 is a component for providing auxiliary data. In one embodiment, LMF 120 may be configured to send an LPP Provide Auxiliary Data Message to the target UE 105 to provide a new DL-PRS configuration. In another embodiment, LMF 120 may be configured to send an NRPPa Auxiliary Information Control Message to the serving base station to provide a new DL-PRS configuration. The DL-PRS configuration information may be provided in the form of posSIB (i.e., using parameters and encoding defined for broadcast auxiliary data). The serving base station may be configured to provide the DL-PRS configuration information to UE 105 in a dedicated (unicast) RRC reconfiguration message. dedicatedPosSysInfoDelivery may consist of an octet string containing the received DL-PRS configuration in posSIB format.

[0152] refer to Figure 14 And further reference Figures 1 to 11B A method 1400 for determining the location of a mobile device using on-demand downlink positioning reference signals and uplink positioning reference signals includes the stages shown. However, method 1400 is illustrative and not limiting. For example, method 1400 can be modified by adding, removing, rearranging, combining, performing stages simultaneously, and / or dividing a single stage into multiple stages. Figure 1 UE 105 or Figure 2 The UE 200 in the UE is used to execute.

[0153] In phase 1402, the method includes sending a request to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes downlink positioning reference signal configuration information and uplink positioning reference signal configuration information. UE 200 is a component for sending (e.g., transmitting) the request for DL-PRS and UL-PRS. In an embodiment, UE 200 may be configured to send an MO-LR request message to serving AMF 115, including a UL NAS TRANSPORT message, which includes a request for increased DL-PRS transmission and UL-PRS configuration. The request may include UE 105's DL-PRS and UL-PRS capabilities and parameters for preferred DL-PRS and UL-PRS configurations (e.g., preferred PRS bandwidth, preferred duration of PRS positioning timing, preferred PRS beam direction, and preferred number of nearby gNBs 110a-110c for which this applies). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP request auxiliary data message included in the MO-LR request. Requests to increase PRS transmission may also include QoS indicators, such as the required accuracy of location estimation and / or indications of when the internal client needs the response time for location estimation. The MO-LR request message may also include the duration for which the requested PRS configuration is required at UE 200 (e.g., the number of seconds or minutes required for DL-PRS and UL-PRS configuration). The MO-LR request may also include RSRP measurements of the DL signals received by the UE (e.g., per beam) (e.g., E-CID location measurement report) to assist the LMF in determining the beam orientation of nearby gNBs and / or PRS.

[0154] In an embodiment, UE 105 may be configured to send an RRC-specific SIB request message to the serving gNB to request on-demand DL-PRS transmission and UL-PRS configuration. This request may include parameters for the UE's DL-PRS and UL-PRS capabilities and preferred DL-PRS and UL-PRS configurations as described above. The RRC-specific SIB request message may also include the duration for which the requested PRS configuration is required at UE 105 (e.g., the number of seconds or minutes required for DL-PRS and UL-PRS configuration). The RRC-specific SIB request message may also include RSRP measurements (e.g., per beam) of the DL signals received by UE 105 (e.g., RRC measurement reports) to assist LMF 120 in determining the beam orientation of the nearby gNB and / or PRS.

[0155] In phase 1404, the method includes receiving uplink configuration parameters based on uplink positioning reference signal configuration information. UE 200 is the component used to receive the UL-PRS configuration parameters. In one example, the serving gNB of UE 200 can provide the UL-PRS configuration parameters to UE 105 in a Radio Resource Control (RRC) message. In another example, LMF 120 can be configured to send an LPP Provide Auxiliary Data Message to UE 200 to provide the UL-PRS configuration parameters. In yet another example, LMF 120 can be configured to send an NRPPa Auxiliary Information Control Message to the serving gNB of UE 200 to provide the UL-PRS configuration parameters. The UL-PRS configuration parameters can be provided in the form of posSIB (i.e., using parameters and encoding defined for broadcast auxiliary data). The serving gNB can provide the UL-PRS configuration parameters to UE 200 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery can consist of an octet string containing the UL-PRS configuration parameters.

[0156] In phase 1406, the method includes transmitting one or more uplink positioning reference signals based on uplink positioning reference signal configuration information provided in phase 1402 and received in phase 1404. UE 200 is the component used to transmit UL-PRS. In the example, the serving gNB may send a MAC CE (or other encapsulated or unencapsulated information elements provided in Layer 1 (i.e., the physical layer) or Layer 2 (i.e., the MAC layer) to UE 105 to activate UL-PRS. UE 200 is configured to transmit UL-PRS based on the MAC-CE.

[0157] In phase 1408, the method includes receiving first auxiliary data based on downlink positioning reference signal configuration information and one or more uplink positioning reference signals. UE 200 is a component for receiving the first auxiliary data. In one embodiment, LMF 120 is configured to send an LPP Provide Auxiliary Data message to UE 200 to provide DL-PRS configuration based on DL-PRS configuration information provided in phase 1402. In another embodiment, LMF 120 may be configured to send an NRPPa Auxiliary Information Control message to the serving gNB to provide DL-PRS configuration based on DL-PRS configuration information provided in phase 1402. The DL-PRS configuration information may be provided in posSIB format (i.e., using parameters and encoding defined for broadcast auxiliary data). In an example, the serving gNB may provide the DL-PRS configuration information to the UE in a dedicated (unicast) RRC reconfiguration message. dedicatedPosSysInfoDelivery may consist of an octet string containing the DL-PRS configuration in posSIB format.

[0158] In phase 1410, the method includes measuring one or more downlink positioning reference signals (DL-PRSs) at least in part based on positioning reference signal configuration information. UE 200 is a component for measuring one or more DL-PRSs. UE 200 is configured to acquire and measure DL-PRS transmitted by gNB 110a-110c according to the DL-PRS configuration provided in the auxiliary data received in phase 1408. For example, but not limited to, UE 200 can obtain a measurement of the time difference between UE reception (Rx) and transmission (Tx) based on DL-PRS reception and UL-PRS transmission. UE 200 can be configured to obtain other measurements based on DL-PRS and / or UL-PRS transmissions.

[0159] In phase 1412, the method includes receiving second auxiliary data based on one or more uplink positioning reference signal measurements. UE 200 is the component for receiving the second auxiliary data. In the example, LMF 120 is also configured to forward UL-PRS measurements received from the base station as second auxiliary data (i.e., based on the UL-PRS sent by UE 200 in phase 1406) to UE 200 in an LPP Provide Auxiliary Data message. The UL-PRS measurement may be a gNB Rx-Tx time difference measurement.

[0160] In phase 1414, the method includes determining location based at least in part on measurements obtained from one or more downlink positioning reference signals and uplink positioning reference signal measurements. UE 200 is an example component for determining location. UE 200 is configured to determine location based on DL-PRS measurements obtained in phase 1206 and UL-PRS measurements and auxiliary data received in phase 1412. For example, UE 200 may utilize UE Rx-Tx time difference measurements and gNB Rx-Tx time difference measurements to determine the distances to multiple gNBs, and the locations of the gNBs, to determine the current location using multi-RTT positioning techniques. Other known positioning techniques such as OTDOA, AoD, and ECID may also be used to determine the location of UE 200.

[0161] refer to Figure 15 And further reference Figures 1 to 11B Method 1500 for providing auxiliary data for on-demand downlink positioning reference signals and uplink positioning reference signals includes the stages shown. However, method 1500 is an example and not a limitation. For example, method 1500 can be modified by adding, removing, rearranging, combining, performing stages simultaneously, and / or dividing a single stage into multiple stages. Method 1500 can be provided by a server or location server (e.g., Figure 1 LMF 120 or Figure 4 The server in the middle (400) is used to execute.

[0162] At stage 1502, the method includes receiving requests for downlink positioning reference signals and uplink positioning reference signals, wherein the requests include downlink positioning reference signal configuration information and uplink positioning reference signal configuration information. Server 400, such as LMF 120, is a component for receiving DL-PRS and UL-PRS requests. In an embodiment, UE 200 may be configured to send an MO-LR request message, including a UL NAS TRANSPORT message, to serving AMF 115, which includes a request for increased DL-PRS transmission and UL-PRS configuration information. This request may include configuration information such as the UE 200's DL-PRS and UL-PRS capabilities and parameters for preferred DL-PRS and UL-PRS configurations (e.g., preferred DL-PRS bandwidth, preferred duration of DL-PRS positioning timing, preferred DL-PRS beam direction, and preferred number of nearby gNBs, etc.). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP request auxiliary data message included in the MO-LR request. In the example, the request for increased DL-PRS transmission may also include Quality of Service (QoS) indicators, such as the required accuracy of location estimation and / or an indication of when the internal client needs the response time for location estimation. The MO-LR request message may also include the duration for which the requested PRS configuration is required at UE200. The MO-LR request may also include RSRP measurements (e.g., per beam) of the DL signal received by UE200 (e.g., E-CID location measurement report) to assist LMF 120 in determining the beam direction of nearby gNBs and / or DL-PRS. AMF 115 may invoke the Nlmf_Location_DetermineLocation service operation to LMF 120. The service operation may include the MO-LR request received from UE200.

[0163] In this embodiment, the serving gNB 110a is configured to send an NRPPa auxiliary information feedback message to the LMF 120. This message may include DL-PRS and UL-PRS configuration information received by gNB 110a from UE 105 via an RRC dedicated SIB request.

[0164] In phase 1504, the method includes determining one or more base stations providing downlink positioning reference signals based on downlink positioning reference signal configuration information. Server 400 is a component for determining one or more base stations. In an embodiment, LMF 120 may be configured to determine a new DL-PRS configuration for a nearby base station (e.g., gNB) based at least in part on configuration information. For example, the new DL-PRS configuration for each base station may use increased DL-PRS bandwidth, longer-duration DL-PRS positioning timing, DL-PRS transmission on a new frequency, and / or higher-frequency DL-PRS positioning timing. In the example, the new DL-PRS configuration may be selected from one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in positioning frequency layer 700. In a network with beamforming DL-PRS, LMF 120 may determine the directional DL-PRS beams that should be received by UE 105 for each base station. The directional DL-PRS beam can be selected by the LMF 120 based on the known approximate location of the target UE 105, such as by the coverage area of ​​the serving or camped cell of the UE 105 and / or by the RSRP / ECID measurements provided in the DL-PRS request received in phase 1502.

[0165] In phase 1506, the method includes requesting uplink positioning reference signal configuration information based on a UL-PRS request received from at least one of one or more base stations in phase 1502. Server 400 is a component for requesting the UL-PRS configuration information. In the example, LMF 120 is configured to send an NRPPa measurement request message to at least one of the one or more base stations determined in phase 1504 to request UL-PRS measurements (e.g., gNB Rx-Tx time difference measurements).

[0166] In phase 1508, the method includes providing downlink positioning reference signal configuration information to one or more base stations. Server 400 is a component for providing DL-PRS configuration information. In the example, LMF 120 is configured to send an NRPPa PRS configuration request message to each of the base stations determined in phase 1504, the message including a new DL-PRS configuration determined for that base station. The request may also include the start time and duration of each new DL-PRS configuration (e.g., provided in a request received in phase 1502, or determined by LMF 120).

[0167] In phase 1510, the method includes receiving uplink positioning reference signal measurement information from one or more base stations (e.g., from one or more base stations determined in phase 1504). Server 400 is a component for receiving UL-PRS measurements. Base stations (e.g., gNB 110a-110c) are configured to acquire and measure UL-PRS transmitted by UE 200. In the example, LMF 120 can determine the start time for switching to a new DL-PRS configuration and activating UL-PRS transmission. Base stations are configured to provide the obtained UL-PRS measurements to LMF 120.

[0168] In phase 1512, the method includes transmitting auxiliary data based on downlink positioning reference signal configuration information and uplink positioning reference signal measurement information. Server 400 is a component for transmitting (e.g., transporting) the auxiliary data. In an embodiment, LMF 120 may be configured to send an LPP Provide Auxiliary Data Message to target UE 105 to provide a new DL-PRS configuration. LMF 120 is also configured to forward the UL-PRS measurements from phase 1510 to target UE 105 in the LPP Provide Auxiliary Data Message.

[0169] In another embodiment, LMF 120 can be configured to send an NRPPa auxiliary information control message to the serving base station to provide a new DL-PRS configuration. The DL-PRS configuration information can be provided in posSIB format (i.e., using parameters and encoding defined for broadcast auxiliary data). The serving base station can be configured to provide the DL-PRS configuration information to UE 105 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery can consist of an octet string containing the received DL-PRS configuration in posSIB format. LMF 120 can also forward the UL-PRS measurement of phase 1510 to the target UE 105 in an LPP provide auxiliary data message.

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

[0171] Unless otherwise stated, the functional or other components shown in the accompanying drawings and / or discussed herein that are interconnected or communicating with each other are communicatively coupled. That is, they may be directly or indirectly connected to enable communication between them.

[0172] Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” as used herein also include the plural forms. For example, “processor” can include one or more processors. The terms “comprising” and / or “including” as used herein specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or combinations thereof.

[0173] Unless otherwise stated, a statement that a function or operation is “based on” an item or condition as used herein means that the function or operation is based on the stated item or condition and may be based on one or more items and / or conditions other than the stated item or condition.

[0174] Furthermore, as used herein, the "or" signifies a separate list in a list of items (which may begin with "at least one" or "one or more"), such that a list of, for example, "at least one of A, B, or C," or a list of "one or more of A, B, or C," or a list of "A, B, or C" means A, B, C, AB (A and B), AC (A and C), BC (B and C), ABC (i.e., A and B and C), or a combination having more than one characteristic (e.g., AA, AAB, ABBC, etc.). Therefore, a statement that an item (e.g., a processor) is configured to perform a function relating to at least one of A or B, or a statement that an item is configured to perform function A or function B, means that the item can be configured to perform a function relating to A, or can be configured to perform a function relating to B, or can be configured to perform functions relating to both A and B. For example, the phrase "a processor configured to measure at least one of A or B" or "a processor configured to measure A or measure B" means that the processor can be configured to measure A (and can be configured to measure B or not measure B), or can be configured to measure B (and can be configured to measure A or not measure A), or can be configured to measure both A and B (and can be configured to select which one or both of A and B to measure). Similarly, a description of a component for measuring at least one of A or B includes a component for measuring A (which can measure B or not measure B), or a component for measuring B (and can be configured to measure A or not measure A), or a component for measuring A and B (which can select which one or both of A and B to measure). As another example, a description of an item (e.g., a processor) being configured to perform at least one of function X or function Y means that the item can be configured to perform function X, or can be configured to perform function Y, or can be configured to perform both functions X and Y. For example, the phrase "a processor configured to measure at least one of X or Y" means that the processor can be configured to measure X (and can be configured to measure Y or not measure Y), or can be configured to measure Y (and can be configured to measure X or not measure X), or can be configured to measure both X and Y (and can be configured to select which one or both of X and Y to measure). Substantial changes can be made depending on specific requirements. For example, custom hardware may also be used, and / or specific components may be implemented in the hardware, the software executed by the processor (including portable software such as applets), or both. Furthermore, connectivity to other computing devices, such as network input / output devices, may be used.

[0175] The systems and devices discussed above are examples. Various operations may be appropriately omitted, substituted, or added to various processes or components. For example, features described with respect to certain configurations may be combined in various other configurations. Different aspects and elements of a configuration may be combined in a similar manner. Furthermore, technology is evolving, therefore many elements are illustrative, and these elements do not limit the scope of this disclosure or the claims.

[0176] A wireless communication system is a system that transmits communication wirelessly, that is, through electromagnetic waves and / or sound waves propagating in atmospheric space, rather than through wired or other physical connections. A wireless communication network may not transmit all communications wirelessly, but is configured to transmit at least some communications wirelessly. Furthermore, the term "wireless communication device" or similar terms do not require that the device's function is specifically or even primarily for communication, or that the device is a mobile device, but rather indicate that the device includes wireless communication capabilities (one-way or two-way), for example, including at least one radio component for wireless communication (each radio component is part of a transmitter, receiver, or transceiver).

[0177] Specific details are provided in the description to offer a comprehensive understanding of the example configurations, including implementations. However, configurations may be implemented without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring these configurations. This description provides example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the foregoing description of the configurations provides a description of the techniques described for implementation. Various changes may be made to the function and arrangement of the elements without departing from the scope of this disclosure.

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

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

Claims

1. A method for determining the location of a mobile device, comprising: The mobile device sends a request for a downlink positioning reference signal to the network server, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Auxiliary data is received at least in part based on the on-demand positioning reference signal configuration information; as well as The location is determined at least in part based on measurements obtained from one or more downlink positioning reference signals associated with the on-demand positioning reference signal and the auxiliary data.

2. The method of claim 1, wherein the request for the downlink positioning reference signal is a Mobile Initiated Location Request (MO-LR).

3. The method of claim 1, wherein the request for the downlink positioning reference signal is a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request.

4. The method of claim 1, wherein the positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

5. The method of claim 1, further comprising receiving a Mobile Initiated Location Request (MO-LR) response message indicating the start time and duration of the one or more downlink positioning reference signals.

6. The method of claim 1, wherein receiving the auxiliary data includes receiving a Radio Resource Control (RRC) reconfiguration message.

7. The method of claim 1, wherein receiving the auxiliary data includes receiving an LPP-provided auxiliary data message.

8. The method of claim 7, wherein the LPP provides auxiliary data messages including the start time and duration of the one or more downlink positioning reference signals.

9. The method of claim 1, wherein the positioning reference signal configuration information is associated with one or more positioning reference signal resources in the positioning frequency layer.

10. A method for providing location information to a mobile device, comprising: The mobile device receives a request for a downlink positioning reference signal, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; The one or more base stations providing the downlink positioning reference signal are determined at least in part based on the on-demand positioning reference signal configuration information; Provide the on-demand positioning reference signal configuration information to the one or more base stations; as well as Auxiliary data is provided, at least in part, based on the on-demand positioning reference signal configuration information.

11. The method of claim 10, wherein the request for the downlink positioning reference signal is based on a Mobile Initiated Location Request (MO-LR) received by the network server.

12. The method of claim 10, wherein the request for the downlink positioning reference signal is based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by the network base station.

13. The method of claim 10, wherein the positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and an RSRP measurement of the downlink signal received by the mobile device.

14. The method of claim 10, further comprising providing a response message indicating the start time and duration of the one or more downlink positioning reference signals.

15. The method of claim 10, wherein determining one or more base stations providing the downlink positioning reference signal comprises selecting one or more positioning reference signal resources from the positioning frequency layer.

16. The method of claim 10, wherein determining one or more base stations providing the downlink positioning reference signal comprises selecting one or more downlink positioning reference signal beams based on the approximate location of the mobile device.

17. The method of claim 16, wherein the approximate location of the mobile device is based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device.

18. The method of claim 10, wherein providing the auxiliary data comprises sending an LPP (Assisted Data Provision) message to the mobile device.

19. The method of claim 18, wherein the LPP provides auxiliary data messages including the start time and duration of the one or more downlink positioning reference signals.

20. The method of claim 10, wherein providing the auxiliary data includes sending an NRPPa auxiliary information control message to the serving base station of the mobile device.

21. The method of claim 20, wherein the NRPPa auxiliary information control message includes the start time and duration of the one or more downlink positioning reference signals.

22. A method for determining the location of a mobile device, comprising: The mobile device sends a request for downlink positioning reference signals and uplink positioning reference signals to the network server, wherein the request includes on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, and the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information include at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; The uplink configuration parameters are received based on the uplink positioning reference signal configuration information. One or more uplink positioning reference signals are sent based on the uplink positioning reference signal configuration information; The first auxiliary data is received at least in part based on the downlink positioning reference signal configuration information; The second auxiliary data is received based on the measurement of one or more uplink positioning reference signals; as well as The location is determined at least in part based on measurements obtained from one or more downlink positioning reference signals associated with the on-demand downlink positioning reference signal and the uplink positioning reference signal measurements.

23. The method of claim 22, wherein the request for the downlink positioning reference signal and the uplink positioning reference signal is a Mobile Initiated Location Request (MO-LR).

24. The method of claim 22, wherein the request for the downlink positioning reference signal and the uplink positioning reference signal is a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request.

25. The method of claim 22, wherein the downlink positioning reference signal configuration information or the uplink positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal and uplink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

26. The method of claim 22, further comprising receiving a Mobile Initiated Location Request (MO-LR) response message indicating the start time and duration of the one or more downlink positioning reference signals.

27. The method of claim 22, wherein receiving the uplink configuration parameters includes receiving a radio resource control (RRC) message including the uplink configuration parameters.

28. The method of claim 22, further comprising receiving an uplink activation message, wherein sending the one or more uplink positioning reference signals is in response to receiving the uplink activation message.

29. The method of claim 22, wherein the uplink activation message is a Media Access Control Element (MAC-CE).

30. The method of claim 22, wherein the uplink positioning reference signal measurement is a gNB Rx-Tx time difference measurement.

31. The method of claim 22, wherein receiving the first auxiliary data includes receiving a Radio Resource Control (RRC) reconfiguration message.

32. The method of claim 22, wherein receiving the first auxiliary data includes receiving an LPP-provided auxiliary data message.

33. The method of claim 32, wherein the LPP provides auxiliary data messages including the start time and duration of the one or more downlink positioning reference signals.

34. The method of claim 22, wherein receiving the second auxiliary data includes receiving an LPP-provided auxiliary data message.

35. The method of claim 22, wherein the downlink positioning reference signal configuration information is associated with one or more positioning reference signal resources in the positioning frequency layer.

36. A method for providing location information to a mobile device, comprising: The mobile device receives requests for downlink positioning reference signals and uplink positioning reference signals, wherein the requests include on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; The one or more base stations providing downlink positioning reference signals are determined at least in part based on the on-demand downlink positioning reference signal configuration information; Request uplink positioning reference signal configuration information from at least one of the one or more base stations; Provide the on-demand downlink positioning reference signal configuration information to the one or more base stations; Receive uplink positioning reference signal measurement information from the one or more base stations; as well as Auxiliary data is transmitted based at least in part on the on-demand downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

37. The method of claim 36, wherein the request for the downlink positioning reference signal is based on a Mobile Initiated Location Request (MO-LR) received by the network server.

38. The method of claim 36, wherein the request for the downlink positioning reference signal is based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by the network base station.

39. The method of claim 36, wherein the downlink positioning reference signal configuration information or the uplink positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal and uplink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

40. The method of claim 36, further comprising providing a response message indicating the start time and duration of the one or more downlink positioning reference signals.

41. The method of claim 36, wherein determining one or more base stations providing the downlink positioning reference signal comprises selecting one or more positioning reference signal resources from the positioning frequency layer.

42. The method of claim 36, wherein determining one or more base stations providing the downlink positioning reference signal comprises selecting one or more downlink positioning reference signal beams based on the approximate location of the mobile device.

43. The method of claim 42, wherein the approximate location of the mobile device is based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device.

44. The method of claim 36, wherein providing the auxiliary data comprises sending an LPP (Assisted Data Provision) message to the mobile device.

45. The method of claim 36, wherein providing the auxiliary data includes sending an NRPPa auxiliary information control message to the serving base station of the mobile device.

46. ​​A mobile device, comprising: Memory; At least one transceiver; At least one processor, communicatively coupled to the memory and the at least one transceiver, is configured to: A request for a downlink location reference signal is sent from at least one transceiver of the mobile device to a network server, wherein the request includes on-demand location reference signal configuration information, the on-demand location reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Auxiliary data is received via the at least one transceiver based on the positioning reference signal configuration information; as well as Location information is determined at least in part based on measurements obtained from one or more downlink positioning reference signals associated with the on-demand positioning reference signal and the auxiliary data.

47. The mobile device of claim 46, wherein the request for the downlink positioning reference signal is a Mobile Initiated Location Request (MO-LR).

48. The mobile device of claim 46, wherein the request for the downlink positioning reference signal is a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request.

49. The mobile device of claim 46, wherein the positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

50. The mobile device of claim 46, wherein the at least one processor is further configured to receive a Mobile Initiated Location Request (MO-LR) response message indicating the start time and duration of the one or more downlink positioning reference signals.

51. The mobile device of claim 46, wherein the at least one processor is configured to receive a Radio Resource Control (RRC) reconfiguration message.

52. The mobile device of claim 46, wherein the at least one processor is configured to receive an LPP-provided auxiliary data message.

53. The mobile device of claim 46, wherein the positioning reference signal configuration information is associated with one or more positioning reference signal resources in the positioning frequency layer.

54. An apparatus comprising: Memory; At least one transceiver; At least one processor, communicatively coupled to the memory and the at least one transceiver, is configured to: Receive a request for a downlink positioning reference signal from a mobile device via the at least one transceiver, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; The one or more base stations providing the downlink positioning reference signal are determined at least in part based on the on-demand positioning reference signal configuration information; Provide the on-demand positioning reference signal configuration information to the one or more base stations; as well as Auxiliary data is provided, at least in part, based on the on-demand positioning reference signal configuration information.

55. The apparatus of claim 54, wherein the request for the downlink positioning reference signal is based on a Mobile Initiated Location Request (MO-LR) received by the network server.

56. The apparatus of claim 54, wherein the request for the downlink positioning reference signal is based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by the network base station.

57. The apparatus of claim 54, wherein the positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal, and an RSRP measurement of the downlink signal received by the mobile device.

58. The apparatus of claim 54, wherein the at least one processor is further configured to provide a response message indicating the start time and duration of the one or more downlink positioning reference signals.

59. The apparatus of claim 54, wherein the at least one processor is further configured to select one or more positioning reference signal resources from the positioning frequency layer.

60. The apparatus of claim 54, wherein the at least one processor is further configured to select one or more downlink positioning reference signal beams based on the approximate location of the mobile device.

61. The apparatus of claim 60, wherein the approximate location of the mobile device is based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device.

62. The apparatus of claim 54, wherein the at least one processor is further configured to send an LPP (Limited Power Providing Assistance) data message to the mobile device.

63. The apparatus of claim 54, wherein the at least one processor is further configured to send an NRPPa auxiliary information control message to the serving base station of the mobile device.

64. A mobile device, comprising: Memory; At least one transceiver; At least one processor, communicatively coupled to the memory and the at least one transceiver, is configured to: The device sends a request for downlink positioning reference signal and uplink positioning reference signal to the network server of the mobile device via the at least one transceiver. The request includes on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, which includes at least one of the following: the start time of the on-demand positioning reference signal or the duration of the on-demand positioning reference signal. The uplink configuration parameters are received via the at least one transceiver based on the uplink positioning reference signal configuration information; Send one or more uplink positioning reference signals; The first auxiliary data is received via the at least one transceiver based on the downlink positioning reference signal configuration information; Second auxiliary data is received via the at least one transceiver based on the one or more uplink positioning reference signals. as well as Location information is determined at least in part based on measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements associated with the on-demand downlink positioning reference signal.

65. The mobile device of claim 64, wherein the request for the downlink positioning reference signal and the uplink positioning reference signal is a Mobile Initiated Location Request (MO-LR).

66. The mobile device of claim 64, wherein the request for the downlink positioning reference signal and the uplink positioning reference signal is a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request.

67. The mobile device of claim 64, wherein the downlink positioning reference signal configuration information or the uplink positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal and uplink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

68. The mobile device of claim 64, wherein the at least one processor is further configured to receive a Mobile Initiated Location Request (MO-LR) response message indicating the start time and duration of the one or more downlink positioning reference signals.

69. The mobile device of claim 64, wherein the at least one processor is further configured to receive a radio resource control (RRC) message including the uplink configuration parameters.

70. The mobile device of claim 64, wherein the at least one processor is further configured to receive an uplink activation message and, in response to receiving the uplink activation message, to send the one or more uplink positioning reference signals.

71. The mobile device of claim 70, wherein the uplink activation message is a Media Access Control Element (MAC-CE).

72. The mobile device of claim 64, wherein the uplink positioning reference signal measurement is a gNB Rx-Tx time difference measurement.

73. The mobile device of claim 64, wherein the at least one processor is further configured to receive a Radio Resource Control (RRC) reconfiguration message.

74. The mobile device of claim 64, wherein the at least one processor is further configured to receive an LPP-provided auxiliary data message.

75. The mobile device of claim 64, wherein the downlink positioning reference signal configuration information is associated with one or more positioning reference signal resources in the positioning frequency layer.

76. An apparatus comprising: Memory; At least one transceiver; At least one processor, communicatively coupled to the memory and the at least one transceiver, is configured to: The device receives requests for on-demand downlink positioning reference signals and uplink positioning reference signals from the mobile device via the at least one transceiver. The requests include on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, wherein the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information include at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; The one or more base stations providing downlink positioning reference signals are determined at least in part based on the on-demand downlink positioning reference signal configuration information; Request uplink positioning reference signal configuration information from at least one of the one or more base stations; Provide the on-demand downlink positioning reference signal configuration information to the one or more base stations; Receive uplink positioning reference signal measurement information from one or more base stations via the at least one transceiver; as well as Auxiliary data is transmitted, at least in part, via the at least one transceiver based on the on-demand downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

77. The apparatus of claim 76, wherein the request for the downlink positioning reference signal is based on a Mobile Initiated Location Request (MO-LR) received by the network server.

78. The apparatus of claim 76, wherein the request for the downlink positioning reference signal is based on a Radio Resource Control (RRC) Dedicated System Information Block (SIB) request received by the network base station.

79. The apparatus of claim 76, wherein the downlink positioning reference signal configuration information or the uplink positioning reference signal configuration information includes at least one of a quality of service indicator, a duration indicating how long the mobile device needs the requested downlink positioning reference signal and uplink positioning reference signal, and a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device.

80. The apparatus of claim 76, wherein the at least one processor is further configured to provide a response message indicating the start time and duration of the one or more downlink positioning reference signals.

81. The apparatus of claim 76, wherein the at least one processor is further configured to select one or more positioning reference signal resources from the positioning frequency layer.

82. The apparatus of claim 76, wherein the at least one processor is further configured to select one or more downlink positioning reference signal beams based on the approximate location of the mobile device.

83. The apparatus of claim 82, wherein the approximate location of the mobile device is based on at least one of the coverage area of ​​the serving cell of the mobile device, a reference signal received power (RSRP) measurement of the downlink signal received by the mobile device, and an enhanced cell identifier (ECID) measurement of the downlink signal received by the mobile device.

84. The apparatus of claim 76, wherein the at least one processor is further configured to send an LPP (Limited Power Providing Assistance) data message to the mobile device.

85. The apparatus of claim 76, wherein the at least one processor is further configured to send an NRPPa auxiliary information control message to the serving base station of the mobile device.

86. A mobile device for determining the location of a mobile device, comprising: A component for sending a request for a downlink positioning reference signal from the mobile device to a network server, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; A component used at least in part to receive auxiliary data based on the on-demand positioning reference signal configuration information; as well as A component for determining the location based at least in part on measurements obtained from one or more downlink positioning reference signals associated with the on-demand positioning reference signal and the auxiliary data.

87. An apparatus for providing location information to a mobile device, comprising: A component for receiving a request for a downlink positioning reference signal from the mobile device, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; At least in part, it is used to determine, based on the on-demand positioning reference signal configuration information, one or more base stations providing the downlink positioning reference signal; Components for providing the on-demand positioning reference signal configuration information to the one or more base stations; as well as A component used at least in part to provide auxiliary data based on the on-demand positioning reference signal configuration information.

88. An apparatus for determining the location of a mobile device, comprising: A component for sending a request from the mobile device to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; A component for receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; A component used to transmit one or more uplink positioning reference signals; Components for receiving first auxiliary data based at least in part on the downlink positioning reference signal configuration information; Components for receiving second auxiliary data based on the one or more uplink positioning reference signal measurements; as well as A component for determining the location based at least in part on measurements obtained from one or more downlink positioning reference signals associated with the on-demand downlink positioning reference signal and the uplink positioning reference signal measurements.

89. An apparatus for providing location information to a mobile device, comprising: A component for receiving requests for downlink positioning reference signals and uplink positioning reference signals from the mobile device, wherein the requests include on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Components for determining one or more base stations providing downlink positioning reference signals based at least in part on the on-demand downlink positioning reference signal configuration information; A component for requesting uplink positioning reference signal configuration information from at least one of the one or more base stations; Components for providing the on-demand downlink positioning reference signal configuration information to the one or more base stations; Components for receiving uplink positioning reference signal measurement information from the one or more base stations; as well as A component for transmitting auxiliary data, at least in part, based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information as needed.

90. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors to determine the location of a mobile device, comprising: Code for sending a request for a downlink positioning reference signal from the mobile device to a network server, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: the start time of the on-demand positioning reference signal, or the duration of the on-demand positioning reference signal; Code for receiving auxiliary data based at least in part on the on-demand positioning reference signal configuration information; as well as Code for determining the location information based at least in part on measurements obtained from one or more downlink positioning reference signals associated with the on-demand positioning reference signal and the auxiliary data.

91. A non-transitory processor-readable storage medium comprising processor-readable instructions configured to cause one or more processors to provide location information to a mobile device, comprising: Code for receiving a request for a downlink positioning reference signal from the mobile device, wherein the request includes on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Code for determining one or more base stations providing the downlink positioning reference signal, based at least in part on the on-demand positioning reference signal configuration information; Code used to provide the on-demand positioning reference signal configuration information to the one or more base stations; as well as Code for providing auxiliary data based at least in part on the on-demand positioning reference signal configuration information.

92. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors to determine the location of a mobile device, comprising: Code for sending a request from the mobile device to a network server for downlink positioning reference signals and uplink positioning reference signals, wherein the request includes on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Code for receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; Code used to send one or more uplink positioning reference signals; Code for receiving first auxiliary data based at least in part on the downlink positioning reference signal configuration information; Code for receiving second auxiliary data based on the one or more uplink positioning reference signal measurements; as well as Code for determining the location based at least in part on measurements obtained from one or more downlink positioning reference signals associated with the on-demand downlink positioning reference signal and the uplink positioning reference signal measurements.

93. A non-transitory processor-readable storage medium comprising processor-readable instructions configured to cause one or more processors to provide location information to a mobile device, comprising: Code for receiving requests for downlink positioning reference signals and uplink positioning reference signals from the mobile device, wherein the requests include on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information including at least one of the following: The start time of the reference signal is determined on demand, or The duration of the reference signal is determined on demand; Code for determining one or more base stations providing downlink positioning reference signals based at least in part on the on-demand downlink positioning reference signal configuration information; Code for requesting uplink positioning reference signal configuration information from at least one of the one or more base stations; Code for providing the on-demand downlink positioning reference signal configuration information to the one or more base stations; Code for receiving uplink positioning reference signal measurement information from the one or more base stations; as well as Code for transmitting auxiliary data based at least in part on the on-demand downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

Images