REQUEST FOR ON-DEMAND POSITIONING REFERENCE SIGNAL POSITIONING SESSION AT FUTURE TIME - Patent application

Abstract

Techniques for wireless communications are disclosed. In one aspect, a position determination entity (PDE) receives a request to schedule an on-demand PRS positioning session for a UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, and the availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received. The PDE determines the availability of the one or more parameters at the future time. The PDE determines a PRS configuration for the scheduled on-demand PRS positioning session in advance of the future time.

Description

[Background technology]

[0001] 1. Field of disclosure Aspects of the present disclosure relate generally to wireless communications.

[0002] 2. Description of Related Art 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, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), and the like.

[0003] The fifth generation (5G) wireless standard, called New Radio (NR), requires higher data rates, a larger number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Network Alliance, the 5G standard is designed to provide data rates of tens of megabits per second to each of tens of thousands of users, providing 1 gigabit per second to a few dozen workers on an office floor. To support large-scale deployment of sensors, hundreds of thousands of simultaneous connections must be supported. Therefore, the spectral efficiency of 5G mobile communications should be significantly increased compared to the current 4G standard. Furthermore, signaling efficiency must be increased and latency significantly reduced compared to the current standard. Summary of the Invention

[0004] The following presents a simplified summary related to one or more aspects disclosed herein. As such, the following summary is not intended to be an extensive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all contemplated aspects or to delineate the scope related to any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0005] In one aspect, a method of operating a user equipment (UE) includes sending a request to a position estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent; and receiving, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session prior to the future time, the PRS configuration including a second parameter set based at least in part on availability of the one or more parameters at the future time.

[0006] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0007] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0008] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0009] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth part (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0010] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0011] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0012] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0013] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0014] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0015] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0016] In some aspects, the PRS configuration is required to be received within a specified time window.

[0017] In some aspects, the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0018] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0019] In one aspect, a method of operating a position estimation entity includes receiving a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; determining, in response to the request, availability of the one or more parameters at the future time prior to the future time; determining a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and, in response to the request, transmitting, in advance of the future time, the PRS configuration to the UE.

[0020] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0021] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0022] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0023] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0024] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0025] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0026] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0027] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0028] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0029] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0030] In some aspects, the PRS configuration is required to be received within a specified time window.

[0031] In some aspects, the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0032] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0033] In one aspect, a user equipment (UE) comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: send, via the at least one transceiver, a request to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent, to a position estimation entity; and receive, in response to the request, via the at least one transceiver, a PRS configuration for the scheduled on-demand PRS positioning session in advance of the future time, the PRS configuration including a second parameter set that is based at least in part on availability of the one or more parameters at the future time.

[0034] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0035] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0036] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0037] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0038] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0039] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0040] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0041] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0042] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0043] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0044] In some aspects, the PRS configuration is required to be received within a specified time window.

[0045] In some aspects, the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0046] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0047] In one aspect, a position estimation entity comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to receive, via the at least one transceiver, a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; determine, in response to the request, availability of the one or more parameters at the future time in advance of the future time; determine a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and transmit, in response to the request, in advance of the future time to the UE via the at least one transceiver.

[0048] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0049] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0050] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0051] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0052] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0053] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0054] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0055] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0056] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0057] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0058] In some aspects, the PRS configuration is required to be received within a specified time window.

[0059] In some aspects, the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0060] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0061] In one aspect, a user equipment (UE) includes means for sending a request to a position estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent, and means for receiving, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session prior to the future time, the PRS configuration including a second parameter set based at least in part on availability of the one or more parameters at the future time.

[0062] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0063] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0064] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0065] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0066] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0067] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0068] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0069] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0070] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0071] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0072] In some aspects, the PRS configuration is required to be received within a specified time window.

[0073] In some aspects, the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0074] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0075] In one aspect, a position estimation entity includes means for receiving a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; means for determining, in response to the request, availability of the one or more parameters at the future time in advance of the future time; means for determining a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and means for transmitting, in response to the request, in advance of the future time to the UE.

[0076] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0077] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0078] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0079] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0080] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0081] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0082] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0083] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0084] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0085] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0086] In some aspects, the PRS configuration is required to be received within a specified time window.

[0087] In some aspects, the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0088] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0089] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to send a request to a position estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent, and receive, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session in advance of the future time, the PRS configuration including a second parameter set that is based at least in part on availability of the one or more parameters at the future time.

[0090] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0091] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0092] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0093] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0094] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0095] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0096] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0097] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0098] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0099] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0100] In some aspects, the PRS configuration is required to be received within a specified time window.

[0101] In some aspects, the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0102] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0103] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to receive a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; determine, in response to the request, availability of the one or more parameters at the future time in advance of the future time; determine a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and transmit, in response to the request, the PRS configuration to the UE in advance of the future time.

[0104] In some aspects, the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0105] In some aspects, the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0106] In some aspects, the first set of parameters includes at least one sidelink (SL) anchor.

[0107] In some aspects, the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0108] In some aspects, one or more parameters that are not determinable at the time the request is transmitted are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0109] In some aspects, one or more other parameters for the at least one stationary anchor can be determined at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0110] In some aspects, the request specifies a time in the future via an indication of a preferred start time and duration.

[0111] In some aspects, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified by reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0112] In some aspects, at least one parameter in the first parameter set is associated with at least one time constraint.

[0113] In some aspects, at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0114] In some aspects, the PRS configuration is required to be received within a specified time window.

[0115] In some aspects, the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0116] In some aspects, the one or more requests for a PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0117] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description. [Brief description of the drawings]

[0118] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate, not limit, the aspects. [Figure 1] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 2A] FIG. 1 illustrates an example wireless network structure according to an aspect of the present disclosure. [Figure 2B] FIG. 1 illustrates an example wireless network structure according to an aspect of the present disclosure. [Figure 3A] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a base station and configured to support communications as taught herein. [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a network entity and configured to support communications as taught herein. [Figure 4] FIG. 2 illustrates an example frame structure according to an aspect of the present disclosure. [Diagram 5] FIG. 2 illustrates various downlink channels in an example downlink slot, according to an aspect of the disclosure. [Figure 6] FIG. 1 illustrates various uplink channels in an example uplink slot, in accordance with an aspect of the disclosure. [Figure 7] 1 is a diagram of an example positioning reference signal (PRS) configuration for a PRS transmission of a given base station, according to an aspect of the disclosure. [Figure 8] FIG. 1 illustrates an example downlink positioning reference signal (DL-PRS) configuration for two transmit receiving points (TRPs) operating in the same positioning frequency layer, in accordance with an aspect of the present disclosure. [Figure 9] FIG. 1 illustrates examples of various positioning methods supported in New Radio (NR) according to an aspect of the present disclosure. [Figure 10] FIG. 1 illustrates an example user equipment (UE) positioning operation according to an aspect of the present disclosure. [Figure 11] FIG. 1 illustrates an example process for wireless communication according to an aspect of the present disclosure. [Figure 12] FIG. 1 illustrates an example process for wireless communication according to an aspect of the present disclosure. [Figure 13] FIG. 1 illustrates on-demand DL PRS parameters that may be requested by a UE, an LMF, or both, according to an aspect of the disclosure. [Figure 14] 13A-13C illustrate example implementations of the processes of FIGS. 11-12, respectively, according to one embodiment of the present disclosure. [Figure 15] 13A-13C illustrate example implementations of the processes of FIGS. 11-12, respectively, according to one embodiment of the present disclosure. [Figure 16]13A-13C illustrate example implementations of the processes of FIGS. 11-12, respectively, according to one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0119] Aspects of the present disclosure are provided in the following description and associated drawings directed to various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the present disclosure.

[0120] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Similarly, the term "aspects of the present disclosure" does not require that all aspects of the present disclosure include the discussed feature, advantage or mode of operation.

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

[0122] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that various actions described herein may be performed by specific circuitry (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or a combination of both. Additionally, the sequence or sequences of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium having stored thereon a corresponding set of computer instructions that, when executed, cause or instruct an associated processor of a device to perform the functions described herein. Thus, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspect may be described herein, for example, as "logic configured to" perform the described actions.

[0123] As used herein, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer location device, a wearable (e.g., a smart watch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station", or variations thereof. In general, a UE may communicate with a core network via a RAN, through which the UE may be connected to external networks, such as the Internet, and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications, etc.).

[0124] A base station may operate according to one of several RATs in communication with UEs depending on the network in which the base station is deployed and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), New Radio (NR) Node B (also referred to as gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functionality, while in other systems, a base station may provide additional control and / or network management functionality. A communication link through which a UE may send signals to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which a base station may send signals to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0125] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station that corresponds to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be serving base stations that receive measurement reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0126] In some implementations that support positioning of UEs, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE) but may instead transmit reference signals to the UE to be measured by the UE and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when it transmits signals to the UE) and / or a position measurement unit (e.g., when it receives and measures signals from the UE).

[0127] An "RF signal" includes electromagnetic waves of a given frequency that transport information through space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0128] 1 illustrates an example wireless communication system 100 according to aspects of the disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network, WWAN) may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In an aspect, the macrocell base stations may include eNBs and / or ng-eNBs where the wireless communication system 100 corresponds to an LTE network, or gNBs where the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0129] The base stations 102 may collectively form a RAN and may interface to a core network 170 (e.g., evolved packet core (EPC) or 5G core (5GC)) through the backhaul links 122 and to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as through an application server (not shown), through a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), through another network, etc. For purposes of signaling, communication between the UE 104 and the location server 172 may be represented as an indirect connection (e.g., through the core network 170), or a direct connection (e.g., as shown via direct connection 128), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

[0130] In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and alert message delivery. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0131] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resources, referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Since a cell is supported by a particular base station, the term "cell" may refer to one or both of the logical communication entity and the base station that supports it, depending on the context. In addition, since a TRP is typically a physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0132] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions) and some of the geographic coverage areas 110 may be substantially overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" instead of "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0133] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be through one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

[0134] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a wireless local area network (WLAN) station (STA) 152 over a communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in the unlicensed frequency spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine if a channel is available.

[0135] The small cell base station 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell base station 102' may utilize LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. A small cell base station 102' employing LTE / 5G in the unlicensed frequency spectrum may extend coverage to and / or increase capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0136] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW and / or sub-mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may extend down to frequencies of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz and is also referred to as centimeter waves. Communications using the mmW / sub-mmW radio frequency bands have high path losses and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely large path losses and short distances. It will be further understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Thus, it will be understood that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0137] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that particular direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to the receiving device(s). To vary the directionality of an RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. In particular, RF current from a transmitter is supplied to each antenna with the proper phase relationship so that the radio waves from the separate antennas combine together to enhance radiation in the desired direction while suppressing and canceling radiation in undesired directions.

[0138] A transmit beam may be quasi-co-located, meaning that the transmit beam appears to a receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located or not. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0139] In receive beamforming, a receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase the gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in a particular direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is the highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of RF signals received from that direction.

[0140] The transmit beam and the receive beam may be spatially related. The spatial relationship means that the parameters for the second beam (e.g., transmit beam or receive beam) for the second reference signal may be derived from information about the first beam (e.g., receive beam or transmit beam) for the first reference signal. For example, the UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0141] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE forms a downlink beam, then it is a receive beam to receive the downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms an uplink beam, then it is an uplink receive beam, and if the UE forms an uplink beam, then it is an uplink transmit beam.

[0142] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers, although a portion of FR1 is above 6 GHz. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0143] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus may in effect extend the features of FR1 and / or FR2 to the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0144] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, it should be understood that unless otherwise specified, terms such as "mmWave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0145] In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell" and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured when an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE specific, the secondary carrier may include only the necessary signaling information and signals, e.g., the signaling information and signals that are UE specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier over which several base stations are communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0146] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or “PCell”), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or data reception rates. For example, two aggregated 20 MHz carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0147] The wireless communications system 100 may further include a UE 164, which may communicate with the macrocell base station 102 via communications link 120 and / or with the mmW base station 180 via mmW communications link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0148] In some cases, the UE 164 and the UE 182 may be capable of sidelink communications. A sidelink-enabled UE (SL-UE) can communicate with the base station 102 over a communication link 120 that uses a Uu interface (i.e., an air interface between the UE and the base station). The SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 that uses a PC5 interface (i.e., an air interface between sidelink-enabled UEs). The wireless sidelink (or simply "sidelink") is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communications having to go through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-everything (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of a group of SL-UEs utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102 or may not be able to receive transmissions from the base station 102. In some cases, a group of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to all other SL-UEs in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between SL-UEs without the involvement of the base station 102.

[0149] In one aspect, the sidelink 160 may operate on a subject wireless communication medium, which may be shared with other vehicular and / or infrastructure access points, as well as other wireless communications between other RATs. The "medium" may consist of one or more time, frequency, and / or spatial communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one aspect, the subject medium may correspond to at least a portion of an unlicensed frequency band shared between various RATs. Although different licensed frequency bands have been reserved for some communications systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi." Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, Orthogonal FDMA (OFDMA) systems, Single Carrier FDMA (SC-FDMA) systems, and various variations thereof.

[0150] It should be noted that while FIG. 1 illustrates only two of the UEs as SL-UEs (i.e., UE 164 and 182), any of the illustrated UEs may be SL-UEs. Additionally, while only UE 182 has been described as being beamforming capable, any of the illustrated UEs may be beamforming capable, including UE 164. If SL-UEs are beamforming capable, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cell 102′, access point 150), and so forth. Thus, in some cases, UE 164 and UE 182 may utilize beamforming over sidelink 160.

[0151] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located within the SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers specifically designed to receive the signals 124 from the SV 112 to derive geolocation information.

[0152] In a satellite positioning system, the use of the signals 124 may be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, the SBAS may include an augmentation system or systems that provide integrity information, differential corrections, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-aided Geo-augmented Navigation, or the GPS and Geo Augmented Navigation system (GAGAN). Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with one or more such satellite positioning systems.

[0153] In one aspect, the SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, the SV 112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In this way, the UE 104 may receive communication signals (e.g., signal 124) from the SV 112 instead of or in addition to communication signals from the terrestrial base station 102.

[0154] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelinks"). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) with one of the UEs 104 connected to one of the base stations 102, and a D2D P2P link 194 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity) with a WLAN STA 152 connected to a WLAN AP 150. In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc.

[0155] 2A illustrates an exemplary wireless network structure 200. For example, a 5GC 210 (also referred to as Next Generation Core (NGC)) may be considered functionally as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) that operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the ng-eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both the ng-eNB 224 and the gNB 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0156] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location servers 230 may be configured to support one or more location services for the UEs 204 that may connect to the location server 230 via the core network 5GC 210 and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0157] 2B illustrates another example wireless network structure 250. 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) may be considered functionally as control plane functionality provided by access and mobility management function (AMF) 264 and user plane functionality provided by user plane function (UPF) 262, which operate cooperatively to form a core network (i.e., 5GC 260). The functions of AMF 264 include registration management, attachment management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between UE 204 and short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204 to receive intermediate keys established as a result of the UE 204 authentication process. In case of universal mobile telecommunications system (UMTS) subscriber identity module (USIM) based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264 functions also include security context management (SCM).The SCM receives keys from the SEAF that the SCM uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulated services, transport for location service messages between the UE 204 and the Location Management Function (LMF) 270 (acting as the location server 230), transport for location service messages between the NG-RAN 220 and the LMF 270, EPS bearer identifier allocation for interworking with evolved packet system (EPS), and UE 204 mobility event notification. In addition, the AMF 264 also supports functions for non-3GPP (Third Generation Partnership Project) access networks.

[0158] The functions of the UPF 262 include serving as an anchor point for intra / inter-RAT mobility (when applicable), serving as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), routing and forwarding of packets, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support forwarding of location service messages on the user plane between the UE 204 and a location server such as the SLP 272.

[0159] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF 262 to route traffic to the appropriate destination, policy enforcement and control of part of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0160] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may be connected to the LMF 270 via a core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functions as the LMF 270, except that the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on the control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data) and the SLP 272 may communicate with the UE 204 and external clients (not shown in FIG. 2B ) on the user plane (e.g., using protocols intended to carry voice and / or data, such as the transmission control protocol (TCP) and / or IP).

[0161] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as the “Uu” interface.

[0162] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is called the "F1" interface. The gNB-CU 226 is a logical node that includes base station functions such as forwarding user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions that are exclusively assigned to the gNB-DU(s) 228. More specifically, the gNB-CU 226 hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that hosts the Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, and with the gNB-DU 228 via the RLC, MAC, and PHY layers.

[0163] 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated in a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including a location server 230 and an LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support file transmission operations taught herein. It will be understood that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include components similar to the illustrated components to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may contain multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0164] The UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.) over one or more wireless communications networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communications medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured to transmit and encode signals 318 and 358, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 318 and 358, respectively (e.g., messages, instructions, information, pilots, etc.), in accordance with a designated RAT. In particular, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, to transmit and encode signals 318 and 358, respectively, and include one or more receivers 312 and 352, respectively, to receive and decode signals 318 and 358, respectively.

[0165] The UE 302 and base station 304 also each, in at least some cases, include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near field communication (NFC), etc.) over a wireless communication medium of interest. The short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368, respectively (e.g., messages, instructions, information, etc.), and conversely, to receive and decode signals 328 and 368, respectively (e.g., messages, instructions, information, pilots, etc.), in accordance with a specified RAT. In particular, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and include one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or Vehicle-to-Vehicle (V2V) and / or Vehicle-to-Everything (V2X) transceivers.

[0166] The UE 302 and the base station 304 also, in at least some cases, include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide a means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. If the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, Navigation Satellite System of India (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. If the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communications signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and action from other systems as appropriate and, at least in some cases, perform calculations to determine the location of UE 302 and base station 304, respectively, using the acquired measurements according to any suitable satellite positioning system algorithms.

[0167] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, that provide a means for communicating (e.g., a means for transmitting, a means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links or with other network entities 306 over one or more wired or wireless core network interfaces.

[0168] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired or wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device in some implementations (e.g., embodying transmitter and receiver circuitry in a single device), may comprise separate transmitter and receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that allows an individual device (e.g., UE 302, base station 304) to perform transmit "beamforming," as may be described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that allows an individual device (e.g., UE 302, base station 304) to perform receive beamforming, as may be described herein. In an aspect, the transmitter circuitry and the receiver circuitry may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that an individual device can only receive or transmit at a given time, but not both at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short range wireless transceivers 320 and 360) may also include network listen modules (NLMs) and the like for performing various measurements.

[0169] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390, in some implementations) and wired transceivers (e.g., network transceivers 380 and 390, in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication being performed. For example, backhaul communications between network devices or servers generally involve signaling via wired transceivers, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involve signaling via wireless transceivers.

[0170] The UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with operations as disclosed herein. The UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, for example, to provide functionality related to wireless communications and to provide other processing functionality. Thus, the processors 332, 384, and 394 may comprise processing means, such as means for determining, means for calculating, means for receiving, means for transmitting, means for directing, etc. In one aspect, the processors 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0171] The UE 302, base station 304, and network entity 306 include memory circuitry implementing memories 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Thus, the memories 340, 386, and 396 may provide suitable storage means, retrieval means, maintenance means, etc. In some cases, the UE 302, base station 304, and network entity 306 may include on-demand PRS components 342, 388, and 398, respectively. The on-demand PRS components 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, which, when executed, cause the UE 302, base station 304, and network entity 306 to perform the functions described herein. In other aspects, the on-demand PRS components 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the on-demand PRS components 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. FIG. 3A illustrates possible locations of the on-demand PRS component 342, which may be part of, for example, one or more WWAN transceivers 310, the memory 340, one or more processors 332, or any combination thereof, or may be a stand-alone component. FIG. 3B shows possible locations of an on-demand PRS component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C shows possible locations of an on-demand PRS component 398, which may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0172] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of movement data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of movement detection sensor. Additionally, the sensor(s) 344 may include multiple different types of devices and combine their outputs to provide movement information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate a position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0173] Additionally, the UE 302 includes a user interface 346 that provides a means for providing instructions to a user (e.g., audio and / or visual instructions) and / or receiving user input (e.g., upon user actuation of a sensing device, such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0174] Turning in more detail to the one or more processors 384, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions associated with system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and broadcasting of measurement configurations for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding of higher layer PDUs, error correction with automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0175] The transmitter 354 and receiver 352 may implement Layer 1 (L1) functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with the individual spatial streams for transmission.

[0176] At the UE 302, the receiver 312 receives the signal through its individual antenna(s) 316. The receiver 312 recovers the information modulated onto the RF carriers and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functions associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. The data and control signals are then provided to one or more processors 332 that implement Layer 3 (L3) and Layer 2 (L2) functions.

[0177] In the uplink, the one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection.

[0178] Similar to the functionality described in connection with downlink transmissions by the base station 304, the one or more processors 332 provide RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with forwarding of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0179] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with the individual spatial streams for transmission.

[0180] Uplink transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver functions at the UE 302. The receiver 352 receives signals through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

[0181] In the uplink, the one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the UE 302. The IP packets from the one or more processors 384 may be provided to a core network. The one or more processors 384 are also responsible for error detection.

[0182] For convenience, the UE 302, base station 304, and / or network entity 306 are illustrated in Figures 3A, 3B, and 3C as including various components that may be configured according to various examples described herein. However, it will be understood that the illustrated components may have different functions in different designs. In particular, various components in Figures 3A-3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, device use, or other considerations. For example, in the case of Figure 3A, a particular implementation of the UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, etc. 3B, a particular implementation of base station 304 may omit WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit short-range wireless transceiver(s) 360 (e.g., cellular only, etc.), or may omit satellite receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but should be readily apparent to one of ordinary skill in the art.

[0183] The various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces of the UE 302, base station 304, and network entity 306, respectively. For example, when various logical entities are embodied within the same device (e.g., gNB and location server functionality integrated within the same base station 304), the data buses 334, 382, ​​and 392 may provide communication therebetween.

[0184] The components of Figures 3A, 3B, and 3C may be implemented in a variety of ways. In some implementations, the components of Figures 3A, 3B, and 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide its functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by the processor component(s) and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by the processor component(s) and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390-398 may be implemented by the processor component(s) and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be understood that such operations, actions, and / or functions may actually be performed by a particular component or combination of components of the UE 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, on-demand PRS components 342, 388, and 398, etc.

[0185] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., the NG RAN 220 and / or the 5GC 210 / 260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0186] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 is a diagram 400 illustrating example frame structures according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0187] LTE and in some instances NR utilize OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, or the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be 15 kilohertz (kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0188] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (μ), e.g., subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or more may be available. At each subcarrier spacing, there are 14 symbols per slot. For a 15 kHz SCS (μ=0), there is one slot per subframe, i.e., 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with an FFT size of 4K is 50. For a 30 kHz SCS (μ=1), there are two slots per subframe, i.e., 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 100. For a 60 kHz SCS (μ=2), there are four slots per subframe, i.e., 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 200. For a 120 kHz SCS (μ=3), there are eight slots per subframe, i.e., 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 μs, and the maximum nominal system bandwidth (in MHz) for a 4K FFT size is 400. For a 240 kHz SCS (μ=4), there are 16 slots per subframe, i.e., 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with an FFT size of 4K is 800.

[0189] In the example of Figure 4, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, with each subframe containing one time slot. In Figure 4, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0190] A resource grid may be used to represent a time slot, with each time slot including one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 4, for a normal cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may include 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0191] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communications. Figure 4 shows example locations of REs carrying reference signals (labeled "R").

[0192] Figure 5 is a diagram 500 illustrating various downlink channels in an exemplary downlink slot. In Figure 5, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top. In the example of Figure 5, a numerology of 15 kHz is used. Thus, in the time domain, the slot shown is 1 millisecond (ms) long and divided into 14 symbols.

[0193] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a contiguous set of RBs selected from a contiguous subset of common RBs for a given numerology on a given carrier. In general, up to four BWPs can be specified in the downlink and uplink. That is, a UE can be configured with up to four BWPs on the downlink and with up to four BWPs on the uplink. Only one BWP (uplink or downlink) may be active at a given time, meaning that a UE can only receive or transmit via one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of an SSB, but each BWP may or may not include an SSB.

[0194] Referring to FIG. 5, the Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the DL-RS mentioned above. The Physical Broadcast Channel (PBCH), which carries the Master Information Block (MIB), may be logically grouped with the PSS and SSS to form an SSB (also called SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as the System Information Block (SIB), and paging messages.

[0195] A physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), where each CCE contains one or more RE group (REG) bundles (which may span multiple symbols in the time domain), and each REG bundle contains one or more REGs, where each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, the PDCCH is confined to a single CORESET and transmitted with its own DMRS. This allows UE-specific beamforming for the PDCCH.

[0196] In the example of Figure 5, there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is confined to a specific region (i.e., the CORESET) in the frequency domain. Thus, the frequency components of the PDCCH shown in Figure 5 are shown as less than a single BWP in the frequency domain. Note that the illustrated CORESET is contiguous in the frequency domain, but does not have to be. In addition, the CORESET may span less than three symbols in the time domain.

[0197] The DCI in the PDCCH carries information about uplink resource allocations (persistent and non-persistent), called uplink grants and downlink grants, respectively, and a description of the downlink data to be transmitted to the UE. More specifically, the DCI indicates resources scheduled for a downlink data channel (e.g., PDSCH) and an uplink data channel (e.g., Physical Uplink Shared Channel (PUSCH)). Multiple (e.g., up to eight) DCIs may be configured in the PDCCH, and these DCIs may have one of multiple formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH may be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.

[0198] Figure 6 is a diagram 600 illustrating various uplink channels in an exemplary uplink slot. In Figure 6, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top. In the example of Figure 6, a numerology of 15 kHz is used. Thus, in the time domain, the slot shown is 1 millisecond (ms) long and divided into 14 symbols.

[0199] A random access channel (RACH), also referred to as a physical random access channel (PRACH), may be in one or more slots in a frame based on a PRACH configuration. The PRACH may include six consecutive RB pairs in a slot. The PRACH allows a UE to perform initial system access and achieve uplink synchronization. A physical uplink control channel (PUCCH) may be located on the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. A physical uplink shared channel (PUSCH) carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0200] FIG. 7 is a diagram of an example PRS configuration 700 for PRS transmissions of a given base station, according to an aspect of the disclosure. In FIG. 7, time is represented horizontally, increasing from left to right. Each long rectangle represents a slot, and each short (shaded) rectangle represents an OFDM symbol. In the example of FIG. 7, a PRS resource set 710 (labeled "PRS resource set 1") includes two PRS resources: a first PRS resource 712 (labeled "PRS resource 1") and a second PRS resource 514 (labeled "PRS resource 2"). The base station transmits PRSs in PRS resources 712 and 714 of PRS resource set 710.

[0201] PRS resource set 710 has an occasion length (N_PRS) of 2 slots and a periodicity (T_PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). Thus, both PRS resources 712 and 714 are two consecutive slots in length and repeat every T_PRS slots starting from the slot in which the first symbol of the respective PRS resource appears. In the example of FIG. 7, PRS resource 712 has a symbol length (N_symb) of 2 symbols and PRS resource 714 has a symbol length (N_symb) of 4 symbols. PRS resource 712 and PRS resource 714 may be transmitted on separate beams of the same base station.

[0202] Each instance of PRS resource set 710, denoted as instances 720a, 720b, and 720c, includes occasions of length "2" (i.e., N_PRS=2) for each PRS resource 712, 714 of the PRS resource set. The PRS resources 712 and 714 are repeated every T_PRS slots up to the muting sequence periodicity T_REP. Thus, a bitmap of length T_REP would be needed to indicate which occasions of instances 720a, 720b, and 720c of PRS resource set 710 are muted (i.e., not transmitted).

[0203] In one aspect, there may be additional constraints on the PRS configuration 700. For example, for all PRS resources (e.g., PRS resources 712, 714) of a PRS resource set (e.g., PRS resource set 710), the base station may configure the following parameters to be the same: (a) occasion length (N_PRS), (b) number of symbols (N_symb), (c) comb type, and / or (d) bandwidth. In addition, for all PRS resources of all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether it is for one base station or for all base stations may depend on the UE's capability to support the first and / or second options.

[0204] FIG. 8 is a diagram 800 illustrating example PRS configurations for two TRPs (labeled “TRP1” and “TRP2”) operating in the same positioning frequency layer (labeled “Positioning Frequency Layer 1”) according to an aspect of the disclosure. For a positioning session, a UE may be provided with assistance data indicating the illustrated PRS configurations. In the example of FIG. 8, a first TRP ("TRP1") is associated with (e.g., transmits from) two PRS resource sets labeled “PRS Resource Set 1” and “PRS Resource Set 2,” and a second TRP ("TRP2") is associated with one PRS resource set labeled “PRS Resource Set 3.” Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set ("PRS resource set 1") includes PRS resources labeled "PRS resource 1" and "PRS resource 2," the second PRS resource set ("PRS resource set 2") includes PRS resources labeled "PRS resource 3" and "PRS resource 4," and the third PRS resource set ("PRS resource set 3") includes PRS resources labeled "PRS resource 5" and "PRS resource 6."

[0205] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink- and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. FIG. 9 illustrates examples of various positioning methods according to aspects of the present disclosure. In an OTDOA or DL-TDOA positioning procedure illustrated by scenario 910, a UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, called reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives an identifier (ID) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., the UE in case of UE-based positioning, or a location server in case of UE-assisted positioning) can estimate the location of the UE.

[0206] For DL-AoD positioning, as illustrated by scenario 920, the positioning entity uses beam reports from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

[0207] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on an uplink reference signal (e.g., Sounding Reference Signal (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

[0208] Downlink and uplink based positioning methods include extended cell ID (E-CID) positioning, and multiple round trip time (RTT) positioning (also called "multi-cell RTT" and "multi-RTT"). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or an SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., an SRS or a PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurement may be made or adjusted to include only the time difference between the nearest subframe boundaries for the received and transmitted signals. Both entities may then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning illustrated by scenario 930, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined based on the distance to the second entity and the known location of the second entity (e.g., using multilateration). As illustrated by scenario 940, RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0209] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and identities of detected neighboring base stations, estimated timing, and signal strength. The location of the UE is then estimated based on this information and the known location of the base station(s).

[0210] To assist the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include identifiers of base stations (or base station cells / TRPs) from which to measure reference signals, reference signal configuration parameters (e.g., number of consecutive positioning subframes, periodicity of positioning subframes, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using the assistance data.

[0211] In the case of OTDOA or DL-TDOA positioning procedures, the assistance data may further include an expected RSTD value and an associated uncertainty around the expected RSTD, i.e., a search window. In some cases, the value range for the expected RSTD may be + / - 500 microseconds (μs). In some cases, the value range for the expected RSTD uncertainty may be + / - 32 μs when any of the resources used for the positioning measurements are in FR1. In other cases, the value range for the expected RSTD uncertainty may be + / - 8 μs when all of the resources used for the positioning measurement(s) are in FR2.

[0212] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, etc. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude), or urban and comprise a street address, postal address, or some other linguistic description of a location. A location estimate may also be defined relative to some other known location, or defined absolutely (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume that the location is expected to be within with some specified or default level of confidence).

[0213] 10 illustrates an example UE positioning operation 1000 according to an aspect of the disclosure. The UE positioning operation 1000 may be performed by the UE 204, an NG-RAN node 1002 in the NG-RAN 220 (e.g., the gNB 222, the gNB-CU 226, the ng-eNB 224, or other nodes in the NG-RAN 220), the AMF 264, the LMF 270, and a 5GC Location Services (LCS) entity 1080 (e.g., any third party application requesting the location of the UE 204, a Public Service Access Point (PSAP), an E-911 server, etc.).

[0214] A location service request to obtain the location of a target (i.e., UE 204) can be initiated by the 5GC LCS entity 1080, the AMF 264 serving the UE 204, or the UE 204 itself. Figure 10 illustrates these options as steps 1010a, 1010b, and 1010c, respectively. Specifically, in step 1010a, the 5GC LCS entity 1080 sends a location service request to the AMF 264. Alternatively, in step 1010b, the AMF 264 generates the location service request itself. Alternatively, in step 1010c, the UE 204 sends a location service request to the AMF 264.

[0215] Upon receiving (or generating) the location service request, the AMF 264 forwards the location service request to the LMF 270 in step 1020. The LMF 270 then performs an NG-RAN positioning procedure with the NG-RAN node 1002 in step 1030a and a UE positioning procedure with the UE 204 in step 1030b. The particular NG-RAN positioning procedure and UE positioning procedure may depend on the type(s) of positioning method(s) used to determine the location of the UE 204, which may depend on the capabilities of the UE 204. The positioning method may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and / or downlink- and uplink-based (e.g., LTE / NR E-CID, multi-RTT, etc.), as described above. The corresponding positioning procedures are publicly available and are described in detail in 3GPP Technical Specification (TS) 38.305, which is incorporated herein by reference in its entirety.

[0216] The NG-RAN and UE positioning procedures may utilize LTE Positioning Protocol (LPP) signaling between the UE 204 and the LMF 270, and LPP type A (LPPa) or New Radio Positioning Protocol type A (NRPPa) signaling between the NG-RAN node 1002 and the LMF 270. LPP is used point-to-point between a location server (e.g., the LMF 270) and a UE (e.g., the UE 204) to obtain location measurements or location estimates or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single Mobile Terminated Location Request (MT-LR), Mobile Originated Location Request (MO-LR), or Network Induced Location Request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions, with each LPP transaction performing a single operation (e.g., capability exchange, assistance data transfer, location information transfer). An LPP transaction is called an LPP procedure.

[0217] A prerequisite for step 1030 is that an LCS correlation identifier (ID) and an AMF ID have been passed by the serving AMF 264 to the LMF 270. Both the LCS correlation ID and the AMF ID may be represented as strings selected by the AMF 264. The LCS correlation ID and the AMF ID are provided to the LMF 270 by the AMF 264 during a location service request in step 1020. Then, when the LMF 270 triggers step 1030, the LMF 270 also includes the LCS correlation ID for this location session along with the AMF ID indicating the AMF instance serving the UE 204. The LCS correlation ID is used during a positioning session between the LMF 270 and the UE 204 to ensure that a positioning response message from the UE 204 is returned by the AMF 264 to the correct LMF 270 and carries an indication (LCS correlation ID) that can be recognized by the LMF 270.

[0218] As described in more detail in 3GPP TS 23.273, which has been published and is incorporated herein by reference in its entirety, it should be noted that the LCS Correlation ID serves as a location session identifier that may be used to identify messages exchanged between the AMF 264 and the LMF 270 for a particular location session for the UE 204. As described above and shown in stage 1020, a location session between the AMF 264 and the LMF 270 for a particular UE 204 is triggered by the AMF 264, and the LCS Correlation ID may be used to identify this location session (e.g., may be used by the AMF 264 to identify state information for this location session, etc.).

[0219] The LPP positioning methods and associated signaling content are defined in the 3GPP LPP standard (3GPP TS37.355, which is published and incorporated by reference in its entirety herein). LPP signaling can be used to request and report measurements related to the following positioning methods: LTE-OTDOA, DL-TDOA, A-GNSS, E-CID, Sensor, TBS, WLAN, Bluetooth, DL-AoD, UL-AoA, and Multi-RTT. Currently, an LPP measurement report may include the following measurements: (1) one or more ToA, TDOA, RSTD, or Rx-Tx time difference measurements; (2) one or more AoA and / or AoD measurements (currently only for base stations that report UL-AoA and DL-AoD to the LMF 270); (3) one or more multipath measurements (ToA, RSRP, AoA / AoD per path); (4) one or more motion states (e.g., walking, driving, etc.) and trajectory (currently only for UE 204); and (5) one or more report quality indications.

[0220] As part of the NG-RAN node positioning procedure (step 1030a) and the UE positioning procedure (step 1030b), the LMF 270 may provide LPP assistance data in the form of Downlink Positioning Reference Signal (DL-PRS) configuration information for the selected positioning method(s) to the NG-RAN node 1002 and the UE 204. Alternatively or additionally, the NG-RAN node 1002 may provide DL-PRS and / or Uplink PRS (UL-PRS) configuration information for the selected positioning method(s) to the UE 204. It should be noted that although FIG. 10 shows a single NG-RAN node 1002, there may be multiple NG-RAN nodes 1002 involved in a positioning session.

[0221] When configured in a DL-PRS configuration and / or a UL-PRS configuration, the NG-RAN node 1002 and the UE 204 transmit and receive / measure the respective PRS at scheduled times. The NG-RAN node 1002 and the UE 204 then transmit their respective measurements to the LMF 270.

[0222] When the LMF 270 obtains measurements from the UE 204 and / or the NG-RAN node 1002 (depending on the type(s) of the positioning method(s)), it uses these measurements to calculate an estimate of the location of the UE 204. Then, in step 1040, the LMF 270 transmits a location service response to the AMF 264 including the location estimate for the UE 204. The AMF 264 then forwards the location service response to the entity that generated the location service request in step 1050. Specifically, if in step 1010a, a location service request is received from the 5GC LCS entity 1080, then in step 1050a, the AMF 264 transmits the location service response to the 5GC LCS entity 1080. However, if in step 1010c, a location service request is received from the UE 204, then in step 1050c, the AMF 264 sends the location service response to the UE 204. Alternatively, if the AMF 264 generated a location service request in step 1010b, in step 1050b, the AMF 264 stores / uses the location service response itself.

[0223] Note that while the above describes the UE positioning operation 1000 as a UE-assisted positioning operation, it may instead be a UE-based positioning operation. A UE-assisted positioning operation is one in which the LMF 270 calculates the location of the UE 204, whereas a UE-based positioning operation is one in which the UE 204 calculates its own location.

[0224] For an on-demand PRS based UE positioning session, such as the process of Figure 10, there is little delay from the time a location service request is issued (e.g., at 1010a, 1010b, or 1010c) to the time the NG-RAN node positioning procedure (step 1030a) and / or the UE positioning procedure (step 1030b) are performed. In this case, the location service request may request several parameters for the on-demand PRS positioning session, and the availability of the requested parameter(s) may be verified in real-time (e.g., since there is no significant gap from the location service request to the on-demand PRS positioning session, the availability of the requested parameter(s) may simply be checked once and, if available, assigned to the on-demand PRS positioning session).

[0225] In some designs, there are situations where it is required that the UE location be known at some time T in the future. In some designs, there may be a one-shot request for location at time T, or a periodic location request with a first instance starting at time T. The need to track future UE location may arise in various use cases, such as IIoT, V2X, asset tracking, etc.

[0226] In some designs, PRS positioning may request measurement information related to both on-demand PRS and scheduled PRS (e.g., periodic or semi-persistent PRS). One issue that may arise is that the UE may move between measurements if the on-demand PRS and the scheduled PRS are separated by a large time gap. Also, clock drift may cause additional timing errors. To limit these issues, the UE may need to request to schedule the on-demand PRS within a requested time window in the future (e.g., to align all PRSs of the positioning session). However, some on-demand PRS configurations may not be immediately available to the UE after the request if the scheduled time in the request is far in the future. For example, if a UE requests to schedule an on-demand SL PRS from a specific mobile UE within an hour of the future, the configuration to the target UE may be because the SL anchor may not be in close proximity to the target UE at that time. In a particular use case, an autonomous vehicle may move according to a planned trajectory in a factory and request to schedule an on-demand PRS at a future time T_1 approximately within region R. The on-demand PRS may be from any anchor (TRP or SL). Although the Uu PRS may be able to be configured in advance, the LMF cannot predict which mobile SL anchors will be available around region R at time T1 (e.g., other robots may be disturbed and therefore unable to follow the planned trajectory).

[0227] Aspects of the present disclosure are directed to a request to schedule an on-demand PRS positioning session for a UE at a future time, where the request is configured to request a first parameter set for the scheduled on-demand PRS positioning session. In contrast to legacy on-demand PRS positioning sessions, where the availability of any requested parameters may simply be checked in real time and then assigned (if available) to the on-demand PRS positioning session, according to aspects of the present disclosure, the availability of one or more parameters of the first parameter set at the future time is not determinable when the request is transmitted. The position estimation entity may then track, in advance of the future time, a PRS configuration for the scheduled on-demand PRS positioning session including a second parameter set based at least in part on the availability of the one or more parameters at the future time. Such aspects may provide various technical advantages, such as facilitating on-demand PRS positioning at a future time, rather than being limited to scheduling real-time on-demand PRS positioning as in legacy systems. Also, in some designs, overhead may be reduced because future on-demand PRS may be scheduled without the need to set up a periodic broadcast PRS.

[0228] 11 illustrates an example process 1100 for wireless communication according to an aspect of the disclosure. In an aspect, the process 1100 may be performed by a UE, such as UE 302 (e.g., a UE for which a position estimate is desired).

[0229] 11 , at 1110, the UE 302 (e.g., transmitter 314 or 324, data bus 334, etc.) transmits a request to a position estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where the availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is transmitted. In some designs, the position estimation entity may correspond to the UE itself (e.g., for UE-based position estimation), or the BS 304 (e.g., an LMF integrated into the RAN), or the network entity 306 (e.g., an LMF integrated into a core network component, a location server, etc.). In the case of UE-based position estimation, the transmission of 1110 may correspond to an internal transfer of data between logical components or a transmission to an external component, such as a gNB or an LMF.

[0230] 11 , at 1120, the UE 302 (e.g., receiver 312 or 322, data bus 334, etc.) receives, upon request, a PRS configuration for a scheduled on-demand PRS positioning session in advance of a future time, the PRS configuration including a second parameter set based at least in part on availability of one or more parameters at the future time. In some designs, the position estimation entity may correspond to the UE itself (e.g., for UE-based position estimation), or the BS 304 (e.g., an LMF integrated into a RAN), or the network entity 306 (e.g., an LMF integrated into a core network component, location server, etc.). In the case of UE-based position estimation, the receiving at 1120 may correspond to an internal transfer of data between logical components or to receiving from an external component, such as a gNB or an LMF.

[0231] 12 illustrates an example process 1200 for wireless communication according to an aspect of the disclosure. In one aspect, process 1200 may be performed by a position estimation entity. In some designs, the position estimation entity may correspond to the UE 302 (e.g., for UE-based position estimation), or the BS 304 (e.g., an LMF integrated into the RAN), or the network entity 306 (e.g., an LMF integrated into a core network component, a location server, etc.).

[0232] 12, at 1210, a position estimation entity (e.g., receiver 312 or 322 or 352 or 362, network transceiver(s) 390, data bus 334 or 382 or 392, etc.) receives a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received. In some designs, the request may be received from a UE, as at 1110 in FIG. 11. In other designs, the request may be received from another entity, such as an LCS client or an LMF. In the case of a UE-based position estimation where the request is received from a UE, the reception at 1210 may correspond to an internal transfer of data between logical components. In the case of UE-assisted position estimation where the request is received from an LMF, the receipt of 1210 may correspond to an internal transfer of data between logical components.

[0233] 12 , at 1220, a location estimation entity (e.g., processor(s) 332 or 382 or 392, on-demand PRS component 342 or 388 or 398, etc.) determines the availability of one or more parameters at a future time in advance of the future time in response to a request. In some designs, this parameter availability lookup operation may be performed similarly to a legacy parameter availability lookup operation except for its timing. For example, a legacy parameter availability lookup operation is generally performed immediately (i.e., without delay) when a location service request for an on-demand PRS is issued. However, the parameter availability lookup operation of 1220 may be performed with a delay or may be offset from the time the request is received at 1210 (e.g., at some future time before the future time at which the on-demand PRS positioning session is performed).

[0234] Referring to FIG. 12, at 1230, a position estimation entity (e.g., processor(s) 332 or 382 or 392, on-demand PRS component 342 or 388 or 398, etc.) determines a PRS configuration for a scheduled on-demand PRS positioning session, the PRS configuration including a second set of parameters based at least in part on a determination of availability of one or more parameters at a future time.

[0235] 12, at 1240, a location estimation entity (e.g., transmitter 314 or 324 or 354 or 364, network transceiver(s) 390, data bus 334 or 382 or 392, etc.) transmits a PRS configuration to the UE in response to a request and in advance of a future time. As described in more detail, the transmission of 1240 may include a single transmission or multiple transmissions. In the case of UE-based location estimation, the transmission of 1240 may correspond to an internal transfer of data between logical components or may be received from an external component, such as a gNB or LMF (e.g., anchor location and / or PRS resources from a particular anchor may be provided to the UE by the gNB or LMF).

[0236] 11-12, in some designs, the "undecidable" parameters may be distinguished from the "decidable" parameters by respective confidence levels with which the parameter availability may be predicted at future times. For example, the availability of a particular SL anchor near a target UE at time 1 may be characterized as undecidable because the prediction is highly unlikely to be successful (e.g., because both the target UE and the SL anchor may be mobile devices).

[0237] 11-12, in some designs, the PRS configuration may include a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or any combination thereof.

[0238] 11-12, in some designs (e.g., 3GPP Rel.17), various on-demand PRS parameters may be specified. FIG. 13 illustrates on-demand DL PRS parameters 1300 that may be requested by a UE, an LMF, or both, according to aspects of the disclosure. In some designs, the requester of the on-demand PRS session (e.g., a UE or an LMF or a gNB or a position estimation entity, etc.) may further specify whether a particular parameter is mandatory or optional. In some designs, if a mandatory parameter cannot be satisfied, the position estimation entity may return a failure (e.g., cancel a scheduled on-demand PRS positioning session). In some designs, if an optional parameter cannot be satisfied, the position estimation entity may configure a compatible parameter or ignore the optional parameter. Thus, in some designs, for each parameter in the first parameter set, the request at 1110 of FIG. 11 or 1210 of FIG. 12 specifies whether the individual parameter is mandatory or optional. In this case, with reference to FIG. 13, any parameter that is associated with "yes" may instead be associated with a "required" or "optional" designation.

[0239] 11-12, in some designs, the first parameter set includes at least one sidelink (SL) anchor. In this case, in one example, the first parameter set includes, for the at least one SL anchor, an SL beam direction, an SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof. In another example, one or more parameters that are undeterminable when the request is transmitted are associated with the at least one SL anchor due to mobility of the at least one SL anchor. In a further example, one or more other parameters for the at least one stationary anchor are determinable when the request is transmitted due to lack of mobility of the least one stationary anchor. Thus, in some designs, the request at 1110 of FIG. 11 or 1210 of FIG. 12 may include only undeterminable parameters, or alternatively a combination of determinable and undeterminable parameters.

[0240] 11-12, in some designs, the request specifies a future time via an indication of a preferred start time (T) and duration. In some designs, the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time (e.g., ms or s), or the preferred start time and duration are specified by referencing future measurement gaps or PRS occasions of the current PRS configuration. In some designs, the request may further specify a minimum number of anchors necessary to achieve the target accuracy requirement.

[0241] 11-12, in some designs, at least one parameter in the first parameter set is associated with at least one time constraint. For example, the at least one time constraint limits when the at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session. In a particular example, assume that a UE sends a scheduled on-demand PRS request to a positioning entity (PE) to schedule an on-demand PRS at a future time T_1. In some designs, each preferred parameter Z_i in the request may be sent within a limited time window [X_i, Y_i]. In some designs, parameter Z_i cannot be requested, modified, or removed earlier than x (e.g., because the position estimation entity requests time to configure / schedule / adjust based on the requested parameter), and parameter Z_i cannot be requested, modified, or removed later than Y_i. In some designs, each parameter may have a different time window. Thus, the on-demand request may be sent in several messages.

[0242] In one particular example with one X_i and Y_i, the location estimation entity (or specification) may define a threshold T_r for scheduled on-demand requests. Only a subset of on-demand PRS parameters are allowed to be specified in the request before T_1 through T_r. The others should be specified after T_1 through T_r. In one example, a specific SL anchor may be added to the on-demand request only if the current time is close to the scheduled time. Otherwise, the SL anchor may move out of the vicinity of the target UE. In another example, the positioning accuracy requirement may be specified at any time. In some designs, the LCS client or UE may send an on-demand PRS request through several messages spanning a time before time T_1. Each request includes partial desired on-demand PRS parameters (e.g., before scheduled T1, the UE should provide a fully customized PRS request. In some designs, the messages may add / modify / remove a subset of on-demand parameters in the previous message(s). In some designs, some parameters cannot be specified given a threshold. In some designs, the position estimation entity (or specification) may further define a threshold T_3 after which no further desired parameters can be added / modified / removed. In one example, this time (T_3) may allow the position estimation entity to configure and schedule a customized PRS based on a fixed set of preferred parameters. The example timings in the various examples provided above may be defined in terms of slots, subframes, frames, absolute time, etc.

[0243] 11-12, in some designs, the PRS configuration is required to be received at the UE within a specified time window. In a particular example, assume that a position estimation entity is required to provide a customized PRS configuration scheduled around T_1. Each on-demand PRS configuration W_i in the response should be sent within a bounded time window [X_i, X_i] (e.g., no earlier than X because the position estimation entity cannot determine the configuration / scheduling before this time, and no later than Y_i because the UE requires time to adjust the configuration). In some designs, each parameter may have a different time window. Thus, the on-demand response may be sent in several messages.

[0244] In one particular example with one X_i and one Y_i, a timing threshold T_{nf} is defined for far future / near future on-demand responses. In some designs, requests within the threshold (T_1 < T_{nf}) are considered near future requests, and the response (i.e., the desired customized PRS configuration and scheduling) can be completed by the location estimation entity as soon as possible before time T_1. Requests exceeding the threshold (T_1 > T_{nf}) are considered far future requests. In some designs, since some detailed configurations are not available in advance, the response (configuration and scheduling) can be completed through several messages. In some designs, each message includes a partial on-demand PRS configuration. In some designs, before the scheduled T1, the location estimation entity can provide a fully customized PRS configuration. In the context, "fully" means there are no missing PRS parameters causing ambiguity, or the UE does not need to perform blind search. In one example, the location estimation entity may be able to configure on-demand PRS from a far future stationary TRP instead of a mobile anchor. In some designs, the location estimation entity can send several on-demand PRS responses through several LPP messages over a time before the requested time. In some designs, the location estimation entity or the UE can further specify a second timing threshold T_2 at which the location estimation entity must respond with a customized PRS configuration before T_1 - T_2. In some designs, T_2 is designed to provide sufficient time for the UE to adjust its configuration / hardware for on-demand PRS operation. The timing examples in the various examples provided above can be defined with respect to slots, subframes, frames, absolute time, etc.

[0245] Referring to FIGS. 11-12, in some designs as described above, the PRS configuration is received through a plurality of partial PRS configurations that cumulatively define each of a first set of parameters for a scheduled on-demand PRS positioning session.

[0246] 11-12, in some designs, the one or more requests for PRS configurations (e.g., the initial request plus any supplemental requests to modify PRS parameters, etc.) and the one or more responses carrying the PRS configurations may include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions. For example, if a UE requests multiple on-demand PRS configurations that overlap in time (e.g., each with its own individual on-demand PRS request and response(s)), the UE and the position estimation entity may have trouble differentiation signaling associated with the multiple on-demand PRS configurations. In this case, as described above, each of the multiple on-demand PRS configurations may be associated with a unique identifier. In some designs, the unique identifier may be assigned by the transmit side (e.g., the UE). Thus, the UE attaches a new identifier to the request at 1110 in FIG. 11 or 1210 in FIG. 12, and the location estimation entity then associates this new identifier with subsequent signaling associated with the request (e.g., signaling conveying the PRS configuration, signaling from the UE requesting one or more changes to the requested PRS parameters, etc.).

[0247] FIG. 14 illustrates an example implementation 1400 of the processes 1100-1200 of FIG. 11-FIG. 12, respectively, according to one aspect of the disclosure. In particular, the example implementation 1400 relates to on-demand DL PRS in Uu. In FIG. 14, in one example, if the UE does not have information about possible on-demand PRS, the UE may request a desired customized PRS configuration. In FIG. 14, in a further example, if the UE has some pre-configured on-demand PRS, the UE may request a specific reconfiguration or switch to a desired configuration. In general, FIG. 14 illustrates a modified implementation of the process 1000 of FIG. 10.

[0248] Referring to FIG. 14, the LMF 270 sends NRPPa assistance information control to the NG-RAN 1002 (1a), which sends system information to the UE 302 via RRC (1b). Then, a "future" on-demand PRS request is sent by the UE 302 to the AMF 264 (2a), or by the 5GC LCS entity 1080 to the AMF 264 (2b), or generated by the AMF 264 itself (2c). A location request is sent by the AMF 264 to the LMF 270 (3). Instead of setting up a PRS configuration immediately, various LPP procedures are performed (4). As the future time for the on-demand PRS approaches, the LMF 270 determines a new DL PRS configuration for the on-demand PRS (5). NRPPa DL PRS reconfiguration is performed for the new DL PRS configuration (6), and DL PRS transmission is performed using the new configuration (7). The LPP procedure and optionally the NRPPa procedure are performed (8). The LMF transmits a location response to the AMF 264 (9), which transmits (e.g., logically forwards) the location response to the UE 302 (10a), or to the 5GC LCS entity 1080 (10b), or to the AMD 264 (10c). The LMF 270 then restores (11a) the old DL PRS configuration. An NRPPa DL PRS reconfiguration is performed for the old DL PRS configuration (11b), and DL PRS transmission is performed using the old configuration (12).

[0249] FIG. 15 illustrates an example implementation 1500 of the processes 1100-1200 of FIG. 11-12, respectively, according to one aspect of the present disclosure. In particular, FIG. 15 illustrates optional signaling that may occur during the process 1400 of FIG. 14. Referring to FIG. 15, the LMF 270 sends an NRPPA message (type: DL PRS reconfiguration request) to the gNB 304 (1). For example, the reconfiguration request in (1) may occur during (6) or (11b) of FIG. 14. In response, the gNB 304 sends an NRPPa message (type: DL PRS reconfiguration response / failure) to the LMF 270 (2). As discussed above, the reconfiguration request may be allowed or denied based on various constraints (e.g., if it is too early for the parameters to be reconfigured to be set yet, or if it is too late for the parameters to be changed anymore, etc.).

[0250] FIG. 16 illustrates an example implementation 1600 of the processes 1100-1200 of FIG. 11-12, respectively, according to one aspect of the disclosure. In particular, FIG. 16 illustrates optional signaling that may occur during the process 1400 of FIG. 14. With reference to FIG. 14, the gNB 304 transmits a positioning SIB (posSIB) to the UE 302 (1a). The LMF 270 transmits assistance data to the UE 302 via the LPP (1b). The UE 302 may later transmit a request for updated assistance data to the LMF 270 via the LPP (2). In response, the LMF 270 transmits the updated assistance data to the UE 302 via the LPP (3). For example, in (3), the updated assistance data may modify or add or remove one or more PRS parameters to the assistance data from (1b).

[0251] In the above detailed description, it can be seen that various features are grouped together in each example. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the disclosure may include fewer than all features of each disclosed exemplary clause. Thus, the following clauses should be considered to be incorporated in the description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspect(s) of the dependent clause are not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the aspect(s) of the dependent clause with the subject matter of any other dependent clause or independent clause, or combinations of any features with other dependent clauses and independent clauses. Unless a specific combination is not intended (e.g., conflicting aspects such as defining an element as both an insulator and a conductor) is expressly expressed or can be easily inferred, the various aspects disclosed herein expressly include those combinations. It is further contemplated that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0252] The following numbered clauses describe example implementations.

[0253] Clause 1. A method of operating a user equipment (UE), the method comprising: sending a request to a position estimation entity for scheduling an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent; and receiving, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session prior to the future time, the PRS configuration including a second parameter set that is based at least in part on availability of the one or more parameters at the future time.

[0254] Clause 2. The method of clause 1, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0255] Clause 3. The method of clause 1 or 2, wherein the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0256] Clause 4. The method of any one of clauses 1 to 3, wherein the first parameter set includes at least one side link (SL) anchor.

[0257] Clause 5. The method of clause 4, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0258] Clause 6. The method according to clause 4 or 5, wherein one or more parameters that are not determinable at the time the request is sent are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0259] Clause 7. The method of clause 6, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the smallest one of the stationary anchors.

[0260] Clause 8. The method of any one of clauses 1 to 7, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0261] Clause 9. The method of clause 8, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0262] Clause 10. The method of any one of clauses 1 to 9, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0263] Clause 11. The method of clause 10, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0264] Clause 12. A method according to any one of clauses 1 to 11, wherein the PRS configuration is required to be received within a specified time window.

[0265] Clause 13. A method according to any one of clauses 1 to 12, wherein the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled and on-demand PRS positioning sessions.

[0266] Clause 14. The method of any one of clauses 1 to 13, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0267] Clause 15. A method of operating a position estimation entity, the method comprising: receiving a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; determining, in response to the request, availability of the one or more parameters at the future time in advance of the future time; determining a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and, in response to the request, transmitting the PRS configuration to the UE in advance of the future time.

[0268] Clause 16. The method of clause 15, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0269] Clause 17. The method of clause 15 or 16, wherein the request specifies, for each parameter in the first parameter set, whether the respective parameter is mandatory or optional.

[0270] Clause 18. The method of any one of clauses 15 to 17, wherein the first parameter set includes at least one side link (SL) anchor.

[0271] Clause 19. The method of clause 18, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0272] Clause 20. The method according to clause 18 or 19, wherein one or more parameters that are not determinable at the time the request is sent are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0273] Clause 21. The method according to clause 20, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is sent due to lack of mobility of the least one stationary anchor.

[0274] Clause 22. A method according to any one of clauses 15 to 21, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0275] Clause 23. A method according to any one of clauses 22, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0276] Clause 24. The method of any one of clauses 15 to 23, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0277] Clause 25. The method of clause 24, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0278] Clause 26. A method according to any one of clauses 15 to 25, wherein the PRS configuration is required to be received within a specified time window.

[0279] Clause 27. The method of any one of clauses 15 to 26, wherein the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled and on-demand PRS positioning sessions.

[0280] Clause 28. The method of any one of clauses 15 to 27, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0281] Clause 29. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: send, via the at least one transceiver, a request to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent, to a position estimation entity; and receive, in response to the request, via the at least one transceiver, a PRS configuration for the scheduled on-demand PRS positioning session in advance of the future time, the PRS configuration including a second parameter set that is based at least in part on availability of the one or more parameters at the future time.

[0282] Clause 30. The UE of clause 29, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or any combination thereof.

[0283] Clause 31. The UE of clause 29 or 30, wherein the request specifies, for each parameter in the first parameter set, whether the respective parameter is mandatory or optional.

[0284] Clause 32. The UE of any one of clauses 29 to 31, wherein the first parameter set includes at least one sidelink (SL) anchor.

[0285] Clause 33. The UE of clause 32, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0286] Clause 34. The UE of clause 32 or 33, wherein one or more parameters that are not determinable at the time the request is sent are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0287] Clause 35. The UE of clause 34, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is sent due to lack of mobility of the smallest one stationary anchor.

[0288] Clause 36. The UE of any one of clauses 29 to 35, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0289] Clause 37. The UE of clause 36, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0290] Clause 38. The UE of any one of clauses 29 to 37, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0291] Clause 39. The UE of clause 38, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0292] Clause 40. The UE of any one of clauses 29 to 39, wherein the PRS configuration is required to be received within a specified time window.

[0293] Clause 41. A UE as claimed in any one of clauses 29 to 40, wherein the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0294] Clause 42. A UE as described in any one of clauses 29 to 41, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0295] Clause 43. A position estimation entity comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to receive, via the at least one transceiver, a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; in response to the request, determine availability of the one or more parameters at the future time in advance of the future time; determine a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and transmit, in response to the request, via the at least one transceiver, the PRS configuration in advance of the future time to the UE.

[0296] Clause 44. The position estimation entity of clause 43, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0297] Clause 45. The position estimation entity of clause 43 or 44, wherein the request specifies, for each parameter in the first parameter set, whether the respective parameter is mandatory or optional.

[0298] Clause 46. A position estimation entity according to any one of clauses 43 to 45, wherein the first parameter set includes at least one side link (SL) anchor.

[0299] Clause 47. The position estimation entity of clause 46, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0300] Clause 48. A position estimation entity according to clause 46 or 47, wherein one or more parameters are associated with at least one SL anchor that are not determinable at the time the request is sent due to the mobility of the at least one SL anchor.

[0301] Clause 49. The position estimation entity of clause 48, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the smallest one of the stationary anchors.

[0302] Clause 50. A location estimation entity according to any one of clauses 43 to 49, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0303] Clause 51. A location estimation entity as described in clause 50, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0304] Clause 52. A position estimation entity according to any one of clauses 43 to 51, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0305] Clause 53. The position estimation entity of clause 52, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0306] Clause 54. A position estimation entity according to any one of clauses 43 to 53, wherein the PRS configuration is required to be received within a specified time window.

[0307] Clause 55. A position estimation entity according to any one of clauses 43 to 54, wherein the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled and on-demand PRS positioning sessions.

[0308] Clause 56. A position estimation entity as described in any one of clauses 43 to 55, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0309] Clause 57. A user equipment (UE), comprising: means for sending a request to a location estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent; and means for receiving, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session prior to the future time, the PRS configuration including a second parameter set based at least in part on availability of the one or more parameters at the future time.

[0310] Clause 58. The UE of clause 57, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or any combination thereof.

[0311] Clause 59. The UE of clause 57 or 58, wherein the request specifies, for each parameter in the first parameter set, whether the respective parameter is mandatory or optional.

[0312] Clause 60. The UE of any one of clauses 57 to 59, wherein the first parameter set includes at least one sidelink (SL) anchor.

[0313] Clause 61. The UE of clause 60, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0314] Clause 62. The UE of clause 60 or 61, wherein one or more parameters that are not determinable at the time the request is sent are associated with at least one SL anchor due to mobility of the at least one SL anchor.

[0315] Clause 63. The UE of clause 62, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the smallest one stationary anchor.

[0316] Clause 64. The UE of any one of clauses 57 to 63, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0317] Clause 65. The UE of clause 64, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0318] Clause 66. The UE of any one of clauses 57 to 65, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0319] Clause 67. The UE of clause 66, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0320] Clause 68. The UE of any one of clauses 57 to 67, wherein the PRS configuration is required to be received within a specified time window.

[0321] Clause 69. The UE of any one of clauses 57 to 68, wherein the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for scheduled and on-demand PRS positioning sessions.

[0322] Clause 70. A UE as described in any one of clauses 57 to 69, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0323] Clause 71. A position estimation entity comprising: means for receiving a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; means for determining, in response to the request, availability of the one or more parameters at the future time in advance of the future time; means for determining a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and means for transmitting, in response to the request, the PRS configuration to the UE in advance of the future time.

[0324] Clause 72. The position estimation entity of clause 71, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0325] Clause 73. The location estimation entity of clause 71 or 72, wherein the request specifies, for each parameter in the first parameter set, whether the respective parameter is mandatory or optional.

[0326] Clause 74. A position estimation entity according to any one of clauses 71 to 73, wherein the first parameter set includes at least one side link (SL) anchor.

[0327] Clause 75. The position estimation entity of clause 74, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0328] Clause 76. A position estimation entity according to clause 74 or 75, wherein one or more parameters are associated with at least one SL anchor that are not determinable at the time the request is sent due to mobility of the at least one SL anchor.

[0329] Clause 77. The position estimation entity of clause 76, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the smallest one of the stationary anchors.

[0330] Clause 78. A position estimation entity as claimed in any one of clauses 71 to 77, wherein the request specifies a time in the future via an indication of a preferred start time and duration.

[0331] Clause 79. A location estimation entity as described in clause 78, wherein the preferred start time and duration are specified via a set of slots, subframes or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0332] Clause 80. The position estimation entity of any one of clauses 71 to 79, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0333] Clause 81. The position estimation entity of clause 80, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0334] Clause 82. A location estimation entity according to any one of clauses 71 to 81, wherein the PRS configuration is required to be received within a specified time window.

[0335] Clause 83. A position estimation entity according to any one of clauses 71 to 82, wherein the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled and on-demand PRS positioning sessions.

[0336] Clause 84. A position estimation entity as described in any one of clauses 71 to 83, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0337] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to send a request to a position estimation entity to schedule an on-demand positioning reference signal (PRS) positioning session for the UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is sent, and receive, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session in advance of the future time, the PRS configuration including a second parameter set that is based at least in part on availability of the one or more parameters at the future time.

[0338] Clause 86. The non-transitory computer-readable medium of clause 85, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0339] Clause 87. The non-transitory computer-readable medium of clause 85 or 86, wherein the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0340] Clause 88. The non-transitory computer-readable medium of any one of clauses 85 to 87, wherein the first parameter set includes at least one sidelink (SL) anchor.

[0341] Clause 89. The non-transitory computer-readable medium of clause 88, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0342] Clause 90. The non-transitory computer-readable medium of clause 88 or 89, wherein one or more parameters are associated with at least one SL anchor that are not determinable at the time the request is transmitted due to mobility of the at least one SL anchor.

[0343] Clause 91. The non-transitory computer-readable medium of clause 90, wherein one or more other parameters for at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the smallest one of the stationary anchors.

[0344] Clause 92. The non-transitory computer-readable medium of any one of clauses 85 to 91, wherein the request specifies a future time via an indication of a preferred start time and duration.

[0345] Clause 93. The non-transitory computer-readable medium of clause 92, wherein the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0346] Clause 94. The non-transitory computer-readable medium of any one of clauses 85 to 93, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0347] Clause 95. The non-transitory computer-readable medium of clause 94, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0348] Clause 96. The non-transitory computer-readable medium of any one of clauses 85 to 95, wherein the PRS configuration is required to be received within a specified time window.

[0349] Clause 97. The non-transitory computer-readable medium of any one of clauses 85 to 96, wherein the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0350] Clause 98. The non-transitory computer-readable medium of any one of clauses 85 to 97, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0351] Clause 99. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to receive a request to schedule an on-demand positioning reference signal (PRS) positioning session for a user equipment (UE) at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, where availability of one or more parameters of the first parameter set at the future time is not determinable at the time the request is received; determine, in response to the request, availability of the one or more parameters at the future time in advance of the future time; determine a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set based at least in part on the determination of availability of the one or more parameters at the future time; and transmit, in response to the request, the PRS configuration to the UE in advance of the future time.

[0352] Clause 100. The non-transitory computer-readable medium of clause 99, wherein the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

[0353] Clause 101. The non-transitory computer-readable medium of clause 99 or 100, wherein the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

[0354] Clause 102. The non-transitory computer-readable medium of any one of clauses 99 to 101, wherein the first parameter set includes at least one sidelink (SL) anchor.

[0355] Clause 103. The non-transitory computer-readable medium of clause 102, wherein the first set of parameters includes, for at least one SL anchor, a SL beam direction, a SL bandwidth or bandwidth portion (BWP), a synchronization signal block (SSB) configuration, or a combination thereof.

[0356] Clause 104. The non-transitory computer-readable medium of clause 102 or 103, wherein one or more parameters are associated with at least one SL anchor that are not determinable at the time the request is sent due to mobility of the at least one SL anchor.

[0357] Clause 105. The non-transitory computer-readable medium of clause 104, wherein one or more other parameters for the at least one stationary anchor are determinable at the time the request is transmitted due to lack of mobility of the least one stationary anchor.

[0358] Clause 106. The non-transitory computer-readable medium of any one of clauses 99 to 105, wherein the request specifies a future time via an indication of a preferred start time and duration.

[0359] Clause 107. The non-transitory computer-readable medium of clause 106, wherein the preferred start time and duration are specified via a set of slots, subframes, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration.

[0360] Clause 108. The non-transitory computer-readable medium of any one of clauses 99 to 107, wherein at least one parameter in the first parameter set is associated with at least one time constraint.

[0361] Clause 109. The non-transitory computer-readable medium of clause 108, wherein at least one time constraint limits when at least one parameter may be requested, modified, or removed from association with a scheduled on-demand PRS positioning session.

[0362] Clause 110. The non-transitory computer-readable medium of any one of clauses 99 to 109, wherein the PRS configuration is required to be received within a specified time window.

[0363] Clause 111. The non-transitory computer-readable medium of any one of clauses 99 to 110, wherein the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of a first parameter set for a scheduled on-demand PRS positioning session.

[0364] Clause 112. The non-transitory computer-readable medium of any one of clauses 99 to 111, wherein the one or more requests for PRS configuration and the one or more responses conveying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions.

[0365] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0366] Moreover, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0367] The various example logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0368] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0369] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0370] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described herein do not have to be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. [Explanation of symbols]

[0371] 102 Base station 102' Small Cell Base Station 110 Geographic Coverage Areas 110' Geographical Coverage Area 112 Earth orbiting space vehicle (SV) 120 Communication Links 122 backhaul links 124 signal 128 Direct Connection 134 backhaul links 150 Access Points (AP) 150 Access Points 152 Wireless local area network (WLAN) station (STA) 154 Communication Links 160 Side Link 170 Core Network 172 Location Server 180 mmW base station 184 mmW communication link 192 P2P links 194 P2P Links 200 Wireless Network Structure 212 User Plane Functions 213 User Plane Interface (NG-U) 214 Control Plane Functions 215 control plane interface (NG-C) 220 NG-RAN 223 Backhaul Connection 226 Central Unit (gNB-CU) 228 Distributed Unit (gNB-DU) 230 Location Server 232 Interface 250 Wireless Network Structure 262 User Plane Function (UPF) 263 User Plane Interface H.264 Access and Mobility Management Function (AMF) 265 Control Plane Interface 266 Session Management Function (SMF) 300GHz band 304 base station 306 Network Entities 310 WWAN Transceiver 312 Receiver 314 Transmitter 316 Antenna 318 Signal 320 Short Range Wireless Transceiver 322 Receiver 324 Transmitter 326 Antenna 328 signal 330 Satellite signal receiver 332 processor 334 Data Bus 336 Antenna 338 Communication Signals 340 Memory 342 On-Demand PRS Components 344 Sensors 346 User Interface 350 Transceiver 350 WWAN Transceiver 352 Receiver 354 Transmitter 356 Antenna 358 Signal 360 Short Range Wireless Transceiver 362 Receiver 364 Transmitter 366 Antenna 368 signals 370 Satellite signal receiver 376 Antenna 378 Communication Signals 380 Network Transceiver 382 Data Bus 384 processor 386 memory 388 On-Demand PRS Components 390 Network Transceiver 392 Data Bus 394 processor 396 Memory 398 On-Demand PRS Components 514 Second PRS Resource 700 PRS configuration 710 PRS Resource Set 712 No. 1 PRS Resource 720a instance 720b instance 910 Scenario 920 Scenario 930 Scenario 940 Scenario 1000 UE positioning operations 1002 NG-RAN nodes 1080 5GC LCS Entity 1300 PRS parameters

Claims

1. A method of operating a user equipment (UE), comprising: sending a request to a positioning entity for scheduling an on-demand positioning reference signal (PRS) positioning session of the UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, wherein the availability of one or more parameters of the first parameter set at the future time is indeterminable when the request is sent; receiving, prior to the future time in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set that is at least partially based on the availability of the one or more parameters at the future time.

2. The method according to claim 1, wherein the PRS configuration includes a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof.

3. The method according to claim 1, wherein the request specifies, for each parameter in the first parameter set, whether the individual parameter is mandatory or optional.

4. The first parameter set includes at least one sidelink (SL) anchor, and the first parameter set includes, for the at least one SL anchor, an SL beam direction, an SL bandwidth or bandwidth part (BWP), a synchronization signal block (SSB) configuration, or a combination thereof. The method according to claim 1.

5. The first parameter set includes at least one sidelink (SL) anchor, and the one or more parameters that are indeterminable when the request is sent are associated with the at least one SL anchor due to the mobility of the at least one SL anchor. The method according to claim 1.

6. One or more other parameters for at least one static anchor are determinable when the request is sent due to the lack of mobility of the smallest static anchor. The method according to claim 5.

7. The request specifies the future time via an indication of a preferred start time and duration, the preferred start time and duration are specified via a set of slots, sub - frames, or frames, or the preferred start time and duration are specified in absolute time, or the preferred start time and duration are specified with reference to future measurement gaps or PRS occasions of the current PRS configuration The method according to claim 1.

8. at least one parameter within the first parameter set is associated with at least one time constraint, the at least one time constraint restricts when the at least one parameter can be requested, modified, or removed from its association with the scheduled on - demand PRS positioning session The method according to claim 1, or the PRS configuration is required to be received within a specified time window The method according to claim 1, or the PRS configuration is received via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled on - demand PRS positioning session The method according to claim 1, or one or more requests for the PRS configuration and one or more responses carrying the PRS configuration include an identifier configured to distinguish the scheduled on - demand PRS positioning session from one or more other scheduled on - demand PRS positioning sessions The method according to claim 1.

9. A method of operating a location estimation entity, comprising: receiving a request for scheduling an on - demand positioning reference signal (PRS) positioning session of a user equipment (UE) at a future time, the request being configured to request a first parameter set for the scheduled on - demand PRS positioning session, wherein the availability of one or more parameters of the first parameter set at the future time is indeterminable when the request is received; determining, prior to the future time and in response to the request, the availability of the one or more parameters at the future time; A PRS configuration for the scheduled on-demand PRS positioning session, the method comprising determining a PRS configuration comprising a second set of parameters based at least in part on the determination of the availability of the one or more parameters at the future time. In response to the request, prior to the future time, transmitting the PRS configuration to the UE. **Claim 10** The method according to claim 9, wherein the PRS configuration comprises a downlink (DL) PRS configuration, an uplink (UL) PRS configuration, a sidelink (SL) PRS configuration, or a combination thereof. **Claim 11** The method according to claim 9, wherein the request specifies, for each parameter in the first set of parameters, whether the individual parameter is essential or optional. **Claim 12** The first set of parameters includes at least one sidelink (SL) anchor. The first set of parameters includes, for the at least one SL anchor, an SL beam direction, an SL bandwidth or bandwidth part (BWP), a synchronization signal block (SSB) configuration, or a combination thereof. The method according to claim 9. **Claim 13** The first set of parameters includes at least one sidelink (SL) anchor. The method according to claim 9, wherein the one or more parameters that are not determinable when the request is transmitted are associated with the at least one SL anchor due to the mobility of the at least one SL anchor. **Claim 14** The method according to claim 13, wherein one or more other parameters for at least one stationary anchor are determinable when the request is transmitted due to the lack of mobility of the smallest stationary anchor. **Claim 15** The request specifies the future time via an indication of a preferred start time and duration, wherein the preferred start time and duration are specified via a set of slots, subframes, or frames, or wherein the preferred start time and duration are specified in absolute time, or wherein the preferred start time and duration are specified with reference to a future measurement gap or PRS occasion of the current PRS configuration. The method according to claim 9. **Claim 16** At least one parameter in the first set of parameters is associated with at least one time constraint. The at least one time constraint limits when the at least one parameter can be requested, modified, or removed from association with the scheduled on-demand PRS positioning session The method according to claim 9, or the PRS configuration is required to be received within a specified time window The method according to claim 9, or the PRS configuration is transmitted via a plurality of partial PRS configurations that cumulatively define each of the first parameter sets for the scheduled on-demand PRS positioning session The method according to claim 9, or one or more requests for the PRS configuration and one or more responses carrying the PRS configuration include an identifier configured to distinguish the scheduled on-demand PRS positioning session from one or more other scheduled on-demand PRS positioning sessions The method according to claim 9

17. A user equipment (UE) comprising a memory; at least one transceiver; 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 to schedule an on-demand positioning reference signal (PRS) positioning session of the UE at a future time, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, wherein the availability of one or more parameters of the first parameter set at the future time is indeterminable when the request is transmitted, to a positioning entity and the at least one processor being configured to receive, via the at least one transceiver, in response to the request, a PRS configuration for the scheduled on-demand PRS positioning session prior to the future time, the PRS configuration including a second parameter set based at least in part on the availability of the one or more parameters at the future time A UE comprising the above

18. A positioning entity comprising a memory; at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver A request for scheduling an on-demand positioning reference signal (PRS) positioning session of a user equipment (UE) at a future time via the at least one transceiver, the request being configured to request a first parameter set for the scheduled on-demand PRS positioning session, wherein the availability of one or more parameters of the first parameter set at the future time is indeterminable when the request is received, receiving the request, Determining, prior to the future time, the availability of the one or more parameters at the future time in response to the request; Determining a PRS configuration for the scheduled on-demand PRS positioning session, the PRS configuration including a second parameter set that is at least partially based on the determination of the availability of the one or more parameters at the future time; A positioning entity comprising at least one processor configured to transmit, via the at least one transceiver, the PRS configuration to the UE prior to the future time in response to the request. **Claim 19**: The at least one processor is the positioning entity according to claim 17, configured to execute the method according to any one of claims 2 to 8, of a UE, or the at least one processor is the positioning entity according to claim 18, configured to execute the method according to any one of claims 10 to 16, of a UE.

Images