Configuration details for autonomous gaps for positioning

Abstract

Techniques for wireless positioning are disclosed. In an aspect, a user equipment (UE) obtains one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both being defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a time period during which the UE prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and reports the one or more positioning measurements to a positioning entity to enable the positioning entity to determine a location of the UE.

Description

[0001] Public background

[0002] I. Open Domain

[0003] The various aspects of this disclosure generally relate to wireless communications.

[0004] 2. Relevant Technical Descriptions

[0005] Wireless communication systems have undergone several generations of development, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data radio service with Internet capabilities, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc.

[0006] The fifth-generation (5G) wireless standard (known as New Radio (NR)) demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard is designed to provide tens of megabits per second (Mbps) of data rate to each of tens of thousands of users, and 1 gigabits per second (Gbps) to dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, 5G mobile communication should have significantly improved spectral efficiency compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency significantly reduced compared to the current standard.

[0007] Overview

[0008] The following is a simplified overview relating to one or more aspects disclosed herein. Therefore, this overview should not be considered an exhaustive overview relating to all aspects of the conception, nor should it be considered to identify key or decisive elements relating to all aspects of the conception or to depict the scope associated with any particular aspect. Accordingly, the sole purpose of the following overview is to present, in a simplified form, certain concepts relating to one or more aspects of the mechanism disclosed herein before the detailed description given below.

[0009] In one aspect, a wireless positioning method performed by a user equipment (UE) includes: acquiring one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both being defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period during which the UE prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and reporting the one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0010] In one aspect, a positioning method performed by a location server includes: transmitting to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a time period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receiving from the UE a measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and determining the location of the UE based on the one or more positioning measurements.

[0011] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: acquire one or more positioning measurements of one or more Positioning Reference Signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both being defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period of time during which the UE prioritizes at least the reception and processing of PRS over the reception, processing, or both of other downlink signals and channels; and report one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0012] In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit via the at least one transceiver one or more autonomous gap configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period of time during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receive via the at least one transceiver a measurement report from the UE, the measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and determine the location of the UE based on the one or more positioning measurements.

[0013] In one aspect, a user equipment (UE) includes: means for acquiring one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both being defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period of time during which the UE prioritizes at least the reception and processing of PRS over the reception, processing, or both of other downlink signals and channels; and means for reporting one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0014] In one aspect, a location server includes: means for transmitting to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period of time during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; means for receiving a measurement report from the UE, the measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and means for determining the location of the UE based on the one or more positioning measurements.

[0015] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: acquire one or more positioning measurements of one or more Positioning Reference Signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both, defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period during which the UE at least prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and report one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0016] In one aspect, a non-transient computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: transmit to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within that autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receive from the UE a measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and determine the location of the UE based on the one or more positioning measurements.

[0017] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. Brief description of the attached diagram

[0019] The accompanying drawings are provided to help describe various aspects of this disclosure, and the drawings are provided for illustrative purposes only and not for limiting the aspects.

[0020] Figure 1 Example wireless communication systems based on various aspects of this disclosure are explained.

[0021] Figure 2A and 2B Example wireless network architectures based on various aspects of this disclosure are explained.

[0022] Figure 3A , 3B The 3C and 3C are simplified block diagrams of several exemplary aspects of components that can be adopted in user equipment (UE), base stations, and network entities and configured to support communications as taught herein.

[0023] Figure 4An example Long Term Evolution (LTE) Location Protocol (LPP) call flow between the UE and the location server for performing location operations is explained.

[0024] Figure 5 This is a diagram illustrating example frame structures based on various aspects of this disclosure.

[0025] Figure 6 This is a diagram illustrating an example PRS configuration for the transmission of a Position Reference Signal (PRS) for a given base station, according to various aspects of this disclosure.

[0026] Figure 7 This is a diagram illustrating various downlink channels within example downlink time slots according to various aspects of this disclosure.

[0027] Figure 8 This is a diagram illustrating the Cell Global Identifier (CGI) reading procedure according to various aspects of this disclosure.

[0028] Figure 9 This is a diagram illustrating an example downlink PRS measurement scenario based on various aspects of this disclosure.

[0029] Figure 10 This is a diagram illustrating an example downlink PRS transmission, processing, and reporting loop for multiple UEs according to various aspects of this disclosure.

[0030] Figure 11 This is a diagram illustrating an example downlink PRS transmission, processing, and reporting loop for a UE (where the UE has been configured to have disjoint processing gaps) according to various aspects of this disclosure.

[0031] Figure 12 This is a diagram illustrating an example downlink PRS transmission, processing, and reporting loop for a UE (where the UE has been configured to transmit uplink signals and channels during processing intervals) according to various aspects of this disclosure.

[0032] Figure 13 This is a diagram illustrating an example PRS measurement procedure utilizing autonomous clearances according to various aspects of this disclosure.

[0033] Figure 14 and 15 The example positioning methods based on various aspects of this disclosure are explained.

[0034] Detailed description

[0035] Various aspects of this disclosure are provided below in the description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of this disclosure. Furthermore, elements well-known in this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0036] The terms “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 superior to or better than the others. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0037] Those skilled in the art will appreciate that the information and signals described below can be represented using any of a variety of different techniques and arts. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof, depending in part on the specific application, in part on the intended design, in part on the corresponding technology, etc.

[0038] Furthermore, many aspects are described in the form of sequences of actions performed by elements of, for example, computing devices. It will be appreciated that the various actions described herein can be performed by special-purpose circuitry (e.g., application-specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be considered to be fully embodied in any form of non-transient computer-readable storage medium storing a corresponding set of computer instructions that, upon execution, will cause an associated processor of the device to perform the functions described herein. Thus, various aspects of this disclosure can be embodied in several different forms, all of which are contemplated to fall within the scope of the claimed subject matter. Furthermore, for each aspect described herein, a corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0039] As used herein, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT) unless otherwise stated. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, consumer asset positioning device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” can be interchangeably referred to as “Access Terminal” or “AT”, “Client Equipment”, “Wireless Equipment”, “Subscriber Equipment”, “Subscriber Terminal”, “Subscriber Station”, “User Terminal” or “UT”, “Mobile Equipment”, “Mobile Terminal”, “Mobile Station”, or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) (e.g., based on the IEEE 802.11 standard), and so on.

[0040] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, B-Node, Evolved B-Node (eNB), Next Generation eNB (ng-eNB), New Radio (NR) B-Node (also referred to as gNB or gNodeB), etc. A base station may primarily be used to support radio access by the UE, including supporting data, voice, and / or signaling connections with the supported UE. In some systems, the base station may provide purely edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can signal to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can signal to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0041] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be a base station antenna corresponding to a cell (or several cell sectors) of the base station. When 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). When 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 via a transmission medium to a shared source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be the serving base station from which the UE receives measurement reports and neighboring base stations where the UE is measuring its reference radio frequency (RF) signal. Since a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmissions from or receptions at a base station should be understood as references to the specific TRP of that base station.

[0042] In some implementations that support UE positioning, the base station may not support the UE's radio access (e.g., it may not support data, voice, and / or signaling connections regarding the UE), but may instead transmit reference signals to the UE for measurement, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning tower (e.g., in the case of transmitting signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring signals from the UE).

[0043] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across 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 RF signal transmitted on different paths between the transmitter and receiver can 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 the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0044] Figure 1An example wireless communication system 100 according to various aspects of this disclosure is described. 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 "BS") and various UEs 104. Base station 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base station may include an eNB and / or an ng-eNB (where the wireless communication system 100 corresponds to an LTE network), or a gNB (where the wireless communication system 100 corresponds to an NR network), or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

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

[0046] In addition to other functions, base station 102 may also perform functions related to one or more of the following: transmitting user data, radio channel cryptography and decoding, 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, location, and delivery of alarm messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) through backhaul link 134 (which may be wired or wireless).

[0047] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can 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 frequency resource, it is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access to different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). Since cells are supported by specific base stations, the term “cell” can refer to either or both of the logical communication entity and the base station supporting that logical communication entity, depending on the context. Additionally, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" are used interchangeably. In some cases, the term "cell" can also refer to the geographical coverage area (e.g., sector) of a base station, in the sense that the carrier frequency can be detected and used for communication within a portion of a geographical coverage area 110.

[0048] While the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in handover areas), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' ("SC" labeled "small cell") may have geographic coverage areas 110' that substantially overlap with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that provide service to a restricted group known as a Closed Subscriber Group (CSG).

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

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

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

[0052] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180, which can operate in mmW and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz and wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to a 3 GHz frequency with a 100 mm wavelength. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can compensate for the extremely high path loss and short range through beamforming (transmit and / or receive) on the mmW communication link 184. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Accordingly, it will be understood that the foregoing explanations are merely illustrative and should not be construed as limiting the aspects disclosed herein.

[0053] Transmit beamforming is a technique for focusing RF signals in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using 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, thus providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (referred to as a "phased array" or "antenna array") that generates a beam of RF waves, which can be "guided" to different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship so that radio waves from the separate antennas add together in the desired direction to increase radiation, while simultaneously canceling each other out in the undesired direction to suppress radiation.

[0054] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., UE) with identical parameters, regardless of whether the network node's 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 of the second reference RF signal on the second beam can be derived from information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

[0055] 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 and / or adjust the phase setting of the antenna array in a specific direction to amplify the RF signal received from that direction (e.g., increase its gain level). Thus, when a receiver is referred to as beamforming in a certain direction, it means that the beam gain in that direction is higher than the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. 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.

[0056] The transmit and receive beams can be spatially correlated. Spatial correlation means that the parameters of the second beam (e.g., transmit or receive beam) used for the second reference signal can be derived from information about the first beam (e.g., receive or transmit beam) of the first reference signal. For example, a UE can 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 can then form a transmit beam based on the parameters of the receive beam to transmit an uplink reference signal (e.g., a probe reference signal (SRS)) to that base station.

[0057] Note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, then the downlink beam is a receive beam for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if a base station is forming an uplink beam, then the uplink beam is an uplink receive beam, while if a UE is forming an uplink beam, then the uplink beam is an uplink transmit beam.

[0058] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise with FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0059] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands of these IF bands as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 into the IF band. Additionally, higher frequency bands are currently being explored to extend 5G NR operation above 52.6 GHz. For example, three higher operating frequency bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0060] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0061] In multi-carrier systems (such as 5G), one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "Scell." In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and on the cell in which 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 shared control channels as well as control channels that vary from UE to UE, and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured once an RRC connection is established between UE 104 and the anchor carrier, and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only necessary signaling information and signals. For example, signaling information and signals that vary from UE to UE may not be present in the secondary carrier, since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Since a “serving cell” (whether PCell or SCell) corresponds to the carrier frequency / component carrier that a base station is using for communication, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc., can be used interchangeably.

[0062] For example, still refer to Figure 1One of the frequencies utilized by the macrocell base station 102 can be an anchor carrier (or "PCell"), and other frequencies utilized by the macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("Scell"). Transmitting and / or receiving on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20MHz aggregated carriers in a multi-carrier system would theoretically result in twice the data rate (i.e., 40MHz) compared to the data rate obtained from a single 20MHz carrier.

[0063] The wireless communication system 100 may further include a UE 164, which can communicate with the macrocell base station 102 via communication link 120 and / or with the mmW base station 180 via mmW communication link 184. For example, the macrocell base station 102 may support 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.

[0064] In some scenarios, UE 164 and UE 182 may be able to perform sidelink communication. A sidelink-capable UE (SL-UE) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via radio sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A radio sidelink (or simply "sidelink") is an adaptation to core cellular (e.g., LTE, NR) standards that allows direct communication between two or more UEs without the need for the communication to pass through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more SL-UEs in a group of SL-UEs utilizing sidelink communication may be within the geographical coverage area 110 of base station 102. Other SL-UEs in this group may be outside the geographical coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each SL-UE transmits to every other SL-UE in the group. In some cases, base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between the SL-UEs without involving base station 102.

[0065] On one hand, the sidelink 160 may operate on a wireless communication medium of interest that may be shared with other vehicles and / or infrastructure access points and other RATs for wireless communication. “Medium” may include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. On another hand, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) of the United States), these systems, particularly those employing small cell access points, have recently extended their operation to unlicensed frequency bands, such as the unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies (most notably the IEEE 802.11xWLAN technology commonly referred to as “Wi-Fi”). Example systems of this type include various variants of CDMA, TDMA, FDMA, Orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), and so on.

[0066] Note that, although Figure 1 Only two of these UEs are referred to as SL-UEs (i.e., UEs 164 and 182), but any UE referred to as such can be an SL-UE. Furthermore, although only UE 182 is described as capable of beamforming, any UE referred to (including UE 164) can be capable of beamforming. When SL-UEs are capable of beamforming, they can beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base stations 102, 180, small cell 102', access point 150), etc. Therefore, in some cases, UEs 164 and 182 can utilize beamforming on sidelink 160.

[0067] exist Figure 1 In the examples, any of the UEs being explained (for simplicity) Figure 1A single UE 104 may receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that can be used by UE 104 as an independent source of location information. Satellite positioning systems typically include transmitter systems (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from these transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While transmitters are typically located in SV 112, they may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 from SV 112 to derive geographic location information.

[0068] In satellite positioning systems, the use of signal 124 can be amplified through various satellite-based augmentation systems (SBAS), which may be associated with or otherwise enabled to work with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Coverage Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted Geographic Augmentation Navigation or GPS and Geographic Augmentation 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.

[0069] On one hand, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In the 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 elements in the 5G network, such as the modified base station 102 (without a ground antenna) or network nodes in the 5GC. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. In this way, UE 104 can receive communication signals (e.g., signal 124) from SV 112 as a replacement or supplement to receiving communication signals from ground base station 102.

[0070] The wireless communication system 100 may further include one or more UEs (such as UE 190) that 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, UE 190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., through which UE 190 indirectly obtains cellular connectivity), and a D2D P2P link 194 with a WLANSTA 152 connected to a WLAN AP 150 (through which UE 190 indirectly obtains WLAN-based Internet connectivity). In one example, D2D P2P links 192 and 194 can use any known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D)). (etc.) to support.

[0071] Figure 2A Example wireless network architecture 200 is explained. For example, 5GC 210 (also known as Next Generation Core (NGC)) can be functionally considered as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), which operate collaboratively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB 222 to 5GC 210, specifically to user plane function 212 and control plane function 214, respectively. In an additional configuration, ng-eNB 224 can also connect to 5GC 210 via NG-C 215 to control plane function 214 and NG-U 213 to user plane function 212. Furthermore, ng-eNB 224 can communicate directly with gNB 222 via 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 ng-eNBs 224 and one or more gNBs 222. The gNB 222 or ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any UE described herein).

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

[0073] Figure 2B Another example wireless network architecture, 250.5GC 260, was explained (which can correspond to...). Figure 2AThe 5GC 210 in the document can be functionally viewed as a control plane function (provided by the Access and Mobility Management Function (AMF) 264) and a user plane function (provided by the User Plane Function (UPF) 262), which operate collaboratively to form the core network (i.e., 5GC 260). The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, session management (SM) message transmission between one or more UEs 204 (e.g., any UE described herein) and session management function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, short message service (SMS) message transmission between UE 204 and short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with the authentication server function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In cases where authentication is based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AMF. The AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF, which it uses to derive a key that varies depending on the access network. The AMF 264's functionality also includes: location service management for regulatory services, location service message transmission between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), location service message transmission between the NG-RAN 220 and the LMF 270, EPS bearer identifier allocation for interoperability with the Evolved Packet System (EPS), and UE 204 mobility event notification. Additionally, the AMF 264 supports functionality for non-3GPP (3rd Generation Partnership Project) access networks.

[0074] The functions of UPF 262 include: acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. UPF 262 may also support the transmission of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

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

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

[0077] Another optional aspect may include a third-party server 274, which can communicate with 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., location estimation) of UE 204. Thus, in some cases, the third-party server 274 may be referred to as a Location Services (LCS) client or an external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

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

[0079] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, positioning, and session management, in addition to those functions specifically allocated to the gNB-DU(228). More specifically, the gNB-CU 226 generally manages the radio resource control (RRC), serving data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) of the gNB 222. The gNB-DU 228 is a logical node that generally manages the radio link control (RLC) and media 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, while a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1 interface". The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Thus, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0080] Figure 3A , Figure 3B and Figure 3C The description includes UE 302 (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 UE 302). Figure 2A and 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as private networks) depicted herein support file transfer operations as taught herein. It will be appreciated that these components may be implemented in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.) in different implementations. The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, 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.

[0081] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, to provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for suppressing transmission, 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 for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB)) over a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum) via at least one designated RAT (e.g., NR, LTE, GSM, etc.). WWAN transceivers 310 and 350 can be configured, according to a specified RAT, in various ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and each includes one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0082] In at least some cases, UE 302 and base station 304 each further include one or more short-range radio transceivers 320 and 360, respectively. The short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access via at least one designated RAT (e.g., WiFi, LTE-D, etc.). A means for communicating with other network nodes (such as other UEs, access points, base stations, etc.) over a wireless communication medium of interest (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for suppressing transmission, etc.) using PC5, Dedicated Short Range Communication (DSRC), Wireless Access in Vehicle Environments (WAVE), Near Field Communication (NFC), etc.). Short-range transceivers 320 and 360 can be configured, according to a specified RAT, in various ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, short-range transceivers 320 and 360 each include one or more transmitters 324 and 364 for transmitting 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 specific examples, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, transceiver and / or Transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0083] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may be provided with means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. When satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals originating from a 5G network (e.g., carrying control and / or user data). 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 information and operations from other systems as appropriate, and in at least some cases perform calculations to determine the respective locations of UE 302 and base station 304 using measurements obtained by any suitable satellite positioning system algorithm.

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

[0085] Transceivers can be configured to communicate over wired or wireless links. A transceiver (whether wired or wireless) includes a transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and a receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter and receiver circuitry in a single device), in some implementations it may include separate transmitter and receiver circuitry, or in other implementations it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., in some implementations, network transceivers 380 and 390) may be coupled to one or more wired network interface ports. 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 permit the corresponding device (e.g., UE 302, base station 304) to perform transmit beamforming as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which permit the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or transmit at a given time, rather than both simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

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

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

[0088] UE 302, base station 304, and network entity 306 include memory circuitry that respectively implements memories 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 storage, means for retrieval, means for maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may respectively include positioning components 342, 388, and 398. Positioning components 342, 388, and 398 may be hardware circuitry as part of or coupled to processors 332, 384, and 394, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other respects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A The possible locations of the positioning component 342 are described. The positioning component 342 may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a self-contained component. Figure 3BThe possible locations of the positioning component 388 are explained. The positioning component 388 may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a self-contained component. Figure 3C The possible locations of the positioning component 398 are explained. The positioning component 398 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 self-contained component.

[0089] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide means for sensing or detecting motion 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. As an example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, 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 multi-axis accelerometers and orientation sensors to provide the ability to calculate position in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

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

[0091] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 may be provided to processor 384. One or more processors 384 may implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide RRC layer functionality associated with system information (e.g., Master Information Block (MIB), System Information Block (SIB)) broadcasting, 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 (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer PDU delivery, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel priority ordering.

[0092] Transmitter 354 and receiver 352 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) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can 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 domains, and subsequently combined 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 precoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from reference signals transmitted by UE 302 and / or channel condition feedback. Each spatial stream can then be provided to one or more different antennas 356. Transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0093] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on this information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. Symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 304. These soft decisions can be based on a channel estimate calculated by a channel estimator. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base station 304 over the physical channel. This data and control signals are then provided to one or more processors 332 that implement Layer 3 (L3) and Layer 2 (L2) functionality.

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

[0095] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 provide RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority ordering.

[0096] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0097] Uplink transmissions are handled at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides that information to one or more processors 384.

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

[0099] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3C The text is shown as including various components that can be configured according to the various examples described herein. However, it will be understood that the components described may have different functionalities in different designs. Specifically, Figures 3A to 3C The various components are optional in the replacement configuration, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In this scenario, a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, PCs, or laptops may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or short-range wireless transceiver 320 (e.g., cellular only), or satellite signal receiver 330, or sensor 344, etc. In another example, in Figure 3B In such cases, a particular implementation of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite receiver 370, etc. For the sake of brevity, explanations of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0100] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other on data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are implemented in the same device (e.g., gNB and location server functionality are incorporated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

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

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

[0103] NR supports several cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, the UE measures the difference between the times of arrival (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurements) and reports these differences to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and the RSTD measurements, the positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0104] For DL-AoD positioning, the positioning entity uses beam reports from the UE regarding received signal strength measurements of multiple downlink transmitted beams to determine the angles between the UE and the transmitting base stations(s). The positioning entity can then estimate the UE's location based on the determined angles and the known locations of the transmitting base stations(s).

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

[0106] Downlink and uplink-based positioning methods include Enhanced Cellular ID (E-CID) positioning and Multiple Round-Trip Time (RTT) positioning (also known as "Multi-Cellular RTT" and "Multi-RTT"). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the receive-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest subframe boundary of the received signal and the transmitted signal. Two entities can then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (i.e., RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can send its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) such that the location of the first entity can be determined based on the distance to the second entities and the known location of the second entities (e.g., using polygonal measurements). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy.

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

[0108] To assist in the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, auxiliary data may include: the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive positioning subframes, the periodicity of the positioning subframes, the silence sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes without using auxiliary data.

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

[0110] Location estimation can be referred to by other names, such as location estimate, location, positioning, location lock, lock, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible elevation), or it can be municipal and include street addresses, postal addresses, or some other verbal description of location. Location estimation can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimation can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to be included with a specified or default confidence level).

[0111] Figure 4 This section explains an example Long Term Evolution (LTE) Location Protocol (LPP) procedure 400 used by the UE 404 and the location server (explained as Location Management Function (LMF) 470) to perform location operations. For example... Figure 4As explained, the location of UE 404 is supported by the exchange of LPP messages between UE 404 and LMF 470. LPP messages can be exchanged between UE 404 and LMF 470 via the serving base station of UE 404 (explained as serving gNB 402) and the core network (not shown). LPP procedure 400 can be used to locate UE 404 to support various location-related services, such as navigation for UE 404 (or its user), routing, providing the accurate location of the PSAP associated with an emergency call from UE 404 to a Public Safety Answering Point (PSAP), or for some other reason. LPP procedure 400 may also be referred to as a location session, and multiple location sessions may exist for different types of location methods (e.g., Downlink Time Difference of Arrival (DL-TDOA), Round Trip Time (RTT), Enhanced Cellular Identity (E-CID), etc.).

[0112] Initially, in phase 410, UE 404 may receive a request for its positioning capabilities from LMF 470 (e.g., an LPP request capability message). In phase 420, UE 404 provides its positioning capabilities relative to the LPP protocol to LMF 470 by sending an LPP provide capability message instructing UE 404 to use positioning methods supported by LPP and the characteristics of those positioning methods. In some aspects, the capabilities indicated in the LPP provide capability message may indicate the positioning types supported by UE 404 (e.g., DL-TDOA, RTT, E-CID, etc.) and may indicate the capabilities of those positioning types that UE 404 supports.

[0113] Upon receiving the LPP provision capability message, in phase 420, LMF 470 determines the specific type of positioning method to use (e.g., DL-TDOA, RTT, E-CID, etc.) based on the positioning types supported by the indicated UE 404, and identifies a set containing one or more Transmit-Receive Points (TRPs). UE 404 will either measure downlink positioning reference signals from this set containing one or more TRPs, or UE 404 will transmit uplink positioning reference signals to this set containing one or more TRPs. In phase 430, LMF 470 sends an LPP provision assistance data message identifying the TRP set to UE 404.

[0114] In some implementations, in response to an LPP request auxiliary data message sent by UE 404 to LMF 470 ( Figure 4(Not shown in the diagram), at stage 430, the LPP Request for Assisted Data Message can be sent from LMF 470 to UE 404. The LPP Request for Assisted Data Message may include the identifier of UE 404's serving TRP and a request for the configuration of Positioning Reference Signals (PRS) for adjacent TRPs.

[0115] In phase 440, LMF 470 sends a request for location information to UE 404. This request can be an LPP request for location information message. This message typically includes information elements defining the type of location information, the expected location estimation accuracy, and the response time (i.e., the expected latency). Note that low latency requirements allow for longer response times, while high latency requirements demand shorter response times. However, long response times are referred to as high latency, and short response times are referred to as low latency.

[0116] Note that in some implementations, the LPP Assistance Data Message sent at phase 430 can be sent after the LPP Request Location Information Message at phase 440. For example, if UE 404 receives a request for location information at phase 440 and then sends a request for assistance data to LMF 470 (e.g., in the LPP Request Assistance Data Message, not in...), Figure 4 (As shown in the image) that can be done.

[0117] At stage 450, UE 404 uses the auxiliary information received at stage 430 and any additional data received at stage 440 (e.g., desired location accuracy or maximum response time) to perform positioning operations for the selected positioning method (e.g., measurement of DL-PRS, transmission of UL-PRS, etc.).

[0118] At stage 460, UE 404 may send an LPP (Location Provided by Provider) message to LMF 470, which conveys the results of any measurements (e.g., Time of Arrival (ToA), Reference Signal Time Difference (RSTD), Received Transmission (Rx-Tx), etc.) obtained before or at the expiration of any maximum response time at stage 450 (e.g., the maximum response time provided by LMF 470 at stage 440). The LPP message at stage 460 may also include one or more times when the positioning measurements were obtained and the identity of the TRP(s) from which the positioning measurements were obtained. Note that the time between the request for location information at 440 and the response at 460 is the "response time" and indicates the waiting time of the positioning session.

[0119] LMF 470 uses appropriate positioning techniques (e.g., DL-TDOA, RTT, E-CID, etc.) to calculate the estimated location of UE404, based at least in part on measurements received in the LPP location information message at stage 460.

[0120] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 5 Figure 500 illustrates an example frame structure according to various aspects of this disclosure. This frame structure can be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0121] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as frequency modulation, frequency slots, etc. Each subcarrier can be modulated with data. Generally, modulation symbols are transmitted in the frequency domain for OFDM and in the time domain for 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 subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0122] LTE supports single-parameter design (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR supports multiple parameter designs (μ), for example, subcarrier spacings of 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger can be available. Within each subcarrier spacing, there are 14 symbols per time slot. For a 15kHz SCS (μ=0), there is one time slot per subframe, 10 time slots per frame, a time slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (μs), and a maximum nominal system bandwidth (in MHz) of 4K FFT size is 50. For a 30kHz SCS (μ=1), there are two time slots per subframe, 20 time slots per frame, a time slot duration of 0.5ms, a symbol duration of 33.3μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size of 100. For a 60kHz SCS (μ=2), there are four time slots per subframe, 40 time slots per frame, a time slot duration of 0.25ms, a symbol duration of 16.7μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size of 200. For a 120kHz SCS (μ=3), there are eight time slots per subframe, 80 time slots per frame, a time slot duration of 0.125ms, a symbol duration of 8.33μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size of 400. For a 240kHz SCS (μ=4), there are 16 time slots per subframe and 160 time slots per frame. The time 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.

[0123] exist Figure 5 In the example, a 15kHz parameter design is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each 1ms in size, and each subframe includes one time slot. Figure 5 In the diagram, 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.

[0124] A resource grid can be used to represent time slots, each time slot comprising one or more concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE corresponds to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 5In the parameter design, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0125] 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), probe reference signals (SRS), etc., depending on whether the interpreted frame structure is used for uplink or downlink communication. Figure 5 An example location (labeled "R") carrying a reference signal is explained.

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

[0127] The transmission of PRS resources within a given PRB has a specific comb tooth size (also known as "comb tooth density"). The comb tooth size 'N' represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration. Specifically, for a comb tooth size 'N', the PRS is transmitted in every Nth subcarrier of a symbol in the PRB. For example, for comb tooth-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS resource. Currently, comb tooth sizes of comb tooth-2, comb tooth-4, comb tooth-6, and comb tooth-12 are supported by DL-PRS. Figure 5 An example PRS resource configuration for comb-4 (which spans 4 symbols) is explained. That is, the position of the shaded RE (marked as "R") indicates the PRS resource configuration for comb-4.

[0128] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a single time slot using a full-frequency interleaved mode. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by a higher layer within a time slot. For all REs of a given DL-PRS resource, there may be a constant energy per resource element (EPRE). The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0,1}; 4-symbol comb-2: {0,1,0,1}; 6-symbol comb-2: {0,1,0,1,0,1}; 12-symbol comb-2: {0,1,0,1,0,1,0,1,0,1,0,1}; 4-symbol comb-4: {0,2,1,3} (as in...). Figure 5 In the example); 12-code comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 6-code comb-6: {0,3,1,4,2,5}; 12-code comb-6: {0,3,1,4,2,5,0,3,1,4,2,5}; and 12-code comb-12: {0,6,3,9,1,7,4,10,2,8,5,11}.

[0129] A PRS resource set is a collection of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources within a PRS resource set are associated with the same Time Responsibility Provider (TRP). A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by a TRP ID). Additionally, PRS resources within a PRS resource set share the same periodicity, a common silent mode configuration, and the same repetition factor (such as the "PRS-ResourceRepetitionFactor") across time slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. The periodicity can have a length chosen from the following: 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} time slots, where μ=0,1,2,3. The repetition factor can have a length chosen from {1,2,4,6,8,16,32} time slots.

[0130] In a PRS resource set, a PRS resource ID is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can be transmitted on a different beam, and thus, a "PRS resource" (or simply a "resource") can also be referred to as a "beam". Note that this does not imply whether the UE is aware of the TRP and beam transmitting the PRS.

[0131] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window (such as a group of one or more consecutive time slots) in which a PRS is expected to be transmitted. A PRS timing may also be referred to as a “PRS positioning timing,” “PRS positioning instance,” “positioning timing,” “positioning instance,” “positioning repetition,” or simply “timing,” “instance,” or “repetition.”

[0132] A “positioning frequency layer” (also simply “frequency layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all parameter designs supported for the Physical Downlink Shared Channel (PDSCH) are also supported by the PRS), the same point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter uses the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying the pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of 4 PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets can be configured per frequency layer per TRP.

[0133] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWPs), but the difference is that component carriers and BWPs are used by a single base station (or macrocell base station and small cell base station) to transmit data channels, while a frequency layer is used by several (often three or more) base stations to transmit PRS (Positioning Signals). A UE can indicate the number of frequency layers it can support when sending its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, a UE can indicate whether it can support one or four positioning frequency layers.

[0134] Figure 6 This is a diagram illustrating an example PRS configuration 600 for PRS transmission at a given base station, based on various aspects of this disclosure. Figure 6In the diagram, time is represented horizontally, increasing from left to right. Each long rectangle represents a time slot, while each short (shaded) rectangle represents an OFDM symbol. Figure 6 In the example, PRS resource set 610 (labeled "PRS resource set 1") includes two PRS resources—first PRS resource 612 (labeled "PRS resource 1") and second PRS resource 614 (labeled "PRS resource 2"). The base station transmits PRS on PRS resources 612 and 614 of PRS resource set 610.

[0135] PRS resource set 610 has a timing length of two time slots (N_PRS) and a periodicity of, for example (for a 15 kHz subcarrier spacing), 160 time slots or 160 milliseconds (ms) (T_PRS). Thus, PRS resources 612 and 614 are both two consecutive time slots in length and repeat every T_PRS time slots starting from the time slot in which the first symbol of the corresponding PRS resource appears. Figure 6 In the example, PRS resource 612 has a symbol length of two symbols (N_symbols), and PRS resource 614 has a symbol length of four symbols (N_symbols). PRS resource 612 and PRS resource 614 can be transmitted on separate beams of the same base station.

[0136] Each instance of PRS resource set 610 (described as instances 620a, 620b, and 620c) includes a timing of length "2" (i.e., N_PRS = 2) for each PRS resource 612, 614 in the PRS resource set. PRS resources 612 and 614 are repeated every T_PRS time slots until the silence sequence is periodically T_REP. Thus, a bit mapping of length T_REP is needed to indicate which timings of instances 620a, 620b, and 620c of PRS resource set 610 are silenced (i.e., not transmitted).

[0137] On the one hand, there may be additional constraints on PRS configuration 600. For example, for all PRS resources (e.g., PRS resources 612, 614) in a PRS resource set (e.g., PRS resource set 610), the base station can configure the following parameters to be the same: (a) timing length (N_PRS), (b) number of symbols (N_symbols), (c) comb type, and / or (d) bandwidth. Additionally, for all PRS resources in all PRS resource sets, the subcarrier spacing and cyclic prefix can be configured to be the same for one base station or for all base stations. Whether it is for one base station or for all base stations depends on the UE's ability to support the first and / or second options.

[0138] Note that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If further distinction is needed regarding the type of PRS, downlink positioning reference signals may be referred to as "DL-PRS," while uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS."

[0139] Figure 7 This is diagram 700 illustrating various downlink channels within an example downlink time slot. Figure 7 In this diagram, time is represented horizontally (on the X-axis), increasing from left to right, while frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top. Figure 7 In the example, a parameter design of 15kHz is used. Therefore, in the time domain, the interpreted time slot length is 1 millisecond (ms), divided into 14 symbols.

[0140] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth portions (BWPs). A BWP is a set of adjacent RBs selected from a subset of shared RBs designed for a given carrier with given parameters. Generally, a maximum of four BWPs can be specified in both the downlink and uplink. That is, a UE can be configured to have up to four BWPs in the downlink and up to four BWPs in the uplink. Only one BWP (uplink or downlink) can be active at a given time, meaning that the UE can only receive or transmit on one BWP at a time. In 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.

[0141] Reference Figure 7The Primary Synchronization Signal (PSS) is used by the UE to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and 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 Primary Information Block (MIB) can be logically grouped with the PSS and SSS to form the SSB (also known 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 not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0142] The Physical Downlink Control Channel (PDCCH) carries downlink control information (DCI) within 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, and each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The physical resource set used to carry the PDCCH / DCI is called the Control Resource Set (CORESET) in NR. In NR, the PDCCH is confined to a single CORESET and transmitted along with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0143] exist Figure 7 In the example, each BWP has one CORESET, and this CORESET spans three symbols in the time domain (although it can be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region in the frequency domain (i.e., the CORESET). Therefore, Figure 7 The frequency components of the PDCCH shown are interpreted in the frequency domain as fewer than a single BWP. Note that although the interpreted CORESETs are contiguous in the frequency domain, they do not need to be contiguous. Additionally, a CORESET can span fewer than three symbols in the time domain.

[0144] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of the downlink data transmitted to the UE (referred to as uplink grant and downlink grant, respectively). More specifically, the DCI indicates the 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 8) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, different DCI formats exist for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or code rates.

[0145] Figure 8 Figure 800 illustrates the Cell Global Identifier (CGI) reading procedure according to various aspects of this disclosure. Currently, when requested by the network using the Information Element (IE) "reportCGI" (e.g., for cell handover), the UE is expected to identify and report the CGI of a known target cell. Only one cell is provided to the UE via the parameter "cellForWhichToReportCGI" used to identify the CGI. The UE can use autonomous gaps in downlink reception and uplink transmission to receive MIB and SIB (e.g., SIB1) messages from the cell under test to determine the CGI. Note that if the parameter "useAutonomousGaps" is set to "false", the UE does not need to use autonomous gaps. If autonomous gaps are used for measurement for the purpose of "reportCGI", the UE is expected to be able to identify new CGIs of NR cells regardless of whether Discontinuous Reception (DRX) is used or whether SCells are configured.

[0146] Reference Figure 8 In order to read the CGI of an unknown cell (unknown to the serving cell) and report that CGI back to the UE's serving cell, the UE first detects the PSS and SSS of the target cell. Figure 8 (Not shown in the image). The UE then decodes the PBCH of the target cell in order to decode the MIB of that target cell. The UE may need to measure and decode multiple instances of the PBCH in order to decode the MIB, as provided by... Figure 8As shown in the diagram, multiple "PBCH Decoding" blocks represent a single PBCH instance. After decoding the MIB of the target cell, the UE decodes the PDSCH of that target cell in order to decode the SIB. The UE may need to measure and decode multiple instances of the PDSCH to decode the SIB, as described by... Figure 8 As shown in the multiple "PDSCH Decoding" blocks, each "PDSCH Decoding" block represents a PDSCH instance. After the SIB of the target cell is decoded, the UE can obtain the CGI of the target cell and report it to the serving cell.

[0147] like Figure 8 As shown, the UE can measure each instance or timing of the PBCH and PDSCH during autonomous gaps. During autonomous gaps, the UE is allowed to temporarily suspend communication with the serving cell, i.e., create an autonomous gap to perform the corresponding measurement (within certain restrictions). Otherwise, the UE can only support measurements if the network has provided sufficient idle time.

[0148] Referring more specifically to autonomous gaps, when a UE uses an autonomous gap to identify the CGI of a target cell, the UE is permitted to interrupt on the primary cell (PCell), primary secondary cell (PSCell), or any active secondary cell (SCell). Currently, such autonomous gaps or interrupts are defined using the following parameters: (1) K1: For each interrupt during the MIB decoding time period TMIB (ms), the maximum number of interrupts with interrupt slots up to the interrupt length X1 specified in Table 1; (2) L1: During the SSB and CORESET SIB1 decoding time period TSIB1 (ms) for Residual Minimal System Information (RMSI) scheduling multiplexing mode 1, the maximum number of interrupts with interrupt slots up to the interrupt length Y1 specified in Table 1; and (3) L2: During the SSB and CORESET SIB1 decoding time period TSIB1 (ms) for RMSI scheduling multiplexing modes 2 and 3, the maximum number of interrupts with interrupt slots up to the interrupt length Y2 specified in Table 1. Currently, for the target cell carrier frequency on FR1, K1 = 6, and for the target cell carrier frequency on FR2, K1 = 25, L1 = TSIB1 / 20, and L2 = TSIB1 / TSMTC, where TSMTC is the periodicity of the SS / PBCH block measurement time configuration (SMTC) timing configured for the target cell carrier.

[0149] The table below indicates the interruption lengths X1, Y1, and Y2 during measurements with autonomous gaps.

[0150]

[0151] Table 1

[0152] The period during which the UE can use the autonomous gap is indicated by timer "T321". Therefore, as Figure 8 As shown, the UE measures and decodes the PBCH and PDSCH timings within the autonomous gaps of the timer period allowed by timer T321.

[0153] As mentioned above, the "useAutonomousGaps" parameter in the "ReportCGI" IE indicates whether the UE is allowed to use autonomous gaps when obtaining system information from neighboring cells. When this field is included, the UE applies the corresponding value of T321. The following table indicates the conditions for starting and stopping timer T321.

[0154]

[0155] Table 2

[0156] If "useAutonomousGaps" is included in the "reportConfig" associated with this "measId (Measurement ID)", then timer T321 is started, with a timer value set to, for example, 200ms for this "measId". Otherwise, timer T321 is started, with a timer value set to 1 second for this "measId".

[0157] Referring back to DL-PRS, currently, DL-PRS has a lower priority than other channels in LTE and NR. This is because when no measurement gap is configured for the UE, the UE does not expect to process DL-PRS in the same symbol transmitted to it as other downlink signals and channels. However, if an increased DL-PRS priority over other channels is supported, various factors should be considered.

[0158] The table below provides the current physical layer DL-PRS processing capacity that the UE can report. These values ​​indicate the amount of time the UE may need to buffer and process DL-PRS at the physical layer.

[0159]

[0160]

[0161] Table 3

[0162] The measurement period (or measurement window) used for each positioning frequency layer depends on (1) the UE reporting capability (e.g., from Table 3), (2) the PRS periodicity (denoted as T). PRS(or T_PRS), (3) Measurement gap periodicity (the UE does not expect to measure PRS in the absence of a measurement gap in which PRS is to be measured), and (4) the number of the UE's receive beams (if operating in FR2).

[0163] Figure 9 This is a diagram 900 illustrating an example DL-PRS measurement scenario according to various aspects of this disclosure. Figure 9 In the diagram, time is represented horizontally. The arrow indicates a 20ms PRS periodicity 910, and the box indicates a PRS resource 920 within the PRS periodicity 910 with a PRS symbol duration of 0.5ms.

[0164] Based on the above considerations related to the measurement window length, and given the following assumptions... Figure 9 The minimum PRS measurement window in the example would be 88ms: (1) one PRS frequency layer in FR1, (2) PRS RSTD measurements performed across four PRS instances (i.e., four repetitions of PRS period 910), (3) both PRS period 910 and measurement gap period (denoted as "measurement gap repetition period" or "MGRP") are equal to 20ms, and (4) the configured PRS resources are within the UE's PRS processing capacity. For the fourth assumption, the parameters (N,T) = (0.5ms,8ms) (from Table 2), where N is the duration in milliseconds of the PRS resource 920 that the UE can process every T = 8ms. Therefore, after the last PRS period 910, there is an 8ms period (i.e., T) during which the UE processes the PRS resource 920 received during the four PRS periods 910, resulting in a total waiting time of 88ms.

[0165] For positioning procedures that require low latency (e.g., less than 10ms at the physical layer), an 88ms measurement window at the physical layer (e.g., in...) Figure 9 (In the example) this would not be sufficient. On the one hand, different UEs can have different time-domain processing windows, while ensuring that network resources are available across UEs.

[0166] Figure 10 This is a diagram 1000 illustrating an example DL-PRS transmission, processing, and reporting loop for multiple UEs according to various aspects of this disclosure. Figure 10In the example, three UEs have been configured to use the “DDDSU” frame structure 1010 in a Time Division Duplex (TDD) 30kHz SCS. As mentioned above, for a 30kHz SCS (μ=1), each frame has 20 time slots, and each time slot lasts for 0.5ms. Therefore, each block of the DDDSU frame structure 1010 represents a 0.5ms time slot. The DDDSU frame structure 1010 includes the repetition of three downlink (D) time slots, a special (S) time slot, and an uplink (U) time slot.

[0167] exist Figure 10 In the example, the PRS is received in the first three downlink time slots of the frame, and the SRS is transmitted in the fourth time slot. The PRS and SRS can be received and transmitted as part of downlink-based and uplink-based positioning sessions (such as RTT positioning sessions), respectively. The three time slots for receiving (i.e., measuring) the PRS can correspond to a PRS instance. Generally, the PRS instance should be included within a few milliseconds (2ms here) after the start of the PRS transmission, processing, and reporting cycle. The SRS transmission (if needed, such as here, for downlink- and uplink-based positioning procedures) should be close to the PRS instance (here, in the next time slot).

[0168] like Figure 10 As shown, the first UE (labeled "UE1") is configured with PRS transmission, processing, and reporting loop 1020, the second UE (labeled "UE2") is configured with PRS transmission, processing, and reporting loop 1030, and the third UE (labeled "UE3") is configured with PRS transmission, processing, and reporting loop 1040. PRS transmission, processing, and reporting loops 1020, 1030, and 1040 may repeat periodically (e.g., every 10 ms). Each UE is expected to send a location report (e.g., its respective Rx-Tx time difference measurement) at the end of its PRS transmission, processing, and reporting loop (e.g., every 10 ms). Each UE sends its report on the PUSCH (e.g., configured uplink permission). Specifically, the first UE sends its report on PUSCH 1024, the second UE sends its report on PUSCH 1034, and the third UE sends its report on PUSCH 1044.

[0169] like Figure 10As shown, each of the different UEs is configured with its own PRS processing gap (or simply "processing gap") or PRS processing window (or simply "processing window"), in which the PRS measured in the first three slots of the frame is processed (e.g., determining the ToA of the PRS and calculating the Rx-Tx time difference measurement). Specifically, the first UE is configured with processing gap 1022, the second UE is configured with processing gap 1032, and the third UE is configured with processing gap 1042. Figure 10 In the example, the length of each processing interval is 4ms.

[0170] like Figure 10 As shown, the processing gap for each UE is offset from the processing gaps of other UEs, but still within the UE's 10ms PRS transmission, processing, and reporting cycle. Additionally, there are still PUSCH opportunities for reporting UE measurements after the processing gap. Even though there are gaps between the PRS instances and processing gaps for the second and third UEs, there is limited aging between measurement and reporting due to the shorter lengths of the corresponding PRS transmission, processing, and reporting cycles 1030 and 1040 for the UEs.

[0171] The technical advantage of configuring UEs with offset processing gaps is greater spectrum utilization. Not all UEs process PRS simultaneously after a PRS instance (and SRS transmission), and therefore do not process other signals; different UEs can continue transmitting and receiving while other UEs are not transmitting and receiving.

[0172] For more detailed reference to processing intervals, such as Figure 10 As shown, the processing gap is the time window following the reception and measurement of the PRS. Therefore, this is the period during which the UE processes the PRS (e.g., to determine the ToA of the PRS for Rx-Tx time difference measurement or RSTD measurement) without having to measure any other signals. In other words, the processing gap is the period during which the UE prioritizes the PRS over other channels, which may include prioritizing data (e.g., PDSCH), control (e.g., PDCCH), and any other reference signals. However, as... Figure 10 As shown, there may be a gap between the measurement and processing time.

[0173] Processing gaps, or processing windows, differ from measurement gaps. In a processing gap, there is no retuning gap as in a measurement gap—the UE does not change its BWP but continues to use the BWP it had before the processing gap. Furthermore, the location server (e.g., LMF 270) can determine the processing gap, and the UE will not need a processing gap to send an RRC request to the serving base station and wait for a response. Processing gaps thus reduce signaling overhead and latency.

[0174] Information related to PRS processing gaps can be provided in the unicast auxiliary data received by the UE. For example, LPP provides auxiliary data messages (e.g., as in...). Figure 4 Phase 430 may include information for determining processing gaps. Alternatively, PRS processing gap information may be included in an LPP providing location information message to the UE (e.g., as in phase 440), or in on-demand PRS information (e.g., UE-initiated on-demand PRS and processing gap information). Processing gaps may be associated with one or more positioning frequency layers, one or more PRS resource sets, one or more PRS resources, or any combination thereof.

[0175] The UE can include a request for a specific processing gap in the LPP auxiliary data request message. Alternatively, the UE can provide a capability message in the LPP (e.g., as in...). Figure 4 Phase 420 includes PRS processing gap information. For example, the UE may optionally include a processing gap request for “tight” PRS processing scenarios (e.g., where there is a limited time between a measured PRS instance and a measurement report). This request may include how long the UE requires for a low-latency PRS processing application. For example, for a PRS instance with 'X' PRS resource sets, resources, or symbols, the UE may require a processing time of 4 ms. The location server may use this recommendation to send auxiliary data associated with a specific PRS processing gap to the UE.

[0176] The processing gap information configured for the UE and / or recommended by the UE may include (1) offsets regarding: (a) the start or offset of the PRS instance (e.g., Figure 10 (a) The processing gap of the second UE in the process has an offset of 4ms from the start of the PRS instance, (b) the end of the PRS instance (e.g., Figure 10 The processing gap of the third UE in the process has an offset of 3.5ms from the end of the PRS instance, (c) PRS resource offset, (d) PRS resource set offset, or (e) time slot, subframe or frame boundary (e.g., Figure 10 The processing gap for the second UE in the frame has an offset of 4.5ms from the start of the frame, (2) the length and / or end time of the processing gap, (3) whether the processing gap is per UE, per band, per band combination (BC), per frequency range (e.g., FR1 or FR2), whether it affects LTE, and / or (4) how many PRS resources, resource sets, or instances can be processed within a processing gap of this length. In some cases, the start / offset position of the processing gap may depend on the UE ID.

[0177] To configure the UE to have processing gaps, the location server (e.g., LMF 270) may first send an on-demand PRS configuration along with a suggestion, recommendation, requirement, or request for processing gaps for the UE to the UE's serving base station. Note that the location server may not need to send the requested processing gaps simultaneously with the on-demand PRS configuration (e.g., in the same message). Second, the serving base station may send a response to the location server. The response may be an acceptance of the requested processing gaps or a configuration of different processing gaps. Third, the location server sends auxiliary data to the UE for use in the positioning session. The auxiliary data includes the PRS configuration and the associated processing gaps.

[0178] In some scenarios, the UE can utilize autonomous processing gaps (i.e., autonomous PRS prioritization). In such scenarios, after a PRS instance, if no measurement gap is configured, the UE can discard or ignore all other traffic for a period of time without notifying the serving base station. In one aspect, there can be a maximum window within which the UE is permitted to perform these autonomous PRS prioritizations. As an example, it can be expected that the UE completes PRS processing within 'X' milliseconds (e.g., 6 ms) after the end of the PRS instance, and within that 'X' milliseconds, the UE can choose a period of 'Y' milliseconds (where 'Y' is less than 'X', e.g., 4 ms) during which the UE autonomously prioritizes the PRS over other channels. During this window, it is up to the UE to decide whether to discard or ignore any other channels and procedures (e.g., CSI procedures)—the serving base station will not suppress transmissions to the UE.

[0179] On the one hand, processing gap information (e.g., processing gap offset) can be implicitly determined through UE-specific parameters. For example, applying modulo operation to the UE ID for different UEs can result in the UEs measuring the same PRS instance and still allowing their PRS processing to be time-division multiplexed (e.g., ...). Figure 10 (as in the example).

[0180] On the one hand, the serving base station can use the MAC control element (MAC-CE) or DCI to configure the UE, instead of the location server configuring the UE via LPP with processing gaps.

[0181] On the one hand, the UE can send a request for a processing gap (directly to the serving base station or via the location server to the serving base station), and the serving base station can respond with a request that is "disjoint" or has a "gap" relative to the PRS being measured. Figure 11 Figure 1100 illustrates an example DL-PRS transmission, processing, and reporting loop for a UE (where the UE has been configured to have disjoint processing intervals) according to various aspects of this disclosure. Figure 11In the example, the UE has been configured to use the "DDDSU" frame structure 1110 in TDD 30kHz SCS. Therefore, each block of the DDDSU frame structure 1110 represents a 0.5ms time slot. (As in...) Figure 10 In the example, the DDDSU frame structure 1110 includes a repetition of three downlink (D) slots, special (S) slots, and uplink (U) slots.

[0182] exist Figure 11 In the example, the PRS is received / measured in the first three downlink time slots of the frame, and the SRS is transmitted in the fourth time slot. The PRS and SRS can be received and transmitted as part of downlink-based and uplink-based positioning sessions (such as RTT positioning sessions), respectively. The three time slots in which the PRS is received / measured can correspond to the PRS instance.

[0183] like Figure 11 As shown, the UE has been configured with PRS transmission, processing, and reporting loop 1120. It is expected that the UE will send a location report (e.g., its corresponding Rx-Tx time difference measurement) on PUSCH 1124 at the end of PRS transmission, processing, and reporting loop 1120. Figure 11 As shown, the UE has been configured to have a PRS processing gap 1122 in which PRS received in the first three time slots of a frame are to be processed. However, with Figure 10 The processing intervals explained are opposite, in Figure 11 In the example, the UE's processing gap 1122 is non-overlapping and consists of two 2ms segments. During the gap between these two segments, the UE can be expected to handle other downlink traffic. Note that the two 2ms segments are merely an example, and the processing gap 1122 can be divided into more than two segments and / or these segments can have different lengths.

[0184] On the one hand, the UE may prioritize PRS over other downlink signals and channels during processing gaps, but may still expect to transmit any scheduled uplink signals and channels during processing gaps. Figure 12 Figure 1200 illustrates an example DL-PRS transmission, processing, and reporting loop for a UE (where the UE has been configured to transmit uplink signals and channels during processing intervals) according to various aspects of this disclosure. Figure 12 In the example, the UE has been configured to use the "DDDSU" frame structure 1210 in TDD 30kHz SCS. Therefore, each block of the DDDSU frame structure 1210 represents a 0.5ms time slot. (As in...) Figure 10 In the example, the DDDSU frame structure 1210 includes a repetition of three downlink (D) slots, special (S) slots, and uplink (U) slots.

[0185] exist Figure 12 In the example, the PRS is received / measured in the first three downlink time slots of the frame, and the SRS is transmitted in the fourth time slot. The PRS and SRS can be received and transmitted as part of downlink-based and uplink-based positioning sessions (such as RTT positioning sessions), respectively. The three time slots in which the PRS is received can correspond to the PRS instance.

[0186] like Figure 12 As shown, the UE has been configured with PRS transmission, processing, and reporting loop 1220. It is expected that the UE will send a location report (e.g., its corresponding Rx-Tx time difference measurement) on PUSCH 1224 at the end of PRS transmission, processing, and reporting loop 1220. Figure 12 As shown, the UE has been configured to have a PRS processing gap 1222 in which PRS received in the first three time slots of a frame are to be processed. However, with Figure 10 The processing intervals explained are opposite, in Figure 12 In the example, the UE is expected to transmit any scheduled uplink signals or channels that occur during the processing gap. Therefore, as... Figure 12 As shown, during the UE's 4ms processing gap 1222, it transmits on the uplink time slot within the processing gap 1222.

[0187] On one hand, the priority ordering of PRS processing within a processing gap can be on a subset of channels, rather than all channels. For example, PRS processing may have a higher priority than PDSCH and CSI-RS processing, but may not have a higher priority than PDCCH or SSB processing. That is, the UE is expected to process any PDCCH or SSB during the PRS processing gap. In some cases, the UE may also be expected to process high-priority PDSCHs during the PRS processing gap (e.g., Ultra-Reliable Low Latency Communication (URLLC) traffic). Whether the UE is expected to process other downlink signals and channels during the PRS processing gap can be based on the UE's ability to do so.

[0188] One option to reduce the signaling used for configuring measurement gaps is to consider autonomous measurement gaps for positioning. The concept of autonomous gaps is currently supported in a subset of scenarios, such as when the network has not configured a measurement gap for the UE and the UE autonomously selects an appropriate gap to receive system information (e.g., CGI) from neighboring cells, as referenced above. Figure 8As described. Therefore, for low latency positioning, the UE is permitted to discard other downlink signaling / traffic during one or more time windows after receiving a low latency positioning request, without explicit requests / configurations from the serving cell. Note that coordination between the UE, serving cell, and LMF can be specified to ensure seamless operation of autonomous measurement gaps used for positioning. However, the signaling details between the LMF and serving cell are not fully defined, nor is the time duration of the associated UE capabilities or autonomous gaps fully defined.

[0189] This disclosure provides techniques for configuring and signaling autonomous gaps for positioning. As used herein, an autonomous gap for positioning (or simply "autonomous gap") is a period of time during which the UE measures and processes the PRS (e.g., to determine the ToA of the PRS for Rx-Tx time difference measurement or RSTD measurement) without having to measure and process any other signals. In other words, an autonomous gap is a period of time during which the UE prioritizes measuring and processing the PRS over other channels, which may include priority over data (e.g., PDSCH), control (e.g., PDCCH), and any other reference signals. An autonomous gap may also be referred to as an interruption because communication with the UE's serving cell is interrupted during the autonomous gap. An autonomous gap is "autonomous" because the UE can determine the exact time-domain and / or frequency-domain location of the gap / interruption based on certain parameters negotiated with or received from the network. More specifically, as further described herein, the UE receives a configuration of the upper or lower bound or the amount or size of the time window during which the UE is permitted to interrupt other traffic (e.g., PDSCH, PDCCH, non-PRS reference signals, etc.) to measure and process the PRS. The UE can then determine the exact time and / or frequency location of the gaps / interruptions in the measurement and processing of PRS within its configured limits.

[0190] On the UE side, the UE can report various parameters related to the configuration of autonomous gaps, such as capabilities and recommendations, to its serving cell and / or location server (e.g., LMF 270). Regarding UE capabilities, the UE can report capabilities indicating the maximum interrupt length it supports when using autonomous gaps for positioning. The maximum interrupt length may be the same as or different from the interrupt length of the autonomous gap used for CGI measurement and reporting. The UE can also report capabilities indicating the maximum number of interrupts it can support for autonomous gaps. The UE can also report capabilities indicating which one or more frequency bands, frequency ranges, component carriers (e.g., PCell, PSCell, SCell), and / or RATs (e.g., LTE, NR) these capabilities are associated with.

[0191] The UE can also provide various recommendations regarding the configuration of autonomous gaps. After receiving positioning assistance data indicating the PRS resources, TRP, frequency layer, etc. to be measured, the UE can transmit recommendations for the interruption length, slot offset (i.e., the start position within the slot), and / or potential time window of the autonomous gap. The UE can also recommend the maximum number of interruptions.

[0192] The UE may also indicate (as a capability and / or recommendation) whether the interruption will apply to downlink traffic, downlink reference signals (e.g., CSI-RS, TRS, SSB, etc.), PDCCH monitoring, and / or uplink traffic (e.g., PUSCH, SRS). The UE may also indicate whether the interruption will also apply to sidelink traffic (i.e., sidelink transmission and / or reception).

[0193] The UE may provide the aforementioned capabilities and recommendations to the serving base station via one or more RRC IEs or one or more MAC control elements (MAC-CEs). The UE may also provide the aforementioned capabilities and recommendations to the location server via one or more LPP IEs. For example, the UE may provide capability messages in the LPP at the start of the LPP positioning session (e.g., as in...). Figure 4 This information is provided in stage 420.

[0194] On the location server side, the location server (e.g., LMF 270) can inform the UE's serving base station (e.g., gNB222) about the maximum number of interruptions; the length of each interruption; and the maximum time window during which the UE is allowed to use autonomous gaps (e.g., ...). Figure 8 The location server may specify the following: timer T321 in the timer; the periodicity of these interrupts; whether these interrupts apply to downlink traffic (i.e., downlink data reception), downlink reference signal measurements (e.g., CSI-RS, TRS, SSB, etc.), PDCCH monitoring, and / or uplink traffic (i.e., uplink data and / or reference signal transmission, e.g., PUSCH, SRS); whether these interrupts apply to sidelink interrupts; and / or which one or more frequency bands, frequency ranges, component carriers (e.g., PCell, PSCell, SCell), and / or RATs (e.g., LTE, NR) these autonomous gaps are associated with. For example, the location server may indicate that up to 100 ms after the UE receives an indication that it can implement autonomous gaps, and periodically at 500 ms, the UE is permitted to execute up to “X” interrupts, each with a duration of up to “Y” ms. The location server may provide this information via one or more New Radio Positioning Protocol Type A (NRPPa) messages.

[0195] Between the location server and the UE, the location server may include the above information in a location request message to the UE (e.g., an LPP request for location information message, such as in...). Figure 4Phase 440) or location-assisted data messages (e.g., LPP provides auxiliary data messages, such as in Figure 4 In stage 430), specifically, the location server may include the maximum number of interruptions; the length of each interruption; and the maximum time window during which the UE is allowed to use the autonomous gap (e.g., ...). Figure 8 The interrupts include: timer T321 in the timer; the periodicity of these interrupts; whether these interrupts apply to downlink traffic, downlink reference signals (e.g., CSI-RS, TRS, SSB, etc.), PDCCH monitoring and / or uplink traffic (e.g., PUSCH, SRS); whether these interrupts apply to sidelink interrupts and / or which one or more frequency bands, frequency ranges, component carriers (e.g., PCell, PSCell, SCell) and / or RATs (e.g., LTE, NR) these autonomous gaps are associated with.

[0196] In all aspects, the location server and / or the UE may be permitted to request an autonomous gap from the UE's serving base station, or the UE may be permitted to execute an autonomous gap, only when the response time or latency QoS of the location session is less than a threshold. Furthermore, different overhead and / or autonomous gap parameters may be permitted for different latency QoS and / or accuracy requirements. Additionally, different overhead and / or autonomous gap parameters may be permitted for different frequency bands.

[0197] In all respects, it may be expected or required that the serving base station confirms that the UE and / or location server are permitted to request autonomous gaps.

[0198] In various aspects, the UE's serving base station may recommend / suggest a specific value or upper bound (maximum) for the maximum number of interruptions; the length of each interruption; and the maximum time window during which the UE is allowed to use autonomous gaps (e.g., Figure 8 The timer T321 in the system; the periodicity of these interrupts; whether these interrupts apply to downlink traffic, downlink reference signals (e.g., CSI-RS, TRS, SSB, etc.), PDCCH monitoring, and / or uplink traffic (e.g., PUSCH, SRS); whether these interrupts apply to sidelink interrupts and / or which one or more frequency bands, frequency ranges, component carriers (e.g., PCell, PSCell, SCell), and / or RATs (e.g., LTE, NR) these autonomous gaps are associated with. The base station may provide these values ​​to the location server so that the location server can configure the UE based on these values.

[0199] In various aspects, a UE may initiate an autonomous gap request to its serving base station. This may be used in the case of a Mobile Origin Location Request (MO-LR). Therefore, for example, when a UE initiates an MO-LR, the request may also include a request for an autonomous gap.

[0200] Figure 13 Figure 1300 illustrates an example PRS measurement procedure utilizing autonomous gaps according to various aspects of this disclosure. The PRS measurement procedure begins at the UE upon receiving a location request 1310 (e.g., an LPP request for location information message, as in...). Figure 4 (Phase 440). Location request 1310 may instruct the UE to implement autonomous gaps and may include parameters defining these autonomous gaps. For example, location request 1310 may include the maximum number of interruptions; the length of each interruption; and the maximum time window during which the UE is allowed to use the autonomous gaps (e.g., ...). Figure 8 The interrupts include: timer T321 in the timer; the periodicity of these interrupts; whether these interrupts apply to downlink traffic, downlink reference signals (e.g., CSI-RS, TRS, SSB, etc.), PDCCH monitoring and / or uplink traffic (e.g., PUSCH, SRS); whether these interrupts apply to sidelink interrupts and / or which one or more frequency bands, frequency ranges, component carriers (e.g., PCell, PSCell, SCell) and / or RATs (e.g., LTE, NR) these autonomous gaps are associated with.

[0201] For example, location request 1310 may indicate that up to 100 ms after the UE receives location request 1310, the UE can implement autonomous gaps periodically at 500 ms, and the UE is permitted to execute up to "X" autonomous gaps or interruptions, each with a duration of up to "Y" ms. Therefore, in Figure 13 In the example, the maximum time window during which the UE is allowed to use autonomous gap 1320 is denoted as "autonomous gap timer for positioning" 1315, and begins within 100ms of receiving a location request 1310. Within the window defined by autonomous gap timer 1315 for positioning, there are four autonomous gaps 1320 (i.e., four less than or equal to X), each with a length less than or equal to Y ms. The time from the start of the window defined by autonomous gap timer 1315 for positioning to the start of the next window defined by autonomous gap timer 1315 for positioning will be 500ms. During each autonomous gap 1320, the UE may measure PRS instance 1325 or a portion of PRS instance 1325 (e.g., a subset of PRS resources of the PRS instance) depending on the configuration of autonomous gap 1320.

[0202] After performing the location measurement in PRS instance 1325, the UE transmits a measurement report (e.g., an LPP report location information message, such as in...) to a location server (e.g., LMF 270) or other location entity (e.g., a location component on the UE (such as location component 342), or a location management function at the serving base station (such as location component 388)). Figure 4 Phase 460).

[0203] Figure 14 An example method 1400 for wireless positioning according to various aspects of this disclosure has been explained. In one aspect, method 1400 can be performed by a UE (e.g., any of the UEs described herein).

[0204] At 1410, the UE acquires one or more positioning measurements (e.g., ToA, RSTD, Rx-Tx time difference, AoA, etc.) of one or more PRS resources during one or more autonomous gaps (e.g., autonomous gap 1320) scheduled within an autonomous gap window (e.g., as defined by "Autonomous Gap Timer for Positioning" 1315), the autonomous gap window, the one or more autonomous gaps, or both, defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period during which the UE prioritizes PRS reception and processing over the reception, processing, or both of other downlink signals and channels. In one aspect, operation 1410 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered means for performing the operation.

[0205] At 1420, the UE reports one or more positioning measurements to a positioning entity (e.g., the UE's positioning component, base station, or location server, such as positioning components 342, 388, 398) so that the positioning entity can determine the UE's location. In one aspect, operation 1420 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which can be considered as means for performing the operation.

[0206] Figure 15 An example location method 1500 according to various aspects of this disclosure has been described. In one aspect, method 1500 may be performed by a location server (e.g., LMF 270).

[0207] At 1510, the location server transmits to the UE (e.g., any UE described herein) one or more autonomous gap configuration parameters defining an autonomous gap window (e.g., as defined by "Autonomous Gap Timer for Positioning" 1315), one or more autonomous gaps scheduled within that autonomous gap window (e.g., autonomous gap 1320), or both, wherein each of the one or more autonomous gaps includes a period during which the UE is expected to prioritize at least PRS reception and processing over reception, processing, or both of other downlink signals and channels. In one aspect, operation 1510 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be considered means for performing the operation.

[0208] At 1520, the location server receives a measurement report from the UE (e.g., LPP provides location information messages, such as in...). Figure 4 Phase 460), the measurement report includes one or more positioning measurements (e.g., ToA, RSTD, Rx-Tx time difference, AoA, etc.) of one or more PRS resources performed during one or more autonomous intervals. In one aspect, operation 1520 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning components 398, any or all of which may be considered means for performing the operation.

[0209] At 1530, the location server determines the location of the UE based on one or more positioning measurements. In one aspect, operation 1530 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning components 398, any or all of these components may be considered as means for performing the operation.

[0210] As will be understood, the technical advantage of methods 1400 and 1500 is that they configure the UE to have autonomous gaps based on the UE's capabilities, thereby reducing latency by avoiding signaling for configuring legacy measurement gaps, while controlling the worst-case scenario of network outages due to PRS processing.

[0211] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to include more features in the example clauses than are expressly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the appended clauses should thus be considered as incorporated into this description, where each clause may be a separate example in itself. Although each dependent clause may refer in its respective clause to a specific combination with one of the other clauses, the aspects of that dependent clause are not limited to that specific combination. It will be appreciated that other example clauses may also include combinations of aspects of the dependent clause with the subject matter of any other dependent or independent clause, or any feature combined with other dependent and independent clauses. The aspects disclosed herein expressly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is intended that aspects of a clause may be included in any other independent clause, even if that clause is not directly subordinate to that independent clause.

[0212] Examples of implementations are described in the following numbered clauses:

[0213] Clause 1. A radio positioning method performed by a user equipment (UE), comprising: acquiring one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both, defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period during which the UE at least prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and reporting the one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0214] Clause 2. The method of Clause 1, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0215] Clause 3. The method of any of Clauses 1 to 2, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of the autonomous gap window received from the indication that the UE is permitted to use the autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0216] Clause 4. As in any of Clauses 1 to 3, the values ​​of one or more autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, response times, or any combination thereof.

[0217] Clause 5. The method of any of Clauses 1 to 4 further includes: receiving one or more autonomous gap configuration parameters from a network entity.

[0218] Clause 6. The method of Clause 5, wherein: the network entity is the serving base station of the UE, and one or more autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

[0219] Clause 7. The method of Clause 5, wherein: the network entity is a location server, and one or more autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0220] Clause 8. As in Clause 7, one or more LPP messages include one or more messages providing auxiliary data, one or more messages requesting location information, or any combination thereof.

[0221] Clause 9. The method of any of Clauses 1 to 8 further includes: transmitting a capability message to a network entity, the capability message including an indication that the UE supports autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0222] Clause 10. The method of any of Clauses 1 to 9 further comprises: transmitting to the network entity a request to be configured to have one or more autonomous gaps, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

[0223] Clause 11. The method of any of Clauses 1 to 10, wherein the positioning entity includes: a positioning component of the UE, a location management function of a base station serving the UE, or a location server.

[0224] Clause 12. A positioning method performed by a location server, comprising: transmitting to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receiving from the UE a measurement report including one or more positioning measurements performed on one or more PRS resources during the one or more autonomous gaps; and determining the location of the UE based on the one or more positioning measurements.

[0225] Clause 13. The method of Clause 12, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0226] Clause 14. The method of any of Clauses 12 to 13, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of the autonomous gap window received from the indication that the UE is permitted to use the autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0227] Clause 15. The method of any of Clauses 12 to 14, wherein the value of one or more autonomous gap configuration parameters is different for different frequency bands, latency requirements, quality of service (QoS) requirements, response time or any combination thereof.

[0228] Clause 16. The method of any of Clauses 12 to 15 further includes: transmitting one or more autonomous gap configuration parameters to the UE in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0229] Clause 17. As in Clause 16, one or more LPP messages include one or more providing auxiliary data messages, one or more requesting location information messages, or any combination thereof.

[0230] Clause 18. The method of any of Clauses 12 to 17 further includes: transmitting recommended values ​​of one or more autonomous gap configuration parameters to the base station serving the UE in one or more New Radio Positioning Protocol Type A (NRPPa) messages.

[0231] Clause 19. The method of Clause 18 further includes: receiving from the base station confirmation of the UE, the location server, or both being granted permission to request autonomous intervals.

[0232] Clause 20. The method of any of Clauses 12 to 19 further includes: receiving a capability message from the UE, the capability message including an indication that the UE supports autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0233] Clause 21. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: acquire one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both being defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period of time during which the UE at least prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and report one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0234] Clause 22. For a UE as described in Clause 21, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0235] Clause 23. For any UE of Clauses 21 to 22, one or more autonomous gap configuration parameters include: the maximum offset from the start of the autonomous gap window received from the indication that the UE is permitted to use autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0236] Clause 24. For any UE of Clauses 21 to 23, the value of one or more autonomous gap configuration parameters is different for different frequency bands, latency requirements, quality of service (QoS) requirements, response time or any combination thereof.

[0237] Clause 25. The UE of any of Clauses 21 to 24, wherein the at least one processor is further configured to receive one or more autonomous gap configuration parameters from a network entity via the at least one transceiver.

[0238] Clause 26. The UE as described in Clause 25, wherein: the network entity is the serving base station of the UE, and one or more autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

[0239] Clause 27. The UE as in Clause 25, wherein: the network entity is a location server, and one or more autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0240] Clause 28. For the UE as in Clause 27, one or more LPP messages include one or more Provide Auxiliary Data messages, one or more Request Location Information messages, or any combination thereof.

[0241] Clause 29. The UE of any of Clauses 21 to 28, wherein the at least one processor is further configured to transmit a capability message to a network entity via the at least one transceiver, the capability message including an indication that the UE supports autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0242] Clause 30. The UE of any of Clauses 21 to 29, wherein the at least one processor is further configured to transmit, via the at least one transceiver, a request to be configured to have one or more autonomous gaps to a network entity, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

[0243] Clause 31. The UE of any of Clauses 21 to 30, wherein the positioning entity includes: the positioning component of the UE, the location management function of the base station serving the UE, or the location server.

[0244] Clause 32. A location server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmit via the at least one transceiver one or more autonomous gap configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period of time during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receive via the at least one transceiver a measurement report from the UE, the measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and determine the location of the UE based on the one or more positioning measurements.

[0245] Clause 33. A location server as described in Clause 32, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0246] Clause 34. A location server as described in any of Clauses 32 to 33, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of an autonomous gap window received from an indication that the UE is permitted to use an autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0247] Clause 35. For any of the location servers mentioned in Clauses 32 to 34, the values ​​of one or more autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, response times, or any combination thereof.

[0248] Clause 36. A location server as described in any of Clauses 32 to 35, wherein the at least one processor is further configured to transmit one or more autonomous gap configuration parameters to the UE via the at least one transceiver in one or more Long Term Evolution (LTE) Location Protocol (LPP) messages.

[0249] Clause 37. As in Clause 36, a location server, wherein one or more LPP messages include one or more providing auxiliary data messages, one or more requesting location information messages, or any combination thereof.

[0250] Clause 38. A location server as described in any of Clauses 32 to 37, wherein the at least one processor is further configured to transmit recommended values ​​of one or more autonomous gap configuration parameters to a base station serving the UE via the at least one transceiver in one or more New Radio Positioning Protocol Type A (NRPPa) messages.

[0251] Clause 39. A location server as described in Clause 38, wherein the at least one processor is further configured to receive from the base station via the at least one transceiver confirmation of an autonomous gap granted to the UE, the location server, or both.

[0252] Clause 40. A location server as described in any of Clauses 32 to 39, wherein the at least one processor is further configured to receive a capability message from the UE via the at least one transceiver, the capability message including an indication that the UE supports autonomous gaps and a capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0253] Clause 41. A user equipment (UE) comprising: means for acquiring one or more positioning measurements of one or more positioning reference signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both, defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period of time during which the UE prioritizes the reception and processing of PRS over the reception, processing, or both of other downlink signals and channels; and means for reporting one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0254] Clause 42. For a UE as described in Clause 41, one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0255] Clause 43. For any UE of Clauses 41 to 42, one or more autonomous gap configuration parameters include: the maximum offset from the start of the autonomous gap window received from the indication that the UE is permitted to use autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0256] Clause 44. For any UE of Clauses 41 to 43, the value of one or more autonomous gap configuration parameters is different for different frequency bands, latency requirements, quality of service (QoS) requirements, response time or any combination thereof.

[0257] Clause 45. The UE of any of Clauses 41 to 44 further includes: means for receiving one or more autonomous gap configuration parameters from a network entity.

[0258] Clause 46. The UE as in Clause 45, wherein: the network entity is the serving base station of the UE, and one or more autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

[0259] Clause 47. The UE as in Clause 45, wherein: the network entity is a location server, and one or more autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0260] Clause 48. For the UE as in Clause 47, one or more LPP messages include one or more Provide Auxiliary Data messages, one or more Request Location Information messages, or any combination thereof.

[0261] Clause 49. The UE of any of Clauses 41 to 48 further includes: means for transmitting a capability message to a network entity, the capability message including an indication that the UE supports autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0262] Clause 50. The UE of any of Clauses 41 to 49 further includes: means for transmitting to a network entity a request to be configured to have one or more autonomous gaps, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

[0263] Clause 51. The UE of any of Clauses 41 to 50, wherein the positioning entity includes: the positioning component of the UE, the location management function of the base station serving the UE, or the location server.

[0264] Clause 52. A location server comprising: means for transmitting to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period of time during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; means for receiving a measurement report from the UE, the measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and means for determining the location of the UE based on the one or more positioning measurements.

[0265] Clause 53. A location server as described in Clause 52, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0266] Clause 54. A location server as described in any of Clauses 52 to 53, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of an autonomous gap window received from an indication that the UE is permitted to use an autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0267] Clause 55. For any of the location servers mentioned in Clauses 52 to 54, the values ​​of one or more autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, response times, or any combination thereof.

[0268] Clause 56. The location server of any of Clauses 52 to 55 further includes: means for transmitting one or more autonomous gap configuration parameters to the UE in one or more Long Term Evolution (LTE) Location Protocol (LPP) messages.

[0269] Clause 57. As in Clause 56, a location server, wherein one or more LPP messages include one or more providing auxiliary data messages, one or more requesting location information messages, or any combination thereof.

[0270] Clause 58. The location server of any of Clauses 52 to 57 further includes: means for transmitting recommended values ​​of one or more autonomous gap configuration parameters to a base station serving the UE in one or more New Radio Positioning Protocol Type A (NRPPa) messages.

[0271] Clause 59. The location server as described in Clause 58 further includes: means for receiving from the base station confirmation of the UE, the location server, or both being permitted to request autonomous intervals.

[0272] Clause 60. The location server of any of Clauses 52 to 59 further includes: means for receiving a capability message from the UE, the capability message including an indication that the UE supports autonomous gaps and a capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0273] Clause 61. A non-transient computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: acquire one or more positioning measurements of one or more Positioning Reference Signal (PRS) resources during one or more autonomous gaps scheduled within an autonomous gap window, the autonomous gap window, the one or more autonomous gaps, or both, defined by one or more autonomous gap configuration parameters, wherein each of the one or more autonomous gaps includes a period during which the UE at least prioritizes PRS reception and processing over reception, processing, or both of other downlink signals and channels; and report one or more positioning measurements to a positioning entity so that the positioning entity can determine the location of the UE.

[0274] Clause 62. A non-transient computer-readable medium as described in Clause 61, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0275] Clause 63. A non-transient computer-readable medium such as any of Clauses 61 to 62, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of an autonomous gap window received from an indication that the UE is permitted to use an autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0276] Clause 64. A non-transient computer-readable medium such as any of Clauses 61 to 63, wherein the values ​​of one or more autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, response times or any combination thereof.

[0277] Clause 65. A non-transient computer-readable medium such as any of Clauses 61 to 64 further includes, when executed by the UE, computer-executable instructions that cause the UE to receive one or more autonomous gap configuration parameters from a network entity.

[0278] Clause 66. A non-transient computer-readable medium as described in Clause 65, wherein: the network entity is the serving base station of the UE, and one or more autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

[0279] Clause 67. A non-transient computer-readable medium as described in Clause 65, wherein: the network entity is a location server, and one or more autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0280] Clause 68. A non-transient computer-readable medium as described in Clause 67, wherein one or more LPP messages include one or more messages providing auxiliary data, one or more messages requesting location information, or any combination thereof.

[0281] Clause 69. A non-transient computer-readable medium such as any of Clauses 61 to 68 further includes, when executed by the UE, computer-executable instructions that cause the UE to: transmit a capability message to a network entity, the capability message including an indication that the UE supports autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

[0282] Clause 70. A non-transient computer-readable medium such as any of Clauses 61 to 69 further includes, when executed by the UE, computer-executable instructions that cause the UE to: transmit to a network entity a request to be configured to have one or more autonomous gaps, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

[0283] Clause 71. A non-transient computer-readable medium such as any of Clauses 61 to 70, wherein the positioning entity includes: a positioning component of the UE, a location management function of a base station serving the UE, or a location server.

[0284] Clause 72. A non-transient computer-readable medium storing computer-executable instructions that, when executed by a location server, cause the location server to: transmit to a user equipment (UE) configuration parameters defining an autonomous gap window, one or more autonomous gaps scheduled within the autonomous gap window, or both, wherein each of the one or more autonomous gaps includes a period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels; receive from the UE a measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and determine the location of the UE based on the one or more positioning measurements.

[0285] Clause 73. A non-transient computer-readable medium as described in Clause 72, wherein one or more autonomous gap configuration parameters include: the maximum length of each of the one or more autonomous gaps; the maximum number of the one or more autonomous gaps; an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, one or more radio access technologies (RATs) or any combination thereof that may be used for the one or more autonomous gaps; an indication of whether the one or more autonomous gaps are suitable for downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception or any combination thereof; one or more time slot offsets for the one or more autonomous gaps; or any combination thereof.

[0286] Clause 74. A non-transient computer-readable medium such as any of Clauses 72 to 73, wherein one or more autonomous gap configuration parameters include: the maximum offset from the start of an autonomous gap window received from an indication that the UE is permitted to use an autonomous gap, the length of the autonomous gap window, the periodicity of the autonomous gap window, or any combination thereof.

[0287] Clause 75. A non-transient computer-readable medium such as any of Clauses 72 to 74, wherein the values ​​of one or more autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, response times, or any combination thereof.

[0288] Clause 76. A non-transient computer-readable medium such as any of Clauses 72 to 75 further includes: computer-executable instructions that, when executed by the location server, cause the location server to perform the following operation: transmit one or more autonomous gap configuration parameters to the UE in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

[0289] Clause 77. A non-transient computer-readable medium as described in Clause 76, wherein one or more LPP messages include one or more messages providing auxiliary data, one or more messages requesting location information, or any combination thereof.

[0290] Clause 78. A non-transient computer-readable medium such as any of Clauses 72 to 77 further includes: computer-executable instructions that, when executed by the location server, cause the location server to perform the following operation: transmit recommended values ​​for one or more autonomous gap configuration parameters to a base station serving the UE in one or more New Radio Positioning Protocol Type A (NRPPa) messages.

[0291] Clause 79. The non-transient computer-readable medium of Clause 78 further includes, when executed by the location server, computer-executable instructions that cause the location server to perform the following operations: receiving confirmation from the base station regarding a request for autonomy from the UE, the location server, or both.

[0292] Clause 80. A non-transient computer-readable medium such as any of Clauses 72 to 79 further includes, when executed by the location server, computer-executable instructions that cause the location server to perform the following actions: receive a capability message from the UE, the capability message including an indication of the UE's ability to support autonomous gaps and the capability associated with the values ​​of one or more autonomous gap configuration parameters.

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

[0294] Furthermore, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.

[0295] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, 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. The general-purpose processor may be a microprocessor, but in alternatives, 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, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0296] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor so that the processor can read and write information from / to the storage medium. In alternatives, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). In alternatives, the processor and storage medium may reside as discrete components in the user terminal.

[0297] In one or more examples, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or codes on or through a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Similarly, any connection is also legitimately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then such coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used in this article, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0298] While the foregoing disclosure has illustrated illustrative aspects of this disclosure, it should be noted that various changes and modifications may be made therein without departing from the scope of this disclosure as defined by the appended claims. The functions, steps, and / or actions in the method claims according to the aspects of this disclosure described herein need not be performed in any particular order. Furthermore, although elements of this disclosure may be described or claimed in the singular, pluralism is also contemplated unless explicitly stated to be limited to the singular.

Claims

1. A wireless positioning method performed by a user equipment (UE), comprising: Multiple autonomous gap configuration parameters are received from a network entity, wherein an autonomous gap includes a period of time during which the UE prioritizes the reception and processing of a Position Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels, and wherein the multiple autonomous gap configuration parameters include a maximum length of one or more autonomous gaps and an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, and / or one or more radio access technologies (RATs) that the one or more autonomous gaps can be used by the UE; One or more positioning measurements are obtained for one or more PRS resources during one or more autonomous gaps scheduled within an autonomous gap window, wherein the autonomous gap window and the one or more autonomous gaps are defined by the plurality of autonomous gap configuration parameters; as well as The location entity reports the one or more location measurements to the location entity so that the location entity can determine the location of the UE.

2. The method of claim 1, wherein the plurality of autonomous clearance configuration parameters include: The maximum number of the one or more autonomous gaps; Indication regarding whether the one or more autonomous gaps are applicable to downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception, or any combination thereof; or One or more time slot offsets for the one or more autonomous gaps.

3. The method of claim 1, wherein the plurality of autonomous clearance configuration parameters include: The maximum offset from the start of the autonomous gap window upon receiving an indication that the UE is permitted to use the autonomous gap; The length of the autonomous gap window; or The periodicity of the autonomous gap window.

4. The method of claim 1, wherein the values ​​of the plurality of autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, or response times.

5. The method of claim 1, wherein: The network entity is the serving network entity of the UE; and The multiple autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

6. The method of claim 1, wherein: The network entity is a location server, and The multiple autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

7. The method of claim 6, wherein the one or more LPP messages include one or more providing auxiliary data messages or one or more requesting location information messages.

8. The method of claim 1, further comprising: A capability message is transmitted to a network entity, the capability message including an indication that the UE supports autonomous gaps and the capabilities associated with the values ​​of the plurality of autonomous gap configuration parameters.

9. The method of claim 1, further comprising: A request to be configured to have the one or more autonomous gaps is transmitted to the network entity, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

10. The method of claim 1, wherein the positioning entity comprises: The positioning component of the UE; Location management functions for network entities serving the UE; or Location server.

11. A location method performed by a location server, comprising: The system transmits to the User Equipment (UE) a plurality of autonomous gap configuration parameters defining an autonomous gap window and one or more autonomous gaps scheduled within the autonomous gap window, wherein each of the one or more autonomous gaps includes a time period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels, and wherein the plurality of autonomous gap configuration parameters include a maximum length of the one or more autonomous gaps and an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, and / or one or more radio access technologies (RATs) that the one or more autonomous gaps can be used by the UE; The UE receives a measurement report, which includes one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps. as well as The location of the UE is determined based on the one or more positioning measurements.

12. The method of claim 11, wherein the plurality of autonomous clearance configuration parameters include: The maximum number of the one or more autonomous gaps; Indication regarding whether the one or more autonomous gaps are applicable to downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception, or any combination thereof; or One or more time slot offsets for the one or more autonomous gaps.

13. The method of claim 11, wherein the plurality of autonomous clearance configuration parameters include: The maximum offset from the start of the autonomous gap window upon receiving an indication that the UE is permitted to use the autonomous gap; The length of the autonomous gap window; or The periodicity of the autonomous gap window.

14. The method of claim 11, wherein the values ​​of the plurality of autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, or response times.

15. The method of claim 11, further comprising: The plurality of autonomous gap configuration parameters are transmitted to the UE in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

16. The method of claim 15, wherein the one or more LPP messages include one or more providing auxiliary data messages or one or more requesting location information messages.

17. The method of claim 11, further comprising: Recommended values ​​for the plurality of autonomous gap configuration parameters are transmitted to the network entity serving the UE in one or more New Radio Positioning Protocol Type A (NRPPa) messages.

18. The method of claim 17, further comprising: Receive confirmation from the network entity regarding the UE, the location server, or both being granted permission to request autonomous gaps.

19. The method of claim 11, further comprising: The UE receives a capability message, which includes an indication of the UE's support for autonomous gaps and the capabilities associated with the values ​​of the plurality of autonomous gap configuration parameters.

20. A user equipment (UE), comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: Multiple autonomous gap configuration parameters are received from a network entity, wherein an autonomous gap includes a period of time during which the UE prioritizes the reception and processing of a Position Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels, and wherein the multiple autonomous gap configuration parameters include a maximum length of one or more autonomous gaps and an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, and / or one or more radio access technologies (RATs) that the one or more autonomous gaps can be used by the UE; One or more positioning measurements are obtained for one or more PRS resources during one or more autonomous gaps scheduled within an autonomous gap window, wherein the autonomous gap window and the one or more autonomous gaps are defined by the plurality of autonomous gap configuration parameters; as well as The location entity reports the one or more location measurements to the location entity so that the location entity can determine the location of the UE.

21. The UE of claim 20, wherein the plurality of autonomous gap configuration parameters include: The maximum number of the one or more autonomous gaps; Indication regarding whether the one or more autonomous gaps are applicable to downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception, or any combination thereof; or One or more time slot offsets for the one or more autonomous gaps.

22. The UE of claim 20, wherein the plurality of autonomous gap configuration parameters include: The maximum offset from the start of the autonomous gap window upon receiving an indication that the UE is permitted to use the autonomous gap; The length of the autonomous gap window; or The periodicity of the autonomous gap window.

23. The UE of claim 20, wherein the values ​​of the plurality of autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, or response times.

24. The UE of claim 20, wherein: The network entity is the serving network entity of the UE; and The multiple autonomous gap configuration parameters are received in one or more Radio Resource Control (RRC) messages, one or more Media Access Control (MAC-CE) elements, or Downlink Control Information (DCI).

25. The UE of claim 20, wherein: The network entity is a location server, and The multiple autonomous gap configuration parameters are received in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

26. The UE of claim 25, wherein the one or more LPP messages include one or more Provide Assistance Data messages or one or more Request Location Information messages.

27. The UE of claim 20, wherein the at least one processor is further configured to: Capability messages are transmitted to network entities via the at least one transceiver, the capability messages including indications of the UE's support for autonomous gaps and capabilities related to the values ​​of the plurality of autonomous gap configuration parameters.

28. The UE of claim 20, wherein the at least one processor is further configured to: A request to be configured to have the one or more autonomous gaps is transmitted to the network entity via the at least one transceiver, the request being transmitted together with a request for a Mobile Origin Location Request (MO-LR) positioning procedure.

29. The UE of claim 20, wherein the positioning entity comprises: The positioning component of the UE; Location management functions for network entities serving the UE; or Location server.

30. A location server, comprising: Memory; At least one transceiver; as well as At least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: The at least one transceiver transmits to the user equipment (UE) a plurality of autonomous gap configuration parameters defining an autonomous gap window and one or more autonomous gaps scheduled within the autonomous gap window, wherein each of the one or more autonomous gaps includes a time period during which the UE is expected to prioritize the reception and processing of a Positioning Reference Signal (PRS) over the reception, processing, or both of other downlink signals and channels, and wherein the plurality of autonomous gap configuration parameters include a maximum length of the one or more autonomous gaps and an indication of one or more frequency bands, one or more frequency ranges, one or more component carriers, and / or one or more radio access technologies (RATs) that the one or more autonomous gaps can be used by the UE; Receive a measurement report from the UE via the at least one transceiver, the measurement report including one or more positioning measurements of one or more PRS resources performed during the one or more autonomous gaps; and The location of the UE is determined based on the one or more positioning measurements.

31. The location server of claim 30, wherein the plurality of autonomous gap configuration parameters include: The maximum number of the one or more autonomous gaps; Indication regarding whether the one or more autonomous gaps are applicable to downlink data reception, downlink reference signal measurement, physical downlink control channel (PDCCH) monitoring, uplink data transmission, uplink reference signal transmission, sidelink data transmission, sidelink data reception, or any combination thereof; or One or more time slot offsets for the one or more autonomous gaps.

32. The location server of claim 30, wherein the plurality of autonomous gap configuration parameters include: The maximum offset from the start of the autonomous gap window upon receiving an indication that the UE is permitted to use the autonomous gap; The length of the autonomous gap window; or The periodicity of the autonomous gap window.

33. The location server of claim 30, wherein the values ​​of the plurality of autonomous gap configuration parameters are different for different frequency bands, latency requirements, quality of service (QoS) requirements, or response times.

34. The location server of claim 30, wherein the at least one processor is further configured to: The plurality of autonomous gap configuration parameters are transmitted to the UE in one or more Long Term Evolution (LTE) Positioning Protocol (LPP) messages.

35. The location server of claim 34, wherein the one or more LPP messages include one or more providing auxiliary data messages or one or more requesting location information messages.

36. The location server of claim 30, wherein the at least one processor is further configured to: The recommended values ​​of the plurality of autonomous gap configuration parameters are transmitted to the network entity serving the UE in one or more New Radio Positioning Protocol Type A (NRPPa) messages via the at least one transceiver.

37. The location server of claim 36, wherein the at least one processor is further configured to: Receive confirmation from the network entity regarding the UE, the location server, or both being granted permission to request autonomous gaps.

38. The location server of claim 30, wherein the at least one processor is further configured to: The UE receives a capability message, which includes an indication of the UE's support for autonomous gaps and the capabilities associated with the values ​​of the plurality of autonomous gap configuration parameters.

Images