Sounding reference signal (SRS) cyclic shift frequency hopping

By introducing SRS cyclic shift frequency hopping parameters into the 5G wireless communication system, the SRS interference problem in multi-TRP scenarios is solved, the accuracy of channel state information measurement and UE positioning is improved, and the system performance is enhanced.

CN119032549APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380033805.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-19
Filing Date
2023-03-07
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

Existing 5G wireless communication systems suffer from sounding reference signal (SRS) interference in high-frequency bands, especially in multi-TRP scenarios, which affects positioning accuracy and system performance.

Method used

By introducing SRS cyclic shift frequency hopping parameters, and configuring SRS resources and sending cyclic shift frequency hopping parameters, SRS interference between UEs can be reduced, thereby improving channel quality measurement and positioning accuracy.

Benefits of technology

It effectively reduces interference between SRS, improves the accuracy of channel state information measurement and UE positioning accuracy, and enhances the overall performance of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032549A_ABST
    Figure CN119032549A_ABST
Patent Text Reader

Abstract

Techniques for wireless communication are disclosed. In an aspect, a user equipment (UE) receives a sounding reference signal (SRS) configuration, the SRS configuration including one or more parameters defining SRS resources; receiving a cyclic shift frequency hopping parameter for SRS (Sounding Reference Signal) transmission; and transmitting an SRS on the SRS resource, the SRS being configured according to at least the cyclic shift frequency hopping parameter.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally 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, wireless service with Internet capabilities, and fourth generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

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

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

[0005] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: receiving a sounding reference signal (SRS) configuration, the SRS configuration including one or more parameters defining an SRS resource; receiving a cyclic shift hopping parameter for SRS transmission; and transmitting the SRS on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.

[0006] On the one hand, a method of wireless communication performed by a network entity includes: sending a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration including one or more parameters defining an SRS resource; sending a cyclic shift hopping parameter for SRS transmission from the UE to the UE; and receiving an SRS from the UE on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.

[0007] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a sounding reference signal (SRS) configuration via the at least one transceiver, the SRS configuration including one or more parameters defining an SRS resource; receive a cyclic shift hopping parameter for SRS transmission via the at least one transceiver; and transmit the SRS on the SRS resource via the at least one transceiver, the SRS being configured based on at least the cyclic shift hopping parameter.

[0008] In one aspect, a network entity includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a sounding reference signal (SRS) configuration to a user equipment (UE) via the at least one transceiver, the SRS configuration including one or more parameters defining an SRS resource; send a cyclic shift hopping parameter for SRS transmission from the UE to the UE via the at least one transceiver; and receive an SRS from the UE on the SRS resource via the at least one transceiver, the SRS being configured based on at least the cyclic shift hopping parameter.

[0009] In one aspect, a user equipment (UE) includes means for receiving a sounding reference signal (SRS) configuration, the SRS configuration including one or more parameters defining an SRS resource; means for receiving a cyclic shift hopping parameter for SRS transmission; and means for transmitting the SRS on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.

[0010] In one aspect, a network entity includes means for sending a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration including one or more parameters defining an SRS resource; means for sending cyclic shift hopping parameters to the UE for SRS transmission from the UE; and means for receiving an SRS from the UE on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameters.

[0011] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining an SRS resource; receive cyclic shift hopping parameters for SRS transmission; and transmit the SRS on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameters.

[0012] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to: send a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining an SRS resource; send a cyclic shift hopping parameter to the UE for SRS transmission from the UE; and receive an SRS from the UE on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.

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

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

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

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

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

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

[0019] Figure 5 A portion of a Radio Resource Control (RRC) "SRS-Resource" Information Element (IE) is illustrated, showing parameters related to the cyclic shift of the SRS resource.

[0020] Figure 6Different options for sounding reference signal (SRS) cyclic shift hopping across SRS repetitions are illustrated in accordance with aspects of the present disclosure.

[0021] Figure 7 Different options for SRS cyclic shift hopping when configuring SRS frequency hopping according to aspects of the present disclosure are illustrated.

[0022] Figure 8 Additional examples of SRS cyclic shift hopping across SRS hopping periods according to aspects of the present disclosure are illustrated.

[0023] Fig. 9 Two options for determining cyclic shift frequency hopping based on SRS transmission opportunities when frequency hopping is disabled in accordance with aspects of the present disclosure are illustrated.

[0024] Fig.10 and Fig.11

[0013] Example methods of wireless communications in accordance with aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0025] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. 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] 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.

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

[0028] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It will be appreciated that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the subject matter claimed. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions".

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

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

[0031] The term "base station" may refer to a single physical transmit receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of a base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from the UE and a neighboring base station whose reference radio frequency (RF) signal the UE is measuring. Since, as used herein, a TRP is the point through 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 the specific TRP of a base station.

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

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

[0034] Figure 1 An 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 as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network), or gNBs (where the wireless communication system 100 corresponds to an NR network), or a combination of the two, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0035] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 via another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and the like. 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.

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

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

[0038] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage 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 services to a restricted group called a closed subscriber group (CSG).

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

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

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

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

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

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

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

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

[0047] It should be noted that, depending on the entity forming the "downlink" beam, the downlink beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the uplink beam can be 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, and if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

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

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

[0050] 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 a frequency 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 a frequency 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.

[0051] 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). The 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 usually UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier on which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. are used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0071] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (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 in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

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

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

[0075] In some aspects, CU 280 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 280. 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 specific implementations, CU 280 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 280 may be implemented to communicate with DU 285 for network control and signaling.

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

[0077] The 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 functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on 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 plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the implementation of the DU 285 and CU 280 in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

[0080] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 259, the non-RT RIC 257 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 259 and may be received from a non-network data source or from a network function at the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the near-RT RIC 259 may be configured to 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 perform corrective actions through the SMO framework 255 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0081] Figure 3A , Figure 3B and Figure 3C The example may be combined with UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in the present invention (such as a dedicated network) are shown to support the operations described herein. It should be understood that these components can be implemented in different types of devices with different specific implementations (for example, in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] In the uplink, 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.

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

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

[0098] 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 a corresponding antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

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

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

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

[0102] 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 may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or be combined with at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by a processor and memory component of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by a processor and memory component of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by a processor and memory component of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor component). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, as will be appreciated, 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 processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, cyclic shift components 342, 388 and 398, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0116] SRS resources are configured by the RRC information element (IE) "SRS-Resource" or "SRS-PosResource". i ), the SRS cyclic shift (CS) is determined based on three RRC parameters (also called "higher layer parameters") defined at the SRS resource level. These parameters are (also expressed as "n_SRS^CS"), (also denoted as "N_ap^SRS") and (Also expressed as “n_SRS^(CS,max)”). The value of is given by the RRC parameter "cyclicShift" and can have a value from 0 to The value of . Indicates the number of antenna ports per SRS resource and can take values ​​of 1, 2 or 4. The number of antenna ports is given by the RRC parameter "nrofSRS-Ports" (if configured). Parameter Indicates the maximum number of cyclic shifts, which depends on the comb value K TC . K TC The value of is given by the RRC parameter "transmissionComb" and can take the value 2, 4 or 8.

[0117] When generating an SRS sequence for an SRS transmission in a symbol (each SRS transmission in a symbol has its own SRS sequence and its own cyclic shift), antenna port p i The cyclic shift α i as follows:

[0118]

[0119] The SRS per-port cyclic shift is calculated as follows:

[0120]

[0121] in Contained in the higher layer (e.g., RRC) parameter "transmissionComb". Maximum number of cyclic shifts Given by the following table:

[0122]

[0123] Table 1

[0124] Figure 5 A portion 500 of the RRC "SRS-Resource" IE is illustrated, which shows parameters related to the cyclic shift of the SRS resource. Specifically, Figure 5 The RRC parameters "nrofSRS-Ports", "transmissionComb" and "cyclicShift" are illustrated. It should be noted that the transmission comb has a choice of "n2", "n4" or "n8", each choice having different comb offset and cyclic shift parameters.

[0125] In order to improve the speed and throughput to the UE, multi-TRP (mTRP) technology has been introduced. In the mTRP scenario, the network forms a TRP cluster or group to serve one or more UEs. For example, one or more base stations may coordinate with each other to schedule TRP clusters to serve downlink transmissions to the UE or receive uplink transmissions from the UE. Coherent joint transmission (CJT) can be used to coordinate transmissions across multiple TRPs. In CJT, based on the CSI shared between the coordinated TRPs, the coordinated TRP sends a signal to the target UE that is jointly pre-coded using previous phase alignment and tight synchronization.

[0126] When two or more UEs send SRS to an mTRP simultaneously, multiple transmissions may cause interference at the receiving / measuring TRP, thereby reducing the measurement quality of the SRS. This may degrade system performance. For example, in a positioning scenario, the reduction in the accuracy of the SRS measurement results may result in a less accurate estimate of the UE's position. Therefore, SRS enhancement for CJT across multiple TRPs can be used to manage SRS interference across different UEs. More specifically, CSI acquisition for CJT for FR1 and up to four TRPs can be used, assuming that the backhaul and synchronization are ideal and the number of antenna ports across TRPs is the same. One of the potential SRS enhancements is to manage cross-SRS interference between TRPs for time division duplex (TDD) CJT via SRS capacity enhancement and / or interference randomization, which has the following constraints: 1) no additional resources for SRS are consumed, 2) existing SRS comb structures are reused, and 3) existing SRS root sequences are reused. To this end, enabling SRS cyclic shift hopping can reduce SRS interference between UEs.

[0127] The present disclosure introduces the SRS cyclic shift frequency hopping parameter (referred to as (also expressed as "n_SRS^(CS, hopping)") to enable SRS cyclic shift hopping. For example, the network entity may send SRS cyclic shift hopping parameters to the UE. The UE may send an SRS configured according to the SRS cyclic shift hopping parameters, thereby enabling SRS cyclic shift hopping, which may reduce SRS interference between UEs.

[0128] In some implementations, the SRS cyclic shift hopping parameter may indicate a hopping pattern of the cyclic shift of the SRS. The above SRS per-port cyclic shift calculation equation then becomes:

[0129]

[0130] SRS cyclic shift frequency hopping parameters Applicable to persistent (P), semi-persistent (SP) and aperiodic (AP) SRS time domain behaviors. In one aspect, the cyclic shift hopping pattern can be cyclic (referred to as "Option 1" in Table 2 below), which means Where n refers to the SRS occasion. On the other hand, the cyclic shift hopping pattern can be a bit reversal mode (referred to as "Option 2" in Table 2 below), which means As an example, The cyclic shift hopping mode may be determined based on a table (e.g., defined in a relevant standard) or configured to the UE via RRC (e.g., as part of the SRS configuration). An example table for the above two options (cyclic or bit reversal mode) is given below:

[0131]

[0132] Table 2

[0133] When the SRS resource is configured so that each SRS transmission opportunity spans multiple OFDM symbols, the SRS repetitions for SRS transmission are determined based on a higher layer (e.g., RRC) configuration of a repetition factor "R", where R is less than or equal to parameter is given by the field "nrofSymbols" contained in the higher layer parameter "resourceMapping" and is Figure 5 The number of consecutive OFDM symbols shown in .

[0134] The present disclosure provides a technique for SRS cyclic shift hopping across SRS repetitions. For example, SRS cyclic shift hopping across SRS repetitions may be enabled or disabled based on an RRC configuration (e.g., an RRC parameter "CS_HoppingRep" having a value of "true" or "false"), and may also be specified as always being disabled or always being enabled.

[0135] Figure 6 Different options for SRS cyclic shift hopping across SRS repetitions according to various aspects of the present disclosure are illustrated. Figure 6 In the example of , R = 4, which means there are four SRS repetitions within the SRS resource, and N = 4, which means there are four consecutive symbols carrying SRS transmissions of the SRS resource per time slot. It should be noted that when N = R, this means there is no frequency hopping repetition. Each shaded block represents an SRS transmission (here a repetition) of an SRS resource. Each SRS transmission in a symbol is configured as an SRS sequence with a cyclic shift. Figure 6 In , four SRS repetitions are sent in the last four symbols of the slot (labeled 10, 11, 12 and 13). In addition, the SRS repetitions do not span the entire available SRS bandwidth.

[0136] In the example illustrated in diagram 600, all four SRS transmissions (repetitions) have the same cyclic shift (as illustrated by having the same cross-hatching). However, in the example illustrated in diagram 650, each SRS transmission (repetition) has a different cyclic shift (as illustrated by having different cross-hatching). Therefore, in the example of diagram 600, SRS cyclic shift hopping across SRS repetitions is disabled, while in the example of diagram 650, SRS cyclic shift hopping across SRS repetitions is enabled (i.e., the UE has been configured to implement SRS cyclic shift hopping across SRS repetitions).

[0137] It should be noted that although diagrams 600 and 650 illustrate portions of a single time slot, a UE may send SRS on more than one time slot. In addition, a UE may send SRS on more or less than four symbols.

[0138] Mechanisms for both intra-slot and inter-slot SRS frequency hopping have been introduced. In addition, to improve SRS capacity, when frequency hopping is enabled (i.e., the UE has been configured to transmit SRS using frequency hopping), partial frequency sounding (also referred to as "sub-hopping") has been introduced. In the case of partial frequency hopping, only a portion of the configured SRS resources are sounded (i.e., transmitted) in a given symbol.

[0139] The present disclosure provides a technique for enabling SRS cyclic shift hopping when SRS hopping is enabled / configured to reduce SRS interference across TRPs. As a first option for enabling SRS cyclic shift hopping when SRS hopping is enabled, a separate RRC parameter (i.e., separate / independent from the parameter for enabling SRS hopping) may be used to enable or disable SRS cyclic shift hopping. As a second option, when SRS hopping is enabled, SRS cyclic shift hopping may always be enabled and the SRS cyclic shift hopping parameter may depend on the UE (i.e., be specific to the UE). For example, the SRS cyclic shift hopping parameter may be specific to the UE-ID, C-RNTI, SRS resource ID, pseudo-random sequence, etc.

[0140] In one aspect, the granularity for enabling SRS cyclic shift hopping may be intra-slot or inter-slot. That is, SRS cyclic shift hopping may be enabled / configured only for inter-slot (i.e., cyclic shift varies across slots), only for intra-slot (i.e., cyclic shift varies across SRS symbols within a slot), or both.

[0141] In one aspect, when SRS frequency hopping is enabled / configured, there are different options for when to enable / configure SRS cyclic shift frequency hopping. As a first option, SRS cyclic shift frequency hopping may be enabled across the legacy frequency hopping period. As a second option, SRS cyclic shift frequency hopping may be enabled only within the frequency hopping period. As a third option, SRS cyclic shift frequency hopping may be enabled as a combination of the first option and the second option (i.e., both across the frequency hopping period and within the frequency hopping period).

[0142] Figure 7 Different options for SRS cyclic shift hopping when configuring SRS frequency hopping according to various aspects of the present disclosure are illustrated. Figure 7 In the example of , the SRS resource is configured with R=1 and N=2, which means that there is one SRS transmission for each frequency hop. Each shaded block represents an SRS transmission of the SRS resource. Each SRS transmission in a symbol is configured as an SRS sequence with a cyclic shift. Figure 7In the example, the SRS is transmitted using frequency hopping in the last two symbols (labeled as 12 and 13) of the time slot. That is, the last two symbols of the time slot are the frequency hopping period. Specifically, the first part of the SRS is transmitted in the first symbol (here, symbol 12) over the first part of the total SRS bandwidth (the first frequency hopping period), and the second part of the SRS is transmitted in the second symbol (here, symbol 13) over the second part of the total SRS bandwidth (the second frequency hopping period).

[0143] In the example illustrated in diagram 700, the UE transmits SRS over two hopping periods using the same cyclic shift (as illustrated by SRS transmissions with the same cross hatching). However, in the example illustrated in diagram 750, the UE transmits SRS over two hopping periods using different cyclic shifts (as illustrated by SRS transmissions with different cross hatching). Therefore, in the example of diagram 700, SRS cyclic shift hopping across SRS hopping periods is disabled, while in the example of diagram 750, SRS cyclic shift hopping across SRS hopping periods is enabled (i.e., the UE has been configured to implement SRS cyclic shift hopping across SRS hopping periods).

[0144] It should be noted that although diagrams 700 and 750 illustrate portions of a single time slot, a UE may transmit an SRS over more than one time slot. Furthermore, a UE may transmit an SRS over more than two symbols. Furthermore, the term "SRS" may refer to an SRS resource, an SRS transmission of an SRS resource, or an SRS sequence based on which an SRS transmission is configured, depending on the context. An SRS transmission is a physical signal that a UE transmits, for example, over a period of time of a symbol.

[0145] Figure 8 Additional examples of SRS cyclic shift hopping across SRS hopping periods according to aspects of the present disclosure are illustrated. Figure 8 In the example of , SRS is transmitted using frequency hopping in the last four symbols (labeled as 10, 11, 12 and 13) of the time slot. That is, the last four symbols of the time slot are the frequency hopping period. Each shaded block represents SRS transmission.

[0146] In the example illustrated in diagram 800, the UE transmits SRS on four time slots (e.g., the SRS transmission may be repeated across four time slots). In each time slot, the UE uses the same cyclic shift (labeled as "CS0", "CS1", "CS2", and "CS3") in each of the four hopping cycles (as illustrated by the SRS transmissions with the same cross hatching). That is, the cyclic shift hopping spans the hopping cycle. In contrast, in the example illustrated in diagram 850, the UE uses a different cyclic shift (labeled as "CS0", "CS1", "CS2", and "CS3") in each of the four hopping cycles (as illustrated by the SRS transmissions with different cross hatching). That is, the cyclic shift hopping is within the hopping cycle.

[0147] It should be noted that although diagram 850 illustrates a portion of a single slot, the UE may send SRS over four slots as in diagram 800. Likewise, the UE may send SRS over more or less than four slots and in more or less than four symbols.

[0148] The present disclosure provides techniques for enabling SRS cyclic shift frequency hopping based on SRS transmission timing. As a first technique, when frequency hopping is disabled, cyclic shift frequency hopping is determined based on the SRS transmission timing (denoted as "n" in the equation below). As a first option (in the equation below), Fig. 9 ), the UE may be configured to use cyclic shift hopping across repetitions within the same SRS resource (which means there may be intra-slot and inter-slot cyclic shift hopping. For persistent (P) and semi-persistent (SP) SRS, the SRS transmission occasion n may be defined as:

[0149]

[0150] For aperiodic (AP) SRS, the SRS transmission opportunity n can be defined as:

[0151]

[0152] As a second option (in the following Fig. 9 In this option, the SRS transmission opportunity n can be defined as:

[0153]

[0154] Fig. 9 Two options for determining cyclic shift frequency hopping based on SRS transmission opportunities when frequency hopping is disabled according to aspects of the present disclosure are illustrated. Fig. 9 In the example, This means that the SRS is sent in two consecutive symbols of the time slot (as illustrated by the cross-hatched blocks). The first symbol is indexed as l'=0 and the second symbol is indexed as l'=1. Diagram 900 illustrates option 1 (cyclic shift hopping across repetitions within the same SRS resource) and n=0,1 in the first time slot, n=2,3 in the second time slot, and n=4,5 in the third time slot. Diagram 950 illustrates option 2 (cyclic shift hopping across SRS periodicity) and n=0 in the first time slot, n=1 in the second time slot, and n=3 in the third time slot.

[0155] As a second technique, when frequency hopping is enabled, cyclic shift frequency hopping is again determined based on the SRS transmission opportunity. As a first option, cyclic shift frequency hopping can be enabled across the legacy frequency hopping period. In this option, the SRS transmission opportunity n can be defined as:

[0156]

[0157] As a second option, cyclic shift hopping can be enabled within and across legacy hopping periods (but not within repetitions). In this option, the SRS transmission opportunity n can be defined as:

[0158]

[0159] In the above equation, is the number of time slots per frame used for subcarrier spacing configuration μ, n f is the system frame number (SFN), is the number of time slots in a frame for subcarrier spacing configuration μ, T 偏移 is the time slot offset, T SRS is the SRS periodicity, is the number of consecutive SRS symbols per time slot (given by the field “nrofSymbols” contained in the higher layer (e.g., RRC) parameter “resourceMapping”), l’ is the SRS symbol count within the resource (where )and is the maximum number of cyclic shifts. In addition, n SRS is the SRS number; if configured, B SRS Given by the field "b-SRS" in the higher layer parameter "freqHopping", otherwise B SRS =0; b 跳 is the frequency hopping parameter, where b hop = {0,1,2,3} and is determined by the higher layer parameter “freqHopping” if configured, otherwise b 跳 =0; N bis determined based on the selected row of Table 6.4.1.4.3-1 in 3GPP Technical Specification (TS) 38.211 corresponding to the following configuration: C SRS Given by the field "c-SRS" in the higher layer parameter "freqHopping" of the SRS resource level; and R is the repetition factor.

[0160] In one aspect, in order to indicate to the UE whether cyclic shift hopping is enabled or disabled, an SRS resource level RRC parameter may be signaled to the UE (e.g., by the UE's serving base station). The configuration may be based on the UE's ability to support cyclic shift hopping. The reporting of UE capabilities may be per frequency band, per frequency band combination, or per feature set. That is, the UE may indicate the ability to support cyclic shift hopping in certain frequency bands, frequency band combinations, or feature sets. When the parameter is disabled (i.e., not signaled to the UE), the UE is expected to follow the legacy SRS cyclic shift, which means that

[0161] In one aspect, to introduce greater flexibility, MAC-CE and / or DCI signaling may be used (eg, by a serving base station of a UE) to enable or disable cyclic shift hopping. In addition, MAC-CE and / or DCI signaling may be used to update the cyclic shift hopping pattern.

[0162] Fig.10 An example method 1000 of wireless communication in accordance with aspects of the present disclosure is illustrated. In an aspect, the method 1000 may be performed by a UE (eg, any of the UEs described herein).

[0163] At 1010, the UE receives an SRS configuration including one or more parameters defining SRS resources. In one aspect, operation 1010 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as means for performing the operation.

[0164] At 1020, the UE receives cyclic shift hopping parameters for SRS transmission. In an aspect, operation 1020 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as a means for performing the operation.

[0165] At 1030, the UE transmits an SRS on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter. In an aspect, operation 1030 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as a means for performing the operation.

[0166] As will be appreciated, a technical advantage of method 1000 is that interference is reduced by randomizing cyclic shift hopping between SRS transmissions by different UEs, thereby resulting in improved measurements at a receiving entity.

[0167] Fig.11 An example method 1100 of wireless communication in accordance with aspects of the present disclosure is illustrated. In an aspect, the method 1100 may be performed by a network entity (eg, a base station or any of the base station components described herein).

[0168] At 1110, the network entity sends an SRS configuration to a UE (e.g., any of the UEs described herein), the SRS configuration including one or more parameters defining SRS resources. In an aspect, operation 1110 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as means for performing the operation.

[0169] At 1120, the network entity sends the cyclic shift hopping parameters for SRS transmission from the UE to the UE. In an aspect, operation 1120 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered as a means for performing the operation.

[0170] At 1130, the network entity receives an SRS from the UE on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter. In an aspect, operation 1130 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered a means for performing the operation.

[0171] As will be appreciated, a technical advantage of method 1100 is that interference is reduced by randomizing cyclic shift hopping between SRS transmissions by different UEs, thereby improving measurements at the network entity. This will result in more accurate SRS channel estimates and improved spatial downlink precoders for selected UEs.

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

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

[0174] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining an SRS resource; receiving a cyclic shift hopping parameter for SRS transmission; and transmitting the SRS on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.

[0175] Clause 2. The method according to clause 1, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission, or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0176] Clause 3. A method as described in any of clauses 1 to 2, wherein the SRS resource is persistent, semi-persistent or aperiodic.

[0177] Clause 4. A method according to any one of clauses 1 to 3, wherein: the SRS resource is configured with one or more antenna ports, and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0178] Clause 5. A method according to any one of clauses 1 to 4, wherein the cyclic shift hopping pattern indicated by the cyclic shift hopping parameter is: a cycle from 0 to n_SRS^(CS,max)-1, where n_SRS^(CS,max) is the maximum cyclic shift number of the SRS resource; or a bit inversion pattern of the SRS resource from 0 to n_SRS^(CS,max).

[0179] Clause 6. A method as described in any of clauses 1 to 5, wherein the SRS transmission is a repetition of multiple symbols across at least one time slot.

[0180] Clause 7. The method of clause 6, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0181] Clause 8. The method of clause 7, wherein a parameter of the SRS resource configuration indicates whether the same cyclic shift or the different cyclic shift is used for the SRS transmission across the plurality of symbols.

[0182] Clause 9. A method according to any one of clauses 6 to 8, wherein: the one or more parameters include parameters for the SRS resource, the parameters configure SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot, and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0183] Clause 10. The method according to clause 9, wherein: the SRS transmission is an SRS hop transmitted according to the parameter configuring SRS frequency hopping, and the SRS hop has the same cyclic shift or the different cyclic shift based on the cyclic shift frequency hopping parameter.

[0184] Clause 11. A method as described in any of clauses 9 to 10, wherein the cyclic shift hopping parameter is specific to the UE.

[0185] Clause 12. A method according to any one of clauses 9 to 11, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple time slots; cyclic shift hopping within a single time slot; or any combination thereof.

[0186] Clause 13. A method according to any one of clauses 9 to 12, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple hopping periods; cyclic shift hopping within a single hopping period; or any combination thereof.

[0187] Clause 14. A method according to any one of clauses 1 to 13, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0188] Clause 15. A method according to any one of clauses 1 to 14, wherein: based on SRS hopping for the SRS resource being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resource or for cyclic shift hopping within and across the hopping period of the SRS resource.

[0189] Clause 16. A method as described in any of clauses 1 to 15, wherein the SRS configuration includes the cyclic shift hopping parameters based on UE capabilities to support SRS cyclic shift hopping.

[0190] Clause 17. The method of clause 16, wherein the UE capabilities are per frequency band, per frequency band combination, or per feature set.

[0191] Clause 18. A method as described in any of clauses 16 to 17, wherein: the one or more parameters and the cyclic shift hopping parameters are radio resource control (RRC) parameters.

[0192] Clause 19. A method according to any one of clauses 1 to 18, wherein: the SRS configuration is received via RRC signaling; the cyclic shift hopping parameters are received in one or more of the following: a medium access control element (MAC-CE), downlink control information (DCI), or both; and the cyclic shift hopping parameters enable, disable, or update another cyclic shift hopping mode indicated by the one or more parameters of the SRS configuration.

[0193] Clause 20. A method of wireless communication performed by a network entity, the method comprising: sending a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining SRS resources; sending cyclic shift hopping parameters for SRS transmission from the UE to the UE; and receiving SRS from the UE on the SRS resources, the SRS being configured based on at least the cyclic shift hopping parameters.

[0194] Clause 21. A method according to clause 20, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0195] Clause 22. A method according to any one of clauses 20 to 21, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0196] Clause 23. A method as described in any of clauses 20 to 22, wherein the SRS transmission is a repetition of multiple symbols across at least one time slot.

[0197] Clause 24. The method of clause 23, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0198] Clause 25. A method according to any one of clauses 23 to 24, wherein: the one or more parameters include parameters for the SRS resource, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0199] Clause 26. A method according to any one of clauses 20 to 25, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0200] Clause 27. A method according to any one of clauses 20 to 26, wherein: based on SRS hopping for the SRS resource being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resource or for cyclic shift hopping within and across the hopping period of the SRS resource.

[0201] Clause 28. A method as set forth in any of clauses 20 to 27, wherein the SRS configuration comprises the cyclic shift hopping parameters based on UE capabilities to support SRS cyclic shift hopping.

[0202] Clause 29. A user equipment (UE), the user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a sounding reference signal (SRS) configuration via the at least one transceiver, the SRS configuration comprising one or more parameters defining SRS resources; receive cyclic shift hopping parameters for SRS transmission via the at least one transceiver; and transmit the SRS on the SRS resources via the at least one transceiver, the SRS being configured based on at least the cyclic shift hopping parameters.

[0203] Clause 30. A UE according to clause 29, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0204] Clause 31. A UE as set forth in any of clauses 29 to 30, wherein the SRS resources are persistent, semi-persistent or aperiodic.

[0205] Clause 32. A UE according to any of clauses 29 to 31, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0206] Clause 33. A UE according to any one of clauses 29 to 32, wherein the cyclic shift hopping pattern indicated by the cyclic shift hopping parameter is: a cycle from 0 to n_SRS^(CS,max)-1, where n_SRS^(CS,max) is the maximum cyclic shift number of the SRS resource; or a bit inversion pattern of the SRS resource from 0 to n_SRS^(CS,max).

[0207] Clause 34. A UE as set forth in any of clauses 29 to 33, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0208] Clause 35. The UE of clause 34, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0209] Clause 36. The UE of clause 35, wherein a parameter of the SRS resource configuration indicates whether the same cyclic shift or the different cyclic shift is used for the SRS transmission across the plurality of symbols.

[0210] Clause 37. A UE according to any one of clauses 34 to 36, wherein: the one or more parameters include parameters for the SRS resources, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resources.

[0211] Clause 38. A UE according to clause 37, wherein: the SRS transmission is an SRS hop transmitted according to the parameter configuring SRS frequency hopping; and the SRS hop has the same cyclic shift or the different cyclic shift based on the cyclic shift frequency hopping parameter.

[0212] Clause 39. A UE as set forth in any of clauses 37 to 38, wherein the cyclic shift hopping parameters are specific to the UE.

[0213] Clause 40. A UE as set forth in any of clauses 37 to 39, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple time slots; cyclic shift hopping within a single time slot; or any combination thereof.

[0214] Clause 41. A UE as described in any of clauses 37 to 40, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple hopping periods; cyclic shift hopping within a single hopping period; or any combination thereof.

[0215] Clause 42. A UE according to any one of clauses 29 to 41, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0216] Clause 43. A UE according to any one of clauses 29 to 42, wherein: based on SRS hopping for the SRS resources being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resources or for cyclic shift hopping within and across the hopping period of the SRS resources.

[0217] Clause 44. A UE as set forth in any of clauses 29 to 43, wherein the SRS configuration comprises the cyclic shift hopping parameters based on the UE capability to support SRS cyclic shift hopping.

[0218] Clause 45. The UE of clause 44, wherein the UE capabilities are per frequency band, per frequency band combination, or per feature set.

[0219] Clause 46. A UE as described in any of clauses 44 to 45, wherein: the one or more parameters and the cyclic shift hopping parameters are radio resource control (RRC) parameters.

[0220] Clause 47. A UE according to any one of clauses 29 to 46, wherein: the SRS configuration is received via RRC signaling; the cyclic shift hopping parameters are received in one or more of the following: a medium access control element (MAC-CE), downlink control information (DCI), or both; and the cyclic shift hopping parameters enable, disable, or update another cyclic shift hopping mode indicated by the one or more parameters of the SRS configuration.

[0221] Clause 48. A network entity, comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: send a sounding reference signal (SRS) configuration to a user equipment (UE) via the at least one transceiver, the SRS configuration comprising one or more parameters defining SRS resources; send cyclic shift hopping parameters for SRS transmission from the UE via the at least one transceiver to the UE; and receive an SRS from the UE on the SRS resources via the at least one transceiver, the SRS being configured based on at least the cyclic shift hopping parameters.

[0222] Clause 49. A network entity according to clause 48, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0223] Clause 50. A network entity as described in any of clauses 48 to 49, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0224] Clause 51. A network entity as set forth in any of clauses 48 to 50, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0225] Clause 52. The network entity of clause 51, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0226] Clause 53. A network entity according to any one of clauses 51 to 52, wherein: the one or more parameters include parameters for the SRS resource, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0227] Clause 54. A network entity according to any one of clauses 48 to 53, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0228] Clause 55. A network entity according to any one of clauses 48 to 54, wherein: based on SRS hopping for the SRS resources being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resources or for cyclic shift hopping within and across the hopping period of the SRS resources.

[0229] Clause 56. A network entity as set forth in any of clauses 48 to 55, wherein the SRS configuration comprises the cyclic shift hopping parameters based on UE capabilities to support SRS cyclic shift hopping.

[0230] Clause 57. A user equipment (UE), comprising: a component for receiving a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining SRS resources; a component for receiving cyclic shift hopping parameters for SRS transmission; and a component for transmitting the SRS on the SRS resources, the SRS being configured according to at least the cyclic shift hopping parameters.

[0231] Clause 58. A UE according to clause 57, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0232] Clause 59. A UE as set forth in any of clauses 57 to 58, wherein the SRS resources are persistent, semi-persistent or aperiodic.

[0233] Clause 60. A UE as described in any of clauses 57 to 59, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0234] Clause 61. A UE according to any one of clauses 57 to 60, wherein the cyclic shift hopping pattern indicated by the cyclic shift hopping parameter is: a cycle from 0 to n_SRS^(CS,max)-1, where n_SRS^(CS,max) is the maximum cyclic shift number of the SRS resource; or a bit inversion pattern of the SRS resource from 0 to n_SRS^(CS,max).

[0235] Clause 62. A UE as set forth in any of clauses 57 to 61, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0236] Clause 63. The UE of clause 62, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0237] Clause 64. The UE of clause 63, wherein a parameter of the SRS resource configuration indicates whether the same cyclic shift or the different cyclic shift is used for the SRS transmission across the plurality of symbols.

[0238] Clause 65. A UE according to any one of clauses 62 to 64, wherein: the one or more parameters include parameters for the SRS resources, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resources.

[0239] Clause 66. A UE according to clause 65, wherein: the SRS transmission is an SRS hop transmitted according to the parameter configuring SRS hopping; and the SRS hop has the same cyclic shift or the different cyclic shift based on the cyclic shift hopping parameter.

[0240] Clause 67. A UE as set forth in any of clauses 65 to 66, wherein the cyclic shift hopping parameters are specific to the UE.

[0241] Clause 68. A UE as set forth in any of clauses 65 to 67, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple time slots; cyclic shift hopping within a single time slot; or any combination thereof.

[0242] Clause 69. A UE as set forth in any of clauses 65 to 68, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple hopping periods; cyclic shift hopping within a single hopping period; or any combination thereof.

[0243] Clause 70. A UE according to any one of clauses 57 to 69, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0244] Clause 71. A UE according to any one of clauses 57 to 70, wherein: based on SRS hopping for the SRS resources being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resources or for cyclic shift hopping within and across the hopping period of the SRS resources.

[0245] Clause 72. A UE as set forth in any of clauses 57 to 71, wherein the SRS configuration comprises the cyclic shift hopping parameters based on the UE capability to support SRS cyclic shift hopping.

[0246] Clause 73. The UE of clause 72, wherein the UE capabilities are per frequency band, per frequency band combination, or per feature set.

[0247] Clause 74. A UE as described in any of clauses 72 to 73, wherein: the one or more parameters and the cyclic shift hopping parameters are radio resource control (RRC) parameters.

[0248] Clause 75. A UE according to any one of clauses 57 to 74, wherein: the SRS configuration is received via RRC signaling; the cyclic shift hopping parameters are received in one or more of the following: a medium access control element (MAC-CE), downlink control information (DCI), or both; and the cyclic shift hopping parameters enable, disable, or update another cyclic shift hopping mode indicated by the one or more parameters of the SRS configuration.

[0249] Clause 76. A network entity, the network entity comprising: a component for sending a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining SRS resources; a component for sending cyclic shift hopping parameters for SRS transmission from the UE to the UE; and a component for receiving an SRS from the UE on the SRS resources, the SRS being configured based on at least the cyclic shift hopping parameters.

[0250] Clause 77. A network entity according to clause 76, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0251] Clause 78. A network entity as described in any of clauses 76 to 77, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0252] Clause 79. A network entity as set forth in any of clauses 76 to 78, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0253] Clause 80. The network entity of clause 79, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0254] Clause 81. A network entity according to any one of clauses 79 to 80, wherein: the one or more parameters include parameters for the SRS resource, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0255] Clause 82. A network entity according to any one of clauses 76 to 81, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0256] Clause 83. A network entity according to any one of clauses 76 to 82, wherein: based on SRS hopping for the SRS resources being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resources or for cyclic shift hopping within and across the hopping period of the SRS resources.

[0257] Clause 84. A network entity as set forth in any of clauses 76 to 83, wherein the SRS configuration comprises the cyclic shift hopping parameters based on UE capabilities to support SRS cyclic shift hopping.

[0258] Clause 85. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), causes the UE to: receive a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining an SRS resource; receive cyclic shift hopping parameters for SRS transmission; and transmit the SRS on the SRS resource, the SRS being configured based on at least the cyclic shift hopping parameters.

[0259] Clause 86. A non-transitory computer-readable medium according to clause 85, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0260] Clause 87. The non-transitory computer-readable medium of any one of Clauses 85 to 86, wherein the SRS resource is persistent, semi-persistent, or aperiodic.

[0261] Clause 88. A non-transitory computer-readable medium as described in any of clauses 85 to 87, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0262] Clause 89. A non-transitory computer-readable medium according to any one of clauses 85 to 88, wherein the cyclic shift hopping pattern indicated by the cyclic shift hopping parameter is: a cycle from 0 to n_SRS^(CS,max)-1, where n_SRS^(CS,max) is the maximum cyclic shift number of the SRS resource; or a bit inversion pattern of the SRS resource from 0 to n_SRS^(CS,max).

[0263] Clause 90. The non-transitory computer-readable medium of any of clauses 85 to 89, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0264] Clause 91. The non-transitory computer-readable medium of clause 90, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0265] Clause 92. The non-transitory computer-readable medium of clause 91, wherein a parameter of the SRS resource configuration indicates whether the same cyclic shift or the different cyclic shift is used for the SRS transmission across the plurality of symbols.

[0266] Clause 93. A non-transitory computer-readable medium according to any one of clauses 90 to 92, wherein: the one or more parameters include parameters for the SRS resource, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift frequency hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0267] Clause 94. A non-transitory computer-readable medium according to clause 93, wherein: the SRS transmission is an SRS hop transmitted according to the parameters for configuring SRS frequency hopping; and the SRS hop has the same cyclic shift or the different cyclic shift based on the cyclic shift frequency hopping parameters.

[0268] Clause 95. The non-transitory computer-readable medium of any of clauses 93 to 94, wherein the cyclic shift hopping parameters are specific to the UE.

[0269] Clause 96. A non-transitory computer-readable medium as described in any of clauses 93 to 95, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple time slots; cyclic shift hopping within a single time slot; or any combination thereof.

[0270] Clause 97. A non-transitory computer-readable medium as described in any one of clauses 93 to 96, wherein the cyclic shift hopping parameters are configured for: cyclic shift hopping across multiple hopping periods; cyclic shift hopping within a single hopping period; or any combination thereof.

[0271] Clause 98. A non-transitory computer-readable medium according to any one of clauses 85 to 97, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0272] Clause 99. A non-transitory computer-readable medium according to any one of clauses 85 to 98, wherein: based on SRS hopping for the SRS resource being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resource or for cyclic shift hopping within and across the hopping period of the SRS resource.

[0273] Clause 100. The non-transitory computer-readable medium of any of clauses 85 to 99, wherein the SRS configuration comprises the cyclic shift hopping parameters based on UE capabilities supporting SRS cyclic shift hopping.

[0274] Clause 101. The non-transitory computer-readable medium of clause 100, wherein the UE capabilities are per frequency band, per frequency band combination, or per feature set.

[0275] Clause 102. The non-transitory computer-readable medium of any one of clauses 100 to 101, wherein: the one or more parameters and the cyclic shift hopping parameters are radio resource control (RRC) parameters.

[0276] Clause 103. A non-transitory computer-readable medium according to any one of clauses 85 to 102, wherein: the SRS configuration is received via RRC signaling; the cyclic shift hopping parameters are received in one or more of the following: a medium access control element (MAC-CE), downlink control information (DCI), or both; and the cyclic shift hopping parameters enable, disable, or update another cyclic shift hopping mode indicated by the one or more parameters of the SRS configuration.

[0277] Clause 104. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a network entity, causes the network entity to: send a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining SRS resources; send cyclic shift hopping parameters to the UE for SRS transmission from the UE; and receive an SRS from the UE on the SRS resources, the SRS being configured based on at least the cyclic shift hopping parameters.

[0278] Clause 105. A non-transitory computer-readable medium as described in clause 104, wherein the cyclic shift hopping parameter indicates: a value of a cyclic shift hopping pattern for the SRS transmission; or an index of the value of the cyclic shift hopping pattern in a cyclic shift hopping pattern table.

[0279] Clause 106. A non-transitory computer-readable medium as described in any of clauses 104 to 105, wherein: the SRS resource is configured with one or more antenna ports; and the cyclic shift hopping parameter is associated with one of the one or more antenna ports.

[0280] Clause 107. The non-transitory computer-readable medium of any of clauses 104 to 106, wherein the SRS transmission is a repetition of a plurality of symbols across at least one time slot.

[0281] Clause 108. The non-transitory computer-readable medium of clause 107, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

[0282] Clause 109. A non-transitory computer-readable medium according to any one of clauses 107 to 108, wherein: the one or more parameters include parameters for the SRS resource, the parameters configuring SRS frequency hopping for the SRS transmission of the multiple symbols across the at least one time slot; and the cyclic shift frequency hopping parameters are received in the SRS configuration based on SRS frequency hopping being configured for the SRS resource.

[0283] Clause 110. A non-transitory computer-readable medium according to any one of clauses 104 to 109, wherein: based on SRS frequency hopping for the SRS resource being disabled, SRS transmissions for cross-SRS repetitions within a time slot and across time slots are configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a time slot index, and the number of SRS symbols of the SRS resource.

[0284] Clause 111. A non-transitory computer-readable medium according to any one of clauses 104 to 110, wherein: based on SRS hopping for the SRS resource being enabled, the cyclic shift hopping parameters are configured for cyclic shift hopping across a hopping period of the SRS resource or for cyclic shift hopping within and across the hopping period of the SRS resource.

[0285] Clause 112. The non-transitory computer-readable medium of any of clauses 104 to 111, wherein the SRS configuration comprises the cyclic shift hopping parameters based on UE capabilities supporting SRS cyclic shift hopping.

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

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

[0288] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or performed 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 an 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.

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

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

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receiving, via the at least one transceiver, a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining SRS resources; receiving, via the at least one transceiver, cyclic shift frequency hopping parameters for SRS transmission; as well as An SRS is transmitted on the SRS resource via the at least one transceiver, the SRS being configured according to at least the cyclic shift hopping parameter.

2. The UE according to claim 1, wherein the cyclic shift frequency hopping parameter indicates: The value of the cyclic shift frequency hopping pattern sent by the SRS; or The index of the value of the cyclic shift hopping pattern in the cyclic shift hopping pattern table. The UE according to claim 1 , wherein the SRS resource is persistent, semi-persistent or aperiodic.

4. The UE according to claim 1, wherein: The SRS resource is configured with one or more antenna ports; and The cyclic shift hopping parameter is associated with one of the one or more antenna ports.

5. The UE according to claim 1, wherein the cyclic shift hopping pattern indicated by the cyclic shift hopping parameter is: Cycle from 0 to n_SRS^(CS,max)-1, where n_SRS^(CS,max) is the maximum cyclic shift number of the SRS resource; or The bit inversion pattern of the SRS resource from 0 to n_SRS^(CS,max). The UE of claim 1 , wherein the SRS transmission is a repetition of multiple symbols across at least one time slot. 7 . The UE according to claim 6 , wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols, or different cyclic shifts are used for different SRS symbols of the plurality of symbols. 8 . The UE according to claim 7 , wherein a parameter of the SRS resource configuration indicates whether the same cyclic shift or the different cyclic shift is used for the SRS transmission across the plurality of symbols.

9. The UE according to claim 6, wherein: The one or more parameters include a parameter for the SRS resource, the parameter configuring SRS frequency hopping for the SRS transmission across the plurality of symbols of the at least one time slot; and The cyclic shift hopping parameter is received in the SRS configuration based on SRS hopping being configured for the SRS resource.

10. The UE according to claim 9, wherein: The SRS transmission is an SRS hopping transmission according to the parameters for configuring the SRS frequency hopping; and The SRS hopping has the same cyclic shift or the different cyclic shift based on the cyclic shift hopping parameter.

11. The UE of claim 9, wherein the cyclic shift hopping parameter is specific to the UE.

12. The UE according to claim 9, wherein the cyclic shift hopping parameter is configured for: Cyclic shift frequency hopping across multiple time slots; Cyclic shift frequency hopping within a single time slot; or Any combination of them.

13. The UE according to claim 9, wherein the cyclic shift hopping parameter is configured for: Cyclic shift frequency hopping across multiple frequency hopping periods; Cyclic shift hopping within a single hopping period; or Any combination of them.

14. The UE according to claim 1, wherein: Based on SRS frequency hopping being disabled for the SRS resource, SRS transmission of cross-SRS repetition within a slot and across slots is configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a slot index, and a number of SRS symbols of the SRS resource.

15. The UE according to claim 1, wherein: Based on SRS frequency hopping for the SRS resource being enabled, the cyclic shift frequency hopping parameters are configured for cyclic shift frequency hopping across a frequency hopping period of the SRS resource or for cyclic shift frequency hopping within and across the frequency hopping period of the SRS resource.

16. The UE of claim 1, wherein the SRS configuration comprises the cyclic shift hopping parameters based on a UE capability of supporting SRS cyclic shift hopping.

17. The UE of claim 16, wherein the UE capabilities are per frequency band, per frequency band combination, or per feature set.

18. The UE according to claim 16, wherein: The one or more parameters and the cyclic shift hopping parameter are radio resource control (RRC) parameters.

19. The UE according to claim 1, wherein: The SRS configuration is received via RRC signaling; The cyclic shift hopping parameters are received in one or more of: a medium access control element (MAC-CE), downlink control information (DCI), or both; and The cyclic shift hopping parameter enables, disables or updates another cyclic shift hopping pattern indicated by the one or more parameters of the SRS configuration.

20. A network entity, comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: transmitting, via the at least one transceiver, a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining SRS resources; transmitting, via the at least one transceiver, to the UE, cyclic shift hopping parameters for SRS transmission from the UE; as well as An SRS is received from the UE on the SRS resource via the at least one transceiver, the SRS being configured according to at least the cyclic shift hopping parameter.

21. The network entity of claim 20, wherein the cyclic shift hopping parameter indicates: The value of the cyclic shift frequency hopping pattern sent by the SRS; or The index of the value of the cyclic shift hopping pattern in the cyclic shift hopping pattern table.

22. The network entity according to claim 20, wherein: The SRS resource is configured with one or more antenna ports; and The cyclic shift hopping parameter is associated with one of the one or more antenna ports.

23. The network entity of claim 20, wherein the SRS transmission is a repetition of multiple symbols across at least one time slot.

24. The network entity of claim 23, wherein the cyclic shift hopping parameter indicates that the same cyclic shift is used for the SRS transmission across the plurality of symbols or that different cyclic shifts are used for different SRS symbols of the plurality of symbols.

25. The network entity according to claim 23, wherein: The one or more parameters include a parameter for the SRS resource, the parameter configuring SRS frequency hopping for the SRS transmission across the plurality of symbols of the at least one time slot; and The cyclic shift hopping parameter is received in the SRS configuration based on SRS hopping being configured for the SRS resource.

26. The network entity according to claim 20, wherein: Based on SRS frequency hopping being disabled for the SRS resource, SRS transmission of cross-SRS repetition within a slot and across slots is configured with different cyclic shifts based on an orthogonal frequency division multiplexing (OFDM) symbol index, a slot index, and a number of SRS symbols of the SRS resource.

27. The network entity according to claim 20, wherein: Based on SRS frequency hopping for the SRS resource being enabled, the cyclic shift frequency hopping parameters are configured for cyclic shift frequency hopping across a frequency hopping period of the SRS resource or for cyclic shift frequency hopping within and across the frequency hopping period of the SRS resource.

28. The network entity of claim 20, wherein the SRS configuration comprises the cyclic shift hopping parameters based on a UE capability to support SRS cyclic shift hopping.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a sounding reference signal (SRS) configuration, the SRS configuration comprising one or more parameters defining SRS resources; receiving cyclic shift frequency hopping parameters for SRS transmission; and An SRS is sent on the SRS resource, wherein the SRS is configured according to at least the cyclic shift hopping parameter.

30. A method of wireless communication performed by a network entity, the method comprising: sending a sounding reference signal (SRS) configuration to a user equipment (UE), the SRS configuration comprising one or more parameters defining SRS resources; sending, to the UE, cyclic shift hopping parameters for SRS transmission from the UE; as well as An SRS is received from the UE on the SRS resource, the SRS being configured according to at least the cyclic shift hopping parameter.