Switching location information types based on power saving considerations - Patents.com

Abstract

In one aspect, a user equipment (UE) receives a location information request from a network entity that configures the UE to report a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and transmits a location information response to the network entity that includes the location estimate or the location measurements of the UE based on power consumption metrics associated with reporting the UE's location estimate to the network entity and reporting the location measurements to the network entity.

Description

[Technical Field]

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

[0002] 2. Description of Related Technology Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS) and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), etc.

[0003]

[0003] The fifth-generation (5G) wireless standard, called New Radio (NR), enables higher data rates, more connections, and better coverage, among other improvements. According to the Next Generation Mobile Network Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and dense deployments for 5G, enable highly accurate 5G-based positioning. Summary of the Invention

[0004]

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

[0005]

[0005] In one aspect, a method of wireless communication performed by user equipment (UE) includes receiving a location information request from a network entity, configuring the UE to report a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and transmitting a location information response to the network entity including the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0006]

[0006] In one aspect, a user equipment (UE) comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive, via the at least one transceiver, a location information request from a network entity, the location information request including parameters that configure the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and to transmit, via the at least one transceiver, a location information response to the network entity, the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0007]

[0007] In one aspect, a user equipment (UE) includes means for receiving a location information request from a network entity including parameters for configuring the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and means for transmitting a location information response to the network entity including the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0008]

[0008] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to receive a location information request from a network entity including parameters that configure the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and send a location information response to the network entity including the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[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. [Brief explanation of the drawings]

[0010]

[0010] The accompanying drawings are presented to aid in the description of various aspects of the present disclosure and are provided solely for illustration of the aspects, not limitation thereof. [Figure 1]

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

[0012] 1 illustrates an exemplary wireless network structure according to aspects of the present disclosure. [Figure 2B] 1 illustrates an exemplary wireless network structure according to aspects of the present disclosure. [Figure 2C] 1 illustrates an exemplary wireless network structure according to an aspect of the present disclosure. 2 illustrates an exemplary wireless network structure according to an aspect 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 communication 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] 1 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the present disclosure. [Figure 5]

[0015] 1 illustrates an exemplary Long Term Evolution (LTE) positioning protocol (LPP) reference source for positioning. [Figure 6]

[0016] 1 illustrates an example Long Term Evolution (LTE) Positioning Protocol (LPP) capability transfer procedure, assistance data transfer procedure, and location information transfer procedure between a target device and a location server, according to an aspect of the present disclosure. [Figure 7]

[0017] 1 illustrates an example location service procedure according to an aspect of the present disclosure. [Figure 8]

[0018] 1 illustrates an example of a UE reporting location measurements despite being configured to report a location estimate, according to an aspect of the present disclosure. [Figure 9]

[0019] 1 illustrates an example of a UE reporting a location estimate despite being configured to report location measurements, according to an aspect of the present disclosure. [Figure 10]

[0020] 1 illustrates an exemplary method of wireless communication according to an aspect of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011]

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

[0012]

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

[0013]

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

[0014]

[0024] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that various actions described herein may be performed by specific circuitry (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein may be considered to be embodied entirely in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions, which, when executed, cause or direct an associated processor of a device to perform the functionality described herein. Accordingly, various aspects of the present disclosure may be embodied in several different forms, all of which are contemplated to be within the scope of the claimed subject matter. Additionally, for each aspect described herein, the corresponding form of any such aspect may be described herein as, for example, “logic configured to” perform the described actions.

[0015]

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

[0016]

[0026] A base station may operate according to one of several RATs with which it communicates with UEs depending on the network in which it is deployed and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), new radio (NR) Node B (also referred to as gNB or 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 only edge node signaling functionality, while in other systems, a base station may provide additional control and / or network management functions. The communication link over which a UE can send signals to a base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0017]

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

[0018]

[0028] In some implementations that support UE positioning, 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., if it transmits signals to the UE) and / or a location measurement unit (e.g., if it receives and measures signals from the UE).

[0019]

[0029] An "RF signal" includes electromagnetic waves of a given frequency that carry 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, due to the propagation characteristics of RF signals through multipath channels, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted over different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" when it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0020]

[0030] 1 illustrates an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one 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.

[0021]

[0031] 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 (5G core, 5GC)) through backhaul links 122 and to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server(s) 172 may be part of the core network 170 or may be external to the core network 170. The location server(s) 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 through 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), etc. 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., via the direct connection 128, as shown), with intervening nodes (if any) omitted from the signaling diagrams for clarity.

[0022]

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

[0023]

[0033] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In one aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resources referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish between 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" can refer to either or both of the logical communication entity and its supporting base station, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" can 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 a portion of the geographic coverage area 110.

[0024]

[0034] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions), and some of the geographic coverage areas 110 may substantially overlap with 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 substantially overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network including both small cell and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve limited groups known as closed subscriber groups (CSGs).

[0025]

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

[0026]

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

[0027]

[0037] The small cell base station 102' may operate in a licensed and / or unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may utilize LTE or NR technology and employ 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 extend coverage to and / or increase the 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 MultiFire.

[0028]

[0038] The wireless communication system 100 may further include an mmW base station 180 that may operate at millimeter wave (mmW) and / or sub-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has wavelengths from 1 millimeter to 10 millimeters. Radio waves within this band may be referred to as millimeter waves. Sub-mmW may fall down to frequencies of 3 GHz with wavelengths of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter waves. Communications using the mmW / sub-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. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Accordingly, it will be appreciated that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0029]

[0039] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and emits a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal (in terms of data rate) 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 one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are supplied to the individual antennas with the appropriate phase relationship so that radio waves from the separate antennas are combined to cancel and suppress radiation in undesired directions while increasing radiation in desired directions.

[0030]

[0040] 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 own transmit antenna is physically colocated. In NR, there are four types of quasi-colocation (QCL) relationships. Specifically, a given type of QCL relationship means that some parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, mean delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0031]

[0041] 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 antenna array in a particular direction to amplify (e.g., increase its gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in a particular direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is the highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of RF signals received from that direction.

[0032]

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

[0033]

[0043] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE forms a downlink beam, it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if a 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.

[0034]

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

[0035]

[0045] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as a frequency range designated FR3 (7.125 GHz to 24.25 GHz). Frequency bands included within FR3 may inherit FR1 and / or FR2 characteristics, thus effectively extending the characteristics of FR1 and / or FR2 to the mid-band frequencies. 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 ranges designated 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 is included within the EHF band.

[0036]

[0046] With the above aspects in mind, it should be understood that unless specifically stated otherwise, 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. Furthermore, unless specifically stated otherwise, it should be understood that terms such as "mmWave," as used herein, may broadly refer to frequencies that may include mid-band frequencies, may be within the ranges of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or may be within the EHF band.

[0037]

[0047] 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 "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and is the cell on which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured 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 among unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE-specific, the secondary carrier shall contain only the necessary signaling information and signals; e.g., there shall be no UE-specific signaling information and signals in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This may be done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier over which several base stations are communicating, terms such as "cell," "serving cell," "component carrier," and "carrier frequency" may be used interchangeably.

[0038]

[0048] 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 other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or data reception rates. For example, two 20 MHz carriers combined in a multi-carrier system would theoretically provide a 2x data rate increase (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0039]

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

[0040]

[0050] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) can communicate with the base station 102 via a communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., the UE 164, the UE 182) may also communicate directly with each other via a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). 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) medium sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-everything (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of a group of SL-UEs utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of the base station 102 or may in some cases be unable 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, where each SL-UE transmits to all other SL-UEs in the group. In some cases, the base station 102 facilitates scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between SL-UEs without the involvement of the base station 102.

[0041]

[0051] In one aspect, the sidelink 160 may operate over a target wireless communications medium, which may be shared with other vehicular and / or infrastructure access points, as well as other wireless communications between other RATs. The “medium” may consist of one or more time, frequency, and / or spatial 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 target medium may correspond to at least a portion of an unlicensed frequency band shared among various RATs. While different licensed frequency bands have been reserved for certain communications systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as “Wi-Fi.” Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and various variations thereof.

[0042]

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

[0043]

[0053] 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 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine the receiver's location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code with a set number of chips. While typically located within the SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers specifically designed to receive the signals 124 from the SV 112 to obtain geolocation information.

[0044]

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

[0045]

[0055] 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 referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network. This element then provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In this way, the UE 104 may receive communication signals (e.g., signal 124) from the SV 112 instead of, or in addition to, communication signals from the terrestrial base station 102.

[0046]

[0056] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, the UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., 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 (e.g., the UE 190 may indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

[0047]

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

[0048]

[0058] 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 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 UEs 204 that can connect to the location server 230 via the core network, the 5GC 210, and / or 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).

[0049]

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

[0050]

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

[0051]

[0061] 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, some control of policy enforcement and QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0052]

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

[0053]

[0063] Yet another optional aspect may include a third-party server 274 that 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 service (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 alternatively, each may correspond to a single server.

[0054]

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

[0055]

[0065] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. 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, and session management, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 typically 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 multiple 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 the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is 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 the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0056]

[0066] The deployment of a communication system, such as a 5G NR system, can be configured in multiple ways using various components or parts. In a 5G NR system or network, network equipment, such as a network node, network entity, network mobility element, RAN node, core network node, network element, or base station, or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), transmit / receive point (TRP), or cell) can be implemented as an aggregated base station (also known as a standalone base station or monolithic base station) or a disaggregated base station.

[0057]

[0067] A centralized base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU or alternatively geographically or virtually distributed throughout one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0058]

[0068] The operation of a base station type or network design may take into account the aggregation characteristics of base station functions. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functions across two or more units in different physical locations, as well as virtually distributing the functions of at least one unit, which may allow flexibility in network design. Various units of a disaggregated base station, or a disaggregated RAN architecture, may be configured for wired or wireless communication with at least one other unit.

[0059]

[0069] 2C illustrates an exemplary disaggregated base station architecture 250 according to an aspect of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link or indirectly with the core network 267 through one or more disaggregated base station units (e.g., a near-real time (RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a non-real time (non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) framework 255, or both). The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DU 228) via respective midhaul links, such as an F1 interface. The DU 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via respective fronthaul links. The RU 287 may communicate with each UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 may be served by multiple RUs 287 simultaneously.

[0060]

[0070] Each of the units, i.e., CU 280, DU 285, RU 287, and quasi-RT RIC 259, non-RT RIC 257, and SMO framework 255, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive signals from or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or transmit signals via a wireless transmission medium to one or more of the other units.

[0061]

[0071] In some aspects, the CU 280 can host one or more upper layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be executed using an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functions (i.e., Central Unit-User Plane (CU-UP)), control plane functions (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units may communicate bidirectionally with the CU-CP units via an interface, such as an E1 interface, when implemented in an O-RAN configuration. The CU 280 may be implemented to communicate with the DU 285, as needed, for network control and signaling.

[0062]

[0072] The DU 285 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional division such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 285 may further host one or more lower PHY layers. Each layer (or module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285 or with control functions hosted by the CU 280.

[0063]

[0073] Lower layer functions may be performed by one or more RUs 287. In some deployments, the RUs 287 controlled by the DUs 285 may correspond to logical nodes hosting RF processing functions, lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, the RU(s) 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU(s) 287 may be controlled by the corresponding DUs 285. In some scenarios, this configuration may enable the DU(s) 285 and CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0064]

[0074] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-cloud) 269) via a cloud computing platform interface (e.g., an O2 interface) to perform network element lifecycle management (e.g., instantiate virtualized network elements). Such virtualized network elements may include, but are not limited to, the CU 280, the DU 285, the RU 287, and the quasi-RT RIC 259. In some implementations, the SMO framework 255 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 261, via the O1 interface. Additionally, in some implementations, the SMO framework 255 can communicate directly with one or more RUs 287 via an O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of the SMO framework 255.

[0065]

[0075] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 259. The non-RT RIC 257 may be coupled to or in communication with the quasi-RT RIC 259 (e.g., via an A1 interface). The quasi-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources by data collection and action via interfaces (e.g., via an E2 interface) that connect one or more CUs 280, one or more DUs 285, or both, and the O-eNB to the quasi-RT RIC 259.

[0066]

[0076] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 259. Such information may be utilized by the quasi-RT RIC 259 or may be received from a non-network data source or from a network function in the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the quasi-RT RIC 259 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 257 may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO framework 255 (e.g., reconfiguration via O1) or through the creation of RAN management policies (e.g., A1 policies).

[0067]

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

[0068]

[0078] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, 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 to transmit and encode signals 318 and 358 (e.g., messages, instructions, information, etc.), respectively, and conversely, to receive and decode signals 318 and 358 (e.g., messages, instructions, information, pilots, etc.), respectively, in accordance with a designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, to transmit and encode signals 318 and 358, respectively, and include one or more receivers 312 and 352, respectively, to receive and decode signals 318 and 358, respectively.

[0069]

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

[0070]

[0080] UE 302 and base station 304 also, in at least some cases, include satellite signal receivers 330 and 370. 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 satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be global navigation satellite system (GNSS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC) signals, Quasi-Zenith Satellite System (QZSS) signals, GPS signals, etc. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and action from other systems as appropriate and, at least in some cases, perform calculations to determine the locations of UE 302 and base station 304, respectively, using the obtained measurements according to any suitable satellite positioning system algorithms.

[0071]

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

[0072]

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

[0073]

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

[0074]

[0084] The UE 302, base station 304, and network entity 306 also include other components that may be used in conjunction with operations as disclosed herein. The UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, e.g., to provide functionality related to wireless communications and to provide other processing functions. Accordingly, the processors 332, 384, and 394 may comprise processing means, such as determining means, calculating means, receiving means, transmitting means, and directing means. In one aspect, the processors 332, 384, and 394 may include, e.g., 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.

[0075]

[0085] 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 indicating reserved resources, thresholds, parameters, etc.). Thus, the memories 340, 386, and 396 may provide storage means, retrieval means, maintenance means, 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 modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. Figure 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 standalone component. FIG. 3B shows possible locations of a positioning component 388, which may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C illustrates possible locations of a positioning component 398, which may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0076]

[0086] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide a means of 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 micro-electrical mechanical systems (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. Furthermore, the sensor(s) 344 may include multiple different types of devices, and their outputs may be combined 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 position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0077]

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

[0078]

[0088] Referring more particularly to the one or more processors 384, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions associated with broadcasting system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding upper 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 associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0079]

[0089] The transmitter 354 and receiver 352 may implement Layer 1 (L1) functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, 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), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with the individual spatial streams for transmission.

[0080]

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

[0081]

[0091] 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.

[0082]

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

[0083]

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

[0084]

[0094] 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 via 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.

[0085]

[0095] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, 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 the core network. The one or more processors 384 are also responsible for error detection.

[0086]

[0096] 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 in accordance with various examples described herein. However, it will be understood that the illustrated components may have different functions in different designs. In particular, various components in 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 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), or may omit satellite signal receiver 370, etc. For brevity, examples of various alternative configurations are not provided herein but should be readily apparent to those skilled in the art.

[0087]

[0097] 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 one 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 embodied within the same device (e.g., gNB and location server functionality incorporated within the same base station 304), the data buses 334, 382, ​​and 392 may provide communication therebetween.

[0088]

[0098] The components of Figures 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of Figures 3A, 3B, and 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide its functionality. For example, some or all of the functionality represented by blocks 310-346 may be performed 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 performed 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). Additionally, some or all of the functionality represented by blocks 390-398 may be performed by 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, functions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it should be understood that such operations, functions, 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 processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0089]

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

[0090]

[0100] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink- and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. FIG. 4 illustrates examples of various positioning methods according to aspects of the present disclosure. In an OTDOA or DL-TDOA positioning procedure illustrated by scenario 410, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, referred to as reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives identifiers (IDs) 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 RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., the UE in the case of UE-based positioning or a location server in the case of UE-assisted positioning) can estimate the location of the UE.

[0091]

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

[0092]

[0102] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on an uplink reference signal (e.g., a sounding reference signal (SRS)) transmitted by the UE to multiple base stations. Specifically, the UE transmits one or more uplink reference signals that are measured by the reference base station and multiple non-reference base stations. Each base station then reports the reception time (referred to as the relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server), which knows the locations and relative timing of the participating base stations. Based on the reception-to-reception (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the UE's location using TDOA.

[0093]

[0103] 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.

[0094]

[0104] Downlink and uplink-based positioning methods include enhanced 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 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 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 referred to as the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurement may be performed or adjusted to include only the time difference between the nearest slot 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 measurement to the other entity, which then calculates the RTT. The distance between the two entities may be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning illustrated by scenario 430, a first entity (e.g., a UE or base station) conducts RTT positioning procedures with multiple second entities (e.g., multiple base stations or UEs) to allow the location of the first entity to be determined based on the distance to the second entities and the known locations of the second entities (e.g., using multilateration). As illustrated by scenario 440, RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0095]

[0105] 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 neighboring base stations. The UE's location is then estimated based on this information and the known location of the base station(s).

[0096]

[0106] To assist in positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include an identifier of the base station (or base station's cell / TRP) where the reference signal is to be measured, reference signal configuration parameters (e.g., the number of consecutive slots containing the PRS, the periodicity of the consecutive slots containing the PRS, the muting sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using the assistance data.

[0097]

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

[0098]

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

[0099]

[0109] In LTE and, at least in some cases, NR, positioning measurements (also referred to as location measurements) are reported through higher layer signaling, particularly the LTE Positioning Protocol (LPP) and / or RRC. LPP is used point-to-point between a location server (e.g., location server 230, LMF 270, SLP 272) and a UE (e.g., any of the UEs described herein) to position the UE using location-related measurements obtained from one or more reference sources. FIG. 5 is a diagram 500 illustrating exemplary LPP reference sources for positioning. In the example of FIG. 5, a target device, particularly a UE 504 (e.g., any of the UEs described herein), engages in an LPP session with a location server 530 (labeled as “E-SMLC / SLP” in the particular example of FIG. 5). The UE 504 is also receiving / measuring wireless positioning signals from a first reference source, particularly one or more base stations 502 (which may correspond to any of the base stations described herein and are labeled as "eNodeBs" in the particular example of FIG. 5), and a second reference source, particularly one or more SPS satellites 520 (which may correspond to SV112 in FIG. 1).

[0100]

[0110] LPP sessions are used between the location server 530 and the UE 504 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 Mobile-Terminated Location Request (MT-LR), Mobile-Originated Location Request (MO-LR), or Network-Induced Location Request (NI-LR)). Multiple LPP sessions may be used between the same endpoints to support multiple different location requests. Each LPP session comprises one or more LPP transactions, each performing a single operation (e.g., capability exchange, assistance data transfer, location information transfer). LPP transactions are called LPP procedures. The initiator of an LPP session initiates the first LPP transaction, but subsequent transactions can be initiated by either endpoint. LPP transactions within a session may occur serially or in parallel. LPP transactions are indicated at the LPP protocol level using transaction identifiers to associate messages (e.g., requests and responses) with each other. Messages within a transaction are linked by a common transaction identifier.

[0101]

[0111] 3GPP LPP specifies LPP positioning methods and associated signaling content. LPP signaling can be used to request and report measurements related to the following positioning methods: Observed Time Difference of Arrival (OTDOA), Downlink Time Difference of Arrival (DL-TDOA), Aided Global Navigation Satellite System (A-GNSS), LTE Enhanced Cell Identity (E-CID), NR E-CID, Sensor, Terrestrial Beacon System (TBS), WLAN, Bluetooth, Downlink Angle of Departure (DL-AoD), Uplink Angle of Arrival (UL-AoA), and Multiple Round Trip Time (RTT). Currently, an LPP measurement report may include the following measurements: (1) one or more Time of Arrival (ToA), Time Difference of Arrival (TDOA), Reference Signal Time Difference (RSTD), or Receive-Transmit (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 location server 530); (3) one or more multipath measurements (ToA, Reference Signal Received Power (RSRP), AoA / AoD per path); (4) one or more motion states (e.g., walking, driving, etc.) and trajectory (currently only for UE 504); and (5) one or more reporting quality indications. In this disclosure, positioning measurements such as the example measurements just listed, regardless of positioning technology, may be collectively referred to as Positioning State Information (PSI).

[0102]

[0112] The UE 504 and / or location server 530 may derive location information from one or more reference sources, shown in the example of FIG. 5 as SPS satellite(s) 520 and base station(s) 502. Each reference source may be used to calculate an independent estimate of the UE 504 location using an associated positioning technique. In the example of FIG. 5, the UE 504 measures characteristics (e.g., ToA, RSRP, RSTD, etc.) of positioning signals received from base station(s) 502 using one or more cellular network-based positioning methods (e.g., multi-RTT, OTDOA, DL-TDOA, DL-AoD, E-CID, etc.) to calculate, or to assist the location server 530 in calculating, an estimate of the UE 504's location. Similarly, the UE 504 measures characteristics (e.g., ToA) of GNSS signals received from SPS satellites 520 to triangulate its location in two or three dimensions, depending on the number of SPS satellites 520 measured. In some cases, the UE 504 or location server 530 may combine location solutions derived from each of the different positioning techniques to improve the accuracy of the final location estimate.

[0103]

[0113] As mentioned above, the UE 504 uses LPP to report location-related measurements obtained from different reference sources (e.g., base stations 502, Bluetooth beacons, SPS satellites 520, WLAN access points, motion sensors, etc.). As an example, in the case of GNSS-based positioning, the UE 504 uses the LPP information element (IE) “A-GNSS-ProvideLocationInformation” to provide location measurements (e.g., pseudo-ranges, location estimates, velocity, etc.) along with time information to the location server 530. It can also be used to provide GNSS positioning-specific error reasons. The “A-GNSS-ProvideLocationInformation” IE includes IEs such as “GNSS-SignalMeasurementInformation,” “GNSS-LocationInformation,” “GNSS-MeasurementList,” and “GNSS-Error.” The UE 504 includes the “GNSS-LocationInformation” IE when it provides location and optionally velocity information derived using GNSS or hybrid GNSS and other measurements to the location server 530. The UE 504 uses the "GNSS-SignalMeasurementInformation" IE to provide GNSS signal measurement information to the location server 530 and to provide GNSS-network time association if requested by the location server 530. This information includes measurements of code phase, Doppler, C / No, and optionally accumulated carrier phase, also called accumulated delta range (ADR), which enables a UE-assisted GNSS method in which location is calculated in the location server 530. The UE 504 uses the "GNSS-MeasurementList" IE to provide measurements of code phase, Doppler, C / No, and optionally accumulated carrier phase (or ADR).

[0104]

[0114] As another example, for motion sensor-based positioning, a currently supported positioning method uses barometric pressure sensors and motion sensors, as described in 3GPP TS36.305 (published and incorporated herein by reference in its entirety). The UE 504 uses the LPP IE "Sensor-ProvideLocationInformation" to provide location information for sensor-based methods to the location server 530. It may also be used to provide sensor-specific error reasons. The UE 504 uses the "Sensor-MeasurementInformation" IE to provide sensor measurements (e.g., barometric pressure readings) to the location server 530. The UE 504 uses the "Sensor-MotionInformation" IE to provide motion information to the location server 530. The motion information may comprise an ordered series of points. This information may be obtained by the UE 504 using one or more motion sensors (e.g., accelerometer, barometer, magnetometer, etc.).

[0105]

[0115] As yet another example, in the case of Bluetooth-based positioning, the UE 504 uses the "BT-ProvideLocationInformation" IE to provide measurements of one or more Bluetooth beacons to the location server 530. This IE may also be used to provide Bluetooth positioning-specific error reasons.

[0106]

[0116] An LPP session generally includes at least a capability transfer or instruction procedure, an assistance data transfer or distribution procedure, and a location information transfer or distribution procedure. Figure 6 shows exemplary LPP capability transfer procedure 610, LPP assistance data transfer procedure 630, and LPP location information transfer procedure 650 between a target device (labeled "target") and a location server (labeled "server") according to aspects of the present disclosure.

[0107]

[0117] The purpose of the LPP Capability Transfer procedure 610 is to enable the transfer of capabilities from a target device (e.g., UE 204) to a location server (e.g., LMF 270). Capabilities in this context refer to positioning capabilities and protocol capabilities related to LPP and the positioning methods supported by LPP. In the LPP Capability Transfer procedure 610, the location server (e.g., LMF 270) indicates the types of capabilities required from the target device (e.g., UE 204) in an LPP Request Capabilities message. The target device responds with an LPP Offer Capabilities message. The capabilities included in the LPP Offer Capabilities message must correspond to any capability types specified in the LPP Request Capabilities message. Specifically, for each positioning method for which a capability request is included in the LPP Request Capabilities message, if the target device supports this positioning method, the target device includes its capabilities for that supported positioning method in the LPP Offer Capabilities message. In the case of the LPP Capability Indication procedure, the target device offers unrequested capabilities (i.e., for which it has not received an LPP Request Capabilities message) to the location server in the LPP Offer Capabilities message.

[0108]

[0118] The purpose of the LPP Assistance Data Forwarding procedure 630 is to allow a target device to request assistance data from a location server to assist positioning and for the location server to forward the assistance data to the target device in the absence of a request. In the LPP Assistance Data Forwarding procedure 630, the target device sends an LPP Request Assistance Data message to the location server. The location server responds to the target device with an LPP Provide Assistance Data message containing the assistance data. The forwarded assistance data must match or be a subset of the assistance data requested in the LPP Request Assistance Data. The location server may also provide any unsolicited information that the server deems useful to the target device. The location server may also send one or more additional LPP Provide Assistance Data messages containing further assistance data to the target device. In the LPP Assistance Data Delivery procedure, the location server provides unsolicited assistance data necessary for positioning. Assistance data may be provided periodically or aperiodically.

[0109]

[0119] The purpose of the LPP Location Information Transfer procedure 650 is to allow a location server to request location measurement data and / or a location estimate from a target device and for the target device to forward the location measurement data and / or a location estimate to the location server in the absence of a request. In the LPP Location Information Transfer procedure 650, the location server sends an LPP Request Location Information message to the target device to request location information, indicating the type of location information required and, in some cases, the associated QoS. The target device responds to the location server with an LPP Offer Location Information message to transfer the location information. The transferred location information must match or be a subset of the location information requested by the LPP Request Location Information message, unless the location server explicitly allows additional location information. More specifically, if the requested information is compatible with the capabilities and configuration of the target device, the target device includes the requested information in the LPP Offer Location Information message. Otherwise, if the target device does not support one or more of the requested positioning methods, the target device continues to process the message as if it contained information only for supported positioning methods and handles the signaling content of unsupported positioning methods with LPP error detection. If requested by the LPP Request Locating Information message, the target device sends additional LPP Provide Location Information messages to the location server to transfer additional location information. The LPP Location Information Delivery procedure supports the delivery of positioning estimates based on unsolicited services.

[0110]

[0120] The LPP also defines procedures related to error indication when a receiving endpoint (target device or location server) receives erroneous or unexpected data or detects that some data is missing. Specifically, if a receiving endpoint determines that a received LPP message contains an error, the receiving endpoint may return an error message indicating one or more errors to the sending endpoint and discard the received / erroneous message. If a receiving endpoint can determine that an erroneous LPP message is an LPP error or abort message, the receiving endpoint discards the received message without returning an error message to the sending endpoint.

[0111]

[0121] The LPP also defines procedures related to abort indications to allow a target device or location server to abort an ongoing procedure due to some unexpected event (e.g., cancellation of a location request by an LCS client). The abort procedure can also be used to stop an ongoing procedure (e.g., periodic location reporting from a target device). In the abort procedure, a first endpoint determines that procedure P must be aborted and sends an abort message carrying the transaction ID of procedure P to a second endpoint. The second endpoint then aborts procedure P.

[0112]

[0122] 7 illustrates an example location services procedure 700 according to an aspect of the present disclosure. The location services procedure 700 may be performed by the UE 204, an NG-RAN node 702 in the NG-RAN 220 (e.g., a gNB 222, a gNB-CU 226, an ng-eNB 224, or other node in the NG-RAN 220), the AMF 264, the LMF 270, and a 5GC location services (LCS) entity 780 (e.g., any third-party application requesting the location of the UE 204, a public service access point (PSAP), an E-911 server, etc.).

[0113]

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

[0114]

[0124] Upon receiving (or generating) the location service request, the AMF 264 forwards the location service request to the LMF 270 in step 720. The LMF 270 then performs an NG-RAN positioning procedure with the NG-RAN node 702 in step 730a and a UE positioning procedure with the UE 204 in step 730b. The specific NG-RAN positioning procedure and UE positioning procedure may depend on the type(s) of positioning method(s) used to determine the location of the UE 204, which may depend on the capabilities of the UE 204. The positioning method(s) may be downlink-based (e.g., LTE-OTDOA, DL-TDOA, DL-AoD, etc.), uplink-based (e.g., UL-TDOA, UL-AoA, etc.), and / or downlink- and uplink-based (e.g., LTE / NR E-CID, multi-RTT, etc.).

[0115]

[0125] A prerequisite for step 730 is that an LCS correlation identifier (ID) and an AMF ID have been passed to the LMF 270 by the serving AMF 264. Both the LCS correlation ID and the AMF ID may be represented as strings selected by the AMF 264. The LCS correlation ID and the AMF ID are provided to the LMF 270 by the AMF 264 during the location service request in step 720. Then, when the LMF 270 triggers step 730, the LMF 270 also includes the LCS correlation ID for this location session along with the AMF ID indicating the AMF instance serving the UE 204. The LCS correlation ID is used during a positioning session between the LMF 270 and the UE 204 to ensure that 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 ID) that can be recognized by the LMF 270.

[0116]

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

[0117]

[0127] As part of the NG-RAN node positioning procedure (step 730a) and the UE positioning procedure (step 730b), the LMF 270 may provide LPP assistance data in the form of downlink positioning reference signal (DL-PRS) configuration information for the selected positioning method(s) to the NG-RAN node 702 and the UE 204. Alternatively or additionally, the NG-RAN node 702 may provide DL-PRS and / or uplink PRS (UL-PRS) configuration information for the selected positioning method(s) to the UE 204. It should be noted that although Figure 7 shows a single NG-RAN node 702, there may be multiple NG-RAN nodes 702 involved in a positioning session.

[0118]

[0128] When configured in a DL-PRS configuration and / or a UL-PRS configuration, the NG-RAN node 702 and the UE 204 transmit and receive / measure their respective PRSs at scheduled times. The NG-RAN node 702 and the UE 204 then transmit their respective measurements to the LMF 270. In some cases, the NG-RAN node 702 may transmit its measurements to the UE 204, which may forward them to the LMF 270 using LPP signaling. Alternatively, the NG-RAN node 702 may transmit its measurements directly to the LMF 270 over LPP type A (LPPa) or New Radio positioning protocol type A (NRPPPa) signaling. In some cases, the UE 204 may transmit its measurements to the NG-RAN node 702 during RRC, uplink control information (UCI), or MAC control element (MAC-CE) signaling, and the NG-RAN node 702 may forward the measurements to the LMF 270 using LPPa or NRPPa signaling. Alternatively, the UE 204 may send its measurements directly to the LMF 270 using LPP signaling.

[0119]

[0129] Once the LMF 270 obtains measurements from the UE 204 and / or the NG-RAN node 702 (depending on the type(s) of positioning method(s)), it uses these measurements to calculate an estimate of the location of the UE 204. Then, in step 740, the LMF 270 sends a location service response to the AMF 264 that includes the location estimate for the UE 204. The AMF 264 then forwards the location service response to the entity that generated the location service request in step 750. Specifically, if in step 710a, the location service request was received from the 5GC LCS entity 780, then in step 750a, the AMF 264 sends the location service response to the 5GC LCS entity 780. However, if in step 710c, the location service request was received from the UE 204, then in step 750c, the AMF 264 sends the location service response to the UE 204. Alternatively, if the AMF 264 generated a location service request in step 710b, then in step 750b the AMF 264 stores / uses the location service response itself.

[0120]

[0130] Note that while the location service procedure 700 is described above as a UE-assisted location service procedure, it may instead be a UE-based positioning procedure. A UE-assisted location service procedure is one in which the LMF 270 calculates the location of the UE 204, while a UE-based location service procedure is one in which the UE 204 calculates its own location. For a UE-based location service procedure, steps 710c and 750c are performed. The LMF 270 may still coordinate DL-PRS (and possibly UL-PRS) transmissions / measurements, but the measurements are forwarded to the UE 204 rather than the LMF 270. Thus, the location service response in steps 740 and 750c may be measurements from the involved NG-RAN node(s) 702 rather than a location estimate for the UE 204. Alternatively, if the involved NG-RAN node(s) 702 forward their respective measurements directly to the UE 204 (e.g., via RRC signaling), the location service response in stage 740 may simply be a confirmation that the NG-RAN node and UE positioning procedure in stage 730 is complete.

[0121]

[0131] Release 16 of the 3GPP standard covers techniques for high-precision positioning, including wide bandwidth, FR2 beam sweeping, angle-based methods and reporting, and multi-cell RTT. However, Release 16 does not focus on latency. UE-based positioning (downlink-based positioning methods are agreed upon in Release 16) reduces latency, and for UE-assisted positioning, "LMF in the RAN" reduces latency, although this aspect has not yet been agreed upon. Additionally, in Release 16, all reporting is via LPP and / or RRC signaling, using mechanisms similar to LTE. There is no specific "low latency" reporting.

[0122]

[0132] Low latency positioning is a target for positioning techniques in Release 17 of the 3GPP standard. For example, Release 17 has a latency target of less than 100 ms, and some Industrial IoT (IoT) cases have a latency target of less than 10 ms. These latency targets motivate L1 / L2 reporting for lower latency. For example, on-demand positioning using special PRACH sequences has been introduced. Note that L1 / L2 reporting reduces the latency between the UE and the base station. The latency between the base station and the location server can be addressed by the "LMF in RAN" aspect.

[0123]

[0133] Whether the UE implements a UE-assisted or UE-based positioning method is indicated by the information element (IE) "LocationInformationType" (e.g., included in the LPP Location Information Request message). This IE indicates whether the location server requires a location estimate (UE-based positioning) or positioning measurements (UE-assisted positioning) in the LPP Provide Location Information message. The "LocationInformationType" IE can have the values ​​"locationEstimateRequired", "locationMeasurementsRequired", "locationEstimatePreferred", or "locationMeasurementsPreferred". For the value "locationEstimateRequired", the target device (UE) shall return a location estimate (e.g., in the LPP Provide Location Information message) if possible, or indicate a location error if not. For the value "locationMeasurementsRequired", the target device shall return positioning measurements (e.g., in the LPP Provide Location Information message) if possible, or indicate a location error if not. For the value "locationEstimatePreferred", the target device will return a location estimate if possible, but may additionally or instead return measurements for any requested positioning methods for which location estimates are not possible. For the value "locationMeasurementsPreferred", the target device will return location measurements if possible, but may additionally or instead return location estimates for any requested positioning methods for which location measurements are not possible.

[0124]

[0134] In the UE-assisted positioning method, the location server and base station schedule assistance data (e.g., in an LPP Provide Assistance Data message) and measurement requests (e.g., in an LPP Request Location Information message), the UE performs measurements and reports the measurements (e.g., in an LPP Provide Location Information message) to the location server, which then calculates a position fix. The location server may provide / forward the position fix to the UE. The location server can run high-performance and computational algorithms, and therefore the fix is ​​of high quality. However, this results in longer end-to-end latency.

[0125]

[0135] In the UE-based positioning method, the location server and base station schedule assistance data (e.g., in an LPP Provide Assistance Data message) and measurement requests (e.g., in an LPP Request Location Information message), and the UE performs measurements and calculates a position fix. The UE has limited resources in terms of power and computation to calculate the fix, and therefore the fix will be of lower quality compared to a fix calculated by the location server. However, this method reduces end-to-end latency.

[0126]

[0136] From the above, it can be seen that the UE-assisted positioning method can provide better positioning fixes and the UE-based positioning method can provide better latency. From the operator / carrier's point of view, the UE-assisted positioning method is preferred because this type of method generates more revenue since the UE is forced to use the services of a location server.

[0127]

[0137] In addition to reducing latency, there is a need to reduce the power consumption of the target device while maintaining high accuracy. Techniques for achieving these goals are called low-power high-accuracy positioning (LPHAP) techniques. To identify the performance gap, the following model and parameter values ​​for conversion between relative power units and battery life have been studied. In the following equations, battery life is used as the metric for determining the gap.

[0128]

number

[0129]

[0138] In the following equation, relative power units are used as the metric for determining the gap.

[0130]

number

[0131]

[0139] In the above formula, C1 is the battery capacity of the reference device, C2 is the battery capacity of the LPHAP device, T1 is the battery life of the reference device, T2 is the battery life of the LPHAP device, and T2 req is the target battery life of the LPHAP device, P1 is the relative power unit obtained based on the reference traffic type, P2 is the estimated relative power unit of the LPHAP device, and P2 req is the target relative power unit for the LPHAP device, and X is the percentage of power consumed by the reference traffic type. As an example, C1 may be equal to 4500 milliamp hours (mAh), T1 may be equal to 10 hours, X may be equal to 20%, C2 may be equal to 800 mAh, and T2 req may be equal to 12 months, and the reference traffic type may be File Transfer Protocol (FTP).

[0132]

[0140] Continuing with the consideration of LPHAP, for downlink positioning, the following power components and parameter values ​​are considered for the baseline evaluation of Release 17 RRC inactive state positioning: For UE-assisted downlink positioning, the power components and parameter values ​​may be: (1) SSB processing with a 2 ms duration and a periodicity of an idle discontinuous reception (I-DRX) cycle; (2) paging with a 2 ms duration, a periodicity of an I-DRX cycle, and a group paging rate of 10%; (3) DL-PRS measurement with a 0.5 ms duration; (4) configured grant small data transmission (CG-SDT) with a 1 ms duration and a periodicity of the positioning interval (RRC release after CG-SDT may optionally be included, e.g., with a 1 ms duration); (5) bandwidth part (BWP) stitching with, e.g., a 1 ms duration; (6) intra-frequency / inter-frequency RRM measurements in low SINR conditions with, e.g., a 1 ms duration; or (7) random access SDT when CG-SDT is not available. SDT, RA-SDT) (e.g., including CORESET0+SIB1, PRACH, Random Access Response (RAR), Msg3 / 4 / 5). Note that options (5), (6), and (7) are optional. Furthermore, the power components and parameter values ​​for UE-assisted downlink positioning are also applicable to the downlink part of UE-assisted downlink and uplink-based positioning.

[0133]

[0141] For UE-based downlink positioning, the power components and parameter values ​​include: (1) SSB processing with 2 ms duration and periodicity of the I-DRX cycle, (2) paging with 2 ms duration, periodicity of the I-DRX cycle, and a group paging rate of 10%, (3) DL-PRS measurement with 0.5 ms duration, (4) BWP stitching with, for example, 1 ms duration, or (5) intra-frequency / inter-frequency RRM measurement in low SINR conditions with, for example, 1 ms duration. Note that options (4) and (5) are optional.

[0134]

[0142] This disclosure provides techniques for switching location information types (e.g., indicated by a "LocationInformationType" IE) based on power saving considerations. For each positioning instance (e.g., each LPP location information transfer procedure 650 within a positioning session, LPP session, location service procedure 700, etc.), the UE determines whether to perform UE-based or UE-assisted positioning by evaluating the expected power consumption. The UE determines the expected power consumption for UE-assisted positioning (denoted "PC-UEA") as the measurement power consumption (denoted "MPC-UEA") plus the measurement report power consumption (denoted "MRPC-UEA"). The UE determines the expected power consumption for UE-based positioning (denoted "PC-UEB") as the measurement power consumption (denoted "MPC-UEB") + the positioning calculation power consumption (denoted "PPC-UEB") + the location report power consumption (denoted "MRPC-UEB").

[0135]

[0143] The values ​​of MRPC-UEA and MRPC-UEB may depend on the size of the report (e.g., number of measurements), with a general expectation that MRPC-UEB will be much less than MRPC-UEA. Depending on whether the UE is in network acquisition mode or tracking mode, MRPC-UEA may be approximately equal to or higher than MRPC-UEB. Different positioning engine modes may result in different PPC-UEB. To determine which positioning engine mode to use, the UE may consider factors such as mobility, completeness, history of positioning estimates, accuracy requirements, and / or latency requirements associated with the location request.

[0136]

[0144] If the UE is configured with "locationEstimatePreferred" or "locationMeasurementsPreferred," the UE may return location measurements (i.e., positioning measurements) or location estimates based on the power consumption metrics PC-UEA and PC-UEB described above. If the UE is configured with "locationEstimatePreferred," the UE may return location measurements if the power consumption for reporting location measurements (PC-UEA) is less than the power consumption for reporting location estimates (PC-UEB) by some non-zero threshold (denoted "T1"). If the UE is configured with "locationMeasurementsPreferred," the UE may return a location estimate if the power consumption for reporting location estimates (PC-UEB) is less than the power consumption for reporting location measurements (PC-UEA) by some non-zero threshold (denoted "T2").

[0137]

[0145] 8 is a diagram 800 illustrating an example of a UE reporting location measurements despite being configured to report a location estimate, according to an aspect of the disclosure. As shown in FIG. 8, the power consumption for reporting location measurements (represented by the block labeled "PC-UEA") is less than the power consumption for reporting a location estimate (represented by the block labeled "PC-UEB") by more than some threshold T1. Thus, even though the UE is configured to report a location estimate (e.g., by receiving a "LocationInformationType" IE with a value of "locationEstimatePreferred"), the UE reports location measurements.

[0138]

[0146] 9 is a diagram 900 illustrating an example of a UE reporting a location estimate despite being configured to report location measurements, according to an aspect of the disclosure. As shown in FIG. 9, the power consumption for reporting a location estimate (represented by the block labeled "PC-UEB") is less than the power consumption for reporting location measurements (represented by the block labeled "PC-UEA") by more than some threshold T2. Thus, even though the UE is configured to report location measurements (e.g., by receiving a "LocationInformationType" IE with a value of "locationMeasurementsPreferred"), the UE reports a location estimate.

[0139]

[0147] In one aspect, the location server (e.g., LMF 270) can switch power consumption key performance indicators (KPIs) on or off, or request "low" or "high" power consumption, so that the UE can make a corresponding decision when a "preferred" location mode is configured.

[0140]

[0148] In one aspect, the update / switch between UE-based and UE-assisted for the positioning procedure may be determined at each measurement reporting instance (e.g., for each LPP location information transfer procedure 650), or may be updated periodically / periodically (e.g., after "X" reporting instances), or may be reconsidered based on certain trigger events. The trigger events for reevaluating the UE-based / UE-assisted decision may include (1) a change in the UE's RRC state (a change in the RRC state may change MPC-UEA, MPC-UEB, MRPC-UEA, and / or MRPC-UEB), (2) a change in the serving cell RSRP and / or SINR, (3) a significant change (e.g., above some threshold) in the size of the measurement report, (4) a change in the assistance data, and / or (5) a change in the UE's DRX configuration.

[0141]

[0149] 10 illustrates an example method 1000 of wireless communication according to an aspect of the present disclosure. In one aspect, the method 1000 may be performed by a UE (e.g., any of the UEs described herein).

[0142]

[0150] At 1010, the UE receives a location information request from a network entity (e.g., LMF 270) that configures the UE to report a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE. In one aspect, operation 1010 may be performed by one or more WWAN transceivers 310, one or more processors 332, memories 340, and / or positioning components 342, any or all of which may be considered a means for performing this operation.

[0143]

[0151] At 1020, the UE transmits a location information response to the network entity that includes the location estimate or the location measurements of the UE based on a power consumption metric associated with reporting the UE's location estimate to the network entity and reporting the location measurements to the network entity. In one aspect, operation 1020 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.

[0144]

[0152] As can be appreciated, a technical advantage of method 1000 is improved power conservation for positioning operations.

[0145]

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

[0146]

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

[0147]

[0155] Clause 1. A method of wireless communications implemented by a user equipment (UE), comprising: receiving a location information request from a network entity comprising parameters for configuring the UE to report a preferred type of location information comprising a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE; and transmitting a location information response to the network entity comprising the location estimate or location measurements of the UE based on a power consumption metric associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0148]

[0156] Clause 2. The method of clause 1, wherein the power consumption metric comprises a comparison of a difference between the estimated power consumption reporting the location measurement and the estimated power consumption reporting the location estimate of the UE to a threshold value.

[0149]

[0157] Clause 3. The method of clause 2, wherein the estimated power consumption for reporting location measurements is based on the estimated power consumption for obtaining location measurements and the estimated power consumption for transmitting the location measurements in a location information response, and the estimated power consumption for reporting a location estimate of the UE is based on the estimated power consumption for obtaining location measurements, the estimated power consumption for determining a location estimate of the UE, and the estimated power consumption for transmitting the location estimate of the UE in a location information response.

[0150]

[0158] Clause 4. The method of clause 3, wherein the estimated power consumption for transmitting location measurements in a location information response is based on the number of location measurements.

[0151]

[0159] Clause 5. The method of clause 4, wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

[0152]

[0160] Clause 6. The method of any of clauses 3 to 5, wherein the estimated power consumption for determining a location estimate for the UE is based on a positioning engine mode used to determine the location estimate for the UE.

[0153]

[0161] Clause 7. The method of clause 6, wherein the positioning engine mode used to determine the location estimate for the UE is based on mobility, completeness, history of positioning estimates, accuracy requirements, latency requirements, or any combination thereof, associated with the location information request.

[0154]

[0162] Clause 8. The method of any of clauses 1 to 7, wherein a first value of the parameter indicates that a location estimate of the UE is the preferred type of location information, and a second value of the parameter indicates that a location measurement is the preferred type of location information.

[0155]

[0163] Clause 9. The method of clause 8, wherein the parameter includes a "LocationInformationType" information element, a first value of the parameter includes a "locationEstimatePreferred" value of the "LocationInformationType" information element, and a second value of the parameter includes a "locationMeasurementsPreferred" value of the "LocationInformationType" information element.

[0156]

[0164] Clause 10. The method of any of clauses 1 to 9, further comprising receiving an indication that the UE is expected to take power consumption into account when responding to the location information request, wherein the location information response includes a location estimate or location measurement value of the UE based on the indication that the UE is expected to take power consumption into account when responding to the location information request.

[0157]

[0165] Clause 11. The method of clause 10, wherein the instruction includes an instruction that a power consumption key performance indicator (KPI) of the UE is turned on or an instruction that the UE is expected to use low power consumption when responding to a location information request.

[0158]

[0166] Clause 12. The method of any of clauses 1 to 11, further comprising determining whether to report a location estimate or location measurements of the UE in a location information response.

[0159]

[0167] Clause 13. The method of clause 12, wherein the determination of whether to report a location estimate or location measurements of the UE in the location information response is performed in response to receiving a location information request, periodically, in response to a trigger event, or any combination thereof.

[0160]

[0168] Clause 14. The method of clause 13, wherein the trigger event comprises a change in the radio resource control (RRC) state of the UE, a change in the serving cell reference signal received power (RSRP), a change in the serving cell signal-to-interference-and-noise ratio (SINR), a change in the size of the location information response, a change in assistance data for a positioning session associated with the location information request, or a change in the discontinuous reception (DRX) configuration of the UE.

[0161]

[0169] Clause 15. The method of any of clauses 1 to 14, wherein the parameters configure the UE to report a location estimate of the UE, and the location information response includes a location measurement instead of the location estimate of the UE based on a power consumption metric.

[0162]

[0170] Clause 16. The method of any of clauses 1 to 14, wherein the parameters configure the UE to report location measurements, and the location information response includes a location estimate of the UE based on a power consumption metric instead of the location measurements.

[0163]

[0171] Clause 17. The method of any of clauses 1 to 16, wherein the network entity is a location server, the location information request comprises a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message, and the location information response comprises an LPP Provide Location Information message.

[0164]

[0172] Clause 18. 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: receive, via the at least one transceiver, a location information request from a network entity, the location information request including parameters for configuring the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE; and transmit, via the at least one transceiver, a location information response to the network entity, the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0165]

[0173] Clause 19. The UE of clause 18, wherein the power consumption metric comprises a comparison of a difference between an estimated power consumption reporting a location measurement and an estimated power consumption reporting a location estimate of the UE to a threshold value.

[0166]

[0174] Clause 20. A UE as described in clause 19, wherein the estimated power consumption for reporting location measurements is based on the estimated power consumption for obtaining location measurements and the estimated power consumption for transmitting the location measurements in a location information response, and wherein the estimated power consumption for reporting a location estimate of the UE is based on the estimated power consumption for obtaining location measurements, the estimated power consumption for determining a location estimate of the UE, and the estimated power consumption for transmitting a location estimate of the UE in a location information response.

[0167]

[0175] Clause 21. The UE of clause 20, wherein the estimated power consumption for transmitting location measurements in a location information response is based on the number of location measurements.

[0168]

[0176] Clause 22. The UE of clause 21, wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

[0169]

[0177] Clause 23. The UE of any of clauses 20 to 22, wherein the estimated power consumption for determining a location estimate for the UE is based on a positioning engine mode used to determine a location estimate for the UE.

[0170]

[0178] Clause 24. The UE of clause 23, wherein the positioning engine mode used to determine the location estimate for the UE is based on mobility, completeness, positioning estimate history, accuracy requirements, latency requirements, or any combination thereof, associated with the location information request.

[0171]

[0179] Clause 25. A UE as described in any of clauses 18 to 24, wherein a first value of the parameter indicates that a location estimate of the UE is the preferred type of location information, and a second value of the parameter indicates that a location measurement is the preferred type of location information.

[0172]

[0180] Clause 26. The UE of clause 25, wherein the parameter comprises a "LocationInformationType" information element, a first value of the parameter comprises a "locationEstimatePreferred" value of the "LocationInformationType" information element, and a second value of the parameter comprises a "locationMeasurementsPreferred" value of the "LocationInformationType" information element.

[0173]

[0181] Clause 27. A UE as described in any of clauses 18 to 26, wherein at least one processor is further configured to receive, via at least one transceiver, an indication that the UE is expected to take power consumption into account when responding to the location information request, and the location information response includes a location estimate or location measurement value of the UE based on the indication that the UE is expected to take power consumption into account when responding to the location information request.

[0174]

[0182] Clause 28. The UE of clause 27, wherein the instructions include an instruction that a power consumption key performance indicator (KPI) of the UE is turned on or an instruction that the UE is expected to use low power consumption when responding to a location information request.

[0175]

[0183] Clause 29. A UE according to any of clauses 18 to 28, wherein at least one processor is further configured to determine whether to report a location estimate of the UE or a location measurement in the location information response.

[0176]

[0184] Clause 30. The UE of clause 29, wherein the determination of whether to report a location estimate of the UE or to report location measurements in a location information response is performed in response to receiving a location information request, periodically, in response to a trigger event, or any combination thereof.

[0177]

[0185] Clause 31. The UE of clause 30, wherein the trigger event comprises a change in the radio resource control (RRC) state of the UE, a change in serving cell reference signal received power (RSRP), a change in serving cell signal to interference and noise ratio (SINR), a change in the size of the location information response, a change in assistance data for a positioning session associated with the location information request, or a change in the discontinuous reception (DRX) configuration of the UE.

[0178]

[0186] Clause 32. The UE of any of clauses 18 to 31, wherein the parameters configure the UE to report a location estimate of the UE, and the location information response includes location measurements instead of the location estimate of the UE based on a power consumption metric.

[0179]

[0187] Clause 33. The UE of any of clauses 18 to 31, wherein the parameters configure the UE to report location measurements, and the location information response includes a location estimate of the UE based on a power consumption metric instead of the location measurements.

[0180]

[0188] Clause 34. A UE according to any of clauses 18 to 33, wherein the network entity is a location server, the location information request comprises a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message, and the location information response comprises an LPP Provide Location Information message.

[0181]

[0189] Clause 35. A user equipment (UE) includes means for receiving from a network entity a location information request including parameters for configuring the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and means for transmitting to the network entity a location information response including the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0182]

[0190] Clause 36. The UE of clause 35, wherein the power consumption metric comprises a comparison of a difference between an estimated power consumption reporting a location measurement and an estimated power consumption reporting a location estimate of the UE to a threshold value.

[0183]

[0191] Clause 37. The UE of clause 36, wherein the estimated power consumption for reporting location measurements is based on the estimated power consumption for obtaining location measurements and the estimated power consumption for transmitting the location measurements in a location information response, and wherein the estimated power consumption for reporting a location estimate of the UE is based on the estimated power consumption for obtaining location measurements, the estimated power consumption for determining a location estimate of the UE, and the estimated power consumption for transmitting a location estimate of the UE in a location information response.

[0184]

[0192] Clause 38. The UE of clause 37, wherein the estimated power consumption for transmitting location measurements in a location information response is based on the number of location measurements.

[0185]

[0193] Clause 39. The UE of clause 38, wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

[0186]

[0194] Clause 40. The UE of any of clauses 37 to 39, wherein the estimated power consumption for determining a location estimate for the UE is based on a positioning engine mode used to determine a location estimate for the UE.

[0187]

[0195] Clause 41. The UE of clause 40, wherein the positioning engine mode used to determine a location estimate for the UE is based on mobility, completeness, history of positioning estimates, accuracy requirements, latency requirements, or any combination thereof, associated with the location information request.

[0188]

[0196] Clause 42. A UE as described in any of clauses 35 to 41, wherein a first value of the parameter indicates that a location estimate of the UE is the preferred type of location information, and a second value of the parameter indicates that a location measurement is the preferred type of location information.

[0189]

[0197] Clause 43. The UE of clause 42, wherein the parameter comprises a "LocationInformationType" information element, a first value of the parameter comprises a "locationEstimatePreferred" value of the "LocationInformationType" information element, and a second value of the parameter comprises a "locationMeasurementsPreferred" value of the "LocationInformationType" information element.

[0190]

[0198] Clause 44. A UE as described in any of clauses 35 to 43, further comprising means for receiving an indication that the UE is expected to take power consumption into account when responding to the location information request, the location information response including a location estimate or location measurement of the UE based on the indication that the UE is expected to take power consumption into account when responding to the location information request.

[0191]

[0199] Clause 45. The UE of clause 44, wherein the instructions include an instruction that a power consumption key performance indicator (KPI) of the UE is turned on or an instruction that the UE is expected to use low power consumption when responding to a location information request.

[0192]

[0200] Clause 46. The UE of any of clauses 35 to 45, further comprising means for determining whether to report a location estimate or location measurements of the UE in a location information response.

[0193]

[0201] Clause 47. The UE of clause 46, wherein the determination of whether to report a location estimate of the UE or to report location measurements in a location information response is performed in response to receiving a location information request, periodically, in response to a trigger event, or any combination thereof.

[0194]

[0202] Clause 48. The UE of clause 47, wherein the trigger event comprises a change in the radio resource control (RRC) state of the UE, a change in the serving cell reference signal received power (RSRP), a change in the serving cell signal-to-interference-and-noise ratio (SINR), a change in the size of the location information response, a change in assistance data for a positioning session associated with the location information request, or a change in the discontinuous reception (DRX) configuration of the UE.

[0195]

[0203] Clause 49. The UE of any of clauses 35 to 48, wherein the parameters configure the UE to report a location estimate of the UE, and the location information response includes location measurements instead of the location estimate of the UE based on a power consumption metric.

[0196]

[0204] Clause 50. The UE of any of clauses 35 to 48, wherein the parameters configure the UE to report location measurements, and the location information response includes a location estimate of the UE based on a power consumption metric instead of the location measurements.

[0197]

[0205] Clause 51. A UE according to any of clauses 35 to 50, wherein the network entity is a location server, the location information request comprises a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message, and the location information response comprises an LPP Provide Location Information message.

[0198]

[0206] Clause 52. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to receive from a network entity a location information request including parameters to configure the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable the network entity to determine a location estimate of the UE, and to transmit to the network entity a location information response including the location estimate or location measurements of the UE based on power consumption metrics associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

[0199]

[0207] Clause 53. The non-transitory computer-readable medium of clause 52, wherein the power consumption metric includes a comparison of a difference between an estimated power consumption reporting a location measurement and an estimated power consumption reporting a location estimate of the UE to a threshold value.

[0200]

[0208] Clause 54. The non-transitory computer-readable medium of clause 53, wherein the estimated power consumption for reporting location measurements is based on the estimated power consumption for obtaining location measurements and the estimated power consumption for transmitting the location measurements in a location information response, and the estimated power consumption for reporting a location estimate of the UE is based on the estimated power consumption for obtaining location measurements, the estimated power consumption for determining a location estimate of the UE, and the estimated power consumption for transmitting the location estimate of the UE in a location information response.

[0201]

[0209] Clause 55. The non-transitory computer-readable medium of clause 54, wherein the estimated power consumption for transmitting location measurements in a location information response is based on the number of location measurements.

[0202]

[0210] Clause 56. The non-transitory computer-readable medium of clause 55, wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

[0203]

[0211] Clause 57. The non-transitory computer-readable medium of any of clauses 54-56, wherein the estimated power consumption for determining a location estimate of the UE is based on a positioning engine mode used to determine the location estimate of the UE.

[0204]

[0212] Clause 58. The non-transitory computer-readable medium of clause 57, wherein the positioning engine mode used to determine a location estimate for the UE is based on mobility, completeness, positioning estimate history, accuracy requirements, latency requirements, or any combination thereof, associated with the location information request.

[0205]

[0213] Clause 59. A non-transitory computer-readable medium according to any of clauses 52 to 58, wherein a first value of the parameter indicates that a location estimate of the UE is the preferred type of location information, and a second value of the parameter indicates that a location measurement is the preferred type of location information.

[0206]

[0214] Clause 60. The non-transitory computer-readable medium of clause 59, wherein the parameter includes a "LocationInformationType" information element, a first value of the parameter includes a "locationEstimatePreferred" value of the "LocationInformationType" information element, and a second value of the parameter includes a "locationMeasurementsPreferred" value of the "LocationInformationType" information element.

[0207]

[0215] Clause 61. A non-transitory computer-readable medium according to any of clauses 52 to 60, further comprising computer-executable instructions that, when executed by a UE, cause the UE to receive an indication that the UE is expected to take power consumption into account when responding to the location information request, the location information response including a location estimate or location measurement value of the UE based on the indication that the UE is expected to take power consumption into account when responding to the location information request.

[0208]

[0216] Clause 62. The non-transitory computer-readable medium of clause 61, wherein the instructions include an instruction that a power consumption key performance indicator (KPI) of the UE is turned on or an instruction that the UE is expected to use low power consumption when responding to a location information request.

[0209]

[0217] Clause 63. A non-transitory computer-readable medium according to any of clauses 52 to 62, further comprising computer-executable instructions that, when executed by the UE, cause the UE to determine whether to report a location estimate of the UE in a location information response or whether to report location measurements.

[0210]

[0218] Clause 64. The non-transitory computer-readable medium of clause 63, wherein the determination of whether to report a location estimate or location measurements of the UE in a location information response is performed in response to receiving a location information request, periodically, in response to a trigger event, or any combination thereof.

[0211]

[0219] Clause 65. The non-transitory computer-readable medium of clause 64, wherein the trigger event includes a change in a radio resource control (RRC) state of the UE, a change in a serving cell reference signal received power (RSRP), a change in a serving cell signal-to-interference-and-noise ratio (SINR), a change in the size of a location information response, a change in assistance data for a positioning session associated with the location information request, or a change in a discontinuous reception (DRX) configuration of the UE.

[0212]

[0220] Clause 66. The non-transitory computer-readable medium of any of clauses 52-65, wherein the parameters configure the UE to report a location estimate of the UE, and the location information response includes a location measurement in lieu of the location estimate of the UE based on a power consumption metric.

[0213]

[0221] Clause 67. The non-transitory computer-readable medium of any of clauses 52-65, wherein the parameters configure the UE to report location measurements, and the location information response includes a location estimate of the UE, instead of the location measurements, based on a power consumption metric.

[0214]

[0222] Clause 68. The non-transitory computer-readable medium of any of clauses 52 to 67, wherein the network entity is a location server, the location information request includes a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message, and the location information response includes an LPP Provide Location Information message.

[0215]

[0223] Those skilled in the art will understand 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.

[0216]

[0224] Furthermore, those skilled in the art will understand that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may realize 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.

[0217]

[0225] The various example logic blocks, modules, and circuits described in connection with 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.

[0218]

[0226] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, removable disk, 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 the user terminal.

[0219]

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

[0220]

[0228] While the above disclosure illustrates exemplary aspects of the present disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the present disclosure, which is defined by the appended claims. The functions, steps, and / or actions of the method claims in accordance with the aspects of the present disclosure described herein need not be performed in any particular order. Furthermore, although elements of the present disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving a location information request from the network entity, the request including parameters to configure the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable a network entity to determine the location estimate of the UE; sending a location information response to the network entity, the location information response including the location estimate or the location measurements of the UE based on a power consumption metric associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity; A method comprising:

2. The method of claim 1 , wherein the power consumption metric comprises a comparison of a difference between an estimated power consumption reporting the location measurement and an estimated power consumption reporting the location estimate of the UE to a threshold value.

3. the estimated power consumption for reporting the location measurements is based on an estimated power consumption for acquiring the location measurements and an estimated power consumption for transmitting the location measurements in the location information response; 3. The method of claim 2, wherein the estimated power consumption for reporting the location estimate of the UE is based on the estimated power consumption for acquiring the location measurements, the estimated power consumption for determining the location estimate of the UE, and the estimated power consumption for transmitting the location estimate of the UE in the location information response.

4. The method of claim 3 , wherein the estimated power consumption for transmitting the location measurements in the location information response is based on a number of the location measurements.

5. The method of claim 4 , wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

6. The method of claim 3 , wherein the estimated power consumption for determining the location estimate of the UE is based on a positioning engine mode used to determine the location estimate of the UE.

7. 7. The method of claim 6, wherein the positioning engine mode used to determine the location estimate for the UE is based on mobility, completeness, history of positioning estimates, accuracy requirements, latency requirements, or any combination thereof associated with the location information request.

8. a first value of the parameter indicating that the location estimate of the UE is the preferred type of location information; The method of claim 1 , wherein a second value of the parameter indicates that the location measurement is the preferred type of location information.

9. The parameters include a "LocationInformationType" information element, the first value of the parameter comprises the "locationEstimatePreferred" value of the "LocationInformationType" information element; The method of claim 8 , wherein the second value of the parameter comprises a “locationMeasurementsPreferred” value of the “LocationInformationType” information element.

10. 2. The method of claim 1, further comprising receiving an indication that the UE is expected to consider power consumption when responding to the location information request, wherein the location information response includes the location estimate or the location measurement of the UE based on the indication that the UE is expected to consider power consumption when responding to the location information request.

11. The instructions are: an indication that the UE's power consumption key performance indicator (KPI) is turned on; or 11. The method of claim 10, comprising: an indication that the UE is expected to use low power consumption when responding to the location information request.

12. determining whether to report the location estimate or the location measurements of the UE in the Location Information Response; The method of claim 1 further comprising:

13. The determining whether to report the location estimate or the location measurements of the UE in the location information response comprises: In response to receiving the location information request, Periodically, In response to a trigger event, or The method of claim 12 performed in any combination thereof.

14. The trigger event is a change in the UE's radio resource control (RRC) state; the change in reference signal received power (RSRP) of the serving cell; the change in the signal-to-interference-and-noise ratio (SINR) of the serving cell; a change in the size of the location information response; a change in assistance data for a positioning session associated with said location information request; or a change in the UE's discontinuous reception (DRX) configuration; 14. The method of claim 13, comprising:

15. the parameters configure the UE to report the location estimate of the UE; the location information response includes the location measurement instead of the location estimate of the UE based on the power consumption metric. The method of claim 1.

16. the parameters configure the UE to report the location measurements; the location information response includes the location estimate of the UE instead of the location measurement based on the power consumption metric. The method of claim 1.

17. the network entity is a location server; the location information request comprises a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message; The method of claim 1 , wherein the location information response comprises an LPP Provided Location Information message.

18. A user equipment (UE), Memory and at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor: receiving, via the at least one transceiver, from the network entity, a location information request including parameters for configuring the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable a network entity to determine the location estimate of the UE; and transmitting, via the at least one transceiver, a location information response to the network entity, the location information response including the location estimate or the location measurements of the UE, based on a power consumption metric associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity.

19. 19. The UE of claim 18, wherein the power consumption metric comprises a comparison of a difference between an estimated power consumption reporting the location measurement and an estimated power consumption reporting the location estimate of the UE to a threshold value.

20. the estimated power consumption for reporting the location measurements is based on an estimated power consumption for acquiring the location measurements and an estimated power consumption for transmitting the location measurements in the location information response; 20. The UE of claim 19, wherein the estimated power consumption for reporting the location estimate of the UE is based on the estimated power consumption for acquiring the location measurements, the estimated power consumption for determining the location estimate of the UE, and the estimated power consumption for transmitting the location estimate of the UE in the location information response.

21. The UE of claim 20 , wherein the estimated power consumption for transmitting the location measurements in the location information response is based on a number of the location measurements.

22. 22. The UE of claim 21, wherein the number of location measurements is based on whether the UE is in a network acquisition mode or a tracking mode.

23. 21. The UE of claim 20, wherein the estimated power consumption for determining the location estimate of the UE is based on a positioning engine mode used to determine the location estimate of the UE.

24. 24. The UE of claim 23, wherein the positioning engine mode used to determine the location estimate for the UE is based on mobility, completeness, history of positioning estimates, accuracy requirements, latency requirements, or any combination thereof associated with the location information request.

25. a first value of the parameter indicating that the location estimate of the UE is the preferred type of location information; 19. The UE of claim 18, wherein a second value of the parameter indicates that the location measurement is the preferred type of location information.

26. The parameters include a "LocationInformationType" information element, the first value of the parameter comprises the "locationEstimatePreferred" value of the "LocationInformationType" information element; 26. The UE of claim 25, wherein the second value of the parameter comprises a "locationMeasurementsPreferred" value of the "LocationInformationType" information element.

27. the at least one processor:

19. The UE of claim 18, further configured to receive, via the at least one transceiver, an indication that the UE is expected to consider power consumption when responding to the location information request, wherein the location information response includes the location estimate or the location measurement of the UE based on the indication that the UE is expected to consider power consumption when responding to the location information request.

28. The instructions are: an indication that the UE's power consumption key performance indicator (KPI) is turned on; or 28. The UE of claim 27, including an indication that the UE is expected to use low power consumption when responding to the location information request.

29. the at least one processor:

19. The UE of claim 18, further configured to determine whether to report the location estimate or the location measurements of the UE in the location information response.

30. The determining whether to report the location estimate or the location measurements of the UE in the location information response comprises: In response to receiving the location information request, Periodically, In response to a trigger event, or 30. The UE of claim 29 implemented in any combination thereof.

31. The trigger event is a change in the UE's radio resource control (RRC) state; the change in reference signal received power (RSRP) of the serving cell; Changes in the signal-to-interference-and-noise ratio (SINR) of the serving cell; a change in the size of the location information response; a change in assistance data for a positioning session associated with said location information request; or a change in the UE's discontinuous reception (DRX) configuration; 31. The UE of claim 30, comprising:

32. the parameters configure the UE to report the location estimate of the UE; the location information response includes the location measurement instead of the location estimate of the UE based on the power consumption metric.

19. The UE of claim 18.

33. the parameters configure the UE to report the location measurements; the location information response includes the location estimate of the UE instead of the location measurement based on the power consumption metric.

19. The UE of claim 18.

34. the network entity is a location server; the location information request comprises a Long Term Evolution (LTE) Positioning Protocol (LPP) Request Location Information message; The UE of claim 18 , wherein the location information response comprises an LPP Provide Location Information message.

35. A user equipment (UE), means for receiving from the network entity a location information request comprising parameters for configuring the UE to report a preferred type of location information comprising a location estimate of the UE or location measurements obtained by the UE to enable a network entity to determine the location estimate of the UE; and means for transmitting a location information response to the network entity, the location information response including the location estimate or the location measurements of the UE, based on a power consumption metric associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity; A UE including:

36. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receiving from the network entity a location information request including parameters to configure the UE to report a preferred type of location information including a location estimate of the UE or location measurements obtained by the UE to enable a network entity to determine the location estimate of the UE; causing the network entity to transmit a location information response including the location estimate or the location measurements of the UE based on a power consumption metric associated with reporting the location estimate of the UE to the network entity and reporting the location measurements to the network entity; Non-transitory computer-readable medium.

Images