Location reference signal measurement period optimization for user equipment handling load awareness
By working together in the 5G wireless communication system, adjusting the processing load and measurement cycle of the positioning reference signal, the problem of excessive processing load of UE is solved, and low latency and efficient positioning measurement are achieved.
Patent Information
- Application Number
- CN202380029777.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-01
- Filing Date
- 2023-01-31
- Publication Date
- 2024-11-08
AI Technical Summary
In 5G wireless communication systems, the positioning reference signal (PRS) processing load received by the user equipment (UE) may exceed its processing capacity, resulting in a prolonged positioning measurement time, affecting positioning accuracy and efficiency.
Through the coordinated work between the network entity and the UE, it is determined that the PRS processing load exceeds the UE's processing capacity, and transmits auxiliary data to reduce the processing load to the UE, adjusts the positioning frequency layer and measurement gap configuration, and optimizes the PRS measurement cycle to reduce measurement time Delay.
It effectively reduces the delay of positioning measurement, improves positioning accuracy and efficiency, adapts to the needs of low-delay positioning, optimizes the PRS processing load, and improves system performance.
Smart Images

Figure CN118922733A_ABST
Abstract
Description
Background Art 1. Technical Field
[0001] Aspects of the present disclosure relate generally to wireless communications.
[0002] 2. Description of related technologies
[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.
[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks 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, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployments of 5G, enable high-precision positioning based on 5G. Summary of the invention
[0005] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all considered aspects, nor should it be considered to identify key or decisive elements related to all considered aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects related to the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.
[0006] In one aspect, a method of wireless positioning performed by a network entity includes: determining that a positioning reference signal (PRS) processing load for a user equipment (UE) exceeds a PRS processing capability of the UE; and transmitting assistance data to the UE that reduces the PRS processing load for the UE.
[0007] In one aspect, a method for wireless positioning performed by a UE includes: determining that one or more PRS measurements are associated with a low-latency location request based on information received from a network entity; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and performing the one or more PRS measurements associated with the low-latency location request based on the modified one or more parameters.
[0008] In one aspect, a network entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine that a PRS processing load for a UE exceeds a PRS processing capability of the UE; and transmit, via the at least one transceiver, to the UE assistance data that reduces the PRS processing load for the UE.
[0009] In one aspect, a UE comprises: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine, based on information received from a network entity, that one or more PRS measurements are associated with a low-latency location request; modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and perform the one or more PRS measurements associated with the low-latency location request based on the modified one or more parameters.
[0010] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.
[0012] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.
[0013] Figure 2A and Figure 2B Example wireless network structures according to aspects of the present disclosure are illustrated.
[0014] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.
[0015] Figure 4 is a diagram illustrating an example frame structure according to aspects of the present disclosure.
[0016] Figure 5 is a diagram illustrating various downlink channels within an example downlink time slot in accordance with aspects of the present disclosure.
[0017] Figure 6 is a diagram of example positioning reference signal (PRS) configurations for PRS transmission for a given base station in accordance with aspects of the present disclosure.
[0018] Figure 7 A time difference of arrival (TDOA) based positioning procedure in an example wireless communication system 700 is illustrated in accordance with aspects of the present disclosure.
[0019] Figure 8 An example Long Term Evolution (LTE) Positioning Protocol (LPP) call flow between a UE and a location server for performing positioning operations is illustrated.
[0020] Fig. 9 An example of measuring PRS data during a measurement gap (MG) according to aspects of the present disclosure is illustrated.
[0021] Fig.10 are time and frequency diagrams illustrating some parameters derived from assistance data and their impact on the measurement period in accordance with aspects of the present disclosure.
[0022] Fig.11 is a flow chart of an example process performed by a network entity associated with UE processing load-aware PRS measurement period optimization according to aspects of the present disclosure.
[0023] Fig.12 is a flow chart of example procedures performed by a UE associated with UE processing load-aware PRS measurement period optimization according to aspects of the present disclosure. DETAILED DESCRIPTION
[0024] Technologies for wireless positioning are disclosed. In one aspect, a network entity may determine that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capability of the UE, and the UE may transmit the PRS processing capability to the network entity in response to a request from the network entity to the UE. The network entity may transmit to the UE auxiliary data that reduces the PRS processing load for the UE. In another aspect, a user equipment (UE) may determine that one or more PRS measurements are associated with a low-latency location request based on information received from the network entity. The UE may modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency. The UE may perform the one or more PRS measurements associated with the low-latency location request based on the modified one or more parameters.
[0025] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.
[0026] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.
[0027] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.
[0028] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been considered within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".
[0029] As used herein, unless otherwise specified, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any specific radio access technology (RAT). In general, a UE may be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a consumer asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) head-mounted device, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or (e.g., at certain times) may be stationary and may communicate with a radio access network (RAN). As used herein, the term "UE" may be interchangeably referred to as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or "UT", "mobile device", "mobile terminal", "mobile station" or variations thereof. In general, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to external networks such as the Internet and to other UEs. Of course, other mechanisms for the UE to connect to the core network and / or the Internet are also possible, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.), etc.
[0030] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may only provide edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.
[0031] The term "base station" may refer to a single physical transmit-receive point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located 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 transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.
[0032] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE, and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).
[0033] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the 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, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.
[0034] Figure 1An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In one aspect, the macro cell 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 the two, and the small cell base stations may include femto cells, pico cells, micro cells, etc.
[0035] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communications between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.
[0036] Among other functions, the base station 102 can perform functions related to one or more of the following: conveying user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through EPC / 5GC) on a backhaul link 134, which can be wired or wireless.
[0037] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a certain frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency 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.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.
[0038] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some of the geographic coverage areas 110 may substantially overlap with the 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 areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG).
[0039] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).
[0040] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.
[0041] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, Licensed Assisted Access (LAA) or MulteFire.
[0042] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended downward to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and it is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmitting and / or receiving) on the mmW communication link 184 to compensate for the extremely high path loss and short range. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.
[0043] 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., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (called a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.
[0044] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent 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 sent 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 the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.
[0045] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.
[0046] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on 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 specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.
[0047] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, it is an uplink receive beam, while if the UE is forming an uplink beam, it is an uplink transmit beam.
[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0050] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.
[0051] 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 a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and can be used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably.
[0052] For example, still refer to Figure 1 , one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.
[0053] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.
[0054] In some cases, UE 164 and UE 182 are capable of sidelink communication. A UE with sidelink capability (SL-UE) can communicate with base station 102 via communication link 120 using a Uu interface (i.e., an air interface between UE and base station). SL-UE (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using a PC5 interface (i.e., an air interface between UEs with sidelink capability). A wireless sidelink (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without communicating through a base station. Sidelink communications can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communications, vehicle-to-vehicle (V2X) communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communications may be located 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 be unable to receive transmissions from the base station 102 for other reasons. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system, in which each SL-UE transmits to each other SL-UE in the group. In some cases, the base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between the SL-UEs without involving the base station 102.
[0055] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.
[0056] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), and the like. Thus, in some cases, UE 164 and UE 182 may utilize beamforming on sidelink 160.
[0057] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SV 112 can 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 transmitter system (e.g., SV 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal of a repeating pseudo-random noise (PN) code marked with a set number of chips. Although typically located in the SV 112, the transmitter can sometimes be located on a ground-based control station, base station 102, and / or other UEs 104. The UE 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SV 112.
[0058] In a satellite positioning system, the use of signal 124 may be enhanced 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 systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.
[0059] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from SV 112.
[0060] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “side links”). Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), etc.
[0061] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In another configuration, the ng-eNB 224 can 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. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the 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 ng-eNBs 224 and gNBs 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).
[0062] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).
[0063] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally considered 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 in conjunction 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 interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of 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, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.
[0064] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, service steering), lawful interception (user plane collection), service usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink service verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.
[0065] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.
[0066] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 may support similar functionality as LMF 270, but LMF 270 may communicate with AMF 264, NG-RAN 220, and UE 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages rather than voice or data), and SLP 272 may communicate with UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).
[0067] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., a location estimate) of the UE 204. 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 server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.
[0068] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically 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 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.
[0069] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including transporting user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 generally hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent 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 layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.
[0070] Figure 3A , Figure 3B and Figure 3C302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the 5GC 210 / 260 to support the operations described herein are shown. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. In addition, a given device may include one or more of these 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.
[0071] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. 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.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 may be configured in various ways according to the specified RAT to send and encode signals 318 and 358 (e.g., messages, indications, information, etc.), and vice versa, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for sending and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.
[0072] At least in some cases, UE 302 and base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are configured to communicate with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), etc.) (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.). The short-range wireless transceivers 320 and 360 can be configured in various ways according to the specified RAT to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively. Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.
[0073] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.
[0074] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.
[0075] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), may include separate transmitter circuit systems and separate receiver circuit systems in some implementations, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system 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 antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.
[0076] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) 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 may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.
[0077] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuit systems, or various combinations thereof.
[0078] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Memories 340, 386, and 396 may thus provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning modules 342, 388, and 398, respectively. Positioning modules 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning modules 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., as part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning modules 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the positioning module 342 are illustrated, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3BPossible locations for the positioning module 388 are illustrated, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for the location module 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.
[0079] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.
[0080] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to a user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when a user actuates 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 a user interface.
[0081] Referring to the one or more processors 384 in more detail, in a 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. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through 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 functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
[0082] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, 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 produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from a reference signal and / or channel condition feedback sent 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 a corresponding spatial stream for transmission.
[0083] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can 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 can 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 and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 304. These soft decisions can 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 sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.
[0084] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.
[0085] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
[0086] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.
[0087] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.
[0088] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from UE 302. IP packets from one or more processors 384 may be provided to the core network. One or more processors 384 are also responsible for error detection.
[0089] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C , is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.
[0090] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form or be part of communication interfaces for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide for communication between the different logical entities.
[0091] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3C The components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). In addition, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific 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 modules 342, 388 and 398, etc.
[0092] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated differently from a network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated 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).
[0093] Figure 4 is a diagram illustrating an example frame structure according to aspects of the present disclosure. Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, a base station and a UE). Figure 4 4 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.
[0094] LTE (and in some cases NR) utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Thus, for a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.
[0095] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.
[0096] exist Figure 4 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 4 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.
[0097] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) in the frequency domain (also referred to as physical RBs (PRBs)). The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 4In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0098] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink communication or downlink communication. Figure 4 Example locations of REs carrying reference signals (labeled "R") are illustrated.
[0099] Figure 5 5 is a diagram 500 illustrating various downlink channels within an example downlink time slot. Figure 5 In , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top. Figure 5 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.
[0100] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a set of contiguous RBs selected from a contiguous subset of common RBs for a given parameter set on a given carrier. In general, a maximum of four BWPs can be specified in the downlink and uplink. That is, the UE can be configured to have up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.
[0101] refer to Figure 5, the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth, and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (such as the system information block (SIB)), and paging messages.
[0102] The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain), each REG bundle includes one or more REGs, each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for PDCCH.
[0103] exist Figure 5 In the example of , there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be just one symbol or two symbols). Unlike LTE control channels that occupy the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Therefore, Figure 5 The frequency components of the PDCCH shown in FIG are illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESETs are continuous in the frequency domain, the CORESETs do not need to be continuous. Furthermore, the CORESETs may span less than three symbols in the time domain.
[0104] The DCI within the PDCCH carries information about uplink resource allocations (persistent and non-persistent) and descriptions of downlink data sent to the UE (referred to as uplink grants and downlink grants, respectively). More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs may be configured in the PDCCH, and these DCIs may have one of a variety of formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH may be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.
[0105] Figure 6 is a diagram of an example PRS configuration 600 for PRS transmission for a given base station in accordance with aspects of the present disclosure. Figure 6 In , time is represented horizontally, increasing from left to right. Each long rectangle represents a time slot, and each short (shaded) rectangle represents an OFDM symbol. Figure 6 In the example of FIG. 1 , a PRS resource set 610 (labeled as “PRS resource set 1”) includes two PRS resources, namely a first PRS resource 612 (labeled as “PRS resource 1”) and a second PRS resource 614 (labeled as “PRS resource 2”). The base station transmits PRS on the PRS resources 612 and 614 of the PRS resource set 610 .
[0106] PRS resource set 610 has an opportunity length (N_PRS) of two slots and a periodicity (T_PRS) of, for example (for 15 kHz subcarrier spacing) 160 slots or 160 milliseconds (ms). Thus, both PRS resources 612 and 614 are two consecutive slots in length and repeat every T_PRS slots starting from the slot in which the first symbol of the corresponding PRS resource appears. Figure 6 In the example of , PRS resource 612 has a symbol length (N_symb) of two symbols, and PRS resource 614 has a symbol length (N_symb) of four symbols. PRS resource 612 and PRS resource 614 may be transmitted on separate beams of the same base station.
[0107] Each instance of the PRS resource set 610 (illustrated as instances 620a, 620b, and 620c) includes a length of '2' opportunities (i.e., N_PRS=2) for each PRS resource 612, 614 in the PRS resource set. The PRS resources 612 and 614 repeat once every T_PRS time slot up to a muting sequence periodicity of T_REP. Therefore, a bitmap of length T_REP will be needed to indicate which opportunities of the instances 620a, 620b, and 620c of the PRS resource set 610 are muted (i.e., not transmitted).
[0108] In one aspect, there may be additional constraints on the PRS configuration 600. For example, for all PRS resources (e.g., PRS resources 612, 614) of a PRS resource set (e.g., PRS resource set 610), the base station may configure the following parameters to be the same: (a) opportunity length (N_PRS), (b) number of symbols (N_symb), (c) comb type and / or (d) bandwidth. In addition, for all PRS resources in all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether for one base station or for all base stations may depend on the ability of the UE to support the first and / or second options.
[0109] Figure 7 A positioning procedure based on time difference of arrival (TDOA) in an example wireless communication system 700 is illustrated in accordance with various aspects of the present disclosure. TDOA is also referred to as reference signal time difference (RSTD). The TDOA-based positioning procedure may be an observed time difference of arrival (OTDOA) positioning procedure in LTE or a downlink time difference of arrival (DL-TDOA) positioning procedure in 5G NR. Other positioning methods include DL-AoD and multi-RTT positioning. Figure 7 In an example, a UE 704 (e.g., any of the UEs described herein) is attempting to compute an estimate of its location (referred to as "UE-based" positioning), or assisting another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in computing an estimate of its location (referred to as "UE-assisted" positioning). The UE 704 may communicate with (e.g., transmit information to and receive information from) one or more of a plurality of base stations 702 (e.g., any combination of base stations described herein), the plurality of base stations being labeled "BS1" 702-1, "BS2" 702-2, and "BS3" 702-3.
[0110] To support position estimation, the base station 702 may be configured to broadcast positioning reference signals (e.g., positioning reference signals (PRS), tracking reference signals (TRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), etc.) to the UEs 704 in its coverage area to enable the UEs 704 to measure the characteristics of such reference signals. In a TDOA-based positioning procedure, the UE 704 measures the time difference (referred to as reference signal time difference (RSTD) or TDOA) between specific downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) sent by different pairs of base stations 702, and reports these RSTD measurements to a location server (e.g., location server 230, LMF 270, SLP 272) or calculates a position estimate based on these RSTD measurements.
[0111] Generally speaking, in a reference cell (e.g., Figure 7 ) and one or more neighboring cells (e.g., Figure 7 RSTD is measured between a reference cell and a base station (e.g., cells supported by base stations 702-2 and 702-3 in the example of ). For any single positioning use of TDOA, the reference cell remains the same for all RSTDs measured by UE 704 and will typically correspond to a serving cell for UE 704 or another nearby cell with good signal strength at UE 704. In one aspect, a neighboring cell is typically a cell supported by a different base station than the base station for the reference cell and may have good or poor signal strength at UE 704. The position calculation can be based on the measured RSTD and knowledge of the locations and relative transmit timing of the base stations 702 involved (e.g., whether the base stations 702 are accurately synchronized or whether each base station 702 transmits at some known time offset relative to the other base stations 702).
[0112] To assist in TDOA-based positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data for a reference cell and neighboring cells relative to the reference cell to UE 704. For example, the assistance data may include an identifier (e.g., PCI, VCI, CGI, etc.) for each cell in a set of cells that the UE 704 is expected to measure (here, cells supported by the base station 702). The assistance data may also provide a center channel frequency for each cell, various reference signal configuration parameters (e.g., number of consecutive positioning slots, periodicity of positioning slots, silent sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth), and / or other cell-related parameters applicable to TDOA-based positioning procedures. The assistance data may also indicate a serving cell for the UE 704 as a reference cell.
[0113] In some cases, the auxiliary data may also include an "expected RSTD" parameter and the uncertainty of the expected RSTD parameter, which provides information about the RSTD value that the expected UE 704 will measure between the reference cell and each adjacent cell at its current position to the UE 704. The expected RSTD and the associated uncertainty may define a search window for the UE 704, within which the expected UE 704 will measure the RSTD value. In some cases, the value range of the expected RSTD may be + / -500 microseconds (μs). In some cases, when any resource used for positioning measurement is in FR1, the value range of the uncertainty of the expected RSTD may be + / -32μs. In other cases, when all resources used for positioning measurement are in FR2, the value range of the uncertainty of the expected RSTD may be + / -8μs.
[0114] The TDOA assistance information may also include positioning reference signal configuration information parameters that allow UE 704 to determine when the positioning reference signal timing will occur on the signals received from various neighboring cells relative to the positioning reference signal timing of the reference cell, and to determine the reference signal sequences sent from the various cells in order to measure the reference signal arrival time (ToA) or RSTD.
[0115] In one aspect, although a location server (e.g., location server 230, LMF 270, SLP 272) can transmit assistance data to UE 704, alternatively, the assistance data can originate directly from base station 702 itself (e.g., in a periodically broadcast overhead message, etc.). Alternatively, UE 704 can detect neighboring base stations on its own without using assistance data.
[0116] UE 704 (e.g., based in part on assistance data, if provided) may measure and (optionally) report RSTD between reference signals received from pairs of base stations 702. Using RSTD measurements, known absolute transmit timing or relative transmit timing of each base station 702, and known locations of reference and neighboring base stations 702, a network (e.g., location server 230 / LMF270 / SLP 272, base stations 702) or UE 704 may estimate the location of UE 704. More specifically, the RSTD of neighboring cell "k" relative to reference cell "Ref" may be represented by (ToA_k-ToA_Ref). Figure 7 In the example of , the RSTD measured between the reference cell of base station 702-1 and the cells of neighboring base stations 702-2 and 702-3 can be represented as T2-T1 and T3-T1, where T1, T2 and T3 represent the ToA of the reference signals from base stations 702-1, 702-2 and 702-3, respectively. Then, UE 704 (if it is not a positioning entity) can transmit the RSTD measurement to a location server or another positioning entity. Using (i) RSTD measurements, (ii) known absolute transmit timing or relative transmit timing of each base station 702, (iii) known location of base station 702 and / or (iv) directional reference signal characteristics (such as transmit direction), the location of UE 704 can be determined (by UE 704 or location server).
[0117] In one aspect, the position estimate may specify the position of the UE 704 in a two-dimensional (2D) coordinate system; however, the aspects disclosed herein are not limited in this regard and may also be adapted to determine a position estimate using a three-dimensional (3D) coordinate system where additional dimensions are desired. Figure 7 One UE 704 and three base stations 702 are illustrated, but it should be understood that more UEs 704 and more base stations 702 may exist.
[0118] Still reference Figure 7 , when UE 704 uses RSTD to obtain a position estimate, necessary additional data (e.g., the position and relative transmit timing of base station 702) may be provided to UE 704 by a location server. In some implementations, a position estimate for UE 704 may be obtained (e.g., by UE 704 itself or by a location server) from RSTD and from other measurements made by UE 704 (e.g., measurements of signal timing from global positioning system (GPS) or other global navigation satellite system (GNSS) satellites). In these implementations (referred to as hybrid positioning), RSTD measurements may help obtain a position estimate for UE 704, but may not fully determine the position estimate.
[0119] Figure 8An example Long Term Evolution (LTE) Positioning Protocol (LPP) procedure 800 is illustrated for performing positioning operations between a UE 802 and a location server (illustrated as a Location Management Function (LMF) 804). Figure 8 As illustrated, positioning of UE 802 is supported via the exchange of LPP messages between UE 802 and LMF 804. LPP messages may be exchanged between UE 802 and LMF 804 via a serving base station of UE 802 (illustrated as serving gNB 806) and a core network (not shown). LPP procedures 800 may be used to locate UE 802 in order to support various location-related services, such as for UE 802 (or for a user of UE 802), or for routing, or for providing an accurate location to a public safety answering point (PSAP) in association with an emergency call from UE 802 to the PSAP, or for navigation for some other reason. LPP procedures 800 may also be referred to as positioning sessions, and there may be multiple positioning sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round trip time (RTT), enhanced cell identification (E-CID), etc.).
[0120] In some aspects, at stage 810, UE 802 may receive a request for the positioning capabilities of the UE from LMF 804 (e.g., an LPP Request Capabilities message). At stage 820, UE 802 provides its positioning capabilities with respect to the LPP protocol to LMF 804 by transmitting an LPP Provide Capabilities message to LMF 804 indicating that UE 802 uses the positioning methods supported by LPP and the characteristics of these positioning methods. In some aspects, the capabilities indicated in the LPP Provide Capabilities message may indicate the positioning types supported by UE 802 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the ability of UE 802 to support those positioning types. In other aspects, UE 802 may unilaterally indicate the capabilities of the UE to LMF 804, for example, UE 802 may transmit an LPP Provide Capabilities message to LMF 804 without first receiving an LPP Request Capabilities message.
[0121] In some aspects, the capabilities indicated by the UE 802 to the LMF 804 are represented as parameters, which may be in the form of information elements (IEs). In some aspects, the capabilities indicated by the UE 802 to the LMF 804 include a parameter NR-DL-PRS-ProcessingCapability, which indicates a common DL-PRS processing capability applicable to all NR positioning methods supported by the UE. The parameter includes the maximum number of supported positioning frequency layers. For each supported frequency band, the UE may indicate one or more of the following:
[0122] dl-PRS-BufferType, which indicates the PRS buffering capability as type 1 (symbol-level buffering) or type 2 (slot-level buffering);
[0123] durationOfPRS-Processing, which indicates the duration N (ms) of PRS that the UE can process every T (ms), assuming the maximum PRS BW is indicated in supportedBandwidthPRS. Possible values of N include {0.125, 0.25, 0.5, 1, 2, 4, 6, 8, 12, 16, 20, 25, 30, 32, 35, 40, 45, 50}. Possible values of T include {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280}; and
[0124] maxNumOfDL-PRS-ResProcessedPerSlot, which indicates the maximum number N' of PRS resources that the UE can process per slot for each SCS (SCS15, SCS30, SCS60, and SCS120). Possible values of N' include {1, 2, 4, 8, 16, 24, 32, 48, 64}.
[0125] In some aspects, upon receiving the LPP Provide Capabilities message, at stage 820, the LMF 804 determines a particular type of positioning method to be used (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated positioning types supported by the UE 802, and determines a set of one or more Transmit Receiving Points (TRPs) from which the UE 802 will measure downlink positioning reference signals or to which the UE 802 will transmit uplink positioning reference signals. At stage 830, the LMF 804 transmits an LPP Provide Assistance Data message identifying the set of TRPs to the UE 802. In other aspects, in response to an LPP Request Assistance Data message ( Figure 8 802). The LPP provides assistance data message at stage 830 may be transmitted by the LMF 804 to the UE 802. The LPP requests assistance data message may include an identifier of the serving TRP of the UE 802 and a request for a positioning reference signal (PRS) configuration for a neighboring TRP. In some aspects, the LMF 804 may transmit an additional assistance data message ( Figure 8 not shown).
[0126] In some aspects, the assistance data includes an IE NR-DL-PRS-AssistanceData, which is used by the location server to provide DL-PRS assistance data. NR-DL-PRS-AssistanceData indicates to the UE 802 the set of PRS resources that the UE 802 is requested to measure. The assistance data may include a reference TRP, which is used as a timing reference to define a search window for all PRS resources. For example, the parameter nr-DL-PRS-ReferenceInfo defines the assistance data reference TRP whose DL-PRS configuration is included in the nr-DL-PRS-AssistanceDataList. One or more nr-DL-PRS-SFN0-Offset parameters and one or more nr-DL-PRS-expectedRSTD parameters in the nr-DL-PRS-AssistanceDataList are provided relative to the assistance data reference TRP.
[0127] In some aspects, the assistance data is organized in positioning frequency layers (PFLs) and PRS resource sets. A PRS resource set is a collection of PRS resources with the same periodicity and slot offset on a single TRP. Example periods include {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, and 10240} ms. The slot offset step size is one slot. The PRS resource may have a repetition pattern, which is defined as the number of repetitions (e.g., {1, 2, 4, 6, 8, 16, or 32} slots) and the step size (e.g., {1, 2, 4, 6, 8, 16, or 32} slots). For a PRS resource set, the assistance data may specify the number of symbols per slot, the muting pattern configuration, the power level, or some combination thereof. PFL is a collection of PRS resource sets on one or more TRPs with the same subcarrier spacing (SCS), cyclic prefix (CP) type, comb size, PRS bandwidth (e.g., {24, 28, 32, 36, ..., 268, 272} physical resource blocks (PRBs)), point A, and starting PRB.
[0128] At stage 840, the LMF 804 transmits a request for location information to the UE 802. The request may be an LPP Request Location Information message. The message typically includes information elements that define the type of location information, the expected location estimate accuracy, and the response time (i.e., expected latency). Note that a high latency requirement allows for a longer response time, while a low latency requirement requires a shorter response time. Thus, a long response time is referred to as high latency, and a short response time is referred to as low latency. A low latency location request may require the UE to process a smaller number of PRS resource samples to speed up the results.
[0129] Note that in some implementations, for example, if UE 802 transmits a request for assistance data to LMF 804 after receiving the request for location information at stage 840 (e.g., in an LPP request assistance data message, Figure 8 (not shown in the figure), the LPP provide assistance data message transmitted at stage 830 can be transmitted after the LPP request location information at 840.
[0130] At stage 850, the UE 802 utilizes the assistance information received at stage 830 and any additional data received at stage 840 (e.g., desired position accuracy or maximum response time) to perform positioning operations (e.g., measurement of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.
[0131] At stage 860, UE 802 may transmit an LPP Provide Location Information message to LMF 804 that conveys the results of any measurements (e.g., time of arrival (ToA), reference signal time difference (RSTD), received to transmit (Rx-Tx) time difference, etc.) obtained at stage 850 and before or at the expiration of any maximum response time (e.g., the maximum response time provided by LMF 804 at stage 840). The LPP Provide Location Information message at stage 860 may also include one or more times at which the positioning measurements were obtained and an identification of the TRP from which the positioning measurements were obtained. Note that the time between the request for location information at 840 and the response at 860 is the "response time" and indicates the latency of the positioning session.
[0132] Based at least in part on the measurements received in the LPP Provide Location Information message at stage 860, LMF 804 computes an estimated location of UE 802 using an appropriate positioning technique (e.g., DL-TDOA, RTT, E-CID, etc.).
[0133] Fig. 9 An example 900 of measuring and processing PRS data during an active mode, which may also be referred to herein as a connected mode or connected state, is illustrated. Fig. 9 In connected mode, the UE processes each PRS occurrence (labeled PRS1, PRS2, and PRS3) almost immediately, and the UE reports the results after the measurement period / response time ends. In connected mode, PRS processing may extend beyond the measurement gap. The length of the measurement period 902 depends on a number of factors, including the number of PRS samples to be collected. For example, T RSTD,i is the measurement period for PRS RSTD measurements in positioning frequency layer i and is calculated as follows:
[0134]
[0135] in:
[0136] ·CSSF PRS,i CSSF is a carrier-specific scaling factor for PRS-based measurements for positioning frequency layer i. This factor accounts for the sharing of measurement gaps between positioning measurements and mobility measurements (intra-frequency, inter-frequency, and inter-RAT). When measurement gaps are shared between multiple measurements, CSSF>1, resulting in longer measurement delays.
[0137] ·N RxBeam,i is the UE Rx beam scanning factor. This is the number of RX beams that the UE uses (sequentially) to measure a given PRS resource. In FR1, N RxBeam,i =1, and in FR2, N RxBeam,i = 8. In case the UE indicates support for a reduced Rx beam scanning factor, the location server may request a reduced Rx beam scanning factor for low latency measurement.
[0138] · is the maximum number of DL PRS resources per time slot in positioning frequency layer i.
[0139] ·{N i , T i} is the UE capability combination per frequency band, where N i is the maximum bandwidth supported by the UE, per T i ms Duration of DL PRS symbol processed in ms, which corresponds to durationOfPRS-Processing reported by the UE.
[0140] ·N′ i is the UE capability of the number of DL PRS resources that the UE can process in a slot, which corresponds to maxNumOfDL-PRS-ResProcessedPerSlot reported by the UE.
[0141] ·T 可用_PRS,i =LCM(T PRS,i , MGRP i ), that is, T PRS,i With MGRP i This parameter indicates the periodicity of the PRS resources available within the measurement gap for each PFL.
[0142] ·L 可用PRS,i It is in T 可用_PRS,i Duration of the available PRS in positioning frequency layer i during which to measure.
[0143] ·N 样本is the number of samples processed for each PRS resource; N 样本 =4. For low latency measurements, N 样本 Can be set to a number less than 4, such as 1 or 2.
[0144] ·
[0145] ·T 最后 is the measurement duration of the last PRS RSTD sample, including sampling time and processing time; T 最后 =T i +T 可用PRS,i .
[0146] MGRP i is the measurement gap periodicity.
[0147] ·T PRS,i is the effective PRS periodicity with PRS muting. Where k is the resource set index.
[0148] · is the higher later parameter DL-PRS-Periodicity.
[0149] ·N 静默 is the scaling factor taking into account PRS muting.
[0150] If a positioning frequency layer i has more than one DL PRS resource set with different PRS periodicities, the maximum PRS periodicity in the DL PRS resource set is used to derive the measurement period for the positioning frequency layer. The measurement period length requirement T for L number of positioning frequency layers (PFL) RSTD , all given by:
[0151]
[0152] where i is the PFL index. The first term is the sum of each PFL duration, and the second term describes the transition between PFLs.
[0153] As can be seen from the above equation, the measurement period formula depends on many parameters. Therefore, one challenge is how to characterize the dependency of the measurement delay on the auxiliary data and the measurement gap configuration, and another challenge is how the network, the UE, or both can use such characterization to reduce the measurement delay for low-latency positioning applications. Some parameters (such as N i 、T i and N′ i ) is a UE PRS processing capability parameter provided by the UE and usually does not change.
[0154] Fig.10 is a time and frequency diagram 1000 illustrating some parameters derived from the assistance data and their impact on the measurement period. Fig.10 Three measurement gaps (MG) 1002 and Fig.10 The six different PRS resources are identified by the legend in FIG. PRS resources can be sent by multiple TRPs. In conventional networks, only PRS resources present in the MG can be measured by the UE. Parameters that depend on the auxiliary data and measurement gap configuration include the number of PFLs (which are processed sequentially), T 可用_PRS,i , L 可用_PRS,i and Therefore, these parameters are parameters that the network can manipulate or configure via the assistance data. 样本 It is another parameter that can be manipulated or configured by the network. The parameters under the control of the UE include CSSF PRS,i and N RxBeam,i .
[0155] In order to characterize the dependency of the measurement delay on the auxiliary data and the measurement gap configuration, it should be noted that the term "PRS processing load" (denoted by the character lambda "λ") refers to the number, duration and availability of PRS resources relative to the ability of the UE to process these PRS resources, and can be expressed as a ratio of PRS resources to the ability of the UE to process these resources. Therefore, when the PRS processing load is greater than one, this indicates that there are more PRS resources to be processed than the UE can process in the required time. In addition, it has been observed that the PRS measurement period length requirement is proportional to the effective normalized PRS load λ. PRS i scales approximately linearly, the effective normalized PRS payload is defined as follows:
[0156]
[0157] When PRS,i = 1, which indicates a load-limited or demand-limited situation, for example, the UE can keep up with the processing in real time. PRS,i When >1, this indicates a processing-limited situation, for example, the UE needs more time to process all PRS signals and therefore will need to skip some processing. For example, given the parameters listed in Table 1 below, the PRS measurement period requirement will be as shown in Table 2 below:
[0158] Table 1 - Sample NR positioning scenarios in FR1
[0159]
[0160] Table 2 - PRS measurement period requirements for the scenarios in Table 1
[0161]
[0162] It is desirable to provide a mechanism by which the network, the UE, or both can implement or adapt to low-latency positioning measurements. Therefore, this document proposes techniques for low-latency positioning measurements.
[0163] Network-based methods. In one method, when providing assistance data and requesting low-latency measurements, the network can consider, for example, PRS,i Quantify the processing load of the UE to optimize the measurement delay. In some aspects, in order to reduce the measurement delay as required, the LMF or other network entity may perform one or more of the following operations:
[0164] Reduce the number of PFLs that the UE is requested to monitor;
[0165] For a given number of PFLs, the network may choose to place the PFLs in bands where the UE has higher processing capabilities;
[0166] Pack no more than N′ per time slot in PFL i i PRS resources;
[0167] Pack at least N PRS per measurement gap in PFL i i duration; or
[0168] Choose the PRS periodicity and measurement gap periodicity so that T 可用PRS,i ≥T i . Please note that T 可用PRS,i Increase to substantially exceed T i It will be counterproductive.
[0169] It should be noted that due to the number of factors involved in the calculation of lambda and the relationship of these factors to the number of PFLs, TRPs, resources per TRP, etc., the problem of minimizing the measurement delay requirements on the assistance data is highly non-linear and is therefore susceptible to a variety of algorithmic solutions. For example, one approach is for the network to attempt to adjust the PRS assistance data to minimize the processing load. Once a uniform processing load is achieved, no further improvements are required from a measurement requirements perspective.
[0170] UE-based approach. In another approach, the UE may determine (or be signaled) that a measurement is associated with a low-latency location request, which may enable the UE to modify behavior that would otherwise be mandated or assumed, such as to prioritize these measurements. For example, in some aspects, if the LMF or other location server requests the UE to report a measurement with less than a sample threshold (e.g., N 样本 ≤N 阈值 ) and / or is less than a normalized PRS load threshold (e.g., λ PRS,i ≤λ 阈值), the UE may consider the localization frequency layer (PFL) as low latency. In some aspects, if the LMF requests the UE to report the normalized PRS load for a particular PFL, N 阈值 = 1 (single sample) and λ 阈值 =1 (load limited), the PFL is considered to be a low-latency PFL.
[0171] The actions that may be taken by the UE in response to determining that the measurement is associated with a low-latency location request may include, but are not limited to, the following actions. In some aspects, when the UE determines or is notified that a particular PFL is a low-latency PFL, the UE may prioritize measurements on that PFL, for example by setting a CSSF PRS,i =1, so that the measurement gap is not shared with the RRM measurement. In some aspects, the UE may process a smaller number of samples than the fixed value of four that is usually mandated by the specification. In some aspects, the UE may use a smaller number of Rx beams to measure resources. The network-based method and the UE-based method may be used together or separately.
[0172] Fig.11 1 is a flow chart of an example process 1100 associated with UE processing load-aware PRS measurement period optimization according to aspects of the present disclosure. In some specific implementations, Fig.11 One or more process blocks of may be performed by a network entity (location server 172, LMF 270, etc.). In some specific implementations, Fig.11 One or more process blocks of may be performed by another device or a group of devices separate from or including the network entity. Additionally or alternatively, Fig.11 One or more process blocks may be performed by one or more components of the network entity 306, such as the processor 394, the memory 396, the network transceiver 390, and the positioning module 398, any or all of which may be components for performing the operations of process 1100.
[0173] like Fig.11As shown, process 1100 may include determining at block 1110 that a positioning reference signal (PRS) processing load for a UE (i.e., how many PRS resources the UE is required to measure) exceeds the PRS processing capability of the UE (i.e., the UE's ability to process PRS in real time without additional delay). If the PRS processing load exceeds the PRS processing capability, the UE will still process all data, but will not be able to do so once the data becomes available over the air interface. Processing the data as soon as it is available should be beneficial for low-latency positioning. Means for performing the operations of block 1110 may include a processor 394, a memory 396, or a network transceiver 390 of a network entity 306. For example, in some aspects, determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE includes: receiving capability information associated with the PRS processing capability of the UE from the UE; and determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information. The network entity 306 may receive the information via the network transceiver 390 and determine, using the processor 394, that the PRS processing load for the UE exceeds the PRS processing capability of the UE.
[0174] In some aspects, receiving capability information associated with a PRS processing capability of the UE includes receiving at least one of: a first duration N of PRS symbols that can be processed per second duration T, or a third number N' of PRS resources that the UE can process during a time slot. In some aspects, determining that a PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information includes calculating a PRS processing load factor based on a maximum number of PRS resources per time slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE. In some aspects, determining that a PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information includes determining that the PRS processing load factor exceeds a first threshold.
[0175] like Fig.11As further shown, process 1100 may include transmitting to the UE, at block 1120, assistance data that reduces a PRS processing load for the UE. Means for performing the operations of block 1120 may include processor 394, memory 396, or network transceiver 390 of network entity 306. For example, the assistance data may be transmitted to the UE via network transceiver 390. In some aspects, transmitting to the UE assistance data that reduces a PRS processing load for the UE includes transmitting assistance data that: reduces a number of positioning frequency layers (PFLs) that the UE is requested to monitor, reduces a number of PRS resources per time slot, reduces a duration of a PRS in each measurement gap, aligns a measurement gap periodicity and a PRS periodicity with a processing time T for each PFL, and reduces a PRS processing load for each PFL. i Match, T 可用 With T for each PFL i matches, or a combination of them.
[0176] In some aspects, process 1100 includes transmitting a location request to the UE, the location request indicating a reduced number of samples to collect for each PRS resource.In some aspects, the network entity includes a location server, a base station, or a combination thereof.
[0177] Process 1100 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Fig.11 An example block diagram of process 1100 is shown, but in some implementations, process 1100 may include Fig.11 The process 1100 may include more boxes, fewer boxes, different boxes, or boxes arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more boxes in the boxes of the process 1100 may be executed in parallel.
[0178] Fig.12 1 is a flow chart of an example process 1200 associated with UE processing load-aware PRS measurement period optimization according to aspects of the present disclosure. In some implementations, Fig.12 One or more process blocks of may be performed by a user equipment (UE) (e.g., UE 104). In some implementations, Fig.12 One or more process blocks of may be performed by another device or a group of devices separate from or including the NE. Additionally or alternatively, Fig.12One or more process blocks of process 1200 may be performed by one or more components of UE 302, such as processor 332, memory 340, WWAN transceiver 310, short-range wireless transceiver 320, satellite signal receiver 330, sensor 344, user interface 346, and positioning module 342, any or all of which may be components for performing the operations of process 1200.
[0179] like Fig.12 As shown, process 1200 may include determining, at block 1210, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements are associated with a low latency location request. Means for performing the operations of block 1210 may include a processor 332, a memory 340, or a WWAN transceiver 310 of the UE 302. For example, the UE 302 may use the processor 332 to determine that one or more positioning reference signal (PRS) measurements are associated with a low latency location request. In some aspects, determining that one or more PRS measurements are associated with a low latency location request includes determining that a positioning frequency layer (PFL) in which one or more PRS measurements are to be performed is a low latency PFL.
[0180] In some aspects, determining that a PFL in which one or more PRS measurements are to be made is a low-latency PFL includes: receiving an indication from a network entity that the PFL is a low-latency PFL. In some aspects, determining that the one or more PRS measurements are associated with a low-latency location request includes: receiving assistance data from the network entity that causes a PRS processing load for the UE to not exceed a PRS processing capability of the UE. In some aspects, receiving assistance data that causes a PRS processing load for the UE to not exceed the PRS processing capability of the UE includes receiving assistance data that: reduces the number of positioning frequency layers (PFLs) that the UE is requested to monitor, reduces the number of PRS resources per time slot, reduces the duration of the PRS in each measurement gap, and aligns the measurement gap periodicity and the PRS periodicity with the processing time T for each PFL. i Match, T 可用 With T for each PFL i In some aspects, determining that one or more PRS measurements are associated with a low-latency location request based on information received from a network entity includes: receiving a location request from the network entity, the location request indicating a reduced number of samples to be collected for each PRS resource. In some aspects, the network entity includes a location server, a base station, or a combination thereof.
[0181] like Fig.12As further shown, process 1200 may include, at block 1220, modifying one or more parameters associated with one or more PRS measurements to reduce measurement latency. Means for performing the operations of block 1220 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may use processor 332 to modify one or more parameters associated with one or more PRS measurements to reduce measurement latency. In some aspects, modifying one or more parameters associated with one or more PRS measurements to reduce measurement latency includes setting a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements, reducing a receive beam scanning factor, or a combination thereof.
[0182] like Fig.12 As further shown, process 1200 may include performing one or more PRS measurements associated with the low latency location request in accordance with the modified one or more parameters at block 1230. Means for performing the operations of block 1230 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may use WWAN transceiver 310 to perform one or more PRS measurements associated with the low latency location request in accordance with the modified one or more parameters.
[0183] Process 1200 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Fig.12 An example block diagram of process 1200 is shown, but in some implementations, process 1200 may include Fig.12 The process 1200 may include more boxes, fewer boxes, different boxes, or boxes arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more boxes in the boxes of process 1200 may be executed in parallel.
[0184] It should be appreciated that the technical advantage of methods 1100 and 1200 is that they allow the network and the UE to respectively optimize parameters associated with positioning measurements for low-latency positioning scenarios. Method 1100 provides a mechanism by which the network can adjust measurement parameters based on the specific capabilities of the UE. Method 1200 provides a mechanism by which the UE can optimize its own operating conditions to achieve low-latency measurement and reporting.
[0185] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause can refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. The various aspects disclosed herein explicitly include these combinations, unless it is explicitly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
[0186] Specific implementation examples are described in the following numbered clauses:
[0187] Clause 1. A method of wireless positioning performed by a network entity, the method comprising: determining that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capability of the UE; and transmitting to the UE assistance data that reduces the PRS processing load for the UE.
[0188] Clause 2. A method according to Clause 1, wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE includes: receiving capability information associated with the PRS processing capability of the UE from the UE; and determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information.
[0189] Clause 3. A method according to clause 2, wherein receiving the capability information associated with the PRS processing capability of the UE includes receiving at least one of the following: a first duration N of PRS symbols that can be processed per second duration T; or a third number N' of PRS resources that the UE can process during a time slot.
[0190] Clause 4. A method according to any one of clauses 2 to 3, wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information includes: calculating a PRS processing load factor based on a maximum number of PRS resources per time slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE.
[0191] Clause 5. The method of clause 4, wherein determining, based on the capability information, that the PRS processing load for the UE exceeds the PRS processing capability of the UE comprises determining that the PRS processing load factor exceeds a first threshold.
[0192] Clause 6. A method according to any one of clauses 1 to 5, wherein transmitting auxiliary data to the UE to reduce the PRS processing load for the UE includes transmitting auxiliary data, wherein the auxiliary data: reduces the number of positioning frequency layers (PFLs) that the UE is requested to monitor; reduces the number of PRS resources per time slot; reduces the duration of the PRS in each measurement gap; increases the period of the PRS resources within the measurement gap for each PFL; matches the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; or a combination thereof.
[0193] Clause 7. The method according to any one of clauses 1 to 6 further comprises: transmitting a location request to the UE, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
[0194] Clause 8. A method for wireless positioning performed by a user equipment (UE), the method comprising: determining one or more positioning reference signal (PRS) measurements associated with a low-latency location request based on information received from a network entity; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and performing the one or more PRS measurements associated with the low-latency location request based on the modified one or more parameters.
[0195] Clause 9. The method of clause 8, wherein determining that the one or more PRS measurements are associated with a low-latency location request comprises determining that a positioning frequency layer (PFL) in which the one or more PRS measurements are to be made is a low-latency PFL.
[0196] Clause 10. The method of clause 9, wherein determining that the PFL in which the one or more PRS measurements are to be made is a low-latency PFL comprises receiving an indication from the network entity that the PFL is a low-latency PFL.
[0197] Clause 11. A method according to any one of clauses 8 to 10, wherein determining that the one or more PRS measurements are associated with a low-latency location request includes: receiving auxiliary data from the network entity so that the PRS processing load for the UE does not exceed the PRS processing capability of the UE.
[0198] Clause 12. A method according to clause 11, wherein receiving the auxiliary data so that the PRS processing load for the UE does not exceed the PRS processing capability of the UE includes receiving auxiliary data, wherein the auxiliary data: reduces the number of positioning frequency layers (PFLs) that the UE is requested to monitor; reduces the number of PRS resources per time slot; reduces the duration of the PRS in each measurement gap; increases the period of the PRS resources within the measurement gap for each PFL; matches the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; or a combination thereof.
[0199] Clause 13. A method according to any one of clauses 8 to 12, wherein determining that the one or more PRS measurements are associated with a low-latency location request based on the information received from the network entity includes: receiving a location request from the network entity, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
[0200] Clause 14. A method according to any one of clauses 8 to 13, wherein modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency comprises: setting a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; reducing a receive beam scanning factor; or a combination thereof.
[0201] Clause 15. A network entity comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine that a positioning reference signal (PRS) processing load for a UE exceeds a PRS processing capability of the UE; and transmit, via the at least one transceiver, to the UE assistance data that reduces the PRS processing load for the UE.
[0202] Clause 16. A network entity according to clause 15, wherein in order to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE, the at least one processor is configured to: receive capability information associated with the PRS processing capability of the UE from the UE via the at least one transceiver; and determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information.
[0203] Clause 17. A network entity according to clause 16, wherein in order to receive the capability information associated with the PRS processing capability of the UE, the at least one processor is configured to receive at least one of the following: a first duration N of PRS symbols that can be processed per second duration T; or a third number N' of PRS resources that the UE can process during a time slot.
[0204] Clause 18. A network entity according to any of clauses 16 to 17, wherein in order to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information, the at least one processor is configured to: calculate a PRS processing load factor based on a maximum number of PRS resources per time slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE.
[0205] Clause 19. A network entity according to clause 18, wherein in order to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information, the at least one processor is configured to: determine that the PRS processing load factor exceeds a first threshold.
[0206] Clause 20. A network entity according to any one of clauses 15 to 19, wherein in order to transmit auxiliary data to the UE to reduce the PRS processing load for the UE, the at least one processor is configured to transmit auxiliary data, wherein the auxiliary data: reduces the number of positioning frequency layers (PFLs) that the UE is requested to monitor; reduces the number of PRS resources per time slot; reduces the duration of PRS in each measurement gap; increases the period of PRS resources within the measurement gap for each PFL; matches the measurement gap periodicity and PRS periodicity with the processing time of PRS symbols for each PFL; or a combination thereof.
[0207] Clause 21. A network entity according to any one of clauses 15 to 20, wherein the at least one processor is further configured to: transmit a location request to the UE via the at least one transceiver, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
[0208] Clause 22. A network entity as recited in any one of Clauses 15 to 21, wherein the network entity comprises a location server, a base station, or a combination thereof.
[0209] Clause 23. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements are associated with a low-latency location request; modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and perform the one or more PRS measurements associated with the low-latency location request based on the modified one or more parameters.
[0210] Clause 24. A UE according to clause 23, wherein in order to determine that the one or more PRS measurements are associated with a low-latency location request, the at least one processor is configured to: determine that the positioning frequency layer (PFL) in which the one or more PRS measurements are to be performed is a low-latency PFL.
[0211] Clause 25. A UE according to clause 24, wherein in order to determine that the PFL in which the one or more PRS measurements are to be performed is a low-latency PFL, the at least one processor is configured to: receive an indication from the network entity that the PFL is a low-latency PFL.
[0212] Clause 26. A UE according to any one of clauses 23 to 25, wherein in order to determine that the one or more PRS measurements are associated with a low-latency location request, the at least one processor is configured to: receive auxiliary data from the network entity so that the PRS processing load for the UE does not exceed the PRS processing capability of the UE.
[0213] Clause 27. A UE according to clause 26, wherein in order to receive the auxiliary data so that the PRS processing load for the UE does not exceed the PRS processing capability of the UE, the at least one processor is configured to receive the auxiliary data, wherein the auxiliary data: reduces the number of positioning frequency layers (PFLs) that the UE is requested to monitor; reduces the number of PRS resources per time slot; reduces the duration of the PRS in each measurement gap; increases the period of the PRS resources within the measurement gap for each PFL; matches the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; or a combination thereof.
[0214] Clause 28. A UE according to any one of clauses 23 to 27, wherein in order to determine that the one or more PRS measurements are associated with a low-latency location request based on the information received from the network entity, the at least one processor is configured to: receive a location request from the network entity, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
[0215] Clause 29. A UE according to any one of clauses 23 to 28, wherein in order to modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency, the at least one processor is configured to: set a carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; reduce a receive beam scanning factor; or a combination thereof.
[0216] Clause 30. A UE as set forth in any of clauses 23 to 29, wherein the network entity comprises a location server, a base station, or a combination thereof.
[0217] Clause 31. An apparatus comprising: a memory; a transceiver; and a processor, the processor being communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor being configured to perform the method of any one of clauses 1 to 14.
[0218] Clause 32. An apparatus comprising means for performing the method of any one of clauses 1 to 14.
[0219] Clause 33. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising at least one instruction for causing a computer or a processor to perform the method according to any one of clauses 1 to 14.
[0220] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0221] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits and steps have been generally described in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0222] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.
[0223] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.
[0224] In one or more example aspects, the function can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, and the communication media include any media that facilitates the computer program to be transported from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices, or can be used in the form of instructions or data structures or to store desired program codes and any other media that can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of the medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0225] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure as described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.
Claims
1. A method for wireless positioning performed by a network entity, the method comprising: determining that a positioning reference signal (PRS) processing load for a user equipment (UE) exceeds a PRS processing capability of the UE; as well as Assistance data is transmitted to the UE that reduces the PRS processing load for the UE.
2. The method of claim 1 , wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE comprises: receiving, from the UE, capability information associated with the PRS processing capability of the UE; as well as A determination is made based on the capability information that the PRS processing load for the UE exceeds the PRS processing capability of the UE.
3. The method of claim 2, wherein receiving the capability information associated with the PRS processing capability of the UE comprises receiving at least one of: A first duration N of a PRS symbol that can be processed per second duration T; or A third number N' of PRS resources that can be processed during a time slot.
4. The method of claim 2, wherein determining, based on the capability information, that the PRS processing load for the UE exceeds the PRS processing capability of the UE comprises: A PRS processing load factor is calculated based on a maximum number of PRS resources per time slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE.
5. The method of claim 4, wherein determining that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information comprises: It is determined that the PRS processing load factor exceeds a first threshold.
6. The method of claim 1 , wherein transmitting to the UE assistance data that reduces the PRS processing load for the UE comprises transmitting assistance data, the assistance data: reducing the number of positioning frequency layers (PFLs) that the UE is requested to monitor; Reduce the number of PRS resources per time slot; Reduce the duration of the PRS in each measurement gap; Increasing a period of a PRS resource within the measurement gap for each PFL; Matching the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; Or a combination of these.
7. The method according to claim 1, further comprising: A location request is transmitted to the UE, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
8. A method of wireless positioning performed by a user equipment (UE), the method comprising: determining, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements are associated with the low latency location request; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; as well as The one or more PRS measurements associated with the low-latency location request are performed according to the modified one or more parameters.
9. The method of claim 8, wherein determining that the one or more PRS measurements are associated with a low-latency location request comprises: A positioning frequency layer (PFL) in which the one or more PRS measurements are to be made is determined to be a low-latency PFL.
10. The method of claim 9, wherein determining that the PFL in which the one or more PRS measurements are to be made is a low-latency PFL comprises: An indication is received from the network entity that the PFL is a low-latency PFL.
11. The method of claim 8, wherein determining that the one or more PRS measurements are associated with a low-latency location request comprises: Receive assistance data from the network entity such that a PRS processing load for the UE does not exceed a PRS processing capability of the UE.
12. The method of claim 11, wherein receiving the assistance data such that the PRS processing load for the UE does not exceed the PRS processing capability of the UE comprises receiving assistance data, the assistance data: reducing the number of positioning frequency layers (PFLs) that the UE is requested to monitor; Reduce the number of PRS resources per time slot; Reduce the duration of the PRS in each measurement gap; Increasing a period of a PRS resource within the measurement gap for each PFL; Matching the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; Or a combination of these.
13. The method of claim 8, wherein determining, based on the information received from the network entity, that the one or more PRS measurements are associated with a low-latency location request comprises: A location request is received from a network entity, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
14. The method of claim 8, wherein modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency comprises: Setting the carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; Reduce the receive beam scanning factor; Or a combination of these.
15. A network entity, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determining that a positioning reference signal (PRS) processing load for a user equipment (UE) exceeds a PRS processing capability of the UE; and Assistance data that reduces the PRS processing load for the UE is transmitted to the UE via the at least one transceiver.
16. The network entity of claim 15, wherein to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE, the at least one processor is configured to: receiving, from the UE via the at least one transceiver, capability information associated with the PRS processing capability of the UE; and A determination is made based on the capability information that the PRS processing load for the UE exceeds the PRS processing capability of the UE.
17. The network entity of claim 16, wherein to receive the capability information associated with the PRS processing capability of the UE, the at least one processor is configured to receive at least one of: A first duration N of a PRS symbol that can be processed per second duration T; or A third number N' of PRS resources that can be processed during a time slot.
18. The network entity of claim 16, wherein to determine that the PRS processing load for the UE exceeds the PRS processing capability of the UE based on the capability information, the at least one processor is configured to calculate a PRS processing load factor based on a maximum number of PRS resources per time slot in a positioning frequency layer (PFL), a periodicity of PRS resources available within a measurement gap for the PFL, a duration of PRS resources available in the PFL, and the capability information associated with the PRS processing capability of the UE.
19. The network entity of claim 18, wherein to determine, based on the capability information, that the PRS processing load for the UE exceeds the PRS processing capability of the UE, the at least one processor is configured to determine that the PRS processing load factor exceeds a first threshold.
20. The network entity of claim 15, wherein to transmit to the UE assistance data that reduces the PRS processing load for the UE, the at least one processor is configured to transmit assistance data, the assistance data: reducing the number of positioning frequency layers (PFLs) that the UE is requested to monitor; Reduce the number of PRS resources per time slot; Reduce the duration of the PRS in each measurement gap; Increasing a period of a PRS resource within the measurement gap for each PFL; Matching the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; Or a combination of these.
21. The network entity of claim 15, wherein the at least one processor is further configured to: A location request is transmitted to the UE via the at least one transceiver, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
22. The network entity of claim 15, wherein the network entity comprises a location server, a base station, or a combination thereof.
23. A user equipment (UE), comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determining, based on information received from a network entity, that one or more positioning reference signal (PRS) measurements are associated with the low latency location request; modifying one or more parameters associated with the one or more PRS measurements to reduce measurement latency; and The one or more PRS measurements associated with the low-latency location request are performed according to the modified one or more parameters.
24. The UE of claim 23, wherein in order to determine that the one or more PRS measurements are associated with a low-latency location request, the at least one processor is configured to: determine that a positioning frequency layer (PFL) in which the one or more PRS measurements are to be performed is a low-latency PFL.
25. The UE of claim 24, wherein in order to determine that the PFL in which the one or more PRS measurements are to be performed is a low-latency PFL, the at least one processor is configured to: receive an indication from the network entity that the PFL is a low-latency PFL.
26. The UE of claim 23, wherein, in order to determine that the one or more PRS measurements are associated with a low-latency location request, the at least one processor is configured to: receive auxiliary data from the network entity so that the PRS processing load for the UE does not exceed the PRS processing capability of the UE.
27. The UE of claim 26, wherein in order to receive the assistance data such that a PRS processing load for the UE does not exceed a PRS processing capability of the UE, the at least one processor is configured to receive assistance data, the assistance data: reducing the number of positioning frequency layers (PFLs) that the UE is requested to monitor; Reduce the number of PRS resources per time slot; Reduce the duration of the PRS in each measurement gap; Increasing a period of a PRS resource within the measurement gap for each PFL; Matching the measurement gap periodicity and the PRS periodicity with the processing time of the PRS symbols for each PFL; Or a combination of these.
28. A UE according to claim 23, wherein in order to determine that the one or more PRS measurements are associated with a low-latency location request based on the information received from the network entity, the at least one processor is configured to: receive a location request from the network entity, the location request indicating a reduced number of samples to be collected for each PRS resource, a reduced receive beam scanning factor, or a combination thereof.
29. The UE of claim 23, wherein to modify one or more parameters associated with the one or more PRS measurements to reduce measurement latency, the at least one processor is configured to: Setting the carrier-specific scaling factor (CSSF) to avoid sharing measurement gaps with other measurements; Reduce the receive beam scanning factor; Or a combination of these.
30. The UE of claim 23, wherein the network entity comprises a location server, a base station, or a combination thereof.
