Reporting granularity and measurement period for positioning reference signal (PRS) measurements

CN122525489APending Publication Date: 2026-08-07QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
QUALCOMM INC
Filing Date
2021-05-10
Publication Date
2026-08-07

Smart Images

  • Figure CN122525489A_ABST
    Figure CN122525489A_ABST
Patent Text Reader

Abstract

The present disclosure relates to reporting granularity and measurement period for positioning reference signal (PRS) measurements, and discloses techniques for wireless positioning. In an aspect, a user equipment (UE) receives, from a network entity, a configuration of one or more positioning reference signal (PRS) resources to measure during a positioning session with a PRS periodicity T PRS and a PRS occasion length L PRS ; and measures the one or more PRS resources during a measurement period, where the measurement period is based on a number of measurement instances of the one or more PRS resources expected to be processed by the UE multiplied by a periodicity parameter, where the periodicity parameter is based on a PRS processing window of ‘T’ milliseconds, the PRS periodicity T PRS , and a measurement gap periodicity of at least one measurement gap.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of Chinese patent application No. 202180033975.2, filed on May 10, 2021, entitled “Report Granularity and Measurement Period for Positioning Reference Signal (PRS) Measurement”.

[0002] Cross-references to related applications

[0003] This patent application claims the benefit of U.S. Provisional Application No. 63 / 025,510, filed May 15, 2020, entitled “Reporting Granularity and Measurement Period for Positioning Reference Signal (PRS) Measurements,” and U.S. Non-Provisional Application No. 17 / 314,258, filed May 7, 2021, entitled “Reporting Granularity and Measurement Period for Positioning Reference Signal (PRS) Measurements,” both of which have been assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety. Public background

[0004] 1. Public domain

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

[0006] 2. Description of relevant technologies

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

[0008] 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. Overview

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

[0010] In one aspect, a radio positioning method performed by a user equipment (UE) includes: configuring one or more positioning reference signal (PRS) resources received from a network entity to measure a periodicity T with PRS during a positioning session. PRS and PRS timing length L PRS The one or more PRS resources; and measuring the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources to be processed by the expected UE multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds, a PRS periodicity TPRS, and a measurement gap periodicity of at least one measurement gap.

[0011] In one aspect, a wireless positioning method performed by a user equipment (UE) includes: receiving from a network entity a recommendation for a first granularity of positioning measurements for reporting one or more Positioning Reference Signal (PRS) resources during a positioning session; performing one or more positioning measurements on the one or more PRS resources; and reporting the one or more positioning measurements at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to a minimum granularity, and wherein the minimum granularity is based on a PRS bandwidth parameter associated with the one or more PRS resources.

[0012] 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: receive one or more Positioning Reference Signal (PRS) resources from a network entity via the at least one transceiver to measure a periodicity T with PRS during a positioning session. PRS and PRS timing length L PRS The one or more PRS resources; and measuring the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources to be processed by the expected UE multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds, a PRS periodicity TPRS, and a measurement gap periodicity of at least one measurement gap.

[0013] 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: receive, via the at least one transceiver, from a network entity a recommendation for a first granularity of positioning measurements for reporting one or more Positioning Reference Signal (PRS) resources during a positioning session; perform one or more positioning measurements on the one or more PRS resources; and report the one or more positioning measurements at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to a minimum granularity, and wherein the minimum granularity is based on a PRS bandwidth parameter associated with the one or more PRS resources.

[0014] In one aspect, a user equipment (UE) includes: a configuration for receiving one or more positioning reference signal (PRS) resources from a network entity to measure a periodicity T with PRS during a positioning session. PRS and PRS timing length L PRS The apparatus for measuring the one or more PRS resources; and the apparatus for measuring the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources expected to be processed by the UE multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds and a PRS periodicity T. PRS And the periodicity of the measurement gap of at least one measurement gap.

[0015] In one aspect, a user equipment (UE) includes: means for receiving from a network entity a recommendation of a first granularity for reporting one or more location reference signal (PRS) resources during a location session; means for performing one or more location measurements on the one or more PRS resources; and means for reporting the one or more location measurements at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to a minimum granularity, and wherein the minimum granularity is based on a PRS bandwidth parameter associated with the one or more PRS resources.

[0016] In one aspect, a non-transient computer-readable storage medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to perform the following operations: receive configurations from a network entity for one or more Positioning Reference Signal (PRS) resources to measure a periodicity T with PRS during a positioning session. PRS and PRS timing length L PRS The measurement of the one or more PRS resources; and the measurement of the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources expected to be processed by the UE multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds and a PRS periodicity T. PRS And the periodicity of the measurement gap of at least one measurement gap.

[0017] In one aspect, a non-transient computer-readable storage medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to perform the following actions: receiving from a network entity a recommendation for a first granularity of positioning measurements for reporting one or more Positioning Reference Signal (PRS) resources during a positioning session; performing one or more positioning measurements on the one or more PRS resources; and reporting the one or more positioning measurements at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to a minimum granularity, and wherein the minimum granularity is based on a PRS bandwidth parameter associated with the one or more PRS resources.

[0018] 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 and2B Example wireless network architectures based on various aspects of this disclosure are explained.

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

[0023] Figure 4A and 4B This is a diagram illustrating example frame structures and channels within these frame structures according to various aspects of this disclosure.

[0024] Figure 5 This is a diagram illustrating an example set of positioning reference signals (PRS) resources with different time intervals according to various aspects of this disclosure.

[0025] Figures 6 to 8 The various information elements (IEs) used for reporting positioning measurements are explained.

[0026] Figure 9 This is a diagram illustrating several DL-PRS resources spanning a given time duration (in milliseconds) according to various aspects of this disclosure.

[0027] Figure 10 and 11 Example wireless positioning methods based on various aspects of this disclosure are explained. Detailed description

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

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

[0030] 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, the 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, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, etc.

[0031] 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."

[0032] 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 Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard), and so on.

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

[0034] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be located in the same place. 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 physical TRPs located in the same place, the physical TRP may be an antenna array of the base station (e.g., in a multiple-input multiple-output (MIMO) system or in the case of beamforming at the base station). When the term "base station" refers to multiple physical TRPs not located in the same place, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, physical TRPs not located in the same place may be the serving base station from which the UE receives measurement reports and neighboring base stations from which 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.

[0035] 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).

[0036] 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 individual RF signals through a multipath channel, 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.

[0037] Figure 1 An 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.

[0038] 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. The location server 172 can be part of the core network 170 or located outside the core network 170. Among other functions, the base station 102 can 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 (such as 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 can communicate with each other directly or indirectly (e.g., via EPC / 5GC) through backhaul link 134 (which can be wired or wireless).

[0039] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographical 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 identifiers (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.

[0040] 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 a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

[0041] 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).

[0042] 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 a listen-before-speak procedure to determine whether the channel is available before communication.

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

[0044] 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 frequency of 3 GHz with a wavelength of 100 mm. 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 utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be appreciated that in alternative configurations, one or more base stations 102 may also 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.

[0045] Transmit beamforming is a technique used to focus 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.

[0046] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., the UE) to have the same parameters regardless of whether the transmit antennas of the network node 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. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal 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.

[0047] 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 along 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.

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

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

[0050] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into several frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). The mmW band generally includes the FR2, FR3, and FR4 frequency ranges. Thus, the terms "mmW" and "FR2" or "FR3" or "FR4" are generally used interchangeably.

[0051] 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 the 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.

[0052] For example, still refer to Figure 1 One 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"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, in a multi-carrier system, two 20 MHz aggregated carriers would theoretically result in twice the data rate (i.e., 40 MHz) compared to the data rate obtained from a single 20 MHz carrier.

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

[0054] exist Figure 1 In the example, one or more Earth-orbiting Satellite Positioning System (SPS) spacecraft (SV) 112 (e.g., satellites) can be used as any of the explained UEs (for simplicity, in... Figure 1 The location information of a single UE 104 is a separate source. UE 104 may include one or more dedicated SPS receivers specifically designed to receive SPS signal 124 from SV 112 to derive geographic location information. The SPS typically includes a transmitter system (e.g., SV 112) positioned such that receivers (e.g., UE 104) can determine their location on or above the earth based at least in part on signals received from the transmitter (e.g., SPS signal 124). 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 a terrestrial control station, base station 102, and / or other UE 104.

[0055] The use of SPS signal 124 can be amplified by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise enabled to be used in conjunction 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, for example, 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, SPS may include any combination of one or more global and / or regional navigation satellite systems and / or augmentation systems, and SPS signal 124 may include SPS, SPS-like systems, and / or other signals associated with one or more such SPS.

[0056] 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., UE 190 can indirectly obtain cellular connectivity from this link), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity from this link). In one example, D2D P2P links 192 and 194 can be supported using any well-known D2D RAT (such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.).

[0057] 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).

[0058] 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, 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).

[0059] Figure 2B Another example wireless network architecture, 250.5GC 260, was explained (which can correspond to...). Figure 2A5GC 210 can be functionally considered as a control plane function (provided by Access and Mobility Management Function (AMF) 264) and a user plane function (provided by 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 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.

[0060] The functions of UPF 262 include: acting as an anchor point for intra-RAT / 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.

[0061] 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 to route 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.

[0062] Another optional aspect may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules extending across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not explained). SLP 272 supports similar functionality 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 but not voice or data), SLP 272 can communicate with UE 204 and external clients on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP). Figure 2B (Not shown in the image) Communication.

[0063] 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 gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or 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 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.

[0064] The functionality of gNB 222 is divided between gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. 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 gNB-DU 228. More specifically, gNB-CU 226 manages the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of gNB 222. gNB-DU 228 is a logical node that manages the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of gNB 222. Its operation is controlled by gNB-CU 226. One gNB-DU 228 can support one or more cells, while a cell is supported by only one gNB-DU 228. Therefore, UE 204 communicates with gNB-CU 226 via RRC, SDAP, and PDCP layers, and with gNB-DU 228 via RLC, MAC, and PHY layers.

[0065] Figure 3A , 3B The explanation of 3C 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 The NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as a private network) depicted herein includes several example components (represented by corresponding boxes) to support file transfer operations as taught herein. It will be appreciated that these components can be implemented in different types of devices (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.) in various implementations. The illustrated components can 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.

[0066] 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 communication 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 communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) on 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.

[0067] 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 may be connected to one or more antennas 326 and 366, respectively, and provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for suppressing transmission, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) over a wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, ZigBee®, Z-Wave®, PC5, Dedicated Short Range Communication (DSRC), Wireless Access in Vehicle Environments (WAVE), Near Field Communication (NFC), etc.). Short-range transceivers 320 and 360 may be configured, in various ways according to a specified RAT, 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 a specific example, short-range transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0068] In at least some cases, UE 302 and base station 304 also include Satellite Positioning System (SPS) receivers 330 and 370. SPS 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 SPS signals 338 and 378, such as 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. SPS receivers 330 and 370 may each include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378. SPS receivers 330 and 370 request information and operations from other systems as appropriate and perform necessary calculations to determine the positioning of UE 302 and base station 304 using measurements obtained by any suitable SPS algorithm.

[0069] 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 employ 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 employ 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.

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

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

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

[0073] 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 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, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, 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 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 3B The possible locations of the positioning component 388 are described. 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 described. 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.

[0074] 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 SPS receivers 330. As an example, sensors 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, sensors 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.

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

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

[0077] 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) decoding / 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 a channel estimator can be used to determine the coding and modulation schemes, as well as for spatial processing. These 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.

[0078] At UE 302, receiver 312 receives signals via its respective antennas 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. This frequency domain signal comprises 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.

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

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

[0081] 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 appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to (a number of) different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0082] 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 respective antenna(s) 356. Receiver 352 recovers the information modulated onto the RF carrier and provides that information to one or more processors 384.

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

[0084] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , 3BThe components shown in 3C are various and 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 such cases, a specific implementation of UE 302 may omit (e.g., wearable devices, tablets, PCs, or laptops may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or (e.g., short-range wireless transceivers 320, e.g., cellular only), or (e.g., SPS receiver 330), or (e.g., sensors 344), etc. In another example, in Figure 3B In such cases, a particular implementation of base station 304 may omit (e.g., a WWAN transceiver 350, for example, a Wi-Fi "hotspot" access point without cellular capabilities), or (e.g., a short-range wireless transceiver 360, for example, a cellular-only transceiver), or (e.g., an SPS 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.

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

[0086] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some implementations, Figure 3A , Figure 3B and Figure 3CThe components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by that circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and / or 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 functionality 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 functionality represented by blocks 390 to 398 may be implemented by the processor and / or 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 of the UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memory components 340, 386, and 396, positioning components 342, 388, and 398, etc.

[0087] 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 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can 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).

[0088] 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 can estimate the UE's location.

[0089] 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 angle between the UE and (e.g.,) transmitting base stations. The positioning entity can then estimate the UE's location based on the determined angle and the known location of the transmitting base stations.

[0090] 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 measurement and the angle of the receive beam to determine the angle between the UE and (the) base stations. Based on the determined angle and the known location of the base stations, the positioning entity can then estimate the location of the UE.

[0091] Downlink and uplink-based positioning methods include Enhanced Cellular ID (E-CID) positioning and Multiple Round Trip (RTT) positioning (also known as "Multi-Cell RTT"). In an RTT procedure, the initiator (base station or UE) transmits an RTT measurement signal (e.g., PRS or SRS) to the responder (UE or base station), which then transmits an RTT response signal (e.g., SRS or PRS) back to the initiator. The RTT response signal includes the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response signal (referred to as the receive-to-transmit (Rx-Tx) time difference). The initiator calculates the difference between the transmission time of the RTT measurement signal and the ToA of the RTT response signal (referred to as the transmit-to-receive (Tx-Rx) time difference). The propagation time (also known as "time of flight") between the initiator and the responder can be calculated from the Tx-Rx and Rx-Tx time differences. Based on the propagation time and the known speed of light, the distance between the initiator and the responder can be determined. For multi-RTT positioning, the UE executes RTT procedures with multiple base stations so that the UE's location can be determined based on the known locations of each base station (e.g., using multilateral positioning). RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy.

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

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

[0094] 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 resources used for positioning measurements are in FR1, the expected RSTD uncertainty may range from + / - 32 µs. In other cases, when all resources used for positioning measurements are in FR2, the expected RSTD uncertainty may range from + / - 8 µs.

[0095] Location estimation can be referred to by other names, such as location estimation, location, positioning, location locking, locking, etc. Location estimation can be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), 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 altitude). 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).

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

[0097] 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.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

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

[0099] exist Figure 4A and Figure 4B In the example, a parameter set of 15 kHz is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equal-sized subframes, each 1 ms long, and each subframe includes one time slot. Figure 4A and 4B 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.

[0100] 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 4Aand Figure 4B In 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.

[0101] Some REs carry downlink reference (pilot) signals (DL-RS). DL-RS 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), etc. Figure 4A Example locations of REs carrying PRS (labeled "R") are explained.

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

[0103] The transmission of PRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size 'N' represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size 'N', the PRS is transmitted in every Nth subcarrier of a symbol in the PRB. For example, for comb size -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 sizes -2, -4, -6, and -12 are supported by DL-PRS. Figure 4A An example PRS resource configuration for comb tooth 6 (which spans 6 symbols) is explained. That is, the position of the shaded RE (marked as "R") indicates the PRS resource configuration for comb tooth 6.

[0104] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a single time slot using a full-frequency-domain interleaved mode. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by higher layers 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-bit comb teeth -2: {0, 1}; 4-bit comb teeth -2: {0,1, 0, 1}; 6-bit comb teeth -2: {0, 1, 0, 1, 0, 1}; 12-bit comb teeth -2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-bit comb teeth -4: {0, 2, 1, 3}; 12-bit comb teeth -4: {0, 2, 1, 3, 0, 2, 1, 3, 0,2, 1, 3}; 6-bit comb teeth -6: {0, 3, 1, 4, 2, 5}; 12-bit comb teeth -6: {0, 3, 1, 4, 2, 5, 0, 3,1, 4, 2, 2, 3} 5}; and 12-bit comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0105] A “PRS resource set” is a group of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by the TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, a common silent mode configuration, and the same repetition factor (such as “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. Periodicity can have a length selected from the following: 2^µ The time slots are {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}, where µ = 0, 1, 2, 3. The repetition factor can have a length selected from the {1, 2, 4, 6, 8, 16, 32} time slots.

[0106] 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 "resource") can also be referred to as a "beam". Note that this does not imply whether the UE is aware of the TRP and the beam transmitted on it by the PRS.

[0107] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window 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.”

[0108] A “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 by PDSCH are also supported by 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.

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

[0110] Figure 4BExamples of various channels within the downlink time slot of a radio frame are explained. In NR, the channel bandwidth, or system bandwidth, is divided into multiple BWPs. A BWP is a set of adjacent PRBs selected from a contiguous 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 an SSB.

[0111] Reference Figure 4B The 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 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 (such as System Information Blocks (SIBs)) not transmitted through the PBCH, and paging messages.

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

[0113] exist Figure 4BIn 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 4B 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.

[0114] 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., PUSCH). Multiple (e.g., up to eight) 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 coding rates.

[0115] 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. Additionally, 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., positioning SRS, PTRS) may be referred to as "UL-PRS." Furthermore, 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."

[0116] Further referring to DL-PRS, which has been defined for NR positioning to enable the UE to detect and measure more neighboring TRPs. Several configurations are supported to achieve various deployments (e.g., indoor, outdoor, sub-6 GHz, mmW). Additionally, beam sweeping for PRS is supported to support PRS beam operation. The table below illustrates the various types of reference signals that can be used for the various positioning methods supported in NR.

[0117]

[0118] Table 1

[0119] As mentioned above, NR supports various DL-PRS resource repetition and beam scanning options. Several purposes exist for repetitive DL-PRS resources, including (1) cross-repetition receive beam sweep, (2) combined gain for coverage extension, and (3) intra-instance silence. The parameters used to configure PRS repetition are shown below.

[0120]

[0121] Table 2

[0122] Figure 5 This is a diagram illustrating example PRS resource sets with different time intervals according to various aspects of this disclosure. Figure 5 In the example, time is represented horizontally and frequency is represented vertically. Each box represents a time slot in the time domain and a bandwidth in the frequency domain.

[0123] Figure 5 Two DL-PRS resource set configurations were explained—the first DL-PRS resource set configuration 510 and the second DL-PRS resource set configuration 550. Each DL-PRS resource set configuration 510 and 550 includes four PRS resources (labeled "Resource 1", "Resource 2", "Resource 3", and "Resource 4") and has a repetition factor of four. A repetition factor of four means that each of the four PRS resources is repeated four times in the DL-PRS resource set (i.e., transmitted four times). That is, each of the four PRS resources within the DL-PRS resource set is repeated four times.

[0124] The DL-PRS resource set configuration 510 has a time slot of one time slot, meaning that each repetition of a PRS resource (e.g., "Resource 1") begins on the first time slot after a previous repetition of that PRS resource. Therefore, as explained by the DL-PRS resource set configuration 510, four repetitions of each of the four PRS resources are grouped together. Specifically, the four repetitions of PRS resource "Resource 1" occupy the first four time slots of the DL-PRS resource set configuration 510 (i.e., time slots n to n+3), the four repetitions of PRS resource "Resource 2" occupy the second four time slots (i.e., time slots n+4 to n+7), the four repetitions of PRS resource "Resource 3" occupy the third four time slots (i.e., time slots n+8 to n+11), and the four repetitions of PRS resource "Resource 4" occupy the last four time slots (i.e., time slots n+12 to n+15).

[0125] Conversely, the DL-PRS resource set configuration 550 has a four-slot time interval, meaning that each repetition of a PRS resource (e.g., "Resource 2") begins on the fourth time slot after a previous repetition of that PRS resource. Therefore, as explained by the DL-PRS resource set configuration 550, the four repetitions of each of the four PRS resources are scheduled every fourth time slot. For example, the four repetitions of PRS resource "Resource 1" occupy the first, fifth, ninth, and thirteenth time slots of the DL-PRS resource set configuration 550 (i.e., time slots n, n+4, n+8, and n+12).

[0126] Note that, as Figure 5 As explained, the time span of a DL-PRS resource set containing repeating DL-PRS resources should not exceed the PRS periodicity. Furthermore, the UE receive beam sweep used to receive / measure the DL-PRS resource set is not specified but depends on the UE implementation.

[0127] The UE needs to accommodate various DL-PRS processing and buffering capabilities. For example, a maximum limit can be defined on the number of DL-PRS resources configured for the UE for all TRPs within a measurement window. Additionally, assuming a maximum PRS bandwidth, the duration of DL-PRS symbols that the UE can process per T ms, measured in milliseconds (ms), can be defined. The following table shows various parameters indicating the UE's capabilities.

[0128]

[0129] Table 3

[0130] The following table illustrates the various differences between PRS in LTE and NR.

[0131]

[0132] Table 4

[0133] Assuming the UE can handle the maximum PRS bandwidth in the frequency domain (e.g., 272 PRBs), the UE reports the duration 'N' of the DL-PRS symbols it can process per 'T' ms (called the PRS processing window) in milliseconds. Additionally, a limit is defined on the maximum number of DL-PRS resources configured for the UE for all TRPs within the measurement window. This limit can also be signaled as a UE capability.

[0134] The reporting granularity for UE / gNB timing measurements (e.g., DL-RSTD, UE Rx-Tx time difference, UL-RTOA, gNB Tx-Rx time difference, etc.) is defined as Where k is a configuration parameter with a minimum value of '0' and a maximum value of '0'. Refer to the measurement report mapping used for RSTD positioning. Figure 6 The various information elements (IEs) used for reporting RSTD measurements are explained. Specifically, “NR-DL-TDOA-MeasElement-rl6” 610 includes RSTD measurements from 0 to 'X' in the 0 to 'X' “nr-RSTD-rl6” field. “NR-DL-TDOA-MeasElement-rl6” 610 also includes the “nr-DL-TDOA-AdditionalMeasurements-rl6” field pointing to “NR-DL-TDOA-AdditionalMeasurements-rl6” IE 620. “NR-DL-TDOA-AdditionalMeasurements-rl6” IE 620 includes a sequence of “NR-DL-TDOA-AdditionalMeasurementElement-rl6” fields, each “NR-DL-TDOA-AdditionalMeasurementElement-rl6” field pointing to “NR-DL-TDOA-AdditionalMeasurementElement-rl6” IE 630.

[0135] The parameter 'k' is used to indicate the reporting granularity for RSTD measurements, Rx-Tx time difference measurements, etc. Location servers (e.g., LMF 270) provide a recommended value for 'k', referred to as 'kl' (also denoted as 'kl'). k 1 Then, the UE selects the value 'k', called 'k2' (also denoted as 'k'). k 2The system then notifies the location server of the selected value. The relationship between the UE's selected parameter 'k2' and the network-recommended value 'k1' needs to be determined. Additionally, for RSTD and UE Rx-Tx time difference reports, the relationship between 'k1' and 'k2', as well as the range of 'k1' and 'k2' in FR1, needs to be determined.

[0136] The location server should correctly set the value of 'kl' regarding the PRS bandwidth. That is, as the PRS bandwidth increases, 'kl' should be set to a smaller value, and vice versa. With this understanding, the value 'k2' chosen by the UE can be equal to or greater than 'k1'. In most scenarios, the UE should adhere to the recommended value from the location server (i.e., kl = k2), but in cases where the PRS bandwidth is greater than the active downlink BWP and the UE has not yet configured or requested an appropriate measurement interval (the period during which the UE's serving base station does not communicate with the UE to allow the UE to measure PRS from other base stations), 'k1' can be less than or equal to 'k2'.

[0137] Another consideration is that, as long as the UE supports PRS bandwidth, it is expected that the UE will meet the accuracy requirements for each PRS bandwidth. Therefore, the UE needs to use [equipment that meets these requirements]. The value of 'k2'.

[0138] To account for potential differences in bandwidth between the reference PRS resource or resource set (e.g., a PRS resource or resource set from a reference TRP used for RSTD measurements) and the neighboring PRS resource or resource set (e.g., a PRS resource or resource set from a neighboring TRP used for RSTD measurements), the minimum of the two bandwidths should be used. Furthermore, the UE can be configured to report up to four DL-RSTD measurements per TRP pair, in accordance with UE capabilities, where each measurement is performed between different DL-PRS resource pairs or DL-PRS resource set pairs configured for those TRPs within the DL-PRS. This is in Figure 6 As shown, in addition to the measurements reported in “NR-DL-TDOA-MeasElement-r16” IE 610, there can be up to three “NR-DL-TDOA-AdditionalMeasurementElement-rl6” fields in “NR-DL-TDOA-AdditionalMeasurement-r16” IE 620. Up to four measurements are performed on the same pair of TRPs, and all DL-RSTD measurements in the same report use a single reference timing.

[0139] These (up to four) DL-RSTD measurements on the same TRP pair can belong to different positioning frequency layers, therefore the constraint should be based on the minimum PRS bandwidth across the positioning frequency layers of the same TRP pair. Accordingly, this disclosure proposes the following relationship between the location server-recommended 'k' value (i.e., 'kl') and the UE-selected 'k' value (i.e., 'k2'):

[0140]

[0141] in It is the bandwidth from the PRS resource or resource set of the reference TRP. It comes from the neighbor TRP i The bandwidth of the PRS resources or resource set. i It is a location frequency layer index. ,and M It is the oversampling factor. Specifically, for all measurements, M It is a constant, but it can also be configurable, or the UE can recommend this value. M This can depend on the frequency band, FR1 / FR2 differentiation, and / or UE capabilities. For example, it can be selected from the set {1, 2, 4, 8}. M .along with M As the value increases, the limit of 'k2' decreases, thus increasing the granularity.

[0142] For example, given the above scenario, the UE can measure the first RSTD (denoted as "RSTD1") as "t2-tl", the second RSTD (denoted as "RSTD2") as "t3-tl", the third RSTD (denoted as "RSTD3") as "t4-tl", and the fourth RSTD (denoted as "RSTD4") as "t5-tl", where 'tl', 't2', 't3', 't4', and 't5' are the times of arrival (ToA) of the PRS from the corresponding TRP. In this example, 't2', 't3', and 't4' may be in a different frequency layer than 'tl' and 't5', while 'tl' and 't5' may be in the same frequency layer. In this case, all RSTD measurements will use the same 'k2' value.

[0143] Now referencing the measurement report mapping used for Rx-Tx positioning, Figure 7 and Figure 8The various information elements (IEs) used for reporting Rx-Tx time difference measurements are explained. Specifically, “NR-Multi-RTT-MeasElement-rl6” 710 includes a certain number of UERx-Tx time difference measurements in one or more “nr-UE-RxTxTimeDiff-rl6” fields. “NR-Multi-RTT-MeasElement-r16” 710 also includes a “nr-Multi-RTT-AdditionalMeasurements-r16” field pointing to “NR-Multi-RTT-AdditionalMeasurements-r16” IE 720. “NR-Multi-RTT-AdditionalMeasurements-r16” IE 720 includes a sequence of up to three “NR-Multi-RTT-AdditionalMeasurementElement-r16” fields, each “NR-Multi-RTT-AdditionalMeasurementElement-r16” field pointing to “NR-Multi-RTT-AdditionalMeasurementElement-r16” IE 730. Figure 8 In IE810, “NR-AdditionalPathList-rl6” can be used to report up to two additional paths for UE Rx-Tx time difference measurements. The “NR-AdditionalPath-rl6” field in IE810 points to IE820 for reporting the actual measurement. The relationship between the 'k' value ('k1') configured by the location server and the 'k' value ('k2') selected by the UE, discussed above regarding RSTD measurements, also applies to UE Rx-Tx time difference measurement reporting.

[0144] To account for potential differences in PRS resource bandwidth between multiple Rx-Tx time difference measurements for the same TRP pair, the minimum bandwidth across frequency layers should be used. Accordingly, this disclosure proposes the following relationship between the location server-recommended 'k' value ('kl') and the UE-selected 'k' value ('k2'):

[0145]

[0146] in It refers to the bandwidth of PRS resources or resource sets. i For locating the frequency layer index, and . The value is actually the sampling time, and M It is the oversampling factor. For all measurements, M It should be a constant, but it can also be configurable, or the UE can recommend a value. It can also, or alternatively, depend on bandwidth or the FR1 / FR2 distinction.

[0147] Now, referring to the determination of the measurement period used for PRS measurements, for the purpose of DL-PRS processing capabilities, any P The duration of DL-PRS symbols in milliseconds within the ms window ( K The capability is determined by either Type 1 or Type 2 time-based calculation. Type 1 or Type 2 is reported as a UE capability.

[0148] Type 1 duration calculation is as follows:

[0149]

[0150]

[0151] Type 2 duration calculation is as follows:

[0152]

[0153] In the above equation, S It is the location frequency layer containing potential DL-PRS resources. P The set of time slots of serving cells within the ms window, the potential DL-PRS resources considering the actual expected RSTD (e.g., given by the parameter "nr-DL-PRS-ExpectedRSTD") and the actual expected RSTD uncertainty (e.g., given by the parameter "nr-DL-PRS-ExpectedRSTD-Uncertainty") provided for each pair of DL-PRS resources or resource sets (target and reference). For type 1, [ T s 开始 , T s 结束 [This is a time slot] s The smallest interval in milliseconds corresponding to an integer number of OFDM symbols of the serving cell covers the union of potential PRS symbols and determines the time slot. s PRS symbol occupancy rate within the range. T s 开始 , T s 结束Consider the actual “nr-DL-PRS-ExpectedRSTD” and “nr-DL-PRS-ExpectedRSTD-Uncertainty” provided for each pair of DL-PRS resources or resource sets (target and reference).

[0154] For UE DL-PRS processing capability, the UE reports a combination of (N, T) values ​​per frequency band, where, as mentioned above, 'N' is the duration of DL-PRS symbols per 'T' ms that the UE can process for a given maximum bandwidth 'B' in MHz supported by the UE. Additionally, the UE reports a new parameter—the number of DL-PRS resources the UE can process in a time slot—reported per frequency band per SCS. The reported number of DL-PRS resources the UE can process in a time slot can be selected from the set {1, 2, 4, 8, 12, 16, 32, 64}.

[0155] The following value sets for 'N', 'T', and 'B' are currently supported. The value of 'N' can be selected from the set {0.125, 0.25, 0.5, 1, 2, 4, 8, 12, 16, 20, 25, 30, 35, 40, 45, 50} ms, the value of 'T' can be selected from the set {8, 16, 20, 30, 40, 80, 160, 320, 640, 1280} ms, and the value of the maximum bandwidth reported by the UE ('B') can be selected from the set {5, 10, 20, 40, 50, 80, 100, 200, 400} MHz.

[0156] The reporting of the (N, T) value of the maximum bandwidth in MHz is independent of the SCS. The UE capability for simultaneous DL-PRS processing across multiple positioning frequency layers is currently not supported (i.e., for UEs supporting multiple positioning frequency layers, it is expected that the UE will process one frequency layer at a time). The UE capability for DL-PRS processing is defined under the assumption of configured measurement gaps and a maximum ratio of measurement gap length (MGL) / measurement gap repetition period (MGRP) not exceeding 'X'%.

[0157] As mentioned above, two categories are defined for PRS duration calculation: Type 1 and Type 2. In Type 2, the entire duration of a time slot is considered in the PRS duration calculation even if only one PRS resource exists within a time slot, regardless of how many symbols it occupies. Type 2 duration calculation is more conservative than Type 1, but the two types are roughly equivalent when PRS symbols occupy most of the time slot duration. For duration measurement purposes, using only the more conservative Type 2 is preferable to having two separate formulas for Type 1 and Type 2.

[0158] Accordingly, this disclosure proposes to define the RSTD measurement period based on type 2 PRS duration calculation. Thus, the RSTD measurement period for type 1 PRS duration calculation should not be longer than that for type 2.

[0159] In order to derive the basic formula for the measurement period, the following assumptions are made: (1) a positioning frequency layer, (2) a shared PRS periodicity among all configured PRS resources, (3) no loss of PRS opportunity due to handover (HO), overlap with SSB or other reasons, (4) no received beam sweep (FR1), and (5) one sample per PRS resource.

[0160] Figure 9 This is a diagram 900 illustrating several DL-PRS resources spanning a given time duration (in milliseconds) according to various aspects of this disclosure. Figure 9 In the example, time is represented horizontally and frequency is represented vertically. Each box represents a symbol in the time domain and a certain amount of bandwidth in the frequency domain.

[0161] exist Figure 9 In the example, there are three DL-PRS resources (distinguished by different hashes), each with a repetition factor of four within a time slot (14 symbols). These DL-PRS resources can be parts of the same or different sets of DL-PRS resources. A repetition factor of four means that each of the three PRS resources is repeated four times within a time slot (i.e., transmitted four times). These DL-PRS resources have a one-symbol time slot, meaning that each repetition of a PRS resource begins on the first symbol after a previous repetition of that PRS resource. Therefore, as... Figure 9 As explained in the text, the four repetitions of each of the three PRS resources are grouped together in four consecutive symbols.

[0162] exist Figure 9 In the example, the first two slots (i.e., the first two groups of 14 symbols) correspond to the first and last slots of the PRS timing or instance. The length of the PRS timing is denoted as L. PRS (Marked as "L_PRS"). Specifically, L PRS This refers to the time from the first symbol of the first DL-PRS resource at the PRS timing to the last symbol of the last DL-PRS resource at the PRS timing. Thus, in Figure 9 In the example, L PRS Crossing L PRS One time slot, that is, from time slot '0' to time slot 'L'. PRS -1' (marked as "L_PRS-1").

[0163] like Figure 9As shown, the PRS periodicity (i.e., the time from the first repetition of the first DL-PRS resource in the first PRS instance to the same first repetition of the same first DL-PRS resource in the next PRS instance) is represented as T. PRS (Marked as "T_PRS"). Thus, in Figure 9 In the example, the PRS timing is interpreted as spanning T PRS One time slot, that is, from time slot '0' to time slot 'T'. PRS -1' (marked as "T_PRS-1").

[0164] The UE can measure or sample one or more repetitions of PRS resources within a time slot, depending on the UE's reported capabilities for 'N' (the duration of DL-PRS symbols in milliseconds that the UE can process per 'T' ms) and 'T' (the number of milliseconds within which the UE can process DL-PRS of duration 'N' ms). Such measurements or samples may also be referred to as measurement instances. If L PRS If the value is less than or equal to 'N', the UE only needs 'T' ms to process the PRS resource. Otherwise, the UE needs to measure the PRS resource in a cyclic manner, and the measurement period consists of 'T', the measurement interval period (MGP), and T. PRS The scaling factor is the maximum value. Similarly, if the number of PRS resources in a time slot (labeled as...) If the value is less than or equal to a prime number 'N', then the UE only needs 'T' ms to process the PRS resource. Otherwise, the measurement period is scaled similarly to the 'N' case.

[0165] Accordingly, this disclosure defines the RSTD measurement period as:

[0166]

[0167] Where 'N' is the duration of DL-PRS symbols that the UE can process per 'T' ms, in milliseconds, for a given maximum bandwidth 'B' supported by the UE in MHz; the prime number 'N' (N') is the number of DL-PRS resources that the UE can process in a time slot, which is reported per frequency band per SCS; L PRS It represents the span of a PRS timing (or instance), which is defined based on Type 2 epochal calculations as the time from the first slot of the earliest PRS resource to the last slot of the latest PRS resource. It is the number of PRS resources configured in the time slot; It is the periodicity of PRS; and MGP is the measurement interval period. Parameters Define the number of measurement instances and parameters. It is a bandwidth periodicity parameter.

[0168] Figure 10An example wireless communication method 1000 according to various aspects of this disclosure has been explained. In one aspect, method 1000 can be performed by a UE (e.g., any UE described herein).

[0169] In 1010, the UE receives configuration of one or more PRS resources from a network entity (e.g., LMF 270) to measure PRS-periodic T during a positioning session. PRS and PRS timing length L PRS The one or more PRS resources. In one aspect, operation 1010 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, wherein any or all of the components may be considered as means for performing the operation.

[0170] In 1020, the UE measures the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources that the UE is expected to process, multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds and a PRS periodicity T. PRS and the periodicity of the measurement gap of at least one measurement gap. In one aspect, operation 1020 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, wherein any or all of the components may be considered as means for performing the operation.

[0171] Figure 11 An example wireless communication method 1100 according to various aspects of this disclosure has been explained. In one aspect, method 1100 can be performed by a UE (e.g., any UE described herein).

[0172] At 1110, the UE receives from a network entity (e.g., LMF 270) a recommendation for a first granularity (e.g., 'kl') of positioning measurements used to report one or more PRS resources during a positioning session. In one aspect, operation 1110 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, wherein any or all of these components may be considered means for performing the operation.

[0173] At 1120, the UE performs one or more positioning measurements on the one or more PRS resources. In one aspect, operation 1120 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, wherein any or all of the components may be considered as means for performing the operation.

[0174] At 1130, the UE reports the one or more positioning measurements at a second granularity ('k2'), wherein the second granularity is less than or equal to the first granularity and greater than or equal to the minimum granularity, and wherein the minimum granularity is based on the PRS bandwidth parameter associated with the one or more PRS resources. In one aspect, operation 1130 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, wherein any or all of these components may be considered means for performing the operation.

[0175] As will be understood, the technical advantage of methods 1000 and 1100 is that they enable the location server and the UE to communicate about the duration of the measurement period required by the UE, thereby enabling the location server and / or the UE to determine the waiting time for the positioning procedure and / or positioning measurement.

[0176] In the detailed description above, it can be seen that different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those of 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. 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 explicitly 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.

[0177] Examples of implementations are described in the following numbered clauses.

[0178] Clause 1. A radio positioning method performed by a user equipment (UE), comprising: receiving a configuration of one or more positioning reference signal (PRS) resources from a network entity to measure a periodicity T with PRS during a positioning session. PRS and PRS timing length L PRS The measurement of the one or more PRS resources; and the measurement of the one or more PRS resources during a measurement period, wherein the measurement period is based on the number of measurement instances of the one or more PRS resources expected to be processed by the UE multiplied by a periodicity parameter, wherein the periodicity parameter is based on a PRS processing window of 'T' milliseconds and a PRS periodicity T. PRSAnd the periodicity of the measurement gap of at least one measurement gap.

[0179] Clause 2. As in Clause 1, where the periodic parameter is the PRS processing window, the PRS periodicity T PRS And the maximum value of the periodicity of the measurement gap.

[0180] Clause 3. The method described in any of Clauses 1 to 2, wherein the periodicity parameter is not less than the PRS processing window and the PRS periodicity T. PRS And the maximum value of the periodicity of the measurement gap.

[0181] Clause 4. The method of any of Clauses 1 to 3, wherein the number of measurement instances is based on the PRS timing length L. PRS .

[0182] Clause 5. As in Clause 4, where the PRS timing length L PRS The duration of a PRS symbol in milliseconds within any PRS processing window is determined based on whether Type 1 or Type 2 epoch calculation is used.

[0183] Clause 6. The method of any one of Clauses 1 to 5, wherein 'T' milliseconds is the number of milliseconds in which the UE can process PRS symbols of duration 'N' in milliseconds during its period, given the maximum PRS bandwidth.

[0184] Clause 7. The method of any one of Clauses 1 to 6, wherein

[0185] PRS timing length L PRS It is the time from the first symbol of the first PRS resource of the PRS timing to the last symbol of the last PRS resource of that PRS timing.

[0186] Clause 8. The method of any of Clauses 1 to 7, wherein the PRS periodic T PRS It is the time from the first repetition of the first PRS resource at the first PRS timing to the first repetition of the first PRS resource at the next PRS timing.

[0187] Clause 9. The method of any one of Clauses 1 to 8, wherein: the measurement period is a Reference Signal Time Difference (RSTD) measurement period, and the one or more PRS resources are transmitted by a Reference Transmitter Receiver (TRP) and at least one neighboring TRP.

[0188] Clause 10. The method of any one of Clauses 1 to 8, wherein the measurement period is the period of receiving the transmission (Rx-Tx) time difference measurement.

[0189] Clause 11. A radio positioning method performed by a user equipment (UE), comprising: receiving from a network entity a recommendation for a first granularity of positioning measurements for reporting one or more positioning reference signal (PRS) resources during a positioning session; performing one or more positioning measurements on the one or more PRS resources; and reporting the one or more positioning measurements at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to a minimum granularity, and wherein the minimum granularity is based on a PRS bandwidth parameter associated with the one or more PRS resources.

[0190] Clause 12. The method of Clause 11, wherein the PRS bandwidth parameter includes the reciprocal of the minimum bandwidth of the one or more PRS resources.

[0191] Clause 13. The method of any one of Clauses 11 to 12, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across all positioning frequency layers on which the one or more PRS resources are transmitted.

[0192] Clause 14. The method of any one of Clauses 11 to 13, wherein the PRS bandwidth parameter includes the reciprocal of the oversampling factor.

[0193] Clause 15. The method of Clause 14, wherein the oversampling factor satisfies the following conditions: configured to the UE by a network entity, recommended by the UE, based on the frequency range of the one or more PRS resources, or the capability of the UE.

[0194] Clause 16. The method of any one of Clauses 11 to 15, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across a reference PRS resource of the one or more PRS resources and at least one neighboring PRS resource of the one or more PRS resources.

[0195] Clause 17. The method of any one of Clauses 15 to 16, wherein the reference PRS resource is transmitted by the reference transmit receiving point (TRP), and the at least one neighbor PRS resource is transmitted by at least one neighbor TRP.

[0196] Clause 18. The method of any one of Clauses 11 to 17, wherein the PRS bandwidth parameter comprises a logarithmic function of the inverse of the bandwidth of the one or more PRS resources.

[0197] Clause 19. The method of any one of Clauses 11 to 18, wherein the one or more positioning measurements include one or more reference signal time difference (RSTD) measurements.

[0198] Clause 20. The method of any one of Clauses 11 to 19, wherein the one or more positioning measurements include one or more received-transmit (Rx-Tx) time difference measurements.

[0199] Clause 21. An apparatus comprising: a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, the memory, the at least one transceiver, and the at least one processor being configured to perform a method according to any one of Clauses 1 to 20.

[0200] Clause 22. An apparatus for performing a method according to any one of Clauses 1 to 20.

[0201] Clause 23. A non-transient computer-readable medium storing computer-executable instructions, the computer-executable instructions including at least one instruction for causing a computer or processor to perform a method according to any one of Clauses 1 to 20.

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

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

[0204] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may 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 alternative embodiments, 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.

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

[0206] 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, disks and discs 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.

[0207] Although the foregoing disclosure illustrates 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: Receive recommendations from network entities for the first granularity of positioning measurements used to report one or more Positioning Reference Signal (PRS) resources during a positioning session; Perform one or more positioning measurements on the one or more PRS resources; and The one or more positioning measurements are reported at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to the minimum granularity, and wherein the minimum granularity is based on the PRS bandwidth parameter associated with the one or more PRS resources.

2. The method of claim 1, wherein the PRS bandwidth parameter includes the reciprocal of the minimum bandwidth of the one or more PRS resources.

3. The method of claim 1, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across all positioning frequency layers on which the one or more PRS resources are transmitted.

4. The method of claim 1, wherein the PRS bandwidth parameter includes the reciprocal of the oversampling factor.

5. The method of claim 4, wherein the oversampling factor satisfies the following condition: Configured by the network entity to the UE, Recommended by the UE, Based on the frequency range of the one or more PRS resources, or This refers to the capabilities of the UE.

6. The method of claim 1, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across a reference PRS resource of the one or more PRS resources and at least one neighboring PRS resource of the one or more PRS resources.

7. The method of claim 6, wherein the reference PRS resource is transmitted by the reference transmit receiving point (TRP), and the at least one neighbor PRS resource is transmitted by at least one neighbor TRP.

8. The method of claim 1, wherein the PRS bandwidth parameter comprises a logarithmic function of the reciprocal of the bandwidth of the one or more PRS resources.

9. The method of claim 1, wherein the one or more positioning measurements include one or more Reference Signal Time Difference (RSTD) measurements.

10. The method of claim 1, wherein the one or more positioning measurements include one or more received transmission Rx-Tx time difference measurements.

11. 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: Receive, via the at least one transceiver, a recommendation for a first granularity of positioning measurements for reporting one or more Positioning Reference Signal (PRS) resources during a positioning session from a network entity; Perform one or more positioning measurements on the one or more PRS resources; and The one or more positioning measurements are reported at a second granularity, wherein the second granularity is less than or equal to the first granularity and greater than or equal to the minimum granularity, and wherein the minimum granularity is based on the PRS bandwidth parameter associated with the one or more PRS resources.

12. The UE of claim 11, wherein the PRS bandwidth parameter includes the reciprocal of the minimum bandwidth of the one or more PRS resources.

13. The UE of claim 11, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across all positioning frequency layers on which the one or more PRS resources are transmitted.

14. The UE of claim 11, wherein the PRS bandwidth parameter includes the reciprocal of the oversampling factor.

15. The UE of claim 14, wherein the oversampling factor satisfies the following condition: Configured by the network entity to the UE, Recommended by the UE, Based on the frequency range of the one or more PRS resources, or This refers to the capabilities of the UE.

16. The UE of claim 11, wherein the PRS bandwidth parameter includes the minimum bandwidth of the one or more PRS resources across a reference PRS resource of the one or more PRS resources and at least one neighboring PRS resource of the one or more PRS resources.

17. The UE of claim 16, wherein the reference PRS resource is transmitted by the reference transmit receiving point (TRP), and the at least one neighbor PRS resource is transmitted by at least one neighbor TRP.

18. The UE of claim 11, wherein the PRS bandwidth parameter comprises a logarithmic function of the reciprocal of the bandwidth of the one or more PRS resources.

19. The UE of claim 11, wherein the one or more positioning measurements include one or more Reference Signal Time Difference (RSTD) measurements.

20. The UE of claim 11, wherein the one or more positioning measurements include one or more received transmission Rx-Tx time difference measurements.