Reference device hardware group delay calibration

Abstract

In an aspect, a communication node selects reference devices for a positioning procedure based on hardware group capabilities (e.g., RTT, differential RTT, double differential RTT, TDOA, etc.) associated with the reference devices involved in the positioning procedure. In another aspect, distances between the reference devices are estimated based on timing measurements of reference signals used for positioning. A hardware group delay associated with the reference devices is estimated based on (i) an estimated distance between a first reference device and a second reference device, and (ii) a known distance between the first reference device and the second reference device.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims the benefit of U.S. Provisional Application No. 63 / 051,206, filed July 13, 2020, entitled “BASE STATION HARDWARE GROUPDELAY CALIBRATION,” and U.S. Non-Provisional Application No. 17 / 348,553, filed June 15, 2021, entitled “REFERENCE DEVICE HARDWARE GROUP DELAY CALIBRATION,” both of which have been assigned to the assignee of this application and are expressly incorporated herein by reference in their entirety. Technical Field

[0003] Generally, aspects of this disclosure relate to wireless communications, and more specifically, aspects of this disclosure relate to hardware group delays in reference devices (e.g., base stations or reference user equipment (UE)). Background Technology

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including the transitional 2.5G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., 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), and TDMA variants of the Global System for Mobile Access (GSM).

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data transmission speeds, more 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 of data to each of tens of thousands of users, or 1 gigabit per second to dozens of workers on an office floor. To support large-scale wireless deployments, it should support hundreds of thousands of simultaneous connections. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signaling efficiency should be enhanced, and latency should be significantly reduced compared to the current standard. Summary of the Invention

[0006] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be deemed to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose of presenting certain concepts relating to one or more aspects disclosed herein in a simplified form to precede the detailed description presented below.

[0007] In one aspect, a method of operating a communication node includes obtaining a hardware group delay calibration capability associated with each of a plurality of reference devices; selecting a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and determining one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0008] In some aspects, the plurality of reference devices includes at least one base station, at least one reference UE, or a combination thereof.

[0009] In some aspects, the method includes sending a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining includes receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0010] In some aspects, the determining is performed in association with a positioning procedure for a user equipment (UE).

[0011] In some aspects, the communication node corresponds to the UE, and the positioning procedure is a UE-based positioning procedure.

[0012] In some aspects, the communication node corresponds to a network device, and the positioning procedure is a network-based positioning procedure.

[0013] In some aspects, the positioning procedure corresponds to a round-trip time (RTT) positioning procedure.

[0014] In some aspects, the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0015] In some aspects, the positioning procedure corresponds to a time difference of arrival (TDOA) based positioning procedure.

[0016] In some aspects, the determining is performed independent of any UE positioning procedure.

[0017] In some aspects, the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0018] In some aspects, the selection selects the selected reference device as the reference device associated with a narrowest hardware group delay error range.

[0019] In some aspects, the selection selects the selected reference device based on hardware group delay calibration capabilities associated with the plurality of reference devices and at least one secondary criterion.

[0020] In some aspects, the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0021] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0022] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0023] In some aspects, the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0024] In an aspect, a method of operating a communication node includes obtaining an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimating a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0025] In some aspects, the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0026] In some aspects, the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0027] In some aspects, the one or more timing measurements are associated with a round trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0028] In some aspects, the first reference device is associated with a reference hardware group delay.

[0029] In some aspects, the estimating estimates a residual hardware group delay corresponding to a difference between a hardware group delay of the second reference device and a reference hardware group delay of the first reference device.

[0030] In one aspect, a communication node 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 configured to: obtain a hardware group delay calibration capability associated with each of a plurality of reference devices; select a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capabilities associated with the plurality of reference devices; and determine one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0031] In some aspects, the plurality of reference devices includes at least one base station, at least one reference UE, or a combination thereof.

[0032] In some aspects, the at least one processor is further configured to: transmit, via the at least one transceiver, a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining includes receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0033] In some aspects, the determining is performed in association with a positioning procedure for a user equipment (UE).

[0034] In some aspects, the communication node corresponds to the UE, and the positioning procedure is a UE-based positioning procedure.

[0035] In some aspects, the communication node corresponds to a network device, and the positioning procedure is a network-based positioning procedure.

[0036] In some aspects, the positioning procedure corresponds to a round-trip-time (RTT) positioning procedure.

[0037] In some aspects, the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0038] In some aspects, the positioning procedure corresponds to a time-difference-of-arrival (TDOA) based positioning procedure.

[0039] In some aspects, the determining is performed independent of any UE positioning procedure.

[0040] In some aspects, the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0041] In some aspects, the selecting selects the selected reference device as the reference device associated with a narrowest hardware group delay error range.

[0042] In some aspects, the selection is based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion.

[0043] In some aspects, the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0044] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0045] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0046] In some aspects, the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0047] In one aspect, a communication node 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 configured to: obtain an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimate a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0048] In some aspects, the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0049] In some aspects, the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0050] In some aspects, the one or more timing measurements are associated with a round trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0051] In some aspects, the first reference device is associated with a reference hardware group delay.

[0052] In some aspects, the estimating estimates a residual hardware group delay corresponding to a difference between a hardware group delay of the second reference device and a reference hardware group delay of the first reference device.

[0053] In one aspect, a communication node includes means for obtaining a hardware group delay calibration capability associated with each of a plurality of reference devices; means for selecting a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capabilities associated with the plurality of reference devices; and means for determining one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0054] In some aspects, the plurality of reference devices includes at least one base station, at least one reference UE, or a combination thereof.

[0055] In some aspects, the method includes means for transmitting a hardware group delay calibration capability request to each of a plurality of reference devices, wherein the obtaining includes receiving a hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0056] In some aspects, the determining is performed in association with a positioning procedure for a user equipment (UE).

[0057] In some aspects, the communication node corresponds to the UE, and the positioning procedure is a UE-based positioning procedure.

[0058] In some aspects, the communication node corresponds to a network device, and the positioning procedure is a network-based positioning procedure.

[0059] In some aspects, the positioning procedure corresponds to a round-trip-time (RTT) positioning procedure.

[0060] In some aspects, the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0061] In some aspects, the positioning procedure corresponds to a time-difference-of-arrival (TDOA) based positioning procedure.

[0062] In some aspects, the determining is performed independent of any UE positioning procedure.

[0063] In some aspects, the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0064] In some aspects, the selecting selects the selected reference device as the reference device associated with a narrowest hardware group delay error range.

[0065] In some aspects, the selection is based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion.

[0066] In some aspects, the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0067] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0068] In some aspects, the hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0069] In some aspects, the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0070] In an aspect, a communication node comprises means for obtaining an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and means for estimating a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0071] In some aspects, the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0072] In some aspects, the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0073] In some aspects, the one or more timing measurements are associated with a round trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0074] In some aspects, the first reference device is associated with a reference hardware group delay.

[0075] In some aspects, the estimating estimates a residual hardware group delay corresponding to a difference between the hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

[0076] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication node, cause the communication node to: obtain a hardware group delay calibration capability associated with each of a plurality of reference devices; select a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capabilities associated with the plurality of reference devices; and determine one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0077] In some aspects, the plurality of reference devices includes at least one base station, at least one reference UE, or a combination thereof.

[0078] In some aspects, the one or more instructions further cause the communication node to: transmit a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining comprises receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0079] In some aspects, the determining is performed in association with a positioning procedure for a user equipment (UE).

[0080] In some aspects, the communication node corresponds to the UE, and the positioning procedure is a UE-based positioning procedure.

[0081] In some aspects, the communication node corresponds to a network device, and the positioning procedure is a network-based positioning procedure.

[0082] In some aspects, the positioning procedure corresponds to a round-trip time (RTT) positioning procedure.

[0083] In some aspects, the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0084] In some aspects, the positioning procedure corresponds to a time difference of arrival (TDOA) based positioning procedure.

[0085] In some aspects, the determining is performed independent of any UE positioning procedure.

[0086] In some aspects, the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0087] In some aspects, the selecting selects the selected reference device as the reference device associated with the narrowest hardware group delay error range.

[0088] In some aspects, the selecting selects the selected reference device based on the hardware group delay calibration capabilities associated with the plurality of reference devices and at least one secondary criterion.

[0089] In some aspects, the at least one secondary criterion comprises reference signal received power (RSRP) measurements between the plurality of reference devices and a user equipment (UE).

[0090] In some aspects, a hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0091] In some aspects, a hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0092] In some aspects, the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0093] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication node, cause the communication node to: obtain an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimate a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0094] In some aspects, the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0095] In some aspects, the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0096] In some aspects, the one or more timing measurements are associated with a round trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0097] In some aspects, the first reference device is associated with a reference hardware group delay.

[0098] In some aspects, the estimating estimates a residual hardware group delay corresponding to a difference between the hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

[0099] Other objects 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 DRAWINGS

[0100] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of such aspects and not limitation thereof.

[0101] Figure 1 FIGURE illustrates an example wireless communication system, in accordance with various aspects.

[0102] Figure 2A AND Figure 2B FIGURE illustrates an example wireless network structure, in accordance with various aspects.

[0103] Figure 3 is a block diagram illustrating an example UE, in accordance with various aspects.

[0104] Figure 4 is a diagram illustrating an example of a frame structure for use in a wireless telecommunications system, in accordance with one aspect of the disclosure.

[0105] Figure 5 is a diagram illustrating an example technique for determining a location of a UE using information obtained from multiple base stations.

[0106] Figure 6 is a diagram showing an example timing of round trip time (RTT) measurement signals exchanged between a base station and a UE, in accordance with aspects of the disclosure.

[0107] Figure 7 FIGURE illustrates an example wireless communication system, in accordance with various aspects of the disclosure.

[0108] Figure 8 FIGURE illustrates an example wireless communication system, in accordance with various aspects of the disclosure.

[0109] Figure 9 is a diagram showing an example timing of RTT measurement signals exchanged between a base station and a UE, in accordance with aspects of the disclosure.

[0110] Figure 10 is a diagram showing an example timing of RTT measurement signals exchanged between a base station (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein), in accordance with other aspects of the disclosure.

[0111] Figure 11 is a diagram showing an example timing of RTT measurement signals exchanged between a base station (gNB) (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein), in accordance with aspects of the disclosure.

[0112] Figure 12 FIGURE illustrates an exemplary wireless communication system, in accordance with aspects of the present disclosure.

[0113] Figure 13 FIGURE illustrates an exemplary method of wireless communication, in accordance with aspects of the present disclosure.

[0114] Figure 14 FIGURE illustrates an exemplary method of wireless communication, in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0115] Aspects of the present disclosure are provided in the following description and related drawings. Alternatives to the aspects of the present disclosure can be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure, or elements of the present disclosure with trivial variations are not described in detail in order to avoid obscuring aspects of the present disclosure.

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

[0117] Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular applications, design choices, and / or implementation technologies or techniques, among others.

[0118] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (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 sequence(s) of actions described herein can be considered to be embodied entirely within any form of non-transitory computer readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or direct an associated processor of a device to perform the functionality described herein. The Thus, the various aspects of the disclosure can be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects can be described herein as, for example, “logic configured to” perform the described action.

[0119] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE can be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. 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 referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected to one or more external networks such as the Internet and / or other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11, etc.) and so on.

[0120] A base station can operate according to one of several RATs with which UEs communicate, depending on the network in which the base station is deployed, and the base station can be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a New Radio (NR) Node B (also referred to as gNB, or gNodeB), etc. Further, in some systems the base station can provide pure edge node signaling functions while in other systems it can provide additional control and / or network management functions. A communication link through which UEs can send signals to the base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The base station can send signals to the UEs through a communication link called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to UL / reverse or DL / forward traffic channels.

[0121] The term “base station” can refer to a single physical transmission point or can include multiple physical transmission points that can or can not be co-located. For example, where the term “base station” refers to a single physical transmission point, the physical transmission point can be an antenna of the base station corresponding to a cell of the base station. Where the term “base station” refers to multiple co-located physical transmission points, the physical transmission points can be an array of antennas of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term “base station” refers to multiple non-co-located physical transmission points, the physical transmission points can be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical transmission points can be the serving base station that receives the measurement report from the UE and a neighbor base station whose reference RF signals the UE is measuring.

[0122] An “RF signal” includes electromagnetic waves of a given frequency that transmit information across space by a transmitter and receiver. As used herein, a transmitter can transmit a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, the receiver can receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal.

[0123] According to various aspects, Figure 1 An exemplary wireless communications system 100 is illustrated. The wireless communications system 100, which can also be referred to as a wireless wide area network (WWAN), can include various base stations 102 and various UEs 104. The base stations 102 can include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station can include eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a 5G network, or a combination of both, and the small cell base stations can include femtocells, picocells, microcells, etc.

[0124] The base stations 102 can collectively form a RAN, and interface with a core network 170 (e.g., evolved packet core (EPC) or next generation core (NGC)) through backhaul links 122, and with one or more location servers 172 through the core network 170. In addition to other functions, the base stations 102 can perform functions such as: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, delivery of warning messages, positioning, and delivery of system information. The base stations 102 can communicate with each other directly or indirectly (e.g., through the EPC / NGC) over backhaul links 134, which can be wired or wireless.

[0125] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more of the cells can be supported by the base station 102 in each coverage area 110. A “cell” is a logical communication entity used for communication with a base station, e.g., on a

[0126] While the geographic coverage area 110 for a base station 102 can overlap for two or more base stations 102, the geographic coverage area 110 for a base station 102 can also be divided into multiple adjacent cells. A cell can be the geographic coverage area of a base station and / or a base station subsystem serving as an access point in a network. In some examples, the geographic coverage area for a base station can be divided into multiple cells, each of which can be served by the base station or by a base station subsystem. In some examples, cells can be designated to serve different types of traffic (e.g., control channels or user data channels).

[0127] The communication links 120 between the base stations 102 and the UEs 104 can include UL (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 can be through one or more carrier frequencies. Allocation of carriers can be asymmetric with respect to DL and UL (e.g., more or less carriers can be allocated for DL than for UL).

[0128] Wireless communications system 100 can also include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or WLAN AP 150 can perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0129] The small cell base stations 102' can operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base stations 102' can employ LTE or 5G technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base stations 102' employing LTE / 5G in an unlicensed frequency spectrum can boost coverage and / or increase capacity for access networks. LTE in an unlicensed frequency spectrum can be referred to as LTE-Unlicensed (LTE-U), License Assisted Access (LAA), or MulteFire.

[0130] The wireless communications system 100 can also include millimeter wave (mmW) base stations 180 that can operate in mmW frequencies and / or near mmW frequencies in communication with UEs 182. Extremely high frequency (EHF) is the part of the radio frequency (RF) in the electromagnetic spectrum between 30 GHz and 300 GHz. It is above the super high frequency (SHF) or microwave band. The EHF band is between 30,000 MHz and 300,000 MHz and has wavelengths from 1 millimeter to 10 millimeters. Radio waves in this band are short and can be used for directional communication from small antennas. This band is used for short-range, high-bandwidth communication, for example, in wireless personal area networks. In some aspects, the mmW base stations 180 can operate in mmW frequencies between 30 GHz and 300 GHz. In some aspects, the mmW base stations 180 can operate in near mmW frequencies between 3 GHz and 30 GHz. The use of mmW / near mmW radio frequency frequency bands can provide for very high bandwidths which can be used for high-speed communication of data. The use of mmW / near mmW radio frequency frequency bands can also provide for very small, low power, and low cost base stations 180. In some aspects, the use of mmW / near mmW radio frequency frequency bands can be used to increase the capacity of a wireless communication system.

[0131] Transmit beamforming is a technique for focusing the RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, which provides a faster (in terms of data rate) and stronger RF signal for the receiving device. To change the direction of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters. For example, a network node can use an array of antennas (referred to as a “phased array” or “antenna array”), which creates a beam of signals that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to each of the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0132] The transmit beams can be quasi-collocated, which means that they appear to have the same parameters to a receiver (e.g., a UE), regardless of whether the network node’s own transmit antennas are physically co-located. In NR, there are four types of quasi-collocation (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a 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 a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameters of a second reference RF signal transmitted on the same channel.

[0133] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver can increase a gain setting and / or adjust a phase setting of an antenna array in a particular direction to amplify (e.g., increase a gain level) an RF signal received from that direction. Thus, when a receiver is said to beamform in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.

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

[0135] Note that a “downlink” beam can be a transmit beam or a receive beam, depending on which entity is forming it. For example, if a base station is forming a downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if a UE is forming a downlink beam, it is a receive beam to receive a downlink reference signal. Similarly, an “uplink” beam can be a transmit beam or a receive beam, depending on which entity is forming it. For example, if a base station is forming an uplink beam, it is an uplink receive beam, while if a UE is forming an uplink beam, it is an uplink transmit beam.

[0136] In 5G, the frequency spectrum in which wireless nodes (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates a RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels. A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once the RRC connection is established between the UE 104 and the anchor carrier and can be used to provide additional radio resources. The secondary carrier can contain only the necessary signaling information and signals, e.g., those that are UE-specific, can be absent from the secondary carrier since both the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier for any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier on which a certain base station communicates, the terms “cell,” “serving cell,” “component carrier,” “carrier frequency,” etc. can be used interchangeably.

[0137] For example, still referring to Figure 1One of the frequencies used by the macrocell base station 102 can be an anchor carrier (or "PCell") and other frequencies used by the macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) as compared to a single 20 MHz carrier.

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

[0139] The wireless communication system 100 can further include a UE 164 that can communicate with the macrocell base station 102 through the communication link 120 and / or with the mmW base station 180 through the mmW communication link 184. For example, the macrocell base station 102 can support a PCell and one or more SCells for the UE 164, and the mmW base station 180 can support one or more SCells for the UE 164. In one aspect, the UE 164 can include a positioning component 166 that can enable the UE 164 to perform the UE operations described herein. Note that although only one UE is illustrated as having the fully staggered SRS component 166 in FIG. 1, any of the UEs in FIG. 1 can be configured to perform the UE operations described herein. Figure 1 Figure 1

[0140] According to various aspects, Figure 2A ​​​An example wireless network structure 200 is illustrated. For example, the NGC 210 (also referred to as a “5GC”) can be viewed functionally as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User and control plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the NGC 210, and specifically to control plane functions 214 and user plane functions 212. In an additional configuration, an eNB 224 can also be connected to the NGC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to the user plane functions 212. Further, eNB 224 can directly communicate with gNB 222 via the backhaul connection 223. In some configurations, the New RAN 220 can only have one or more gNBs 222, while other configurations include one or more of both eNBs 224 and gNBs 222. Any of the gNBs 222 or eNBs 224 can communicate with UEs 204 (e.g., Figure 1 Any of the UEs depicted in FIG. 3 can be in communication with one another. Another optional aspect can include a location server 230, which can be in communication with the NGC 210 to provide location assistance for UEs 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or can alternatively each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network NGC 210, and / or via the Internet (not illustrated). Further, the location server 230 can be integrated into a component of the core network, or can alternatively be external to the core network.

[0141] According to various aspects, Figure 2BAnother example wireless network structure 250 is illustrated. For example, an NGC 260 (also referred to as a “5GC”) can be viewed functionally as control plane functions (provided by access and mobility management function (AMF) / user plane function (UPF) 264) and user plane functions (provided by session management function (SMF) 262) that operate together to form the core network (i.e., NGC 260). User and control plane interfaces 263 and 265 connect the eNB 224 to the NGC 260 and specifically to SMF 262 and AMF / UPF 264, respectively. In an additional configuration, gNB 222 can also be connected to the NGC 260 via the control plane interface 265 to AMF 264 and user plane interface 263 to UPF 262. Further, eNB 224 can communicate directly with gNB 222 via the backhaul connection 223, with or without gNB direct connectivity to the NGC 260. In some configurations, the New RAN 220 can only have one or more gNBs 222, while other configurations include one or more of both eNBs 224 and gNBs 222. Any of the gNBs 222, or eNBs 224, can communicate with UEs 204 (e.g., Figure 1 Any of the UEs depicted in FIG. 3 can communicate with each other over the wireless network structure 250. The base stations of the New RAN 220 communicate with the AMF side of the AMF / UPF 264 over the N2 interface and with the UPF side of the AMF / UPF 264 over the N3 interface.

[0142] The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful intercept, transport for session management (SM) messages between the UE 204 and SMF 262, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives a medium key established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF retrieves the security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives a key from the SEAF, which it uses to derive access-network specific keys. The functions of the AMF also include location management for regulatory services, transport for location service messages between the UE 204 and the location management function (LMF) 270, and between the New RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. Additionally, the AMF also supports non-3GPP access network functionality.

[0143] Functions of the UPF include serving as an anchor point for intra- / inter-RAT mobility when applicable, serving as an external protocol data unit (PDU) session point of interconnect to data networks (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful intercept (user plane collection), traffic usage reporting, quality of service (QoS) handling for user plane (e.g., UL / DL rate enforcement, reflection QoS marking in DL), UL traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding of one or more “end markers.”

[0144] Functions of the SMF 262 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF to route traffic to the proper destination, control of part of policy implementation and QoS, and downlink data notifications. The interface by which the SMF 262 communicates with the AMF side of the AMF / UPF 264 is referred to as the N11 interface.

[0145] Another optional aspect can include an LMF 270, which can be in communication with the NGC 260 to provide location assistance for UEs 204. The LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or can alternatively each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network NGC 260 and / or via the Internet (not illustrated).

[0146] Figure 3Figures illustrate several example components (represented by corresponding blocks) that can be incorporated into UE 302 (which can correspond to any of the UEs described herein), base station 304 (which can correspond to any of the base stations described herein), and network entity 306 (which can correspond to or embody any of the network functions described herein, including location server 230 and LMF 270) to support file transfer operations taught herein. It will be appreciated that these components can be implemented in different implementations in different types of apparatuses (e.g., in ASICs, in system-on-chips (SoCs), etc.). The illustrated components can also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system can include similar components to those described to provide similar functionality. Moreover, a given apparatus can contain one or more components. For example, an apparatus can include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0147] UE 302 and base station 304 each include at least one wireless communication device (represented by communication devices 308 and 314 (and 320 if apparatus 304 is a relay)) for communicating with other nodes via at least one designated RAT. For example, communication devices 308 and 314 can communicate over wireless communication links 360 that can correspond to communication links 120 in FIG. 1. Figure 1 Communication devices 308 of UE 302 and communication devices 314 of base station 304 communicate with each other using wireless communication links 360 in FIG. 3. Each communication device 308 includes at least one transmitter (represented by transmitter 310) for transmitting and encoding signals (e.g., messages, indications, information, etc.) and at least one receiver (represented by receiver 312) for receiving and decoding signals (e.g., messages, indications, information, pilots, etc.). Similarly, each communication device 314 includes at least one transmitter (represented by transmitter 316) for transmitting signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 318) for receiving signals (e.g., messages, indications, information, etc.). If base station 304 is a relay station, each communication device 320 can include at least one transmitter (represented by transmitter 322) for transmitting signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 324) for receiving signals (e.g., messages, indications, information, etc.).

[0148] In some implementations, transmitters and receivers can include integrated devices (e.g., embodied as transmitter and receiver circuits of a single communication device, commonly referred to as a “transceiver”), in some implementations can include separate transmitter devices and separate receiver devices, or can be embodied in other manners in other implementations. The wireless communication devices of base station 304 (e.g., one of a plurality of wireless communication devices) can also include a network listening module (NLM) or the like for performing various measurements.

[0149] Network entity 306 (and base station 304, if it is not a relay station) includes at least one communication device (represented by communication devices 326 and, optionally, 320) for communicating with other nodes. For example, communication device 326 can include a network interface configured to communicate with one or more network entities via a wire-based backhaul or wireless backhaul 370 (which can correspond to backhaul link 122 in FIG. 1). In some aspects, communication device 326 can be implemented as a transceiver configured to support wire-based or wireless signal communication, and transmitter 328 and receiver 330 can be integrated units. This communication can involve, for example, transmitting and receiving messages, parameters, or other types of information. Thus, in the example of FIG. 3, communication device 326 is shown as including transmitter 328 and receiver 330. Alternatively, transmitter 328 and receiver 330 can be separate devices within communication device 326. Similarly, if base station 304 is not a relay station, communication device 320 can include a network interface configured to communicate with one or more network entities 306 via a wire-based backhaul or wireless backhaul 370. Like communication device 326, communication device 320 is shown as including transmitter 322 and receiver 324. Figure 1 Figure 3

[0150] Apparatuses 302, 304, and 306 also include other components that can be used in conjunction with file transfer operations as disclosed herein. UE 302 includes a processing system 332 for providing functionality relating to, for example, UE operations described herein, and for providing other processing functionality. Base station 304 includes a processing system 334 for providing functionality relating to, for example, base station operations described herein, and for providing other processing functionality. Network entity 306 includes a processing system 336 for providing functionality relating to, for example, network functionality operations described herein, and for providing other processing functionality. Apparatuses 302, 304, and 306 include memory components 338, 340, and 342, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, etc.). Additionally, UE 302 includes a user interface 350 for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such as a keypad, a touchpad, a microphone, etc.). Although not shown, apparatuses 304 and 306 can also include user interfaces.

[0151] ​​Referring to the processing system 334 in more detail, in the downlink, IP packets from the network entity 306 can be provided to the processing system 334. The processing system 334 can implement functionality for the radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The processing system 334 can provide RRC layer functionality associated with system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error detection at the protocol interface, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC data PDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0152] The transmitter 316 and the receiver 318 can implement Layer-1 functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, can include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to a orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream can be spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator can be used to determine the coding and

[0153] At the UE 302, a receiver 312 receives a signal through its respective antenna(s). The receiver 312 recovers information modulated onto an RF carrier and provides the information to the processing system 332. The transmitter 310 and the receiver 312 implement layer- 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they can be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions can be based on channel estimates computed by the channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the processing system 332, which implements layer 3 and layer 2 functionality.

[0154] In the UL, the processing system 332 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.

[0155] Similar to the functionality described in connection with the DL transmission by the base station 304, the processing system 332 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0156] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 can be used by the transmitter 310 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 310 can be provided to different antenna(s). The transmitter 310 can utilize a plurality of transmitter antenna groups to conduct MIMO

[0157] At the base station 304, the UL transmission is processed in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 318 receives information from the respective antennas 320 and processes the information to recover the information modulated onto the RF carrier. The information is provided to the processing system 334.

[0158] In the UL, the processing system 334 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from UEs 302. IP packets from the processing system 334 can be provided to the core network. The processing system 334 is also responsible for error detection.

[0159] In an aspect, the apparatuses 302, 304, and 306 can include positioning components 344, 348, and 349, respectively. It will be appreciated that the functionality of the various positioning components 344, 348, and 349 can differ based on the device in which they are implemented. The positioning components 344, 348, and 349 can be hardware circuits that are part of, or coupled to, the processing systems 332, 334, and 336, respectively, which when executed, cause the apparatuses 302, 304, and 306 to perform the functionality described herein. Alternatively, the positioning components 344, 348, and 349 can be memory modules stored in the memory components 338, 340, and 342, respectively, which when executed by the processing systems 332, 334, and 336, cause the apparatuses 302, 304, and 306 to perform the functionality described herein.

[0160] For convenience, the apparatuses 302, 304, and / or 306 are shown Figure 3 as including various components that can be configured according to the various examples described herein. It will be appreciated, however, that the illustrated blocks can have different functionality in different designs.

[0161] The various components of the apparatuses 302, 304, and 306 can communicate with one another and with various other components, including the data buses 352, 354, and 356, respectively. Figure 3 The components of the apparatuses 302, 304, and 306 can be implemented in a variety of ways. In some implementations Figure 3The components of the various embodiments can be implemented in one or more circuits, such as, for instance, one or more processors and / or one or more ASICs (which can include one or more processors). Here, each circuit can use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide the functionality described above. For instance, some or all of the functionality represented by blocks 308, 332, 338, 344, and 350 can be implemented by the processor and memory component of UE 302 (e.g., through execution of appropriate code and / or through proper configuration of the processor component). Similarly, some or all of the functionality represented by blocks 314, 320, 334, 340, and 348 can be implemented by the processor and memory component of base station 304 (e.g., through execution of appropriate code and / or through proper configuration of the processor component). Also, some or all of the functionality represented by blocks 326, 336, 342, and 349 can be implemented by the processor and memory component of network entity 306 (e.g., through execution of appropriate code and / or through proper configuration of the processor component). For simplicity, various operations, acts, and / or functions are described herein as being performed by a UE, a base station, a positioning entity, and / or the like. However, as will be appreciated, such operations, acts, and / or functions can actually be performed by specific components or combinations of components of the UE, base station, positioning entity, and / or the like, such as the processing systems 332, 334, 336, the communication devices 308, 314, 326, the positioning components 344, 348, and 349, and / or the like.

[0162] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 An example of a downlink frame structure 400 is illustrated in accordance with aspects of the present disclosure. However, as those skilled in the art will readily appreciate, the frame structure for any particular application can vary as between different Figure 4 In the example 400, time is represented horizontally (e.g., on the X-axis), with time increasing from left to right, and frequency is represented vertically (e.g., on the Y-axis), with frequency increasing (or decreasing) from down to up. In the time domain, a frame 410 (10 ms) is divided into 10 equally sized subframes 420 (1 ms). Each subframe 420 includes two consecutive time slots 430 (0.5 ms).

[0163] A resource grid can be used to represent two time slots 430, each including one or more resource blocks (RBs) 440 (also referred to as “physical resource blocks” or “PRBs”) in the frequency domain. In LTE, and in some cases NR, a resource block 440 contains 12 consecutive subcarriers 450 in the frequency domain and, for a normal cyclic prefix (CP), 7 consecutive OFDM symbols 460 in the time domain (or 6 OFDM symbols 460 for an extended cyclic prefix). One such resource in the time domain (one OFDM symbol length) and one such resource in the frequency domain (one subcarrier) is known as a resource element (RE). Thus, in the example of FIG. 4, there are 84 resource elements in a resource block 440. Figure 4

[0164] LTE (and in some cases NR) uses OFDM on the downlink and uses single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, different from LTE, NR also has an option of using OFDM on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers 450, which are also commonly referred to as tones, bins, etc. Each subcarrier 450 can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing of the adjacent subcarriers 450 can be fixed, and the total number of subcarriers 450 (K) can be dependent on the system bandwidth. For example, the spacing of the subcarriers 450 can be 15 kHz and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Consequently, for a 1.25, 2.5, 5, 10, or 20 megahertz (MHz) system bandwidth, the nominal FFT size can be equal to 128, 256, 512, 1024 or 2048, respectively. The system bandwidth can also be partitioned into sub-bands. For example, a sub-band can cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 sub-bands for a 1.25, 2.5, 5, 10, or 20 MHz system bandwidth, respectively.

[0165] LTE supports a single numerology (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple numerologies, e.g., 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 204 kHz or larger subcarrier spacing can be available. Table 1, provided below, lists some various parameters for different NR numerologies.

[0166] Subcarrier Spacing (kHz) Symbols / slot Slots / subframe Slots / frame Slot (ms) Symbol duration (μs) Maximum nominal system BW with 4K FFT size (MHz) 15 14 1 10 1 66.7 50 30 14 2 20 0.5 33.3 100 60 14 4 40 0.25 16.7 100 120 14 8 80 0.125 8.33 400 204 14 16 160 0.0625 4.17 800

[0167] Table 1 ​

[0168] Continue to refer to Figure 4 Some resource elements designated R0 and R1 include downlink reference signals (DL-RS). DL-RS can include cell-specific RS (CRS) (sometimes also called common RS) and UE-specific RS (UE-RS). UE-RS is transmitted only on resource block 440 that maps the corresponding physical downlink shared channel (PDSCH). The number of bits carried by each resource element depends on the modulation scheme. Therefore, the more resource blocks 440 the UE receives and the higher the modulation scheme, the higher the UE's data rate.

[0169] On one hand, DL-RS can be a Positioning Reference Signal (PRS). The base station can then use it in conjunction with... Figure 4 The frame configurations shown are similar or identical to those used to transmit radio frames (e.g., radio frame 410) or other physical layer signaling sequences that support PRS signals, which can be measured and used for UE (e.g., any UE described herein) location estimation. Other types of wireless nodes in the wireless communication network (e.g., distributed antenna systems (DAS), remote radio heads (RRHs), UEs, APs, etc.) can also be configured to transmit to... Figure 4 The PRS signal is configured in a manner similar to (or identical to) the one described in the text.

[0170] The set of resource elements used to transmit a PRS is called a "PRS resource". The set of resource elements can span multiple PRBs in the frequency domain and 'N' (e.g., one or more) consecutive symbols 460 within a time slot 430 in the time domain. In a given OFDM symbol 460, the PRS resource occupies a consecutive PRB. A PRS resource is described by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size N, resource element offset in the frequency domain, start time slot and start symbol, number of symbols per PRS resource (i.e., duration of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying the PRS. For example, a comb size of comb 4 means that every fourth subcarrier of a given symbol carries the PRS.

[0171] A “PRS resource set” is a set of PRS resources for transmission of PRS signals, where each PRS resource has a PRS resource ID. Also, the PRS resources in a PRS resource set are associated with the same transmission reception point (TRP). A PRS resource ID in a PRS resource set is associated with a single beam 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” can also be referred to as a “beam.” Note that this does not have any implications as to whether the UE knows the TRP and the beam on which PRS is transmitted. A “PRS occasion” is one instance of a periodically repeating window of time (e.g., a set of one or more consecutive slots) in which PRS is expected to be transmitted. A PRS occasion can also be referred to as a “PRS positioning occasion,” “positioning occasion,” or simply “occasion.”

[0172] Note that the terms “positioning reference signal” and “PRS” can sometimes refer to specific reference signals used for positioning in LTE systems. However, as used herein, unless otherwise indicated, the terms “positioning reference signal” and “PRS” refer to any type of reference signal that can be used for positioning, such as but not limited to PRS signals in LTE or 5G, transmitter reference signals (TRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), primary synchronization signals (PSS), secondary synchronization signals (SSS), SSS, etc.

[0173] Figure 5 FIG. illustrates an exemplary DL PRS 500 processed by a wireless communication system, in accordance with aspects of the present disclosure. In Figure 5 the PRS transmission beams are transmitted by a cell (or transmission reception point (TRP)) on a series of beam-specific positioning occasions on respective slots / symbols during a positioning session (T PRS ) at the UE. These PRS transmission beams are received at the UE as PRS reception beams, which are then processed (e.g., various positioning measurements taken by the UE, etc.).

[0174] Figure 6 FIG. illustrates an exemplary wireless communication system 600, in accordance with aspects of the present disclosure. In Figure 6 the eNBs 1, 2, and 3 are synchronized with each other such that TOA (e.g., TDOA) measurements (denoted as T1, T2, and T3) can be used to generate a positioning estimate for the UE. Multiple TDOA measurements can be used for triangulation (e.g., 4 or more cells or eNBs). In a TDOA-based positioning scheme, network synchronization error is a major bottleneck in terms of positioning accuracy.

[0175] Another positioning technique that requires cell (or satellite) synchronization is based on Observed Time Difference of Arrival (OTDOA). One example OTDOA-based positioning scheme is GPS, which is limited to 50-100 ns (e.g., 15-30 meters) of accuracy.

[0176] In NR, there is no need for precise timing synchronization on the network. Instead, it is sufficient to have coarse time synchronization across gNBs (e.g., within the cyclic prefix (CP) duration of an OFDM symbol). RTT-based methods typically only require coarse timing synchronization, and as such are the preferred method in NR.

[0177] In a network-centric RTT estimation, a serving base station (e.g., base station 102) instructs a UE (e.g., UE 104) to scan / receive RTT measurement signals (e.g., PRS) on the serving cell and two or more neighboring base stations (e.g., at least three base stations are required). One of the multiple base stations transmits the RTT measurement signals on low-reuse resources (e.g., resources used by the base station to transmit system information) allocated by the network (e.g., location server 230, LMF 270). The UE records the time of arrival (also referred to as the time of reception, time of reception, or time of arrival (ToA)) of each RTT measurement signal relative to the UE’s current downlink timing (e.g., as derived by the UE from DL signals received from its serving base station) and transmits a common or individual RTT response message (e.g., SRS, UL-PRS) to one or more base stations (e.g., when instructed by its serving base station) and can include in the payload of each RTT response message the difference between the ToA of the RTT measurement signal and the transmission time of the RTT response message (e.g., Figure 9 in 912). The RTT response message will include a reference signal from which the base station can infer the ToA of the RTT response. By comparing the transmission time of the RTT measurement signal with the difference (e.g., Figure 9 in 912) reported by the UE, the base station can infer the propagation time between the base station and the UE, and then the base station can determine the distance between the UE and the base station from the propagation time by assuming the speed of light during the propagation time. Figure 9 (e.g., 922). The base station can infer the propagation time between the base station and the UE by comparing the transmission time of the RTT measurement signal with the difference

[0178] ​UE-centric RTT estimation is similar to the network-based approach, except that the UE transmits an uplink RTT measurement signal (e.g., when instructed by a serving base station), which is received by multiple base stations in the UE's neighborhood. Each involved base station responds with a downlink RTT response message, which can include the time difference between the ToA of the RTT measurement signal at the base station and the transmission time of the RTT response message from the base station in the RTT response message payload.

[0179] For both the network-centric and UE-centric procedures, the side (network or UE) that performs the RTT computation typically (though not always) transmits the first message or signal (e.g., the RTT measurement signal), while the other side responds with one or more RTT response messages or signals, which can include the difference between the ToA of the first message or signal and the transmission time of the RTT response message or signal.

[0180] Figure 7 An example wireless communication system 700 is illustrated in accordance with aspects of the present disclosure. In Figure 7 In an example, a UE 704 (which can correspond to any of the UEs described herein) attempts to compute an estimate of its position, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in computing an estimate of its position. The UE 704 can wirelessly communicate with multiple base stations 702-1, 702-2, and 702-3 (collectively, base stations 702, and which can correspond to any of the base stations described herein) using RF signals and standardized protocols for the modulation and exchange of information packets of the RF signals. By extracting different types of information from the exchanged RF signals, and utilizing the layout of the wireless communication system 700 (i.e., the locations, geometry, etc. of the base stations), the UE 704 can determine its position, or assist in determining its position, in a predefined reference coordinate system. In an aspect, the UE 704 can use a two-dimensional coordinate system to specify its position; however, aspects disclosed herein are not so limited, and can also be applied to determine a position using a three-dimensional coordinate system if additional dimensions are needed. Additionally, while the UE 704 is illustrated as a mobile device, aspects disclosed herein are not so limited, and can also be applied to other types of UEs, such as a fixed UE, a stationary UE, etc. Figure 7 One UE 704 and three base stations 702 are illustrated, but as will be appreciated, there can be more UEs 704 and more base stations 702.

[0181] To support location estimation, base station 702 can be configured to broadcast reference RF signals (e.g., PRS, NRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UE 704 within its coverage area, enabling UE 704 to measure the characteristics of such reference RF signals. For example, UE 704 can measure the ToA of a specific reference RF signal (e.g., PRS, NRS, CRS, CSI-RS, etc.) transmitted by at least three different base stations 702, and can use RTT positioning methods to report these ToA (and additional information) back to serving base station 702 or another positioning entity (e.g., location server 230, LMF 270).

[0182] On one hand, although described as UE 704 measuring a reference RF signal from base station 702, UE 704 may measure a reference RF signal from one of a plurality of cells supported by base station 702. In the case where UE 704 measures a reference RF signal transmitted by a cell supported by base station 702, at least two other reference RF signals measured by UE 704 to perform the RTT procedure will originate from cells supported by base station 702 that are different from the first base station 702 and may have good or poor signal strength at UE 704.

[0183] To determine the location (x, y) of UE 704, the entity determining the location of UE 704 needs to know the location of base station 702, which can be represented in the reference coordinate system as (x, y). k y k ), among which Figure 7 In the example, k = 1, 2, 3. When the location of UE 704 is determined by one of the base stations 702 (e.g., the serving base station) or UE 704, a location server (e.g., location server 230, LMF 270) that knows the network geometry can provide the location of the involved base station 702 to the serving base station 702 or UE 704. Alternatively, the location server can use known network geometry to determine the location of UE 704.

[0184] UE 704 or the corresponding base station 702 can determine the distance (d) between UE 704 and the corresponding base station 702. k Where k = 1, 2, 3). On one hand, the RTT 710 for determining the signals exchanged between UE 704 and any base station 702 can be performed and converted into distance (d). kAs discussed further below, RTT techniques can measure the time between sending a signaling message (e.g., a reference RF signal) and receiving a response. These methods can utilize calibration to eliminate any processing delays. In some environments, it can be assumed that the processing delays of the UE 704 and the base station 702 are the same. However, this assumption can not be true in practice.

[0185] Once each distance d k , the UE 704, the base station 702, or a location server (e.g., location server 230, LMF 270) can solve for the location (x, y) of the UE 704 by using various known geometric techniques (e.g., trilateration). From Figure 7 It can be seen that the location of the UE 704 ideally lies at the common intersection of three semicircles, each semicircle defined by a radius d k and a center (x k , y k ) where k = 1, 2, 3.

[0186] In some instances, additional information can be obtained in the form of an angle of arrival (AoA) or angle of departure (AoD) that defines a straight line direction (e.g., which can be in a horizontal plane or in three dimensions) or a range of possible directions (e.g., for the UE 704 from the location of the base station 702). The intersection of two directions at or near a point (x, y) can provide another estimate of the location of the UE 704.

[0187] A location estimate (e.g., for a UE 704) can be referred to by other names, such as location fix, position estimate, position fix, position solution, etc. A location estimate can be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or can be civic and include a street address, postal address, or some other verbal description of a location. A location estimate can be further defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate can include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default confidence level).

[0188] Figure 8 An example wireless communications system 800 is illustrated in accordance with aspects of the present disclosure. While Figure 7 depicts an example of a multi-cell RTT positioning scheme, Figure 8 depicts an example of a single-cell RTT positioning scheme. In Figure 8 RTT1 is measured along with AoD1 associated with the beam on which the DL PRS is transmitted from the cell to the UE. Figure 9The overlapping region of the depicted RTT1 and AoD1 provides a coarse position estimate for the associated UE.

[0189] Figure 9 is a diagram 900 illustrating exemplary timing of RTT measurement signals exchanged between a base station 902 (e.g., any of the base stations described herein) and a UE 904 (e.g., any of the UEs described herein), in accordance with aspects of the present disclosure. In the example of FIG. 9, the base station 902 transmits an RTT measurement signal 910 (e.g., a PRS, NRS, CRS, CSI-RS, etc.) to the UE 904 at time T1. The RTT measurement signal 910 has some propagation delay Tprop as it travels from the base station 902 to the UE 904. At time T2 (the ToA of the RTT measurement signal 910 at the UE 904), the UE 904 receives / measures the RTT measurement signal 910. After some UE processing time, the UE 904 transmits an RTT response signal 920 at time T3. After the propagation delay Tprop, the base station 902 receives / measures the RTT response signal 920 from the UE 904 at time T4 (the ToA of the RTT response signal 920 at the base station 902). Figure 9 prop prop

[0190] To identify the ToA (e.g., T2) of a reference signal (e.g., the RTT measurement signal 910) transmitted by a given network node (e.g., the base station 902), a receiver (e.g., the UE 904) first jointly processes all resource elements (REs) on the channel over which the transmitter is transmitting the reference signal, and performs an inverse Fourier transform to convert the received reference signal to the time domain. Converting the received reference signal to the time domain is referred to as an estimate of the channel energy response (CER). The CER shows the peaks on the channel over time, and the earliest “significant” peak should thus correspond to the ToA of the reference signal. Typically, the receiver will use a quality threshold related to the noise to filter out spurious local peaks, thus correctly identifying the significant peak on the channel with some probability. For example, the receiver can select the ToA estimate that is the earliest local maximum of the CER that is at least X dB higher than the median of the CER and at most Y dB lower than the main peak on the channel. The receiver determines the CER for each reference signal from each transmitter in order to determine the ToA for each reference signal from different transmitters.

[0191] In some designs, the RTT response signal 920 can explicitly include the difference between time T3 and time T2 (i.e., T3-T2). Using this measurement and the difference between time T4 and time T1 (i.e., T4-T1), the UE 904 can determine the distance between the UE 904 and the base station 902. 912). Using this measurement and the difference between time T4 and time T1 (i.e., T4-T1), the UE 904 can determine the distance between the UE 904 and the base station 902. ​​​922), the base station 902 (or other positioning entity such as the location server 230, LMF 270, etc.) can compute the distance to the UE 904 as follows:

[0192]

[0193] where c is the speed of light.

[0194] Figure 10 is a diagram 1000 illustrating exemplary timing of RTT measurement signals exchanged between a base station (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) according to other aspects of the present disclosure. In particular, Figure 10 1002-1004 of 1000 represent portions of the frame delay associated with the Rx-Tx difference measured at the gNB and the UE, respectively.

[0195] An additional source of delay or error is due to the UE and gNB hardware group delays used for position location. Figure 11 is a diagram 1100 illustrating exemplary timing of RTT measurement signals exchanged between a base station (gNB) (e.g., any of the base stations described herein) and a UE (e.g., any of the UEs described herein) according to aspects of the present disclosure. Figure 11 In certain aspects similar to Figure 9 However, in Figure 11 , the UE and gNB hardware group delays (which are primarily due to the internal hardware delays between the baseband (BB) components and antennas at the UE and gNB) are shown with respect to 1102-1108 (denoted as AR x and AT x ). As will be appreciated, both the Tx-side and Rx-side path-specific or beam-specific delays affect the RTT measurement.

[0196] Figure 12 is an exemplary wireless communication system 1200 according to aspects of the present disclosure. The wireless communication system 1200 is similar to the wireless communication system 600 of Figure 6 However, the wireless communication system 1200 also depicts beams associated with respective TOA (e.g., TDOA) measurements (denoted as T1, T2, and T3). As will be appreciated, the Rx-side specific path or specific beam delays affect the DL TDOA measurements. Although not explicitly shown, the Tx-side path-specific or beam-specific delays affect the UL TDOA measurements in a similar manner.

[0197] The accuracy of the positioning estimate at the UE at the UE side is limited by how fine the group delay / timing error can be maintained. For example, a 1 ns error for ARx and ATx can result in a limit of about 2 feet in accuracy. Some 3GPP standards target positioning accuracy of less than 3 m (for Rel-16) and less than 1 m (for Rel-17 for general commercial products). Knowledge of the UE and / or gNB hardware group delay can thus help improve the positioning accuracy.

[0198] As an example, in RTT-based positioning, the RTT can be estimated between a UE and two gNBs. The positioning estimate for the UE can then be narrowed down to the intersection of the geographic ranges mapped to the two RTTs (e.g., to a hyperbola). RTTs to additional gNBs (or to specific TRPs of such gNBs) can further narrow down (or refine) the positioning estimate for the UE. Differential RTT is a positioning scheme whereby the difference between two RTT measurements (or measurement ranges) is used to generate the positioning estimate for the UE.

[0199] In some designs, the positioning engine (e.g., at the UE, base station, or server / LMF) can choose between whether the RTT measurements will be used to compute a positioning estimate using typical RTT or differential RTT. For example, if the positioning engine receives RTTs that are known to have considered the hardware group delay, then a typical RTT positioning is performed (e.g., as shown in Figure 6 、 Figure 7 ). Otherwise, in some designs, differential RTT is performed so that some hardware group delay can be eliminated. In some designs where the positioning engine is implemented at the network side (e.g., gNB / LMU / eSMLC / LMF), the group hardware delay at the UE is unknown (and vice versa).

[0200] An example of the theoretical Rx-Tx delay measurement between a UE and base stations 1 and 2, respectively, is as follows:

[0201]

[0202] Equation 1

[0203]

[0204] Equation 2

[0205] where W represents the hardware group delay.

[0206] As will be appreciated, if the hardware group delay w is the same for both and , then when in and When taking the difference between

[0207]

[0208] Equation 3

[0209]

[0210] Equation 4

[0211] where and reflect times ti and t2, respectively.

[0212] In this case, when taking the difference between and there is a residual error due to the difference between and This residual error is due to a phenomenon referred to herein as time drift. As an example, time drift in hardware group delay can occur due to various environmental factors such as humidity, temperature, etc.

[0213] Another issue with differential RTT can occur in the case where UE-side hardware group delay (e.g., 912 in Figure 9 1104-1108 in Figure 11 is effectively cancelled out along with the reference gNB hardware group delay but residual gNB hardware group delay still exists. For example, the residual gNB hardware group delay of gNB i can be represented as GD ,diff,gNB,i , e.g.:

[0214] GD ,diff,gNB,i = GD gNB,i - GD gNB_ref Equation 5

[0215] where GD gNB,i is the hardware group delay of gNB i (e.g., 1102 or 1106 of Figure 11 and GD gNB_ref is the hardware group delay of the reference gNB. GD gNB_ref is common across all RTTs associated with the differential RTT positioning procedure.

[0216] While described above with respect to reference gNBs, in other designs, any wireless communication device associated with a known location (e.g., a reference UE with a recent position fix, etc.) can be used as a reference device in various positioning schemes (e.g., RTT, differential RTT, double differential RTT, TDOA, etc.). In some systems, the reference device (e.g., gNB or reference UE) is selected based on a signal quality criterion such as RSRP. However, a reference device (e.g., gNB or reference UE) with good signal quality is not necessarily the best choice in terms of hardware group delay calibration. Aspects of the present disclosure thus relate to reference device (e.g., gNB or reference UE) selection based at least in part on hardware group delay calibration capability associated with the reference device (e.g., gNB and / or reference UE) associated with a positioning procedure (e.g., RTT, differential RTT, double differential RTT, TDOA, etc.) of a UE. These aspects can provide various technical advantages, including improved positioning estimation accuracy of a UE.

[0217] Figure 13 FIGURE 13 illustrates an exemplary process 1300 of wireless communication, in accordance with aspects of the present disclosure. Process 1300 can be performed by a communication node. In some designs, the communication node performing process 1300 is a UE (e.g., any of the UEs described herein, such as UE 302). In other designs, the communication node performing process 1300 is a BS (e.g., any of the BSs or gNBs described herein, such as BS 304, which can include an integrated LMF). In other designs, the communication node performing process 1300 is a network entity, such as network entity 306 (e.g., a LMF). Moreover, while process 1300 is described in some aspects with respect to RTT (e.g., differential RTT), in some designs, process 1300 can be applicable to other types of RTT (e.g., double differential RTT, where a first differential RTT is measured between a target UE and two reference nodes, and a second differential RTT is measured between a reference device and two reference nodes) or non-RTT positioning techniques, such as DL or UL TDOA. Figure 13 Process 1300 can also be applicable to other types of RTT (e.g., double differential RTT, where a first differential RTT is measured between a target UE and two reference nodes, and a second differential RTT is measured between a reference device and two reference nodes) or non-RTT positioning techniques, such as DL or UL TDOA.

[0218] At 1310, the communication node (e.g., receiver 312, receiver 318, receiver 324, receiver 330, processing system 334, memory component 340, etc.) obtains a hardware group delay calibration capability associated with each of a plurality of reference devices (e.g., gNBs and / or reference UEs), where the plurality of reference devices are associated with a positioning procedure for a UE. In one example, the communication node can correspond to the UE, and the positioning procedure (e.g., traditional RTT, differential RTT, double differential RTT, TDOA, etc.) is a UE-based positioning procedure. In another example, the communication node can correspond to a network device (e.g., gNB, LMF, etc.), and the positioning procedure (e.g., traditional RTT, differential RTT, double differential RTT, TDOA, etc.) is a network-based positioning procedure.

[0219] At 1320, the communication node (e.g., processing system 332, processing system 334, processing system 336, etc.) selects a reference device (e.g., gNB or reference UE) from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices. For example, assume each reference device (e.g., gNB or reference UE) reports its hardware group delay calibration capability as a respective hardware group delay error range of ns. In some designs, the communication node at 1320 can select the reference device (e.g., gNB or reference UE) for the positioning procedure (e.g., traditional RTT, differential RTT, double differential RTT, TDOA, etc.) as the reference device associated with the narrowest hardware group delay error range (e.g., or the minimum value of T1) as the selected reference device (e.g., gNB or reference UE). In some designs, the selection at 1320 can select the reference device based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion. For example, the at least one secondary criterion can include RSRP measurements between the plurality of reference devices and the UE (e.g., higher RSRP measurements can more favorably weight the respective reference device in the reference device selection).

[0220] At 1330, the communication node (e.g., processing system 332, processing system 334, processing system 336, component 344 / 348 / 349, etc.) determines (e.g., calibrates) one or more timing (e.g., positioning) measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value (GDgNB_ref) associated with the selected reference device (e.g., as in Equation 5 above).

[0221] Reference is made to Figure 13 ​In some designs, the communication node can send a hardware group delay calibration capability request to each of the plurality of reference devices, where the obtaining includes receiving a hardware group delay calibration capability of each of the plurality of reference devices in response to the request. In one example, for UE-based positioning, the UE can send a request to the reference devices (e.g., BSs and / or reference UEs), which then report their hardware group delay calibration capabilities to the LMF, which in turn propagates the information back to the UE. In other designs, for network-based positioning, the LMF can send a request to the reference devices (e.g., BSs and / or reference UEs), which then report their hardware group delay calibration capabilities to the LMF.

[0222] Referring to Figure 13 In some designs, the hardware group delay calibration capability of at least one of the plurality of reference devices (e.g., BSs and / or reference UEs) is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP). For example, in some designs, each reference device (e.g., gNB or UE) can report its respective hardware group delay calibration capability (or calibration error) with an indication of the associated timestamp, frequency band, positioning frequency layer, UE ID, and / or TRP ID. In some designs, the hardware group delay calibration capability (or calibration error) can be different for different frequency bands. In some designs, certain parameters can be grouped or commoned with respect to a positioning frequency layer (e.g., center frequency), in which case the hardware group delay calibration capability (or calibration error) can be specific to the positioning frequency layer. In some designs, different beams can be associated with different hardware group delay calibration capabilities (or calibration errors), e.g., a UE / TRP can have multiple antenna panels, in which case the hardware group delay calibration capability (or calibration error) can be specific to a particular UE ID or TRP.

[0223] Referring to Figure 13 In some designs, the hardware group delay calibration capability of at least one of the plurality of reference devices (e.g., BSs and / or reference UEs) is time-varying. In this case, at block 1310, the communication node can obtain at least one parameter (e.g., timestamp, etc.) that models a time-varying function of the hardware group delay calibration capability of the at least one reference device (e.g., BS or reference UE).

[0224] Referring to Figure 13 In some designs, at block 1310, the communication node can receive differential hardware group delay calibration capability information related to previously received hardware group delay calibration capability information. For example, if the hardware group delay calibration capability of a particular reference device (e.g., BS and / or reference UE) does not change frequently, then a differential report can be used to reduce the reporting overhead.

[0225] As described above with reference to Equation 5, in a gNB-specific example, a residual gNB hardware group delay (GD ,diff,gNB,i ) is a factor that can reduce the accuracy of UE positioning. Aspects of the present disclosure thus relate to estimation of a residual reference device (e.g., gNB or reference UE) hardware group delay (e.g., GD ,diff,gNB,i in a gNB-specific example) so that the residual reference device hardware group delay (e.g., GD ,diff,gNB,i in a gNB-specific example) can be canceled out during a position estimation procedure for a UE. These aspects can provide various technical advantages, including improved positioning estimation accuracy for a UE.

[0226] Figure 14 FIG. 13 illustrates an example process 1300 of wireless communication, in accordance with aspects of the present disclosure. Process 1300 can be performed by a communication node. In some designs, the communication node performing process 1300 is a BS (e.g., any of the BSs or gNBs described herein, such as BS 304, which can include an integrated LMF). In other designs, the communication node performing process 1300 is a network entity, such as network entity 306 (e.g., an LMF). Moreover, while process 1300 is described in some aspects with respect to RTT (e.g., differential RTT), in some designs, Figure 14 Process 1300 can also be applicable to other types of RTT (e.g., double differential RTT, where a first differential RTT is measured between a target UE and two reference nodes, and a second differential RTT is measured between a reference device and two reference nodes) or non-RTT positioning techniques, such as DL or UL TDOA.

[0227] At 1410, the communication node (e.g., receiver 318, receiver 324, positioning component 348 or 349, receiver 330, etc.) obtains an estimated distance between a first reference device (e.g., gNB or reference UE) and a second reference device (e.g., gNB or reference UE), the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device. In some designs, the one or more timing measurements can be associated with an RTT measurement (e.g., traditional RTT, differential RTT, double differential RTT, etc.), similar to Figure 9 or Figure 11, except that the reference signals used for positioning are exchanged between two reference devices (e.g., BSs or gNBs or reference UEs) instead of between a UE and a BS. In other designs, one or more timing measurements can be associated with UL or DL TDOA measurements. In some designs, the one or more reference signals can be configured similarly to PRS, although this is optional. In some designs, the one or more reference signals used for positioning can correspond to an OTA signal having a direct LOS between the first reference device and the second reference device (e.g., gNB and / or reference UE).

[0228] At 1420, the communication node (e.g., the processing system 334 or 336, the positioning component 348 or 349, etc.) estimates a hardware group delay associated with the first reference device and the second reference device based on (i) an estimated distance between the first reference device and the second reference device and (ii) a known distance between the first reference device and the second reference device. In one example, the known distance between the first reference device and the second reference device can be preconfigured or predetermined based on known locations of the first reference device and the second reference device (e.g., obtained from a base station almanac or a recent positioning fix of a reference UE, etc.).

[0229] Referring to Figure 14 In some designs, the communication node corresponds to one of the first reference device and the second reference device (e.g., a base station or a reference UE). In other designs, where the communication node corresponds to a network entity (e.g., an LMF) separate from the first reference device and the second reference device.

[0230] Referring to Figure 14 In a gNB-specific example, the first reference device can correspond to a reference base station (gNB_ref), and the estimated hardware group delay at 1420 can correspond to a residual gNB hardware group delay (GD ,diff,gNB,i ), e.g.,:

[0231] GD ,diff,gNB,i = RTTi - Distance_i * 2

[0232] Equation 6

[0233] where RTTi is an estimated distance between the first base station and the second base station (e.g., gNB_ref and gNB_i), GD ,diff,gNB,i is a total group delay error between gNB_ref and gNB_i, and Distance_i is a known distance between the first base station and the second base station (e.g., obtained based on a base station almanac).

[0234] In an example, RTT measurements between a first reference device (reference gNB) and a second reference device (gNB_i) can be implemented as follows:

[0235] • the reference gNB transmits a first reference signal for positioning (RS-P_1) to gNB_i at T_1,

[0236] • after receiving RS-P from the reference gNB at T_2, gNB_i transmits a second reference signal for positioning (RS-P_2) at T_3,

[0237] • gNB_i reports the Rx-Tx time difference T_3-T_2 to the network (e.g., LMF, reference gNB, etc.),

[0238] • after receiving RS-P_2 from gNB_i at T_4, the reference gNB reports its Rx-Tx time difference T_4-T_1 to the network (e.g., LMF),

[0239] • the network (e.g., LMF) derives the RTT (RTTi) as T_4-T_1-T_3 + T_2.

[0240] As noted above, the reference device can alternatively correspond to a reference UE rather than a gNB. Moreover, although the above provides an RTT-specific example, in other designs, the positioning procedure can be non-RTT, such as TDOA.

[0241] In some designs, Figure 14 The process 1400 of FIG. 14 can be implemented between a specified reference device (e.g., a gNB or reference UE) and multiple other reference devices (e.g., each other reference device gNB or reference UE associated with a positioning procedure, such as a differential RTT positioning procedure for a particular UE). In other designs, the process 1400 of FIG. 14 can be performed only for reference devices that have a direct LOS connection to the specified reference device. Figure 14 In other designs, the process 1400 of FIG. 14 can be performed on a periodic basis, rather than being event-triggered based on a positioning procedure. Figure 14

[0242] ​In the detailed description above, it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly recited in each clause. Rather, the various aspects of the disclosure can include fewer than all features of a single example clause disclosed. Therefore, the following clauses should be considered as being incorporated in this document as if each individual clause was a separate example. Although each dependent clause can refer to a particular combination of features in the clause to which this dependent clause refers, the aspect of the dependent clause is not limited to the specific combination. It is to be understood that the other example clauses can also include a combination of the dependent clause aspects with the subject matter of any other dependent clause or independent clause, or a combination of any features with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any of the other independent clauses even if the clause does not directly depend on the independent clause.

[0243] Implementations are described in the following numbered clauses:

[0244] Clause 1. A method of operating a communication node, the method comprising: obtaining a hardware group delay calibration capability associated with each of a plurality of reference devices; selecting a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and determining one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0245] Clause 2. The method of clause 1, wherein the plurality of reference devices comprises at least one base station, at least one reference UE, or a combination thereof.

[0246] Clause 3. The method of any of clauses 1-2, further comprising: transmitting a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining comprises receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0247] Clause 4. The method of any of clauses 1-3, wherein the determining is performed in association with a positioning procedure for a user equipment (UE).

[0248] Clause 5. The method of clause 4, wherein the communication node corresponds to the UE, and wherein the positioning procedure is a UE-based positioning procedure.

[0249] Clause 6. The method of any of clauses 4-5, wherein the communication node corresponds to a network device, and wherein the positioning procedure is a network-based positioning procedure.

[0250] Clause 7. The method of any of clauses 4-6, wherein the positioning procedure corresponds to a round-trip time (RTT) positioning procedure.

[0251] Clause 8. The method of clause 7, wherein the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0252] Clause 9. The method of any of clauses 4-8, wherein the positioning procedure corresponds to a time-difference-of-arrival (TDOA) based positioning procedure.

[0253] Clause 10. The method of any of clauses 1-9, wherein the determining is performed independent of any UE positioning procedure.

[0254] Clause 11. The method of any of clauses 1-10, wherein the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0255] Clause 12. The method of clause 11, wherein the selecting selects the selected reference device as a reference device associated with a narrowest hardware group delay error range.

[0256] Clause 13. The method of any of clauses 1-12, wherein the selecting selects the selected reference device based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion.

[0257] Clause 14. The method of any of clauses 11-13, wherein the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0258] Clause 15. The method of any of clauses 1-14, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0259] Clause 16. The method of any of clauses 1-15, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and the obtaining obtains at least one parameter modeling a time-varying function of the hardware group delay calibration capability for the at least one reference device.

[0260] Clause 17. The method of any of clauses 1-16, wherein the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0261] Clause 18. A method of operating a communication node, the method comprising: obtaining an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimating a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0262] Clause 19. The method of clause 18, wherein the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0263] Clause 20. The method of any of clauses 18-19, wherein the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0264] Clause 21. The method of any of clauses 18-20, wherein the one or more timing measurements are associated with round trip time (RTT) measurements or time difference of arrival (TDOA) measurements.

[0265] Clause 22. The method of any of clauses 18-21, wherein the first reference device is associated with a reference hardware group delay.

[0266] Clause 23. The method of clause 22, wherein the estimating estimates a residual hardware group delay corresponding to a difference between a hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

[0267] Clause 24. A communication node, the communication node comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: obtain a hardware group delay calibration capability associated with each of a plurality of reference devices; select a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and determine one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0268] Clause 25. The communication node of clause 24, wherein the plurality of reference devices comprises at least one base station, at least one reference UE, or a combination thereof.

[0269] Clause 26. The communication node of any of clauses 24 to 25, wherein the at least one processor is further configured to: transmit, via the at least one transceiver, a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining comprises receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0270] Clause 27. The communication node of any of clauses 24 to 26, wherein the determining is performed in association with a positioning procedure for a user equipment (UE).

[0271] Clause 28. The communication node of clause 27, wherein the communication node corresponds to the UE, and wherein the positioning procedure is a UE-based positioning procedure.

[0272] Clause 29. The communication node of any of clauses 27 to 28, wherein the communication node corresponds to a network device, and wherein the positioning procedure is a network-based positioning procedure.

[0273] Clause 30. The communication node of any of clauses 27 to 29, wherein the positioning procedure corresponds to a round-trip-time (RTT) positioning procedure.

[0274] Clause 31. The communication node of clause 30, wherein the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0275] Clause 32. The communication node of any of clauses 27 to 31, wherein the positioning procedure corresponds to a time-difference-of-arrival (TDOA) based positioning procedure.

[0276] Clause 33. The communication node of any of clauses 24 to 32, wherein the determining is performed independent of any UE positioning procedure.

[0277] Clause 34. The communication node of any of clauses 24 to 33, wherein the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0278] Clause 35. The communication node of clause 34, wherein the selecting selects the selected reference device as the reference device associated with the narrowest hardware group delay error range.

[0279] Clause 36. The communication node of any of clauses 24 to 35, wherein the selection is based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion to select the selected reference device.

[0280] Clause 37. The communication node of any of clauses 34 to 36, wherein the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0281] Clause 38. The communication node of any of clauses 24 to 37, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0282] Clause 39. The communication node of any of clauses 24 to 38, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is time- varying, and wherein the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0283] Clause 40. The communication node of any of clauses 24 to 39, wherein the obtaining comprises receiving differential hardware group delay calibration capability information that relates to previously received hardware group delay calibration capability information.

[0284] Clause 41. A communication node, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: obtain an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimate a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0285] Clause 42. The communication node of clause 41, wherein the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0286] Clause 43. The communication node of any of clauses 41 to 42, wherein the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0287] Clause 44. The communication node of any of clauses 41-43, wherein the one or more timing measurements are associated with a round-trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0288] Clause 45. The communication node of any of clauses 41-44, wherein the first reference device is associated with a reference hardware group delay.

[0289] Clause 46. The communication node of clause 45, wherein the estimate estimates a residual hardware group delay corresponding to a difference between a hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

[0290] Clause 47. A communication node, comprising: means for obtaining a hardware group delay calibration capability associated with each of a plurality of reference devices; means for selecting a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and means for determining one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0291] Clause 48. The communication node of clause 47, wherein the plurality of reference devices comprises at least one base station, at least one reference UE, or a combination thereof.

[0292] Clause 49. The communication node of any of clauses 47-48, further comprising: means for sending a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining comprises receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0293] Clause 50. The communication node of any of clauses 47-49, wherein the determining is performed in association with a positioning procedure for a user equipment (UE).

[0294] Clause 51. The communication node of clause 50, wherein the communication node corresponds to the UE, and wherein the positioning procedure is a UE-based positioning procedure.

[0295] Clause 52. The communication node of any of clauses 50-51, wherein the communication node corresponds to a network device, and wherein the positioning procedure is a network-based positioning procedure.

[0296] Clause 53. The communication node of any of clauses 50-52, wherein the positioning procedure corresponds to a round-trip time (RTT) positioning procedure.

[0297] Clause 54. The communication node of clause 53, wherein the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0298] Clause 55. The communication node of any of clauses 50 to 54, wherein the positioning procedure corresponds to a time difference of arrival (TDOA) based positioning procedure.

[0299] Clause 56. The communication node of any of clauses 47 to 55, wherein the determining is performed independent of any UE positioning procedure.

[0300] Clause 57. The communication node of any of clauses 47 to 56, wherein the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0301] Clause 58. The communication node of clause 57, wherein the selecting selects the selected reference device as the reference device associated with the narrowest hardware group delay error range.

[0302] Clause 59. The communication node of any of clauses 47 to 58, wherein the selecting selects the selected reference device based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion.

[0303] Clause 60. The communication node of any of clauses 57 to 59, wherein the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0304] Clause 61. The communication node of any of clauses 47 to 60, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0305] Clause 62. The communication node of any of clauses 47 to 61, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is time- varying, and wherein the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability for the at least one reference device.

[0306] Clause 63. The communication node of any of clauses 47 to 62, wherein the obtaining comprises receiving differential hardware group delay calibration capability information, the differential hardware group delay calibration capability information pertaining to previously received hardware group delay calibration capability information.

[0307] Clause 64. A communication node, comprising: means for obtaining an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and means for estimating a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device and (ii) a known distance between the first reference device and the second reference device.

[0308] Clause 65. The communication node of clause 64, wherein the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0309] Clause 66. The communication node of any of clauses 64 to 65, wherein the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0310] Clause 67. The communication node of any of clauses 64 to 66, wherein the one or more timing measurements are associated with a round trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0311] Clause 68. The communication node of any of clauses 64 to 67, wherein the first reference device is associated with a reference hardware group delay.

[0312] Clause 69. The communication node of clause 68, wherein the estimate estimates a residual hardware group delay corresponding to a difference between the hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

[0313] Clause 70. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication node, cause the communication node to: obtain a hardware group delay calibration capability associated with each of a plurality of reference devices; select a reference device from among the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and determine one or more timing measurements associated with each of the plurality of reference devices based on a reference hardware group delay calibration value associated with the selected reference device.

[0314] Clause 71. The non-transitory computer-readable medium of clause 70, wherein the plurality of reference devices comprise at least one base station, at least one reference UE, or a combination thereof.

[0315] Clause 72. The non-transitory computer-readable medium of any of clauses 70-71, wherein the one or more instructions further cause the communication node to: transmit a hardware group delay calibration capability request to each of the plurality of reference devices, wherein the obtaining comprises receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request.

[0316] Clause 73. The non-transitory computer-readable medium of any of clauses 70-72, wherein the determining is performed in association with a positioning procedure for a user equipment (UE).

[0317] Clause 74. The non-transitory computer-readable medium of clause 73, wherein the communication node corresponds to the UE, and wherein the positioning procedure is a UE-based positioning procedure.

[0318] Clause 75. The non-transitory computer-readable medium of any of clauses 73-74, wherein the communication node corresponds to a network device, and wherein the positioning procedure is a network-based positioning procedure.

[0319] Clause 76. The non-transitory computer-readable medium of any of clauses 73-75, wherein the positioning procedure corresponds to a round-trip time (RTT) positioning procedure.

[0320] Clause 77. The non-transitory computer-readable medium of clause 76, wherein the positioning procedure corresponds to a differential RTT positioning procedure or a double differential RTT positioning procedure.

[0321] Clause 78. The non-transitory computer-readable medium of any of clauses 73-77, wherein the positioning procedure corresponds to a time difference of arrival (TDOA) based positioning procedure.

[0322] Clause 79. The non-transitory computer-readable medium of any of clauses 70-78, wherein the determining is performed independent of any UE positioning procedure.

[0323] Clause 80. The non-transitory computer-readable medium of any of clauses 70-79, wherein the hardware group delay calibration capability of each of the plurality of reference devices indicates a respective hardware group delay error range.

[0324] Clause 81. The non-transitory computer-readable medium of clause 80, wherein the selecting selects the selected reference device as the reference device associated with the narrowest hardware group delay error range.

[0325] Clause 82. The non-transitory computer-readable medium of any of clauses 70 to 81, wherein the selection is based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion to select the selected reference device.

[0326] Clause 83. The non-transitory computer-readable medium of any of clauses 80 to 82, wherein the at least one secondary criterion comprises a reference signal received power (RSRP) measurement between the plurality of reference devices and a user equipment (UE).

[0327] Clause 84. The non-transitory computer-readable medium of any of clauses 70 to 83, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is specific to a particular set of frequency domain resources, a particular set of beams, a particular transmission reception point (TRP).

[0328] Clause 85. The non-transitory computer-readable medium of any of clauses 70 to 84, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and wherein the obtaining obtains at least one parameter that models a time-varying function of the hardware group delay calibration capability of the at least one reference device.

[0329] Clause 86. The non-transitory computer-readable medium of any of clauses 70 to 85, wherein the obtaining comprises receiving differential hardware group delay calibration capability information that relates to previously received hardware group delay calibration capability information.

[0330] Clause 87. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a communication node, cause the communication node to: obtain an estimated distance between a first reference device and a second reference device, the estimated distance based on one or more timing measurements of one or more reference signals used to position between the first reference device and the second reference device; and estimate a hardware group delay associated with the first reference device and the second reference device based on (i) the estimated distance between the first reference device and the second reference device, and (ii) a known distance between the first reference device and the second reference device.

[0331] Clause 88. The non-transitory computer-readable medium of clause 87, wherein the first reference device and the second reference device comprise at least one base station, at least one reference user equipment (UE), or a combination thereof.

[0332] Clause 89. The non-transitory computer-readable medium of any of clauses 87-88, wherein the communication node corresponds to one of the first reference device and the second reference device, or the communication node corresponds to a network entity separate from the first reference device and the second reference device.

[0333] Clause 90. The non-transitory computer-readable medium of any of clauses 87-89, wherein the one or more timing measurements are associated with a round-trip time (RTT) measurement or a time difference of arrival (TDOA) measurement.

[0334] Clause 91. The non-transitory computer-readable medium of any of clauses 87-90, wherein the first reference device and reference hardware group delay are associated.

[0335] Clause 92. The non-transitory computer-readable medium of clause 91, wherein the estimate estimates a residual hardware group delay corresponding to a difference between the hardware group delay of the second reference device and the reference hardware group delay of the first reference device.

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

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

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

[0339] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in Random Access Memory (RAM), flash memory, Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal (e.g., an UE). In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

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

[0341] While the foregoing disclosure demonstrates illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and / or actions of the methods according to the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure can be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. A method for operating a communication node, comprising: Send a hardware group delay calibration capability request to each of the multiple reference devices; Obtaining a hardware group delay calibration capability associated with each of the plurality of reference devices, wherein obtaining includes: receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request, the hardware group delay calibration capability indicating a corresponding hardware group delay error range; A reference device is selected from the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and One or more timing measurements associated with each of the plurality of reference devices are determined based on the reference hardware group delay calibration values ​​associated with the selected reference device.

2. The method of claim 1, wherein the plurality of reference devices includes at least one base station, at least one reference user equipment (UE), or a combination thereof.

3. The method of claim 1, wherein the determination is performed in association with the positioning process for the UE.

4. The method according to claim 3, The communication node corresponds to the UE, and The positioning process mentioned above is based on the UE's positioning process.

5. The method according to claim 3, The communication node refers to a network device, and The positioning process described above is a network-based positioning process.

6. The method of claim 3, wherein the positioning process corresponds to a round-trip time (RTT) positioning process.

7. The method according to claim 6, The positioning process described therein corresponds to a differential RTT positioning process or a dual differential RTT positioning process.

8. The method of claim 3, wherein the positioning process corresponds to a positioning process based on Time Difference of Arrival (TDOA).

9. The method of claim 1, wherein the determination is performed independently of any UE positioning process.

10. The method of claim 1, wherein the selection selects the reference device as a reference device associated with the narrowest hardware set delay error range.

11. The method of claim 1, wherein the selection of the selected reference device is based on the hardware group delay calibration capability associated with the plurality of reference devices and at least one secondary criterion.

12. The method of claim 11, wherein the at least one secondary criterion includes a reference signal received power (RSRP) measurement between the plurality of reference devices and the UE.

13. The method of claim 1, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is dedicated to a specific set of frequency domain resources, a specific set of beams, and a specific transmit-receive point (TRP).

14. The method according to claim 1, The hardware group delay calibration capability of at least one of the plurality of reference devices is time-varying, and The acquisition refers to acquiring at least one parameter for modeling the time-varying function of the hardware group delay calibration capability of the at least one reference device.

15. The method of claim 1, wherein obtaining comprises: Receive differential hardware group delay calibration capability information, which is related to previously received hardware group delay calibration capability information.

16. A communication node, 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: Send a hardware group delay calibration capability request to each of the multiple reference devices; Obtaining a hardware group delay calibration capability associated with each of the plurality of reference devices, wherein obtaining includes: receiving the hardware group delay calibration capability of each of the plurality of reference devices in response to the request, the hardware group delay calibration capability indicating a corresponding hardware group delay error range; A reference device is selected from the plurality of reference devices based at least on the hardware group delay calibration capability associated with the plurality of reference devices; and One or more timing measurements associated with each of the plurality of reference devices are determined based on the reference hardware group delay calibration values ​​associated with the selected reference device.

17. The communication node of claim 16, wherein the plurality of reference devices includes at least one base station, at least one reference user equipment (UE), or a combination thereof.

18. The communication node of claim 16, wherein the determination is performed in association with the positioning process for the UE.

19. The communication node of claim 16, wherein the hardware group delay calibration capability of at least one of the plurality of reference devices is dedicated to a specific set of frequency domain resources, a specific set of beams, and a specific transmit-receive point (TRP).

20. A communication node comprising components for performing the method of any one of claims 1 to 15.

21. A computer-readable medium having stored thereon computer-executable instructions, wherein the computer-executable instructions are executable by one or more processors to cause the processors to perform the method of any one of claims 1 to 15.

Images