Assistance data delivery for reference location devices - Patents.com

Abstract

Techniques for wireless communications are disclosed. In one aspect, a user equipment (UE) may register with a first network entity as a reference location device. The UE may receive positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one transmit reception point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

Description

[Technical field]

[0001] Aspects of the present disclosure generally relate to wireless communications. [Background technology]

[0002] Wireless communication systems have evolved through various generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including intermediate 2.5G and 2.75G networks), third generation (3G) high speed data, Internet-enabled wireless service, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular and personal communication service (PCS) systems. Examples of known cellular systems include Cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0003]

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

[0004]

[0004] The following provides a simplified summary related to one or more aspects disclosed herein. Therefore, the following summary should not be considered an extensive overview related to all contemplated aspects, nor should the following summary be considered to identify key or critical elements related to all contemplated aspects or to define the scope related to a particular aspect. Thus, the following summary has the sole purpose of presenting, in a simplified form, some concepts related to one or more aspects related to the mechanisms disclosed herein, prior to the detailed description presented below.

[0005]

[0005] In one aspect, a method of wireless communications implemented by a User Equipment (UE) includes registering with a first network entity as a reference location device; and receiving positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one transmission-reception point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0006]

[0006] In one 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, wherein the at least one processor is configured to register with a first network entity as a reference location device, and receive, via the at least one transceiver, positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit receiving point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0007]

[0007] In one aspect, a user equipment (UE) includes means for registering with a first network entity as a reference location device, and means for receiving positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit receiving point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0008]

[0008] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to register with a first network entity as a reference location device; and receive positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit receiving point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0009]

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

[0010]

[0010] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided merely to illustrate the aspects, not to limit the aspects. [Brief description of the drawings]

[0011] [Figure 1]

[0011] FIG. 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 2A]

[0012] FIG. 1 illustrates an example wireless network structure, according to aspects of the present disclosure. [Figure 2B] FIG. 1 illustrates an example wireless network structure, according to aspects of the present disclosure. [Figure 3A]

[0013] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a base station and configured to support communication as taught herein. [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a network entity and configured to support communications as taught herein. [Figure 4]

[0014] FIG. 2 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) call flow between a UE and a location server for performing a positioning operation. [Diagram 5]

[0015] 1 illustrates an example frame structure in accordance with aspects of the present disclosure. [Figure 6]

[0016] FIG. 1 illustrates an example downlink positioning reference signal (DL-PRS) configuration for two transmit receiving points (TRPs) operating in the same positioning frequency layer, in accordance with an aspect of the disclosure. [Figure 7]

[0017] FIG. 1 illustrates an example wireless communication network in which reference location devices (RLDs) are used to assist in positioning of UEs, according to aspects of the present disclosure. [Figure 8]

[0018] 4 illustrates an example UE positioning operation according to an aspect of the present disclosure. [Figure 9]

[0019] 1 illustrates an example reference location device positioning operation according to an aspect of the disclosure. [Figure 10]

[0020] FIG. 14 illustrates an example of a modification that may be made to an information element (IE) to identify whether the PRS resources specified in the PRS-Resource-r16 IE are applicable to RLD, non-RLD UEs, or both. [Figure 11]

[0021] 1 illustrates an example of PRS resource groups, where each PRS resource group is dedicated for use by either RLD or non-RLD UEs. [Figure 12]

[0022] FIG. 2 illustrates another example of PRS resource groups, where some PRS resources within each PRS resource group are dedicated for use by an RLD, and other PRS resources within the PRS group are dedicated for use by non-RLD UEs. [Figure 13]

[0023] FIG. 2 illustrates another example of PRS resource groups, where some PRS resources within a PRS resource group are dedicated for use by an RLD and other PRS resources within other PRS resource groups are dedicated for use by non-RLD UEs. [Figure 14]

[0024] FIG. 13 illustrates a table illustrating an example of modifications that may be made to an IE to distinguish positioning AD used by an RLD from positioning AD used by non-RLD UEs. [Figure 15]

[0025] FIG. 13 shows a table illustrating an example of modifications that may be made to another IE to distinguish positioning AD used by RLD from positioning AD used by non-RLD UEs. [Figure 16]

[0026] FIG. 13 shows a table illustrating an example of modifications that may be made to yet another IE to distinguish positioning AD used by RLD from positioning AD used by non-RLD UEs. [Figure 17]

[0027] 1 illustrates an example method of wireless communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012]

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

[0013]

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

[0014]

[0030] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to 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, in part on the desired design, in part on the corresponding technology, etc.

[0015]

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

[0016]

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

[0017]

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

[0018]

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

[0019]

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

[0020]

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

[0021]

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

[0022]

[0038] The base stations 102 collectively form a RAN and may interface with a core network 170 (e.g., Evolved Packet Core (EPC) or 5G Core (5GC)) through backhaul links 122 and through the core network 170 to one or more location servers 172 (e.g., a Location Management Function (LMF) or a Secure User Plane Location (SUPL) Location Platform (SLP)). The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as through an application server (not shown), through another network, such as through a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below). For signaling purposes, 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 direct connection 128), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

[0023]

[0039] In addition to other functions, the base stations 102 may perform functions related to one or more of the following: forwarding user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracing, 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 / 5GC) via backhaul links 134, which may be wired or wireless.

[0024]

[0040] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage to a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, 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.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Because a cell is supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. Additionally, the terms "cell" and "TRP" may be used interchangeably, since a TRP is generally a physical transmission point of a cell. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, so long as the carrier frequency can be detected and used for communication within any portion of the geographic coverage area 110.

[0025]

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

[0026]

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

[0027]

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

[0028]

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

[0029]

[0045] The wireless communication system 100 may further include a mmW base station 180 that may operate in millimeter wave (mmW) and / or near-mmW frequencies in communication with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Near-mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The very high frequency (SHF) band, also called centimeter wave, extends between 3 GHz and 30 GHz. Communications using the mmW / near-mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely high path loss and short range. Moreover, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Thus, it will be appreciated that the above description is by way of example only and should not be construed as limiting various aspects disclosed herein.

[0030]

[0046] Transmit beamforming is a technique for focusing an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). In 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(s). To change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. In particular, RF current from the transmitter is fed to the individual antennas with the proper phase relationship so that the waves from the separate antennas add together to increase radiation in the desired direction while canceling and suppressing radiation in undesired directions.

[0031]

[0047] A transmit beam may be quasi-colocated, meaning that the transmit beam appears to a receiver (e.g., a UE) to have the same parameters, regardless of whether the network node's transmit antennas themselves are physically colocated. In NR, there are four types of quasi-colocated (QCL) relationships. In particular, a QCL relationship of a given type means that some parameters for a second reference RF signal on a second beam may be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the 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 receive parameters of a second reference RF signal transmitted on the same channel.

[0032]

[0048] In receive beamforming, a receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase its gain level) an RF signal received from that direction. Thus, when a receiver is said to beamform in a direction, it means that the beam gain in that direction is high relative to the beam gains along other directions, or that the beam gain in that direction is highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-Plus-Noise Ratio (SINR), etc.) of the RF signal received from that direction.

[0033]

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

[0034]

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

[0035]

[0051] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers, although portions of FR1 are greater than 6 GHz. A similar naming issue sometimes arises with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though FR2 is distinct from the extremely high frequency (EHF) bands (30 GHz to 300 GHz) identified as "millimeter wave" bands by the International Telecommunications Union (ITU).

[0036]

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

[0037]

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

[0038]

[0054] 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., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and may be a carrier in licensed frequencies (although this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in unlicensed frequencies. The secondary carrier may contain only the necessary signaling information and signals, and the signaling information and signals that are UE-specific may not be present in the secondary carrier, for example, since both the primary uplink carrier and the primary downlink carrier are typically UE-specific. 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 different carriers. Since a "serving cell" (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0039]

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

[0040]

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

[0041]

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

[0042]

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

[0043]

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

[0044]

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

[0045]

[0061] In a satellite positioning system, the use of the signals 124 may be augmented by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, the SBAS may include augmentation system(s) that provide integrity information, differential corrections, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and the like. 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.

[0046]

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

[0047]

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

[0048]

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

[0049]

[0065] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, alternatively, each may correspond to a single server. The location servers 230 may be configured to support one or more location services for the UEs 204 that may connect to the location server 230 via the core network, the 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).

[0050]

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

[0051]

[0067] The functions of the UPF 262 include serving as an anchor point for intra / inter-RAT mobility (when applicable), serving as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), 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 for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "termination markers" to the source RAN node. The UPF 262 may also support the transfer of location service messages over the user plane between the UE 204 and a location server, such as the SLP 272.

[0052]

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

[0053]

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

[0054]

[0070] Yet another optional aspect may include a third party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 may be referred to as a location services (LCS) client or an external client. The third party servers 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or may alternatively each correspond to a single server.

[0055]

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

[0056]

[0072] The functions of the gNB 222 may be divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions such as forwarding user data, mobility control, radio access network sharing, positioning, session management, etc., except for functions exclusively allocated to the gNB-DU(s). More specifically, the gNB-CU 226 generally hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that 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 can 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 one or more gNB-DUs 228 is referred to as an "F1" interface. The physical (PHY) layer functions of the gNB 222 are generally hosted by one or more standalone gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as an "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, with the gNB-DU 228 via the RLC layer and the MAC layer, and with the gNB-RU 229 via the PHY layer.

[0057]

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

[0058]

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

[0059]

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

[0060]

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

[0061]

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

[0062]

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

[0063]

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

[0064]

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

[0065]

[0081] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). The memories 340, 386, and 396 may thus provide a means for storing, a means for retrieving, a means for maintaining, etc. In some cases, the UE 302, the base station 304, and the 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, the base station 304, and the network entity 306 to perform the functions 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 functions described herein. FIG. 3A illustrates possible locations of the positioning component 342, which may be, for example, part of 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 shows possible locations of a positioning component 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C illustrates possible locations of a positioning component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0066]

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

[0067]

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

[0068]

[0084] Referring to the one or more processors 384 in more detail, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions related to broadcasting 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 related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to transfer of higher layer PDUs, error correction via automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0069]

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

[0070]

[0086] At the UE 302, the receiver 312 receives the signal through its respective antenna(s) 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement Layer 1 functions related to various signal processing functions. The receiver 312 may perform spatial processing on the information to recover the spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted 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) functions.

[0071]

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

[0072]

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

[0073]

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

[0074]

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

[0075]

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

[0076]

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

[0077]

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

[0078]

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

[0079]

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

[0080]

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

[0081]

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

[0082]

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

[0083]

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

[0084]

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

[0085]

[0101] To assist the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of the base station (or cell / TRP of the base station) from which to measure the reference signal, reference signal configuration parameters (e.g., number of consecutive positioning subframes, periodicity of the positioning subframes, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may originate directly from the base station itself (e.g., in a periodically broadcasted overhead message, etc.). In some cases, the UE may be able to detect neighbor network nodes on its own without using the assistance data.

[0086]

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

[0087]

[0103] A location estimate may be called by other names, such as a position estimate, location, position, position fix, fix, etc. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of the location. A location estimate may further be defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume that the location is expected to cover with some specified or default confidence level).

[0088]

[0104] 4 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 400 between a UE 404 and a location server (shown as Location Management Function (LMF) 470) for performing a positioning operation. As shown in FIG. 4, positioning of the UE 404 is supported via an exchange of LPP messages between the UE 404 and the LMF 470. The LPP messages may be exchanged between the UE 404 and the LMF 470 via a serving base station of the UE 404 (shown as a serving gNB 402) and a core network (not shown). The LPP procedure 400 may be used to position the UE 404 to support various location-related services, such as navigation for the UE 404 (or for a user of the UE 404), for routing, or to provide an accurate location to a public safety answering point (PSAP) in connection with an emergency call from the UE 404 to the PSAP, or for some other reason. The LPP procedure 400 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), Extended Cell Identity (E-CID), etc.).

[0089]

[0105] Initially, the UE 404 may receive a request for its positioning capabilities (e.g., an LPP Capability Request message) from the LMF 470 at stage 410. At stage 420, the UE 404 provides the LMF 470 with its positioning capabilities for the LPP protocol by sending an LPP Capability Provision message to the LMF 470 indicating the positioning methods and characteristics of these positioning methods supported by the UE 404 using LPP. The capabilities indicated in the LPP Capability Provision message may, in some aspects, indicate the types of positioning that the UE 404 supports (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the ability of the UE 404 to support those types of positioning.

[0090]

[0106] Upon receipt of the LPP capability provision message in stage 420, the LMF 470 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated type(s) of positioning that the UE 404 supports, and determines a set of one or more Transmission Reception Points (TRPs) from which the UE 404 should measure downlink positioning reference signals or to which the UE 404 should transmit uplink positioning reference signals. In stage 430, the LMF 470 sends an LPP assistance data provision message to the UE 404 identifying the set of TRPs.

[0091]

[0107] In some implementations, the Provide LPP Assistance Data message in stage 430 may be sent by the LMF 470 to the UE 404 in response to an LPP Request Assistance Data message (not shown in FIG. 4) sent by the UE 404 to the LMF 470. The Request LPP Assistance Data message may include an identifier of the serving TRP of the UE 404 and a request for Positioning Reference Signal (PRS) configuration of the neighboring TRPs.

[0092]

[0108] In stage 440, the LMF 470 sends a request for location information to the UE 404. The request may be an LPP Location Information Request message. This message typically includes information elements that define the location information type, the desired accuracy of the location estimate, and the response time (i.e., the desired latency). Note that a low latency requirement allows for a longer response time, while a high latency requirement requires a shorter response time. However, a long response time is referred to as a high latency, and a short response time is referred to as a low latency.

[0093]

[0109] It should be noted that in some implementations, for example, if the UE 404 sends a request for assistance data to the LMF 470 (e.g., in an LPP Assistance Data Request message, not shown in FIG. 4) after receiving a request for location information at stage 440, the LPP Provide Assistance Data message sent at stage 430 may be sent after the LPP Request Location Information message at 440.

[0094]

[0110] In step 450, the UE 404 utilizes the assistance information received in step 430 and any additional data received in step 440 (e.g., desired location accuracy or maximum response time) to perform positioning operations (e.g., measuring DL-PRS, transmitting UL-PRS, etc.) for the selected positioning method.

[0095]

[0111] In stage 460, the UE 404 may send an LPP Provide Location Information message to the LMF 470 conveying the results of the measurements (e.g., Time of Arrival (ToA), Reference Signal Time Difference (RSTD), Receive-Transmit (Rx-Tx), etc.) obtained in stage 450 and before or when any maximum response time (e.g., the maximum response time provided by the LMF 470 in stage 440) expires. The LPP Provide Location Information message in stage 460 may also include the time(s) at which the positioning measurements were obtained and the identity of the TRP(s) from which the positioning measurements were obtained. Note that the time between the request for location information in 440 and the response in 460 is the "response time" and indicates the latency of the positioning session.

[0096]

[0112] The LMF 470 calculates an estimated location of the UE 404 using an appropriate positioning technique (e.g., DL-TDOA, RTT, E-CID, etc.) based at least in part on the measurements received in the LPP location information provision message in stage 460.

[0097]

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

[0098]

[0114] LTE, and possibly 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 use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be fifteen kilohertz (15 kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Thus, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0099]

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

[0100]

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

[0101]

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

[0102]

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

[0103]

[0119] PRS are defined for NR positioning to enable the UE to detect and measure more neighboring TRPs. Several configurations are supported to enable different deployments (e.g., indoor, outdoor, sub-6 GHz, mmW). Furthermore, PRS can be configured for both UE-based and UE-assisted positioning procedures. The following table shows different types of reference signals that can be used for different positioning methods supported in NR.

[0104] [Table 1]

[0105]

[0120] A set of resource elements (REs) used for transmission of a PRS is called a "PRS resource." A set of resource elements may span multiple PRBs in the frequency domain and may span "N" consecutive symbols (such as one or more) within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

[0106]

[0121] The transmission of PRS resources in a given PRB has a particular comb size (also called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. In particular, for comb size "N", the PRS is transmitted in every Nth subcarrier of the symbol of the PRB. For example, for Com 4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes of Com 2, Com 4, Com 6, and Com 12 are supported for DL-PRS. Figure 5 shows an example PRS resource configuration for Com 4 (spanning four symbols). That is, the location of the shaded REs (labeled "R") indicates the Com 4 PRS resource configuration.

[0107]

[0122] Currently, DL-PRS resources may span 2, 4, 6, or 12 consecutive symbols in a slot with a fully frequency-domain staggered pattern. DL-PRS resources may be configured in any upper layer configured downlink or flexible (FL) symbol of a slot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. Below are the frequency offsets between symbols for comb sizes 2, 4, 6, and 12 across 2, 4, 6, and 12 symbols. Comb 2 with 2 symbols: {0,1}, Comb 2 with 4 symbols: {0,1,0,1}, Comb 2 with 6 symbols: {0,1,0,1,0,1}, Comb 2 with 12 symbols: {0,1,0,1,0,1,0,1,0,1,0,1}, Comb 4 with 4 symbols: {0,2,1,3} (shown in the example in Figure 5), Comb 4 with 12 symbols: {0,2,1,3,0,2,1,3,0,2,1,3}, Comb 6 with 6 symbols: {0,3,1,4,2,5}, Comb 6 with 12 symbols: {0,3,1,4,2,5,03,1,4,2,5}, and Com 12 with 12 symbols: {0,6,3,9,1,7,4,10,2,8,5,11}.

[0108]

[0123] A "PRS resource set" is a set of PRS resources used for transmission of a PRS signal, where each PRS resource has a PRS resource ID. Furthermore, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID). Furthermore, the PRS resources in a PRS resource set have the same periodicity across slots, a common muting pattern configuration, and the same repetition factor (e.g., "PRS-ResourceRepetitionFactor"). The periodicity is the time from the first repetition of the first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} slots, with μ=0, 1, 2, 3. The repetition factor may have a length selected from {1,2,4,6,8,16,32} slots.

[0109]

[0124] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or multiple beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus a "PRS resource" or simply a "resource" may also be referred to as a "beam." Note that this does not have any implication as to whether the TRP and the beam on which the PRS is transmitted are known to the UE.

[0110]

[0125] A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (e.g., a group of one or more contiguous slots) during which a PRS is expected to be transmitted. A PRS occasion may also be called a "PRS positioning occasion", "PRS positioning instance", "positioning occasion", "positioning instance", "positioning repetition", or simply an "occasion", "instance", or "repetition".

[0111]

[0126] A "positioning frequency layer" (also simply called a "frequency layer") is a collection of one or more PRS resource sets across one or more TRPs with the same values ​​for some parameters. In particular, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for the PRS), the same point A, the same value of the 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" ("ARFCN" stands for "Absolute Radio Frequency Channel Number"), which is an identifier / code that specifies the pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers are defined, and up to two PRS resource sets may be configured per TRP per frequency layer.

[0112]

[0127] The concept of frequency layers is somewhat like that of component carriers and bandwidth portions (BWPs), except that component carriers and BWPs are used by one base station (or macrocell base station and small cell base station) to transmit data channels, and frequency layers are used by several (usually three or more) base stations to transmit PRSs. When a UE sends its positioning capabilities to the network, such as during an LTE Positioning Protocol (LPP) session, it may indicate the number of frequency layers it can support. For example, a UE may indicate whether it can support one or four positioning frequency layers.

[0113]

[0128] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to the unique reference signals used for positioning in NR and LTE systems. However, the terms "positioning reference signal" and "PRS" as used herein may also refer to any type of reference signal that may be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS defined in LTE and NR. Furthermore, the terms "positioning reference signal" and "PRS" may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If further differentiation of PRS types is required, downlink positioning reference signals may be referred to as "DL-PRS" and uplink positioning reference signals (e.g., SRS, PTRS for positioning) may be referred to as "UL-PRS". Furthermore, for signals that may be transmitted in both uplink and downlink (e.g., DMRS, PTRS), those signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be differentiated from "DL-DMRS."

[0114]

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

[0115]

[0130] 7 is a diagram 700 of an example wireless communication network in which an RLD 710 (also referred to as a reference device) is used to assist in positioning of a UE 704, according to an aspect of the disclosure. In the example of FIG. 7, a UE 704 (e.g., any of the UEs described herein) is engaged in a positioning session with three TRPs 702-1, 702-2, and 702-3 (collectively, TRPs 702), labeled "TRP1," "TRP2," and "TRP3," respectively. The TRPs 702 are transmitting downlink reference signals (e.g., DL-PRS) toward the UE 704 to enable the UE 704 to perform positioning measurements of the reference signals (e.g., RSTD measurements in the example of FIG. 7).

[0116]

[0131] The RLD 710 also receives and measures downlink reference signals from the TRPs 702 and reports the measurements (e.g., RSTD) to a location server (not shown). If the TRP 702-1 is the reference TRP, the RSTD for the TRP 702-2 measured by the RLD 710 is RSTD meas = t2 - t1. The location server knows the locations of the RLD 710 and the TRP 702 and can therefore calculate the "true" (expected) RSTD at the location of the RLD 710 as follows:

[0117]

number

[0118] where c is the speed of light. (x0,y0) (represented in FIG. 7 as (x0,y0)) is the known location of RLD 710, (x1,y1) (represented in FIG. 7 as (x1,y1)) is the known location of TRP 702-1, and (x2,y2) (represented in FIG. 7 as (x2,y2)) is the known location of TRP 702-2.

[0119]

[0132] The location server can then determine the error term (e) as follows:

[0120]

number

[0121]

[0133] When a normal UE 704 (in an unknown location) is measuring the RSTD between TRP 702-1 and TRP 702-2, the location server can use the previously determined error term to correct the measured RSTD of the UE 704 as follows:

[0122]

number

[0123]

[0134] The location server can then use the corrected RSTD to estimate the location of the UE 704. The same principle applies to uplink positioning methods, where the RLD transmits an uplink positioning signal (e.g., SRS) that is measured by the TRP. Given the known locations of the RLD and the TRP, the TRP uplink measurements can be compared to the "true" (expected) uplink measurements (e.g., UL-AoA, UL-RTOA, etc.). The difference between the "true" (expected) uplink measurements and the actually performed measurements will define an error term that can be used to correct the UE's uplink measurements.

[0124]

[0135] To support NR positioning techniques, an RLD with known location is expected to support the following functions: Measure DL-PRS and report related measurements (e.g. RSTD, Rx-Tx time difference, RSRP, etc.) to the location server. · Transmits the SRS and enables the TRP to measure measurements related to the reference device (e.g. RTOA, Rx-Tx time difference, AoA) and report the same to the location server.

[0125]

[0136] The RLD may also support the following features: Reporting signalling, measurements, parameters related to receive and transmit timing delays, AoD and AoA extensions, and measurement calibration details. Reporting device location coordinate information to LMF if LMF does not have the information. The RLD with known location is a UE and / or a gNB. · The accuracy to which the location of the reference device is known.

[0126]

[0137] The RLD performs positioning measurements just like a normal UE, but at a pre-known location, so the positioning protocol terminated in the RLD and TRP can be the same protocol used for positioning of a normal UE.

[0127]

[0138] 8 illustrates an example UE positioning operation 800 according to an aspect of the disclosure. The UE positioning operation 800 may be performed by the UE 204, an NG-RAN node 802 in the NG-RAN 220 (e.g., the gNB 222, the gNB-CU 226, the ng-eNB 224, or other nodes in the NG-RAN 220), the AMF 264, the LMF 270, and a 5GC Location Services (LCS) entity 880 (e.g., any third party application requesting the location of the UE 204, a public safety access point (PSAP), an E-911 server, etc.).

[0128]

[0139] A location service request to obtain the location of the target (i.e., the UE 204) may be initiated by the 5GC LCS entity 880, the AMF 264 serving the UE 204, or the UE 204 itself. Figure 8 illustrates these options as steps 810a, 810b, and 810c, respectively. In particular, in step 810a, the 5GC LCS entity 880 sends a location service request to the AMF 264. Alternatively, in step 810b, the AMF 264 generates the location service request itself. Alternatively, in step 810c, the UE 204 sends a location service request to the AMF 264.

[0129]

[0140] When the AMF 264 receives (or generates) the location service request, the AMF 264 forwards the location service request to the LMF 270 in stage 820. The LMF 270 then performs an NG-RAN positioning procedure with the NG-RAN node 802 in stage 830a and a UE positioning procedure with the UE 204 in stage 830b. The specific NG-RAN positioning procedure and UE positioning procedure may depend on the type(s) of positioning method(s) used to locate the UE 204, which may depend on the capabilities of the UE 204. The positioning method(s) may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, and DL-AoD), uplink-based (e.g., UL-TDOA and UL-AoA), and / or downlink- and uplink-based (e.g., LTE / NR E-CID and RTT), as described above. The corresponding positioning procedures are described in detail in 3GPP Technical Specification (TS) 38.305, which is published and incorporated herein by reference in its entirety.

[0130]

[0141] NG-RAN and UE positioning procedures may utilize LTE Positioning Protocol (LPP) signaling between the UE 204 and the LMF 270, and LPP Type A (LPPa) or NR Positioning Protocol Type A (NRPPa) signaling between the NG-RAN node 802 and the LMF 270. LPP is used point-to-point between a location server (e.g., the LMF 270) and a UE (e.g., the UE 204) to obtain location-related measurements or location estimates or to transfer assistance data. A single LPP session is used to support a single location request (e.g., for a single MT-LR, MO-LR, or Network Induced Location Request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions, with each LPP transaction performing a single operation (e.g., capability exchange, assistance data transfer, location information transfer). LPP transactions are referred to as LPP procedures.

[0131]

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

[0132]

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

[0133]

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

[0134]

[0145] As part of the NG-RAN node positioning procedure (stage 830a) and the UE positioning procedure (stage 830b), the LMF 270 may provide LPP assistance data in the form of DL-PRS configuration information to the NG-RAN node 802 and the UE 204 for the selected positioning method(s). Alternatively or additionally, the NG-RAN node 802 may provide DL-PRS and / or UL-PRS configuration information to the UE 204 for the selected positioning method(s). It should be noted that although FIG. 8 shows a single NG-RAN node 802, there may be multiple NG-RAN nodes 802 involved in a positioning session.

[0135]

[0146] When configured in DL-PRS and UL-PRS configurations, the NG-RAN node 802 and the UE 204 transmit and receive / measure their respective PRS at scheduled times. The NG-RAN node 802 and the UE 204 then send their respective measurements to the LMF 270.

[0136]

[0147] Once the LMF 270 has obtained measurements from the UE 204 and / or the NG-RAN node 802 (depending on the type(s) of the positioning method(s)), the LMF 270 uses those measurements to calculate an estimate of the location of the UE 204. Then, in stage 840, the LMF 270 sends a location service response to the AMF 264 including the location estimate for the UE 204. The AMF 264 then forwards the location service response to the entity that generated the location service request in stage 810. In particular, if in stage 810a a location service request is received from the 5GC LCS entity 880, then in stage 850a the AMF 264 sends a location service response to the 5GC LCS entity 880. However, if in stage 810c a location service request is received from the UE 204, then in stage 850c the AMF 264 sends a location service response to the UE 204. Alternatively, if the AMF 264 generated a location service request in step 810b, in step 850b, the AMF 264 stores / uses the location service response itself.

[0137]

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

[0138]

[0149] Referring to the RLD in the context of FIG. 8, any RLD location measurements will be used by the LMF 270 to correct measurements for the target UE 204. That is, the consumer of the RLD location information is the LMF 270, and therefore steps 810 and 820 will not be performed for the RLD. This essentially means that the LMF 270 needs to become an "LCS client" for the RLD and be enabled to trigger a location session with the RLD in the absence of steps 810 and 820. Thus, for an RLD, the AMF 264 / LMF 270 will not receive a location request from an LCS client; instead, the location client for the RLD measurements will be the LMF 270 itself.

[0139]

[0150] As a result of the above, for an RLD positioning operation, steps 810 and 820 in FIG. 8 may be replaced by an "RLD registration" procedure to make the LMF aware of the RLD in the network, and thus the LMF is enabled to induce an LPP or NRPPa session with the desired RLD or NG-RAN serving the RLD, respectively. FIG. 9 illustrates an example RLD positioning operation 900 according to an aspect of the disclosure. The RLD positioning operation 900 may be performed by an RLD 904 (e.g., any of the RLDs described herein), an NG-RAN node 902 (e.g., gNB 222, ng-eNB 224), an AMF 264, and an LMF 270.

[0140]

[0151] In stage 910, an RLD registration procedure is performed to make the LMF 270 aware of the RLD 904 in the network. In an aspect, the registration procedure may depend on whether the RLD 904 is considered to be a UE or a gNB, and different registration procedures may be used for each. In stage 920, the LMF 270 internally initiates a location service request to obtain the location of the target RLD 904 to determine correction data for UE positioning. The LMF 270 then performs an NG-RAN procedure with the NG-RAN node 902 in stage 930a and an RLD procedure with the RLD 904 in stage 930b. The RLD registration procedure in stage 910 allows the LMF 270 to trigger the positioning procedure in stage 930 in a similar manner as currently specified for the target UE. In stage 940, the LMF 270 determines correction data for UE positioning as described above with reference to FIG. 7.

[0141]

[0152] The positioning assistance data (AD) is common between UEs operating in normal capacity (referred to herein as "non-RLD") and UEs operating as RLDs. Thus, the same positioning AD is used by both RLD and non-RLD UEs. Note that the positioning AD indicates a hierarchy of positioning frequency layers (PFLs), TRPs, PRS resource sets, and PRS resources, as shown in Figure 6.

[0142]

[0153] Unlike measurements from non-RLD UEs, measurements from a UE acting as an RLD are used for calibration purposes, not for actual positioning. Thus, an RLD does not need to have the same processing capabilities, transmit power, etc. of a non-RLD UE. Furthermore, a UE acting as an RLD does not necessarily need to measure the same PRS resources or the same number of PRS resources as a non-RLD UE. Furthermore, an RLD may have a different priority for measuring PRS resources than a non-RLD UE. Thus, the present disclosure provides various techniques for making special provisions for positioning AD for an RLD.

[0143]

[0154] Broadcasting of positioning AD is supported via the positioning system information block (posSIB). The posSIB is carried in the RRC system information (SI) transmitted by the gNB (e.g., gNB222) using a wireless communication protocol. The mapping of the posSIB to the SI message can be flexibly configured according to the pos-schedulingInfoList parameter included in the SIB type 1 message (also called SIB1) that is periodically broadcast from the gNB (e.g., gNB222), defined for the RRC protocol. A separate posSIB type can be defined for each AD element defined in the LPP. As examples, posSIBs designated as posSibType1-1 to posSibType1-7 may contain common GNSS assistance data, posSibType2-1 to posSibtype2-19 may contain GNSS specific assistance data, where the specific GNSS is indicated in the "pos-schedulingInfoList" in SIB1, posSibType3-1 may contain OTDOA assistance data, posSibType6-1 may contain NR-"DL-PRS-AssistanceData", "posSibType6-2" may contain "R-UEB-TRP-LocationData", and "posSibType6-3" may contain "NR-UEB-TRP-RTD-Info".

[0144]

[0155] The existing posSIB is broadcast for use by all UEs, regardless of whether the UE is an RLD or non-RLD UE. Thus, no provision is made to distinguish positioning AD that is applicable to RLDs from positioning AD that is applicable to non-RLD UEs. Currently, differences in processing capabilities, transmit power, and / or functionality that may exist between RLD and non-RLD UEs are effectively ignored when providing positioning AD.

[0145]

[0156] According to various aspects of the disclosure, a new posSIB type may be defined. The new posSIB type (e.g., "posSibType 6-4" or other posSibType designation) may be used to provide positioning AD that is specifically applicable to UEs operating as RLDs as opposed to UEs operating as non-RLD UEs. In an aspect, only UEs that register as RLDs with an AMF or location server (LS) may request the new posSIB type. Furthermore, since current standards allow encryption of different posSIBs using different encryption keys, e.g., 128-bit Advanced Encryption Standard (AES) algorithms. The RLD may be provided with the encryption key for the new posSIB type during the UE's registration as an RLD with an AMF or LS, e.g., as in step 910 of FIG. 9. In an aspect, only RLDs with the correct encryption key will have access to the positioning AD of the new posSIB, and non-RLD UEs will not have such access. In an aspect, an indication of whether the new posSIB type is encrypted or not encrypted may be provided in the "pos-schedulingInfoList" parameter. By using the new posSIB type, the LS or gNB may adapt the positioning AD for the RLD to take advantage of the unique characteristics and capabilities of the RLD. UEs with reduced processing capabilities and / or power consumption may be used for the RLD by allowing the LS or gNB to reduce the number of PRS resources expected to be measured by the RLD during a positioning session compared to the larger number of PRS resources that would be measured by non-RLD UEs. In an aspect, the LS or gNB may set priorities for the measurement of PRS resources of the positioning AD using the new posSIB type. Furthermore, the new posSIB type may be an addition to currently existing posSIB types, so that systems adopting the new posSIB type will be backward compatible with existing standards.

[0146]

[0157] Additionally or alternatively, one or more information elements (IEs) may specify PRS resources of the positioning AD applicable to the RLD. In one example, the LS or gNB may select a specific PRS resource to be measured by the RLD versus a PRS resource to be measured by a non-RLD UE. As an example, the "NR-DL-PRS-Resource-r16" IE may be modified in the manner shown in Table 1000 of FIG. 10 to identify whether the PRS resource specified in the "PRS-Resource-r16" IE is applicable to the RLD, non-RLD UE, or both. The IE NR-DL-PRS is one of the information elements that defines the downlink PRS resource configuration.

[0147]

[0158] In the example shown in table 1000, a dl-PRS-RLD Applicability IE is added to the "NR-DL-PRS-Resource-r16" IE. The "dl-PRS-RLD Applicability" IE includes an optional flag (e.g., ENUMERATED{n0,n1,n2})) indicating whether the PRS structure is applicable to RLD, non-RLD UEs, or both. As an example, the following values ​​may be used in the ENUMERATED field:

[0148] 0, indicating that the specified PRS resource is applicable for both RLD and non-RLD UEs; 1, indicating that the specified PRS resource is only applicable for non-RLD UEs; and Indicates that the PRS resource is only applicable for the RLD2.

[0149]

[0159] A "DL-PRS-Resource-r16" IE with "dl-PRS-RLD Applicability" IE set to 0 or 1 informs a non-RLD UE that it should use the PRS resources defined by the "DL-PRS-Resource-r16" IE. A non-RLD UE receiving a "DL-PRS-Resource-r16" IE with "dl-PRS-RLD Applicability" IE set to 2 may ignore the PRS resources defined by the "DL-PRS-Resource-r16" IE. Similarly, an RLD receiving a "DL-PRS-Resource-r16" IE with "dl-PRS-RLD Applicability" IE set to 0 or 2 informs the RLD that it should use the PRS resources defined by the "DL-PRS-Resource-r16" IE. However, an RLD receiving the "DL-PRS-Resource-r16" IE with the "dl-PRS-RLD Applicability" IE set to 1 may ignore the PRS resources defined by the "DL-PRS-Resource-r16" IE. Thus, the LS or gNB may define PRS resources separately for RLD and non-RLD UEs. According to one aspect of the present disclosure, the ENUMERATED field may be set to 0 such that the modified DL-PRS-Resource-r16 IE is backward compatible with legacy UEs.

[0150]

[0160] Additionally or alternatively, the LS or gNB may structure the positioning AD using separate PFL / TRP / PRS resources that are dedicated for use by the RLD for non-RLD UEs. The division of PFL / TRP / PRS resources may be implemented, for example, using IEs defined in the positioning SIB. Additionally or alternatively, the division of PFL / TRP / PRS resources may be implemented using other IEs described herein.

[0151]

[0161] 11 is a diagram 1100 illustrating an example of two groups of PRS resources, where each PRS resource group is dedicated for use by either RLD or non-RLD UEs, where the PRS resources of the PRS resource groups are in different PFLs dedicated for use by either RLD or non-RLD UEs. In this example, PRS resource group 1102 is dedicated for use by one or more non-RLD UEs 1104, and PRS resource group 1106 is dedicated for use by one or more RLDs 1108. The PRS resources of PRS resource group 1102 are in a first dedicated positioning frequency layer labeled "PFL1," and the PRS resources of PRS resource group 1106 are in a second different dedicated positioning frequency layer labeled "PFL2."

[0152]

[0162] As shown in FIG. 11, PRS resource group 1102 includes TRPs labeled "TRP1" and "TRP2", each operating in positioning frequency layer PFL1. TRP1 includes two PRS resource sets, shown as "Set1" and "Set2". Each PRS resource set will include one or more PRS resources (not shown). Within PRS resource group 1102, TRP2 includes different PRS resource sets, shown as "Set3" and "Set4". Unlike PRS resource group 1102, PRS resource group 1104 includes different TRPs, shown as "TRP3" and "TRP4", each operating in positioning frequency layer PFL2. TRP3 of PFL2 includes two PRS resource sets, shown as "Set5" and "Set6". TRP4 of PFL2 includes separate PRS resource sets, shown as "Set7" and "Set8". According to some aspects of the present disclosure, the PRS resources of PFL2 will be measured by the RLD during a positioning session involving the RLD, and according to some aspects of the present disclosure, the PRS resources of PFL1 will be measured by the non-RLD UE during a positioning session involving the non-RLD UE.

[0153]

[0163] FIG. 12 is a diagram 1200 illustrating another example of PRS resource groups in which some PRS resources of each PRS resource group are dedicated for use by an RLD and other PRS resources of the PRS resource group are dedicated for use by non-RLD UEs. In this example, the PRS resources in PRS resource group 1202 are dedicated for use by one or more non-RLD UEs 1204, and the PRS resources of PRS resource group 1206 are dedicated for use by one or more RLDs 1208. Here, PRS resource group 1202 and PRS resource group 1206 are in a common positioning frequency layer PFL1. However, non-RLD UE 1204 uses PRS resources associated with TRP1, and RLD 1208 uses PRS resources associated with TRP2. In FIG. 12, TRP1 includes PRS resource sets labeled as "Set1" and "Set2." PRS resource set Set1 includes PRS resources labeled "R1", "R2", and "R3", and PRS resource set Set2 includes PRS resources labeled "R4", "R5", "R6", and "R7". As also shown in FIG. 12, TRP2 includes PRS resource sets labeled "Set3" and "Set4". PRS resource set Set3 includes PRS resources labeled "R8", and PRS resource set Set4 includes PRS resources labeled "R9" and "R10". According to aspects of the present disclosure, the PRS resources of TRP2 will be measured by the RLD during a positioning session involving the RLD. Also, according to some aspects of the present disclosure, the PRS resources of TRP1 will be measured by non-RLD UEs during a positioning session involving non-RLD UEs.

[0154]

[0164] 13 is a diagram 1300 illustrating another example of PRS resource groups where some PRS resources of one PRS resource group are dedicated for use by RLDs and PRS resources of other PRS resource groups are dedicated for use by non-RLD UEs. In this example, the PRS resources in PRS resource group 1302 are dedicated for use by one or more non-RLD UEs 1304, and the PRS resources of PRS resource group 1306 are dedicated for use by one or more RLDs 1308. PRS resource group 1302 and PRS resource group 1306 share a common positioning frequency layer PFL1 and a common TRP, shown in FIG. 13 as "TRP2." However, the non-RLD UE 1304 uses PRS resources labeled "R8", "R9", "R10", and "R11" in the PRS resource set Set3 associated with TRP2, and the RLD 1308 uses PRS resources labeled "R12", "R13", and "R14" associated with the PRS resource set Set4 of TRP2. As also shown in FIG. 13, the non-RLD UE also uses PRS resources labeled "R1", "R2", and "R3" in the PRS resource set Set1 and PRS resources labeled "R4", "R5", "R6", and "R7" in the PRS resource set Set2, where both the PRS resource set Set1 and the PRS resource set Set2 are associated with TRP1. According to aspects of the present disclosure, the PRS resources of the PRS resource set Set4 are measured by the RLD during a positioning session involving the RLD. Also, according to some aspects of the disclosure, a PRS resource associated with TRP1 and a PRS resource of PRS resource set Set3 associated with TRP2 are measured by a non-RLD UE during a positioning session involving the non-RLD UE.

[0155]

[0165] FIG. 14 shows a table 1400 illustrating an example of modifications that may be made to an IE to distinguish positioning AD used by an RLD from positioning AD used by a non-RLD UE. The example shown in table 1400 illustrates modifications to the currently defined "OTDOA-UE-Assisted" IE. The modified "OTDOA-UE-Assisted" IE may be invoked if a new posSIB type described herein is defined for UE-assisted OTDOA measurements. Here, the modified "OTDOA-UE-Assisted" IE includes an "otdoa-NeighbourCellInfo-r15-RLD" IE to specify a list of neighboring cells to be measured by the RLD during a positioning session in which the RLD should be involved in UE-assisted OTDOA measurements.

[0156]

[0166] FIG. 15 illustrates a table 1500 illustrating an example of modifications that may be made to another IE to distinguish the positioning AD used by the RLD from the positioning AD used by non-RLD UEs. In this example, the "NR-DL-PRS-AssistanceData" IE used by the location server to provide DL-PRS AD has been modified. As shown in table 1500, the "NR-DL-PRS-AssistanceData" IE has been modified to include the "nr-DL-PRS-AssistanceDataPerFreq-r16-RLD" IE. In one aspect of the disclosure, the "nr-DL-PRS-AssistanceDataPerFreq-r16-RLD" specifies DL-PRS resources for TRPs in the positioning frequency layer that should be measured by the RLD during the positioning session.

[0157]

[0167] FIG. 16 illustrates a table 1600 illustrating an example of modifications that may be made to yet another IE to distinguish the positioning AD used by the RLD from the positioning AD used by non-RLD UEs. In this example, the "NR-RTD-Info" IE used by the LS to provide time synchronization information between the reference TRP and the list of neighbor TRPs has been modified. As shown in table 1600, the "NR-RTD-Info" IE has been modified to include the "rtd-InfoList-r16-RLD" IE. In one aspect of the present disclosure, the "rtd-InfoList-r16-RLD" IE may be used to specify time synchronization for the list of neighbor TRPs to be measured by the RLD.

[0158]

[0168] 17 illustrates an example method 1700 of wireless communication according to an aspect of the present disclosure. In one aspect, the method 1700 may be performed by a UE as described herein.

[0159]

[0169] 17, the UE registers with a first network entity as a reference location device in operation 1702. In an aspect, operation 1702 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 a means for performing this operation.

[0160]

[0170] In operation 1704, the UE receives positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more PRS resources of at least one positioning reference signal (PRS) resource set of at least one transmit reception point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as a reference location device. In an aspect, operation 1704 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 a means for performing this operation.

[0161]

[0171] According to some aspects, the first network entity is an AMF. According to some aspects, the first network entity is a location server. According to some aspects, the second network entity is a location server, and the positioning assistance data is received in one or more LPP messages.

[0162]

[0172] According to some aspects, the positioning assistance data is received from the second network entity in one or more positioning system information blocks (posSIBs) that may be dedicated for use by transmitting positioning assistance data for the UE registered as a reference location device. In some aspects, the UE decodes the one or more posSIBs using information received from the first network entity during registration of the UE as a reference location device. In some aspects, the one or more posSIBs include a prioritization of measurements performed based on the positioning assistance data.

[0163]

[0173] In accordance with certain aspects of the disclosure, the positioning assistance data includes an indication associated with each of the one or more PRS resources indicating that the one or more PRS resources are for use by UEs registered as reference location devices, for use by UEs not registered as reference location devices, or for use by both UEs registered as reference location devices and UEs not registered as reference location devices. In some aspects, the positioning assistance data indicates at least one positioning frequency layer that is dedicated for UEs registered as reference location devices.

[0164]

[0174] In some aspects, the positioning assistance data indicates one or more positioning frequency layers that are common to UEs registered as reference location devices and UEs not registered as reference location devices. In one aspect, the one or more positioning frequency layers include a plurality of TRPs, where one or more TRPs of the plurality of TRPs are dedicated for use by UEs registered as reference location devices.

[0165]

[0175] In some aspects, the positioning assistance data indicates one or more TRPs that are common to UEs registered as reference location devices and UEs not registered as reference location devices. In one aspect, the one or more TRPs include a plurality of PRS resource sets, where one or more PRS resource sets of the plurality of PRS resource sets are dedicated for use by UEs registered as reference location devices.

[0166]

[0176] As will be appreciated, a technical advantage of method 1700 is that a UE configured as an RLD may receive positioning assistance data that is specific to the RLD, such that a network entity, such as an LS, may configure the positioning assistance data in view of functional characteristics that are specific to the RLD compared to non-RLD UEs in the RAN.

[0167]

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

[0168]

[0178] Example implementations are described in the following numbered clauses.

[0169]

[0179] Clause 1. A method of wireless communications implemented by a user equipment (UE), comprising: registering with a first network entity as a reference location device; and receiving positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit reception point (TRP) of at least one positioning frequency layer, wherein the positioning assistance data is dedicated for use by the UE registered as a reference location device.

[0170]

[0180] Clause 2. The method of clause 1, wherein the positioning assistance data includes an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0171]

[0181] Clause 3. A method according to any of clauses 1 to 2, wherein positioning assistance data is received from a second network entity in one or more positioning system information blocks (posSIBs), the one or more posSIBs being dedicated to transmitting positioning assistance data for UEs registered as reference location devices.

[0172]

[0182] Clause 4. The method of clause 3, further comprising decoding one or more posSIBs using information received from the first network entity while registering as a reference location device.

[0173]

[0183] Clause 5. The method according to any of clauses 3 to 4, wherein one or more posSIBs include prioritization of measurements performed based on positioning assistance data.

[0174]

[0184] Clause 6. The method of any of clauses 3 to 5, wherein the second network entity is a base station.

[0175]

[0185] Clause 7. A method as described in any of clauses 1 to 6, wherein the positioning assistance data includes an indication associated with each of the one or more PRS resources indicating that the one or more PRS resources are dedicated for use by a UE registered as a reference location device.

[0176]

[0186] Clause 8. A method as claimed in any of clauses 1 to 6, wherein the positioning assistance data includes an indication associated with each of the one or more PRS resources indicating whether the one or more PRS resources are dedicated for use by UEs registered as reference location devices, dedicated for use by UEs not registered as reference location devices, or dedicated for use by both UEs registered as reference location devices and UEs not registered as reference location devices.

[0177]

[0187] Clause 9. The method of any of clauses 1 to 7, wherein the positioning assistance data does not include an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0178]

[0188] Clause 10. A method according to any of clauses 1 to 8, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is dedicated for use by a UE registered as a reference location device.

[0179]

[0189] Clause 11. A method according to any of clauses 1 to 10, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more positioning frequency layers including a plurality of TRPs, including at least one TRP, one or more of the plurality of TRPs being dedicated for use by UEs registered as reference location devices.

[0180]

[0190] Clause 12. A method according to any of clauses 1 to 11, wherein the positioning assistance data indicates one or more TRPs, including at least one TRP that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more TRPs including a plurality of PRS resource sets, one or more of the plurality of PRS resource sets including at least one PRS resource set that is dedicated for use by UEs registered as reference location devices.

[0181]

[0191] Clause 13. The method of any one of clauses 1 to 12, wherein the first network entity is an AMF.

[0182]

[0192] Clause 14. The method of any one of clauses 1 to 12, wherein the first network entity is a location server.

[0183]

[0193] Clause 15. The method of any of clauses 1 to 5 and 7 to 14, wherein the second network entity is a location server and the positioning assistance data is received in one or more LPP messages.

[0184]

[0194] Clause 16. 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, wherein the at least one processor is configured to: register with a first network entity as a reference location device; and receive, via the at least one transceiver, positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit reception point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0185]

[0195] Clause 17. The UE of clause 16, wherein the positioning assistance data includes an indication that the positioning assistance data is dedicated for use by the UE registered as a reference location device.

[0186]

[0196] Clause 18. A UE as described in any of clauses 16 to 17, wherein positioning assistance data is received from a second network entity in one or more positioning system information blocks (posSIBs), one or more posSIBs being dedicated to transmitting positioning assistance data for UEs registered as reference location devices.

[0187]

[0197] Clause 19. The UE of clause 18, further configured by the at least one processor to decode one or more posSIBs using information received from the first network entity while registering as a reference location device.

[0188]

[0198] Clause 20. A UE as described in any of clauses 18 to 19, wherein one or more posSIBs include prioritization of measurements performed based on positioning assistance data.

[0189]

[0199] Clause 21. The UE according to any of clauses 18 to 20, wherein the second network entity is a base station.

[0190]

[0200] Clause 22. A UE as described in any of clauses 16 to 21, wherein the positioning assistance data includes an indication associated with each of one or more PRS resources indicating that the one or more PRS resources are dedicated for use by the UE registered as a reference location device.

[0191]

[0201] Clause 23. A UE as described in any of clauses 16 to 21, wherein the positioning assistance data includes an indication associated with each of one or more PRS resources indicating whether the one or more PRS resources are dedicated for use by UEs registered as reference location devices, dedicated for use by UEs not registered as reference location devices, or dedicated for use by both UEs registered as reference location devices and UEs not registered as reference location devices.

[0192]

[0202] Clause 24. A UE as claimed in any of clauses 16 to 22, wherein the positioning assistance data does not include an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0193]

[0203] Clause 25. A UE as described in any of clauses 16 to 23, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is dedicated for use by a UE registered as a reference location device.

[0194]

[0204] Clause 26. A UE as described in any of clauses 16 to 25, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more positioning frequency layers including a plurality of TRPs, including at least one TRP, one or more of the plurality of TRPs being dedicated for use by UEs registered as reference location devices.

[0195]

[0205] Clause 27. A UE as described in any of clauses 16 to 26, wherein the positioning assistance data indicates one or more TRPs, including at least one TRP that is common to UEs registered as reference location devices and UEs not registered as reference location devices, and the one or more TRPs include a plurality of PRS resource sets, including at least one PRS resource set, one or more of the plurality of PRS resource sets being dedicated for use by UEs registered as reference location devices.

[0196]

[0206] Clause 28. The UE according to any one of clauses 16 to 27, wherein the first network entity is an AMF.

[0197]

[0207] Clause 29. The UE according to any of clauses 16 to 28, wherein the first network entity is a location server.

[0198]

[0208] Clause 30. The UE of any of clauses 16 to 20 and 21 to 28, wherein the second network entity is a location server and the positioning assistance data is received in one or more LPP messages.

[0199]

[0209] Clause 31. A user equipment (UE), comprising: means for registering with a first network entity as a reference location device; and means for receiving positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit reception point (TRP) of at least one positioning frequency layer, wherein the positioning assistance data is dedicated for use by the UE registered as a reference location device.

[0200]

[0210] Clause 32. The UE of clause 31, wherein the positioning assistance data includes an indication that the positioning assistance data is dedicated for use by the UE registered as a reference location device.

[0201]

[0211] Clause 33. A UE as described in any of clauses 31 to 32, wherein positioning assistance data is received from a second network entity in one or more positioning system information blocks (posSIBs), one or more posSIBs being dedicated to transmitting positioning assistance data for UEs registered as reference location devices.

[0202]

[0212] Clause 34. The UE of clause 33, further comprising means for decoding one or more posSIBs using information received from the first network entity while registering as a reference location device.

[0203]

[0213] Clause 35. A UE according to any of clauses 33 to 34, wherein one or more posSIBs include prioritization of measurements performed based on positioning assistance data.

[0204]

[0214] Clause 36. The UE according to any of clauses 33 to 35, wherein the second network entity is a base station.

[0205]

[0215] Clause 37. A UE as described in any of clauses 31 to 36, wherein the positioning assistance data includes an indication associated with each of one or more PRS resources indicating that the one or more PRS resources are dedicated for use by the UE registered as a reference location device.

[0206]

[0216] Clause 38. A UE as described in any of clauses 31 to 36, wherein the positioning assistance data includes an indication associated with each of one or more PRS resources indicating whether the one or more PRS resources are dedicated for use by UEs registered as reference location devices, dedicated for use by UEs not registered as reference location devices, or dedicated for use by both UEs registered as reference location devices and UEs not registered as reference location devices.

[0207]

[0217] Clause 39. A UE as claimed in any of clauses 31 to 37, wherein the positioning assistance data does not include an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0208]

[0218] Clause 40. A UE as described in any of clauses 31 to 38, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is dedicated for use by the UE registered as a reference location device.

[0209]

[0219] Clause 41. A UE as described in any of clauses 31 to 40, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more positioning frequency layers including a plurality of TRPs, including at least one TRP, one or more of the plurality of TRPs being dedicated for use by UEs registered as reference location devices.

[0210]

[0220] Clause 42. A UE as described in any of clauses 31 to 41, wherein the positioning assistance data indicates one or more TRPs, including at least one TRP that is common to UEs registered as reference location devices and UEs not registered as reference location devices, and the one or more TRPs include a plurality of PRS resource sets, including at least one PRS resource set, one or more of the plurality of PRS resource sets being dedicated for use by UEs registered as reference location devices.

[0211]

[0221] Clause 43. The UE according to any of clauses 31 to 42, wherein the first network entity is an AMF.

[0212]

[0222] Clause 44. The UE according to any of clauses 31 to 42, wherein the first network entity is a location server.

[0213]

[0223] Clause 45. The UE of any of clauses 31 to 35 and 37 to 44, wherein the second network entity is a location server and the positioning assistance data is received in one or more LPP messages.

[0214]

[0224] Clause 46. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to register with a first network entity as a reference location device; and receive positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or more positioning reference signal (PRS) resources of at least one PRS resource set of at least one transmit reception point (TRP) of at least one positioning frequency layer, where the positioning assistance data is dedicated for use by the UE registered as the reference location device.

[0215]

[0225] Clause 47. The non-transitory computer-readable medium of clause 46, wherein the positioning assistance data includes an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0216]

[0226] Clause 48. A non-transitory computer-readable medium according to any of clauses 46 to 47, wherein the positioning assistance data is received from a second network entity in one or more positioning system information blocks (posSIBs), the one or more posSIBs being dedicated to transmitting positioning assistance data for UEs registered as reference location devices.

[0217]

[0227] Clause 49. The non-transitory computer-readable medium of clause 48, further comprising computer-executable instructions that, when executed by the UE, cause the UE to decode one or more posSIBs using information received from the first network entity while registering as a reference location device.

[0218]

[0228] Clause 50. A non-transitory computer-readable medium according to any of clauses 48 to 49, wherein one or more posSIBs include prioritization of measurements performed based on positioning assistance data.

[0219]

[0229] Clause 51. The non-transitory computer-readable medium of any of clauses 48 to 50, wherein the second network entity is a base station.

[0220]

[0230] Clause 52. A non-transitory computer-readable medium as described in any of clauses 46 to 51, wherein the positioning assistance data includes an indication associated with each of the one or more PRS resources indicating that the one or more PRS resources are dedicated for use by a UE registered as a reference location device.

[0221]

[0231] Clause 53. A non-transitory computer-readable medium as described in any of clauses 46 to 51, wherein the positioning assistance data includes an indication associated with each of the one or more PRS resources indicating whether the one or more PRS resources are dedicated for use by UEs registered as reference location devices, dedicated for use by UEs not registered as reference location devices, or dedicated for use by both UEs registered as reference location devices and UEs not registered as reference location devices.

[0222]

[0232] Clause 54. The non-transitory computer-readable medium of any of clauses 46 to 52, wherein the positioning assistance data does not include an indication that the positioning assistance data is dedicated for use by UEs registered as reference location devices.

[0223]

[0233] Clause 55. A non-transitory computer-readable medium according to any of clauses 46 to 53, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is dedicated for use by a UE registered as a reference location device.

[0224]

[0234] Clause 56. A non-transitory computer-readable medium according to any of clauses 46 to 55, wherein the positioning assistance data indicates one or more positioning frequency layers, including at least one positioning frequency layer that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more positioning frequency layers including a plurality of TRPs, including at least one TRP, one or more of the plurality of TRPs being dedicated for use by UEs registered as reference location devices.

[0225]

[0235] Clause 57. A non-transitory computer-readable medium according to any of clauses 46 to 56, wherein the positioning assistance data indicates one or more TRPs, including at least one TRP that is common to UEs registered as reference location devices and UEs not registered as reference location devices, the one or more TRPs including a plurality of PRS resource sets, one or more of the plurality of PRS resource sets including at least one PRS resource set that is dedicated for use by UEs registered as reference location devices.

[0226]

[0236] Clause 58. The non-transitory computer-readable medium of any of clauses 46 to 57, wherein the first network entity is an AMF.

[0227]

[0237] Clause 59. The non-transitory computer-readable medium of any of clauses 46 to 57, wherein the first network entity is a location server.

[0228]

[0238] Clause 60. The non-transitory computer-readable medium of any of clauses 46-50 and 52-59, wherein the second network entity is a location server and the positioning assistance data is received in one or more LPP messages.

[0229]

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

[0230]

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

[0231]

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

[0232]

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

[0233]

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

[0234]

[0244] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and / or actions of the method claims according to the aspects of the disclosure described herein 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

1. A method of wireless communication performed by a user equipment (UE), comprising: registering with a first network entity as a reference location device; receiving positioning assistance data from a second network entity for a positioning session between the UE and a location server, the positioning assistance data indicating at least one or a plurality of positioning reference signal (PRS) resources of at least one transmission and reception point (TRP) of at least one positioning frequency layer, wherein the positioning assistance data is dedicated for use by a UE registered as a reference location device; A method comprising the above steps.

2. The method according to claim 1, wherein the positioning assistance data includes an indication that the positioning assistance data is dedicated for use by a UE registered as a reference location device. The method according to claim 1.

3. The method according to claim 1, wherein the positioning assistance data is received from the second network entity in one or more positioning system information blocks (posSIBs), and the one or more posSIBs are dedicated to transmitting positioning assistance data for a UE registered as a reference location device. The method according to claim 1.

4. The method according to claim 3, further comprising decoding the one or more posSIBs using information received from the first network entity during registration as the reference location device. The method according to claim 3.

5. The method according to claim 3, wherein the one or more posSIBs include prioritization of measurements performed based on the positioning assistance data. The method according to claim 3.

6. The method according to claim 3, wherein the second network entity is a base station.

7. The positioning assistance data: indicates that the one or more PRS resources are dedicated for use by a UE registered as a reference location device, or indicating whether the one or more PRS resources are dedicated for use by a UE registered as a reference location device, dedicated for use by a UE not registered as a reference location device, or dedicated for use by both a UE registered as a reference location device and a UE not registered as a reference location device, including an indication associated with each of the one or more PRS resources, The method according to claim 1.

8. wherein the positioning assistance data, includes one or more positioning frequency layers that are dedicated for use by a UE registered as a reference location device, or, indicates one or more positioning frequency layers including the at least one positioning frequency layer that are common to a UE registered as a reference location device and a UE not registered as a reference location device, wherein the one or more positioning frequency layers include a plurality of TRPs, one or more of the plurality of TRPs including the at least one TRP are dedicated for use by a UE registered as a reference location device, The method according to claim 1.

9. indicating one or more TRPs including the at least one TRP that are common to a UE registered as a reference location device and a UE not registered as a reference location device, wherein the one or more TRPs include a plurality of PRS resource sets, one or more of the plurality of PRS resource sets including the at least one PRS resource set are dedicated for use by a UE registered as a reference location device, The method according to claim 1.

10. The method according to claim 1, wherein the first network entity is an access and mobility management function (AMF).

11. The method according to claim 1, wherein the first network entity is the location server.

12. wherein the second network entity is the location server, and the positioning assistance data is received in one or more LPP messages, The method according to claim 1.

13. a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver A user equipment (UE) comprising: wherein the at least one processor is configured to register with a first network entity as a reference location device; receive positioning assistance data from a second network entity for a positioning session between the UE and a location server via the at least one transceiver, wherein the positioning assistance data indicates at least one or a plurality of positioning reference signal (PRS) resources of at least one transmission and reception point (TRP) of at least one positioning frequency layer, and wherein the positioning assistance data is dedicated for use by a UE registered as a reference location device; A user equipment (UE) configured to perform the above.

14. The UE according to claim 13, further configured to execute the method according to any one of claims 2 to 12.

15. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to execute the method according to any one of claims 1 to 12.

Images