Dynamic adaptation of sounding reference signal frequency domain parameters

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first network node may receive, from a second network node, a sounding reference signal (SRS) configuration associated with a set of SRS resources including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the set of SRS resources. The first network node may receive, from the second network node, a message indicating modification information for dynamic reconfiguration of one or more frequency domain parameters associated with at least one SRS resource from the set of one or more frequency domain parameters. The first network node may transmit an SRS to the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Israel Patent Application No. 294194, filed on June 22, 2022, entitled “DYNAMIC ADAPTATION OF SOUNDING REFERENCE SIGNAL FREQUENY DOMAIN PARAMETERS”, which is assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for dynamic adaptation of sounding reference signal (SRS) frequency domain parameters. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0006] Some aspects described herein relate to a first network node for wireless communication. The first network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an SRS configuration associated with an SRS resource set including one or more sounding reference signal (SRS) resources from a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The one or more processors may be configured to receive a message indicating modification information from the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The one or more processors may be configured to send an SRS to the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

[0007] Some aspects described herein relate to a first network node for wireless communication. The first network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The one or more processors may be configured to send a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The one or more processors may be configured to receive an SRS from the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

[0008] Some aspects described herein relate to a method of wireless communication performed by a first network node. The method may include receiving an SRS configuration associated with an SRS resource set including one or more SRS resources from a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The method may include receiving a message indicating modification information from the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The method may include sending an SRS to the second network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0009] Some aspects described herein relate to a method of wireless communication performed by a first network node. The method may include sending an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The method may include sending a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The method may include receiving an SRS from the second network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium having stored thereon instructions for wireless communication, the instructions, when executed by a first network node, causing the first network node to receive from a second network node an SRS configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The instructions, when executed by the first network node, can cause the first network node to receive from the second network node a message indicating modification information, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The instructions, when executed by the first network node, can cause the first network node to send an SRS to the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium having stored thereon instructions for wireless communication, the instructions, when executed by a first network node, causing the first network node to send an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The instructions, when executed by the first network node, can cause the first network node to send a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The instructions, when executed by the first network node, can cause the first network node to receive an SRS from the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving an SRS configuration associated with an SRS resource set including one or more SRS resources from a network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The apparatus may include a component for receiving a message indicating modification information from the network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The apparatus may include a component for sending an SRS to the network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending an SRS configuration associated with an SRS resource set including one or more SRS resources to a network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The apparatus may include a component for sending a message indicating modification information to the network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The apparatus may include a component for receiving an SRS from the network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings illustrate certain example aspects of the disclosure and therefore are not intended to limit the scope. The same reference numbers in different drawings may identify the same or similar elements.

[0015] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0016] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0017] Figure 3 is an example of a disaggregated base station architecture according to the present disclosure.

[0018] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of a sounding reference signal (SRS) resource set according to the present disclosure.

[0020] Figure 6 is a diagram of an example associated with dynamic adaptation of SRS frequency domain parameters according to the present disclosure.

[0021] Figure 7 is a diagram of an example associated with a communication timeline for dynamic adaptation of SRS frequency domain parameters according to the present disclosure.

[0022] Figure 8 is a diagram of an example associated with a communication timeline for dynamic adaptation of SRS frequency domain parameters according to the present disclosure.

[0023] Fig. 9 is a diagram of an example associated with SRS triggering state configuration and activation for dynamic adaptation of SRS frequency domain parameters according to the present disclosure.

[0024] Fig.10 is a diagram illustrating an example process performed, for example, by a first network node according to the present disclosure.

[0025] Fig.11 is a diagram illustrating an example process performed, for example, by a first network node according to the present disclosure.

[0026] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0027] Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure, function, example, aspect, etc. presented throughout the present disclosure. For example, the present disclosure includes any structure, function, example, aspect, etc. disclosed herein, whether implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement an apparatus or practice a method.

[0029] In addition, the scope of the present disclosure includes such devices or methods implemented using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein.Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0030] Aspects and examples generally include methods, apparatuses, nodes, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as described or fully described herein with reference to the figures and description and as illustrated in the figures and description.

[0031] The present disclosure can be easily used as a basis for modifying or designing other structures for performing the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages are better understood from the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims.

[0032] Although various aspects are described in the present disclosure by illustrating some examples, such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein can be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of different sizes, shapes and compositions.

[0033] Several aspects of telecommunication systems are presented with reference to various devices and techniques. These devices and techniques are described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0035] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0036] A wireless network may include one or more base stations that support communication of a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communication and uplink communication. A "downlink" (or "DL") refers to a communication link from a base station to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a base station. Additionally or alternatively, a wireless network may include one or more UEs that communicate with each other. For example, a first UE may communicate with a second UE via a sidelink communication. A "sidelink" (or "SL") refers to a communication link between UEs.

[0037] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0038] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base station 110 can be interconnected with each other and / or to one or more other base stations 110 (which may also be referred to as "network nodes") in the wireless network 100 using any transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0039] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0040] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0041] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0042] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0043] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0044] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other device, system, device, node, etc. configured to communicate via a wireless medium.

[0045] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0046] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur 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.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower 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, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0051] In some aspects, the first network node (e.g., Figure 1 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive from a second network node an SRS configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; receive from the second network node a message indicating modification information for dynamically reconfiguring one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and send an SRS to the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] In some aspects, the first network node (e.g., Figure 1 The communication manager 150 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; send a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and receive an SRS from the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0053] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0054] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0055] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a group of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based on the MCS selected for the UE 120 and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0056] At the UE 120, a group of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from the base station 110 and / or other base stations 110, and a group of received signals (e.g., R received signals) can be provided to a group of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert and / or digitize) the received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from the modem 254, can perform MIMO detection on the received symbols where applicable, and can provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0057] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0058] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0059] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 13 ) or any aspects of any of the methods described herein.

[0060] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 6 to 13 ) or any aspects of any of the methods described herein.

[0061] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in can perform or direct e.g. Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0062] In some aspects, a first network node (e.g., UE 120 or another network node) includes: means for receiving, from a second network node, an SRS configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; means for receiving, from the second network node, a message indicating modification information for dynamically reconfiguring one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and / or means for sending an SRS to the second network node using the at least one SRS resource in accordance with the modification information for the one or more frequency domain parameters. In some aspects, means for the first network node to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0063] In some aspects, a first network node (e.g., base station 110, network entity, or another network node) includes: means for sending an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; means for sending a message indicating modification information to the second network node, the modification information for dynamically reconfiguring one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and / or means for receiving an SRS from the second network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters. In some aspects, means for the first network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0064] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0065] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0066] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. 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 (BS, e.g., base station 110) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5GNB, an access node (AP), a TRP, a cell, etc.) can be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a decomposed base station.

[0067] 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 centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0068] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. 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.

[0069] Figure 3 is an example of a disaggregated base station architecture 300 according to the present disclosure. Figure 3 The decomposed base station architecture 300 shown in FIG. 3 may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0070] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, 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 that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0071] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 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 310 may be implemented to communicate with DU 330 for network control and signaling.

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

[0073] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, the RU 340 controlled by the DU 330 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 on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0074] The SMO framework 305 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 305 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 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) 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 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

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

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

[0077] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0078] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown, the downlink channel and the downlink reference signal may carry information from a network entity (e.g., in conjunction with Figure 4 The uplink channel and the uplink reference signal may carry information from the UE 120 to the base station 110 as described and depicted as an example.

[0079] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, UE 120 may send confirmation (ACK) or negative confirmation (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on PUCCH and / or PUSCH.

[0080] As further shown in the figure, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS) or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0081] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the base station 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0082] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The base station 110 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least on these measurements, the UE 120 may perform channel estimation and may report channel estimation parameters (e.g., in a CSI report) such as a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or a reference signal received power (RSRP), etc., to the base station 110. Base station 110 can use CSI reports to select transmission parameters for downlink communication to UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), modulation and coding scheme (MCS), or refined downlink beams (e.g., using a beam refinement procedure or a beam management procedure), etc.

[0083] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and can be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0084] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0085] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the base station 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may require detecting downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive the PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the base station 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0086] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The base station 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The base station 110 may measure the SRS, may perform channel estimation based at least on the measurement, and may use the SRS measurement to configure communications with the UE 120.

[0087] Reference signals may be used to increase the reliability and efficiency of communications between wireless devices. For example, base station 110 may measure uplink reference signals to select a configuration or other transmission parameters for communications between base station 110 and UE 120. For example, base station 110 may measure uplink reference signals to estimate delay spread, signal-to-noise ratio (SNR), and / or Doppler parameters (e.g., Doppler shift or Doppler spread) associated with an uplink channel, etc.

[0088] "Doppler shift" refers to the displacement or change of the frequency of a signal between a transmitter and a receiver. Doppler shift may sometimes be referred to as frequency offset. For example, when the transmitter of a signal moves relative to a receiver, Doppler shift may occur. Relative movement can shift the frequency of a signal so that the frequency of the signal received at the receiver is different from the frequency of the signal sent at the transmitter. In other words, the frequency of the signal received by the receiver is different from the frequency of the signal originally transmitted. "Doppler spread" refers to the widening of the spectrum of a narrowband signal transmitted through a multipath propagation channel. When there is relative motion between the transmitter and the receiver, Doppler spread may be caused by different Doppler shifts associated with multiple propagation paths. For example, when there is no relative motion between the transmitter and the receiver, due to the multipath propagation channel, the receiver may receive the same signal at different times because one copy of the signal uses a shorter path and arrives quickly, while another copy of the signal may use a longer path. In the case of relative motion between the transmitter and the receiver, signals on different paths may arrive at the receiver at different times and at different frequencies (e.g., due to different Doppler shifts associated with each path). Doppler spread may be a measure of the frequency difference of signals on paths associated with a multipath propagation channel. Doppler spread may sometimes be referred to as a channel time correlation or channel time coherence characteristic of a multipath propagation channel.

[0089] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0090] Figure 5 is a diagram illustrating an example 500 of an SRS resource set according to the present disclosure. A network entity (e.g., in conjunction with Figure 5 The base station 110 (depicted and described as an example) may configure the UE 120 with one or more SRS resource sets to allocate resources for SRS transmission by the UE 120. For example, the configuration for the SRS resource set may be indicated in a radio resource control (RRC) message (e.g., an RRC configuration message or an RRC reconfiguration message). As shown by reference numeral 505, the SRS resource set may include one or more resources (e.g., shown as SRS resources), which may be associated with or configured with different time resources and / or frequency resources (e.g., time slots, symbols, resource blocks, resource element subsets, and / or periodicity of time resources).

[0091] As shown by reference numeral 510, the SRS resource may be configured to be associated with one or more antenna ports on which the SRS is to be sent (e.g., on corresponding time-frequency resources). Thus, the configuration for one or more SRS resources associated with or configured with an SRS resource set may indicate one or more time-frequency resources on which the SRS is to be sent, and may indicate one or more antenna ports on which the SRS is to be sent on these time-frequency resources. In some aspects, the configuration for the SRS resource set may indicate a use case for the SRS resource set (e.g., in an SRSResourceSet.Usage information element). For example, the SRS resource set may have use cases for antenna switching, codebook, non-codebook, or beam management.

[0092] The antenna switching SRS resource set may be used to determine downlink CSI with reciprocity between the uplink channel and the downlink channel. For example, when there is reciprocity between the uplink channel and the downlink channel, the base station 110 may use the antenna switching SRS (e.g., an SRS sent using SRS resources configured under one or more antenna switching SRS resource sets) to obtain downlink CSI (e.g., to determine a downlink precoder to be used for communication with the UE 120).

[0093] When base station 110 evaluates and indicates an uplink pre-decoder to UE 120 based on the uplink CSI, the codebook SRS resource set may be used to determine the uplink CSI. For example, when base station 110 is configured to determine an uplink pre-decoder to UE 120 (e.g., using a pre-decoder codebook), base station 110 may use a codebook SRS (e.g., an SRS sent using resources in a codebook SRS resource set) to obtain uplink CSI (e.g., to determine an uplink pre-decoder to be indicated to UE 120 and used by UE 120 to communicate with base station 110). In some aspects, a virtual port (e.g., a combination of two or more antenna ports) that may be associated with a maximum received signal power or reception quality experienced by base station 110 may be used for the codebook SRS.

[0094] When UE 120 pre-selects one or more uplink precoder candidate options, a non-codebook SRS resource set may be used to assist in uplink CSI evaluation in the case of reciprocal uplink and downlink channels (e.g., rather than base station 110 autonomously evaluating uplink precoder candidates and selecting one uplink precoder candidate to be explicitly indicated to UE 120 for uplink predecoding). For example, when UE 120 is configured to send non-codebook based SRS, UE 120 may select one or more uplink precoder candidates based on downlink measurements, and the one or more uplink precoder candidates will be sent for different SRS resources (e.g., precoded SRS will be sent, where each SRS resource will be associated with a different uplink precoder candidate). The base station 110 may use a non-codebook SRS (e.g., an SRS sent using resources in a non-codebook SRS resource set) to select one of the precoder candidates and obtain other uplink CSI parameters given the selected uplink precoder candidate. In this case, the base station 110 may indicate the uplink transmission parameters to the UE 120 at least partially implicitly (e.g., precoding information) based on the selected non-codebook SRS resources (e.g., via an SRI indicator). The beam management SRS resource set may be used for uplink beam selection and / or evaluation (e.g., for mmWave communications) by the base station 110.

[0095] SRS resources may be configured as periodic, semi-persistent (sometimes referred to as semi-persistent scheduling (SPS), or aperiodic. Periodic SRS resources may be configured via a configuration message indicating the periodicity of the SRS resources (e.g., slot-level periodicity, where the SRS resources occur every Y slots) and a slot offset. A periodic SRS resource set may always be activated (e.g., transmitted) and may not be dynamically activated or deactivated. Semi-persistent SRS resources may also be configured via a configuration message indicating the periodicity and slot offset for the semi-persistent SRS resources and may be dynamically activated and deactivated (e.g., using DCI or a medium access control (MAC) control element (CE) (MAC-CE)). Aperiodic SRS resources may be dynamically triggered, such as via DCI (e.g., UE-specific DCI or group-common DCI).

[0096] In some examples, aperiodic SRS resources may be triggered via an SRS request field included in a DCI message. For example, the SRS request field may include a value (e.g., a code point) associated with an SRS trigger state. When the DCI (e.g., via an SRS request field in the DCI) indicates a specific SRS trigger state, the "SRS trigger state" may refer to a configuration (e.g., an RRC configuration) of a list of one or more SRS resource sets to be triggered by the DCI. The SRS trigger state may be an RRC configured by a network entity (e.g., via one or more aperiodicSRS-ResourceTrigger parameters). The base station 110 may dynamically indicate or select different SRS trigger states via the DCI. For example, configuration information (e.g., RRC configuration information) may map or link each SRS trigger state to a code point for a DCI field (e.g., an SRS request field) or to another indicator. The base station 110 may include a code point or indicator in the DCI (e.g., in the SRS request field) to dynamically trigger or select an SRS trigger state linked or associated with an SRS resource set (or several SRS resource sets). In some examples, the configuration information may configure the linking or association of different SRS triggering states with different SRS resource sets having different usage types (such as antenna switching, codebook, non-codebook, beam management, and / or positioning, etc.).

[0097] In some aspects, the UE 120 may be configured with a mapping between SRS ports (e.g., antenna ports) and corresponding SRS resources (e.g., which antenna port(s) will be used for each SRS resource). The UE 120 may use the SRS ports indicated in the configuration to send a particular SRS resource. In some aspects, the SRS resource may span N adjacent symbols within a time slot (e.g., where N is equal to 1, 2, or 4). The UE 120 may be configured with X SRS ports (e.g., where X=1, 2, 4). In some aspects, each of the X SRS ports may be mapped to a corresponding symbol of the SRS resource and used to send the SRS on that symbol.

[0098] like Figure 5As shown, in some aspects, different SRS resource sets indicated to UE 120 (e.g., having different use cases) can overlap in terms of associated SRS resources (e.g., can be configured with one or more identical SRS resource identifiers). For example, as shown by reference numeral 515, a first SRS resource set (e.g., shown as SRS resource set 1) is shown as having an antenna switching use case. As shown, the example antenna switching SRS resource set includes a first SRS resource (shown as SRS resource A) and a second SRS resource (shown as SRS resource B). Therefore, antenna port 0 and antenna port 1 will be used to send antenna switching SRS according to or using SRS resource A configuration (e.g., a first time-frequency resource), and antenna port 2 and antenna port 3 will be used to send antenna switching SRS according to or using SRS resource B configuration (e.g., a second time-frequency resource).

[0099] As shown by reference numeral 520, a second SRS resource set (e.g., shown as SRS resource set 2) can be configured for a codebook use case or type. As shown, the example codebook SRS resource set includes only a first SRS resource (shown as SRS resource A). Therefore, the codebook SRS can be sent via antenna port 0 and antenna port 1 using SRS resource A configuration (e.g., a first time-frequency resource).

[0100] As described above, the network entity (e.g., base station 110) may configure one or more SRS resource sets. For example, the network entity may configure an SRS resource set including one or more frequency domain parameters (e.g., information or configuration indicating a position and / or pattern of SRS resources linked to an SRS resource set in the frequency domain), one or more time domain parameters (e.g., information indicating a position and / or pattern of SRS resources linked to an SRS resource set in the time domain), and / or one or more spatial domain parameters, etc. For example, the frequency domain parameters may include a transmission combination parameter associated with frequency domain density (e.g., a transmissionComb parameter), a transmission combination offset parameter (e.g., a combOffset parameter), a frequency domain shift parameter (e.g., a freqDomainShift parameter), a frequency domain position parameter (e.g., a freqDomainPosition parameter), a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value (e.g., a freqHopping.c-SRS parameter), a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value (e.g., a freqHopping.b-SRS parameter), a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hops, or at least one of an offset associated with frequency hopping (e.g., a freqHopping.b-hop parameter), and / or one or more partial frequency detection parameters, etc.

[0101] The transmission combination parameter (e.g., transmissionComb parameter) may indicate the frequency domain density associated with the SRS resource and / or SRS resource set (e.g., for each SRS port). In some examples, the transmission combination parameter may indicate the pattern of the frequency domain resources associated with the SRS resource set. For example, the SRS may not be transmitted in every subcarrier of the bandwidth associated with the SRS resource and / or SRS resource set. The value of the transmission combination parameter may indicate the spacing or distribution of the occupied subcarriers or resource elements on the bandwidth associated with the SRS resource. The transmission combination parameter may have a value of 2 (e.g., indicating that one subcarrier or resource element in every 2 subcarriers or resource elements includes SRS), 4 (e.g., indicating that one subcarrier or resource element in every 4 subcarriers or resource elements includes SRS) or 8 (e.g., indicating that one subcarrier or resource element in every 8 subcarriers or resource elements includes SRS), etc. The transmission combination offset parameter (e.g., combOffset parameter) may indicate an offset value from the first resource element included in the bandwidth associated with the SRS resource, and the first SRS resource element (RE) will be included in the SRS resource. Thus, the transmit combination parameter in conjunction with the transmit combination offset parameter may indicate a particular resource element index to be associated with the SRS resource.

[0102] The frequency domain shift parameter (e.g., freqDomainShift parameter) may indicate the frequency domain offset of the SRS resource RE relative to the starting position of the corresponding bandwidth part in the frequency domain. The frequency domain position parameter (e.g., freqDomainPosition parameter) may indicate an additional offset in the frequency domain resource block per SRS transmission relative to the offset defined by the frequency domain shift parameter.

[0103] In some examples, frequency hopping may be enabled for SRS transmission. "Frequency hopping" may refer to the UE using different subsets of frequency domain resources for different SRS transmissions within a bandwidth portion associated with an SRS resource set. For example, for a first SRS transmission, the UE may use a first set of frequency domain resources. For a second SRS transmission, the UE may use a second set of frequency domain resources. The first set of frequency domain resources and the second set of frequency domain resources may be included in a bandwidth portion associated with an SRS resource set. A first frequency domain hopping parameter (e.g., a freqHopping.c-SRS parameter) may indicate a configuration row index value associated with an SRS bandwidth configuration table (e.g., a table defined by 3GPP or otherwise fixed). A second frequency domain hopping parameter (e.g., a freqHopping.b-SRS parameter) may indicate a configuration column index value associated with an SRS bandwidth configuration table. The entries of the SRS bandwidth configuration table indicated by the row index value and the column index value may indicate the SRS bandwidth (e.g., for each transmission), the SRS bandwidth position within the bandwidth portion of each SRS transmission, and / or other frequency hopping related parameters. The third frequency-domain frequency hopping parameter (eg, freqHopping.b-hop parameter) may indicate whether frequency hopping is enabled, the number of frequency hopping and / or an offset associated with the frequency hopping, and the like.

[0104] In some examples, partial frequency sounding (PFS) may be enabled (e.g., in addition to SRS frequency hopping being enabled) to improve SRS capacity and / or coverage. For example, in order to improve SRS capacity and enable multiplexing of more SRS ports / UEs, the UE may be configured to detect only a subset of contiguous resource blocks from the configured SRS BW for each SRS transmission or hop. A partial frequency (PF) parameter (e.g., a PartialFrequency.PF parameter) may indicate that the SRS bandwidth indicated by the frequencyHopping.c-SRS parameter and the frequencyHopping.b-SRS parameter will be scaled by a value (e.g., PF), where a value of 1 indicates that partial frequency sounding is disabled. A second parameter (e.g., a PartialFrequency.KF parameter) may indicate the starting sub-hop (or starting RB) of the partial SRS bandwidth per frequency hopping cycle. The starting RB of the SRS PFS may change with the frequency hopping cycle. This enables the UE to detect other RBs across multiple frequency hopping cycles.

[0105] In some examples, a change in a single frequency domain parameter may require a change in other frequency domain parameters. For example, a change in the value or information associated with a transmission combination parameter may require a change or reconfiguration of a transmission combination offset parameter. As another example, a change in a first frequency domain hopping parameter (e.g., a freqHopping.c-SRS parameter) may require a change or reconfiguration of a second frequency domain hopping parameter (e.g., a freqHopping.b-SRS parameter) and / or a third frequency domain hopping parameter (e.g., a freqHopping.b-hop parameter). For example, as described above, multiple frequency domain parameters may be used in combination to indicate frequency domain information associated with an SRS resource. Therefore, modifying and / or reconfiguring frequency domain parameters associated with an SRS resource and / or an SRS resource set may be a cumbersome task.

[0106] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0107] As described above, SRS may be used for uplink channel estimation, which in turn may be used for scheduling, link adaptation, pre-decoder selection, or beam management by a network entity, etc. In some wireless communication systems (such as 5G NR wireless communication systems), a UE may include an increased number of antennas or antenna ports (e.g., compared to deployments of UEs associated with earlier wireless communication systems) to achieve spatial precoding / beamforming and / or increased uplink data capacity, etc. Therefore, SRS transmission may require an increased number of resources (e.g., time domain resources and / or frequency domain resources) because the UE may need to send multiple SRSs to probe a channel associated with each antenna, each antenna element, and / or each antenna panel associated with the UE.

[0108] Additionally, advances in wireless communication technology have enabled increases in cell capacity (e.g., the number of UEs that can be supported in a single cell) and cell coverage (e.g., the geographic area associated with a single cell). As a result, overhead associated with uplink channel estimation and / or SRS signaling has increased. For example, massive MIMO scenarios may be associated with increased overhead associated with uplink channel estimation (e.g., performed by a network entity via SRS uplink transmissions). For example, a network entity may be required to perform uplink channel estimation for multiple UEs (e.g., included in a group associated with coordinated scheduling) simultaneously. Furthermore, enhanced support for UE mobility (e.g., limited quality of service degradation for mobile UEs) may require increasing the rate at which channel estimation or updates are performed by a network entity.

[0109] Therefore, the signaling overhead associated with SRS transmission (e.g., the number of time domain resources and / or frequency domain resources used for SRS transmission) may increase in such wireless communication systems to accommodate an increased number of UE antennas or antenna ports, increased cell capacity, increased cell coverage, and / or enhanced UE mobility support, etc. Therefore, the network (e.g., a network entity) may need to allocate more resources (e.g., time domain resources and / or frequency domain resources) for SRS transmission, which would otherwise be used for other uplink transmissions or downlink transmissions. This may reduce the throughput (or link capacity) associated with the communication between the network (e.g., a network entity) and the UE, or equivalently, the overall cell capacity may be limited due to the increased SRS overhead in the cell. Therefore, an intelligent tradeoff should be managed by the network (e.g., by the network entity) for overall cell capacity optimization.

[0110] Different mobile UE terminals have different speeds, SNRs, channel characteristics, and locations (e.g., located at the cell edge or not at the cell edge) at different times. Channel estimation and tracking (e.g., channel refresh) requirements depend on the UE speed, UE SNR, and the number of layers used for UE transmission. Accordingly, for different UE speeds, SNRs, and channel types, different time domain and / or frequency domain SRS patterns will be required in an ideal situation, so that the overall link quality of the UE will not be limited by the channel estimation and tracking accuracy from one side, and unnecessary SRS allocations that consume uplink resources will be avoided from the other side. Therefore, the SRS resource allocation (e.g., bandwidth, density in the frequency domain, allocation rate / periodicity in the time domain) for the required uplink channel estimation can be based on UE speed, SNR, channel characteristics, and / or UE geographic location (e.g., whether the UE is close to the cell edge), etc. Accordingly, the required SRS allocation and / or SRS signaling overhead associated with uplink channel estimation can be dynamically determined and can change over time for a given UE. Thus, the amount of SRS resources required for a given UE (e.g., that the UE will use to send SRS measured by a network entity for uplink channel estimation) may change over time. Furthermore, the number of UEs within a cell (e.g., communicating with a network entity) may change over time. Thus, different SRS configurations for a network (e.g., corresponding to different SRS overhead levels or thresholds) may be acceptable at different times (e.g., in a scenario where fewer UEs are connected to the network entity, the network entity may configure the connected UEs to send SRS using a higher SRS transmission amount and / or overhead or a larger bandwidth or a higher rate).

[0111] Given the above considerations, in order to be able to obtain the best compromise between SRS overhead and possible capacity increase and / or link quality in the cell (e.g., due to increased SRS transmission volume), it would be beneficial to use a per-UE dynamic SRS mode that is adapted to UE speed, SNR, channel conditions, scheduling scenarios, and NW loading. Therefore, the SRS configuration can be dynamically determined by the network for different UEs over time. However, in some cases, the reconfiguration of one or more SRS resource sets for a UE may be a cumbersome and lengthy procedure. For example, in order to change the configuration of an SRS resource set, a network entity may use an RRC reconfiguration procedure. Dynamic RRC-based SRS reconfiguration (e.g., which is associated with high latency and is not a synchronization procedure between the UE and the network) may not be a suitable option for "on the fly" dynamic reconfiguration.

[0112] For non-periodic SRS resource sets, although the non-periodic SRS resource sets may be dynamically triggered by a network entity (e.g., in a DCI message), the network entity may use RRC reconfiguration between triggering events to change some SRS parameters including time domain and / or frequency domain resources or patterns associated with the non-periodic SRS resource sets, however this introduces scheduling restrictions on the non-periodic SRS during the time period that may be involved in the RRC reconfiguration procedure (e.g., which may be hundreds of milliseconds in some cases). As described above, the RRC reconfiguration procedure is associated with high latency and is not synchronized (e.g., there may be ambiguity as to when the UE and the network entity will switch to using the new configuration indicated by the RRC reconfiguration). Therefore, dynamic RRC reconfiguration of the SRS resource set may not be practical. Therefore, the UE and the network entity may communicate using an SRS resource set associated with a static configuration that is not optimized for current cell conditions or cell loads, scheduling scenarios, channel conditions, and / or UE conditions, etc. This may cause the UE to unnecessarily consume resources (eg, time domain resources and / or frequency domain resources) associated with transmitting SRS using static configurations (including frequency domain pattern configurations) associated with SRS resources and / or SRS resource sets.

[0113] Some techniques and apparatuses described herein implement dynamic adaptation and / or reconfiguration of SRS frequency domain parameters (e.g., configuration parameters associated with indicating a frequency domain pattern for an SRS resource and / or an SRS resource set). In some aspects, a network entity may configure an SRS resource set (e.g., and a corresponding SRS resource) associated with one or more frequency domain parameters for a UE. For example, a network entity may send an SRS configuration associated with an SRS resource and / or an SRS resource set, and the UE may receive the SRS configuration, the SRS configuration indicating information (e.g., values, index values, and / or other information) for a set of one or more frequency domain parameters associated with an SRS resource set (e.g., and a corresponding SRS resource). The network entity may send a message indicating modification information (modification configuration or dynamic reconfiguration), and the UE may receive the message, the modification information being used for a subset of (e.g., one or more) frequency domain parameters associated with at least one SRS resource associated with an SRS resource set from a set of one or more frequency domain parameters (e.g., dynamic reconfiguration of frequency domain parameters may be based on each SRS resource or on each SRS resource set). In other words, the network entity may send a message that dynamically modifies the configuration of one or more frequency domain parameters (e.g., RRC parameters) for an SRS resource set (e.g., and all related SRS resources) and / or for each SRS resource associated with the SRS resource set. The message may be a MAC-CE message or a DCI message, etc. The SRS resource set may be an aperiodic SRS resource set, a periodic SRS resource set, or a semi-persistent SRS resource set.

[0114] Thus, the network entity may be enabled to dynamically adapt or change one or more frequency domain parameters for an SRS resource set over time. For example, the network entity may be enabled to dynamically adapt a frequency domain pattern or density associated with a given SRS resource set (SRS resource). Thus, the network entity and the UE may save resources (e.g., frequency domain resources) that were originally associated with communicating the SRS using SRS resources that do not have a frequency domain configuration optimized for the current cell condition or cell load, scheduling scenario, channel condition, and / or UE condition.

[0115] Figure 6 6 is a diagram of an example 600 associated with dynamic adaptation of SRS frequency domain parameters according to the present disclosure. Figure 6 As shown, a network entity 605 (e.g., base station 110, CU 310, DU 330, and / or RU 340, etc.) may communicate with a UE (e.g., UE 120). In some aspects, the network entity 605 and the UE 120 may be part of a wireless network (e.g., wireless network 100). The UE 120 and the network entity 605 may be in a Figure 6 The operations shown in the figure have already established a wireless connection.

[0116] As indicated by reference numeral 610, the network entity 605 may send configuration information, and the UE 120 may receive the configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC-CEs, and / or DCI, etc. In some aspects, the configuration information may include an indication (e.g., an implicit indication) of one or more configuration parameters for selection by the UE 120 (e.g., stored by the UE 120 and / or previously indicated by the network entity 605 or another network device) and / or explicit configuration information for the UE 120 to configure the UE 120, etc. For example, the DU or CU may determine the configuration information, and the RU may send the configuration information to the UE 120. The DU or CU may send the configuration information to the RU.

[0117] In some aspects, the configuration information may include an SRS configuration. The SRS configuration may configure one or more SRS resource sets (e.g., in a manner similar to that described in more detail elsewhere herein). For example, the SRS configuration may configure an SRS resource set and one or more SRS resources associated with the SRS resource set. The SRS configuration may indicate (e.g., in an SRSResourceSet.Usage information element) a type of use associated with the SRS resource set (e.g., the SRS resource set may be associated with use cases such as antenna switching, codebook, non-codebook, or beam management). Additionally or alternatively, the SRS configuration may indicate that the SRS resource set is a periodic SRS resource set, a semi-persistent SRS resource set, or an aperiodic SRS resource set. The SRS configuration may be an RRC configuration. For example, the network entity 605 may send an indication of the SRS configuration via an RRC message, and the UE 120 may receive an indication of the SRS configuration via an RRC message. In some aspects, the configuration information may be partially indicated by another message. For example, for an aperiodic SRS resource set (and an aperiodic SRS resource included in an SRS resource set), the network entity 605 may send a DCI that triggers the aperiodic SRS resource set, wherein the DCI at least partially indicates the configuration information. Similarly, the configuration information may be partially indicated by a MAC-CE message (e.g., for a semi-persistent SRS resource).

[0118] In some aspects, the configuration information may indicate one or more SRS resource identifiers. For example, the configuration information may indicate one or more SRS resource identifiers in an SRS-ResourceIDList information element. In some aspects, the configuration information may indicate multiple SRS resource identifiers (e.g., for each SRS resource or symbol associated with an SRS resource set). In some other aspects, the configuration information may indicate a single SRS resource identifier associated with multiple SRS symbols.

[0119] The SRS configuration may indicate a time domain configuration and / or a frequency domain configuration associated with an SRS resource set (e.g., and related SRS resources). For example, the SRS configuration may indicate information (e.g., configuration information, values, indexes, and / or code points, etc.) for a set of one or more frequency domain parameters associated with an SRS resource and / or an SRS resource set. The information for a set of one or more frequency domain parameters may indicate a frequency domain configuration and / or a frequency domain mode associated with an SRS resource. For example, the information for a set of one or more frequency domain parameters may indicate a frequency domain resource (e.g., a subchannel or a resource element) to be associated with one or more SRS resources and SRS transmissions. For example, a set of one or more frequency domain parameters may include a transmission combination parameter associated with a frequency domain density (e.g., a transmissionComb RRC parameter), a transmission combination offset parameter (e.g., a combOffsetRRC ​​parameter), a frequency domain shift parameter (e.g., a freqDomainShift RRC parameter), a frequency domain position parameter (e.g., a freqDomainPosition RRC parameter), a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value (e.g., a freqHopping.c-SRS RRC parameter), a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value (e.g., a freqHopping.b-SRS RRC parameter), a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hops, or at least one of an offset associated with frequency hopping (e.g., a freqHopping.b-hop RRC parameter), and / or one or more partial frequency detection parameters (e.g., a PartialFrequency.PF RRC parameter and / or a PartialFrequency.KF RRC parameter), etc. In this manner, the network entity 605 may configure frequency domain information associated with an SRS resource set (eg, and SRS resources associated with the SRS resource set).

[0120] The network entity 605 may determine the SRS configuration. For example, the base station, CU and / or DU may determine the SRS configuration. In some aspects, the network entity 605 may determine the SRS configuration based on at least carrier frequency, subcarrier spacing, deployment type, cell loading, scheduling scenario, UE channel conditions (e.g., SNR, delay spread and / or Doppler parameters), UE channel type, geographic location of UE 120 and / or mobile information associated with UE 120 (e.g., speed of UE 120, acceleration of UE 120 and / or direction of travel of UE 120), etc. In some aspects, the network entity 605 may adaptively determine the SRS configuration to optimize the frequency domain resources used by UE 120 to send SRS based on at least information at or before the time when the SRS configuration is sent to UE 120 (e.g., as described above).

[0121] UE 120 may configure UE 120 based at least on the configuration information. In some aspects, UE 120 may be configured to perform one or more operations described herein based at least on the configuration information.

[0122] In some aspects, the UE 120 may send a capability report and the network entity 605 may receive the capability report. For example, the UE 120 may send a capability report to the RU. The RU may send an indication of the capability report to the DU. In some aspects, the capability report may indicate that the UE supports dynamically adopting configuration parameters for SRS, as described in more detail elsewhere herein. For example, the capability report may indicate that the UE 120 is capable of dynamically adapting information or configuration of one or more frequency domain parameters associated with SRS resources, as described in more detail elsewhere herein. In some aspects, the network entity 605 may dynamically adapt one or more frequency domain parameters based at least on the capability report indicating that the UE 120 supports dynamic adaptation of frequency domain parameters associated with an SRS resource set, as described in more detail elsewhere herein.

[0123] In some aspects (e.g., for aperiodic SRS adaptation), as shown by reference numeral 615, the network entity 605 may send a message to activate one or more SRS triggering states, and the UE 120 may receive the message. For example, the configuration information (e.g., RRC configuration) may configure a set of SRS triggering states. For example, the UE 120 may receive an RRC configuration of multiple SRS triggering states associated with a given SRS resource set (e.g., a given aperiodic SRS resource set) from the network entity 605. The multiple SRS triggering states may be associated with different corresponding configurations of a set of one or more frequency domain parameters for SRS resources linked to the SRS resource set. The UE 120 may receive a MAC-CE message (e.g., synchronization and low latency signaling) to activate one or more SRS triggering states from the network entity 605. The MAC-CE message may indicate an association (e.g., mapping) of one or more SRS triggering states with a code point (e.g., index value) of an SRS request field of a DCI message. In this way, by configuring and dynamically activating or deactivating multiple SRS triggering states associated with the same SRS resource set (e.g., for a non-periodic SRS resource set) but having different configurations for the SRS resource set, the network entity 605 can be enabled to dynamically adapt the frequency domain configuration associated with different triggering events sent for a non-periodic SRS resource set to be used by the UE 120, as explained in more detail elsewhere herein.

[0124] As indicated by reference numeral 620, the network entity 605 may determine a modification to one or more frequency domain parameters associated with the SRS (e.g., to one or more (or all) SRS resources associated with the SRS resource set). For example, the network entity 605 may determine modification information for one or more (or all) frequency domain parameters associated with the SRS resource set from a set of one or more frequency domain parameters. In other words, the network entity 605 may determine a modified configuration or reconfiguration for one or more frequency domain parameters. In some aspects, the network entity 605 may determine a modified frequency domain pattern to be associated with the SRS resource set (e.g., and related SRS resources), a modified SRS bandwidth or bandwidth position within a corresponding BWP to be associated with the SRS, a modified frequency hopping configuration to be associated with the SRS, and / or a modified partial frequency detection configuration to be associated with the SRS, etc.

[0125] In some aspects, the network entity 605 may determine to modify and / or modify the information based at least on some characteristic or information that has changed since the time when the configuration information (e.g., SRS configuration) was sent to the UE 120. For example, the network entity 605 may determine to modify and / or modify the information based at least on a current SNR of a channel between the UE 120 and the network entity 605, a channel type or a channel delay spread characteristic or a channel frequency response characteristic, a speed of the UE 120, a geographic location of the UE 120 (e.g., near a cell edge), an amount of data associated with the UE 120 (e.g., an amount or size of data communicated between the UE 120 and the network entity 605), a number of UEs served by the network entity, and / or a co-scheduling determination (e.g., associated with uplink massive MIMO scenarios), or a scheduling mechanism / scenario for the UE, etc.

[0126] As indicated by reference numeral 625, a network entity 605 (e.g., base station 110 or RU) may send a message indicating modification information for one or more frequency domain parameters associated with SRS resources associated with an SRS resource set from a set of one or more frequency domain parameters, and a UE 120 may receive the message. For example, rather than reconfiguring SRS resources associated with an SRS set via an RRC reconfiguration procedure (e.g., asynchronous and with high latency), the network entity 605 may dynamically adapt information for one or more (or all) frequency domain parameters associated with an SRS resource set (e.g., via dynamically reconfiguring SRS resources), as described in more detail elsewhere herein. One or more frequency domain parameters (e.g., dynamically adapted or modified for a periodic SRS resource set, a semi-persistent SRS resource set, or an aperiodic SRS resource set) may include a transmission combination parameter associated with a frequency domain density (e.g., a transmissionComb RRC parameter), a transmission combination offset parameter (e.g., a combOffset RRC parameter), a frequency domain shift parameter (e.g., a freqDomainShift RRC parameter), a frequency domain position parameter (e.g., a freqDomainPosition RRC parameter), a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value (e.g., a freqHopping.c-SRS RRC parameter), a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value (e.g., a freqHopping.b-SRS RRC parameter), a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hopping, or at least one of an offset associated with frequency hopping (e.g., a freqHopping.b-hop RRC parameter), and / or one or more partial frequency detection parameters (e.g., a PartialFrequency.PF RRC parameter). RRC parameters and / or PartialFrequency.KF RRC parameters), etc.

[0127] In some aspects, when a given frequency domain parameter is modified or adapted, all frequency domain parameters in a subset (e.g., one or more) of frequency domain parameters including the given frequency domain parameter may also be modified or adapted. For example, in some cases, when a given frequency domain parameter is modified or adapted, one or more other frequency domain parameters may also necessarily need to be modified or adapted. A first example subset of one or more frequency domain parameters may include a transmission combination parameter (e.g., a transmissionComb RRC parameter) and a transmission combination offset parameter (e.g., a combOffset RRC parameter). For example, information associated with the frequency domain parameters included in the first example subset may affect the SRS density or pattern in the frequency domain and the specific resource elements occupied by each SRS port within a given resource block. Therefore, the frequency domain parameters included in the first example subset may be dynamically adapted together to ensure that complete information for the SRS density or pattern in the frequency domain and the specific resource elements occupied by each SRS port within a given resource block is provided to the UE 120. In some aspects, a first example subset of one or more frequency domain parameters may include a cyclic shift parameter (e.g., a transmissionComb.cyclicShift RRC parameter).

[0128] Dynamic adaptation, modification and / or reconfiguration of frequency domain parameters included in the first example subset may provide one or more benefits. For example, the network entity 605 may be enabled to dynamically adjust the SRS capacity within the cell. For example, the number of frequency domain multiplexed SRS transmissions may be increased using a higher comb (e.g., a higher value of the transmissionComb RRC parameter) and / or a modified frequency domain density or pattern for various UEs included in the cell. As another example, the network entity 605 may be enabled to reduce the signaling overhead associated with the SRS by dynamically adjusting the SRS resolution or density in the frequency domain for different UEs (e.g., including for UE 120) based at least on channel correlation in the frequency domain or time domain, channel type and / or SNR associated with each UE. For example, the network entity 605 may be enabled to dynamically instruct the UE 120 to use the minimum acceptable SRS resolution or density in the frequency domain (e.g., to allow sufficient SRS-based uplink channel estimation accuracy for a given UE channel and SNR conditions). The released resources (e.g., resources no longer used by UE 120 for SRS transmission) may allow for a higher density of SRS for other UEs that may require a higher SRS density to support higher channel estimation accuracy requirements for these other UEs. The channel and / or SNR characteristics are dynamic in time for each UE, and the dynamic adaptation, modification, and / or reconfiguration of the frequency domain parameters included in the first example subset may enable the network entity 605 to reconfigure the transmissionComb RRC parameter and / or combOffset RRC parameter for different UEs over time as this information changes to optimize or more efficiently distribute the frequency domain resources used by the UE to send SRS.

[0129] For example, if the UE 120 is associated with a channel having lower frequency selectivity, the network entity 605 may indicate that the transmissionComb RRC parameter may be associated with a higher value (e.g., 4, 8, or a higher value), at least until the UE SNR meets the first threshold. In contrast, if the UE 120 is associated with a channel having higher frequency selectivity, the network entity 605 may indicate that the transmissionComb RRC parameter is associated with a lower value (e.g., 2 or another value), at least until the UE SNR meets the second threshold. Additionally, if the UE 120 is associated with a higher SNR value, the uplink channel estimation may be more sensitive to channel frequency interpolation errors or backgrounds that may be introduced, and may affect SRS-based PMI, RI, and / or MCS selection. Therefore, in such examples, a transmissionComb RRC parameter associated with a lower value (e.g., 2 or another value) may be required to efficiently utilize the higher SNR characteristics of the UE link. As another example, if UE 120 is associated with a lower SNR value, UE 120 may be thermal noise limited for SRS processing, and a higher SRS-based channel interpolation error floor may be acceptable, so that UE 120 may be configured with a higher transmissionComb parameter value. In this case (e.g., thermal noise limited scenario), higher SRS transmit power / boost may be used on the relevant resource elements coupled to the higher transmissionComb usage to improve SRS processing gain.

[0130] As another example, a high mobility UE may be more sensitive to channel tracking or interpolation errors in the time domain than channel estimation or interpolation errors in the frequency domain. Therefore, the network entity 605 may balance between the SRS frequency domain resolution / mode (e.g., transmissionComb parameter value) of the SRS resource set and the time domain resolution / mode of the SRS resource set based on UE-specific Doppler, delay spread, and SNR parameters, while also maintaining a constant SRS resource budget per UE to achieve optimal utilization of the SRS capacity associated with the UE 120.

[0131] As another example, the network entity 605 may be enabled to improve SRS coverage by dynamically increasing a value associated with a transmissionComb parameter (e.g., and correspondingly indicating a power boost for each resource element used to transmit SRS). For example, when the UE 120 is located near a cell edge, the network entity 605 may dynamically increase a value associated with the transmissionComb parameter to improve SRS coverage associated with the UE 120. In an example where the UE 120 is thermal noise limited and is not sensitive to the frequency interpolation error background, this may enable the UE 120 to focus SRS energy for channel estimation (e.g., the network entity 605 may dynamically adapt the UE 120 to use lower density resource elements associated with higher transmit power or boost values, rather than relying on channel estimation processing gain from a more densely allocated resource element pattern). As another example, when the UE 120 is located near a cell edge, the network entity 605 may be enabled to reduce SRS interference and / or conflicts between different cells. For example, the network entity 605 may dynamically select and indicate a value of a transmissionComb RRC parameter and / or a combOffset RRC parameter (or a cyclic shift option) to avoid interference and / or conflict with SRS transmissions from neighboring cells. For example, when the UE 120 is located near a cell edge with the second cell, the network entity 605 may dynamically select and indicate a value of a transmissionComb RRC parameter and / or a combOffsetRRC ​​parameter (or a cyclic shift option) such that the UE 120 transmits the SRS using REs different from REs used by the cell edge UEs included in the second cell to transmit the SRS.

[0132] As another example, the network entity 605 may be enabled to reduce inter-carrier interference (ICI) for frequency-domain multiplexed SRS transmissions for two UEs associated with different SNR channel characteristics. For example, ICI caused by a stronger SRS signal (e.g., from a UE associated with a higher SNR channel characteristic) to a weaker SRS signal (e.g., from a UE associated with a lower SNR channel characteristic) may be reduced by selecting appropriate combOffset RRC parameter and / or transmissionComb RRC parameter values ​​for the two UEs. For example, an SRS transmission from a first UE associated with high transmit phase noise (e.g., associated with a higher carrier frequency (such as FR2 or below terahertz frequencies)) or a high frequency offset may result in ICI for an SRS transmission from a second UE associated with a lower SNR value. Thus, the network entity 605 may dynamically adapt the transmissionComb RRC parameter and / or combOffset RRC parameter values ​​for the first UE and the second UE to reduce ICI.

[0133] Dynamic adaptation and / or modification of the frequency domain parameters included in the first example subset can enable higher values ​​(such as 8 or 16) of the transmit combination parameters, which can be applied to SRS resource sets and / or SRS resources associated with any SRS usage type. For example, currently, higher values ​​of the transmit combination parameters can be limited to certain usage types. However, by implementing dynamic adaptation and / or modification of the frequency domain parameters as described herein, higher values ​​can be used for SRS resource sets associated with any SRS usage type.

[0134] A second example subset of one or more frequency domain parameters may include a frequency domain shift parameter (e.g., a freqDomainShift RRC parameter), a frequency domain position parameter (e.g., a freqDomainPosition RRC parameter), a first frequency domain hopping parameter (e.g., a freqHopping.c-SRS RRC parameter), a second frequency domain hopping parameter (e.g., a freqHopping.b-SRS RRC parameter), a third frequency domain hopping parameter (e.g., a freqHopping.b-hop RRC parameter), and one or more partial frequency detection parameters (e.g., a PartialFrequency.PF RRC parameter and / or a PartialFrequency.KF RRC parameter). For example, information associated with the frequency domain parameters included in the second example subset may affect the bandwidth of a given SRS transmission, the range of resource elements associated with a corresponding bandwidth portion associated with the given SRS transmission, and frequency hopping parameterization for the SRS transmission. A third example subset of one or more frequency domain parameters may include a frequency domain position parameter (e.g., a freqDomainPosition RRC parameter), a first frequency domain hopping parameter (e.g., a freqHopping.c-SRS RRC parameter), a second frequency domain hopping parameter (e.g., a freqHopping.b-SRS RRC parameter), and a third frequency domain hopping parameter (e.g., a freqHopping.b-hop RRC parameter). For example, the information indicated by the frequency domain parameters included in the third example subset and / or the fourth example subset may indicate in combination the resource elements to be associated with a given SRS transmission. Therefore, it may be necessary to dynamically adapt and / or reconfigure a subset of parameters together.

[0135] A fourth example subset of one or more frequency domain parameters may include a frequency domain shift parameter (e.g., a freqDomainShift RRC parameter). For example, in some cases, the frequency domain shift parameter may be independently dynamically adapted or reconfigured. A fifth example subset of one or more frequency domain parameters may include a first frequency domain frequency hopping parameter (e.g., a freqHopping.c-SRS RRC parameter), a second frequency domain frequency hopping parameter (e.g., a freqHopping.b-SRS RRC parameter), and a PartialFrequency.PF RRC parameter. For example, any change in the parameters included in the fifth example subset may also affect the location of a given SRS transmission (e.g., in the frequency domain), and may affect frequency hopping applicability (e.g., whether frequency hopping is enabled or disabled) and frequency hopping-related parameters. A sixth example subset of one or more frequency domain parameters may include one or more partial frequency detection parameters (e.g., a PartialFrequency.PF RRC parameter and / or a PartialFrequency.KF RRC parameter). For example, parameters associated with partial frequency detection may be dynamically adapted and / or reconfigured together.

[0136] Dynamic adaptation, modification and / or reconfiguration of frequency domain parameters included in the second example subset, the third example subset, the fourth example subset, the fifth example subset and / or the sixth example subset can provide one or more benefits. For example, the network entity 605 can be enabled to dynamically select a subband for downlink and / or uplink allocation for the UE 120 (e.g., and correspondingly select related SRS transmissions, such as for antenna switching use cases, non-codebook use cases and / or codebook use cases). For example, the network entity 605 can identify a resource element subband or range based at least on a subband (SB) channel state feedback (CSF) report sent by the UE 120. For example, the network entity 605 can dynamically increase or decrease the bandwidth associated with the SRS transmission or change the bandwidth position associated with the SRS transmission by dynamically adapting the parameters included in the second example subset, the third example subset, the fourth example subset, the fifth example subset and / or the sixth example subset. Dynamic subband selection can improve the scheduling and / or interference mitigation operations performed by the network entity 605.

[0137] As another example, modification and / or reconfiguration of frequency domain parameters included in the second example subset, the third example subset, the fourth example subset, the fifth example subset, and / or the sixth example subset can enable dynamic selection of an SRS bandwidth for a given SRS transmission and / or a total frequency range associated with SRS frequency hopping. For example, a UE located at a cell edge or with limited available transmit power can be dynamically adapted to use a smaller SRS bandwidth for a given SRS transmission (e.g., to focus transmit power on a smaller frequency range) and use frequency hopping to cover a wider or required bandwidth across the frequency hopping period (e.g., to improve the SNR on the resource elements used to transmit the SRS for each frequency hop). Alternatively, a UE with a better SNR value and / or with more available uplink transmit power can be dynamically adapted to use a larger bandwidth and not use frequency hopping (e.g., to reduce SRS periodicity and / or increase the SRS-based channel tracking rate).

[0138] As another example, modification and / or reconfiguration of frequency domain parameters included in the second example subset, the third example subset, the fourth example subset, the fifth example subset, and / or the sixth example subset may enable the network entity 605 to dynamically indicate different frequency hopping parameter values ​​and / or dynamically enable or disable frequency hopping for a given SRS resource set. For example, different frequency hopping parameters may be used for SRS resource sets based on UE mobility to adjust the rate of channel refresh / tracking over a fully correlated channel bandwidth (e.g., a lower number of frequency hopping or no frequency hopping will effectively increase the rate of channel refresh). As another example, modification and / or reconfiguration of frequency domain parameters included in the second example subset, the third example subset, the fourth example subset, the fifth example subset, and / or the sixth example subset may enable the network entity 605 to dynamically adapt the SRS bandwidth, subband, and / or frequency hopping usage for SRS-based Doppler tracking according to UE uplink channel flatness. For example, in the case where UE 120 is associated with a relatively flat channel, UE 120 may use a smaller bandwidth for Doppler tracking SRS transmissions. In other cases where UE 120 is associated with a more frequency selective channel, UE 120 may use a larger bandwidth for Doppler tracking SRS transmissions.

[0139] In some aspects, a message (e.g., indicating modification information for one or more frequency domain parameters) may be included in a MAC-CE message. For example, the network entity 605 may use MAC-CE-based reconfiguration of frequency domain parameters for an SRS resource set and / or for SRS resources included in an SRS resource set (e.g., for a periodic SRS resource set, a semi-persistent SRS resource set, or an aperiodic SRS resource set). The information indicated by the MAC-CE message may be applicable to all SRS resources associated with the SRS resource set (e.g., the reconfiguration may be performed per SRS resource set identifier and may be applicable to all SRS resources listed under the indicated SRS resource set identifier). In some aspects, the UE 120 and / or the network entity 605 may apply the information indicated by the MAC-CE message a certain number of time slots (e.g., N time slots) after the UE sends a corresponding acknowledgment message (ACK) message associated with the MAC-CE message. For example, as shown by reference numeral 630, UE 120 may send an ACK message associated with a message indicating that a communication (e.g., a PDSCH) associated with a MAC-CE message was successfully decoded by UE 120. UE 120 and / or network entity 605 may apply modification information for one or more frequency-domain parameters for an SRS resource set a certain number (e.g., N) of time slots after the time slot in which the ACK message was sent. In some aspects, the information indicated by the MAC-CE message may apply to one or more activated SRS resource sets (or SRS resources) and one or more inactivated SRS resource sets (or SRS resources).

[0140] In some aspects, the MAC-CE message indicates modification information for one or more frequency domain parameters. In other words, the MAC-CE message may explicitly indicate modification information for one or more frequency domain parameters for an SRS resource set. In some other aspects, the MAC-CE message may implicitly indicate modification information for one or more frequency domain parameters for an SRS resource set. For example, the UE 120 may receive (e.g., in an RRC configuration and / or via configuration information) an indication of one or more information sets for one or more frequency domain parameters associated with an SRS resource set. In other words, the network entity 605 may configure one or more options for information associated with a frequency domain parameter associated with an SRS resource set (e.g., several configuration options per SRS resource or SRS resource set identifier may be listed or pre-configured by the RRC configuration). The MAC-CE message may indicate or activate an information set (e.g., a set or option from an RRC configuration) for one or more frequency domain parameters associated with an SRS resource set.

[0141] For example, a MAC-CE message may activate an information set from one or more information sets, wherein the information set includes modification information about a currently activated or semi-statically configured information set for an SRS resource set. In some aspects, one of the SRS configuration options for each SRS resource or SRS resource set identifier may be dynamically activated, selected, or indicated by a MAC-CE message. The indicated option may become the active or used SRS configuration for the associated (indicated by MAC-CE) SRS resource or SRS resource set until the next MAC-CE reactivation or indication. As described above, the UE 120 and / or the network entity 605 may apply information of frequency domain parameters indicated by the information set activated by the MAC-CE message N time slots after the time slot in which the UE 120 sends an ACK message associated with the PDSCH allocation carrying the MAC-CE message (e.g., as described in conjunction with reference number 630).

[0142] In some aspects, at least one information set or option for frequency domain parameters of the SRS resource set may be defined by a wireless communication standard (such as 3GPP) or otherwise fixed. For example, at least one of the one or more information sets may be defined by the wireless communication standard as a default configuration option applicable prior to any activation MAC-CE message (e.g., to be used by the UE 120 prior to receiving a first MAC-CE message indicating which information set from the RRC configured options the UE 120 will use).

[0143] For example, the network entity 605 may indicate a first configuration option, a second configuration option, and a third configuration option for a given SRS resource set. The first configuration option may indicate that a value of 8 (e.g., comb8) for a transmissionComb RRC parameter, a first SRS bandwidth, and frequency hopping are enabled. The second configuration option may indicate that a value of 2 (e.g., comb2) for a transmissionComb RRC parameter, a second SRS bandwidth, and frequency hopping are disabled. The third configuration option may indicate that a value of 4 (e.g., comb4) for a transmissionComb RRC parameter, a third SRS bandwidth, and frequency hopping are enabled. The second SRS bandwidth may be greater than the third SRS bandwidth, and the third SRS bandwidth may be greater than the first SRS bandwidth. The network entity may activate (e.g., via a MAC-CE message) different configuration options for a given SRS resource set in different situations. For example, the network entity 605 may activate the first configuration option in a low SNR scenario. The network entity 605 may activate the second configuration option in a high SNR scenario, a high delay spread scenario, and / or a scenario where the UE 120 is mobile. The network entity 605 may activate the third configuration option in high SNR scenarios, high delay spread scenarios, and / or scenarios where the UE 120 is less mobile. In this way, the size of the MAC-CE message may be reduced (e.g., because the network entity may only need to indicate the configured options, rather than all information for frequency domain parameters), while still enabling the network entity 605 to dynamically adapt the frequency domain parameters for the SRS resource set.

[0144] In some other aspects, a message (e.g., indicating modification information for one or more frequency domain parameters) may be included in a DCI message. In some aspects, a message is included in a DCI message that is not associated with a data transmission schedule (e.g., a DCI message that does not schedule data transmission). A DCI message that is not associated with a data transmission schedule may also be referred to as a "dummy DCI". In some aspects, a DCI message may be associated with a DCI format 1_1 or a DCI format 1_2 (e.g., as defined by 3GPP or otherwise fixed). For example, a non-data-scheduled DCI (e.g., using DCI format 1_1 or DCI format 1_2) may be used to indicate information about one or more frequency domain parameters for an SRS resource set. In some other aspects, a non-data-scheduled DCI message may be associated with a dedicated DCI format that is associated with modifying SRS configuration parameters. For example, a DCI format associated with dynamic SRS parameter adaptation may be defined (e.g., by a wireless communication standard such as 3GPP).

[0145] In some aspects, the non-data scheduling DCI message may indicate modification information for one or more frequency domain parameters (e.g., in an explicit manner that the DCI message includes the modification information). In some other aspects, the DCI message may implicitly indicate modification information for one or more frequency domain parameters. For example, a table with SRS configuration parameters may be indicated by the network entity 605 (e.g., in an RRC configuration) and / or may be defined by a wireless communication standard (such as 3GPP). The DCI message may indicate an identifier (e.g., a row index and / or a column index) of the table to indicate modification information for one or more frequency domain parameters. The UE 120 may identify modification information for one or more frequency domain parameters based at least on the identifier and information indicated by the table.

[0146] The modification information for one or more frequency domain parameters indicated by the DCI message may be associated with all SRS resources associated with the SRS resource set (e.g., may refer to a specific SRS resource set identifier). The UE 120 may confirm the receipt of the modification information (e.g., reconfiguration) associated with the SRS resource set via an ACK message associated with the non-data scheduling DCI message. For example, as shown by reference numeral 630, the UE 120 may send a corresponding ACK message indicating that the DCI message was successfully decoded by the UE 120 (e.g., instead of indicating that the corresponding scheduled PDSCH allocation was successfully decoded by the UE, and other situations may also exist). The UE 120 and / or the network entity 605 may apply the modification information for one or more frequency domain parameters for the SRS resource set a certain number of time slots (e.g., M time slots) after the time slot in which the UE 120 sends the ACK message. The modification information may overwrite the current RRC configuration of the one or more frequency domain parameters. The modification information indicated by the non-data scheduling DCI message may be associated with one or more active SRS resource sets and / or one or more inactive (eg, unactivated) SP SRS resources and / or SRS resource sets.

[0147] In some aspects, for dynamic adaptation of frequency domain parameters for aperiodic SRS resource sets, a message may be included in a DCI message that schedules the transmission of aperiodic SRS resource sets. For example, the dynamic adaptation of frequency domain parameters for aperiodic SRS resource sets may be coupled with aperiodic SRS resource set triggering procedure (e.g., may be performed in accordance with aperiodic SRS scheduling event). For example, a DCI message may schedule the transmission of aperiodic SRS resource sets by indicating an SRS triggering state associated with or mapped to aperiodic SRS resource sets in an SRS request field of the DCI. In some aspects, the DCI message does not schedule any UL data communication (e.g., the DCI message may be a dummy DCI). For example, a DCI message may be associated with a non-PUSCH scheduling format (e.g., a dummy DCI of format 0_1 ​​or format 0_2 as defined by 3GPP).

[0148] For example, the DCI message may schedule a non-periodic SRS resource set (e.g., one or more non-periodic SRS resource sets may be scheduled) via the SRS triggering state indicated by the SRS request field. Additionally, the DCI message may indicate modification information for one or more frequency domain parameters for the non-periodic SRS resource set via one or more other fields of the DCI message. For example, one or more fields of the non-PUSCH scheduling format may be used to (e.g., explicitly or implicitly) indicate dynamic information for one or more frequency domain parameters. For example, a table with SRS configuration parameters may be indicated by the network entity 605 (e.g., in an RRC configuration) and / or may be defined by a wireless communication standard (such as 3GPP). The DCI message may indicate an identifier (e.g., a row index and / or a column index) of a table (e.g., in one or more other fields of the DCI message) to implicitly indicate modification information for one or more frequency domain parameters. For example, the DCI message may indicate one or more indexes associated with a data structure including a plurality of SRS configuration options, and the one or more indexes correspond to the modification information. UE 120 may identify modification information for one or more frequency domain parameters based at least on the identifier and the information indicated by the table.Alternatively, one or more other fields may indicate explicit information for one or more frequency domain parameters.

[0149] The information indicated by the non-PUSCH scheduling DCI message sent by the scheduling non-periodic SRS resource set may be applied to all SRS resources associated with the non-periodic SRS resource set. In some aspects, the SRS trigger state scheduling (e.g., indicated by the SRS request field of the DCI message) includes multiple non-periodic SRS resource sets of the non-periodic SRS resource set. In some aspects, the DCI message indicates corresponding modification information for one or more frequency domain parameters for each of the multiple triggered non-periodic SRS resource sets. For example, information for frequency domain parameters may be separately indicated for each of the triggered or scheduled SRS resource set identifiers. Alternatively, modification information for one or more frequency domain parameters may be associated with each non-periodic SRS resource set in multiple non-periodic SRS resource sets. For example, information for frequency domain parameters may be collectively indicated for all triggered or scheduled non-periodic SRS resource set identifiers. For example, a single information set for frequency domain parameters may be applicable to all triggered or scheduled non-periodic SRS resource set identifiers.

[0150] In some other aspects, the DCI message scheduling the non-periodic SRS resource set may schedule one or more data communications. For example, the DCI message may be a PUSCH or PDSCH scheduled DCI message (e.g., using DCI format 0_1, DCI format 0_2, DCI format 1_1, or DCI format 1_2, etc.). As described above in conjunction with reference numeral 615, UE 120 may receive an RRC configuration of multiple SRS triggering states associated with an SRS resource set, wherein the multiple SRS triggering states are associated with different corresponding configurations of a set of one or more frequency domain parameters for the SRS resource set. In other words, multiple SRS triggering states may be configured for the same non-periodic SRS resource set, wherein each of the multiple SRS triggering states is associated with a different frequency domain configuration for the same non-periodic SRS resource set. Because the DCI message may schedule one or more data communications, additional fields in the DCI may not be available for indicating information for one or more frequency domain parameters (e.g., contrary to the case of non-data scheduled DCI messages). Thus, the network entity 605 may configure several frequency domain configuration options for the same SRS resource set via the SRS triggering state to provide additional flexibility to dynamically adapt or modify the frequency domain allocation, density, and / or pattern associated with the SRS resource set. The DCI message may indicate a triggered SRS triggering state associated with information or a modified configuration of one or more frequency domain parameters for a non-periodic SRS resource set (e.g., determined by the network entity, as described in conjunction with reference numeral 620) from multiple SRS triggering states. For example, the SRS configuration option indicated via the scheduled SRS triggering state may override the RRC configuration (e.g., SRS configuration) for the triggered SRS resource or SRS resource set (e.g., the non-periodic SRS may be dynamically reconfigured according to a scheduling event).

[0151] For example, referring to the above example including the first configuration option, the second configuration option, and the third configuration option, the first code point (e.g., 01) may be mapped to the SRS resource set and the first configuration option, the second code point (e.g., 10) may be mapped to the SRS resource set and the second configuration option, and the third code point (e.g., 11) may be mapped to the SRS resource set and the third configuration option. The network entity 605 may indicate different code points in the SRS request field of the DCI message to dynamically adapt the frequency domain configuration of a given non-periodic SRS resource set according to a scheduling event.

[0152] As described above in conjunction with reference numeral 615, in some cases, the network entity 605 may activate one or more SRS triggering states from a larger number of RRC configured SRS triggering states (e.g., to reduce the number of activated triggering states). The DCI message may indicate the SRS triggering states from the list of activated SRS triggering states. For example, activating a subset of the configured SRS triggering states may enable a smaller size of the SRS request field, or may enable maintaining the currently used SRS request field size while also enabling configuration and dynamic activation or deactivation of additional SRS triggering states to allow dynamic SRS configuration adaptation by the network entity 605.

[0153] Alternatively, the field of the extended or modified format data scheduling DCI message may indicate an index associated with a frequency domain configuration and / or one or more frequency domain parameters associated with a non-periodic SRS resource set. For example, the field may explicitly indicate an index of a frequency domain configuration and / or one or more frequency domain parameters associated with a non-periodic SRS resource set for a triggered or scheduled non-periodic SRS resource set. The field may be a bit field. In some aspects, the field may have a size of log2(K), where K is the number (e.g., maximum number) of SRS configurations that will be dynamically signaled for an SRS resource / SRS resource set.

[0154] In some aspects, as shown by reference numeral 630, the UE 120 may send an ACK message associated with a message indicating modified and / or reconfigured frequency domain resource parameters for an SRS resource set, and the network entity 605 may receive the ACK message. For example, the ACK message may be associated with a PDSCH allocation (e.g., which carries a MAC-CE message). As described herein, the ACK message may be associated with a DCI message. The ACK message may indicate whether the message indicating modified and / or reconfigured frequency domain resource parameters for an SRS resource set was successfully received and / or decoded by the UE 120.

[0155] In some aspects, the UE 120 and / or the network entity 605 may apply the modified and / or reconfigured frequency-domain resource parameters for the SRS resource set a number of time slots (e.g., N time slots or M time slots) after the UE 120 sends the ACK message. Alternatively, the UE 120 and / or the network entity 605 may apply the modified and / or reconfigured frequency-domain resource parameters for the SRS resource set a number of time slots after the network entity 605 sends a message indicating the modified and / or reconfigured frequency-domain resource parameters for the SRS resource set.

[0156] As indicated by reference numeral 635, the UE 120 may send one or more SRS using the modified or reconfigured information (reconfiguration) for one or more frequency domain parameters, and the network entity 605 may receive the one or more SRS. For example, the UE 120 may send the SRS using one or more SRS resources included in the SRS resource set according to the modified information for one or more frequency domain parameters.

[0157] Therefore, the network entity 605 can be enabled to dynamically adapt or change one or more frequency domain parameters for the SRS resource set over time. For example, the network entity 605 can be enabled to dynamically adapt the frequency domain pattern or density associated with a given SRS resource set. Therefore, the network entity 605 and the UE 120 can save resources (e.g., frequency domain resources) that were originally associated with using SRS resources that do not have frequency domain configurations optimized for the current cell conditions, UE channel conditions, and / or UE conditions to convey SRS. Additionally, the network entity 605 can dynamically adapt the SRS capacity (e.g., by multiplexing more or less SRS resources in the frequency domain) to serve additional UEs in the cell while maintaining the fixed SRS overhead in the cell. As another example, the RRC signaling overhead can be reduced because the SRS resources may not require RRC reconfiguration to adapt or adjust the frequency domain parameters of the SRS resource set. In addition, the network entity 605 can improve SRS coverage (e.g., for mobile UEs, UEs near the cell edge, or UEs associated with low SNR conditions). Dynamic adaptation of frequency domain parameters for SRS resources may be associated with additional benefits as described in more detail elsewhere herein.

[0158] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0159] Figure 7 700 is a diagram of an example associated with a communication timeline for dynamic adaptation of SRS frequency domain parameters according to the present disclosure. As shown by reference numeral 705, UE 120 may transmit SRS using a first frequency domain configuration. For example, UE 120 may transmit SRS using information for a set of one or more frequency domain parameters associated with an SRS resource set. The information for the set of one or more frequency domain parameters may be indicated by an RRC configuration in a manner similar to that described elsewhere herein.

[0160] As shown by reference numeral 710, UE 120 may receive a message indicating dynamic reconfiguration of one or more frequency domain parameters associated with an SRS resource set. For example, the message may indicate modification information (e.g., from an RRC configuration modification) for one or more frequency domain parameters. UE 120 may use the same method as described elsewhere herein (such as in conjunction with Figure 6 UE 120 may receive the message in a manner similar to that described in more detail in the embodiments of the present invention and / or reference numeral 625. For example, as described above, the message may be a MAC-CE message or a DCI message. As shown by reference numeral 715, UE 120 may send an ACK message associated with the message indicating the dynamic reconfiguration of one or more frequency domain parameters associated with the SRS resource set (e.g., in conjunction with the ACK message). Figure 6 and / or in a manner similar to that described with reference numeral 630). For example, the ACK message may be associated with a PDSCH allocation associated with a MAC-CE message. As another example, the ACK message may be used to confirm reconfiguration and / or reception of a DCI message.

[0161] As shown by reference numeral 720, a certain number of time slots (e.g., N time slots or M time slots) after sending an ACK message or receiving a message indicating a dynamic reconfiguration of one or more frequency domain parameters, both the UE 120 and the network may apply the reconfiguration of one or more frequency domain parameters for the SRS resource set in a synchronized manner. For example, as shown by reference numeral 725, before the time indicated by the certain number of time slots, the UE 120 may use a first frequency domain configuration to send an SRS associated with the SRS resource set. As shown by reference numeral 730, after the time indicated by the certain number of time slots, the UE 120 may use a second frequency domain configuration to send an SRS associated with the SRS resource set. For example, as shown by reference numeral 735, the UE 120 may use a second frequency domain configuration (e.g., indicated by the message shown by reference numeral 710) to send an SRS associated with the SRS resource set.

[0162] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0163] Figure 8 8 is a diagram of an example 800 associated with a communication timeline for dynamic adaptation of SRS frequency domain parameters according to the present disclosure. Example 800 may be associated with an aperiodic SRS resource set. For example, in contrast, example 700 described above may be associated with a periodic SRS resource set, a semi-persistent SRS resource set, and an aperiodic SRS resource set.

[0164] As shown by reference numeral 805, UE 120 may receive a first DCI message that schedules a non-periodic SRS resource set (e.g., Figure 8 The first DCI message may indicate a first frequency domain configuration for a non-periodic SRS resource set (e.g., in conjunction with other places in this document (such as in conjunction with Figure 6 UE 120 may transmit one or more SRSs associated with a non-periodic SRS resource set scheduled by the first DCI message and used on the first frequency domain configuration.

[0165] As shown by reference numeral 810, UE 120 may receive a second DCI message that schedules a non-periodic SRS resource set (eg, Figure 8 The second DCI message may indicate a second frequency domain configuration for the aperiodic SRS resource set (e.g., in conjunction with other places herein (such as in conjunction with Figure 6 8 and / or in a manner similar to that described in more detail by reference numeral 625). For example, the second DCI message may include explicit information for one or more frequency domain parameters that is different from information for one or more frequency domain parameters indicated by the first DCI message. As another example, the second DCI message may indicate an SRS triggering state associated with an aperiodic SRS resource set that is different from the SRS triggering state associated with the aperiodic SRS resource set indicated by the first DCI message. UE 120 may send one or more SRS associated with an aperiodic SRS resource set scheduled by the second DCI message and used on the first frequency domain configuration.

[0166] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0167] Fig. 9 is a diagram of an example 900 associated with SRS trigger state configuration and activation for dynamic adaptation of SRS frequency domain parameters according to the present disclosure. Fig. 9 As shown, the network entity may configure a set of SRS triggering states (e.g., in an RRC configuration). For example, the network entity may configure a first triggering state associated with a first group (e.g., one or more) of SRS resource set identifiers and a second triggering state associated with a second group (e.g., one or more) of SRS resource set identifiers. Fig. 9As shown, the network entity may configure multiple (e.g., L) triggering states associated with a third group of SRS resource set identifiers, which may be adapted for dynamic configuration. For example, a first SRS triggering state associated with a third group of SRS resource set identifiers may be associated with a first frequency domain configuration (e.g., first information for a set of one or more frequency domain parameters), a second SRS triggering state associated with a third group of SRS resource set identifiers may be associated with a second frequency domain configuration (e.g., second information for a set of one or more frequency domain parameters), and an Lth SRS triggering state associated with a third group of SRS resource set identifiers may be associated with an Lth frequency domain configuration (e.g., Lth information for a set of one or more frequency domain parameters). The network entity may configure additional SRS triggering states associated with other groups of SRS resource set identifiers in a similar manner.

[0168] As indicated by reference numeral 905, the network entity may dynamically map or associate one or more of the configured SRS triggering states to a DCI field value (e.g., a code point associated with an SRS request field of the DCI). For example, the network entity may send a MAC-CE message indicating a corresponding mapping or association of one or more SRS triggering state activation / deactivation and activated triggering states with corresponding DCI field code points, and the UE 120 may receive the MAC-CE message. Fig. 9 As shown, the network entity may activate a first trigger state associated with a first group of SRS resource set identifiers and map it to a first code point (e.g., 01), may activate a second trigger state associated with a second group of SRS resource set identifiers and may map the second trigger state to a second code point (e.g., 10), and may also activate an Lth SRS trigger state and its Lth configuration option associated with a third group of SRS resource identifiers, and may map the Lth SRS trigger state to a third code point (e.g., 11). Different RRC configured SRS trigger states may be dynamically activated or deactivated by the network (e.g., by the network entity) over time. For example, the network entity may be enabled to dynamically adjust the frequency domain configuration options (from the L configuration options) for activation of the third group of SRS resource set identifiers by adjusting which (which) SRS trigger states from the configured SRS trigger state set associated with the third group of SRS resource set identifiers are active or mapped to DCI field values. In this way, a network entity may be enabled to configure multiple SRS triggering states, thereby providing flexibility and multiple configuration options for a given SRS resource set, while also minimizing the required size of a DCI field (eg, SRS request field) or maintaining a predefined size of the DCI field.

[0169] As indicated above, Fig. 9are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0170] Fig.10 is a diagram illustrating an example process 1000, performed, for example, by a first network node, according to the present disclosure. Example process 1000 is an example in which a first network node (eg, UE 120 or another network node) performs operations associated with dynamic adaptation of SRS frequency domain parameters.

[0171] like Fig.10 As shown, in some aspects, process 1000 may include receiving, from a second network node, an SRS configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set (block 1010). Fig.12 The communication manager 140 and / or receiving component 1202 depicted in the figure can receive an SRS configuration associated with an SRS resource set including one or more SRS resources from a second network node, the SRS configuration indicating information of a set of one or more frequency domain parameters associated with the SRS resource set, as described above.

[0172] like Fig.10 As further shown, in some aspects, process 1000 may include receiving a message from a second network node indicating modification information for dynamically reconfiguring one or more frequency domain parameters associated with at least one of the one or more SRS resources from a set of one or more frequency domain parameters (block 1020). Fig.12 The communication manager 140 and / or receiving component 1202 depicted in the figure can receive a message indicating modification information from a second network node, wherein the modification information is used to dynamically reconfigure one or more frequency domain parameters associated with at least one SRS resource of one or more SRS resources from a set of one or more frequency domain parameters, as described above.

[0173] like Fig.10 As further shown, in some aspects, process 1000 may include sending an SRS to a second network node using at least one SRS resource based on modification information for one or more frequency domain parameters (block 1030). Fig.12 The communication manager 140 and / or the sending component 1204) depicted in FIG. 1 may send an SRS to a second network node using at least one SRS resource based on modification information for one or more frequency domain parameters, as described above.

[0174] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0175] In a first aspect, a set of one or more frequency domain parameters includes at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0176] In a second aspect, alone or in combination with the first aspect, the set of one or more frequency domain parameters includes one or more RRC configuration parameters.

[0177] In the third aspect, alone or in combination with one or more of the first and second aspects, the set of one or more frequency domain parameters includes at least one of the following: a transmit combination parameter associated with frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0178] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the set of one or more frequency domain parameters includes a transmit combination parameter and a transmit combination offset parameter associated with the frequency domain density.

[0179] In the fifth aspect, alone or in combination with one or more aspects from the first to the fourth aspects, the set of one or more frequency domain parameters includes a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth index value, a second frequency domain hopping parameter associated with an SRS bandwidth column index value, and a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping.

[0180] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message is included in a MAC-CE message.

[0181] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a MAC-CE message indicates modification information for one or more frequency domain parameters.

[0182] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the modification information is associated with all SRS resources associated with the SRS resource set.

[0183] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the modification information is associated with one or more inactivated SRS resource sets.

[0184] In a tenth aspect, alone or in combination with one or more of aspects 1 to 9, process 1000 includes: sending an ACK message to a second network node during a time slot, the ACK message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node; and applying modification information for one or more frequency domain parameters for at least one SRS resource a certain number of time slots after the time slot.

[0185] In the eleventh aspect, alone or in combination with one or more aspects of the first to tenth aspects, process 1000 includes receiving one or more information sets for one or more frequency domain parameters associated with an SRS resource set, and a MAC-CE message activates an information set from the one or more information sets, and the information set includes modification information about a currently activated or semi-statically configured information set for at least one SRS resource.

[0186] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation of a MAC-CE message.

[0187] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the message is included in a DCI message not associated with a data transmission schedule.

[0188] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the DCI message is associated with DCI format 1_1 or 1_2.

[0189] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the DCI message indicates modification information for one or more frequency domain parameters.

[0190] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the modification information is associated with all SRS resources associated with the SRS resource set.

[0191] In the seventeenth aspect, alone or in combination with one or more aspects of the first to sixteenth aspects, process 1000 includes: sending an ACK message to the second network node during a time slot, the ACK message indicating that the DCI message has been successfully decoded by the first network node; and applying modification information for one or more frequency domain parameters for at least one SRS resource a certain number of time slots after the time slot.

[0192] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the DCI message is associated with a DCI format associated with modifying an SRS configuration parameter.

[0193] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the SRS resource set is a non-periodic SRS resource set, and the message is included in a DCI message scheduling the transmission of the non-periodic SRS resource set.

[0194] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the DCI message does not schedule any data communication.

[0195] In aspect 21, alone or in combination with one or more aspects from aspect 1 to aspect 20, a DCI message schedules a non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and the DCI message indicates modification information for one or more frequency domain parameters via one or more other fields of the DCI message.

[0196] In aspect twenty-second, alone or in combination with one or more aspects from aspect one to aspect twenty-first, the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of non-periodic SRS resource sets, and the DCI message indicates corresponding modification information for one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0197] In the twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of non-periodic SRS resource sets, and modification information for one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0198] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the DCI message includes modification information.

[0199] In a twenty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, the DCI message indicates one or more indexes associated with a data structure including a plurality of SRS configuration options, and the one or more indexes correspond to modification information.

[0200] In a twenty-sixth aspect, alone or in combination with one or more of the first to twenty-fifth aspects, a DCI message schedules one or more data communications.

[0201] In the twenty-seventh aspect, alone or in combination with one or more of aspects one to twenty-six, process 1000 includes receiving an RRC configuration of multiple SRS triggering states associated with an SRS resource set from a second network node, wherein the multiple SRS triggering states are associated with different corresponding configurations of a set of one or more frequency domain parameters for at least one SRS resource, and the DCI message indicates a triggered SRS triggering state from the multiple SRS triggering states associated with modification information for one or more frequency domain parameters.

[0202] In the twenty-eighth aspect, alone or in combination with one or more of aspects one to twenty-seven, process 1000 includes receiving a MAC-CE message from a second network node that activates one or more SRS triggering states including an SRS triggering state, wherein the MAC-CE message indicates an association of the one or more SRS triggering states with a code point of an SRS request field of a DCI message.

[0203] In a twenty-ninth aspect, alone or in combination with one or more of the first to twenty-eighth aspects, the SRS resource set is a periodic SRS resource set, a semi-persistent SRS resource set, or an aperiodic SRS resource set.

[0204] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted in the process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0205] Fig.111 is a diagram illustrating an example process 1100 performed, for example, by a first network node according to the present disclosure. Example process 1100 is an example in which a first network node (e.g., base station 110, network entity 605, CU, DU, and / or RU) performs operations associated with dynamic adaptation of SRS frequency domain parameters.

[0206] like Fig.11 As shown, in some aspects, process 1100 may include sending an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set (block 1110). Fig.13 The communication manager 150 and / or sending component 1304 depicted in the figure can send an SRS configuration associated with an SRS resource set including one or more SRS resources to a second network node, and the SRS configuration indicates information about a set of one or more frequency domain parameters associated with the SRS resource set, as described above.

[0207] like Fig.11 As further shown, in some aspects, process 1100 may include sending a message to a second network node indicating modification information for dynamically reconfiguring one or more frequency domain parameters associated with at least one of the one or more SRS resources from a set of one or more frequency domain parameters (block 1120). Fig.13 The communication manager 150 and / or sending component 1304 depicted in the figure can send a message indicating modification information to the second network node, wherein the modification information is used to dynamically reconfigure one or more frequency domain parameters associated with at least one SRS resource among the one or more SRS resources from a set of one or more frequency domain parameters, as described above.

[0208] like Fig.11 As further shown, in some aspects, process 1100 may include receiving an SRS from a second network node using at least one SRS resource based on modification information for one or more frequency domain parameters (block 1130). Fig.13 The communication manager 150 and / or receiving component 1302 depicted in the figure can receive an SRS from a second network node using at least one SRS resource based on the modification information for one or more frequency domain parameters, as described above.

[0209] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0210] In a first aspect, a set of one or more frequency domain parameters includes at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0211] In a second aspect, alone or in combination with the first aspect, the set of one or more frequency domain parameters includes one or more radio resource control (RRC) configuration parameters.

[0212] In the third aspect, alone or in combination with one or more of the first and second aspects, the one or more frequency domain parameters include at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0213] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the one or more frequency domain parameters include a transmit combination parameter and a transmit combination offset parameter associated with the frequency domain density.

[0214] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the one or more frequency domain parameters include a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth index value, a second frequency domain hopping parameter associated with an SRS bandwidth column index value, and a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping.

[0215] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the message is included in a MAC-CE message.

[0216] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a MAC-CE message indicates modification information for one or more frequency domain parameters.

[0217] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the modification information is associated with all SRS resources associated with the SRS resource set.

[0218] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the modification information is associated with one or more inactivated SRS resource sets.

[0219] In a tenth aspect, alone or in combination with one or more of aspects 1 to 9, process 1100 includes: receiving an ACK message from a second network node during a time slot, the ACK message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node; and applying modification information for one or more frequency domain parameters for at least one SRS resource a certain number of time slots after the time slot.

[0220] In the eleventh aspect, alone or in combination with one or more aspects of the first to tenth aspects, process 1100 includes sending one or more information sets for one or more frequency domain parameters associated with an SRS resource set or an SRS resource to a second network node, and a MAC-CE message activates an information set from the one or more information sets, wherein the information set includes modification information about a currently activated or semi-statically configured information set for at least one SRS resource.

[0221] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation of a MAC-CE message.

[0222] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the message is included in a DCI message not associated with scheduled communications.

[0223] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the DCI message is associated with DCI format 1_1 or 1_2.

[0224] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the DCI message indicates modification information for one or more frequency domain parameters.

[0225] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the modification information is associated with all SRS resources associated with the SRS resource set.

[0226] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1100 includes: receiving an ACK message from the second network node during a time slot, the ACK message indicating that the DCI message has been successfully decoded by the first network node; and applying modification information for one or more frequency domain parameters for at least one SRS resource a certain number of time slots after the time slot.

[0227] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the DCI message is associated with a DCI format associated with modifying an SRS configuration parameter.

[0228] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the SRS resource set is a non-periodic SRS resource set, and the message is included in a DCI message scheduling the transmission of the non-periodic SRS resource set.

[0229] In a twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the DCI message does not schedule any data communication.

[0230] In aspect 21, alone or in combination with one or more aspects from aspect 1 to aspect 20, a DCI message schedules a non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and the DCI message indicates modification information for one or more frequency domain parameters via one or more other fields of the DCI message.

[0231] In aspect twenty-second, alone or in combination with one or more aspects from aspect one to aspect twenty-first, the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of non-periodic SRS resource sets, and the DCI message indicates corresponding modification information for one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0232] In the twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of non-periodic SRS resource sets, and modification information for one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0233] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the DCI message includes modification information.

[0234] In the twenty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, the DCI message indicates one or more indexes associated with a data structure including multiple SRS configuration options, and the one or more indexes correspond to one modification information in the modification information.

[0235] In a twenty-sixth aspect, alone or in combination with one or more of the first to twenty-fifth aspects, a DCI message schedules one or more data communications.

[0236] In the twenty-seventh aspect, alone or in combination with one or more of aspects one to twenty-six, process 1100 includes sending an RRC configuration of multiple SRS triggering states associated with an SRS resource set to a second network node, wherein the multiple SRS triggering states are associated with different corresponding configurations of a set of one or more frequency domain parameters for at least one SRS resource set, and the DCI message indicates a triggered SRS triggering state from the multiple SRS triggering states associated with modification information for one or more frequency domain parameters.

[0237] In the twenty-eighth aspect, alone or in combination with one or more of aspects one to twenty-seven, process 1100 includes sending a MAC-CE message to a second network node to activate one or more SRS triggering states including an SRS triggering state, wherein the MAC-CE message indicates an association of the one or more SRS triggering states with a code point of an SRS request field of a DCI message.

[0238] In a twenty-ninth aspect, alone or in combination with one or more of the first to twenty-eighth aspects, the SRS resource set is a periodic SRS resource set, a semi-persistent SRS resource set, or an aperiodic SRS resource set.

[0239] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted in the process 1100 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks in the blocks of the process 1100 may be performed in parallel.

[0240] Fig.121 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network node, or a network node may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include a configuration application component 1208, etc.

[0241] In some aspects, the apparatus 1200 may be configured to perform Figures 6 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein (such as Fig.10 In some aspects, Fig.12 The apparatus 1200 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0242] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0243] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0244] The receiving component 1202 may receive an SRS configuration associated with an SRS resource set including one or more SRS resources from another network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The receiving component 1202 may receive a message indicating modification information from another network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters. The sending component 1204 may send an SRS to another network node using at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0245] The sending component 1204 can send an ACK message to the second network node during the time slot, the ACK message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node. The configuration applying component 1208 can apply the modification information for one or more frequency domain parameters for the SRS resource set a certain number of time slots after the time slot.

[0246] Receiving component 1202 can receive one or more sets of information for one or more frequency domain parameters associated with a set of SRS resources.

[0247] Transmitting component 1204 may transmit an ACK message to the second network node during the time slot indicating that the DCI message has been successfully decoded by the first network node.Configuration applying component 1208 may apply modification information for one or more frequency domain parameters for at least one SRS resource a number of time slots after the time slot.

[0248] Receiving component 1202 may receive, from a second network node, an RRC configuration of a plurality of SRS triggering states associated with an SRS resource set, wherein the plurality of SRS triggering states are associated with different respective configurations for a set of one or more frequency domain parameters for the SRS resource set.

[0249] Receiving component 1202 may receive a MAC-CE message from a second network node activating one or more SRS triggering states including an SRS triggering state, wherein the MAC-CE message indicates an association of the one or more SRS triggering states with a codepoint of an SRS request field of a DCI message.

[0250] Fig.12 The number and arrangement of components shown in are provided as examples. In practice, there may be Fig.12 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.12 Two or more components shown in may be implemented in a single component, or Fig.12 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The collection of (one or more) components shown in can perform the operations described by Fig.12 Another collection of components shown in the figure performs one or more functions.

[0251] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a network entity, or a network entity may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and sending component 1304. As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include one or more of a determining component 1308 and / or a configuration applying component 1310, etc.

[0252] In some aspects, the apparatus 1300 may be configured to perform Figures 6 to 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein (such as Fig.11 In some aspects, Fig.13 The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0253] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1306. The receiving component 1302 may provide the received communications to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described base stations.

[0254] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described base stations. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0255] The sending component 1304 may send an SRS configuration associated with an SRS resource set including one or more SRS resources to another network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set. The sending component 1304 may send a message indicating modification information to another network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one SRS resource in the one or more SRS resources from the set of one or more frequency domain parameters. The receiving component 1302 may receive an SRS from another network node using at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0256] Determining component 1308 can determine an SRS configuration associated with the SRS resource set.Determining component 1308 can determine modification information for one or more frequency domain parameters.

[0257] Receiving component 1302 can receive an ACK message from the second network node during the time slot, the ACK message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node.Configuration applying component 1310 can apply modification information for one or more frequency domain parameters for at least one SRS resource a certain number of time slots after the time slot.

[0258] Transmitting component 1304 may transmit one or more information sets for one or more frequency domain parameters associated with an SRS resource set or an SRS resource to a second network node.

[0259] Receiving component 1302 may receive an ACK message from the second network node during the time slot, the ACK message indicating that the DCI message has been successfully decoded by the first network node.Configuration applying component 1310 may apply modification information for one or more frequency domain parameters for at least one SRS resource a number of time slots after the time slot.

[0260] The transmitting component 1304 may transmit, to the second network node, an RRC configuration of a plurality of SRS triggering states associated with the SRS resource set, wherein the plurality of SRS triggering states are associated with different respective configurations of a set of one or more frequency domain parameters for at least one SRS resource.

[0261] The sending component 1304 can send a MAC-CE message to the second network node to activate one or more SRS triggering states including an SRS triggering state, wherein the MAC-CE message indicates an association of the one or more SRS triggering states with a codepoint of an SRS request field of a DCI message.

[0262] Fig.13The number and arrangement of components shown in are provided as examples. In practice, there may be Fig.13 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.13 Two or more components shown in may be implemented in a single component, or Fig.13 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The collection of (one or more) components shown in can perform the operations described by Fig.13 Another collection of components shown in the figure performs one or more functions.

[0263] The following provides an overview of some aspects of the disclosure:

[0264] Aspect 1: A method of wireless communication performed by a first network node, comprising: receiving an SRS configuration associated with an SRS resource set including one or more sounding reference signal (SRS) resources from a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; receiving a message indicating modification information from the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and sending an SRS to the second network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0265] Aspect 2: A method according to Aspect 1, wherein the set of one or more frequency domain parameters includes at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hopping, or at least one of an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0266] Aspect 3: The method according to any one of aspects 1 to 2, wherein the set of one or more frequency domain parameters includes one or more radio resource control (RRC) configuration parameters.

[0267] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the one or more frequency domain parameters include at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hopping or at least one of an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0268] Aspect 5: According to the method according to any one of Aspects 1 to 4, the one or more frequency domain parameters include: a transmit combination parameter and a transmit combination offset parameter associated with the frequency domain density.

[0269] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the one or more frequency domain parameters include: a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth index value, a second frequency domain hopping parameter associated with an SRS bandwidth column index value, and a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping.

[0270] Aspect 7: The method according to any one of aspects 1 to 6, wherein the message is included in a Medium Access Control (MAC) Control Element (MAC-CE) message.

[0271] Aspect 8: The method according to aspect 7, wherein the MAC-CE message indicates the modification information for the one or more frequency domain parameters.

[0272] Aspect 9: The method according to aspect 8, wherein the modification information is associated with all SRS resources associated with the SRS resource set.

[0273] Aspect 10: The method according to any one of aspects 8 to 9, wherein the modification information is associated with one or more inactivated SRS resource sets.

[0274] Aspect 11: The method according to any one of Aspects 7 to 10 further includes: sending an acknowledgment (ACK) message to the second network node during a time slot, the acknowledgment (ACK) message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node; and applying the modification information for the one or more frequency domain parameters for the at least one SRS resource in a certain number of time slots after the time slot.

[0275] Aspect 12: The method according to any one of Aspects 7 to 11 further includes: receiving one or more information sets for the one or more frequency domain parameters associated with the SRS resource set, and wherein the MAC-CE message activates an information set from the one or more information sets, wherein the information set includes the modification information about the currently activated or semi-statically configured information set for the at least one SRS resource.

[0276] Aspect 13: The method according to aspect 12, wherein at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation of a MAC-CE message.

[0277] Aspect 14: The method according to any one of aspects 1 to 6, wherein the message is included in a downlink control information (DCI) message that is not associated with data transmission scheduling.

[0278] Aspect 15: The method according to Aspect 14, wherein the DCI message is associated with DCI format 1_1 or 1_2.

[0279] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the DCI message indicates the modification information for the one or more frequency domain parameters.

[0280] Aspect 17: The method according to Aspect 16, wherein the modification information is associated with all SRS resources associated with the SRS resource set.

[0281] Aspect 18: The method according to any one of Aspects 14 to 17 further includes: sending an acknowledgment (ACK) message to the second network node during a time slot, the acknowledgment (ACK) message indicating that the DCI message has been successfully decoded by the first network node; and applying the modification information for the one or more frequency domain parameters for the at least one SRS resource in a certain number of time slots after the time slot.

[0282] Aspect 19: The method according to any one of aspects 14 to 18, wherein the DCI message is associated with a DCI format associated with modifying SRS configuration parameters.

[0283] Aspect 20: A method according to any one of Aspects 1 to 6, wherein the SRS resource set is a non-periodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message scheduling the transmission of the non-periodic SRS resource set.

[0284] Aspect 21: The method according to aspect 20, wherein the DCI message does not schedule any data communication.

[0285] Aspect 22: A method according to Aspect 21, wherein the DCI message schedules the non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message.

[0286] Aspect 23: A method according to Aspect 22, wherein the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource sets, and wherein the DCI message indicates corresponding modification information of the one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0287] Aspect 24: A method according to any one of Aspect 22, wherein the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource sets, and wherein the modification information for the one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0288] Aspect 25: A method according to any one of Aspects 21 to 24, wherein the DCI message includes the modification information.

[0289] Aspect 26: The method according to any one of aspects 21 to 25, wherein the DCI message indicates one or more indexes associated with a data structure including a plurality of SRS configuration options, and the one or more indexes correspond to the modification information.

[0290] Aspect 27: The method according to aspect 20, wherein the DCI message schedules one or more data communications.

[0291] Aspect 28: The method according to aspect 27 further includes: receiving a radio resource control (RRC) configuration of a plurality of SRS triggering states associated with the SRS resource set from the second network node, wherein the plurality of SRS triggering states are associated with different corresponding configurations of the set of the one or more frequency domain parameters for the at least one SRS resource, and wherein the DCI message indicates a triggered SRS triggering state associated with the modification information for the one or more frequency domain parameters from the plurality of SRS triggering states. wherein the DCI message indicates a triggered SRS triggering state associated with the modification information for the one or more frequency domain parameters from the plurality of SRS triggering states.

[0292] Aspect 29: The method according to Aspect 28 also includes: receiving a medium access control (MAC) control element (MAC-CE) message from the second network node to activate one or more SRS triggering states including the SRS triggering state, wherein the MAC-CE message indicates an association between the one or more SRS triggering states and a code point of the SRS request field of the DCI message.

[0293] Aspect 30: The method according to any one of Aspects 1 to 29, wherein the SRS resource set is a periodic SRS resource set, a semi-persistent SRS resource set or an aperiodic SRS resource set.

[0294] Aspect 31: A method of wireless communication performed by a first network node, comprising: sending an SRS configuration associated with an SRS resource set including one or more sounding reference signal (SRS) resources to a second network node, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; sending a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; and receiving an SRS from the second network node using the at least one SRS resource based on the modification information for the one or more frequency domain parameters.

[0295] Aspect 32: A method according to Aspect 31, wherein the set of one or more frequency domain parameters includes at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hopping, or at least one of an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0296] Aspect 33: The method according to any one of Aspects 31 to 32, wherein the set of one or more frequency domain parameters includes one or more radio resource control (RRC) configuration parameters.

[0297] Aspect 34: A method according to any one of Aspects 31 to 33, wherein the one or more frequency domain parameters include at least one of the following: a transmit combination parameter associated with a frequency domain density, a transmit combination offset parameter, a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth configuration row index value, a second frequency domain hopping parameter associated with an SRS bandwidth configuration column index value, a third frequency domain hopping parameter associated with indicating whether frequency hopping is enabled, the number of frequency hopping or at least one of an offset associated with frequency hopping, or one or more partial frequency detection parameters.

[0298] Aspect 35: A method according to any one of Aspects 31 to 34, wherein the one or more frequency domain parameters include: a transmit combination parameter and a transmit combination offset parameter associated with the frequency domain density.

[0299] Aspect 36: A method according to any one of Aspects 31 to 35, wherein the one or more frequency domain parameters include: a frequency domain shift parameter, a frequency domain position parameter, a first frequency domain hopping parameter associated with an SRS bandwidth index value, a second frequency domain hopping parameter associated with an SRS bandwidth column index value, and a third frequency domain hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, the number of frequency hopping, or an offset associated with frequency hopping.

[0300] Aspect 37: A method according to any one of aspects 31 to 36, wherein the message is included in a Medium Access Control (MAC) Control Element (MAC-CE) message.

[0301] Aspect 38: The method according to Aspect 37, wherein the MAC-CE message indicates the modification information for the one or more frequency domain parameters.

[0302] Aspect 39: The method according to Aspect 38, wherein the modification information is associated with all SRS resources associated with the SRS resource set.

[0303] Aspect 40: A method according to any one of aspects 38 to 39, wherein the modification information is associated with one or more inactivated SRS resource sets.

[0304] Aspect 41: The method according to any one of Aspects 37 to 40 further includes: receiving an acknowledgment (ACK) message from the second network node during a time slot, the acknowledgment (ACK) message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node; and applying the modification information for the one or more frequency domain parameters for the at least one SRS resource in a certain number of time slots after the time slot.

[0305] Aspect 42: The method according to any one of Aspects 37 to 41 further includes: sending one or more information sets for the one or more frequency domain parameters associated with the SRS resource set or the SRS resource to the second network node, and wherein the MAC-CE message activates an information set from the one or more information sets, wherein the information set includes the modification information about the currently activated or semi-statically configured information set for the at least one SRS resource.

[0306] Aspect 43: The method according to aspect 42, wherein at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation MAC-CE message.

[0307] Aspect 44: A method according to any one of aspects 31 to 36, wherein the message is included in a downlink control information (DCI) message not associated with scheduled communications.

[0308] Aspect 45: A method according to Aspect 44, wherein the DCI message is associated with DCI format 1_1 or 1_2.

[0309] Aspect 46: A method according to any one of Aspects 44 to 45, wherein the DCI message indicates the modification information for the one or more frequency domain parameters.

[0310] Aspect 47: The method according to Aspect 46, wherein the modification information is associated with all SRS resources associated with the SRS resource set.

[0311] Aspect 48: The method according to any one of Aspects 44 to 47 further includes: receiving an acknowledgment (ACK) message from the second network node during a time slot, the acknowledgment (ACK) message indicating that the DCI message has been successfully decoded by the first network node; and applying the modification information for the one or more frequency domain parameters for the at least one SRS resource in a certain number of time slots after the time slot.

[0312] Aspect 49: The method according to any one of Aspects 44 to 48, wherein the DCI message is associated with a DCI format associated with modifying SRS configuration parameters.

[0313] Aspect 50: A method according to any one of Aspects 31 to 36, wherein the SRS resource set is a non-periodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message scheduling the transmission of the non-periodic SRS resource set.

[0314] Aspect 51: The method according to aspect 50, wherein the DCI message does not schedule any data communication.

[0315] Aspect 52: A method according to Aspect 51, wherein the DCI message schedules the non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message.

[0316] Aspect 53: A method according to Aspect 52, wherein the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource sets, and wherein the DCI message indicates corresponding modification information of the one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0317] Aspect 54: A method according to Aspect 52, wherein the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource sets, and wherein the modification information for the one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

[0318] Aspect 55: A method according to any one of Aspects 51 to 54, wherein the DCI message includes the modification information.

[0319] Aspect 56: A method according to any one of Aspects 51 to 55, wherein the DCI message indicates one or more indexes associated with a data structure including a plurality of SRS configuration options, and the one or more indexes correspond to one of the modification information.

[0320] Aspect 57: A method according to any one of aspects 50 to 56, wherein the DCI message schedules one or more data communications.

[0321] Aspect 58: The method according to aspect 57 further includes: sending a radio resource control (RRC) configuration of multiple SRS triggering states associated with the SRS resource set to the second network node, wherein the multiple SRS triggering states are associated with different corresponding configurations of the set of one or more frequency domain parameters for the at least one SRS resource, and wherein the DCI message indicates a triggered SRS triggering state associated with the modification information for the one or more frequency domain parameters from the multiple SRS triggering states. wherein the DCI message indicates a triggered SRS triggering state associated with the modification information for the one or more frequency domain parameters from the multiple SRS triggering states.

[0322] Aspect 59: The method according to Aspect 58 further includes: sending a medium access control (MAC) control element (MAC-CE) message to the second network node to activate one or more SRS triggering states including the SRS triggering state, wherein the MAC-CE message indicates the association of the one or more SRS triggering states with the code point of the SRS request field of the DCI message.

[0323] Aspect 60: The method according to any one of aspects 31 to 59, wherein the SRS resource set is a periodic SRS resource set, a semi-persistent SRS resource set or an aperiodic SRS resource set.

[0324] Aspect 61: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.

[0325] Aspect 62: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 30.

[0326] Aspect 63: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 1 to 30.

[0327] Aspect 64: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

[0328] Aspect 65: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.

[0329] Aspect 66: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 31 to 60.

[0330] Aspect 67: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 31 to 60.

[0331] Aspect 68: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 31 to 60.

[0332] Aspect 69: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 31 to 60.

[0333] Aspect 70: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 31 to 60.

[0334] The foregoing disclosure provides illustration and description, but is neither exhaustive nor limiting to the scope of the present disclosure. For example, various aspects and examples are disclosed herein, but the present disclosure is not limited to the precise form in which such aspects and examples are described. Additionally, the terms aspect and example are used interchangeably. Modifications and variations may be made based on the above disclosure, or modifications and variations may be obtained from the practice of various aspects.

[0335] As used herein, the term "component" should be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, any combination thereof, or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, and other examples. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. The systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art understand that software and hardware can be designed to implement the technology described herein based on the present disclosure.

[0336] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0337] Although the specific combination of features is described in the claims and / or disclosed in the specification, these combinations do not limit the scope of the present disclosure to such specific combinations or features. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of each aspect includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0338] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly stated. In addition, as used herein, the articles "one" and "an" include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" includes one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to a project, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (wherein "A" can be information, conditions, factors, etc.) should be interpreted as "at least based on A", unless stated differently in particular.

Claims

1. A first network node for wireless communication, comprising: Memory; as well as one or more processors communicatively coupled to the memory, wherein the one or more processors are configured to: receiving, from a second network node, a sounding reference signal (SRS) configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; receiving, from the second network node, a message indicating modification information for dynamically reconfiguring one or more frequency domain parameters from the set of one or more frequency domain parameters associated with at least one of the one or more SRS resources; as well as and transmitting an SRS to the second network node using the at least one SRS resource included in the SRS resource set according to the modification information for the one or more frequency domain parameters.

2. The first network node of claim 1, wherein the message is included in a Medium Access Control (MAC) Control Element (MAC-CE) message. 3 . The first network node according to claim 2 , wherein the MAC-CE message indicates the modification information for the one or more frequency domain parameters.

4. The first network node of claim 2, wherein the one or more processors are further configured to: sending an acknowledgement (ACK) message to the second network node during the time slot, the acknowledgement (ACK) message indicating that the communication associated with the MAC-CE message has been successfully decoded by the first network node; and The modification information for the one or more frequency domain parameters for the at least one SRS resource is applied a certain number of time slots after the time slot.

5. The first network node of claim 2, wherein the one or more processors are further configured to: receiving one or more sets of information for the one or more frequency domain parameters associated with the SRS resource set, and The MAC-CE message activates an information set from the one or more information sets, wherein the information set includes the modification information about a currently activated or semi-statically configured information set for the at least one SRS resource.

6. The first network node according to claim 5, wherein at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation of a MAC-CE message.

7. The first network node according to claim 1, wherein the message is included in a downlink control information (DCI) message not associated with a data transmission schedule.

8. The first network node according to claim 7, wherein the DCI message indicates the modification information for the one or more frequency domain parameters.

9. The first network node of claim 7, wherein the one or more processors are further configured to: sending an acknowledgement (ACK) message to the second network node during a time slot, the acknowledgement (ACK) message indicating that the DCI message has been successfully decoded by the first network node; and The modification information for the one or more frequency domain parameters for the at least one SRS resource is applied a certain number of time slots after the time slot.

10. The first network node of claim 1, wherein the SRS resource set is an aperiodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message scheduling transmission of the aperiodic SRS resource set.

11. The first network node according to claim 10, wherein the DCI message does not schedule any data communication, wherein the DCI message schedules the non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message.

12. A first network node for wireless communication, comprising: Memory; as well as one or more processors communicatively coupled to the memory, wherein the one or more processors are configured to: sending, to a second network node, a sounding reference signal (SRS) configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; sending a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; as well as According to the modification information for the one or more frequency domain parameters, an SRS is received from the second network node using the at least one SRS resource.

13. The first network node according to claim 12, wherein the set of one or more frequency domain parameters comprises at least one of the following: transmit combination parameters associated with the frequency domain density, Send the combined offset parameter, Frequency domain shift parameters, Frequency domain location parameters, a first frequency domain frequency hopping parameter associated with the SRS bandwidth configuration row index value, a second frequency domain frequency hopping parameter associated with the SRS bandwidth configuration column index value, a third frequency domain frequency hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, a number of frequency hopping, or an offset associated with frequency hopping, or One or more partial frequency detection parameters.

14. The first network node of claim 12, wherein the SRS resource set is an aperiodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message that schedules transmission of the aperiodic SRS resource set, and wherein the DCI message does not schedule any data communication.

15. A first network node according to claim 14, wherein the DCI message schedules the non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message, and wherein the SRS triggering state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource set, and wherein the DCI message indicates corresponding modification information for the one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets, or the modification information for the one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

16. A method of wireless communication performed by a first network node, comprising: receiving, from a second network node, a sounding reference signal (SRS) configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; receiving, from the second network node, a message indicating modification information for dynamically reconfiguring one or more frequency domain parameters from the set of one or more frequency domain parameters associated with at least one of the one or more SRS resources; as well as and sending an SRS to the second network node using the at least one SRS resource according to the modification information for the one or more frequency domain parameters.

17. The method of claim 16, wherein the message is included in a Medium Access Control (MAC) Control Element (MAC-CE) message.

18. The method according to claim 17, wherein the MAC-CE message indicates the modification information for the one or more frequency domain parameters.

19. The method according to claim 17, further comprising: sending an acknowledgement (ACK) message to the second network node during a time slot, the acknowledgement (ACK) message indicating that a communication associated with the MAC-CE message has been successfully decoded by the first network node; as well as The modification information for the one or more frequency domain parameters for the at least one SRS resource is applied a certain number of time slots after the time slot.

20. The method of claim 17, further comprising: receiving one or more sets of information for the one or more frequency domain parameters associated with the SRS resource set, and The MAC-CE message activates an information set from the one or more information sets, wherein the information set includes the modification information about a currently activated or semi-statically configured information set for the at least one SRS resource.

21. The method of claim 20, wherein at least one of the one or more information sets is defined by a wireless communication standard as a default configuration option applicable before any activation MAC-CE message.

22. The method of claim 16, wherein the message is included in a downlink control information (DCI) message that is not associated with a data transmission schedule.

23. The method of claim 22, wherein the DCI message indicates the modification information for the one or more frequency domain parameters.

24. The method of claim 22, further comprising: sending an acknowledgement (ACK) message to the second network node during a time slot, the acknowledgement (ACK) message indicating that the DCI message has been successfully decoded by the first network node; as well as The modification information for the one or more frequency domain parameters for the at least one SRS resource is applied a certain number of time slots after the time slot.

25. The method of claim 16, wherein the SRS resource set is an aperiodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message scheduling transmission of the aperiodic SRS resource set.

26. A method according to claim 25, wherein the DCI message does not schedule any data communication, wherein the DCI message schedules the non-periodic SRS resource set via an SRS triggering state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message.

27. A method of wireless communication performed by a first network node, comprising: sending, to a second network node, a sounding reference signal (SRS) configuration associated with an SRS resource set including one or more SRS resources, the SRS configuration indicating information for a set of one or more frequency domain parameters associated with the SRS resource set; sending a message indicating modification information to the second network node, the modification information being used to dynamically reconfigure one or more frequency domain parameters associated with at least one of the one or more SRS resources from the set of one or more frequency domain parameters; as well as According to the modification information for the one or more frequency domain parameters, an SRS is received from the second network node using the at least one SRS resource.

28. The method of claim 27, wherein the set of one or more frequency domain parameters comprises at least one of the following: transmit combination parameters associated with the frequency domain density, Send the combined offset parameter, Frequency domain shift parameters, Frequency domain location parameters, a first frequency domain frequency hopping parameter associated with the SRS bandwidth configuration row index value, a second frequency domain frequency hopping parameter associated with the SRS bandwidth configuration column index value, a third frequency domain frequency hopping parameter associated with at least one of an indication of whether frequency hopping is enabled, a number of frequency hopping, or an offset associated with frequency hopping, or One or more partial frequency detection parameters.

29. The method of claim 27, wherein the SRS resource set is a non-periodic SRS resource set, and wherein the message is included in a downlink control information (DCI) message that schedules transmission of the non-periodic SRS resource set, and wherein the DCI message does not schedule any data communication.

30. A method according to claim 29, wherein the DCI message schedules the non-periodic SRS resource set via an SRS trigger state indicated by an SRS request field, and wherein the DCI message indicates the modification information for the one or more frequency domain parameters via one or more other fields of the DCI message, and wherein the SRS trigger state scheduling includes multiple non-periodic SRS resource sets of the non-periodic SRS resource set, and wherein the DCI message indicates corresponding modification information for the one or more frequency domain parameters for each non-periodic SRS resource set in the multiple non-periodic SRS resource sets, or the modification information for the one or more frequency domain parameters is associated with each non-periodic SRS resource set in the multiple non-periodic SRS resource sets.

Images