Measurement of sounding reference signal via uplink relay

Abstract

Techniques for wireless positioning estimation of a user equipment (UE) involving one or more uplink (UL) relays are disclosed. The UL relay receives UL data communications from the UE and relays the UL data communications to a serving network component (e.g., gNB) via a backhaul connection (wired or wireless). In an aspect, an uplink relay is selected by a network component for a location estimation session of a target UE (1030). The uplink relay measures a UL SRS for positioning from the target UE (1040) and reports UL SRS measurement information to the network component and / or the serving network component (1050).

Description

Background Art 1. Technical Field

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

[0002] 2. Description of related technologies

[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS processes and technologies, and high-density deployment of 5G, enable high-precision positioning based on 5G. Summary of the invention

[0005] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Therefore, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects related to the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0006] In one aspect, a method of operating a network component includes: determining a coarse positioning estimate associated with a target user equipment (UE); determining location information associated with an uplink relay set; and selecting a wireless node group for a positioning estimation session of the target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group including at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more service network components, the one or more service network components being configured to send downlink wireless data communications to the one or more UEs; sending at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE in association with the positioning estimation session to the at least one uplink relay; receiving at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and determining a positioning estimate of the target UE based on the at least one report.

[0007] In one aspect, a method of operating an uplink relay includes: receiving one or more uplink wireless data communications from one or more user equipment (UE); relaying the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receiving a request from the network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; measuring the uplink SRS for positioning from the target UE in accordance with the request; and sending a report to the network component including measurement information associated with the measured uplink SRS for positioning.

[0008] In one aspect, a network component includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a coarse positioning estimate associated with a target user equipment (UE); determine location information associated with an uplink relay set; and select a wireless node group for a positioning estimate session for the target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group including at least one uplink relay, the at least one uplink relay being configured to transmit uplink wireless data communications from the UE to the wireless node group. Relaying to one or more serving network components, the one or more serving network components being configured to send downlink wireless data communications to the one or more UEs; sending at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE to the at least one uplink relay in association with the positioning estimation session via the at least one transceiver; receiving at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay, via the at least one transceiver; and determining a positioning estimate of the target UE based on the at least one report.

[0009] In one aspect, an uplink relay includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more uplink wireless data communications from one or more user equipment (UE) via the at least one transceiver; relay the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receive a request to measure an uplink sounding reference signal (SRS) for positioning from a target UE from the network component via the at least one transceiver; measure the uplink SRS for positioning from the target UE according to the request; and send a report including measurement information associated with the measured uplink SRS for positioning to the network component via the at least one transceiver.

[0010] In one aspect, an uplink relay includes: a component for determining a coarse positioning estimate associated with a target user equipment (UE); a component for determining location information associated with a set of uplink relays; and a component for selecting a wireless node group for a positioning estimation session of the target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group including at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more service network components, the one or more service network components being configured to send downlink wireless data communications to the one or more UEs; a component for sending at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE to the at least one uplink relay in association with the positioning estimation session; a component for receiving at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and a component for determining a positioning estimate of the target UE based on the at least one report.

[0011] In one aspect, a network component includes: a component for receiving one or more uplink wireless data communications from one or more user equipment (UE); a component for relaying the one or more uplink data communications to one or more serving network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; a component for receiving a request from the network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; a component for measuring the uplink SRS for positioning from the target UE in accordance with the request; and a component for sending a report including measurement information associated with the measured uplink SRS for positioning to the network component.

[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: determine a coarse positioning estimate associated with a target user equipment (UE); determine location information associated with a set of uplink relays; and select a wireless node group for a positioning estimation session for the target UE based on the coarse positioning estimate and the location information associated with the set of uplink relays, the wireless node group comprising at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more serving network components, the one or more serving network components being configured to send downlink wireless data communications to the one or more UEs; send at least one request to the at least one uplink relay to measure an uplink sounding reference signal (SRS) for positioning from the target UE in association with the positioning estimation session; receive at least one report comprising measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and determine a positioning estimate for the target UE based on the at least one report.

[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by an uplink relay, cause the uplink relay to: receive one or more uplink wireless data communications from one or more user equipment (UE); relay the one or more uplink data communications to one or more serving network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receive a request from the network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; measure the uplink SRS for positioning from the target UE in accordance with the request; and send a report to the network component including measurement information associated with the measured uplink SRS for positioning.

[0014] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0016] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0017] Figure 2A , Figure 2B and Figure 2C Example wireless network structures according to aspects of the present disclosure are illustrated.

[0018] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0019] Figure 4 is a diagram illustrating an example frame structure according to aspects of the present disclosure.

[0020] Figure 5 is a diagram illustrating various downlink channels within an example downlink time slot in accordance with aspects of the present disclosure.

[0021] Figure 6 is a diagram illustrating various uplink channels within an example uplink time slot in accordance with aspects of the present disclosure.

[0022] Figure 7 Examples of various positioning methods supported in New Radio (NR) according to aspects of the present disclosure are illustrated.

[0023] Figure 8 UL relay deployment according to aspects of the present disclosure is illustrated.

[0024] Fig. 9 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0025] Fig.10 An exemplary process of communication according to an aspect of the present disclosure is illustrated.

[0026] Fig.11 Illustrate various aspects of the present disclosure Figures 9 and 10 An example specific implementation of the process.

[0027] Fig.12 Illustrate various aspects of the present disclosure Figures 9 and 10 An example specific implementation of the process. DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. In addition, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

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

[0030] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0031] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. In addition, the sequence of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functions described herein. Therefore, various aspects of the present disclosure may be embodied in a variety 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 various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".

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

[0033] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide only edge node signaling functions, while in other systems, it may provide additional control and / or network management functions. The communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). The communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term "traffic channel (TCH)" may refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0034] The term "base station" may refer to a single physical transmit-receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0035] In some specific implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead send a reference signal to be measured by the UE to the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending a signal to the UE) and / or as a position measurement unit (e.g., in the case of receiving and measuring a signal from the UE).

[0036] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0037] Figure 1An example wireless communication system 100 is illustrated in accordance with various aspects of the present disclosure. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femtocells, picocells, microcells, etc.

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

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

[0040] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both of the logical communication entity and the base station supporting it, depending on the context. In addition, because the TRP is generally the physical transmission point of the cell, the terms "cell" and "TRP" can be used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area (e.g., sector) of a base station, as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0041] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG).

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

[0043] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or a listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

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

[0045] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended downward to a frequency of 3 GHz, with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and it is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmitting and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short distances. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0046] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (called a "phased array" or "antenna array") that creates RF beams that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together to increase the radiation in the desired direction while canceling to suppress the radiation in the undesired direction.

[0047] The transmit beams can be quasi-co-located, which means that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antenna is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0048] In receive beamforming, the receiver uses receive beams to amplify RF signals detected on a given channel. For example, the receiver may increase the gain setting of the antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to perform beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or 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.

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

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

[0051] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0052] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0053] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0054] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection reestablishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.

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

[0056] The wireless communication system 100 may also include a UE 164, which may communicate with the macrocell base station 102 via a communication link 120 and / or communicate with the mmW base station 180 via a mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

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

[0058] In one aspect, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources associated with wireless communications between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers). In one aspect, the medium of interest may correspond to at least a portion of an unlicensed band shared between various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those that employ small cell access points) have recently expanded operations into unlicensed bands such as the unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technology (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0059] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UEs 164 and 182), but any of the illustrated UEs may be SL-UEs. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including UE 164) may be capable of beamforming. In the case where SL-UEs are capable of beamforming, they may beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward base stations (e.g., base stations 102, 180, small cells 102', access point 150), etc. Therefore, in some cases, UE 164 and UE 182 may utilize beamforming via side link 160.

[0060] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any of the UEs 104 (shown as a single UE 104 in FIG. 1 ) may receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 may be part of a satellite positioning system that the UEs 104 may use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on a positioning signal (e.g., signal 124) received from the transmitter. Such transmitters typically transmit signals marked with a repeating pseudo-random noise (PN) code of a set number of chips. Although typically located in the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 may include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0061] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), etc. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0062] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as an improved base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from a ground base station 102, a UE 104 can receive communication signals (e.g., signal 124) from a SV 112.

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

[0064] Figure 2A An example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

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

[0066] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally viewed as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

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

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

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

[0070] Yet another optional aspect may include a third-party server 274 that may communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party server 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively may each correspond to a single server.

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

[0072] The functionality of the gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DU) 228, and one or more gNB radio units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and the like. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 may support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0073] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5GNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as a standalone base station or a single-chip base station) or a decomposed base station.

[0074] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0075] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0076] Figure 2C An example disaggregated base station architecture 250 is illustrated in accordance with aspects of the present disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226) that may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 259 via an E2 link or a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. The CU 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RU 287 can communicate with a corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

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

[0078] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 280. CU280 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

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

[0080] The lower layer functionality may be implemented by one or more RUs 287. In some deployments, the RU 287 controlled by the DU 285 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0082] The non-RT RIC 257 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 259. The non-RT RIC 257 may be coupled to or communicate with the near-RT RIC 259 (such as via an A1 interface). The near-RT RIC 259 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 280, one or more DUs 285, or both, and the O-eNB with the near-RT RIC 259.

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

[0084] Figure 3A , Figure 3B and Figure 3C The examples may be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the present invention (such as a dedicated network) are shown to support operations as described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functions. In addition, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0085] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) on a wireless communication medium of interest (e.g., a set of time / frequency resources in a particular spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, the WWAN transceivers 310 and 350 include: one or more transmitters 314 and 354 for transmitting and encoding the signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding the signals 318 and 358, respectively.

[0086] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are components (e.g., components for sending, components for receiving, components for measuring, components for tuning, components for preventing sending, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) using a PC5, dedicated short-range communication (DSRC), wireless access for vehicle environments (WAVE), near field communication (NFC), ultra-wideband (UWB), etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0087] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the positions of UE 302 and base station 304, respectively.

[0088] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0089] The transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit system (e.g., transmitters 314, 324, 354, 364) and a receiver circuit system (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., implementing the transmitter circuit system and the receiver circuit system in a single device), in some implementations may include separate transmitter circuit systems and separate receiver circuit systems, or may be implemented in other ways in other implementations. The transmitter circuit system and the receiver circuit system of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

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

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

[0092] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398, respectively, may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which when executed cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the positioning components 342, 388, and 398 can be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0093] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

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

[0095] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0096] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

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

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

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

[0100] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0101] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to the one or more processors 384.

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

[0103] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. Specifically, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of a wearable device or a tablet computer or a PC or a laptop computer, a specific implementation of the UE 302 may omit the WWAN transceiver 310 (e.g., a wearable device or a tablet computer or a PC or a laptop computer may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), may omit the short-range wireless transceiver 320 (e.g., only cellular, etc.), may omit the satellite signal receiver 330, may omit the sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0104] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, ​​and 392 may provide for communication between the different logical entities.

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

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

[0107] Various frame structures may be used to support downlink and uplink transmissions between network nodes (eg, base stations and UEs). Figure 4 4 is a diagram illustrating an example frame structure according to aspects of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0108] LTE (and in some cases NR) utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often called tones, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of the subcarriers can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180kHz). Thus, for a system bandwidth of 1.25 megahertz (MHz), 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, respectively.

[0109] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple parameter sets (μ), for example, 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger subcarrier spacings may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5ms, the symbol duration is 33.3μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25ms, the symbol duration is 16.7μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125ms, the symbol duration is 8.33μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625ms, the symbol duration is 4.17μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0110] exist Figure 4 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each subframe is 1 ms, and each subframe includes one time slot. Figure 4 , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top.

[0111] A resource grid may be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. Figure 4In the parameter set of , for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0112] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 Example locations of REs carrying reference signals (labeled "R") are illustrated.

[0113] On the one hand, Figure 4 The reference signal carried on the RE marked with "R" in the figure can be an SRS. The SRS sent by the UE can be used by the base station to obtain channel state information (CSI) for the transmitting UE. CSI describes how the RF signal propagates from the UE to the base station and represents the combined effect of scattering, attenuation, and power attenuation with distance. The system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

[0114] The set of REs used for transmission of SRS is called "SRS resource" and can be identified by the parameter "SRS-ResourceId". The set of resource elements can span multiple PRBs in the frequency domain and 'N' (e.g., one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol, an SRS resource occupies one or more consecutive PRBs. An "SRS resource set" is a set of SRS resources used for transmission of SRS signals and is identified by an SRS resource set ID ("SRS-ResourceSetId").

[0115] The transmission of the SRS resource within a given PRB has a specific comb size (also referred to as "comb density"). The comb size 'N' represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the SRS resource configuration. Specifically, for comb size 'N', the SRS is transmitted in every Nth subcarrier of a symbol of the PRB. For example, for comb-4, for each symbol of the SRS resource configuration, the REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit the SRS of the SRS resource. Figure 4In the example of FIG. 1 , the illustrated SRS is comb-tooth-4 on four symbols. That is, the position of the shaded SRS RE indicates the SRS resource configuration of comb-tooth-4.

[0116] Currently, SRS resources with a comb size of Comb-2, Comb-4, or Comb-8 can span 1, 2, 4, 8, or 12 consecutive symbols within a slot. The following are the symbol-by-symbol frequency offsets for the currently supported SRS comb patterns. 1-Symbol Comb-2: {0}; 2-Symbol Comb-2: {0,1}; 2-Symbol Comb-4: {0,2}; 4-Symbol Comb-2: {0,1,0,1}; 4-Symbol Comb-4: {0,2,1,3} (as in Figure 4 in the example); 8-symbol comb-4: {0,2,1,3,0,2,1,3}; 12-symbol comb-4: {0,2,1,3,0,2,1,3,0,2,1,3}; 4-symbol comb-8: {0,4,2,6}; 8-symbol comb-8: {0,4,2,6,1,5,3,7}; and 12-symbol comb-8: {0,4,2,6,1,5,3,7,0,4,2,6}.

[0117] In general, as mentioned, the UE sends the SRS to enable the receiving base station (serving base station or neighboring base station) to measure the channel quality (i.e., CSI) between the UE and the base station. However, the SRS may also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round trip time (RTT), uplink angle of arrival (UL-AoA), etc. As used herein, the term "SRS" may refer to an SRS configured for channel quality measurement or an SRS configured for positioning purposes. When it is necessary to distinguish between two types of SRS, the former may be referred to as "SRS for communication" and / or the latter may be referred to as "SRS for positioning" or "positioning SRS" in this article.

[0118] Several enhancements to the previous definition of SRS have been proposed for "SRS for positioning" (also known as "UL-PRS"), such as a new staggering pattern within the SRS resource (in addition to a single symbol / comb-2), a new comb type for SRS, a new sequence for SRS, a larger number of SRS resource sets per component carrier, and a larger number of SRS resources per component carrier. In addition, the parameters "SpatialRelationInfo" and "PathLossReference" are to be configured based on downlink reference signals or SSBs from neighboring TRPs. Furthermore, one SRS resource may be sent outside the active BWP, and one SRS resource may span multiple component carriers. Moreover, the SRS may be configured in the RRC connected state and sent only within the active BWP. In addition, there may be no frequency hopping, no repetition factor, a single antenna port, and new lengths for the SRS (e.g., 8 and 12 symbols). There may also be open-loop power control and no closed-loop power control, and comb-8 (i.e., SRS sent every eighth subcarrier in the same symbol) may be used. Finally, the UE may transmit from multiple SRS resources through the same transmit beam for UL-AoA. All of these are features outside the current SRS framework, which is configured through RRC higher layer signaling (and potentially triggered or activated through MAC Control Element (MAC-CE) or Downlink Control Information (DCI)).

[0119] Figure 5 5 is a diagram 500 illustrating various downlink channels within an example downlink time slot. Figure 5 In , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top. Figure 5 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0120] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth parts (BWPs). A BWP is a set of contiguous RBs selected from a contiguous subset of common RBs for a given parameter set on a given carrier. In general, a maximum of four BWPs can be specified in the downlink and uplink. That is, the UE can be configured to have up to four BWPs on the downlink and up to four BWPs on the uplink. Only one BWP (uplink or downlink) can be active at a given time, which means that the UE can only receive or transmit on one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0121] refer to Figure 5 , the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form an SSB (also referred to as SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (such as the system information block (SIB)), and paging messages.

[0122] The physical downlink control channel (PDCCH) carries downlink control information (DCI) in one or more control channel elements (CCEs), each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain), each REG bundle includes one or more REGs, each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for PDCCH.

[0123] exist Figure 5 In the example of , there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be just one symbol or two symbols). Unlike LTE control channels that occupy the entire system bandwidth, in NR, the PDCCH channel is localized to a specific region (i.e., CORESET) in the frequency domain. Therefore, Figure 5 The frequency components of the PDCCH shown in FIG are illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESETs are continuous in the frequency domain, the CORESETs do not need to be continuous. Furthermore, the CORESETs may span less than three symbols in the time domain.

[0124] The DCI within the PDCCH carries information about uplink resource allocations (persistent and non-persistent) and descriptions of downlink data sent to the UE (referred to as uplink grants and downlink grants, respectively). More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs may be configured in the PDCCH, and these DCIs may have one of a variety of formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. The PDCCH may be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or coding rates.

[0125] Figure 6 6 is a diagram illustrating various uplink channels within an example uplink time slot. Figure 6 In , time is represented horizontally (on the X-axis), where time increases from left to right, while frequency is represented vertically (on the Y-axis), where frequency increases (or decreases) from bottom to top. Figure 6 In the example of , a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), divided into 14 symbols.

[0126] The random access channel (RACH), also known as the physical random access channel (PRACH), may be within one or more time slots within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a time slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. The physical uplink control channel (PUCCH) may be located at the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The physical uplink shared channel (PUSCH) carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0127] NR supports a variety of cellular network-based positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and downlink and uplink-based positioning methods. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 7Examples of various positioning methods according to various aspects of the present disclosure are illustrated. In the OTDOA or DL-TDOA positioning process illustrated in scenario 710, the UE measures the difference between the arrival times (ToA) of reference signals (e.g., positioning reference signals (PRS)) received from paired base stations (referred to as reference signal time difference (RSTD) or arrival time difference (TDOA) measurements), and reports these differences to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known positions of the base stations involved and the RSTD measurements, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the position of the UE.

[0128] For DL-AoD positioning illustrated in scenario 720, the positioning entity uses measurement reports from the UE regarding received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the position of the UE based on the determined angle and the known position of the transmitting base station.

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

[0130] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle of the receive beams to determine the angle between the UE and the base station. Based on the determined angle and the known location of the base station, the positioning entity can then estimate the location of the UE.

[0131] Downlink and uplink based positioning methods include: enhanced cell ID (E-CID) positioning and multiple round trip time (RTT) positioning (also referred to as "multi-cell RTT" and "multi-RTT"). In the RTT procedure, a first entity (e.g., a base station or UE) sends a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity sends a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference is called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest time slot boundary of the received signal and the transmitted signal. The two entities may then transmit their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round trip propagation time (i.e., RTT) between the two entities based on the two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may transmit its Rx-Tx time difference measurements to the other entity, which then calculates the RTT. The distance between the two entities may be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning illustrated in scenario 730, a first entity (e.g., a UE or a base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distance to the second entity and the known location of the second entity. RTT and multi-RTT methods may be combined with other positioning techniques (such as UL-AoA and DL-AoD) to improve location accuracy, as illustrated in scenario 740.

[0132] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing and signal strength of the detected neighboring base stations. The UE's position is then estimated based on this information and the known location of the base stations.

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

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

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

[0136] In a typical communication scenario, a UE communicates directly with a serving cell (e.g., gNBs) via DL signals and UL signals, as described above. In some designs, to enhance UL performance (e.g., particularly due to limited UL power from the UE), a UL "dense" deployment may be used, whereby one or more UL relays are used to relay UL signals from a UE (e.g., a UE located at an edge, etc.) to a serving cell. In an example, a UL relay may be attached to a serving cell. In some designs, UL relays may be densely deployed so that at multiple cell locations, a UE in a serving cell may use relatively close UL relays (e.g., which may help reduce UL power requirements for the UE).

[0137] Figure 8 An UL relay deployment 800 is illustrated in accordance with aspects of the present disclosure. Figure 8 , UE 1 and UE 2 communicate with gNB 810. Specifically, on the DL, DL signals 812 and 814 are sent directly by gNB 810 to UE 1 and UE 2. However, UL signaling is mediated by UL relays 820 and 830. UL relay 820 includes a wireless interface 822 (e.g., for receiving UL signals from the UE) and a wireless backhaul interface 824 (e.g., for forwarding any detected UL signals as wireless signals to gNB 810). UL relay 830 includes a wireless interface 832 (e.g., for receiving UL signals from the UE) and a wired backhaul interface 834 (e.g., for forwarding any detected UL signals as wired signals to gNB 810). At 844, UE 1 sends the UL signal 842 to the wireless interface 822 of the UL relay 820, which wirelessly relays the UL signal to the gNB 810 via the wireless backhaul interface 824. At 854, UE 2 sends the UL signal 852 to the wireless interface 832 of the UL relay 830, which relays the UL signal to the gNB 810 via the wired backhaul interface 834. In some designs, the UL relay 820 and / or the UL relay 830 may correspond to a network component (e.g., a version of BS 304, a roadside unit, etc.). In some designs, the UL relay 820 may correspond to a UE (e.g., UE 302).

[0138] In some designs, the UL relay may implement a resource reuse scheme (e.g., UEs in the coverage area of ​​the serving cell may use the same resources or RBs to communicate with different UL relays). In this case, UL interference may be a consideration. In other designs, resources may be shared by UL relays to reduce interference (e.g., for a particular RB, only one UL relay may use the RB at a particular time).

[0139] In the current implementation, the UL relay is used only to relay UL communications and not to facilitate other functionality such as positioning estimation of the UE. Various aspects of the present disclosure are thus directed to utilizing the UL relay to improve the positioning estimation of the UE. In certain aspects, the UL relay may be configured to measure the UL SRS from the UE for positioning and report the UL SRS measurements to the positioning estimation entity. Such aspects may provide various technical advantages, such as improved positioning estimation of the UE, reduced power consumption of the UE (e.g., because the UE can send the SRS at a lower power because the UL relay is closer to the UE than the neighboring gNB), etc.

[0140] Fig. 9 An exemplary process 900 of communicating according to an aspect of the present disclosure is illustrated. Fig. 9The process 900 is performed by a network component (eg, BS 304, an O-RAN component such as RU or CU or DU, an LMF implemented at BS 304 or at network entity 306, etc.) as a positioning estimation entity.

[0141] refer to Fig. 9 At 910, a network component (e.g., processor 384 or 394, positioning component 388 or 398, etc.) determines a coarse positioning estimate associated with the target UE. For example, the coarse positioning estimate may correspond to (or be based on) a most recent (e.g., previous) positioning estimate of the target UE, a set of UL relays or other UEs within communication range of the target UE's UL signal, a beam used by the gNB for DL ​​communications with the target UE, etc. In general, in an example, the coarse positioning estimate may be sufficient to identify several UL relays within range of an SRS transmission from the target UE (e.g., a transmission of the SRS at a relatively low power level (e.g., lower than the transmit power level required for the UE to transmit directly to the serving network component or gNB)).

[0142] refer to Fig. 9 At 920, a network component (e.g., processor 384 or 394, positioning component 388 or 398, etc.) determines location information associated with an uplink relay set. The determination at 920 can be performed in a variety of ways. For example, the uplink relay set can be associated with a serving network component (e.g., a gNB) that manages the uplink relay set. The serving network component can report the location information associated with the uplink relay set to the network component to facilitate the determination at 920. In other aspects, the execution Fig. 9 The network component of process 900 may correspond to a serving network component. In other designs, the set of uplink relays may be registered directly with the network component, in which case the location information is obtained from the set of uplink relays. In still other designs, the location information may be determined from a positioning estimation process (e.g., RTT-based positioning estimation, TDOA-based positioning estimation, AoA / AoD-based positioning estimation, etc.). For example, such a positioning estimation process may be used for a non-stationary uplink relay (e.g., a UE).

[0143] refer to Fig. 9At 930, a network component (e.g., processor 384 or 394, positioning component 388 or 398, etc.) selects a wireless node group for a positioning estimation session of a target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group including at least one uplink relay, the at least one uplink relay configured to relay uplink wireless data communications from the UE to one or more serving network components, the one or more serving network components configured to send downlink wireless data communications to one or more UEs. In some designs, the wireless node group may consist of only uplink relays. In other designs, the wireless node group may include uplink relays and other device types, such as other UEs (e.g., performing positioning estimation via sidelink signaling), or even gNBs (e.g., serving gNBs, non-serving gNBs, etc.).

[0144] refer to Fig. 9 , at 940, a network component (e.g., transmitter 354 or 364, network transceiver 380 or 390, etc.) sends at least one request to measure an uplink sounding reference signal (SRS) for positioning from a target UE to at least one uplink relay in association with the positioning estimation session.

[0145] refer to Fig. 9 , at 950, a network component (e.g., receiver 352 or 362, network transceiver 380 or 390, etc.) receives at least one report including measurement information associated with an uplink SRS for positioning from a target UE, as measured by at least one uplink relay.

[0146] refer to Fig. 9 At 960, a network component (eg, processor 384 or 394, positioning component 388 or 398, etc.) determines a positioning estimate for the target UE based on at least one report.

[0147] refer to Fig. 9, in one aspect, the network component corresponds to a location management function (LMF). In some designs, presence information associated with an uplink relay set, location information associated with an uplink relay set, or both are received at the LMF from a serving network component (e.g., a serving gNB) of a target UE. For example, presence information associated with an uplink relay set, location information associated with an uplink relay set, or both are received at the LMF from a serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling. In some designs, the LMF also sends a request to enable an SRS measurement mode for at least one uplink relay to a serving network component (e.g., a serving gNB) of the target UE. In an example, a request to enable an SRS measurement mode for at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling. In some designs, at least one report includes combined information associated with measurement information from multiple uplink relays. In some designs, at least one report is received from at least one uplink relay or from a serving network component (e.g., a serving gNB for the target UE).

[0148] refer to Fig. 9 In another aspect, the network component corresponds to a serving network component (e.g., a serving gNB) of the target UE. In this case, in an example, a coarse positioning estimate is received at the serving network component from a location management function (LMF).

[0149] refer to Fig. 9 In some designs, the selection at 930 is based in part on the number of network components associated with each uplink relay in the set of uplink relays. For example, the selection may be weighted to favor selecting uplink relays associated with a greater number of network components (e.g., selecting uplink relays associated with two gNBs rather than uplink relays associated with a single gNB, etc.).

[0150] refer to Fig. 9 In some designs, a transmit power level of an uplink SRS for positioning may be determined by a network component based on location information associated with the group of wireless nodes selected at 930.

[0151] refer to Fig. 9 In some designs, the at least one uplink relay includes a single uplink relay. In other designs, the at least one uplink relay includes a plurality of uplink relays.

[0152] refer to Fig. 9 In some designs, the network component may also send a beam configuration associated with the transmission of an uplink SRS for positioning to the target UE.

[0153] Fig.10 An exemplary process 1000 of communicating according to an aspect of the present disclosure is illustrated. Fig.10 The process 1000 is performed by an uplink relay such as uplink relay 820 or 830, which may correspond to example implementations of UE 302, BS 304, O-RAN components such as RU, etc. as described above.

[0154] refer to Fig.10 At 1010, an uplink relay (eg, receiver 312 or 322 or 352 or 362, network transceiver 380, wireless backhaul interface 824, wired backhaul interface 834, etc.) receives one or more uplink wireless data communications from one or more user equipment (UE).

[0155] refer to Fig.10 At 1020, an uplink relay (e.g., transmitter 314 or 324 or 354 or 364, network transceiver 380, wireless backhaul interface 824, wired backhaul interface 834, etc.) relays one or more uplink data communications via a backhaul connection to one or more serving network components configured to send downlink wireless data communications to one or more UEs.

[0156] refer to Fig.10 At 1030, the uplink relay (e.g., receiver 312 or 322 or 352 or 362, network transceiver 380, wireless backhaul interface 824, wired backhaul interface 834, etc.) receives a request from a network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE.

[0157] refer to Fig.10 At 1040, the uplink relay (e.g., receiver 312 or 322 or 352 or 362, network transceiver 380, wireless backhaul interface 824, wired backhaul interface 834, etc.) measures the uplink SRS for positioning from the target UE according to the request. For example, the SRS measurement at 1040 may include TOA or TDOA measurement, RTT measurement, AoA / AoD measurement, etc.

[0158] refer to Fig.10 At 1050, the uplink relay (e.g., transmitter 314 or 324 or 354 or 364, network transceiver 380, wireless backhaul interface 824, wired backhaul interface 834, etc.) sends a report to the network component including measurement information associated with the measured uplink SRS used for positioning.

[0159] refer to Fig.10In some designs, the network component corresponds to a location management function (LMF) of the target UE or a serving network component (e.g., a serving gNB). In some designs, the uplink relay is closer to the target UE than the serving network component (e.g., a serving gNB) of the target UE. For example, in Fig. 9 Each uplink relay selected at 930 for the positioning estimation process may be within a relatively small location area "A" around the target UE. In an aspect, the target UE may be configured to send the UL SRS at a lower transmit power (e.g., compared to the transmit power required to send the UL SRS for serving gNB and / or neighbor gNB measurements). In some designs, the backhaul connection includes a wireless backhaul connection. In other designs, the backhaul connection includes a wired backhaul connection.

[0160] Fig.11 Illustrate various aspects of the present disclosure Figures 9 and 10 An example implementation of the processes 900-1000 is 1100. Fig.11 In the example implementation 1100, the network component corresponds to LMF 306, the serving network component corresponds to gNB 304, the UL relay set includes multiple UL relays each configured as UL relay 820 or UL relay 830, and the target UE corresponds to UE 302.

[0161] At 1102, the gNB 304 sends an indication of the presence of UE relays associated with the UL relay set (e.g., availability, location, etc. of the UL relay set) to the LMF 306. At 1102, the LMF 306 optionally configures the UL SRS on the UL relay set. In an aspect, the UL relay set may be selected by the LMF 306 based on a coarse positioning estimate of the UE 302. Alternatively, at 1106, the LMF 306 may optionally send the coarse positioning estimate of the UE 302 to the gNB 304, which in turn selects the UL relay set for the positioning estimation process. In either case, at 1108, the gNB 304 sends an SRS configuration for the UE 302 to send the UL SRS. In an aspect, the SRS configuration may be associated with a reduced transmit power level, a directional configuration (e.g., a beam configuration) based on the UL relay location, and the like. At 1110, the gNB 304 shares the UL SRS configuration with the LMF 306. At 1112, the LMF 306 sends a request to the gNB 304 to measure the UL SRS for the selected set of UL relays. At 1114, the gNB 304 sends a request to measure the UL SRS to each UL relay in the selected set of UL relays. At 1116, the UE 302 sends a UL SRS, which is measured at 1118 by the selected UL relays. At 1120, the selected set of UL relays sends the UL SRS measurements to the gNB 304. At 1122, the gNB 304 sends the combined UL SRS measurements from the selected set of UL relays to the LMF 306. At 1124, the LMF 306 derives a positioning estimate for the UE 302 based at least in part on the combined UL SRS measurements from the selected set of UL relays.

[0162] Fig.12 Illustrate various aspects of the present disclosure Figures 9 and 10 An example implementation of the processes 900-1000 is 1200. Fig.12 In the example implementation 1200, the network component corresponds to LMF 306, the serving network component corresponds to gNB 304, the UL relay set includes a plurality of UL relays each configured as UL relay 820 or UL relay 830, and the target UE corresponds to UE 302. Fig.11 Different, in Fig.12 In the embodiment, the LMF 306 is able to communicate directly with the UL relay.

[0163] At 1202, the gNB 304 sends an indication of the presence of UE relays associated with a UL relay set to the LMF 306 (e.g., availability, location, etc. of the UL relay set). At 1202, the LMF 306 optionally configures a UL SRS on the UL relay set. In an aspect, the UL relay set may be selected by the LMF 306 based on a coarse positioning estimate of the UE 302. Alternatively, at 1206, the LMF 306 may optionally send the coarse positioning estimate of the UE 302 to the gNB 304, which in turn selects the UL relay set for the positioning estimation process. In either case, at 1208, the gNB 304 sends an SRS configuration for the UE 302 to send the UL SRS. In an aspect, the SRS configuration may be associated with a reduced transmit power level, a directional configuration (e.g., a beam configuration) based on the UL relay location, and the like. At 1210, the gNB 304 shares the UL SRS configuration with the LMF 306. At 1212, the LMF 306 sends a request to the selected UL relay set for the selected UL relay set to measure the UL SRS. At 1216, the UE 302 sends the UL SRS, which is measured by the selected UL relay set at 1218. At 1220, the selected UL relay sends the UL SRS measurement to the LMF 306. At 1224, the LMF 306 derives a positioning estimate for the UE 302 based at least in part on the UL SRS measurement from the selected UL relay set.

[0164] refer to Figures 9 and 10 , in some designs, various technical advantages may include:

[0165] Using UL relays near the target UE may improve accuracy and capacity, and / or

[0166] The target UE may send UL SRS at lower power so as to be received and measured only by nearby UL relays in a small location area "A" around the target UE, and / or

[0167] Lower transmit power reduces interference outside of area A, thereby allowing other UEs outside area A to transmit UL SRS and locate simultaneously (relayed by other ULs), thereby increasing capacity, and / or

[0168] The proximity of the UL relay in region A will increase the positioning estimate accuracy of the target UE,

[0169] and / or

[0170] The positioning estimation process can be performed via various techniques (such as UL-TDOA, UL-AOA and

[0171] / or RTT positioning estimation process) is flexibly performed.

[0172] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, wherein each clause itself can be used as a separate example. Although each subordinate clause may refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to a specific combination. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. Various aspects disclosed herein explicitly include these combinations, unless it is clearly expressed or can be easily inferred that a specific combination is not intended to be used (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0173] Specific implementation examples are described in the following numbered clauses:

[0174] Clause 1. A method of operating a network component, the method comprising: determining a coarse positioning estimate associated with a target user equipment (UE); determining location information associated with an uplink relay set; and selecting a wireless node group for a positioning estimation session of the target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group comprising at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more service network components, the one or more service network components being configured to send downlink wireless data communications to the one or more UEs; sending at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE in association with the positioning estimation session to the at least one uplink relay; receiving at least one report comprising measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and determining a positioning estimate of the target UE based on the at least one report.

[0175] Clause 2. The method of clause 1, wherein the network component corresponds to a location management function (LMF).

[0176] Clause 3. A method according to clause 2, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

[0177] Clause 4. A method according to Clause 3, wherein the presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from the serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0178] Clause 5. A method as described in any of clauses 2 to 4, the method further comprising: sending a request to a serving network component of the target UE to enable an SRS measurement mode for the at least one uplink relay.

[0179] Clause 6. A method according to clause 5, wherein the request to enable the SRS measurement mode of the at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0180] Clause 7. A method as described in any of clauses 2 to 6, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

[0181] Clause 8. A method as described in any of clauses 2 to 7, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

[0182] Clause 9. A method as described in any of clauses 1 to 8, wherein the network component corresponds to a serving network component of the target UE.

[0183] Clause 10. The method of clause 9, wherein the coarse positioning estimate is received at the serving network component from a location management function (LMF).

[0184] Clause 11. The method of any of clauses 1 to 10, wherein the selecting is based in part on a number of network components associated with each uplink relay in the set of uplink relays.

[0185] Clause 12. The method of clause 11, wherein the selection is weighted to favor selection of uplink relays associated with a higher number of network components.

[0186] Clause 13. The method of any one of clauses 1 to 12, further comprising determining a transmit power level of the uplink SRS for positioning based on location information associated with the group of wireless nodes.

[0187] Clause 14. The method of any of clauses 1 to 13, wherein the at least one uplink relay comprises a single uplink relay.

[0188] Clause 15. The method of any one of clauses 1 to 14, wherein the at least one uplink relay comprises a plurality of uplink relays.

[0189] Clause 16. A method according to any one of clauses 1 to 15, the method further comprising: sending a beam configuration associated with the transmission of the uplink SRS for positioning to the target UE.

[0190] Clause 17. A method for operating an uplink relay, the method comprising: receiving one or more uplink wireless data communications from one or more user equipment (UE); relaying the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receiving a request from the network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; measuring the uplink SRS for positioning from the target UE based on the request; and sending a report to the network component including measurement information associated with the measured uplink SRS for positioning.

[0191] Clause 18. The method of clause 17, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

[0192] Clause 19. A method as described in any of clauses 17 to 18, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

[0193] Clause 20. The method of any one of clauses 17 to 19, wherein the backhaul connection comprises a wireless backhaul connection.

[0194] Clause 21. The method of any one of clauses 17 to 20, wherein the backhaul connection comprises a wired backhaul connection.

[0195] Clause 22. A network component, the network component comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a coarse position estimate associated with a target user equipment (UE); determine location information associated with an uplink relay set; and select a wireless node group for a location estimation session of the target UE based on the coarse position estimate and the location information associated with the uplink relay set, the wireless node group comprising at least one uplink relay, the at least one uplink relay being configured to communicate uplink wireless data Relayed from the UE to one or more serving network components, the one or more serving network components being configured to send downlink wireless data communications to the one or more UEs; send at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE to the at least one uplink relay in association with the positioning estimation session via the at least one transceiver; receive at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay, via the at least one transceiver; and determine a positioning estimate for the target UE based on the at least one report.

[0196] Clause 23. The network component of Clause 22, wherein the network component corresponds to a location management function (LMF).

[0197] Clause 24. A network component according to clause 23, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

[0198] Clause 25. A network component according to clause 24, wherein the presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from the serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0199] Clause 26. A network component according to any one of clauses 23 to 25, wherein the at least one processor is further configured to: send a request to enable an SRS measurement mode of the at least one uplink relay to a serving network component of the target UE via the at least one transceiver.

[0200] Clause 27. A network component according to clause 26, wherein the request to enable the SRS measurement mode of the at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0201] Clause 28. A network component as set forth in any of clauses 23 to 27, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

[0202] Clause 29. A network component as described in any of clauses 23 to 28, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

[0203] Clause 30. A network component as described in any of clauses 22 to 29, wherein the network component corresponds to a serving network component of the target UE.

[0204] Clause 31. The network component of Clause 30, wherein the coarse positioning estimate is received at the serving network component from a location management function (LMF).

[0205] Clause 32. A network component as set forth in any of clauses 22 to 31, wherein the selection is based in part on a number of network components associated with each uplink relay in the set of uplink relays.

[0206] Clause 33. The network component of clause 32, wherein the selection is weighted to favor selection of uplink relays associated with a higher number of network components.

[0207] Clause 34. A network component as described in any of clauses 22 to 33, wherein the at least one processor is further configured to: determine a transmit power level of the uplink SRS used for positioning based on location information associated with the group of wireless nodes.

[0208] Clause 35. A network component as described in any of clauses 22 to 34, wherein the at least one uplink relay comprises a single uplink relay.

[0209] Clause 36. A network component as described in any of clauses 22 to 35, wherein the at least one uplink relay comprises a plurality of uplink relays.

[0210] Clause 37. A network component according to any of clauses 22 to 36, wherein the at least one processor is further configured to: send a beam configuration associated with the transmission of the uplink SRS for positioning to the target UE via the at least one transceiver.

[0211] Clause 38. An uplink relay, the uplink relay comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive one or more uplink wireless data communications from one or more user equipment (UE) via the at least one transceiver; relay the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receive a request to measure an uplink sounding reference signal (SRS) for positioning from a target UE from a network component via the at least one transceiver; measure the uplink SRS for positioning from the target UE based on the request; and send a report including measurement information associated with the measured uplink SRS for positioning to the network component via the at least one transceiver.

[0212] Clause 39. An uplink relay as described in clause 38, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

[0213] Clause 40. An uplink relay as described in any of clauses 38 to 39, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

[0214] Clause 41. Uplink relay as described in any of clauses 38 to 40, wherein the backhaul connection comprises a wireless backhaul connection.

[0215] Clause 42. An uplink relay as described in any of clauses 38 to 41, wherein the backhaul connection comprises a wired backhaul connection.

[0216] Clause 43. An uplink relay, the uplink relay comprising: a component for determining a coarse positioning estimate associated with a target user equipment (UE); a component for determining location information associated with a set of uplink relays; and a component for selecting a wireless node group for a positioning estimation session for the target UE based on the coarse positioning estimate and the location information associated with the uplink relay set, the wireless node group comprising at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more service network components, the one or more service network components being configured to send downlink wireless data communications to the one or more UEs; a component for sending at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE in association with the positioning estimation session to the at least one uplink relay; a component for receiving at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and a component for determining a positioning estimate for the target UE based on the at least one report.

[0217] Clause 44. The uplink relay of clause 43, wherein the network component corresponds to a location management function (LMF).

[0218] Clause 45. An uplink relay according to clause 44, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

[0219] Clause 46. An uplink relay according to clause 45, wherein the presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from the serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0220] Clause 47. An uplink relay as described in any of clauses 44 to 46, the uplink relay further comprising means for sending a request to a serving network component of the target UE to enable an SRS measurement mode for the at least one uplink relay.

[0221] Clause 48. An uplink relay according to clause 47, wherein the request to enable the SRS measurement mode of the at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0222] Clause 49. An uplink relay as described in any of clauses 44 to 48, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

[0223] Clause 50. An uplink relay as described in any of clauses 44 to 49, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

[0224] Clause 51. Uplink relay as described in any of clauses 43 to 50, wherein the network component corresponds to a serving network component of the target UE.

[0225] Clause 52. The uplink relay of clause 51, wherein the coarse positioning estimate is received at the serving network component from a location management function (LMF).

[0226] Clause 53. An uplink relay as described in any of clauses 43 to 52, wherein the selection is based in part on a number of network components associated with each uplink relay in the set of uplink relays.

[0227] Clause 54. The uplink relay of clause 53, wherein the selection is weighted to favor selection of uplink relays associated with a higher number of network components.

[0228] Clause 55. An uplink relay as described in any of clauses 43 to 54, the uplink relay further comprising: means for determining a transmit power level of the uplink SRS used for positioning based on location information associated with a group of wireless nodes.

[0229] Clause 56. An uplink relay as described in any of clauses 43 to 55, wherein the at least one uplink relay comprises a single uplink relay.

[0230] Clause 57. An uplink relay as described in any of clauses 43 to 56, wherein the at least one uplink relay comprises a plurality of uplink relays.

[0231] Clause 58. An uplink relay as described in any of clauses 43 to 57, the uplink relay further comprising: means for sending a beam configuration associated with the transmission of the uplink SRS for positioning to the target UE.

[0232] Clause 59. A network component comprising: a component for receiving one or more uplink wireless data communications from one or more user equipment (UE); a component for relaying the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; a component for receiving a request from the network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; a component for measuring the uplink SRS for positioning from the target UE based on the request; and a component for sending a report to the network component including measurement information associated with the measured uplink SRS for positioning.

[0233] Clause 60. A network component as described in Clause 59, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

[0234] Clause 61. A network component as described in any of clauses 59 to 60, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

[0235] Clause 62. A network component as described in any of clauses 59 to 61, wherein the backhaul connection comprises a wireless backhaul connection.

[0236] Clause 63. The network component of any one of clauses 59 to 62, wherein the backhaul connection comprises a wired backhaul connection.

[0237] Clause 64. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: determine a coarse positioning estimate associated with a target user equipment (UE); determine location information associated with a set of uplink relays; and select a wireless node group for a position estimation session for the target UE based on the coarse position estimate and the location information associated with the set of uplink relays, the wireless node group comprising at least one uplink relay, the at least one uplink relay being configured to relay uplink wireless data communications from the UE to one or more serving network components, the one or more serving network components being configured to send downlink wireless data communications to the one or more UEs; send at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE in association with the positioning estimation session to the at least one uplink relay; receive at least one report comprising measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; and determine a positioning estimate for the target UE based on the at least one report.

[0238] Clause 65. The non-transitory computer-readable medium of Clause 64, wherein the network component corresponds to a location management function (LMF).

[0239] Clause 66. A non-transitory computer-readable medium according to clause 65, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

[0240] Clause 67. A non-transitory computer-readable medium according to clause 66, wherein the presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from the serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0241] Clause 68. A non-transitory computer-readable medium according to any one of clauses 65 to 67, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the network component, cause the network component to: send a request to the serving network component of the target UE to enable the SRS measurement mode of the at least one uplink relay.

[0242] Clause 69. A non-transitory computer-readable medium according to clause 68, wherein the request to enable the SRS measurement mode of the at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

[0243] Clause 70. The non-transitory computer-readable medium of any of clauses 65 to 69, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

[0244] Clause 71. The non-transitory computer-readable medium of any of clauses 65 to 70, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

[0245] Clause 72. The non-transitory computer-readable medium of any of clauses 64 to 71, wherein the network component corresponds to a serving network component of the target UE.

[0246] Clause 73. The non-transitory computer-readable medium of Clause 72, wherein the coarse positioning estimate is received at the serving network component from a location management function (LMF).

[0247] Clause 74. The non-transitory computer-readable medium of any of clauses 64 to 73, wherein the selection is based in part on a number of network components associated with each uplink relay in the set of uplink relays.

[0248] Clause 75. The non-transitory computer-readable medium of clause 74, wherein the selection is weighted to favor selection of uplink relays associated with a higher number of network components.

[0249] Clause 76. A non-transitory computer-readable medium according to any one of clauses 64 to 75, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the network component, cause the network component to: determine a transmit power level of the uplink SRS used for positioning based on location information associated with the wireless node group.

[0250] Clause 77. The non-transitory computer-readable medium of any one of clauses 64 to 76, wherein the at least one uplink relay comprises a single uplink relay.

[0251] Clause 78. The non-transitory computer-readable medium of any one of clauses 64 to 77, wherein the at least one uplink relay comprises a plurality of uplink relays.

[0252] Clause 79. A non-transitory computer-readable medium according to any one of clauses 64 to 78, wherein the non-transitory computer-readable medium also includes computer-executable instructions, which, when executed by the network component, cause the network component to: send a beam configuration associated with the transmission of the uplink SRS for positioning to the target UE.

[0253] Clause 80. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by an uplink relay, cause the uplink relay to: receive one or more uplink wireless data communications from one or more user equipment (UE); relay the one or more uplink data communications to one or more service network components configured to send downlink wireless data communications to the one or more UEs via a backhaul connection; receive a request from a network component to measure an uplink sounding reference signal (SRS) for positioning from a target UE; measure the uplink SRS for positioning from the target UE in accordance with the request; and send a report to the network component including measurement information associated with the measured uplink SRS for positioning.

[0254] Clause 81. The non-transitory computer-readable medium of clause 80, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

[0255] Clause 82. The non-transitory computer-readable medium of any of clauses 80 to 81, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

[0256] Clause 83. The non-transitory computer-readable medium of any one of clauses 80 to 82, wherein the backhaul connection comprises a wireless backhaul connection.

[0257] Clause 84. The non-transitory computer-readable medium of any one of clauses 80 to 83, wherein the backhaul connection comprises a wired backhaul connection.

[0258] Clause 85. An apparatus, comprising: a memory; a transceiver; and a processor, the processor being communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor being configured to perform the method of any one of clauses 1 to 84.

[0259] Clause 86. An apparatus comprising means for performing the method of any one of clauses 1 to 84.

[0260] Clause 87. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions comprising at least one instruction for causing a computer or a processor to perform the method according to any one of clauses 1 to 84.

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

[0262] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the various aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described above in terms of their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

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

[0264] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0265] In one or more example aspects, the function can be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the function can be stored on a computer-readable medium or sent by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server or other remote source using a coaxial cable, an optical fiber cable, a twisted pair, a digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of the medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0266] Although the foregoing disclosure illustrates the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of operating a network component, the method comprising: determining a coarse positioning estimate associated with a target user equipment (UE); determining location information associated with an uplink relay set; as well as selecting a wireless node group for a positioning estimation session for the target UE based on the coarse positioning estimate and the location information associated with the set of uplink relays, the wireless node group including at least one uplink relay, the at least one uplink relay configured to relay uplink wireless data communications from the UE to one or more serving network components, the one or more serving network components configured to send downlink wireless data communications to the one or more UEs; sending, in association with the positioning estimation session, to the at least one uplink relay at least one request to measure an uplink sounding reference signal (SRS) from the target UE for positioning; receiving at least one report including measurement information associated with the uplink SRS used for positioning from the target UE, as measured by the at least one uplink relay; as well as A positioning estimate for the target UE is determined based on the at least one report.

2. The method of claim 1, wherein the network component corresponds to a location management function (LMF).

3. The method of claim 2, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

4. The method of claim 3, wherein the presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from the serving network component of the target UE via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

5. The method according to claim 2, further comprising: A request is sent to a serving network component of the target UE to enable an SRS measurement mode for the at least one uplink relay.

6. The method of claim 5, wherein the request to enable the SRS measurement mode of the at least one uplink relay is sent via NR Positioning Protocol A (NRPPa) signaling or Long Term Evolution Positioning Protocol A (LPPa) signaling.

7. The method of claim 2, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

8. The method of claim 2, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

9. The method of claim 1, wherein the network component corresponds to a serving network component of the target UE.

10. The method of claim 9, wherein the coarse positioning estimate is received at the serving network component from a location management function (LMF).

11. The method of claim 1 , wherein the selecting is based in part on a quantity of network components associated with each uplink relay in the set of uplink relays.

12. The method of claim 11, wherein the selection is weighted to favor selection of uplink relays associated with a higher number of network components.

13. The method according to claim 1, further comprising: A transmission power level of the uplink SRS used for positioning is determined based on location information associated with the wireless node group.

14. The method of claim 1, wherein the at least one uplink relay comprises a single uplink relay.

15. The method of claim 1, wherein the at least one uplink relay comprises a plurality of uplink relays.

16. The method according to claim 1, further comprising: A beam configuration associated with transmission of the uplink SRS for positioning is transmitted to the target UE.

17. A method of operating an uplink relay, the method comprising: receiving one or more uplink wireless data communications from one or more user equipment (UE); relaying the one or more uplink data communications via a backhaul connection to one or more serving network components configured to send downlink wireless data communications to the one or more UEs; receiving a request from a network component to measure an uplink sounding reference signal (SRS) from a target UE for positioning; measuring the uplink SRS for positioning from the target UE according to the request; as well as A report including measurement information associated with the measured uplink SRS used for positioning is sent to the network component.

18. The method of claim 17, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

19. The method of claim 17, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

20. The method of claim 17, wherein the backhaul connection comprises a wireless backhaul connection.

21. The method of claim 17, wherein the backhaul connection comprises a wired backhaul connection.

22. A network component, the network component comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determining a coarse positioning estimate associated with a target user equipment (UE); determining location information associated with an uplink relay set; and selecting a wireless node group for a positioning estimation session for the target UE based on the coarse positioning estimate and the location information associated with the set of uplink relays, the wireless node group including at least one uplink relay, the at least one uplink relay configured to relay uplink wireless data communications from the UE to one or more serving network components, the one or more serving network components configured to send downlink wireless data communications to the one or more UEs; sending, via the at least one transceiver, to the at least one uplink relay in association with the positioning estimation session, at least one request to measure an uplink sounding reference signal (SRS) for positioning from the target UE; receiving, via the at least one transceiver, at least one report including measurement information associated with the uplink SRS for positioning from the target UE, as measured by the at least one uplink relay; as well as A positioning estimate for the target UE is determined based on the at least one report.

23. The network component of claim 22, wherein the network component corresponds to a location management function (LMF).

24. The network component of claim 23, wherein presence information associated with the uplink relay set, the location information associated with the uplink relay set, or both are received at the LMF from a serving network component of the target UE.

25. The network component of claim 23, wherein the at least one report comprises combined information associated with measurement information from a plurality of uplink relays.

26. The network component of claim 23, wherein the at least one report is received from the at least one uplink relay or from a serving network component of the target UE.

27. The network component of claim 22, wherein the network component corresponds to a serving network component of the target UE.

28. An uplink relay, the uplink relay comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, one or more uplink wireless data communications from one or more user equipment (UE); relaying the one or more uplink data communications via a backhaul connection to one or more serving network components configured to send downlink wireless data communications to the one or more UEs; receiving, via the at least one transceiver, from a network component a request to measure an uplink sounding reference signal (SRS) from a target UE for positioning; measuring the uplink SRS for positioning from the target UE according to the request; as well as A report including measurement information associated with the measured uplink SRS used for positioning is sent to the network component via the at least one transceiver.

29. The uplink relay of claim 28, wherein the network component corresponds to a location management function (LMF) or a serving network component of the target UE.

30. The uplink relay of claim 28, wherein the uplink relay is closer to the target UE than a serving network component of the target UE.

Images