CN117678291A - Controlling repeated requests from User Equipment (UE) for positioning assistance in a wireless network - Google Patents

Abstract

Techniques for wireless positioning are disclosed. In an aspect, a User Equipment (UE) sends a first request assistance data message to a location server, the first request assistance data message comprising a request for first positioning assistance; receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

Description

Controlling repeated requests from User Equipment (UE) for positioning assistance in a wireless network

Technical Field

Aspects of the present disclosure relate generally to wireless communications.

Background

Wireless communication systems have evolved over many generations including first generation analog radiotelephone services (1G), second generation (2G) digital radiotelephone services (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, internet-capable wireless services, and fourth generation (4G) services (e.g., long Term Evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular and Personal Communication Services (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), as well as 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.

The fifth generation (5G) wireless standard, known as new air interface (NR), requires higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the next generation mobile network alliance, the 5G standard is designed to provide tens of megabits per second data rate to each of tens of thousands of users, with 1 gigabit per second data rate being provided to tens of staff on an office floor. To support large sensor deployments, hundreds of thousands of simultaneous connections should be supported. Therefore, the spectral efficiency of 5G mobile communication should be significantly improved compared to the current 4G standard. Furthermore, the signaling efficiency should be improved and the delay should be significantly reduced compared to the current standard.

Disclosure of Invention

The following presents a simplified summary in relation to one or more aspects disclosed herein. Thus, the following summary is not to be considered an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all contemplated aspects nor delineate the scope associated with any particular aspect. Accordingly, the sole purpose of the summary below is to present some concepts related to one or more aspects related to the mechanisms disclosed herein in a simplified form prior to the detailed description that is presented below.

In an aspect, a wireless location method performed by a User Equipment (UE) includes: transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

In one aspect, a positioning method performed by a location server includes: receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

In an aspect, a User Equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: transmitting, via the at least one transceiver, a first request assistance data message to a location server, the first request assistance data message comprising a request for first positioning assistance; receiving, via the at least one transceiver, a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and transmitting, via the at least one transceiver, a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: receiving, via the at least one transceiver, a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting, via the at least one transceiver, a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving, via the at least one transceiver, a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

In an aspect, a User Equipment (UE) includes: means for sending a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; means for receiving a provide assistance data message from a location server, the provide assistance data message indicating that the location server is currently unable to provide first positioning assistance; and means for sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

In one aspect, a location server includes: means for receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; means for sending a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and means for receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to: transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the drawings and the detailed description.

Drawings

The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration and not limitation of the various aspects.

Fig. 1 illustrates an example wireless communication system in accordance with aspects of the present disclosure.

Fig. 2A and 2B illustrate example wireless network structures in accordance with aspects of the present disclosure.

Fig. 3A, 3B, and 3C are simplified block diagrams of several example aspects of components that may be employed in a User Equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

Fig. 4 illustrates examples of various positioning methods supported in a new air interface (NR) in accordance with aspects of the present disclosure.

Fig. 5 illustrates an example Long Term Evolution (LTE) positioning protocol (LPP) call flow between a UE and a location server for performing positioning operations.

Fig. 6 is a diagram illustrating an example frame structure in accordance with aspects of the present disclosure.

Fig. 7A and 7B illustrate examples of a location server initiated on-demand Positioning Reference Signal (PRS) positioning procedure in accordance with aspects of the present disclosure.

FIG. 8A illustrates an example of an on-demand PRS positioning process, according to aspects of the present disclosure.

Fig. 8B illustrates an example of a positioning process in accordance with aspects of the present disclosure.

FIG. 9 illustrates an example of an on-demand PRS positioning process for a plurality of positioning methods, in accordance with aspects of the present disclosure.

Fig. 10 illustrates an example method for suspending a positioning session due to incorrect or insufficient assistance data in accordance with current practice.

Fig. 11 illustrates an example method for reporting requirements for a new PRS configuration in accordance with aspects of the present disclosure.

Fig. 12 and 13 illustrate example positioning methods according to aspects of the present disclosure.

Detailed Description

Aspects of the disclosure are provided in the following description and related drawings for various examples provided for purposes of illustration. Alternative aspects may be devised without departing from the scope of the disclosure. In addition, 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.

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. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

Those of skill in the art would understand that 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, on the desired design, on the corresponding technology, and so forth.

Furthermore, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application Specific Integrated Circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered to be embodied entirely within any form of non-transitory computer readable storage medium having stored therein a corresponding set of computer instructions that upon execution would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. Additionally, for each of the aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to" perform the described action.

As used herein, unless otherwise indicated, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE may be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset location device, wearable device (e.g., smart watch, glasses, augmented Reality (AR)/Virtual Reality (VR) head-mounted device, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), internet of things (IoT) device, etc. The UE may be mobile or may be stationary (e.g., at certain times) and may be in communication with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "access terminal" or "AT," "client device," "wireless 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, and through the core network, the UE may connect with external networks such as the internet as well as with other UEs. Of course, other mechanisms of connecting to the core network and/or the internet are possible for the UE, such as through 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 specification, etc.), and so forth.

A base station may operate according to one of several RATs to communicate with a UE depending on the network in which the base station is deployed, and may alternatively be referred to as an Access Point (AP), a network node, a node B, an evolved node B (eNB), a next generation eNB (ng-eNB), a new air interface (NR) node B (also referred to as a gNB or gndeb), and so on. The base station may be primarily used to support wireless access for UEs, including supporting data, voice, and/or signaling connections for the supported UEs. In some systems, the base station may provide only edge node signaling functionality, while in other systems it may provide additional control and/or network management functionality. The communication link through which a UE can communicate signals to a base station is called an Uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which a base station can transmit signals to a UE is called a Downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term "Traffic Channel (TCH)" may refer to an uplink/reverse or downlink/forward traffic channel.

The term "base station" may refer to a single physical Transmission Reception Point (TRP) or multiple physical TRPs that may or may not be co-located. For example, in the case where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to the cell (or several cell sectors) of the base station. In the case where the term "base station" refers to a plurality of co-located physical TRP, the physical TRP may be an antenna array of the base station (e.g., as in a Multiple Input Multiple Output (MIMO) system or where the base station employs beamforming). In the case where the term "base station" refers to a plurality of non-co-located physical TRPs, the physical TRPs may be a Distributed Antenna System (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a Remote Radio Head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station receiving measurement reports from the UE and a neighboring base station whose reference Radio Frequency (RF) signal is being measured by the UE. Because as used herein, a TRP is a point at which a base station transmits and receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to a particular TRP of a base station.

In some implementations supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and/or signaling connections for the UE), but may instead send reference signals to the UE to be measured by the UE, and/or may receive and measure signals sent by the UE. Such base stations may be referred to as positioning towers (e.g., in the case of transmitting signals to a UE) and/or as position measurement units (e.g., in the case of receiving and measuring signals from a UE).

An "RF signal" comprises electromagnetic waves of a given frequency that transmit information through a 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, due to the propagation characteristics of the RF signals through the multipath channel, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and the receiver may be referred to as a "multipath" RF signal. As used herein, where the term "signal" refers to a wireless signal or RF signal, as clear from the context, an RF signal may also be referred to as a "wireless signal" or simply "signal.

Fig. 1 illustrates an example wireless communication system 100 in accordance with aspects of the present disclosure. The wireless communication system 100, which may also be referred to as a Wireless Wide Area Network (WWAN), may include various base stations 102 (labeled "BSs") and various UEs 104. Base station 102 may include a macrocell base station (high power cellular base station) and/or a small cell base station (low power cellular base station). In an aspect, the macrocell base station may include an eNB and/or a ng-eNB (where wireless communication system 100 corresponds to an LTE network), or a gNB (where wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include a femtocell, a picocell, a microcell, and so on.

The base stations 102 may collectively form a RAN and interact with a core network 170 (e.g., an Evolved Packet Core (EPC) or a 5G core (5 GC)) through a backhaul link 122 and with 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 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 directly or indirectly with the location server 172. 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 via another path, such as via an application server (not shown), via another network, such as via a Wireless Local Area Network (WLAN) Access Point (AP) (e.g., AP 150 described below), and so forth. 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, etc.) or a direct connection (e.g., as shown via the direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

Among other functions, the base station 102 may perform functions related to one or more of the following: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia Broadcast Multicast Services (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through EPC/5 GC) over a backhaul link 134, which may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity for communicating with a base station (e.g., on some frequency resource, referred to as a carrier frequency, component carrier, frequency band, etc.), and may be associated with an identifier (e.g., physical Cell Identifier (PCI), enhanced Cell Identifier (ECI), virtual Cell Identifier (VCI), cell Global Identifier (CGI), etc.) for distinguishing between cells operating via 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 other protocol types) that may provide access for different types of UEs. Because a cell is supported by a particular base station, the term "cell" may refer to either or both of a logical communication entity and the base station supporting it, depending on the context. Furthermore, because TRP is typically the 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 of a base station (e.g., a sector) as long as the carrier frequency can be detected and used for communication within some portion of the geographic coverage area 110.

Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with a larger geographic coverage area 110. For example, a small cell base station 102 '(labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network comprising both small cell base stations and macro cell base stations may be referred to as a heterogeneous network. The heterogeneous network may also include home enbs (henbs) that may provide services to a restricted group called a Closed Subscriber Group (CSG).

The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and/or Downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use MIMO antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. Communication link 120 may be over 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 to the downlink than to the uplink).

The wireless communication system 100 may also include a Wireless Local Area Network (WLAN) Access Point (AP) 150 in unlicensed spectrum (e.g., 5 GHz) that communicates with a WLAN Station (STA) 152 via a communication link 154. When communicating in the unlicensed spectrum, WLAN STA 152 and/or WLAN AP 150 may perform a Clear Channel Assessment (CCA) or Listen Before Talk (LBT) procedure prior to communication in order to determine whether a channel is available.

The small cell base station 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5GHz unlicensed spectrum as used by the WLAN AP 150. The use of LTE/5G small cell base stations 102' in the unlicensed spectrum may improve access network coverage and/or increase access network capacity. NR in the unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, licensed Assisted Access (LAA), or multewire.

The wireless communication system 100 may also include a millimeter wave (mmW) base station 180 that may operate at mmW frequencies and/or near mmW frequencies to communicate with the UE 182. Extremely High Frequency (EHF) is a part of the RF in the electromagnetic spectrum. EHF has a range of 30GHz to 300GHz, with wavelengths between 1 millimeter and 10 millimeters. The radio waves in this band may be referred to as millimeter waves. The near mmW can be extended down to a frequency of 3GHz with a wavelength of 100 mm. The ultra-high frequency (SHF) band extends between 3GHz and 30GHz, which is also known as a centimeter wave. Communications using mmW/near mmW radio frequency bands have high path loss 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 extremely high path loss and short distances. Further, it should be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it is to be understood that the foregoing illustration is merely an example and should not be construed as limiting the various aspects disclosed herein.

Transmit beamforming is a technique for focusing RF signals in a particular direction. Conventionally, 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 (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitted, the network node may control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, a network node may use an antenna array (referred to as a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antenna. In particular, RF currents from the transmitters are fed to the respective antennas in a correct phase relationship such that radio waves from the separate antennas add together to increase radiation in the desired direction while canceling to suppress radiation in the undesired direction.

The transmit beams may be quasi co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the transmit antennas of the network node itself are physically co-located. In NR, there are four types of quasi co-located (QCL) relationships. In particular, a QCL relationship of a given type means that certain parameters with respect to a second reference RF signal on a second beam can be derived from information with respect to a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type a, the receiver may use the source reference RF signal to estimate the doppler shift, doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver may use the source reference RF signal to estimate the doppler shift and doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver may 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 may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and/or adjust the phase setting of the antenna array in a particular direction to amplify (e.g., increase the gain level of) an RF signal received from that direction. Thus, when the receiver is said to beam-form in a certain direction, this means that the beam gain in that direction is high relative to the beam gain in other directions, or that the beam gain in that direction is highest compared to the beam gain 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 the RF signal received from that direction.

The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived from information about the first beam (e.g., the receive beam or the transmit beam) of the first reference signal. For example, the UE may use a particular receive beam to receive a reference downlink reference signal (e.g., a Synchronization Signal Block (SSB)) from the base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a Sounding Reference Signal (SRS)) to the base station based on the parameters of the receive beam.

Note that depending on the entity forming the "downlink" beam, this beam may be either the transmit beam or the receive beam. For example, if the base station is forming a downlink beam to transmit reference signals to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, it is a reception beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam may be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink reception beam, and if the UE is forming an uplink beam, it is an uplink transmission beam.

Electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency/wavelength. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" frequency band in various documents and articles. With respect to FR2, a similar naming problem sometimes occurs, which is commonly (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Furthermore, 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 names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

In view of the above, unless specifically stated otherwise, it is to be understood that, if used herein, the term "below 6GHz" and the like may broadly represent frequencies that may be less than 6GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless specifically stated otherwise, it is to be understood that if the term "millimeter wave" or the like is used herein, it may be broadly meant to include mid-band frequencies, frequencies that may be within FR2, FR4-a or FR4-1 and/or FR5, or frequencies that may be within the EHF band.

In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on a primary frequency (e.g., FR 1) used by the UE 104/182 and the cell in which the UE 104/182 performs an initial Radio Resource Control (RRC) connection establishment procedure or initiates an RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and may be a carrier in a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR 2), where once an RRC connection is established between the UE 104 and the anchor carrier, the carrier may be configured and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals, e.g., since the primary uplink and downlink carriers are typically UE-specific, those 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 is true for the uplink primary carrier. The network can change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on the different carriers. Because the "serving cell" (whether the PCell or SCell) corresponds to the carrier frequency/component carrier on which a certain base station communicates, the terms "cell," "serving cell," "component carrier," "carrier frequency," and the like may be used interchangeably.

For example, still referring to fig. 1, one of the frequencies used by the macrocell base station 102 may be an anchor carrier (or "PCell") and the other frequencies used by the macrocell base station 102 and/or the mmW base station 180 may be secondary carriers ("scells"). The simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission and/or reception rate. For example, two 20MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained for a single 20MHz carrier.

The wireless communication system 100 may also include a UE 164 that may communicate with the macrocell base station 102 via a communication link 120 and/or with the mmW base station 180 via a mmW communication 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.

In some cases, UE 164 and UE 182 may be capable of side link communication. A side-link capable UE (SL-UE) may communicate with base station 102 over communication link 120 using a Uu interface (i.e., an air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over wireless side link 160 using a PC5 interface (i.e., an air interface between side link capable UEs). The wireless side link (or simply "side link") is an adaptation of the core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without requiring the communication to pass through the base station. The side link communication may be unicast or multicast and may be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, internet of vehicles (V2X) communication (e.g., cellular V2X (cV 2X) communication, enhanced V2X (eV 2X) communication, etc.), emergency rescue applications, and the like. One or more of a group of SL-UEs communicating with a side link may be located within geographic coverage area 110 of base station 102. Other SL-UEs in such a group may be outside of the geographic coverage area 110 of the base station 102 or otherwise unable to receive transmissions from the base station 102. In some cases, groups of SL-UEs communicating via side link communications may utilize a one-to-many (1:M) system, where each SL-UE transmits to each other SL-UE in the group. In some cases, base station 102 facilitates scheduling of resources for side link communications. In other cases, side-link communications are performed between SL-UEs without involving base station 102.

In an aspect, the side link 160 may operate over a wireless communication medium of interest that may be shared with other vehicles and/or other infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and/or spatial communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter/receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared between the various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC)) these systems, particularly those employing small cell access points, have recently expanded operation into unlicensed frequency bands such as unlicensed national information infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technology, most notably IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi. Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

It should be noted that although fig. 1 only shows two of these UEs as SL-UEs (i.e., UEs 164 and 182), any of the UEs shown may be SL-UEs. Furthermore, although only UE 182 is described as being capable of beamforming, any of the UEs shown (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base stations 102, 180, small cell 102', access point 150), etc. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on side link 160.

In the example of fig. 1, any one of the UEs shown (shown as a single UE 104 in fig. 1 for simplicity) may receive signals 124 from one or more geospatial vehicles (SVs) 112 (e.g., satellites). In an aspect, SV 112 may be part of a satellite positioning system that UE 104 may use as a standalone source of location information. Satellite positioning systems typically include a transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SV 112, the transmitter may sometimes be located on a ground-based control station, base station 102, and/or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 in order to derive geographic location information from SV 112.

In a satellite positioning system, the use of signals 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enable use with one or more global and/or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation Systems (WAAS), european Geosynchronous Navigation Overlay Services (EGNOS), multi-functional satellite augmentation systems (MSAS), global Positioning System (GPS) assisted geographic augmentation navigation, or GPS and geographic augmentation navigation systems (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and/or regional navigation satellites associated with such one or more satellite positioning systems.

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

The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communications via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links")A network. In the example of fig. 1, the UE 190 has a D2D P P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., the UE 190 may indirectly obtain cellular connectivity over the D2D P2P link) and a D2D P P link 194 with the WLAN STA 152 connected to the WLAN AP 150 (the UE 190 may indirectly obtain WLAN-based internet connectivity over the D2D P P link). 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),Etc.

Fig. 2A illustrates an example wireless network structure 200. For example, the 5gc 210 (also referred to as a Next Generation Core (NGC)) may be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to a data network, IP routing, etc.), which cooperate 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 and specifically to the user plane function 212 and the control plane function 214, respectively. In further configurations, the NG-eNB 224 can also connect to the 5GC 210 via the NG-C215 to the control plane function 214 and the NG-U213 to the user plane function 212. Further, 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 NG-enbs 224 and gnbs 222. Either (or both) of the gNB 222 or the ng-eNB 224 can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

Another optional aspect may include a location server 230 that may communicate with the 5gc 210 to provide location assistance for the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or may alternatively each correspond to a single server. The location server 230 may be configured to support one or more location services for UEs 204 that may be connected 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).

Fig. 2B illustrates another example wireless network structure 250. The 5gc 260 (which may correspond to the 5gc 210 in fig. 2A) may be functionally regarded as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a User Plane Function (UPF) 262, which cooperate to form a core network (i.e., the 5gc 260). Functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, delivery of Session Management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and Session Management Function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, delivery of Short Message Service (SMs) messages between a UE 204 and a Short Message Service Function (SMSF) (not shown), and security anchoring functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204 and receives an intermediate key established as a result of the UE 204 authentication procedure. In the case of authentication based on UMTS (universal mobile telecommunications system) subscriber identity module (USIM), AMF 264 extracts security material from AUSF. The functions of AMF 264 also include Security Context Management (SCM). The SCM receives a key from the SEAF, which uses the key to derive an access network specific key. The functionality of AMF 264 also includes location service management for policing services, delivery of location service messages for use between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), delivery of location service messages for use between NG-RAN 220 and LMF 270, evolved Packet System (EPS) bearer identifier assignment for use in interoperation with EPS, and UE 204 mobility event notification. In addition, AMF 264 also supports functions for non-3 GPP (third generation partnership project) access networks.

The functions of UPF 262 include: acting as an anchor point for intra-RAT/inter-RAT mobility (when applicable), acting as an external Protocol Data Unit (PDU) session point to an interconnect to a data network (not shown), providing packet routing and forwarding, 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) handling of the user plane (e.g., uplink/downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (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 transmitting and forwarding one or more "end marks" to the source RAN node. UPF 262 may also support the transfer of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

The functions of the SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration at the UPF 262 for routing traffic to the correct destination, policy enforcement and partial control of QoS, and downlink data notification. The interface used by the SMF 266 to communicate with the AMF 264 is referred to as the N11 interface.

Another optional aspect may include an LMF 270 that may be in communication with the 5gc 260 to provide location assistance for 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 distributed across multiple physical servers, etc.), or may alternatively each 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 the core network 5gc 260 and/or via the internet (not shown). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third party server 274) on a user plane (e.g., using protocols intended to carry voice and/or data, such as Transmission Control Protocol (TCP) and/or IP).

Yet another optional aspect may include a third party server 274 that may communicate with the LMF 270, SLP 272, 5gc 260 (e.g., via AMF 264 and/or UPF 262), NG-RAN 220, and/or UE 204 to obtain location information (e.g., a location estimate) of the UE 204. As such, in some cases, the third party server 274 may be referred to as a location services (LCS) client or an external client. Third party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.

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, to one or more of the gnbs 222 and/or NG-enbs 224 in the NG-RAN 220, respectively. The interface between the gNB 222 and/or the ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, while the interface between the gNB 222 and/or the ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNB 222 and/or the NG-eNB 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNB 222 and/or the ng-eNB 224 may communicate with one or more UEs 204 over a wireless interface referred to as a "Uu" interface.

The functionality of the gNB 222 is divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. gNB-CU 226 is a logical node that includes base station functions, other than those specifically assigned to gNB-DU 228, that communicate user data, mobility control, radio access network sharing, positioning, session management, and so forth. More specifically, gNB-CU 226 generally hosts the Radio Resource Control (RRC), service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 222. The gNB-DU 228 is a logical node that generally hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the "F1" interface. The Physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229 that perform functions such as power amplification and signal transmission/reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

Fig. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including a location server 230 and an LMF 270, or alternatively may be independent of NG-RAN 220 and/or 5gc 210/260 infrastructure depicted in fig. 2A and 2B, such as a private network) to support file transfer operations as taught herein. It should be appreciated that these components may be implemented in different implementations in different types of devices (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Further, a given device may include one or more of these components. For example, an apparatus may comprise multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.

The UE 302 and the base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, respectively, that provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for blocking transmission, etc.) for communicating via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, etc. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (e.g., other UEs, access points, base stations (e.g., enbs, gnbs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., a set of time/frequency resources in a particular spectrum). The WWAN transceivers 310 and 350 may be variously configured to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.), respectively. Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

In at least some cases, UE 302 and base station 304 each also include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provided for communicating over a wireless communication medium of interest via at least one designated RAT (e.g., wiFi, LTE-D,PC5, dedicated Short Range Communication (DSRC), wireless Access for Vehicle Environment (WAVE), near Field Communication (NFC), etc.) with other network nodes such as other UEs, access points, base stations, etc. (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for blocking transmission, etc.). Short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) and conversely receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively, according to a specified RAT. Specifically, the short-range wireless transceivers 320 and 360 each include: for transmitting and encoding one or more of signals 328 and 368, respectivelyA plurality of transmitters 324 and 364, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, +. >Transceiver, < - > on>And/or +.>A transceiver, NFC transceiver, or vehicle-to-vehicle (V2V) and/or internet of vehicles (V2X) transceiver.

In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be coupled to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring satellite positioning/communication signals 338 and 378, respectively. In the case where satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning/communication signals 338 and 378 may be Global Positioning System (GPS) signals, global navigation satellite system (GLONASS) signals, galileo signals, beidou signals, indian regional navigation satellite system (NAVIC), quasi-zenith satellite system (QZSS), or the like. In the case of satellite signal receivers 330 and 370 being non-terrestrial network (NTN) receivers, 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 include any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request the appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.

The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, that provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 can 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.

The transceiver may be configured to communicate over a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), may include separate transmitter circuits and separate receiver circuits in some implementations, or may be implemented in other ways in other implementations. The transmitter circuitry and receiver circuitry of the wired transceivers (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 a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that allows the respective devices (e.g., UE 302, base station 304) to perform transmit "beamforming," as described herein. Similarly, 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 respective devices (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and the receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366) such that respective devices may only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a Network Listening Module (NLM) or the like for performing various measurements.

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 "transceivers," at least one transceiver, "or" one or more transceivers. In this way, it can be inferred from the type of communication performed whether a particular transceiver is a wired transceiver or a wireless transceiver. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) typically involves signaling via a wireless transceiver.

The UE 302, base station 304, and network entity 306 also include other components that may be used in connection with the operations disclosed herein. The UE 302, base station 304, and network entity 306 comprise one or more processors 332, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. Accordingly, processors 332, 384, and 394 may provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, and the like. In an aspect, 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 circuitry, or various combinations thereof.

The UE 302, base station 304, and network entity 306 comprise memory circuitry implementing memories 340, 386, and 396 (e.g., each comprising a memory device), respectively, for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Accordingly, memories 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, and the like. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. The positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that when executed cause the UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning 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 positioning components 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that 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 functionality described herein. Fig. 3A illustrates possible locations of a positioning component 342, which may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a stand-alone component. Fig. 3B illustrates possible locations for a positioning component 388, which may be part of, for example, 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 illustrates a possible location of a positioning 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.

The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and/or orientation information independent of motion 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. As an example, the sensor 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. Further, the sensor 344 may include a plurality of different types of devices and combine their outputs to provide movement information. For example, the sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in a two-dimensional (2D) and/or three-dimensional (3D) coordinate system.

In addition, the UE 302 includes a user interface 346 that provides means for providing an indication (e.g., an audible and/or visual indication) to a user and/or for receiving user input (e.g., upon actuation of a sensing device (such as a keypad, touch screen, microphone, etc.) by the user). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

Referring in more detail to the one or more processors 384, in 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 functionality associated with broadcast of 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 measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs by error correction of automatic repeat request (ARQ); MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, prioritization, and logical channel prioritization.

The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the Physical (PHY) layer, may include: error detection on a transmission channel, forward Error Correction (FEC) decoding/decoding of the transmission channel, interleaving, rate matching, mapping to physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter 354 processes the mapping to the signal constellation 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 decoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to Orthogonal Frequency Division Multiplexing (OFDM) subcarriers, 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 produce a physical channel carrying the time domain OFDM symbol stream. The OFDM symbol streams are spatially precoded to produce a plurality of spatial streams. Channel estimates from the channel estimator may be used to determine coding and modulation schemes and for spatial processing. The channel estimate may be derived from reference signals and/or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. Transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

At the UE 302, the receiver 312 receives signals through its corresponding antenna 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality 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 the destination of the multiple spatial streams is UE 302, they may be combined by 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 comprises 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 signal constellation points most likely to be transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332 that implement layer 3 (L3) and layer 2 (L2) functionality.

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

Similar to the functionality described in connection with the 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 and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with upper layer PDU delivery, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs and re-ordering 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), de-multiplexing of MAC SDUs from TBs, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), prioritization and logical channel prioritization.

Channel estimates derived by the channel estimator from reference signals or feedback transmitted by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

Uplink transmissions are processed at base station 304 in a manner similar to that described in connection with the receiver functionality at UE 302. The receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. 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.

For convenience, UE 302, base station 304, and/or network entity 306 are illustrated in fig. 3A, 3B, and 3C as including various components that may be configured according to various examples described herein. However, it should be understood that the illustrated components may have different functions in different designs. In particular, the various components in fig. 3A-3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choices, cost, use of equipment, or other considerations. For example, in the case of fig. 3A, a particular implementation of the UE 302 may omit the WWAN transceiver 310 (e.g., a wearable device or tablet computer or PC or laptop computer may have Wi-Fi and/or bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver 320 (e.g., cellular only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor 344, etc. In another example, in the case of fig. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hot spot" access point that does not have cellular capability), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, and so on. For brevity, illustrations of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

The various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to each other by data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or be part of the communication interfaces of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are contained in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), data buses 334, 382, and 392 may provide communications therebetween.

The components of fig. 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of fig. 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). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and/or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 through 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and/or by appropriate configuration of the processor components). Further, some or all of the functionality represented by blocks 390 through 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed by a UE, by a base station, by a network entity, etc. However, it should be understood that such operations, acts, and/or functions may in fact be performed by a particular component or combination of components (such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.) of UE 302, base station 304, network entity 306, and the like.

In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may operate differently than a network operator or cellular network infrastructure (e.g., NG RAN 220 and/or 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., over a non-cellular communication link such as WiFi).

NR supports several cellular network based positioning techniques including downlink based positioning methods, uplink based positioning methods, and downlink and uplink based positioning methods. The downlink-based positioning method comprises the following steps: observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink departure angle (DL-AoD) in NR. Fig. 4 illustrates examples of various positioning methods in accordance with aspects of the present disclosure. In an OTDOA or DL-TDOA positioning procedure, as shown in scenario 410, the UE measures differences between the times of arrival (toas) of reference signals (e.g., positioning Reference Signals (PRSs)) received from paired base stations, referred to as Reference Signal Time Difference (RSTD) or time difference of arrival (TDOA) measurements, and reports these differences to the positioning entity. More specifically, the UE receives Identifiers (IDs) of a reference base station (e.g., a serving base station) and a plurality of non-reference base stations in the assistance data. The UE then measures RSTD between the reference base station and each non-reference base station. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) may estimate the location of the UE.

For DL-AoD positioning, as shown in scenario 420, the positioning entity uses a beam report from the UE regarding received signal strength measurements for multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity may then estimate the location of the UE based on the determined angle and the known location of the transmitting base station.

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 uplink reference signals (e.g., sounding Reference Signals (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beam to determine the angle between the UE and the base station. Based on the determined angle and the known position of the base station, the positioning entity may then estimate the position of the UE.

The positioning method based on the downlink and the uplink comprises the following steps: enhanced cell ID (E-CID) positioning and multiple Round Trip Time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). During RTT, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or base station), which sends the second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures a time difference between an arrival time (ToA) of the received RTT-related signal and a transmission time of the transmitted RTT-related signal. This time difference is referred to as the received transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement may be made, or may be adjusted, to include only the time difference between the received signal and the nearest subframe boundary of the transmitted signal. The two entities may then communicate their Rx-Tx time difference measurements to a location server (e.g., LMF 270) that 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 transmit its Rx-Tx time difference measurement to another entity, which then calculates RTT. The distance between these two entities may be determined from RTT and a known signal speed (e.g., speed of light). For multi-RTT positioning, as shown in scenario 430, a first entity (e.g., a UE or base station) performs RTT positioning procedures with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable a location of the first entity to be determined (e.g., using multilateration) based on a distance to the second entity and a known location of the second entity. As shown in scenario 440, RTT and multi-RTT methods may be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve position accuracy.

The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In the E-CID, the UE reports a serving cell ID, a Timing Advance (TA), and identifiers of detected neighbor base stations, estimated timing, and signal strength. The location of the UE is then estimated based on the information and the known location of the base station.

NR also supports a variety of non-cellular positioning techniques, sometimes referred to as "RAT-independent" positioning, including network assisted GNSS methods, WLAN positioning, bluetooth positioning, terrestrial Beacon System (TBS) positioning such as urban beacon systems (MBS), sensor-based methods such as barometric pressure sensors, motion sensors, or Inertial Measurement Units (IMUs).

The network assisted GNSS method utilizes a UE equipped with a radio receiver capable of receiving GNSS signals. WLAN positioning methods utilize WLAN measurements (e.g., AP identifiers and other measurements) and databases to determine the location of the UE. Bluetooth positioning methods utilize bluetooth measurements (e.g., beacon identifiers and other measurements) to determine the location of a UE. TBSs consist of a network of ground-based transmitters that broadcast signals for positioning purposes only. The sensor method acquires location information of the UE using different sensors such as an atmospheric pressure sensor, an accelerometer, a gyroscope, a magnetometer, etc.

To assist in positioning operations, 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: an identifier of a base station (or cell/TRP of the base station) from which the reference signal is measured, a reference signal configuration parameter (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 suitable for a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE itself may be able to detect the neighboring network node without using assistance data.

In the case of an OTDOA or DL-TDOA positioning procedure, the assistance data may also include expected RSTD values and associated uncertainties, or a search window around the expected RSTD. In some cases, the expected range of values for RSTD may be +/-500 microseconds (μs). In some cases, the range of values of uncertainty of the expected RSTD may be +/-32 μs when any resources used for positioning measurements are in FR 1. In other cases, the range of values of uncertainty of the expected RSTD may be +/-8 μs when all resources used for positioning measurements are in FR 2.

In the case of a network assisted GNSS positioning procedure, the assistance data may include: data to assist in the measurements such as reference time, list of visible satellites, satellite signal doppler, code phase, doppler and code phase search windows; providing data for a position calculation method, such as reference time, reference position, satellite ephemeris, clock correction, code and carrier phase measurements from a GNSS reference receiver or receiver network; data that improves position accuracy, such as satellite code bias, satellite orbit correction, satellite clock correction, atmospheric model, real-time kinematic (RTK) or Precision Point Positioning (PPP) assistance data in an Observation Space Representation (OSR) or State Space Representation (SSR).

In the case of a WLAN positioning procedure, the assistance data may include the WLAN AP along with a list of AP identifiers and possible AP locations. In the case of a bluetooth positioning procedure, the assistance data may comprise a list of bluetooth beacons together with identifiers and possible beacon locations. In the case of a TBS positioning procedure, the assistance data may include a list of terrestrial beacons along with the beacon location. In the case of a sensor positioning process, the assistance data may include reference barometric pressure information.

The position estimate may be referred to by other names such as position estimate, location, position fix, and the like. The location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or may be municipal and include a street address, postal address, or some other verbally-located description of the location. The location estimate may be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). The position estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the position is expected to be contained with some specified or default confidence).

Fig. 5 illustrates an example Long Term Evolution (LTE) positioning protocol (LPP) procedure 500 between a UE 504 and a location server, shown as a Location Management Function (LMF) 570, for performing positioning operations. As shown in fig. 5, the positioning of the UE 504 is supported via the exchange of LPP messages between the UE 504 and the LMF 570. LPP messages may be exchanged between the UE 504 and the LMF 570 via a serving base station (shown as serving gNB 502) and a core network (not shown) of the UE 504. The LPP process 500 may be used to locate the UE 504 to support various location related services, such as for navigation of the UE 504 (or a user of the UE 504), or for route planning, or for providing an accurate location to a Public Safety Answering Point (PSAP) in association with an emergency call from the UE 504, or for some other reason. The LPP process 500 may also be referred to as a positioning session, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round Trip Time (RTT), enhanced cell identification (E-CID), etc.).

Initially, at stage 510, the UE 504 may receive a request for its positioning capabilities (e.g., an LPP request capability message) from the LMF 570. At stage 520, the UE 504 provides its positioning capabilities relative to the LPP protocol to the LMF 570 by transmitting an LPP provide capability message to the LMF 570 indicating that the UE 504 uses the LPP supported positioning methods and features of these positioning methods. In some aspects, the capabilities indicated in the LPP provisioning capability message may indicate the types of positioning supported by the UE 504 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the capabilities of the UE 504 to support those types of positioning.

Upon receiving the LPP provide capability message, at stage 520, the LMF 570 determines, based on the indicated location types supported by the UE 504, that a particular type of location method (e.g., DL-TDOA, RTT, E-CID, etc.) is to be used, and determines a set of one or more Transmit Reception Points (TRPs) from which the UE 504 is to measure downlink location reference signals or to which the UE 504 is to transmit uplink location reference signals. At stage 530, LMF 570 transmits an LPP provide assistance data message to UE 504 identifying the set of TRPs.

In some implementations, the LPP provide assistance data message at stage 530 may be transmitted by the LMF 570 to the UE 504 in response to an LPP request assistance data message (not shown in fig. 5) transmitted by the UE 504 to the LMF 570. The LPP request assistance data message may include an identifier of a serving TRP of the UE 504 and a request for a Positioning Reference Signal (PRS) configuration of neighboring TRPs.

At stage 540, the LMF 570 transmits a request for location information to the UE 504. The request may be an LPP request location information message. The message typically includes information elements defining the type of location information, the accuracy of the desired location estimate, and the response time (i.e., the desired delay). Note that low latency requirements allow longer response times, while high latency requirements require shorter response times. However, a long response time is referred to as a high delay and a short response time is referred to as a low delay.

Note that in some implementations, the LPP provide assistance data message transmitted at stage 530 may be transmitted after the LPP request for location information at stage 540, for example, if the UE 504 transmits a request for assistance data to the LMF 570 after receiving the request for location information at stage 540 (e.g., in the LPP request assistance data message, not shown in fig. 5).

At stage 550, the UE 504 performs positioning operations (e.g., measurements on DL-PRS, transmission on UL-PRS, etc.) for the selected positioning method using the assistance information received at stage 530 and any additional data received at stage 540 (e.g., desired position accuracy or maximum response time).

At stage 560, the UE 504 may transmit an LPP provided location information message to the LMF 570 conveying the results (e.g., time of arrival (ToA), reference Signal Time Difference (RSTD), received transmission (Rx-Tx), etc.) of any measurements obtained at stage 550 and before or upon expiration of any maximum response time (e.g., the maximum response time provided by the LMF 570 at stage 540). The LPP provided location information message at stage 560 may also include one or more times at which the location measurement was obtained and an identification of the TRP from which the location measurement was obtained. Note that the time between the request for location information at 540 and the response at 560 is the "response time" and indicates the delay of the positioning session.

The LMF 570 uses appropriate positioning techniques (e.g., DL-TDOA, RTT, E-CID, etc.) to calculate an estimated location of the UE 504 based at least in part on the measurements received in the LPP provide location information message at stage 560.

Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Fig. 6 is a diagram 600 illustrating an example frame structure in accordance with aspects of the present 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.

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

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

In the example of fig. 6, a parameter set of 15kHz is used. Thus, in the time domain, a 10ms frame is divided into 10 equally sized subframes, each of 1ms, and each subframe includes one slot. In fig. 6, time is represented horizontally (on the X-axis) where time increases from left to right, while frequency is represented vertically (on the Y-axis) where frequency increases (or decreases) from bottom to top.

A resource grid may be used to represent time slots, each of which includes one or more time-concurrent Resource Blocks (RBs) (also referred to as Physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of Resource Elements (REs). REs may correspond to one symbol length of a time domain and one subcarrier of a frequency domain. In the parameter set of fig. 6, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For the extended cyclic prefix, the RB may contain 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.

Some REs may carry a reference (pilot) signal (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), and so forth, depending on whether the illustrated frame structure is used for uplink or downlink communications. Fig. 6 shows example locations (labeled "R") of REs carrying reference signals.

PRS has been defined for NR positioning to enable UEs to detect and measure more neighboring TRPs. Several configurations are supported to enable various deployments (e.g., indoor, outdoor, below 6GHz, mmW). In addition, PRSs may be configured for both UE-based positioning procedures and UE-assisted positioning procedures. The following table shows various types of reference signals that can be used for various positioning methods supported in NR.

TABLE 1

The set of Resource Elements (REs) used for transmission of PRSs is referred to as "PRS resources. The set of resource elements may span multiple PRBs in the frequency domain and "N" (such as 1 or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, PRS resources occupy consecutive PRBs in the frequency domain.

The transmission of PRS resources within a given PRB has a particular comb size (also referred to as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency/tone spacing) within each symbol of the PRS resource allocation. Specifically, for a comb size "N", PRSs are transmitted in every nth subcarrier of a symbol of a PRB. For example, for comb-4, for each symbol of the PRS resource configuration, REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit PRS of PRS resources. Currently, the comb sizes for comb-2, comb-4, comb-6, and comb-12 are supported by DL-PRS. FIG. 6 illustrates an example PRS resource configuration for comb-4 (which spans 4 symbols). That is, the location of the shaded RE (labeled "R") indicates the PRS resource configuration of comb-4.

Currently, DL-PRS resources may span 2,4,6, or 12 consecutive symbols within a slot using a full frequency domain interleaving pattern. DL-PRS resources may be configured in any downlink or Flexible (FL) symbol of a slot that is configured by a higher layer. There may be a constant Energy Per Resource Element (EPRE) for all REs for a given DL-PRS resource. The symbol-by-symbol frequency offsets for comb sizes 2,4,6 and 12 over 2,4,6 and 12 symbols are as follows. 2 symbol comb teeth-2: {0,1};4 symbol comb teeth-2: {0,1,0,1};6 symbol comb teeth-2: {0,1,0,1,0,1};12 symbol comb teeth-2: {0,1,0,1,0,1,0,1,0,1,0,1};4 symbol comb teeth-4: {0,2,1,3} (as in the example of fig. 6); 12 symbol comb teeth-4: {0,2,1,3,0,2,1,3,0,2,1,3};6 symbol comb teeth-6: {0,3,1,4,2,5};12 symbol comb teeth-6: {0,3,1,4,2,5,0,3,1,4,2,5}; 12 symbol comb teeth-12: {0,6,3,9,1,7,4,10,2,8,5,11}.

A "PRS resource set" is a set of PRS resources used to communicate PRS signals, where each PRS resource has a PRS resource Identifier (ID). In addition, PRS resources in the PRS resource set are associated with the same TRP. The PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by the TRP ID). In addition, the PRS resources in the PRS resource set have the same periodicity, common muting pattern configuration, and the same repetition factor (such as "PRS-resourceredepositionfactor") across the slots. Periodicity is the time from a first repetition of a first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of a next PRS instance. The periodicity may have a length selected from: 2 x 4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240 slots, where μ=0, 1,2,3. The repetition factor may have a length selected from 1,2,4,6,8,16,32 slots.

The PRS resource IDs in the PRS resource set are associated with a single beam (or beam ID) transmitted from a single TRP (where one TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam and, as such, "PRS resources" (or simply "resources") may also be referred to as "beams. Note that this does not have any implications as to whether the UE knows the TRP and beam that sent the PRS.

A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (such as a group of one or more consecutive time slots) in which PRSs are expected to be transmitted. PRS occasions may also be referred to as "PRS positioning occasions", "PRS positioning instances", "positioning occasions", "positioning repetitions", or simply "occasions", "instances", or "repetitions".

A "positioning frequency layer" (also simply referred to as a "frequency layer") is a set of one or more PRS resource sets with the same value for certain parameters across one or more TRPs. In particular, the set of PRS resource sets have the same subcarrier spacing and Cyclic Prefix (CP) type (meaning that all parameter sets supported for Physical Downlink Shared Channel (PDSCH) are also supported for PRS), the same point a, the same value of downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point a parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" stands for "absolute radio frequency channel number") and is an identifier/code that specifies a pair of physical radio channels to be used for transmission and reception. The downlink PRS bandwidth may have a granularity of 4 PRBs with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to 4 frequency layers have been defined, and up to 2 PRS resource sets per TRP are configurable per frequency layer.

The concept of the frequency layer is somewhat similar to that of component carriers and bandwidth parts (BWP), but differs in that component carriers and BWP are used by one base station (or macrocell base station and small cell base station) to transmit data channels, while the frequency layer is used by several (often three or more) base stations to transmit PRS. The UE may indicate the number of frequency layers that the UE can support when the UE transmits its positioning capabilities to the network, such as during an LTE Positioning Protocol (LPP) session. For example, the UE may indicate whether the UE can support one or four positioning frequency layers.

Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to: PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS as defined in LTE and NR, and the like. In addition, the terms "positioning reference signal" and "PRS" may refer to a downlink or uplink positioning reference signal unless otherwise indicated by the context. If further differentiation of the type of PRS is required, the downlink positioning reference signal may be referred to as "DL-PRS" and the uplink positioning reference signal (e.g., SRS for positioning, PTRS) may be referred to as "UL-PRS". In addition, for signals (e.g., DMRS, PTRS) that may be transmitted in both uplink and downlink, these signals may be preceded by "UL" or "DL" to distinguish directions. For example, "UL-DMRS" may be distinguished from "DL-DMRS".

On-demand PRS refers to the ability to allow a UE or LMF to request a change in DL-PRS or available DL-PRS for positioning measurements, such as a change in resources assigned for DL-PRS transmission (e.g., changed bandwidth, changed positioning occasion duration and/or changed positioning occasion frequency, etc.), and possibly indicate when (changed) DL-PRS transmission is no longer needed.

For example, the signaling may allow for an increase in resources assigned for DL-PRS transmission (e.g., increased bandwidth, specific TRP, or beam direction) and possibly indicate when DL-PRS transmission is no longer needed. The increased DL-PRS transmissions may be simplified by being limited to certain DL-PRS configurations that may only be configured in the gNB and/or LMF. For example, in the absence of any request for an increased DL-PRS transmission, there may be a set of DL-PRS configuration parameters corresponding to a "normal" DL-PRS transmission. In some networks, a "normal" DL-PRS transmission may be equivalent to no DL-PRS transmission at all (to minimize resource usage). There may then be one or more levels of increased DL-PRS transmissions, each level associated with a different set of DL-PRS configuration parameters. In the simplest case, DL-PRS transmissions may be turned on only when needed and turned off when not needed according to a default set of DL-PRS configuration parameters.

The UE-initiated on-demand PRS request may be enabled by an enhanced LPP request assistance data message. The UE may transmit an LPP request assistance data message including parameters for a desired PRS configuration (e.g., a desired bandwidth, periodicity of PRS, etc.). The on-demand PRS request in the LPP request assistance data message may also include a start time and a duration (or a stop time) as to when and how long the UE needs the requested PRS configuration.

The network may also indicate one or more possible predefined PRS configurations to the UE. Each predefined PRS configuration has an associated set of PRS parameters (e.g., defining bandwidth, duration, power, periodicity, frequency range, muting, etc.) and is identifiable by a unique PRS configuration identifier/index. The predefined PRS configuration may be provided to the UE in advance in an LPP provide assistance data message or via broadcast, e.g., a positioning SIB (posSIB). The LPP request assistance data message may then include a PRS configuration identifier/index of the desired on-demand PRS configuration (or a list of desired PRS configuration identifiers/indices sorted according to priority).

When the LMF receives the LPP request assistance data message for the on-demand PRS, it is desirable for the LMF to configure the requested PRS configuration on multiple TRP/gnbs around the UE location and to provide the configured PRS information to the UE in the LPP provide assistance data message. The LPP provisioning assistance data message may also include an indication of how long the PRS configuration will be available. The UE may then use PRSs to perform position measurements.

Fig. 7A and 7B illustrate an example of a location server initiated PRS positioning procedure 700 in accordance with aspects of the present disclosure. At stage 1 (consisting of stages 1a and 1 b), LMF 270 may provide one or more positioning SIBs (possibs) containing a set of possible on-demand DL-PRS configurations to the gNB in NG-RAN 220 in an NR positioning protocol type a (NRPPa) assistance information control message for broadcasting in positioning system information. The set of possible on-demand DL-PRS configurations may contain a primary DL-PRS configuration (e.g., a default DL-PRS configuration) and one or more secondary DL-PRS configurations, wherein the secondary DL-PRS configurations define possible changes in DL-PRS as compared to the primary DL-PRS configuration (e.g., different bandwidths, duration of positioning occasions, and/or frequency of positioning occasions, etc.). Each possible on-demand DL-PRS configuration is associated with a unique identifier. Alternatively or in addition, the posSIB may also indicate which specific DL-PRS parameters may be requested to be changed as needed.

At stage 2a, the UE 204 transmits a terminal-initiated location request (MO-LR) request message including a request for on-demand DL-PRS transmission included in a UL NAS send message to the serving AMF 264. The MO-LR request carries an LPP request assistance data message defining parameters for the preferred DL-PRS configuration, which also includes a start time for when the requested DL-PRS configuration is needed at the UE 204 and/or a duration (e.g., seconds, minutes, or hours) of how long the requested DL-PRS configuration is needed. The request may also include an LPP provisioning capability message (including DL-PRS capabilities of UE 204) and an LPP provisioning location information message (e.g., providing E-CID measurements).

Alternatively, at stage 2b, the 5GC LCS entity 280 (e.g., gateway Mobile Location Center (GMLC)) requests some location service (e.g., location) for the target UE 204 from the serving AMF 264.

Alternatively, at stage 2c, the serving AMF 264 of the target UE 204 determines the need for some positioning service (e.g., positioning the UE 204 for an emergency call).

At stage 3, AMF 264 invokes a "Nlmf_location_DetermineLocation" service operation to the LMF. If stage 2a is performed, the service operation includes an MO-LR request from stage 2 a. If stage 2b or 2c is performed, the service operation includes a request for the current location of the UE 204, LCS client type, and may include the required QoS.

At stage 4, the LMF 270 may perform one or more LPP procedures to, for example, obtain DL-PRS positioning capabilities of the UE.

At stage 5, the LMF 270 determines a new DL-PRS configuration for one or more gnbs in the NG-RAN 220 based on the request received at stage 3. The determination at stage 5 may also be based on other UEs received by LMF 270 from and/or location requests for other UEs in proximity to target UE 204 at approximately the same time.

At stage 6, the LMF 270 initiates NRPPa DL-PRS reconfiguration procedures with each of the gnbs involved in the NG-RAN 220 determined at stage 5. If some of the gNBs indicate that a new DL-PRS configuration cannot be supported, then LMF 270 may perform stage 11 to recover old DL-PRS configurations in each gNB that indicates that a new DL-PRS configuration can be supported to avoid interference between gNBs that support a new DL-PRS configuration and gNBs that do not support a new DL-PRS configuration. In this case, at stage 8, the LMF 270 may provide the old DL-PRS configuration to the UE 204 instead of the new DL-PRS configuration.

At stage 7, each gNB in NG-RAN 220 that acknowledges support of the new DL-PRS configuration at stage 6 changes from the old DL-PRS configuration to the new DL-PRS configuration after (or just before) the acknowledgement is transmitted at stage 6 if no start time is provided, or at the start time indicated in stage 6. In some cases, the old DL-PRS configuration may correspond to not transmitting DL-PRS.

At stage 8, the LMF 270 transmits an LPP provisioning assistance data message to the target UE 204 to provide the new DL-PRS configuration determined at stage 5 and acknowledged at stage 6. The message may also include a start time and/or duration configured for each new DL-PRS. If stage 2b or 2c is performed, the LMF 270 may initiate LPP and possibly NRPPa procedures to obtain the location of the target UE 204.

At stage 9, LMF 270 returns a "nlmf_location_determinelocation" response to AMF 264. If stage 2a is performed, the message indicates whether the DL-PRS assistance data has been successfully delivered. If stage 2b or 2c is performed, the message includes the location of the target UE 204.

At stage 10, if stage 2a is performed, AMF 264 forwards the response from stage 9 to target UE 204. If stage 2b is performed, the AMF 264 forwards the response to the 5GC LCS entity 280.

At stage 11, if the duration of the new DL-PRS is not included at stage 6, the LMF 270 may initiate an NRPPa DL-PRS reconfiguration procedure with each of the gnbs determined at stage 5 to recover the old DL-PRS configuration of each of the gnbs.

At stage 12, each of the gnbs begins to transmit the old DL-PRS configuration when the duration received in stage 6 expires or after stage 11 receives and acknowledges a request to resume the old DL-PRS configuration. In some cases, the old DL-PRS configuration may correspond to not transmitting DL-PRS.

In some cases, the LMF may receive on-demand PRS requests for a certain (potentially large) number of UEs, and each UE may potentially request a different PRS configuration. However, the LMF may have reached the limit (overload) of on-demand PRS requests (or, in general, assistance data requests) that it can handle, or the possible PRS transmissions on at least some gnbs may have reached the limit resulting in additional requested PRS transmissions no longer being possible or allowed (e.g., by the operator). Thus, the LMF may not be able to perform the on-demand PRS request and will provide an error message to the UE indicating that the UE request is not possible.

However, this may result in the UE transmitting a repeated on-demand PRS request, as the UE may still need PRS to perform position measurements, which then will further increase the load of the LMF and other network elements, as the LMF will have to transmit repeated error messages to the UE until it can eventually grant the request. Alternatively, the UE may assume that the LMF is permanently unable to provide the requested on-demand PRS and may not repeat the request, however, this would mean that not only the current positioning attempt (which requires PRS) may fail, but also a possible future positioning attempt may fail, since the UE may not repeat the request for PRS in the future when a position measurement using PRS is needed.

The above problem is not specific to LPP request assistance data messages for PRS on demand, but applies to any assistance data request from a UE, where the LMF is only temporarily unable to grant the request, but may in principle be able to grant the request at a future time.

The present disclosure provides techniques for controlling repeated on-demand PRS requests. As described above, the support of on-demand PRSs by LMF may vary over time (e.g., may not be available when the network is under heavy load, but is available at other times). Thus, the UE may be allowed to request PRS on demand at a later time. The LMF may provide a time interval in any failure response after which the UE is allowed to request again. The UE may then repeat the on-demand PRS request at or after this future time. This avoids the UE transmitting repeated on-demand PRS requests to the LMF (until the request is ultimately granted) and avoids assuming that the LMF is permanently unable to grant the request at the UE.

The techniques described further below are flexible and controlled by the LMF, which will not affect other network entities (i.e., may be supported by only UE and LMF upgrades). It allows the LMF to provide a dedicated "retry time" specific to each UE (e.g., each UE transmitting an on-demand request that cannot currently be granted by the LMF may receive a separate "retry time"), which also allows the LMF to schedule potential future attempts so that many UEs do not occur at about the same time. The technique is also applicable to other types of assistance data requests.

FIG. 8A illustrates an example of an on-demand PRS positioning process 800 in accordance with aspects of the present disclosure. At stage 1a, the gNB 222 may broadcast multiple PRS configurations that may be requested on demand in one or more possibs. At stage 1b, the LMF 270 may provide the target UE 204 (or other target device) with multiple PRS configurations in an LPP provide assistance data message, e.g., as part of a location session. Each PRS configuration in phases 1a and 1b has an associated identifier.

At stage 2, the target UE 204 determines that PRS transmissions or changes in PRS transmissions (e.g., changed PRS bandwidth, duration of change in PRS occasion, or PRS transmissions from a more recent gNB, etc.) are required to meet the location requirement and transmits an LPP request assistance data message to the LMF 270 to request a change in PRS transmissions. The message may include a PRS configuration identifier for the requested PRS configuration from the set of possible PRS configurations provided at stage 1. Alternatively or in addition, the message may include an indication of which PRS parameters to request to change (which may include a change in PRS bandwidth, a change in PRS positioning occasion, a change in PRS beam, etc.). The message may also include a duration of how long the (modified) PRS configuration is required at the target UE 204 (e.g., number of seconds, minutes, or hours for which PRS configuration is required).

At stage 3, the LMF 270 is currently unable to fulfill the request and includes an error indication along with a "retry time" in the LPP provide assistance data message transmitted to the target UE 204. The "retry time" indicates a future time that allows the UE 204 to transmit a next LPP request assistance data message for the PRS on demand. The "retry time" may be provided as an absolute time (e.g., coordinated Universal Time (UTC) time) or as a number of seconds, minutes, or hours from when the LPP provide assistance data message is received at the UE 204.

At stage 4, after the "retry time" occurs (e.g., UTC time occurs, or the number of seconds, minutes, or hours have elapsed), the UE 204 transmits another LPP request assistance data message to the LMF 270 to request a change in PRS transmission. This may be a repetition of the request at phase 2, or may include different on-demand PRS requests (e.g., different configuration identifiers as in phase 2, or different durations of how long the (modified) PRS configuration is required, etc.).

At stage 5, the LMF 270 is now able to carry out the request from stage 4 and determine a new PRS configuration for the one or more gnbs 222 based on the request received at stage 4. The LMF 270 provides the determined PRS configuration information to the gNB 222 that begins broadcasting the new PRS requested by the LMF 270.

At stage 6, the LMF 270 transmits an LPP provisioning assistance data message to the target UE 204 that includes the new PRS configuration determined at stage 5. The message may also include a start time and/or duration configured for each new PRS. The target UE 204 then performs the desired location measurements using PRS transmissions from the gNB 222, and may calculate the location of the target UE 204 based on these measurements.

Fig. 8B illustrates an example of a positioning process 850 in accordance with aspects of the present disclosure. Unlike the on-demand PRS positioning procedure 800, the positioning procedure 850 is not specific to on-demand PRSs.

At stage 1, the target UE 204 determines that certain positioning assistance data is desired and transmits an LPP request assistance data message to the LMF 270. The positioning assistance data may be any assistance data supporting a positioning method (e.g. assisted GNSS (a-GNSS), OTDOA, DL-TDOA, DL-AoD, multi-cell RTT, E-CID, real Time Kinematic (RTK), state Space Representation (SSR), WLAN, bluetooth or sensor).

At stage 2, the LMF 270 is currently unable to fulfill the request and includes an error indication along with a "retry time" in the LPP provide assistance data message transmitted to the target UE 204. The "retry time" indicates a future time at which the UE 204 is allowed to transmit the next LPP request assistance data message. The "retry time" may be provided as an absolute time (e.g., coordinated Universal Time (UTC) time) or as a number of seconds, minutes, or hours from when the LPP provide assistance data message is received at the UE 204.

At stage 3, after the "retry time" occurs (e.g., UTC time occurs, or the number of seconds, minutes, or hours have elapsed), the UE 204 transmits another LPP request assistance data message to the LMF 270 to request assistance data for the positioning method. This may be a repetition of the request at stage 1 or may include different requests (e.g., for different positioning methods).

At stage 4, the LMF 270 transmits an LPP provide assistance data message including the requested assistance data to the target UE 204. The target UE 204 then uses the assistance data to perform the desired positioning method.

Referring back to on-demand PRS, in some cases, the LPP request assistance data message (e.g., at stage 2 and stage 4 of fig. 8A) may include a request for on-demand PRS for one or more positioning methods (e.g., DL-TDOA, DL-AoD, or multi-RTT) requiring PRS. The UE may determine different desired PRS configurations for different positioning methods. For example, the UE may request on-demand PRS configuration only specifically for the need to perform DL AoD measurements from the serving gNB, and another on-demand PRS configuration specifically for DL-TDOA measurements from several gnbs around the UE location. The LMF may then provide error indications and "retry times" for each positioning method, as shown in fig. 9 below.

Similarly, in some cases, the LPP request assistance data message (e.g., at stage 1 and stage 3 of fig. 8B) may include a request for positioning assistance data for one or more positioning methods (e.g., DL-TDOA, DL-AoD, multi RTT, GNSS, WLAN, bluetooth, sensors, etc.). The LMF may then provide an error indication and a "retry time" for each positioning method.

Different "retry times" may also be determined by the LMF according to different PRS parameters of a single positioning method. For example, the LPP request assistance data at stage 2 of fig. 8A may request PRS configuration for two or more positioning frequency layers (e.g., one PRS in FR1 and one PRS in FR 2). The LMF may then provide different "retry times" for the requested PRSs in FR1 and FR 2.

FIG. 9 illustrates an example of an on-demand PRS positioning process 900 for a plurality of positioning methods in accordance with aspects of the present disclosure. Stage 1 of fig. 9 is the same as stage 1 of fig. 8A. At stage 2, the target UE 204 determines that PRS transmissions or changes in PRS transmissions (e.g., changed PRS bandwidth, duration of change in PRS occasion, or PRS transmissions from a more recent gNB, etc.) are required to meet the location requirement and transmits an LPP request assistance data message to the LMF 270 to request a change in PRS transmissions. In this case, the UE 204 determines that a different on-demand PRS configuration is required for different positioning methods. Thus, the message includes a PRS configuration identifier from the requested PRS configuration of the set of possible PRS configurations provided at stage 1 for different positioning methods (e.g., DL-TDOA, DL-AoD, multi-RTT). The message may also include a duration of how long the (modified) PRS configuration is required at the target UE 204 (e.g., number of seconds, minutes, or hours for which PRS configuration is required).

At stage 3, the LMF 270 is currently unable to fulfill the request and includes an error indication along with a "retry time" in the LPP provide assistance data message transmitted to the target UE 204. The message includes a "retry time" for each requested PRS configuration/positioning method.

At stage 4a, after the "retry time" for the DL-TDOA location method occurs, the UE 204 transmits another LPP request assistance data message to the LMF 270 to request a change in PRS transmissions for the DL-TDOA location method. This may be a repetition of the request for DL-TDOA location method at stage 2, or may include different on-demand PRS requests (e.g., different configuration identifiers as in stage 2, or different durations of how long the (modified) PRS configuration is required, etc.).

At stage 4b, after the "retry time" for the DL-AoD positioning method occurs, the UE 204 transmits another LPP request assistance data message to the LMF 270 to request a change in PRS transmission for the DL-AoD positioning method. This may be a repetition of the request for DL-AoD positioning method at phase 2, or may include different on-demand PRS requests (e.g. different configuration identifiers as in phase 2, or different durations of how long the (modified) PRS configuration is required, etc.).

At stage 4c, after a "retry time" for the multi-RTT positioning method occurs, the UE 204 transmits another LPP request assistance data message to the LMF 270 to request a change in PRS transmissions for the multi-RTT positioning method. This may be a repetition of the request for the multi-RTT positioning method at phase 2, or may include a different on-demand PRS request. Note that in the example of fig. 9, the three "retry times" are different. However, this is not necessarily the case, but rather they may be identical.

Stage 5 and stage 6 of fig. 8A will now be performed. For brevity, they will not be described again here.

There are different variants of the above technique, including the following variants. As a first variant (referred to as "variant a"), at stage 1a of fig. 8A/9, a "retry time" is provided in advance in the broadcast message. In this case, the LPP provisioning assistance data at stage 3 of FIG. 8A/9 would include only an error indication. The "retry time" from stage 1a of fig. 8A/9 is used by the UE to determine when to perform the retry at stage 4 of fig. 8A/9. However, in this case, all UEs receiving the broadcast message in the cell will use the same value for the "retry time". That is, the LMF cannot provide a dedicated "retry time" for each UE.

As a second variant (referred to as "variant B"), at stage 1B of fig. 8A/9, a "retry time" is provided in advance in the LPP provisioning assistance data message, along with a possible PRS configuration on demand. Similar to variant a above, the LPP provisioning assistance data at phase 3 of fig. 8A/9 will only include an error indication. The "retry time" from stage 1b of fig. 8A/9 is used by the UE to determine when to perform the retry at stage 4 of fig. 8A/9. In contrast to variant a, the "retry time" can now be dedicated to each UE, since the LPP provided assistance data message is a UE-specific message. Thus, different UEs in the network may receive different "retry times", e.g., to allocate retries from several UEs over time.

Both variants a and B will require a pre-configuration of the "retry time". However, when an on-demand PRS request actually occurs at stage 2 of FIG. 8A/9, the actual load of the LMF may be different and may allow for a shorter or possibly longer "retry time" than preconfigured at stage 1 of FIG. 8A/9. Therefore, providing a "retry time" in the failure message at stage 3 of fig. 8A/9 would be the most flexible solution.

As a third variant (referred to as "variant C"), the LMF provides the UE with two timer values at stage 3 of fig. 8A/9 or stage 2 of fig. 8B: first timer T ₁ Indicating when the UE may repeat the current request; and a second timer T ₂ Which indicates when the UE may transmit further assistance data requests (e.g., PRS on-demand requests as in fig. 8A and 9). The LMF will then store the UE assistance data request from phase 2 of fig. 8A/9 or phase 1 of fig. 8B. At T ₁ Thereafter, the UE may perform stage 4 of fig. 8A/9 or stage 3 of fig. 8B without including any specific information (or other assistance data) regarding the requested PRS. The LMF then uses the stored information for the UE to determine the specific assistance data requested. This variant has the following advantages: the messages at stage 4 of fig. 8A/9 and stage 3 of fig. 8B can now be very small messages, with essentially no information content, because the assistance data request details now refer to the previous or original assistance data request from stage 2 of fig. 8A/9 or stage 1 of fig. 8B stored at the LMF. LMF will be at T ₁ The originally stored auxiliary data request is then erased.

If the UE needs assistance data different from the original data requested in phase 2 of FIG. 8A/9 or phase 1 of FIG. 8B, the UE will be at the provided time T ₂ Stage 4 of fig. 8A/9 or stage 3 of fig. 8B is then performed. This variant allows for very short repeated assistance data request messages, which may be advantageous in case of transmitting phase 4 of fig. 8A/9 or phase 3 of fig. 8B using lower layer signaling (e.g. layer 1 or layer 2 signaling). However, assistance data requests for (potentially many) UEs will need to be stored at the LMF.

As a fourth variant (referred to as "variant D"), the UE performs stage 2 of fig. 8A/9 or fig. 8BIncluding a start time as to when assistance data is requested (e.g., PRS on demand in the case of fig. 8A and 9) and a duration or stop time of how long assistance data is requested. Then, at phase 3 of fig. 8A/9 or phase 2 of fig. 8B, the LMF provides the UE with two timer values: first time T ₁ Which is greater than the requested start time but less than the stop time, indicating a time at which the LMF is expected to be able to carry out the assistance data request; and a second time T ₂ Which indicates the earliest time at which the UE is allowed to transmit the next assistance data request.

Then, when time T ₁ When this occurs, the LMF may perform phase 6 of fig. 8A or phase 4 of fig. 8B, and the UE will not perform phase 4 of fig. 8A/9 or phase 3 of fig. 8B, but will wait for phase 6 of fig. 8A or phase 4 of fig. 8B to occur. If at T ₁ After which either stage 6 of fig. 8A or stage 4 of fig. 8B does not occur, the UE may be at T ₂ Stage 4 of fig. 8A/9 or stage 3 of fig. 8B is then performed. As an alternative variant (referred to as "variant D1"), the LMF does not store information about individual UE requests at stage 2 of fig. 8A/9 or stage 1 of fig. 8B, and thus does not perform stage 6 of fig. 8A or stage 4 of fig. 8B. Instead, the LMF accumulates information applicable to requests from one or more UEs and, when capable of reconfiguration, reconfigures PRSs for the UEs (in the case of fig. 8A and 9). In this case, time T ₁ Indicating to each UE when reconfiguration may occur. The UE discovers the reconfiguration by monitoring PRS configuration information (or other assistance information for non-on-demand PRS methods) conveyed in the posSIB broadcast message (e.g., as at stage 1 of fig. 8A/9). Thus, the UE may be at time T ₁ The posSIB monitoring starts after occurrence and will only be at time T if no reconfiguration is observed ₂ The on-demand PRS request (or other assistance data request) is then repeated.

In contrast to variant C, this variant (in particular variant D1) would not require storage of auxiliary data requests (e.g., on-demand requests) at the LMF, and phase 4 of fig. 8A/9 or phase 3 of fig. 8B could be avoided altogether, but would require that the LMF be able to carry out the request for the duration requested at phase 2 of fig. 8A/9 or phase 1 of fig. 8B.

On the UE side, there are various conditions that can trigger the UE to request PRS on demand. For example, the trigger criteria may include a threshold for measurement quality, a confidence level, a change in radio conditions, and so forth. In some cases, qoS in the LPP request location information message may trigger the UE to transmit a request for on-demand PRS. However, more specific trigger criteria should be defined.

As a first technique described herein, a boolean flag may be added to the NRPPa assistance information control message of phase 1a or the new location request at phase 2 of fig. 7A. The boolean flag may control: for a particular session or period of time, whether the UE is allowed to request on-demand configuration for a given positioning session (value "true") or not (value "false"). This would allow the LMF and/or the gNB to prevent the UE from attacking the network with on-demand configuration requests per session.

As a second technique, a bitmap (e.g., 8 bits) may be used to negotiate which PRS configuration parameters may be used between the UE and the LMF for on-demand requests. For example, the first bit of the bitmap may indicate whether the UE is allowed to request a change in PRS bandwidth, the second bit may indicate a change in comb/symbol options, the third bit may indicate a change in PRS period, the fourth bit may indicate a change in the number of repetitions, the fifth bit may indicate a reduction in the number of TRPs, and the sixth bit may indicate a reduction in the number of positioning frequency layers. The remaining bits (e.g., two bits for an eight bit bitmap) may be reserved for other purposes. At stage 520 of fig. 5, the UE may transmit its bitmap request in an LPP provide capability message. At stage 530 of fig. 5, the LMF may include a similar bitmap in the LPP provide assistance data message to indicate to the UE which PRS configuration parameters may be requested to be changed. This will ensure that the UE will not request to change parameters that are not supported by the LMF and/or the gNB.

As a third technique, a maximum number of requests that a UE can make for a given on-demand PRS configuration may be defined. The LMF may configure the value to the UE in the LPP provide assistance data message. UEs with different capabilities may be given different retry values. More specifically, UEs may be classified into low-level UEs (e.g., wearable devices such as smartwatches, glasses, bracelets, rings, etc.) and high-level UEs (e.g., smartphones, tablets, laptops, etc.). The low-level UEs may alternatively be referred to as capability-limited NR UEs, capability-limited UEs ("RedCap" UEs), NR light UEs, NR ultra-light UEs, or ultra-light UEs. Advanced UEs may alternatively be referred to as full capability UEs or simply UEs. The low-level UEs typically have lower baseband processing capability, fewer antennas (e.g., one receiver antenna as a baseline in FR1 or FR2, optionally with two receiver antennas), lower operating bandwidth capability (e.g., 20MHz for FR1 without supplemental uplink or carrier aggregation, or 50MHz or 100MHz for FR 2), half-duplex frequency division duplex (HD-FDD) only capability, smaller HARQ buffers, reduced Physical Downlink Control Channel (PDCCH) monitoring, limited modulation (e.g., 64QAM for the downlink and 16QAM for the uplink), relaxed processing timeline requirements, and/or lower uplink transmit power, as compared to the high-level UEs. Different UE levels may be distinguished by UE category and/or UE capability. For example, certain types of UEs may be assigned a "low-level" category (e.g., original Equipment Manufacturer (OEM), applicable wireless communication standard, etc.), while other types of UEs may be assigned a "high-level" category. Certain classes of UEs may also report their type (e.g., "low-level" or "high-level") to the network. In addition, certain resources and/or channels may be dedicated to certain types of UEs. For example, with respect to the number of requests for a given PRS configuration, a "advanced" UE may be given a higher retry value than a RedCap UE.

As a fourth technique, a maximum time may be defined for which the UE should wait for the first on-demand PRS to send or wait for a response to an on-demand request. If the UE does not receive a response to the request or does not detect any on-demand PRS transmissions (e.g., from the requested TRP, on the requested positioning frequency layer, at the requested time, etc.), the UE has two options. As a first option, the UE may assume that the on-demand request has failed and go to a different positioning method (e.g., a non-NR positioning method). As a second option, the UE may transmit a message to the LMF to notify it of the error. The UE may perform one or both of these options.

As an alternative technique, the indicated time may be the maximum time that the UE should allow the NR positioning method to require PRS configuration on demand before switching to another positioning method. In an aspect, the UE may inform the LMF of how long the UE will wait for the LMF to transmit a response to the request or on-demand configuration. The techniques may be applied to Uu positioning (i.e., a UE receiving PRSs from one or more TRPs) or side chain positioning (i.e., a UE receiving PRSs from one or more UEs). For side-link positioning, one UE will transmit an on-demand request, while the other UE will respond with a configuration.

The present disclosure also provides techniques for locating status updates to indicate a need for a particular assistance data configuration (i.e., a particular PRS configuration). There may be multiple PRS configurations supported by the LMF in a given geographic region, but only a few configuration(s) will be activated at a given time. In this technique, an active configuration index for active PRS configuration may be broadcast from the gNB/LMF using a new posSIB. Note that this is simply an active configuration index, not a full PRS configuration, which may have previously been signaled to UEs in the region via other posSIB or unicast signaling. The new posSIB will provide information about all PRS configurations activated at the current time. The new posSIB may also provide the length of time that the PRS configuration will be activated.

By decoding the posSIB, the UE will be able to determine whether one or more of the activated PRS configurations are useful for positioning. If at least one of the activated configurations is useful, the UE may normally start a positioning session. If none of the activated configurations is available, the UE will not initiate a positioning session. This will save a lot of signaling between the UE and the network that would otherwise be consumed negotiating the PRS configuration on demand.

In case the UE does not start the positioning session, the UE should indicate to the network the reason (i.e. the reason that it cannot start the positioning session) in the positioning state update message. For example, the UE may indicate that the required assistance data (i.e., the required PRS configuration) is not activated and may also indicate what the required assistance data is. The UE should continue to monitor the posSIB for any changes in the activated PRS configuration.

Fig. 10 illustrates an example method 1000 for suspending a positioning session due to incorrect or insufficient assistance data in accordance with current practice. Stages 1a and 1b are identical to stages 510 and 520 of fig. 5, and stage 2b is identical to stage 530 of fig. 5. At stage 2a, the UE 204 transmits an LPP request assistance data message to the LMF 270. The request may include a particular PRS configuration that the UE needs for the positioning session. At stage 2b, the LMF 270 transmits an LPP provide assistance data message to the UE 204. The response may include a PRS configuration that is different from the requested configuration and that the UE 204 cannot use for the positioning session (e.g., due to the UE's capabilities). Thus, at stage 3, the UE 204 transmits an LPP suspension positioning message to the LMF 270 indicating that the assistance data is incorrect.

Fig. 11 illustrates an example method 1100 for reporting requirements for a new PRS configuration in accordance with aspects of the present disclosure. In the example of fig. 11, there are five PRS configurations (indexes "1", "2", "3", "4", and "5") available for LMF 270. These different PRS configurations may be used for different sets of one or more TRPs, different sets of one or more positioning frequency layers, different frequency bands, different sets of BWP, etc. In the example of fig. 11, configurations 1 and 3 are currently activated. The identifiers of the available PRS configurations and the currently activated configurations may be broadcast by the serving gNB of the UE 204 in one or more possibs, as described above.

At stage 1, the UE 204 initiates a first positioning session and determines that it needs configuration 3 and that configuration 3 is activated based on the broadcasted posSIB. At stages 2 a-4 b, the UE 204 and LMF 270 perform an LPP positioning session, as described above with reference to fig. 5. At stage 5, the UE 204 initiates a second positioning session. The second positioning session may be the same or a different type of positioning session than the first positioning session. For this positioning session, the UE 204 needs a different PRS configuration, specifically configuration 4. This may be because the UE 204 needs to measure more, fewer, or different TRPs, more, fewer, or different frequency layers, etc. However, in the example of fig. 11, configuration 4 is currently inactive. Thus, at stage 6, the UE 204 transmits a location status update message to the LMF 270 indicating that the UE 204 needs to configure 4 for the second location session. In response, LMF 270 may or may not activate configuration 4, and thus, UE 204 may wait for a response from LMF 270 or an indication that configuration 4 has been activated (e.g., via a posSIB) for a period of time before suspending the second positioning session.

The present disclosure provides other techniques for indicating PRS configuration capabilities. As described above, the gNB and/or LMF may support multiple PRS configurations in a given geographic region. In an aspect, a UE may request a particular on-demand PRS configuration. The network may accept the request and activate the new configuration, or the network may reject the request and provide a timer or future time to the UE. The UE cannot request this particular PRS configuration until the timer expires or the indicated future time.

In an aspect, the UE may provide (e.g., in an LPP provide capability message) a capability indicating how many PRS configurations the UE may store simultaneously. The UE may maintain a configuration timer for each configuration or apply a timer for all configurations. The LMF may simultaneously provide a configured number at the beginning of the positioning session.

The present disclosure provides other techniques for on-demand rules based on UE category. The following table indicates DL-PRS pre-configuration associated with QoS and radio conditions.

TABLE 2

As described above, the LMF may support multiple PRS configurations. Some of which may be used for positioning sessions requiring high positioning accuracy, some of which may be used for positioning sessions requiring low latency, and some of which may be used for positioning sessions requiring low power use. The PRS configuration that a UE may request may be based on the class and capabilities of the UE. For example, advanced UEs may be permitted to request a configuration of high accuracy, low latency, and low power compared to the currently active PRS configuration. A normal UE may only be permitted to request a low latency and low power configuration compared to the currently active configuration. An industrial IoT (IIoT) or lower layer UE may only be permitted to request PRS configurations that are low power compared to the currently active configuration. These rules may be defined in the applicable wireless standards or may be set by the LMF based on the UE capabilities and then provided in the assistance data (e.g., at stage 530 of fig. 5).

Fig. 12 illustrates an example wireless location method 1200 in accordance with aspects of the disclosure. In an aspect, the method 1200 may be performed by a UE (e.g., any UE described herein).

At 1210, the UE sends a first request assistance data message to a location server (e.g., LMF 270) including a request for first positioning assistance, as for example at stage 2 of fig. 8A or stage 1 of fig. 8B. In an aspect, operation 1210 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and/or positioning component 342, any or all of which may be considered means for performing the operation.

At 1220, the UE receives a provide assistance data message from the location server indicating that the location server is currently unable to provide the first positioning assistance, as for example at stage 3 of fig. 8A or stage 2 of fig. 8B. In an aspect, operation 1220 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and/or positioning component 342, any or all of which may be considered means for performing the operation.

At 1230, the UE sends a second request assistance data message to the location server after expiration of the retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance was not received by the UE prior to the retry time, as for example at stage 4 of fig. 8A or stage 3 of fig. 8B. In an aspect, operation 1230 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and/or positioning component 342, any or all of which may be considered means for performing the operation.

It should be appreciated that a technical advantage of method 1200 is to prevent multiple requests for assistance data that cannot be serviced by a network.

Fig. 13 illustrates an example positioning method 1300 of communication in accordance with aspects of the disclosure. In an aspect, the method 1300 may be performed by a location server (e.g., LMF 270).

At 1310, the location server receives a first request assistance data message from a UE (e.g., any of the UEs described herein) that includes a request for first positioning assistance, as for example at stage 2 of fig. 8A or stage 1 of fig. 8B. In an aspect, operation 1310 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and/or positioning components 398, any or all of which may be considered means for performing the operation.

At 1320, the location server sends a provide assistance data message to the UE indicating that the location server is currently unable to provide the first positioning assistance, as for example at stage 3 of fig. 8A or stage 2 of fig. 8B. In an aspect, operation 1320 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and/or positioning components 398, any or all of which may be considered means for performing the operation.

At 1330, the location server receives a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE prior to the retry time, as for example at stage 4 of fig. 8A or stage 3 of fig. 8B. In an aspect, operation 1330 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and/or positioning component 398, any or all of which may be considered a means for performing the operation.

It should be appreciated that a technical advantage of method 1300 is to prevent multiple requests for assistance data that cannot be serviced by a network.

In the detailed description above, it can be seen that the different features are grouped together in various examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, aspects of the present disclosure may include less than all of the features of the disclosed individual example clauses. Accordingly, the following clauses are hereby considered to be included in the specification, wherein each clause may be individually as separate examples. Although each subordinate clause may refer to a particular combination with one of the other clauses in the clauses, aspects of the subordinate clause are not limited to the particular combination. It should be understood that other example clauses may also include combinations of subordinate clause aspects with the subject matter of any other subordinate clause or independent clause, or combinations of any feature with other subordinate and independent clauses. Various aspects disclosed herein expressly include such combinations unless specifically expressed or inferred that no particular combination (e.g., contradictory aspects, such as defining elements as insulators and conductors) is contemplated. Furthermore, it is also contemplated that aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

Specific examples of implementations are described in the following numbered clauses:

clause 1. A wireless positioning method performed by a User Equipment (UE), comprising: transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

Clause 2. The method of clause 1, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

Clause 3 the method of clause 2, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 4. The method of any of clauses 1-3, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 5 the method of clause 4, further comprising: transmitting one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and transmitting one or more parameters for the second on-demand PRS configuration in a second request assistance data message.

Clause 6 the method of any of clauses 4 to 5, further comprising: a plurality of on-demand PRS configurations capable of being activated to support positioning of a UE are received, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 7 the method of clause 6, further comprising: receiving the plurality of on-demand PRS configurations from a location server in one or more provide assistance data messages; or the plurality of on-demand PRS configurations are received from the base station by broadcast in one or more positioning system information blocks (possibs).

Clause 8 the method of any of clauses 4 to 7, wherein: the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

Clause 9 the method of any of clauses 4 to 8, further comprising: a second provisioning assistance data message is received from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

The method of any one of clauses 4 to 9, wherein: the first on-demand PRS configuration is for a first type of positioning method between the UE and a location server, the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

Clause 11. The method of any of clauses 4 to 10, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and the method further includes: determining that the first on-demand PRS configuration has been activated prior to or at a fulfillment time; and based on determining that the first on-demand PRS configuration has been activated, refraining from sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 12 the method of clause 11, further comprising: the first on-demand PRS configuration is determined to have been activated based on monitoring system information from the base station.

Clause 13 the method of any of clauses 1 to 12, further comprising: receiving a retry time in the provide assistance data message; receiving a retry time from the base station in the system information; or a retry time received in a previously provided assistance data message received prior to the transmission of the first request assistance data message.

The method of any one of clauses 1 to 13, wherein the retry time is: absolute time, seconds, minutes or hours.

Clause 15 the method of any of clauses 1 to 14, further comprising: a second time is received from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide a second positioning assistance to the UE.

Clause 16 the method of clause 15, further comprising: receive a second positioning assistance from the one or more gnbs via broadcast before a second time; or receiving a second positioning assistance in a second provide assistance message before a second time.

The method of any one of clauses 15 to 16, wherein the second time occurs before the retry time, the method further comprising: verifying that the first positioning aid was not received before the second time; and based on not receiving the first positioning assistance before the second time, sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 18 the method of any of clauses 1 to 17, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

Clause 19. A positioning method performed by a location server, comprising: receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

Clause 20 the method of clause 19, wherein: each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 21 the method of any of clauses 19 to 20, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 22 the method of clause 21, further comprising: receiving one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and receiving one or more parameters for a second on-demand PRS configuration in a second request assistance data message.

Clause 23 the method of any of clauses 21 to 22, further comprising: a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are transmitted to the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

The method of any one of clauses 21 to 23, further comprising: a second provide assistance data message is sent to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

The method of any one of clauses 21 to 24, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and the provision assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

The method of any one of clauses 19 to 25, further comprising: transmitting a retry time in the provide assistance data message; or a retry time in a previously provided assistance data message sent prior to the first request assistance data message.

The method of any one of clauses 19 to 26, further comprising: a second time is sent to the UE in the provide assistance data message, the second time indicating a time at which the location server expects to provide second positioning assistance to the UE.

Clause 28 the method of clause 27, further comprising: a second positioning assistance is sent in a second provide assistance message before a second time.

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: transmitting, via the at least one transceiver, a first request assistance data message to a location server, the first request assistance data message comprising a request for first positioning assistance; receiving, via the at least one transceiver, a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and transmitting, via the at least one transceiver, a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

Clause 30 the UE of clause 29, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

Clause 31 the UE of clause 30, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 32 the UE of any of clauses 29-31, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 33 the UE of clause 32, wherein the at least one processor is further configured to: transmitting, via the at least one transceiver, one or more parameters for the first on-demand PRS configuration in a first request assistance data message; and transmitting, via the at least one transceiver, one or more parameters for a second on-demand PRS configuration in a second request assistance data message.

Clause 34 the UE of any of clauses 32 to 33, wherein the at least one processor is further configured to: a plurality of on-demand PRS configurations capable of being activated to support positioning of a UE are received via the at least one transceiver, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 35 the UE of clause 34, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a plurality of on-demand PRS configurations from a location server in one or more provide assistance data messages; or receive the plurality of on-demand PRS configurations from the base station via the at least one transceiver in one or more positioning system information blocks (possibs) by broadcasting.

The UE of any of clauses 32 to 35, wherein: the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

Clause 37 the UE of any of clauses 32 to 36, wherein the at least one processor is further configured to: a second provisioning assistance data message is received from the location server via the at least one transceiver, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

The UE of any of clauses 32-37, wherein: the first on-demand PRS configuration is for a first type of positioning method between the UE and a location server, the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

Clause 39 the UE of any of clauses 32 to 38, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and the at least one processor is further configured to: determining that the first on-demand PRS configuration has been activated prior to or at a fulfillment time; and based on determining that the first on-demand PRS configuration has been activated, refraining from sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 40 the UE of clause 39, wherein the at least one processor is further configured to: the first on-demand PRS configuration is determined to have been activated based on monitoring system information from the base station.

Clause 41 the UE of any of clauses 29-40, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a retry time in providing the assistance data message; receiving a retry time from the base station in the system information via the at least one transceiver; or receiving, via the at least one transceiver, a retry time in a previously provided assistance data message received prior to the transmission of the first request assistance data message.

Clause 42 the UE of any of clauses 29 to 41, wherein the retry time is: absolute time, seconds, minutes or hours.

The UE of any of clauses 29-42, wherein the at least one processor is further configured to: a second time is received from the location server in providing the assistance data message via the at least one transceiver, the second time indicating a time at which the location server expects to provide a second positioning assistance to the UE.

Clause 44 the UE of clause 43, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a second positioning assistance from the one or more gnbs via broadcast prior to a second time; or receiving, via the at least one transceiver, a second positioning assistance in a second provide assistance message before a second time.

Clause 45 the UE of any of clauses 43 to 44, wherein the second time occurs before the retry time, the at least one processor being further configured to: verifying that the first positioning aid was not received before the second time; and based on not receiving the first positioning assistance before the second time, transmitting, via the at least one transceiver, a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 46 the UE of any of clauses 29 to 45, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

Clause 47, a location server 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: receiving, via the at least one transceiver, a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting, via the at least one transceiver, a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving, via the at least one transceiver, a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

Clause 48 the location server of clause 47, wherein: each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 49 the location server of any of clauses 47 to 48, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 50 the location server of clause 49, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and receiving, via the at least one transceiver, one or more parameters for a second on-demand PRS configuration in a second request assistance data message.

Clause 51 the location server of any of clauses 49 to 50, wherein the at least one processor is further configured to: a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are transmitted to the UE via the at least one transceiver, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

The location server of any of clauses 49-51, wherein the at least one processor is further configured to: a second provide assistance data message is sent to the UE via the at least one transceiver, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

Clause 53 the location server of any of clauses 49 to 52, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and the provision assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

Clause 54 the location server of any of clauses 47 to 53, wherein the at least one processor is further configured to: transmitting, via the at least one transceiver, a retry time in providing the assistance data message; or transmitting, via the at least one transceiver, a retry time in a previously provided assistance data message transmitted prior to the transmission of the first request assistance data message.

Clause 55, the location server of any of clauses 47 to 54, wherein the at least one processor is further configured to: a second time is sent to the UE in providing the assistance data message via the at least one transceiver, the second time indicating a time at which the location server expects to provide a second positioning assistance to the UE.

Clause 56 the location server of clause 55, wherein the at least one processor is further configured to: a second positioning assistance is transmitted in a second provide assistance message before a second time via the at least one transceiver.

Clause 57, a User Equipment (UE), comprising: means for sending a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; means for receiving a provide assistance data message from a location server, the provide assistance data message indicating that the location server is currently unable to provide first positioning assistance; and means for sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

Clause 58 the UE of clause 57, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

Clause 59 the UE of clause 58, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 60 the UE of any of clauses 57-59, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 61 the UE of clause 60, further comprising: means for transmitting one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and means for sending one or more parameters for the second on-demand PRS configuration in a second request assistance data message.

Clause 62 the UE of any of clauses 60-61, further comprising: means for receiving a plurality of on-demand PRS configurations that can be activated to support positioning of a UE, wherein a first on-demand PRS configuration and a second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 63 the UE of clause 62, further comprising: means for receiving the plurality of on-demand PRS configurations from a location server in one or more provide assistance data messages; or means for receiving the plurality of on-demand PRS configurations from a base station by broadcast in one or more positioning system information blocks (possibs).

Clause 64 the UE of any of clauses 60 to 63, wherein: the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

Clause 65 the UE of any of clauses 60 to 64, further comprising: means for receiving a second provisioning assistance data message from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

The UE of any of clauses 60-65, wherein: the first on-demand PRS configuration is for a first type of positioning method between the UE and a location server, the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

Clause 67 the UE of any of clauses 60 to 66, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and the UE further includes: means for determining that the first on-demand PRS configuration has been activated prior to or at a fulfillment time; and means for: based on determining that the first on-demand PRS configuration has been activated, sending a second request assistance data message to the location server is prevented after expiration of a retry time since receipt of the provide assistance data message.

Clause 68 the UE of clause 67, further comprising: means for determining that the first on-demand PRS configuration has been activated based on monitoring system information from the base station.

Clause 69 the UE of any of clauses 57-68, further comprising: means for receiving a retry time in the provide assistance data message; means for receiving a retry time from a base station in system information; or means for receiving a retry time in a previously provided assistance data message received prior to the transmission of the first request assistance data message.

Clause 70 the UE of any of clauses 57 to 69, wherein the retry time is: absolute time, seconds, minutes or hours.

Clause 71 the UE of any of clauses 57-70, further comprising: means for receiving a second time from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide second positioning assistance to the UE.

Clause 72 the UE of clause 71, further comprising: means for receiving a second positioning assistance from the one or more gnbs via broadcast prior to a second time; or means for receiving a second positioning assistance in a second assistance message before a second time.

Clause 73 the UE of any of clauses 71-72, wherein the second time occurs before the retry time, the UE further comprising: means for verifying that the first positioning aid was not received before the second time; and means for: the second request assistance data message is sent to the location server after expiration of a retry time since receipt of the provide assistance data message based on the first positioning assistance not being received before the second time.

Clause 74 the UE of any of clauses 57 to 73, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

Clause 75. A location server comprising: means for receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; means for sending a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and means for receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

Clause 76 the location server of clause 75, wherein: each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 77 the location server of any of clauses 75 to 76, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 78 the location server of clause 77, further comprising: means for receiving one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and means for receiving one or more parameters for a second on-demand PRS configuration in a second request assistance data message.

Clause 79 the location server of any of clauses 77-78, further comprising: means for transmitting to the UE a plurality of on-demand PRS configurations that can be activated to support positioning of the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 80 the location server of any of clauses 77 to 79, further comprising: the apparatus includes means for sending a second provide assistance data message to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

Clause 81 the location server of any of clauses 77 to 80, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and the provision assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

Clause 82 the location server of any of clauses 75 to 81, further comprising: means for transmitting a retry time in the provide assistance data message; or means for transmitting a retry time in a previously provided assistance data message transmitted prior to the transmission of the first request assistance data message.

Clause 83 the location server of any of clauses 75 to 82, further comprising: means for transmitting a second time to the UE in the provide assistance data message, the second time indicating a time at which the location server expects to provide second positioning assistance to the UE.

Clause 84 the location server of clause 83, further comprising: means for sending a second positioning assistance in a second assistance message before a second time.

Clause 85, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to: transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance; receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

Clause 86. The non-transitory computer-readable medium of clause 85, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

Clause 87 the non-transitory computer-readable medium of clause 86, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 88 the non-transitory computer-readable medium of any of clauses 85 to 87, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 89 the non-transitory computer-readable medium of clause 88, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmitting one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and transmitting one or more parameters for the second on-demand PRS configuration in a second request assistance data message.

Clause 90. The non-transitory computer readable medium of any of clauses 88 to 89, further comprising computer executable instructions that, when executed by the UE, cause the UE to: a plurality of on-demand PRS configurations capable of being activated to support positioning of a UE are received, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 91 the non-transitory computer-readable medium of clause 90, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receiving the plurality of on-demand PRS configurations from a location server in one or more provide assistance data messages; or the plurality of on-demand PRS configurations are received from the base station by broadcast in one or more positioning system information blocks (possibs).

Clause 92 the non-transitory computer readable medium of any of clauses 88 to 91, wherein: the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

Clause 93 the non-transitory computer-readable medium of any of clauses 88 to 92, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: a second provisioning assistance data message is received from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

Clause 94 the non-transitory computer readable medium of any of clauses 88 to 93, wherein: the first on-demand PRS configuration is for a first type of positioning method between the UE and a location server, the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

Clause 95 the non-transitory computer readable medium of any of clauses 88 to 94, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and the non-transitory computer-readable medium further includes computer-executable instructions that, when executed by the UE, cause the UE to: determining that the first on-demand PRS configuration has been activated prior to or at a fulfillment time; and based on determining that the first on-demand PRS configuration has been activated, refraining from sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 96 the non-transitory computer-readable medium of clause 95, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: the first on-demand PRS configuration is determined to have been activated based on monitoring system information from the base station.

Clause 97 the non-transitory computer readable medium of any of clauses 85 to 96, further comprising computer executable instructions that, when executed by the UE, cause the UE to: receiving a retry time in the provide assistance data message; receiving a retry time from the base station in the system information; or a retry time received in a previously provided assistance data message received prior to the transmission of the first request assistance data message.

The non-transitory computer readable medium of any one of clauses 85 to 97, wherein the retry time is: absolute time, seconds, minutes or hours.

The non-transitory computer-readable medium of any one of clauses 85 to 98, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: a second time is received from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide a second positioning assistance to the UE.

Clause 100. The non-transitory computer-readable medium of clause 99, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: receive a second positioning assistance from the one or more gnbs via broadcast before a second time; or receiving a second positioning assistance in a second provide assistance message before a second time.

Clause 101 the non-transitory computer readable medium of any of clauses 99 to 100, wherein the second time occurs before the retry time, the non-transitory computer readable medium further comprising computer executable instructions that, when executed by the UE, cause the UE to: verifying that the first positioning aid was not received before the second time; and based on not receiving the first positioning assistance before the second time, sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message.

Clause 102 the non-transitory computer readable medium of any of clauses 85 to 101, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

Clause 103, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance; transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

Clause 104 the non-transitory computer readable medium of clause 103, wherein: each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

Clause 105 the non-transitory computer-readable medium of any of clauses 103-104, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

Clause 106 the non-transitory computer-readable medium of clause 105, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: receiving one or more parameters for a first on-demand PRS configuration in a first request assistance data message; and receiving one or more parameters for a second on-demand PRS configuration in a second request assistance data message.

Clause 107 the non-transitory computer readable medium of any of clauses 105 to 106, further comprising computer executable instructions that, when executed by the location server, cause the location server to: a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are transmitted to the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

Clause 108 the non-transitory computer readable medium of any of clauses 105 to 107, further comprising computer executable instructions that, when executed by the location server, cause the location server to: a second provide assistance data message is sent to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

Clause 109 the non-transitory computer readable medium of any one of clauses 105 to 108, wherein: the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and the provision assistance data message further includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

Clause 110 the non-transitory computer readable medium of any of clauses 103 to 109, further comprising computer executable instructions that, when executed by the location server, cause the location server to: transmitting a retry time in the provide assistance data message; or a retry time in a previously provided assistance data message sent prior to the first request assistance data message.

Clause 111 the non-transitory computer readable medium of any of clauses 103 to 110, further comprising computer executable instructions that, when executed by the location server, cause the location server to: a second time is sent to the UE in the provide assistance data message, the second time indicating a time at which the location server expects to provide second positioning assistance to the UE.

Clause 112 the non-transitory computer-readable medium of clause 111, further comprising computer-executable instructions that, when executed by the location server, cause the location server to: a second positioning assistance is sent in a second provide assistance message before a second time.

Those of skill in the art would understand that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Furthermore, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative 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 upon the particular application and design constraints imposed on the overall system. Skilled artisans 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.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with 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 in the alternative, 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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. A software module may reside in Random Access Memory (RAM), flash memory, read-only memory (ROM), erasable Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, 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). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more example 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 over as one or more instructions or code on a computer-readable medium. 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. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can 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 a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes: compact Discs (CDs), laser discs, optical discs, digital Versatile Discs (DVDs), floppy disks, and blu-ray discs where disks usually reproduce data magnetically, while discs reproduce data with lasers. Combinations of the above should also be included within the scope of computer-readable media.

While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. Furthermore, the functions, steps, and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not 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.

Claims (112)

1. A wireless location method performed by a User Equipment (UE), comprising:

transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance;

receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

2. The method as recited in claim 1, wherein each of said first positioning assistance and said second positioning assistance comprises assistance data for one or more positioning methods.

3. The method of claim 2, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

4. The method of claim 1, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

5. The method of claim 4, further comprising:

transmitting one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are sent in the second request assistance data message.

6. The method of claim 4, further comprising:

a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are received, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

7. The method of claim 6, further comprising:

receiving the plurality of on-demand PRS configurations from the location server in one or more provide assistance data messages; or alternatively

The plurality of on-demand PRS configurations are received from a base station by broadcast in one or more positioning system information blocks (possibs).

8. The method according to claim 4, wherein:

the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

9. The method of claim 4, further comprising:

a second provisioning assistance data message is received from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

10. The method according to claim 4, wherein:

the first on-demand PRS configuration is for a first type of positioning method between the UE and the location server,

The first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and

the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

11. The method according to claim 4, wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration time and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and

the method further comprises the steps of:

determining that the first on-demand PRS configuration has been activated prior to or at the fulfillment time; and

based on determining that the first on-demand PRS configuration has been activated, after expiration of the retry time from receipt of the provide assistance data message, the second request assistance data message is prevented from being sent to the location server.

12. The method of claim 11, further comprising:

the first on-demand PRS configuration is determined to have been activated based on monitoring system information from a base station.

13. The method of claim 1, further comprising:

receiving the retry time in the provide assistance data message;

receiving the retry time from the base station in system information; or alternatively

The retry time is received in a previously provided assistance data message received prior to sending the first request assistance data message.

14. The method of claim 1, wherein the retry time is:

the absolute time of the time period of the time,

the number of seconds of which is known per se,

number of minutes, or

Hours.

15. The method of claim 1, further comprising:

a second time is received from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

16. The method of claim 15, further comprising:

receive the second positioning assistance from one or more gnbs via broadcast prior to the second time; or alternatively

The second positioning assistance is received in a second provide assistance message before the second time.

17. The method of claim 15, wherein the second time occurs before the retry time, the method further comprising:

Verifying that the first positioning aid was not received before the second time; and

based on the first positioning assistance not being received before the second time, sending the second request assistance data message to the location server after expiration of the retry time since receipt of the provide assistance data message.

18. The method of claim 1, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

19. A positioning method performed by a location server, comprising:

receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance;

transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

a second request assistance data message is received from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

20. The method according to claim 19, wherein:

each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and

the one or more positioning methods include: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

21. The method of claim 19, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

22. The method of claim 21, further comprising:

receiving one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are received in the second request assistance data message.

23. The method of claim 21, further comprising:

A plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are sent to the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

24. The method of claim 21, further comprising:

and sending a second provide assistance data message to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

25. The method according to claim 21, wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message also includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

26. The method of claim 19, further comprising:

transmitting the retry time in the provide assistance data message; or alternatively

The retry time is sent in a previously provided assistance data message sent prior to sending the first request assistance data message.

27. The method of claim 19, further comprising:

and sending a second time to the UE in the provide assistance data message, the second time indicating a time when the location server expects to provide the second positioning assistance to the UE.

28. The method of claim 27, further comprising:

the second positioning assistance is sent in a second provide assistance message before the second time.

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:

transmitting, via the at least one transceiver, a first request assistance data message to a location server, the first request assistance data message comprising a request for first positioning assistance;

receiving, via the at least one transceiver, a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

sending, via the at least one transceiver, a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance was not received by the UE prior to the retry time.

30. The UE of claim 29, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

31. The UE of claim 30, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

32. The UE of claim 29, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

33. The UE of claim 32, wherein the at least one processor is further configured to:

transmitting, via the at least one transceiver, one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are sent in the second request assistance data message via the at least one transceiver.

34. The UE of claim 32, wherein the at least one processor is further configured to:

a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are received via the at least one transceiver, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

35. The UE of claim 34, wherein the at least one processor is further configured to:

receiving, via the at least one transceiver, the plurality of on-demand PRS configurations from the location server in one or more provide assistance data messages; or alternatively

The plurality of on-demand PRS configurations are received from a base station via the at least one transceiver in one or more positioning system information blocks (possibs) by broadcasting.

36. The UE of claim 32, wherein:

the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

37. The UE of claim 32, wherein the at least one processor is further configured to:

a second provisioning assistance data message is received from the location server via the at least one transceiver, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

38. The UE of claim 32, wherein:

the first on-demand PRS configuration is for a first type of positioning method between the UE and the location server,

the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and

the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

39. The UE of claim 32, wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration time and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and

the at least one processor is further configured to:

determining that the first on-demand PRS configuration has been activated prior to or at the fulfillment time; and

based on determining that the first on-demand PRS configuration has been activated, after expiration of the retry time from receipt of the provide assistance data message, the second request assistance data message is prevented from being sent to the location server.

40. The UE of claim 39 wherein said at least one processor is further configured to:

the first on-demand PRS configuration is determined to have been activated based on monitoring system information from a base station.

41. The UE of claim 29, wherein the at least one processor is further configured to:

receiving, via the at least one transceiver, the retry time in the provide assistance data message;

receiving the retry time from a base station in system information via the at least one transceiver; or alternatively

The retry time is received, via the at least one transceiver, in a previously provided assistance data message received prior to sending the first request assistance data message.

42. The UE of claim 29, wherein the retry time is:

the absolute time of the time period of the time,

the number of seconds of which is known per se,

number of minutes, or

Hours.

43. The UE of claim 29, wherein the at least one processor is further configured to:

a second time is received from the location server in the provide assistance data message via the at least one transceiver, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

44. The UE of claim 43, wherein the at least one processor is further configured to:

receiving, via the at least one transceiver, the second positioning assistance from one or more gnbs via broadcast prior to the second time; or alternatively

The second positioning assistance is received in a second provide assistance message before the second time via the at least one transceiver.

45. The UE of claim 43, wherein the second time occurs before the retry time, the at least one processor is further configured to:

verifying that the first positioning aid was not received before the second time; and

based on the first positioning assistance not being received before the second time, sending, via the at least one transceiver, the second request assistance data message to the location server after expiration of the retry time since receipt of the provide assistance data message.

46. The UE of claim 29, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

47. A location server, 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:

receiving, via the at least one transceiver, a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance;

transmitting, via the at least one transceiver, a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

receiving, via the at least one transceiver, a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance,

wherein the first positioning assistance is not sent to the UE before the retry time.

48. The location server of claim 47 wherein:

each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and

The one or more positioning methods include: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

49. The location server of claim 47, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

50. The location server of claim 49, wherein the at least one processor is further configured to:

receiving, via the at least one transceiver, one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are received in the second request assistance data message via the at least one transceiver.

51. The location server of claim 49, wherein the at least one processor is further configured to:

A plurality of on-demand PRS configurations that can be activated to support positioning of the UE are sent to the UE via the at least one transceiver, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

52. The location server of claim 49, wherein the at least one processor is further configured to:

a second provide assistance data message is sent to the UE via the at least one transceiver, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

53. The location server of claim 49 wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message also includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

54. The location server of claim 47, wherein the at least one processor is further configured to:

Transmitting the retry time in the provide assistance data message via the at least one transceiver; or alternatively

The retry time is transmitted, via the at least one transceiver, in a previously provided assistance data message transmitted prior to the transmission of the first request assistance data message.

55. The location server of claim 47, wherein the at least one processor is further configured to:

a second time is sent to the UE in the provide assistance data message via the at least one transceiver, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

56. The location server of claim 55, wherein the at least one processor is further configured to:

the second positioning assistance is sent in a second provide assistance message before the second time via the at least one transceiver.

57. A User Equipment (UE), comprising:

means for sending a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance;

means for receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

Means for sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

58. The UE of claim 57, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

59. The UE of claim 58, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

60. The UE of claim 57, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

61. The UE of claim 60, further comprising:

means for sending one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

means for sending one or more parameters for the second on-demand PRS configuration in the second request assistance data message.

62. The UE of claim 60, further comprising:

means for receiving a plurality of on-demand PRS configurations that can be activated to support positioning of the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

63. The UE of claim 62, further comprising:

means for receiving the plurality of on-demand PRS configurations from the location server in one or more provide assistance data messages; or (b)

Means for receiving the plurality of on-demand PRS configurations from a base station by broadcasting in one or more positioning system information blocks (possibs).

64. The UE of claim 60, wherein:

the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

65. The UE of claim 60, further comprising:

means for receiving a second provisioning assistance data message from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

66. The UE of claim 60, wherein:

the first on-demand PRS configuration is for a first type of positioning method between the UE and the location server,

the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and

the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

67. The UE of claim 60, wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration time and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and

the UE further includes:

means for determining that the first on-demand PRS configuration has been activated prior to or at the fulfillment time; and

A component for: based on determining that the first on-demand PRS configuration has been activated, after expiration of the retry time from receipt of the provide assistance data message, the second request assistance data message is prevented from being sent to the location server.

68. The UE of claim 67, further comprising:

means for determining that the first on-demand PRS configuration has been activated based on monitoring system information from a base station.

69. The UE of claim 57, further comprising:

means for receiving the retry time in the provide assistance data message;

means for receiving the retry time from a base station in system information; or (b)

Means for receiving the retry time in a previously provided assistance data message received prior to sending the first request assistance data message.

70. The UE of claim 57, wherein the retry time is:

the absolute time of the time period of the time,

the number of seconds of which is known per se,

number of minutes, or

Hours.

71. The UE of claim 57, further comprising:

means for receiving a second time from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

72. The UE of claim 71, further comprising:

means for receiving the second positioning assistance from one or more gnbs via broadcast prior to the second time; or (b)

Means for receiving the second positioning assistance in a second provide assistance message before the second time.

73. The UE of claim 71, wherein the second time occurs before the retry time, the UE further comprising:

means for verifying that the first positioning aid was not received before the second time; and

a component for: based on the first positioning assistance not being received before the second time, sending the second request assistance data message to the location server after expiration of the retry time since receipt of the provide assistance data message.

74. The UE of claim 57, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

75. A location server, comprising:

means for receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance;

Means for sending a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

means for receiving a second request assistance data message from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

76. The location server of claim 75, wherein:

each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and

the one or more positioning methods include: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

77. The location server of claim 75, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

78. The location server of claim 77, further comprising:

means for receiving one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

means for receiving one or more parameters for the second on-demand PRS configuration in the second request assistance data message.

79. The location server of claim 77, further comprising:

means for sending to the UE a plurality of on-demand PRS configurations that can be activated to support positioning of the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

80. The location server of claim 77, further comprising:

means for sending a second provide assistance data message to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

81. The location server of claim 77, wherein:

the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and

the providing assistance data message also includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

82. The location server of claim 75, further comprising:

means for transmitting the retry time in the provide assistance data message; or (b)

Means for transmitting the retry time in a previously provided assistance data message transmitted prior to transmitting the first request assistance data message.

83. The location server of claim 75, further comprising:

means for sending a second time to the UE in the provide assistance data message, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

84. The location server of claim 83, further comprising:

means for sending the second positioning assistance in a second provide assistance message before the second time.

85. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a User Equipment (UE), cause the UE to:

transmitting a first request assistance data message to a location server, the first request assistance data message comprising a request for first location assistance;

receiving a provide assistance data message from the location server, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

Sending a second request assistance data message to the location server after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for second positioning assistance, wherein the first positioning assistance is not received by the UE before the retry time.

86. The non-transitory computer-readable medium of claim 85, wherein each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods.

87. The non-transitory computer-readable medium of claim 86, wherein the one or more positioning methods comprise: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

88. The non-transitory computer-readable medium of claim 85, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

89. The non-transitory computer-readable medium of claim 88, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

transmitting one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are sent in the second request assistance data message.

90. The non-transitory computer-readable medium of claim 88, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are received, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

91. The non-transitory computer-readable medium of claim 90, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

receiving the plurality of on-demand PRS configurations from the location server in one or more provide assistance data messages; or alternatively

The plurality of on-demand PRS configurations are received from a base station by broadcast in one or more positioning system information blocks (possibs).

92. The non-transitory computer readable medium of claim 88, wherein:

the second on-demand PRS configuration is the same as the first on-demand PRS configuration or the second on-demand PRS configuration is different from the first on-demand PRS configuration.

93. The non-transitory computer-readable medium of claim 88, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

a second provisioning assistance data message is received from the location server, the second provisioning assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

94. The non-transitory computer readable medium of claim 88, wherein:

the first on-demand PRS configuration is for a first type of positioning method between the UE and the location server,

the first request assistance data message further includes a third identifier of a third on-demand PRS configuration, and

the third on-demand PRS configuration is for a second type of positioning method between the UE and the location server.

95. The non-transitory computer readable medium of claim 88, wherein:

the first request assistance data message also includes a start time and a duration for the first on-demand PRS configuration,

the providing assistance data message further includes a fulfillment time that is greater than the start time and less than the duration time and indicates when the location server expects to be able to activate the first on-demand PRS configuration, and

the non-transitory computer-readable medium further includes computer-executable instructions that, when executed by the UE, cause the UE to:

determining that the first on-demand PRS configuration has been activated prior to or at the fulfillment time; and

based on determining that the first on-demand PRS configuration has been activated, after expiration of the retry time from receipt of the provide assistance data message, the second request assistance data message is prevented from being sent to the location server.

96. The non-transitory computer-readable medium of claim 95, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

The first on-demand PRS configuration is determined to have been activated based on monitoring system information from a base station.

97. The non-transitory computer-readable medium of claim 85, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

receiving the retry time in the provide assistance data message;

receiving the retry time from the base station in system information; or alternatively

The retry time is received in a previously provided assistance data message received prior to sending the first request assistance data message.

98. The non-transitory computer-readable medium of claim 85, wherein the retry time is:

the absolute time of the time period of the time,

the number of seconds of which is known per se,

number of minutes, or

Hours.

99. The non-transitory computer-readable medium of claim 85, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

a second time is received from the location server in the provide assistance data message, the second time indicating a time at which the location server expects to provide the second positioning assistance to the UE.

100. The non-transitory computer-readable medium of claim 99, further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

receive the second positioning assistance from one or more gnbs via broadcast prior to the second time; or alternatively

The second positioning assistance is received in a second provide assistance message before the second time.

101. The non-transitory computer-readable medium of claim 99, wherein the second time occurs before the retry time, the non-transitory computer-readable medium further comprising computer-executable instructions that, when executed by the UE, cause the UE to:

verifying that the first positioning aid was not received before the second time; and

based on the first positioning assistance not being received before the second time, sending the second request assistance data message to the location server after expiration of the retry time since receipt of the provide assistance data message.

102. The non-transitory computer-readable medium of claim 85, wherein the second request assistance data message indicates that the second request assistance data message is a repetition of the first request assistance data message.

103. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to:

receiving a first request assistance data message from a User Equipment (UE), the first request assistance data message comprising a request for first positioning assistance;

transmitting a provide assistance data message to the UE, the provide assistance data message indicating that the location server is currently unable to provide the first positioning assistance; and

a second request assistance data message is received from the UE after expiration of a retry time since receipt of the provide assistance data message, the second request assistance data message indicating a request for a second positioning assistance, wherein the first positioning assistance is not sent to the UE before the retry time.

104. The non-transitory computer-readable medium of claim 103, wherein:

each of the first positioning assistance and the second positioning assistance comprises assistance data for one or more positioning methods, and

the one or more positioning methods include: assisted global navigation satellite system (a-GNSS), observed time difference of arrival (OTDOA), downlink time difference of arrival (DL-TDOA), downlink departure angle (DL-AoD), multi-cell Round Trip Time (RTT), enhanced cell identification (E-CID), real-time kinematic (RTK), state Space Representation (SSR), wireless Local Area Network (WLAN), bluetooth, sensor or any combination thereof.

105. The non-transitory computer-readable medium of claim 103, wherein the first positioning assistance comprises a first on-demand Positioning Reference Signal (PRS) configuration, wherein the second positioning assistance comprises a second on-demand PRS configuration.

106. The non-transitory computer readable medium of claim 105, further comprising computer executable instructions that, when executed by the location server, cause the location server to:

receiving one or more parameters for the first on-demand PRS configuration in the first request assistance data message; and

one or more parameters for the second on-demand PRS configuration are received in the second request assistance data message.

107. The non-transitory computer readable medium of claim 105, further comprising computer executable instructions that, when executed by the location server, cause the location server to:

a plurality of on-demand PRS configurations capable of being activated to support positioning of the UE are sent to the UE, wherein the first on-demand PRS configuration and the second on-demand PRS configuration are each members of the plurality of on-demand PRS configurations.

108. The non-transitory computer readable medium of claim 105, further comprising computer executable instructions that, when executed by the location server, cause the location server to:

and sending a second provide assistance data message to the UE, the second provide assistance data message indicating at least that the location server activated the second on-demand PRS configuration.

109. The non-transitory computer readable medium of claim 105, wherein:

the first request assistance data message further includes a start time and a duration for the first on-demand PRS configuration, and

the providing assistance data message also includes a fulfillment time that is greater than the start time and less than the duration and indicates when the location server expects to be able to activate the first on-demand PRS configuration.

110. The non-transitory computer readable medium of claim 103, further comprising computer executable instructions that, when executed by the location server, cause the location server to:

transmitting the retry time in the provide assistance data message; or alternatively

The retry time is sent in a previously provided assistance data message sent prior to sending the first request assistance data message.

111. The non-transitory computer readable medium of claim 103, further comprising computer executable instructions that, when executed by the location server, cause the location server to:

and sending a second time to the UE in the provide assistance data message, the second time indicating a time when the location server expects to provide the second positioning assistance to the UE.

112. The non-transitory computer-readable medium of claim 111, further comprising computer-executable instructions that, when executed by the location server, cause the location server to:

the second positioning assistance is sent in a second provide assistance message before the second time.