Systems and methods for on-demand positioning reference signal support in wireless networks

Abstract

Techniques are provided for enabling on-demand positioning reference signals (PRS) for user equipment (UE). An exemplary method for determining a position of a mobile device includes sending a request for downlink positioning reference signals to a network server, the request including positioning reference signal configuration information, receiving assistance data based on the positioning reference signal configuration information, measuring one or more downlink positioning reference signals based at least in part on the positioning reference signal configuration information, and determining a position of the mobile device based at least in part on the measurements and the assistance data obtained from the one or more downlink positioning reference signals.

Description

[Background technology]

[0001] Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax), and fifth-generation (5G) service (e.g., 5G New Radio (NR)). Many different types of wireless communication systems are currently in use, including cellular systems and personal communications services (PCS) systems. Examples of known cellular systems include the Cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile access (GSM) variant of TDMA, and the like. Summary of the Invention [Problem to be solved by the invention]

[0002] Obtaining the location (also called "place") of a mobile device accessing a wireless network can be useful for many applications, including, for example, emergency calling, personal navigation, consumer asset management, locating friends or family, etc. Existing positioning methods include methods based on measuring radio signals transmitted from various devices, including spacecraft and terrestrial radio sources in the wireless network, such as base stations and access points. Base stations in the wireless network can be configured to transmit reference signals to enable mobile devices to perform positioning measurements. Improvements in positioning-related signaling can improve the accuracy, latency, and / or efficiency of mobile device location determination. [Means for solving the problem]

[0003] An exemplary method for determining a location of a mobile device according to the present disclosure includes sending a request for downlink positioning reference signals to a network server, the request including positioning reference signal configuration information; receiving assistance data based on the positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the positioning reference signal configuration information; and determining a location based at least in part on the measurement results and assistance 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 the downlink positioning reference signal may be a Mobile-Originated Location Request (MO-LR). The request for the 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 time length indicating how long the requested downlink positioning reference signal is needed by the mobile device, and a Reference Signal Received Power (RSRP) measurement result of the downlink signal received by the mobile device. A Mobile-Originated Location Request (MO-LR) Response message may be received indicating a start time and a time length for the one or more downlink positioning reference signals. Receiving assistance data may include receiving a Radio Resource Control (RRC) Reconfiguration message. Receiving assistance data may include receiving an LPP Provide Assistance Data message. The positioning reference signal configuration information may be associated with one or more positioning reference signal resources in a positioning frequency layer.

[0005] An exemplary method for providing location information to a mobile device according to the present disclosure includes receiving a request for a downlink positioning reference signal, the request including positioning reference signal configuration information; determining one or more base stations for 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 assistance data based on the positioning reference signal configuration information.

[0006] Implementations of such a method may include one or more of the following features: The request for the downlink positioning reference signal may be based on a mobile-originated positioning request (MO-LR) received by a network server. The request for the downlink positioning reference signal may be based on a radio resource control (RRC) dedicated system information block (SIB) request received by a network base station. The positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink positioning reference signal is needed by the mobile device, and RSRP measurement results of the downlink signal received by the mobile device. A response message indicating a start time and a time length for the one or more downlink positioning reference signals may be provided. Determining one or more base stations to provide the downlink positioning reference signal may include selecting one or more positioning reference signal resources from a positioning frequency layer. Determining one or more base stations to provide the downlink positioning reference signal may include selecting one or more downlink positioning reference signal beams based on a coarse location of the mobile device. The coarse location of the mobile device may be based on at least one of a coverage area of ​​a serving cell for the mobile device, a Reference Signal Received Power (RSRP) measurement of a downlink signal received by the mobile device, and an Enhanced Cell Identification (ECID) measurement of a downlink signal received by the mobile device. Providing assistance data may include transmitting an LPP Provide Assistance Data message to the mobile device. Providing assistance data may include transmitting an NRPPa Assistance Information Control message to a serving base station for the mobile device.

[0007] An exemplary method for determining a location of a mobile device according to the present disclosure includes the steps of: sending a request for downlink and uplink positioning reference signals to a network server, the request including 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; receiving first assistance data based on the downlink positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the downlink positioning reference signal configuration information; receiving second assistance data based on one or more uplink positioning reference signal measurement results; and determining a location based at least in part on measurement results obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurement results.

[0008] Implementations of such a method may include one or more of the following features: The request for the downlink and uplink positioning reference signals may be a mobile-originated positioning request (MO-LR). The request for the downlink and uplink positioning reference signals may be a radio resource control (RRC) dedicated system information block (SIB) request. The downlink or uplink positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink and uplink positioning reference signals are needed by the mobile device, and a reference signal received power (RSRP) measurement result of the downlink signal received by the mobile device. A mobile-originated positioning request (MO-LR) response message may be received indicating a start time and a time length for the one or more downlink positioning reference signals. Receiving the uplink configuration parameters may include receiving a radio resource control (RRC) message including the uplink configuration parameters. An uplink enablement message may be received, whereby transmitting the one or more uplink positioning reference signals is in response to receiving the uplink enablement message. The uplink activation message may be a Medium Access Control Element (MAC-CE) or other information element provided encapsulated or unencapsulated at Layer 1 (i.e., the physical layer) or Layer 2 (i.e., the MAC layer). The uplink positioning reference signal measurement result may be a gNB Rx-Tx time difference measurement result. The assistance data may be included in a Radio Resource Control (RRC) reconfiguration message. Receiving the second assistance data may include receiving an LPP Provide Assistance Data message. The downlink positioning reference signal configuration information may be associated with one or more positioning reference signal resources in a positioning frequency layer.

[0009] An exemplary method for providing location information to a mobile device according to the present disclosure includes receiving a request for downlink and uplink positioning reference signals, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; determining one or more base stations for providing the downlink positioning reference signals 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 assistance 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: The request for the downlink positioning reference signal may be based on a mobile-originated positioning request (MO-LR) received by a network server. The request for the downlink positioning reference signal may be based on a radio resource control (RRC) dedicated system information block (SIB) request received by a network base station. The downlink or uplink positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink and uplink positioning reference signals are needed by the mobile device, and a reference signal received power (RSRP) measurement result of the downlink signal received by the mobile device. A response message indicating a start time and a time length for the one or more downlink positioning reference signals may be provided. Determining one or more base stations to provide the downlink positioning reference signal may include selecting one or more positioning reference signal resources from a positioning frequency layer. Determining one or more base stations to provide the downlink positioning reference signal may include selecting one or more downlink positioning reference signal beams based on a coarse location of the mobile device. The coarse location of the mobile device may be based on at least one of a coverage area of ​​a serving cell for the mobile device, a Reference Signal Received Power (RSRP) measurement of a downlink signal received by the mobile device, and an Enhanced Cell Identity (ECID) measurement of a downlink signal received by the mobile device. Providing the assistance data may include transmitting an LPP Provide Assistance Data message to the mobile device. Providing the assistance data may include transmitting an NRPPa Assistance Information control message to a serving base station for the mobile device.

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

[0012] Implementations of such an apparatus may include one or more of the following features: The request for the downlink positioning reference signal may be a mobile-originated positioning request (MO-LR). The request for the 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 time length indicating how long the requested downlink positioning reference signal is needed by the mobile device, and a reference signal received power (RSRP) measurement result of the downlink signal received by the mobile device. The at least one processor may be further configured to receive a mobile-originated positioning request (MO-LR) response message indicating a start time and a time length for one or more downlink positioning reference signals. The at least one processor may be configured to receive a radio resource control (RRC) reconfiguration message. The at least one processor may be configured to receive an LPP assistance data provision message. The positioning reference signal configuration information may be associated with one or more positioning reference signal resources in a positioning frequency layer.

[0013] An example apparatus according to the present disclosure includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive, via the at least one transceiver, a request for a downlink positioning reference signal, the request including positioning reference signal configuration information, determine one or more base stations for 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 assistance data based on the positioning reference signal configuration information.

[0014] Implementations of such an apparatus may include one or more of the following features: The request for the downlink positioning reference signal may be based on a mobile-originated positioning request (MO-LR) received by a network server. The request for the downlink positioning reference signal may be based on a radio resource control (RRC) dedicated system information block (SIB) request received by a network base station. The positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink positioning reference signal is needed by the mobile device, and an RSRP measurement result of the downlink signal received by the mobile device. The at least one processor may be further configured to provide a response message indicating a start time and a time length for the one or more downlink positioning reference signals. The at least one processor may be further configured to select one or more positioning reference signal resources from a positioning frequency layer. The at least one processor may be further configured to select one or more downlink positioning reference signal beams based on a coarse location of the mobile device. The coarse location of the mobile device may be based on at least one of a coverage area of ​​a serving cell for the mobile device, a Reference Signal Received Power (RSRP) measurement of a downlink signal received by the mobile device, and an Enhanced Cell Identity (ECID) measurement of a downlink signal received by the mobile device. The at least one processor may be further configured to transmit an LPP assistance data provide message to the mobile device. The at least one processor may be further configured to transmit an NRPPa assistance information control message to a serving base station for the mobile device.

[0015] an at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to: send, via the at least one transceiver, a request for downlink and uplink positioning reference signals to a network server, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; receive, via the at least one transceiver, uplink configuration parameters based on the uplink positioning reference signal configuration information; transmit one or more uplink positioning reference signals; receive, via the at least one transceiver, first assistance data based on the downlink positioning reference signal configuration information; measure the one or more downlink positioning reference signals based at least in part on the downlink positioning reference signal configuration information; receive, via the at least one transceiver, second assistance data based on the one or more uplink positioning reference signal measurement results; and determine a position based at least in part on measurement results obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurement results.

[0016] Implementations of such an apparatus may include one or more of the following features: The request for the downlink and uplink positioning reference signals may be a mobile-originated positioning request (MO-LR). The request for the downlink and uplink positioning reference signals may be a radio resource control (RRC) dedicated system information block (SIB) request. The downlink or uplink positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink and uplink positioning reference signals are needed by the mobile device, and a reference signal received power (RSRP) measurement result of the downlink signal received by the mobile device. The at least one processor may be further configured to receive a mobile-originated positioning request (MO-LR) response message indicating a start time and a time length for one or more downlink positioning reference signals. The at least one processor may be further configured to receive a radio resource control (RRC) message including uplink configuration parameters. The at least one processor may be further configured to receive an uplink enablement message and to transmit one or more uplink positioning reference signals in response to receiving the uplink enablement message. The uplink activation message may be a medium access control (MAC-CE) control element or other information element provided encapsulated or unencapsulated at Layer 1 (i.e., the physical layer) or Layer 2 (i.e., the MAC layer). The uplink positioning reference signal measurement result may be a gNB Rx-Tx time difference measurement result. The at least one processor may be further configured to receive a radio resource control (RRC) reconfiguration message. The at least one processor may be further configured to receive an LPP assistance data provision message. The downlink positioning reference signal configuration information may be associated with one or more positioning reference signal resources in a positioning frequency layer.

[0017] An example apparatus according to the present disclosure includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to: receive, via the at least one transceiver, a request for downlink and uplink positioning reference signals, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; determine one or more base stations for providing the downlink positioning reference signals based on the 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 downlink positioning reference signal configuration information to the one or more base stations; receive, via the at least one transceiver, uplink positioning reference signal measurement information from the one or more base stations; and transmit, via the at least one transceiver, assistance data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0018] Implementations of such an apparatus may include one or more of the following features: The request for the downlink positioning reference signal may be based on a mobile-originated positioning request (MO-LR) received by a network server. The request for the downlink positioning reference signal may be based on a radio resource control (RRC) dedicated system information block (SIB) request received by a network base station. The downlink or uplink positioning reference signal configuration information may include at least one of a quality of service indicator, a time length indicating how long the requested downlink and uplink positioning reference signals are needed by the mobile device, and a reference signal received power (RSRP) measurement result of the downlink signal received by the mobile device. The at least one processor may be further configured to provide a response message indicating a start time and a time length for the one or more downlink positioning reference signals. The at least one processor may be further configured to select one or more positioning reference signal resources from a positioning frequency layer. The at least one processor may be further configured to select one or more downlink positioning reference signal beams based on a coarse location of the mobile device. The coarse location of the mobile device may be based on at least one of a coverage area of ​​a serving cell for the mobile device, a Reference Signal Received Power (RSRP) measurement of a downlink signal received by the mobile device, and an Enhanced Cell Identity (ECID) measurement of a downlink signal received by the mobile device. The at least one processor may be further configured to transmit an LPP assistance data provide message to the mobile device. The at least one processor may be further configured to transmit an NRPPa assistance information control message to a serving base station for the mobile device.

[0019] An exemplary apparatus for determining a position of a mobile device according to the present disclosure includes means for transmitting a request for downlink positioning reference signals to a network server, the request including positioning reference signal configuration information; means for receiving assistance data based on the positioning reference signal configuration information; means for measuring one or more downlink positioning reference signals based at least in part on the positioning reference signal configuration information; and means for determining a position based at least in part on the measurement results and the assistance data obtained from the one or more downlink positioning reference signals.

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

[0021] an exemplary apparatus for determining a position of a mobile device according to the present disclosure includes means for transmitting a request for downlink and uplink positioning reference signals to a network server, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; means for receiving uplink configuration parameters based on the uplink positioning reference signal configuration information; means for transmitting one or more uplink positioning reference signals; means for receiving first assistance data based on the downlink positioning reference signal configuration information; means for measuring one or more downlink positioning reference signals based at least in part on the downlink positioning reference signal configuration information; means for receiving second assistance data based on one or more uplink positioning reference signal measurement results; and means for determining a position based at least in part on measurement results obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurement results.

[0022] An exemplary apparatus for providing location information to a mobile device according to the present disclosure includes means for receiving a request for downlink and uplink positioning reference signals, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; means for determining one or more base stations for providing the downlink positioning reference signal based on the downlink positioning reference signal configuration information; means for requesting uplink positioning reference signal configuration information from at least one of the one or more base stations; means for providing the downlink positioning reference signal configuration information to the one or more base stations; means for receiving uplink positioning reference signal measurement information from the one or more base stations; and means for transmitting assistance data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0023] An exemplary non-transitory processor-readable storage medium comprising processor-readable instructions configured to cause one or more processors to determine a position of a mobile device in accordance with the present disclosure includes code for sending a request for downlink positioning reference signals to a network server, the request including positioning reference signal configuration information; code for receiving assistance data based on the positioning reference signal configuration information; code for measuring one or more downlink positioning reference signals based at least in part on the positioning reference signal configuration information; and code for determining a position based at least in part on measurements obtained from the one or more downlink positioning reference signals and the assistance data.

[0024] An exemplary 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 in accordance with the present disclosure includes code for receiving a request for a downlink positioning reference signal, the request including positioning reference signal configuration information; code for determining one or more base stations to provide 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 assistance data based on the positioning reference signal configuration information.

[0025] an exemplary non-transitory processor-readable storage medium comprising processor-readable instructions configured to cause one or more processors to determine a position of a mobile device in accordance with the present disclosure includes: code for sending a request for downlink and uplink positioning reference signals to a network server, the request including 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 transmitting one or more uplink positioning reference signals; code for receiving first assistance data based on the downlink positioning reference signal configuration information; code for measuring one or more downlink positioning reference signals based at least in part on the downlink positioning reference signal configuration information; code for receiving second assistance data based on one or more uplink positioning reference signal measurement results; and code for determining a position based at least in part on measurement results obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurement results.

[0026] An exemplary 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 in accordance with the present disclosure includes: code for receiving a request for downlink and uplink positioning reference signals, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information; code for determining one or more base stations to provide the downlink positioning reference signals based on the 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 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 assistance data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

[0027] The items and / or techniques described herein may provide one or more of the following capabilities, as well as other capabilities not mentioned: A mobile device may be configured to request a downlink positioning reference signal or provide an uplink positioning reference signal on demand. An on-demand request may enable a communication network to dynamically change positioning reference signal resource allocation. A Mobile-Originated Positioning Request (MO-LR) procedure or an On-Demand System Information (SI) Request procedure may be used by a mobile device to request a DL-PRS transmission on demand from the network or to request a UL-PRS configuration on demand. An on-demand positioning reference signal procedure may be implemented by extending existing MO-LR and / or SI request procedures, thus reducing the need to create new procedures. Other capabilities may be provided, and not all implementations according to the present disclosure must provide any, much less all, of the discussed capabilities. [Brief explanation of the drawings]

[0028] [Figure 1] 1 is a schematic diagram of an exemplary wireless communication system. [Figure 2] FIG. 2 is a block diagram of components of an exemplary user equipment. [Figure 3] FIG. 2 is a block diagram of components of an exemplary transmit / receive point. [Figure 4] FIG. 2 is a block diagram of components of an exemplary server. [Figure 5A] FIG. 1 illustrates an example downlink positioning reference signal resource set. [Figure 5B] FIG. 1 illustrates an example downlink positioning reference signal resource set. [Figure 6] FIG. 1 is a diagram of an example subframe format for positioning reference signal transmission. [Figure 7] FIG. 1 is a conceptual diagram of an exemplary positioning frequency layer. [Figure 8] FIG. 10 is an example message flow diagram for extending a mobile-originated location request procedure to enable on-demand DL-PRS. [Figure 9A] FIG. 10 is an example message flow diagram for extending the mobile-originated location request procedure to allow for on-demand DL-PRS and UL-PRS. [Figure 9B] FIG. 10 is an example message flow diagram for extending the mobile-originated location request procedure to allow for on-demand DL-PRS and UL-PRS. [Figure 10A] FIG. 10 is an example message flow diagram for extending the on-demand system information procedure to enable on-demand DL-PRS. [Figure 10B] FIG. 10 is an example message flow diagram for extending the on-demand system information procedure to enable on-demand DL-PRS. [Figure 11A] FIG. 10 is an example message flow diagram for extending the on-demand system information procedure to enable on-demand DL-PRS and UL-PRS. [Figure 11B]FIG. 10 is an example message flow diagram for extending the on-demand system information procedure to enable on-demand DL-PRS and UL-PRS. [Figure 12] 1 is a process flow of an exemplary method for determining the position of a mobile device using an on-demand positioning reference signal. [Figure 13] 1 is a process flow of an exemplary method for providing assistance data for an on-demand positioning reference signal. [Figure 14] 1 is a process flow of an exemplary method for determining a position of a mobile device using on-demand downlink and uplink positioning reference signals. [Figure 15] 1 is a process flow of an exemplary method for providing assistance data for on-demand downlink and uplink positioning reference signals. DETAILED DESCRIPTION OF THE INVENTION

[0029] Elements, phases, steps, and / or actions with the same reference label in different drawings may correspond to one another (e.g., may be similar or identical to one another). Additionally, multiple instances of an element may be indicated by the first numeral of that element followed by a letter. For example, multiple instances of element 110 may be indicated as 110a, 110b, 110c, etc. When referring to such an element using only the first numeral, it should be understood to refer to any instance of that element (e.g., element 110 in the previous example refers to elements 110a, 110b, and 110c).

[0030] Techniques for providing an on-demand positioning reference signal (PRS) to user equipment (UE) are discussed herein. Previous implementations of downlink (DL) PRS transmission are typically in an “always-on” configuration, such that a base station transmits the PRS regardless of the UE's requirements in the network. Such an “always-on” configuration may utilize scarce resources, such as bandwidth and energy, and may require unnecessary overhead when UE positioning is not required during a specific time or in a specific network area. In networks utilizing beamformed DL-PRS transmission (e.g., 5G NR), DL-PRS transmission in all beam sweep directions may result in unnecessary transmission of the DL-PRS. The “always-on” configuration may also utilize static allocation of DL-PRS resources. Generally, static DL-PRS resource allocation does not allow for temporary increase of DL-PRS resources to achieve higher positioning accuracy and / or lower latency positioning requirements in a certain area or at a certain time. Similarly, static allocation of DL-PRS resources does not allow reducing DL-PRS resources when positioning requirements can be met with fewer DL-PRS resources or when there are no UEs that need to be positioned for a certain period of time.

[0031] The on-demand DL-PRS techniques described herein enable a network to dynamically change DL-PRS resource allocation as needed (e.g., based on requirements for a particular use case or application). In one example, the on-demand DL-PRS techniques may enable a network to dynamically change configuration parameters such as the periodicity of the DL-PRS opportunity, the duration of the DL-PRS opportunity, the bandwidth of the DL-PRS, and the spatial direction of the DL-PRS.

[0032] A DL PRS configuration may define transmission of DL-PRS (e.g., in one or more cells and / or by one or more base stations) according to a particular set of DL-PRS configuration parameter values. For example, a DL-PRS transmission may use specific values ​​for parameters such as the DL-PRS bandwidth, the DL-PRS frequency (or frequencies), the time length of the DL-PRS positioning occasion, the spatial direction of the DL-PRS positioning occasion, the periodicity of the DL-PRS positioning occasion, the DL-PRS encoding, the DL-PRS muting pattern, etc. A DL PRS configuration may be static, which may correspond to an “always-on” DL-PRS transmission if the specific values ​​of the parameters of the DL-PRS transmission are not changed, or may be capable of being changed (e.g., replaced with a different DL PRS configuration) as described herein.

[0033] In one embodiment, on-demand DL-PRS may be implemented in a network by defining a set of different DL-PRS configurations, whose parameter values ​​may be configured in the network using operation and maintenance (O&M) procedures. For example, one set of DL-PRS configuration parameter values ​​(simply referred to herein as “parameters”) may be configured to correspond to “regular” DL-PRS transmissions, and in some networks, “regular” DL-PRS transmissions may not correspond to any DL-PRS transmissions at all (e.g., to minimize resource usage). In other examples, one or more levels of increased DL-PRS transmission may each be associated with a different set of DL-PRS configuration parameter values, such as parameter values ​​defining the DL-PRS bandwidth, the DL-PRS frequency, the time length of the DL-PRS positioning occasion, the spatial direction of the DL-PRS positioning occasion, and the periodicity of the DL-PRS positioning occasion. DL-PRS transmissions may then be changed (e.g., increased or decreased) by changing the DL-PRS configuration used to transmit the DL-PRS. This change may be "on-demand" in the sense that an entity such as a UE or a location services (LCS) client may be allowed to indicate parameter values ​​or characteristics (e.g., "high QoS", "low QoS") for a new DL PRS configuration or a set of new DL PRS configurations to be used for transmitting DL PRS in a particular cell or cells and / or by a particular base station or base stations.

[0034] On-demand DL-PRS may have a presumption for UE-based positioning based on a request from an internal UE client. For example, when an application resident on the UE requires location, there may be no (or insufficient) DL-PRS resources available (e.g., all gNBs located around the UE's location may have DL-PRS "off"). Furthermore, for some positioning results (e.g., UE Rx-Tx time difference measurement results), the UE may require both DL-PRS and uplink PRS (UL-PRS, also referred to as Sounding Reference Signal (SRS) for positioning) to perform the positioning measurement. When an internal UE client requests location, the UE may not be configured with the desired UL-PRS (e.g., with the desired periodicity, bandwidth, duration, etc.). The on-demand PRS techniques described herein may enable the UE to request DL-PRS transmission from the network and / or provide a UL-PRS configuration on demand.

[0035] In an embodiment, a Mobile-Originated Location Request (MO-LR) procedure or an On-Demand System Information (SI) Request procedure may be used by the target UE to request on-demand DL-PRS transmission or one or more DL-PRS transmissions from the network and / or to request UL-PRS configuration information. The techniques provided herein extend existing procedures rather than creating new procedures, thereby reducing the impact on the UE and the network. In an example, the procedures for determining and configuring a new PRS may be the same and may be independent of whether the request for the PRS is initiated by the network or the UE. These techniques and configurations are examples, and other techniques and configurations may be used.

[0036] 1 , an example communication system 100 includes a UE 105, a radio access network (RAN) 135, here a fifth-generation (5G) next-generation (NG) RAN (NG-RAN), and a 5G core network (5GC) 140. The UE 105 may be, for example, an IoT device, a location tracking device, a mobile phone, or other device. The 5G network may also be referred to as a New Radio (NR) network, the NG-RAN 135 may also be referred to as a 5G RAN or an NR RAN, and the 5GC 140 may also be referred to as an NG core network (NGC). The NG-RAN 135 may be another type of RAN, for example, a 3G RAN, a 4G Long Term Evolution (LTE) RAN, etc. The communications system 100 may utilize information from a constellation 185 of space vehicles (SVs) 190, 191, 192, 193 for a satellite positioning system (SPS) (e.g., a Global Navigation Satellite System (GNSS)), such as the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Galileo, or Beidou, or some other local or regional SPS, such as the Indian Regional Navigation Satellite System (IRNSS), the European Geostationary Satellite Navigation Overlay Service (EGNOS), or the Wide Area Augmentation System (WAAS). Additional components of the communications system 100 are described below. The communications system 100 may include additional or alternative components.

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

[0038] FIG. 1 provides a generalized illustration of various components, any or all of which may be utilized as appropriate, and each of which may be duplicated or omitted as needed. Specifically, while one UE 105 is illustrated, many UEs (e.g., hundreds, thousands, millions, etc.) may be utilized in communications system 100. Similarly, communications system 100 may include many (or fewer) SVs (i.e., more or fewer than the four SVs 190-193 shown), gNBs 110a, 110b, ng-eNB 114, AMF 115, external client 130, and / or other components. The illustrated connections connecting the various components in communications system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, substituted, and / or omitted depending on desired functionality.

[0039] 1 illustrates a 5G-based network, similar network implementations and configurations may be used for other communication technologies, such as 3G, Long Term Evolution (LTE), etc. Implementations described herein (whether for 5G technology and / or for one or more other communication technologies and / or protocols) may be used to transmit (or broadcast) directional synchronization signals, receive and measure the directional signals at a UE (e.g., the UE 105), and / or provide location assistance to the UE 105 (via the GMLC 125 or other location server), and / or calculate the location of the UE 105 at a location-enabled device, such as the UE 105, gNBs 110a, 110b, or LMF 120, based on measurements received at the UE 105 for such directional transmitted signals. The 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 may each be replaced by or include various other location server functions and / or base station functions in various embodiments.

[0040] The UE 105 may comprise and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a Secure User Plane Location (SUPL)-enabled terminal (SET), or some other name. Additionally, the UE 105 may correspond to a mobile phone, a smartphone, a laptop, a tablet, a PDA, a consumer asset tracking device, a navigation device, an Internet of Things (IoT) device, an asset tracker, a health monitor, a security system, a smart city sensor, a smart meter, a wearable tracker, or some other portable or mobile device. Typically, although not necessarily, the UE 105 may support wireless communications 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 Rate Packet Data (HRPD), IEEE 802.11 WiFi (also referred to as Wi-Fi), Bluetooth (BT), Worldwide Interoperability for Microwave Access (WiMAX), 5G new radio (NR) (e.g., using NG-RAN 135 and 5GC 140), etc. The UE 105 may also support wireless communications using a wireless local area network (WLAN), which may connect to other networks (e.g., the Internet) using, for example, a digital subscriber line (DSL) or packet cable. Use of one or more of these RATs may enable UE 105 to communicate with external client 130 (e.g., via elements of 5GC140 not shown in FIG. 1 or possibly via GMLC125) and / or enable external client 130 to receive location information regarding UE 105 (e.g., via GMLC125).

[0041] The UE 105 may comprise a single entity or may include multiple entities, such as in a personal area network where a user may utilize audio, video, and / or data I / O (input / output) devices and / or body sensors, and a separate wired or wireless modem. An estimate of the UE 105's location may be referred to as a position, position estimate, position fix, fix, location, location estimate, or location fix, and provides location coordinates (e.g., latitude and longitude) of the UE 105 that may or may not include an altitude component (e.g., elevation, height or depth above ground, floor, or basement). Alternatively, the UE 105's location may be expressed as a civic location (e.g., as an address or designation of some point or small area within a building, such as a particular room or floor). The UE 105's location may also be expressed as an area or volume (defined either geographically or in civic format) within which the UE 105 is expected to be located with some probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 105 may be expressed as a relative location, e.g., comprising a distance and a direction from a known location. The relative location may be expressed as relative coordinates (e.g., X, Y (and Z) coordinates) defined relative to some origin at a known location, which may be defined, e.g., geographically, civic-wise, or by reference to a point, area, or volume shown on a map, floor plan, or building plan. In the description contained herein, use of the term location may include any of these variations unless otherwise specified. When calculating the location of a UE, it is common to solve for local x, y, and possibly z coordinates and then convert the local coordinates to absolute coordinates (e.g., for latitude, longitude, and altitude above or below mean sea level) if desired.

[0042] The UE 105 may be configured to communicate with other entities using one or more of a variety of technologies. The UE 105 may 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 may be supported using any suitable D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc. One or more of a group of UEs utilizing D2D communication may be within the geographic coverage area of ​​a transmit / receive point (TRP), such as one or more of the gNBs 110a, 110b, and / or ng-eNB 114. Other UEs in such a group may be outside such geographic coverage area or may otherwise be unable to receive transmissions from the base station. A group of UEs communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE may transmit to other UEs in the group. The TRP may facilitate scheduling of resources for D2D communication. In other cases, D2D communication may be performed between UEs without the involvement of a TRP.

[0043] The base stations (BSs) in the NG-RAN 135 shown in FIG. 1 include NR NodeBs referred to as gNodeBs (gNBs) 110a and 110b. The pair of gNBs 110a, 110b in the NG-RAN 135 may be connected to each other via one or more other gNBs. Access to a 5G network is provided to the UE 105 via wireless communication between the UE 105 and one or more of the gNBs 110a, 110b, which may provide wireless communication access to a 5G network controller 140 on behalf of the UE 105 using 5G. In FIG. 1, the serving gNB for the UE 105 is assumed to be gNB 110a, although another gNB (e.g., gNB 110b) may function as the serving gNB if the UE 105 moves to another location or may function as a secondary gNB to provide additional throughput and bandwidth to the UE 105.

[0044] 1 may include the ng-eNB 114, also referred to as a next-generation evolved Node B. The ng-eNB 114 may be connected to one or more of the gNBs 110a, 110b in the NG-RAN 135, possibly via one or more other gNBs and / or one or more other ng-eNBs. The ng-eNB 114 may provide LTE wireless access and / or evolved LTE (eLTE) wireless access to the UE 105. One or more of the gNBs 110a, 110b, and / or ng-eNB 114 may be configured to function as positioning-only beacons, which may transmit signals to assist in determining the location of the UE 105 but may not receive signals from the UE 105 or other UEs.

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

[0046] As mentioned, while Figure 1 illustrates nodes configured to communicate according to a 5G communication protocol, nodes configured to communicate according to other communication protocols, such as, for example, an LTE protocol or an IEEE 802.11x protocol, may also be used. For example, in an Evolved Packet System (EPS) providing LTE wireless access to the UE 105, the RAN may comprise an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), which may comprise base stations comprising evolved Node Bs (eNBs). The core network for the EPS may comprise an Evolved Packet Core (EPC). The EPS may comprise the E-UTRAN plus the EPC, where in Figure 1, the E-UTRAN corresponds to the NG-RAN 135 and the EPC corresponds to the 5GC 140.

[0047] The gNBs 110a, 110b, and the ng-eNB 114 may communicate with the AMF 115, which in turn communicates with the LMF 120 for positioning functions. The AMF 115 may support mobility of the UE 105, including cell changes and handovers, and may participate in supporting signaling connections to the UE 105 and, possibly, data and voice bearers for the UE 105. The LMF 120 may communicate directly with the UE 105, for example, through wireless communication. The LMF 120 may support positioning of the UE 105 when the UE 105 accesses the NG-RAN 135 and may support positioning procedures / methods such as Assisted Global Positioning System (A-GNSS), Observed Time Difference of Arrival (OTDOA), Real Time Kinematic (RTK), High Precision Point Positioning (PPP), Differential Global Positioning System (DGNSS), Enhanced Cell ID (E-CID), Angle of Arrival (AOA), Angle of Departure (AOD), and / or other positioning methods. The LMF 120 may process location service requests for the UE 105 received, for example, from the AMF 115 or from the GMLC 125. The LMF 120 may be connected to the AMF 115 and / or the GMLC 125. The LMF 120 may be referred to by other names, such as a Location Manager (LM), Location Function (LF), Commercial LMF (CLMF), or Value Added LMF (VLMF). A node / system implementing the LMF 120 may additionally or alternatively implement other types of positioning support modules, such as an Enhanced Serving Mobile Location Center (E-SMLC) or a Secure User Plane Location (SUPL) Location Platform (SLP). At least a portion of the positioning functions (including deriving the position of the UE 105) may be performed at the UE 105 (e.g., using signal measurements obtained by the UE 105 on signals transmitted by wireless nodes such as the gNBs 110a, 110b, and / or the ng-eNB 114, and / or assistance data provided to the UE 105 by, for example, the LMF 120).

[0048] The GMLC 125 may support location requests for the UE 105 received from the external client 130 and may forward such location requests to the AMF 115 for forwarding by the AMF 115 to the LMF 120, or may forward the location requests directly to the LMF 120. A location response (e.g., including a position estimate for the UE 105) from the LMF 120 may be returned to the GMLC 125 either directly or via the AMF 115, which may then return the location response (e.g., including the position estimate) to the external client 130. While the GMLC 125 is shown connected to both the AMF 115 and the LMF 120, one of these connections may be supported by the 5GC 140 in some implementations.

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

[0050] Using a UE-assisted positioning method, the UE 105 may obtain position measurements and may transmit the measurements to a location server (e.g., the LMF 120) for calculation of a position estimate for the UE 105. For example, the position measurements may include one or more of a received signal strength indication (RSSI), a round-trip signal propagation time (RTT), a reference signal time difference (RSTD), a UE receive-transmit time difference (Rx-Tx Time Difference), a reference signal received power (RSRP), and / or a reference signal received quality (RSRQ) for the gNB 110a, 110b, the ng-eNB 114, and / or a WLAN AP. The position measurements may also or instead include GNSS pseudorange, code phase, and / or carrier phase measurements for the SV 190-193.

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

[0052] Using a network-based positioning method, one or more base stations (e.g., gNBs 110a, 110b, and / or ng-eNB 114) or APs may obtain position measurements (e.g., RSSI, RTT, Rx-Tx time difference, RSRP, RSRQ, or time of arrival (TOA) measurements for signals transmitted by the UE 105) and / or may receive measurements obtained by the UE 105. The one or more base stations or APs may transmit the measurements to a location server (e.g., LMF 120) for calculation of a position estimate for the UE 105.

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

[0054] An LPP message sent from the LMF 120 to the UE 105 may instruct the UE 105 to do any of a variety of things depending on the desired functionality. For example, the LPP message may include instructions for the UE 105 to acquire measurements for GNSS (or A-GNSS), WLAN, E-CID, and / or OTDOA (or some other positioning method). In the case of E-CID, the LPP message may instruct the UE 105 to acquire one or more measurements (e.g., beam ID, beam width, average angle, RSRP, RSRQ measurements) of directional signals transmitted within a particular cell supported by one or more of the gNBs 110a, 110b, and / or ng-eNB 114 (or supported by some other type of base station, such as an eNB or WiFi AP). The UE 105 may send the measurement quantities back to the LMF 120 via the serving gNB 110a (or serving ng-eNB 114) and the AMF 115 or in an LPP message (e.g., inside a 5G NAS message).

[0055] As mentioned, although communication system 100 is described with respect to 5G technology, communication system 100 may be implemented to support other communication technologies (e.g., to implement voice, data, positioning, and other functions), such as GSM, WCDMA, LTE, etc., used to support and interwork with mobile devices such as UE 105. In some such embodiments, 5GC 140 may be configured to control different air interfaces. For example, 5GC 140 may connect to a WLAN using a Non-3GPP InterWorking Function (N3IWF, not shown in FIG. 1 ) in 5GC 150. For example, the WLAN may support IEEE 802.11 WiFi access for UE 105 and may comprise one or more WiFi APs. Here, N3IWF may connect to the WLAN and to other elements 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 an EPS, the NG-RAN 135 may be replaced by an E-UTRAN including eNBs, and the 5GC 140 may be replaced by an EPC including a mobility management entity (MME) instead of the AMF 115, an E-SMLC instead of the LMF 120, and a GMLC that may be similar to the GMLC 125. In such an EPS, the E-SMLC may use LPPa instead of NRPPa to send and receive location information to and from the eNBs in the E-UTRAN and may use LPP to support positioning of the UE 105. In these other embodiments, positioning of the UE 105 using directional PRS may be supported in a similar manner as described herein for a 5G network, with the difference being that the functions and procedures described herein for the gNBs 110a, 110b, ng-eNB 114, AMF 115, and LMF 120 may instead apply to other network elements, such as eNBs, WiFi APs, MMEs, and E-SMLCs, as the case may be.

[0056] As mentioned, in some embodiments, the positioning functionality may be implemented, at least in part, using directional SS or PRS beams transmitted by base stations (such as gNBs 110a, 110b, and / or ng-eNB 114) that are within range of the UE (e.g., UE 105 of FIG. 1) whose location is to be determined. The UE may, in some instances, use directional SS or PRS beams from multiple base stations (such as gNBs 110a, 110b, ng-eNB 114) to calculate the UE's location.

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

[0058] 2 is an example of the present disclosure, including the claims, and is not limiting, and other configurations may be used. For example, an exemplary configuration of a 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, one or more of sensors 213, user interface 216, SPS receiver 217, camera 218, PMD 219, and / or wired transceiver 250.

[0059] The UE 200 may include a modem processor 232 that may be capable of performing baseband processing of signals received and downconverted by the transceiver 215 and / or the SPS receiver 217. The modem processor 232 may perform baseband processing of the signals to be upconverted for transmission by the transceiver 215. Also or alternatively, the baseband processing may be performed by the general purpose processor 230 and / or the DSP 231. However, other configurations may be used to perform the baseband processing.

[0060] The UE 200 may include sensors 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. The IMU 270 may comprise one or more inertial sensors, for example, one or more accelerometers 273 (e.g., collectively responsive to acceleration of the UE 200 in three dimensions) and / or one or more gyroscopes 274. The magnetometers may provide measurements for determining orientation (e.g., relative to magnetic north and / or true north), which may be used for any of a variety of purposes, for example, to support one or more compass applications. The environmental sensors 272 may comprise, for example, one or more temperature sensors, one or more barometric pressure sensors, one or more ambient light sensors, one or more camera imagers, and / or one or more microphones, etc. The sensors 213 may generate analog and / or digital signals, and indications of the signals may be stored in memory 211 and processed by the DSP 231 and / or general-purpose processor 230 to support one or more applications, such as applications directed to positioning and / or navigation operations, for example.

[0061] The sensors 213 may be used in relative position measurement, relative position determination, motion determination, etc. Information detected by the sensors 213 may be used for motion detection, relative displacement, autonomous navigation, sensor-based position determination, and / or sensor-assisted position determination. The sensors 213 may be useful in determining whether the UE 200 is fixed (stationary) or mobile and / or whether any useful information regarding the mobility of the UE 200 should be reported to the LMF 120. For example, based on information acquired / measured by the sensors 213, the UE 200 may notify / report to the LMF 120 that the UE 200 has detected movement or that the UE 200 has moved, and may report a relative displacement / distance (e.g., via autonomous navigation, or sensor-based position determination, or sensor-assisted position determination enabled by the sensors 213). In another example, for relative positioning information, the sensors / IMU may be used to determine the angle and / or orientation of other devices relative to the UE 200, etc.

[0062] The IMU 270 may be configured to provide measurements of the direction and / or speed of movement of the UE 200, which may be used in relative position determination. For example, one or more accelerometers 273 and / or one or more gyroscopes 274 of the IMU 270 may detect the linear acceleration and rotational velocity of the UE 200, respectively. The linear acceleration and rotational velocity measurements of the UE 200 may be integrated over time to determine the instantaneous direction and displacement of the UE 200's movement. The instantaneous direction and displacement of the movement may be integrated to track the position of the UE 200. For example, a reference position of the UE 200 may be determined for a certain instant using, for example, the SPS receiver 217 (and / or by some other means), and measurements from the accelerometer 273 and the gyroscope 274 obtained after this instant may be used in autonomous navigation to determine the current position of the UE 200 based on the movement (direction and distance) of the UE 200 compared to the reference position.

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

[0064] The transceiver 215 may include a wireless transceiver 240 and a wired transceiver 250 configured to communicate with other devices over wireless and wired connections, respectively. For example, the wireless transceiver 240 may include a transmitter 242 and a receiver 244 coupled to one or more antennas 246 to transmit (e.g., on one or more uplink channels and / or one or more sidelink channels) and / or receive (e.g., on one or more downlink channels and / or one or more sidelink channels) wireless signals 248 and convert signals from the wireless signals 248 to wired (e.g., electrical and / or optical) signals and from the wired (e.g., electrical and / or optical) signals to the wireless signals 248. Thus, the transmitter 242 may include multiple transmitters, which may be separate components or combined / integrated components, and / or the receiver 244 may include multiple receivers, which may be separate components or combined / integrated components. The wireless transceiver 240 may be configured to communicate signals (e.g., with the TRP and / or one or more other devices) in accordance with various radio access technologies (RATs), such as 5G New Radio (NR), Global System for Mobiles (GSM), Universal Mobile Telecommunications System (UMTS), Advanced Mobile Phone System (AMPS), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Long-Term Evolution (LTE), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), V2C (Uu), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Bluetooth, Zigbee, etc.An NR system may be configured to operate on different frequency tiers, such as FR1 (e.g., 410-7125 MHz) and FR2 (e.g., 24.25-52.6 GHz), and may extend to new bands, such as sub-6 GHz and / or above 100 GHz (e.g., FR2x, FR3, FR4). The wired transceiver 250 may include a transmitter 252 and a receiver 254 configured for wired communication with, for example, the NG-RAN 135, for example, to send communications to and receive communications from the gNB 110a. The transmitter 252 may include multiple transmitters, which may be separate components or combined / integrated components, and / or the receiver 254 may include multiple receivers, which may be separate components or combined / integrated components. The wired transceiver 250 may be configured for optical and / or electrical communication, for example. The transceiver 215 may be communicatively coupled to the transceiver interface 214, for example, by an optical and / or electrical connection. The transceiver interface 214 may be at least partially integrated with the transceiver 215 .

[0065] The user interface 216 may comprise one or more of several devices, such as, for example, a speaker, a microphone, a display device, a vibrating device, a keyboard, a touchscreen, etc. The user interface 216 may include two or more of any of these devices. The user interface 216 may be configured to allow a user to interact with one or more applications hosted by the UE 200. For example, the user interface 216 may store in the memory 211 indications of analog and / or digital signals to be processed by the DSP 231 and / or the general-purpose processor 230 in response to actions from the user. Similarly, applications hosted on the UE 200 may store in the memory 211 indications of analog and / or digital signals to present output signals to the user. The user interface 216 may include audio input / output (I / O) devices, including, for example, a speaker, a microphone, digital-to-analog circuitry, analog-to-digital circuitry, an amplifier, and / or gain control circuitry (including two or more of any of these devices). Other configurations of audio I / O devices may be used. Also or alternatively, the user interface 216 may include one or more touch sensors that respond to contact and / or pressure, for example, on a keyboard and / or touchscreen of the user interface 216 .

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

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

[0068] Positioning (motion) device (PMD) 219 may be configured to determine the position, and possibly the movement, of UE 200. For example, PMD 219 may be in communication with and / or include part or all of SPS receiver 217. PMD 219 may also or alternatively be configured to determine the position of UE 200 using terrestrial-based signals (e.g., at least some of signals 248), to assist in acquiring and using SPS signals 260 for trilateration, or both. PMD 219 may be configured to use one or more other techniques for determining the position of UE 200 (e.g., relying on the UE's self-reported position (e.g., part of the UE's location beacon)) or may use a combination of techniques (e.g., SPS signals and terrestrial positioning signals) to determine the position of UE 200. The PMD 219 may include one or more of the sensors 213 (e.g., gyroscopes, accelerometers, magnetometers, etc.) that may sense the orientation and / or movement of the UE 200 and provide indications of the orientation and / or movement that the processor 210 (e.g., the general-purpose processor 230 and / or the DSP 231) may configure to use to determine the movement (e.g., velocity vector and / or acceleration vector) of the UE 200. The PMD 219 may be configured to provide an indication of uncertainty and / or error in the determined location and / or movement. In one example, the PMD 219 may be referred to as a positioning engine (PE) and may be executed by the general-purpose processor 230. For example, the PMD 219 may be a logical entity and may be integrated with the general-purpose processor 230 and the memory 211.

[0069] 3 , an example TRP 300 of the gNB 110a, gNB 110b, and ng-eNB 114 comprises a computing platform including 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 may be communicatively coupled to each other by a bus 320 (e.g., which may be configured for optical and / or electrical communications). One or more of the devices shown (e.g., the wireless interface and / or the SPS receiver 317) may be omitted from the TRP 300. The SPS receiver 317 may be configured similarly to the SPS receiver 217 to be able to receive and acquire SPS signals 360 via an SPS antenna 362. The processor 310 may include one or more intelligent hardware devices, e.g., a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), etc. The processor 310 may comprise multiple processors (e.g., including a general-purpose / application processor, a DSP, a modem processor, a video processor, and / or a sensor processor, as shown in FIG. 4). The memory 311 is a non-transitory storage medium that may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. The memory 311 stores software 312, which may be processor-readable, processor-executable software code that includes instructions configured, when executed, to cause the processor 310 to perform various functions described herein. Alternatively, the software 312 may not be directly executable by the processor 310, but may be configured, for example, when compiled and executed, to cause the processor 310 to perform a function. While this description may refer to the processor 310 performing a function, this includes other implementations, such as when the processor 310 executes software and / or firmware.The description may refer to the processor 310 performing a function as shorthand for one or more of the processors included in the processor 310 performing the function. The description may refer to the TRP 300 performing a function as shorthand for one or more suitable components of the TRP 300 (and thus one of the gNB 110a, gNB 110b, ng-eNB 114) performing the function. The processor 310 may include memory in addition to and / or in place of the memory 311 on which instructions are stored. The functionality of the processor 310 is discussed more fully below.

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

[0071] 3 is an example, not a limitation, of the present disclosure, including the claims, and other configurations may be used. For example, although the description herein discusses the TRP 300 being configured to perform or performing certain functions, one or more of these functions may be performed by the LMF 120 and / or the UE 200 (i.e., the LMF 120 and / or the UE 200 may be configured to perform one or more of these functions).

[0072] 4, an exemplary server, such as the LMF 120, comprises a computing platform including a processor 410, a memory 411 including software (SW) 412, and a transceiver 415. The processor 410, the memory 411, and the transceiver 415 may be communicatively coupled to each other by a bus 420 (which may be configured for optical and / or electrical communication, for example). One or more of the depicted devices (e.g., a wireless interface) may be omitted from the server 400. The processor 410 may include one or more intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), etc. The processor 410 may comprise multiple processors (e.g., including a general-purpose / application processor, a DSP, a modem processor, a video processor, and / or a sensor processor, as shown in FIG. 4). The memory 411 is a non-transitory storage medium and may include random access memory (RAM), flash memory, disk memory, and / or read-only memory (ROM), etc. The memory 411 stores software 412, which may be processor-readable, processor-executable software code including instructions that, when executed, are configured to cause the processor 410 to perform various functions described herein. Alternatively, the software 412 may not be directly executable by the processor 410, but may be configured, for example, when compiled and executed, to cause the processor 410 to perform a function. The description may refer to the processor 410 performing a function, which includes other implementations, such as when the processor 410 executes software and / or firmware. The description may refer to the processor 410 performing a function as shorthand for one or more of the processors included in the processor 410 performing the function. The description may refer to the server 400 (or the LMF 120) performing a function as shorthand for one or more suitable components of the server 400 performing the function.The processor 410 may include memory in which instructions are stored in addition to and / or in place of the memory 411. The functionality of the processor 410 is discussed more fully below.

[0073] The transceiver 415 may include a wireless transceiver 440 and / or a wired transceiver 450 configured to communicate with other devices over wireless and wired connections, respectively. For example, the wireless transceiver 440 may include a transmitter 442 and a receiver 444 coupled to one or more antennas 446 to transmit (e.g., on one or more downlink channels) and / or receive (e.g., on one or more uplink channels) wireless signals 448 and convert signals from the wireless signals 448 to wired (e.g., electrical and / or optical) signals and from the wired (e.g., electrical and / or optical) signals to the wireless signals 448. Thus, the transmitter 442 may include multiple transmitters, which may be separate components or combined / integrated components, and / or the receiver 444 may include multiple receivers, which may be separate components or combined / integrated components. The wireless transceiver 440 may be configured to communicate signals (e.g., with the UE 200, one or more other UEs, and / or one or more other devices) according to various radio access technologies (RATs), such as 5G New Radio (NR), Global System for Mobiles (GSM), Universal Mobile Telecommunications System (UMTS), Advanced Mobile Phone System (AMPS), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Long-Term Evolution (LTE), LTE Direct (LTE-D), 3GPP LTE-V2X (PC5), IEEE 802.11 (including IEEE 802.11p), WiFi, WiFi Direct (WiFi-D), Bluetooth, Zigbee, etc. The wired transceiver 450 may include a transmitter 452 and a receiver 454 configured for wired communication with the NG-RAN 135, e.g., for transmitting communications to and receiving communications from the TRP 300.The transmitter 452 may include multiple transmitters, which may be separate components or combined / integrated components, and / or the receiver 454 may include multiple receivers, which may be separate components or combined / integrated components. The wired transceiver 450 may be configured for optical and / or electrical communication, for example.

[0074] 4 is an example of the present disclosure, including the claims, and other configurations may be used. For example, wireless transceiver 440 may be omitted. Also or alternatively, although the description herein describes server 400 as being configured to perform or performing certain functions, 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).

[0075] 5A and 5B, exemplary downlink PRS resource sets are shown. Generally, a PRS resource set is a collection of PRS resources across one base station (e.g., TRP 300) that have the same periodicity, a common muting pattern configuration, and the same repetition factor across slots. A first PRS resource set 502 includes four resources and a repetition factor of four, with a time gap equal to one slot. A second PRS resource set 504 includes four resources and a repetition factor of four, with a time gap equal to four slots. The repetition factor indicates the number of times each PRS resource is repeated within each single instance of a PRS resource set (e.g., a value of 1, 2, 4, 6, 8, 16, or 32). The time gap represents the offset in slots (e.g., a value of 1, 2, 4, 8, 16, or 32) between two repeated instances of PRS resources corresponding to the same PRS resource ID within a single instance of a PRS resource set. The length of time spanned by one PRS resource set, including the repeated PRS resources, does not exceed the PRS period. Repetition of PRS resources allows for sweeping of the receiver beam across the repetitions and RF gain combining to increase coverage. Repetition may also allow for intra-instance muting. A single instance of a PRS resource set, such as that shown in Figures 5A and 5B, may be referred to as a "PRS opportunity."

[0076] Referring to Figure 6, exemplary subframe and slot formats for positioning reference signal transmission are shown. The exemplary subframe and slot formats are included in the PRS resource set illustrated in Figures 5A and 5B. The subframe and slot formats in Figure 6 are by way of example and not limitation, and include Comb 2 602 having a 2-symbol format, Comb 4 604 having a 4-symbol format, Comb 2 606 having a 12-symbol format, Comb 4 608 having a 12-symbol format, Comb 6 610 having a 6-symbol format, Comb 12 612 having a 12-symbol format, Comb 2 614 having a 6-symbol format, and Comb 6 616 having a 12-symbol format. Generally, a subframe may include 14 symbol periods with indices 0 through 13. Typically, a base station may transmit a PRS from antenna port 5000 on one or more slots in each subframe configured for PRS transmission.

[0077] A base station may transmit a PRS over a specific PRS bandwidth, which may be configured by higher layers. The PRS resources may be located anywhere within the frequency grid. A common reference point for the PRS may be defined as "PRS Point A." "PRS Point A" may serve as a common reference point for the PRS resource block grid and may be represented by an absolute radio frequency channel number (ARFCN). A PRS starting physical resource block (PRB) may then be defined as the frequency offset, expressed in resource blocks, between PRS Point A and the lowest subcarrier of the lowest PRS resource block. A base station may transmit a PRS on subcarriers spaced across the PRS bandwidth.

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

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

[0080] In general, the PRS resource shown in Figures 5A and 5B may be a set of resource elements used for transmitting a PRS. The set of resource elements may span multiple physical resource blocks (PRBs) in the frequency domain and N (e.g., one or more) consecutive symbols within a slot in the time domain. Within a given OFDM symbol, the PRS resource occupies consecutive PRBs. A PRS resource is described by at least the following parameters: a PRS resource identifier (ID), a sequence ID, a comb size N, a resource element offset in the frequency domain, a starting slot and symbol, the number of symbols per PRS resource (i.e., the time length of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). The comb size indicates the number of subcarriers in each symbol carrying a PRS. For example, a comb size of comb4 means that every fourth subcarrier in a given symbol carries a PRS.

[0081] A PRS resource set is a set of PRS resources used for transmitting PRS signals, and each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same transmission / reception point (e.g., TRP 300). Each of the PRS resources in a PRS resource set may have the same periodicity, a common muting pattern, and the same repetition factor across slots. A PRS resource set may be identified by a PRS resource set ID and associated with a specific TRP (identified by a cell ID) transmitted by a base station antenna panel. A PRS resource ID in a PRS resource set may be associated with an omnidirectional signal and / or a single beam (and / or beam ID) transmitted from a single base station (a base station may transmit one or more beams). Each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, a PRS resource, or simply a resource, may also be referred to as a beam. Note that this does not have any implications on whether the base station and the beam on which the PRS is transmitted are known to the UE.

[0082] Referring to FIG. 7, a conceptual diagram of an exemplary positioning frequency layer 700 is shown. In one example, the positioning frequency layer 700 may be a collection of PRS resource sets across one or more TRPs. The positioning frequency layer may have the same subcarrier spacing (SCS) and cyclic prefix (CP) type, the same PRS point A, the same PRS bandwidth, the same starting PRB, and the same comb size. Numerologies supported for PDSCH may be supported for PRSs. Each PRS resource set in the positioning frequency layer 700 is a collection of PRS resources across one TRP with the same periodicity, a common muting pattern configuration, and the same repetition factor across slots.

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

[0084] When the PRS is transmitted by the TRP, the PRS may be referred to as a DL-PRS. When the PRS is transmitted by the UE, the PRS may be referred to as a UL-PRS. The UL-PRS may be based on the SRS with modifications for positioning purposes. The UL-PRS may also be referred to as an "SRS for positioning." In some aspects, the UL-PRS may be considered the uplink equivalent of the DL-PRS.

[0085] The capability of a UE to process PRS signals may vary based on the UE's capabilities. However, in general, industry standards may be developed to establish common PRS capabilities for UEs in a network. For example, an industry standard may require that a UE be able to process a DL PRS symbol duration in milliseconds (ms) every T ms, assuming a maximum DL PRS bandwidth in MHz supported and reported by the UE. By way of example and not limitation, the maximum DL PRS bandwidth for the FR1 band may be 5, 10, 20, 40, 50, 80, or 100 MHz, and the maximum DL PRS bandwidth for the FR2 band may be 50, 100, 200, or 400 MHz. The standard may also indicate DL PRS buffering capability as Type 1 (i.e., subslot / symbol-level buffering) or Type 2 (i.e., slot-level buffering). The common UE capability may indicate that a UE is able to process a DL PRS symbol duration N in ms every T ms, assuming a maximum DL PRS bandwidth in MHz supported and reported by the UE. Exemplary values ​​of T may include 8, 16, 20, 30, 40, 80, 160, 320, 640, and 1280 ms, and exemplary values ​​of N may include 0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, and 50 ms. The UE may be configured to report a combination of (N, T) values ​​per band, where N is the time length in ms of DL PRS symbols processed per T ms for a given maximum bandwidth (B) in MHz supported by the UE. In general, the UE may not be expected to support DL PRS bandwidths that exceed this reported DL PRS bandwidth value. UE DL PRS processing capability may be defined for a single positioning frequency layer 700. UE DL PRS processing capability may not depend on a DL PRS comb coefficient configuration, such as that illustrated in FIG. 6. The UE processing capability may indicate the maximum number of DL PRS resources under which the UE can process in a slot.For example, the maximum number of FR1 bands may be 1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64 for each SCS: 15 kHz, 30 kHz, 60 kHz, and the maximum number of FR2 bands may be 1, 2, 4, 6, 8, 12, 16, 24, 32, 48, 64 for each SCS: 15 kHz, 30 kHz, 60 kHz, 120 kHz.

[0086] 8, an example message flow 800 for extending a Mobile-Originated Location Request (MO-LR) procedure to enable on-demand DL-PRS is shown. The example message flow 800 includes a UE 105, three example TRPs 300, such as a first gNB1 110a, a gNB2 110b, and a third gNB3 110c, and elements of the core network 140, such as the AMF 115 and the LMF 120. The message flow 800 may be used to extend an existing MO-LR procedure for requesting assistance data (e.g., for DL-TDOA, DL-AoD, or multi-RTT). For example, the UE 105 may be configured to request assistance data from the LMF 120 for UE-assisted or UE-based positioning using one or more of the positioning methods and may include an additional parameter to indicate a preference for DL-PRS.The additional parameters may, for example, describe the desired PRS configuration, a preferred time or duration for the PRS configuration (e.g., current time, start time and stop time), a preferred PRS resource bandwidth, a preferred time length for the PRS positioning occasion, a preferred periodicity for the PRS positioning occasion, a preferred carrier frequency or frequency tier for the PRS resources, a preferred number and location of gNBs / TRPs for which the PRS configuration is requested around the UE's location, where the location of the gNBs / TRPs may be specified using PCI or CGI, or may be expressed in absolute global coordinates, or a zone identifier (e.g., NR The PRS parameters may include one or more of the following: a preferred number and locations of gNBs / TRPs, which may be specified as a particular location or geographical area, which may be expressed using a zone ID (similar to a zone ID used in Rel-16 sidelink) or using coordinates relative to a known reference location (such as the location of a particular cell, such as a serving cell, provided to the UE in assistance data); one or more directions of a preferred PRS beam for individual gNBs, RSRP, or RSRQ measurements (e.g., radio resource management (RRM) measurements) performed by the UE on available DL signals; quality of service (QoS) parameters describing the accuracy and latency of the target location (e.g., desired accuracy and response time for any location estimation based on PRS measurements (e.g., as requested by a UE internal client (e.g., app)); and PRS capabilities of the UE (e.g., as defined for LPP). Other parameters may also be used based on the configuration and capabilities of the respective gNBs and UEs.

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

[0088] Referring to message flow 800, in stage 0, the UE 105 may receive a location request from an internal client (e.g., an app). The UE 105 may determine that a change in DL-PRS transmission is needed to meet QoS requirements from the application (e.g., increased DL-PRS bandwidth, increased duration of positioning occasions (e.g., increased PRS resource repetition factor), DL-PRS transmission from a closer gNB, etc.). In stage 1, when the UE 105 is in a CM-IDLE state, the UE 105 may be configured to trigger a UE-initiated service request as defined in section 4.2.3.2 of 3GPP TS 23.502 to establish a signaling connection with the AMF. During this stage, the AMF 115 may inform the UE 105 that it can support MO-LR for on-demand DL-PRS requests, for example, in a 5GS Network Capability Support information element defined in 3GPP TS 24.501. In stage 2, the UE 105 is configured to send an MO-LR request message included in a UL NAS TRANSPORT message containing a request for a change in DL-PRS transmission to the serving AMF 115. This request may include the UE's 105 DL-PRS capabilities (e.g., in the embedded LPP Capability Provision message) and parameters for a preferred DL-PRS configuration (which may include a preferred DL-PRS bandwidth, a preferred duration of DL-PRS positioning occasions, a preferred DL-PRS beam direction for a gNB if known by 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 Assistance Data message included in the MO-LR request. In one example, the request for a change (e.g., an increase) in DL-PRS transmission may also include a quality of service (QoS) indicator, such as a required accuracy of the position estimate and / or a response time indicating when the internal client needs a position estimate. The MO-LR request message may also include a time length for how long the requested DL-PRS configuration is needed at the UE (eg, the number of seconds or minutes the DL-PRS configuration is needed).The MO-LR request may also include (e.g., in an embedded LPP location information provision message) RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID location measurement reports) received by the UE to assist the LMF120 in determining beam directions for nearby gNBs and / or DL-PRSs.

[0089] In stage 3, the AMF 115 selects the LMF 120 (e.g., as described in 3GPP TS 23.273, section 5.1), and in stage 4, the AMF 115 invokes an Nlmf_Location_DetermineLocation service operation on the LMF 120. The service operation may indicate one or more of: (i) a request for assistance data, (ii) a request for an on-demand DL-RS, or (iii) an MO-LR request. The service operation may also include the MO-LR request received in stage 2, any LPP messages received in stage 2 that were included in the MO-LR request in stage 2, and / or a list of assistance data types for which the UE 105 has a subscription.

[0090] In stage 5, the LMF 120 may first verify that the UE 105 has a subscription to request a new DL-PRS configuration based on the list of assistance data types for which the UE 105 has subscriptions received in stage 4. Based on the request in stage 4, the LMF 120 may then be configured to determine a new DL-PRS configuration (or multiple configurations) for nearby gNBs in stage 5 (e.g., based on the preferred number of gNBs indicated in stage 2). The determination in stage 5 may also be based on DL-PRS requests received from other UEs in stage 2 and / or location procedures of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-c may use a modified (e.g., increased) DL-PRS bandwidth, a modified (e.g., longer) time length of DL-PRS positioning occasions, DL-PRS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In an example, the new DL-PRS configuration may be selected from one set of one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in the positioning frequency layer 700. In a network with beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each gNB 110a-c to be received by the UE 105. The directional DL-PRS beam may be selected by the LMF 120 according to the known approximate location of the target UE 105, for example, as given by the coverage area of ​​a serving or camped-on cell for the UE 105 and / or the RSRP / ECID measurement results provided by the UE 105 in stage 2.

[0091] In step 6, the LMF 120 is configured to send an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, the NRPPa PRS configuration request message including requested DL-PRS transmission characteristics defining a new DL-PRS configuration to be determined for that gNB. For example, the LMF 120 may include parameter values ​​defining a new DL-PRS configuration to be determined for a gNB 110 in the NRPPa PRS configuration request message sent to that gNB 110. The request may also include a start time and duration (e.g., as requested by the UE in step 2 or as determined by the LMF in step 5) of each new DL-PRS configuration. In step 7, each of the gNBs 110a-c may return a response to the LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs 110a-c indicate that they cannot support the new DL-PRS configuration, LMF 120 may perform steps 15 and 16 to restore the old DL-PRS configuration in each of the gNBs that indicated that they can support the new DL-PRS configuration, in order to avoid interference between gNBs 110 that support the new DL-PRS configuration and gNBs 110 that do not. In this case, LMF 120 may provide the old DL-PRS configuration to the UE in step 9 instead of the new DL-PRS configuration.

[0092] In step 8, each of the gNBs 110a-c that acknowledged support for the new DL-PRS configuration in step 7 changes from the old DL-PRS configuration to the new DL-PRS configuration either after (or just before) sending an acknowledgment in step 7 if no start time was provided, or at the start time indicated in step 6. In some cases, the old DL-PRS configuration may correspond to not transmitting DL-PRS. In some cases, the start time for switching to the new DL-PRS configuration may result in transmitting the new DL-PRS after steps 9 or 10 / 11. This may typically be the case when the new DL-PRS configuration consists of a single or a few DL-PRS opportunities. In step 9, the LMF 120 transmits an LPP Provide Assistance Data message to the target UE 105 to provide the new DL-PRS configuration determined in step 5 and acknowledged in step 7. For example, the LMF 120 may include parameter values ​​defining each of the new DL-PRS configurations determined in step 5 in the Provide LPP Assistance Data message and may indicate the cell, gNB 110, and / or TRP to which each DL PRS configuration applies. In step 10, once the Assistance Data with the new DL-PRS configurations is forwarded to the UE 105, the LMF 120 returns an Nlmf_Location_DetermineLocation response to the AMF 115. The response in step 10 (or the message in step 9) may indicate whether the MO-LR request from step 2 can be supported (i.e., can be satisfied) and may include a start time and duration for each new DL-PRS configuration (e.g., if different from those requested by the UE 105 in step 2 and determined by the LMF 120 in step 5). The start time and duration for the new DL-PRS configuration may also be referred to as a validity time, expiration time, etc. for the LPP Provide Assistance Data message containing the DL-PRS configuration. If the on-demand DL-PRS request from stage 2 cannot be satisfied, the cause of the failure may be included in the service action in stage 10 or in the LPP assistance data provision in stage 9 .

[0093] In step 11, the AMF 115 forwards the response from step 10 to the target UE 105 in the form of an MO-LR response, which may indicate whether it can support (i.e., fulfill) the MO-LR request from step 2, and which may include the start time and duration of each new DL-PRS configuration if received in step 10, or may include any indication of failure received in step 10.

[0094] In step 12, the target UE 105 acquires and measures the DL-PRS transmitted by the gNBs 110a-c according to the new DL-PRS configuration provided in step 9. For example, the UE 105 may acquire RSTD measurement results. In step 13, the UE 105 determines its location based on the DL-PRS measurement results acquired in step 12 and the assistance data received in step 9. In step 14, the UE 105 provides a location estimate to the internal client that requested location in step 0. In step 15, if a time length for the new DL-PRS was not included in step 6, the LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including a request to restore the old DL-PRS configuration for each gNB 110a-c. The LMF 120 may use the determined time length for the DL-PRS from step 5 to determine when to perform step 15. In step 16, each of gNBs 110a-c returns a response to LMF 120 indicating whether it can restore the old DL-PRS configuration. In step 17, each of gNBs 110a-c begins transmitting the old DL-PRS configuration either once the length of time received in step 6 expires or after receiving and acknowledging a request to restore the old DL-PRS configuration in steps 15 and 16.

[0095] 9A and 9B show an example message flow 900 for extending a mobile-initiated location request procedure to enable on-demand DL-PRS and UL-PRS. The example message flow 900 includes a UE 105, three example TRPs 300, such as a first gNB1 110a, a gNB2 110b, and a third gNB3 110c, and elements of the core network 140, such as an AMF 115 and an LMF 120. The message flow 900 can be used to extend the existing MO-LR procedure for on-demand DL-PRS and UL-PRS initiated by the UE.

[0096] In stage 0, the UE 105 may receive a location request from an internal client (e.g., an app). The UE 105 is configured to determine that a change in DL-PRS transmission and UL-PRS is needed to meet QoS requirements from the application (e.g., increased PRS bandwidth, increased length of positioning occasions, DL-PRS transmission from a closer gNB, etc.). In stage 1, when the UE 105 is in a CM-IDLE state, the UE 105 may be configured to trigger a UE-initiated service request as defined in section 4.2.3.2 of 3GPP TS 23.502 to establish a signaling connection with the AMF 115. In stage 2, the UE 105 is configured to send an MO-LR request message to the serving AMF 115, the MO-LR request message being included in a UL NAS TRANSPORT message including a request for a change in DL-PRS transmission and UL-PRS configuration. The request may include the UE's 105 DL-PRS and UL-PRS capabilities and parameters for a preferred DL-PRS and UL-PRS configuration (e.g., these may include, for each preferred DL-PRS and UL-PRS configuration, a preferred PRS bandwidth, a preferred length of time for PRS positioning occasions, a preferred PRS beam direction, and / or a preferred number of nearby gNBs 110a-c to which this applies). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP Assistance Data Request message included in the MO-LR request. The request for a change (e.g., an increase) in PRS transmission may also include a quality of service (QoS) indicator, such as a required accuracy of the position estimate and / or a response time indicating when the position estimate is needed by the internal client. The MO-LR request message may also include a time length for how long the requested PRS configuration is needed at the UE (e.g., the number of seconds or minutes the DL-PRS and UL-PRS configuration is needed). The MO-LR request may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID location measurement reports) received by the UE to assist the LMF in determining beam directions for nearby gNBs and / or PRSs.

[0097] In stage 3, the AMF 115 is configured to select the LMF 120 (e.g., as described in 3GPP TS 23.273, section 5.1). In stage 4, the AMF 115 invokes an Nlmf_Location_DetermineLocation service operation to the LMF 120. The service operation may indicate one or more of: (i) a request for assistance data, (ii) a request for on-demand DL-PRS and / or UL-PRS, (iii) an MO-LR request. The service operation may also include the MO-LR request received in stage 2, any LPP messages received in stage 2 that were included in the MO-LR request in stage 2, and / or a list of assistance data types for which the UE 105 has a subscription.

[0098] In stage 5, the LMF 120 may first verify that the UE 105 has a subscription to request a new DL-PRS and UL-PRS configuration based on the list of assistance data types for which the UE 105 has a subscription received in stage 4. Then, in stage 5, based on the request in stage 4, the LMF 120 determines a new DL-PRS configuration for the nearby gNBs 110a-c (e.g., based on the preferred number of gNBs indicated in stage 2). The determination in stage 5 may also be based on DL-PRS requests received from other UEs in stage 2 and / or location procedures of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-c may use a modified (e.g., increased) DL-PRS bandwidth, a modified (e.g., longer) length of time for DL-PRS positioning occasions, DL-RPS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In an example, the new DL-PRS configuration may be selected from a set of one or more pre-configured sets of DL-PRS configuration parameters. In a network with beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each gNB 110a-c to be received by the UE 105. The directional DL-PRS beam may be selected by the LMF 120 according to, for example, the coverage area of ​​a serving or camped-on cell for the UE and / or the known approximate location of the target UE 105, as given by RSRP / ECID measurements provided by the UE 105 in stage 2. As an option in stage 5, the LMF 120 may determine, adjust, or modify one or more of the parameters for the preferred UL-PRS configuration, which may have possibly been transmitted by the UE 105 in stage 2 (and received by the LMF 120 in stage 4). For example, LMF120 may determine or modify such UL-PRS parameters, such as a preferred UL-PRS bandwidth and / or preferred duration of a UL-PRS positioning occasion, if such a determination or modification is indicated as supported by the UL-PRS capabilities of UE105 transmitted in stage 2.

[0099] In stage 6, the LMF 120 sends an NRPPa Positioning Information Request message to the serving gNB 110a to request a UL-PRS configuration for the target UE 105. The NRPPa Positioning Information Request message includes the desired UL-PRS configuration parameters from stage 2 or stage 5, if the parameters were determined or changed in stage 5.

[0100] In step 7, the serving gNB 110a of the target UE 105 determines a UL-PRS configuration according to the parameters received in step 6. If the request can be partially fulfilled, the gNB 110a selects possible configuration parameters, which may be different compared to the requested parameters in step 6. In step 8, the serving gNB 110a of the target UE 105 provides the UL-PRS configuration parameters to the LMF 120. In step 9, the serving gNB 110a of the target UE 105 provides the UL-PRS configuration parameters to the UE 105 in a radio resource control (RRC) message. In some examples, steps 6-9 may not be required if a UL-PRS configuration is also selected by the LMF 120 in step 5 (in addition to selecting a DL-PRS). In that case, the UL-PRS configuration parameters may be provided to the UE 105 in step 13. In step 10, the LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including requested DL-PRS transmission characteristics that define the new DL-PRS configuration to be determined for that gNB. The request may also include a start time and duration of each new DL-PRS configuration (e.g., as requested by the UE in step 2 or as determined by the LMF 120 in step 5). In step 11, each of the gNBs 110a-c returns a response to the LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs indicate that they cannot support the new DL-PRS configuration, the LMF 120 may perform steps 26 and 27 to restore the old DL-PRS configuration in each of the gNBs 110a-c that indicated that they can support the new DL-PRS configuration, in order to avoid interference between gNBs that support the new DL-PRS configuration and gNBs that do not. In this case, the LMF 120 may provide the UE with the old DL-PRS configuration in step 13 instead of the new DL-PRS configuration.

[0101] In step 12, each of the gNBs 110a-c that acknowledged support for the new DL-PRS configuration in step 11 changes from the old DL-PRS configuration to the new DL-PRS configuration either after (or just before) sending an acknowledgment in step 11 if no start time was provided, or at the start time indicated in step 10. In some cases, the old DL-PRS configuration may be equivalent to not transmitting DL-PRS. In step 13, the LMF 120 sends an LPP Provide Assistance Data message to the target UE 105 to provide the new DL-PRS configuration determined in step 5 and acknowledged in step 11 (e.g., to provide parameters defining these configurations). In step 14, the LMF 120 sends an NRPPa Positioning Activation Request message to the serving gNB 110a of the target UE 105 to request activation of the UL-PRS in the UE 105 according to the one or more configurations provided to the UE 105 in step 9. In step 15, the serving gNB 110a sends a MAC control element to the UE 105 to activate the UL-PRS as requested in step 14. If a start time was provided in step 14, the serving gNB 110a sends this command at the requested start time. In step 16, if the UL-PRS activation is successful, the serving gNB 110a returns an NRPPa Positioning Activation Response message to the LMF 120. If the requested start time provided in step 14 cannot be met, the serving gNB 110a may determine a different start time and provide the selected start time to the LMF 120. In step 17, the target UE 105 transmits the UL-PRS according to the activated configuration in step 15.

[0102] 9B, in step 18, the LMF 120 sends an NRPPa Measurement Request message to the gNBs 110a-c selected in step 5 to request UL-PRS measurements (e.g., gNB Rx-Tx time difference measurements). In step 19, once the assistance data with the new DL-PRS configuration is forwarded to the UE 105 and the NRPPa UL-PRS measurement request is enabled in the gNBs 110a-c, the LMF 120 returns an Nlmf_Location_DetermineLocation response to the AMF 115, which may indicate success or failure of the request sent by the AMF 115 in step 4. If the on-demand PRS request from step 2 cannot be fulfilled, the cause of the failure may be included in the service action in step 19 or the LPP assistance data provision in step 13. In step 20, the AMF 115 sends an MO-LR Response message to the target UE 105, which may indicate success or failure to support the MO-LR request as shown in step 19 and may include any cause of failure received in step 19.

[0103] 9A / B 。 Alternatively, steps 19 and 20 may occur later in the procedure of Figure 9A / B. In one alternative, steps 19 and 20 may occur after step 23 when both the LPP Provide Assistance Data message with DL-PRS configuration in step 13 and the LPP Provide Assistance Data message with UL-PRS measurements in step 23 have been provided to UE 105. In another alternative, steps 19 and 20 may occur after step 30 when there is an LPP Provide Assistance Data message with DL-PRS configuration in step 13, an LPP Provide Assistance Data message with UL-PRS measurements in step 23, and UL-PRS Deactivation in step 30.

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

[0105] In one example, the LMF 120 may determine the start time of switching to the new DL-PRS configuration (step 12) and enabling UL-PRS transmission (step 17) such that steps 12 and 17 occur approximately simultaneously (e.g., when a single or a few UL-PRS and DL-PRS opportunities are transmitted / requested). For example, the start time may be selected such that steps 12 and 17 occur together (e.g., after step 20). In step 22, the gNBs 110a-c provide the UL-PRS measurement results to the LMF 120. In step 23, the LMF 120 forwards the UL-PRS measurement results received in step 22 to the target UE 105 in an LPP Provide Assistance Data message.

[0106] In step 24, the UE 105 is configured to determine a location based on the DL-PRS measurements obtained in step 21a and the UL-PRS measurements received in step 23, and the assistance data received in step 13. In step 25, the UE 105 may provide a location estimate to an internal client that requested location in step 0.

[0107] In step 26, if a time length for a new DL-PRS was not included in step 10, LMF 120 may send an NRPPa PRS configuration request message to each of gNBs 110a-c determined in step 5, including a request to restore the old DL-PRS configuration for each gNB 110a-c. LMF 120 may use the determined time length for DL-PRS from step 5 to determine when to perform step 26. In step 27, each of gNBs 110a-c returns a response to LMF 120 indicating whether it can restore the old DL-PRS configuration. In step 28, each of gNBs 110a-c may start transmitting the old DL-PRS configuration either when the time length received in step 10 expires or after receiving and acknowledging the request to restore the old DL-PRS configuration in steps 26 and 27. At step 29, the LMF 120 may send an NRPPa Positioning Disable Request message to the serving gNB 110a of the target UE 105 to request the disabling of UE UL-PRS transmissions. , and sends a MAC Control element to the target UE to disable the

[0108] 10A and 10B, an example message flow 1000 is shown for extending an on-demand system information procedure to enable on-demand DL-PRS. The example message flow 1000 includes a UE 105, three example TRPs 300, such as a first gNB1 110a, a gNB2 110b, and a third gNB3 110c, and elements of the core network 140, such as an AMF 115 and an LMF 120. The message flow 1000 can be used to extend the on-demand system information (SI) procedure to request broadcast assistance data. The positioning assistance data can be provided via LPP point-to-point (unicast) or via positioning SI (broadcast). The positioning SI message containing DL-PRS assistance data can be broadcast periodically or upon request from the UE. In one example, the core network 140 may be configured to determine whether requested broadcast assistance data (i.e., positioning system information block (posSIB)) is provided using broadcast or point-to-point (unicast) via an RRC reconfiguration message. This procedure may be adapted for on-demand PRS. For example, a broadcast message (e.g., system information block 1 (SIB1) or broadcast assistance data element, etc.) may include an indicator of whether on-demand PRS is supported by the network. For example, the broadcast message may indicate on-demand-prs ENUMERATED {dl-prs, ul-prs, ul-and-dl-prs}.

[0109] This indicator (or an equivalent indicator) may also be used in conjunction with the example message flows 800 and 900 described above to indicate to the UE that on-demand PRS is supported in the network via the MO-LR procedure.

[0110] Referring to FIG. 10A , in stage 1, gNBs 110a-c in the network broadcast SIB1, which may include an indicator of whether on-demand DL-PRS is available / supported by the gNB. UE 105 may receive SIB1 from serving gNB 110a. In stage 2, UE 105 is configured to receive a location request from an internal client (e.g., an app). UE 105 may determine that a change in DL-PRS transmission is needed (e.g., increased DL-PRS bandwidth, increased duration of positioning occasions (e.g., increased PRS resource repetition factor), DL-PRS transmission from a closer gNB, etc.) to meet QoS requirements from the application. In stage 3, UE 105 sends an RRC dedicated SIB request message to the serving gNB to request on-demand DL-PRS (e.g., a request for a change in DL-PRS transmission). The request may include the UE's 105 DL-PRS capabilities and parameters for a preferred DL-PRS configuration (which may include a preferred DL-PRS bandwidth, a preferred length of time for DL-PRS positioning occasions, a preferred DL-PRS beam direction for a gNB if known by the UE), and a preferred number of nearby gNBs to which this applies. The request for increased DL-PRS transmission may also include a quality of service (QoS) indicator, such as a required accuracy of the position estimate and / or a response time indicating when the internal client needs a position estimate. The RRC dedicated SIB request message may also include a length of time for how long the requested DL-PRS configuration is needed at the UE (e.g., the number of seconds or minutes the DL-PRS configuration is needed). The RRC dedicated SIB request message may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., RRC measurement reports) received by the UE to assist the LMF 120 in determining beam directions for nearby gNBs and / or DL-PRS. In stage 4, the serving gNB 110a sends an NRPPa assistance information feedback message to the LMF 120.The message includes the on-demand DL-PRS request received from the UE 105 in stage 3.

[0111] In stage 5, based on the request in stage 4, the LMF 120 is configured to determine a new DL-PRS configuration for the nearby gNBs 110a-c (e.g., based on the preferred number of gNBs indicated in stage 3). The determination in stage 5 may also be based on DL-PRS requests received from other UEs in stage 3 and / or position location procedures of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB 110a-c may use a modified (e.g., increased) DL-PRS bandwidth, a modified (e.g., longer) length of time for DL-PRS positioning occasions, DL-RPS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In some cases, the new DL-PRS configuration may be selected from one of one or more pre-configured sets of DL-PRS configuration parameters. In a network with beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each gNB to be received by the UE 120. The directional DL-PRS beam may be selected by the LMF 120 according to the known approximate location of the target UE 105, for example, as given by the coverage area of ​​the serving cell or camp-on cell for the UE 105 and / or the RSRP measurement results provided by the UE in stage 3.

[0112] In step 6, the LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including requested DL-PRS transmission characteristics that define the new DL-PRS configuration to be determined for that gNB. The request may also include a start time and duration of each new DL-PRS configuration (e.g., as requested by the UE 105 in step 3 or as determined by the LMF 120 in step 5). In step 7, each of the gNBs 110a-c returns a response to the LMF 120 indicating whether the new DL-PRS configuration can be supported. If some of the gNBs 110a-c indicate that they cannot support the new DL-PRS configuration, the LMF 120 may perform steps 15 and 16 to restore the old DL-PRS configuration in each of the gNBs 110a-c that indicated that they cannot support the new DL-PRS configuration, in order to avoid interference between gNBs that support the new DL-PRS configuration and gNBs that do not. In this case, the LMF 120 provides the old DL-PRS configuration to the UE 105 in steps 9 and 10 instead of the new DL-PRS configuration.

[0113] In step 8, each of the gNBs 110a-c that acknowledged support for the new DL-PRS configuration in step 7 changes from the old DL-PRS configuration to the new DL-PRS configuration either after (or just before) sending an acknowledgment in step 7 if no start time was provided, or at the start time indicated in step 6. In some cases, the old DL-PRS configuration may be equivalent to not transmitting DL-PRS. In step 9, the LMF 120 is configured to send an NRPPa assistance information control message to the serving gNB 110a to provide the new DL-PRS configuration determined in step 5 and acknowledged in step 7. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and coding as defined for broadcast assistance data). In step 10, the serving gNB 110a is configured to provide the DL-PRS configuration information received in step 9 to the 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 as received in step 9. In step 11, the UE 105 acknowledges the RRC reconfiguration and returns an RRC reconfiguration complete message to the serving gNB.

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

[0115] In step 15, if a time length for a new DL-PRS was not included in step 6, the LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including a request to restore the old DL-PRS configuration for each gNB. The LMF 120 may use the determined time length for the DL-PRS from step 5 to determine when to perform step 15. In step 16, each of the gNBs 110a-c returns a response to the LMF 120 indicating whether it can restore the old DL-PRS configuration. In step 17, each of the gNBs 110a-c may start transmitting the old DL-PRS configuration either when the time length received in step 6 expires or after receiving and acknowledging the request to restore the old DL-PRS configuration in steps 15 and 16. In stage 18, the LMF 120 may be configured to send an NRPPa assistance information control message to the serving gNB, including posSIB information for the restored DL-PRS configuration.

[0116] 11A and 11B, an example message flow 1100 is shown for extending an on-demand system information procedure to enable on-demand DL-PRS and UL-PRS. The example message flow 1100 includes a UE 105 and includes three example TRPs 300, such as a first gNB1 110a, a gNB2 110b, and a third gNB3 110c, as well as elements of the core network 140, such as the AMF 115 and the LMF 120. The message flow 1100 may be used to extend an on-demand system information (SI) procedure to request broadcast assistance data.

[0117] Referring to FIG. 11A , in stage 1, gNBs 110a-c in the network broadcast SIB1, which may include an indicator of whether on-demand DL-PRS and UL-PRS are available / supported by the gNB. UE 105 may receive SIB1 from serving gNB 110a. In stage 2, UE 105 may receive a location request from an internal client (e.g., an app). UE 105 may determine that changes in DL-PRS transmission and UL-PRS are needed (e.g., increased PRS bandwidth, increased length of positioning occasion, DL-PRS transmission from a closer gNB, etc.) to meet QoS requirements from the application. In stage 3, UE 105 sends an RRC-dedicated SIB request message to serving gNB 110a to request on-demand DL-PRS transmission and UL-PRS configuration. The request may include the UE's DL-PRS and UL-PRS capabilities, as well as parameters for the preferred DL-PRS and UL-PRS configurations (which may include the preferred PRS bandwidth, the preferred length of time for PRS positioning occasions, the preferred PRS beam direction, and the preferred number of nearby gNBs to which this applies). The request for a change in PRS transmission may also include a quality of service (QoS) indicator, such as the required accuracy of the position estimate and / or a response time indicating when the internal client needs a position estimate. The RRC dedicated SIB request message may also include a length of time for how long the requested PRS configuration is needed at the UE 105 (e.g., the number of seconds or minutes the DL-PRS and UL-PRS configurations are needed). The RRC dedicated SIB request message may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., RRC measurement reports) received by the UE 105 to assist the LMF 120 in determining beam directions for nearby gNBs and / or PRSs.

[0118] In stage 4, the serving gNB 110a sends an NRPPa assistance information feedback message to the LMF 120. The message includes the on-demand DL-PRS and UL-PRS request received from the UE 105 in stage 3. In stage 5, based on the request in stage 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 stage 3). The determination in stage 5 may also be based on DL-PRS requests received from other UEs in stage 3 and / or location procedures of other UEs occurring approximately simultaneously. The new DL-PRS configuration for each gNB may use increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-PRS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In some cases, the new DL-PRS configuration may be selected from one or more pre-configured sets of DL-PRS configuration parameters. In a network utilizing beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each gNB to be received by the UE 105. The directional DL-PRS beam may be selected by the LMF 120 according to, for example, the coverage area of ​​a serving cell or camp-on cell for the UE 105 and / or the known approximate location of the target UE 105, as given by RSRP measurement results provided by the UE 105 in stage 3. In stage 6, the LMF 120 sends an NRPPa Positioning Information Request message to the serving gNB 110a to request a UL-PRS configuration for the target UE 105. The NRPPa Positioning Information Request message includes the desired UL-PRS configuration parameters from stage 3. In stage 7, the serving gNB 110a of the target UE 105 determines the UL-PRS configuration according to the parameters received in stage 6. If the request can be partially met, gNB110a selects possible configuration parameters that may be different compared to the requested parameters in stage 6.In step 8, the serving gNB 110a of the target UE 105 provides the UL-PRS configuration parameters to the LMF 120. In step 9, the serving gNB 110a of the target UE 105 provides the UL-PRS configuration parameters to the UE 105 in an RRC message. In an embodiment, steps 6-9 may not be required if the UL-PRS configuration is also selected by the LMF 120 in step 5 (in addition to selecting the DL-PRS). In that case, the UL-PRS configuration parameters may be provided to the UE 105 in steps 13 / 14.

[0119] In step 10, the LMF 120 sends an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including the new DL-PRS configuration determined for that gNB. This request may also include the start time and duration of each new DL-PRS configuration (e.g., as requested by the UE 105 in step 3 or as determined by the LMF 120 in step 5). In step 11, each of the gNBs 110a-c returns a response to the LMF 120 indicating whether the new DL-PRS configuration can be supported. If some gNBs indicate that they cannot support the new DL-PRS configuration, the LMF 120 may perform steps 26 and 27 to restore the old DL-PRS configuration in each of the gNBs 110a-c that indicated that they can support the new DL-PRS configuration, in order to avoid interference between gNBs that support the new DL-PRS configuration and gNBs that do not. In this case, the LMF 120 may provide the UE 105 with the old DL-PRS configuration in steps 13 / 14 instead of the new DL-PRS configuration. In step 12, each of the gNBs 110a-c that acknowledged support for the new DL-PRS configuration in step 11 changes from the old DL-PRS configuration to the new DL-PRS configuration either after (or just before) transmitting an acknowledgment in step 11 if no start time was provided, or at the start time indicated in step 10. In some cases, the old DL-PRS configuration may be equivalent to not transmitting DL-PRS. In step 13, the LMF 120 sends an NRPPa assistance information control message to the serving gNB 110a to provide the new DL-PRS configuration determined in step 5 and acknowledged in step 11. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and coding as defined for broadcast assistance data).

[0120] In step 14, the serving gNB 110a may provide the UE with the DL-PRS configuration information received in step 13 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an OCTET STRING including the DL-PRS configuration in posSIB format as received in step 13. In step 15, the UE 105 acknowledges the RRC reconfiguration and returns an RRC reconfiguration complete message to the serving gNB 110a. In step 16, the LMF 120 sends an NRPPa Positioning Activation Request message to the serving gNB 110a of the target UE 105 to request activation of the UL-PRS in the UE 105 according to one or more configurations provided to the UE 105 in step 9. In step 17, the serving gNB 110a may send a MAC Control element to the UE 105 to activate the UL-PRS as requested in step 16. If a start time was provided in step 16, the serving gNB 110a may send this command at the requested start time. In step 18, if the UL-PRS is successfully activated, the serving gNB 110a returns an NRPPa Positioning Activation Response message to the LMF 120. If the requested start time provided in step 16 cannot be met, the serving gNB 110a may determine a different start time and provide the selected start time to the LMF 120.

[0121] 11B, where in step 19, the target UE 105 is configured to transmit an UL-PRS according to the enabled configuration in step 17. In step 20, the LMF 120 sends an NRPPa measurement request message to the gNBs 110a-c selected in step 5 to request an UL-PRS measurement (e.g., gNB Rx-Tx time difference measurement). In step 21a, the target UE acquires and measures the DL-PRS transmitted by the gNB according to the new DL-PRS configuration provided in step 14. In step 21b, the gNBs 110a-c that receive the measurement request in step 20 acquire and measure the UL-PRS transmitted by the target UE 105 in step 19. In step 22, the gNBs 110a-c may provide the UL-PRS measurement results to the LMF 120. In one example, the LMF 120 may determine the start times for switching to the new DL-PRS configuration (step 12) and enabling UL-PRS transmission (step 19) such that steps 12 and 19 occur approximately simultaneously (e.g., when a single or a small number of UL-PRS and DL-PRS opportunities are transmitted / requested). For example, the start times may be selected such that steps 12 and 19 occur together (e.g., after step 20).

[0122] In an embodiment, in step 23, the LMF 120 may forward the UL-PRS measurement results received in step 22 to the target UE 105 in an LPP Provide Assistance Data message. In step 24, the UE 105 may be configured to determine a location based on the DL-PRS measurement results obtained in step 21a and the UL-PRS measurement results received in step 23, and the assistance data received in step 14. In step 25, the UE 105 may be configured to provide a location estimate to an internal client that requested location in step 2.

[0123] In step 26, if a time length for a new DL-PRS was not included in step 10, the LMF 120 may send an NRPPa PRS configuration request message to each of the gNBs 110a-c determined in step 5, including a request to restore the old DL-PRS configuration for each gNB. The LMF 120 may use the determined time length for the DL-PRS from step 5 to determine when to perform step 26. In step 27, each of the gNBs 110a-c may return a response to the LMF 120 indicating whether it can restore the old DL-PRS configuration. In step 28, each of the gNBs 110a-c begins transmitting the old DL-PRS configuration either when the time length received in step 10 expires or after receiving and acknowledging the request to restore the old DL-PRS configuration in steps 26 and 27. At step 29, the LMF 120 may send an NRPPa Assistance Information control message to the serving gNB, including posSIB information for the restored DL-PRS configuration. At step 30, the LMF 120 may send an NRPPa Positioning Disable Request message to the serving gNB 110a of the target UE to request disabling of UE UL-PRS transmission. At step 31, the serving gNB 110a may send a MAC control element to the target UE 105 to disable UL-PRS transmission as requested in step 30.

[0124] Referring to FIG. 12 with further reference to FIGS. 1-11B, a method 1200 for determining a location of a mobile device using an on-demand positioning reference signal includes the steps shown. However, method 1200 is exemplary and not limiting. Method 1200 may be modified, for example, by adding, removing, reordering, combining, or simultaneously performing steps, and / or dividing a single step into multiple steps. Method 1200 may be performed by a UE, such as UE 105 of FIG. 1 or UE 200 of FIG. 2.

[0125] At stage 1202, the method includes sending a request for a downlink positioning reference signal to a network server (e.g., the AMF 115 or the LMF 120), the request including positioning reference signal configuration information. A mobile device such as the UE 200 is a means for sending (e.g., transmitting) the request for the downlink positioning reference signal. In an embodiment, the UE 200 may receive a position location request from an internal application and determine that an increased DL-PRS bandwidth, an increased duration of the positioning occasion, and / or DL-PRS transmission from a closer gNB may be needed to meet QoS requirements from the application. In an example, the UE 200 may send an MO-LR request message included in an UL NAS TRANSPORT message including the request for the increased DL-PRS transmission to the serving AMF 115. The request may include the UE's 200 DL-PRS capabilities and parameters for a preferred DL-PRS configuration (e.g., a preferred DL-PRS bandwidth, a preferred length of time for DL-PRS positioning occasions, a preferred DL-PRS beam direction, and a preferred number of nearby gNBs, etc.). The requested DL-PRS configuration parameters may be provided in an LPP Request Assistance Data message included in the MO-LR request. In an example, the request for increased DL-PRS transmission may also include a quality of service (QoS) indicator, such as a required accuracy of the position estimate and / or a response time indicating when the internal client needs a position estimate. The MO-LR request message may also include a length of time for how long the requested DL-PRS configuration is needed at the UE 200. The MO-LR request may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID position measurement reports) received by the UE 200 to assist the LMF 120 in determining beam directions for nearby gNBs and / or DL-PRS.

[0126] In another embodiment, UE 200 may be configured to send an RRC dedicated SIB request message to a serving gNB to request on-demand DL-PRS (e.g., a request for increased DL-PRS transmission). This request may include UE 200's DL-PRS capabilities and parameters for a preferred DL-PRS configuration (e.g., a preferred DL-PRS bandwidth, a preferred length of time for DL-PRS positioning occasions, a preferred DL-PRS beam direction for a gNB, a preferred number of nearby gNBs, etc.). The request may also include a QoS indicator, such as a required accuracy of the position estimate and / or a response time indicating when an internal client requests a position estimate. The RRC dedicated SIB request message may also include a length of time for how long the requested DL-PRS configuration is needed at the UE (e.g., the number of seconds or minutes for which the DL-PRS configuration is needed). The RRC dedicated SIB request message may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., RRC measurement reports) received by UE200 to assist LMF120 in determining beam directions for nearby gNBs and / or DL-PRSs.

[0127] In an embodiment, a request for a downlink positioning reference signal may be provided to the LMF 120 from the AMF 115, a previously serving AMF, a previously serving LMF, and / or a previously serving TRP 300, such as the gNB 110a. For example, there may be a handoff between serving cells (e.g., serving TRPs), and the request for a downlink positioning reference signal may be a persistent request for a particular length of time.

[0128] At stage 1204, the method includes receiving assistance data based on the positioning reference signal configuration information. UE 200 is a means for receiving the assistance 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 at stage 1202. This determination may also be based on DL-PRS requests received from other UEs and / or location procedures of other UEs occurring approximately simultaneously. The new DL-PRS configuration may use increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-PRS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In an example, the new DL-PRS configuration may be selected from a set of one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in positioning frequency layer 700. In a network with beamformed DL-PRS, the LMF 120 may determine directional DL-PRS beams for various gNBs that may be received by the UE 200. The directional DL-PRS beams may be selected by the LMF 120 according to the known approximate location of the UE 200, for example, as given by the coverage area of ​​a serving or camped-on cell for the UE 105 and / or the RSRP / ECID measurement results provided by the UE 200 in stage 1202.

[0129] In one embodiment, the LMF 120 may be configured to send an NRPPa assistance information control message to the serving gNB 110a to provide the new DL-PRS configuration. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and encoding as defined for broadcast assistance data). The serving gNB 110a may be configured to provide the DL-PRS configuration information to the UE 200 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an OCTET STRING containing the DL-PRS configuration, in posSIB format.

[0130] At step 1206, the method includes measuring one or more downlink positioning reference signals based at least in part on the downlink positioning reference signal configuration information. The UE 200 is a means for measuring the one or more downlink positioning reference signals. The UE 200 is configured to acquire and measure DL-PRS transmitted by the gNBs 110a-c according to the DL-RS configuration provided in the assistance data received at step 1204. For example, but not limited to, the UE 200 may obtain RSTD measurements based on the DL-PRS transmissions. The UE 200 may be configured to obtain other measurements based on the DL-PRS transmissions.

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

[0132] 1-11B, a method 1300 for providing assistance data for an on-demand positioning reference signal includes the steps shown. However, method 1300 is exemplary and not limiting. Method 1300 may be modified, for example, by adding, removing, reordering, combining, or simultaneously performing steps, and / or dividing a single step into multiple steps. Operations 1300 may be performed by a server or location server (e.g., by LMF 120 of FIG. 1 or server 400 of FIG. 4).

[0133] At stage 1302, the method includes receiving a request for a downlink positioning reference signal (e.g., transmitted by a UE such as UE 105), the request including positioning reference signal configuration information. A server 400, such as the LMF 120, is a means for receiving the request for DL-PRS. In an embodiment, the UE 200 may be configured to send an MO-LR request message to the serving AMF 115 included in a UL NAS TRANSPORT message including a request for increased DL-PRS transmission. The request may include configuration information such as the UE 200's DL-PRS capabilities and parameters for a preferred DL-PRS configuration (e.g., a preferred DL-PRS bandwidth, a preferred duration of a DL-PRS positioning occasion, a preferred DL-PRS beam direction, and a preferred number of nearby gNBs). The requested DL-PRS configuration parameters may be provided in an LPP Request Assistance Data message included in the MO-LR request. In one example, the request for increased DL-PRS transmission may also include a quality of service (QoS) indicator, such as the required accuracy of the location estimate and / or a response time indicating when the internal client requests a location estimate. The MO-LR request message may also include a time length for how long the requested DL-PRS configuration is needed at the UE 200. The MO-LR request may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID location measurement reports) received by the UE 200 to assist the LMF 120 in determining beam directions for nearby gNBs and / or DL-PRS. The AMF 115 may invoke a Nlmf_Location_DetermineLocation service operation to the LMF 120. The service operation may include the MO-LR request received from the UE 200.

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

[0135] At stage 1304, the method includes determining, based on the positioning reference signal configuration information, one or more base stations for providing downlink positioning reference signals. The server 400 is a means for determining the one or more base stations. In an embodiment, the LMF 120 may be configured to determine a new DL-PRS configuration for nearby base stations (e.g., gNBs) based at least in part on the configuration information. For example, the new DL-PRS configuration for each base station may use an increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-PRS transmissions on new frequencies, and / or a higher frequency of DL-PRS positioning occasions. In an example, the new DL-PRS configuration may be selected from one of one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in the positioning frequency layer 700. In a network with beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each base station to be received by the UE 105. The directional DL-PRS beam may be selected by the LMF 120 according to the known approximate location of the target UE 105, for example, as given by the coverage area of ​​the serving cell or camp-on cell for the UE 105 and / or the RSRP / ECID measurement results provided in the request for DL-PRS received in step 1302.

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

[0137] At stage 1308, the method includes providing assistance data based on the positioning reference configuration information. The server 400 is a means for providing assistance data. In one embodiment, the LMF 120 may be configured to send an LPP Provide Assistance Data message to the target UE 105 to provide the new DL-PRS configuration. In another embodiment, the LMF 120 may be configured to send an NRPPa Assistance Information control message to the serving base station to provide the new DL-PRS configuration. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and coding as defined for broadcast assistance data). The serving base station may be configured to provide the DL-PRS configuration information to the UE 105 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an OCTET STRING containing the DL-PRS configuration in the posSIB format as received.

[0138] Referring to FIG. 14 with further reference to FIGS. 1-11B, a method 1400 for determining a location of a mobile device using on-demand downlink and uplink positioning reference signals includes the steps shown. However, method 1400 is exemplary and not limiting. Method 1400 may be modified, for example, by adding, removing, reordering, combining, or simultaneously performing steps, and / or dividing a single step into multiple steps. Operations 1400 may be performed by a UE, such as UE 105 of FIG. 1 or UE 200 of FIG. 2.

[0139] At stage 1402, the method includes sending a request for downlink and uplink positioning reference signals to a network server, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information. The UE 200 is a means for sending (e.g., transmitting) the request for DL-PRS and UL-PRS. In an embodiment, the UE 200 may be configured to send an MO-LR request message to the serving AMF 115 included in an UL NAS TRANSPORT message including a request for increased DL-PRS transmission and UL-PRS configuration. The request may include the UE 105's DL-PRS and UL-PRS capabilities and parameters for a preferred DL-PRS and UL-PRS configuration (e.g., a preferred PRS bandwidth, a preferred duration of PRS positioning occasions, a preferred PRS beam direction, and a preferred number of nearby gNBs 110a-c to which this applies). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP Request Assistance Data message included in the MO-LR request. The request for increased PRS transmission may also include a QoS indicator, such as the required accuracy of the position estimate and / or a response time indicating when the internal client needs the position estimate. The MO-LR request message may also include a time length for how long the requested PRS configuration is needed at the UE 200 (e.g., the number of seconds or minutes the DL-PRS and UL-PRS configurations are needed). The MO-LR request may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID location measurement reports) received by the UE to assist the LMF in determining beam directions for nearby gNBs and / or PRSs.

[0140] In an embodiment, the UE 105 may be configured to send an RRC dedicated 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 previously described. The RRC dedicated SIB request message may also include a time length for how long the requested PRS configuration is needed at the UE 105 (e.g., the number of seconds or minutes the DL-PRS and UL-PRS configuration is needed). The RRC dedicated SIB request message may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., RRC measurement reports) received by the UE 105 to assist the LMF 120 in determining beam directions for nearby gNBs and / or PRSs.

[0141] At step 1404, the method includes receiving uplink configuration parameters based on the uplink positioning reference signal configuration information. The UE 200 is a means for receiving the UL-PRS configuration parameters. In one example, the serving gNB of the UE 200 may provide the UL-PRS configuration parameters to the UE 105 in a radio resource control (RRC) message. In another example, the LMF 120 may be configured to send an LPP Assistance Data Provide message to the UE 200 to provide the UL-PRS configuration parameters. In another example, the LMF 120 may be configured to send an NRPPa Assistance Information Control message to the serving gNB for the UE 200 to provide the UL-PRS configuration parameters. The UL-PRS configuration parameters may be provided in the form of a posSIB (i.e., using parameters and encoding as defined for broadcast assistance data). The serving gNB may provide the UL-PRS configuration parameters to the UE 200 in a dedicated (unicast) RRC reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an OCTET STRING including the UL-PRS configuration parameters.

[0142] At step 1406, the method includes transmitting one or more uplink positioning reference signals based on the uplink positioning reference signal configuration information provided at step 1402 and received at step 1404. UE 200 is a means for transmitting the UL-PRS. In an example, the serving gNB may transmit a MAC CE (or other information element provided encapsulated or not at Layer 1 (i.e., physical layer) or Layer 2 (i.e., MAC layer)) to UE 105 to enable the UL-PRS. UE 200 is configured to transmit the UL-PRS based on the MAC CE.

[0143] At stage 1408, the method includes receiving first assistance data based on downlink positioning reference signal configuration information and one or more uplink positioning reference signals. UE 200 is a means for receiving the first assistance data. In an embodiment, LMF 120 is configured to transmit an LPP Provide Assistance Data message to UE 200 to provide a DL-PRS configuration based on the DL-PRS configuration information provided at stage 1402. In another embodiment, LMF 120 may be configured to transmit an NRPPa Assistance Information control message to the serving gNB to provide a DL-PRS configuration based on the DL-PRS configuration information provided at stage 1402. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and coding as defined for broadcast assistance data). In one 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 in posSIB format that includes the DL-PRS configuration.

[0144] At step 1410, the method includes measuring one or more downlink positioning reference signals based at least in part on the positioning reference signal configuration information. The UE 200 is a means for measuring one or more DL-PRSs. The UE 200 is configured to acquire and measure the DL-PRSs transmitted by the gNBs 110a-c according to the DL-RS configurations provided in the assistance data received at step 1408. For example, without limitation, the UE 200 may obtain UE receive (Rx)-transmit (Tx) time difference measurements based on the DL-PRS reception and the UL-PRS transmission. The UE 200 may be configured to obtain other measurements based on the DL-PRS and / or the UL-PRS transmission.

[0145] At step 1412, the method includes receiving second assistance data based on one or more uplink positioning reference signal measurements. UE 200 is a means for receiving the second assistance data. In an example, LMF 120 is also configured to forward UL-PRS measurements received from the base station to UE 200 as the second assistance data in an LPP Provide Assistance Data message (i.e., based on the UL-PRS transmitted by UE 200 at step 1406). The UL-PRS measurements may be measurements of a gNB Rx-Tx time difference.

[0146] At step 1414, the method includes determining a 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 exemplary means for determining a location. UE 200 is configured to determine a location based on DL-PRS measurements obtained at step 1206 and UL-PRS measurements and assistance data received at step 1412. For example, UE 200 may utilize UE Rx-Tx time difference measurements and gNB Rx-Tx time difference measurements to determine distances to multiple gNBs, and utilize the locations of the gNBs to determine a current location using a multi-RTT positioning technique. Other known positioning techniques, such as OTDOA, AoD, and ECID, may also be used to determine the location of UE 200.

[0147] 1-11B, a method 1500 for providing assistance data for on-demand downlink and uplink positioning reference signals includes the steps shown. However, method 1500 is exemplary and not limiting. Method 1500 may be modified, for example, by adding, removing, reordering, combining, or simultaneously performing steps, and / or dividing a single step into multiple steps. Operations 1500 may be performed by a server or location server (e.g., by LMF 120 of FIG. 1 or server 400 of FIG. 4).

[0148] At stage 1502, the method includes receiving a request for downlink and uplink positioning reference signals, the request including downlink positioning reference signal configuration information and uplink positioning reference signal configuration information. A server 400, such as the LMF 120, is a means for receiving the DL-PRS and UL-PRS request. In an embodiment, the UE 200 may be configured to send an MO-LR request message to the serving AMF 115, the MO-LR request message being included in an UL NAS TRANSPORT message including a request for increased DL-PRS transmission and UL-PRS configuration information. The request may include configuration information such as the UE 200's DL-PRS and UL-PRS capabilities and parameters for a preferred DL-PRS and UL-PRS configuration (e.g., a preferred DL-PRS bandwidth, a preferred duration of a DL-PRS positioning occasion, a preferred DL-PRS beam direction, and a preferred number of nearby gNBs). The requested DL-PRS and UL-PRS configuration parameters may be provided in an LPP Request Assistance Data message included in the MO-LR request. In one example, the request for increased DL-PRS transmission may also include a quality of service (QoS) indicator, such as the required accuracy of the location estimate and / or a response time indicating when the internal client needs the location estimate. The MO-LR request message may also include a time length for how long the requested PRS configuration is needed at the UE 200. The MO-LR request may also include RSRP measurement results (e.g., per beam) of DL signals (e.g., E-CID location measurement reports) received by the UE 200 to assist the LMF 120 in determining beam directions for nearby gNBs and / or DL-PRS. The AMF 115 may invoke a Nlmf_Location_DetermineLocation service operation to the LMF 120. The service operation may include the MO-LR request received from the UE 200.

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

[0150] At stage 1504, the method includes determining, based on the downlink positioning reference signal configuration information, one or more base stations for providing downlink positioning reference signals. The server 400 is means for determining the one or more base stations. In an embodiment, the LMF 120 may be configured to determine a new DL-PRS configuration for nearby base stations (e.g., gNBs) based at least in part on the configuration information. For example, the new DL-PRS configuration for each base station may use an increased DL-PRS bandwidth, a longer duration of DL-PRS positioning occasions, DL-RPS transmissions on a new frequency, and / or a higher frequency of DL-PRS positioning occasions. In an example, the new DL-PRS configuration may be selected from a set of one or more pre-configured sets of DL-PRS configuration parameters, such as PRS resources in the positioning frequency layer 700. In a network with beamformed DL-PRS, the LMF 120 may determine a directional DL-PRS beam for each base station to be received by the UE 105. The directional DL-PRS beam may be selected by the LMF 120 according to the known approximate location of the target UE 105, for example, as given by the coverage area of ​​the serving cell or camp-on cell for the UE 105 and / or the RSRP / ECID measurement results provided in the request for DL-PRS received in step 1502.

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

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

[0153] At step 1510, the method includes receiving uplink positioning reference signal measurement information from one or more base stations, for example, from one or more base stations determined at step 1504. The server 400 is a means for receiving UL-PRS measurement results. The base stations (e.g., gNBs 110a-c) are configured to acquire and measure the UL-PRS transmitted by the UE 200. In an example, the LMF 120 may determine a start time for switching to a new DL-PRS configuration and enabling UL-PRS transmission. The base stations are configured to provide the obtained UL-PRS measurement results to the LMF 120.

[0154] At stage 1512, the method includes transmitting assistance data based on the downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information. The server 400 is a means for sending (e.g., transmitting) the assistance data. In an embodiment, the LMF 120 may be configured to transmit an LPP Provide Assistance Data message to the target UE 105 to provide the new DL-PRS configuration. The LMF 120 is also configured to forward the UL-PRS measurement results of stage 1510 to the target UE 105 in the LPP Provide Assistance Data message.

[0155] In another embodiment, the LMF 120 may be configured to send an NRPPa Assistance Information control message to the serving base station to provide the new DL-PRS configuration. The DL-PRS configuration information may be provided in the form of a posSIB (i.e., using parameters and encoding as defined for broadcast assistance data). The serving base station may be configured to provide the DL-PRS configuration information to the UE 105 in a dedicated (unicast) RRC Reconfiguration message. The dedicatedPosSysInfoDelivery may consist of an OCTET STRING containing the DL-PRS configuration in the posSIB format as received. The LMF 120 may forward the UL-PRS measurement results of stage 1510 to the target UE 105 in an LPP Provide Assistance Data message.

[0156] 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 may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features that implement the functions may also be physically located in different locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0157] Functional or otherwise components shown in the figures and / or discussed herein as being connected to or in communication with each other are, unless otherwise stated, communicatively coupled, i.e., the components may be directly or indirectly connected so as to enable communication therebetween.

[0158] As used herein, the singular forms "a," "an," and "the" include the plural forms unless the context clearly dictates otherwise. For example, "a processor" may include one processor or multiple processors. As used herein, the terms "comprises," "comprising," "includes," and / or "comprising" 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 groups thereof.

[0159] As used herein, unless otherwise stated, a statement that a function or operation is "based on" an item or condition 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 in addition to the stated item or condition.

[0160] Also, as used herein, "or" in a list of items (which may be preceded by "at least one of" or "one or more of") indicates a disjunctive list, such as a list of "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 or B or C" meaning A, or B, or C, or AB (A and B), or AC (A and C), or BC (B and C), or ABC (i.e., A and B and C), or a combination of two or more features (e.g., AA, AAB, ABBC, etc.). Thus, stating that an item, e.g., a processor, is configured to perform a function with respect to at least one of A or B, or that an item is configured to perform function A or function B, means that the item can be configured to perform the function with respect to A, or can be configured to perform the function with respect to B, or can be configured to perform the function with respect to 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 may be configured to measure A (and may or may not be configured to measure B), or may be configured to measure B (and may or may not be configured to measure A), or may be configured to measure A and measure B (and may be configured to select whether to measure A or B, or to select both A and B). Similarly, a reference to a means for measuring at least one of A or B includes a means for measuring A (which may or may not be able to measure B), or a means for measuring B (which may or may not be configured to measure A), or a means for measuring A and B (which may be able to select whether to measure A or B, or to select both A and B).As another example, a statement that an item, e.g., a processor, is configured to at least one of perform function X or perform function Y means that the item may be configured to perform function X, or may be configured to perform function Y, or may be configured to perform function X and then perform function Y. For example, the phrase "a processor configured to perform at least one of measuring X or measuring Y" means that the processor may be configured to measure X (and may or may not be configured to measure Y), or may be configured to measure Y (and may or may not be configured to measure X), or may be configured to measure X and measure Y (and may be configured to select whether to measure X or Y, or to select to measure both X and Y). Considerable variation may be made according to specific requirements. For example, customized hardware may also be used, and / or particular elements may be implemented in hardware, software executed by the processor (including portable software, such as applets), or both. Furthermore, connection to other computing devices, such as network input / output devices, may be utilized.

[0161] The systems and devices discussed above are examples. Various configurations may omit, substitute, or add various procedures or components as appropriate. For example, features described with respect to some configurations may be combined in various other configurations. Different aspects and elements of the configurations may be similarly combined. Also, technology evolves, and thus many of the elements are examples and do not limit the scope of the disclosure or claims.

[0162] A wireless communication system is a communication system in which communications are conveyed wirelessly, i.e., by electromagnetic and / or acoustic waves propagating through atmospheric space rather than through wires or other physical connections. A wireless communication network is configured to cause at least some, but not all, communications to be transmitted wirelessly. Furthermore, the term "wireless communication device" or similar terms does not require that the function of the device be exclusively, or even primarily, for communication, or that the device be a mobile device, but indicates that the device includes wireless communication capabilities (unidirectional or bidirectional), e.g., at least one radio for wireless communication (each radio being part of a transmitter, receiver, or transceiver).

[0163] Specific details are given in the description to provide a thorough understanding of example configurations (including implementations). However, the configurations may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques are shown without unnecessary detail to avoid obscuring the configurations. This description provides example configurations and does not limit the scope, applicability, or configurations of the claims. Rather, the foregoing description of the configurations provides a description for implementing the described techniques. Various changes may be made in the function and arrangement of elements without departing from the scope of the present disclosure.

[0164] 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 causes a machine to operate in a specific manner. When using a computing platform, various processor-readable media may be involved in providing instructions / code to the processor for execution and / or may be used to store and / or carry such instructions / code (e.g., signals). In many implementations, processor-readable media are physical and / or tangible storage media. Such media may take many forms, including, but not limited to, non-volatile media and volatile media. Non-volatile media include, for example, optical and / or magnetic disks. Volatile media include, but are not limited to, dynamic memory.

[0165] A statement that a value exceeds (i.e., is greater than or exceeds) a first threshold is equivalent to a statement that the value meets or exceeds a second threshold that is slightly greater than the first threshold, e.g., the second threshold is a value higher than the first threshold at the resolution of the computing system. A statement that a value is less than (i.e., is within or below) a first threshold is equivalent to a statement that the value is equal to or less than a second threshold that is slightly less than the first threshold, e.g., the second threshold is a value lower than the first threshold at the resolution of the computing system. [Explanation of symbols]

[0166] 105 User Equipment 110 gNB 114 ng-eNB 115 AMF 117 SMF 120 LMF 125 GMLC 130 external clients 135 NG-RAN 140 5G cores 185 Constellation 190 Spacecraft 191 Spacecraft 192 Spacecraft 193 Spacecraft 200 User Equipment 210 processors 211 memory 212 Software 213 Sensors 214 Transceiver Interface 215 Transceiver 216 User Interface 217 SPS receiver 218 Camera 219 Positioning Devices 220 Bus 230 General Purpose / Application Processor 231 DSP 232 modem processor 233 Video Processor 234 Sensor Processor 240 Wireless Transceiver 242 Transmitter 244 receiver 246 Antenna 248 Wireless Signal 250 Wired Transceiver 252 Transmitter 254 receiver 260 SPS signal 262 Antenna 270 IMU 271 Magnetometer 272 Environmental Sensors 273 Accelerometer 274 Gyroscope 300 sending / receiving points 310 processor 311 memory 312 Software 315 Transceiver 317 SPS receiver 320 Bus 340 Wireless Transceiver 342 Transmitter 344 Receiver 346 Antenna 348 Wireless Signal 350 Wired Transceiver 352 Transmitter 354 Receiver 360 SPS signal 362 SPS Antenna 400 servers 410 processor 411 memory 412 Software 415 Transceiver 420 Bus 440 Wireless Transceiver 442 Transmitter 444 receiver 446 Antenna 448 Wireless Signal 450 Wired Transceiver 452 Transmitter 454 receiver 502 First PRS Resource Set 504 Second PRS Resource Set 602 2 symbols with com2 604 4 symbols with com4 606 com2 with 12 symbols 608 12 symbols with com4 610 6 Com with symbols 6 612 com 12 with 12 symbols 614 6 symbols with com2 616 12 symbols with com6

Claims

1. 1. A method performed by a mobile device for determining a location of the mobile device, comprising: sending an assistance data request for a downlink positioning reference signal to a network side, the assistance data request including on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including one or both of a start time and a duration for the on-demand positioning reference signal; receiving assistance data with updated on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information being determined by the network side based on the on-demand positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the updated on-demand positioning reference signal configuration information; determining the position based at least in part on measurements obtained from the one or more downlink positioning reference signals and the assistance data.

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

3. The method of claim 1 , wherein the assistance data request for the downlink positioning reference signal is a radio resource control (RRC) dedicated system information block (SIB) request.

4. 2. The method of claim 1, wherein the on-demand positioning reference signal configuration information includes at least one of a quality of service indicator, a time length indicating how long the requested downlink positioning reference signal is needed by the mobile device, and a reference signal received power (RSRP) measurement result of a downlink signal received by the mobile device.

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

6. The method of claim 1 , wherein receiving the assistance data comprises receiving a radio resource control (RRC) reconfiguration message.

7. 2. The method of claim 1, wherein receiving the assistance data comprises receiving a LTE Positioning Protocol (LPP) Provide Assistance Data message including a start time and a duration for the one or more downlink positioning reference signals.

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

9. 1. A network-side implemented method for providing location information to a mobile device, comprising: receiving, from the mobile device, a request for assistance data for a downlink positioning reference signal, the request for assistance data including on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including one or both of a start time and a duration for an on-demand positioning reference signal; determining one or more base stations to provide the downlink positioning reference signal based on the on-demand positioning reference signal configuration information; providing the on-demand positioning reference signal configuration information to the one or more base stations; and providing assistance data to the mobile device with updated on-demand positioning reference signal configuration information, the assistance data being determined based on the on-demand positioning reference signal configuration information.

10. 1. A method performed by a mobile device for determining a location of the mobile device, comprising: sending an assistance data request for downlink and uplink positioning reference signals to a network side, the assistance data request including on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information including one or both of a start time and a duration for the downlink on-demand positioning reference signal; receiving uplink configuration parameters determined by the network side based on the uplink positioning reference signal configuration information; transmitting one or more uplink positioning reference signals based on the uplink configuration parameters; receiving first assistance data with updated on-demand downlink positioning reference signal configuration information, the first assistance data being determined by the network side based on the on-demand downlink positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the updated on-demand downlink positioning reference signal configuration information; receiving second assistance data based on the one or more uplink positioning reference signal measurements; determining the position based at least in part on measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements included in the second assistance data.

11. 1. A network-side performed method for providing location information to a mobile device, comprising: receiving, from the mobile device, a request for assistance data for downlink and uplink positioning reference signals, the request for assistance data including on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information including one or both of a start time and a duration for the on-demand downlink positioning reference signal; determining one or more base stations for providing downlink positioning reference signals based on the on-demand downlink positioning reference signal configuration information; requesting at least one of the one or more base stations to measure an uplink positioning reference signal; providing the on-demand 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; transmitting assistance data to the mobile device based on the on-demand downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information.

12. Memory and 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: transmitting, via the at least one transceiver, a request for assistance data for a downlink positioning reference signal to a network side, the request for assistance data including on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including one or both of a start time and a duration for the on-demand positioning reference signal; receiving, via the at least one transceiver, assistance data with updated on-demand positioning reference signal configuration information, the updated on-demand positioning reference signal configuration information being determined by the network side based on the on-demand positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the updated on-demand positioning reference signal configuration information; determining a position based at least in part on measurements obtained from the one or more downlink positioning reference signals and the assistance data; The apparatus is configured to:

13. Memory and 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: receiving, via the at least one transceiver, a request for assistance data for a downlink positioning reference signal, the request for assistance data including on-demand positioning reference signal configuration information, the on-demand positioning reference signal configuration information including one or both of a start time and a duration for the on-demand positioning reference signal; determining one or more base stations for providing the downlink positioning reference signal based on the on-demand positioning reference signal configuration information; providing the on-demand positioning reference signal configuration information to the one or more base stations; providing assistance data based on the on-demand positioning reference signal configuration information The apparatus is configured to:

14. Memory and 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: transmitting, via the at least one transceiver, an assistance data request for downlink and uplink positioning reference signals to a network side, the assistance data request including on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information including one or both of a start time and a duration for the on-demand downlink positioning reference signal; receiving, via the at least one transceiver, uplink configuration parameters determined by the network side based on the uplink positioning reference signal configuration information; transmitting one or more uplink positioning reference signals based on the uplink configuration parameters; receiving, via the at least one transceiver, first assistance data with updated downlink positioning reference signal configuration information, the updated downlink positioning reference signal configuration information being determined by the network side based on the on-demand downlink positioning reference signal configuration information; measuring one or more downlink positioning reference signals based at least in part on the updated on-demand downlink positioning reference signal configuration information; receiving, via the at least one transceiver, second assistance data based on the one or more uplink positioning reference signal measurements; determining a position based at least in part on measurements obtained from the one or more downlink positioning reference signals and the uplink positioning reference signal measurements included in the second assistance data; The apparatus is configured to:

15. Memory and 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: receiving, via the at least one transceiver, a request for assistance data for downlink and uplink positioning reference signals, the request for assistance data including on-demand downlink positioning reference signal configuration information and uplink positioning reference signal configuration information, the on-demand downlink positioning reference signal configuration information including one or both of a start time and a duration for the on-demand downlink positioning reference signal; determining one or more base stations for providing a downlink positioning reference signal based on the on-demand downlink positioning reference signal configuration information; requesting at least one of the one or more base stations to measure an uplink positioning reference signal; providing the on-demand 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 via the at least one transceiver; transmitting, via the at least one transceiver, assistance data based on the on-demand downlink positioning reference signal configuration information and the uplink positioning reference signal measurement information. The apparatus is configured to:

Images