Sounding reference signal and positioning reference signal frequency hopping mode

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE) may select a first sounding reference signal (SRS) configuration from a plurality of SRS configurations, each SRS configuration defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop overlaps the contiguous subcarrier frequency of at least one other SRS hop by an amount of overlap, and wherein the amount of overlap of one SRS configuration of the plurality of SRS configurations is different from the amount of overlap of another SRS configuration of the plurality of SRS configurations. The UE may transmit the SRS in a plurality of hops having an amount of overlap according to a first SRS configuration.

Description

Technical Field

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

[0002] 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, internet-enabled wireless services, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, 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.

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), enables higher data speeds, increased connections, and improved 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 Sounding Reference Signals (SRS)), and other technical enhancements compared to previous standards. These enhancements, along with the use of higher frequency bands, advances in PRS procedures and technologies, and high-density deployments of 5G, enable highly accurate positioning based on 5G. Summary of the Invention

[0004] The following presents a simplified summary of one or more aspects disclosed herein. Therefore, the following summary should neither be considered an exhaustive overview of all contemplated aspects nor be considered to identify key or critical elements related to all contemplated aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0005] In one aspect, a wireless communication method performed by a user equipment (UE) includes: selecting a first sounding reference signal (SRS) configuration from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a continuous subcarrier frequency range, wherein the continuous subcarrier frequency range of each of the plurality of SRS hops overlaps with the continuous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmitting SRS in the plurality of hops having the overlap amount according to the first SRS configuration.

[0006] In one aspect, a wireless communication method performed by a network entity includes: selecting a first SRS configuration from a plurality of SRS configurations for use by a UE, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a continuous subcarrier frequency range, wherein the continuous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the continuous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmitting information identifying the first SRS configuration from the plurality of SRS configurations to the UE.

[0007] In one aspect, a UE includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: select a first SRS configuration from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a continuous subcarrier frequency range, wherein the continuous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the continuous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmit SRS in the plurality of hops having the overlap amount according to the first SRS configuration via the at least one transceiver.

[0008] In one aspect, a network entity includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: select a first SRS configuration for use by a UE from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a continuous subcarrier frequency range, wherein the continuous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the continuous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmit information identifying the first SRS configuration from the plurality of SRS configurations to the UE via the at least one transceiver.

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

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

[0011] Figure 1 An example wireless communication system according to aspects of the present disclosure is illustrated.

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

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

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

[0015] Figure 5A 、 Figure 5B and Figure 5C Various sounding reference signal (SRS) configurations used by conventional networks are illustrated.

[0016] Figure 6is a frequency versus time diagram showing the location of SRS frequency allocations during conventional SRS frequency hopping.

[0017] Figure 7 is a frequency versus time diagram 700 illustrating the location of SRS frequency allocations during SRS frequency hopping with frequency overlap in accordance with aspects of the present disclosure.

[0018] Figure 8A and Figure 8B is a frequency versus time diagram showing different SRS configurations with overlap.

[0019] Figure 9A and Figure 9B is a frequency versus time diagram illustrating different SRS configurations with different frequency overlap values ​​according to aspects of the present disclosure.

[0020] Figure 10A and Figure 10B is a frequency versus time diagram illustrating different SRS configurations with different frequency overlap values ​​according to aspects of the present disclosure.

[0021] Figure 11 is a frequency versus time diagram illustrating an example of PRS hopping in accordance with aspects of the present disclosure, wherein a receiving UE opportunistically receives non-PRS signals while in a retuning state.

[0022] Figure 12 is a flow chart of example procedures performed by a UE associated with SRS and positioning reference signal (PRS) frequency hopping patterns according to aspects of the present disclosure.

[0023] Figure 13 is a flow chart of example processes performed by a network entity associated with SRS and PRS frequency hopping patterns according to aspects of the present disclosure. DETAILED DESCRIPTION

[0024] Technologies for wireless communications are disclosed. In one aspect, a user equipment (UE) may determine a first sounding reference signal (SRS) configuration from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop defining a set of time and frequency resources allocated for SRS transmission by the UE and having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein a subcarrier frequency of one SRS hop overlaps a subcarrier frequency of at least one other SRS hop by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations. The UE may transmit the SRS in the plurality of hops having the overlap amount according to the first SRS configuration.

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

[0026] Various aspects generally relate to SRS configurations having SRS hops that overlap with other SRS hops in the frequency domain. Some aspects more specifically relate to mechanisms for providing different SRS hopping configurations with different levels of overlap. In some examples, the amount of overlap may be related to the bandwidth of each SRS hop, e.g., the smaller the SRS hop bandwidth, the less overlap. In some examples, SRS hopping configurations are defined as hierarchies with different SRS hop bandwidths depending on which level of the hierarchy is being used. In these examples, the amount of overlap may be related to the current level of the hierarchy being used. Other aspects address artifacts that may arise from defining overlapping SRS hops—i.e., higher-frequency subcarriers (which may not contain SRS signals at those frequencies) may not be detected. To address this issue, in some examples, SRS configurations with overlap may define additional SRS hops (or multiple SRS hops) to ensure detection of those higher-frequency subcarriers. Still other aspects allow a UE that has retuned its RF circuitry to prepare for reception of PRS hopping that is fully or partially outside the UE's currently active bandwidth part (BWP) to opportunistically receive non-PRS signals when returned.

[0027] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by providing an SRS configuration that supports overlapping SRS hops, multiple SRS measurements (i.e., from multiple SRS hops) can be concatenated to create the equivalent of a higher-bandwidth SRR with better resolution and increased accuracy. Because the amount of overlap is not static but can vary depending on the SRS configuration, the amount of overlap can be tuned to an optimal value for each SRS configuration. In other examples, allowing a UE to opportunistically receive non-PRS signals when it is returned to receive a PRS hop that is not completely within the active BWP allows the UE to receive potentially useful information when retuned, rather than simply waiting to receive the next PRS hop.

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

[0029] 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 voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0030] Furthermore, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that the various actions described herein may be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein may be viewed as being fully embodied within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, when executed, will cause or command an associated processor of a device to perform the functionality described herein. Accordingly, various aspects of the present disclosure may be embodied in a variety of different forms, all of which are contemplated to be within the scope of the claimed subject matter. Furthermore, 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."

[0031] 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 particular radio access technology (RAT). Generally speaking, a UE can be any wireless communication device (e.g., a mobile phone, router, tablet, laptop, consumer asset location device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE can be mobile or stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can 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. Generally speaking, a UE can communicate with a core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and other UEs. Of course, other mechanisms are also possible for the UE to connect to the core network and / or the Internet, such as through a wired access network, a wireless local area network (WLAN) network (eg, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.).

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

[0033] 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 the 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 TRPs may be a serving base station that receives measurement reports from a UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is the point at which a base station transmits and receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0034] In some implementations that support UE positioning, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but may instead transmit a reference signal to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when transmitting a signal to the UE) and / or as a position measurement unit (e.g., when receiving and measuring a signal from the UE).

[0035] An "RF signal" comprises 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 as a "signal" where the context clearly indicates that the term "signal" refers to either a wireless signal or an RF signal.

[0036] Figure 1An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100, which may also be referred to as a wireless wide area network (WWAN), may include various base stations 102 (labeled "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.

[0037] 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)) via backhaul links 122. The base stations 102 may also 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)) via the core network 170. The location servers 172 may be part of the core network 170 or external to the core network 170. The location servers 172 may be integrated with the base stations 102. The UEs 104 may communicate with the location servers 172 directly or indirectly. For example, the UE 104 may communicate with the location servers 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location servers 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.

[0038] Among other functions, the base stations 102 may perform functions related to one or more of: transporting 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 the EPC / 5GC) over a backhaul link 134, which may be wired or wireless.

[0039] Base stations 102 can communicate wirelessly with UEs 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communicating with a base station (e.g., via a frequency resource, such as a carrier frequency, component carrier, carrier, or frequency band) and can 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.) that distinguishes cells operating on the same or different carrier frequencies. In some cases, different cells can 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 can provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" can refer to either or both the logical communication entity and the base station supporting the logical communication entity, depending on the context. Furthermore, since the TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a base station, as long as a carrier frequency can be detected and used for communications within a portion of the geographic coverage area 110.

[0040] While the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a handover area), some areas of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage area 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 service to a restricted group known as a Closed Subscriber Group (CSG).

[0041] The communication link 120 between the base station 102 and the UE 104 may include uplink (also known as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also known as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may utilize 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).

[0042] The wireless communication system 100 may also include a wireless local area network (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 communicating to determine whether a channel is available.

[0043] 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 employ LTE or NR technology and use the same 5 GHz unlicensed spectrum used by the WLAN AP 150. Small cell base stations 102' employing LTE / 5G in the unlicensed spectrum can improve the coverage 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, License Assisted Access (LAA), or MulteFire.

[0044] The wireless communication system 100 may also include a millimeter wave (mmW) base station 180, which can operate at mmW and / or near-mmW frequencies to communicate with UEs 182. Extremely high frequencies (EHF) are part of the RF portion of the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 and 10 mm. Radio waves in this frequency band may be referred to as millimeter waves. Near-mmW frequencies extend down to frequencies of 3 GHz, with wavelengths of 100 mm. Super high frequencies (SHF) frequency bands extend between 3 GHz and 30 GHz and are also referred to as centimeter waves. Communications using mmW / near-mmW radio frequency bands have high path loss and relatively short range. mmW base stations 180 and UEs 182 can utilize beamforming (transmit and / or receive) on mmW communication links 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that, in alternative configurations, one or more base stations 102 may also transmit using mmW or near-mmW frequencies and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0045] Transmit beamforming is a technique used to focus an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts it 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 the receiving device with a faster and stronger RF signal (in terms of data rate). To alter the directionality of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (referred to as a "phased array" or "antenna array"), which forms an RF beam that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are fed to the individual antennas with the correct phase relationship, so that the radio waves from the individual antennas add together in the desired direction to increase radiation, while canceling out in undesired directions to suppress radiation.

[0046] Transmit beams can be quasi-co-located, meaning they appear to have the same parameters to a receiver (e.g., a UE), regardless of whether the network node's own transmit antenna is physically co-located. In NR, four types of quasi-co-location (QCL) relationships exist. Specifically, a given type of QCL relationship means that certain parameters about a second reference RF signal on a second beam can be derived based on information about the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is 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.

[0047] In receive beamforming, a 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 (e.g., increase the gain level of) the RF signals received from that direction. Therefore, when a receiver is said to be beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain in other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) for the RF signals received from that direction.

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

[0049] Note that depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit 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 for receiving downlink reference signals. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, and so on, based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, despite a portion of FR1 exceeding 6 GHz, FR1 is often (and interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often (and interchangeably) referred to as the "millimeter wave" band in documents and articles, despite being distinct from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0051] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0052] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as frequencies that may be less than 6 GHz, may be within FR1, or may 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 frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0053] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells." In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that 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 typically UE-specific, UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," "carrier frequency," etc. may be used interchangeably.

[0054] For example, still referring to Figure 1 In the example, 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 double the data rate (i.e., 40 MHz) compared to the data rate achieved with a single 20 MHz carrier.

[0055] The wireless communication system 100 may also include a UE 164 that may communicate with the macrocell base station 102 via a communication link 120 and / or 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.

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

[0057] In one aspect, sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points, as well as 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., encompassing 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 frequency band shared among various RATs. While various licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded their operation into unlicensed frequency bands, such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology, commonly referred to as "Wi-Fi"). Example systems of this type include various variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and the like.

[0058] Note that although Figure 1 Only two of these UEs are illustrated as SL-UEs (i.e., UE 164 and UE 182), but any of the illustrated UEs could be SL-UEs. Furthermore, while only UE 182 is depicted as capable of beamforming, any of the illustrated UEs (including UE 164) could be capable of beamforming. Where SL-UEs are beamforming capable, they can beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE 104), toward a base station (e.g., base station 102, base station 180, small cell 102′, access point 150), and so on. Thus, in some cases, UE 164 and UE 182 could utilize beamforming via sidelink 160.

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

[0060] 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, and the like, such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS)-Assisted Geo-Augmented Navigation, or the GPS and Geo-Augmented Navigation System (GAGAN). 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.

[0061] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also known as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G cellular network (5GC). This element, in turn, provides access to other elements in the 5G network and ultimately to entities external to the 5G network, such as internet web servers and other user devices. Thus, UE 104 may receive communication signals (e.g., signal 124) from SV 112 instead of, or in addition to, communication signals from terrestrial base station 102.

[0062] The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "side links"). Figure 1 In the example shown in FIG1 , 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 via 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 via the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

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

[0064] 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, each can 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 connect 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).

[0065] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the 5GC 210 can be functionally considered to include control plane functions provided by the access and mobility management function (AMF) 264 and user plane functions provided by the user plane function (UPF) 262, which operate in conjunction to form the 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 of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and 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 intermediate keys established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264's functionality also includes Security Context Management (SCM). The SCM receives keys from the SEAF, which it uses to derive access network-specific keys. The AMF 264's functionality also includes location service management for regulated services, transport of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as the location server 230), transport of location service messages between the NG-RAN 220 and the LMF 270, allocation of Evolved Packet System (EPS) bearer identifiers for interoperability with EPS, and notification of UE 204 mobility events. Furthermore, the AMF 264 supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0066] The UPF 262 functions include serving as an anchor point for intra-RAT / inter-RAT mobility (when applicable), serving 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, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the delivery of location service messages between the UE 204 and a location server (such as the SLP 272) on the user plane.

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

[0068] 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, each can correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functionality as the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 on a control plane (e.g., using interfaces and protocols designed to carry signaling messages rather than voice or data), the SLP 272 may communicate with the UE 204 and external clients (e.g., third-party servers 274) on a user plane (e.g., using protocols designed to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP).

[0069] Yet another optional aspect may include a third-party server 274 that can communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via the AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., a location estimate) of the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party servers 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, each may correspond to a single server.

[0070] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and 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, while 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 can 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 can communicate with one or more UEs 204 over a wireless interface, referred to as a "Uu" interface.

[0071] The functionality of a gNB 222 can be divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DUs) 228, and one or more gNB Radio Units (gNB-RUs) 229. The gNB-CU 226 is a logical node that includes base station functions, including delivery of user data, mobility control, radio access network sharing, positioning, session management, and more, in addition to those functions specifically assigned to the gNB-DU 228. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols for the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers for the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a 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, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0072] The deployment of a communication system, such as a 5G NR system, can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or 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 a converged or disaggregated architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), a NR base station, a 5G NR base station, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as a converged base station (also known as a standalone base station or a single-chip base station) or a disaggregated base station.

[0073] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0074] Base station type operation or network design 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 (such as the network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The 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.

[0075] Figure 2C An example disaggregated base station architecture 250 according to aspects of the present disclosure is illustrated. Disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CUs 226), which may communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via backhaul links, 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, a non-real-time (non-RT) RIC 257 associated with a service management and orchestration (SMO) framework 255, or both. CUs 280 may communicate with one or more distributed units (DUs) 285 (e.g., gNB-DUs 228) via corresponding midhaul links, such as the F1 interface. DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via corresponding fronthaul links. The RUs 287 can communicate with corresponding UEs 204 via one or more radio frequency (RF) access links. In some implementations, a UE 204 can be served by multiple RUs 287 simultaneously.

[0076] Each of the units (i.e., CU 280, DU 285, RU 287, as well as 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 transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface, which may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or transmit signals, or both, to one or more of the other units over the wireless transmission medium.

[0077] In some aspects, the 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 the CU 280. The CU 280 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 implementations, the 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 units may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 280 may be implemented to communicate with the DU 285 for network control and signaling.

[0078] The 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, the DU 285 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on a functional split (such as that defined by the Third Generation Partnership Project (3GPP)). In some aspects, the DU 285 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 285 or with control functions hosted by the CU 280.

[0079] Lower layer functionality may be implemented by one or more RUs 287. In some deployments, a RU 287 controlled by a DU 285 may correspond to a logical node that hosts RF processing functionality or low-PHY layer functionality (such as performing Fast Fourier Transforms (FFTs), Inverse FFTs (iFFTs), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering), or both, based at least in part on a functional split (such as a lower layer functional split). 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 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.

[0080] The SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 255 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 255 can be configured to interact with a cloud computing platform (such as 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 the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, the SMO framework 255 can communicate with 4G RAN hardware (such as the Open eNB (O-eNB) 261) via the O1 interface. Additionally, in some implementations, the SMO framework 255 can 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 .

[0081] The non-RT RIC 257 can be configured to include logic that enables 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 can be coupled to or in communication with the near-RT RIC 259 (e.g., via an A1 interface). The near-RT RIC 259 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., 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.

[0082] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed in the near-RT RIC 259. This information may be utilized by the near-RT RIC 259 and may be received from non-network data sources or from network functions 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 tune RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ AI / ML models to execute corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0083] Figure 3A 、 Figure 3B and Figure 3C 2. The diagram illustrates a method that may be incorporated into a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a 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 thereof. Figure 2A and Figure 2B Several example components (represented by corresponding blocks) within the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as a dedicated network) depicted in the present disclosure are illustrated to support operations as described herein. It should be understood that these components may be implemented in different types of devices with different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0084] 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 transmission, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 can 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.) over a wireless communication medium of interest (e.g., a certain 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 a designated RAT, and conversely, receive and decode the signals 318 and 358 (e.g., messages, indications, information, pilots, etc.), respectively. 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.

[0085] In at least 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 means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmission, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, Dedicated Short Range Communications (DSRC), Wireless Access for Vehicular Environments (WAVE), Near Field Communications (NFC), Ultra-Wideband (UWB), etc.). Short-range wireless transceivers 320 and 360 can be configured in various ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively, according to a designated RAT. Specifically, short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368. As specific examples, short-range wireless transceivers 320 and 360 can be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0086] At least in some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. If satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), and the like. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 may be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as appropriate and, 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.

[0087] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. For another example, 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 with other network entities 306 via one or more wired or wireless core network interfaces.

[0088] A transceiver can be configured to communicate over a wired or wireless link. A transceiver (whether a wired or wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some implementations, a transceiver can be an integrated device (e.g., implementing transmitter circuitry and receiver circuitry in a single device), in some implementations can include separate transmitter circuitry and separate receiver circuitry, or in other implementations can be implemented in other ways. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) can be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, that allow a corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming," as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, that allow a 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.

[0089] 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 referred to as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver can 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) typically involve signaling via a wireless transceiver.

[0090] 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 each include one or more processors 332, 384, and 394 for providing functionality related to, for example, wireless communication, as well as for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for computing, means for receiving, means for transmitting, means for indicating, and the like. 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 circuits, or various combinations thereof.

[0091] UE 302, base station 304, and network entity 306, respectively, include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Memories 340, 386, and 396 may thus provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include SRS / PRS modules 342, 388, and 398, respectively. SRS / PRS modules 342, 388, and 398 may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, and that, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, the SRS / PRS modules 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 SRS / PRS modules 342, 388, and 398 can be memory modules stored in the memories 340, 386, and 396, respectively, which, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the SRS / PRS module 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 3BPossible locations for the SRS / PRS module 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 the SRS / PRS module 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0092] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide means for sensing or detecting movement and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receiver 330. By way of example, sensors 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. Furthermore, sensors 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensors 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate a position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0093] In addition, the UE 302 includes a user interface 346 that provides means for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the 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.

[0094] Referring in more detail to the one or more processors 384, 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 the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the 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 (ciphering, deciphering, 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), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

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

[0096] At UE 302, receiver 312 receives the signal via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on this information to recover any spatial streams destined for UE 302. If there are multiple spatial streams destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by 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 transmitted by 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.

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

[0098] Similar to the functionality described in conjunction with downlink transmissions 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 (ciphering, deciphering, 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.

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

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

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

[0102] For convenience, UE 302, base station 304 and / or network entity 306 Figure 3A 、 Figure 3B and Figure 3C 1 is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, Figures 3A to 3C Various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. For another example, in Figure 3B In certain cases, particular implementations 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.

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

[0104] 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 3C The components of the present invention 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). Each circuit may utilize and / or incorporate at least one memory component to store information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 through 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 through 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). Furthermore, some or all of the functionality represented by blocks 390 through 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 may be described herein as being performed "by a UE," "by a base station," "by a network entity," and the like. However, it should be understood that such operations, actions and / or functions may actually be performed by a specific component or combination of components of the UE 302, base station 304, network entity 306, etc., such as one or more components such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, SRS / PRS components 342, 388 and 398, etc.

[0105] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may operate independently of 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).

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

[0107] 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, often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Generally speaking, modulation symbols are transmitted in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kilohertz (kHz), while the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, 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.

[0108] LTE supports a single parameter set (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR supports multiple parameter sets (µ). For example, subcarrier spacings of 15 kHz (µ=0), 30 kHz (µ=1), 60 kHz (µ=2), 120 kHz (µ=3), and 240 kHz (µ=4) or larger may be available. In each subcarrier spacing, there are 14 symbols per slot. For a 15 kHz SCS (µ=0), there is one slot per subframe, 10 slots per frame, a slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (µs), and a maximum nominal system bandwidth (in MHz) of 50 with a 4K FFT size. For a 30 kHz SCS (µ=1), there are two slots per subframe, 20 slots per frame, a slot duration of 0.5 ms, a symbol duration of 33.3 µs, and a maximum nominal system bandwidth (in MHz) of 100 with a 4K FFT size. 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.

[0109] exist Figure 4 In the example, a 15 kHz parameter set is used. Therefore, in the time domain, a 10 ms frame is divided into 10 equally sized subframes, each 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.

[0110] A resource grid can be used to represent a time slot, each of which includes one or more time-concurrent resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple 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 100 Mbps, for a normal cyclic prefix, a PRB 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, a PRB 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.

[0111] 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 (SSBs), and sounding reference signals (SRS), 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.

[0112] On the one hand, Figure 4 The reference signals carried by the REs marked with an "R" in the figure may be SRSs. The SRSs transmitted 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 effects of scattering, attenuation, and power loss over distance. Systems use SRSs for resource scheduling, link adaptation, massive MIMO, beam management, and more.

[0113] Figure 5A 、 Figure 5B and Figure 5C Various SRS configurations used by conventional networks are illustrated. Figures 5A to 5C Each of the OFDM symbols illustrates a portion of an example frame structure—that is, in this example, the frequency allocation of the SRS occupying OFDM symbols 11 and / or 12. The set of REs used for SRS transmission is called an "SRS resource" and can be identified by the parameter "SRS-ResourceId." A set of resource elements can span multiple PRBs in the frequency domain and 'N' (e.g., one or more) consecutive symbols within a 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 group of SRS resources used for transmission of an SRS signal and is identified by an SRS resource set ID ("SRS-ResourceSetId").

[0114] The SRS resource within a given PRB is transmitted with 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 one 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 4 In the example of FIG, the illustrated SRS is comb-tooth-4 spanning four symbols. That is, the position of the shaded SRS RE indicates the SRS resource configuration of comb-tooth-4.

[0115] Currently, an SRS resource with a comb size of Comb-2, Comb-4, or Comb-8 may 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 the example of FIG5); 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}.

[0116] Generally speaking, as mentioned above, the UE transmits 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 can 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 the two types of SRS, the former may be referred to herein as "SRS for communication" and / or the latter may be referred to as "SRS for positioning" or "positioning SRS."

[0117] The SRS frequency resource configuration may vary depending on whether frequency hopping is enabled or disabled. A portion of the SRS configuration is shown below: :

[0119] freqDomainPositionINTEGER (0..67),

[0120] freqDomainShiftINTEGER (0..268),

[0121] freqHoppingSEQUENCE {

[0122] c-SRSINTEGER (0..63),

[0123] b-SRSINTEGER (0..3),

[0124] b-hopINTEGER (0..3)

[0125] }, :

[0127] If the freqHopping field is configured, the c-SRS field defines the parameter C SRS , field b-SRS defines parameter B SRS , and the field b-hop defines the parameter b hop The frequency hopping of the sounding reference signal is determined by the parameter ∈ {0,1,2,3}, which is given by the field b-hop contained in the high-level parameter freqHopping (if configured), otherwise .if , enable frequency hopping, otherwise if , then frequency hopping is disabled. Parameter C SRS Identifies the row of the SRS frequency hopping parameter table, and parameter B SRS Identifies the set of columns for this table. A portion of an example table of SRS frequency hopping parameters is shown below:

[0128]

[0129] Parameter m SRS，b Specifies the number of PRBs used for SRS transmission per hop; the next hop will use another m SRS,b PRB is used to send SRS. Parameter b hop Defines the number of allowed transitions, and parameter B SRS Define the m covered by each jump SRS,b Which part of the PRB.

[0130] Frequency domain starting position It is defined by the following formula:

[0131]

[0132] in is the frequency position index, and where

[0133] ,and

[0134]

[0135] if ,but The reference point is subcarrier 0 in common resource block 0, otherwise the reference point is the lowest subcarrier of the BWP. The length of the SRS sequence is given by:

[0136]

[0137] Number of sent comb teeth Contained in the high-level parameter transmissionComb. Frequency domain shift value Adjusts the SRS allocation relative to the reference point grid and is contained in the higher layer parameter freqDomainShift in the SRS-Resource IE or SRS-PosResource IE. Send comb offset Contained in the higher-layer parameter transmissionComb in the SRS-Resource IE or SRS-PosResource IE.

[0138] Frequency domain starting position It is defined by the following formula:

[0139]

[0140] in The number of overlapping tones between two adjacent frequency hops.

[0141] Figure 6 is a frequency versus time diagram 600 illustrating the location of SRS frequency allocations during conventional SRS frequency hopping. Figure 6 There are five SRS hops in Figure 6 They are labeled 1 to 5. None of the five SRS hops overlap in the frequency domain, and together they cover the entire UL bandwidth 602 of the UE.

[0142] Figure 7700 is a frequency versus time diagram illustrating the location of SRS frequency allocations during SRS frequency hopping with frequency overlap according to aspects of the present disclosure. Because the maximum number of PRBs occupied by SRS per hop is typically a limitation of UE hardware, it is typically not possible to create frequency overlap by increasing the number of PRBs used for each hop. Instead, frequency overlap is created by changing the set of sub-frequencies on which each SRS hop is located—for example, by shifting the SRS hop downward in frequency. Figure 7 In Figure 6 Compared to their positions in , SRS hop 4 is shifted downward by a certain offset (e.g., by a certain number of PRBs to create a fixed frequency overlap), and similarly, Figure 6 Compared to the position in , SRS hop 2 is shifted down by two offsets, SRS hop 5 is shifted down by three offsets, and SRS hop 3 is shifted down by four offsets.

[0143] While creating SRS hops that overlap by a fixed amount in the frequency domain allows their results to be concatenated together to produce a higher accuracy position estimate or sensing operation, there are some disadvantages. For example, as a result of this downward shift, the top portion of the UL bandwidth 602 is no longer covered by any SRS hop. Figure 8A and Figure 8B Another disadvantage of using a fixed amount of overlap in the frequency domain is illustrated in .

[0144] Figure 8A and Figure 8B is a frequency versus time diagram showing different SRS configurations with overlap. Figure 8A In , there are three SRS hops with 8 PRBs each, and Figure 8B There are six SRS hops with 4 PRBs each. Figure 8A and Figure 8B If the hops in do not overlap, the UE will detect the same number of subcarriers whether it uses three hops with 8 PRBs or six hops with 4 PRBs. Figure 8A An example configuration is shown in which three SRS hops with 8 PRBs overlap each other by 3 PRBs. However, if six SRS hops with 4 PRBs overlap each other by 3 PRBs, the total number of detected subcarriers is significantly reduced, leaving undetected frequencies in the upper part of the UL bandwidth. The same problem can occur even if the overlap size is relatively small but the number of SRS hops is relatively large. For example, when there are 30 hops with 8 PRBs each, even overlapping only two PRBs can reduce the bandwidth detected by 29*2=58 PRBs.

[0145] To address these drawbacks, the present disclosure presents techniques for improved SRS (and PRS) frequency hopping patterns with frequency overlap. In some aspects, the amount of frequency overlap varies based on the SRS configuration, e.g., changes according to how many hops are configured or the bandwidth per hop. In some aspects, additional hops are generated to cover any frequencies that would otherwise not be detected due to the implementation of the overlap.

[0146] Figure 9A and Figure 9B are frequency-versus-time plots showing different SRS configurations with different frequency overlap values according to aspects of the present disclosure. Figure 9A Illustrates an example SRS configuration with three hops each having 8 PRBs, where each hop overlaps 2 PRBs with another hop. Figure 9B Illustrates an example SRS configuration with six hops each having 4 PRBs, but in this configuration, each hop only overlaps 1 PRB with another hop. These illustrations show the following key point: Instead of defining a fixed overlap for all SRS configurations, the size of the overlap can vary from one SRS configuration to another.

[0147] In some aspects, a fixed value is replaced by a set of values or other sets of values such as etc. In a specific implementation, the value of index b corresponds to the value of When the value of increases, the value of decreases. It is recognized that when increases, the value of decreases, and thus the size of the overlap should also decrease. This is represented by the following table:

[0148]

[0149] In another specific implementation, the value of index b corresponds to the value of When the value of increases, the value of decreases. It is recognized that when decreases, the size of the overlap should also decrease. This is represented by the following table:

[0150]

[0151] or by these conditions: If <m1, then b = 0; if m1 ≤ <m2, then b = 1; if m2 ≤ <m3, then b = 2; if m3 ≤ <m4, then b = 3, where m1 to m4 define For example, in one embodiment, for <16 PRBs, the overlap can only be 1, but for For larger values ​​of m1, the overlap may be greater than 1. In some aspects, each UE may be configured with multiple thresholds, e.g., m1 to m4. In some aspects, the thresholds configured for one UE may differ from the thresholds configured for another UE, e.g., based on the UL bandwidth supported by the UE. This configuration may be received by the serving gNB.

[0152] In some aspects, the frequency domain starting position It is defined by the following formula:

[0153]

[0154] It takes into account the size of the overlap, as given by defined.

[0155] Figure 10A and Figure 10B is a frequency versus time diagram illustrating different SRS configurations with different frequency overlap values ​​according to aspects of the present disclosure. Figure 10A An SRS configuration with four SRS hops (labeled 1 to 4, with no overlap) is shown. Figure 10B An SRS configuration with four SRS hops (labeled 1' to 4', with some overlap) is shown. Figure 10B In the example shown, the configuration also includes or generates an additional SRS hop 5 that covers the higher frequency subcarriers that the overlapping SRS hops no longer cover due to their downward frequency shift.

[0156] Despite Figure 10B In the example shown, the additional SRS hop 5 is the same size as SRS hops 1 to 4, but in some aspects, the size of the additional SRS hop can be different from the size of the other hops; for example, the additional SRS hop only needs to be just large enough to cover the subcarriers that were not detected, and can be smaller than the other hops. Similarly, if the bandwidth of the undetected subcarriers is larger than the maximum size of the SRS hop, two or more additional hops can be included or generated to cover the subcarriers that were not detected.

[0157] In some aspects, a location server, location management function (LMF), or equivalent node may request a specific In some aspects, the serving gNB may report back the allocated , and the location server can report those values ​​to neighboring gNBs.

[0158] In some aspects, overlapping SRS frequency hopping may be supported for only a subset of the legacy hopping scenarios. For example, for FR1, for 20 MHz devices, an option is supported where 48 PRBs are used for 30 kHz, 24 PRBs are used for 15 kHz, with up to 5 hops, and for FR2, for 100 MHz devices, an option is supported where 64 PRBs are used for 120 kHz (and up to 4 hops). These examples are illustrative and non-limiting.

[0159] In some aspects, the maximum duration span of a hop may be limited to less than a threshold. This limitation will avoid undesirable scenarios, such as 30 hops spanning dozens of time slots. In some aspects, this limitation may be specified as "SRS hopping is supported only for those rows where the total number of required hops is less than a threshold (e.g., 8 hops) or the span of the SRS hopping pattern does not exceed X time slots." In some aspects, requirements related to SRS hopping may only apply when the total number of hops does not exceed the threshold or the span of the hopping pattern does not exceed X time slots.

[0160] The same concepts described herein can also be applied to the downlink, such as PRS hopping. Furthermore, if the UE is expected to perform a retuning in a specific time period in order to measure PRS signals outside its active bandwidth part (BWP), in some aspects, the UE can opportunistically receive Physical Downlink Shared Channel (PDSCH) signals, control signals, or Channel State Information Reference Signals (CSI-RS) while in the retuning state, provided that these other signals do not overlap with the PRS signals. Figure 11 An example of this operation is shown in .

[0161] Figure 11 is a frequency versus time diagram illustrating an example of PRS hopping according to aspects of the present disclosure, wherein a receiving UE opportunistically receives non-PRS signals while in a retuning state. Figure 11 In the example shown, the UE is initially in its active BWP ( Figure 11 When tuned to BW1, the UE receives the first DL PRS hop (at Figure 11 (labeled as PRS Hop 1 in the figure). The UE then re-tunes to BW2 in anticipation of receiving PRS Hop 2. However, while waiting for the arrival of PRS Hop 2, the UE opportunistically receives CSI-RS on some of the subcarriers within BW2. After receiving PRS Hop 2, the UE re-tunes to BW3 in anticipation of receiving PRS Hop 3. However, while waiting for the arrival of PRS Hop 3, the UE opportunistically receives PDSCH on some of the subcarriers within BW3.

[0162] Figure 12is a flow chart of an example process 1200 associated with SRS and PRS frequency hopping patterns according to aspects of the present disclosure. In some implementations, Figure 12 One or more process blocks of may be performed by a user equipment (UE) (eg, UE 104). In some implementations, Figure 12 One or more process blocks of may be performed by another device or a group of devices separate from or including the UE. Additionally or alternatively, Figure 12 The one or more process blocks of process 1200 may be performed by one or more components of UE 302, such as processor 332, memory 340, WWAN transceiver 310, short-range wireless transceiver 320, satellite signal receiver 330, sensor 344, user interface 346, and SRS / PRS module 342, any or all of which may be means for performing the operations of process 1200.

[0163] like Figure 12 As shown, process 1200 may include, at block 1210, selecting a first sounding reference signal (SRS) configuration from a plurality of sounding reference signal (SRS) configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each of the plurality of SRS hops overlaps a contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one of the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations. Means for performing the operations of block 1210 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may determine the first SRS configuration from the plurality of SRS configurations by selecting from a set of SRS configurations stored in memory 340 using processor 332 or receiving an indication of the selection via receiver 312.

[0164] like Figure 12 As further shown in FIG1 , process 1200 may include, at block 1220, transmitting the SRS in a plurality of hops having an overlapping amount according to the first SRS configuration. Means for performing the operations of block 1220 may include processor 332, memory 340, or WWAN transceiver 310 of UE 302. For example, UE 302 may use transmitter 314 to transmit the SRS in a plurality of hops.

[0165] In some aspects, determining the first SRS configuration from the plurality of SRS configurations includes: receiving the plurality of SRS configurations from a network entity; and selecting one of the plurality of SRS configurations as the first SRS configuration.

[0166] In some aspects, determining the first SRS configuration from the plurality of SRS configurations includes: receiving the plurality of SRS configurations from a network entity; and receiving information identifying one of the plurality of SRS configurations as the first SRS configuration.

[0167] In some aspects, the amount of overlap for each SRS configuration is a function of the hop bandwidth of the SRS configuration.

[0168] In some aspects, each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

[0169] In some aspects, the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0170] In some aspects, the first SRS configuration further includes at least one additional SRS hop to cover subcarriers not covered by the multiple (overlapping) SRS hops.

[0171] In some aspects, process 1200 includes receiving a plurality of PRS hops, each PRS hop occupying a different contiguous subcarrier frequency range and requiring the UE to re-tune its radio frequency receiver away from an active bandwidth part (BWP) to include the contiguous subcarrier frequency range of the PRS hop; and receiving a non-PRS signal while the radio frequency receiver is tuned away from the active BWP.

[0172] Process 1200 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Figure 12 Example blocks of process 1200 are shown, but in some implementations, process 1200 may include Figure 12 The blocks depicted in the process 1200 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of the process 1200 may be performed in parallel.

[0173] Figure 13 is a flow chart of an example process 1300 associated with SRS and PRS frequency hopping patterns according to aspects of the present disclosure. In some implementations, Figure 13 One or more process blocks of may be performed by a network entity (eg, location server 172, base station 102). In some implementations, Figure 13One or more process blocks of may be performed by another device or a group of devices separate from or including the network entity. Additionally or alternatively, Figure 13 One or more process blocks may be performed by one or more components of the network entity 306, such as the processor 394, the memory 396, the network transceiver 390, and the SRS / PRS module 398, any or all of which may be means for performing the operations of process 1300.

[0174] like Figure 13 As shown, process 1300 may include, at block 1310, selecting a first SRS configuration for use by a UE from a plurality of SRS configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations. Means for performing the operations of block 1310 may include the processor 394, the memory 396, or the network transceiver 390 of the network entity 306. For example, the network entity 306 may determine the plurality of SRS configurations using the processor 394 and the memory 396.

[0175] like Figure 13 As further shown in FIG, process 1300 may include, at block 1320, transmitting information identifying a first SRS configuration from a plurality of SRS configurations to the UE. Means for performing the operations of block 1320 may include the processor 394, the memory 396, or the network transceiver 390 of the network entity 306. For example, the network entity 306 may use the network transceiver 390 to transmit the information identifying the first SRS configuration from the plurality of SRS configurations.

[0176] In some aspects, the amount of overlap for each SRS configuration is a function of the hop bandwidth of the corresponding SRS configuration.

[0177] In some aspects, each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

[0178] In some aspects, the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0179] In some aspects, the first SRS configuration further includes at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

[0180] In some aspects, process 1300 includes requesting information from a base station mapping an amount of overlap to be used for overlapping SRS hops in each of a plurality of SRS configurations; receiving the information from the base station; and providing the information to a neighboring base station.

[0181] In some aspects, each SRS configuration of the plurality of SRS configurations defines a maximum allowed time duration for a number of SRS hops defined in the respective SRS configuration or for all SRS configurations.

[0182] Process 1300 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein. Figure 13 Example blocks of process 1300 are shown, but in some implementations, process 1300 may include Figure 13 1300. In some embodiments, the process 1300 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1300 may be performed in parallel.

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

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

[0185] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: selecting a first sounding reference signal (SRS) configuration from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each of the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmitting SRS in the plurality of hops having an overlap amount according to the first SRS configuration.

[0186] Clause 2. The method of clause 1, wherein determining the first SRS configuration from the plurality of SRS configurations comprises: receiving the plurality of SRS configurations from a network entity; and selecting one of the plurality of SRS configurations as the first SRS configuration.

[0187] Clause 3. A method according to any one of clauses 1 to 2, wherein determining the first SRS configuration from the multiple SRS configurations comprises: receiving the multiple SRS configurations from a network entity; and receiving information identifying one SRS configuration among the multiple SRS configurations as the first SRS configuration.

[0188] Clause 4. The method of any of clauses 1 to 3, wherein the amount of overlap of each SRS configuration varies with the hop bandwidth of the SRS configuration.

[0189] Clause 5. The method of any of clauses 1 to 4, wherein each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

[0190] Clause 6. The method of any of clauses 1 to 5, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0191] Clause 7. The method of any of clauses 1 to 6, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

[0192] Clause 8. A method according to any of clauses 1 to 7, the method further comprising: receiving a plurality of PRS hops, each PRS hop occupying a different contiguous subcarrier frequency range and requiring the UE to re-tune its RF receiver away from an active bandwidth part (BWP) to include the contiguous subcarrier frequency range of the PRS hop; and receiving a non-PRS signal while the RF receiver is tuned away from the active BWP.

[0193] Clause 9. A wireless communication method performed by a base station, the method comprising: selecting a first sounding reference signal (SRS) configuration for use by a user equipment (UE) from a plurality of SRS configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmitting to the UE information identifying the first SRS configuration from the plurality of SRS configurations.

[0194] Clause 10. The method of clause 9, wherein the amount of overlap of each SRS configuration varies with the hop bandwidth of the corresponding SRS configuration.

[0195] Clause 11. The method of any of clauses 9 to 10, wherein each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

[0196] Clause 12. A method as described in any of clauses 9 to 11, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0197] Clause 13. The method of any of clauses 9 to 12, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

[0198] Clause 14. A method according to any one of clauses 9 to 13, the method further comprising: requesting from a base station information mapping an amount of overlap of SRS hops to be used for overlapping each of a plurality of SRS configurations; receiving the information from the base station; and providing the information to a neighboring base station.

[0199] Clause 15. The method of any of clauses 9 to 14, wherein each SRS configuration of the plurality of SRS configurations defines a maximum allowed time duration for the plurality of SRS hops defined in the respective SRS configuration or for all SRS configurations.

[0200] Clause 16. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: select a first sounding reference signal (SRS) configuration from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each of the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; and transmit the SRS in the plurality of hops having the overlap amount according to the first SRS configuration via the at least one transceiver.

[0201] Clause 17. A UE according to clause 16, wherein, to determine the first SRS configuration from the multiple SRS configurations, the at least one processor is configured to: receive the multiple SRS configurations from a network entity; and select one SRS configuration from the multiple SRS configurations as the first SRS configuration.

[0202] Clause 18. A UE according to any one of clauses 16 to 17, wherein, in order to determine the first SRS configuration from the multiple SRS configurations, the at least one processor is configured to: receive the multiple SRS configurations from a network entity; and receive information identifying one SRS configuration among the multiple SRS configurations as the first SRS configuration.

[0203] Clause 19. The UE of any of clauses 16 to 18, wherein the amount of overlap of each SRS configuration varies with the hop bandwidth of the SRS configuration.

[0204] Clause 20. A UE as set forth in any of clauses 16 to 19, wherein each SRS configuration defines a frequency hopping layer and a level of the frequency hopping layer, and wherein the amount of overlap varies with the level of the frequency hopping layer.

[0205] Clause 21. A UE as set forth in any of clauses 16 to 20, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0206] Clause 22. A UE as set forth in any of clauses 16 to 21, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of (overlapping) SRS hops.

[0207] Clause 23. A UE according to any of clauses 16 to 22, wherein the at least one processor is further configured to: receive, via the at least one transceiver, a plurality of PRS hops, each PRS hop occupying a different contiguous subcarrier frequency range and requiring the UE to re-tune its radio frequency receiver away from an active bandwidth part (BWP) to include the contiguous subcarrier frequency range of the PRS hop; and receive, via the at least one transceiver, a non-PRS signal when the radio frequency receiver is tuned away from the active BWP.

[0208] Clause 24. A network entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: select a first sounding reference signal (SRS) configuration for use by a user equipment (UE) from a plurality of SRS configurations, each of the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each of the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other of the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one of the plurality of SRS configurations is different from the overlap amount of another of the plurality of SRS configurations; and transmit, via the at least one transceiver, to the UE, information identifying the first SRS configuration from the plurality of SRS configurations.

[0209] Clause 25. The network entity of Clause 24, wherein the amount of overlap of each SRS configuration varies with the hop bandwidth of the corresponding SRS configuration.

[0210] Clause 26. The network entity of any of clauses 24 to 25, wherein each SRS configuration defines a frequency hopping hierarchy and a level of the frequency hopping hierarchy, and wherein the amount of overlap varies with the level of the frequency hopping hierarchy.

[0211] Clause 27. A network entity as set forth in any of clauses 24 to 26, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or contiguous subcarriers.

[0212] Clause 28. A network entity as set forth in any of clauses 24 to 27, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

[0213] Clause 29. A network entity according to any one of clauses 24 to 28, wherein the at least one processor is further configured to: request information from a base station mapping an amount of overlap of SRS hops to be used for overlapping each of a plurality of SRS configurations; receive the information from the base station via the at least one transceiver; and provide the information to a neighboring base station.

[0214] Clause 30. A network entity as recited in any of clauses 24 to 29, wherein each of the plurality of SRS configurations defines a maximum allowed time duration for the plurality of SRS hops defined in the respective SRS configuration or for all SRS configurations.

[0215] Clause 31. An apparatus comprising: a memory; a transceiver; and a processor communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor configured to perform the method of any one of clauses 1 to 15.

[0216] Clause 32. An apparatus comprising means for performing the method of any one of clauses 1 to 15.

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

[0218] Those skilled in the art will appreciate that information and signals can 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 voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0219] In addition, it will be understood by those skilled in the art that the various illustrative 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 illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as resulting in a departure from the scope of this disclosure.

[0220] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using 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 the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A 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.

[0221] The methods, sequences, and / or algorithms described in conjunction with the various aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, 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 the processor such that the processor can read information from and write information to the storage medium. In an alternative embodiment, the storage medium may be integral to the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). In an alternative embodiment, the processor and storage medium may reside in the user terminal as discrete components.

[0222] In one or more exemplary aspects, the described functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A storage medium 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, magnetic disk storage 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 instructions or data structures and that can be accessed by a computer. Furthermore, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of 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. 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.

[0223] Although the foregoing disclosure illustrates 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. Furthermore, although elements of the present disclosure may be described or claimed in the singular, plural forms are also contemplated unless expressly stated to be limited to the singular.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: selecting a first sounding reference signal (SRS) configuration from a plurality of sounding reference signal (SRS) configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; as well as SRSs are sent in a plurality of hops with an overlapping amount according to the first SRS configuration.

2. The method of claim 1 , wherein determining the first SRS configuration from the plurality of SRS configurations comprises: receiving the plurality of SRS configurations from a network entity; And selecting one SRS configuration from the multiple SRS configurations as the first SRS configuration.

3. The method of claim 1 , wherein determining the first SRS configuration from the plurality of SRS configurations comprises: receiving the plurality of SRS configurations from a network entity; and receiving information identifying one of the plurality of SRS configurations as the first SRS configuration. 4 . The method of claim 1 , wherein the overlap amount of each SRS configuration varies with the hop bandwidth of the SRS configuration. 5 . The method of claim 1 , wherein each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level. The method of claim 1 , wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or consecutive subcarriers. 7 . The method of claim 1 , wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

8. The method according to claim 1, further comprising: receiving a plurality of PRS hops, each PRS hop occupying a different contiguous subcarrier frequency range and requiring the UE to re-tune its radio frequency receiver away from an active bandwidth part (BWP) to include the contiguous subcarrier frequency range of the PRS hop; as well as A non-PRS signal is received while the RF receiver is tuned away from the active BWP.

9. A method of wireless communication performed by a network entity, the method comprising: selecting a first sounding reference signal (SRS) configuration for use by a user equipment (UE) from a plurality of sounding reference signal (SRS) configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; as well as Information identifying the first SRS configuration from among the plurality of SRS configurations is transmitted to the UE.

10. The method of claim 9, wherein the amount of overlap of each SRS configuration varies with the hop bandwidth of the SRS configuration.

11. The method of claim 9, wherein each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

12. The method of claim 9, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or consecutive subcarriers. 13 . The method of claim 9 , wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

14. The method according to claim 9, further comprising: requesting, from a base station, information mapping an overlap amount to be used for overlapping SRS hops in each of a plurality of SRS configurations; receiving the information from the base station; as well as The information is provided to neighboring base stations.

15. The method of claim 9, wherein each of the plurality of SRS configurations defines a maximum allowed time duration for the plurality of SRS hops defined in the SRS configuration or for all SRS configurations.

16. A user equipment (UE), comprising: Memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: selecting a first sounding reference signal (SRS) configuration from a plurality of sounding reference signal (SRS) configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; as well as SRS is transmitted in a plurality of hops with an overlapping amount according to the first SRS configuration via the at least one transceiver.

17. The UE of claim 16, wherein, in order to determine the first SRS configuration from the multiple SRS configurations, the at least one processor is configured to: receive the multiple SRS configurations from a network entity; and select one SRS configuration from the multiple SRS configurations as the first SRS configuration.

18. The UE of claim 16, wherein, in order to determine the first SRS configuration from the multiple SRS configurations, the at least one processor is configured to: receive the multiple SRS configurations from a network entity; and receive information identifying one SRS configuration among the multiple SRS configurations as the first SRS configuration.

19. The UE of claim 16, wherein the overlap amount of each SRS configuration varies with the hop bandwidth of the SRS configuration.

20. The UE of claim 16, wherein each SRS configuration defines a hopping level and a level of the hopping level, and wherein the amount of overlap varies with the level of the hopping level.

21. The UE of claim 16, wherein the overlap amount is defined in terms of physical resource blocks (PRBs) or consecutive subcarriers.

22. The UE of claim 16, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

23. The UE of claim 16, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a plurality of PRS hops, each PRS hop occupying a different contiguous subcarrier frequency range and requiring the UE to re-tune its radio frequency receiver away from an active bandwidth part (BWP) to include the contiguous subcarrier frequency range of the PRS hop; and A non-PRS signal is received via the at least one transceiver while the radio frequency receiver is tuned away from the active BWP.

24. A network entity, comprising: Memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: selecting a first sounding reference signal (SRS) configuration for use by a user equipment (UE) from a plurality of sounding reference signal (SRS) configurations, each SRS configuration in the plurality of SRS configurations defining a plurality of SRS hops separated in time, each SRS hop comprising a set of time and frequency resources allocated for SRS transmission by the UE and each SRS hop having a hop bandwidth occupying a contiguous subcarrier frequency range, wherein the contiguous subcarrier frequency range of each SRS hop in the plurality of SRS hops overlaps with the contiguous subcarrier frequency range of at least one other SRS hop in the plurality of SRS hops by an overlap amount, and wherein the overlap amount of one SRS configuration in the plurality of SRS configurations is different from the overlap amount of another SRS configuration in the plurality of SRS configurations; as well as Information identifying the first SRS configuration from among the plurality of SRS configurations is transmitted to the UE via the at least one transceiver.

25. The network entity of claim 24, wherein the overlap amount of each SRS configuration varies with the hop bandwidth of the SRS configuration.

26. The network entity of claim 24, wherein each SRS configuration defines a hopping hierarchy and a level of the hopping hierarchy, and wherein the amount of overlap varies with the level of the hopping hierarchy.

27. The network entity of claim 24, wherein the amount of overlap is defined in terms of physical resource blocks (PRBs) or consecutive subcarriers.

28. The network entity of claim 24, wherein the first SRS configuration further comprises at least one additional SRS hop to cover subcarriers not covered by the plurality of SRS hops.

29. The network entity of claim 24, wherein the at least one processor is further configured to: requesting, from a base station, information mapping an overlap amount to be used for overlapping SRS hops in each of a plurality of SRS configurations; receiving the information from the base station via the at least one transceiver; as well as The information is provided to neighboring base stations.

30. The network entity of claim 24, wherein each of the plurality of SRS configurations defines a maximum allowed time duration for the plurality of SRS hops defined in the SRS configuration or for all SRS configurations.

Images