Method and apparatus for sounding reference signal flexibility enhancement

Abstract

Systems and methods for sounding reference signal (SRS) flexibility enhancements are presented. A wireless communication device can receive, from a wireless communication node, a configuration of a plurality of SRS parameter sets. The plurality of SRS parameter sets can each be associated with corresponding downlink control information (DCI) related information. The wireless communication device can receive, from the wireless communication node, a DCI. For an SRS transmission, the wireless communication device can identify, from the plurality of SRS parameter sets, a first SRS parameter set associated with a first DCI related information identified by the DCI.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for enhancing the flexibility of sensing reference signals (SRS). Background Technology

[0002] The standards organization 3GPP is currently specifying a new radio interface called 5G New Radio (5G NR) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and the User Equipment (UE). To facilitate the implementation of different data services and needs, the elements of 5GC (also known as network functions) have been simplified, some of which are software-based and some hardware-based, allowing them to be adapted as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues presented in the prior art, and to provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not as limiting, and that various modifications can be made to the disclosed embodiments by those skilled in the art who read this disclosure, while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication device can receive configurations of multiple SRS parameter sets from a wireless communication node. Each of the multiple SRS parameter sets can be associated with a corresponding downlink control information (DCI) related information. The wireless communication device can receive the DCI from the wireless communication node. For SRS transmission, the wireless communication device can identify a first SRS parameter set from the multiple SRS parameter sets that is associated with a first DCI related information identified by the DCI.

[0005] In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Downlink Control Channel (PDCCH). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Digital Interchange Channel (DCI). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Uplink Shared Channel (PUSCH). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Downlink Shared Channel (PDSCH). In some embodiments, the time offset may consist of a number of time slots or symbols.

[0006] In some embodiments, the first DCI-related information may include at least one of the following: the DCI format, the value of the New Data Indicator (NDI), the value of the Redundancy Value (RV), the value of the Hybrid Automatic Repeat Request (HARQ) process number, the value of the Time Domain Resource Allocation (TDRA), the value of the Frequency Domain Resource Allocation (FDRA), or the value of the frequency hopping flag. In some embodiments, the wireless communication device may identify one or more SRS resources or sets of SRS resources for SRS transmission based on the value of the SRS Request field of the DCI. In some embodiments, uplink transmission of data may not be scheduled by the DCI.

[0007] In some embodiments, the bit value of RV can form the most significant bit (MSB) of the first DCI-related information. In some embodiments, the bit value of NDI can form the least significant bit (LSB) of the first DCI-related information. In some embodiments, the bit value of the HARQ process number can form the most significant bit (MSB) of the first DCI-related information. In some embodiments, the bit value of NDI can form the least significant bit (LSB) of the first DCI-related information. In some embodiments, the bit order of the first DCI-related information from MSB to LSB may include the bit value of RV, the bit value of HARQ process number, and the bit value of NDI. In some embodiments, the bit order of the first DCI-related information from MSB to LSB may include the bit value of HARQ process number, the bit value of RV, and the bit value of NDI. In some embodiments, when uplink data transmission is scheduled by DCI, the wireless communication device can use a default SRS parameter set for SRS transmission.

[0008] In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the New Data Indicator (NDI) in the DCI. In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the Redundancy Value (RV) in the DCI. In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the Hybrid Automatic Repeat Request (HARQ) process number in the DCI.

[0009] In some embodiments, each SRS parameter set may be associated with a corresponding value of TDRA or FDRA. In some embodiments, scheduling information regarding data transmission and the first SRS parameter set may be jointly indicated by the values ​​of TDRA or FDRA in the DCI. In some embodiments, the location of SRS transmission may be associated with the location of Physical Uplink Shared Channel (PUSCH) or Physical Downlink Shared Channel (PDSCH) transmission. In some embodiments, the wireless communication device may receive a frequency hopping flag in the DCI from the wireless communication node. In some embodiments, the frequency hopping flag may indicate at least one of the following: a configured SRS repetition factor, or whether SRS frequency hopping in a time slot is enabled.

[0010] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication node can transmit the configuration of multiple SRS parameter sets to a wireless communication device. Each of the multiple SRS parameter sets can be associated with a corresponding downlink control information (DCI) related information. The wireless communication node can transmit the DCI to the wireless communication device. For SRS transmission, the wireless communication node can cause the wireless communication device to identify, from the multiple SRS parameter sets, a first SRS parameter set associated with the first DCI related information identified by the DCI.

[0011] In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Downlink Control Channel (PDCCH). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Digital Interchange Channel (DCI). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Uplink Shared Channel (PUSCH). In some embodiments, each of the SRS parameter sets may include a time offset to determine the time interval between SRS transmission and the Physical Downlink Shared Channel (PDSCH). In some embodiments, the time offset may consist of a number of time slots or symbols.

[0012] In some embodiments, the first DCI-related information may include at least one of the following: the DCI format, the value of the New Data Indicator (NDI), the value of the Redundancy Value (RV), the value of the Hybrid Automatic Repeat Request (HARQ) process number, the value of the Time Domain Resource Allocation (TDRA), the value of the Frequency Domain Resource Allocation (FDRA), or the value of the frequency hopping flag. In some embodiments, the wireless communication node may cause the wireless communication device to identify one or more SRS resources or sets of SRS resources for SRS transmission based on the value of the SRS Request field of the DCI. In some embodiments, uplink transmission of data may not be scheduled by the DCI.

[0013] In some embodiments, the bit value of RV can form the most significant bit (MSB) of the first DCI-related information. In some embodiments, the bit value of NDI can form the least significant bit (LSB) of the first DCI-related information. In some embodiments, the bit value of the HARQ process number can form the most significant bit (MSB) of the first DCI-related information. In some embodiments, the bit value of NDI can form the least significant bit (LSB) of the first DCI-related information. In some embodiments, the bit order of the first DCI-related information from MSB to LSB may include the bit value of RV, the bit value of HARQ process number, and the bit value of NDI. In some embodiments, the bit order of the first DCI-related information from MSB to LSB may include the bit value of HARQ process number, the bit value of RV, and the bit value of NDI. In some embodiments, when uplink data transmission is scheduled by DCI, the wireless communication device can use a default SRS parameter set for SRS transmission.

[0014] In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the New Data Indicator (NDI) in the DCI. In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the Redundancy Value (RV) in the DCI. In some embodiments, the first DCI-related information may be provided via a DCI field that does not exist simultaneously with at least a portion of the Hybrid Automatic Repeat Request (HARQ) process number in the DCI.

[0015] In some embodiments, each SRS parameter set may be associated with a corresponding value of TDRA or FDRA. In some embodiments, scheduling information regarding data transmission and the first SRS parameter set may be jointly indicated by the values ​​of TDRA or FDRA in the DCI. In some embodiments, the location of SRS transmission may be associated with the location of Physical Uplink Shared Channel (PUSCH) or Physical Downlink Shared Channel (PDSCH) transmission. In some embodiments, the wireless communication node may send a frequency hopping flag in the DCI to the wireless communication device. In some embodiments, the frequency hopping flag may indicate at least one of the following: a configured SRS repetition factor, or whether SRS frequency hopping in a time slot is enabled. Attached Figure Description

[0016] Various exemplary embodiments of the present solution are described in detail below with reference to the accompanying drawings or illustrations. The provided drawings are for illustrative purposes only and depict only exemplary embodiments of the present solution to facilitate the reader's understanding. Therefore, the drawings should not be considered as limitations on the breadth, scope, or applicability of the present solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0017] Figure 1 An example cellular communication network in which the techniques disclosed herein can be implemented, according to embodiments of the present disclosure, is shown;

[0018] Figure 2 Block diagrams of example base station and user equipment apparatuses according to some embodiments of the present disclosure are shown;

[0019] Figure 3 A table showing example time-division duplex (TDD) slot configurations according to some embodiments of the present disclosure is illustrated;

[0020] Figure 4 Example methods for redefining slot offset values ​​according to some embodiments of this disclosure are shown;

[0021] Figures 5-7 Various methods for indicating a triggering state using downlink control information (DCI) according to some embodiments of this disclosure are illustrated;

[0022] Figures 8-11 Various methods for identifying the values ​​of one or more SRS parameters using DCI, according to some embodiments of this disclosure, are illustrated;

[0023] Figures 12-13 Various methods for scheduling probe reference signal (SRS) transmissions using time offsets, according to some embodiments of the present disclosure, are illustrated;

[0024] Figure 14Example methods for configuring one or more candidate SRS parameter sets in a DCI format according to some embodiments of this disclosure are shown; and

[0025] Figure 15 A flowchart of an example method for enhancing SRS flexibility according to embodiments of the present disclosure is shown. Detailed Implementation

[0026] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use the present solution. As will be apparent to those skilled in the art upon reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and the present solution is not limited to the specific order or hierarchy presented, unless otherwise expressly stated.

[0027] The following acronyms are used throughout this disclosure:

[0028] acronym Full name 3GPP Third-generation partner project 5G 5G mobile network 5G-AN 5G access network 5G gNB Next-generation NodeB 5G-GUTI 5G- Globally unique temporary UE identifier AF Application Functions AMF Access and mobility management features AN Access Network ARP Assignment and Retention Priorities CA Carrier aggregation CM Connection mode CMR Channel measurement resources CSI Channel state information CQI Channel quality indicator CSI-RS Channel State Information Reference Signal CRI CSI-RS Resource Indicator CSS Public search space DAI Downlink Allocation Index DCI Downlink control information DL downlink or downlink DN Data Network DNN Data network name ETSI European Telecommunications Standards Association FR Frequency range GBR Guaranteed bit rate GFBR Guarantee the bit rate of traffic HARQ Hybrid Automatic Repeat Request MAC-CE Media Access Control (MAC) Controller Element (CE) MCS Modulation and coding schemes MBR Maximum bit rate MFBR Maximum flow bit rate NAS Non-access layer NF Network function NG-RAN Next-generation node wireless access node NR Next-generation RAN NZP Non-zero power OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access PCF Policy control function PDCCH Physical downlink control channel PDSCH Physical downlink shared channel PDU Grouped Data Unit PUCCH Physical uplink control channel PMI Precoding matrix indicator PPCH Physical broadcast channel PRI PUCCH resource indicator QoS Service quality RAN Wireless Access Network RAN CP Wireless Access Network Control Plane RAT Wireless access technology RBG resource block group RRC Radio Resource Control RV Redundant version SM NAS Session Management Non-Access Layer SMF Session management function SRS Detection reference signal SS Synchronization signal SSB SS / PBCH block TB Transport block TC Transmission configuration TCI Transmission configuration indicator TRP Transmit / Receive Point UCI Uplink control information UDM Unified Data Management UDR Unified Data Repository UE User equipment UL Uplink or uplink UPF User plane functionality USS UE-specific search space

[0029] 1. Mobile communication technology and environment

[0030] Figure 1 An example wireless communication network and / or system 100, in which the technologies disclosed herein may be implemented according to embodiments of this disclosure, is illustrated. In the following discussion, wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and user equipment device 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device) capable of communicating with each other via communication link 110 (e.g., a wireless communication channel), and cell clusters 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the respective geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0031] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described herein as non-limiting examples of "communication nodes" that can practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be capable of wireless and / or wired communication.

[0032] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics, which need not be described in detail herein. In one illustrative embodiment, as described above, system 200 can be used in applications such as... Figure 1 In the wireless communication environment 100, data symbols are transmitted (e.g., sent and received).

[0033] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0034] As those skilled in the art will understand, system 200 may further include, in addition to Figure 2Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend on the design constraints imposed on the overall system and the specific application. Those skilled in the art can implement such functionality in a suitable manner for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.

[0035] According to some embodiments, UE transceiver 230 may be referred to herein as "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred to herein as "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-duplex manner. The operation of the two transceiver modules 210 and 230 can be coordinated in time such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time such that while the uplink transmitter is coupled to the uplink antenna 232, the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250. In some embodiments, tight time synchronization exists, with a minimum guard time between changes in duplex direction.

[0036] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 that can be appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to specific standards and associated protocols in application. Rather, UE transceiver 230 and base transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0037] According to various embodiments, for example, BS 202 may be an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0038] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 214 and 236 respectively, such that processor modules 214 and 236 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 214 and 236. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 214 and 236 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions that will be executed by processor modules 214 and 236, respectively.

[0039] Network communication module 218 typically represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes (configured to communicate with base station 202). For example, network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). As used herein with respect to a specified operation or function, the terms “configured for,” “configured to,” and their variants refer to means of means, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0040] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is decomposed into seven sub-components or layers, each representing a conceptual collection of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes the transmission of computer data packets using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Media Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0041] 2. Systems and methods for enhancing the flexibility of reference signal detection (SRS)

[0042] In certain specifications (e.g., 3GPP specifications and / or other specifications), higher-layer configurations may determine or specify one or more parameters of the aperiodic sounding reference signal (SRS) resource and / or SRS resource set. If the higher-layer configuration determines the SRS parameters (e.g., parameters of the aperiodic SRS, parameters of the SRS resource set, and / or other SRS parameters), the wireless communication node (e.g., ground terminal, base station, gNB, eNB, or serving node) may not be able to change / modify / adjust one or more parameters of the aperiodic SRS and / or SRS resource set.

[0043] In some systems (e.g., LTE, NR, and / or other systems), SRS can be a common feature. In wireless communication systems, SRS can be used for uplink (UL) and / or downlink (DL) channel measurements. For example, SRS (and / or other signaling) can be used to acquire / obtain one or more UL channel state measurements and / or other measurements. In some systems with DL and UL time slots in the same frequency band (e.g., Time Division Duplex (TDD) systems and / or other systems), SRS can be used to acquire one or more DL channel state information (CSI) measurements and / or other measurements.

[0044] In some embodiments, SRS can be transmitted / broadcast / transmitted according to one or more time-domain types, such as periodic SRS, semi-persistent SRS, aperiodic SRS, and / or other types. The time-domain type can be configured and / or determined for an SRS resource set, wherein the SRS resource set includes one or more SRS resources. One or more SRS resources may include one or more frequency-domain and / or time-domain resources allocated for the SRS (e.g., location in the time domain, location in the frequency domain, and / or other resources). Radio Resource Control (RRC) signaling and / or other types of signaling can be used to configure periodic SRS transmissions. In some embodiments, Media Access Control Element (MAC-CE) signaling (or other types of signaling) can be used to configure / trigger semi-persistent SRS transmissions. One or more SRS configurations can be configured via RRC signaling and / or other types of signaling. One or more SRS configurations may include frequency resources, time-domain resources (e.g., the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols), periodicity, time offset (e.g., time slot offset), and / or other SRS configurations. In some embodiments, the SRS configuration corresponding to aperiodic SRS transmissions can be configured using RRC signaling, MAC-CE signaling, and / or other types of signaling. One or more aperiodic SRS transmissions can be activated / triggered / caused by downlink control information (DCI), such as device-specific DCI and / or public group DCI.

[0045] Compared to other time-domain SRS types (such as periodic SRS and / or semi-persistent SRS), aperiodic SRS offers greater flexibility (e.g., aperiodic SRS can be used / triggered / caused when necessary). SRS parameters can be configured / determined in each of multiple SRS resources and / or SRS resource sets. Therefore, each SRS resource and / or SRS resource set can be linked / associated with one or more SRS trigger states.

[0046] Wireless communication devices (e.g., UE, terminal, or serving node) can use the SRS request field (or other fields) of the DCI to indicate / provide / specify the value of the SRS trigger state. The value of the SRS trigger state (e.g., indicated by the DCI) can trigger one or more SRS resource sets linked / associated / associated with the value of the SRS trigger state. For example, RRC signaling (or other types of signaling) can configure five (or other numbers) aperiodic SRS resource sets (e.g., SRS resource set 0, SRS resource set 1, SRS resource set 2, SRS resource set 3, and SRS resource set 4). For example, among the five aperiodic SRS resource sets, SRS resource set 0 and / or SRS resource set 2 can be linked / associated / associated with SRS trigger state value 1. SRS resource set 1 and / or SRS resource set 3 can correspond to SRS trigger state value 2 (or other values), while SRS resource set 4 can be linked to SRS trigger state value 3 (or other values). If the SRS Request field of the DCI indicates an SRS trigger state value of 1, the wireless communication node can send / transmit / broadcast SRS resource set 0 and / or SRS resource set 2. For example, if the SRS Request field indicates an SRS trigger state value of 2, the wireless communication node can broadcast SRS resource set 1 and / or SRS resource set 3. If the SRS Request field specifies an SRS trigger state value of 3, the wireless communication node can transmit SRS resource set 4. In another example, if the SRS Request field indicates an SRS trigger state value of 0 (or another value), then no SRS resource set (e.g., SRS resource set 0, SRS resource set 1, and / or other resource sets) can be transmitted.

[0047] In some embodiments, the SRS request field of the DCI can be specified using at least two bits (or other number of bits) of the DCI. Therefore, although the SRS request field of the DCI can trigger an SRS resource set (e.g., a value linked to the SRS trigger state), higher-layer signaling (e.g., RRC signaling and / or MAC-CE signaling) can configure / determine the SRS parameters of the SRS resource set and / or the SRS parameters of the SRS resources included in the SRS resource set. The SRS parameters (e.g., of the SRS resource set and / or SRS resources) can include time offsets (e.g., multiple slots, multiple symbols, and / or other offsets) between the DCI (or Physical Downlink Control Channel (PDCCH)) and the triggered SRS resource (or SRS resource set), transmissionComb, resourceMapping, freqDomainPosition, freqDomainShift, freqHopping, and / or other SRS parameters.

[0048] Now for reference Figure 3This describes an example of a TDD timeslot format or configuration 300. In some embodiments, a TDD timeslot configuration may include five consecutive timeslots (e.g., timeslot 0, timeslot 1, timeslot 2, timeslot 3, and / or timeslot 4). Columns 304, 306, 308, 310, and 312 of the example TDD timeslot configuration 300 correspond to individual timeslots among the five consecutive timeslots. Column 302 of the TDD timeslot format 300 specifies the timeslot offset value between PDCCH and SRS transmissions. In this example, timeslots 0, 1, and / or 2 correspond to DL timeslots (e.g., D timeslots) that can support DL symbols (e.g., PDCCH and / or Physical Downlink Shared Channel (PDSCH)). Timeslot 3 may correspond to a special and / or flexible timeslot (e.g., S timeslot) that can support DL symbols and / or UL symbols (e.g., PDCCH, SRS, and / or other DL / UL symbols). Slot 4 may correspond to a UL slot (e.g., U slot), where the UL slot supports UL symbols (e.g., SRS and / or Physical Uplink Shared Channel (PUSCH)).

[0049] In some embodiments, RRC signaling (and / or other types of signaling) can be used to configure / determine the value of a slot offset (or other time offset). If the configured slot offset value corresponds to 0, the same slot (e.g., slot 3 and / or other slots supporting DL and UL symbols) can be used to transmit / transmit / broadcast PDCCH 314 (or other DL channels / symbols) and triggered SRS 316 (e.g., SRS resources and / or SRS resource sets). In example TDD slot format 300, PDCCH 314 and / or SRS 316 can be transmitted in slot 3 (e.g., S slot) or transmitted by using slot 3. Unless RRC signaling reconfigures the slot offset value (e.g., from 0 to another value), slot 4 (or other UL slots) may not be available for transmitting SRS 316 and PDCCH 314.

[0050] In another example, if the configured slot offset value corresponds to 1, slot 2 and / or slot 3 (or other slots supporting DL symbols) can be used to transmit PDCCH 314. If PDCCH 314 is transmitted using slot 2, slot 3 can be used to transmit SRS 316. If, alternatively, PDCCH 314 uses slot 3, SRS 316 can be transmitted using slot 4. The wireless communication device may not be able to trigger SRS 316 transmission by sending / transmitting PDCCH 314 using slot 0 and / or slot 1 (e.g., the RRC signaling update interval may be long, which could lead to PDCCH congestion).

[0051] In some embodiments, the configured time slot offset value may correspond to the value 2. If the configured time slot offset value corresponds to 2, then time slot 1 and / or time slot 2 (or other time slots supporting DL symbols) can be used to transmit PDCCH 314. If PDCCH 314 is transmitted using time slot 1, then time slot 3 can be used to transmit SRS 316. If, alternatively, PDCCH 314 uses time slot 2, then SRS 316 can be transmitted using time slot 4. In another example, if the configured time slot offset value corresponds to 3, then time slot 0 and / or time slot 1 can be used to transmit PDCCH 314. If time slot 0 is used to transmit PDCCH 314, then time slot 3 can be used to transmit SRS 316. If PDCCH 314 is transmitted using time slot 1, then SRS 316 can be transmitted using time slot 4. In some embodiments, the configured time slot offset value may correspond to the value 4. If the configured slot offset value is 4, then slot 0 and slot 4 can be used to transmit PDCCH 314 and SRS 316, respectively.

[0052] One or more SRS parameters (e.g., time offset) of SRS resources and / or SRS resource sets can be configured using higher-level signaling (e.g., RRC signaling). If one or more SRS parameters are configured via higher-level signaling, the DCI may be unable to change / update / adjust / modify one or more SRS parameters. The current level of SRS flexibility may not be able to meet the variability of traffic, channel conditions, wireless communication device mobility, and / or other parameters. For example, the systems and methods presented herein include novel methods for increasing / enhancing SRS flexibility by at least 25% (e.g., 35, 45, or other percentages).

[0053] A. Example 1

[0054] Now for reference Figure 4This describes an example method 400 for redefining slot offset values. In some embodiments, SRS flexibility can be enhanced by establishing novel / new / different definitions / interpretations of slot offset (sometimes called time offset) values. For example, a slot offset value can be interpreted / defined as indicating the slot offset between a PDCCH 414 transmission (or other DL channel / transmission) and the k-th or (k+1)-th slot available for SRS 416 transmission. If the slot offset value is configured (e.g., via RRC signaling) to a value of 0, the configured slot offset can be interpreted as indicating that the first available / allowed slot, starting from the slot of the PDCCH 414 transmission, is available for SRS 416 transmission. For example, if PDCCH 414 is transmitted using DL slots (e.g., slot 0, slot 1, and / or slot 2), the first available slot may correspond to slot 3. Therefore, slot 3 can transmit SRS 416. Available time slots can indicate the time slots in which one or more SRS symbols of an SRS resource and / or an SRS resource set can be transmitted / transmitted. Alternatively, available time slots can indicate the time slots in which all SRS symbols of an SRS resource or all SRS symbols of all SRS resources within an SRS resource set can be transmitted / transmitted. If a time slot offset parameter is configured for each SRS resource, multiple SRS resources within an SRS resource set may have different time slot offsets, and available time slots can be replaced by a set of available time slots that may include one or more time slot offsets. In this case, the set of available time slots can indicate the set of time slots in which all SRS symbols of all SRS resources within the SRS resource set can be transmitted / transmitted.

[0055] In another example, RRC signaling (or other types of signaling) can be used to configure / determine the slot offset value to a value of 1. Therefore, the configured slot offset value can be interpreted as indicating that a second available / allowed slot, starting from / from the slot where PDCCH 414 is transmitted, is available for transmitting SRS 416. For example, if PDCCH 414 is transmitted using slot 0 (or another DL slot), the second available slot could correspond to slot 4. Therefore, slot 4 can transmit / send / broadcast SRS416.

[0056] In some embodiments, the slot offset value can be interpreted / defined as indicating the first available slot after the k-th slot from the transmission of PDCCH 414. For example, if the slot offset value is k and PDCCH 414 is transmitted in slot n, then SRS 416 can be transmitted in the first available slot after / starting from slot n + k. Additional interpretations / definitions of the slot offset value can be considered. However, some methods designed to redefine the slot offset value may not provide sufficient SRS flexibility (e.g., at most 2 bits of DCI used to indicate the SRS request field). In some embodiments, increasing / expanding the size of the SRS request field in the DCI can improve SRS flexibility. Combining one or more methods, such as increasing the size of the SRS request field and / or reinterpreting the slot offset value, can further enhance SRS flexibility. However, combining one or more methods may result in additional DCI overhead.

[0057] In some embodiments, one or more DCI formats (e.g., DCI format 0_1 ​​and / or DCI format 0_2) may be used to trigger / cause UL data transmission. One or more DCI formats may include / provide / specify an SRS request field to trigger aperiodic SRS transmissions. In some embodiments, one or more DCI formats may include / provide / specify a CSI request field to trigger / cause a CSI report. In some embodiments, DCI format 0_1 ​​and / or DCI format 0_2 may trigger a CSI report and / or one or more SRS transmissions. Although a DCI format (e.g., DCI format 0_1 ​​and / or DCI format 0_2) may trigger / cause a CSI report and / or SRS transmission, a DCI format may not trigger / cause one or more UL data transmissions. In some embodiments, the value of the uplink shared channel (UL-SCH) indicator of the DCI may correspond to a value of 0 and / or other values ​​(e.g., corresponding to or indicating no UL data transmission). In another example, the value of the CSI request may correspond to a value other than 0 and / or other values ​​(e.g., with CSI report triggering). If the UL-SCH value is 0 and / or the CSI request value is not 0, the SRS request field and / or other DCI fields (e.g., New Data Indicator (NDI), Redundancy Version (RV), Hybrid Automatic Repeat Request (HARQ) process number, and / or other fields) can be used to trigger / cause at least one SRS transmission. Therefore, the SRS request field and / or other DCI fields can be used to indicate / provide / specify a specific SRS triggering state to trigger / cause a transmission corresponding to an SRS resource and / or a set of SRS resources. The SRS request field and / or other DCI fields can jointly trigger at least one SRS transmission.

[0058] Now for reference Figure 5This describes an example method 500 for using a DCI to indicate trigger states. In some embodiments, the DCI of DCI format 0_1 ​​and / or DCI format 0_2 may indicate / include an NDI field (or other fields). The DCI of certain DCI formats (e.g., DCI format 0_2) may exclude a HARQ process number field and / or an RV field. Therefore, one or more SRS transmissions can be triggered using / combining an NDI field and / or an SRS request field (e.g., at least M bits). Bits in the NDI field (e.g., at least 1 bit) may correspond to the most significant bit (MSB) (e.g., the MSB position of M bits), while bits in the SRS request field (e.g., one or more bits) may correspond to the least significant bit (LSB) (e.g., the LSB position of M bits). For example, combining the NDI and SRS request fields (e.g., at least 2 bits or other numbers of bits) can expand / increase the number of SRS trigger states from 4 to 8. For example, if an SRS request field (e.g., 2 bits) is used, up to 4 trigger states can be indicated. However, if both the NDI field and the SRS request field are used (e.g., 3 bits), up to 8 trigger states can be specified. In some embodiments, the SRS request field of DCI format 0_1 ​​can use 2 bits (or other numbers), while the SRS request field of DCI format 0_2 can use 1 or 2 bits. If DCI format 0_2 provides 1 bit for the SRS request field, some trigger states may not be available for SRS triggering (e.g., trigger states 2, 3, 6, and / or 7).

[0059] Now for reference Figure 6This describes an example method 600 for using a DCI to indicate a trigger state. In some embodiments, a DCI of a certain DCI format (e.g., DCI format 0_2) may include / use / provide 1 bit to indicate an SRS request field. A DCI may trigger / cause a CSI report and / or one or more SRS transmissions, but may not trigger one or more UL data transmissions (or other transmissions). If the DCI fails to trigger / cause one or more UL data transmissions, an NDI field (e.g., at least 1 bit) and / or an SRS request field (e.g., at least 1 bit) may indicate at least one of four trigger states (e.g., trigger states 0, 1, 2, and / or 3). For example, if the NDI field has a value of 1 and the SRS request field has a value of 0, the NDI and SRS request fields may together indicate a trigger state value of 2. In another example, if the NDI field has a value of 0 and the SRS request field has a value of 1, the NDI and SRS request fields may be combined to indicate a trigger state value of 1. In some embodiments, the bit value of the NDI field may correspond to an MSB (or other location), while the bit value of the SRS request field may correspond to an LSB (or other location).

[0060] Now for reference Figure 7This describes an example method 700 for using DCI to indicate trigger states. In some embodiments, the RV, HARQ process number, NDI, and / or SRS request fields can be used to indicate one or more trigger states (e.g., trigger states 0, 1, 2, 3, and / or other trigger states). For example, RV (e.g., 2 bits or other numbers of bits), NDI (e.g., 1 bit), and / or SRS request field (e.g., 2 bits) can be combined / used to specify one or more trigger states. For example, if the value of RV is 01, the value of NDI is 0, and the value of the SRS request field is 01, then each value can be combined to indicate a trigger state value of 9. For example, combining the RV (e.g., 2 bits), NDI (e.g., 1 bit), and / or SRS request (e.g., 2 bits) fields can expand / increase the number of SRS trigger states to 32. The bit values ​​of the RV, NDI, and / or SRS request fields can be ordered from MSB to LSB, where the bit value of the RV (or other DCI field) corresponds to the MSB, the bit value of the SRS request field (or other DCI field) corresponds to the LSB, and the bit value of the NDI (or other DCI field) is located between the MSB and LSB. The bit values ​​of the RV, NDI, SRS request fields, and / or HARQ process number can be ordered in one or more sequences from MSB to LSB. In some embodiments, the HARQ process number, NDI field, and / or SRS request field can be used / combined to trigger one or more SRS transmissions (e.g., to indicate one or more trigger states). The bit value of the HARQ process number (or other DCI field) can correspond to the MSB, while the bit value of the SRS request field (or other DCI field) can correspond to the LSB. The bit value of the NDI field (or other DCI field) can be located between the MSB and LSB. In some embodiments, the HARQ process number, NDI field, RV, and / or SRS request field can be used / combined to trigger one or more SRS transmissions (e.g., to indicate one or more trigger states). The bit values ​​of the HARQ process number, RV, and / or other DCI fields may correspond to the MSB. The bit values ​​of the SRS request and / or other DCI fields may correspond to the LSB. The bit values ​​of the HARQ process number, RV, NDI, and / or other DCI fields may be located between the MSB and LSB. In some embodiments, higher-level signaling (e.g., RRC signaling) may be used to configure the order of the DCI fields (e.g., from MSB to LSB).

[0061] In some embodiments, one or more SRS transmissions (e.g., SRS resources and / or SRS resource sets) may be associated with / linked to one or more DCI fields, such as the SRS request field, HARQ process number, RV, and / or NDI. In some specifications, the SRS request field may be extended from X1 bits (e.g., X1 = 2 bits in DCI format 0_1 ​​and / or X1 = 0, 1, or 2 bits in DCI format 0_2) to M bits (e.g., excluding bits used for the non-supplementary uplink (SUL) / SUL indicator). If the value of the DCI's UL-SCH indicator is 0 (e.g., no UL data transmission), then M may be greater than X1. Therefore, one or more DCI fields (e.g., RV, HARQ process number, and / or NDI) may be removed / eliminated to keep the DCI size less than or equal to a conventional one. For example, if M is greater than X1, one or more DCI fields (e.g., RV, HARQ process number, and / or NDI) may be excluded / removed from the DCI. Therefore, M-X1 may be less than or equal to the number of bits in the DCI field (e.g., RV, HARQ process number, and / or NDI).

[0062] If the number of trigger states increases (e.g., by combining information from one or more DCI fields), each SRS resource and / or SRS resource set can be linked / associated / related with additional trigger states, thus increasing / enhancing / improving SRS flexibility. For example, two SRS resource sets (e.g., resource set 1 and / or resource set 2) can be configured with the same SRS parameters except for slot offset (or other time offset). A first SRS resource set (e.g., resource set 1 configured with slot offset k1) can be linked / associated with SRS trigger state 1. Another SRS resource set (e.g., resource set 2 configured with slot offset k2) can be linked / associated with SRS trigger state 2. A PDCCH (or other DL channel / transmission) in slot n can trigger / cause the first SRS resource set (e.g., resource set 1) in slot n+k1 using SRS request value 1. A PDCCH in slot n can trigger / cause another SRS resource set (e.g., resource set 2) in slot n+k2 using SRS request value 2. In some embodiments, expanding the number of SRS trigger states can increase the number of SRS resources and / or SRS resource sets.

[0063] B. Example 2

[0064] In some embodiments, the DCI's UL-SCH indicator may have a value of 0 (e.g., indicating no UL data transmission). If the UL-SCH indicator is 0, higher-level signaling (e.g., RRC signaling, MAC-CE signaling, and / or other types of signaling) can configure one or more candidate values ​​for one or more SRS parameters (e.g., time offsets). For example, one or more candidate values ​​for slot offsets (or other time offsets) can be configured (e.g., via RRC signaling) for one or more SRS resources and / or SRS resource sets. NDI, RV, HARQ process number, and / or other DCI fields can provide values ​​that can be used to select / determine / identify / specify at least one slot offset value from the candidate values. The SRS request field (or other DCI fields) can provide values ​​that can specify / indicate which SRS resources and / or SRS resource sets are triggered / transmitted.

[0065] Now for reference Figure 8 This describes an example method 800 for using a DCI to identify the value of one or more SRS parameters. For example, RRC signaling (or other types of signaling) can configure eight candidate values ​​(e.g., k1, k2, k3, k4, k5, k6, k7, and / or k8) for the slot offset of an SRS resource and / or an SRS resource set. One or more fields of the DCI (e.g., RV and / or NDI) can be used to indicate / select / specify a slot offset value from the eight candidate values. For example, if the bit value of RV (e.g., 2 bits or other bits) is 01, and the bit value of NDI (e.g., 1 bit or other bits) is 0, then RV and NDI can jointly indicate the slot offset value k3. In another example, if the bit value of RV is 10 and the bit value of NDI is 1, then RV and NDI can specify the slot offset value k6. The bit value of RV (or other DCI field) can correspond to an MSB (or other location), while the bit value of NDI (or other DCI field) can correspond to an LSB (or other location). In other words, the bit order from MSB to LSB is the RV field of SRS, then the NDI field. In some embodiments, the SRS request field of DCI can indicate / specify a specific SRS resource and / or SRS resource set.

[0066] Now for reference Figure 9This describes an example method 900 for using a DCI to identify the value of one or more SRS parameters. In addition to the slot offset, one or more SRS parameters may also include parameters to inform the SRS frequency location, bandwidth, and / or other parameters. For example, one or more SRS parameters may include transmissionComb, resourceMapping, freqDomainPosition, freqDomainShift, freqHopping, and / or other SRS parameters. In some embodiments, one or more fields of the DCI (e.g., RV, NDI, and / or HARQ process number) can be used to indicate / select / specify a slot offset value from multiple candidate values ​​(e.g., 64 candidate values). For example, if the bit value of RV (e.g., 2 bits or other bits) is 01, the bit value of NDI (e.g., 1 bit or other bits) is 0, and the bit value of HARQ process number (e.g., 3 bits or other bits) is 001, then the combined DCI fields can collectively indicate a slot offset value of k11. In another example, if the bit value of RV is 10, the bit value of NDI is 1, and the bit value of HARQ process number is 001, the combined DCI fields can provide an indication / value to specify a slot offset value of k14. In some embodiments, the bit values ​​of RV and / or HARQ process number (or other DCI fields) form the MSB of DCI-related information, while the bit values ​​of NDI (or other DCI fields) form the LSB of DCI-related information. In some embodiments, the bit order of DCI-related information from MSB to LSB includes the bit value of RV, the bit value of HARQ process number, and the bit value of NDI. In other words, the order of the NDI, RV, and HARQ process number bits can be a combination of fields such as (HARQ process number, RV, NDI) or (RV, HARQ process number, NDI).

[0067] If the NDI, RV, and / or HARQ process number are excluded from the DCI, one or more candidate values ​​for one or more SRS parameters may become unavailable. For example, if the RV field is excluded from the DCI, it can be assumed that the bit value of the RV field corresponds to 00 (or other bit values). Therefore, the slot offset values ​​corresponding to RV bit values ​​01, 10, and / or 11 (e.g., k3, k4, k5, and / or other slot offset values) may be unavailable / invalid. One or more slot offset values ​​indicated by using RV bit value 00 (e.g., k1, k2, k9, k10, and / or other slot values) may be available / valid.

[0068] Now for reference Figure 10This describes an example method 1000 for using a DCI to identify the value of one or more SRS parameters. In some embodiments, one or more DCI fields (e.g., NDI, RV, and / or HARQ process number) may be excluded from the DCI. If at least one DCI field (e.g., RV) is excluded from the DCI, the bits corresponding to the excluded one or more DCI fields may not be considered when selecting a value for the SRS parameter (e.g., time offset) (e.g., from one or more candidate values). For example, if RV is excluded from the DCI, the HARQ process number (e.g., 3 bits) and / or NDI (e.g., 1 bit) may be used to select / identify a slot offset value from a list of candidate values. For example, if the bit value of NDI is 0 and the bit value of HARQ process number is 001, the combined DCI fields may collectively indicate the slot offset value k3.

[0069] In some embodiments, the NDI (or other DCI field) can be used to extend / add SRS trigger states. In some embodiments, the RV, HARQ process number, and / or other DCI fields can be used to select / identify / specify at least one of a plurality of candidate values ​​(e.g., slot offset value) for one or more SRS parameters. If the DCI triggers / schedules UL data, the first (or other) of the plurality of candidate values ​​(e.g., for one or more SRS parameters) can be used / selected (e.g., by default). In some embodiments, a novel / additional / new DCI field can be defined to select at least one of a plurality of candidate values ​​for one or more SRS parameters. If a new DCI field is defined, one or more bits of an existing DCI field (e.g., RV, HARQ process number, and / or NDI) can be empty / unused (e.g., to keep the size of the DCI less than or equal to a conventional one). In some embodiments, the new DCI field may not coexist with at least a portion of the NDI, RV, HARQ process number, and / or other DCI fields. If DCI fails to trigger / schedule UL data, new DCI fields may exist, while at least some of the NDI, RV, HARQ process number, and / or other DCI fields may no longer exist. If DCI triggers / schedules UL data, the NDI, RV, HARQ process number, and / or other DCI fields may exist as configured, while new DCI fields may not exist.

[0070] C. Example 3

[0071] In some embodiments, UL data may not be transmitted and / or CSI reporting may not occur (e.g., no uplink control information (UCI) to be reported in the PUSCH and / or the CSI trigger state value indicated by the DCI is 0). Therefore, other fields of the DCI (e.g., the Time Domain Resource Allocation (TDRA) field and / or the Frequency Domain Resource Allocation (FDRA) field) can be used / combined to increase / improve SRS flexibility. For example, N bits of the TDRA and / or FDRA fields can be used / combined with the SRS request field (or other DCI fields) to increase / extend the number of trigger states. In another example, N bits of the TDRA and / or FDRA fields can be used (e.g., together with other DCI fields) to select / identify / specify at least one value (e.g., from multiple candidate values) of one or more SRS parameters. Therefore, one or more SRS parameters can correspond to values ​​of the TDRA and / or FDRA fields.

[0072] In some specifications, a novel DCI field may replace the TDRA and / or FDRA fields. If the DCI fails to trigger a CSI report and / or UL data, the new DCI field may not coexist with at least part of the TDRA and / or FDRA fields. If the alternative DCI triggers / schedules UL data, the new DCI may not exist and / or the TDRA / FDRA fields may exist (e.g., as shown in specification 38.212). The TDRA and / or FDRA fields may be used when the DCI fails to trigger / cause UL data transmission and / or a CSI report.

[0073] Now for reference Figure 11This describes an example method 1100 for using a DCI to identify the value of one or more SRS parameters. In some embodiments, candidate values ​​for one or more configurations of one or more SRS parameters may be associated / related / linked with TDRA entries and / or FDRA entries. TDRA entries and / or FDRA entries may indicate / correspond to trigger state values ​​of TDRA and / or FDRA. For example, higher-level signaling (e.g., RRC signaling) may configure four slot offsets (e.g., t1, t2, t3, and / or t4) and / or other SRS parameters. Each configured slot offset may correspond to a TDRA trigger state value (e.g., values ​​0, 1, 2, and / or 3). For example, SRS slot offset t2 may be linked / related / related to TDRA trigger state value 1. Therefore, if the DCI indicates that the value of the TDRA trigger state is 1, the SRS slot offset may correspond to the value t2. The SRS request field (or other DCI fields) of the DCI may trigger / cause one or more SRS resources and / or SRS resource sets. In another example, if the DCI indicates / specifies that the TDRA trigger status value corresponds to 0, then the SRS slot offset value may correspond to t1. In some embodiments, the TDRA (and / or FDRA) trigger status value may indicate / specify at least one of the following: mappingType, time offset (e.g., k2) between PDCCH and PUSCH, startSymbolAndLength, and / or other information.

[0074] Slot offset is an illustrative example of at least one SRS parameter, and therefore, in the embodiments discussed herein, it can be replaced / substituted with any one or more SRS parameters. For example, TDRA, NDI, RV, and / or HARQ process numbers can be used to select / identify at least one set of SRS parameters from a candidate set of multiple configurations.

[0075] D. Example 4

[0076] Now for reference Figure 12This describes an example method 1200 for scheduling SRS transmissions using time offsets. In certain frequency bands (e.g., high-frequency bands), PDCCH (or other channel / transmission) transmissions can utilize beamforming techniques (e.g., to compensate for large path losses). However, the beam direction between wireless communication nodes and wireless communication devices may face obstructions (e.g., blocked by a human body). In some embodiments, PDCCH repetition (e.g., in different time slots) can be supported / used / enabled to enhance the reliability of PDCCH transmissions. For example, one or more transmit and receive points (TRPs) (e.g., TRP0 and / or TRP1) can send / transmit DCIs (e.g., DCI1 and / or DCI0) to schedule the same transmissions (e.g., PUSCH and / or other UL channels). A DCI (e.g., DCI0) from a first TRP (e.g., TRP0) can trigger at least one SRS transmission in time slot n + t1 (or other time slots). Another DCI (e.g., DCI1) from a second TRP (e.g., TRP1) can trigger / cause another SRS transmission in time slot n + t1 + 1 (or other time slots). If the same time offset (e.g., time slot offset t1) is notified / instructed / specified / provided for each SRS resource and / or SRS resource set, then each DCI (e.g., DCI0 and / or DCI1) can trigger a corresponding SRS transmission (e.g., in time slot n + t1 and / or time slot n + t1 + 1). Therefore, wireless communication devices may repeatedly transmit / send / broadcast the same SRS, and this may therefore lead to a waste of UL resources.

[0077] Now for reference Figure 13 This describes an example method 1300 for scheduling SRS transmissions using time offsets. In some embodiments, an SRS slot offset can be defined / interpreted as indicating a time offset between a PUSCH / PDSCH transmission (and / or other transmission) and an SRS transmission. The time offset can correspond to a slot offset, symbol offset, or some other duration offset. Figure 12 Four candidate SRS slot offsets (e.g., t1, t2, t3, and / or t4) can indicate / specify / provide the time interval between PUSCH transmission and SRS transmission. Therefore, candidate SRS slot offsets (e.g., t1, t2, t3, and / or t4) can include negative values ​​(e.g., SRS transmission can precede PUSCH transmission).

[0078] like Figure 13As shown, the SRS slot offset can indicate the time interval between a PUSCH transmission and an SRS transmission. In some embodiments, at least two DCIs (e.g., DCI0 and / or DCI1) can schedule the same PUSCH transmission. Therefore, at least two DCIs (e.g., DCI0 and / or DCI1) can simultaneously trigger an SRS resource and / or an SRS resource set. The wireless communication device can simultaneously (e.g., at the same time, in the same slot, and / or in the same OFDM symbol) receive / acquire at least two DCIs that trigger the same SRS resource and / or SRS resource set. Therefore, the wireless communication device can determine to send / transmit / broadcast an SRS resource and / or SRS resource set once (e.g., a single DCI is triggering the same SRS).

[0079] In some embodiments, the location of one or more data transmissions scheduled by a DCI (e.g., PUSCH and / or PDSCH) can be associated with / related to one or more SRS locations scheduled by the same DCI. This location can indicate / specify time-domain and / or frequency-domain locations. For example, in Figure 13 In this context, the time-domain location of an SRS (e.g., time slot n + k + t1) can be associated with the time-domain location of a PUSCH (e.g., time slot n + k). Similarly, the frequency-domain location of at least one SRS can be associated with / related to the frequency-domain location of at least one PUSCH / PDCSH (or other channel / transmission). For example, the frequency-domain start position of a PUSCH and / or PDSCH can be indicated / specified by the FDRA field of the DCI. The frequency-domain start position of a PUSCH / PDSCH can correspond to the frequency-domain start position of an SRS transmission (e.g., the frequency-domain start positions can be the same). In another example, a PDSCH / PUSCH transmission overlaps with an SRS transmission in the frequency domain.

[0080] In some specifications, the frequency hopping flag of the DCI can indicate / specify whether frequency hopping is enabled for a transmission (e.g., a PUSCH transmission or other transmission). In some embodiments, the frequency hopping flag (or other flags) can be used to increase the flexibility of SRS transmissions. For example, the frequency hopping flag can indicate / specify / provide frequency hopping information for SRS transmissions. In one example, if the value of the frequency hopping flag is 0 (or other value), SRS frequency hopping can be disabled in a time slot. In some embodiments, if the value of the frequency hopping flag is 0, RRC signaling (or other types of signaling) can configure / determine the SRS repetition factor R. In another example, if the value of the frequency hopping flag is 1 (or other value), SRS frequency hopping can be enabled in a time slot (e.g., the SRS repetition factor R is 1).

[0081] E. Example 5

[0082] In addition to DCI formats 0_1 and / or DCI format 0_2, other DCI formats (e.g., DCI format 1_1, DCI format 1_2, and / or DCI format 2_3) can trigger / cause one or more SRS transmissions. In some embodiments, one or more candidate SRS parameter sets (e.g., time offset and / or other values) can be configured for one or more SRS parameters. Each candidate SRS parameter set may correspond to a specific DCI format. A candidate SRS parameter set may include one or more candidate values ​​for at least one SRS parameter (e.g., time / slot offset). If an SRS resource and / or SRS resource set is triggered by a DCI, the candidate SRS parameter set corresponding to the DCI format can be used for the triggered SRS resource and / or SRS resource set.

[0083] Now for reference Figure 14 This describes an example method 1400 for configuring one or more candidate SRS parameter sets according to a DCI format. For example, four candidate SRS parameter sets (e.g., candidate set 0, candidate set 1, candidate set 2, and / or candidate set 3) can be configured for an SRS resource set (e.g., SRS resource set 0) according to a DCI format (e.g., DCI format 0_1, DCI format 0_2, DCI format 1_1, and / or DCI format 1_2). If SRS resource set 0 is triggered by DCI format 0_1, candidate set 0 can be used. If SRS resource set 0 is triggered by DCI format 0_2, candidate set 1 can be used. If SRS resource set 0 is triggered by DCI format 1_1, candidate set 2 can be used. If SRS resource set 0 is triggered by DCI format 1_2, candidate set 3 can be used. In another example, candidate set 0 may include a slot offset with a value of k0, while candidate set 1 may include a slot offset with a value of k1. In the same example, candidate set 2 may include a slot offset with a value of k2, while candidate set 3 may include a slot offset with a value of k3. If SRS resource set 0 is triggered by DCI format 0_1, candidate set 0 can be used, and therefore the time slot offset of k0 can be utilized. If SRS resource set 0 is triggered by DCI format 0_2, the time slot offset of k1 can be utilized (e.g., candidate set 1 can be used). If SRS resource set 0 is triggered by DCI format 1_1, the time slot offset of k2 can be used (e.g., candidate set 2 can be utilized). If SRS resource set 0 is triggered by DCI format 1_2, the time slot offset of k3 can be used (e.g., candidate set 3 can be utilized). One or more candidate sets (e.g., candidate sets 0 to 3) may include at least one value of one or more SRS parameters, such as values ​​for frequency domain location, values ​​indicating / enabling frequency hopping, and / or values ​​of other SRS parameters.

[0084] In some embodiments, the parameter values ​​transmitted by SRS (e.g., SRS resources and / or SRS resource sets triggered by DCI) may be associated / linked / related to at least one of the following DCI-related information: DCI format, NDI field, RV field, HARQ process number field, TDRA field, FDRA field, "frequency hopping flag" field, and / or other DCI-related information. If the SRS parameter is a time / slot offset, the time / slot offset may correspond to any of the interpretations in Embodiment 1.

[0085] F. Methods for enhancing the flexibility of the detection reference signal (SRS)

[0086] Figure 15 A flowchart of method 1550 for enhancing SRS flexibility is shown. Method 1550 can be used in conjunction with this document. Figures 1-14 The detailed description may be used to implement this method. In general, method 1550 may include a configuration for receiving multiple SRS parameter sets (1552). Method 1550 may include receiving DCI (1554). Method 1550 may include identifying a first SRS parameter set (1556).

[0087] Referring now to operation (1552), and in some embodiments, a wireless communication device (e.g., a UE) can receive / obtain configurations of multiple SRS parameter sets. In some embodiments, a wireless communication node (e.g., a BS) can send / transmit / broadcast (e.g., via RRC signaling and / or other types of signaling) the configurations of multiple SRS parameter sets to the wireless communication device. The wireless communication device can receive (e.g., via RRC signaling, MAC-CE signaling, and / or other types of signaling) the configurations of multiple SRS parameter sets from the wireless communication node. For example, the wireless communication device can receive / obtain one or more configuration values ​​for the time offset of SRS resources and / or SRS resource sets via RRC signaling. The configurations of multiple SRS parameter sets can each be associated / correlated / linked with corresponding DCI-related information. For example, the RV bit value of 00 and / or the NDI bit value of 0 can be associated with a time offset value corresponding to k1 time slots. In another example, the HARQ process number bit value of 001 and the NDI bit value of 0 can be associated with a time offset value corresponding to k3 time slots (or other time slot numbers). In some embodiments, each SRS parameter set may include a time offset (or other parameters) to determine a time interval. This time interval may correspond to the time interval between an SRS transmission (e.g., an SRS resource and / or an SRS resource set) and one of the PDCCH, DCI, PUSCH, PDSCH, and / or other channels / transmissions. In some embodiments, the time offset may be specified / defined by multiple time slots and / or multiple symbols.

[0088] Referring now to operation (1554), and in some embodiments, the wireless communication device can receive / obtain a DCI from a wireless communication node. The wireless communication node can send / transmit / broadcast the DCI to the wireless communication device. The DCI may include one or more DCI fields (e.g., NDI, RV, HARQ process number, and / or other DCI fields). The wireless communication device can use the values ​​of one or more DCI fields to identify / select at least one set of SRS parameters (e.g., time offset) for SRS transmission. In response to receiving / obtaining the DCI, the wireless communication device can identify a first set of SRS parameters for SRS transmission.

[0089] Referring now to operation (1556), and in some embodiments, the wireless communication device can identify / determine a first SRS parameter set (e.g., a candidate set) for SRS transmission (e.g., SRS resources and / or SRS resource sets). The wireless communication node can cause the wireless communication device to identify the first SRS parameter set for SRS transmission. In one example, the wireless communication device can identify the first SRS parameter set (e.g., a slot offset with a value of k4) by using one or more DCI fields (e.g., NDI, RV, HARQ process number, and / or other DCI fields). The wireless communication device can identify / select / determine the first SRS parameter set (e.g., a slot offset with a value of k4) from multiple SRS parameter sets (e.g., multiple slot offset values ​​ranging from k1 to k8). The first SRS parameter set can be associated / correlated with first DCI-related information identified by the DCI. For example, the SRS slot offset (or other SRS parameters of the first SRS parameter set) can be associated with the value of TDRA (or other DCI-related information). Therefore, if the DCI indicates / specifies the value of TDRA as 1 (or other value), the wireless communication device can identify the value of the SRS slot offset as t2 (or other value).

[0090] In some embodiments, the first DCI-related information may include the DCI format, the value of NDI, the value of RV, the value of HARQ process number, the value of TDRA, the value of FDRA, the value of frequency hopping flag, and / or other DCI fields. The wireless communication device may use the first DCI-related information (e.g., the values ​​of TDRA and / or FDRA) to identify / determine a first SRS parameter set. For example, the wireless communication device may use the bit value of RV (e.g., 00) and / or the bit value of NDI (e.g., 1) to identify the value of the time offset (e.g., k2 time slots and / or symbols). In another example, the wireless communication device may identify the first SRS parameter set (e.g., candidate set 0, candidate set 1, and / or other candidate sets) based on the type of DCI format (e.g., DCI format 0_1, DCI format 0_2, and / or other DCI formats). In some embodiments, the wireless communication device may identify / select one or more SRS resources and / or sets of SRS resources for SRS transmission. The wireless communication node may cause the wireless communication device to perform the identification / selection. Wireless communication devices can use the values ​​of the SRS Request field and / or other DCI fields of the DCI to identify one or more SRS resources and / or SRS resource sets. In some embodiments, uplink transmissions of data (e.g., PUSCH and / or other UL transmissions) may not be scheduled by the DCI (e.g., the value of the UL-SCH indicator in the DCI is 0). For example, if uplink transmissions are not scheduled by the DCI, the first DCI-related information may include the value of the NDI, the value of the RV, and / or the value of the HARQ process number.

[0091] In some embodiments, the bit value of RV can form the MSB of the first DCI-related information. The bit value of NDI can form the LSB of the first DCI-related information. Therefore, if the bit value of RV corresponds to 00 and / or the bit value of NDI corresponds to 1, the first DCI-related information can have a value of 001. The first DCI-related information (e.g., having a value of 001) can be associated with one or more SRS parameter sets (e.g., the slot offset value of k2). In some embodiments, the bit value of HARQ process number can form the MSB of the first DCI-related information. The bit value of NDI can form the LSB of the first DCI-related information. For example, if the bit value of NDI is 1 and / or the bit value of HARQ process number is 011, the first DCI-related information can have a value of 0111 (e.g., it can be associated with the slot offset value of k8). If the uplink transmission of data is not scheduled by DCI, the first DCI-related information can include RV, NDI, and / or HARQ process number.

[0092] In some embodiments, the bit order (from MSB to LSB) of the first DCI-related information may include the bit value of RV, the bit value of HARQ process number, and / or the bit value of NDI. For example, if RV, HARQ process number, and / or NDI have bit values ​​of 11, 000, and / or 1, respectively, then the first DCI-related information may have the value 100001. In some embodiments, the bit order (from MSB to LSB) of the first DCI-related information may include the bit value of HARQ process number, the bit value of RV, and / or the bit value of NDI. For example, if HARQ process number, RV, and / or NDI have bit values ​​of 001, 10, and / or 1, respectively, then the first DCI-related information may have the value 001101.

[0093] In some embodiments, the wireless communication device may use a default SRS parameter set for SRS transmission. The wireless communication device may use the default SRS parameter set when uplink transmission of data is scheduled by DCI. For example, if UL data is scheduled by DCI, a first configured (e.g., via RRC signaling) candidate SRS parameter set may be selected by default from one or more configured candidate SRS parameter sets. In some embodiments, first DCI-related information may be provided via a DCI field (e.g., a new DCI field) that does not exist simultaneously with at least a portion of the NDI, RV, HARQ process number, and / or other DCI fields. For example, if UL data is not scheduled by DCI, a new DCI field may provide first DCI-related information. If a new DCI field indicates / provides first DCI-related information, other DCI fields (e.g., NDI, RV, HARQ process number, and / or other DCI fields) may not exist. In some embodiments, each SRS parameter set may be associated / linked / related to corresponding values ​​of TDRA and / or FDRA. For example, the TDRA value of t2 may be associated with the SRS slot offset value (or other value) of t3.

[0094] In some embodiments, the first SRS parameter set and scheduling information regarding data transmission can be jointly indicated by the values ​​of TDRA and / or FDRA in the DCI. For example, N bits of the TDRA field and / or M bits of the FDRA field can be used / combined to indicate at least one configured (e.g., via RRC signaling) SRS parameter set from a plurality of configured SRS parameter sets. In some embodiments, the location of SRS transmissions (e.g., time-domain location and / or frequency-domain location) is associated with the location of Physical Uplink Shared Channel (PUSCH) and / or Physical Downlink Shared Channel (PDSCH) transmissions. For example, at least two DCIs (e.g., DCI0 and / or DCI1) can schedule the same data transmissions (e.g., PUSCH, PDSCH, and / or other transmissions) at time-domain locations corresponding to time slot n + k (or other time slots). The wireless communication device can receive at least two DCIs, where each DCI triggers SRS resources and / or an SRS resource set. Therefore, a wireless communication device can transmit / transmit at least one SRS resource and / or a set of SRS resources in the same time domain location (e.g., time slot n + k + t1). The time domain location of at least one SRS transmission (e.g., time slot n + k + t1) can be associated with the time location of the data transmission (e.g., time slot n + k).

[0095] In some embodiments, a wireless communication node can send / transmit a frequency hopping flag from the DCI to a wireless communication device. The wireless communication device can receive / obtain the frequency hopping flag from the wireless communication node. In some embodiments, the frequency hopping flag can indicate frequency hopping information used for SRS transmission. The frequency hopping flag can indicate one or more SRS parameters, such as a configured SRS repetition factor, or whether SRS frequency hopping is enabled in a time slot. For example, if the value of the frequency hopping flag is 0 (or another value), SRS frequency hopping can be disabled in a time slot. If the value of the frequency hopping flag is 1 (or another value), SRS frequency hopping can be enabled.

[0096] While various embodiments of the present solution have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various figures may depict example architectures or configurations, provided to enable those skilled in the art to understand the example features and functionality of the present solution. However, such individuals will understand that the present solution is not limited to the example architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0097] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of those elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, references to the first element and the second element do not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0098] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0099] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether these functionalities are implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and design constraints imposed on the overall system. Those skilled in the art can implement the described functionalities in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0100] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC) that may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, or any combination thereof. Logic blocks, modules, and circuits may further include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

[0101] If implemented as software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that enables the transfer of computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that is accessible to a computer.

[0102] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements to perform the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0103] Additionally, memory or other storage and communication components may be employed in embodiments of this solution. It should be understood that, for clarity, embodiments of this solution have been described above with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from this solution. For example, functionality shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means of providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0104] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A communication method, comprising: The configuration of receiving multiple sets of sounding reference signals (SRS) parameters from a wireless communication node by a wireless communication device, wherein each of the multiple SRS parameter sets is associated with a corresponding downlink control information (DCI) related information; The wireless communication device receives the DCI from the wireless communication node, wherein the uplink transmission of the data is not scheduled by the DCI; and For SRS transmission, the wireless communication device identifies a first SRS parameter set associated with the first DCI-related information identified by the DCI from the plurality of SRS parameter sets, wherein... The first DCI-related information includes the value of the New Data Indicator (NDI), the value of the Redundancy Value (RV), and the value of the Hybrid Automatic Repeat Request (HARQ) process number, wherein... The bit order of the first DCI-related information satisfies any of the following: The bit order of the first DCI-related information from the most significant bit (MSB) to the least significant bit (LSB) includes the bit value of the RV, the bit value of the HARQ process number, and the bit value of the NDI, wherein the bit value of the RV forms the MSB of the first DCI-related information, and the bit value of the NDI forms the LSB of the first DCI-related information; or The bit order of the first DCI-related information from MSB to LSB includes the bit value of the HARQ process number, the bit value of the RV, and the bit value of the NDI, wherein the bit value of the HARQ process number forms the MSB of the first DCI-related information, and the bit value of the NDI forms the LSB of the first DCI-related information.

2. The method according to claim 1, wherein, Each of the SRS parameter sets includes a time offset to determine the time interval between the SRS transmission and one of the following: Physical Downlink Control Channel (PDCCH), DCI, Physical Uplink Shared Channel (PUSCH), or Physical Downlink Shared Channel (PDSCH).

3. The method according to claim 2, wherein, The time offset consists of a certain number of time slots or symbols.

4. The method according to claim 1, wherein, The first DCI-related information also includes at least one of the following: the DCI format of the DCI, the value of the time-domain resource allocation (TDRA), the value of the frequency-domain resource allocation (FDRA), or the value of the frequency hopping flag.

5. The method according to claim 4, comprising: The wireless communication device identifies one or more SRS resources or sets of SRS resources based on the value of the SRS request field of the DCI for the SRS transmission.

6. The method according to claim 4, wherein, Each SRS parameter set is associated with a corresponding value of the TDRA or the FDRA.

7. The method according to claim 1, wherein, The location of the SRS transmission is associated with the location of the Physical Uplink Shared Channel (PUSCH) or Physical Downlink Shared Channel (PDSCH) transmission.

8. The method according to claim 1, comprising: The wireless communication device receives a frequency hopping flag from the wireless communication node in the DCI, wherein the frequency hopping flag indicates at least one of the following: the configured SRS repetition factor, or whether SRS frequency hopping in the time slot is enabled.

9. A communication method, comprising: The configuration of sending multiple sets of sounding reference signals (SRS) parameters from a wireless communication node to a wireless communication device, each of the SRS parameter sets being associated with a corresponding downlink control information (DCI) related information; The wireless communication node sends a DCI to the wireless communication device, wherein the uplink transmission of data is not scheduled by the DCI; and This causes the wireless communication device to identify, for SRS transmission, a first SRS parameter set associated with the first DCI-related information identified by the DCI from the plurality of SRS parameter sets, wherein The first DCI-related information includes the value of the New Data Indicator (NDI), the value of the Redundancy Value (RV), and the value of the Hybrid Automatic Repeat Request (HARQ) process number, wherein... The bit order of the first DCI-related information satisfies any of the following: The bit order of the first DCI-related information from the most significant bit (MSB) to the least significant bit (LSB) includes the bit value of the RV, the bit value of the HARQ process number, and the bit value of the NDI, wherein the bit value of the RV forms the MSB of the first DCI-related information, and the bit value of the NDI forms the LSB of the first DCI-related information; or The bit order of the first DCI-related information from MSB to LSB includes the bit value of the HARQ process number, the bit value of the RV, and the bit value of the NDI, wherein the bit value of the HARQ process number forms the MSB of the first DCI-related information, and the bit value of the NDI forms the LSB of the first DCI-related information.

10. The method according to claim 9, wherein, Each of the SRS parameter sets includes a time offset to determine the time interval between the SRS transmission and one of the following: Physical Downlink Control Channel (PDCCH), DCI, Physical Uplink Shared Channel (PUSCH), or Physical Downlink Shared Channel (PDSCH).

11. The method according to claim 10, wherein, The time offset consists of a certain number of time slots or symbols.

12. The method according to claim 9, wherein, The first DCI-related information also includes at least one of the following: the DCI format of the DCI, the value of the time-domain resource allocation (TDRA), the value of the frequency-domain resource allocation (FDRA), or the value of the frequency hopping flag.

13. The method of claim 12, comprising: This causes the wireless communication device to identify one or more SRS resources or sets of SRS resources based on the value of the SRS request field of the DCI for the SRS transmission.

14. The method according to claim 12, wherein, Each SRS parameter set is associated with a corresponding value of the TDRA or the FDRA.

15. The method according to claim 9, wherein, The location of the SRS transmission is associated with the location of the Physical Uplink Shared Channel (PUSCH) or Physical Downlink Shared Channel (PDSCH) transmission.

16. The method of claim 9, comprising: The wireless communication node sends a frequency hopping flag in the DCI to the wireless communication device, wherein the frequency hopping flag indicates at least one of the following: the configured SRS repetition factor, or whether SRS frequency hopping in the time slot is enabled.

17. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-16.

18. A communication device, comprising: At least one processor is configured to implement the method of any one of claims 1-16.

Images